On (2012-11-28 09:55 +0100), Gert Doering wrote: > > I'm sure there are topologies in which mst is suitable > > Textbook topologies, obviously :-) - where you sit down, design your > network, implement it, *and then go elsewhere* instead of modifying > your network on-the-fly.
We've ran MST as long as it's been in IOS. Mostly in metrorings. We have 4 instances, for not particular reason but somewhat even VLAN divisors. But they all have always been using same topology. And we never touch the MST config, nor have ever had the need to do it. We could do some micro-optimization to make sure that metroVLAN which is terminated to eastPE has eastPE as root and meteroVLAN which is terminated to westPE has westPE as root. And we could then define 1-2000 are westPE terminated VLANs and 2001-4000 are eastPE terminated VLANs. But we're not even doing this, if we'd want to do it, we wouldn't need to touch MST config. I know I don't see eye-to-eye to this with Gert, but I think MST is perfectly usable in most networks if you design the network and you have system to allocate VLANs. Quite few networks actually need unique topology per VLAN without it being hard-to-observe micro-optimization. But there certainly are some how can capitalize on it. But for completely other (numerous) reasons, we're ditching whole L2 and rocking MPLS end to end. -- ++ytti _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
