I run a LOT of "All Matching Sessions, Custom Column" queries, since they let me more quickly see the Host Pairs involved with an incident (and/or to see ALL of the host pairs matching certain criteria)
Anyways, there are two options for having a column on Destination Address. The first is the Dest. Address all by itself, so if you wanted Port and/or Protocol you'd have to explicitly request them. The other option is a single field "Destination Address, Port, and Protocol" (e.g. the results are grouped together.)
My questions is: which field type is more efficient from a MARS SQL query perspective? In other words, is it faster to split the fields out (e.g. one field for Destination Address, another field for Destination Port) or is it faster to have them a single, combined field.
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...
[toc:faq]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 and UDP are I...