Viper SC+™ IP Router for Licensed Spectrum PN 001-5008-000 Rev. C
| Page 170
OID
In SNMP, each object has a unique OID consisting of numbers separated by decimal points. These object identifiers
form a tree-like structure. The following figure illustrates this tree-like structure for the dataradio-regs.mib MIB, which
comes bundled with the Viper firmware. A path to any object can be traced starting from the root (top of the tree). For
example, the object titled “dataradio” has a unique OID 1.3.6.1.4.1.3732. The MIB associates each OID with a label (in
this example, “dataradio”) and various other parameters. When an SNMP manager wants to obtain information on an
object, it will assemble a specific message (for example, 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 95 – Dataradio-REGS MIB tree
Viewing MIB Files
To view the hierarchy of SNMP variables in the form of a tree and view additional information about each node, open
each of the MIB files with an MIB browser. In a MIB browser, each object (or node) can be selected and its properties
(including OID) can be viewed. For simple networks, any MIB browser supporting SNMP v2c can be used. However, for
managing complex networks, a more advanced SNMP Manager/Browser is recommended.
Both
Read Community
and
Read/Write Community
passwords are required to operate SNMP MIB for all Vipers. The
same password can be used for both read and read/write. This password is not the same password used to access the
Viper Web Interface.
The following figure shows top-level objects of the Viper_scx.mib file. It includes eight branches (b) and three nodes or
leaves (l).
ViperModule (l)
ViperStatus (b)
ViperDiagnostics (b)
ViperSetup (b)
ViperSetupAdv (b)
ViperStatistics (b)
ViperSecurity (b)
ViperNetworkManagement (b)
