cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
7277
Views
0
Helpful
2
Replies

ASA failover isnt working

mx
Level 1
Level 1

I am trying to get 2 ASA's to failover in the lab but Im not having any success:

kentasa1# sho fail

Failover On

Failover unit Primary

Failover LAN Interface: failover GigabitEthernet0/3.1 (Failed - No Switchover)

Unit Poll frequency 1 seconds, holdtime 15 seconds

Interface Poll frequency 5 seconds, holdtime 25 seconds

Interface Policy 1

Monitored Interfaces 3 of 250 maximum

failover replication http

Version: Ours 7.2(1), Mate Unknown

Last Failover at: 10:21:03 EST Sep 19 2006

This host: Primary - Active

Active time: 1126090 (sec)

slot 0: ASA5520 hw/sw rev (1.1/7.2(1)) status (Up Sys)

Interface management (10.0.10.10): Normal (Waiting)

Interface inside (10.254.0.2): No Link (Waiting)

Interface outside (206.67.136.3): No Link (Waiting)

Interface dmz (192.168.1.3): No Link (Not-Monitored)

Interface mtadmz (192.168.255.1): No Link (Not-Monitored)

slot 1: empty

Other host: Secondary - Failed

Active time: 0 (sec)

slot 0: empty

Interface management (0.0.0.0): Unknown (Waiting)

Interface inside (10.254.0.252): Unknown (Waiting)

Interface outside (206.67.136.253): Unknown (Waiting)

Interface dmz (192.168.1.253): Unknown (Not-Monitored)

Interface mtadmz (192.168.255.253): Unknown (Not-Monitored)

slot 1: empty

Stateful Failover Logical Update Statistics

Link : failover GigabitEthernet0/3.1 (Failed)

Stateful Obj xmit xerr rcv rerr

General 0 0 0 0

sys cmd 0 0 0 0

up time 0 0 0 0

RPC services 0 0 0 0

TCP conn 0 0 0 0

UDP conn 0 0 0 0

ARP tbl 0 0 0 0

Xlate_Timeout 0 0 0 0

VPN IKE upd 0 0 0 0

VPN IPSEC upd 0 0 0 0

VPN CTCP upd 0 0 0 0

VPN SDI upd 0 0 0 0

VPN DHCP upd 0 0 0 0

Logical Update Queue Information

Cur Max Total

Recv Q: 0 0 0

Xmit Q: 0 0 0

I went through the docs but I think Im doing everything right. Attached are the configs to see if I missed anything. Thank you!

Bob

1 Accepted Solution

Accepted Solutions

jshelmer
Level 1
Level 1

First off, it doesn't look the Failover Interface is up. It should look like:

Failover LAN Interface: FAILOVER GigabitEthernet0/3 (up)

Also, a sh int on your failover interface should show that it is up/up.

-Jon

View solution in original post

2 Replies 2

jshelmer
Level 1
Level 1

First off, it doesn't look the Failover Interface is up. It should look like:

Failover LAN Interface: FAILOVER GigabitEthernet0/3 (up)

Also, a sh int on your failover interface should show that it is up/up.

-Jon

UGH Youre right! Thank you!

as soon as I did a no shut, it all came to life.

Thank you much!

Review Cisco Networking products for a $25 gift card