User's Manual

label (e.g. “dataradio”) 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.
1.3.6.1.4.1.3732
Figure 7.5 - Dataradio-REGS MIB tree
7.2.2.3 Viewing MIB Files
To view the hierarchy of SNMP MIB variables in the form of a tree and view additional
information about each node, Dataradio 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, any MIB browser supporting
SNMP v2c could be used.
However, for managing complex networks, a more advanced SNMP Manager/Browser is
recommended.
Note: Both “Read Community” and “Read/Write Community” passwords are required to
operate SNMP MIB. For all Viper radio modems the same password is used for both read
and read/write. This password is the same password used to access the Viper web pages.
Figure 7.6 shows top-level objects of the viper.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)
• viperTraps (b)
• viperSaveConfig (l)
• viperResetUnit (l)
001-5008-000(Rev8) Page 66