05-23-2012 11:46 AM - edited 03-04-2019 04:27 PM
Hello,
i have 2 sup32's that i just upgraded the IOS on. they were both stable, 1 being active and the other being hot. I then write erase(d) the ios on the sup1 and rebooted. now the sup1 is up but sup2 is in an unknown state. i consoled into the sup2 (unknown) and it is in rommon mode. i am familiar with rommon and uploading IOS. My question is, can i load the IOS from the active supervisor module? I believe the boot variable is incorrect.
Any help is appreciated.
Regards!
05-23-2012 03:03 PM
My question is, can i load the IOS from the active supervisor module?
No.
I believe the boot variable is incorrect.
Then console into the sup 2 and type "boot
05-23-2012 08:45 PM
Hello Anthony,
You cannot access redundant switch file systems while in ROMMON but you can boot it first (using "boot
copy bootflash:
To see the list of available file systems you can use command "show file systems".
Kind Regards,
Ivan
**Please grade this post if you find it useful.
05-24-2012 11:24 AM
This worked.
Thank you!
05-29-2012 10:51 AM
Another question,
Why is my standby sup32 having issues. It is going to rommon. I console into the rommon and tell it to boot from disk0 and it comes up ok.
I believe I am missing the boot statement in the config? Here is an output of my chassis
File Systems:
Size(b) Free(b) Type Flags Prefixes
- - opaque rw system:
- - opaque rw tmpsys:
- - opaque ro flexwan-fpd:
65536000 60636764 flash rw bootflash:
512180224 507920384 disk rw disk0:
255938560 131895296 disk rw sup-bootdisk:
62818478 0 opaque ro sup-microcode:
0 162007156 opaque wo sup-image:
126956 125732 nvram rw const_nvram:
1961976 1954470 nvram rw nvram:
- - opaque rw null:
- - opaque ro tar:
- - network rw tftp:
- - opaque wo syslog:
- - network rw rcp:
- - network rw ftp:
- - network rw http:
- - network rw scp:
- - network rw https:
- - opaque ro cns:
1961976 1954470 nvram rw slavenvram:
126956 125732 nvram rw slaveconst_nvram:
511705088 441860096 disk rw slavedisk0:
256462848 198037504 disk rw slavesup-bootdisk:
65536000 60317424 flash rw slavebootflash:
- - nvram rw slavercsf:
- - opaque rw slavesystem:
- - opaque rw revrcsf:
05-29-2012 11:01 AM
Hi Anthony,
Possible config-register is incorrect on switch or route processors. Or boot string is incorrect.
Please check for that by booting the supervisor and executing the following commands:
remote command standby-sp show boot
remote command standby-rp show boot
I suppose you are running SSO redundancy, otherwise this commands may not work.
If you see config-register different from 0x2102, execute the following commands to change it:
conf t
conf-reg 0x2102
end
wr
After that you should see correct values:
remote command standby-sp show boot
remote command standby-rp show boot
Also check if the boot string image exists on the standby sup in the same location as on active.
Kind Regards,
Ivan
**Please grade this post if you find it useful.
05-29-2012 11:27 AM
Router#remote command standby-sp show boot
Standby not ready yet. Try later.
Router#remote command standby-rp show
Router#remote command standby-rp show
Standby not ready yet. Try later.
Here is the output from the rommon
rommon 1 > set
PS1=rommon ! >
LOG_PREFIX_VERSION=1
SLOTCACHE=cards;
SUPW_2=1
SUPW_7=1
SUPW_8=1
SUPW_6=1
CRASHINFO=bootdisk:crashinfo_20120517-170544
SUPW_5=1
PF_REDUN_CRASH_COUNT=0
RET_2_RTS=20:08:58 UTC Thu May 17 2012
IP_ADDRESS=192.168.1.1
IP_SUBNET_MASK=255.255.255.0
DEFAULT_GATEWAY=192.168.1.1
TFTP_SERVER=192.168.1.2
TFTP_FILE=s3223-advipservicesk9_wan-mz.122-33.SXI5.bin
BOOT=
?=1
ACL_DENY=0
RANDOM_NUM=1158325460
BSI=0
RET_2_RCALTS=
05-29-2012 11:48 AM
Hi Anthony,
"Standby not ready yet" means that standby is either not booted (e.g. in ROMMON) or in not synronized with active yet. Did you confirm the standby is up and running? You can do it by checking module status in "show module" or redundancy status in "show redundancy".
Kind Regards,
Ivan
**Please grade this post if you find it useful.
05-29-2012 12:56 PM
Done. Thank you.
Booted the rommon
Went back to active sup, formatted hot flash, recopied ios, verified ios, then set boot:
BOOT variable = sup-bootdisk:s3223-advipservicesk9_wan-mz.122-33.SXI5.bin,1;
CONFIG_FILE variable does not exist
BOOTLDR variable does not exist
Configuration register is 0x2102
Standby is up
Standby has 524288K/65536K bytes of memory.
Standby BOOT variable = sup-bootdisk:s3223-advipservicesk9_wan-mz.122-33.SXI5.bin,1;
Standby CONFIG_FILE variable does not exist
Standby BOOTLDR variable =
Standby Configuration register is 0x2102
05-29-2012 08:58 PM
Hi Anthony,
This settings look good. Did you check if the standby auto-boots after reload now? You can verify it by manually reloading standby with "hw-mod slot
Kind Regards,
Ivan
**Please grade this post if you find it useful.
02-13-2013 05:03 AM
Hi Guys,
I have upgraded to IOS version s3223-adventerprisek9_wan-mz.122-33.SXJ4.bin and since I upgraded the SSO is not working.
The redundand Sup loads the IOS and when it tries complete the process it reboots the whole time. This is happening on 4 out of 60 switches I upgraded. All is using sup32 and same IOS version.
I have lookup up on this and didn't find anything rock solid for this.
Can you guys help please?
Regards,
Clifton.
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: