I have a sup32 running in a 6513 switch running in native mode. My boot var is set to BOOT=sup-bootdisk:s3223-adventerprisek9_wan-mz.122-18.SXF8.bin and my config register is 0x02102.
When I reload the switch autoboot tries to open the image with this statement âboot bootdisk: s3223-adventerprisek9_wan-mz.122-18.SXF8.binâ but fails with an error stating
open(): Open Error = -13
loadprog: error - on file open
From there it goes directly into rommon. From rommon if I issue the exact same statement âboot bootdisk: s3223-adventerprisek9_wan-mz.122-18.SXF8.binâ it works fine and loads the image. Also if I change the BOOT variable to BOOT= s3223-adventerprisek9_wan-mz.122-18.SXF8.bin leaving out the bootdisk part and reload it works as well.
I just can't seem to understand why autoboot has a problem with the bootdisk: portion of the command. Rommon can read from bootdisk: just fine.
In your second instance of the statement there is a space; check that doesn't exist.
I have also seen strange problems on 6500s where once you have the system booted and looked at the boot variables everything was fine. However, if you boot to rommon and look at the variables there they are completely different. I set the variables from rommon, rebooted and everything worked, even after a reset. Unfortunately I ddn't have time to investigate the problem as they were new switches that needed to be in production ASAP. So unfortunately I don't know why that happened, but it would seem there are two palces for the boot variables on the 6500 platform!!!!!
If anyone can explain this, then I would be very greatful!!
After several reload and reset commands I ended up powering the switch down and then back on. After I did that the autoboot statement worked. Go figure. But that still doesn't explain why it wouldn't work when I issued the reset command from rommon.
Anyway, not sure if this was a bug or not.. but even though my config register was set to 0x2102, after each reload/ cold boot it was going into rommon. did a lot of looking and found FiLeinster post with the url.
In the end it was just re-applying the config-register.
This is actually a pretty cool feature, i didn't even know it existed until I was looking for a solution to advertise a subnet (prefix in BGP talk), only if a certain condition existed. This is exactly what conditional advertisements does
j ai une question j ai achete un routeur cisco 887VA-k9 , je le configuré avec la configuration ci- dessous
si je le lier avec mon pc portable sur l un de ses ports directement ça marche toute est bien ( la connexion internet + m...
Attached policy provides CLI access to the Cisco 4G router over text messaging. Two files are in the attached .tar file:
2. PDF with instructions on how to load and use the .tcl file.