topic Re: PIX debug failover reference in Network Security https://community.cisco.com/t5/network-security/pix-debug-failover-reference/m-p/621814#M1025483 <HTML><HEAD></HEAD><BODY><P>Here ..</P><P></P><P></P><P>Number Description</P><P></P><P>0 No error</P><P>1 normal master</P><P>2 no fail over cable</P><P>3 no power detected from other side</P><P>4 unable to talk to the other side</P><P>5 interface failed at other side</P><P>6 do not see traffic count change</P><P>7 the otherside want me take over</P><P>8 fail reported by the other side</P><P>9 LAN FO interface failed at other side</P><P>10 because state check</P><P>11 set by the ioctl cmd</P><P></P><P> Addition Reason for switch to Standby</P><P></P><P>12 bad/incompleted config</P><P>13 ifc check, mate is healhier</P><P>14 the otherside want me standby</P><P>15 in failed state, can not be Active</P><P>16 switch to failed state</P><P></P><P> Reason for switch to failed</P><P></P><P>17 MATE_ASKED </P><P>18 MATE_BETTER </P><P>19 MY_IFCFAILED </P><P>20 MY_COMMFAILED </P><P>21 FOVER_UNKNOWN </P><P></P><P>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.</P><P></P><P>Regards,</P><P>Vibhor.</P></BODY></HTML> Tue, 20 Feb 2007 17:23:37 GMT vitripat 2007-02-20T17:23:37Z PIX debug failover reference https://community.cisco.com/t5/network-security/pix-debug-failover-reference/m-p/621813#M1025482 <P>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:</P><P></P><P> fover_parse: Secondary: Switching to FAILED for reason 17.</P> Mon, 11 Mar 2019 09:35:56 GMT https://community.cisco.com/t5/network-security/pix-debug-failover-reference/m-p/621813#M1025482 scottvivian 2019-03-11T09:35:56Z Re: PIX debug failover reference https://community.cisco.com/t5/network-security/pix-debug-failover-reference/m-p/621814#M1025483 <HTML><HEAD></HEAD><BODY><P>Here ..</P><P></P><P></P><P>Number Description</P><P></P><P>0 No error</P><P>1 normal master</P><P>2 no fail over cable</P><P>3 no power detected from other side</P><P>4 unable to talk to the other side</P><P>5 interface failed at other side</P><P>6 do not see traffic count change</P><P>7 the otherside want me take over</P><P>8 fail reported by the other side</P><P>9 LAN FO interface failed at other side</P><P>10 because state check</P><P>11 set by the ioctl cmd</P><P></P><P> Addition Reason for switch to Standby</P><P></P><P>12 bad/incompleted config</P><P>13 ifc check, mate is healhier</P><P>14 the otherside want me standby</P><P>15 in failed state, can not be Active</P><P>16 switch to failed state</P><P></P><P> Reason for switch to failed</P><P></P><P>17 MATE_ASKED </P><P>18 MATE_BETTER </P><P>19 MY_IFCFAILED </P><P>20 MY_COMMFAILED </P><P>21 FOVER_UNKNOWN </P><P></P><P>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.</P><P></P><P>Regards,</P><P>Vibhor.</P></BODY></HTML> Tue, 20 Feb 2007 17:23:37 GMT https://community.cisco.com/t5/network-security/pix-debug-failover-reference/m-p/621814#M1025483 vitripat 2007-02-20T17:23:37Z