Member for 5 years, 9 months
Last seen more than a month ago
Tallmadge, OH 44278, United States
Thanks. I'm aware of the Class deprecation; I was using that as a descriptor. I will look into the
no switchport stuff in a bit.
added 178 characters in body
Darn. I was really hoping that pseudo interface was a thing. Yeah I've done that IP aliasing with no problem, but these are two wildly different IP spaces. One's a class A private address, the other is in Class C. I can't change the other device's Class C address to be in the same VLAN either.
I did find that the BIN specified in the startup-config file referenced a BIN that wasn't available on the standby module, so it just boot looped. I'm collecting the various BINs (7 altogether) and configs with the purpose of getting all of them on each module for maximum redundancy.
I found a couple newer versions of IOS on the spare supervisors. Step 4 might be a possibility. My predecessor wouldn't have put them in bootflash: if we didn't have the licenses.
Marking this one as answered because it got me to where I needed to be.
I used a pin to reset the slot 2 supervisor. It went into a repeated boot loop, which I could Ctrl+c to stop. " Current BOOT file is --- bootflash:cat4000-is-mz.121-12c.EW1.bin boot: can not load 'bootflash:cat4000-is-mz.121-12c.EW1.bin'" There is a different BIN (newer version of IOS too) in bootflash, "cat4000-i9s-mz.122-18.EW3.bin". I issued
boot. It booted and now it's at "STANDBY SUPERVISOR REDUNDANCY mode is RPR Waiting for Switchover Activity".
sh red states looks kosher too. Can I copy the active's BIN to the standby's bootflash?
@RonMaupin, I just got in. I'll try the steps 1-3 mere3ortal suggested below.
Will try steps 1-3 Wednesday. Thx.
added command output.