12-12-2009 02:41 AM - edited 03-06-2019 08:55 AM
Hi,
There are two 3750 switch to be stacked together. The "sh tech-support" was executed from the master device. Does the device intelligence enough to dump the second 3750 switch? if so, how to config it? Thanks
regards
Solved! Go to Solution.
12-12-2009 10:15 AM
when we talk about a stack of 3750 it may be different switches when you look at them physically but once you connect them to a stack then they start acting as one logical unit. so if you do a sh tech it will ha ve a complete output of everything with respect to all the switches in stack.
telenet, console and username pass willl remain the same till the time those switches are in one stack.
So any changes in config you make it will be synced with other switches in stack, in other words all switches will have identical config file.
This link has all necessary procedures when managing switch stacks:
http://www.cisco.com/univercd/cc/td/doc/product/lan/cat3750/12220se/3750scg/swstack.htm
A switch stack is a set of up to nine Catalyst 3750 switches connected through their StackWise ports. One of the switches controls the operation of the stack and is called the stack master. The stack master and the other switches in the stack are stack members. The stack members use the Cisco StackWise technology to behave and work together as a unified system. Layer 2 and Layer 3 protocols present the entire switch stack as a single entity to the network.
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
A switch stack is identified in the network by its bridge ID and, if the switch stack is operating as a Layer 3 device, its router MAC address. The bridge ID and router MAC address are determined by the MAC address of the stack master. Every stack member is uniquely identified by its own stack member number.
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.
The system-level features supported on the stack master are supported on the entire switch stack. If the switch stack must have switches running both standard multilayer image (SMI) and enhanced multilayer image (EMI) software, we recommend that a switch running the EMI software be the stack master. EMI features are unavailable if the stack master is running the SMI software.
Similarly, we recommend that a switch running the cryptographic (that is, supports encryption) version of the SMI or EMI software be the stack master. Encryption features are unavailable if the stack master is running the noncryptographic version of the SMI or EMI software.
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.
12-12-2009 04:13 AM
The "sh tech-support" should show the entire stack.
12-12-2009 05:14 AM
Hi,
How do I check the men, CPU status, .... of second switch? how do I telnet to second switch?
regards
12-12-2009 06:18 AM
HI anitachoi3,
You can access member switches of a stack from the master by running 'session x' where x is the switch number in the stack. In your case you would want to run 'session 2'. You'll notice the prompt will change. Any commands you then run will be able to access commands pretaining to that stack member.
As for running a show tech-support on switch stack, it seems it outputs all relevant information from each member switch also.
12-12-2009 08:35 AM
Hi,
thanks, the "session 2" command should be executed on the master (switch 1), isn't it?
e.g.
master#
master# session 2
member2#
Can I config different "password" for member switch? any issue if the password are different? does it overwrite master's password if the "wr mem" to be executed on member switch?
Thanks
rdgs
12-12-2009 08:49 AM
Hi,
You should always configure the master. Once you configure the master the config from the master will sync with the reset of the members.
Think of whole stack being as one switch. They are phsycally multiple switches, but logically one.
Yes, that is how you session.
Also, please refer to this document for more info an managing your switch stack.
HTH
Reza
12-12-2009 10:15 AM
when we talk about a stack of 3750 it may be different switches when you look at them physically but once you connect them to a stack then they start acting as one logical unit. so if you do a sh tech it will ha ve a complete output of everything with respect to all the switches in stack.
telenet, console and username pass willl remain the same till the time those switches are in one stack.
So any changes in config you make it will be synced with other switches in stack, in other words all switches will have identical config file.
This link has all necessary procedures when managing switch stacks:
http://www.cisco.com/univercd/cc/td/doc/product/lan/cat3750/12220se/3750scg/swstack.htm
A switch stack is a set of up to nine Catalyst 3750 switches connected through their StackWise ports. One of the switches controls the operation of the stack and is called the stack master. The stack master and the other switches in the stack are stack members. The stack members use the Cisco StackWise technology to behave and work together as a unified system. Layer 2 and Layer 3 protocols present the entire switch stack as a single entity to the network.
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
A switch stack is identified in the network by its bridge ID and, if the switch stack is operating as a Layer 3 device, its router MAC address. The bridge ID and router MAC address are determined by the MAC address of the stack master. Every stack member is uniquely identified by its own stack member number.
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.
The system-level features supported on the stack master are supported on the entire switch stack. If the switch stack must have switches running both standard multilayer image (SMI) and enhanced multilayer image (EMI) software, we recommend that a switch running the EMI software be the stack master. EMI features are unavailable if the stack master is running the SMI software.
Similarly, we recommend that a switch running the cryptographic (that is, supports encryption) version of the SMI or EMI software be the stack master. Encryption features are unavailable if the stack master is running the noncryptographic version of the SMI or EMI software.
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.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide