Hello everyone,
Today I will share with you how to deal with device node information that cannot be read through a third-party NMS.
Issue Description
Device model: S5700-28C-EI-24S
Networking overview: S5700--- third-party NMS
SNMP Configuration scripts:
snmp-agent
snmp-agent local-engineid 800007DB03E4C2D1FDXXXX
snmp-agent community read cipher xxxx
snmp-agent sys-info version v2c v3
Currently, there are two S5700-28C-EI-24S switches. After SNMP parameters are configured, switch the information (such as the user MAC address and switch IP address) cannot be obtained through the third-party NMS. S5700-52C-EI and S5700S-52P-LI-AC are normal.
Handling Process
1. Query the SNMP configurations of the switches. The configurations are the same, and no exception occurs.
2. Check the debugging information about the SNMP packets and find that the NMS queries the MIB object ipNetToMediaPhysAddress through SNMP packets. The device does not respond, as shown in the following figure.
The following figure shows the packets that are normally delivered.
3. Run the display snmp-agent mib-view command to query the MIB view. It is found that the faulty switch does not have the corresponding MIB view. Therefore, the NMS cannot access the MIB information of the switch through SNMP information.
4. Run the snmp-agent community read cipher xxx@XX mib-view iso command.
snmp-agent mib-view included iso iso
The problem is resolved after the ISO view is added and the read and write community names are bound.
Root Cause
The S5700-28C-EI-24S does not have a default MIB view. Therefore, the MIB node information cannot be read.
Solution
Run the snmp-agent community read cipher xxx@XX mib-view iso command.
snmp-agent mib-view included iso iso
The MIB view is added and the read and write community names configured by users are bound to solve the problem.
That is all I want to share with you! Thank you!
