Snmp Version - 3onedata NP318T-8DI User Manual

SNMP includes 2 parts: NMS and Agent:
NMS (Network Management System) is the manager of the SNMP network, can

provide a very friendly human-computer interaction interface, to facilitate the
network administrator to complete the vast majority of network management.
Agent is a managed object of the SNMP network. It is responsible for receiving

and processing request packets from the NMS. In some emergency situations, if
the interface status changes, Agent will automatically send alarm information to
the NMS.
NMS management equipment, usually pay attention to some parameters, such as
interface status, CPU utilization, etc. The collection of these parameters called MIB
(Management Information Base). These parameters are called nodes in the MIB. The
MIB defines the hierarchical relationships between the nodes and the attributes of the
object, such as the name of the object, the access rights, and the data type. Each
Agent has its own MIB. The managed devices have their own MIB files, and the MIB
files are compiled on the NMS to generate the MIB of the device. The NMS performs
read / write operations on the MIB nodes according to the access rights to implement
the management of the Agent. The relationship between NMS, Agent and MIB is
shown in the following figure.
SNMP supports 3 kinds of basic operating in total:
Get: Manager can use this to get some variable value of Agent.

Set: Manager can use this to set up some variable value of Agent.

Trap: Agent uses this to send an alarm to manager. The Agent does not require

the NMS to send a response packet. The NMS does not respond to the Trap
message. SNMP V1 and SNMP V2 support Trap operation.

7.1.3 SNMP Version

Currently, Agent supports SNMP V1 and SNMP V2.
SNMP V1 uses the Community Name authentication mechanism. The community

name is similar to the password used to limit the communication between the
NMS and the agent. If the community name set by the NMS is different from the
community name set on the managed device, the NMS and the agent can not
establish an SNMP connection, causing the NMS to fail to access the agent. The
3onedata proprietary and confidential
Copyright © 3onedata Co., Ltd.
User Manual
50