Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
New Member

Lost Failover communications

Hi

I have in logg periodically this messages

105005: (Secondary) Lost Failover communications with mate on interface 0

105008: (Secondary) Testing Interface 0

105009: (Secondary) Testing on interface 0 Passed

105005: (Secondary) Lost Failover communications with mate on interface 0

105008: (Secondary) Testing Interface 0

105009: (Secondary) Testing on interface 0 Passed

105005: (Secondary) Lost Failover communications with mate on interface 0

105008: (Secondary) Testing Interface 0

105009: (Secondary) Testing on interface 0 Passed

105005: (Secondary) Lost Failover communications with mate on interface 0

105008: (Secondary) Testing Interface 0

105009: (Secondary) Testing on interface 0 Passed

105005: (Secondary) Lost Failover communications with mate on interface 0

105008: (Secondary) Testing Interface 0

105009: (Secondary) Testing on interface 0 Passed

and interfaces is:

interface gb-ethernet0 1000full

interface gb-ethernet1 1000full

interface gb-ethernet2 1000full

interface ethernet0 auto shutdown

interface ethernet1 auto shutdown

which is the interface 0 ?

and interface outside and inside is connected to catalyst 6509, failover is directly connected to other PIX.

Where can by problem?

Thanx

Peter

2 REPLIES
New Member

Re: Lost Failover communications

How is the primary and secondary connected, via crossover cable, switch, hub? Has the primary or secondary rebooted directly before these errors appeared? Will need a "show failover" and "show interface" output. Also, are you running PIX 535?

New Member

Re: Lost Failover communications

Hi,

Interface 0 will always be the first one listed when you use "show interface". Looks like yours would be gb-ethernet0.

You might check on your Cat6509 and make sure you have Spanning Tree PortFast enabled on the ports where the PIX interfaces connect. Otherwise, those ports could be going through the normal progression of Spanning Tree Protocol states where no traffic will pass for at least 30 seconds.

Lastly, it would be interesting to see some timestamps on your syslog messages ("logging timestamp", only for syslog servers & not for logging buffered). That might show how long interface 0 was not communicating during these events.

Hope this helps,

DaveH

216
Views
0
Helpful
2
Replies
CreatePlease to create content