[theBobMcCormick]

I'm actually rather surprised to hear about switches that don't support MSTP. I've worked with managed switches from some rather low tier manufacturers like Milan, Allied Telesys, Adtran, etc. that still support MSTP. MSTP actually isn't that recent. It was incorporated into 802.1q in 2003, but it was introduced as an amendment to 802.1q in 802.1s way back in 1998. If you've got gear that doesn't support MSTP (or the Cisco proprietary RSTP), through it out. Failover and convergence time with original STP is atrociously slow.

At any rate, I still don't see this as a STP/VLAN problem. If you want network redundancy than clearly your redundant links need to carry all of your VLAN's. Otherwise you'll have redundancy for some VLAN's but not others. That's not STP's fault, it's just plain logic.

Not that I think STP is a great protocol mind you. It sucks in MANY ways. Just not in the ways you seem to be claiming it does. :-)

[alaricsp]

Perhaps I've just been unlucky ;-) This was Allied Telesyn kit IIRC.

But this is by the by! Rather than a damning indictment of STP, my real point was that having to configure all the layers of a network - physical cabling, VLANs, routing, firewalling - independently involves a load of effort that I'm not convinced is necessary. It'd be lovely to have routing functions occur in every switch, automatically routing between VLANs that are present together on the switch, and then doing MPLS-esque fast switching of frames across the network to destination switches if not - merging the switching and routing layers of the stack would just simplify things; why should we need the complex techniques we have to make networks resilient to failure?