On Wednesday, February 22, 2012 10:45:20 PM Scott Harvanek wrote: > I've tried many different traceoptions but nothing has > proven useful in generating an error message that can be > acted upon. Does anyone have any ideas on why a label > that exists both on the l2circuit and in mpls.0 would > not be getting inserted into the ldp database such as > this?
Can we see the Cisco side as well? That should be: #sh mpls l2transport vc 777 detail Cheers, Mark.
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ juniper-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/juniper-nsp
