Congratulations on your purchase of SolarWinds Orion Network Performance Monitor (Orion NPM). Orion NPM provides a comprehensive fault and performance monitoring platform that allows you to collect and view availability and both realtime and historical statistics directly from your web browser. While monitoring, collecting, and analyzing data from routers, switches, firewalls, servers, and any other SNMP- or WMI-enabled devices, Orion NPM successfully offers a simple-to-use, scalable network monitoring solution for IT professionals managing any size network.

 Note: If you have applied Service Packs or Hotfixes to your product, they were delivered with readme.txt files. These files contain fixes that supercede the information found in the Release Notes.

Why Install this Version

In keeping with SolarWinds' commitment to provide a comprehensive fault and network performance monitoring platform that scales with your network and expands with your network management needs, this version of Orion NPM introduces a number of significant enhancements to improve performance and provide greater stability in more demanding environments.

New Orion NPM Features

Orion NPM version 10.2.1 provides the following new features:

• NPM can now monitor Cisco UCS devices over https.

New Orion Core Features

Orion Core version 2011.2.1 is a service release, providing no new features.

New Orion NPM Fixes

Orion NPM version 10.2.1 includes the following fixes and updates:

• Network Sonar Discovery is now capable of adding all interfaces on a single device when multiple interfaces are assigned the same index.
• The Auto-hide feature for Multiple Object Charts of interface data now function as designed.
• Network Sonar Discovery has been improved to better handle the addition of large amounts of interfaces for monitoring.
• Interface Last Status Change (ifLastChange) values are now recorded correctly in the SolarWinds database.

New Orion Core Fixes

Orion Core version 2011.2.1 includes the following fixes and updates:

• A condition preventing the Trap Viewer from displaying received SNMPv3 traps has been corrected.
• An error condition encoutered while loading the Manage Dependencies view has been fixed.
• NPM now supports the use of Windows-1251 encoding on the SolarWinds server operating system.
• An issue resulting in excessively high CPU utilization on SolarWinds NPM servers has been corrected.
• Polling engine status is now correctly reported when the polling engine and the SolarWinds database server are in different timezones.
• The Configuration Wizard now properly handles the pending deletion of unneeded files after completing an upgrade to NPM version 10.2.1.
• Received traps are now displayed correctly in the order requested in the web console.
• The Syslog Service is now able to properly handle filters that use regular expressions.
• A correction script in this version of NPM properly handles the fact that different Cisco IOS versions may use different OIDs to report the same CPU utilization statistics.
• The Syslog Service is now able to properly parse Syslog messages that use IPv6 addresses.
• NPM now properly respects account limitations based on custom properties when displaying traps in the web console.

Updated Requirements

The following requirement notes are in addition to those requirements currently published in the SolarWinds Orion Network Performance Monitor documentation set, including the Administrator, and Evaluation Guides:

• The web console is no longer supported on Internet Explorer version 6 (IE6).
• Simplified Chinese is a supported operating system language.
• Simplified Chinese with collation setting Chinese_PRC_CI_AS is a supported SQL Server collation.
• The section, "Requirements for Virtual Machines and Servers" may incorrectly state that only 4 GB of memory are required for monitoring virtual environents. The correct memory requirement is 8 GB.
• The section, "Server Sizing" may incorrectly state that an additional polling engine is recommended for environments with 8000 monitored elements. The current version of SolarWinds NPM can support monitoring up to 10000 elements on a single polling engine.

Installing and Upgrading Orion NPM

The following sections provide required information to consider before and during an installation or upgrade of Orion NPM, including information relating to the interaction between Orion NPM and Orion modules.

 Note: Licensed users also have access to Upgrade Instructions for Orion NPM and Orion modules. A link to this document is available in your Orion license listing on the License Management page of your SolarWinds Customer Portal.

• Upgrading from NPM 10.0 to NPM 10.2 Requires Deletion of SolarWinds.NPM.Common.dll
• Supported Orion NPM Versions
• EOC Hotfix Required for Upgrades to Orion NPM 10.1 and higher
• Orion NPM, Additional Polling Engines, and SQL Server on WANs
• Migrating Maps and Reports for Upgrades from Older Versions of Orion NPM
• Upgrading Orion NPM
• Installing Orion Additional Polling Engines and Web Servers
• Upgrading Orion NPM Modules and Components
• Hot Standby Engine and Orion Failover Engine
• Upgrading the Syslog Table in the Orion Database
• Installing this Version
• Install Directory on Windows Server 2008 R2
• ESX Server Details View is Missing the Current Percent Utilization of Each Interface Resource
• SQL Server Error 9002 (Full Database Log)
• Uninstalling SolarWinds Products

Upgrading from NPM 10.0 to NPM 10.2 Requires Deletion of SolarWinds.NPM.Common.dll

When upgrading directly from NPM version 10.0 to version 10.2, SolarWinds.NPM.Common.dll is not deleted, as required, resulting in errors when viewing node list resources in the web console. For more information about this error and its resolution, see the SolarWinds Knowledge Base article, "Error when opening a Node List Resource".

Supported Orion NPM Versions

As of the release of Orion NPM 10.0, SolarWinds no longer officially supports Orion NPM versions older than Orion NPM version 9.0.

EOC Hotfix Required for Upgrades to Orion NPM 10.1 and higher

A hotfix is required for all current Orion EOC users upgrading from Orion NPM version 10.0 to Orion NPM version 10.1 or higher. If you are a current EOC user, this hotfix is available in your Customer Portal.

Orion NPM, Additional Polling Engines, and SQL Server on WANs

Due to potential latency effects, SolarWinds does not recommend installing your SQL Server and your Orion server or Additional Polling Engines in different locations across a WAN. Though it is possible to deploy your Orion server and Additional Polling Engines in such a way that they connect across a WAN to your Orion database, SolarWinds can not guarantee that your circuit can meet the I/O specifications (i.e. bandwidth, speed, and latency) Orion NPM requires to function properly. In most cases, QoS or a dedicated circuit will be required specifically for this traffic between your Orion server and the database. If distributed deployment is a requirement, SolarWinds recommends an installation of the Orion Enterprise Operations Console (EOC) with multiple Orion instances at each distinct location across your WAN. For more information about Orion EOC, see Orion EOC at solarwinds.com.

Migrating Maps and Reports for Upgrades from Older Versions of Orion NPM

If you are uninstalling a pre-8.0 version of Orion NPM before upgrading to this version, the Configuration Wizard neither finds nor migrates your maps and reports to the new directory structure. You will not see maps or reports in the web console until you copy your maps folder and reports folder from the previous directory structure to the new directory structure. The old default location was: Volume:\Program Files\SolarWinds\Network Performance Monitor v7. The new default installation location is: Volume:\Program Files\SolarWinds\Orion.

Upgrading Orion NPM

Backup your database before performing any upgrade of Orion NPM, regardles of whether you are upgrading from version to version or you are upgrading the licensed number of elements you can monitor. For more information, see "Creating Database Backups".

The following sections provide guidance for completing an upgrade to the latest version of Orion NPM, regardless of your current version.

 Warnings:

• Whenever you install a new module or upgrade Orion NPM, ensure you first create a backup of your database. For more information, see "Creating Database Backups".
• Though the upgrade of version 7 and its point releases to Orion NPM version 8.5 should be blocked on a server running Microsoft Windows 2000, it is not. Do not upgrade your Orion NPM implementation until you upgrade your server to Windows 2003. Windows 2000 is not a supported operating system, and the database upgrades cannot be rolled back.
• When upgrading from versions prior to 8.0, you must first upgrade to an 8.X version of Orion NPM before you can upgrade to the current version. Contact SolarWinds Support to obtain required Orion NPM versions.
• When upgrading from version 8.0.2 or earlier, database changes required to improve performance cause the database update to take longer than in previous upgrades. For example, a database of 10GB can take over an hour to upgrade.
• Orion NPM does not support the use of case-sensitive database servers.
• Discovery profiles from older Orion NPM versions are not retained through upgrades to this Orion NPM version. If you want to retain a discovery profile, prior to starting your upgrade, externally record the configuration of the profiles you want to retain.

 Note: Due to significant updates that are applied to the Orion Database Maintenance utility, the Configuration Wizard may require a significant amount of time, upwards of 15 minutes or more for larger databases, to complete a full upgrade to Orion NPM version 10.

Upgrading from Orion NPM Versions Before 7.8.5

If your currently installed version of Orion NPM is older than version 7.8.5, you must upgrade to Orion NPM 7.8.5.

Upgrading from Orion NPM Versions 7.8.5 through 8.5

If you currently have Orion NPM version 7.8.5 through 8.5 installed, you must upgrade to Orion NPM 8.5.1.

Upgrading from Orion NPM 8.5.1

If you currently have Orion NPM version 8.5.1, you must upgrade to version 9.1.

Upgrading from Orion NPM Versions 9.0 through 9.5.1

If you currently have Orion NPM version 9.0 through 9.5.1, you must upgrade to version 10.0 before upgrading to the current version.

Hot Standby Engine and Orion Failover Engine

Depending on the version of Orion you currently have installed, SolarWinds provides either of two failover and disaster recovery solutions: Hot Standby Server and Orion Failover Engine. Hot Standby Server provides limited failover protection for Orion installations older than version 10.0. For Orion version 10.0 and higher, SolarWinds offers the Orion Failover Engine, which can protect your primary Orion installation and any installed modules.

For more information about the Orion Failover Engine, see the SolarWinds Orion Failover Engine Administrator Guide and related documentation provided at http://www.solarwinds.com/support/failoverengine/FailoverEngineDoc.aspx.

For more information about the Orion Hot Standby Engine, see the following sections in the SolarWinds Orion Core Administrator Guide:

• Using a Hot Standby Engine
• Installing a Hot Standby Engine
• Configuring a Hot Standby Engine
• Testing a Hot Standby Engine

Installing Orion Additional Polling Engines and Web Servers

In your SolarWinds Customer Portal, you will find installers for Orion Additional Polling Engines and Orion Additional Web Servers packaged into the following products, respectively: Orion Additional Polling Engine v2011.2 and Orion Additional Web Server v2011.2. Click Download Now next to the appropriate additional component listing to download the following files:

• SolarWinds-Orion-AdditionalPoller.exe
• SolarWinds-Orion-AdditionalWebsite.exe

Execute each of these files to extract the installers for the Orion NPM Additional Polling Engine and Orion NPM Additional Web Server, respectively. For more information, read the HTML readme documentation included with the extracted files.

Upgrading Orion NPM Modules and Components

To ensure proper operation of your Orion NPM installation, upgrade all Orion NPM Additional Web Servers, Additional Polling Engines, and Hot Standby Engines to the current Orion NPM version. This version of Orion NPM also supports the following versions of Orion NPM modules:

 Notes:

• Storage Manager, Virtual & Server Profiler, and Backup Profiler may also be installed on the same server as Orion NPM 10.1 and higher.
• Download the latest module and component versions for which you are licensed from the SolarWinds Customer Portal.
• Licensed users also have access to Upgrade Instructions for Orion NPM and Orion modules. A link to this document is available in your Orion license listing on the License Management page of your SolarWinds Customer Portal.
• For more information about upgrading Orion NPM, see Upgrading Orion NPM.

Upgrading the Syslog Table in the Orion Database

While completing an upgrade to Orion NPM version 10.0, the Configuration Wizard will attempt to complete an upgrade of the Syslog table in your Orion database. If you have retained a large number of Syslog records, the Configuration Wizard will notify you in a dialog, asking you if you want to continue with the Syslog table upgrade. Before continuing with the upgrade, consider the following points:

• The upgrade may take a significant period of time to complete. Internal testing has revealed that it may take upwards of 15 minutes to upgrade 4 million Syslog records.
• If there is not sufficient disk space on your database server to contain the transaction log entries created during the upgrade, the upgrade will fail.

Generally, SolarWinds recommends the following:

• Use a dedicated server to host your Orion database.
• The dedicated database server should also have at least as much empty disk space as the size of your Orion database. For example, if you know your Orion database to be 10GB, you should have at least 10GB free on the same disk for a total disk size of no less than 20GB.

An upgrade failure will occur if the database transaction log fills completely before the upgrade completes. In this case, you will see the following error:

SQL Server Error 9002

The log file for database DbName is full. Back up the transaction log for the database to free up some log space.

For more information about this error, see "SQL Server Error 9002 (Full Database Log)".

If you have not started your upgrade, complete the following procedure to truncate your Syslog table before starting your upgrade to ensure that you do not encounter this error while you are upgrading your database:

 Warning: The successful completion of the following procedure involves the deletion of existing data from your database. SolarWinds strongly recommends that you create a backup of your Orion database before completing this procedure. For more information, see "Creating Database Backups".

 Note: The following procedure stops the Syslog service. As a result, Orion NPM will be unable to receive any Syslog messages until you restart the Syslog Service.

1. Click Start > All Programs > SolarWinds Orion > Advanced Features > Orion Service Manager.
2. Click SolarWinds Syslog Service, and then click Stop.
    Note: Do not close the Orion Service Manager.
3. Create a backup of your Orion database. For more information, see "Creating Database Backups".
4. Truncate the Syslog table in your Orion database.
    Warning: The TRUNCATE command deletes data from your database. SolarWinds strongly recommends that you create a backup of your Orion database before executing this command. If you are not comfortable completing this operation, submit a technical support ticket.
5. In the Orion Service Manager, click SolarWinds Syslog Service, and then click Start.

Installing this Version

You do not need to uninstall your previous version before installing this version of Orion NPM. Shutdown any running Orion NPM applications, and then run the setup program provided in your download. The setup program will detect and uninstall your previous version without a loss of customizations.

Warnings:

• Orion NPM does not support the use of case-sensitive database servers. For more information, see the section, "Case-Sensitive Database Servers".
• Whenever you install a new module or upgrade Orion NPM, ensure you first back up your database. For more information, see "Creating Database Backups".

 Note: This version of Orion NPM requires Microsoft .NET Framework 3.5, and version 3.5 SP1 is recommended. The Configuration Wizard can download this automatically from Microsoft, but download and installation can take 20 minutes or more to complete.

Install Directory on Windows Server 2008 R2

If you are installing Orion NPM on Windows Server 2008 R2, confirm that you are installing to the Volume:\Program Files (x86) directory and not the Volume:\Program Files directory.

ESX Server Details View is Missing the Current Percent Utilization of Each Interface Resource

If you are upgrading from Orion NPM version 9.0 to Orion NPM version 10.0 and you change ESX Server monitoring from ICMP to SNMP, the Current Percent Utilization of Each Interface resource will not be present on the ESX Server Details view. If you are monitoring interfaces on a monitored ESX Server, you can add this resource to the ESX Server Details view, as you would any other resource. For more information, see "Editing Views" in the SolarWinds Orion Network Performance Monitor Administrator Guide.

SQL Server Error 9002 (Full Database Log)

If you are seeing the following error while completing the Configuration Wizard, a required upgrade of your Orion database has failed:

SQL Server Error 9002

The log file for database DbName is full. Back up the transaction log for the database to free up some log space.

