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

128 Brocade Virtual ADX Server Load Balancing Guide
53-1003247-01
Miscellaneous options
2
Defining the health of a VIP port globally
To globally define the percentage of bound real server ports that must be healthy to consider a VIP
port healthy, enter commands such as the following.
Virtual ADX(config)#server rhi-active-bindings-threshold 20
Syntax: [no] server rhi-active-bindings-threshold percent
Defining the health of a VIP port per VIP
To define the percentage of bound real server ports that must be healthy to consider a VIP port
healthy for a specific VIP, enter commands such as the following.
Virtual ADX(config)#server virtual-name-or-ip dns-p1
Virtual ADX(config-vs-dns-p1)#rhi-active-bindings-threshold 30
NOTE
The VIP level configuration applies to all Virtual ports on the configured virtual server.
Syntax: [no] rhi-active-bindings-threshold percent
A valid range for percent is 1 through 100.
If the percent variable is not set, the percentage is 0. In this case, the default method will be used
to determine the health of the VIP port. For example, a VIP port will be considered healthy as long
as there is at least one healthy real server port bound to it.
As another example, consider a virtual server 10.1.1.101 with the port http command configured.
This port http of the virtual server is bound to port http of real server 10.1.1.15 and port http of real
server 10.1.1.44. If you have not configured any active bindings threshold percentage, then port
http of VIP 10.1.1.101 will be considered healthy as long as at least one of the two bound real
server ports is healthy.
If you configure an active bindings threshold percentage of 100, then this setting requires all
bound real server ports for the VIP port to be healthy in order to consider the VIP port healthy. If real
server port http for real server 10.1.1.15 goes down, then VIP port http is no longer considered
healthy because only 50 percent of the bound real server ports are healthy. The configuration in
this example requires 100 percent of the bound real server ports to be up in order to consider the
VIP port as healthy.
Defining the health of a VIP
Multiple VIP ports can be configured for a VIP. There are two options provided for determining the
health of a VIP:
• By default, a VIP will be considered healthy if all VIP ports for the VIP are healthy.
• You can specify a VIP to be considered healthy as long as there is at least one healthy VIP port.
To specify that a VIP should be considered healthy if at least one VIP port is healthy, enter
commands such as the following.
Virtual ADX(config)#server rhi-one-vip-port-up
Syntax: [no] server rhi-one-vip-port-up
If this command is not configured, a VIP will be considered healthy only if all VIP ports are healthy.