HP 7102dl - ProCurve Secure Router Configuration Manual page 344

Content Filtering
Troubleshooting Web Content Filtering
7-16
current problem. If Allow mode is enabled, it may very well be that the router
cannot contact the Websense server. See "The Router Cannot Connect to the
Websense Server" on page 7-18 to diagnose and fix this problem.
Finally, it is possible that the filtering policy on the Websense server is
misconfigured. By default, the Websense server does not prohibit any traffic.
You must configure a filtering policy that blocks certain categories. Remember
also to:
add users, groups, workstations, or networks as monitored clients
change the policy from monitoring only (the default) to active filtering
Detailed instructions for configuring policies and troubleshooting the Web-
sense server are beyond the scope of this guide. For more instructions, use
the Websense Manager's help tools or visit http://www.websense.com/global/
en/SupportAndKB/ProductDocumentation.
Some, But Not All, Inappropriate Traffic Is Filtered. The most likely
culprit for inconsistent filtering is a misconfigured Websense filtering policy.
Again, refer to the Websense Manager's help and product documentation.
It is also possible that the router has lost contact with the Websense server and
is applying its own policies, configured through the ip urlfilter exclusive-
domain command. You can enter show ip urlfilter exclusive-domain, view
permitted and denied URLs, and if necessary add to them. However, creating
an entire filtering policy using exclusive domains is not feasible. The most
important thing is to reestablish contact with the Websense server. (See "The
Router Cannot Connect to the Websense Server" on page 7-18.)
An overburdened Websense server may filter traffic inconsistently. This is
both because the router may drop requests until it receives responses to
outstanding requests and because the router may time out the connection
before the server has a chance to reply. Until the router can reconnect to the
server, it will either allow or block all HTTP traffic (according to its Allow
mode). You can attempt the following measures to deal with such a problem:
increase the Websense server's timeout setting (ip urlfilter server
<A.B.C.D> timeout <seconds>)
decrease the number of different policies that the Websense server
enforces