ample, object titled “SNMP” has a unique OID: 1.3.6.1.2.1.11. The MIB associates each OID with a label (e.g.
“SNMP”) and various other parameters. When an SNMP manager wants to obtain information on an object, it will
assemble a specific message (e.g. GET packet) that includes the OID of the object of interest. If the OID is found, a
response packet is assembled and sent back. If the OID is not found, a special error response is sent that identifies
the unmanaged object.
Figure 29 - Branch of the 1234.mib OID tree
VIEWING MIB FILES
To view the hierarchy of SNMP MIB variables in the form of a tree and view additional information about each
node, CalAmp recommends opening all MIB files with a MIB browser. In a MIB browser, each object (or node) can
be selected and its properties (including its OID) can be observed. For simple networks, a basic, free application
such as ”iReasoning MIB browser” could be used.
However, for managing complex networks, CalAmp recommends a more advanced software application, one ca-
pable of browser function as well as being a full-featured SNMP manager, such as the optional “Castle Rock SNMPc
Network Manager”. Refer to Network Management using SNMP User Manual (Part no. 120 47001-nnn for more
details).
GCU3.MIB
Figure 30 shows top-level objects of the gcu3.mib file:
•
gcu3Identity
•
gcu3RadioIdentity
•
gcu3NetStatistics
org (3)
iso(1)
ip(4)
icmp(5)
SNMP (11)
udp(7)
system (1)
interfaces (2)
dod (6)
internet (1)
mgmt (2)
mib-2 (1)
tcp (6)
transmission (10)
1.3.6.1.2.1
1.3.6.1.2.1.11
1
1.3.6
1.3
45