An upgrade failure will occur if the database transaction log fills completely before the required upgrade of your Syslog table completes. If you have encountered this error, submit a technical support ticket, and a SolarWinds technical support representative can provide a script that will assist you in completing the required upgrade.

Uninstalling SolarWinds Products

If you need to uninstall NetFlow Traffic Analyzer, Network Configuration Manager (formerly Cirrus Configuration Manager), or Toolset, perform a repair on Orion NPM after uninstalling the selected application, as shown in the following procedure.

To repair Orion NPM after uninstalling another SolarWinds application:

1. Click Start > Control Panel > Add or Remove Programs.
2. Select your SolarWinds Orion Network Performance Monitor installation, and then click Change.
3. Select Repair, and then click Next.
4. Complete the wizard to repair your Orion NPM installation.

Orion NPM Databases

The following sections provide information covering the interaction between Orion NPM and Orion databases.

• SQL Server Requirements
• Case-Sensitive Database Servers
• SQL Express Databases

SQL Server Requirements

The following database servers are supported as the Orion datastore:

• SQL Server 2005 SP1 Express, Standard, or Enterprise
• SQL Server 2008, including R2, Express, Standard, or Enterprise
• SQL Server Compact 3.5 SP1 is only supported for Orion evaluations.

Your server must support either mixed-mode or SQL authentication.

Due to latency effects, SolarWinds does not recommend installing your SQL Server and your Orion server or additional polling engine in different locations across a WAN. For more information, see SolarWinds Knowledge Base article, "Can I install my Orion server or Additional Polling Engine and my Orion database (SQL Server) in different locations across a WAN?"

If you are managing your Orion database, SolarWinds recommends you install the SQL Server Management Studio component.

Use the following database select statement to check your SQL Server version, service pack or release level, and edition:

select SERVERPROPERTY ('productversion'), SERVERPROPERTY ('productlevel'), SERVERPROPERTY ('edition')

The following x86 components must also be installed (if the components are not found on the target computer, the setup program downloads and installs the components):

• SQL Server System Common Language Runtime (CLR) Types
• Microsoft SQL Server Native Client
• Microsoft SQL Server Management Objects

 Notes:

• If SQL Server System Common Language Runtime (CLR) Types are not already installed, Orion NPM will install them. This installation will require a restart of the SQL Server service for your Orion database.
• For improved performance, Orion NPM uses secure SQL CLR stored procedures for selected, non-business data operations.
• If you are using SQL Server 2005 SP1 Express Edition on a Windows XP operating system, enable the following protocols: Shared memory, TCP/IP, and Named Pipes.

Case-Sensitive Database Servers

There are a number of known issues that may be encountered when installing the Orion NPM database on case-sensitive database servers, therefore the use of case-sensitive database servers is not recommended.

To check the collation and case-sensitivity of your database and your server, run the following query using the Database Manager shipped with Orion NPM:

select databasepropertyex( db_name(), 'Collation') as DatabaseCollation, serverproperty('Collation') as ServerCollation

To run a query in Database Manager:

1. Click Start > All Programs > SolarWinds Orion > Database Utilities > Database Manager.
2. Expand your Orion NPM database in the left pane to view database tables.
3. Right-click on any table in the database and click Query Table.
4. Type the query in the Query window, and then click Refresh to run the query.

If you have either Enterprise Manager or SQL Server Management Studio Express, the following procedure will display the current collation settings for your Orion NPM database.

To view collation settings in Enterprise Manager or SQL Server Management Studio Express:

1. Open Enterprise Manager or SQL Server Management Studio Express.
2. Connect to your database server.
3. Expand Databases.
4. Right-click the name of your database server, typically NetPerfMon, and then click Properties.
5. Click General and the collation for your database server is listed under Maintenance.

In the following example, the letters CI show that the database is case-insensitive:

SQL_Latin1_General_CP1_CI_AS

If the database were case-sensitive, the letters CS would be present, instead.

 Note: If you are experiencing issues and your database server is case-sensitive, SolarWinds recommends that you install the Orion NPM database on a case-insensitive database server.

SQL Express Databases

SQL Express, a free version of SQL Server 2005 that has a 4GB database limit, is a supported database platform for Orion NPM, and it is made available for evaluation installations. However, SolarWinds does not recommend the use Of SQL Express in production environments or with the NetFlow Traffic Analyzer module, due to the 4GB database limit.

Specifying a SQL Express Instance

During the database section of the Configuration Wizard, it is possible that the browse function of the configuration wizard will not find your database. If you experience difficulty browsing to your SQL Express instance, type ServerName\sqlexpress in the SQL Server field on the Login to SQL Server dialog, where ServerName is the pre-Windows 2000 name of your SQL Server.

Strong Passwords for SQL Express Instances

The selected SQL Express instance must support mixed mode or SQL authentication with strong passwords. For more information about authentication with strong passwords, see Microsoft.com.

Configuration and Device Discovery

The following sections provide required information relating to Orion NPM configuration and device discovery.

• SNMP Community String Limits
• SNMPv3 Passwords
• Regional Settings in Firefox 3.0+
• Special Characters in Machine Names

SNMP Community String Limits

At this time, due to a limitation existing in the topology control Orion NPM uses, individual discoveries may not include any more than 10 separate community strings per SNMP version. In other words, for any individual discovery, you may not provide more than 10 community strings each for SNMPv1, SNMPv2, and SNMPv3, resulting in a maximum of 30 community strings for any individual discovery. If you need to provide more than 10 community strings of a specific SNMP version, you will need to configure multiple discoveries. This is a limitation that may be addressed in a future release.

SNMPv3 Passwords

At this time, SNMP v3 passwords are limited in length to 30 characters.

Regional Settings in Firefox 3.0+

Mozilla Firefox versions 3.0 and higher do not automatically respect regional systems settings. As a result, dates and other regional data may not display correctly. If Firefox is not correctly displaying regionally-influenced data in the web console, complete the following procedure to configure Firefox with the appropriate regional settings.

To configure appropriate regional settings in Firefox versions 3.0 and higher:

1. Open the Mozilla Firefox version 3.0 or higher browser you are using to view the Orion Web Console.
2. Click Tools > Options.
3. Click Content.
4. In the Languages area, click Choose.
5. If the language you want to use for viewing the web console is not listed, select your preferred language from the Select a language to add menu, and then click Add.
6. If the language you want to use for viewing the web console is already listed, confirm that your preferred language is listed first, by clicking your preferred language in the list, and then clicking Move Up until your preferred language is listed first.
7. When your language preference list is ordered correctly, click OK.
8. Click OK on the Options window to return to the web console.
9. Refresh your web browser to enable your new regional settings.

Special Characters in Machine Names

Due to limitations based on RFC 952 - DOD Internet Host Table Specification that are maintained by Windows Internet Information Services (IIS), the machine names of monitored network devices may only be composed of the following:

• Alphabetic characters (a-z or A-Z, case-insensitive)
• Digits (0-9)
• Minus sign (-)
• Period (.)

 Note: For more information about permitted machine names, see RFC 952 - DOD Internet Host Table Specification.

Orion NPM and Windows Server 2008

The following known issues exist for Orion installations on Windows Server 2008.

• It is not possible to use the System Manager chart email function (File > Send to > Mail Recipient) when Orion NPM is installed on Windows Server 2008.
• User Account Control (UAC) may prevent some Orion applications from executing correctly. If an Orion application is not loading correctly under UAC, right-click the application name (e.g. click Start > All Programs > SolarWinds Orion > Alerting, Reporting, and Mapping, and then right-click Report Writer) and then click Run as Administrator.
• On upgrade from Orion NPM version 9.5 SP2, all SSL settings in the Internet Information Services Manager are reset to default. This condition has been discovered on both German and English versions of Windows Server 2008, and it may be addressed in a future release.

Orion NPM and the SolarWinds Orion Management Pack

Users of the SolarWinds Orion Management Pack who want to upgrade to SolarWinds NPM version 10.2 must also upgrade to SolarWinds Orion Management Pack version 1.1.1. Current users of SolarWinds Orion NPM version 10.1 may upgrade to SolarWinds Orion Management Pack version 1.1.1 to receive the benefit of SolarWinds Orion Management Pack bug fixes.

Download the latest version of SolarWinds Orion Management Pack from the SolarWinds Customer Portal.

Orion Web Console

The following sections provide information related to the Orion Web Console.

• Reports Display Different Data in Report Writer and the Web Console
• thwack is Unreachable from an Additional Web Server
• Node Status Rollup on Maps and in All Nodes Resources
• Custom Text Properties in All Nodes Resources
• Viewing Charts and Chart Thumbnails
• Custom Menu Items After Upgrading
• Custom Web Console Resources
• Orion Web Console Navigation in Firefox 3.5.9
• Web Console Account Limitations in Internet Explorer
• Minimum Volume Polling Interval

Reports Display Different Data in Report Writer and the Web Console2^, 3

Some reports may show data when displayed in Report Writer that is different from the data shown when they are displayed in the web console. This slight difference may be attributed to checking the Group Historical Data by Days option when configuring the report in question. Enabling this option has no effect on reports displayed in Report Writer, but it does ensure that more accurate report data is displayed in the web console. Clearing this option will ensure that data is consistent, though potentially less accurate, between Report Writer and the web console. For more information, see "Reports display different data in Orion Report Writer and in the Orion Web Console".

thwack is Unreachable from an Additional Web Server

On Additional Web Servers that are configured to use a proxy, thwack resources in the web console may display "Unable to contact thwack server" errors. To resolve this issue, add the following lines within the <configuration></configuration> tags of the web.config file for the Additional Web Server:
<system.net>
  <defaultProxy enabled="false" />
</system.net>
For more information, see "thwack is Unreachable from an Additional Web Server".

Node Status Rollup on Maps and in All Nodes Resources

By default, in a previous version of Orion NPM, if any interface was down or in an otherwise defined problem state, the status icon of the parent node reflected the problem state of the child interface by displaying as red. In other words, node status icons reflected the worst state of any and all child interfaces on the selected node. This status rollup change was intended to more clearly highlight nodes where problems may exist.

For more information about how status is determined in this version of Orion NPM, see "Status Rollup Mode". The following steps configure the status rollup mode for your Orion Web Console.

To configure the status rollup mode for the Orion Web Console:

1. Log on as an administrator to your Orion Web Console.
2. Click Settings in the top right corner of the web console.
3. Click Web Console Settings in the Settings grouping of the Orion Website Administration page.
4. Select either of the following options as your Status Rollup Mode:
   
   • If you want the parent node status icon to show the worst status of all child devices, select Show Worst Status.
   • If you only want the parent node status icon to show as yellow (warning) if there are problems with any or all child devices, select Mixed Status shows Warning
   .
5. Select any of the following options as your Child Status Rollup Mode:
   
   • If you want the parent node status icon to show the worst status of all child devices, select Show Worst Status.
   • If you want the parent node status icon to show the worst status of all child interfaces, select Show Worst Status (Interfaces Only).
   • If you only want to Up/Down status, select Show only ICMP Status
   .
6. Click Submit.

Custom Text Properties in All Nodes Resources

With the introduction of the AJAX-enabled All Nodes resource in Orion NPM version 9.0, the ability to group devices using the Comment or Memo custom properties was deprecated in order to maintain resource performance. The Memo custom property has been enabled for use with non-AJAX All Nodes resources. If you require the ability to group nodes on the basis of an otherwise undefined text property, create a Text property in Custom Property Editor and apply it as necessary to your monitored nodes. For more information about custom properties in Orion NPM, see "Creating Custom Properties" in the SolarWinds Orion Network Performance Monitor Administrator Guide.

Viewing Charts and Chart Thumbnails

Regardless of the actual size of a web console chart resource, if the width of the column in which the chart is displayed is set narrower than 300 pixels, Orion NPM replaces the chart with a chart thumbnail. The following procedure shows how to avoid this issue by setting appropriate column widths for any Orion NPM Web Console view.

To set column widths in an Orion NPM Web Console view:

1. Log on to the Orion NPM Web Console as an Administrator.
2. Click Settings in the top right corner of the web console.
3. Click Manage Views in the Views grouping of the Orion Website Administration page.
4. Select the view containing the column you want to configure, and then click Edit.
5. Click Edit next to the list of column widths.
6. Provide an appropriate width, in pixels, for the column you are configuring, and then click Submit.
7. Click Done.

Clicking a chart thumbnail produces the same result as clicking a full-size chart, opening the Custom Chart page in a new window. The Custom Chart page allows you to customize the appearance of the selected chart. For more information, see "Custom Chart View" in the SolarWinds Orion Network Performance Monitor Administrator Guide.

Custom Menu Items After Upgrading

Orion NPM 8.5 introduced a new website directory structure to the Orion Web Console. Because of this, if you are upgrading to Orion NPM 8.5, some of your custom menu items in the Orion Web Console may need to be updated. Previous versions of Orion NPM used the /NetPerfMon directory for all files which allowed you to use relative links such as View.asp?ViewID=24. These URLs will need to be updated to an absolute URL starting with /Orion. For example, /Orion/SummaryView.aspx?ViewID=24. For information on how to edit your menu bar items, see "Customizing Menu Bars" in the SolarWinds Orion Network Performance Monitor Administrator Guide.

Custom Web Console Resources

In Orion NPM versions 9.5 and higher, custom resources created for use in the Orion Web Console must be written in ASP.NET. For more information, see the announcement, "Support for custom ASP resources ends in v9.5 - switch to ASP.NET" on thwack.com.

Orion Web Console Navigation in Firefox 3.5.9

Firefox 3.5.9, a recent update to Firefox 3.5, incorrectly renders the Orion Web Console navigation bar. To correct this issue, upgrade your Firefox browser to version 3.6 or higher. For more information about upgrading your Firefox browser, see Mozilla Firefox.

Web Console Account Limitations in Internet Explorer

In some cases, when the Orion Web Console is running in Internet Explorer, account limitations may not be recognized as intended on a custom view created with custom charts and reports. This issue is under investigation and may be addressed, if necessary, in a future release.

Minimum Volume Polling Interval

On the Orion Polling Settings view (Settings > Polling Settings), it is possible to enter a value for the Default Volume Poll Interval that is actually lower than the minimum interval allowed by the Orion polling engine. By default, in new installations, the Default Volume Poll Interval is set to 120 seconds. The Orion polling engine allows a minimum interval 30 seconds, even though values lower than 30 may be entered. In the event that a value less than 30 seconds is entered, the Orion polling engine automatically applies the minimum interval of 30 seconds.

Network Atlas and Orion NPM Maps

Orion Network Atlas may be installed on Microsoft Windows XP, Windows Vista, Windows Server 2003, or Windows Server 2008.

The following sections provide information related to Network Atlas and maps in Orion NPM.

• Updated Topology Algorithm in NPM 10.2
• Using ConnectNow in Older Versions on SolarWinds NPM
• Node Status Rollup on Maps
• Network Map Resource Error in the Orion EOC Web Console
• Open Issues Related to Network Atlas

Updated Topology Algorithm in NPM 10.2

