Task 1.4 - failover timers

Hi,

I had a problem with the ASA4 and its group 2 which supossed to be the active one. When I forced the failover after few seconds I saw 'failed' on one of interfaces:


Output from ASA4:

asa34/stby# failover active group 2

...
asa34/act# sh failover
Failover On
Failover unit Secondary
Failover LAN Interface: FAILOVER GigabitEthernet0/2 (up)
Unit Poll frequency 1 seconds, holdtime 15 seconds
Interface Poll frequency 5 seconds, holdtime 25 seconds
Interface Policy 1
Monitored Interfaces 4 of 114 maximum
Version: Ours 8.6(1)10, Mate 8.6(1)10
Group 1 last failover at: 22:27:34 UTC Mar 30 2015
Group 2 last failover at: 22:27:52 UTC Mar 30 2015

  This host:    Secondary
  Group 1       State:          Active
                Active time:    31 (sec)
  Group 2       State:          Standby Ready
                Active time:    536 (sec)

                slot 0: ASA5515 hw/sw rev (1.0/8.6(1)10) status (Up Sys)
                  VLAN13 Interface outside (130.1.13.17): Failed (Waiting)
                  VLAN13 Interface inside (130.1.13.17): Normal (Monitored)
                  VLAN16 Interface outside (130.1.16.18): Normal (Waiting)
                  VLAN16 Interface inside (130.1.16.18): Normal (Waiting)
                slot 1: IPS5515 hw/sw rev (N/A/) status (Unresponsive/Up)

  Other host:   Primary
  Group 1       State:          Standby Ready
                Active time:    3264 (sec)
  Group 2       State:          Active
                Active time:    2761 (sec)

                slot 0: ASA5515 hw/sw rev (1.0/8.6(1)10) status (Up Sys)
                  VLAN13 Interface outside (130.1.13.17): Normal (Waiting)
                  VLAN13 Interface inside (130.1.13.17): Normal (Waiting)
                  VLAN16 Interface outside (130.1.16.17): Normal (Waiting)
                  VLAN16 Interface inside (130.1.16.17): Normal (Waiting)
                slot 1: IPS5515 hw/sw rev (N/A/) status (Unresponsive/Up)

Stateful Failover Logical Update Statistics
        Link : Unconfigured.

asa34/stby#



Next time:

asa34/stby# failover active group 2
...
asa34/stby# sh failover
Failover On
Failover unit Secondary
Failover LAN Interface: FAILOVER GigabitEthernet0/2 (up)
Unit Poll frequency 1 seconds, holdtime 15 seconds
Interface Poll frequency 5 seconds, holdtime 25 seconds
Interface Policy 1
Monitored Interfaces 4 of 114 maximum
Version: Ours 8.6(1)10, Mate 8.6(1)10
Group 1 last failover at: 22:28:07 UTC Mar 30 2015
Group 2 last failover at: 22:31:27 UTC Mar 30 2015

  This host:    Secondary
  Group 1       State:          Standby Ready
                Active time:    33 (sec)
  Group 2       State:          Failed
                Active time:    573 (sec)

                slot 0: ASA5515 hw/sw rev (1.0/8.6(1)10) status (Up Sys)
                  VLAN13 Interface outside (130.1.13.18): Normal (Monitored)
                  VLAN13 Interface inside (130.1.13.18): Normal (Monitored)
                  VLAN16 Interface outside (130.1.16.18): Failed (Waiting)
                  VLAN16 Interface inside (130.1.16.18): Normal (Waiting)
                slot 1: IPS5515 hw/sw rev (N/A/) status (Unresponsive/Up)

  Other host:   Primary
  Group 1       State:          Active
                Active time:    3465 (sec)
  Group 2       State:          Active
                Active time:    2926 (sec)

                slot 0: ASA5515 hw/sw rev (1.0/8.6(1)10) status (Up Sys)
                  VLAN13 Interface outside (130.1.13.17): Normal (Monitored)
                  VLAN13 Interface inside (130.1.13.17): Normal (Monitored)
                  VLAN16 Interface outside (130.1.16.17): Normal (Waiting)
                  VLAN16 Interface inside (130.1.16.17): Normal (Waiting)
                slot 1: IPS5515 hw/sw rev (N/A/) status (Unresponsive/Up)

Stateful Failover Logical Update Statistics
        Link : Unconfigured.

asa34/stby#


When the group was standby I saw the status 'normal' on all interfaces:

asa34/stby# sh failover
Failover On
Failover unit Secondary
Failover LAN Interface: FAILOVER GigabitEthernet0/2 (up)
Unit Poll frequency 1 seconds, holdtime 15 seconds
Interface Poll frequency 5 seconds, holdtime 25 seconds
Interface Policy 1
Monitored Interfaces 4 of 114 maximum
Version: Ours 8.6(1)10, Mate 8.6(1)10
Group 1 last failover at: 22:28:07 UTC Mar 30 2015
Group 2 last failover at: 22:31:27 UTC Mar 30 2015

  This host:    Secondary
  Group 1       State:          Standby Ready
                Active time:    33 (sec)
  Group 2       State:          Standby Ready
                Active time:    573 (sec)

                slot 0: ASA5515 hw/sw rev (1.0/8.6(1)10) status (Up Sys)
                  VLAN13 Interface outside (130.1.13.18): Normal (Monitored)
                  VLAN13 Interface inside (130.1.13.18): Normal (Monitored)
                  VLAN16 Interface outside (130.1.16.18): Normal (Monitored)
                  VLAN16 Interface inside (130.1.16.18): Normal (Monitored)
                slot 1: IPS5515 hw/sw rev (N/A/) status (Unresponsive/Up)

  Other host:   Primary
  Group 1       State:          Active
                Active time:    3617 (sec)
  Group 2       State:          Active
                Active time:    3078 (sec)

                slot 0: ASA5515 hw/sw rev (1.0/8.6(1)10) status (Up Sys)
                  VLAN13 Interface outside (130.1.13.17): Normal (Monitored)
                  VLAN13 Interface inside (130.1.13.17): Normal (Monitored)
                  VLAN16 Interface outside (130.1.16.17): Normal (Monitored)
                  VLAN16 Interface inside (130.1.16.17): Normal (Monitored)
                slot 1: IPS5515 hw/sw rev (N/A/) status (Unresponsive/Up)

Stateful Failover Logical Update Statistics
        Link : Unconfigured.

asa34/stby#


Once I changed default timers to :

failover group 1 (and 2)
polltime interface 15 holdtime 75

the ASA4 kept their active state for group 2.

Did you find similar issue on others racks (my is scrack1) with the default timers?

regards
Hubert

Comments

  • Hi,


    If it worked and stopped working without you changing anything but who’s active, clearly looks like a bug. Reload should fix.


    Regards,

    Cristian.

Sign In or Register to comment.