Juniper JUNOS OS 10.3 - SOFTWARE Manual page 3615

Table 475: show rsvp session Output Fields (continued)
Field Name Field Description
LSP type:
Type
Link protected LSP
interface. The name of the bypass used is also listed here (
Node/Link protected LSP
protection at the outgoing interface. The name of the bypass used is also
listed here (
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
A
Creating backup link down
LSP.
LSP, link down
Link has come back up and the LSP has been restored. Because the backup
Deleting backup
LSP is no longer needed, it is deleted.
LSP, protected LSP
restored
Displays the value of the path MTU received from the network (through
Path mtu
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.
Address of the previous-hop (upstream) routing device or client, interface the
PATH rcvfrom
neighbor used to reach this routing device, and number of packets received
from the upstream neighbor.
Adspec MTU signaled from the ingress routing device to the egress routing device by
means of the adspec object.
Address of the next-hop (downstream) routing device or client, interface used
PATH sentto
to reach this neighbor (or peer-name in the GMPLS LSP case), and number of
packets sent to the downstream routing device.
Explct route Explicit route for the session. Normally this value will be the same as that of
record route. Differences indicate that path rerouting has occurred, typically
during fast reroute.
Copyright © 2010, Juniper Networks, Inc.
—LSP has been protected by link protection at the outgoing
—LSP has been protected by node and link
).
extensive
—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
allow-fragmentation
hierarchy level. If there is a detour LSP, the
Chapter 126: Operational Mode Commands for MPLS
).
extensive
—LSP that has been temporarily
statement configured at
Level of Output
detail extensive
extensive
extensive
extensive
extensive
detail
detail
detail
detail
detail
3519