Beginning with NPM 10.2 (Orion Core version 2011.2) the same technology and data for determining topology are used as in previous versions, but topology data is no longer gathered using Network Sonar Discovery. Instead, individual polling jobs are assigned to each device that provides layer 2 and layer 3 topology data. This data is gathered and stored in the database for a centralized topology calculation that runs periodically. So, though NPM 10.1.X could only calculate topology for devices within a given discovery range, NPM 10.2 is not so limited. Network topology can now be calculated for all monitored devices providing layer 2 and layer 3 topology data.
Note: NPM 10.2 still uses the BRIDGE MIB layer 2 information as the primary method for determining edges. Therefore, some inaccuracies in version 10.1.X may persist in version 10.2. Some edges detected by NPM will not necessarily be directly connected, but they may represent an indirect connection between the two connected devices or interfaces. Future versions of NPM will incorporate different techniques to improve the accuracy of directly connected devices.

Using ConnectNow in Older Versions on SolarWinds NPM

In versions of SolarWinds Orion NPM prior to version 10.2, topological data about your network is only generated during Network Sonar Discovery, so ConnectNow can only draw lines between discovered nodes. Nodes that are added manually, as in Web Node Management, cannot be connected using ConnectNow. Additionally, nodes discovered in previous version of Orion NPM will not have associated topological data until Orion NPM discovers them again with a new network discovery. Orion NPM version 10.0 does allow you to schedule network discoveries, so you can have regularly updated topological information about your network. For more information about using ConnectNow, see "Connecting Objects Automatically with ConnectNow" in the SolarWinds Orion Network Atlas Administrator Guide. For more information about network discovery, see "Discovering and Adding Network Devices" in the SolarWinds Orion Network Performance Monitor Administrator Guide.

Node Status Rollup on Maps

By default, in the previous version of Orion NPM, if any node in a mapped group of nodes is down or in an otherwise defined problem state, the status icon of the group reflects the problem state of the member node by displaying as red. In other words, group status icons reflected the worst state of any and all nodes in the selected group. This status rollup change was intended to more clearly highlight groups with nodes where problems may exist.

This version of Orion NPM provides two options for displaying the status of a group of nodes on a map. You can either show the worst status of the group (red if any of the nodes are down) or you can show warning (yellow) if some nodes are down and some are up. The following steps configure the status rollup mode for your Orion Web Console.

To configure the status rollup mode for the Orion Web Console:

1. Log on as an administrator to your Orion Web Console.
2. Click Settings in the top right corner of the web console.
3. Click Web Console Settings in the Settings grouping of the Orion Website Administration page.
4. Select either of the following options as your Status Rollup Mode:
   
   • If you want the parent node status icon to show the worst status of all child devices, select Show Worst Status.
   • If you only want the parent node status icon to show as yellow (warning) if there are problems with any or all child devices, select Mixed Status shows Warning.
5. Select any of the following options as your Child Status Rollup Mode:
   
   • If you want the parent node status icon to show the worst status of all child devices, select Show Worst Status.
   • If you want the parent node status icon to show the worst status of all child interfaces, select Show Worst Status (Interfaces Only).
   • If you only want to Up/Down status, select Show only ICMP Status
   .
6. Click Submit.

Network Map Resource Error in the Orion EOC Web Console

If you are upgrading an installation of Orion NPM version 9.1 that is currently monitored by an Orion Enterprise Operations Console (Orion EOC), the Network Map resource in the Orion EOC Web Console may not display network maps correctly. The following steps correct this issue.

To restore the Network Map resource in the Orion EOC Web Console:

1. Click Download Network Atlas in the Network Map resource.
2. Run the Network Atlas installation executable file.
3. Click Repair.
4. Complete the Configuration Wizard.

Open Issues Related to Network Atlas

The following known issues are related to the interaction between Orion NPM and Network Atlas.

• When renaming an existing map, it is not currently possible to use a new name that includes a period. This limitation does not affect new maps. For example, naming a new map New.Map.OrionMap is allowed, but renaming an old map (OldMap.OrionMap) as Old.Map.OrionMap is not currently allowed.
• After performing a Repair operation on an installation of Orion Network Atlas that has been upgraded during an upgrade of Orion NPM from version 9.5.X to version 10, the legacy icons folder, if it exists, is relocated. This relocation may result in a failure to correctly display legacy icons on existing Network Atlas maps. To correct this issue, copy the Icons folder from Volume:\Program Files\SolarWinds\Network Atlas\Maps\NetObjects\ to Volume:\Program Files\SolarWinds\Orion\Network Atlas\Maps\NetObjects\. After completing the repair, you may also need to restart Network Atlas on your Orion NPM server.
• Orion Network Atlas does not support Orion NPM login credentials that use Integrated Windows Authentication. To connect Orion Network Atlas to Orion NPM servers, you must provide an Orion NPM credential that was created in the Orion Account Manager.
• The EOC Map converter tool only converts MapMaker Maps. You can use the converter tool to convert maps prior to upgrading to Orion NPM 9.5, but after you upgrade, all existing maps are converted to Orion Network Atlas maps and can no longer be converted with this tool.
• Objects in Orion Network Atlas with an icon size smaller than 10 points are drawn only with simple shapes.
• Performing more than ten Undo actions in a row in Orion Network Atlas marks the map as having been saved.
• The background color in Orion Network Atlas is not saved if the map also has a linked background.

Orion NPM and Orion EOC

The following sections provide information related to the interaction between Orion NPM and the Orion Enterprise Operations Console (Orion EOC).

• EOC Hotfix Required for Upgrades to Orion NPM 10.1 and higher
• UTC Server Time Synchronization
• Network Map Resource Error in the Orion EOC Web Console

EOC Hotfix Required for Upgrades to Orion NPM 10.1

A hotfix is required for all current Orion EOC users upgrading from Orion NPM version 10.0 to Orion NPM version 10.1. To acquire this hotfix, submit a technical support ticket.

UTC Server Time Synchronization

The coordinated universal time (UTC) of the Orion NPM server must be within five minutes of the UTC of the Orion EOC server. If there is a time discrepancy greater than five minutes, a secure connection to the Orion NPM server cannot be established. If you receive an invalid credential error even though you are sure the credentials are correct, check the UTC of both servers.

Network Map Resource Error in the Orion EOC Web Console

If you are upgrading an installation of Orion NPM version 9.1 that is currently monitored by an Orion Enterprise Operations Console (Orion EOC), the Network Map resource in the Orion EOC Web Console may not display network maps correctly. The following steps correct this issue.

To restore the Network Map resource in the Orion EOC Web Console:

1. Click Download Network Atlas in the Network Map resource.
2. Run the Network Atlas installation executable file.
3. Click Repair.
4. Complete the Configuration Wizard.

Orion NCM Integration

The following sections provide information about the Orion Network Configuration Manager (Orion NCM) Integration for Orion NPM.

• Orion NCM Integration for Orion NPM - Inventory Reports
• Removing the Orion NCM Integration for NPM

Orion NCM Integration for Orion NPM - Inventory Reports

If you are using Internet Explorer 8, you need to be running in Compatibility mode to ensure Inventory report navigation works correctly.

Removing the Orion NCM Integration for NPM

Removal of the Orion NCM Integration for NPM component requires manual interaction with the Orion NPM website. Complete the following procedure to completely remove the integration component.

To remove the Orion NCM Integration component:

1. Stop the Orion NPM website using the Microsoft Internet Information Service Manager.
2. Stop the IIS Admin Service using the Service Control Manager (services.msc).
3. Delete the NCM folder in the \inetpub\SolarWinds\Orion folder.
4. Restart the IIS Admin Service.
5. Restart the Orion NPM website.
6. Navigate to http://hostnameOrIPaddress/orion/admin/listviews.aspx and remove Orion NCM resources from the following views:
• Network Summary Home
• Node Details

EnergyWise

The following sections provide information about using Orion NPM to monitor Cisco EnergyWise-enabled network devices.

• Importance
• EnergyWise Device Time
• Recurrence Policies and Chron Jobs

Importance

Currently, the importance of policy updates is hard coded to 100. At this time, this is caused by a limitation imposed by the EnergyWise MIB data collection mechanism.

EnergyWise Device Time

The time returned by an EnergyWise device is based on the device time. Therefore, recurrence policies (based on chron jobs) respect the time set on the device, not the time of Orion NPM or Orion NCM.

Recurrence Policies and Chron Jobs

Do not use a 7 to represent Sunday in the day of the week option of your recurrence policy. At this time, 7 is not recognized by Orion NPM as Sunday. Using 7 to represent Sunday will cause problems with your EnergyWise Policy Overview Calendar resource.

VMware Devices

The following sections provide information about using Orion NPM to monitor VMware ESX Servers.

• Virtual Machine Details Resource Not Displaying
• Enabling SNMP on ESXi Server 4.0
• ESX Server 2.0.2
• Polling ESX Server 4.0 Memory Usage

Virtual Machine Details Resource Not Displaying

In previous versions of Orion NPM, the Virtual Machine Details resource would display on Node Details views for virtual machines that Orion NPM was actually unable to poll for performance data. Orion NPM is able to determine the existence of the virtual machine by virtue of its MAC address. Because additional data beyond the MAC address of the virtual machine is not available, there is no information to display in the Virtual Machine Details resources, so the resource is hidden.

Enabling SNMP on ESX/ESXi Server 4.0

You must enable SNMP on VMware ESX/ESXi 4.0 Servers. For more information see "Enabling SNMP on VMware ESXi, ESX 3.5 Server, or ESX 4.0 Server".

ESX Server 2.0.2

When polled by Orion NPM, VMware ESX Servers on version 2.0.2 do not provide correct data. This is a known issue that may be fixed in a future release.

Polling ESX Server 4.0 Memory Usage

On an SNMP-enabled ESX 4.0 Server, there is a known discrepancy between reported and actual values provided in the Disk Volumes resource. The standard OID reports the amount of memory assigned to the host on which the ESX Server is based. The VMware API proivdes the actual memory usage of the hosted ESX Servers. For this release, Orion NPM places a priority on data polled using SNMP over data provided through the VMware API.

Other Known Orion NPM Issues

The following sections provide information related to previously unmentioned, known issues in Orion NPM.

• Interface Index for Interfaces of Unknown Status
• Wireless Views Revert to Default View Type on Upgrade
• Adding Nodes Using System Manager
• Calculated Interface Utilization Values

Interface Index for Interfaces of Unknown Status

Beginning with Orion NPM version 10.2, interfaces with an unknown status are assigned an index of -1, instead of 0, as in previous releases. This change is due to the SolarWinds' support for monitoring Juniper sub-interfaces, for which an interface index of 0 is valid.

This change may affect users with alerts configured to trigger on an interface index of 0 to indicate when an interface has gone Unknown.

To address this condition, edit alerts for unknown interfaces to trigger on an interface index of -1 instead of on an interface index of 0.

Wireless Views Revert to Default View Type on Upgrade

There is a known issue where edits to views by device type for wireless devices are not maintained through Orion NPM upgrades.

If the Orion Web Console is displaying the (default) web view after an upgrade, complete the following procedure to restore the Wireless Autonomous AP device type view for your wireless autonomous APs:

1. Log in to the Orion Web Console using an account with administrative privileges.
2. Click Settings in the top right of the web console.
3. Click Views by Device Type in the Views group of the Orion Website Administration page.
4. Select Wireless Autonomous AP for each listed wireless device that has reverted to the (default) web view.
5. Click Submit.

Additionally, after upgrade, there may be a delay of a few polling cycles after changing the (default) web view to Wireless Autonomous AP. If this is occurring in your web console, the device type view should be updated to Wireless Autonomous AP within a few polling cycles.

Adding Nodes Using System Manager

Beginning with Orion NPM 10.1, it is no longer possible to add nodes to the Orion database using System Manager. Network Sonar Discovery should be used for bulk additions, and Node Management in the Orion Web Console should be used for individual additions. For more information about Network Discovery, see "Discovering and Adding Network Devices" in the SolarWinds Orion Common Components Administrator Guide. For more information about Node Management, see "Managing Devices in the Web Console" in the SolarWinds Orion Common Components Administrator Guide.

Calculated Interface Utilization Values

It is possible for interface tooltips to show utilization at more than 100%, even when the Top XX Interface Utilization resource correctly shows utilization at a maximum of 100%. This is due to the fact that Orion NPM is reporting the interface bandwidth as provided by the interface itself. To correct the polled interface bandwidth, edit the interface, as directed in this Knowledge Base article.

Other Known Orion Core Issues

The following sections provide information related to previously unmentioned, known issues in Orion Core.

• Credentials Used When One User Account is a Member of Two Windows Groups
• Storage Reservation on Red Hat Enterprise Linux 5 Server Volumes
• The ${AcknowledgeURL} Variable Does Not Respect SSL
• Export to PDF is not Working withSelf-signed Certificates (SSL)
• Report Scheduler is Unable to Convert Web Page to PDF
• Alert Trigger Variables Are Not Available in Advanced Alert Manager
• Windows Net Message Not Supported in Windows Vista, Windows Server 2008, or Windows 7
• Maximum Number of Searchable Events on Web Console Events View
• Groups and IP SLA Manager
• Email a Web Page Alert Action with Active Directory
• Installer Log Files on non-English Windows Server 2003
• Toolset Integration Does Not Automatically Install on Windows Server 2008 R2
• Case Sensitivity in Trap Rules
• Printing Web Pages from Report Scheduler
• Orion Report Scheduler and Internet Explorer Enhanced Security
• Scheduled Tasks in Windows 2008
• Charts in Orion Application Performance Monitor
• Sending Alert Emails
• Internationalization
• Syslog Messages Reporting Incorrect Source IP Address
• Remote Access to System Manager
• Special Characters in Custom Property Names
• Discovery Profiles in Upgrade
• Log Adjuster Fault
• Database Names and the Trap and Syslog Viewers
• Reports and Users with Account Limitations
• Error on Links from the Last XX Syslog Message Resource

Credentials Used When One User Account is a Member of Two Windows Groups

When a single user is a member of two different Windows groups at the same time, Orion NPM only recognizes the credentials and permissions of the user account in the group with the lower order number.

Storage Reservation on Red Hat Enterprise Linux 5 Server Volumes95

SolarWinds products do not properly account for the storage reservation when polling volumes on Red Hat Enterprise Linux 5 servers. This discrepancy should be addressed in a future release. For more information, see "Storage Reservation on Red Hat Enterprise Linux 5 (RHEL5) Server Volumes".

The ${AcknowledgeURL} Variable Does Not Respect SSL13

Links provided by Orion applications to acknowledge alerts using the ${AcknowledgeURL} variable do not automatically respect Secure Sockets Layer (SSL) security (https:) settings on your Orion server. By default, Orion operates as though SSL is not enabled. For more information about a possible workaround, see "Links provided to acknowledge alerts using the ${AcknowledgeURL} variable do not respect SSL."

Export to PDF is not Working with Self-signed Certificates (SSL)16

In environments using self-signed certificates, the following error has occurred when attempting to use the Export to PDF function in the Orion Web Console:

There was an error trying to export the page to PDF. Please try again later.

