Routing

Hello All, 

I have the following issue. I have RSVP LSPs between R1, R3, R4 and R5. The LSPs which are between the directly connected routers are up and running but the one between R1 and R5 is not. Protocol RSVP/MPLS are enabled on all interfaces as well as interface family MPLS.  All subnets in the topology are accessable/reachable. 

config and logs available here: http://pastebin.com/kEWmRDgb

172.27.255.5
From: 172.27.255.1, State: Dn, ActiveRoute: 0, LSPname: r1-to-r5
ActivePath: (none)
LSPtype: Static Configured
LoadBalance: Random
Encoding type: Packet, Switching type: Packet, GPID: IPv4
Primary r1-strict-r4-to-r5 State: Dn
Priorities: 7 0
SmartOptimizeTimer: 180
5 Dec 16 12:24:49.760 172.27.0.22: Explicit Route: wrong delivery[11 times]
4 Dec 16 12:18:40.746 Originate Call
3 Dec 16 12:18:40.744 Clear Call
2 Dec 16 12:18:00.513 172.27.0.22: Explicit Route: wrong delivery[17 times]
1 Dec 16 12:08:01.702 Originate Call
Standby r1-alternative-to-r5 State: Dn
Priorities: 7 0
SmartOptimizeTimer: 180
2 Dec 16 12:25:20.322 172.27.0.25: Explicit Route: wrong delivery[14 times]
1 Dec 16 12:17:35.300 Originate Call
Created: Sun Dec 16 12:08:02 2012
Total 3 displayed, Up 2, Down 1

label-switched-path r1-to-r3 {
to 172.27.255.3;
}
label-switched-path r1-to-r4 {
to 172.27.255.4;
}
label-switched-path r1-to-r5 {
from 172.27.255.1;
to 172.27.255.5;
no-cspf;
primary r1-strict-r4-to-r5;
secondary r1-alternative-to-r5 {
standby;
}
}
path r1-strict-r4-to-r5 {
172.27.0.9 strict;
}
path r1-alternative-to-r5 {
172.27.0.13 strict;
}
interface all;

[edit logical-systems r1 protocols]

Hello,

If you are using explicit paths with "strict" knob, you have to enumerate/include _ALL_ interface addresses along the path's trajectory in the "path" definition.

Using only 1 "strict" IP won't get your LSP established unless this LSP is towards directly connected node.

HTH

Rgds

Alex

Hello Alex, 

I agree with you. The strict next-hop address is the address of the next-hop router. 

label-switched-path r1-to-r5 {
from 172.27.255.1;
to 172.27.255.5;
no-cspf;
primary r1-strict-r4-to-r5;
secondary r1-alternative-to-r5 {
standby;
}
}
path r1-strict-r4-to-r5 {
172.27.0.9 strict;
}
path r1-alternative-to-r5 {
172.27.0.13 strict;

Hey there,

 I agree that this configuration should work, although it's IMHO a better practise to enumerate all the hops until the endpoint, even if the endpoint is defined as 'loose' after the first/a couple of 'strict'.

 I would focus on the configuration of R5. The error "wrong delivery" is something JUNOS would throw out for instance in case the rsvp message received over an interface does not match the local address of the node/interface.

 Essentially, R5 thinks "this RSVP message is not for me".

 Cheers,

Hello,

---

nabromov@gmail.com wrote:

Hello Alex, 

 

I agree with you. The strict next-hop address is the address of the next-hop router. 

 

}
path r1-strict-r4-to-r5 {
172.27.0.9 strict;
}
path r1-alternative-to-r5 {
172.27.0.13 strict;

 

---

Your path "r1-strict-r4-to-r5" is not complete because it does not include any IP addresses on tailend/r5. According to your diagram ,it should be

172.27.0.9 strict

172.27.0.22 strict

HTH

Alex

Hi Alex, 

I tried that yesterday.  This is a lab emulation from the Juniper bootcamp course and they are also using just single 'strict'  next-hop in the official solution. 

Thank you once again for helping.

}
path r1-strict-r4-to-r5 {
172.27.0.9 strict;
172.27.0.22 strict;
}

R1 show mpls lsp exten logical-system r1 ->> 

