Are you sure if R3 is forwarding path message to R4?
I just cheked in lab and not seeing this behavior.
In lab, since interface to R5 is not part of rsvp/mpls, R3 itself is sending back the error.
1. From tcpdump , no rsvp path message to R4.
lab@Haf-Arun-re1# run monitor traffic interface fe-1/0/2.30 size 1500
verbose output suppressed, use <detail> or <extensive> for full protocol decode
Address resolution is ON. Use <no-resolve> to avoid any reverse lookup delay.
Address resolution timeout is 4s.
Listening on fe-1/0/2.30, capture size 1500 bytes
Reverse lookup for 224.0.0.5 failed (check DNS reachability).
Other reverse lookup failures will not be reported.
Use <no-resolve> to avoid reverse lookups on IP addresses.
06:24:41.067950 In IP 30.30.30.1 > 224.0.0.5: OSPFv2, LS-Update, length 92
06:24:41.756728 Out IP 30.30.30.2 > 224.0.0.5: OSPFv2, Hello, length 48
06:24:42.070981 Out IP 30.30.30.2 > 224.0.0.5: OSPFv2, LS-Ack, length 44
06:24:43.030094 Out IP 30.30.30.2 > 224.0.0.5: OSPFv2, LS-Update, length 60
06:24:44.033464 In IP 30.30.30.1 > 224.0.0.5: OSPFv2, LS-Ack, length 44
06:24:45.331681 In IP 30.30.30.1 > 224.0.0.5: OSPFv2, Hello, length 48
06:24:49.431532 Out IP 30.30.30.2 > 224.0.0.5: OSPFv2, Hello, length 48
06:24:53.563404 In IP 30.30.30.1 > 224.0.0.5: OSPFv2, Hello, length 48
06:24:59.418963 Out IP 30.30.30.2 > 224.0.0.5: OSPFv2, Hello, length 48
06:25:02.268963 In IP 30.30.30.1 > 224.0.0.5: OSPFv2, Hello, length 48
06:25:08.991457 Out IP 30.30.30.2 > 224.0.0.5: OSPFv2, Hello, length 48
06:25:11.278604 In IP 30.30.30.1 > 224.0.0.5: OSPFv2, Hello, length 48
06:25:17.749075 Out IP 30.30.30.2 > 224.0.0.5: OSPFv2, Hello, length 48
06:25:19.232007 In IP 30.30.30.1 > 224.0.0.5: OSPFv2, Hello, length 48
06:25:27.198653 In IP 30.30.30.1 > 224.0.0.5: OSPFv2, Hello, length 48
06:25:27.379556 Out IP 30.30.30.2 > 224.0.0.5: OSPFv2, Hello, length 48
06:25:36.329655 In IP 30.30.30.1 > 224.0.0.5: OSPFv2, Hello, length 48
06:25:37.135011 Out IP 30.30.30.2 > 224.0.0.5: OSPFv2, Hello, length 48
2. Bad strict route reported by R3
lab@Haf-Arun-re1# run show mpls lsp logical-system 1HLR extensive
Apr 11 06:24:24
Ingress LSP: 1 sessions
4.4.4.4
From: 1.1.1.1, State: Dn, ActiveRoute: 0, LSPname: test
ActivePath: (none)
LSPtype: Static Configured
LoadBalance: Random
Encoding type: Packet, Switching type: Packet, GPID: IPv4
Primary test State: Dn
Priorities: 7 0
SmartOptimizeTimer: 180
2 Apr 11 06:24:02.740 20.20.20.2: Explicit Route: bad strict route[7 times] >>>> By R3
1 Apr 11 06:21:38.728 Originate Call
Created: Wed Apr 11 06:21:38 2012
Can you please enable traceoptions in R3/R4 and check?
Also check "show mpls lsp extensive" on ingress router?
- Arun Kumar S