Manage FS 5000 call server quarantine status | |||
GO |
This topic describes the steps to quarantine and un-quarantine an FS 5000 call server. An administrator manually quarantines an FS 5000 call server when the call server is unable to provide services. Quarantining call server is not an automatic process.
Important! This procedure is normally performed at the OMC-P in case of disasters. The procedure must only be performed using Explorer in case of emergency. For example, when no OMC-P is operational.
The protection call server is not intended to act as an alternate call server when the primary call server is temporarily unavailable. For example, due to a failing connection to the primary call server.
When users register with the protection call server or with the primary call server, there is a minor performance impact on the Lucent CM system.
The performance impact is the same as when users register during a normal Lucent CM system startup.
Perform the following steps to quarantine an FS 5000 call server:
1 |
At the Lucent CM Explorer tree view, navigate to the Call server folder (Lucent CM System → Services → Call Server) Result: The Call Server List displays, listing the available call servers. | ||||||
2 |
Select the call server and click Edit. | ||||||
3 |
| ||||||
4 |
Click Yes to confirm you want to change the quarantine status of the call server. End of steps |
When you quarantine a call server, Lucent CM performs the following actions:
Lucent CM de-registers users with the quarantined call server.
Lucent CM disconnects connections to the quarantined call server.
Lucent CM establishes connections the protection call server.
Lucent CM registers users with the protection call server.
When you un-quarantine a call server, Lucent CM returns to the original configuration. Connections to the protection call server are disconnected, connections to the original call server are re-established, and users register with the original call server.
GO | |||
© Lucent Technologies |