Routing

Hi,

Given below is the topology. We need to create an l2circuit (martini) between PE1 and PE2 between AS1 and AS2.

AS1 is Cisco enabled and AS2 is Juniper enabled.

PE1 (Cisco) ------ MPLS Cloud (AS1) ----- ASBR1 (Cisco) _______ ASBR2 (Juniper) ------- MPLS Cloud (AS2) ------ PE2 (Juniper)

Cisco talks about using "l2 vfi", e-bgp "send label", and "mpls forwarding" on the ASBR's (if both the AS'es are Cisco enabled).

Whats the Juniper equivalent of "l2 vfi"?

Thanks in advance

Anand 

Hello, 

Actually you have many options to achieve your tasks, the most simple is to enable labeled unicast for eBGP connection between AS and labeled unicast for iBGP sessions inside each AS, just don't forget to announce PEs loopback addresses via BGP. This way you'll have an end-to-end LSP between PEs.

Another method is to enable labeled unicast for eBGP connection between AS and redistribute at each ASBR PEs loopback addresses into OSPF(although it's not a good option).

Another method is to create an inter-as LSP...

Hello Dumitru,

I guess the 1st option you mentioned is inter-as option C (correct me if i am wrong).

Also please suggest the configuration for the last option mentioned by you "create inter-as LSP...".

BR,

Anand

Yes, the first option is a variation of Inter-AS option C.

Regarding Inter-AS LSPs I actually meant LSP stitching(see link bellow), it's a flexible way but you have to keep in mind that you should have the remote PE loopback address in your routing table.

http://www.juniper.net/techpubs/en_US/junos10.1/topics/usage-guidelines/mpls-configuring-lsp-stitching-cross-connects-using-ccc.html

The point is that you can create one RSVP LSP in each ISP and stitch them at the border to 3rd LSP that's going to be common for both AS, this way you'll have 3 LSPs forming one single end-to-end LSP. I'm just not sure if Cisco supports this functionality...

Hi Dumitru,

The l2circuit across autonomous-systems worked. We were already running option-C inter-connect where in we were exchanging the labeled unicast infrastructure routes (loopbacks). The availability of the far end PE loopbacks (belonging to the other AS) in the corresponding AS meant that the targeted ldp session shall come up and the VC labels could be exchanged.

Thanks 🙂

BR,

Anand

Hello,

I assume Cisco talks about this

http://www.cisco.com/en/US/docs/ios/12_0s/feature/guide/fsstitch.html

The Juniper near-equivalent would be iw0 interface

http://www.juniper.net/techpubs/en_US/junos11.1/topics/concept/layer-2-circuit-layer-2vpn-overview.html

http://forums.juniper.net/t5/Routing/iw-interfaces-and-stitching-pseudowires/td-p/18523

However, you can save yourself a bit of config effort if you just use MPLS/L2circuit over GRE (CSCO name "AToM over GRE") end-to-end (CSCO "PE-to-PE tunneling"), it should be supported on both CSCO and JNPR though I haven't tested this myself

http://www.cisco.com/en/US/docs/interfaces_modules/shared_port_adapters/configuration/6500series/76cfgeth.html#wp1173777

HTH

Rgds

Alex