User's Manual

Misconfigurations and Optimizations Report 875
No Free Redirection Table Entries The switch is already redirecting to
a Webcache (4400) or a number of Webcaches (49xx) and there are no
more free cache entries in the internal redirection table, therefore
Webcache Redirection cannot be enabled to this Webcache. This will
result in the following status text being returned to the client browser:
Unable to redirect web traffic to this Webcache. There are no
free redirection table entries available. Click the back
button to return to the Misconfigurations and Optimizations
Report.
Already Redirecting to Webcache Redirection is already enabled
from this switch to this Webcache. This will result in the following status
text being returned to the client browser:
The device is already redirecting web traffic to this
Webcache. Click the back button to return to the
Misconfigurations and Optimizations Report.
No Health Checks Webcache redirection has previously been
configured to the Webcache, however there are no health checks being
performed on the Webcache. This will result in the following response
being returned to the client browser:
Web traffic redirection is already configured to this
Webcache but there are no health checks being performed on
the Webcache.
Webcache Redirection Not Being Performed Redirection has been
enabled to this Webcache, the health check is ok but redirection is not
being performed. This may be due to the Webcache being attached to a
port that is a member of an aggregation or a resilient pair. This will result
in the following response being returned to the client browser:
Web traffic redirection is already configured to this
Webcache, the health check is working but redirection is not
being performed. Please consult your Webcache user guide.
This may be due to the Webcache being attached to a port that
is a member of an aggregated link or a resilient pair.
Health Check Failed The health check has failed and although
Webcache Redirection is already enabled to this cache, redirection is not
actually being performed. This will result in the following response being
returned to the client browser: