Submit a ticketCall us

Webinar: Web Help Desk for HR, Facilities and Accounting Departments
This webinar will focus on use cases for HR, Facilities and Accounting.

Having a unified ticketing and asset management system for all the departments in your company can provide end-users with a seamless experience and make things easier for your IT team. Yet, with different business tasks and objectives, many departments don’t fully understand the capabilities of Web Help Desk and how the software can be customized for effective use in their departments.
Register Now.

Home > Success Center > Network Performance Monitor (NPM) > Network Performance Monitor Getting Started Guide > Troubleshoot network issues > Use SolarWinds NPM to identify and troubleshoot a node that has a problem

Use SolarWinds NPM to identify and troubleshoot a node that has a problem

Created by Chris.Moyer, last modified by Chris.Moyer on Oct 03, 2016

Views: 233 Votes: 0 Revisions: 9

Before you begin:

By default, devices monitored by NPM are polled for data every nine minutes. It might take some time before all the nodes you added have data you can review.

Step 1: Determine there is a problem

The easiest way to identify a problem is to have an alert notify you. Some alerts are enabled by default. You can enable additional alerts described later in this guide.

The Node down alert is enabled by default. Therefore, if a node goes down (that is, it does not respond to a ping), you will see it immediately in the Active Alerts resource on the Home page.

File:Success_Center/New_Articles/NPM-Getting-Started-CHM/040/020/NodeDownAlert.png

Down nodes appear in resources as red (down) or yellow (warning).

File:Success_Center/New_Articles/NPM-Getting-Started-CHM/040/020/NodeDownAlert2.png

If you have configured your alerts to send email, you will get an email when a node goes down.

If you do not see any alerts, click My Dashboards > Network > Network Top 10.

File:Success_Center/New_Articles/NPM-Getting-Started-CHM/040/020/NetworkTop10-Nav.png

The resources on this page help identify nodes that respond to a ping but have other health problems.

File:Success_Center/New_Articles/NPM-Getting-Started-CHM/040/020/NetworkTop10.png

Step 2: Get more details about the node

When you find a node with a problem, click the node name in any resource to open the Node Details page.

If a node is down (red), this means it does not respond to a ping. To resolve an issue of this severity:

  1. Check the power. Is it plugged in?
  2. Check the LAN link light. Is it connected to the network?
  3. Log in to the device and begin troubleshooting it.

    If a node responds to a ping but shows signs of health or performance issues, use the information on the Node Details page to help troubleshoot.

    • Check the Response Time, Packet Loss, CPU load, and Memory Utilization. Usually, those statistics are the first indicators of a problem. In our example, the CPU load on this node is high.

      File:Success_Center/New_Articles/NPM-Getting-Started-CHM/040/020/AvgCPU_Load.png

    • Use the Network Latency & Packet Loss, as well as the Min/Max/Average Response Time resources to see if this is a momentary problem or a continuing issue.

      File:Success_Center/New_Articles/NPM-Getting-Started-CHM/040/020/NetworkLatencyAndPacketLoss.png

      Min/Max/Average Response Time & Packet Loss

      File:Success_Center/New_Articles/NPM-Getting-Started-CHM/040/020/NetworkLatencyAndPacketLoss-1.png

    • Depending on what type of node you are monitoring, you may see additional resources specific to that type of device. For example:

      Hardware health: Reports on physical elements of the hardware for Cisco, Dell, F5, HP, and Juniper.

      File:Success_Center/New_Articles/NPM-Getting-Started-CHM/040/020/CurrentHardwardHealth.png

      Routing table information: For routers and switches, multiple resources show a variety of route-related information. Look under the Network subview for these resources.

      File:Success_Center/New_Articles/NPM-Getting-Started-CHM/040/020/NodeDetails.png

      Routing Neighbors

      File:Success_Center/New_Articles/NPM-Getting-Started-CHM/040/020/RoutingNeighbors.png

      Routing Table

      File:Success_Center/New_Articles/NPM-Getting-Started-CHM/040/020/RoutingTable.png

      Default Route Changes

      File:Success_Center/New_Articles/NPM-Getting-Started-CHM/040/020/DefaultRouteChanges.png

Step 3: Get more details about the alert

When a problem causes an alert to be issued, that alert appears on the Node Details page in the Alerts for this Node resource. Click the alert name to go to the Alert Details page. Use the resources on this page to investigate the cause of the alert.

File:Success_Center/New_Articles/NPM-Getting-Started-CHM/040/020/ActiveAlertDetails.png

File:Success_Center/New_Articles/NPM-Getting-Started-CHM/040/020/callout1.png Alert Status Overview: Tells you when the alert happened, its importance, and whether or not it was acknowledged.
File:Success_Center/New_Articles/NPM-Getting-Started-CHM/040/020/callout2.png History: If the same alert is triggered repeatedly, there may be a systemic problem. For example, if a device frequently goes up and down, it may be a sign of a flapping route.
File:Success_Center/New_Articles/NPM-Getting-Started-CHM/040/020/callout3.png Other Objects: Sometimes the same alerts occur on multiple nodes because of a single trigger. For example, if an edge device is having problems, any devices that are dependent on the edge device might also report problems.
File:Success_Center/New_Articles/NPM-Getting-Started-CHM/040/020/callout4.png Acknowledge: Acknowledging an alert indicates that you are aware of the issue and the problem is being investigated.
File:Success_Center/New_Articles/NPM-Getting-Started-CHM/040/020/callout5.png Alert Notes: Each person troubleshooting an issue can enter notes about their activities and any discoveries. The Acknowledge and Notes features are helpful when multiple people are troubleshooting a problem.
Last modified
12:20, 3 Oct 2016

Tags

Classifications

Public