|
Hi, Cisco declare some restriction for propagation BPDU across EoMPLS cloud, may be this decision for your problem... The following
restrictions apply to using trunks with EoMPLS: you must disable the supervisor engine spanning tree for the Ethernet-over-MPLS VLAN. This ensures that the EoMPLS VLANs are carried only on the trunk to the customer router. Otherwise, the BPDUs are directed to the supervisor engine and not to the EoMPLS cloud. – The native VLAN of a trunk must not be configured as an EoMPLS VLAN. http://www.cisco.com/en/US/docs/routers/7600/ios/12.2SXF/configuration/guide/pfc3mpls.html#wp1279824 Mateusz Blaszczyk пишет: you could probably do something like this R1 ==(trunk)== Q1 -- R2 --(MPLS cloud)-- R3 -- Q2 ==(trunk)== R4Where Q1 and Q2 would on the trunk side: switchport mode dot1q-tunnel switchport access vlan QinQ l2tunnel-protocol STP and then the "tunneled" STP may get forwarded via xconnect. Specifically Q1-R2 function could be done on R2 with an external loop. But that is just a workaround not a solution. And I wouldn't do it. A solution would be to extended mpls towards R1 and R4 but that probably is not possible. Best Regards, -mat On 11 March 2010 09:09, Gert Doering <[email protected]> wrote: |
_______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
