[c-nsp] stp on me3600 on efp's with locally connected older switch

[Waris Sagheer (waris)]

Team,
MST AG is in roadmap to solve this problem.

Best Regards,

Waris Sagheer
Technical Marketing Manager
Service Provider Access Group
waris at cisco.com
Phone: +1 408 853 6682
Mobile: +1 408 835 1389

CCIE - 19901

 <http://www.cisco.com/>

 Think before you print.
This email may contain confidential and privileged material for the sole
use of the intended recipient. Any review, use, distribution or disclosure
by others is strictly prohibited. If you are not the intended recipient
(or authorized to receive for the recipient), please contact the sender by
reply email and delete all copies of this message.
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/index.html






On 2/8/13 9:27 AM, "Christian Meutes" <christian at errxtx.net> wrote:

>> There isn't much you can do afaik: STP on ACs (CE-only, and consistent
>>port configurations / prone PVSTP), waiting for MST-AG or even MC LAG,
>>keep away from loop-capable ACs per L2 site.
>
>I'am really missing here s/w support for H-VPLS based setups. Currently I
>see no way other then running full STP on ME-based PEs to solve problem
>of blackholing on hubs when customer STP converges. With STP on PE, TCN
>there triggers LDP MAC withdrawal message to hub[s], hence hub[s] can
>flood to customer site over all remaining PWs until MACs are learned via
>new PW. 
>
>One solution would be to ship MSTAG also with ME code, which can catch
>TCNs, feed LDP for withdrawal, without actually running any STP
>topologies. 
>
>Even simpler would be to let MST or MSTAG on hubs inside of VFI-based
>bridge-domain working, plain customer TCN processing would be sufficient
>here. That way SP network would only be involved in MAC table flushing on
>TCN reception - real STP only in customer equipment, which cares about
>topology.
>
>Cisco, any plans here?
>_______________________________________________
>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/