ping srv6-te policy

Function

The ping srv6-te policy command tests the connectivity of an SRv6 TE Policy.

Format

ping srv6-te policy { policy-name policyName | endpoint-ip endpointIpv6 color colorId | binding-sid bsid } [ force-match-slice ] [ end-op endOp | destination dest ] [ -a sourceAddr6 | -c count | -m interval | -s packetSize | -t timeout | -tc tc | -h hopLimit ] ^*

Parameters

Parameter	Description	Value
policy-name policyName	Specifies the name of an SRv6 TE Policy.	The value is a string of 1 to 31 case-sensitive characters. It cannot contain spaces.
endpoint-ip endpointIpv6	Specifies the destination address of an SRv6 TE Policy.	The value is a 32-digit hexadecimal number, in the format of X:X:X:X:X:X:X:X.
color colorId	Specifies the color of an SRv6 TE Policy. This parameter applies to the scenario where traffic is diverted to an SRv6 TE Policy based on the color value.	The value is an integer that ranges from 0 to 4294967295.
binding-sid bsid	Specifies a binding SID for an SRv6 TE Policy. End.B6 type defined in a binding SID, which is used in scenarios such as SRv6 TE Policy import, tunnel interworking, and SD-WAN route selection.	The value is a 32-digit hexadecimal number, in the format X:X:X:X:X:X:X:X.
force-match-slice	Forcibly matches slices and takes effect only for segment lists with slice attributes.	-
end-op endOp	Specifies the type of an End.OP segment ID. If no remote end-op is configured, you can manually specify an End.OP SID. If the last SID in an SRv6 TE Policy Segment List is an End.X SID or Binding SID, the configured remote end-op does not take effect, when initiating a ping srv6-te policy, you also need to manually specify the End.OP SID or destination.	The value is a 32-digit hexadecimal number, in the format of X:X:X:X:X:X:X:X.
destination dest	Specifies the Local IPv6 address or SRv6 local SID of the destination.	The value is a 32-digit hexadecimal number, in the format X:X:X:X:X:X:X:X.
-a sourceAddr6	Specifies a source IPv6 address.	The value is a 32-digit hexadecimal number, in the format of X:X:X:X:X:X:X:X.
-c count	Specifies the number of ICMP echo request messages to be sent.	The value is an integer ranging from 1 to 4294967295. The default value is 5.
-m interval	Specifies an interval at which ICMP echo request messages are sent.	The value is an integer ranging from 1 to 10000, in milliseconds. The default value is 2000.
-s packetSize	Specifies the payload length of an ICMP echo request message.	The value is an integer ranging from 65 to 9600. The default value is 100.
-t timeout	Specifies a timeout time for waiting for the response to an ICMP echo request message.	The value is an integer ranging from 0 to 65535, in milliseconds. The default value is 2000.
-tc tc	Specifies a traffic class for ICMP echo request messages.	The value is an integer ranging from 0 to 255. The default value is 0.
-h hopLimit	Specifies a hop limit.	The value is an integer ranging from 1 to 255. The default value is 255.

Views

All views

Default Level

0: Visit level

Task Name and Operations

Task Name	Operations
sla	execute

Usage Guidelines

Usage Scenario

On an SRv6 TE Policy network, if data forwarding fails over the SRv6 TE Policy, the control plane for SRv6 establishment cannot detect this failure, making network maintenance difficult. The SRv6 TE Policy ping mechanism can be used to detect such faults and locate faulty nodes. This mechanism is implemented using the ping srv6-te policy command. To test the connectivity of an SRv6 TE Policy, run the ping srv6-te policy command.

Prerequisites

SRv6 has been enabled on the device and is working properly.

Precautions

During an SRv6 TE Policy ping test, if the segment list in the policy changes, the ping result may be inaccurate. You are advised to run the Ctrl_C command to stop the test and then initiate the test again.

If neither IPv6 router ID nor Encapsulation source-address is configured, you are advised to use the -a parameter to specify the source address. Otherwise, the detection may fail.

In a non-TE FRR scenario, the ingress of an SRv6 TE Policy cannot have more than one local END SID. Otherwise, the ping operation may fail.

Example

# Ping an SRv6 TE Policy named abc.

<HUAWEI> ping srv6-te policy policy-name abc end-op 2001:db8:2::1 -a 2001:db8:1::1 -c 5 -m 2000 -t 2000 -s 100 -tc 0 -h 255
  PING srv6-te policy : 100  data bytes, press CTRL_C to break
  srv6-te policy's segment list:
  Preference: 200; Path Type: primary; Protocol-Origin: local; Originator: 0, 0.0.0.0; Discriminator: 200; Segment-List ID: 1; Xcindex: 1; end-op: 2001:DB8:2::1
    Reply from 2001:DB8:2::1 
    bytes=100 Sequence=1 time=8 ms
    Reply from 2001:DB8:2::1 
    bytes=100 Sequence=2 time=2 ms
    Reply from 2001:DB8:2::1 
    bytes=100 Sequence=3 time=3 ms
    Reply from 2001:DB8:2::1 
    bytes=100 Sequence=4 time=3 ms
    Reply from 2001:DB8:2::1 
    bytes=100 Sequence=5 time=3 ms

  --- srv6-te policy ping statistics ---
    5 packet(s) transmitted
    5 packet(s) received
    0.00% packet loss
    round-trip min/avg/max = 2/3/8 ms

**Table 1** Description of the **ping srv6-te policy** command output
Item	Description
end-op	End OP.
Path Type	Path type.
Segment-List ID	Segment list ID.
transmitted	Number of sent packets.
received	Number of received packets.
packet loss	Packet loss rate.
round-trip min/avg/max	Minimum, average, or maximum response time.
bytes	Packet size.
Sequence	Sequence number.
time	Round-trip time (RTT), in milliseconds.
Preference	Preference.
Protocol-Origin	Protocol origin.
Discriminator	Discriminator.
Xcindex	XC index.
Originator	Originator.