Export to PDF failed. Err: The underlying connections was closed; could not establish trust relationship for the SSL/TLS secure channel.

For more information about a possible workaround, see "Export to PDF is not working.".

Report Scheduler is Unable to Convert Web Page to PDF32

The default timeout for completing the conversion of a web page to .pdf using Orion Report Scheduler with the Retrieve a Printable Version of this Page option enabled is three (3) minutes. Some larger reports may take a significant period of time to complete conversion, and in a default configuration, the following error displays if it takes longer than three (3) minutes to complete the conversion:

Unable to convert the Web Page to PDF

For more information about a possible workaround, see "I am unable to convert a web page to PDF in Report Scheduler".

Alert Trigger Variables Are Not Available in Advanced Alert Manager39

Alert trigger variables may not be available if the schemas associated with monitored network objects are not updated when the Advanced Alert manager starts. Typically, these updates occur automatically, but there have been cases where these updates are prevented by having Windows User Account Control (UAC) enabled on Windows Server 2008. For more information about a possible workaround, see "Alert trigger variables for nodes are not available in Advanced Alert Manager".

Windows Net Message Not Supported in Windows Vista, Windows Server 2008, or Windows 715

Beginning with Windows Vista, Microsoft has removed Net Send as a function from all operating systems, so the Send a Windows Net message alert action is not available to Orion installations on either Windows Vista, Windows Server 2008, or Windows 7. As a result, the Send a Windows Net Message alert action is not functional for Orion installations on these operating systems. For more information about a possible workaround, see "I am unable to send a Windows Net Message".

Maximum Number of Searchable Events on Web Console Events View

Currently, the web console Events view is unable to search more than 3000 events. This maximum may be increased in a future release.

Groups and IP SLA Manager

Links from IP SLA operations listed in Group Members and Group Root Cause resources in the web console are inoperable. This is a known issue that is scheduled to be addressed in a future release.

Email a Web Page Alert Action with Active Directory

The Email a Web Page alert action does not function as designed for users who are logged in to the Orion Web Console using an Active Directory account or group. This is a known issue that may be addressed in a future release.

Installer Log Files on non-English Windows Server 2003

Installer log files are not packaged with SolarWinds Diagnostics on non-English operating systems. When providing diagnostics for installations of Orion on non-English Windows Server 2003, SolarWinds Support will specifically request installer logs from the native language equivalent of Volume:\Documents and Settings\All Users\Application Data\SolarWinds\.

Toolset Integration Does Not Automatically Install on Windows Server 2008 R2

The SolarWinds Toolset Integration for the Orion Web Console is unable to install automatically on Windows Server 2008 R2 due to an Internet Explorer version 8 (IE8) security feature. As a result, whenever the web console opens a view containing resources that can use the Toolset integration, a warning dialog displays. If you want to install the Toolset integration, click More Options, and then click Always Install. If you do not want to install the Toolset integration, click More Options, and then click Never Install.

Case Sensitivity in Trap Rules

When defining trap rules for the Trap Viewer, the DNS Hostname Pattern is case-sensitive.

Printing Web Pages from Report Scheduler

If any warning dialogs are open on the Orion server when a web page is scheduled for printing in Report Scheduler, the print job may not complete. To ensure that print jobs configured in the Report Scheduler complete, confirm the following:

• Print the Web Page is selected when the scheduled task is configured in Report Scheduler
• All open dialogs, including SWToolset.exe and javascript warnings, are closed
• All scheduled print tasks are configured to run even when the current user is not logged in

Orion Report Scheduler and Internet Explorer Enhanced Security

When Internet Explorer (IE) Enhanced Security Configuration is installed, Orion report Scheduler may hang intermittently when attempting to perform a scheduled report print job. To address this issue, complete either of the following procedures:

• Recommended - Add the Orion Web Console to the listed of trusted sites in your browser. For more information about Internet Explorer Enhanced Security Configuration and adding sites to the trusted sites list, see, "Adding Sites to the Enhanced Security Configuration Zones"
• Uninstall IE Enhanced Security Configuration.

Scheduled Tasks in Windows 2008 Server

The Orion Report Scheduler uses the Windows Task Scheduler technology to execute scheduled tasks. These scheduled tasks are configured to run in user-based contexts, and, by default in Windows Server 2008, they will only run when the user who scheduled the task is logged in. In the event that the currently logged-in user is different from the user corresponding to the configured task, the scheduled task may not proceed as expected. The default configuration of any scheduled task may be edited as shown in the following procedure:

To modify the configuration of a scheduled task in Windows Server 2008:

1. Click Start > All Programs > Accessories > System Tools > Task Scheduler.
2. Right-click scheduled task, and then click Properties.
3. Check Run whether user is logged on or not.

Note: You may need to change the context of the job to enable the ability to change this settings.

4. Click OK.

Charts in Orion Application Performance Monitor

In installations of Orion APM 2.0 on Orion NPM 9.1, labels on the y-axis of Orion Application Performance Monitor charts may display as misaligned or staggered. Chart data is not affected by this misalignment. This is a known issue to be fixed in a future release.

Internationalization

International Date/Time Settings

A number of areas in the Orion Web Console, including the Orion NCM Integration for Orion NPM, display the wrong time format when you change the system settings to display an international time setting. This is a known issue and will be corrected in an upcoming release.

Cyrillic Characters

The Orion Web Console does not permit the use of Cyrillic characters in user account passwords.

Syslog Messages Reporting Incorrect Source IP Address

In an earlier release, it was thought that the source field of forwarded Syslog messages was correctly populated with the IP address of the Syslog message source, instead of the IP address of the forwarding Orion NPM server, but this is not the case. This is a known issue, and it will be corrected in an upcoming release.

Remote Access to System Manager

System Manager uses DCOM (Distributed Component Object Model) to interact with monitored network devices. With the release of Windows 2003 Server Service Pack 1, Microsoft tightened default DCOM permissions settings for remote connections. For more information about these changes, see the following Microsoft Support articles:

• Description of the changes to DCOM security settings after you install Windows Server 2003 Service Pack 1
• Programs that use DCOM do not work correctly after you install Microsoft Windows Server 2003 Service Pack 1

As a result of these changes, remote connections to System Manager may not have sufficient permissions. Attempts to connect remotely to System Manager may result in the following error:

Run-time error '70':
Permission Denied

For more information about resolving this error by increasing the permissions granted to clients accessing DCOM remotely, see the Microsoft Support article "How To Troubleshoot Run-time Error '70' in DCOM Applications".
Note: System Manager is no longer a component of the current version of SolarWinds NPM.

Special Characters in Custom Property Names

