Submit a ticketCall us

whitepaperYour VM Perplexities Called, and They Need You to Read This.

Virtualization can give you enormous flexibility with future workloads and can be a key enabler for other areas, like cloud computing and disaster recovery. So, how can you get a handle on the performance challenges in your virtual environment and manage deployments without erasing the potential upside? Learn the four key areas you need to be focusing on to help deliver a healthy and well-performing data center.

Get your free white paper.

Home > Success Center > Network Configuration Manager (NCM) > NCM Documentation > NCM 7.9 Administrator Guide > About real-time change detection

About real-time change detection

Updated: August 14, 2018

When you configure real-time change detection (RTCD), SolarWinds NCM sends an email notification whenever a device configuration changes. Use RTCD notifications to quickly determine if the config change could potentially cause a problem. Immediate notification of changes helps you improve network security, prevent unexpected downtime, and resolve known errors faster.

Unlike the Config Change Report, RTCD detects changes only on the same configuration type. For example, if you download a startup configuration, make changes to it, and upload it as a running configuration, the change will be detected against the previous running configuration. RTCD does not compare running and startup configuration types.

How does real-time change detection work?

To enable real-time change detection, you configure your network devices to send syslog or trap messages to the Orion server, and then configure a rule to detect messages that indicate a config was changed. After you configure RTCD:

  1. A user logs in to a device and changes the config.
  2. The device sends a syslog or trap message to the Orion server.
  3. A rule in your syslog or trap receiver detects a message that indicates a config change. The action in the rule launches the NCM executable RTNForwarder.exe.
  4. RTNForwarder.exe downloads the updated config from the device.
  5. NCM compares the updated config to a baseline to determine what changed.
  6. NCM sends an email with details of the change to the designated recipient.


Next steps

Last modified