3500 stacking issues
01-23-2015 10:12 AM
I'm working on a stack of 3500 switches. After completing the GUI quick setup and the reboot, the GUI display doesn't match the LED display on the switches. And CLI can show some thing different. I've tried multiple methods of steps in the process as far as when do I plug in the cable, when do I power on each switch, in several different orders and can't seem to find the magic process. This has occurred on multiple switch stacks with same results. I'm frustrated with what should be a simple process.
This is quite confusing when you configure a specific port on the 2nd or 3rd switch in a stack and then the GUI doesn't reflect what you're looking at.
How do I ensure the GUI reflects the status of the switch? How do I ensure the switches are in a specific order?
Re: 3500 stacking issues
01-23-2015 03:19 PM - edited 01-23-2015 03:19 PM
The GUI and CLI build the topology based upon the neighbor relationship starting from the perspective of member 0. It has no knowledge of physical placement as in switch 0 is on top, then switch 1 is in the middle and switch 2 is on the bottom.
Putting the role of the switch aside for a moment (e.g. primary, secondary, linecard), the way to ensure proper numbering and the easiest is how you described so I'm unclear of where it went sideways. What you want to do is power on the 1st switch and it will become member 0. Before powering on any other switches, go ahead and configure this switch including a stack-profile and save it. Here is an example of one:
member-id 0 election-priority 255
member-id 1 election-priority 255
Remember to save the config. Then power on the second switch, this switch should then become member 1. A short period of time later, go ahead and power on member 2.
Now to correct the switches already in deployment, you can use the "set stacking renumber" or "set stacking swap" commands to correct the member IDs.
Regarding the roles of the switches, by using an election-priority of 255, means that these switches will either be primary or secondary and all other switches will be linecards. I recommend the usage of 255 for both as that eliminates pre-emption should the primary fail.