Snmp Commands; How A Mib Is Organized - Motorola BSR 2000 Reference Manual

Release 1.0

SNMP Commands

Table
RFC 1157, that are supported by the SNMP agent software on the BSR:

How a MIB is Organized

Because networking devices are made by a variety of manufacturers they must all be
able to communicate with one another. The Internet standards organization requires
that each network device organize its management information according to a
pre-defined tree format. This tree structure branches out from the Internet layer into
several subtrees, with each subtree organized into branches (groups of related
information) and leaves (the individual pieces of information, or objects). Among
these subtrees is an Enterprises subtree, in which private vendors can apply to the
Internet Assigned Numbers Authority for a branch in which to store management
information (or objects) specific to their products.
Each layer of this tree is numerically encoded, so that each group and object is
identified by a unique number known as an Object Identifier (OID). This identifier is
a path to the information stored as the object's value, and provides the means by
which the SNMP agent is able to locate the object in a device's MIB. An ASCII name
is also assigned to each branch or OID, for convenience in identifying a management
object. For example, the MIB II object ipForwarding is identified as follows:
Numeric OID: 1.3.6.1.2.1.4.1
ASCII string: iso/org/dod/internet/mgmt/mib-2/ip/ipForwarding
526362-001-00
Introduction to the Simple Network Management Protocol
describes the SNMP Get, GetNext, and Set commands, as defined in
Table 1-1 SNMP Commands
Command
Get
GetNext
Set
Description
Retrieves the value of a specific object from
one of the supported MIBs.
Traverses the MIB tree to retrieve the next
object's management information.
Modifies the values of MIB objects. The BSR
2000 private MIBs and several objects in the
standard MIBs allow you to configure the
BSR 2000 from an SNMP management
station on the network.
MGBI 1-3