Network Management
In/Out Errors and Discards information is blank for some nodes in NPM
This article explains how to check why some nodes are showing no information for In/Out Errors and Discards.
First published date
2/7/2020 8:31 PM
Last published date
8/2/2022 9:30 PM
Overview
To understand this, first you need to identify the OIDs used by NPM to get the In/Out Errors and Discards.
Then Run SNMP walk and check the data provided by the machine.
Then Run SNMP walk and check the data provided by the machine.
Product section
Network Performance Monitor
Cause
Node did return any data for In/Out Errors and Discards.
Resolution
First, see the article below that tells us which OID is being used by Orion to get interface information.
https://support.solarwinds.com/SuccessCenter/s/article/What-object-IDs-OIDs-does-NPM-poll-for-interface-information
ifDesc 1.3.6.1.2.1.2.2.1.2 - OID used to get the interface name. Also notice the last digit. The last digit is the ifIndex which is unique to every interface.
.1.3.6.1.2.1.2.2.1.2.11 = String: "GigabitEthernet0/0/0.609"
.1.3.6.1.2.1.2.2.1.2.12 = String: "GigabitEthernet0/0/0.709"
Now that we know the interface index, we can now look for the In/Out Errors and Discards. To look at this, we will use the OIDs for In/Out Errors and Discards. Note that there is an OID of each so we are looking for 4 OIDs. Then, this OID should followed by the index. In the data below, you can see the OIDs followed by different indexes, we are looking for 11 and 12 indexes. Notice that they are not listed in the walk. This means that the machine did not provide any information about these.
ifInDiscards 1.3.6.1.2.1.2.2.1.13 - OID for Interface In Discards.
.1.3.6.1.2.1.2.2.1.13.1 = Counter32: 0
.1.3.6.1.2.1.2.2.1.13.2 = Counter32: 0
.1.3.6.1.2.1.2.2.1.13.3 = Counter32: 0
.1.3.6.1.2.1.2.2.1.13.4 = Counter32: 0
.1.3.6.1.2.1.2.2.1.13.5 = Counter32: 0
.1.3.6.1.2.1.2.2.1.13.6 = Counter32: 0
.1.3.6.1.2.1.2.2.1.13.7 = Counter32: 0
.1.3.6.1.2.1.2.2.1.13.8 = Counter32: 0
.1.3.6.1.2.1.2.2.1.13.9 = Counter32: 0
.1.3.6.1.2.1.2.2.1.13.10 = Counter32: 0
ifInErrors 1.3.6.1.2.1.2.2.1.14 - OID for Interface In Errors
.1.3.6.1.2.1.2.2.1.14.1 = Counter32: 136
.1.3.6.1.2.1.2.2.1.14.2 = Counter32: 0
.1.3.6.1.2.1.2.2.1.14.3 = Counter32: 0
.1.3.6.1.2.1.2.2.1.14.4 = Counter32: 0
.1.3.6.1.2.1.2.2.1.14.5 = Counter32: 0
.1.3.6.1.2.1.2.2.1.14.6 = Counter32: 0
.1.3.6.1.2.1.2.2.1.14.7 = Counter32: 0
.1.3.6.1.2.1.2.2.1.14.8 = Counter32: 0
.1.3.6.1.2.1.2.2.1.14.9 = Counter32: 0
.1.3.6.1.2.1.2.2.1.14.10 = Counter32: 0
ifOutDiscards 1.3.6.1.2.1.2.2.1.19 - OID for Interface Out Discards
.1.3.6.1.2.1.2.2.1.19.1 = Counter32: 554378
.1.3.6.1.2.1.2.2.1.19.2 = Counter32: 54
.1.3.6.1.2.1.2.2.1.19.3 = Counter32: 0
.1.3.6.1.2.1.2.2.1.19.4 = Counter32: 0
.1.3.6.1.2.1.2.2.1.19.5 = Counter32: 0
.1.3.6.1.2.1.2.2.1.19.6 = Counter32: 0
.1.3.6.1.2.1.2.2.1.19.7 = Counter32: 0
.1.3.6.1.2.1.2.2.1.19.8 = Counter32: 0
.1.3.6.1.2.1.2.2.1.19.9 = Counter32: 0
.1.3.6.1.2.1.2.2.1.19.10 = Counter32: 0
ifOutErrors 1.3.6.1.2.1.2.2.1.20 - OID for Interface Out Errors
.1.3.6.1.2.1.2.2.1.20.1 = Counter32: 0
.1.3.6.1.2.1.2.2.1.20.2 = Counter32: 0
.1.3.6.1.2.1.2.2.1.20.3 = Counter32: 0
.1.3.6.1.2.1.2.2.1.20.4 = Counter32: 0
.1.3.6.1.2.1.2.2.1.20.5 = Counter32: 0
.1.3.6.1.2.1.2.2.1.20.6 = Counter32: 0
.1.3.6.1.2.1.2.2.1.20.7 = Counter32: 0
.1.3.6.1.2.1.2.2.1.20.8 = Counter32: 0
.1.3.6.1.2.1.2.2.1.20.9 = Counter32: 0
.1.3.6.1.2.1.2.2.1.20.10 = Counter32: 0
For this scenario, I would advise to contact the device vendor to fix the problem.
https://support.solarwinds.com/SuccessCenter/s/article/What-object-IDs-OIDs-does-NPM-poll-for-interface-information
ifDesc 1.3.6.1.2.1.2.2.1.2 - OID used to get the interface name. Also notice the last digit. The last digit is the ifIndex which is unique to every interface.
.1.3.6.1.2.1.2.2.1.2.11 = String: "GigabitEthernet0/0/0.609"
.1.3.6.1.2.1.2.2.1.2.12 = String: "GigabitEthernet0/0/0.709"
Now that we know the interface index, we can now look for the In/Out Errors and Discards. To look at this, we will use the OIDs for In/Out Errors and Discards. Note that there is an OID of each so we are looking for 4 OIDs. Then, this OID should followed by the index. In the data below, you can see the OIDs followed by different indexes, we are looking for 11 and 12 indexes. Notice that they are not listed in the walk. This means that the machine did not provide any information about these.
ifInDiscards 1.3.6.1.2.1.2.2.1.13 - OID for Interface In Discards.
.1.3.6.1.2.1.2.2.1.13.1 = Counter32: 0
.1.3.6.1.2.1.2.2.1.13.2 = Counter32: 0
.1.3.6.1.2.1.2.2.1.13.3 = Counter32: 0
.1.3.6.1.2.1.2.2.1.13.4 = Counter32: 0
.1.3.6.1.2.1.2.2.1.13.5 = Counter32: 0
.1.3.6.1.2.1.2.2.1.13.6 = Counter32: 0
.1.3.6.1.2.1.2.2.1.13.7 = Counter32: 0
.1.3.6.1.2.1.2.2.1.13.8 = Counter32: 0
.1.3.6.1.2.1.2.2.1.13.9 = Counter32: 0
.1.3.6.1.2.1.2.2.1.13.10 = Counter32: 0
ifInErrors 1.3.6.1.2.1.2.2.1.14 - OID for Interface In Errors
.1.3.6.1.2.1.2.2.1.14.1 = Counter32: 136
.1.3.6.1.2.1.2.2.1.14.2 = Counter32: 0
.1.3.6.1.2.1.2.2.1.14.3 = Counter32: 0
.1.3.6.1.2.1.2.2.1.14.4 = Counter32: 0
.1.3.6.1.2.1.2.2.1.14.5 = Counter32: 0
.1.3.6.1.2.1.2.2.1.14.6 = Counter32: 0
.1.3.6.1.2.1.2.2.1.14.7 = Counter32: 0
.1.3.6.1.2.1.2.2.1.14.8 = Counter32: 0
.1.3.6.1.2.1.2.2.1.14.9 = Counter32: 0
.1.3.6.1.2.1.2.2.1.14.10 = Counter32: 0
ifOutDiscards 1.3.6.1.2.1.2.2.1.19 - OID for Interface Out Discards
.1.3.6.1.2.1.2.2.1.19.1 = Counter32: 554378
.1.3.6.1.2.1.2.2.1.19.2 = Counter32: 54
.1.3.6.1.2.1.2.2.1.19.3 = Counter32: 0
.1.3.6.1.2.1.2.2.1.19.4 = Counter32: 0
.1.3.6.1.2.1.2.2.1.19.5 = Counter32: 0
.1.3.6.1.2.1.2.2.1.19.6 = Counter32: 0
.1.3.6.1.2.1.2.2.1.19.7 = Counter32: 0
.1.3.6.1.2.1.2.2.1.19.8 = Counter32: 0
.1.3.6.1.2.1.2.2.1.19.9 = Counter32: 0
.1.3.6.1.2.1.2.2.1.19.10 = Counter32: 0
ifOutErrors 1.3.6.1.2.1.2.2.1.20 - OID for Interface Out Errors
.1.3.6.1.2.1.2.2.1.20.1 = Counter32: 0
.1.3.6.1.2.1.2.2.1.20.2 = Counter32: 0
.1.3.6.1.2.1.2.2.1.20.3 = Counter32: 0
.1.3.6.1.2.1.2.2.1.20.4 = Counter32: 0
.1.3.6.1.2.1.2.2.1.20.5 = Counter32: 0
.1.3.6.1.2.1.2.2.1.20.6 = Counter32: 0
.1.3.6.1.2.1.2.2.1.20.7 = Counter32: 0
.1.3.6.1.2.1.2.2.1.20.8 = Counter32: 0
.1.3.6.1.2.1.2.2.1.20.9 = Counter32: 0
.1.3.6.1.2.1.2.2.1.20.10 = Counter32: 0
For this scenario, I would advise to contact the device vendor to fix the problem.