Use disable ess to disable a Survivable Core Server or main server from connecting to Procr. The disable ess cluster n command allows a Survivable Core Server cluster to be disabled (taken out of service).
Communication Manager preserves the enabled/disabled status of Survivable Core Servers and Main servers across server shutdown and restart.
A disabled Survivable Core Server remains registered and receives file sync translation updates.
Execute disable ess from either a main or Survivable Core Server. A Survivable Core Server may disable only its own cluster ID. When disable ess is run from the main server, any and all clusters may be disabled including the main server itself.
Caution:
Use caution when using disable ess all. Since the main typically controls Procr and a cluster may not be disabled when it controls Procr, it is generally safe to use disable ess cluster all to disable only the Survivable Core Server clusters.
Be aware that if the main is not controlling Procr and disable ess cluster all is used, the main will also be disabled.
When a Survivable Core Server is disabled, it reboots. After the reboot, the server is in the Survivable Core Server disabled state and will not connect to any Procr. If the cluster involves duplicated servers, this process may take slightly longer while the active server informs the standby of its new Survivable Core Server disabled state. When the system duplicates Survivable Core Server, the standby server also gets updated and rebooted.
When a valid disable ess command is run from a Survivable Core Server:
The server reboots.
No SAT screen is displayed.
Once the server has rebooted, use status ess cluster to confirm that the disable operation succeeded.
When a valid disable ess command is run from a main server:
TEST RESULTS screen appears
If the disable ess command specifies the cluster ID of the main itself, the server reboots and no SAT screen is displayed.
Use status ess cluster to confirm that the disable operation succeeded.
