Routing

Hi 

I found my l2cirucit is working via ldp. But not while enabled RSVP with static label. 

Could some provide me some advice about how to fix it?

via LDP :

Neighbor: 192.168.146.9

    Interface                 Type  St     Time last up          # Up trans

    ge-4/0/9.0(vc 10001)      rmt   RD   

      local PW status code: 0x00000000, Neighbor PW status code: 0x00000001

    ge-4/2/9.0(vc 10002)      rmt   RD   

      local PW status code: 0x00000000, Neighbor PW status code: 0x00000001

via RSVP with static label.

Neighbor: 192.168.146.96
Interface Type St Time last up # Up trans
ge-4/0/9.0(vc 10001) rmt OL
ge-4/2/9.0(vc 10002) rmt OL  

This is the infrastructure : Router1(192.168.131.22) -- Router 2 -- Router 3 -- Router 4(192.168.146.9,192.168.146.96)

And the attached is the configuration of MPLS on those routers

thanks 

Cloud

Attachment(s)

Configuration.rtf   5 KB 1 version

Hey Cloud,

Greetings, please check out this information, if you need both signaling protocols to coexist you might want to see this: https://www.juniper.net/documentation/en_US/release-independent/nce/topics/task/configuration/layer-two-circuits-rsvp-ldp-lsp-solutions.html

If this solves your problem, please mark this post as "Accepted Solution" so we can help others too \:)/

Regards,

Lil Dexx
JNCIE-ENT#863, 3X JNCIP-[SP-ENT-DC], 4X JNCIA [cloud-DevOps-Junos-Design], Champions Ingenius, SSYB

If you need you l2circuit forwarded via label-switched-path, you can enable ldp-tunneling on this lsp. 
Or , if you want to map l2circuit to specific lsp , you can configure lsp and map l2circuit with psn-tunnel-endpoint

Hello,

First things first - in Your configs, I don't see "strict path" so either You supplied wrong configs, or Your post' title is wrong.

Secondly, there are 2 problems with Your config, namely:

a/ for  L2circuit to use RSVP transport, the L2circuit "neighbor" IP/32 must match the [RSVP/7] /32 route 

b/ for L2circuit to be Up, the [RSVP/7] /32 route must exist in inet.3 table

As I can see, Your l2circuit neighbor is 103.198.146.9 and looks like 103.198.146.9/32 route does not exist in inet.3 table.

For this L2circuit to use [RSVP/7]  route to 192.168.146.96/32, You need to do 2 things :

1/ make sure L2circuit config includes line saying "psn-tunnel-endpoint 192.168.146.96" 

https://www.juniper.net/documentation/en_US/junos/topics/reference/configuration-statement/psn-tunnel-endpoint-edit-protocols-l2circuit.html

2/ make sure  [RSVP/7]  route to 192.168.146.96/32 exists in inet.3 - You have a line in Your config saying "protocols mpls traffic-engineering bgp-igp-both-ribs" so show us Your inet.3 table

https://www.juniper.net/documentation/en_US/junos/topics/reference/configuration-statement/traffic-engineering-edit-protocols-mpls.html

HTH

Thx

Alex

Hi 

Sorry to omit the information of inet.3. I've attached the status and ensure it will be shown from inet.3. 

Please refer to this attachment. 

Also, I make sure this configuration "protocols mpls traffic-engineering bgp-igp-both-ribs"  was done before this quesiton.

Why I don't show you the strict path is I don't understand how to make it working really.

For instance blew, I don't get what defferent "strict" and "loose".

Strcit --> must be IP learning from direct routes ?

Lose  --> any IP from routing table and don't need that it's the end point ?

