Submit a ticketCall us

AnnouncementsSystem Monitoring for Dummies

Tired of monitoring failures disrupting the system, application, and service? Learn the key monitoring concepts needed to help you create sophisticated monitoring and alerting strategies that can help you save time and money. Read the eBook.

Get your free eBook.

Home > Success Center > VoIP & Network Quality Manager (VNQM) > VNQM Documentation > Previous Versions > IP SLA Manager 3.5.1 Release Notes

IP SLA Manager 3.5.1 Release Notes

Created by Beatrix.Turan, last modified by Caroline Juszczak on Mar 30, 2017

Views: 921 Votes: 0 Revisions: 5

Updated 11/16/2010

Formerly know as Orion VoIP Monitor, IP SLA Manager maintains the functionality of previous versions of VoIP Monitor and adds the ability to monitor eight additional types of IP SLA operations. IP SLA Manager offers extensive monitoring capabilities, presenting detailed realtime and historical statistics, for devices on your Network.


New Features in this Version

IP SLA Manager version 3.5.1 includes the following new features:

  • You can now create IP SLA operation dependecies. This enables you to prevent unnecessary alerts from operations associated with unresponsive devices. Operations will now show a status of "Unreachable" when one or more of the associated devices are down or unresponsive. For more information, see "How do I define and use dependencies in Orion NPM?"

    Note: You must have Orion NPM version 10.1 or later installed to use this feature.


Features of Previous Versions

IP SLA Manager version 3.5 includes the following new features:

  • You can now discover existing operations automatically.
  • Ability to monitor, report, and alert on two additional IP SLA operations, including:
    • ICMP Path Echo
    • ICMP Path Jitter
  • You can now group nodes by custom properties when adding nodes and when selecting source nodes for operations.
  • Simplified wizards enable you to configure operations to monitor much easier.
  • Added support for Owner and Tag fields in IP SLA operations.
  • Various performance enhancements.

IP SLA Manager version 3.1 included the following new features:

  • Ability to edit read/write credentials when adding nodes to IP SLA Manager
  • Automatically discover and add IP SLA-capable devices
  • Ability to view bidirectional jitter statistics
  • IP SLA Manager can now target external servers (nodes not monitored by Orion NPM) for TCP Connect, ICMP Echo, and UDP Echo operations when using custom paths
  • Ability to specify the source IP address for each operation

IP SLA Manager version 3.0 included the following new features:

  • Ability to monitor, report, and alert on eight additional IP SLA operations, including:
    • DHCP
    • DNS
    • FTP
    • HTTP
    • ICMP Echo
    • TCP Connect
    • UDP Echo
    • UDP Jitter
  • Easily configure IP SLA operations on multiple Cisco IOS devices at the same time using the intuitive web console
  • View IP SLA operation status on your custom Orion network maps
  • Ability to alert on all IP SLA operation thresholds and status
  • Dozens of new IP SLA operation historical reports have been added
  • View stacked bar charts showing the overall health of operations
  • Detailed HTTP operation statistics that breaks down the time between DNS resolution, transaction, and opening the connection

VoIP Monitor version 2.1 included the following new features:

  • Ability to group your VoIP equipment for greater ease of use
  • You can now assign Multi Protocol Label Switching (MPLS) Virtual Routing and Forwarding (VRF) names
  • Ability to assign a specific voice codec at the site level
  • You can specify voice path source by interface IP
  • Ability to assign multiple devices as a site at one time

VoIP Monitor version 2.0 included the following features:

  • Support for SNMP v3 devices
  • Improved navigation and usability
  • Manual configuration of call paths
  • More secure, restricted use of read/write credentials
  • Support for multiple VoIP pollers
  • Additional CallManager data resources
  • CallManager alerts
  • New resource gauges
  • Improved performance and scalability

VoIP Monitor version 1.0 included the following features:

  • Performance metrics of jitter, latency, packet loss for sites and call paths
  • Up-to-the-minute calculation of Mean Opinion Score (MOS) for sites and call paths
  • Automatic configuration of Cisco IOS routers for IP SLA operation
  • Call manager performance statistics, including measures of registered and unregistered phones and gateways, interface traffic, and CPU load
  • Resources specifically tailored to monitoring Cisco CallManager and CallManager Express devices
  • Full integration with Orion Network Performance Monitor, providing a customizable web console and easily configurable alerting and reporting engines


Fixes in this Release

