Brocade Virtual ADX Server Load Balancing Guide (Supporting ADX v03.1.00) - Manual (Page 202)

186 Brocade Virtual ADX Server Load Balancing Guide
53-1003247-01
Server and application port states
4
Displaying real server state information
To display real server information, enter the following command at any level of the CLI.
Information about the remaining real servers has been omitted for brevity.
Syntax: show server real
The state information lists the state of the server itself first. Then the states of each of the
application ports configured on the server are displayed.
In this example, the server itself is enabled. The HTTP port is also enabled, but the “default” port (a
port the Brocade Virtual ADX automatically configures on all the real and virtual servers) is
unbound (unbnd). These states are typical of a Brocade Virtual ADX that is configured for
deployment but has not been connected to the real servers.
If information appears under the row for the HTTP application, it shows settings for the Layer 7
health checks for the port. For information about HTTP health checks and other configurable Layer
7 health check parameters, refer to
“Port-specific settings for Layer 7 health checks” on page 176.
SUSPECT The Brocade Virtual ADX associates a time stamp with each packet sent to and received from the
real servers. If the time gap between the last packet received from the server and the last packet
sent to the server grows to 3 or 4 seconds, the Brocade Virtual ADX sends a Layer 4 health check
to the service. (If applicable, and if the server passes the Layer 4 health check, the Brocade
Virtual ADX then sends a Layer 7 health check to the application.) If the application does not
respond within a specified interval, the Brocade Virtual ADX changes the state to SUSPECT and
resends the Layer 4 (and if applicable, Layer 7) health check up to a specific number of retries. If
the application still does not respond after all the retries, the state changes to FAILED and the
server state changes to TEST. If the application does respond, the application state changes to
ACTIVE.
GRACE_DN The forced-shutdown option has been used to gracefully shut the server down.
ACTIVE The application has passed its Layer 4 (and if applicable, Layer 7) health check.
UNBND The application is configured on the real server but is not yet bound to a virtual server.
TABLE 16 Application port states (Continued)
State Description
Virtual ADX(config)#show server real
Real Servers Info
========================
State - ACT:active, ENB:enabled, FAL:failed, TST:test, SUS:suspect,
GDN:grace-dn, DIS:disabled, UNK:unknown, UNB:unbind,
AWU:await-unbind, AWD: await-shutdown
Name: rs1 State: Enabled IP:10.95.7.1: 1
Mac: Unknown Weight: 1/1 MaxConn: n/a
SrcNAT: not-cfg, not-op DstNAT: not-cfg, not-op Serv-Rsts: 0
Port St Ms CurConn TotConn Rx-pkts Tx-pkts Rx-octet Tx-octet Reas
---- -- -- ------- ------- ------- ------- -------- -------- ----
default UNB 0 0 0 0 0 0 0 0
http ENB 0 0 0 0 0 0 0 0
Server Total 0 0 0 0 0 0 0