|
In SNMP, the Structure of Management Information (SMI) is the
standard that defines the rules for identifying managed objects.
SMI also defines the:
- Syntax for sending and receiving information.
- Means for organizing information into logical groups.
- Naming mechanisms, known as object identifiers, that identify
managed elements.
SMI requires all managed elements in the SNMP environment to be
arranged in a hierarchical structure known as a Management Information
Base (MIB), which is a special kind of database for network management
information.
The SMI structural design that MIBs must follow is sometimes referred
to as a tree. Branches of this tree represent the logical grouping
of information objects. Each end node, or leaf, represents a piece
of information to be managed and has a unique identifier to define
its location on the MIB tree. This identifier consists of a string
of integers separated by periods. Alternately, in text descriptions,
the identifier can consist of a series of text strings separated
by periods.
Starting at the root of the tree, the tree branches out until each
object has been placed and defined with both an integer string and
a text string.
Modular Messaging uses the standard Management Information Base
(MIB)-II definition, as well as the following Avaya-provided MIBs:
- avaya_snmp_mib.txt: This MIB
includes information related to alarm notification to a primary
NMS.
- avaya_oam_mib.txt: This MIB
includes information related to alarm notification to secondary
NMSs.
Note: If you want to use SNMP for alarm notification,
you must first transfer the appropriate Avaya MIBs to the NMSs you
administer to receive alarm notification. The Avaya OAM and SNMP
MIBs are available from the Avaya Support Web site.
Top of page
|
