This is not normal, this indicates there is no synch between standby unit and active unit , the interfaces are not being monitor by the standby towards the active.
What you need to do is to make sure that stanby interfaces are indeed connected on the same vlans as your Active unit interfaces vlans, after you confirm this is fine in terms of vlans configurations on the switch, issue on the Primary unit first failover then after that issue the same command on the standby unit, this sequence will make stanby to sync with primary and pools is configuration as well as become standby.
Before you do all this above read this link first carefully so that you can get a picture of what needs to be done and cover every angle to ensure you meet all requirements for Active/Standby configurations.
i think "(Waiting)" is normal when you have no standby IP Address configured.
If you do not enter a failover IP address, the show failover command displays 0.0.0.0 for the IP address and interface monitoring remains in a waiting state. Refer to the show failover section of the Cisco Security Appliance Command Reference, Version 7.2 for more information about the different failover states.
I guess my concern is that when we had a Standby address configured on the "inside" interface it did not failover as expected when the network cable was pulled.
Could this be because of the Active/Active setting?
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...