[j-nsp] RSVP LSP inconsistency
David Ball
davidtball at gmail.com
Fri Jan 19 17:58:12 EST 2007
I have 2 T640s running 8.1R5 connected via 10GigE. OSPF and BGP
are up and exchanging routes. I have LDP configured and is building
LSPs as expected, and traffic is passing. I've also configured RSVP
on both routers, and it...almost...works.
The issue I'm seeing is that according to 1 of the T640s, both
ingress and egress RSVP-signalled LSPs are 'Up'. However, according
to the other router, only 1 of them is up. I can't think of how it
may be possible that 2 routers think differently about the current
state of the same LSP. Was hoping someone here might have an idea.
I've already opened a TAC case, but I have yet to hear anything.
Thought I might try you good folks concurrently. Thanks in advance for
any guidance.
First, a 'show rsvp session from ROUTER1:
dball at ROUTER1-re0> show rsvp session
Ingress RSVP: 1 sessions
To From State Rt Style Labelin Labelout LSPname
1.7.1.22 1.7.1.1 Up 0 1 FF - 3
NCP-LSP-00813-001-022
Total 1 displayed, Up 1, Down 0
Egress RSVP: 1 sessions
To From State Rt Style Labelin Labelout LSPname
1.7.1.1 1.7.1.22 Up 0 1 FF 3 -
NCP-LSP-00820-022-001
Total 1 displayed, Up 1, Down 0
Transit RSVP: 0 sessions
Total 0 displayed, Up 0, Down 0
dball at ROUTER1-re0>
And now, a 'show rsvp session' from ROUTER2, showing the same 2 LSPs,
but in different states:
dball at ROUTER2-re0> show rsvp session
Ingress RSVP: 1 sessions
To From State Rt Style Labelin Labelout LSPname
1.7.1.1 1.7.1.22 Dn 0 0 - - -
NCP-LSP-00820-022-001
Total 1 displayed, Up 0, Down 1
Egress RSVP: 1 sessions
To From State Rt Style Labelin Labelout LSPname
1.7.1.22 1.7.1.1 Up 0 1 FF 3 -
NCP-LSP-00813-001-022
Total 1 displayed, Up 1, Down 0
Transit RSVP: 0 sessions
Total 0 displayed, Up 0, Down 0
dball at ROUTER2-re0>
A bit more info from ROUTER2 (the router that sees 1of the LSPs as 'Dn':
dball at ROUTER2>show mpls lsp extensive
<snip>
1.7.1.1
From: 1.7.1.22, State: Dn, ActiveRoute: 0, LSPname: NCP-LSP-00820-022-001
Description: NCP-LSP-00820-022-001
ActivePath: (none)
FastReroute desired
LoadBalance: Random
Encoding type: Packet, Switching type: Packet, GPID: IPv4
Primary State: Dn
OptimizeTimer: 30
SmartOptimizeTimer: 180
Reoptimization in 12 second(s).
Computed ERO (S [L] denotes strict [loose] hops): (CSPF metric: 1)
1.7.2.21 S
9283 Jan 19 15:36:30.800 Originate Call
9282 Jan 19 15:36:30.800 Clear Call
9281 Jan 19 15:36:30.800 CSPF: computation result accepted 1.7.2.21
9280 Jan 19 15:36:01.368 Originate Call
9279 Jan 19 15:36:01.368 Clear Call
9278 Jan 19 15:36:01.368 CSPF: computation result accepted 1.7.2.21
9277 Jan 19 15:35:32.356 Originate Call
9276 Jan 19 15:35:32.356 Clear Call
<snip>
And finally, the log entries. I can't find decently descriptive info
on what the 'RSVP error' lines mean. Found what 'code 4' means, but
not much in the way of what I should/could do to fix it.
dball at ROUTER2>show log rsvp (traceoptions are set to 'packets' and 'error')
Jan 19 15:35:05.474619 RSVP send Path 1.7.1.22->1.7.1.1 Len=248 ge-0/0/0.0
Jan 19 15:35:05.585878 RSVP recv Ack 1.7.2.1->1.7.2.22 Len=20 ge-0/0/0.0
Jan 19 15:35:06.056029 RSVP recv SummaryRefresh 1.7.2.1->1.7.2.22
Len=24 ge-0/0/0.0
Jan 19 15:35:06.056114 RSVP send Ack 1.7.2.22->1.7.2.1 Len=20 ge-0/0/0.0
Jan 19 15:35:06.056176 RSVP recv Path 1.7.2.1->1.7.2.22 Len=248 ge-0/0/0.0
Jan 19 15:35:06.056189 RSVP send Ack 1.7.2.22->1.7.2.1 Len=20 ge-0/0/0.0
Jan 19 15:35:06.185954 RSVP recv Resv 1.7.2.1->1.7.2.22 Len=132 ge-0/0/0.0
Jan 19 15:35:06.185999 RSVP send Ack 1.7.2.22->1.7.2.1 Len=20 ge-0/0/0.0
Jan 19 15:35:06.186053 RSVP error, recv resv no path info Resv
1.7.2.1->1.7.2.22 Len=132
Jan 19 15:35:06.186067 RSVP error, originate ResvErr ResvErr
1.7.2.22->1.7.2.1 Len=8 code 4 subcode 0
Jan 19 15:35:06.186075 RSVP send ResvErr 1.7.2.22->1.7.2.1 Len=104 ge-0/0/0.0
David
More information about the juniper-nsp
mailing list