label-switched-path KMH05-HKG02-VC {
to 192.168.146.96;
primary KMH05-HKG02-VC-P;
secondary KMH05-HKG02-VC-S;
}
path KMH05-HKG02-VC-P {
192.168.131.26 strict;
192.168.146.96 loose;
}
path KMH05-HKG02-VC-S {
192.168.131.46 strict;
192.168.146.96 loose;

thanks 

Cloud

Attachment(s)

RSVP&Inet.3.rtf   6 KB 1 version

Hello,

Thanks for sharing the printout. As expected the L2circuit "neighbor" address does not exist in Your inet.3 table and such L2circuit cannot be established.

Please follow the solution given You earlier,  using "psn-endpoint-address" knob.

---

@Cloud wrote:

 

Why I don't show you the strict path is I don't understand how to make it working really.

For instance blew, I don't get what defferent "strict" and "loose".

Strcit --> must be IP learning from direct routes ?

Lose  --> any IP from routing table and don't need that it's the end point ?

 

Please see https://tools.ietf.org/html/rfc3209#section-4.3.3

   The path between a strict node and its preceding node MUST include
   only network nodes from the strict node and its preceding abstract
   node.

   The path between a loose node and its preceding node MAY include
   other network nodes that are not part of the strict node or its
   preceding abstract node.

In plain English - the strict path MUST include all specified IP addresses with "strict" tag and only these IP addresses, and such path must be loop-free.

The loose path MUST include all specified IP addresses with "loose" tag, does not matter if there are intermediate IPs in between, and such path must be loop-free.

With strict path, the interface IP of the tailend must be included. Which interface - up to You to decide. WIth loose path, You don't need to include tailend interface' IP into the path.

Nevertheless, this strict/loose discussion is not related to Your L2circuit problem, You are simply missing a "psn-endpoint-address" knob under [protocols l2circuit neighbor] .

HTH

Thx

Alex

Hi 

Thanks for your prompt reply.

My plan for L2 circuit via RSVP label is as follow :

         lo0:192.168.131.10                                               lo0:192.168.146.9           

Router1(192.168.131.22) -- Router 2 -- Router 3 -- Router 4(192.168.146.96).

So, my l2circuit's neighbors are 192.168.131.22 and 192.168.146.96 on Router1 and Router 4.

And also exist on inet.3 table after I checked. 

Is it correct my psn-endpoint-address 192.168.131.22 and 192.168.146.96 ?

Router1> show configuration protocols l2circuit

neighbor 192.168.146.96 {

    interface ge-4/0/9.0 {

        psn-tunnel-endpoint 192.168.146.96;

        virtual-circuit-id 10001;

        control-word;                   

        mtu 8800;

        encapsulation-type ethernet;

        pseudowire-status-tlv;

    }

    interface ge-4/2/9.0 {

        psn-tunnel-endpoint 192.168.146.96;

        virtual-circuit-id 10002;

        control-word;

        mtu 8800;

        encapsulation-type ethernet;

        pseudowire-status-tlv;

    }

}

BTW, thanks for the explanation of strict and loose.

Router1> show route 192.168.131.22 table inet.3

inet.3: 41 destinations, 41 routes (41 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

192.168.131.22/32 *[RSVP/7/1] 20:03:10, metric 25
> to 192.168.146.101 via ae1.1, label-switched-path HKG02-KMH05-VC
   to 192.168.146.45 via ae0.0, label-switched-path HKG02-KMH05-VC

Router 4> show route 192.168.146.96 table inet.3

inet.3: 41 destinations, 45 routes (41 active, 0 holddown, 4 hidden)
+ = Active Route, - = Last Active, * = Both

192.168.146.96/32 *[RSVP/7/1] 01:14:59, metric 25
> to 192.168.131.26 via xe-1/2/1.0, label-switched-path KMH05-HKG02-VC
   to 192.168.131.46 via xe-1/1/3.0, label-switched-path KMH05-HKG02-VC

Cloud

Hello,

I sense a change of narrative here.

Your L2circuit neighbor address on Router1 was either 192.168.146.9 in this post:

https://forums.juniper.net/t5/Routing/L2circuit-via-RSVP-with-strict-path/m-p/475688/highlight/true#M21206

or or 103.198.146.9 in attachment to the same post.

192.168.146.9 does NOT exist in Your inet.3 table on Router1.

103.198.146.9 does not exist in Your inet.3 table on Router1.

That's where and why You need "psn-endpoint-address" in the above situation.

Now You are saying Your L2circuit neighbor somehow becomes 192.168.131.22 as seen by Router1 and You have 192.168.131.22 in inet.3 table on Router1.

Asuuming 192.168.131.22 is the Router4 router-id and 192.168.131.96 is the Router1 router-id , please go ahead and on R1 configure the usual L2circuit neighbor 192.168.131.22, You don't need "psn-endpoint-address" knob here.

Don't forget to put reciprocal configuration on Router4.

HTH

Thx

Alex

Hi 

Sorry to make you confused. 

192.168.146.9 is my Router4's loop back address for ISIS/LDP/iBGP to connect.

So, it has ldp label there and working.

Now I hope to add additional address in this loopback as second address for RSVP.

Just like I said 192.168.146.96(Router4) and 192.168.131.22(Router1).

And I also test strict path for l2circuit bwtween new address and don't affect our ldp environment.

So, I don't need "psn-endpoint-address" anymore in my l2circuit configuration ?

I just confuse that l2cirucit is working via LDP, but seems not work via RSVP

thanks 

Cloud 

Hello,

---

@Cloud wrote:

 

192.168.146.9 is my Router4's loop back address for ISIS/LDP/iBGP to connect.

So, it has ldp label there and working.

---

Ok good. Let me guess - 192.168.146.9 is the Router4 router-id then?

---

@Cloud wrote:

Now I hope to add additional address in this loopback as second address for RSVP.

Just like I said 192.168.146.96(Router4) and 192.168.131.22(Router1).

 

---

Right, then it looks like 192.168.146.96 is not the Router4 router-id and  192.168.131.22 is not the Router1 router-id.

---

@Cloud wrote:

And I also test strict path for l2circuit bwtween new address and don't affect our ldp environment.

 

So, I don't need "psn-endpoint-address" anymore in my l2circuit configuration ?

I just confuse that l2cirucit is working via LDP, but seems not work via RSVP

 

---

Let me explain why it works over LDP:

1/ by default JUNOS LDP uses router-id as transport endpoint and

2/ JUNOS L2circuit expects the control connection to be made to the router-id IP.

When You add secondary loopback and keep the old router-id then L2circuit needs to be told that remote transport endpoint is now NOT the router-id anymore. So, You need "psn-endpoint-address" in this situation.

For this L2circuit, on Router1 , the "psn-transport-address 192.168.146.96" line is required.

For this L2circuit, on Router4,  the "psn-transport-address 192.168.131.22" line is required.

HTH

Thx

Alex

Hi 

You're right. 192.168.146.9  is the router ID of Router4. And 192.168.131.10 is the router ID of router1.

It's running via LDP and working.

Now I added two IP for RSVP with strict path for specific purpose.

thanks for your advice about "psn-endpoint-address". 

I will add this function on l2circuit and see if work well. Then accpet your reply as answer.

Best regards,

Cloud

You can run this only with RSVP. For L2CIRCUIT, it only works with LDP to assign inner label. The outer label can be RSVP or LDP or whatever. If you need only RSVP, you would need to think about other L2 VPN like bgp based L2VPN, VPLS, EVPN

Hi 

Does that mean what I can't pick RSVP with strict path for l2circuit connection? 

I added second address for loopback of two sides router and hope I can control it's routing path for certain sakes. And won't affect current LDP environment. 

But looks like it still has not outging labels. 

Router1> show l2circuit connections 

<omit>

OL -- no outgoing label

<omit>

Neighbor: 192.168.146.96
Interface Type St Time last up # Up trans
ge-4/0/9.0(vc 10001) rmt OL
ge-4/2/9.0(vc 10002) rmt OL

thanks