Guest

Preview Tool

Cisco Bug: CSCvt37745 - Traceback while secondary reverting from active to standby

Last Modified

May 12, 2020

Products (1)

  • Cisco ASA 5500-X Series Firewalls

Known Affected Releases

9.12(2.4) 99.15(1.106)

Description (partial)

Symptom:
Secondary device traceback and reload while reverting from active to standby due to a comm failure while on a deployment with the following output from FMC transcript

========= INFRASTRUCTURE MESSAGES =========
This is a slave/ha standby device, rejecting deployment

Conditions:
change roles of HA setup while ongoing deployment
is this case the traceback happen due to a connection failure in between HA pairs

*(Difference time zones are noted)

Firepower-module1 up 47 days 6 hours
failover cluster up 1 year 107 days

14:37:53 UTC Feb 20 2020
Standby Ready              Just Active                HELLO not heard from mate

14:37:53 UTC Feb 20 2020
Just Active                Active Drain               HELLO not heard from mate

14:37:53 UTC Feb 20 2020
Active Drain               Active Applying Config     HELLO not heard from mate

14:37:53 UTC Feb 20 2020
Active Applying Config     Active Config Applied      HELLO not heard from mate

14:37:53 UTC Feb 20 2020
Active Config Applied      Active                     HELLO not heard from mate

Firepower-module1 up 47 mins 38 secs 
failover cluster up 1 year 102 days


Other host -   Secondary
               Failed         Comm Failure             11:37:24 CLT Feb 20 2020

11:37:53 CLT Feb 20 2020
Standby Ready              Just Active                HELLO not heard from mate

11:37:53 CLT Feb 20 2020
Just Active                Active Drain               HELLO not heard from mate

11:37:53 CLT Feb 20 2020
Active Drain               Active Applying Config     HELLO not heard from mate

11:37:53 CLT Feb 20 2020
Active Applying Config     Active Config Applied      HELLO not heard from mate

11:37:53 CLT Feb 20 2020
Active Config Applied      Active                     HELLO not heard from mate
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.