Easy way to locate what's 'eating' the outside interface bandwidth?
Via the CLI what is the best way to see what is eating our bandwidth on the outside interface? I'm going to set up Netflow shortly, but in the meantime can the CLI quickly show this as I don't have access to the ASDM as I know this can show it.
Not sure I can capture the traffic and use wireshark to view?
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...