cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
896
Views
0
Helpful
3
Replies

Failover error standby failure

upendargoud
Level 1
Level 1

When i am trying to configure failvoer i am getting following error stating secondary state as failed. Please let me know where i went wrong

DR-INT-FW# sh failover

Failover On

Failover unit Primary

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 2 of 160 maximum

Version: Ours 8.2(5), Mate 8.2(5)

Last Failover at: 17:48:09 UTC Jul 17 2012

        This host: Primary - Active

                Active time: 10322 (sec)

                slot 0: ASA5520 hw/sw rev (2.0/8.2(5)) status (Up Sys)

                  Interface outside (10.230.40.18): Normal (Waiting)

                  Interface inside (10.230.20.254): Normal (Waiting)

                slot 1: empty

        Other host: Secondary - Failed

                Active time: 3134 (sec)

                slot 0: ASA5520 hw/sw rev (2.0/8.2(5)) status (Up Sys)

                  Interface outside (0.0.0.0): No Link (Waiting)

                  Interface inside (0.0.0.0): No Link (Waiting)

                slot 1: empty

Stateful Failover Logical Update Statistics

        Link : state GigabitEthernet0/3 (Failed)

        Stateful Obj    xmit       xerr       rcv        rerr

DR-INT-FW#  sh failover state

               State          Last Failure Reason      Date/Time

This host  -   Primary

               Active         None

Other host -   Secondary

               Failed         Ifc Failure              19:15:15 UTC Jul 17 2012

                              outside: No Link

                              inside: No Link

3 Replies 3

mulhollandm
Level 1
Level 1

marupakula

have you configured the interface statements on our secondary box and are all the interfaces patched correctly?

can you post the interface and failover configurations from both boxes

a show interface might also help

Thanks mulhollandm for your reply.. as sought, below is show interface output.

Interface GigabitEthernet0/2 "FAILOVER", is up, line protocol is up

  Hardware is i82546GB rev03, BW 1000 Mbps, DLY 10 usec

        Full-Duplex(Full-duplex), 1000 Mbps(1000 Mbps)

        Input flow control is unsupported, output flow control is off

        Description: LAN Failover Interface

        MAC address 0019.e8c9.9c8e, MTU 1500

        IP address 192.168.1.1, subnet mask 255.255.255.0

        12809 packets input, 1160072 bytes, 0 no buffer

        Received 5 broadcasts, 0 runts, 0 giants

        0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort

        0 pause input, 0 resume input

        0 L2 decode drops

        12441 packets output, 1175260 bytes, 0 underruns

        0 pause output, 0 resume output

        0 output errors, 0 collisions, 2 interface resets

        0 late collisions, 0 deferred

        0 input reset drops, 0 output reset drops, 0 tx hangs

        input queue (blocks free curr/low): hardware (255/253)

        output queue (blocks free curr/low): hardware (255/249)

  Traffic Statistics for "FAILOVER":

        12809 packets input, 929306 bytes

        12457 packets output, 951558 bytes

        0 packets dropped

      1 minute input rate 1 pkts/sec,  106 bytes/sec

      1 minute output rate 1 pkts/sec,  111 bytes/sec

      1 minute drop rate, 0 pkts/sec

      5 minute input rate 1 pkts/sec,  105 bytes/sec

      5 minute output rate 1 pkts/sec,  110 bytes/sec

      5 minute drop rate, 0 pkts/sec

Interface GigabitEthernet0/3 "state", is up, line protocol is up

  Hardware is i82546GB rev03, BW 1000 Mbps, DLY 10 usec

        Auto-Duplex(Full-duplex), Auto-Speed(1000 Mbps)

        Input flow control is unsupported, output flow control is off

        Description: STATE Failover Interface

        MAC address 0019.e8c9.9c8f, MTU 1500

        IP address 192.168.10.1, subnet mask 255.255.255.0

        9613 packets input, 669364 bytes, 0 no buffer

        Received 0 broadcasts, 0 runts, 0 giants

        0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort

        0 pause input, 0 resume input

        0 L2 decode drops

        15394 packets output, 4609596 bytes, 0 underruns

        0 pause output, 0 resume output

        0 output errors, 0 collisions, 3 interface resets

        0 late collisions, 0 deferred

        0 input reset drops, 0 output reset drops, 0 tx hangs

        input queue (blocks free curr/low): hardware (255/249)

        output queue (blocks free curr/low): hardware (255/238)

  Traffic Statistics for "state":

        9613 packets input, 394514 bytes

        15394 packets output, 4231004 bytes

        0 packets dropped

      1 minute input rate 1 pkts/sec,  46 bytes/sec

      1 minute output rate 1 pkts/sec,  527 bytes/sec

      1 minute drop rate, 0 pkts/sec

      5 minute input rate 1 pkts/sec,  46 bytes/sec

      5 minute output rate 1 pkts/sec,  502 bytes/sec

      5 minute drop rate, 0 pkts/sec

Hi Bro

Can you kindly paste your Cisco ASA FW latest show run failover command here? Besides that, please do provide the output for debug fover rx and debug fover tx as well. This problem is easy. It's either you’ve the wrong configuration or your physical setup is wrong. Before I move into the physical setup, let’s do this configuration verification for now. No worries, I'll help you :-)

Warm regards,
Ramraj Sivagnanam Sivajanam
Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:

Review Cisco Networking products for a $25 gift card