Secondary ASA successfully sync’d after re-attaching state/failover links to primary
Secondary ASA achieved secondary/Failed state
after re-attaching secondary ASA network links, it still remained in secondary/Failed state with “Ifc Failure admin management: Failed”.
TAC suggested “failover reset” on secondary, but it did not remedy the problem
tried reloading the secondary ASA, current state is the secondary will NOT sync with the primary
will disconnect secondary ASA network links to the backbone and leave thejfailover/state links to the primary connected
Posted Nov 09, 2025 - 13:03 EST
Completed
The scheduled maintenance has been completed.
Posted Nov 09, 2025 - 12:15 EST
In progress
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Posted Nov 09, 2025 - 11:15 EST
Scheduled
We will be performing maintenance on the DCB-ASA units on November 9th, 2025 - 1115h-1215h, to restore the secondary ASA unit back into service. No outage is expected as the primary active ASA unit should continue to operate normally while the secondary ASA unit is brought back into service.
Reference Change Request: CHG0031727
Posted Nov 04, 2025 - 14:35 EST
This scheduled maintenance affected: Enterprise Networks (Campus Backbone Network).