H3C Technologies H3C SecPath F1000-E - Manual (Page 155)

5
To do… Use the command… Remarks
Configure an
SNMP group
snmp-agent group { v1 |
v2c } group-name
[ read-view read-view ]
[ write-view write-view ]
[ notify-view notify-view ]
[ acl acl-number ]
Configure
indirectly
Add a user to
an SNMP
group
snmp-agent usm-user { v1
| v2c } user-name group-name
[ acl acl-number ]
was introduced to be
compatible with SNMPv3.
The community name
configured on the NMS should
be consistent with the username
configured on the agent.
Configure the maximum size of an
SNMP packet that can be received or
sent by an SNMP agent
snmp-agent packet
max-size byte-count
Optional
1,500 bytes by default.
CAUTION:
•
The validity of a USM user depends on the engine ID of the SNMP agent. If the engine ID generated
when the USM user is created is not identical to the current engine ID, the USM user is invalid.
• A MIB view is a subset of MIB and is uniquely identified by its view name and the MIB subtree together.
MIB views with the same view name but containing different subtrees are considered different views.
Except default MIB views, you can create at most 16 MIB views.
Configuring Network Management-Specific
Interface Index
Introduction to Network Management-Specific Interface Index
Interface index (ifindex) and network management (NM)-specific ifindex are both interface
identifications. ifindex is an internal parameter for software implementation of the device, and it is used
to uniquely identify an interface for internal resource allocation and management. NM-specific ifindex is
a parameter provided by the device to the NMS. In other words, it is the index for ifTable entries.
An NM-specific ifindex is in either of the following two formats:
1. 16-bit NM-specific ifindex
As its name implies, a 16-bit NM-specific ifindex value contains 16 bits and ranges from 1 to 65534. The
NM-specific ifindex value of each interface is allocated dynamically and increased sequentially. The
16-bit NM-specific ifindex is an index value without any syntax explanation, and is only used to uniquely
identify an interface.
2. 32-bit NM-specific ifindex
As its name implies, a 32-bit NM-specific ifindex value contains 32 bits, as shown in Figure 3 . The value
is composed of the following parts: Chassis ID, Slot ID, interface type, and interface offset.
Figure 3 32-bit NM-specific ifindex