04-10-2013 07:54 AM - edited 03-11-2019 06:26 PM
Hi all,
I have an Interface that is up/up but "show fail" reports "no link"
Any ideas on what the cause may be?
I am seeing input errors on the switch port this interface is connected to. Tried swapping the cable, but no change. I may have a hardware problem but curious if anyone has specific insight as to why I would see "no link" from "show fail"
PIX515E-01/pri/act# sh fail
Failover On
Cable status: Normal
Failover unit Primary
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 3 of 250 maximum
Version: Ours 7.2(3), Mate 7.2(3)
Last Failover at: 00:24:54 EDT Jul 6 2012
This host: Primary - Active
Active time: 32270310 (sec)
Interface outside (xxxxxxxx): Normal
Interface core (xxxxxxxxx): Normal
Interface testing (172.20.81.30): No Link (Not-Monitored)
Other host: Secondary - Standby Ready
Active time: 0 (sec)
Interface outside (xxxxxxxxx): Normal
Interface core (xxxxxxxxxxxxx): Normal
Interface testing (0.0.0.0): No Link (Not-Monitored)
PIX515E-01/pri/act# sh int eth3
Interface Ethernet3 "testing", is up, line protocol is up
Hardware is i82559, BW 100 Mbps
Auto-Duplex(Full-duplex), Auto-Speed(100 Mbps)
MAC address 000d.8810.1585, MTU 1500
IP address 172.20.81.30, subnet mask 255.255.255.0
0 packets input, 0 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 L2 decode drops
91 packets output, 6074 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets
0 babbles, 0 late collisions, 0 deferred
0 lost carrier, 0 no carrier
input queue (curr/max packets): hardware (0/0) software (0/0)
output queue (curr/max packets): hardware (0/1) software (0/1)
Traffic Statistics for "testing":
0 packets input, 0 bytes
79 packets output, 2572 bytes
0 packets dropped
1 minute input rate 0 pkts/sec, 0 bytes/sec
1 minute output rate 0 pkts/sec, 0 bytes/sec
1 minute drop rate, 0 pkts/sec
5 minute input rate 0 pkts/sec, 0 bytes/sec
5 minute output rate 0 pkts/sec, 0 bytes/sec
5 minute drop rate, 0 pkts/sec
04-10-2013 08:30 AM
Could it be that you don't have a standby IP address configured?
How does the sh int eth3 looks on the standby firewall?
04-10-2013 08:33 AM
That has not been a problem in the past.
I have ran active/standby pairs where just 1 side had an IP.
04-10-2013 09:40 AM
Hello,
This would happen when there is a problem with connectivity between the boxes, in this case the timeout threshold for the hello packets expired ( it could because of the directly connected switch interface going down or even it's own interface)
It is expected that failover gets triggered here.
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: