On Tue, Nov 27, 2012 at 03:22:27PM -0500, Chuck Church wrote: > Just curious, is the VLAN mapping to instances the big issue you guys have > with MST? In our deployments we used pretty large ranges to cover growth, > and mapped purposes such as L2-only VLANs (no SVI), servers, users, VoIP, > etc into separate instances, worked pretty solidly. Except when Nexus > changes the mappings on you because some are reserved that is... > > Chuck >
In our last test in the datacenter environment, we had deployed MSTP according to Cisco recommended practices (pre-map all vLANs). This wasn't a large issue to us, as we really only have 2 paths through our datacenter fabric. However, on the Dell side, with the PowerConnect 5324s we tested, mapping a vLAN to an MSTP instance attempted to create the vLAN on the Powerconnect. This was a non-starter, and we stopped evaluating the platform. The test we did crashed the Powerconnect as it attempted to create 4000+ vLANs at once. -- Brandon Ewing ([email protected])
pgpylZs81Xeyw.pgp
Description: PGP signature
_______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
