Supported Mibs - H3C S5600 Series Operation Manual

SNMPv3 adopts user name and password authentication.
SNMPv1 and SNMPv2c adopt community name authentication. The SNMP packets
containing invalid community names are discarded. SNMP community name is used to
define the relationship between SNMP NMS and SNMP agent. Community name functions
as password. It can limit accesses made by SNMP NMS to SNMP agent. You can perform
the following community name-related configuration.
Specifying MIB view that a community can access.
Set the permission for a community to access an MIB object to be read-only or
read-write. Communities with read-only permissions can only query the switch
information, while those with read-write permission can configure the switch as well.
Set the basic ACL specified by the community name.

Supported MIBs

An SNMP packet carries management variables with it. Management variable is used to
describe the management objects of a switch. To uniquely identify the management objects
of the switch, SNMP adopts a hierarchical naming scheme to organize the managed
objects. It is like a tree, with each tree node representing a managed object, as shown in
Figure 1-1. Each node in this tree can be uniquely identified by a path starting from the
root.
Figure 1-1 Architecture of the MIB tree
1
1
1
1
B
5
A
MIB describes the hierarchical architecture of the tree and it is the set defined by the
standard variables of the monitored network devices. In the above figure, the managed
object B can be uniquely identified by a string of numbers {1.2.1.1}. The number string is
the object identifier (OID) of the managed object.
The common MIBs supported by switches are listed in
2
2
2
6
Table
1-2
1-1.