Brocade Virtual ADX MIB Reference (Supporting ADX v03.1.00) User Manual
Page 207

Brocade Virtual ADX MIB Reference
195
53-1003312-01
Real server objects
snL4RealServerPortStatisticSt
ate
brcdIp.1.1.4.24.1.1.5
Syntax: Integer
Read
only
Shows the operational state of the server when the statistics were
obtained:
•
disabled(0) – This value has been deprecated and is not used.
•
enabled(1) – There is no link to the server. The server is configured
on the ServerIron but is not physically connected to the ServerIron.
•
failed(2) – The server has failed to respond to repeated Layer 3
health checks (IP pings). Typically, a server changes to the failed(2)
state from the suspect(4) state.
•
testing(3) – The server is still reachable at Layer 3, but at least one
of the application ports on the server has failed to respond to its
health checks. If the application port is not a TCP or UDP port
known to the ServerIron or if the Layer 7 health check for the port is
disabled, only the Layer 4 health check is used. If the service is a
TCP or UDP port known to the ServerIron and the Layer 7 health
check is enabled, then the application must pass both health
checks to avoid entering the testing(3) state. The ServerIron
continues to try to reach the application indefinitely. If the server
continues to be reachable at Layer 3, the state will remain
testing(3) as long as the ServerIron cannot reach the application
that is failing its health check.
•
suspect(4) – The ServerIron associates a time stamp with each
packet sent to and received from the servers. If the time gap
between the last packet received from the server and the last
packet sent to the server increases to three or four seconds, the
ServerIron sends a Layer 3 health check (ping) to the server. If the
server does not respond within the ping interval (configured in the
object) the ServerIron changes the state to
suspect(4) and resends the ping, up to the number of retries
specified by the
object. If the server still doesn't
respond after all the retries, the state changes to failed(2). If the
server does respond, the state changes to active(6).
•
shutdown(5) – The forced-shutdown option has been used to
gracefully shut down the server.
•
active(6) – The server has responded to the Layer 3 health check
(IP ping), and all the services on the server have passed their Layer
4, and if applicable, Layer 7) health checks.
•
unbound(7) – The unbind action is complete.
•
awaitUnbind(8) – The unbind action has been issued and is waiting
for completion.
•
awaitDelete(9) – The delete action has been issued and is waiting
for completion.
Await actions occur because ServerIron sends a command
from MP to all BPs and needs to wait for all BPs to have
gracefully synced with other BPs that, for example, are
deleting real servers, etc.
snL4RealServerPortStatisticF
ailTime
brcdIp.1.1.4.24.1.1.6
Syntax: Integer
Read
only
This object applies only ports whose operational state is failed(2).
Shows the number of seconds that has elapsed since the last time the
port tried to re-establish connection with the server.
snL4RealServerPortStatisticC
urrentConnection
brcdIp.1.1.4.24.1.1.7
Syntax: Integer
Read
only
Shows the number of client connections currently on the this port of the
server. A connection consists of two sessions, the client-to-server
session and the server-to-client session.
Name, OID, and Syntax
Access Description