If the daemon or the service restarts successfully, manually clear the alarm:
ADDITIONAL INFORMATION:
From the Web interface, select Current Alarms and the appropriate alarm, and click Clear.
From the Linux command line, enter almclear -n #id.
If the daemon or the service fails to restart, go to the Avaya Support website at http://support.avaya.com to open a service request.
Enter grep svc_mon /var/log/messages to determine why the daemon failed to restart.
ADDITIONAL INFORMATION:
Caution:
The following procedure causes a brief service outage and must be executed only at the convenience of the customer.
If the output of the grep command does not help:
ADDITIONAL INFORMATION:
For duplicated servers, enter server to verify that the suspected server is the standby. If necessary and at the convenience of the customer, enter server -if to force a server interchange.
For non-duplicated servers, proceed to Step d.
For duplicated servers, reboot the standby server:
ADDITIONAL INFORMATION:
From the Web interface, select Shutdown This Server.
From the Linux command line, enter /sbin/shutdown -r now.
For non-duplicated servers, reboot the server:
ADDITIONAL INFORMATION:
From the web interface, select Shutdown This Server.
From the Linux command line, enter /sbin/shutdown -r now.
If rebooting the standby does not help or if the problem recurs, go to the Avaya Support website at http://support.avaya.com to open a service request.
