QTECH
Software Configuration Manual
2-33
Inform operation : NMS sends Trap information to other NMSs through this operation.
2.10 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 for short),
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.
2.11 MIB Overview
Management Information Base (MIB) is a collection of all the objects managed by NMS. It defines the 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.
Figure 1 MIB tree
2.12 SNMP Configuration
SNMP configuration command list includes :
1)
Configure community
2)
Configure sysContact
3)
Configure Trap destination host adress
4)
Configure sysLocation
5)
Configure sysName
6)
Configure notify
7)
Configure engine id
8)
Configure view
9)
Configure group
10)
Configure user
11)
Configure community
SNMP adopts community authentication. The SNMP packets which are not matching the authenticated
