I am looking at my PIX interface counters to see if I have any problems on the interfaces. I notice that some of the interfaces have values in the No buffer, Overrun, Underrun and Dropped packets.
I assume the dropped packets are those dropped due to the firewall rules.
With the no buffer, overrun and underrun I know these are all to do with the PIX and the Interfaces performance. Can someone please explain what is causing these counters and therefore what problem there may be. An example from my worst interface is copied below.
Result of the command: "sh int g0"
Interface GigabitEthernet0 "", is up, line protocol is up
Hardware is i82543 rev02, BW 1000 Mbps
(Full-duplex), 1000 Mbps(1000 Mbps)
Available but not configured via nameif
MAC address 000e.0c2b.b71a, MTU not set
IP address unassigned
65487795 packets input, 18953217272 bytes, 191025 no buffer
I don't find any error in the interface. The counters are increasing because of normal traffic flow. For examle "packets input" counter will increase when a new packet is received on the interface. All the counters that indicate any error are showing 0. For example "input errors" counter will increase if a packet is received on an interface but it is unreadable, likewise the "CRC" counter will increase if the packet does not pass the CRC check.
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...