I get these 402101 errors every few days. The duration of the messages getting logged is about 10 minutes. When this occurs, one of my remote sites that is connected to this firewall via the VPN (Another PIX) "loses" connectivity to this site where...
Hi,I wanted to know what are some of the most common PIX syslog messages that folks omit from having logged (i.e. no logging message xxxxxx).Is it common to get rid of 106011?Let me know.Thanks,Chris
I know that there was a problem with Cisco PIX and duplicate e-mail messages being received on an Exchange server.There was a Cisco Caveat article, does anyone know what it is?I know that the fix for the caveat was to simply upgrade the IOS to 6.2(3)...
My syslog showed a 105005 then 105008 then 105009 message.I logged into the pix and did a "show fail" and everything looks fine except for one of the interfaces on the other host:Interface outside (my ip address here): TestingIt never changes from te...
Well it is strange. These vpn tunnels have been working fine for a good while now.It only happens about 1 time a week, and the duration of the outage is only for about 5 or 10 minutes. During that time period, I see the 402101 errors.The site that ...
Thanks, but I did already see this on CCO. What I was looking for was a "real life" user experience related answer. I do understand the "logic" behind the errors, but not sure what might cause a VPN that has been working fine for over 3 years to st...
I appreciate you taking the time to answer.The network isn't new...actually about 3 years old...and yes, I have already a while ago actually, blocked logging of certain messages. It's just a couple of my offices exist in Asia, and you could imagine ...
That is a good point. I make a habit to look at the syslogs everyday.If I don't omit things, the logs are well over 1MB in size....which can be ridiculous to look at everyday (i.e. over 1MB of text).Do you, from your experience gather that sysadmins...
A 'Cisco TAC' engineer identified the caveat...so I am not dreaming this up.It doesn't happen to everyone....and I never said I was running 6.1.2 at the time either...so 6.1.2 probably doesn't have the problem...:^)-Chris
