[c-nsp] Deploying MSTP

[Jay Nakamura]

We have made a pretty clear decision on sticking with one vendor and
not inter-operate on MSTP level.  So we are safe on that front.

Our long term goal is to move to some kind of MPLS Ethernet tunneling
at some point and not rely on STP as much as possible but our budget
does not allow it yet.  In the mean time we have to use STP to achieve
redundancy.

On Tue, Dec 27, 2011 at 5:00 PM, Mack McBride <mack.mcbride at viawest.com> wrote:
> Interactions with legacy gear that does not support MSTP or does not support it the same way.
> That is the biggest headache during transition.
> After transition the biggest headache is making vlan changes as you noted.
>
> LR Mack McBride
> Network Architect
>
> -----Original Message-----
> From: cisco-nsp-bounces at puck.nether.net [mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of Jay Nakamura
> Sent: Tuesday, December 27, 2011 2:16 PM
> To: cisco-nsp
> Subject: [c-nsp] Deploying MSTP
>
> Are there anything special with MSTP that I should consider in deploying in a network?
>
> Only thing I can think of is to pre-configure VLANs for future use since topology will re-converge every time you add a VLAN to the MSTP instance.
>
> Any other special issues I should be looking out for?
>
> Thanks!
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/