This release of Orion IP SLA Manager includes the following fixes:

Version 3.5.1

  • IP SLA Manager now shows all IP SLA operations when grouped by source while viewing in Internet Explorer versions 7 and 8.
  • Test packets are now sent with the correct data size for all codecs.
  • The IP SLA Manager Services resource now shows the correct "Last Registered" time for all polling engines.

Version 3.5

  • IP SLA Manager now polls the correct MIB for HTTP operations when verifying operations status.
  • Historical UDP Jitter reports no longer display no results.
  • Operation availability charts no longer indicate warning when stats are below warning thresholds.
  • The Events resource on the Operations Details page now displays time using the server's time zone instead of UTC.
  • The correct view is now displayed when previewing while editing a copied version of another view.
  • Operations in the Operation Selection page are now organized by Operation Type.
  • You can now customize values on the Y-axis for IP SLA graphs.
  • You can now see IP addresses for selected nodes when adding nodes to IP SLA Manager.
  • Improved load balancing algorithms.
  • You can now group by custom properties when adding nodes to IP SLA Manager.
  • IP SLA Manager now polls the correct MIB for UPD Jitter operations when verifying operations status.
  • Scaling has been fixed so that peaks no longer appear off the screen on custom charts.
  • Unselected parameters are no longer being cleared when editing multiple operations at once.
  • Packet Loss gauges no longer show a range of 0-100%.

Version 3.1

  • You can now upgrade from VoIP Monitor 2.0.2.
  • IP SLA Manager can now be installed on Windows 2008 R2.
  • Improvements have been made in the timestamp algorithm to accommodate a bug in the Cisco 12.2 IOS.
  • Operation status no longer indicates "warning" instead of "critical" when the completion time has exceeded the critical threshold.
  • After changing Cisco CallManager credentials, IP SLA Manager no longer uses the old credentials.
  • After upgrading from VoIP 2.1, the ability to edit threshold values in some gauges no longer become disabled.
  • Clicking Delete to remove an additional poller on the Collector Service resource no longer causes the service to stop responding.

Version 3.0

  • Additional websites are no longer required to be on the same domain as the primary IP SLA installation.
  • When adding infrastructure nodes, the page no longer refreshes when selecting an interface.
  • You can now alert on unregistered phones.
  • You no longer encounter an error when adding a CallManager device on an additional web server installation.
  • The 95th Percentile on MOS Min/Max/Avg charts has been replaced with 5th Percentile because of the reversed logic of MOS.
  • Resolved an issue where several "deadlock" events would be encountered over a short period of time.
  • The IP SLA Manager component of additional pollers no longer looks for an IP SLA license.


Version 2.1

  • The Call Manager Connected Phones graph now includes all appropriate default time frame options.
  • You can no longer add a device with a down status as a Call Manager device.
  • "VoIP Auto-Configured Call Path Configuration" page is no longer displayed when VoIP Monitor has no created call paths.
  • IP SLA operations using a custom codec wont be recreated when the global codec is changed.
  • All related call paths (IP SLA operations) are now deleted when the associated site is deleted.
  • Call Paths that are created with invalid IP addresses can no longer be created.
  • Integration: NetFlow performance monitor counters are no longer deleted after installing IP SLA Manager on a server with NetFlow Traffic Analyzer installed.
  • Polling is no longer interrupted when the database and poller operate in different time zones.
  • The MOS score chart maximum has been reduced from 10 to 5.
  • The "Access denied" error message that is sometimes displayed on graphs has been resolved.
  • Routers that only support SNMP v1 can no longer be designated as VoIP devices.
  • IP SLA Manager no longer recognizes Cisco Unified Call Manager (CUCM) version 6.1 as Call Manager Express.
  • Latency and jitter graphs now properly scale the Y-axis.
  • MOS graphs now display data when selecting a period of less than 24 hours.
  • The values of scale tic marks on the Y-axis on MOS and Phone charts are now aligned properly.
  • The VoIP Thwack resource in now listed properly within the VoIP Summary resources list.

Version 2.0.2

  • Fixed a problem with the 2.0.1 installer that failed to update a previous install if it was not installed in the default drive/folder location.
  • Resolved an issue where sites could not be added using a read/write community string after upgrading from 2.0.1.

Version 2.0.1

  • The ability to add devices via SNMPv3 has been implemented.
  • Fixed issue where upgrading from an evaluation version to Orion 9.1 would cause errors.
  • Resolved the issue where IP SLA Manager would stop checking on call paths that were labeled as misconfigured.
  • Corrected an issue where a failed IP SLA operation would show a status of "OK".

