These are primarily used for our internal developers.
They are counting the number fo each type of Object in memory.
Each signature is based off a kind of key.
For signatures with a single source address, but mutliple destination addresses then the key is the source address and a Src Object is created to analyze traffic for that signature. Example: Network Sweep
The opposite is trued for Dst Objects. Example: Flood
The Dual Objects is used by signatures which are basd on multiple connections between 2 machines. Example: Single Host Port Sweeps
The Quad Object is used when the signature is also based on connections to specific ports. Example: tftp download of the passwd file
There is also Stream Objects for signatures requiring TCP Streams for their analysis. Example: Most of the HTTP sigs.
These are not normally of concern to the user, until there is a problem and our engineering team requests the numbers. In general the higher the numbers, the more memory being consumed for storage of the Objects. Engineering uses these numbers to determine if customer problems may be related to memory.
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...