No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search


To have a better experience, please upgrade your IE browser.


A Third-Party NMS Fails to Collect MPU Data of a Device Based on the MIB

Publication Date:  2018-10-09 Views:  228 Downloads:  0
Issue Description
The customer's third-party NMS collects the CPU usage data of the MPUs on two NE40E-X8s. The data collected are all 0s, whereas the data about the LPU's CPU usage is correct.
Handling Process
Search the MIB node for the board node ID corresponding to the entity name.

In the MIB node, search for the return value corresponding to the board node ID.

The returned values of MPU 9, MPU 10, SRU 9, and SRU 10 are all 0s, whereas those of CR56RPUA 9 and CR56RPUA 10 are 4 and 6, respectively. Log in to the NE40E-X8 and check the CPU usage of the device. The CPU usage of MPU 9 is 4, and that of MPU 10 is 6, which corresponds to the values returned from the CR56RPUA node.
Root Cause
The MIB entity name of the MPU of the NE40E-X8 series routers is CR56RPUA, and correct data can be collected only when you use the entity name for data search. The entity name used by the customer for data search is MPU. Therefore, incorrect data is returned.
Nodes and instance names in the MIB are not closely related to the software and hardware versions. If a similar problem occurs, perform the preceding steps for troubleshooting.