User's Manual Part 3

Release8OperationsGuide


Issue2,November2007 Draft5forRegula toryReview 392
To monitor a network element (Cyclone module), SNMPv2 supports
• the get command, which instructs the agent to send information about the
module to the manager in the NMS.
• traversal operations, which the manager uses to identify supported objects and to
format information about those objects into relational tables.
In a typical Cyclone network, the manager issues these commands to the agents of more
than one module (to all SMs in the operator network, for example).
24.1.6 TrapsfromtheAgent
When a specified event occurs in the module, the agent initiates a trap, for which the
agent sends an unsolicited asynchronous message to the manager.
24.1.7 APSNMPProxytoSMs
When the AP receives from Prizm or an NMS an SNMP request for an SM, it is capable
of sending that request via proxy to the SM. In this case, the SM responds directly to
Prizm or the NMS. (The AP performs no processing on the response.)
24.2 MANAGEMENTINFORMATIONBASE(MIB)
The MIB, the SNMP-defined data structure, is a tree of standard branches that lead to
optional,
non-standard positions in the data hierarchy. The MIB contains both
• objects that SNMP is allowed to control (bandwidth allocation or access, for
example)
• objects that SNMP is allowed to monitor (packet transfer, bit rate, and error data,
for example).
The path to each object in the MIB is unique to the object. The endpoint of the path is the
object identifier.
24.2.1 CascadingPathtotheMIB
The standard MIB hierarchy includes the following cascading branch structures:
• the top (standard body) level:
• ccitt (0)
• iso (1)
• iso-ccitt (2)
• under iso (1) above:
• standard (0)
• registration-authority (1)
• member-body (2)
• identified-organization (3)
• under identified-organization (3) above:
• dod (6)
• other branches