Submit a ticketCall us

AnnouncementsFace your biggest database issues head-on

Our new eCourse helps you navigate SQL Server performance blocks by teaching you how to recognize and deal with the three DBA Disruptors: Performance Hog, Blame Shifter, and Query Blocker. Register today to learn how to defend your environment and fend off menacing disruptions.

Register for your free eCourse.

Home > Success Center > Network Configuration Manager (NCM) > NCM Documentation > NCM 7.8 Administrator Guide > Real-time change detection > Configure real-time change detection

Configure real-time change detection

Updated: August 14, 2018

When you configure real-time change detection, NCM sends an email notification whenever a config changes. To configure real-time change detection, complete the following steps.

Step 1
Configure devices to send syslog or trap messages to the Orion server.

devicessendmessagestoorion.png

Step 2
Configure rules to detect syslog or trap messages that indicate a config has been changed.

rtcd step2_61x59.png

Step 3
Create the account that NCM uses to access devices and download the updated config.

rtcd step3.png

Step 4
Specify config comparison and email notification options.

rtcd step4_38x46.png

Step 5
Enter NCM SMTP server details.

rtcd step5.png

Step 6
Enable real-time config change notifications.

rtcd step6.png

Step 1: Configure your devices to send syslog or trap messages to the Orion server

devicessendmessagestoorion.png

Manually configure each device to send either syslog or trap data to the Orion server.

If your devices already send syslog or trap messages to Kiwi Syslog Server or a third-party syslog or trap receiver, you can skip this step and continue with Step 2.

SolarWinds strongly recommends that you configure Cisco devices to send syslog messages, not trap messages. Cisco devices send trap messages when a user enters config mode but not when the user exits. Therefore, if you configure Cisco devices to send trap messages, you aren't notified of a change until the next time a user enters config mode.

  1. Click My Dashboards > Configs > Configuration Management.
  2. Select the nodes, and then click Execute Script.
  3. Enter the commands to forward syslog or trap messages to the Orion server.

    See this topic for examples of the commands. For more information, see your device documentation.

    In addition, consider disabling logging for logins from the NCM server, especially if NCM must open config mode to download the device configuration. Disabling logging for NCM logins ensures that changes made by NCM don't trigger RTCD, which would result in a loop.

  4. Click Execute.
  5. Click Transfer Status.
  6. In the Action column, locate the most recent entry labeled Execute Script.
  7. Click Show Script Results in the Status/Details column.

You can remove device configurations by running a command with no in front of it. For example, no set logging server {ip_address} removes that target from the remote logging stream.

Step 2: Configure rules to detect config change notifications

rtcd step2.png

Configure rules to detect syslog or trap messages that indicate a config has been changed. You might need different rules for different device types. Each rule should include an action to execute RTNForwarder.exe, which downloads the config and determines what changed.

The message text used to trigger the rule should be from a message received after all the changes made in the session have been completed, for example when exiting configuration mode.

See the appropriate instructions below, depending on the message type and what product you use to manage syslog or trap messages:

Step 3: Create the account that NCM uses to access devices and download configs

rtcd step3.png

When a config change is detected, NCM must be able to access the device and download the latest config so that it can determine what changed. Use the Config Changes page to create the Windows account that NCM uses to create and run RTCD-related download jobs.

  1. Open the Real-Time Change Detection page.
    1. In the Orion Web Console, click Settings > All Settings.
    2. Under Product Specific Settings, click NCM Settings.
    3. Under Real-Time Change Detection, click Configure Real-Time Change Detection.
  2. Click the Config Changes link in Step 3.

    rtcd config changes.png

    The Config Changes page opens.

  3. Select Enable these account credentials to access all NCM-managed devices.

    If the check box is disabled, then the Device Login & User Account Credentials option is set to Global - Device Level. To change this option, click the Security link to open the Security page, and then select Individual - User Level.

  4. Enter the credentials that NCM can use to access devices and run RTCD-related download jobs.
  5. If you want the email message NCM generates to include the syslog or trap message that signaled a config change, select Include syslog/trap message.
  6. Click Submit.

Step 4: Specify config comparison and email notification options

rtcd step4.png

When a config change is detected, NCM accesses the device, downloads the modified config file, and compares it to an existing config file to determine what changed. NCM then emails the specified recipients to notify them of the changes. Complete the following steps to specify config comparison and email notification options.

  1. Open the Real-Time Change Detection page.
  2. Click the Config Downloads and Notification Settings link in Step 4.

    rtcd config downloads.png

  3. Under Previously Downloaded Config File, select the type of config file that NCM should download for comparison when a config change is detected.

  4. Under Baseline Config File, select the config file you want NCM to use as the baseline for comparison when it determines what changed.

  5. Select the desired Email Notification Options.
  6. Enter the Sender Name and Subject for NCM to use in RTCD email notifications, and specify at least one recipient. The Reply Address is optional.
  7. Click Submit.

Step 5: Enter NCM SMTP server details

rtcd step5.png

The email server settings you enter here are used to send notifications regarding RTCD, config change approvals, and running jobs. For information on config change approvals, see Approval system for device configuration changes

  1. Open the Real-Time Change Detection page.
  2. Click the NCM SMTP Server link in Step 5.

    rtcd_smpt_server.png

  3. Enter the fully qualified domain name (FQDN) or IP address of the mail server.
  4. Enter the port number on which the mail server handles messages.
  5. Select None or Password as the Authentication method.
  6. Enter a user name and password.
  7. Click Submit.

Step 6: Enable real-time config change notification

rtcd step6.png

  1. Open the Real-Time Change Detection page.
  2. Under Enable Real-Time Config Change Notifications, click Enable.
  3. Click Submit.

If a large number of config downloads is an issue after you configure RTCD, you can limit the number of simultaneous downloads.

Last modified

Tags

Classifications

Public