I decided to set up constant pings to our devices and use the "reload at" command to reload all of the switch stacks on all 6 floors of one building at the same time.
We are currently on code version 03.03.05 and are upgrading to 03.07.00 at the advice of Cisco TAC.
I couldn't find much good documentation on the "reload at" command so I used my test switch stack to figure it out (using the question mark on the CLI is kind of ambiguous).
Below shows what I typed into the CLI:
Switch#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
slot Slot number card
standby-cpu Standby RP
<cr>
Switch#reload
at ?
hh:mm Time to reload (hh:mm)
Switch#reload
at 21:05 ?
<1-31> Day of the month
LINE Reason for reload
MONTH Month of the year
<cr>
Switch#reload
at 21:05 PDT ?
LINE
<cr>
Switch#reload
at 21:05 PDT Jun
Switch#reload
at 21:05 PDT Jun ?
LINE
<cr>
Switch#reload
at 21:05 ?
<1-31> Day of the month
LINE Reason for reload
MONTH Month of the year
<cr>
Switch#reload
at 21:05 ?
<1-31> Day of the month
LINE Reason for reload
MONTH Month of the year
<cr>
Switch#reload
at 21:05 Upgrade ?
LINE
<cr>
That is what I mean by ambiguous... It keeps giving me that "LINE" command.
After some trial and error, I figured out the following command works:
Switch#
Reload
scheduled for 21:05:00 PDT Tue Jun 9 2015 (in 6 hours and 36 minutes) by
console
Reload reason:
6/09/15 UpgradeReload command is being issued on Active unit, this will
reload the whole stack
Proceed with
reload? [confirm]
Switch#
Jun 9
21:28:27.309: %SYS-5-SCHEDULED_RELOAD: Reload requested for 21:05:00 PDT Tue
Jun 9 2015 at 14:28:18 PDT Tue Jun 9 2015 by console. Reload Reason: 6/09/15 Upgrade.
Jun 9
21:28:27.309: %SYS-5-SCHEDULED_RELOAD: Reload requested for
Switch#sh ver
Cisco IOS
Software, IOS-XE Software, Catalyst L3 Switch Software
(CAT3K_CAA-UNIVERSALK9-M), Version 03.03.02SE RELEASE SOFTWARE (fc2)
Technical
Support: http://www.cisco.com/techsupport
Copyright (c)
1986-2014 by Cisco Systems, Inc.
Compiled Thu
20-Feb-14 21:17 by prod_rel_team
Output truncated..
Switch Ports
Model
SW Version SW
Image
Mode
------ -----
-----
----------
----------
----
*
1 32 WS-C3850-24P
03.03.02SE cat3k_caa-universalk9
INSTALL
2 32 WS-C3850-24P
03.03.02SE cat3k_caa-universalk9
INSTALL
Switch 02
---------
Switch
uptime
: 1 week, 5 days, 3 hours, 39 minutes
Base Ethernet
MAC Address :
Motherboard
Assembly Number :
Motherboard
Serial Number :
Model Revision
Number
: K0
Motherboard
Revision Number : C0
Model
Number
: WS-C3850-24P
System Serial
Number
:
Configuration
register is 0x102
Reload
scheduled for 21:05:00 PDT Tue Jun 9 2015 (in 6 hours and 36 minutes) by
console
Reload reason:
As you can see, this shows I am using code version 03.03.02. This is my non-production stack.
You can also issue the following command to reload on a specific day:
Switch#reload at 20:00 07 Dec Upgrade
or a specific time:
Switch#reload in 120 (reloads the switch in 2 hours)
Update - 6/10/2015
Reload/Upgrade successful!
Here is what the switch does when you are logged in to it.
Reload scheduled for 21:05:00 PDT Tue Jun 9 2015 (in 1 minute and 20 seconds) by xxxxxxxxx on vty0 (x.x.x.x)
Reload reason: 6/09/15 Upgrade
Swtich#sh clo
21:03:56.858 PDT Tue Jun 9 2015
Switch#
***
*** --- SHUTDOWN in 0:01:00 ---
***
Switch#
***
*** --- SHUTDOWN NOW ---
***
You can also issue the following command to reload on a specific day:
Switch#reload at 20:00 07 Dec Upgrade
or a specific time:
Switch#reload in 120 (reloads the switch in 2 hours)
Update - 6/10/2015
Reload/Upgrade successful!
Here is what the switch does when you are logged in to it.
Reload scheduled for 21:05:00 PDT Tue Jun 9 2015 (in 1 minute and 20 seconds) by xxxxxxxxx on vty0 (x.x.x.x)
Reload reason: 6/09/15 Upgrade
Swtich#sh clo
21:03:56.858 PDT Tue Jun 9 2015
Switch#
***
*** --- SHUTDOWN in 0:01:00 ---
***
Switch#
***
*** --- SHUTDOWN NOW ---
***
Update - 4/29/2016
We are no longer on IOS 03.07.00 and have actually downgraded to 03.06.04 which is the recommended release. We were having some "bug"gy behavior.
No comments:
Post a Comment