Juniper JUNOS OS 10.4 - FOR EX REV 1 Manual page 3917

Table 520: show rsvp session Output Fields (continued)
Field Name Field Description
(Data [not a bypass or backup] LSP when the protection scheme has been
Node/Link
requested) Node and link protection (many-to-one backup) has been requested
protection desired
by the ingress routing device.
Type LSP type:
Link protected LSP
interface. The name of the bypass used is also listed here (
Node/Link protected LSP
at the outgoing interface. The name of the bypass used is also listed here
(
extensive
Protection down
Bypass LSP
link failure.
Backup LSP at Point-of-Local-Repair (PLR)
established to protected a user LSP at the ingress of a failed link.
Backup LSP at Merge Point (MP)
to protected a user LSP at the egress of a failed link.
New bypass (the bypass name is also displayed) has been activated to protect
New bypass
the LSP.
Link protection (the bypass name is also displayed) has been activated for
Link protection up,
the LSP.
using bypass-name
Creating backup A link down
LSP, link down
Deleting backup Link has come back up and the LSP has been restored. Because the backup
LSP is no longer needed, it is deleted.
LSP, protected LSP
restored
Path mtu Displays the value of the path MTU received from the network (through
signaling) and the value used for forwarding. This value is only displayed on
ingress routing devices with the
the [edit protocols mpls path-mtu]
path MTU for the detour is also displayed.
PATH rcvfrom Address of the previous-hop (upstream) routing device or client, interface the
neighbor used to reach this routing device, and number of packets received
from the upstream neighbor.
MTU signaled from the ingress routing device to the egress routing device by
Adspec
means of the adspec object.
PATH sentto Address of the next-hop (downstream) routing device or client, interface used
to reach this neighbor (or peer-name in the GMPLS LSP case), and number of
packets sent to the downstream routing device.
Copyright © 2010, Juniper Networks, Inc.
—LSP has been protected by link protection at the outgoing
—LSP has been protected by node and link protection
).
—LSP is not currently protected.
—LSP that is used to protected one or more user LSPs in case of
—LSP that has been temporarily established
event occurred, and traffic is being switched over to the bypass LSP.
allow-fragmentation
hierarchy level. If there is a detour LSP, the
Chapter 137: Operational Commands for MPLS
extensive ).
—LSP that has been temporarily
statement configured at
Level of Output
detail extensive
detail extensive
extensive
extensive
extensive
extensive
detail
detail
detail
detail
3813