None. No errors, no traps. In the past, all I had to do is start up an OS and do 1 ping and everything would come back up. I have not verified it to that extent, but one office closes at 5pm, dropped at about 10:30pm, and came back up at 8am when they open. Obviously this causes an issue with my monitoring even though there may not be any user impact. I am considering setting a scheduled outage for 6pm-8am.
Sent from my iPhone Begin forwarded message: > From: Deny IP Any Any <[email protected]> > Date: January 19, 2011 8:58:02 AM EST > To: Marshall <[email protected]> > Subject: Re: Cisco ASA question > > What is the disconnect reason given? Idle timeout, or connection dropped? > > On Wed, Jan 19, 2011 at 6:39 AM, Marshall <[email protected]> wrote: >> I have several ASA's connecting through a VPN concentrator through DSL >> connections. It seems that exactly 5 hours after any traffic originating >> from behind the ASA has stopped, the ASA stops responding and disconnects >> from the concentrator. The device nor the DSL connection (outside IP, at >> least) go down. I had a similar issue with a Pix 501e at a client and wound >> up sticking an old XP laptop in a closet with just a constant ping to our >> Corp office going - worked well, but should not have been needed. I did not >> vary from the initial config except internal if ip, VPN settings, dhcp >> server settings, and recently SNMP. Is there a config I need to add or look >> for to change? TIA! >> >> Sent from my iPhone >> --------------------------------------------------------------------- >> Archive http://marc.info/?l=jaxlug-list&r=1&w=2 >> RSS Feed http://www.mail-archive.com/[email protected]/maillist.xml >> Unsubscribe [email protected] >> >> > > > > -- > deny ip any any (4393649193 matches)
