Configuring Multicast Ping - Zte ZXR10 ZSR V2 Configuration Manual (System Management

ZXR10 ZSR V2 Configuration Guide (System Management)
l Configuration Commands
For RSVP configuration, refer to the OSPF-TE configuration example.
l Configuration Verification
Run the following commands on R1 to view configurations. The execution result is
displayed as follows:
R1#show mpls traffic-eng tunnels brief
Signalling Summary:
LSP Tunnels Process:
RSVP Process:
Forwarding:
TUNNEL NAME
tunnel_1
Test trace on R1. The execution result is displayed as follows:
R1#trace
Tracing MPLS Lable Switched to te_tunnel1,timeout is 3 second(s).
Codes:'!' - success,
ut,
ismatch,
label,
wn return code, 'x' - return code 0
0
R 1
! 2
[finished]

15.9 Configuring Multicast Ping

Overview
Multicast ping sends an ICMP request packet to a multicast group address and waits for an
ICMP reply packet from the remote end. Multicast ping is applicable to PIM-SM only, and
can only be initiated by a node in an RPT (excluding a multicast receiver). The destination
address is a multicast group address. The request packet is forwarded to a multicast
receiver node through a multicast forwarding path. The receiver node responds with an
ICMP reply packet through unicast.
The work flow of multicast ping is shown in
SJ-20140504150128-007|2014-05-10 (R1.0)
DESTINATION
10.28.0.4
mpls traffic-eng te_tunnel1
'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 147457 ]
10.28.1.6 MTU 1500 [label 3 ]
10.28.1.22 4 ms
running
running
enabled
UP IF DOWN IF
- gei-1/8
'Q' - request not sent,
'F' - no FEC mapping,
'm' - unsupported tlvs,
'p' - premature termination of LSP,
'I' - unknown upstream index, 'X' - unkno
3 ms
Figure 15-16.
15-26
ZTE Proprietary and Confidential
STATE/PROT
up/up
'*' - timeo
'f' - FEC m
'N' - no rx