I have managed to find another bug which may be relevent in this situation.
CSCsr75501 Bug Details
FOVER:Standby MAC addr is improperly registered as Active MAC on Primary
After the customer changed configuration on FWSM/VLANs, the ARP entry was wrongly updated and fails to update with the proper mac address.
The secondary/standby is advertising the primary/active's MAC for the secondary/standby's interface. The primary/active is adding this MAC to his ARP table.
This issue has been observed on 3.1.x.
Further Problem Description:
When the ARP timeout is reached, it should update the ARP table with the correct address. However, the Secondary/Standby IP's MAC address is registered as the Active MAC. Because of that, the Primary/Secondary cannot communicate properly and the failover status on the Secondary is "failed".
But our main foucus is why we are not able to access the one of the contexts
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...