[c-nsp] ME3600 - xconnect, vlan remap, and STP

Brandon Ewing nicotine at warningg.com
Tue Mar 18 09:46:28 EDT 2014


Greetings,

We are thinking about leveraging the ME3600 platform to provide MPLS
connectivity between two switch fabrics, connecting arbitrary VLANs on each
end to each other in a redundant fashion.  We have a 2 switch fabric at
location A, with each switch connected to a different ME3600 via trunk.
At location B, the same config is replicated.

We want to be able to connect arbitrary VLANs to each other on MPLS
xconnects -- IE, vlan 12 on side A is in the same broadcast domain as vlan
23 on side B.

My main concern is redundancy and loop prevention -- we want to build two
xconnects per pairing, one on each ME3600 per location, and are trying to
work out how STP protocols will work and interop in this situation.

If MSTP is used on both sides (different regions), should we just build an
xconnect for vlan 1 to vlan 1, and transport the BPDUs?

What is R-PVSTP is used on one side, and MSTP on the other?  How can we
ensure that the MST0 BPDU is replicated into each PVST instance when we are
doing the mapping?

-- 
Brandon Ewing                                        (nicotine at warningg.com)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/cisco-nsp/attachments/20140318/37f541d8/attachment.sig>


More information about the cisco-nsp mailing list