10 — Troubleshooting 5620 SAM server issues
Alcatel-Lucent 5620 Service Aware Manager, Release 10-9
3HE 05723 TQZZA Edition 01 Troubleshooting Guide
iv Review the information, which includes:
• the auxiliary server IP address
• the auxiliary server host name
• the auxiliary server port number
• the auxiliary server type (Reserved or Preferred)
• the auxiliary server status (Unknown, Down, Up, or Unused)
v If the auxiliary server status is Down, perform Procedure 10-1 on the auxiliary
server.
vi If the auxiliary server status is Unknown, perform Procedure 10-11 to check
the connectivity between the managed network and the main and auxiliary
servers.
5 Close the System Information form.
Procedure 10-7 Problem: Unable to receive alarms on the 5620 SAM,
or alarm performance is degraded
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.
1 Check the status bar of the 5620 SAM 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 5620 SAM User Guide.
3 If the 5620 SAM system includes one or more auxiliary servers, perform
Procedure 10-6 to ensure that system performance is not degraded because of
auxiliary-server unavailability.
4 Contact your Alcatel-Lucent support representative for more information.
Caution — Exceeding the alarm limit configured in the nms-server.xml
file may cause system performance problems.
To Next Page
Loading...
