(3 votes, average: 4.67 out of 5)
Loading ...
Print This Post
Operational Notes:
The stack master is the single point of stack-wide management. From the stack master, you configure:
- System-level (global) features that apply to all stack members
- Interface-level features for each stack member
All stack members are eligible stack masters. If the stack master becomes unavailable, the remaining stack members participate in electing a new stack master from among themselves. A set of factors determine which switch is elected the stack master. One of the factors is the stack member priority value. The switch with the highest priority value becomes the stack master.
A higher priority value for a stack member increases its likelihood to be elected stack master and to retain its stack member number. The priority value can be 1 to 15. The default priority value is 1.
The stack master contains the saved and running configuration files for the switch stack. The configuration files include the system-level settings for the switch stack and the interface-level settings for each stack member. Each stack member has a current copy of these files for back-up purposes.
You manage the switch stack through a single IP address. The IP address is a system-level setting and is not specific to the stack master or to any other stack member. You can manage the stack through the same IP address even if you remove the stack master or any other stack member from the stack.
A switch stack has up to nine stack members connected through their StackWise ports. A switch stack always has one stack master.
Command Usage Notes:
You can display the stack member number by using the user EXEC command:
Switch#show switch
You can manually change the stack member number by using the global configuration command:
Switch(Config)#switch (current-stack-member-number) renumber (new-stack-member-number)
The new number goes into effect after that stack member resets.
A single switch can be reset in the stack by using the privileged EXEC command:
Switch#reload slot (stack-member-number)
You can change the priority value for a stack member by using the global configuration command:
Switch(Config)#switch (stack-member-number) priority (new-priority-value)
To manually upgrade a stack member using the IOS from another stack member:
Switch#archive copy-sw /destination-system (destination-stack-member-number) /force-reload (source-stack-member-number)
To run a command (such as show version) on a single switch in the stack:
remote command (stack-member-number) show version
Valid values for stack-member-number are 1-9
October 26th, 2009 at 6:19 am
Great little guide for 3750 stack basics, I found this very handy being a noob.
Though the question I was looking to have answered was: How can you stack two dissimiler 3750 switches without getting an IOS configuration mismatch issue?
For example,
WS-C3750-24TS 12.2(35)SE5 C3750-IPSERVICES-M
stacked with a
WS-C3750G-24PS 12.2(25)SEC2 C3750-IPSERVICESK9-M
If you could answer this for me I’m all ears and would be very appreciative.
Thanks
David
March 23rd, 2010 at 10:47 am
I want to remove the Stack Number 2 and 9 in Cisco 3750
June 7th, 2010 at 11:22 am
In response to
Though the question I was looking to have answered was: How can you stack two dissimiler 3750 switches without getting an IOS configuration mismatch issue?
The problem is
12.2(35)SE5 C3750-IPSERVICES-M & 12.2(25)SEC2 C3750-IPSERVICES-M you MUST run the same IOS
Once they are running the same IOS they will be happy. The hardware isn’t an issue, it’s the feature set and version.
June 17th, 2010 at 6:10 pm
This was exactly what I was looking for. Quick and to the point.
Thx billion Scott
July 1st, 2010 at 3:21 am
This is very helpful, thanks man
Msizi,South Africa
February 15th, 2011 at 3:26 pm
Let’s say you have a stack and want to renumber the members, however the 2 members in mind have ports labeled/etc. Do these names follow the rename? In other words gi3/0/4 is labeled “Server1″, I renumber this switch to 2, will gi2/0/4 inherit the name “Server1″ after it reloads? More importantly, I’m concerned with VLAN memberships, speed, duplex, etc.
February 15th, 2011 at 4:29 pm
The interface-specific configuration of each stack member is associated with the stack member number. If the switch is manually renumbered the following rules apply:
– If an interface-specific configuration does not exist for that member number, the stack member uses its default interface-specific configuration.
– If an interface-specific configuration exists for that member number, the stack member uses the interface-specific configuration associated with that member number.
May 5th, 2011 at 1:58 am
Hi,
Even after removing the devices from stack it is still in stack mode.
Can you please let me know how to reset the stack configs.
Switch#sh switch
Switch/Stack Mac Address : c471.fea0.6b00
H/W Current
Switch# Role Mac Address Priority Version State
———————————————————-
*1 Master c471.fea0.6b00 1 1 Ready
Regards
Enbanathan.E
October 12th, 2011 at 10:01 pm
Very good guide. Straight and Concise.
By the way, i want to enable PBR but it needs a switch reload. Will the new configuration will take effect if I reload the master first, then member?
November 1st, 2011 at 1:55 am
Even after removing the devices from stack it is still in stack mode.
Can you please let me know how to reset the stack configs.
I have a stand alone 2960-s switch witch before was belong to stack member . How now i can restore it to the right port number 0/1…. and not 1/0/1…….
December 3rd, 2011 at 2:35 am
Hi, just a question perhaps is very easy I have a stack of 5 switches but I dont know why I have switch 2&3 in Provisioned mode, is there a way to for the change of mode ?