You can specify the level of service availability for Avaya Aura® MS which is in the started state. The level of service availability is useful under certain conditions as follows:
|
Action
|
Description
|
|
Lock
|
Locks the system and ends existing sessions. The media server no longer accepts new requests, and redirects new traffic to other nodes in the cluster. You typically place the system into locked state when performing maintenance. The Operational State of Avaya Aura® MS must be set to Unlocked or Pending Locked before you can lock Avaya Aura® MS.
|
|
Unlock
|
Unlocks the media server and allows incoming session requests to be accepted by the system for processing. The Operational State of Avaya Aura® MS must be set to Locked or Pending Locked before you can unlock Avaya Aura® MS.
|
|
Pending Lock
|
The system does not accept new requests. It redirects new traffic to other nodes in the cluster. Unlike Lock, Pending Lock preserves existing sessions. You typically place the system into a Pending Locked state before transiting to a Locked state when you prepare for system maintenance. This allows sessions to naturally end over time, without being ended unexpectedly for users of the system. The system automatically changes to the Locked state after all the sessions have ended. The Operational State of Avaya Aura® MS must be set to Unlocked or Locked before you set the system to Pending Lock.
|
|
Failover
|
Transfers all the active sessions from this media server to the peer. The peer automatically becomes the active node. All new session requests are automatically directed to the newly active peer node. The failed node enters the Standby state and is ready for maintenance or other activities while the peer continues to provide service. You can select Failover when the media server is in a High Availability configuration with another node.
|
