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

In the Troubleshoot a network issue caused by a network 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 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.

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.

   

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.

• If you are already monitoring internal nodes on the path, you see data about the nodes. In this example, nodes 10.196.3.50 and 10.1.2.1 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 10.0.2.82.

  

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 the SolarWinds Platform.

   

3. Enter the node credentials.

   To learn how to complete the remaining steps for adding a node, see Add a single node for monitoring to the SolarWinds Platform.

   

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 is triggered.

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.