04-07-2011 01:20 AM - edited 03-11-2019 01:18 PM
Hi,
I have a server having ip address 172.21.X.X, and it is always getting shunned. I have to manually clear the shuna everytime. Why the server is getting blocked at shun, i am unable to understand ? I can bypass the server adress at shun, but that's not solution. The server contains linux OS. Can anyone please help on this ?
Thanks in advance
Dipak
Solved! Go to Solution.
07-15-2011 12:33 AM
Hi Dipak,
We would need to verify it on the IPS as well as threat-detection as well:
For threat-detection you can use the "except" keyword to exclude your server.
threat-detection scanning-threat shun except ip-address 172.21.10.13 255.255.255.255
To check on IP, login to the IDM, and on the top go to monitoring------> Active hosts Block--------> There you can see if this server is being blocked by the IPS server.
If it is blocked by IPS, go to Configuration ----------> Blocking Properties -----------> Never block IP's.
Screenshot are attached.
Hope this helps.
Thanks,
Varun
07-15-2011 09:22 PM
Hi Dipak,
Login to the device, and issue the command:
tls generate-key
http://www.cisco.com/en/US/products/hw/vpndevc/ps4077/products_qanda_item09186a008025c533.shtml
this would genrate new key.
Thanks,
Varun
07-16-2011 01:31 AM
Hi Dipak,
These docs would help you great deal in configuring IPS with IME:
http://www.cisco.com/en/US/docs/security/ips/7.0/configuration/guide/ime/ime_event_monitoring.html
If you face any configuration issues, raise a TAC ticket and involve an engineer on it.
Thanks,
Varun
04-07-2011 02:51 AM
Hi,
The best way to find out would be to enable debug level logging and wait for the server to be shunned again.
The logs should give more insight.
Paps
07-11-2011 08:57 AM
Hi,
What is the debug command for shun ? I have searched a lot over internet, but counldn't find anything.
Thanks a lot in advance
Regards
Dipak
07-11-2011 09:37 AM
Hi Dipak,
Can u explain what is the purpose for it, what information are you trying to see??
Varun
07-11-2011 08:23 PM
Hi Varun,
As suggested by Mr. Padatta, i am trying to do debug level logging for the shunned server. It's creating a lot of problem when the server are getting shunned and i have to remove it manually. Is there is any other way to solve this issue ? Please help me.
Thanks a lot in advance.
Regards
Dipak
07-11-2011 08:37 PM
Hi Dipak,
There is no debug command for shun, wat he suggested wasd takong logs friom the ASA at debug level:
To enable it you need the command:
logging buffered 7
logging monitor 7
or
logging trap 7
level 7 is for debugging
here is a doc:
http://www.cisco.com/en/US/customer/docs/security/asa/asa82/system/message/logsevp.html
and
Hope this helps
Thanks,
Varun
07-11-2011 10:30 PM
Hi Varun,
I have enabled debugging on ASA. It's only showing the below mentioned message :
Shunned packet: 172.21.x.x ==> 10.40.x.x on interface DMZ
Please suggest.
07-11-2011 11:00 PM
Hi Dipak,
If you want to see what all Ip addresses are getting shunned on the firewall, use the command "show shun", now the IP addresses that should not be shunned, add a "no" in front of them and save the changes, those ip's would be removed from the shun list.
http://www.cisco.com/en/US/customer/docs/security/asa/asa82/command/reference/s8.html#wp1525925
Hope this helps
Thanks,
Varun
07-12-2011 10:54 PM
Hi,
I have tried with "no shun ip address" command with saving the changes, but after sometime it's again getting shunned.
Is there any other way ? Please suggest.
Regards
Dipak
07-13-2011 12:08 AM
Hi Dipak,
I am a bit confused about your issue here:
Are you not able to access a server and the reason taht you see in the logs is because it has been shunned ?? You have tried removing the shun command but after sometime does comeback on the firewall????
I am asking you this because the access to the server could be blocked due to someother reason as well, do you always see the ip of the server in the shunned list.
provide me the following outputs:
ip of the server
show shun
the logs that you get when you access the server.
Thanks,
Varun
07-13-2011 01:55 AM
Hi,
We are able to access and ping the server, before shun. As soon as it get shunned, we are neither able to ping nor access to the server. After removing with no shun command, then we are able to access and ping the server. After sometime the server ip automatically get shun. Yes, the server ip is always get shunned. The server is our dns server.
IP of the server : 172.21.10.13
Show shun : shun (DMZ) 172.21.10.13 0.0.0.0 0 0 0
The logs that you get when you access the server: Built outbound TCP connection 197491880 for DMZ:172.21.10.13/22 (172.15.22/22) to INSIDE:172.21.15.12 (172.21.15.12/1122)
Regards
Dipak
07-14-2011 08:40 AM
Hi,
Please help me to solve this issue.
Thanks a lot in advance.
Regards
Dipak
07-14-2011 09:09 AM
Hi Dipak,
Automatic shunning can happen on ASAs because of 2 reasons:
1) You have scanning threat-detection enabled iwth shunning on the ASA.
2) There is an IPS device configured on your network for blocking which adds this shun on the ASA.
So my questions are:
1) Please post the output of show run all threat-detection from the ASA.
2) Do you have a Cisco IPS in your network?
Regards,
Prapanch
07-15-2011 12:06 AM
Hi,
sh run all threat-detection (output)
threat-detection rate dos-drop rate-interval 600 average-rate 100 burst-rate 400
threat-detection rate dos-drop rate-interval 3600 average-rate 80 burst-rate 320
threat-detection rate bad-packet-drop rate-interval 600 average-rate 100 burst-rate 400
threat-detection rate bad-packet-drop rate-interval 3600 average-rate 80 burst-rate 320
threat-detection rate acl-drop rate-interval 600 average-rate 400 burst-rate 800
threat-detection rate acl-drop rate-interval 3600 average-rate 320 burst-rate 640
threat-detection rate conn-limit-drop rate-interval 600 average-rate 100 burst-rate 400
threat-detection rate conn-limit-drop rate-interval 3600 average-rate 80 burst-rate 320
threat-detection rate icmp-drop rate-interval 600 average-rate 100 burst-rate 400
threat-detection rate icmp-drop rate-interval 3600 average-rate 80 burst-rate 320
threat-detection rate scanning-threat rate-interval 600 average-rate 5 burst-rate 10
threat-detection rate scanning-threat rate-interval 3600 average-rate 4 burst-rate 8
threat-detection rate syn-attack rate-interval 600 average-rate 100 burst-rate 200
threat-detection rate syn-attack rate-interval 3600 average-rate 80 burst-rate 160
threat-detection rate fw-drop rate-interval 600 average-rate 400 burst-rate 1600
threat-detection rate fw-drop rate-interval 3600 average-rate 320 burst-rate 1280
threat-detection rate inspect-drop rate-interval 600 average-rate 400 burst-rate 1600
threat-detection rate inspect-drop rate-interval 3600 average-rate 320 burst-rate 1280
threat-detection rate interface-drop rate-interval 600 average-rate 2000 burst-rate 8000
threat-detection rate interface-drop rate-interval 3600 average-rate 1600 burst-rate 6400
threat-detection basic-threat
threat-detection scanning-threat shun duration 3600
threat-detection statistics host
threat-detection statistics port
threat-detection statistics protocol
threat-detection statistics access-list
no threat-detection statistics tcp-intercept
Yes, we have Cisco IPS in our network.
Please suggest.
Thanks a lot in advance.
Regards
Dipak
07-15-2011 12:33 AM
Hi Dipak,
We would need to verify it on the IPS as well as threat-detection as well:
For threat-detection you can use the "except" keyword to exclude your server.
threat-detection scanning-threat shun except ip-address 172.21.10.13 255.255.255.255
To check on IP, login to the IDM, and on the top go to monitoring------> Active hosts Block--------> There you can see if this server is being blocked by the IPS server.
If it is blocked by IPS, go to Configuration ----------> Blocking Properties -----------> Never block IP's.
Screenshot are attached.
Hope this helps.
Thanks,
Varun
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