Configuring the reply-error action, Configuring the log action – Brocade Virtual ADX Server Load Balancing Guide (Supporting ADX v03.1.00) User Manual
Page 269
![background image](/manuals/361724/269/background.png)
Brocade Virtual ADX Server Load Balancing Guide
253
53-1003247-01
Layer 7 content switching
5
The persist-method variable specifies which of the following persist methods you want to use.
•
hash-to-bucket – Hashes the persist string to a hashing bucket, as illustrated in
. This
is the default.
•
hash-to-group-id – Hashes the persist string to a server group ID, instead of to a hashing
bucket.
•
group-or-server-id – Translates the persist string to the ID of a real server or server group.
•
server-name – Translates the persist string to the name of a real server.
•
alias-name – Translates the persist string to the name of an alias.
The secondary keyword indicates that this is a secondary persist action for the rule. If the primary
persist action does not return a valid persist string, or if the server indicated by the primary persist
string is not available, the Brocade Virtual ADX uses the secondary persist action to direct packets
to a server.
NOTE
By configuring both a CSW policy that utilizes the persist action and a TCP or UDP port as sticky, you
can implicitly enable persistence fallback. In this scenario, the CSW policy defines the default
method of defining persistence. However, If no cookie is detected, the Brocade Virtual ADX falls back
to the sticky persistence configured for the address.
Configuring the reply-error action
The reply-error action causes the Brocade Virtual ADX to send a 403 error code page back to the
client when the specified rule is matched.
For example, to cause the Brocade Virtual ADX to send a 403 error code page to a client that sent a
packet that matched rule r1, enter the following command.
Virtual ADX(config-csw-policy1)#match r1 reply-error
Syntax: [no] match rule-name reply-error
Configuring the log action
The CSW match log action only logs to a log server, not the local log of the Brocade Virtual ADX
displayed by the show logging command. You must configure a remote server (per the global
logging ip-addr command) to receive the log. The syslog server cannot be connected to the
management port because CSW log action is processed by the BP, and the management port is
controlled by the MP.
NOTE
The log action requires a primary action forward or persist to be configured.
An example Syslog message follows.
192.168.9.210 80 HTTP Rule matched, Forward
To cause the Brocade Virtual ADX to write a message to Syslog when rule r1 is matched, enter a
command such as the following:
Virtual ADX(config-csw-policy1)#match r1 log
Syntax: [no] match rule-name log [format]