The periodic maintenance test of SAL Agent failure might indicate that the Avaya Breeze® platform alarm service might not be running.
To troubleshoot the database failure, you must perform the troubleshooting steps for Avaya Breeze® platform and System Manager. You must have root user privileges to perform the troubleshooting steps on System Manager.
Procedure
Perform the following steps for Avaya Breeze® platform:
On the System Manager web console, click Elements > Avaya Breeze.
Select System Tools and Monitoring > Maintenance Tests.
Select the affected Avaya Breeze® platform instance from the Select Target list.
Select the Test sanity of Secure Access Link (SAL) Agent test.
Click Execute Selected Tests.
If the test passes, clear the alarm. The problem no longer exists, and you do not need to continue with this procedure.
If the test fails, establish an SSH connection to the Avaya Breeze® platform instance using either the craft login (Avaya) or an established customer login.
Run the statapp command to verify the status of sal-agent.
If the status of sal-agent is Down, run restart sal-agent and wait for the sal-agent service to restart.
If the status of sal-agent is Partially UP, wait for the status to change to Up.
Run the statapp command to verify the status of sal-agent.
Run the Test sanity of Secure Access Link (SAL) Agent test again.
If the test still fails, reboot the Avaya Breeze® platform server using the Shutdown System > Reboot option on the Avaya Breeze® platform Server Administration page.
Perform the following steps for System Manager:
On the System ManagerHome page, under Elements, select Session Manager.
Select System Tools and Monitoring > Maintenance Tests.
Select System Manager from the Select Target list.
Select the Test sanity of Secure Access Link (SAL) Agent test.
Click Execute Selected Tests.
If the test passes, clear the alarm. The problem no longer exists, and you do not need to continue with this procedure.
Run the systemctl status spiritAgent command to verify the SAL agent service is running.
If the sal-agent service is up, nothing further needs to be done.
If the sal-agent service is down, run the service spritAgent restart command.
Wait for the sal-agent service to restart.
Run the systemctl status spiritAgent command to verify the sal-agent service is running.
Run the Test sanity of Secure Access Link (SAL) Agent test.
