Figure 15-15 Rsvp Lsp Trace Configuration Example - Zte ZXR10 ZSR V2 Configuration Manual (System Management

label,
wn return code, 'x' - return code 0
0
! 1
[finished]
Test trace on R1. The execution result is displayed as follows:
R1#trace mpls ipv4 10.28.0.4 32
Tracing MPLS Lable Switched to 10.28.0.4,timeout is 3 second(s).
Codes:'!' - success,
ut,
ismatch,
label,
wn return code, 'x' - return code 0
0
R 1
! 2
[finished]
RSVP LSP Trace Configuration Example
l
Configuration Description
As shown in
R1, R2 and R3. Build an OSPF-TE network. It is required to configure LSP trace on
R1 to check connectivity.

Figure 15-15 RSVP LSP Trace Configuration Example

l
Configuration Flow
1. Build an OSPF-TE network.
2. Perform RSVP LSP trace on R1.
SJ-20140504150128-007|2014-05-10 (R1.0)
'M' - malformed request,
'P' - no rx intf label prot,
'R' - transit router,
'd' - DDMAP
10.28.1.5 MTU 1500 [label 3 ]
10.28.1.6 10 ms
'L' - labeled output interface, 'B' - unlabeled output interface,
'D' - DS Map mismatch,
'M' - malformed request,
'P' - no rx intf label prot,
'R' - transit router,
'd' - DDMAP
10.28.1.5 MTU 1500 [label 49 ]
10.28.1.21 MTU 1500 [label 0 ]
10.28.1.22 7 ms
Figure 15-15, the Resource ReSerVation Protocol (RSVP) is enabled on
Chapter 15 Network Layer Detection
'm' - unsupported tlvs,
'p' - premature termination of LSP,
'I' - unknown upstream index, 'X' - unkno
'Q' - request not sent,
'F' - no FEC mapping,
'm' - unsupported tlvs,
'p' - premature termination of LSP,
'I' - unknown upstream index, 'X' - unkno
8 ms
15-25
ZTE Proprietary and Confidential
'N' - no rx
'*' - timeo
'f' - FEC m
'N' - no rx