Guidelines and examples
Review the following table for examples of valid input for the MIB Table to download field.
MIB Table to download field |
Description |
---|---|
RFC1213-MIB:system |
MIB-II system tree |
1.3.6.1.2.1.1 |
Numeric OID equivalent to RFC1213-MIB:system |
hrSWRunTable |
Running software from the Host-Resources MIB |
ipInReceives & next 16 |
IP Statistics |
ICMP |
ICMP statistics from RFC-1213 |
tcpRtoAlgorithm & Next 11 & tcpInErrs & tcpOutRsts |
TCP Statistics |
etherStatsTable |
RMON Ethernet Statistics |
frCircuitTable |
Frame Relay circuits |
bgpPeerTable |
BGP peer table |
ifPhysAddress |
MAC addresses for all interfaces on a device |
hrSWInstalledTable |
Installed software |
OLD-CISCO-MEMORY-MIB:freeMem & Next 39 & bufferHgSize & Next 7 |
Cisco Buffers |
cdpCacheTable |
Cisco Discovery Protocol table |
tcpConnTable |
TCP connection table |
- You can add
Next
X, where X represents the number of OIDs to return. The Cisco Buffers in the previous table of examples provides an excellent example of the Next X syntax. - Each OID can be fully qualified with the MIB Name, a colon, and the OID name. Or, you can provide only the MIB tree.
For common OID names that could exist in multiple MIBs, include the MIB Name when specifying the value. For example, system
exists in RFC1213-MIB, HP-UNIX, INTEL-GEN-MIB, and the Apple Macintosh MIB, therefore specify the MIB when retrieving the value: RFC1213-MIB:system
or HP-UNIX:system
or INTEL-GEN-MIB:system
.
Valid formats for the OID name are provided in the following table:
MIBName:OIDName |
RFC1213-MIB:system |
OLD-CISCO-MEMORY-MIB:freeMem |
Numeric OID |
1.3.6.1.2.1.1 |
1.3.6.1.4.1.9.9.27.1.1.2 |
OIDName |
tcpConnTable |
cdpCacheTable |