Use status ess clusters to see the state of the main server and all administered Survivable Core Servers. Under normal conditions, with full network connectivity, all Survivable Core Servers should register with the main.
Syntax
status ess cluster
When status ess clusters is run on a main server (Cluster ID 1), the Main server:
knows the identities of all of its associated Survivable Core Server from the translations input to the main server.
knows the state of all of the Survivable Core Servers that have successfully registered with it.
shows its own state.
status ess clusters field descriptions
Note:
The field definitions are the same whether the status ess command is executed on a main server or Survivable Core Server.
Field
Description
Cluster ID (title line)
Cluster Identifier (1–999) of the server where status ess was run. In a duplex server environment, both the active and the standby server have the same cluster ID. Cluster ID is initially obtained from the license file (where it is called the Module ID or MID). Once save translation is executed, the cluster ID is saved in translations.
Cluster ID (detail line)
Cluster Identifier (1–999) of a server who’s state is known to the server where status ess was run. The detail lines are shown in cluster ID order. When status ess is issued on a main server, there is one detail line for the main server itself and a detail line for every Survivable Core Server that is registered with the main server. When status ess is issued on a Survivable Core Server there is only one detail line since a Survivable Core Server only knows its own state.
Enabled
The Survivable Core Server enabled or disabled state of the server.
y — enabled. This server will connect to administered Procr.
n — disabled. This server will not connect to administered Procr.
unknown — the main server does not yet know the maintenance state of the Survivable Core Server. This may be because:
the Survivable Core Server is not registered with the main server
the Survivable Core Server has not yet acknowledged a maintenance state change request from the Main via an enable ess or disable ess command.
Active Server ID
The server identifier of the active server for each cluster, Survivable Core Server or main server (1–99). This is the Server ID that was entered for this server in the Set Server Identities page during configuration.
If the server is a simplex configuration, there is only one Server Identifier.
If the server is a duplex configurations, the A and B servers each have unique server identifiers. Because in a duplex configuration only the active server registers with the Main, only its server identifier is displayed. Only server IDs for registered Survivable Core Servers are displayed.
Registered
The registration state of the server.
y — registered
n — not registered
The main server does not register with itself, but always displays its own registration as y.
Translations Updated
For a Survivable Core Server: The time and date of the latest translation update reported by the Survivable Core Server to the Main server over the registration link.
For a main server (Cluster ID 1): The time and date of the latest successful save translation command of any kind.
Note:
For a main server, this time stamp may be later than those shown for Survivable Core Servers. A save translation on the Main updates its time stamp. A save translation [ess | all] updates the Survivable Core Server translations and time stamp.
Software Version
The software version of Communication Manager running on the server. For a Survivable Core Server, this is reported to the Main server over the registration link.
