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

30 Brocade Virtual ADX Server Load Balancing Guide
53-1003247-01
Real server ports
2
Configuring a real port as TCP-only or UDP-only
This feature allows you to configure a Brocade Virtual ADX to allow traffic to a virtual port being
load-balanced to a different set of real ports based on its protocol (TCP or UDP). No configuration
change is required for the virtual server. A virtual port can be bound to tcp-only, udp-only and a
regular real port at the same time.
By default, a real port accepts both TCP and UDP traffic. If a real port is configured as tcp-only,
when a given traffic is UDP traffic, the real port will not participate in the server selection, even if it
is bound to the virtual port. Similarly, a udp-only port will not be considered for TCP traffic.
The behaviors of all predictors remain unchanged among eligible real ports (i.e., tcp-only and
regular real ports for TCP traffic, and udp-only and regular real ports for UDP traffic).
The tcp-only, and udp-only commands for a real port are configured under the real port
configuration mode as shown in the following.
Virtual ADX(config)#server real R1 10.10.10.1
Virtual ADX(config-rs-R1)#port 80 tcp-only
Virtual ADX(config-rs-R1)#exit
Virtual ADX(config)#server real R2 10.10.11.1
Virtual ADX(config-rs-R2)#port 80 udp-only
Syntax: [no] port portnum {tcp-only | udp-only}
The portnum variable specifies the application port you want to make tcp-only or udp-only.
TCP only and UDP only are mutually exclusive. This means that when tcp-only is configured,
udp-only cannot be configured for a port at the same time. udp-only will be automatically disabled if
tcp-only is configured, and vice versa.
Configuring a stateless port
By default, the Brocade Virtual ADX creates session table entries for sessions between clients and
applications on real servers. The Brocade Virtual ADX uses the session table entries to maintain
state information for the sessions. The Brocade Virtual ADX uses the state information for features
such as health checking and session failover in Hot Standby HA configurations.
You can configure individual application ports to be stateless. The Brocade Virtual ADX does not
maintain state information for a stateless port. Making a port stateless is useful when you want to
conserve session table resources or when you have configured the VIP to be transparent.
For examples and configuration information, refer to Chapter 3, “Stateless Server Load Balancing” .
To configure an application port to be stateless, enable the stateless parameter on the port in the
virtual server, such as the following.
Virtual ADX(config)#server real R1 10.10.10.1
Virtual ADX(config-rs-R1)#port http
Virtual ADX(config-rs-R1)#exit
Virtual ADX(config)#server real R2 10.10.11.1
Virtual ADX(config-rs-R2)#port http
Virtual ADX(config-rs-R2)#exit
Virtual ADX(config)#server virtual-name-or-ip StatelessHTTP 192.168.4.69
Virtual ADX(config-vs-StatelessHTTP)#port http stateless
Virtual ADX(config-vs-StatelessHTTP)#bind http R1 http
Virtual ADX(config-vs-StatelessHTTP)#bind http R2 http
Syntax: [no] port tcp/udp-portnum stateless