User's Manual Part 3
Release8OperationsGuide
Issue2,November2007 Draft5forRegula toryReview 391
24 MANAGINGTHENETWORKFROMA
MANAGEMENTSTAT ION(NMS)
SNMPv2 (Simple Network Management Protocol Version 2) can be used to manage and
monitor the Cyclone modules under SMI (Structure of Management Information)
specifications. SMI specifies management information definitions in ASN.1 (Abstract
Syntax Notation One) language. SNMPv2 supports both 32-bit and 64-bit counters. The
SMI for SNMPv2 is defined in RFC 1902 at http://www.faqs.org/rfcs/rfc1902.html
.
24.1 ROLESOFHARDWAREANDSOFTWAREELEMENTS
24.1.1 RoleoftheAgent
In SNMP, software on each managed device acts as the agent. The agent collects and
stores management information in ASN.1 format, in a structure that a MIB (management
information base) defines. The agent responds to commands to
• send information about the managed device.
• modify specific data on the managed device.
24.1.2 RoleoftheManagedDevice
In SNMP, the managed device is the network element that operates on the agent
software. In the Cyclone network, this managed device is the module (AP, SM, or BH).
With the agent software, the managed device has the role of server in the context of
network management.
24.1.3 RoleoftheNMS
In SNMP, the NMS (network management station) has the role of client. An application
(manager software) operates on the NMS to manage and monitor the modules in the
network through interface with the agents.
24.1.4 DualRolesfortheNMS
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.
24.1.5 SimpleNetworkManagementProtocol(SNMP)Commands
To manage a module, SNMPv2 supports the set command, which instructs the agent to
change the data that manages the module.