- If you manually change the stack member number by using the switch current-stack-member-number renumber new-stack-member-number EXEC command, the new number goes into effect after that stack member resets (or after you use the reload slot stack-member-number privileged EXEC command) and only if that number is not already assigned to any other.
- Password recovery on the newer Cat3k boxes (3850/3650) is slightly different then how it used to be on pretty much all of the other catalyst pizza box switches. Here is a short instruction set from the Cisco support forums.
Hi all, We would like to reboot every member of our 3850 stack (6 members). Poker saint amand tournoi. Share market gambling. Here is the current state: 1- Master 2- Standby 3- Member 4- Member 5- Member 6- Member The goal is to reload them one by one. What is the preferable order to do this while keeping the same state (same master/standy.
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:
/noverify Don't verify file signature before reload.
LINE Reason for reload
- If you manually change the stack member number by using the switch current-stack-member-number renumber new-stack-member-number EXEC command, the new number goes into effect after that stack member resets (or after you use the reload slot stack-member-number privileged EXEC command) and only if that number is not already assigned to any other.
- Password recovery on the newer Cat3k boxes (3850/3650) is slightly different then how it used to be on pretty much all of the other catalyst pizza box switches. Here is a short instruction set from the Cisco support forums.
Hi all, We would like to reboot every member of our 3850 stack (6 members). Poker saint amand tournoi. Share market gambling. Here is the current state: 1- Master 2- Standby 3- Member 4- Member 5- Member 6- Member The goal is to reload them one by one. What is the preferable order to do this while keeping the same state (same master/standy.
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:
/noverify Don't verify file signature before reload.
LINE Reason for reload
cancel Cancel pending reload
slot Slot number card
Switch#reloadat ?
<1-31> Day of the month
MONTH Month of the year
LINE
Switch#reloadat 21:05 PDT Jun
LINE
Switch#reloadat 21:05 ?
LINE Reason for reload
Switch#reloadat 21:05 ?
LINE Reason for reload
Switch#reloadat 21:05 Upgrade ?
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 at 21:05 6/09/15 Upgrade
Reloadscheduled for 21:05:00 PDT Tue Jun 9 2015 (in 6 hours and 36 minutes) byconsole
Reload reason:6/09/15 UpgradeReload command is being issued on Active unit, this willreload the whole stack
Switch#
Jun 921:28:27.309: %SYS-5-SCHEDULED_RELOAD: Reload requested for 21:05:00 PDT TueJun 9 2015 at 14:28:18 PDT Tue Jun 9 2015 by console. Reload Reason: 6/09/15 Upgrade.
Jun 921:28:27.309: %SYS-5-SCHEDULED_RELOAD: Reload requested for
Cisco IOSSoftware, IOS-XE Software, Catalyst L3 Switch Software(CAT3K_CAA-UNIVERSALK9-M), Version 03.03.02SE RELEASE SOFTWARE (fc2)
TechnicalSupport: http://www.cisco.com/techsupport
Compiled Thu20-Feb-14 21:17 by prod_rel_team
Switch PortsModel SW Version SWImage Mode
* 1 32 WS-C3850-24P 03.03.02SE cat3k_caa-universalk9INSTALL
2 32 WS-C3850-24P 03.03.02SE cat3k_caa-universalk9INSTALL
Cisco Ios Reload Command
---------
Switchuptime : 1 week, 5 days, 3 hours, 39 minutes
MotherboardAssembly Number :
Model RevisionNumber : K0
ModelNumber : WS-C3850-24P
Reloadscheduled for 21:05:00 PDT Tue Jun 9 2015 (in 6 hours and 36 minutes) byconsole
Cisco 3850 Configuration Guide
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 ---
***
Cisco 3850 Switch Commands
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.
