1/23/2024 0 Comments Renaine switchIn that case if you looking new model to master switch and old to be slave, in the case re-numbering of switch number means ports also going to change, this means you need to Physically patch back where they rquired to be. We always suggest to numbering when you planning time and installing in greenfiled, some case that is not possible organically capacity has been changed. You are overlap with other requirement with the orginal post vs your requirement (i would adivse to post new thread for more clarity than follow the same) Afterwards, I can clean up by resetting the configs on switch #1. I take it in my use case, with only switch #1 in use so far, all I need to do is copy all used port configurations from #1 to the corresponding ports on #3 first, particularly the uplink, then pull the switcharoo on the switch numbers 1>3 and 3>1, before reloading. There's no need for the intermediate step of #1->#3, then #2->#1, and lastly #3->#2, as no change occurs until reload anyway. In the original question #1->#2, then #2->1. Please let me know if I'm incorrect: In my case, I can renumber #1 -> #3, then #3->#1. However, it would be a great help if port renumbering as it refers to configuration wasn't just a vague thing that would happen on reload, but was described better, and the original question still hasn't been answered, either. (Thus, I'm looking to swap members #1 and #3.) To lock this down, I need to specify it, and reload the entire stack, before having someone move the uplink. However, for neatness (and ease of management, like you describe,) our stacks are always set up with ascending numbers as you descend in the cabinet, and that is still the other way around in this stack. Uplink (just one yet) will be moved to the first mGig switch, and a second one added. However, most users will be connected to the mGig switches, and the first (lower grade model) switch will mostly be used for low priority traffic, like building automation. They thus became #2 and #3, respectively, despite being much superior models to the older one. Later, the ordered mGig switches arrived, and we added two of those to the first one. The stack was first implemented with a switch we had in stock, just to start connecting building automation, still during building. You kind of just described my latest use case: I have a 3-switch stack in a new building an hour away. It is ok you sitting next to stack have 1 stack, if you have 100 or 1000 stacks in the network hard to manage engineers running in the ground for no reason, so that is the reason standard operation policy should be in place, how you config the switch - easy for troubleshoot and replacement. priority who will be the master and memeber (you can also disable some device not to elect as master).Ībove practice done to make it standard, also most cases you only may have 2 uplinks, so Master and Slave should be Sw1 and Sw2 (since other stack members have no uplink modules, if that switch elect as master, then there is no reachability from network to device) Switch number to tied up the ports numbersĢ. sure you looking to more ground running for no reason to check where the users conencted.ġ. If renumbering just makes my stack neater, that's my decision, right? it matter, when the switch reboot, who ever come first they will become master,as per the stack master election process.Īlso switch numbering in terms of port allocation gi 1/0/1 (sw1) G2/0/1 (sw2). Why does the reason for renumbering matter?
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |