2009/12/3 Jeff Kell <[email protected]>: > Both of your remote command examples tell me 256M. The active > supervisor 'show ver' has 512M. And as someone else pointed out, I > don't think it would be running redundancy if the two didn't match up. > But it is... > >> #sho redundancy states >> my state = 13 -ACTIVE >> peer state = 8 -STANDBY HOT > > And appears they may not (or these are the wrong commands)... > > "show ver" says cisco WS-C6509 (R7000) processor (revision 3.0) with > 458752K/65536K bytes of memory. > > "remote command standby-rp show ver" says cisco WS-C6509 (R7000) > processor (revision 3.0) with 227328K/34816K bytes of memory. > > "remote command mod 2 show ver" says cisco WS-C6509 (R7000) processor > (revision 3.0) with 227328K/34816K bytes of memory. > > And the "show boot" says the standby only has 256M... but don't know if > that is relevant to the MSFC2 or PFC2. > >> UTC-6509#show boot >> BOOT variable = >> disk0:s222-ipservicesk9-mz.122-18.SXF17.bin,1;disk0:c6sup22-jk2s-mz.121-26.E7.bin,1; >> CONFIG_FILE variable does not exist >> BOOTLDR variable = >> Configuration register is 0x2102 >> >> Standby is up >> Standby has 227328K/34816K bytes of memory.
This is definitely cause for concern. This prompted me to check the docs: http://cisco.com/en/US/docs/switches/lan/catalyst6500/ios/12.2SXF/native/configuration/guide/nsfsso.html#wp1095529 "If they are not identical, one will boot first and become active and hold the other supervisor engine and MSFC in a reset condition." "Each supervisor engine must have the resources to run the switch on its own, which means all supervisor engine resources are duplicated..." STANDBY HOT and the standby console prompt don't suggest a reset condition. AFAIR when I had mixed IOS versions, the incompatible 2nd Sup2 was kicked out to SP ROMMON or went round and round in the boot... fail... loop. Seems Sup2 doesn't consider RAM a resource. Might wanna set your NMS for 240MB usage alerts :) -- Chris _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
