otello1

Regarding the 1° above question we've made more test. If we stack 4 switch they autoconfigure for example in the following schema: 4 - master (primary) 3 - Backup 2 - Linecard 1 - Linecard If you are in ring topology there are no problems. You can cut connection at every level without issues. When you are in chain you can…

Well, so when you add a switch to the stack in a second moment and mistakenly put an ID that's already present, the stack goes crazy due to a conflict we created. But at least the graphical interface should prevent you from allowing you to enter the same value on multiple Switches already in the stack. Do you agree?

Intsead of increasing business continuity with stacking mode this is like a bomb that broke all the switches and the network. For example if you have a 2 switch stack setup and after some month you insert a third switch in this old setup forgetting to place a new ID for the new switch all the network will crash.

We have saved the configuration, disabled stacking mode but only the master switch rebooted enterning in standalone mode. So we have to remove the master one by one from the stack ? After the reboot the switch correctly show the choise "2-port-mode / 4-port-mode" stack. 2. So we have to choose the port mode only when the…

Your assumption is correct. We have some switch in stacking mode but we cannot see the option to convert from 4 to 2 port stacking mode as written in the manual. So we have to backup the configuration, return to standalone and after that?