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 -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Gert Doering Sent: Tuesday, November 27, 2012 5:47 AM To: Phil Mayers Cc: [email protected] Subject: Re: [c-nsp] Dell switches (specifically PowerConnect 7048P) and Ciscos Hi, On Tue, Nov 27, 2012 at 10:30:00AM +0000, Phil Mayers wrote: > Normally I'm not a big fan of "proprietary" protocols, but MST is so > awesomely sucky for Campus environments ("map all your VLANs to > instances before you start, and never change it" - yeah, right!) that > we mandate Cisco compatible PVST in all our edge. MST is equally awsome sucky for datacenter :-) (R-)PVST here as well, or "flexlink style" dual-uplinks where possible. gert -- USENET is *not* the non-clickable part of WWW! //www.muc.de/~gert/ Gert Doering - Munich, Germany [email protected] fax: +49-89-35655025 [email protected] _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
