User guide

460
pmp-0229 (Mar 2013)
Roles of Hardware and Software Elements Managing the Network From a
Management Station (NMS)
Dual Roles for the NMS
The NMS can simultaneously act as an agent. In such an implementation, the NMS acts as
• client to the agents in the modules, when polling for the agents for information and sending
modification data to the agents.
• server to another NMS, when being polled for information gathered from the agents and
receiving modification data to send to the agents.
Simple Network Management Protocol (SNMP) Commands
To manage a module, SNMPv2 supports the set command, which instructs the agent to change
the data that manages the module.
To monitor a network element, 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 network, the manager issues these commands to the agents of more than one module
(to all SMs in the operator network, for example).
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.
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.)