Hi, Can you share the output of:
show route table inet.3 5.1.1.2 (ASN1234) show route table inet.3 5.1.1.1 (ASN 4321) show ldp database l2circuit -- on both PEs Alex, imho redistributing ldp through egress-policy wouldn't stitch mpls transport (assume LDP) b/w remote PEs(domains). Using ldp peering b/w ASBRs (since IGP is redistributed) should be enough since LDP downstream unsolicited with ordered control is default for J/C. Best Regards, Krasi On Tue, Nov 20, 2012 at 1:07 PM, Peter Nyamukusa <peternyamuk...@yahoo.com>wrote: > Thanks Alex, > > I had already redistibuted all my loopback into my IGP and all were > reachable > > > ------------------------------------------------------------------------------------ > | Kind Regards, | > | Peter Nyamukusa | > | MCSE-2000/2003, CCNP, CCIP, CCDP, CCVP, | > | JNICIS-ent, JNCIS-er, JNCIS-Sec, JNCIA-Ex, Linux+, A+ | > > ------------------------------------------------------------------------------------- > > > ________________________________ > From: Alex Arseniev <alex.arsen...@gmail.com> > To: Peter Nyamukusa <peternyamuk...@yahoo.com>; > juniper-nsp@puck.nether.net > Sent: Tuesday, November 20, 2012 12:28 PM > Subject: Re: [j-nsp] Fw: L2 Circuits accross domains > > You should have remote loopbacks also redistributed into LDP (if your > transport label is from LDP). > In JUNOS, this does not happen by default, you must have LDP egress-policy > for this to occur. By default, LDP announces only primary lo0.0 IP@. > Absent this, your L2circuits would show OL error (no outgoing label). > Before you ask, this is totally different to CSCO IOS which announces all > routes (bar BGP ones) as LDP FECs. > HTH > Rgds > Alex > > ----- Original Message ----- From: "Peter Nyamukusa" < > peternyamuk...@yahoo.com> > To: <juniper-nsp@puck.nether.net> > Cc: <pe...@nyamukusa.com> > Sent: Tuesday, November 20, 2012 7:46 AM > Subject: [j-nsp] Fw: L2 Circuits accross domains > > > ----- Forwarded Message ----- > > From: Peter Nyamukusa <peternyamuk...@yahoo.com> > To: "juniper-nsp@puck.nether.net" <juniper-nsp@puck.nether.net> > Sent: Tuesday, November 20, 2012 9:33 AM > Subject: L2 Circuits accross domains > > > Hi Folks, > > I have an exsisting L3 / L2 MPLS network with Cisco ASR on the Core as PE > router and Junper routers as PE router, i have been running l2circuits > sucessfully for some time now with out any problems using the below configs > on my PEs, I am running IS-IS as my IGP and BGP > > > > [edit protocols l2circuit] > peter@xxx-PE1# show > > } > neighbor 41.x.x.1 { > interface ge-0/0/2.2001 { > virtual-circuit-id 2001; > description "XYZ L2"; > no-control-word; > > ignore-mtu-mismatch; > > [edit interfaces ge-0/0/2] > peter@xxx-PE1# show > description "Customers L2 Circuits"; > vlan-tagging; > encapsulation vlan-ccc; > unit 2001 { > description "XYZ L2"; > encapsulation vlan-ccc; > vlan-id 2001; > } > > Neighbor: 41.x.x.2 > Interface Type St Time last up # Up trans > ge-0/0/2.2001(vc 2001) rmt Up Nov 13 15:29:31 2012 1 > Remote PE: 41.x.x.2, Negotiated control-word: No > Incoming label: 299776, Outgoing label: 299776 > Local interface: ge-0/0/2.2001, Status: Up, Encapsulation: > VLAN > Description: XYZ L2 > Neighbor: 41.x.x.x.1 > Interface Type St Time last up # Up trans > ge-0/0/2.2101(vc 2101) rmt Up Nov 13 15:29:28 2012 1 > Remote PE: 41.x.x.1, Negotiated control-word: Yes (Null) > Incoming label: 299792, Outgoing label: 333568 > Local interface: ge-0/0/2.2101, Status: Up, Encapsulation: VLAN > Description: ABC L2 - ANY POP > > > > Now I am trying to extend these L2 circuits to anther MPLS Domain where we > have direct Gigabit fibre connection I am using the same concept and > establish ospf peering on the ASBR router with the remote ASN and > redistributed my IGP so my loopbacks are seen by the PEs on both sides of > the domains and establish ldp peering how ever the l2circuit is not coming > up any help is appriciated as I have been working on this more than 24hrs > and think that i am now a bit clouded > > > peter@yyy-BR1# run show l2circuit connections (ASN 1234) > Layer-2 Circuit Connections: > > Legend for connection status (St) > EI -- encapsulation invalid NP -- interface h/w not present > MM -- mtu mismatch Dn -- down > EM -- encapsulation mismatch VC-Dn -- Virtual > circuit Down > CM -- control-word mismatch Up -- operational > VM -- vlan id mismatch CF -- Call admission control failure > OL -- no outgoing label IB -- TDM incompatible bitrate > NC -- intf encaps not CCC/TCC TM -- TDM misconfiguration > BK -- Backup Connection ST -- Standby Connection > CB -- rcvd cell-bundle size bad XX -- unknown > > Legend for interface status > Up -- operational > Dn -- down > Neighbor: 5.1.1.2 > Interface Type St Time last up # Up trans > ge-0/0/0.2900(vc 2900) rmt OL > > peter@xxx-PE1# run show l2circuit connections (ASN4321) > Layer-2 Circuit Connections: > > Legend for connection status (St) > EI -- encapsulation invalid NP -- interface h/w not present > MM -- mtu mismatch Dn -- down > EM -- encapsulation mismatch VC-Dn -- Virtual circuit Down > CM -- control-word mismatch Up -- operational > VM -- vlan id mismatch CF -- Call admission control failure > OL -- no outgoing label IB -- TDM incompatible bitrate > NC -- intf encaps not CCC/TCC TM -- TDM misconfiguration > BK -- Backup Connection ST -- Standby Connection > CB -- rcvd > cell-bundle size bad XX -- unknown > > Legend for interface status > Up -- operational > Dn -- down > Neighbor: 5.1.1.1 > Interface Type St Time last up # Up trans > ge-0/0/2.2900(vc 2900) rmt OL > > > > > --------------------------------------------------------------------------- > | Kind Regards, | > | Peter > Nyamukusa | > | MCSE-2000/2003, CCIP, CCDP, CCVP, CCNP, | > | JNCIS-ent, JNCIS-er, JNCIS-Sec, JNCIA-Ex, Linux+, A+ | > --------------------------------------------------------------------------- > _______________________________________________ > juniper-nsp mailing list juniper-nsp@puck.nether.net > https://puck.nether.net/mailman/listinfo/juniper-nsp > _______________________________________________ > juniper-nsp mailing list juniper-nsp@puck.nether.net > https://puck.nether.net/mailman/listinfo/juniper-nsp > _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp