These release notes provide pre-installation and post-installation guidance for SolarWinds Orion Network Configuration Manager (NCM) 7.2.2
SolarWinds NCM versions 7.0 and after differ from other SolarWinds NCM releases in that it is integrated with a core platform of components that are common to all SolarWinds network monitoring products. As a result, the SolarWinds NCM software interacts with two separate databases: an NCM database for storing NCM-related data and an Orion Platform database to manage information such as account information that can be shared across all SolarWinds network monitoring products.
One-time jobs may run unexpectedly after job migration. To mitigate this behavior, manually disable all one-time jobs.
By default, during device discovery, the Orion node discovery software adds new nodes both to the Orion Platform and NCM node lists. While you can have Orion Platform nodes that are not managed NCM nodes, you cannot have NCM nodes that are not also Orion Platform nodes. If you were to remove a node from Orion Platform that node would also be removed from SolarWinds NCM along with all currently stored data about inventory, configs, etc. In short, DO NOT delete any node from Orion Platform (HOME) for which you want to retain such historical data.
SolarWinds NCM version 7.2.X includes the following new features and improvements:
Note:The web interface for selecting individual nodes supports adding up to 1000 nodes to an xisting scheduled job.
Upgrading to version 7.2 NCM migrates jobs from the desktop application to the Orion Web Console. As a final step in the upgarde process, you must check that your jobs have been correctly migrated. For any job that is not migrated or incorrectly migrated, use the job management features (CONFIGS > Jobs) in the Orion Web Console to recreate or adjust them.
NCM was tested for scalability in a standalone deployment of three servers: One server hosts the main NCM server and the other two servers each host an NCM additional polling engine. The main NCM server manages up to 10K NCM nodes, as do each NCM additional polling engine. The deployment therefore supports up to 30K nodes total.
And while using the NCM web console in a normal way, with the Orion Platform on the main NCM polling for node status at the default rate, the tested deployment supports 2 NCM operations (inventory update, configuration download) being performed per day on all 30K nodes.
Though the main NCM server and each additional polling engine can manage up to 10K nodes, the actual total depends on the system hardware of the server hosts, the types of devices being monitored, and the number of jobs being run concurrently. Should you need to manage more devices, and you decide to add NCM servers, consider consolidating your views of multiple servers with the Orion Enterprise Operations Console. For more information about scaling NCM, please contact your account manager.
|Fixes a conflict with NCM Win32 application related to jobs that prevents the application from starting. |
|Fixes an issue that prevents adding nodes to a nightly config backup job. |
|Enhances ASA device template to send carriage return/line feed with each command. |
|Fixes error on Edits Job page when a custom property used for grouping is deleted. |
|Fixes a problem related to a memory leak that causes scheduled jobs to fail when the targeted node count is high (5K+). |
|Fixes a problem related to a scheduled job failing to start on schedule; it replaces the Job Engine with a new version (220.127.116.11). |
|Fixes NCM Additional Poller installation |
|Fixes frequent return of no results in IP searches. |
|189806, 293953, 304513, 340673|
|Unblocked ability to save a config change report to a file. |
|Fixes error related to upgraded from 7.1 to 7.2.||510132|
|Fixes problem with creating a job when SMTP is invalidly configured. |
|Fixes a SolarWinds Configuration Wizard error. |
|Enhances jobs performance. |
|Provides validation for SMTP server settings. |
|Fixes and issue with a download job spread over three pollers generating three emails related to the job. |
|Fixes a problem with node selection criteria that results in jobs running on the same nodes on all pollers |
|Improves error messaging when NCM application fails to start. |
|Fixes website error when specific characters are used in a job name. |
|Fixes problems associated with complex passwords. |
|Fixes error in accessing an NCM web page. |
|Fixes issue with NCM web component being removed with when you re-run NCM installation. |
|Fixes issue FIPS manager that erroneously indicates a node has unsupported protocols. |
|Fixes limitation on the ability to enter an external link in manuallly assigning EOS dates. |
|Improves Regex syntax documentation. |
|Configs can be imported from a file and then managed with downloaded configs. |
|Fixes search failure in web console for "last downloaded configs" |
|Fixes issue in which diffs between two running configs are reported as a running vs. start-up config |
|Fixes Web Console error "Object reference not set to an instance of an object" |
|A restore of a configuration reports that I did not select Write to NVRAM - yet there does not appear to be an option to write t - Verified. Created TC_1586 |
|Fixes config export job |
|Adds VLAN Report. |
|Fixes node password encryption settings |
|Fixes an error with the NCM application not running - adds better error handling when user does not add information in Configuration Wizard. |
|Fixes handling of error state in which language in database is set to other than English |
|Fixes Policy Reporter error by addings logic in which NCM replaces all CRLF by LF in downloaded config before the config is added to th database |
|Fixes a problem with custom properties partially sharing a name |
|Fixes a problem with NCM picking-up node name changes that originate on the device |
|Upgrades security for storing passwords to FIPS standard. |
|Corrects reporting so that no policy violations displays an accurate message instead of show no data |
|Adjusts NCM "Add or Manage Nodes" page to honor account limitations |
|Fixes issue with real-time jobs never being removed from the Windows Task Scheduler |
|Adjust NCM's ability to recognize the beginning of a device config and filter out extraneous echo information as irrelevant to config download. |
|Fixes ability to run "Backup Status of Running Config" or "Backup Status of Startup Config" reports either within NCM application or within the Orion Web Console |
One-time jobs may run unexpectedly after job migration. To mitigate this behavior, manually disable all one-time jobs.
|Due to a limitation in the logic of CRON functionality, specifing that a job should run Daily, Every X days, does not work.||NA|
|EOC 1.3 cannot poll NCM 7.2. See this KB article.||NA|
|NCM will not honor node limitations in executing jobs. So if you are an Orion platform administrator with account limitations that are designed to limit your area of operation to a specific set of nodes, but you use NCM job editing controls to limit the nodes upon which a specific job acts, NCM will ignore those limitations. Keep in mind that any job you create or edit will affect all nodes to which your Orion platform Administrator account gives you access.||NA|
|"Start Now" job execution does not work if your running a separate server integration of NCM/NPM||NA|
|Several protocols/settings/encryption algorithms were not tested: ||NA|
|NCM resources do not work correctly when they are on same view as PaM's resources||NA|
|Node List Loads Slowly in NCM Application |
The list loads slowly with a large number (10K) of nodes in the database and if the nodes are not grouped.
|Browser Script Error |
A script fails when loading a node list that contains a group with 30K or more nodes.
|Physical Entities (Serial Number) report loads slowly |
When there is a large number of records (a million or more) this report loads slowly. However, if you select the sort on a single column option (Settings > NCM Settings > Advanced Settings) then the report runs normally.
|Access to Orion Web Console Blocked After NCM Installation |
This happens if the SQL account you have assigned to your Orion Platform database has not been configured with apppropriate permissions. You must create a new SQL account with required permissions as detailed in thisKnowledge Base article.
|Config Download Aborts |
When downloading a config from a device, if the config line (for example, the hostname on a line by itself in the banner text) exactly matches the length of the device's prompt, the download ends.
Since the issue is almost always triggered by banner text, make sure that you surround any such text with comment operators. For example, if your hostname appears in the banner text as LGC6509E, you would change it to "*LGC6509E*
|NCM Repair and Change Processes |
If you are running NCM server on Windows 2008, and you need to repair NCM or change its installation, follow the steps in this Knowledge Base article.
|Telnet Icon in NCM Node Details (IE) |
The Telnet icon on the NCM Node Details page and the Configuration Change Report results page of the SolarWinds NCM Web Console does not launch the Telnet window. To correct this issue, add the following registry value:
|NCM Search Does Not Find Partial Word Values (IE) |
Due to the use of Full-Text Search, partial word searches are not supported. You can find the beginning of a word, but you cannot specify the middle or end of a word on which to search.
|Importance of policy updates (Cisco Energywise) |
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.
|Time returned by device (EnergyWise) |
The time returned by and 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 SolarWinds NPM or SolarWinds NCM.
|Recurrence Policy 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 SolarWinds NPM as Sunday and will cause problems with your EnergyWise Policy Overview Calendar.
|International time format |
A number of areas in the Local Client application, the Web Console, and the SolarWinds NCM Integration for SolarWinds 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.
|NCM resources added to NPM |
Adding SolarWinds NPM summary or node details resources to SolarWinds NCM views can result in the SolarWinds NPM resources no longer respecting node filtering, essentially providing a network-wide view.
Note:: Do not install NCM on a machine with a hostname containing more than 15 characters.
This version of SolarWinds NCM depends on Orion Platform components (most notably, the polling engine, network sonar discovery, the alert engine) with which SolarWinds NCM is tightly integrated during the installation and configuration processes. As part of this new architecture, regardless of whether or not SolarWinds NCM is integrated with another SolarWinds network monitoring product (such as SolarWinds NPM), the installation software creates a new Orion Platform database where nodes are primarly managed. So, essentially, SolarWinds NCM uses an Orion Platform database to manage all nodes, and an SolarWinds NCM database to manage node configs. During the installation/upgrade process, two different Configuration Wizards run; one for the Orion Platform database, the Orion Platform website and services; and another for the SolarWinds NCM database and services.
If you are aware of your own deployment type and the installation process it entails, installing this version of SolarWinds NCM should go smoothly. However, SolarWinds strongly recommends that you carefully follow the procedures in the "Installing Orion Network Configuration Manager" section of either the Orion Network Configuration Manager Administrator Guide or the Orion Network Configuration Manager Evaluation Guide as you are installing and configuring this version of the product.
You do not need to uninstall your previous version before installing this version of SolarWinds NCM. Shutdown any running SolarWinds NCM applications, and then run the setup program. The setup program will detect and uninstall your previous version without a loss of customizations, other than customizations to the toolbar. Toolbar customizations are overwritten to ensure new toolbar options are included.
Backup your database before performing any upgrade of SolarWinds NCM.
If you are an existing customer, and your current version does not qualify for a direct upgrade to SolarWinds NCM version 7.2, you first must install the versions of SolarWinds NCM that at least bring your installation to SolarWinds NCM version 7.0. For example, if you are running SolarWinds NCM version 5.5, you need to install SolarWinds NCM versions 5.5.1, 5.5.2, 6.0, 6.1, and 7.0 before you can install SolarWinds NCM 7.2. Additionally, in this case, should you want to gain access to the latest NCM/NPM integration features, you would need to upgrade your SolarWinds Network Performance Manager software to version 10.5 (Orion Platform 2013.1).
If you need previous versions of SolarWinds NCM, Contact Customer Service and Support (firstname.lastname@example.org).
NCM 7.2 uses an Orion Platform of core components shared by all SolarWinds network monitoring and management products. If NCM is installed on a server with another of these products the installer automatically integrates them.
So, for example: You are currently running SolarWinds NCM on a server with SolarWinds NPM, but the two products are operating independently. If you upgrade to SolarWinds NCM version 7.2, the installer will automatically integrate SolarWinds NCM with NPM. In this case or cases like it, if you do not want to integrate SolarWinds NCM with another SolarWinds network monitoring product currently running on the same server, install SolarWinds NCM version 7.2 on its own server. To do that, consult the section “Moving Orion Network Configuration Manager” in the SolarWinds Network Configuration Manager Administrator Guide.
Note: The Orion Platform software components does not support multiple address types associated with a node. So if in NCM you have an IPV4 and an IPV6 address associated with an NCM node, when you upgrade to NCM 7.2, and synchronize your databases, only the IPV4 address will be retained in the Orion Platform database for the node.
Note: In upgrading a deployment that is already integrated with SolarWinds NPM, the SolarWinds NCM installer will shutdown all SolarWinds services on the host machine where SolarWinds NPM is running. Bear this in mind in choosing a time to perform your upgrade.
You must license SolarWinds NCM from the appropriate server in your deployment.
If you are deploying SolarWinds NCM on one server and integrating with SolarWinds network monitoring products on a different server, then you must install the SolarWinds NCM license on the server running the other SolarWinds network monitoring product.
For example, if you are integrating SolarWinds NCM on one machine with SolarWinds NPM on another, you would install your SolarWinds NCM license on the machine that is hosting SolarWinds NPM. Keep in mind that such a deployment is possible only if you are an existing user of NCM 7.x and are upgrading to version 7.2. A new installation of NCM 7.2 does not support the separate server deployment type.
See "Obtaining a Software License Key" in the Orion Network Configuration Administrator Guide for details on licensing SolarWinds NCM.
In order to continue to drive innovation and new functionality into our products, SolarWinds must transition customers from legacy versions of software to our current versions. Please review the below support schedule:
View the SolarWinds EOL Policy online.
Copyright 1995-2012 SolarWinds Worldwide, LLC. 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 respective licensors.
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, NOR 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.
The SolarWinds, the SolarWinds & Design, ipMonitor, LANsurveyor, Orion, and other SolarWinds marks, identified on the SolarWinds website, as updated from SolarWinds from time to time and incorporated herein, are registered with the U.S. Patent and Trademark Office and may be registered or pending registration in other countries. All other SolarWinds trademarks may be common law marks or registered or pending registration in the United States or in other countries. All other trademarks or registered trademarks contained and/or mentioned herein are used for identification purposes only and may be trademarks or registered trademarks of their respective companies. Microsoft®, Windows® and SQL Server® are registered trademarks of Microsoft Corporation in the United States and/or other countries.