ASA Stateful Failover problem

Answered Question
Apr 29th, 2010

Dear Forum Community!

We have recently implemented ASA stateful failover between two ASA 5540 operating at two different location. Unfortunately, because of a temporary switch installation, the standby peer has one physical interface at speed 100-duplex full, while the primary device has all interface at speed 1000-duplex full.

Please refer to the output of the "show failover" command executed in the standby device below: the receive error counters shows that something is wrong with stateful HA.

Could anyone help me to find out, if the asymmetric interface speed could cause this symptom?

Thanks and BR


Budapest, Hungary

Stateful Failover Logical Update Statistics
        Link : ***** (up)
        Stateful Obj    xmit       xerr       rcv        rerr
        General         555244     0          696813995  65685015
        sys cmd         555244     0          555244     0
        up time         0          0          0          0
        RPC services    0          0          0          0
        TCP conn        0          0          199265403  56098066
        UDP conn        0          0          487869778  9492795
        ARP tbl         0          0          9121627    94154
        Xlate_Timeout   0          0          0          0
        VPN IKE upd     0          0          556        0
        VPN IPSEC upd   0          0          1132       0
        VPN CTCP upd    0          0          0          0
        VPN SDI upd     0          0          0          0
        VPN DHCP upd    0          0          0          0
        SIP Session     0          0          255        0

        Logical Update Queue Information
                        Cur     Max     Total
        Recv Q:         0       138     713534140
        Xmit Q:         0       1       555244

I have this problem too.
0 votes
Correct Answer by Jennifer Halim about 6 years 5 months ago

Good to hear that upgrade resolves the issue. Please kindly mark the question as answered. Thank you.

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Jennifer Halim Thu, 04/29/2010 - 14:38

You are right. Interface speed for the stateful failover link needs to be the same on both firewalls. It also needs to be the highest speed on your ASA, so the ASA that has the stateful interface down to 100, you would need to fix the interface so it's 1000, the same as the other ASA stateful interface speed.

Otherwise, you will be seeing what you are currently seeing, ie: receive error (rerr). The standby ASA can't receive the failover state information fast enough through the stateful link, hence you saw the received error.

Hope that answers your question.

Bela Mareczky Fri, 04/30/2010 - 02:07

Dear halijenn!

Thanks for Your reply, I think it helps to resolve the problem.

I have just double-checked the configuration: the outside interface of the primary ASA has a speed 100-duplex full state, because it is connected to a temporary device which is C2960 10/100 switch :-O Every other ports connect to gigabit switchport and have speed 1000-duplex full state, including gigabit 0/3 which serve as state and failover VLAN trunk.

Primary ASA:


Outside: speed 100/duplex full

Inside: speed 1000/duplex full

DMZ: speed 1000/duplex full

HA: speed 1000/duplex full

Secondary ASA:


Outside: speed 1000/duplex full
Inside: speed 1000/duplex full 
DMZ: speed 1000/duplex full
HA: speed 1000/duplex full

Do You think, the speed 100 state of the outside interface could also cause the errors?

Thanks in advance !

Regards, Belabacsi

Jennifer Halim Fri, 04/30/2010 - 06:41

Speed 100 on the outside interface is OK. However, I am concern about all the rerr that you are getting on the stateful failover link.

You might want to double check if the rerr errors are increasing. Also what version of ASA are you running?

Bela Mareczky Mon, 05/03/2010 - 00:18

Dear halijenn !

Thanks for Your reply, unfortunately the err counters are increasing... :-(

The ASA version information:

Cisco Adaptive Security Appliance Software Version 8.2(1)
Device Manager Version 6.2(5)

Hardware:   ASA5540, 1024 MB RAM, CPU Pentium 4 2000 MHz

Internal ATA Compact Flash, 256MB

Do You think, it can be a software bug?



Jennifer Halim Mon, 05/03/2010 - 03:50

Please check the "show interface" output for the stateful failover link/interface on both ASA firewall. You might also want to check the corresponding switch interfaces/ports. Possibly it could be faulty cable.

Don't think it's software bug at this stage. It's more looking like an interface issue.

Bela Mareczky Thu, 05/06/2010 - 02:59

Dear halijenn!

Thanks for the tips! Unfortunataly, the switch interfaces connecting to the ASA seem to be OK, I hava fount no CRC / errors counting.

We have a scheduled maintenance window on Saturday, when we plan to force-switchover the ASA HA and reboot the device...we expect some posotive results :-) I 'll inform You about the err counter status.

Thanks and BR


Bela Mareczky Thu, 05/13/2010 - 07:16

Dear halijenn!

After ASA HA switchover and reload both devices, the err counters stop counting   The software version and HA configuration are the same as before, however we successfully migrated all ASA interfaces to gigabit speed, so all ASA interfaces (of both devices) operating at 1000 / full duplex.

It is an interesting story after the first reboot, everything seemed to be OK...suddenly the ASA ASDM service crashed, the "show asdm session" command output stated that, we reached the permitted concurrent ASDM session limit. I had one active connection from IP address. Trying to  disconnect the "stucked" sessions, but no luck...

firewall# show asdm sessions
0 mbela_172.16.129.221
1 mbela_172.16.129.221
2 mbela_172.16.129.221
3 mbela_172.16.129.221
4 mbela_172.16.129.221


firewall# asdm disconnect 0

firewall# asdm disconnect 1

firewall# asdm disconnect 2

firewall# asdm disconnect 3

firewall# asdm disconnect 4

firewall# show asdm sessions
0 mbela_172.16.129.221
1 mbela_172.16.129.221
2 mbela_172.16.129.221
3 mbela_172.16.129.221
4 mbela_172.16.129.221


Suddenly, I lost the SSH connection and the device rebooted. Finally,this reboot solved the issue.

It is annoying, because we don't know what was the real cause of the problem...

Thanks for Your help!



Correct Answer
Jennifer Halim Fri, 05/14/2010 - 02:06

Good to hear that upgrade resolves the issue. Please kindly mark the question as answered. Thank you.

Bela Mareczky Tue, 05/18/2010 - 05:54

Dear halijenn!

Thanks for Your help!

We have not upgraded the ASA software, the HA configuration and software version are the same as before...only the 2nd reboot solves the error counter issue

Unfortunately, we don't know the cause of the problem...




This Discussion

Related Content