Contents
Table of Contents
Article Contents
...
...
Below is the list of the OIDs used to collect configuration data and performance metrics related to Network Device elements in up.time.
...
Uptime Infrastructure Monitor.
Configuration OIDs
\n \nThese configuration information OIDs are collected when the Network Device is added to up.time Uptime Infrastructure Monitor and updated regularly by the Configuration Update Gatherer which rescans every 24 hours.
...
| OID | \nMIB | \nName | \nMandatory | \n||
|---|---|---|---|---|---|
| 1.3.6.1.2.1.1.5.0 | \nRFC1213-MIB | \nSystem Name | \nYes | \n||
| 1.3.6.1.2.1.1.1.0 | \nRFC1213-MIB | \nSystem Description | \n\tYes | \n||
| 1.3.6.1.2.1.1.4.0 | \nRFC1213-MIB | \nSystem Contact | \nNo | \n||
| 1.3.6.1.2.1.1.6.0 | \nRFC1213-MIB | \nSystem Location | \n\tNo | \n||
| 1.3.6.1.2.1.31.1.1 | \nIF-MIB | \nInterface Table | \nYes | \n
...
If the Network Device being added is a switch or router, the following additional OIDs will be gathered as well.
...
| OID | \nMIB | \nName | \nNotes | \n||
|---|---|---|---|---|---|
| 1.3.6.1.2.1.2.2.1.1 | \nRFC1213-MIB | \nPort Index | \n\n | ||
| Yes | |||||
| 1.3.6.1.2.1.31.1.1.1.1 | \nIF-MIB | \nPort Name | \nYes - If unavailable, 1.3.6.1.2.1.2.2.1.1 (RFC1213-MIB) will be used instead | \n||
| 1.3.6.1.2.1.2.2.1.2 | \nRFC1213-MIB | \nPort Description | \n\n | ||
| No | |||||
| 1.3.6.1.2.1.2.2.1.3 | \nRFC1213-MIB | \nPort Type | \n\n | ||
| Yes | |||||
| 1.3.6.1.2.1.2.2.1.7 | RFC1213-MIB | Port Admin Status | Yes | \n||
| 1.3.6.1.2.1.2.2.1.8 | \nRFC1213-MIB | \nPort Admin Operational Status | \n\n | ||
| Yes | |||||
| 1.3.6.1.2.1.2.2.1.5 | \nRFC1213-MIB | \nPort Speed | \n\n | ||
| Yes | |||||
| 1.3.6.1.2.1.2.2.1.6 | \nRFC1213-MIB | \nPort MAC | \n\n |
...
| Yes |
Performance Metric OIDs \n \n
Performance metrics are only collected for Network Devices that are switches or routers added in up.timeUptime Infrastructure Monitor. Metrics will be gathered for ports that are have "Port Admin Status" as up and have a valid speed value available.
...
| OID | \nMIB | \nName | \nUnits | \nNotes | \n|||||
|---|---|---|---|---|---|---|---|---|---|
| 1.3.6.1.2.1.31.1.1.1.6 | \nIF-MIB | \nIn Rate | \nKbps | \nIf unavailable, 1.3.6.1.2.1.2.2.1.10 (RFC1213-MIB) will be used instead | \n|||||
| \n | \n | \n | In Usage | \nPercent | \nCalculated by dividing In Rate by interface speed. | \n||||
| 1.3.6.1.2.1.31.1.1.1.10 | \nIF-MIB | \nOut Rate | \nKbps | \nIf unavailable, 1.3.6.1.2.1.2.2.1.16 (RFC1213-MIB) will be used instead | \n|||||
| \n | \n | \n | Out Usage | \nPercent | \nCalculated by dividing Out Rate by interface speed. | \n||||
| Usage | \n\n | \n | Usage | \nPercent | \nCalculated by adding In Usage and Out Usage together. | \n||||
| 1.3.6.1.2.1.2.2.1.14 | \nRFC1213-MIB | \nIn Errors | \n#/sec | \n\n | |||||
| 1.3.6.1.2.1.2.2.1.20 | \nRFC1213-MIB | \nOut Errors | \n#/sec | \n\n | |||||
| Errors | \n\n | \n | Errors | \n#/sec | \nCalculated by adding In Errors and Out Errors together. | \n||||
| 1.3.6.1.2.1.2.2.1.13 | \nRFC1213-MIB | \nIn Discards | \n#/sec | \n\n | |||||
| 1.3.6.1.2.1.2.2.1.19 | \nRFC1213-MIB | \nOut Discards | \n#/sec | \n\n | |||||
| \n | \n | \n | Discards | \n#/sec | \nCalculated by adding In Discards and Out Discards together. | \n
...
Troubleshooting with snmpwalk
...
Although most SNMP enabled network devices provide the OID's listed above, not all do. If there are issues adding a network device to up.timeUptime Infrastructure Monitor, it is helpful to use snmpwalk to review the OIDs available on the device. The article "Troubleshooting Network Device Issues with snmpwalk" explains how to do this.