Thats interesting - it might be worth playing around & testing - is there a command / way to speed test a 'theoretical' transfer between two lagged switches (which I have setup already)?Stacking and a simple LAG trunk are two very different things. Also, be aware that in a LAG while you'd have 30Gb of aggregate bandwidth, you'll see single stream speeds no faster than 10Gb. I am unsure how bandwidth works over stacking, having never deployed it; I suspect it's a LAG underneath along with extra settings for the various coordination required for stacking and failover.
I have two 7250's I can setup as a standalone stack to test - again assuming I can use a command to do a speed test.
Thats interesting - does this mean if I have 3 switches,For ICX 7k series, the default is hitless stacking; and whichever unit has highest stack priority is the master; upon failure, next highest takes over; see Traditional stack unit priority (ruckuswireless.com)
stack ID #1 (priority 100)
stack ID #2 (priority 50)
stack ID #3 (priority 10)
If #1 dies, does that mean #2 is the new master and reprograms the other switches?
If Stack ID #4 (priority 5) is added, will it be auto reprogrammed by #2?
If so, if I change Stack ID #4 to Priority 100 - will it be the new master & take all its existing info & send it down stream?
I am equating it to a raid rebuild (sort of).