Display the RSVP Log File

Purpose

There are at least two ways to display the RSVP log file. After you configure and commit the tracing configuration, information is immediately sent to the log file. The log information can be displayed in real time on your computer screen with the monitor start command, or you can issue the show log filename command to display the entries already gathered in the log file.

Also, you may need to issue clear commands to ensure that your records are current. However, if your network is large with many LSPs and RSVP sessions, this may not be advisable. For more information about the clear rsvp session command, see the JUNOS Routing Protocols and Policies Command Reference.

To display the RSVP log file, follow these steps:

1. (Optional) Clear the RSVP Session and Log File
2. Display Real-Time RSVP Log Entries
3. View the RSVP Log File
4. Deactivate and Reactivate RSVP Tracing

(Optional) Clear the RSVP Session and Log File

Purpose

To ensure that the entries in the log file are current.

Action

To clear the RSVP session and log file, enter the following JUNOS command-line interface (CLI) operational mode commands:

Sample Output

user@R1> clear rsvp session

user@R1> clear log rsvp-log

Meaning

The sample output shows that the clear commands were issued correctly, with the following results:

• The RSVP sessions were reset and restarted. For more information about options for the clear rsvp session command that can limit the impact to your network, see the JUNOS Routing Protocols and Policies Command Reference.
• The contents of the log file were removed. For more information about the clear log command, see JUNOS System Basics and Services Command Reference.

Display Real-Time RSVP Log Entries

Purpose

To examine the RSVP log file in real-time to obtain more detailed information about the problem with the LSP.

Action

To display real-time log entries on your computer screen, enter the following JUNOS CLI operational mode command:

Note: To stop displaying real-time RSVP log entries on your computer screen, issue the monitor stop command. The monitor stop command does not stop tracing information from going into the RSVP log file.

Sample Output

user@R1> monitor start rsvp-log

user@R1> 
*** rsvp-log ***
Jun 16 17:12:23 R1 clear-log[9511]: logfile cleared
Jun 16 18:34:51 trace_on: Tracing to "/var/log/rsvp-log" started
Jun 16 18:35:09 RSVP send Path 10.0.0.1->10.0.0.5 Len=216 so-0/0/2.0
Jun 16 18:35:09   Session7 Len 16 10.0.0.5(port/tunnel ID 26619) Proto 0
Jun 16 18:35:09   Hop      Len 12 10.1.13.1/0x08678198
Jun 16 18:35:09   Time     Len  8 30000 ms
Jun 16 18:35:09   SrcRoute Len 28  10.1.13.2 S 10.1.36.2 S 10.1.56.1 S
Jun 16 18:35:09   LabelRequest Len  8 EtherType 0x800
Jun 16 18:35:09   Properties Len 12 Primary path
Jun 16 18:35:09   SessionAttribute Len 16 Prio (7,0) flag 0x0 "R1-to-R5"
Jun 16 18:35:09   Sender7  Len 12 10.0.0.1(port/lsp ID  3)
Jun 16 18:35:09   Tspec    Len 36 rate 0bps size 0bps peak Infbps m 20 M 1500
Jun 16 18:35:09   ADspec   Len 48 MTU 1500
Jun 16 18:35:09   RecRoute Len 12  10.1.13.1
Jun 16 18:35:27 RSVP recv Path 10.0.0.5->10.0.0.1 Len=216 so-0/0/2.0
Jun 16 18:35:27   Session7 Len 16 10.0.0.1(port/tunnel ID 23942) Proto 0
Jun 16 18:35:27   Hop      Len 12 10.1.13.2/0x08680198
Jun 16 18:35:27   Time     Len  8 30000 ms
Jun 16 18:35:27   SrcRoute Len 12  10.1.13.1 S
Jun 16 18:35:27   LabelRequest Len  8 EtherType 0x800
Jun 16 18:35:27   Properties Len 12 Primary path
Jun 16 18:35:27   SessionAttribute Len 16 Prio (7,0) flag 0x0 "R5-to-R1"
Jun 16 18:35:27   Sender7  Len 12 10.0.0.5(port/lsp ID  2)
Jun 16 18:35:27   Tspec    Len 36 rate 0bps size 0bps peak Infbps m 20 M 1500
Jun 16 18:35:27   ADspec   Len 48 MTU 1500
Jun 16 18:35:27   RecRoute Len 28  10.1.13.2 10.1.36.2 10.1.56.1
monitor stop

Meaning

The sample output shows real-time tracing information displayed on your computer screen (*** rsvp-log ***), and that display to the computer screen was started (monitor start) and then stopped (monitor stop). Even though you have stopped displaying log file entries on your screen, the tracing is still occurring on the router configured with trace options. The log file displays a Path message that was sent from R1 to R5, and another that R1 received from R5, indicating that the two unidirectional LSPs between R1 and R5 are established. For more information about Path messages, see Examining RSVP Log Messages.

