50
Copyright © 2000 - 2005 KEMP Technologies, Inc. All Rights Reserved.
3.7. Exit
Leave the health check command level, any changes to the health check parameters will be saved and the
system will be configured accordingly.
4. Rules command level
The following commands can be performed at the rules command level.
4.1. Add <Rule-name>
This command creates a new rule <Rule-name>. It also switches into the Rule Edit command level. Upon
return to the Rules command level. Further rules may be added.
A rule must be added before a Real Server can use it.
4.2. Modify <Rule-name>
This command switches into the Rule Edit command level, so that the rule <Rule-name> can be edited.
4.3. Delete <Rule-name>
This deletes the specified rule. The rule will be deleted from all Real Servers to which it has been assigned.
4.4. Show [ <Rule-name> ]
Displays a list of all the rules (if no <Rule-name> parameter) is specified or the specified rule.
4.5. Help
Lists the commands that are available at the rules command level.
4.6. End
Terminate the CLI session. Any changes since entering the health check command level will be ignored.
4.7. Exit
Leave the rules command level, any changes to the rules will be saved and the system will be configured
accordingly.
5. Rule Edit command level
The following commands can be performed at the rule edit command level.
5.1. value <string>
This option allows the match string value of the rule to be set. Spaces are significant. By default a string is
treated as a regular expression. If <prefix> or <postfix> is set, then the string is treated as a literal string,
which is then matched at the start or end of the received URL respectively.
5.2. [no] negation
This command inverts (reverts to normal if [no] is specified) the sense of a rule. I.e. If negation is set, the
rule will be true if the received URL does NOT match the value of the rule.
5.3. [no] prefix
This specifies that the value of the rule should be matched at the start of the received URL.
5.4. [no] postfix
To Next Page
Loading...