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

28 Brocade Virtual ADX Server Load Balancing Guide
53-1003247-01
Real server ports
2
To disable all the application ports on a real server, enter the following command at the
configuration level for the server.
Virtual ADX(config-rs-R1)#port disable-all
To re-enable all the application ports, enter the following command.
Virtual ADX(config-rs-R1)#no port disable-all
Syntax: [no] port disable-all
Globally disabling application ports
You can globally disable a Layer 4 port on the Brocade Virtual ADX. The port can be disabled for all
real servers, all virtual servers, or all real and virtual servers. After you disable a port globally, you
can enable the port on individual real or virtual servers as necessary. By default, all real and virtual
ports are enabled.
When the Brocade Virtual ADX is booted, if the command to globally disable a real or virtual port
exists in the startup-config file, the specified port is disabled at startup. When a real or virtual port
is created, and the port has been disabled globally, the real or virtual port is disabled as well. You
must enable the port explicitly.
To disable all real HTTP ports, enter the following commands.
Virtual ADX(config)#server port 80
Virtual ADX(config-port-http)#disable real
Virtual ADX(config-port-http)#
To disable all virtual HTTP ports, enter the following commands.
Virtual ADX(config)#server port 80
Virtual ADX(config-port-http)#disable virtual
Virtual ADX(config-port-http)#
To disable all real and virtual HTTP ports, enter the following commands.
Virtual ADX(config)#server port 80
Virtual ADX(config-port-http)#disable
Virtual ADX(config-port-http)#
Syntax: disable [real | virtual]
Disabling SLB to a server when an application goes down
By default, if an application on a real server becomes unavailable, but the real server itself is still
up, the Brocade Virtual ADX continues to include the real server in its load balancing decisions for
the application. For example, if the HTTP application on a real server stops responding to Layer 4
health checks, but the real server continues to respond to Layer 3 health checks (IP pings) from the
Brocade Virtual ADX, the Brocade Virtual ADX continues to forward HTTP requests to the real
server.
NOTE
New connections are only sent to servers that have passed an application health check.
In some configurations, such as those that use a cluster of servers for an application, you may want
to configure the Brocade Virtual ADX to stop sending requests to a server when the requested
application is down on the server. For example, this feature is useful in an NFS configuration.