Avaya ESS

Maintenance
154 Avaya Enterprise Survivable Servers (ESS) Users Guide
Use status ess clusters to see the state of the Main server and all administered ESS
servers. Under normal conditions, with full network connectivity, all ESS servers should register
with the Main server.
Figure 46: status ess clusters command example - Main server
is a typical example of status
ess clusters executed on a Main server (Cluster ID 1). The Main server knows the identities
of all of its associated ESS servers from the translations input to the Main server. The Main
server knows the state of all of the ESS servers that have successfully registered with it. When
status ess clusters is run on the Main server it shows its own state.
Figure 46: status ess clusters command example - Main server
See status ess clusters field descriptions on page 155.
Figure 47: status ess clusters command example - ESS
on page 155 is a typical example of
status ess clusters executed on an ESS (Cluster ID 60). The ESS server knows only its own
state. It takes time for this state to be propagated to the Main server via the registration link, and
for a short time (minutes) there may be a discrepancy between the state displayed by the ESS
server and the equivalent state displayed for the ESS server on the Main server.
Action/Object Qualifier Qualifier Description Login
status ess cluster none Examples:
status ess cluster
init
inads
craft
cust su
status ess clusters
Cluster ID 1 ESS CLUSTER INFORMATION
Active
Cluster Server Translations Software
ID Enabled? ID Registered? Updated Version
1 y 1 y 11:02 3/7/2005 R013x.00.0.338.0
10 y 91 y 11:02 3/7/2005 R013x.00.0.338.0
20 y 97 y 11:02 3/7/2005 R013x.00.0.338.0
30 y 96 y 11:02 3/7/2005 R013x.00.0.338.0
40 n 95 y 11:02 3/7/2005 R013x.00.0.338.0
50 y 94 y 11:02 3/7/2005 R013x.00.0.338.0
60 y 90 y 11:02 3/7/2005 R013x.00.0.338.0
70 y 88 y 11:02 3/7/2005 R013x.00.0.338.0
80 n 8 y 11:02 3/7/2005 R013x.00.0.338.0
90 y 9 y 11:02 3/7/2005 R013x.00.0.338.0
Command successfully completed
Command: