RTCD Enancement Request

Question

Add logic so originating IP address of the syslog message does not need to match the IP of the device in the node list.  All the IP addresses for a device are stored in the IPAddresses table.  Query the originating IP address of the syslog message to verify it belongs to a node.  If so then proceed with downloading the config and doing the comparison.

This will be a huge time saver and prevent detection being missed due to a change in the IP address in the node list, Not having to add the logging source-interface in hundreds of devices, and not missing detection due to an IP re-address on interfaces of the node which could make the logging source-interface IP change.

Regards.

chris.lapoint · Answer

Sorry about that.  We'll get that fixed in the doc.  Here's how RTCD operates with v5:

* Syslog message comes into Syslog
* ConfiogAutoDownload.exe is run with IP address parameter
* ConfigAutoDownload check this IP in Nodes table – this table contains NCM managed nodes. 
* In case IP exist in Nodes table, the process runs as normal
* In case IP does not exist in Nodes table, the process attempts to search this IP in IPAdresses table – this is only one additional table on which search is performed.
* In case IP is found in IPAdresses table, the process determines the node to which this IP belongs and runs as normal
* In case IP does not exist in nodes table, the process fails and logs an appropriate error message

To make this work, you'll need to ensure that inventory has been run on the network devices that you want managed with RTCD.

FormerMember · Answer

Yes, only speaking to what the DOC says.  Glad I stopped changing routers after the first dozen or so.

"The IP address the device uses to send messages must be the same IP address used to
manage the device in Orion Network Configuration Manager?"   Page 48 of the admin guide.

chris.lapoint · Answer

Are you running NCM v5?   We enhanced RTCD to support multi-homed devices as part of v5.