Operation Manual – SNMP and RMONH3C S7500 Series Ethernet Switches Chapter 1 SNMP Configuration1-21.1.2 SNMP VersionsCurrently an SNMP agent of a device supports SNMPv3, and is compatible withSNMPv1 and SNMPv2c.SNMPv3 adopts user name and password authentication.SNMPv1 and SNMPv2c adopt community name authentication. SNMP packets failingto pass community name authentication are discarded. A community name is used todefine the relationship between SNMP NMS and SNMP agents. Similar to passwords,a community name can limit access to SNMP agents from the SNMP NMS. You candefine the following features relevant to a community name.z Define a MIB view that a community name can access.z Assign read-only or read-write access right to MIB objects for the communityname. A community name with read-only access right can only query the deviceinformation, while a community name with read-write access right can not onlyquery the device information but also configure the device.z Set the basic ACL specified by the community name.1.1.3 MIBs Supported by the DeviceThe management variable in a SNMP packet is used to describe a management objectof a device. To uniquely identify a management object of a device in an SNMP packet,SNMP adopts the hierarchical naming scheme to identify managed objects. Thehierarchical architecture is like a tree, and each tree node represents a managed object,as shown in Figure 1-1. In this way, an object can be identified through a unique pathstarting from the root.A15111B2622Figure 1-1 Architecture of the MIB treeThe Management Information Base (MIB) is used to describe the hierarchicalarchitecture of the tree and it is the set defined by the standard variables of themonitored network devices. In Figure 1-1, the managed object B can be uniquelyidentified by a string of numbers {1.2.1.1}. The number string is the object identifier ofthe managed object B.Common MIBs supported by the system are listed in Table 1-1.