Thanks for all these details, Dave. We want stack mode so we can manage all switches with one page and so we can use LAG on multiple switches. My concern now isn't that the stack isn't a ring, but that I can't see whether it is or not. In proper ring operation it shows one link down. That misinformation hides whether that link is actually physically down or just displaying that way. Is there any way around that? The illustration you have with LAG ring on the switches is intended as a substitute for stack mode? We actually need a LAG ring anyway just to keep transfer rates between the switches decent. Thanks. John, ... View more

Thanks, Dave. Certainly I can see a ring that has been broken twice resulting in two chains. Goal, however, is to see first break of ring which results in a chain so I can fix it before a second break creates two chains and thus destroys the stack. As it stands now, I cannot tell if a "link down" message is a real physical failure causing ring to be a chain, or just a logical adjustment by the switch to avoid a loop. Only after another second physical failure would it become clear that the first was physical and not logical and that is too late to do me any good. I also see a fault in the least cost algorithm as a ring provides option for data to travel shortest direction. If ring is purposely broken into chain by the switch then some paths become longer. In short, I would hope ring would remain instact and internal routing (STP for example) would handle shortest path and avoiding looping communications. However most important is for me to be able to see a physical failure remotely at first occurence. Any ideas how to do this? Thanks. John, ... View more