Policy and Rule Descriptions
Policies Set in WebQoS
Corrective Actions for SLO and Threshold Policy Violations
Corrective actions are those actions taken to bring an SLO or threshold policy into compliance. These actions are only performed on new sessions. Existing sessions that are already admitted into the system are not affected. The corrective actions supported by WebQoS are:
•Redirect sessions up to NUMBER times for CLASS priority request
This corrective action limits the number of times a packet can be redirected. You enter the NUMBER of times for the respective priority request. It is highly recommended that these specific URL and /or cluster domain machines all have mirrored sites. You have two choices for redirection of the session:
—To the URL of a website (for example,
—To a cluster domain (for example,
If the NUMBER of redirection is met, the next corrective action for this class is executed. If no other corrective action for this class is found, the session is admitted into the system. Therefore, it is highly recommended that every redirection policy has a redirection action of the same class following it in the corrective action list.
•Reject CLASS priority requests
This corrective action rejects sessions for the respective priority request.
When a session is rejected, WebQoS sends the rejected session a web page indicating that the server is not available.
If both redirection and rejection actions are configured for any class, the rejection action should be the last in the corrective action list. For example, for any class, the order of its corrective action class could be: “redirect, reject” but not “reject, redirect.”
Refer to “Customizing the Reject and Defer Web Pages” on page 162 for information about how to customize the Reject web page.
Appendix A | 161 |