Version 2.0

  • Multiple issues with the user interface, including format inconsistencies, incorrect error messages, and unordered listing of elements in resources, have been fixed.
  • An issue where the configuration wizard was not properly parsing dates in non-US formats has been fixed.
  • IP SLA Manager now correctly tests devices for IP SLA-compatibility. As a result, IP SLA Manager is now able to add any valid IP SLA-enabled device.
  • The Last XX VoIP Events resource currently honors configured account and view limitations.
  • IP SLA Manager now properly handles the lifetime reset of IP SLA operations on SNMPv1 devices.
  • Issues causing the failure of data collection from SNMPv1 devices have been fixed.
  • The configuration wizard no longer displays twice when completing a new installation of IP SLA Manager.
  • The IP SLA Manager website no longer fails when displaying a VoIP interface that does not have a parent node.
  • IP SLA Manager now correctly reschedules and recreates expired IP SLA operations.
  • Data values in the CallManagers resource now link directly to the corresponding CallManager view.
  • IP SLA Manager can now delete configured hubs from the IP SLA Manager Call Paths page without error.
  • The CallManager resource on the CallManager view now lists percentage values as whole numbers.
  • Call Path gauges now show Packet Loss values as whole numbers.
  • Licensing required for both the installation of an additional VoIP poller and the installation of VoIP on an Orion web-only server now functions correctly.
  • The Call Paths resource on the VoIP Summary View is now better able to handle larger call path lists.


Installing IP SLA Manager

The server that you use to host IP SLA Manager must also support an installation of Orion Network Performance Monitor version 9.5 SP4 or higher. IP SLA Manager does not require any additional resources beyond those required for the underlying implementation of Orion NPM.

To install IP SLA Manager:

  1. Shut down any Orion NPM applications that you may have running.
  2. Run the installation executable.



  • If you are upgrading, back up your Orion database before you install IP SLA Manager, to ensure that none of your data is lost during the upgrade.
  • When upgrading to Orion NPM version 10.1, you must install Orion IP SLA Manager version 3.5.1 on your primary and any additional servers before upgrading Orion.
  • IP SLA Manager does not support the use of case-sensitive database servers.


Upgrading from VoIP Monitor to IP SLA Manager

Upgrading from a previous version of IP SLA Manager or from VoIP Monitor does not require you to uninstall your current installation. To upgrade IP SLA Manager, install IP SLA Manager normally. None of your historical data or customized settings will be lost in the process. 


  • Backup your Orion database before you install IP SLA Manager, to ensure that none of your data is lost during the upgrade.
  • When upgrading from VoIP Monitor, you must have VoIP Monitor 2.0.2 or later installed before upgrading to the latest version of IP SLA Manager.
  • If you have a large amount of VoIP and CallManager data, the upgrade may take more than 30 minutes to an hour to complete.
  • You must upgrade any additional web servers or additional polling engines prior to upgrading your base installation.


IP SLA Manager and Additional Polling Engines

In order for IP SLA Manager statistics to be properly recorded by additional polling engines, IP SLA Manager must be installed on every additional polling engine you are running. To install IP SLA on an additional polling engine, run the IP SLA Manager setup program on the additional polling engine server. The IP SLA Manager setup program recognizes the type of server on which you are installing (additional or primary), and will install appropriately.

Note: For an additional polling engine to properly process IP SLA data, you must install the same version of IP SLA Manager on the additional polling engines as the version running on the primary polling engine.


Adding Devices to IP SLA Manager

To add a device to IP SLA Manager, the device must already be monitored by Orion NPM. The device must also be a Cisco device that supports SNMP v2 or v3. To confirm that the Cisco IOS release for your device supports IP SLA operations, visit the Cisco Feature Navigator, click Search by Feature, and then select IP SLAs - DHCP Operation.


Changing the Source Node IP Address

With IP SLA Manager you have the ability to change the source node IP address certain IP SLA operations use. For example, a node has three outbound interfaces with three different IP addresses. You can effectively designate which of these IP addresses will be used as the source IP address for operations created on that node. The designated IP address will be used for the following IP SLA operation types:

  • DHCP
  • FTP
  • HTTP
  • ICMP Echo
  • TCP Connect
  • UDP Echo
  • UDP Jitter
  • VoIP UDP Jitter

