beautypg.com

Optimized fast-path slb processing, Configuring tcp fast aging, Configuration considerations – Brocade Virtual ADX Server Load Balancing Guide (Supporting ADX v03.1.00) User Manual

Page 132

background image

116

Brocade Virtual ADX Server Load Balancing Guide

53-1003247-01

Miscellaneous options

2

Optimized fast-path SLB processing

You can enable the Brocade Virtual ADX to use fast-path processing for stateful SLB. Stateful SLB is
the standard form of SLB that uses session table entries to track session information. All traffic for
stateful SLB takes an optimized processing path.

When you enable fast-path processing, the Brocade Virtual ADX does not process every TCP or UDP
packet in a given session in detail. Instead, the Brocade Virtual ADX uses information gathered
during setup of the session to forward packets in the session.

NOTE

SLB optimization is useful if simple stateful SLB is the primary or sole application on the device.

NOTE

Stateful SLB traffic is optimized by default.

Configuration considerations

Consider the following:

Optimization applies only to SLB TCP or UDP traffic that is initiated by clients. Other types of
traffic are not optimized.

Optimization does not apply to fragmented IP packets.

In the current release, the port name or number on the VIP must be same as the one on the
real server bound to the VIP. Port translation is not supported.

FTP traffic is not supported.

Source NAT (source-nat command) is not supported.

Host ranges (host-range command) are not supported.

Many-to-one TCP or UDP port binding (no port tcp/udp-port translate command) is not
supported.

NOTE

Traffic for an SLB configuration that does not meet these criteria is still forwarded using normal
processing, but fast-path processing is not used.

Configuring TCP fast aging

Following a RST from the server, the Brocade Virtual ADX ages out session table entries in the
amount of time specified in the server msl seconds command, by default 8 seconds. You can
optionally configure the Brocade Virtual ADX to use the 1- to 2- minute aging time used in previous
releases.

To set the amount of time a session table entry stays in the delete queue following a RST from the
server, enter a command such as the following.

Virtual ADX(config)#server msl 2

Syntax: server msl seconds

The seconds variable can be from 1 through 180 seconds. The default is 8 seconds. Note that
attempting to set the value to 0 resets the value to the default (8 sec.).