Having major problems with our FWSM and its ability to end connections. Our used memory continues to climb higher and higher (as the conns build, 560,000+), traffic begins to NOT pass in and out of our interfaces. Because our timeout values are NOT the default by Cisco, this is our problem until the code fixes this...anyone else running into similar problems?
We changed our connection time and xlate time to 3hrs....yes, older code had the same problem. Memory begins to creep up day by day, and when we look at the connections "sh pc conn" at times we see 500,000+ connections...it is at this point when we start to see major problems w/traffic not passing thru our interfaces (we have 5 intf's at present).
Table of ContentsIntroductionVersion HistoryPossible Future
UpdatesDocuments PurposeNAT Operation in ASA 8.3+ SectionsRule Types
Network Object NATTwice NAT / Manual NATRule Types used per SectionNAT
Types used with Twice NAT / Manual NAT and Network Obje...
Table of Contents Introduction:This document describes details on how
NAT-T works. Background: ESP encrypts all critical information,
encapsulating the entire inner TCP/UDP datagram within an ESP header.
ESP is an IP protocol in the same sense that TCP an...