172.27.255.5
From: 172.27.255.1, State: Dn, ActiveRoute: 0, LSPname: r1-to-r5
ActivePath: (none)
LSPtype: Static Configured
LoadBalance: Random
Encoding type: Packet, Switching type: Packet, GPID: IPv4
Primary r1-strict-r4-to-r5 State: Dn
Priorities: 7 0
SmartOptimizeTimer: 180
Computed ERO (S [L] denotes strict [loose] hops): (CSPF metric: 2)
172.27.0.9 S 172.27.0.22 S
2913 Dec 17 10:15:32.466 172.27.0.22: Explicit Route: wrong delivery[3 times]
2912 Dec 17 10:15:23.459 CSPF: computation result accepted 172.27.0.9 172.27.0.22
2911 Dec 17 10:15:03.817 172.27.0.22: Explicit Route: wrong delivery[3 times]
2910 Dec 17 10:14:54.809 CSPF: computation result accepted 172.27.0.9 172.27.0.22
2909 Dec 17 10:14:34.841 172.27.0.22: Explicit Route: wrong delivery[3 times]
2908 Dec 17 10:14:25.835 CSPF: computation result accepted 172.27.0.9 172.27.0.22
2907 Dec 17 10:14:05.304 172.27.0.22: Explicit Route: wrong delivery[3 times]
2906 Dec 17 10:13:56.298 CSPF: computation result accepted 172.27.0.9 172.27.0.22
2905 Dec 17 10:13:36.571 172.27.0.22: Explicit Route: wrong delivery[3 times]
2904 Dec 17 10:13:27.564 CSPF: computation result accepted 172.27.0.9 172.27.0.22
2903 Dec 17 10:13:07.109 172.27.0.22: Explicit Route: wrong delivery[3 times]
2902 Dec 17 10:12:58.102 CSPF: computation result accepted 172.27.0.9 172.27.0.22
2901 Dec 17 10:12:37.390 172.27.0.22: Explicit Route: wrong delivery[3 times]
2900 Dec 17 10:12:28.384 CSPF: computation result accepted 172.27.0.9 172.27.0.22
2899 Dec 17 10:12:07.817 172.27.0.22: Explicit Route: wrong delivery[3 times]

I just upgraded the MX80 router to 12.2R1.3 and LSP is UP now. 

------------------------
172.27.255.5
From: 172.27.255.1, State: Up, ActiveRoute: 0, LSPname: r1-to-r5
ActivePath: r1-strict-r4-to-r5 (primary)
LSPtype: Static Configured, Penultimate hop popping
LoadBalance: Random
Encoding type: Packet, Switching type: Packet, GPID: IPv4
*Primary r1-strict-r4-to-r5 State: Up
Priorities: 7 0
SmartOptimizeTimer: 180
Computed ERO (S [L] denotes strict [loose] hops): (CSPF metric: 2)
172.27.0.9 S 172.27.0.22 S
Received RRO (ProtectionFlag 1=Available 2=InUse 4=B/W 8=Node 10=SoftPreempt 20=Node-ID):
172.27.0.9 172.27.0.22
6 Dec 17 11:50:00.778 Selected as active path: due to 'primary'
5 Dec 17 11:48:59.154 Record Route: 172.27.0.9 172.27.0.22
4 Dec 17 11:48:59.153 Up
3 Dec 17 11:48:59.121 Originate Call
2 Dec 17 11:48:59.121 CSPF: computation result accepted 172.27.0.9 172.27.0.22
1 Dec 17 11:48:29.359 CSPF failed: no route toward 172.27.0.9
Standby r1-alternative-to-r5 State: Up
Priorities: 7 0
SmartOptimizeTimer: 180
Computed ERO (S [L] denotes strict [loose] hops): (CSPF metric: 2)
172.27.0.13 S 172.27.0.25 S
Received RRO (ProtectionFlag 1=Available 2=InUse 4=B/W 8=Node 10=SoftPreempt 20=Node-ID):
172.27.0.13 172.27.0.25
6 Dec 17 11:50:00.777 Deselected as active: due to 'primary'
5 Dec 17 11:48:59.151 Selected as active path
4 Dec 17 11:48:59.150 Record Route: 172.27.0.13 172.27.0.25
3 Dec 17 11:48:59.149 Up
2 Dec 17 11:48:59.121 Originate Call
1 Dec 17 11:48:59.121 CSPF: computation result accepted 172.27.0.13 172.27.0.25
Created: Mon Dec 17 11:46:32 2012
Total 3 displayed, Up 3, Down 0