What is "Error 503" when using PacketShaper

Products

• PacketShaper

Issue/Introduction

The 503 error message means that admission control (web-refuse) was used on an HTTP flow because PacketShaper did not have enough bandwidth to satisfy the request. 

Resolution

If you get the 503 error message, the problem probably can be found in the policy or partition settings. Most likely the guaranteed rate specified in a rate policy is too large, or the partition is too small. You can eliminate this message by adjusting the partition, policy, or both. You can also change the admissions control from (web refuse) to (Squeeze) by selecting the admission control option when creating a rate policy. For specific steps, see Apply Admission Control in PacketGuide.

Packeteer recommends that you do NOT use a guaranteed rate for HTTP flows. Remember that policies affect flows and a single web request can generate many flows. For example, going to www.starwars.com generates 20 flows. Each file (image, text, Java applet) is a separate flow. If you do use guarantee rate policy for HTTP flows, then use a 0 guarantee and make sure you have enough bandwidth.

In addition you can check 

• Guaranteed Rate Policy
• Dynamic Partition
• Never-Admit Policy (specially using redirects over https)
• Class license
• Policy Flow Limit