If you stop monitoring to your screen and want to view the contents of the log file, use the show log filename command. For steps to view the log file, see Examining RSVP Log Messages.

View the RSVP Log File

Purpose

To examine the entries already gathered in the RSVP log file to obtain more detailed information about the problem with the LSP.

Action

To view the contents of the RSVP log file, enter the following JUNOS CLI operational mode command:

Sample Output

user@R1> show log rsvp-log
Jun 16 17:12:23 R1 clear-log[9511]: logfile cleared
Jun 16 18:34:51 trace_on: Tracing to "/var/log/rsvp-log" started
Jun 16 18:35:09 RSVP send Path 10.0.0.1->10.0.0.5 Len=216 so-0/0/2.0
Jun 16 18:35:09   Session7 Len 16 10.0.0.5(port/tunnel ID 26619) Proto 0
Jun 16 18:35:09   Hop      Len 12 10.1.13.1/0x08678198
Jun 16 18:35:09   Time     Len  8 30000 ms
Jun 16 18:35:09   SrcRoute Len 28  10.1.13.2 S 10.1.36.2 S 10.1.56.1 S
Jun 16 18:35:09   LabelRequest Len  8 EtherType 0x800
Jun 16 18:35:09   Properties Len 12 Primary path
Jun 16 18:35:09   SessionAttribute Len 16 Prio (7,0) flag 0x0 "R1-to-R5"
Jun 16 18:35:09   Sender7  Len 12 10.0.0.1(port/lsp ID  3)
Jun 16 18:35:09   Tspec    Len 36 rate 0bps size 0bps peak Infbps m 20 M 1500
Jun 16 18:35:09   ADspec   Len 48 MTU 1500
Jun 16 18:35:09   RecRoute Len 12  10.1.13.1
Jun 16 18:35:27 RSVP recv Path 10.0.0.5->10.0.0.1 Len=216 so-0/0/2.0
Jun 16 18:35:27   Session7 Len 16 10.0.0.1(port/tunnel ID 23942) Proto 0
Jun 16 18:35:27   Hop      Len 12 10.1.13.2/0x08680198
Jun 16 18:35:27   Time     Len  8 30000 ms
Jun 16 18:35:27   SrcRoute Len 12  10.1.13.1 S
Jun 16 18:35:27   LabelRequest Len  8 EtherType 0x800
Jun 16 18:35:27   Properties Len 12 Primary path
Jun 16 18:35:27   SessionAttribute Len 16 Prio (7,0) flag 0x0 "R5-to-R1"
Jun 16 18:35:27   Sender7  Len 12 10.0.0.5(port/lsp ID  2)
Jun 16 18:35:27   Tspec    Len 36 rate 0bps size 0bps peak Infbps m 20 M 1500
Jun 16 18:35:27   ADspec   Len 48 MTU 1500
Jun 16 18:35:27   RecRoute Len 28  10.1.13.2 10.1.36.2 10.1.56.1

Meaning

The sample output shows the tracing information in the rsvp-log file. The first entry shows that the log file was cleared, and the second entry shows that tracing is going to the rsvp-log file in the /var/log/ directory.

The log file displays a Path message that was sent from R1 to R5, and another that R1 received from R5, indicating that the two unidirectional LSPs between R1 and R5 are established. For more information about Path messages, see Examining RSVP Log Messages.

Deactivate and Reactivate RSVP Tracing

Purpose

When you configure and commit a tracing configuration, tracing information is immediately sent to the configured log file. The tracing activity goes on in the background and can create additional activity on the CPU. In this case, it is good practice to deactivate trace options, and then reactivate it when you need more tracing information.

Note: Implementing trace options consumes CPU resources and affects the packet processing performance.

Action

To deactivate and then reactivate tracing, enter the following JUNOS CLI operational mode command:

Sample Output

[edit protocols rsvp]
user@R1# deactivate traceoptions 

[edit protocols rsvp]
user@R1# show 
inactive: traceoptions {
    file rsvp-log;
    flag error detail;
    flag path detail;
    flag pathtear detail;
}
interface so-0/0/0.0;
interface so-0/0/1.0;
interface so-0/0/2.0;
interface fxp0.0 {
    disable;
}

[edit protocols rsvp]
user@R1# commit 
commit complete

[edit protocols rsvp]
user@R1# activate traceoptions 

[edit protocols rsvp]
user@R1# show 
traceoptions {
    file rsvp-log;
    flag error detail;
    flag path detail;
    flag pathtear detail;
}
interface so-0/0/0.0;
interface so-0/0/1.0;
interface so-0/0/2.0;
interface fxp0.0 {
    disable;
}

[edit protocols rsvp]
user@R1# commit 
commit complete

Meaning

The sample output shows that trace options was deactivated and then reactivated.

In a configuration, you can deactivate statements and identifiers so that they do not take effect when you issue the commit command. Any deactivated statements and identifiers are marked with the inactive: tag. They remain in the configuration, but are not activated when you issue a commit command.