Reload Command Unexpected Results (Bug?)

[hauchinango]

As others probably do, when making a possible service affecting change I have used the "Reload in X" command to reboot the router in the event the change I am making blocks my access to the device.  

I wanted to share an unfortunate experience I had recently that may help others and possible have someone from Cisco verify if this is a bug or working as designed.

When typing the command on a core switch, I inadvertently typed reload iin 5.  Instead of rejecting the command, the switch rebooted immediately.

I tried this again on a lab 3850 switch (IOS version 03.03.03.SE.150-1.EZ3 ) with the same results.  In fact, if you type "reload" followed by any unrecognized characters, the switch ignores anything after the reload and proceeds with the reboot.  I assumed you would get the % Unknown command response.

Hope this helps someone to take a moment before using the command and ensure your spelling is correct.

[milan.kulik · Accepted solution]

Hi,

as you can see:

router#reload ?
  /noverify  Don't verify file signature before reload.
  /verify    Verify file signature before reload.
  LINE       Reason for reload
  at         Reload at a specific time/date
  cancel     Cancel pending reload
  in         Reload after a time interval
  warm       Reload should be warm
  <cr>

So your "iin 5" is considered to be the "Reason for reload".

But the router is still asking for an immediate reload confirmation:

router#reload iin 5
Proceed with reload? [confirm]

While when the correct syntax is used:

router#reload in 5
Reload scheduled in 5 minutes by userx on console
Reload reason: Reload Command
Proceed with reload? [confirm]
 

So you just need to be careful before confirming - if the "scheduled" line is missing, you are confirming an immediate reload!

Best regards,

Milan
 

[hauchinango]

5 for you.  Thanks for clarifying.