Feb 15 00:42:41: %SYS-5-CONFIG_I: Configured from console by n2net on vty1 (207.166.192.127) Feb 15 00:42:42: %LINK-3-UPDOWN: Interface Serial10/1/0/2:0, changed state to down Feb 15 00:47:39: %LINK-6-BERTSTATUS: Interface T3 10/1/0/2, BERT is completed Feb 15 00:47:40: %CONTROLLER-5-UPDOWN: Controller T3 10/1/0 T1 2, changed state to UP Feb 15 00:47:42: %LINK-3-UPDOWN: Interface Serial10/1/0/2:0, changed state to up Feb 15 00:47:43: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial10/1/0/2:0, changed state to up Feb 15 00:47:55: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial10/1/0/2:0, changed state to down Feb 15 00:49:57: %HA-3-SYNC_ERROR: CCB Playback error. Feb 15 00:49:57: %HA-5-SYNC_RETRY: Reloading standby and retrying sync operation (retry 1).
I must have missed this last night.. Feb 15 00:50:02: %SYS-5-CONFIG_I: Configured from console by n2net on vty1 (207.166.192.127) Feb 15 00:50:12: %RSP-3-SLAVECHANGE: Slave changed state from Slave to Non-participant Feb 15 00:50:12: %HA-5-MODE: Operating mode is hsa, configured mode is sso. Feb 15 00:50:15: %RSP-3-SLAVECHANGE: Slave changed state from Non-participant to Slave Feb 15 00:50:20: %RSP-3-SLAVECHANGE: Slave changed state from Slave to Non-participant Feb 15 00:50:22: %RSP-3-SLAVECHANGE: Slave changed state from Non-participant to Slave Feb 15 00:50:25: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial10/1/0/2:0, changed state to up Feb 15 00:50:27: %RSP-3-SLAVECHANGE: Slave changed state from Slave to Non-participant Feb 15 00:50:30: %RSP-3-SLAVECHANGE: Slave changed state from Non-participant to Slave Feb 15 00:50:57: %CLEAR-5-COUNTERS: Clear counter on interface Serial10/1/0/2:0 by n2net on vty1 (207.166.192.127) Feb 15 00:51:13: %BGP-5-ADJCHANGE: neighbor 207.166.197.25 Up Feb 15 00:51:16: %RSP-5-SLAVEUP: Slave changed to state Running, Buffer memory state : disabled Feb 15 00:51:16: %HA-5-NOTICE: Standby (slave) configured to run hw-module HA image "slot0:rsp-ik91sv-mz.122-25.S12.bin" Feb 15 00:51:17: %HA-5-NOTICE: Loading Standby (slave) image: "slot0:rsp-ik91sv-mz.122-25.S12.bin" Feb 15 00:51:23: %IF-4-BACKWARD_COUNTERS: Corrected for backward rxtx_errors counters (897 -> 896) on Serial10/1/0/20:0 Feb 15 00:52:51: %RSP-5-SLAVEUP: Slave changed to state Running, Buffer memory state : disabled Feb 15 00:52:51: %HA-5-MODE: Operating mode is hsa, configured mode is sso. Feb 15 00:53:18: %ISSU_PROCESS-7-DEBUG: Peer state is hot redundant Feb 15 00:53:23: %HA-5-SYNC_NOTICE: Standby has restarted. Feb 15 00:53:24: %HA-5-MODE: Operating mode is sso, configured mode is sso. So it seems that there was a configuration synch error, so the slave dropped out and restarted? > -----Original Message----- > From: David Coulson [mailto:[EMAIL PROTECTED] > Sent: Friday, February 15, 2008 9:41 AM > To: Gregory Boehnlein > Cc: [email protected] > Subject: Re: [c-nsp] 7513 RSP4+ SSO Failover Question - 12.2(25)S12 > > What is in the log for the previous five minutes? > > sh log | inc HA > > Gregory Boehnlein wrote: > > Hello, > > We're running a Cisco 7513 w/ Dual RSP 4+s in SSO mode. IOS is > > version Version 12.2(25)S12. We received a notification of an SSO > failover > > from our Master RSP to our Slave. Prior to the failover, I had been > doing a > > BERT test on a T1 riding on a PA-MC-T3. You can see from the logs > below > > where I cleared the logs. About 30 seconds later, the BGP peer on the > other > > side of the T1 I was testing on came back online and then 3 seconds > after > > that, we got the message. > > > > Feb 15 00:50:57: %CLEAR-5-COUNTERS: Clear counter on interface > > Serial10/1/0/2:0 by n2net on vty1 (207.166.192.127) > > Feb 15 00:51:13: %BGP-5-ADJCHANGE: neighbor 207.166.197.25 Up > > Feb 15 00:51:16: %RSP-5-SLAVEUP: Slave changed to state Running, > Buffer > > memory state : disabled > > Feb 15 00:51:16: %HA-5-NOTICE: Standby (slave) configured to run hw- > module > > HA image "slot0:rsp-ik91sv-mz.122-25.S12.bin" > > Feb 15 00:51:17: %HA-5-NOTICE: Loading Standby (slave) image: > > "slot0:rsp-ik91sv-mz.122-25.S12.bin" > > Feb 15 00:51:23: %IF-4-BACKWARD_COUNTERS: Corrected for backward > rxtx_errors > > counters (897 -> 896) on Serial10/1/0/20:0 > > Feb 15 00:52:51: %RSP-5-SLAVEUP: Slave changed to state Running, > Buffer > > memory state : disabled > > Feb 15 00:52:51: %HA-5-MODE: Operating mode is hsa, configured mode > is sso. > > Feb 15 00:53:18: %ISSU_PROCESS-7-DEBUG: Peer state is hot redundant > > Feb 15 00:53:23: %HA-5-SYNC_NOTICE: Standby has restarted. > > Feb 15 00:53:24: %HA-5-MODE: Operating mode is sso, configured mode > is sso. > > > > Things look normal, and the RSP4+ in slot 6 is marked as active. > > > > core-ar1#show redundancy debug > > Operating mode is sso > > redundancy mode sso > > hw-module slot 6 image slot0:rsp-ik91sv-mz.122-25.S12.bin > > hw-module slot 7 image slot0:rsp-ik91sv-mz.122-25.S12.bin > > > > Active High Availability version is 3.0 > > Standby High Availability version is 3.0 > > > > Active is in slot 6 > > Standby is in slot 7 > > > > The system total uptime since last reboot is 10 weeks, 3 days, 13 > hours 50 > > minutes. > > The system has experienced 0 switchovers. > > > > There doesn't appear to be any switchover history: > > core-ar1#show redundancy switchover history > > > > I'm thinking that the Slave in slot 7 crashed and rebooted, but I > can't seem > > to find any logs that would indicate it, other than the messaged in > the > > system log. Any suggestions? Ideas? > > > > > > _______________________________________________ > > cisco-nsp mailing list [email protected] > > https://puck.nether.net/mailman/listinfo/cisco-nsp > > archive at http://puck.nether.net/pipermail/cisco-nsp/ > > > > -- > This message has been scanned for viruses and > dangerous content by N2Net Mailshield, and is > believed to be clean. _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
