Yep, definitely important to verify what VLANs are mapped to the instances. The Nexus for example reserves some VLANs that aren't obvious, so when you map them, they end up back in instance 0 with no warning. IOS didn't reserve those, so both my instance 0 and the one with high-numbered VLANs didn't match, so I had all kinds of problems till we discovered that. There is a checksum that you can get it to display that should match between all connected devices. Can't remember the command, but it worked well.
Chuck -----Original Message----- From: cisco-nsp-boun...@puck.nether.net [mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of Frédéric Loui Sent: Wednesday, December 28, 2011 6:26 AM To: Jay Nakamura Cc: cisco-nsp Subject: Re: [c-nsp] Deploying MSTP If you have a complex L2 topology and lots of VLAN per instance. VLANs per MST instance can become tedious. Might be worth to use some configuration/check scripts so as to make sure that all VLANs are bound to the right MST instance. My 2 cents ... -- Frédéric Le 27 déc. 2011 à 23:13, Jay Nakamura <zeusda...@gmail.com> a écrit : > 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.mcbr...@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-boun...@puck.nether.net >> [mailto:cisco-nsp-boun...@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@puck.nether.net >> https://puck.nether.net/mailman/listinfo/cisco-nsp >> archive at http://puck.nether.net/pipermail/cisco-nsp/ > > _______________________________________________ > cisco-nsp mailing list cisco-nsp@puck.nether.net > https://puck.nether.net/mailman/listinfo/cisco-nsp > archive at http://puck.nether.net/pipermail/cisco-nsp/ _______________________________________________ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/ _______________________________________________ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
