That’s correct Mark! I don’t need run BGP in every router or switch that I have, and I don’t have VPLS capable equipments in every location, but i have l2circuits equipments in every location because our business is provide l2 services for Carriers and Corporations. When VPLS p2mp or mp2mp is needed, we use l2circuits to a routing location POP and VPLS to bridge all routing location POP(PointOfPresence). With IP transit L3 customers, peering partners, upstream providers, the same.
We don’t have small users( xDSL, FTTx, GPON) só we don’t need to take care about some type of usage. We can tshoot BGP fast and discard after few minutes BGP problems, but Operation Team, NOC Team, can’t or they will be stuck at some point. Less complexity, more fast to solve the problem. att Alexandre Em 9 de jul de 2018, à(s) 07:54, Mark Tinka <mark.ti...@seacom.mu<mailto:mark.ti...@seacom.mu>> escreveu: On 9/Jul/18 11:58, adamv0...@netconsultings.com<mailto:adamv0...@netconsultings.com> wrote: That is faulty fibre causes BGP session problems but not targeted-LDP session problems? Faulty fibre will affect any control plane sessions. I think what Alexandre was trying to say is that troubleshooting the network where issues could be fibre-related is easier with LDP than with BGP, because with BGP, you now have to check iBGP sessions, routing policies (if you have them), BGP routing tables, e.t.c. This could divert your attention for longer than is necessary before you realize the fibre could be the issue. Mark. _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
