Hi
You'll need to pre-configure your vlan mappings. This was discussed
on this list only last week. When we moved from RPVST to MST we went
from odds-and-evens mapping to "blocks of 50 vlans" mapping. It makes
the config a whole lot smaller :)
All in all it's working well and when the
When adding ports to a spanning-tree instance, spanning-tree discovers and
eliminates
loops in the topology. What your are experiencing is an "as designed"
feature of spanning tree.
You can segment your layer2 domain via PVST/PVST+ or you can segment your
layer 2 domain
using MST via customer span
On Thu, Jul 23, 2009 at 01:34:01PM -0400, Steven Fischer wrote:
> It seems that we can create VLANs with no issue, and by default, those VLANs
> are placed in the default instance, instance 0. This really isn't a
> problem, but when we move the VLAN into its proper instance, a spanning-tree
> reca
When we relocated our data center, we opted to deploy MST as the
spanning-tree protocol, given that our data center is almost exclusively
layer 2, we have a lot of vlans, and that number is only going to grow. We
have two spanning-tree MST instances, 1 and 2, and each contains the vlans
that are e
