Operation Manual – SNMP-RMON
H3C S3610&S5510 Series Ethernet Switches
Chapter 1 SNMP Configuration
1-2
z
Get operation: NMS gets the value of a certain variable of Agent through this
operation.
z
Set operation: NMS can reconfigure certain values in the Agent MIB (Management
Information Base) to make the Agent perform certain tasks by means of this
operation.
z
Trap operation: Agent sends Traps to the NMS through this operation.
z
Inform operation: NMS sends Traps to other NMSs through this operation.
1.1.2 SNMP Protocol Version
Currently, SNMP agents support SNMPv3 and are compatible with SNMPv1 and
SNMPv2c.
SNMPv1 and SNMPv2c authenticate by means of community name, which defines the
relationship between an SNMP NMS and an SNMP Agent. SNMP packets with
community names that did not pass the authentication on the device will simply be
discarded. A community name performs a similar role as a key word and can be used to
regulate access from NMS to Agent.
SNMPv3 offers an authentication that is implemented with a User-Based Security
Model (USM), which could be authentication with privacy, authentication without
privacy, or no authentication no privacy. USM regulates the access from NMS to Agent
in a more efficient way.
1.1.3 MIB Overview
Management Information Base (MIB) is a collection of all the objects managed by NMS.
It defines a set of characteristics associated with the managed objects, such as the
object identifier (OID), access right and data type of the objects.
MIB stores data using a tree structure. The node of the tree is the managed object and
can be uniquely identified by a path starting from the root node. As illustrated in the
following figure, the managed object B can be uniquely identified by a string of numbers
{1.2.1.1}. This string of numbers is the OID of the managed object B.
A
2
6
1
5
2
1
1
2
1
B
Figure 1-1
MIB tree
