I was using RSVP at the time, sorry I left that part out. If you're getting one-way traffic it might be that one of the LSPs isn't up.
--chip Sent from my mobile device, please excuse any typos. > On Nov 12, 2014, at 5:16 PM, Eduardo Schoedler <lis...@esds.com.br> wrote: > > There's no need to run "protocols ldp" ? > > -- > Eduardo Schoedler > > 2014-11-12 17:18 GMT-02:00 Alexander Arseniev <arsen...@btinternet.com>: >> There is a line missing on MX side: >> >> set interfaces lt-0/0/0.0 family ccc >> >> Thanks >> Alex >> >> 12/11/2014 16:51, Raphael Mazelier wrote: >>> >>> >>> >>> Le 11/11/14 22:29, chip a écrit : >>>> >>>> http://pastebin.com/YYfHk9M2 >>>> >>>> That should get you. *Caveats apply* but it does work =) >>>> >>>> --chip >>> >>> >>> Thks you chip. >>> >>> With your configuration I've made some progress. >>> Now I've got some arp replies on the CE connected to the EX : >>> >>> 2.1.1.5 > 2.1.1.6: ICMP echo request, id 26654, seq 11, length 64 >>> 17:42:39.031721 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has >>> 2.1.1.5 tell 2.1.1.6, length 46 >>> 17:42:39.031731 ARP, Ethernet (len 6), IPv4 (len 4), Reply 2.1.1.5 is-at >>> 78:2b:cb:28:2d:55, length 28 >>> >>> The lt mac is correctly learn on the CE. >>> But for one reason or another the mac address of the ce is not learn on >>> the mx80 side ?! >>> >>> >>> I'm just out of luck for this setup :( >> >> _______________________________________________ >> juniper-nsp mailing list juniper-nsp@puck.nether.net >> https://puck.nether.net/mailman/listinfo/juniper-nsp > > > > -- > Eduardo Schoedler _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp