Performance Data Is Unavailable on the Server Page 1 of 3

http://127.0.0.1:8890/go_outfiles/Lib20180702163517_R1_0/documents/NetNumenU... 15/12/2021
Performance Data Is Unavailable on the Server Page 2 of 3

http://127.0.0.1:8890/go_outfiles/Lib20180702163517_R1_0/documents/NetNumenU... 15/12/2021
Performance Data Is Unavailable on the Server Page 3 of 3

Performance Data Is Unavailable on the Server

Symptom

■ The performance data of some measurement types is unavailable on the NetNumen U31 server; while the performance data of the other measurement types is
available.

■ The performance data of some measured objects of a measurement type is unavailable on the NetNumen U31 server; while the performance data of the other
measured objects of the same type is available.

■ No performance data can be received from a lower-layer EMS suddenly.

■ The NetNumen U31 server receives the performance data of all measured objects from a lower-layer EMS after a fixed time delay.

■ The performance data of all measured objects is intermittently missing.

Probable Cause

■ No measurement task is created for some measurement types or measured objects.

■ The corresponding NEs are in "Testing" or "PM Testing" status.

■ The NetNumen U31 server fails to connect the lower-layer EMS, or the lower-layer EMS fails to connect the corresponding NE.

■ A failure occurs in the lower-layer EMS.

■ No free disk space is available on the lower-layer EMS, the NetNumen U31 server, or the database.

■ The system time of the lower-layer EMS is different from that of the server.

■ The corresponding NE agent has not been suspended or deleted in the previous version before the NetNumen U31 system is upgraded.

■ A transmission delay exists due to the network bandwidth limit.

Action

1 Verify that measurement tasks are created for all measured objects of each measurement type.

2 Verify that all NEs are in "Normal" status. If an NE is in "Testing" or "PM Testing" status, change its status to "Normal", to resume the reporting of performance
data.

3 Verify that the corresponding lower-layer EMS operate properly.

4 Verify that the network connection between the NetNumen U31 server and the lower-layer EMS is secure.

5 Verify that the link between the lower-layer EMS and the corresponding log server is normal.

6 Verify that sufficient free space is available on the disk of the lower-layer EMS, the disk of the NetNumen U31 server, and the tablespace in the database. If no
enough free space is available, remove unnecessary files to free up some space.

7 Verify that the system time of the NetNumen U31 system, the lower-layer EMS, and the NEs are the same.

8 Verify that all NE agents are suspended or deleted in the previous version before the upgrade of the NetNumen U31 system.

9 Test the transmission delay by sending a large file through FTP from the lower-layer EMS to the NetNumen U31 server. If the transmission delay is long, allocate
more bandwidth to the server and the lower-layer EMS.

10 If the failure still exists after the previous steps are completed, send related logs on the NetNumen U31 server and client to ZTE Technical Support for
troubleshooting.

http://127.0.0.1:8890/go_outfiles/Lib20180702163517_R1_0/documents/NetNumenU... 15/12/2021