Administration Guide - Avaya Support

Introduction to the Messaging Application Server (MAS)
Rebooting MASs for Routine Maintenance
Messaging Application Servers (MASs) must be rebooted as part of routine
administration and ongoing maintenance.
Reboot Frequency
You must reboot your MASs at regular intervals, for instance every 3 or 4 months. The
exact reboot period depends on your system.
Note: If you go to Microsoft with a Windows support problem on your MAS, then
they'll turn you away, if the server has been running for more than 90 days.
If you have high usage MASs, you should reboot more frequently, for instance once per
month.
Note: The reboot cycle of the Avaya Message Store Server (MSS) can be less
frequent and does not need to match the MASs reboot cycle.
Disabling Alarming Before a Reboot
Before you reboot an MAS, you should disable alarming on the Avaya MSS.
Once the MAS is back up and running, go to the Alarm Log to verify that the alarm has
been resolved. This normally takes about 5 minutes. Then reactivate the alarming on
the Avaya MSS.
For more information, see Chapter 10, “MAS Event, Error & Alarm Logs” and the Avaya
Modular Messaging MSS Administration Guide.
Note: If you reboot the Avaya MSS, you should first disable alarming on the MAS.
For the setting to disable alarming, see Serviceability - General Tab on page
3-137.
Rebooting Multiple MAS Systems
For a Modular Messaging system with multiple MASs, you must reboot the primary
MAS first, then reboot each of the other MASs in any order. You must reboot one MAS
at a time, waiting for each to come back before rebooting the next.
The reboot of each MAS should be an orderly shutdown and restart, as described in
“Procedure 1” and “Procedure 2” below.
Avaya Modular Messaging Release 3.1 with the Avaya MSS
February 2007 MAS Administration Guide
1–13