Reload member switch in stack?

Answered Question
Apr 5th, 2012

Hello,

I have just upgraded 2 3750 switches in a stack via the master and reloaded the master switch remotely, how can I reload the 2nd (member) switch?

Regards

I have this problem too.
0 votes
Correct Answer by JosephDoherty about 2 years 1 week ago

Disclaimer

The    Author of this posting offers the information contained within this    posting without consideration and with the reader's understanding that    there's no implied or expressed suitability or fitness for any  purpose.   Information provided is for informational purposes only and  should not   be construed as rendering professional advice of any kind.  Usage of  this  posting's information is solely at reader's own risk.

Liability Disclaimer

In    no event shall Author be liable for any damages whatsoever  (including,   without limitation, damages for loss of use, data or  profit) arising  out  of the use or inability to use the posting's  information even if  Author  has been advised of the possibility of such  damage.

Posting

Andy White wrote:

Thanks, I orginally just did a manual tftp upgrade on both switches (master, member), then just did a reload on the master.  I guess this is all I needed to do and not worry about the individual reload of the member as this was already done via the first reload of the master?

If you just did a "reload", all the stack members should have reloaded.

  • 1
  • 2
  • 3
  • 4
  • 5
Average Rating: 5 (1 ratings)
amikat Fri, 04/06/2012 - 00:49

Hi,

You can use the "reload slot stack-member-number" command (e.g.: reload slot 2).

Best regards,

Antonin

amikat Fri, 04/06/2012 - 04:03

Hi,

The "show version" command should give you the IOS versions of all the stack members. It is displayed as a short table further down the output. You can also connect to a stack member via the "session stack-member-number" command and when connected you can issue various commands including the "sh ver". The session can be terminated via the "exit" command and the connection is returned to the stack master.You have also the option to use the "remote command stack-member-number show version" command issued from the stack master.

Having said all of that finally you should be aware of the fact that there are IOS compatibility requirements for all the switches within the same stack. Basically with the major version number incompatibility the switches cannot co-exist within the stack while in the case of the minor version number incompatibility the software tries to upgrade or downgrade the partialy incompatible switch. So I would expect all your switches within the stack should have the same IOS version.

Best regards,

Antonin

JosephDoherty Fri, 04/06/2012 - 05:26

Disclaimer

The     Author of this posting offers the information contained within this     posting without consideration and with the reader's understanding  that    there's no implied or expressed suitability or fitness for any   purpose.   Information provided is for informational purposes only and   should not   be construed as rendering professional advice of any kind.   Usage of  this  posting's information is solely at reader's own risk.

Liability Disclaimer

In     no event shall Author be liable for any damages whatsoever   (including,   without limitation, damages for loss of use, data or   profit) arising  out  of the use or inability to use the posting's   information even if  Author  has been advised of the possibility of  such  damage.

Posting

BTW how did you reload the master?  Reason I ask, believe a generic reload will reload the whole stack.

Reza Sharifi Fri, 04/06/2012 - 12:30

Joe is right a generic reload will reload the entire stack

Sent from Cisco Technical Support iPhone App

Whiteford_2 Fri, 04/06/2012 - 13:33

When you say a generic reload, do you mean when I reload the master every member gets reloaded also?

Reza Sharifi Fri, 04/06/2012 - 14:08

Correct when you issue the reload command it will reload the whole stack

HTH

Sent from Cisco Technical Support iPhone App

amikat Sat, 04/07/2012 - 01:42

Hi,

The answer to your question is: it depends. When you issue the "reload" command from the stack master the system TRIES to reload all the stack members, but there is quite a bunch of reasons it may not succeed which results in the partial reload only.

Best regards,
Antonin

Leo Laohoo Fri, 04/06/2012 - 18:26
I have just upgraded 2 3750 switches in a stack via the master and reloaded the master switch remotely, how can I reload the 2nd (member) switch?

This doesn't make sense.  When you upgrade the stack master and reloaded the stack master ONLY, the second switch (not the stack master) will become THE master (by choice).  Once this happens the stack member #1 will NOT be able to join the stack because of version mismatch.

Whiteford_2 Sat, 04/07/2012 - 00:42

Sorry for my description.  I have 2 x 3750 switches in a stack and I upgraded the master then the member at the same time and only reloaded the master after.  I wasn't sure if rebooting the master only would reload the member also.  I issued the "reload stack member number" and all is good.

