Troubleshooting Common Problems; Web Content Filtering Does Not Take Effect - HP 7102dl - ProCurve Secure Router Configuration Manual

Content Filtering
Troubleshooting Web Content Filtering
Messages
• Could not connect to Websense
Enterprise server A.B.C.D
• Trying to connect to Websense
Enterprise server A.B.C.D
• Websense Enterprise server
A.B.C.D refused connection
Reached maximum number of
outstanding requests
Reached maximum number of buffered
responses
Allow mode set to allow all requests
Allow mode set to block all requests
N o t e
7-14
Table 7-2. Web Content Filtering Debug Messages
Meaning
The router cannot connect to the
Websense server.
The router cannot submit the request to
access a Web site to the Websense
server because the router is waiting for
responses to previous requests.
The router is dropping responses from
a Web server because its buffer is full.
The router cannot connect to the
Websense server and will allow
unlimited access to the Internet.
The router cannot connect to the
Websense server and will block all
access to the Internet.
Debug messages are processor-intensive and can seriously degrade network
performance. Take care when using debug commands.

Troubleshooting Common Problems

This section will teach you how to look for and fix some common problems.

Web Content Filtering Does Not Take Effect

When your filtering policies do not seem to actually prevent users from
reaching inappropriate Web sites, first determine the scope of the problem.
Are any Web sites being prohibited or none at all?
No Filtering. If no Web sites at all are being prohibited, first verify that the
firewall is enabled on the ProCurve Secure Router. The router cannot filter
traffic unless the firewall is on.
Possible Problems
• The link to the Websense server is
down.
• The server's IP address has been
entered incorrectly.
• The route to the server's network is
incorrect.
• The server is running a firewall.
• The server has failed.
• The ip urlfilter maximum-requests
setting is too low.
• The Websense server is
overburdened.
• The ip urlfilter maximum-responses
setting is too low.
• The network is congested.
See Row 1.
See Row 1.