04-26-2016 01:47 AM
Hi Guys
I have an issue with my WSA. when I run a policy trace on my WSA - it doesn't seem to match on some URL like www.google.com.
The result of this, is that the WSA is blocking all the request to this site
Does anyone have any suggestions as to how resolve this.
Two examples bellow.
1.URL Check
WBRS Score: 3.2
URL Category: Search Engines and Portals
Scanner "AVC" Verdict (Request): Google (Search Engine)
Policy Match
Cisco Data Security policy: None
Decryption policy: None
Routing policy: Global Routing Policy
Identification Profile: WHO
Access policy: (null)
Final Result
Request blocked
Details: Gateway timeout
Trace session complete
2.URL Check
WBRS Score: 3.4
URL Category: Pornography
Policy Match
Cisco Data Security policy: None
Decryption policy: None
Routing policy: None
Identification Profile: WHO
Access policy: Business_Hours
Final Result
Request blocked
Details: Request blocked based on URL category
Trace session complete
04-28-2016 06:19 PM
From the policy trace provided for google.com, you are getting 'gateway timeout' error that could indicate there is network issue for that destination.
Normal scenario when WSA getting gateway timeout is that WSA received the request and pass the request out however does not get any response from next hop or hops after it.
Also check if you have L4TM enabled (checked if T1/T2 interface is plug in) in WSA and make sure not blocking google.com
04-29-2016 02:08 AM
05-01-2016 06:56 PM
From logs provided, means that the WSA is having issues in sending the request out to the internet and most likely the WSA is not getting response back from outside or next hop of WSA.
This is matching from the logs that WSA is getting NONE\504 means that it is gateway timeout.
This not occurring if you set the policy to block, since WSA will block the traffic first and will not send the traffic out to internet/next hop since already blocked by its policy.
Would suggest running packet capture to see who is not responding back to WSA request. Also recommend to open TAC case to investigate deeper.
04-05-2017 07:46 AM
I had the same situation. WSA included the P1 port in the nexus 5596, which was off the port.
It turned out that the blocking rule on porn worked and determined group. And when were not included in the blocking rule, then the request is not left and were given Access policy: (null).
Turned on the port helped
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide