There are two kinds of MIB objects:
Intermapper reads and displays both scalar values and table entries in its SNMP probes.
A scalar value must have a ".0" suffix in its OID. For example, the OID for ifNumber in MIB-II is often written as
In a probe, it should be represented as
(This ".0" is technically part of the OID - it's convenient not to write it, though.)
A table object is generally suffixed with the index of its row. ( This isn't always true: see About Table Indexes below.) For example, the Cisco Environment Monitoring MIB defines two objects for the input air temperature and input voltage as the first rows in each of these tables:
ciscoEnvMonTemperatureStatusValue 220.127.116.11.18.104.22.168.22.214.171.124.3 ciscoEnvMonVoltageStatusValue 126.96.36.199.188.8.131.52.184.108.40.206.3
If you add a suffix ".1" to each of these, you'll get the value of the first row; add ".2" to as a suffix, you'll get the second row, etc.
As noted above, some tables don't have a separate index column. These rows are named (their OIDs are specified by) data in the row. For example, the OID for tcpConnState row, the status of a particular TCP connection is
Its index is the source and destination IP address and port (all four values) which are appended to the tcpConnState OID. Thus, the full OID for the state of a TCP connection from 220.127.116.11 port 543 to 18.104.22.168 port 8765 would be:
Still have questions? We can help. Submit a case to Technical Support.