KYLAND Technology SICOM3024P, Web Operation Manual

Page: 84 / 147

Advanced Configuration
77
NMS.
The NMS is the manager of an SNMP network, while the agent is the managed device of the
SNMP network. The NMS and agents exchange management packets through SNMP.
SNMP involves the following basic operations:

Get-Request

Get-Response

Get-Next-Request

Set-Request

Trap
The NMS sends Get-Request, Get-Next-Request, and Set-Request packets to agents to
query, configure, and manage variables. After receiving these requests, agents reply with
Get-Response packets. When an alarm occurs, an agent proactively reports it to the NMS
with a trap message.
6.11.3 Description
This series switches support SNMPv2. SNMPv2 is compatible with SNMPv1.
SNMPv1 uses community name for authentication. A community name acts as a password,
limiting NMS's access to agents. If the switch does not acknowledged the community name
carried by an SNMP packet, the packet is discarded.
SNMPv2 also uses community name for authentication. It is compatible with SNMPv1, and
extends the functions of SNMPv1.
To enable the communication between the NMS and agent, their SNMP versions must
match. Different SNMP versions can be configured on an agent, so that it can use different
versions to communicate with different NMSs.
6.11.4 MIB
Any managed resource is called managed object. The Management Information Base (MIB)
stores managed objects. It defines the hierarchical relationships of managed objects and
attributes of objects, such as names, access permissions, and data types. Each agent has
its own MIB. The NMS can read/write MIBs based on permissions. The following figure