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

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

PIX debug failover reference

Does anyone have a good reference for understanding the PIX debug fover commands? I'm currently looking for help with the "debug fover switch" where I'm seeing the error below:

fover_parse: Secondary: Switching to FAILED for reason 17.

1 ACCEPTED SOLUTION

Accepted Solutions
Silver

Re: PIX debug failover reference

Here ..

Number Description

0 No error

1 normal master

2 no fail over cable

3 no power detected from other side

4 unable to talk to the other side

5 interface failed at other side

6 do not see traffic count change

7 the otherside want me take over

8 fail reported by the other side

9 LAN FO interface failed at other side

10 because state check

11 set by the ioctl cmd

Addition Reason for switch to Standby

12 bad/incompleted config

13 ifc check, mate is healhier

14 the otherside want me standby

15 in failed state, can not be Active

16 switch to failed state

Reason for switch to failed

17 MATE_ASKED

18 MATE_BETTER

19 MY_IFCFAILED

20 MY_COMMFAILED

21 FOVER_UNKNOWN

I hope this table helps. In your case, Secondary failed because Primary asked Secondary to go in Failed state. We need to look into syslogs to find out the reason why Primary asked so.

Regards,

Vibhor.

1 REPLY
Silver

Re: PIX debug failover reference

Here ..

Number Description

0 No error

1 normal master

2 no fail over cable

3 no power detected from other side

4 unable to talk to the other side

5 interface failed at other side

6 do not see traffic count change

7 the otherside want me take over

8 fail reported by the other side

9 LAN FO interface failed at other side

10 because state check

11 set by the ioctl cmd

Addition Reason for switch to Standby

12 bad/incompleted config

13 ifc check, mate is healhier

14 the otherside want me standby

15 in failed state, can not be Active

16 switch to failed state

Reason for switch to failed

17 MATE_ASKED

18 MATE_BETTER

19 MY_IFCFAILED

20 MY_COMMFAILED

21 FOVER_UNKNOWN

I hope this table helps. In your case, Secondary failed because Primary asked Secondary to go in Failed state. We need to look into syslogs to find out the reason why Primary asked so.

Regards,

Vibhor.

361
Views
0
Helpful
1
Replies