No the ASA is not using M0/0 but Inside for management... But now when I read this again I see that I need to use the M0/0 for CX. I misunderstood that one, I thought that I could use Inside but it actually say M0/0 for ASA CX and Inside for ASA.
Easy to miss :-)
If you have only one inside network, then you cannot also have a separate management network. In this case, you can manage the ASA from the inside interface instead of the Management 0/0 interface. If you remove the ASA-configured name from the Management 0/0 interface, you can still configure the ASA CX IP address for that interface. Because the ASA CX module is essentially a separate device from the ASA, you can configure the ASA CX management address to be on the same network as the inside interface.
Yes, that is confusing at first. Especially so since it contrasts from the behavior of the ASA. It's sort of a hybrid of the behavior of a CSC module (always use a dedicated hardware port) and that of a base ASA (Management port available but use is optional).
It took me three readings of the setup document to follow the language and I had the benefit of a deep dive training with hands-on lab to drill the need into my head. :)
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...