Cirrus & Orion Config Listing

Question

Hi Everyone,

I have an issue where the Config Listing module within Orion cannot find the config that is downloaded from Cirrus.

I have pin pointed the issue down to the actual node name naming difference between the 2 applications.

For example in Orion I have a node called "node" with ip address "1.1.1.1" , if I then add the same device in Cirrus with ip address "1.1.1.1" it then populates the name (which it gets from device) with "node.aus.company.com". So when I click the config listing within Orion its looking for the configs for "node", but within Cirrus that does not exist, its "node.aus.company.com", so essentially it tells me the file does not exist.

When I view the node details in Cirrus the Node Name, and System Name are different, where in lies the issue.

Has anyone had this same issue? I am thinking it may be an issue with the actual config on the device and with the "ip domain-name ...."

chris.lapoint · Answer

If you're on the Cirrus 4.x, the database upgrade is taken care of by the NCM 5.0 installer.   If you're on 3.x.x, you'll need to get to 4.x before you're ready to upgrade.

Pankaj.kakade · Answer

Hi ,

How to upgrade from Cirrus to NCM 5.0 .

chris.lapoint · Answer

Ok, that's what I figured.  The good news is we are introducing a new version of Cirrus called Network Configuration Manager (NCM) v5 next week which provides new resources for Orion NPM Node Details View, including Node Configuration History, Recent Configurations, Last 10 Configuration Changes (with drill-down to config change report), and Config Change Report (over time).   With this new integration, NCM can be installed on a separate server and Orion NPM will pull the data remotely (no need to copy configs into a particular directory).

Other highlights include:

* NCM standalone website - provides web-based interface for viewing configurable config mgmt dashboard, device details, search for configs, config change reports, inventory reports, and compliance reports
* Network discovery - provides automated network discovery for initial population of devices into Cirrus database
* Orion node synch job - provides ability to access Cirrus config management data from Orion website
* Device rediscovery through Inventory Job - provides ability to turn off node polling and leverage inventory jobs to rediscover device properties required for automated template selection (e.g. system OID, system description, etc.)