show rsvp neighbor

RSVP neighbor

Number of neighbors that the routing device has learned of. Each neighbor has one line of output.

via

Name of the interface where the neighbor has been detected. In the case of generalized MPLS (GMPLS) LSPs, the name of the peer where the neighbor has been detected.

Address

Address of a learned neighbor.

Idle

Length of time the neighbor has been idle, in seconds.

Up/Dn

Number of neighbor up or down transitions detected by RSVP hello packets. If the up count is 1 greater than the down count, the neighbor is currently up. Otherwise, the neighbor is down. Neighbors that do not support RSVP hello packets, such as routers running Junos OS Release 3.2 or earlier, are not reported as up or down.

Up cnt and Down cnt

Number of neighbor up or down transitions detected by RSVP hello packets. If the up count is 1 greater than the down count, the neighbor is currently up. Otherwise, the neighbor is down. Neighbors that do not support RSVP hello packets, such as routers running Junos OS Release 3.2 or earlier, are not reported as up or down.

status

State of the RSVP neighbor:

• Up—Routing device can detect RSVP Hello messages from the neighbor.

• Down—Routing device has received one of the following indications:

  • Communication failure from the neighbor.

  • Communication from IGP that the neighbor is unavailable.

  • Change in the sequence numbers in the RSVP Hello messages sent by the neighbor.

• Restarting—RSVP neighbor is unavailable and might be restarting. The neighbor remains in this state until it has restarted or is declared dead. This state is possible only when graceful restart is enabled.

• Restarted—RSVP neighbor has restarted and is undergoing state recovery (graceful restart) procedures.

• Dead—Routing device has lost all communication with the RSVP neighbor. Any RSVP sessions with that neighbor are torn down.

LastChange

Time elapsed since the neighbor state changed either from up to down or from down to up. The format is hh:mm:ss.

Last changed time

Time elapsed since the neighbor state changed either from up to down or from down to up.

HelloInt

Frequency at which RSVP hellos are sent on this interface (in seconds).

HelloTx/Rx

Number of hello packets sent to and received from the neighbor.

Hello

Number of RSVP hello packets that have been sent to and received from the neighbor.

Message received

Number of Path and Resv messages that this routing device has received from the neighbor.

Remote Instance

Identification provided by the remote routing device during Hello message exchange.

Local Instance

Identification sent to the remote routing device during Hello message exchange.

Refresh reduction

Measure of processing overhead requests of refresh messages. Refresh reduction extensions improve routing device performance by reducing the process overhead, thus increasing the number of LSPs a routing device can support. Refresh reduction can have the following values:

• operational—All four RSVP refresh reduction extensions—message ack, bundling, summary refresh, and staged refresh timer—are functional between the two neighboring routing devices. For a detailed explanation of these extensions, see RFC 2961.

• incomplete—Some RSVP refresh reduction extensions are functional between the two neighboring routing devices.

• not operational—Either the refresh reduction feature has been turned off, or the remote routing device cannot support the refresh reduction extensions.

Remote end

Neighboring routing device’s status with regard to refresh reduction:

• enabled—Remote routing device has requested refresh reduction during RSVP message exchanges.

• disabled—Remote routing device does not require refresh reduction.

Pop label

Pop labels of the RSVP-TE pop-and-forward LSP tunnels.

Ack-extension

An RSVP refresh reduction extension:

• enabled—Both local and remote routing devices support the ack-extension (RFC 2961).

• disabled—Remote routing device does not support the ack-extension.

Link protection

Status of the MPLS fast reroute mechanism that protects traffic from link failure:

• enabled—Link protection feature has been turned on, protecting the neighbor with a bypass LSP.

• disabled—No link protection feature has been enabled for this neighbor.

LSP name

Name of the bypass LSP.

Bypass LSP

Status of the bypass LSP. It can have the following values:

• does not exist—Bypass LSP is not available.

• connecting—Routing device is in the process of establishing a bypass LSP, and the LSP is not available for link protection at the moment.

• operational—Bypass LSP is up and running.

• down—Bypass LSP has gone down, with the most probable cause a node or a link failure on the bypass path.

Backup routes

Number of user LSPs (or routes) that are being protected by a bypass LSP (before link failure).

Backup LSPs

Number of LSPs that have been temporarily established to maintain traffic by refreshing the downstream LSPs during link failure (not a one-to-one correspondence).

Bypass explicit route

Explicit route object's (ERO) path that is taken by the bypass LSP.

Restart time

Length of time a neighbor waits to receive a Hello from the restarting node before declaring the node dead and deleting the states (in milliseconds).

Recovery time

Length of time during which the restarting node attempts to recover its lost states with help from its neighbors (in milliseconds). Recovery time is advertised by the restarting node to its neighbors, and applies to nodal faults. The restarting node considers its graceful restart complete after this time has elapsed.