Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation

Tracing RSVP Protocol Traffic

To trace RSVP protocol traffic, include the traceoptions statement:

traceoptions { file filename <files number> <size size> <world-readable | no-world-readable>;flag flag <flag-modifier> <disable>; }

You can include this statement at the following hierarchy levels:

  • [edit protocols rsvp]
  • [edit logical-systems logical-system-name protocols rsvp]

You can specify the following RSVP-specific flags in the RSVP traceoptions statement:

Use the file statement to specify the name of the file that receives the output of the tracing operation. All files are placed in the directory /var/log. We recommend that you place RSVP tracing output in the file rsvp-log.

  • all—All tracing operations.
  • error—All detected error conditions
  • event—RSVP-related events (helps to trace events related to RSVP graceful restart)
  • lmp—RSVP-Link Management Protocol (LMP) interactions
  • packets—All RSVP packets
  • path—All path messages
  • pathtear—PathTear messages
  • resv—Resv messages
  • resvtear—ResvTear messages
  • route—Routing information
  • state—Session state transitions, including when RSVP-signaled LSPs come up and go down.

To view the log file generated when you enable RSVP traceoptions, issue the show log file-name command, where file-name is the file you specified using the traceoptions statement.

For general information about tracing and global tracing options, see the Junos OS Routing Protocols Library for Routing Devices.

Examples: Tracing RSVP Protocol Traffic

Trace RSVP path messages in detail:

[edit]
protocols {rsvp {traceoptions {file rsvp size 10m files 5;flag path;}}}

Trace all RSVP messages:

[edit]
protocols {rsvp {traceoptions {file rsvp size 10m files 5;flag packets;}}}

Trace all RSVP error conditions:

[edit]
protocols {rsvp {traceoptions {file rsvp size 10m files 5;flag error;}}}

Trace RSVP state transitions:

[edit]
protocols {rsvp {traceoptions {file rsvp-data;flag state;}}}

RSVP Log File Output

The following is sample output generated by issuing the show log file-name command on a router on which RSVP traceoptions have been enabled with the state flag configured. The RSVP-signaled LSP E-D is shown being torn down on Mar 11 14:04:36.707092. On Mar 11 14:05:30.101492, it is shown coming back up.

user@host> show log rsvp-data    
Mar 11 13:58:51 trace_on: Tracing to "/var/log/E/rsvp-data" started
Mar 11 13:58:51.286413 rsvp_iflchange for vt ifl vt-1/2/0.69206016
Mar 11 13:58:51.286718 RSVP add interface vt-1/2/0.69206016, ifindex 101, ifaddr (null), family 1, is_appl_vt 0, already known
Mar 11 13:58:51.286818 RSVP Peer vt-1/2/0.69206016 TE-link __rpd:vt-1/2/0.69206016 Up
Mar 11 13:58:51.286978 RSVP add interface vt-1/2/0.69206016, ifindex 101, ifaddr (null), family 3, is_appl_vt 0, already known
Mar 11 13:58:51.287962 RSVP add interface lt-1/2/0.2, ifindex 113, ifaddr (null), family 2, is_appl_vt 0, already known
Mar 11 13:58:51.288629 RSVP add interface lt-1/2/0.2, ifindex 113, ifaddr 10.0.0.2, family 1, is_appl_vt 0, already known
Mar 11 13:58:51.288996 RSVP add interface lt-1/2/0.17, ifindex 114, ifaddr (null), family 2, is_appl_vt 0, already known
Mar 11 13:58:51.289593 RSVP add interface lt-1/2/0.17, ifindex 114, ifaddr (null), family 3, is_appl_vt 0, already known
Mar 11 13:58:51.289949 RSVP add interface lt-1/2/0.17, ifindex 114, ifaddr 10.0.0.17, family 1, is_appl_vt 0, already known
Mar 11 13:58:51.290049 RSVP Peer lt-1/2/0.17 TE-link __rpd:lt-1/2/0.17 Up
Mar 11 13:59:05.042034 RSVP new bypass Bypass->10.0.0.18 on interface lt-1/2/0.17 to 10.0.0.18 avoid 0.0.0.0
Mar 11 14:04:36.707092 LSP "E-D" is Down (Reason: Reservation state deleted)
        Session: 192.168.0.4(port/tunnel ID 10321 Ext-ID 192.168.0.5) Proto 0 Sender: 192.168.0.5(port/lsp ID  1)
Mar 11 14:04:36.707661 RSVP delete resv state, session 192.168.0.4(port/tunnel ID 10321 Ext-ID 192.168.0.5) Proto 0
Mar 11 14:04:36.781185 RSVP delete path state, session 192.168.0.4(port/tunnel ID 10321 Ext-ID 192.168.0.5) Proto 0
Mar 11 14:04:36.781440 RSVP delete session 192.168.0.4(port/tunnel ID 10321 Ext-ID 192.168.0.5) Proto 0
Mar 11 14:05:30.101492 RSVP new Session 192.168.0.4(port/tunnel ID 10321 Ext-ID 192.168.0.5) Proto 0, session ID 3
Mar 11 14:05:30.101722 RSVP new path state, session 192.168.0.4(port/tunnel ID 10321 Ext-ID 192.168.0.5) Proto 0
Mar 11 14:05:30.179124 RSVP new resv state, session 192.168.0.4(port/tunnel ID 10321 Ext-ID 192.168.0.5) Proto 0
Mar 11 14:05:30.179395 RSVP PSB E-D, allocating psb resources for label 4294967295
Mar 11 14:05:30.180353 LSP "E-D" is Up
        Session: 192.168.0.4(port/tunnel ID 10321 Ext-ID 192.168.0.5) Proto 0 Sender: 192.168.0.5(port/lsp ID  2)

Published: 2013-07-31

Supported Platforms

Published: 2013-07-31