The other guys are basically saying I didn't need to do that, as reloading the master would restart the member also. 

If I had 5 switches in a stack, my process would be to upgrade all the 5 switches first then just reload the master only as the remaining 4 switches would also reload at the same time and use the new IOS, stops the mismatch I guess.  No need to individually reload each member after the master is reloaded.

Hope that helps

Leo Laohoo Sat, 04/07/2012 - 00:57

What you are describing is called as the "Rolling Stack Upgrade".

Each stack member will upgrade their IOS.  Once the upgrade for the ENTIRE stack is complete, each switch member will reload one by one.

JosephDoherty Sat, 04/07/2012 - 03:10

Disclaimer

The   Author of this posting offers the information contained within this   posting without consideration and with the reader's understanding that   there's no implied or expressed suitability or fitness for any purpose.   Information provided is for informational purposes only and should not   be construed as rendering professional advice of any kind. Usage of  this  posting's information is solely at reader's own risk.

Liability Disclaimer

In   no event shall Author be liable for any damages whatsoever (including,   without limitation, damages for loss of use, data or profit) arising  out  of the use or inability to use the posting's information even if  Author  has been advised of the possibility of such damage.

Posting

Andy White wrote:

Sorry for my description.  I have 2 x 3750 switches in a stack and I upgraded the master then the member at the same time and only reloaded the master after.  I wasn't sure if rebooting the master only would reload the member also.  I issued the "reload stack member number" and all is good.

The other guys are basically saying I didn't need to do that, as reloading the master would restart the member also. 

If I had 5 switches in a stack, my process would be to upgrade all the 5 switches first then just reload the master only as the remaining 4 switches would also reload at the same time and use the new IOS, stops the mismatch I guess.  No need to individually reload each member after the master is reloaded.

Hope that helps

No, not reloading the master alone, per se, but to reload the whole stack, i.e. just issue reload.  If you issue reload stack #, then you telling it to only reload an individual stack member instead of the whole stack.

Whiteford_2 Sat, 04/07/2012 - 04:09

Thanks, I orginally just did a manual tftp upgrade on both switches (master, member), then just did a reload on the master.  I guess this is all I needed to do and not worry about the individual reload of the member as this was already done via the first reload of the master?

Correct Answer
JosephDoherty Sat, 04/07/2012 - 04:17

Disclaimer

The    Author of this posting offers the information contained within this    posting without consideration and with the reader's understanding that    there's no implied or expressed suitability or fitness for any  purpose.   Information provided is for informational purposes only and  should not   be construed as rendering professional advice of any kind.  Usage of  this  posting's information is solely at reader's own risk.

Liability Disclaimer

In    no event shall Author be liable for any damages whatsoever  (including,   without limitation, damages for loss of use, data or  profit) arising  out  of the use or inability to use the posting's  information even if  Author  has been advised of the possibility of such  damage.

Posting

Andy White wrote:

Thanks, I orginally just did a manual tftp upgrade on both switches (master, member), then just did a reload on the master.  I guess this is all I needed to do and not worry about the individual reload of the member as this was already done via the first reload of the master?

If you just did a "reload", all the stack members should have reloaded.

Whiteford_2 Tue, 04/10/2012 - 02:11

Hi,

As I have 2 switches in a stack, from the master can type "show flash", "show flash1" and "show flash2".  Is flash and flash1  the master or the same switch and flash 2 the member?

I don't understand why I have 3 flash areas and 2 switches?

Thanks

Leo Laohoo Tue, 04/10/2012 - 02:18

The command "dir flash:" means "show me the flash content of the MASTER switch".

The command "dir flash1:" means "show me the flash content of switch stack member 1".

The command "dir flash2:" means "show me the flash content of switch stack member 2".

Stack member 1 does not necessarily mean it is the stack master hence the two commands are "different".

Actions

Login or Register to take actions

This Discussion

Posted April 5, 2012 at 11:22 PM
Stats:
Replies:16 Avg. Rating:5
Views:2990 Votes:0
Shares:0
Tags: No tags.

Discussions Leaderboard

Rank Username Points
1 15,007
2 8,150
3 7,730
4 7,083
5 6,742
Rank Username Points
165
82
70
69
55