It's always best to get the console logs of both active and standby for a cold reboot and see what is going on.
All the things folks have mentioned are good too. On Wed, Dec 19, 2007 at 12:19:57AM -0500, Andy Dills wrote: > On Tue, 18 Dec 2007, neal rauhauser wrote: > > > Can anyone comment on RSP redundancy with SSO mode? > > > > I have a test 7507 with rsp-k4pv-mz.120-32.S8.bin on both RSP2s. I've done > > this: > > > > service single-slot-reload-enable > > > > > > redundancy > > no keepalive-enable > > mode sso > > > > And it doesn't seem to ever sync the slave > > Try adding: > > hw-module slot 2 image slot0:/rsp-k4pv-mz.120-32.S8.bin > hw-module slot 3 image slot0:/rsp-k4pv-mz.120-32.S8.bin > slave auto-sync config > > And then (make sure to wr mem first): > > hw-module standby-cpu reset > > > Peer (slot: 3) information is not available because it is in 'DISABLED' > > state > > Sounds like the slave RSP didn't boot, I'm guessing because of one of the > above. Make sure the image exists in both slot0 and slaveslot0. > > Andy > > --- > Andy Dills > Xecunet, Inc. > www.xecu.net > 301-682-9972 > --- > _______________________________________________ > cisco-nsp mailing list cisco-nsp@puck.nether.net > https://puck.nether.net/mailman/listinfo/cisco-nsp > archive at http://puck.nether.net/pipermail/cisco-nsp/ _______________________________________________ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/