05-22-2008 04:16 AM - edited 03-11-2019 05:48 AM
Hi,
While configuring the cable based failover, i selected one of the data interface to be also failover link
command i used was failover link interface2. The ip address is already assigned to interface 2. This was on the primary unit only. on the secondary unit just enabled the command failover. but
when used the command show failover i see the below
Failover On
Cable status: xxxx
Failover unit Secondary
Failover LAN Interface: N/A - Serial-based failover enabled
Unit Poll frequency 15 seconds, holdtime 45 seconds
Interface Poll frequency 5 seconds, holdtime 25 seconds
Interface Policy 1
Monitored Interfaces 4 of 250 maximum
Version: Ours 7.2(2), Mate xxx
Last Failover at: 00:00:38 UTC Jan 1 1xxxx
This host: Secondary - Active
Active time: 62400 (sec)
Interface interface2 (xxxxxxx): Normal (Waiting)
Interface ixxxx (xxxxxx): Normal (Waiting)
Interface wexxxx (xxxxx): Normal (Waiting)
Interface daxxxxx (xxxx): Normal (Waiting)
Other host: Primary - Not Detected
Active time: 0 (sec)
Interface interface2 (xxxxxxxxx): Unknown (Waiting)
Interface ixxxx (xxxxxxxxxx): Unknown (Waiting)
Interface wexxxxx (xxxxxxxxx): Unknown (Waiting)
Interface daxxxxx (1xxxxxxxxxx): Unknown (Waiting)
Stateful Failover Logical Update Statistics
Link : Unconfigured.
Its says link unconfigured on the secondary unit. Primay Pix crashed so we have to get it back online. why the link is shown unconfigured?
Also when primary is bought up again, if i dont copy the entier config from TFTP and just configure interfaces with failover commands, the secondary should see primary up . then if i do write standy by will it copy the config from secondary to primary unit? once done i want to force primary to be active. but with the stateful link shown unconfigured on secondary, i m not sure how will stateful failover work. can you guys help here
Thanks
05-22-2008 07:21 AM
below is a cut and past of one of my failver 535's:
interface GigabitEthernet3
description STATE Failover Interface
!
failover
failover polltime unit 1 holdtime 3
failover polltime interface 3
failover replication http
failover timeout 0:00:03
failover link failover GigabitEthernet3
failover interface ip failover x.x.x.x 255.255.255.252 standby x.x.x.x
xxxxxx# show failover
Failover On
Cable status: Normal
Failover unit Primary
Failover LAN Interface: N/A - Serial-based failover enabled
Unit Poll frequency 1 seconds, holdtime 3 seconds
Interface Poll frequency 3 seconds
Interface Policy 1
Monitored Interfaces 6 of 250 maximum
failover replication http
Last Failover at: 18:00:00 UTC Jan 19 2008
This host: Primary - Active
Active time: 10704935 (sec)
Interface outside (x.x.x.x): Normal
Interface inside (x.x.x.x): Normal
Interface 1 (x.x.x.x): Normal
Interface 2 (x.x.x.x): Normal
Interface 3 (x.x.x.x): Normal
Interface 4 (x.x.x.x): Normal
Other host: Secondary - Standby Ready
Active time: 0 (sec)
Interface outside (x.x.x.x): Normal
Interface inside (x.x.x.x): Normal
Interface 1 (x.x.x.x): Normal
Interface 2 (x.x.x.x): Normal
Interface 3 (x.x.x.x): Normal
Interface 4 (x.x.x.x): Normal
Stateful Failover Logical Update Statistics
Link : failover GigabitEthernet3 (up)
Stateful Obj xmit xerr rcv rerr
General 1501926632 0 1392457 0
sys cmd 1392457 0 1392457 0
up time 0 0 0 0
RPC services 0 0 0 0
TCP conn 1059123901 0 0 0
UDP conn 440179664 0 0 0
ARP tbl 1230610 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 3 12097244
Xmit Q: 0 4 1512636085
configure, wr mem and power down. then bring the primary up 5 seconds before the secondary!
HTH.
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: