Submit a ticketCall us

Training Class Getting Started with SolarWinds Backup - February 28

This course offers customers an introduction to SolarWinds Backup, focusing on configuring the backup technology, taking backups, data restoration and data security. It is a great primer and will get you up to speed quickly on SolarWinds Backup.
Register for class.

Home > Success Center > Network Configuration Manager (NCM) > Network Configuration Manager Getting Started Guide > Network troubleshooting and remediation > How was it done? Troubleshoot a network issue caused by a config change

How was it done? Troubleshoot a network issue caused by a config change

Created by Chris.Moyer, last modified by Melanie Boyd on Jan 03, 2018

Views: 432 Votes: 0 Revisions: 8

In the Troubleshoot a network issue caused by a config change topic, a system administrator finds the root cause of a network problem and reverts a config to resolve the alert. This topic explains all of the setup necessary to replicate the troubleshooting and solution steps performed by the system administrator.

Create a path to NetSuite

Before you can monitor, you must first create a new service path. This example creates a path to NetSuite.

After the first polling interval, the network path from the probe to the NetSuite service is active. The system administrator knows that all nodes beginning with the number 10 are internal nodes.

  1. Navigate to My Dashboards > Network > NetPath Services.
  2. Click Create New Service.
  3. Enter the Service Details and click Next.


  4. Assign a probe or create a probe.
  5. Click Create.


    • If you are already monitoring internal nodes on the path, you see data about the nodes. In this example, nodes EAST-4506E-CORE and EAST-2821-WAN are monitored.
    • If you are not monitoring internal nodes on the path, you can add them. See the Monitor nodes on a path section below. In this example, the system is not monitoring node


Monitor nodes on a path

Before you begin, ensure that you know the credentials for the nodes you want to monitor.

  1. Click any node on the path that you want to monitor.
  2. Click Add this device to Orion.


  3. Enter the node credentials. To learn how to complete the remaining steps for adding a node, see the NPM Getting Started Guide.


Create a NetPath alert for NetSuite

This example shows how to duplicate and edit the out-of-the-box alert Path to Google to create an alert for the new path to NetSuite. When the path to Netsuite breaks, an alert triggers.

  1. Navigate to the Manage Alert page.


  2. On the Properties page, update the name and description of the alert. For example, you can enter Path to NetSuite for the name.
  3. On the Trigger Condition page, change Google to NetSuite.


  4. Click Next until you reach the Trigger Action page.
  5. Edit the email action so you (or other responsible party) receive a notification email when the alert is triggered.


  6. Complete the rest of the alert wizard steps, and then click Submit on the Summary page.

You can review possible errors made to configs before an alert is sent. Enable real-time change detection and receive an email notification whenever there is a change to a config. Real-time change detection also has an option to restrict access to users so you can prevent unauthorized changes to configs.


Last modified