I would like to ask if this is a known issue and if there is a remedy:
When issuing a "sh local-host <ip-address>" I often get an increasing count of connections for this address, whereas a "sh conn local <ip-address>" and a snmp query with .188.8.131.52.184.108.40.206.6.1.9 both show a different (and much lower) count.
Unfortunately, the pretended count of active connections "sh local-host <ip-address>" seems to cause trouble so that new connections are declined and I have to "clear local-host <ip-address>".
So my questions are:
1. Why is there a different count with "sh local-host <ip-address>" and "sh conn local <ip-address>" (or SNMP query)?
2. How may I prevent this connection congestion?
(Yes, we have static connection limits, but this is curing the sympton not the root of wrong accumulated connections.)
It's possible that the counters are not synchronized correctly if the network processors (NPs) are receiving too much traffic and are oversubscribed. If you see the thresholds in 'show np block' increasing, this could potentially cause these symptoms. The solution would be to move some of the load off of the FWSM to prevent oversubscription of the NPs.
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...