Problem: Unable to receive alarms on the NFM-P, or alarm performance is degraded

General information

By default, the system begins purging alarms when the outstanding alarm count reaches 50 000, unless historical alarm record logging and purging alarm policies are configured to keep the outstanding alarm count below that level.

Steps
CAUTION 

CAUTION

Service Disruption

Exceeding the alarm limit configured in the nms-server.xml file may cause system performance problems.

Contact your technical support representative for assistance.

 
1 

Check the status bar of the NFM-P client GUI status bar for indications that the maximum number of alarms for the system is reached.

2 

If required, clear outstanding alarms or delete them to the alarm history record log, as described in the NSP NFM-P Classic Management User Guide.

3 

If the NFM-P system includes one or more auxiliary servers, perform Problem: Excessive NFM-P server-to-client response time to ensure that system performance is not degraded because of auxiliary-server unavailability.

4 

Contact your technical support representative for more information.

End of steps