beautypg.com

Brocade Virtual ADX Server Load Balancing Guide (Supporting ADX v03.1.00) User Manual

Page 206

background image

190

Brocade Virtual ADX Server Load Balancing Guide

53-1003247-01

Port profiles and attributes

4

Keepalive port

By default, the Brocade Virtual ADX bases the health of an application port on the port
itself. You can specify a different application port for the health check. In this case, the
Brocade Virtual ADX bases the health of an application port on the health of the other port
you specify.
Refer to

“Basing a port’s health on the health of another port”

on page 220.

NOTE: You cannot base the health of a port well-known to the Brocade Virtual ADX on the

health of another port, whether the port is well-known or not well-known.

Source of health for
alias port

By default, the Brocade Virtual ADX performs independent health checks on an alias port
and its master port. You can configure the Brocade Virtual ADX to base the health of an
alias port on the state of its master port.
Refer to

“Basing an alias port’s health on the health of its master port”

on page 219.

TCP or UDP age

The number of minutes a TCP or UDP session table entry can remain inactive before the
Brocade Virtual ADX times out the entry. This parameter is set globally for all TCP or UDP
ports but you can override the global setting for an individual port by changing that port’s
profile.
Refer to

“Overriding the global TCP or UDP age”

on page 192.

You can specify a TCP age from 2 through 60 minutes and a multiplier from 2 through 20.
Thus, the maximum configurable TCP age for an individual port is 1200 minutes (20
hours).
NOTE: You cannot specify a multiplier when configuring the global TCP age.
NOTE: Because UDP is a connectionless protocol, the Brocade Virtual ADX does not

remove a UDP session from its session table until the session times out. TCP is a
connection-based protocol. Therefore, for TCP sessions, the Brocade Virtual ADX
removes the session as soon as the client or server closes the session.

NOTE: For DNS and RADIUS UDP load balancing, the age value does not follow the normal

configuration and default value unless udp-normal-age is configured on the port.
The default UDP age will always be 2 minutes unless udp-normal-age is configured.

NOTE: The Brocade Virtual ADX immediately deletes a UDP DNS or RADIUS session table

entry when the Brocade Virtual ADX receives a reply for the application from a real
server. If desired, you can configure the Brocade Virtual ADX to age these ports like
other UDP ports, using the UDP age timer. Refer to

“Setting TCP and UDP ages for

VIPs”

on page 121.

Connection logging

You can enable logging for session table entries created for this port.
Refer to

“Syslog for session table entries”

on page 240.

Slow start

Configures the Brocade Virtual ADX to control the rate of new connections to the
application port to allow the server to ramp up.
Refer to

“Port slow-start mechanism”

on page 227.

Smooth factor

If you plan to use server response time as a load-balancing method, you can adjust the
amount of preference the Brocade Virtual ADX gives the most recent response time
compared to the previous response time.
Refer to

“Changing the smooth factor on an application port”

on page 192.

Recursive DNS
health checks

By default, a Layer 7 health check for a DNS port sends the query only to the real server
(DNS server). If the DNS server does not reply with the IP address or zone name requested
by the health check, the port fails the health check.
You can enable the real server to perform a recursive lookup for the IP address or zone
requested by the health check of the well-known DNS port (53).
Refer to

“Enabling recursive DNS health checks”

on page 179.

TABLE 18

Port profile attributes (Continued)

Attribute

Description