Although most non-alphanumeric characters used in custom property names are replaced by underscores (_) when names are stored in the Orion database, SolarWinds recommends against using non alphanumeric characters in custom property names. Hash characters (#) are not allowed in any property name. This is a known issue that may be addressed in a future release.

Discovery Profiles in Upgrade

Discovery profiles from older Orion NPM versions are not retained through upgrades to this Orion NPM version. If you want to retain a discovery profile, prior to starting your upgrade, externally record the configuration of the profiles you want to retain.

Log Adjuster Fault

If you are unable to launch the Log Adjuster utility or you are receiving an error with Event ID 1000 when you try to launch the Log Adjuster utility, it may be due to a limitation of your .NET Framework installation. Upgrade your .NET Framework to version 3.5 SP1. For more information about upgrading your .NET Framework, see Microsoft .NET Framework 3.5 Service Pack 1. This condition may be addressed in a future release.

Database Names and the Trap and Syslog Viewers

Both the Trap and Syslog Viewers may fail to connect to the Orion database if special characters are used in the database name. This condition may be addressed in a future release.

Reports and Users with Account Limitations

For security reasons, by default, web console users with account limitations may not be able to view reports in the web console. For more information, see "Reports and Account Limitations" in the SolarWinds Orion Network Performance Monitor Administrator Guide.

Error on Links from the Last XX Syslog Message Resource

Clicking messages in the Last XX Syslog Messages resource may result in an exception. To address this issue, confirm that you are using EN-US regional browser settings and confirm that you have installed the latest version of the SolarWinds Information Service (SWIS). For more information about SWIS, see "Why is the SolarWinds Information Service (SWIS) failing to upgrade?"

Features of Previous Orion NPM Releases

Previous versions of Orion NPM added the following features:

• Monitor Juniper sub-interfaces alongside your existing interfaces
• Monitor CPU and memory data for JunOS and Netscreen devices

• Monitor HP 420 autonomous access points (AP)
• Configure wireless-only data retention settings

• Interface Availability charts are now available.
• The new SolarWinds Collector corrects numerous interface polling issues.
• Multiple Interface Charts are now capable of showing a single line representing the sum of transmitted and received traffic on a single interface.
• The allowed lengths of Interface captions (Interfaces.Caption), names (Interfaces.InterfaceName), and full names (Interfaces.FullName) have been extended to 768, 512, and 1024 characters, respectively.
• Multiple Interface Charts now use dots to show discontinuously polled values.
• MAC addresses are now provided as a column to identify client machines in the Historical Wireless Client view.

Discovery Central

Discovery Central gives you a centralized overview of the types and number of network objects you are monitoring with your currently installed Orion products. The Discovery Central view is subdivided into sections corresponding to the Orion products you have installed, and each section provides direct links to related object discovery and addition views in the web console.

Wireless Monitoring Enhancements

• Support for monitoring HP Procurve Access Point 41028
• Cisco Aironet 1130 AG access points are now recognized as a Cisco devices

License Level Notification

The notification bannner in the web console now informs you when you are close to maximizing your license for any and all installed Orion products. This license level notification provides links to review and upgrade your license.

Complete Active Directory Authentication Support

• Authenticate to the Orion Web Console using Active Directory Users and Groups
• Enable automatic pass-through login or require authentication with each login

Dynamic Groups and Dependencies

• Organize Orion objects of different types (e.g. nodes, volumes, interfaces, etc.) into groups to roll up service level status
• Define dependencies to reduce redundant node reachability or downstream device alerts. For more information, see "How do I define and use dependencies in Orion NPM?"

DataCenter Monitoring Enhancements

• New resources and reports for Cisco Unified Computing Systems (UCS) devices
• Fiber Channel monitoring for Cisco MDS, Brocade, and McData devices

Alert Management Enhancements

• Use mobile devices to remotely view and acknowledge alerts
• Create advanced alerts using custom SQL queries
• Enable, disable, and delete advanced alerts in the web console
• Acknowledge alerts using links in emailed alerts
• View alerts, syslog, traps, and events in a single Message Center view

New Resources

• Use the Custom Object Resource to add node, interface, and volume charts directly to summary views
• Use Multiple Series Charts to display multiple interfaces and Universal Device Pollers to the same chart

Wireless Monitoring Enhancements

Support for monitoring Meru Wireless Controllers

VMware Monitoring Enhancements

Monitor your entire VMware virtual infrastructure, including Virtual Centers, Datacenters, and ESX Clusters.

Scheduled Discovery

With the addition of scheduled discovery, you can now automatically perform regular network discoveries at any time of the day or night. Using the Network Sonar Wizard, you can easily schedule discoveries to occur whenever best suits your network monitoring and management requirements.

VMware vSphere Monitoring

This version of Orion NPM adds the ability to monitor VMware vSphere installations by employing the VMware API to supplement ESX/ESXi server data available to SNMP polling.

Syslog and Traps

The following Syslog and Traps features have been included in this version of Orion NPM:

• Using the standard Orion ${vbName1} and ${vbData1}variable format,, trap variable binding names and value pairs are now available as alerting and message variables.
• The Trap Viewer now allows you to use pattern matching on trap details to create custom trap alerts.
• Orion NPM node variables are now available for use in Syslog and trap alerts.
• Syslog and trap alerts now respect unmanaged node status.
• Orion NPM can now change the status of an interface based on the content of a trap message.
• Forwarded Syslog messages may now be configured to retain the IP address of the original message source.
• Forwarded Syslog messages may also be configured to spoof network packets using WinPCap 3.0+.

Orion Product Team Blog

Stay in touch with the people who bring you the products in the Orion family by following the Orion Product Team Blog on thwack, the SolarWinds online user community. Read posts from Orion product managers and developers to learn how to extend and optimize your Orion installation to best meet the needs of your network.

Product Update Notifications

Receive regular, automatic notification of updates to your installed Orion monitoring and management applications in the Orion Web Console as soon as they are available from SolarWinds. Product updates can include upgrade opportunities, service packs, and hotfixes.

ConnectNow

Using topology data collected during network discovery, the ConnectNow feature in Orion Network Atlas can automatically draw lines between map objects that are directly linked (Layer 2) on your network.

Scheduled Discovery

With the addition of scheduled discovery, you can now automatically perform regular network discoveries at any time of the day or night. Using the Network Sonar Wizard, you can easily schedule discoveries to occur whenever best suits your network monitoring and management requirements.

VMware vSphere Monitoring

This version of Orion NPM adds the ability to monitor VMware vSphere installations by employing the VMware API to supplement ESX/ESXi server data available to SNMP polling.

Syslog and Traps

The following Syslog and Traps features have been included in this version of Orion NPM:

• Using the standard Orion ${vbName1} and ${vbData1}variable format,, trap variable binding names and value pairs are now available as alerting and message variables.
• The Trap Viewer now allows you to use pattern matching on trap details to create custom trap alerts.
• Orion NPM node variables are now available for use in Syslog and trap alerts.
• Syslog and trap alerts now respect unmanaged node status.
• Orion NPM can now change the status of an interface based on the content of a trap message.
• Forwarded Syslog messages may now be configured to retain the IP address of the original message source.
• Forwarded Syslog messages may also be configured to spoof network packets using WinPCap 3.0+.

Orion Product Team Blog

Stay in touch with the people who bring you the products in the Orion family by following the Orion Product Team Blog on thwack, the SolarWinds online user community. Read posts from Orion product managers and developers to learn how to extend and optimize your Orion installation to best meet the needs of your network.

Product Update Notifications

Receive regular, automatic notification of updates to your installed Orion monitoring and management applications in the Orion Web Console as soon as they are available from SolarWinds. Product updates can include upgrade opportunities, service packs, and hotfixes.

ConnectNow

Using topology data collected during network discovery, the ConnectNow feature in Orion Network Atlas can automatically draw lines between map objects that are directly linked (Layer 2) on your network.

Cisco EnergyWise Support

Cisco EnergyWise technology allows you to responsibly manage energy usage across the enterprise. With Orion NPM, you can view EnergyWise device management data to measure, report, and reduce the energy consumption of any devices connected to EnergyWise-enabled switches.

Network Atlas

Network Atlas, the Orion network mapping application, gives you the ability to create multi-layered, fully customizable, web-based maps of your network to visually track the performance of any device in any location across your network in real time.

Integrated Wireless Network Monitoring

An integrated wireless device poller enables you to leverage proven Orion NPM alerts, reports, and web console resources as you monitor and manage wireless thin and autonomous access points in the same views in which you are already monitoring your wired network devices.

Expanded Node Management Options

Orion NPM now provides the following node management options:

• You can designate any node as External if you want to use Orion Application Performance Monitor (Orion APM) to monitor applications hosted on the selected node without using Orion NPM to monitor the performance of the node itself.
• Orion NPM enables you to designate selected ports as unpluggable, so you no longer receive unnecessary alerts when users undock or shutdown connected devices. This feature is particularly useful for differentiating lower priority ports connected to laptops and PCs from more critically important infrastructure ports.
• It is now possible to unmanage individual interfaces.

Network Sonar

Network Sonar, the improved wizard-driven device discovery utility, further simplifies the addition of devices and interfaces to Orion NPM. Answer a few general questions about your devices, and the discovery application takes over, populating the Orion database and immediately beginning network analysis.

VMware ESX Server Monitoring

Orion NPM now provides views and resources that are tailored for virtual machines, specifically VMware ESX Servers. These new views and resources give you immediate insight into the performance of VMware ESX Servers and the virtual machines they host on your network. This version of Orion NPM also allows you to create VM-specific alerts and track the performance of your virtualization solution with custom reports generated by Orion NPM.

Custom Views of External Websites

Orion NPM now gives you the ability to include views of external websites within your Orion Web Console. With an external website view, you can designate any website as an additional tab on the Views menu bar in the web console, giving you the ability to bring web content directly into the Orion Web Console.

Additional Universal Device Poller Transform Functions

The proven power and flexibility of Universal Device Pollers have been extended with additional poller transform functions. Now you can create your own poller transforms using the sum, minimum, maximum, and average of the values in any column of any polled table.

Performance and User Interface Upgrades

In keeping with SolarWinds' commitment to give you the tools you need to manage your network, the following performance enhancements have been included in this release:

• The Web Node Management utility has both a new search capability and new interface-only views.
• Orion Web Console views for Syslog messages, Traps, and Alerts all feature new, more informative Quick Start screens to introduce you to the many related features of Orion NPM.
• A new Thwack integration resource highlights the latest Universal Device Pollers, submitted by both users and SolarWinds developers, that are available for inclusion in web console views.
• The default Start menu listing of SolarWinds tools and applications is now more intuitively organized.

Universal Device Pollers

Universal Device Pollers are a significant improvement over prior Orion NPM custom pollers in terms of scalability, ease of use, and functional capability. With Universal Device Pollers you can now test poller results, poll MIB tables, and create your own powerful transforms that can manipulate results from multiple pollers to instantly provide custom network metrics. Additionally, Orion NPM provides a more intuitive MIB Browser interface to use when creating pollers. Universal Device Pollers are fully compatible with older Orion custom pollers as well, offering full import and export, reporting, and improved alerting based on values polled from tables, transforms, and network devices.

Web Node Management

Orion NPM users can manage network devices directly from the Orion Web Console. An intuitive user interface gives you the ability to add, delete, and modify devices, both individually and in bulk, apply Universal Device Pollers, and assign custom properties, all from the Orion Web Console.

Improved User Interface and Orion Web Console Resources

The Orion Web Console user interface is continually being improved with the addition of new resources, improved charts and gauges, and more intuitive navigation features, including the following:

• A high-performance, AJAX-enabled All Nodes resource that minimizes view load times
• An Active Alerts resource listing alerts from the Application Performance Monitor and VoIP Monitor modules
• An updated Admin interface
• An option to run the web console without a session timeout
• A Custom HTML resource that now accepts variables
• A custom message that administrators can display on the Orion Web Console login screen

Thwack.com Integration

Thwack.com is the active online community for SolarWinds users, and Orion NPM provides a resource integrated on the Network Summary Home view of the web console that gives you direct access.

Monitoring Support for New Devices

Additions to the SolarWinds MIB database ensure that Orion NPM supports monitoring dozens of new devices, including VMware ESX Server.

For more information about any of these features or the many other features of Orion NPM, see the SolarWinds Orion Network Performance Monitor Administrator Guide.

Features of Previous Orion Core Releases

Previous releases of the Orion Core include the following fixes, listed by version:

• Features in the Orion Core Version 2011.2
• Features in the Orion Core Version 2011.1

Features in the Orion Core Version 2011.2

Orion Core version 2011.2 provided the following new feature.

• Discover and monitor IPv6 devices
• Discover and monitor Windows servers using WMI
• Gather statistics on a per-CPU basis for many devices
• Send and receive SNMPv3 traps
• Track and report interface availability
• Topology improvements allow you to correctly see more network device connections. For more information, see "Updated Topology Algorithm in NPM 10.2".
• CPU/Memory resources now display memory data polled from Windows devices using the Volumes MIB, even if the volume is not managed by SolarWinds
• New OIDs for CPU and memory utilization for selected Cisco and Juniper devices are now polled.

• Accelerated map rendering in the web console corrects many issues with incorrectly displayed map information
• Improved web console view-loading performance

• Network objects with Chinese labels are now represented correctly in the web console.
• Updates to the Export to PDF function properly respect filters applied to exported data.
• The Start menu now provides direct links to SolarWinds online documentation.
• New line colors in web console charts now provide improved visibility.
• Maps may now be included in Group Details views.
• Updates to the Export to PDF function properly size generated PDFs.
• Icons for Carrier Access Corporation have been added.
• Icons for Apresia / Hitachi Cable, Ltd. have been added.
• The machine types for multiple Solaris devices--including Sparc and Sun Fire devices--are now recognized.
• The text provided in the E-mail/Page Action wizard has been edited for clarity to indicate that "Multiple E-Mail Addresses should be separated by commas".
• Text input fields in Report Writer now accept Unicode characters.
• Additional Polling Engines are now able to poll all monitored objects and calculate data, independent of whether or not the primary polling engine is responsive.
• The default port for receiving incoming SNMP traps is now configurable.
• Displayed icons for ieee8023adLag interfaces have been updated.
• Page headers now display correctly for customized three-column views.
• The machine types for multiple Cisco devices--including ASA 5585, Nexus 5548, and Pix 501 devices--are now recognized.
• Hostnames are now resolved for ICMP-only nodes.

Features in the Orion Core Version 2011.1

Orion Core version 2011.1 provided the following new feature.

Extension to Multiple Series Charts82

Multiple Series Charts may now be used to display data from multiple devices on the same chart. For example, a multiple series chart can now be used to chart usage for multiple CPUs on a single node.

Fixes in Previous Orion NPM Releases

Previous releases of Orion NPM include the following fixes, listed by version:

• Fixes in Orion NPM Version 10.2
• Fixes in Orion NPM Version 10.1.3
• Fixes in Orion NPM Version 10.1.2
• Fixes in Orion NPM Version 10.1.1
• Fixes in Orion NPM Version 10.1
• Fixes in Orion NPM Version 10.0
• Fixes in Orion NPM Version 9.5.1
• Fixes in Orion NPM Version 9.5
• Fixes in Orion NPM Version 9.1
• Fixes in Orion NPM Version 9.0

Fixes in Orion NPM Version 10.2

Orion NPM version 10.2 included the following fixes and updates:

• When adding a node to an existing Universal Device Poller, changing the Group by criterion now applies to all nodes and not just the newly added nodes.
• Updates to column names in the SolarWinds database correct potential issues with custom properties.
• Updated interface polling correctly handles interfaces for which the interface name is a substring of the interface alias.
• Chart titles have been updated to clarify the distinction between bits per second (bps) and Bytes per second (Bps) and to accurately reflect the type of data presented.
• Network Sonar Discovery is now able to gracefully handle interfaces with MAC addresses longer than 50 characters by adding the corresponding interface with an empty MAC address field in the database.
  Note: Topology and mapping features require a MAC address.
• NPM charts now properly handle both ":" and "." as separators in provided dates and times.
• A blank chart no longer displays as a result of changing the timeframe of a multiple interface chart to under eight hours.
• Custom timeframes are now correctly respected on Interface Aggregate charts.
• Group status now updates correctly after interfaces previously in the group are removed from monitoring.
• Network Wide charts now properly respect view limitations.
• An issue preventing custom bandwidth changes from immediately taking effect has been corrected.
• A condition that includes extra characters in interface descriptions has been corrected.
• Filters for the types of interfaces added during Network Sonar Discovery have been updated to ensure that both licensing and import requests are properly respected.
• Network Sonar Discovery is now able to gracefully handle interfaces with indexes larger than 32-bits by skipping them and then logging the skip to the discovery log.
• SolarWinds NPM web console resources and views can now handle interfaces with indexes that are either negative or larger than 32-bits.
• Interface names that include characters from extended character sets are now represented correctly in the web console.
• The algorithm used by SolarWinds NPM to detect duplicate interfaces has been corrected to allow the import of interfaces that should have been discovered but were incorrectly judged to duplicates in NPM version 10.1.2.
• Max/Min bps In/Out charts are now included as options in the Multiple Interface Chart resource.
• An issue causing an overwrite of the view type for selected device types has been corrected.
• Stopping SolarWinds services on an additional polling engine no longer causes services on the main SolarWinds server to crash.
• A condition resulting in the storage and display of incorrect rates for Multicast and Unicast traffic has bee corrected.

Fixes in Orion NPM Version 10.1.3

Orion NPM version 10.1.3 included the following fixes and updates:

• An issue causing database maintenance issues due to duplicate keys created in the database tables for monitored wireless devices has been corrected.
• Incorrect reports of the status of some monitored interfaces as unknown was traced to frequent SNMP timeouts that are addressed in this release.98, 99, 100
• Rogue access points are now correctly identified and displayed in the web console.102
• Options to display multiple series options on Universal Device Poller charts have been restored.105
• An issue introduced on upgrade to Orion NPM 10.1.2 that caused errors in previously functional Universal Device Poller transforms has been fixed.107

Fixes in Orion NPM Version 10.1.2

Orion NPM version 10.1.2 included the following fixes and updates:

• An issue where disabled wireless and EnergyWise polling templates were enabled after upgrade has been corrected so that templates that are disabled remain disabled through and after an Orion NPM upgrade.
• Inventory reports viewed within the web console now correctly link to Node Details views for listed nodes.47
• Multiple Series Chart resources now correctly respect account limitations preventing users from editing views.
• The Set Power Level feature now functions as designed for EnergyWise-enabled interfaces on both SNMPv2c and SNMPv3 nodes monitored by Orion NPM.17
• The status of wireless and EnergyWise-enabled devices is now reported correctly after a repair to the Core SNMP library has addressed an issue with successfully completing asynchronous polling requests on SNMPv3-enabled devices.7^, 23^, 27
• Historical wireless data collected by previous Orion NPM versions that was then lost during index changes is now retained correctly.6
• Due to an known issue in certain versions the firmware (IOS) on EnergyWise-capable Cisco devices that incorrectly parses interface power levels, Orion NPM applies a correction factor to supplied interface power levels when the defective IOS is detected on a monitored device.8

Fixes in Orion NPM Version 10.1.1

Orion NPM version 10.1.1 included the following fixes and updates:

• A condition preventing the installation of Microsoft Message Queuing (MSMQ) in some environments has been corrected.
• A Configuration Wizard failure related to virtual directories created when a site for the Orion Web Console is assigned in IIS has been corrected.
• Polling completion is no longer dependent on the existence and activation of the default Admin web console account. Polling continues, even when the default Admin web console account is disabled.
• SolarWinds Collector Services have been updated to address polling delays.
• A condition where the datetime of the next node poll (Nodes.NextPoll) may report as earlier than the datetime of the last database synchronization (Nodes.LastSync) has been corrected.
• When required to stop, SolarWinds Collector Services now stop as quickly as other services.
• Database conditions generating SQL collation errors displayed in the web console Message Center have been corrected.
• Predefined Groups alerts are available as designed for users upgrading from Orion NPM version 9.5.1.
• The data type of the Notes field in alerts has been reverted to text to restore previous functionality in installations with Orion Network Configuration Manager (NCM).
• Predefined alerts packaged with Orion NPM 10.0 that have been customized prior to an upgrade to Orion NPM 10.1 are now included in the upgrade and function as designed.
• 95th percentile lines that may have been missing after an upgrade to Orion NPM version 10.1 have been restored.
• Rendering performance has been improved for nested maps and maps displayed in the web console for account-limited users.
• The correct function of Syslog filter rules has been restored.

Fixes in Orion NPM Version 10.1

Orion NPM version 10.1 included the following fixes and updates:

• Charts provided for EnergyWise-enabled devices now properly respect defined web console view limitations.
• Selected icons for wireless devices now display correctly in emailed reports.
• An issue causing Cisco Wireless Services Modules to display with multiple instances of the same thin access point has been corrected.
• Node status is now reported correctly for Cisco 4402 access points when multiple Cisco 4402 devices have similar MAC addresses.
• Historical - Interface Errors reports now display correctly in the web console.
• The titles of custom interface chart resources now correctly reflect the types of charts that are selected after resource edits are completed.
• Clicking an event listed in an Event Summary for this Interface resource now opens an Events view that is properly limited to only display events on the selected interface.
• An incorrect path used when installing the Orion NCM Integration has been corrected.
• Universal Device Poller reports that include a DateTime field now display correctly in the web console.
• The DateTime formatting of interface utilization reports that are displayed in the web console with hourly data has been corrected.
• Historical-Interface Traffic and Historical-Interface Errors now load more quickly.
• URLs provided for the ${WirelessAccessPointDetailsURL} and ${WirelessControllerDetailsURL} variables are now correct.
• Correct status reporting and node name sorting for custom Universal Device Poller reports have been restored.
• Inventory reports have been fixed to again include interfaces, as initially designed and implemented.
• Unnecessarily duplicated authentication requests have been eliminated to improve the efficiency of discovery and monitoring for SNMPv3-enabled devices.
• Charts of interfaces monitored by additional polling engines now display correctly in System Manager.
• An issue where previews of interface history reports do not show the correct date and time has been fixed.
• In charts and tables, Universal Device Poller transforms are now labeled correctly.
• An error resulting in the inability of the web console to display the Orion IP SLA Manager Internal Interface List resource has been fixed.
• URLs returned for the ${CustomPollers.CustomPollersDetailsURL}, ${CustomNodePollerDetailsURL}, and ${CustomPollerStatus.CustomPollerStatusDetailsURL} variables are now correct.
• A javascript error occurring when using the Toolset Integration to view a bandwidth gauge has been fixed.
• Custom properties using special characters - and _ are now valid for use as columns in both the Managed Nodes view and the Universal Device Poller application.
• Universal Device Pollers now retrieve full context information from SNMPv3-enabled devices.
• Security vulnerabilities in the file dwBkThrd.dll, allowing the execution of arbitrary code within the context of a currently logged-on user, have been addressed. These vulnerabilities were found by Lincoln, a member of the Corelan Team.

Fixes in Orion NPM Version 10.0

Orion NPM version 10.0 included the following fixes and updates:

• Network Atlas map icons now display consistently in Network Atlas and the Orion Web Console.
• The Last XX Syslog Messages resource now correctly sorts listed Syslog messages by date and time.
• Nodes marked as External are no longer included in the Down Nodes resource.
• Report subtitles, dates, and times now display correctly in both Report Writer and the web console.
• The Search for Wireless Clients resource now functions as intended, both for users with account limitations and for users without account limitations.
• Default colors on Network Atlas maps have been changed for improved legibility.
• An error condition related to polling the 1.3.6.1.4.1.13858.7.1.1.1.3 OID with a Universal Device Poller has been corrected.
• A socket error in the SNMP library of Windows Server 2008 that prevented the NetPerfMon service from starting successfully has been fixed.
• Automatic refresh has been restored for child maps, ensuring that realtime status is currently available.
• Orion NPM now properly handles temporary losses of connections to the Orion database.
• An issue preventing the full and automatic SNMP discovery of thin access points on some wireless controllers has been resolved.
• The Nodes with Problems resource now sorts problem nodes by problem severity.
• Configured advanced alert actions, including triggered email actions, now function more consistently.
• It is now possible to complete bulk changes to interface states using Web Node Management.
• Status bars in resources on the Top 10 view are now displayed correctly when the Top 10 view is sent by email as a scheduled report attachment.
• Text boxes and copied labels on new Network Atlas maps may now be resized in the same way that text boxes and labels both on imported maps and on upgraded MapMaker maps are normally resized.
• An Orion Website Error stating that the Object references were not set to an instance of an object on Volume Details views has been corrected.
• The ability to apply interface filters to Report from Orion Report Writer resources in the web console has been restored.
• Disk space calculations have been reconfigured to use 1024 instead of 1000 as the sizing factor for stored data and subsequent calculations.
  Note: This change does not currently apply to data displayed in graphs.
• Scheduled reports no longer include unreadable text when they are sent as attachments in printable format.
• Exporting web console data to Microsoft Excel using the URL suffix &dataformat=excel now properly handles ampersands as special characters.
• It is now possible to edit the title of selected Top XX resources in the web console that had lost the Edit functionality.
• Orion NPM now properly handles dynamic wireless access points that are switching either temporarily or intermittently between different wireless controllers.
• Predefined 95th percentile reports now function as intended in Report Writer.
• Links within attachments to emailed scheduled reports now use the fully qualified domain name (FQDN) of the Orion server.
• The following interface-related web console resources now sort correctly:
  
  • Current Traffic on All Interfaces (sorted by interface index)
  • Current Traffic on All Interfaces (sorted by node caption index)
  • Interfaces with High Percent Usage (sorted by utilization)
  • Percent Utilization of all Interfaces
• The original functionality of the Event Summary resource on Interface Details views has been restored.
• Interfaces supporting the ifAlias OID 1.3.6.12.1.31.1.1.1.18 no longer generate duplicate Interface name changed events when the ifAlias is changed.
• Automatic refresh has been restored for reports and events in the web console.
• An issue in Interface Errors and Discard charts in the web console that caused errors to display as negative values and megative chart values to display as blank has been corrected.
• Node rediscovery now correctly polls the status of interfaces on a monitored node after the node credentials are changed from SNMPv2c to SNMPv3.
• Nodes on Network Atlas maps no longer change relative positions when background images are changed.
• Changing the credentials of a monitored device from SNMPv3 to SNMPv2c can now complete successfully for valid SNMPv2c credentials.
• Values returned by variables used on Network Atlas maps now display to two digits instead of four digits.
• Traps are now displaying correctly when the Orion Web Console is viewed on Internet Explorer version 6.0.
• Temporary files created during normal refreshes of Network Atlas maps that use linked backgrounds are now correctly deleted upon expiration.
• Orion NPM now allows the inclusion of commas in the names of hosted virtual machines on monitored ESX Servers.
• Webpage detail errors occurring when hovering over web console elements have been corrected.
• The Orion Web Console no longer sounds a new alerts alarm when Internet Information Services (IIS) reboots on the Orion server.
• Top XX Syslog resources now show timestamps in local time, instead of Greenwich Mean Time (GMT).
• The Top XX Wireless APs by Clients Count resource now properly respects applied SQL filters.
• Custom property names longer than 10 characters now display correctly in the web console on Internet Explorer (IE) version 6.0.
• The ability of the Monitor Polling Engines utility to automatically connect to all Orion services has been restored.
• An issue where custom and modified reports in the web console generated errors requiring a NodeID, even for reports already containing a NodeID field, has been resolved.
• The status of unmanaged devices no longer affects the indicated status of maps on which the unmanaged devices are included.
• Default object sorting and grouping now function consistently between the Report Writer and the web console.
• When devices are discovered without resolved hostnames, instead of displaying N/A, Orion NPM now shows the device IP address, as in older Orion NPM versions.
• For EnergyWise monitoring, Orion NPM now correctly recognizes that Cisco IOS version 12.2.50 SE2 is more recent than Cisco IOS version SE.
• Network Sonar Discovery is now able to discover nodes with community strings that include ampersands (&).
• Web console users that do not have node management rights can no longer access node management buttons from Interface Details views.
• High CPU, High Memory Utilization, and High Response Time resources in the web console now properly handle devices with severity equal to 0.
• Scheduled reporting for reports containing maps has been restored.
• Traps created using Engineer's Toolset templates now correctly parse the ${IP} variable.
• A condition that prevented the return of database connections to the connection pool after selected database quesries, resulting in errors stating that the timeout period elapsed prior to obtaining a connection from the pool has been corrected.
• The "Send an Email" action for traps no longer requires an email subject.
• Traps are now displaying correctly over user-designated time periods when viewed in both the web console and the Trap Viewer.
• An issue where wireless access points with multiple SSIDs were reported in the web console as having only a single SSID has been corrected.
• An incorrect SQL query responsible for generating Invalid column name 'MachineType' errors on the Traps view of the web console has been fixed.
• An issue where alert actions fire on reset, but not on trigger has been corrected.
• Color-coded events have been restored to the Orion Web Console.
• Orion NPM can now properly poll devices, including selected Covaro and Adtran devices, that provide MAC addresses in ASCII instead of binary.
• In web console resources, node sorting by Node Name (alphabetical), instead of HodeID (numerical) has been restored.
• A condition where an Orion Universal Device Poller is not able to poll new interfaces on Cisco Adaptive Security Appliances (ASA) has been corrected.
• Correct sorting by greatest usage to least has been restored to Volumes with High Percent Usage resources.
• Percentages in Top 10 Interfaces by Percent Utilization resources now display to two digits instead of four digits.
• In the web console, it is now possible to sort nodes by community string.
• Links between nested child and parent maps have been restored when maps are upgraded to Network Atlas.
• Report grouping for custom SQL reports currently functions as designed in both Report Writer and the web console.
• The interface Out Errors Today resource has been corrected to use Packets instead of Packets per second (PPS) as measurement units.
• Clicking Edit on EnergyWise-related web console resources now displays the correct settings view.
• Network Atlas maps now properly handle interface names that include " and other selected special characters.
• As in Orion NPM versions prior to version 9.5, when clicked, a child map opens in the same window as its parent map.
• Average and peak traffic rates reports now display correctly in both Report Writer and the web console.
• The Top XX Volumes by Disk Space resource in the web console now displays correct volume-related icons instad of status icons.
• The SeverityIcon column, displaying icons representing the severity of listed Syslog messages, has been added to the Syslog view in the Orion Web Console.
• Custom properties used in Orion modules now display correctly in reports viewed in both Report Writer and the web console.
• An issue concerning incorrect or nonfunctional alert suppressions has been fixed.
• The Orion Alerting Engine now correctly parses strings containing "*".
• Orion NPM now correctly resolves selected UPS-MIB trap OIDs in the default SolarWinds MIB.
• Node captions now update correctly.
• 95th percentile reports displayed in the web console now properly respect web console account limitations.
• An exception related to updating varbinding information for traps has been corrected by providing the correct OID.
• Memory and CPU usage data for hosted virtual machines on ESX servers is now polled correctly using the VMware API.
• A new Perform reverse DNS lookup option allows you to enable or disable DNS lookups on DHCP nodes, as needed.
• Audible alerts now function as designed on remote servers.
• Syslog messages now display correctly, displaying the same information, in both the Syslog Viewer and the web console.
• Trap variables ${Raw} and ${RawValue} providing raw trap data have been implemented as designed.
• Orion NPM no longer polls the deprecated ssCpuIdle OID on Net-SNMP agents.
• The Alerts view in the web console now correctly reports the actual Network Object triggering the listed alert.
• The realtime bandwidth Gauge feature no longer attempts to use invalid security identifiers as community strings.
• Availability reports providing incorrect data have been fixed.
• Orion NPM now properly recognizes and handles events related to down DHCP nodes.
• The is not equal to operator for trap alert conditions now functions as intended.
• Custom poller reports now display times using correct offsets from Greenwich Mean Time (GMT).
• An issue where Cisco icons were duplicated and displayed in the web console for devices from non-Cisco vendors has been corrected.
• Traps of the same type from different devices are now correctly sorted in the Trap Viewer.
• Stop processing rules for traps are now correctly recognized.
• Unmanaged nodes are no longer listed in Availability reports.

Fixes in Orion NPM Version 9.5.1

Orion NPM version 9.5.1 included the following fixes and updates:

• The Orion SNMP polling engine has been updated to properly handle the case when a BGP node goes down between the Orion NPM server and a monitored device.
• The Orion SNMP polling engine has been updated to properly handle cases when SNMP sessions between the Orion NPM server and monitored SNMPv3 devices, including Foundry NetIron XMR routers, are broken.
• Memory leaks related to node rediscovery, reports, the Universal Device Poller, and wireless polling have been resolved.
• Load times for Events, Syslog, and Traps views have been improved.
• The Orion Configuration Wizard now conducts additional database maintenance operations to improve Orion NPM performance.
• Additional maintenance operations have been included in this version to improve Orion NPM polling performance.
• Monitored devices are now sorted alphabetically in the Network Object field of Events, Syslog, and Traps views.

Fixes in Orion NPM Version 9.5

Orion NPM version 9.5 included the following fixes and updates:

• The Select All and Select None functions have been restored to the web console Syslog view.
• Details tables in the Orion database are now indexed to improve performance during database maintenance.
• The loopback address for a selected device may now be used for discovery with Network Sonar.
• The Configuration Wizard no longer overwrites existing, user-defined reports with the default reports provided during the initial Orion NPM installation and configuration.
• Interface captions on Cisco Catalyst devices are now reset automatically whenever an existing caption is deleted.
• Web Node Management availability has been restored for remote users using Integrated Windows Authentication.
• The evaluation period countdown clock in System Manager is now consistent with the same clock in the Orion Web Console.
• Objects linked from within reports emailed using Orion Report Scheduler are now referenced using a full URL, instead of merely a path relative to the Orion server.
• The host server and port number are now included in object links within reports emailed using Orion Report Scheduler.
• Universal Device Poller alerts now respect reverse thresholds as designed.
• An issue resulting in unnecessarily high CPU load during database maintenance has been fixed.
• Orion NPM now triggers multi-conditional alerts on VMware ESX servers as designed.
• Web Node Management corrects an issue seen in System Manager where SNMPv1/v2 nodes reconfigured as SNMPv3 revert to SNMPv1/v2 when System Manager restarts.
• The Universal Device Poller now correctly handles transforms of counter-type pollers.
• An issue where administrative links were unavailable to accounts using Windows Pass-through authentication has been fixed.
• Orion NPM charts now honor interface-based view limitations in the same way that account limitations are respected.
• Users no longer require administrative privileges to change their own web console account passwords.
• The Current Percent Utilization of Each Interface resource now correctly displays interface data to account-limited users.
• The ability of account-limited users to filter alerts has been restored.
• The Web Configuration Backup now properly handles install paths that include spaces or dashes.
• Interface names now display correctly, even when the corresponding interface alias is undefined or absent.
• The Last XX Traps resource now properly respects column widths imposed by the view in which it placed.
• Network Atlas corrects an issue where exceeding a specific zoom level on a map renders map icons unclickable.
• An error resulting in incorrect reports of memory utilization for VMware ESX servers has been corrected.
• Word wrapping has been restored to long custom property values and descriptions.
• Icons for Aruba, ComTechEFdataMoxa, IWatsu, Sensatronics, Sofaware, and Twente have been added for use in the Orion Web Console.
• An issue preventing the display of icons for some American Power Conversion Corporation devices has been fixed.
• The Network Overview now displays correctly for both account-limited users and users with administrative rights.
• Report Scheduler no longer emails reports before confirming that Orion NPM has been able to load all requested data.
• The Alert Variables and Examples section of the Orion NPM Administrator Guide has been amended to state that some variables may require table names in the variable reference, as in ${TableName.VariableName}.
• For users with Orion modules, custom properties are no longer overwritten upon install or upgrade.
• The Orion Web Console now properly respects both user accounts using Windows Pass-through Authentication (IWA) and the DirectLink user, when both are available.
• A validation dialog has been added to confirm that a Subject is provided whenever an action is defined for a Syslog rule.
• Network Atlas corrects an issue where a number is displayed instead of a requested map.
• The ability to use host headers in Internet Information Services (IIS) has been restored.
• An issue preventing the display of reports in the web console has been fixed.
• The polling engine version for Hot Standby Engines now displays correctly in the web console.
• A deadlock condition occurring when alert definitions are updated has been corrected.
• Report Scheduler now sends Syslog reports from the web console as designed.
• The Hot Standby Engine has been updated to correct an issue related to basic alerting.
• The ViaVideo icon has been updated to display as Polycom, the Colubris icon has been updated to display as HP, and the icon for Fore systems has been added for use in the Orion Web Console.
• Availability reports that include COUNT functions are now generated correctly.
• The Orion Web Console no longer requires COM+ objects.
• Audible alerts now function correctly on remote Orion servers.
• The ability of advanced alerts to trigger the execution of external applications has been restored.
• The ability to edit the title of the Custom Properties for Nodes resource has been restored.
• Events sorted by device type now display correctly in the web console.
• Custom Node Chart resource titles now correctly update to match newly selected node chart types.
• The ability to group traps by type in the Traps Summary view has been restored.

Fixes in Orion NPM Version 9.1

Orion NPM version 9.1 included the following fixes and updates:

• Alerts, Syslog, and Traps views in the Orion Web Console currently display dates in accordance with regional settings.
• An issue involving differences among SQL Server, Outlook Express, and the Orion Web Console with respect to character encoding settings that resulted in incorrect characters appearing in emailed reports has been fixed.
• The Syslog Viewer now properly supports the Copy action from right-click context menus for viewed Syslog messages.
• A SQL error commonly seen with node alerts generated for the Application Monitor or with a Custom Poller on older versions of Orion NPM has been fixed.
• An incorrect link has been fixed for VoIP events in the Events resource on the Network Summary Home view of Orion NPM installations that include VoIP Monitor.
• It is now possible to create reports of filtered tables of data collected by Universal Device Pollers.
• Time Frame options are now respected, as designed, by custom Syslog reports created using the Syslog Viewer.
• Cisco Bridge BR500DE V8.80 bridges now display the correct machine type in Orion NPM.
• Custom charts with custom date/time periods now correctly display the date in accordance with existing regional settings.
• A duplicate "Interface Changed" event type icon has been removed.
• Web Node Management (Manage Nodes) and Application Performance Monitor links now work correctly when pass-through authentication is configured for the Orion Web Console.
• The resolution of Interface Total Bytes Transferred and Interface Total Packets Transmitted/Received charts for time intervals less than one hour has been fixed.
• Memory usage charts are now available, as designed, in the web console of Orion NPM upgrades.
• The performance of AJAX-enabled All Nodes resources has been improved for installations using many defined custom properties.
• Orion NPM has corrected the MIBs used to poll Cisco CatOS devices for interface port information.
• The Custom Property Editor is now available on Orion NPM Additional Web Server installations, allowing for the use of custom properties created in a primary installation on Additional Web Servers.
• An issue where the Universal Device Poller splash screen closes before it fully loads has been fixed.
• The ability to generate images of custom charts using URL query strings has been restored.
• An issue that resulted in website timeouts when Orion NPM attempted to create CPU Load charts for certain types of nodes has been resolved.
• The scale of the Packet Loss axis on Average Response Time and Packet Loss charts has been corrected.
• The Universal Device Poller now exhibits improved performance, including faster startup, more efficient execution, and the ability to properly poll large numbers of SNMPv3 devices.
• A duplicate key issue in the Universal Device Poller has been corrected.
• The Trap Viewer now properly respects configured trap destination ports other than 162.
• The default bandwidth value for VLAN interfaces has been corrected to 0.
• The Active Alerts resource on a Node Details view now only shows alerts for the viewed node, as designed.
• The alignment of status items in the All Nodes resource has been corrected.
• The Availability of Each Node resource now properly respects applied SQL filters.
• The Group By function in Web Node Management now works correctly for larger node groups.
• The Configuration Wizard now confirms that the SolarWinds Network Performance Monitor service has stopped before continuing, so that it is no longer necessary to restart the service after configuration completes.
• Min/Max/Avg charts now properly respect axis modifications made to corresponding *.charts files.
• Orion NPM now correctly converts variable values between bytes and megabytes (MB).
• An issue where user-created charts caused the web console to crash has been fixed.
• Web console view limitations no longer carry over to limit subsequently viewed reports if the report is not also subject to the same limitations.
• Orion NPM now properly handles custom properties with either null or empty string values.
• True/False custom properties now default to False for nodes added using Web Node Management.
• Orion NPM is now more forgiving of poorly formatted Syslog packets.
• Grouping devices using true/false custom properties no longer generates errors when creating Universal Device Pollers or when using Web Node Management.
• An issue involving the disappearance, on rediscovery, of interfaces on monitored Juniper routers has been corrected.
• Labels for Universal Device Pollers of tables are now determined and displayed correctly, even when the polled device truncates empty values at the end of the table column.
• Interface limitations no longer affect data displayed on node poller resources.
• Custom properties are now maintained on upgrade without opening Custom Property Editor.
• Min/Max/Avg charts now properly display min/max bars on charts with longer time periods.
• The search function on the web console Syslog view has been improved to provide more relevant results.
• Universal Device Poller resources have been modified to better handle specific situations when the poller is deleted.
• An issue where interfaces on deleted nodes remained in the database has been fixed, so that now, all interfaces on any deleted node are also deleted automatically.
• An icon for SONET/SDH interfaces has been added to Orion NPM.
• Bold, red highlighting has been restored for values beyond the error level threshold on packet loss chart data views.
• True/False or Yes/No custom properties now default to False or No for nodes added using Web Node Management, instead of defaulting to NULL.
• An issue where the Define SQL Variable feature of the Advanced Alert Manager was not properly forming SQL variables has been fixed.
• The datetime format used for Orion NPM charts has been changed for better international compliance.
• When creating a poller transform, the Universal Device Poller now properly respects a user selection to not display intermediate poller results in the web console.
• An SNMP timeout is now being set appropriately for interface pollers, eliminating the gaps in monitoring data that were occurring when SNMP requests were timing out before responses could be received.
• The default timeout of the AJAX-enabled All Nodes resource has been increased for better handling of nodes with large numbers of interfaces.
• Changes to the port names of Cisco devices with both CatOS and IOS are now accurately recorded.
• An issue resulting in a 404 website error in Internet Explorer 7 when Web Node Management is used to list the resources on a node has been fixed.
• The Orion Web Console now accepts multiple Custom HTML or Text resources in a single view.
• The final time period for web console charts now displays correctly.
• Advanced Alert Manager processes now stop correctly when clicking File > Exit to close the Advanced Alert Manager application.
• An issue where the x-axis on some charts was not scaling correctly over different time periods has been fixed.
• The Traps view in the Orion Web Console now correctly summarizes received trap messages.

Fixes in Orion NPM Version 9.0

Orion NPM version 9.0 included the following fixes and updates:

• Both the Orion Web Console and System Manager user interfaces have been improved.
• Event icons in the Orion NPM Web Console have been updated.
• With the new Universal Device Poller, area charts for Universal Device Pollers now display correctly when changed from the linear format.
• Old custom pollers improperly formatted data of type IP Address. Data of this type is now formatted correctly in Universal Device Pollers.
• An issue where the old custom poller service would wait for ten minutes after failing to establish a connection with the database has been with fixed with the new Universal Device Poller.
• Custom poller starvation issues have been fixed with the new Universal Device Poller.
• Since MSDE is no longer supported by Orion NPM, it is now blocked by the Configuration Wizard, which does not continue until an installation of SQL Express, SQL Server 2000, or SQL Server 2005 is detected.
• Errors in Orion NPM components related to the uninstallation of Cirrus Configuration Manager have been fixed.
• A issue with the location of navigation buttons in the Configuration Wizard has been fixed.
• The Orion Web Console now properly respects the selection of a Home Page View on the Default Menu Bar and Views page.
• The default value for Allow account to acknowledge events and alerts? option on the Account Settings page has been changed to YES.
• The Search Interface resource now functions correctly with all options.
• The IP address of the source node is now included with all forwarded SNMP traps and Syslog messages.
• The latest MIBs for multiple Cisco, Juniper, and Adtran devices have been included in the SolarWinds MIB database.
• The new Universal Device Poller fixes an issue where no data is reported for a custom poller of APC devices when there are more than 16 devices.
• Map Maker now correctly lists node and interface vendors when clicking Show All Nodes and Interfaces.
• An issue where edits to the Down Nodes resource in a Node Details view generated an error has been fixed.
• Advanced Alerts can now send messages with forwarded SNMP traps.
• Map Maker now respects the automatic hyperlink option for map objects.
• The Volume Details view now displays the node name, next to the volume caption, in the view title.
• The Configuration Wizard now enables the COM+ System Application service, if necessary.
• ICMP Echo packets are no longer sent with empty payloads.
• The status of unmanaged nodes is now properly updated and correctly reported in both System Manager and the Orion Web Console.
• The Configuration Wizard now enables the SQL Server Browser service when SQL Express is installed.
• The Configuration Wizard now properly handles ASP extensions in French and Polish versions of Windows.
• The username and password of DirectLink users is now fully validated before login.
• Triggered alerts no longer stop firing after only eight hours of activity when the alert trigger persists.
• Nodes are now properly updated with complete information when they are promoted from ICMP to SNMPv3 in both System Manager and the Orion Web Console.
• The DirectLink user is no longer logged-in automatically when activated for the Orion Web Console.
• Devices listed in the Traps Summary resource now actively link to the SNMP Traps view where all traps from the selected device are listed.
• The predefined interface status advanced alert now reports interface status correctly.
• A security issue with the report scheduler has been fixed.
• The Execute External Program action now works correctly for advanced alerts.
• The predefined Syslog Messages report now works correctly.
• A security issue with the event viewer has been fixed.
• Vendor icons for Extreme Networks, Linksys, and SNMP Research devices now display correctly.
• An error that occurred when clicking either Execute SQL Query or Preview while editing predefined Historical Traffic reports in Orion Report Writer has been fixed.
• Nordic characters now display correctly when used in node names.
• Advanced alerts, traps, and Syslog messages now pass variables through the VBscript action as designed.
• An error that would occur when filtering nodes on certain machine types has been fixed.
• Predefined 95th percentile reports now properly respect account limitations.
• An issue involving alerts not respecting escalation rules involving time offsets has been fixed.
• An issue involving the failure of a triggered percent utilization alert to reset has been fixed.
• An arithmetic overflow error encountered with 95th percentile reports has been corrected.
• Alerts that are configured to email a web page upon trigger now function correctly with Time of Day instructions.
• The traps retention period has been reduced to 30 days to limit unnecessary expansion of the database.
• An issue involving the parsing of available volume space variables has been fixed.
• Orion NPM currently polls Cisco 6500 devices correctly for utilization data.
• Orion NPM now correctly handles non-ASCII characters in maps and web console resources.
• SQL queries using custom properties in reports now function correctly.
• A database maintenance issue related to retention settings on a 64-bit system has been resolved.
• The email URL action now works correctly.
• Summarization and count reports currently display correct results.
• An issue related to the calculation of memory utilization for Net-SNMP devices has been fixed.
• Value sorting for predefined Orion reports has been fixed.

Orion Core Fixes

The following sections provide information related to fixes in this and previous versions of Orion Core.

• Fixes to the Orion Core in this Release
• Fixes to the Orion Core in Previous Versions

Fixes in Previous Orion Core Releases

Previous releases of Orion Core include the following fixes, listed by version:

• Fixes in Orion Core Version 2011.2
• Fixes in Orion Core Version 2011.1.1
• Fixes in Orion Core Version 2011.1
• Fixes in Orion Core Version 2010.2

Fixes in Orion Core Version 2011.2

Orion Core version 2011.2 included the following fixes and updates:

• Errors arising when deleting orphaned objects during database maintenance have been resolved.
• Values returned by selected date and time variables have been corrected.
• Network Sonar Discovery and Node Management no longer truncate node names to 32 and 40 characters, respectively.
• Orion Report Scheduler now correctly shows existing jobs as scheduled for the current Windows user, even when they are scheduled for other users. Changing the account name under which a job is scheduled no longer defines a completely new job under the new user account name.
• An issue resulting in the display of incorrect text in exported PDFs has been fixed.
• An issue causing errors when previewing reports in the web console has been traced to a failure to translate Wahr/Falsch, in German, as True/False boolean values. Report schemas have been updated accordingly.
• Database Manager now allows Orion user accounts with dbo_owner and public permissions to access the SolarWinds database. Previously, sysadmin privileges were required.
• It is now possible to use the Select All checkbox, without causing errors, to select more than 250 objects in Node Management.
• The SolarWinds MIB database (MIBs.cfg) has been updated Alvarion OIDs.
• The Seed Router selection method available in Network Sonar Discovery now properly handles seed routers requiring SNMPv3 credentials.
• The correct NetObjectID property was added to trap templates that were not properly updated for a previous release.
• An issue resulting in the requirement of an excessive period of time to add a single monitored object has been corrected.
• With improvements to Network Discovery, the full name of nodes with names longer than 32 characters is now stored in the SolarWinds database.
• An issue preventing the successful get of required security identifiers (SIDs) for group accounts has been resolved. SolarWinds no longer allows Active Directory authentication or account creation for groups that do not have non-empty SIDs.
• The Export to PDF feature now functions correctly when the web console is assigned to a specific IP address and the PDF is exported from a remote machine accessing the web console by hostname and not by IP address.
• An issue resulting in failures to poll volumes after performing database maintenance has been corrected.
• The contact SolarWinds link provided on the Completing the Orion Configuration Wizard view has been corrected.
• Negative values supplied by the VMware API for memory usage statistics are properly handled to provide correct results.
• Learn more links on the Add New Account page have been fixed.
• The acknowledge alert link in emails sent by triggered Orion APM application alerts now functions as designed.
• The Unmanage Scheduling Utility now properly handles the case when default custom properties are deleted.
• Schemas for selected Inventory reports have been updated to correctly report polling engines.
• New Scheduled Report tasks can now be created without error for Active Directory users.
• The web console now properly handles the maintenance of multiple Edit Object Properties views, each in different tabs in the same browser.
• Updates to the SolarWinds poller have improved polling completion percentages.
• A website script error that is thrown when managing groups containing large numbers of devices on the Manage Groups view has been fixed.
• The Configuration Wizard no longer deletes existing https bindings on upgrade or repair.
• An issue where domain names for DHCP nodes were truncated before insertion into the SolarWinds database has been corrected.
• New Scheduled Report tasks can now be created without error when the Terminal Server Windows component is installed.
• Network Atlas no longer fails to complete file synchronization with the Orion database. This failure had been linked to Network Atlas users who had insufficient permissions to access the Network Atlas synchronization folder.
• Cisco Catalyst 2960-S Series Switches (Model WS-C2960S-48FPS-L) are now correctly identified by Network Sonar Discovery.90^, 94
• SolarWinds now polls the correct object identifiers (OIDs) for monitoring IBM AS/400 disks.
• The web console now properly handles the maintenance of multiple list resources, each in different tabs in the same browser.
• Updates to Network Atlas improve how Network Atlas handles groups and custom properties.
• Spaces are no longer removed from messages supplied to the Modify Syslog Message action.
• Updates to the SolarWinds Information Service (SWIS) enable the Configuration Wizard to more gracefully handle corrupt performance counters when validating the NetPerfMon service.
• An error that left the To: field out of email messages sent as alert actions has been fixed.
• The machine types for multiple American Power Conversion Corp. devices--including back-ups, matrix-ups, and smart-ups devices--are now correctly recognized.
• Events for node name changes have been restored.
• Clicking displayed results in the Nodes with High Memory Utilization resource now displays the correct Memory Utilization chart.
• The web console now proparly handles resources assigned a ResourceID of 0. Previously, resources with a ResourceID=0 would cause web console errors.
• Removing a VMware DataCenter from monitoring no longer generates an error in the VMware Assets resource. ESX hosts on the removed Datacenter are automatically reassigned to their new DataCenter for monitoring.
• The Selected Node Properties resource now correctly provides all custom properties that are available for listing for a selected node.
• A condition where objects in a scheduled unmanage period are not restored to a managed state as scheduled, if the DataProcessor service is restarted during the unmanaged period has been corrected.
• Trap messages for email that include null characters (\0) in the values for listed variable bindings are no longer cut off at the null character.
• A condition preventing secured WCF sommunication between polling engines in a multiple polling engine environment, resulting in website errors, has been corrected.
• The Last XX Syslog Messages resource is now capable of displaying more than 25 messages at a time.
• IOS version information is now reported correctly on the Node Details view for selected Cisco devices.
• Grid lines have been restored to separate items listed in web console resources.
• Resources on the Node Details view now properly handle virtual machines returning null as the Powered State.
• SQL variables using the "@" prefix now function correctly when included in HTML-formatted email messages.
• Failures of the SolarWinds Collector Job Engine v2 due to incorrectly handling an error resulting from attempts to poll an incorrect OID for interface MAC addresses have been corrected.
• Updates to code in the Orion SNMP library enable the addition of SNMPv3 devices, as designed.
• The machine type for Cisco ASA5580 devices is now correctly recognized.
• URLs longer than 255 characters are no longer truncated when provided in the Orion Report Scheduler.
• The machine type for IBM P595 PowerPC devices is now correctly recognized.
• Node custom properties assigned floating point values, are now validated correctly in the web console.
• The web console now uses the UTF character set. This corrects a number of issues with how reports appear in the web console.
• Network Atlas running on Windows 7 now accepts Active Directory credentials, as designed.
• Network Atlas map resources now display correctly on the Group Details veiw of the web console.
• SolarWinds SSL certificates are now created using the SHA1 has algorithm, instead of the less-secure MD5 algorithm.
• SolarWinds APM variables ${ComponentsWithStatusFormatted} and ${ComponentsWithProblemsFormatted} are now translated correctly for use in email actions.
• The Send Syslog Message action now functions as designed when the Syslog Message Facility is set to local use - level 0.
• It is now possible to edit the filenames of PDFs exported by the Orion Report Scheduler.
• The compressed archive created for the SolarWinds Diagnostic Utility has been updated to enable extraction on Windows Server 2003.
• Network objects selected in Network Sonar Discovery to be ignored no longer display on the Devices to Import tab.
• The Send New Syslog Message alert action can now send messages to custom ports.
• An issue preventing the correct display of node states in the web console has been corrected.
• An error that regularly corrupts the collector SDF has been fixed, allowing the Collector Data Processor and Collector Polling Controller to start, as required.
• Job Engine v2 credentials are now correctly synchronized, allowing effective communication between polling engines.
• An issue resulting in errors in Syslog resources on the Network Summary page, has been traced to an incorrect translation of a localized date, using "." instead of ":", and it has been fixed.
• A security issue preventing valid user access to selected reports and views in the web console has been corrected.
• Failures in vCenter polling due to undetermined validity of provided credentials have been fixed.
• An issue resulting in stopped polling and 'VMware Guests with Problems" errors has been resolved.
• The titles of object properties, including custom properties, are now stored correctly, with spaces, in the database, preventing the collapse of Custom Property List resources into a single line.
• The correct timestamp is now displayed for syslog messages both in the Node Related X Syslog Messages resource and in the Last X Syslog Messages resource.
• The SolarWinds MIB database (MIBs.cfg) has been updated with the correct value for the cExtSnmpTargetAuthInetAddr OID.
• An issue that forced links to the Admin Settings view to instead open the Network Summary view has been corrected.
• A change in the format of forwarded Syslog messages has been corrected.
• Monitored objects with Chinese names are now correctly displayed with Chinese names in the web console.
• Cisco Catalyst 2960, 3560, and 3760 Series Switches are now correctly identified by Network Sonar Discovery.
• The alignment of labels in Network Atlas has been improved to better indicate object status.
• Network Sonar Discovery can now accept community strings of up to 250 characters in length.
• Virtualization monitoring now better handles credentials for wireless ESX hosts that regularly lose connection (drift in and out of range).
• Documentation has been updated to direct the installation of Additional Polling Engines and Additional Web Servers.
• An issue that has caused both the trap service and the SolarWinds Information Service to restart repeatedly when upgrading multiple poller environments has been fixed.
• An issue related to dependencies that resulted in polling delays has been fixed.
• An issue preventing the display of variables in triggered alerts has been fixed.
• An issue preventing the trigger of basic alerts from additional polling engines has been fixed.
• An issue with trap filters that prevented trap alerts from triggering has been fixed.
• The SolarWinds installer now deletes orphaned job scheduler results before completing an upgrade to the current version of SolarWinds NPM.
• Groups defined on a dynamic basis now update as required.
• A condition resulting in the display of negative polling completion rates has been corrected.
• An update to the SolarWinds Information Service corrects an error with serialized query results seen when the NCM web console integration is installed.

Fixes in Orion Core Version 2011.1.1

Orion Core version 2011.1.1 included the following fixes and updates:

• An error in the Orion Core preventing the proper completion of interface rediscovery in Orion NPM has been corrected.96
• A condition resulting in the occurrence of Polling Out Of Memory errors when moving monitored objects from one poller to another has been fixed.97
• Both the SolarWinds MIB database and the SolarWinds Traps service have been updated to correctly parse OCTET varbind OIDS.101, 103
• This release corrects a condition causing incorrect reports of some monitored objects as removed and added back. These incorrect reports have been traced to database connectivity issues leading to unexpected, empty database records.104, 108
• In environments where multiple virtual machines are monitored, clearing the Poll for VMware option for any single virtual machine no longer stops monitoring for all virtual machines.106

Fixes in Orion Core Version 2011.1

Orion Core version 2011.1 included the following fixes and updates:

• Unpluggable interfaces no longer generate "Up" events when they are reconnected.4^, 5^, 9
• Default database connection timeouts were reconfigured to correct an issue causing frequent restarts of the SolarWinds Orion Module Engine service.1
• Security vulnerabilities (dwBkThrd.dll) allowing the execution of arbitrary code within the context of a currently logged-on user have been addressed. These vulnerabilities were found by Lincoln, a member of the Corelan Team.
• An issue with successfully completing asynchronous polling requests on SNMPv3-enabled devices has been addressed with a repair to the Core SNMP library.10
• The Trap Viewer now correctly handles IPSEC tunnel-related peer addresses provided in hexadecimal format.11
• Square bracket characters ([ and ]) used in virtual machine names are now displayed correctly in virtual machine resources in the web console.11^, 12
• The following vendor icons are now correctly displayed in the web console:21
  
  • Asentria
  • Ceragon
  • Dragonwave
  • Motorola PTP (formerly Piping Hot Networks or Orthogon System)
  • Redline
  • Wichorus/Tellabs
• Additional Poller installations that encounter licensing issues requiring a license reset no longer fail quietly.14
• Cisco Small Business Pro ESW 520 series switches are no longer incorrectly identified as Cisco Catalyst Express 520 series switches.18
• A condition leading to false reboot alerts after certain Orion upgrades has been fixed.24^, 52^, 53^, 54^, 55^, 57^, 59^, 66^, 67^, 69^, 70^, 71^, 72^, 73^, 75^, 78^, 83^, 84^, 85^, 87^, 91
• SNMP traps sent to multiple specific destinations as the result of an alert trigger are now correctly sent to only those destinations designated and are no longer broadcast, as previously.20
• When completing an installation, the Configuration Wizard now correctly identifies and properly handles older copies of required .dll files.22^, 30^, 31
• Auto-detection for mobile devices has been improved, and it is now enabled by default.29
• The acknowledge alert link in emails sent by triggered Orion APM application alerts now functions as designed.26^, 48
• An issue encountered by users using account names starting with u (Domain\User) while attempting to acknowledge alerts through the web console as viewed in Internet Explorer has been resolved.37
• The method used to calculate response time was reverted to restore correct results, as displayed in earlier versions of Orion NPM.35^, 61^, 86^, 88^, 89
• Network Sonar now accepts discovery profiles supplying unencrypted SNMPv3 credentials.36
• Delays in the Syslog Viewer related to high memory utilization by the Syslog service and have been corrected.33^, 34^, 38^, 46^, 50^, 56
• A note prohibiting the use of physical address extension (PAE) on x86 servers has been added to the Orion Server Hardware Requirements section in the SolarWinds Orion Network Performance Monitor Administrator Guide.42
• A "No Software License Key Installed for Standard Edition" error caused by a failure to update Orion8NetPerfMon.dll on upgrade has been corrected.40^, 41^, 44^, 45
• Orion no longer displays Cisco 1900 Series integrated services routers as wireless devices.43
• The Orion Server Hardware Requirements section in the SolarWinds Orion Network Performance Monitor Administrator Guide has been updated to indicate the minimum size of the primary C: drive on the Orion server.25
• Credentials handling for monitored SNMPv3 devices has been improved to address high CPU usage on the Orion server.58^, 64
• An issue preventing Orion from respecting custom values greater than 300 seconds for the Node Warning Level polling setting has been resolved.51
• The caption field for traps is now updated correctly, so the caption field is now viewable, as intended, in the Trap Viewer.19^, 60
• The method used to calculate packet loss was reverted to restore correct results, as displayed in earlier versions of Orion NPM.49
• An issue where cached maps were displayed for different users, overriding local settings, has been fixed.62^, 79
• When multiple Syslog messages are forwarded as traps, each trap is now assigned its own varbind, so that all Syslog messages are now received and viewed correctly in Trap viewer, instead of only the first.63
• AccountID and Password are no longer included in links to original views that are exported as .pdf from Report Scheduler.68^, 65
• Data losses due to a fatal error where access to the Job Engine is denied because of the excessive size of a job result have been corrected.74^, 81
• Changes made to community strings stored for devices monitored by Orion no longer require a restart of the SolarWinds Network Performance Monitor service to take effect.76^, 77^, 80^, 92^, 93

Fixes in Orion Core Version 2010.2

Orion Core version 2010.2 included the following fixes and updates:

• The Orion Report Scheduler is now able to update the associated tasks in the Windows Task Scheduler, as required to disable a currently scheduled report, on both Windows Server 2008 and Windows Server 2008 R2.
• Cisco 4400 and 5500 series wireless controllers are now correctly identified in the web console.
• Group names are no longer duplicated when used for sorting in web console reports.
• Error messaging has been improved in the Orion Report Scheduler to more clearly indicate when insufficient permissions exist to create a Windows task for a scheduled report.
• Web Node Management operations, including deletion, now operate as designed when multiple objects are selected simultaneously.
• The Orion Web Console now properly handles both views that have been administratively deleted and views that have been edited to not include any resources.
• Typographical errors in the web console have been corrected.
• An error that would occur when the Configuration Wizard would attempt to connect to a SQL Server hosting both full and express instances has been fixed.
• A conflict error occurring during database maintenance on selected tables related to network discovery profiles has been fixed.
• The ConnectNow feature of Network Atlas is now able to correctly connect Cisco switches with VLAN functionality regardless of whether or not VLAN indexing is enabled on the switch.
• SNMPv3 credentials now update to empty strings when the SNMP version used to poll a monitored device is changed from SNMPv1 or SNMPv2c to SNMPv3.
• Syslog- and traps-related errors occurring on installations that include multiple polling engines and that monitor multiple nodes with the same IP address have been resolved.
• A condition where changes to the IP address of a monitored object are overwritten during Network Discovery has been corrected.
• In the event that SNMPv3 is selected as the SNMP version for a monitored device, Orion no longer tries to use default SNMPv2c credentials if no SNMPv3 credentials are provided.
• Unmanaged devices are now cleared from web console resources and views, as designed.
• Existing schema files required by Orion modules are no longer deleted during an upgrade.
• Upgrades no longer create new menu bars within additional tabs for all web console users.
• The SolarWinds Information Service is now able to properly handle Memo-type custom properties.
• For installations that include it, the Orion NetFlow Traffic Analyzer tab is no longer deleted on upgrade.
• On upgrade, older SolarwindsJobEngine and SolarwindsJobScheduler registry entries are correctly deleted.
• More accurate OIDs are now used to determine the memory utilization of monitored Linux devices.
• Reports with Day of Week and Time of Day fields now display correctly, consistent with each other, both in Orion Report Writer and in the Orion Web Console.
• Network Sonar Discovery correctly determines and deletes duplicate node and volume entries.
• A security vulnerability related to windows authentication that allowed one user to log in, log out, and then log in again as a second user if the second user's password was blank, has been fixed.
• Nodes marked as External no longer display in the Nodes with High Response Time resource.
• Orion is now able to better handle upgrades of installations that maintain tens or hundreds of thousand of Syslog records.
• Conditions leading to an Exception in Service Timer Tick error occurring in environments where a Hot Standby Engine is deployed have been corrected.
• Files required for Network Atlas maps have been reorganized to improve performance.
• This version of Orion introduces significant performance improvements to regular and upgraded installations of Network Atlas.
• Non-administrative web console users are no longer denied access to Events and Alerts views, provided they are not otherwise aubject to related account limitations.
• Report Scheduler is now able create scheduled reporting jobs for user that are authenticated with passwords that include special characters.
• When multiple web console administrator accounts have been enabled, the Configuration Wizard now uses the correct account to import sample maps, correcting an issue causing "Import of Sample Map Failed" errors.
• The Current Response Time & Packet Loss resource on Node Details views now displays correct values for Current Response Time and Packet Loss. The Nodes with High Response Time resource on Node Details views now displays the correct values for Current and Minimum Response Time.
• A report generation error occurring in the Report from Orion Report Writer resource in the Orion Web Console has been corrected.
• Filtering by interface has been restored to the Custom Property Editor.
• Status is now correctly determined and reported for volumes on nodes that have been down in the past.
• A condition causing some advanced alerts to trigger twice when they should only fire once has been corrected.
• Report Writer and Advanced Alert Manager now function as designed when launched by multiple users, some administrative and others not.
• A condition causing unauthorized access exceptions when running the SolarWinds Diagnostics tool on Windows Server 2008 has been corrected.
• Images now display as designed in resources and reports generated as Report Scheduler jobs.
• Reports resources now display correctly in the web console when viewed in Internet Explorer.
• The installation path for the MIB database has been corrected for Orion installations on German operating systems.
• Monitored devices previously displaying with "Sunfire" as the vendor now display correctly with Sun as the vendor.
• The "Change interface status" action now functions as designed when triggered by a received trap.

Development and Support ID Fix Table

The following table provides the internal Development ID numbers and external support ID numbers for recent items documented in these release notes. Search in the Support ID Number column for the number assigned to your support case. The Superscript link will take you to the relevant item in these release notes.

Legal

Copyright © 1995-2012 SolarWinds, Inc. all rights reserved worldwide. No part of this document may be reproduced by any means nor modified, decompiled, disassembled, published or distributed, in whole or in part, or translated to any electronic medium or other means without the written consent of SolarWinds All right, title and interest in and to the software and documentation are and shall remain the exclusive property of SolarWinds and its licensors. SolarWinds ®, the SolarWinds logo, ipMonitor ®, LANsurveyor ®, and Orion ® are among the trademarks or registered trademarks of the company in the United States and/or other countries. All other trademarks contained in this document and in the Software are the property of their respective owners.

SOLARWINDS DISCLAIMS ALL WARRANTIES, CONDITIONS OR OTHER TERMS, EXPRESS OR IMPLIED, STATUTORY OR OTHERWISE, ON SOFTWARE AND DOCUMENTATION FURNISHED HEREUNDER INCLUDING WITHOUT LIMITATION THE WARRANTIES OF DESIGN, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL SOLARWINDS, ITS SUPPLIERS OR ITS LICENSORS BE LIABLE FOR ANY DAMAGES, WHETHER ARISING IN TORT, CONTRACT OR ANY OTHER LEGAL THEORY EVEN IF SOLARWINDS HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

Microsoft ®, and Windows 2000 Server ®, Windows 2003 Server ®, and Windows 2008 Server ® are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.

Graph Layout Toolkit and Graph Editor Toolkit © 1992 - 2001 Tom Sawyer Software, Oakland, California. All Rights Reserved.

Portions Copyright © ComponentOne, LLC 1991-2002. All Rights Reserved.