The U2000 can properly deliver performance monitoring instances to devices, but the related performance data cannot be collected. After real-time performance is clicked, an error message is displayed indicating device offline.
1. The SMMP configuration is incorrect.
2. The Telnet or FTP configuration is incorrect.
3. The U2000 configuration is incorrect.
4. The device configuration is incorrect.
1. Perform the Telnet or STelnet test on NEs. The test result is normal, indicating that the Telnet configuration on the U2000 is the same as that on NEs.
2. Perform the FTP test. Data synchronization and data backup and restoration can be properly performed on NEs.
3. Perform the SNMPv3 function test on NEs. The test result is normal and the SNMP-related user name, password, and encryption settings are correct.
4. Check that other NEs on the U2000 can work properly and the license insufficiency problem does not occur.
5. Check the configuration script. It is found that the snmp-agent local-engineid configuration is the same for four devices. There is a possibility that this configuration is copied and pasted on different devices.
6. Run the undo snmp-agent local-engineid command to restore the default setting of snmp-agent local-engineid. Then, perform NE synchronization. After the operation, the performance monitoring function can be used properly.
The SNMP engine ID is the unique identifier for management of the SNMP module, which identifies an SNMP entity in an administrative domain. The SNMP engine ID is key to an SNMP entity. It implements functions such as message scheduling, message processing, authentication, and access control of SNMP messages.
In SNMPv3, an SNMP proxy needs to define a unique engineid as a response to an SNMPv3 request.
The local-engineid configuration is modified by default on the local device, which conflicts with that of a network device. The U2000 receives information from devices with the same local-engineid configuration; therefore, the U2000 fails to respond to an SNMPv3 request. In the data packets replied by the U2000 to the device, the local-engineid field is not identified, causing some NE functions on the U2000 to be restricted.
During data configuration for deployment, do not perform copy and paste on too many configurations. This may cause duplicate local-engineid on multiple devices.