View the RSVP Log File on Transit Routers
Purpose
Transit router messages that appear in the RSVP log file can help you analyze the problem with an RSVP session. You may need to issue the clear rsvp session and clear log filename commands to ensure that your records are current. However, if your network is large with many RSVP sessions, this may not be advisable because it may take a while for all sessions to reestablish. However, the clear rsvp session command has various options you can include to minimize the effect on your network. For more information about the clear rsvp session command, see the Junos Routing Protocols and Policies Command Reference.
Action
To view the RSVP log file, enter the following Junos OS CLI operational mode commands:
Sample Output 1
user@R3> clear rsvp session user@R3> clear log rsvp-log user@R3> show log rsvp-log Jul 21 16:51:23 R3 clear-log[30656]: logfile cleared Jul 21 16:51:24 RSVP recv Path 10.0.0.1->10.0.0.5 Len=208 so-0/0/2.0 Jul 21 16:51:24 Session7 Len 16 10.0.0.5(port/tunnel ID 11956) Proto 0 Jul 21 16:51:24 Hop Len 12 10.1.13.1/0x086cd198 Jul 21 16:51:24 Time Len 8 30000 ms Jul 21 16:51:24 SrcRoute Len 20 10.1.13.2 S 10.1.36.2 S Jul 21 16:51:24 LabelRequest Len 8 EtherType 0x800 Jul 21 16:51:24 Properties Len 12 Primary path Jul 21 16:51:24 SessionAttribute Len 16 Prio (7,0) flag 0x0 "R1-to-R5" Jul 21 16:51:24 Sender7 Len 12 10.0.0.1(port/lsp ID 32) Jul 21 16:51:24 Tspec Len 36 rate 0bps size 0bps peak Infbps m 20 M 1500 Jul 21 16:51:24 ADspec Len 48 MTU 1500 Jul 21 16:51:24 RecRoute Len 12 10.1.13.1 Jul 21 16:51:24 RSVP send Path 10.0.0.1->10.0.0.5 Len=208 so-0/0/3.0 Jul 21 16:51:24 Session7 Len 16 10.0.0.5(port/tunnel ID 11956) Proto 0 Jul 21 16:51:24 Hop Len 12 10.1.36.1/0x08680264 Jul 21 16:51:24 Time Len 8 30000 ms Jul 21 16:51:24 SrcRoute Len 12 10.1.36.2 S Jul 21 16:51:24 LabelRequest Len 8 EtherType 0x800 Jul 21 16:51:24 Properties Len 12 Primary path Jul 21 16:51:24 SessionAttribute Len 16 Prio (7,0) flag 0x0 "R1-to-R5" Jul 21 16:51:24 Sender7 Len 12 10.0.0.1(port/lsp ID 32) Jul 21 16:51:24 Tspec Len 36 rate 0bps size 0bps peak Infbps m 20 M 1500 Jul 21 16:51:24 ADspec Len 48 MTU 1500 Jul 21 16:51:24 RecRoute Len 20 10.1.36.1 10.1.13.1
Sample Output 2
user@R6> clear rsvp session user@R6> clear log rsvp-log user@R6> show log rsvp-log Jul 21 17:01:21 R6 clear-log[41496]: logfile cleared Jul 21 17:01:23 RSVP recv Path 10.0.0.1->10.0.0.5 Len=208 so-0/0/3.0 Jul 21 17:01:23 Session7 Len 16 10.0.0.5(port/tunnel ID 11956) Proto 0 Jul 21 17:01:23 Hop Len 12 10.1.36.1/0x08680264 Jul 21 17:01:23 Time Len 8 30000 ms Jul 21 17:01:23 SrcRoute Len 12 10.1.36.2 S Jul 21 17:01:23 LabelRequest Len 8 EtherType 0x800 Jul 21 17:01:23 Properties Len 12 Primary path Jul 21 17:01:23 SessionAttribute Len 16 Prio (7,0) flag 0x0 "R1-to-R5" Jul 21 17:01:23 Sender7 Len 12 10.0.0.1(port/lsp ID 32) Jul 21 17:01:23 Tspec Len 36 rate 0bps size 0bps peak Infbps m 20 M 1500 Jul 21 17:01:23 ADspec Len 48 MTU 1500 Jul 21 17:01:23 RecRoute Len 20 10.1.36.1 10.1.13.1 Jul 21 17:01:23 RSVP send Path 10.0.0.1->10.0.0.5 Len=204 so-0/0/0.0 Jul 21 17:01:23 Session7 Len 16 10.0.0.5(port/tunnel ID 11956) Proto 0 Jul 21 17:01:23 Hop Len 12 10.1.56.2/0x086f9000 Jul 21 17:01:23 Time Len 8 30000 ms Jul 21 17:01:23 LabelRequest Len 8 EtherType 0x800 Jul 21 17:01:23 Properties Len 12 Primary path Jul 21 17:01:23 SessionAttribute Len 16 Prio (7,0) flag 0x0 "R1-to-R5" Jul 21 17:01:23 Sender7 Len 12 10.0.0.1(port/lsp ID 32) Jul 21 17:01:23 Tspec Len 36 rate 0bps size 0bps peak Infbps m 20 M 1500 Jul 21 17:01:23 ADspec Len 48 MTU 1500 Jul 21 17:01:23 RecRoute Len 28 10.1.56.2 10.1.36.1 10.1.13.1
Meaning
Sample Output 1 from transit router R3 shows that R3 ( so-0/0/2.0) correctly received a Path request message (recv Path) from R1, and correctly sent the Path message (send Path) through interface so-0/0/3.0 to R6. The route record object (RecRoute) indicates the list of addresses this Path message transited, in this case, 10 1.36.1 and 10.1.13.1.
Sample Output 2 from transit router R6 shows that R6 (so-0/0/3.0) correctly received a Path request message (recv Path) from R3, and correctly sent the Path message (send Path) through interface so-0/0/0 to R5. The route record object (RecRoute) indicates the list of addresses this Path message transited, in this case, 10.1.56.2, 10 1.36.1, and 10.1.13.1.
With the information above, the focus shifts to egress router R5 as the source of the problem, with indications that R5 ignored the RSVP message.