To change the source node IP address, edit the node in IP SLA Node Management, type then new address the IP Address field, and then click Save.


Migrating Reports to Another IP SLA Manager Installation

Custom reports that you have created for a standard installation of IP SLA Manager are easily migrated to a second IP SLA Manager installation that is typically an Additional Poller. The following procedure copies existing reports from one IP SLA Manager installation to another.

To migrate IP SLA Manager reports from one installation to another:

  1. Open the Orion Reports folder, located in Program Files\SolarWinds\Orion\ on your original IP SLA Manager server.
  2. Select the reports you want to copy to your second IP SLA Manager server, using Ctrl+Click or Shift+Click as necessary, and then click Edit > Copy.
  3. Locate your second IP SLA Manager server on your network, and then open its Orion Reports folder, located in Program Files\SolarWinds\Orion\.
  4. Click Edit > Paste to paste your reports in the Reports folder on your second IP SLA Manager server.

Your original VoIP reports are now available to your second IP SLA Manager installation.


Using Hostnames for External Targets

When using hostnames instead of IP addresses for external targets, the source node of the operation must be able to successfully resolve the hostname for the operation to be successful.


Known Issues

The following issues may arise in your installation of IP SLA Manager. These are known issues that are being addressed for a future release.

  • The VoIP Call Path resource indicates invalid latency thresholds when highlighting values in red. This resource does not use the latency thresholds configured when editing individual IP SLA Operations as it should. Instead, the resource uses an old global threshold setting that is no longer used by IP SLA Manager.
  • When customizing the IP SLA Operation Details page, clicking the Preview button results in an error.
  • You cannot add the Operation Availablity resource when editing the Custom Object resource.
  • Old IP SLA jobs are not deleted after configuring to the new database format and sometimes after upgrading from 3.5 to 3.5.1
  • When the number of open telnet connections are limited on a router, results may take longer than expected to appear.
  • Operations running on devices using a time zone code set to something other than UTC will show an incorrect time offset. The time zone will be considered to be UTC+0. Consider the following work-arounds:
    • Change the time zone code on the device to UTC format.
    • Modify the ipsla.timezones.xml file located in the C:\Program Files\SolarWinds\Orion\VoIP Monitor folder and add a new time zone using the example provided with an offset in minutes. Restart the Orion Module Engine and Job Engine.
  • CLI operations without read/write SNMP credentials cannot be deleted. To work around this issue, specify the read/write community string for the operations you want to delete before deleting them.
  • Hops are not displayed for ICMP Path Echo operations when the operations have been manually created with an invalid configuration. In this situation, the operation status is still displayed as Up, but will only report the entire round trip time instead of each individual hop.
  • Using > characters in graph names causes rendering failures. To work around this issue, do not use the > character in your graph names.
  • IP SLA Manager only reports what the network devices are reporting. In some cases, path operations will not show all hops in a path or show one hop more than once because the device is reporting these hops inaccurately.
  • URLs that have uppercase letters for "ftp" and "http" are not processed properly. When creating or editing IP SLA operations, type URLs using lowercase letters for ftp and http. For example, instead of HTTP://
  • Reports that include details from two identical operations will only list one instance the operation.
  • If the SolarWinds Information service is stopped, IP SLA web resources may display SQL errors.
  • IP SLA Manager will continue to poll and display IP SLA operation data after unmanaging associated nodes.
  • Additional pollers may indicate a "down" status when the poller is actually up and running on the Collector Services resource.
  • The Operation Availability resource does not have an Edit button to allow users to configure the resource and specify a date range.
  • There is not a way to change the operation number of an existing manual operation created by the user.
  • When editing IP SLA Node properties, clicking Use Default does not set the source IP address to the IP address assigned to the Orion node.
  • Cisco Call Manager version 4.1 is not fully supported at this time.
  • Administrative functions may be limited if your IP SLA Manager server and your Orion NPM server are not in the same domain. SolarWinds recommends that you install IP SLA Manager on the same server as Orion NPM.
  • An SQL exception may occur when you try to open IP SLA Manager on an additional Orion Web Console if the Orion server hosting the shared database does not also have IP SLA Manager installed. SolarWinds recommends that you not install IP SLA Manager on an additional Orion Web Console unless the original Orion server is also hosting IP SLA Manager.
  • German-specific characters may not display correctly.



Last modified


This page has no custom tags.