Field	Description
Link ID	Link ID of the SRv6 tunnel on the VSI or cross-connect group.
Type	Route recursion mode. After the PE receives a customer packet destined for an End.DX2, End.DT2M, or End.DT2U SID, it forwards the packet according to the route recursion mode. · BE—SRv6 BE mode. In this mode, the PE first encapsulates the End.DX2, End.DT2M, or End.DT2U SID into the packet. Then, the PE searches the IPv6 routing table based on the SID encapsulated in the packet to forward the encapsulated packet. · TE—SRv6 TE mode. In this mode, the PE first searches the tunnel policies for a matching SRv6 TE policy based on the next hop of a matching route. Then, the PE adds an SRH to the packet. The SRH includes the End.DX2, End.DT2M, or End.DT2U SID and the SID list of the SRv6 TE policy. Finally, the PE forwards the encapsulated packet through the SRv6 TE policy. · BE/TE—SRv6 TE and SRv6 BE hybrid mode. In this mode, the PE preferentially uses the SRv6 TE mode to forward the packet. If no SRv6 TE policy is available for the packet, the PE forwards the packet in SRv6 BE mode.
State	SRv6 tunnel status: · Up—The SRv6 tunnel is up. · Down—The SRv6 tunnel is down. · Blocked—The SRv6 tunnel is a backup tunnel. Its tunnel interface is up, but the tunnel is blocked because the primary tunnel is operating correctly.
In SID	Input SID, which is a local SID.
Out SID	Output SID, which is a remote SID.

Field	Description
Link ID	Link ID of the SRv6 tunnel on the VSI or cross-connect group.
SRv6 PW Type	SRv6 PW data encryption type, Ethernet or VLAN. If no SRv6 PW data encryption type is specified, this field displays a hyphen (-).
SRv6 Tunnel State	SRv6 tunnel status: · Up—The SRv6 tunnel is up. · Down—The SRv6 tunnel is down. · Blocked—The SRv6 tunnel is a backup tunnel. Its tunnel interface is up, but the tunnel is blocked because the primary tunnel is operating correctly.
In SID	Input SID, which is a local SID.
Out SID	Output SID, which is a remote SID.
MTU	Maximum transmission unit, in bytes.
SRv6 Tunnel Attributes	SRv6 tunnel attributes: · Main—The primary tunnel. · Backup—The backup tunnel. · ac-Bypass—The Bypass tunnel for AC bypass. · ECMP—ECMP tunnel.
SRv6 Forwarding IDs	Forwarding entry IDs of the candidate paths in an SRv6 TE policy. If service traffic is not forwarded through an SRv6 TE policy tunnel, this field displays a hyphen (-).
Remote Leaf Argument	Argument value used by the remote PE to identify leaf ACs. If no argument value exists, this field displays a hyphen (-).

Field	Description
Peer	IPv6 address of the peer PE.
Flag	SRv6 tunnel flags: · Main—The primary tunnel. · Backup—The backup tunnel. · ac-Bypass—The Bypass tunnel for AC bypass. · ECMP—ECMP tunnel.
State/SRv6 Tunnel State	SRv6 tunnel status: · Up—The SRv6 tunnel is up. · Down—The SRv6 tunnel is down. · Blocked—The SRv6 tunnel is a backup tunnel. Its tunnel interface is up, but the tunnel is blocked because the primary tunnel is operating correctly.
SRv6 PW Type	SRv6 PW data encryption type, Ethernet or VLAN. If no SRv6 PW data encryption type is specified, this field displays a hyphen (-).
Remote SrvID/Remote Service ID	Remote service ID.
Signaling Protocol	Signaling protocol used to establish the SRv6 tunnel. The value is EVPN.
Link ID	Link ID of the SRv6 tunnel on the VSI or cross-connect group.
In SID	Input SID, which is a local SID.
Out SID	Output SID, which is a remote SID.
MTU	Maximum transmission unit, in bytes.
SRv6 Tunnel Attributes	SRv6 tunnel attributes: · Main—The primary tunnel. · Backup—The backup tunnel. · ac-Bypass—The Bypass tunnel for AC bypass. · ECMP—ECMP tunnel.
Tunnel Group ID	ID of the public network tunnel group that carries the SRv6 tunnel.
Tunnel NHLFEIDs	NHLFE ID of the public tunnel that carries the SRv6 tunnel when SRv6 TE route recursion mode is used for traffic forwarding. This field displays a hyphen (-) if traffic is not forwarded over an SRv6 TE policy tunnel.
Color	Color attribute of the expected SRv6 TE policy for route recursion. If no color attribute is available, this field displays a hyphen (-).
Remote Leaf Argument	Argument value used by the remote PE to identify leaf ACs. If no argument value exists, this field displays a hyphen (-).
Recursion Mode	Route recursion mode of the SRv6 tunnel: · SID based—SRv6 BE mode. · Nexthop based—SRv6 TE mode. · Nexthop based/SID based—SRv6 TE and SRv6 BE hybrid mode.
Down Reason	SRv6 tunnel down reason: · MTU not match—The MTUs at the two ends of the SRv6 tunnel do not match. · Local AC Down—The local AC is down. · Local VSI admin Down—The local VSI is administratively down. · EVPN VPWS AD per EVI route received from peer—In the EVPN VPWS over SRv6 network, the local end does not receive A-D per EVI routes sent from the peer end. · EVPN VPWS AD per ES route not received from peer—In the EVPN VPWS over SRv6 network, the local end does not receive A-D per ES routes sent from the peer end. · SRv6 not configured with best effort or traffic engineering—No route recursion mode is configured for the SRv6 tunnel. · Tunnel Down—The route is not reachable in SRv6 BE recursion mode or no SRv6 TE policy is configured in SRv6 TE recursion mode. · BFD session for SRv6 PW down—BFD detects that the SRv6 tunnel is down. · Unknown.
Input Statistics	SRv6 PW incoming traffic statistics: · Octets—Number of incoming bytes. · Packets—Number of incoming packets. · Errors—Number of error packets. · Discards—Number of dropped packets. This field is not available in an EVPN VPLS over SRv6 network.
Output statistics	SRv6 PW outgoing traffic statistics: · Octets—Number of outgoing bytes. · Packets—Number of outgoing packets. · Errors—Number of error packets. · Discards—Number of dropped packets.
Input Rate	SRv6 PW incoming traffic rate: · Bytes per second—Number of incoming bytes per second. · Packets per second—Number of incoming packets per second. This field is not available in an EVPN VPLS over SRv6 network.
Output Rate	SRv6 PW outgoing traffic rate: · Bytes per second—Number of outgoing bytes per second. · Packets per second—Number of outgoing packets per second.

Field	Description
Main SRv6 Tunnel	Primary SRv6 tunnel.
Peer	IPv6 address of the remote PE for the SRv6 tunnel.
Service ID	Service ID of the remote PE.
Backup SRv6 Tunnel	Backup SRv6 tunnel.
Signaling Protocol	Signaling protocol used to establish the SRv6 tunnels. The value is EVPN.
Main SRv6 Defect State	Defect state of the primary SRv6 tunnel: · No defect. · Signal defect—The signaling protocol detected defects.
Backup SRv6 Defect State	Defect state of the backup SRv6 tunnel: · No defect. · Signal defect—The signaling protocol detected defects. If no backup SRv6 tunnel exists, this field displays a hyphen (-).
Switch Result	SRv6 tunnel in use after a primary/backup tunnel switchover: · None—Neither the primary nor the backup SRv6 tunnel is in use. · Working—The primary SRv6 tunnel is in use. · Backup—The backup SRv6 tunnel is in use.
Switch Reason	Reason that causes the primary/backup tunnel switchover: · Config changed—An SRv6 tunnel is added to or removed from the tunnel redundancy group. · Fault detected—An SRv6 tunnel fault is detected. · SRv6 down—The state of an SRv6 tunnel changes from active to down. · SRv6 up—The state of an SRv6 tunnel changes from active to up. · None—No primary/backup tunnel switchover has occurred.
Remote Event	This field is not supported in the current software version. Remote state machine event.
Local Event	Local state machine event: · SFW—Local primary SRv6 tunnel defect event. · SFP—Local backup SRv6 tunnel defect event. · SFCW—Local primary SRv6 tunnel up event. · SFCP—Local backup SRv6 tunnel up event. · None—No local event.
SRv6 Group Old State	SRv6 tunnel redundancy group state before switchover: · Idle—Both the primary and backup SRv6 tunnels are not available. · Normal—Both the primary and backup SRv6 tunnels are available. The primary SRv6 tunnel is up and the backup SRv6 tunnel is blocked. The primary SRv6 tunnel is used to forward traffic. · UA:P:L—The backup SRv6 tunnel has defects and the primary SRv6 tunnel is up. · PF:W:L—The primary SRv6 tunnel has defects and the back SRv6 tunnel is up.
SRv6 Group State	SRv6 tunnel redundancy group state after switchover. The supported values are the same as those of the SRv6 Group Old State field.

Field	Description
MTU	Maximum transmission unit of the VSI.
State	VSI state: · Up—The VSI is up. · Down—The VSI is down. · Admin down—The VSI is manually shut down by using the shutdown command.

Field	Description
VSI Description	VSI description. If no description is configured, this field is not available.
VSI State	VSI state: · Up—The VSI is up. · Down—The VSI is down. · Administratively down—The VSI is manually shut down by using the shutdown command.
MTU	Maximum transmission unit of the VSI.
Diffserv Mode	DiffServ mode. Options include the following: · ingress—DiffServ mode for the inbound direction. · egress—DiffServ mode for the outbound direction. · pipe—Pipe mode. · short-pipe—Short-pipe mode. · uniform—Uniform mode · trust—Priority trust mode ¡ inner-dot1p—Trusts the inner 802.1p priority in packets. ¡ dscp—Trusts the DSCP in packets. af1, af2, af3, af4, be, cs6, cs7, or ef represents the MPLS EXP value. If no DiffServ mode is configured, this field displays a hyphen (-).
Bandwidth	Maximum bandwidth (in kbps) for known unicast traffic on the VSI.
Broadcast Restrain	Broadcast restraint bandwidth (in kbps).
Multicast Restrain	Multicast restraint bandwidth (in kbps).
Unknown Unicast Restrain	Unknown unicast restraint bandwidth (in kbps).
MAC Learning	State of the MAC learning feature.
MAC Tabel Limit	Maximum number of MAC address entries on the VSI. If the VSI does not limit the maximum number of MAC address entries, this field displays Unlimited.
MAC Learning rate	MAC address entry learning rate of the VSI.
Local MAC aging time	MAC aging time for dynamic local-MAC entries, in seconds. If dynamic local-MAC entries do not age out, this field displays NotAging.
Remote MAC aging time	MAC aging time for dynamic remote-MAC entries, in seconds. If dynamic remote-MAC entries do not age out, this field displays NotAging.
Drop Unknown	Action on source MAC-unknown frames received after the maximum number of MAC entries is reached.
PW Redundancy Mode	PW redundancy operation mode: · Slave—Master/slave mode and the local PE operates as the slave node. · Master—Master/slave mode and the local PE operates as the master node. · Independent—Independent mode.
Flooding	State of the VSI's flooding feature. This field is not supported by VPLS.
Redundancy Mode	ES redundancy mode: · All-active. · Single-active.
Statistics	Packet statistics state.
Input Statistics	Incoming traffic statistics: · Octets—Number of incoming bytes. · Packets—Number of incoming packets. · Errors—Number of error packets. · Discards—Number of dropped packets.
Output statistics	Outgoing traffic statistics: · Octets—Number of outgoing bytes. · Packets—Number of outgoing packets. · Errors—Number of error packets. · Discards—Number of dropped packets.
Input Rate	Incoming traffic rate: · Bytes per second—Number of incoming bytes per second. · Packets per second—Number of incoming packets per second. This field is not available in an EVPN VPLS over SRv6 network.
Output Rate	Outgoing traffic rate: · Bytes per second—Number of outgoing bytes per second. · Packets per second—Number of outgoing packets per second.
EVPN Encapsulation	EVPN encapsulation type: · VXLAN. · MPLS. · SRv6.
SRv6 SIDs	SRv6 SIDs of the VSI.
End.DT2U	SRv6 SID used for unicast forwarding in the EVPN VPLS over SRv6 network. The values in parentheses are the length of each segment in the SID, which are the locator length, opcode length, and argument length in sequence. The total length of those segments is 128.
End.DT2UL	SRv6 SID used for unicast forwarding over the bypass tunnel at the multihomed EVPN VPLS over SRv6 site. The values in parentheses are the length of each segment in the SID, which are the locator length, opcode length, and argument length in sequence. The total length of those segments is 128.
End.DT2M	SRv6 SID used for flood forwarding in the EVPN VPLS over SRv6 network. The values in parentheses are the length of each segment in the SID, which are the locator length, opcode length, and argument length in sequence. The total length of those segments is 128.
SRv6 Tunnels	SRv6 tunnels on the VSI.
Peer	IPv6 address of the PW remote PE.
Link ID	Link ID of the SRv6 tunnel on the VSI.
State	SRv6 tunnel state, which can be Up, Down, Blocked, or Defect.
ACs	ACs of the VSI.
AC	For a Layer 3 interface, this field displays the interface name. For an Ethernet service instance, this field displays the name of the Ethernet service instance and the name of the Layer 2 interface where the Ethernet service instance name resides.
Link ID	Link ID of the AC on the VSI.
State	AC state, which can be Up or Down.
Statistics	AC packet statistics state.

display l2vpn xconnect-group

Use display l2vpn xconnect-group to display L2VPN cross-connect group information.

Syntax

display l2vpn xconnect-group [ evpn-srv6 | name group-name ] [ count | verbose ]

display l2vpn xconnect-group name group-name connection connection-name [ verbose ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

evpn-srv6: Specifies cross-connect groups in the EVPN VPWS over SRv6 network using dynamically established SRv6 PWs.

name group-name: Specifies a cross-connect group by its name, a case-sensitive string of 1 to 31 characters.

connection connection-name: Specifies a cross-connect by its name, a case-sensitive string of 1 to 20 characters. The cross-connect name cannot contain hyphens (-). If you do not specify a cross-connect, this command displays information about all cross-connects in the specified cross-connect group.

count: Displays cross-connect group statistics.

verbose: Displays detailed cross-connect group information.

Usage guidelines

If you do not specify a cross-connect group or the evpn-srv6 keyword, this command displays information for all cross-connect groups.

If you do not specify the count or verbose keyword, this command displays brief cross-connect group information.

Examples

# Display brief information about all cross-connect groups in the EVPN VPWS over SRv6 network.

<Sysname> display l2vpn xconnect-group evpn-srv6

Status Codes: UP - Up, DN - Down, DF - Defect, BD - Blocked, AD - Admin Down,

DL - Idle, DP - Duplicate

Total number of cross-connections: 1, 1 up, 0 down, 0 admin down

Xconnect-group Connection ST

Segment1 ST Segment2 ST

--------------------------------------------------------------------------------

vpna pw1 UP

HGE1/0/2 UP EVPN 2::2 UP

--------------------------------------------------------------------------------

# Display statistics about all cross-connect groups in the EVPN VPWS over SRv6 network.

<Sysname> display l2vpn xconnect-group evpn-srv6 count

Status Codes: UP - Up, DN - Down, DF - Defect, BD - Blocked, AD - Admin Down,

DL - Idle, DP - Duplicate

Total number of cross-connections: 1, 1 up, 0 down, 0 admin down

Table 7 Command output

Field	Description
ST	State of the cross-connect: · UP—The cross-connect is up. · DN—The cross-connect is down. · AD—The cross-connect is manually shut down by using the shutdown command.
Segment1 / Segment2	For an AC segment: · If the AC is a Layer 3 interface, this field displays the interface name. · If the AC is an Ethernet service instance, this field displays the Ethernet service instance name. For an SRv6 tunnel segment, this field displays the establishment method of the SRv6 tunnel and the IPv6 address of the remote PE. Only the EVPN establishment method is supported.
ST	If this field displays AC state, the following options are available: · UP—The AC is up. · DN—The AC is down. If this field displays SRv6 tunnel state, the following options are available: · UP—The tunnel is up. · DN—The tunnel is down. · DF—BFD detects that the tunnel has defects. · BD—The tunnel is a backup tunnel. Its tunnel interface is up, but the tunnel is blocked because the primary tunnel is operating correctly. · DL—The input SID of the tunnel is not available. · DP—This option is not supported in the current software version.

‌

# Display detailed information about all cross-connect groups in the EVPN VPWS over SRv6 network.

<Sysname> display l2vpn xconnect-group evpn-srv6 verbose

Xconnect-group Name: vpna

Connection Name : pw1

Connection ID : 1

State : Up

MTU : 1500

PW Redundancy Mode : Slave

Diffserv Mode : -

SRv6 tunnels:

Peer : 2::2

Link ID : 0x8000000

State : Up

ACs:

AC Link ID State

HGE1/0/1 0x0 Up

Statistics: Disabled

Table 8 Command output

Field	Description
Description	Description of the cross-connect group. If no description is configured, this field is not available.
State	Cross-connect group state: · Up—The cross-connect group is up. · Down—The cross-connect group is down. · Administratively down—The cross-connect group is manually shut down by using the shutdown command.
MTU	Maximum transmission unit of cross-connects.
PW Redundancy Mode	PW redundancy operation mode: · Slave—Master/slave mode and the local PE operates as the slave node. · Master—Master/slave mode and the local PE operates as the master node. · Independent—Independent mode.
Diffserv Mode	DiffServ mode. Options include the following: · ingress—DiffServ mode for the inbound direction. · egress—DiffServ mode for the outbound direction. · pipe—Pipe mode. · short-pipe—Short-pipe mode. · uniform—Uniform mode · trust—Priority trust mode ¡ inner-dot1p—Trusts the inner 802.1p priority in packets. ¡ dscp—Trusts the DSCP in packets. af1, af2, af3, af4, be, cs6, cs7, or ef represents the MPLS EXP value. If no DiffServ mode is configured, this field displays a hyphen (-).
SRv6 tunnels	Information about dynamic SRv6 PWs.
Peer	IPv6 address of the SRv6 PW remote PE.
Link ID	Link ID of the SRv6 PW on the cross-connect.
State	SRv6 PW state, which can be Up, Down, Blocked, or Defect.
ACs	AC information.
AC	For a Layer 3 interface, this field displays the interface name. For an Ethernet service instance, this field displays the name of the Ethernet service instance and the name of the Layer 2 interface where the Ethernet service instance name resides.
Link ID	Link ID of the AC on the cross-connect.
State	AC state, which can be Up or Down.
Statistics	AC packet statistics state.

‌

evpn encapsulation srv6

Use evpn encapsulation srv6 to create an EVPN instance, configure it to use SRv6 encapsulation, and enter its view, or enter the view of an existing EVPN instance that uses SRv6 encapsulation.

Use undo evpn encapsulation to restore the default.

Syntax

evpn encapsulation srv6

undo evpn encapsulation

Default

No EVPN instance is created.

Views

Cross-connect group view

Predefined user roles

network-admin

Usage guidelines

Before you can configure EVPN settings for a VSI or cross-connect group, you must create an EVPN instance on it.

Examples

# Create an EVPN instance and specify it to use SRv6 encapsulation on VSI aaa and enter its view.

<Sysname> system-view

[Sysname] xconnect-group vpna

[Sysname-xcg-vpna] evpn encapsulation srv6

[Sysname-xcg-vpna-evpn-srv6]

evpn encapsulation srv6 binding instance

Use evpn encapsulation srv6 binding instance to bind a VSI to an EVPN instance.

Use undo evpn encapsulation to restore the default.

Syntax

evpn encapsulation srv6 binding instance instance-name vsi-tag tag-id

undo evpn encapsulation

Default

A VSI is not bound to any EVPN instance.

Views

VSI view

Predefined user roles

network-admin

Parameters

instance-name: Specifies an EVPN instance by its name, a case-sensitive string of 1 to 31 characters.

vsi-tag tag-id: Specifies a VSI tag ID in the range of 1 to 4094. An EVPN instance uses tag IDs to identify VSIs when it is bound to multiple VSIs.

Usage guidelines

You can bind a VSI only to one EVPN instance.

This command is mutually exclusive with the evpn encapsulation srv6 command. You cannot use them together on the same VSI.

Examples

# Bind VSI vpna to EVPN instance evpna.

<Sysname> system-view

[Sysname] vsi vpna

[Sysname-vsi-vpna] evpn encapsulation srv6 binding instance evpna vsi-tag 1000

Related commands

evpn encapsulation srv6

locator-sbfd enable

Use locator-sbfd enable to enable SBFD for SRv6 locators.

Use undo locator-sbfd enable to restore the default.

Syntax

locator-sbfd enable [ template template-name ] [ prefix-list prefix-list-name ]

undo locator-sbfd enable

Default

SBFD is not configured for SRv6 locators.

Views

SRv6 view

Predefined user roles

network-admin

Parameters

template template-name: Specifies a BFD template name, a case-sensitive string of 1 to 63 characters. If you do not specify this option, an SBFD session uses the multihop BFD parameters configured in system view.

prefix-list prefix-list-name: Specifies an IPv6 prefix list by its name, a case-sensitive string of 1 to 63 characters. If you do not specify this option, the system performs SBFD on all locators advertised by BGP.

Usage guidelines

Application scenarios

In the IP L3VPN over SRv6 BE, EVPN L3VPN over SRv6 BE, public IP over SRv6 BE scenario, with FRR enabled on a local PE, the PE can use the backup path upon failure of the primary path when a peer CE is dualhomed to two PEs. For fast traffic switchover to the backup path when the primary path fails, configure this feature on the local PE to detect connectivity of the SRv6 locators advertised through BGP by the peer PE.

Operating mechanism

SBFD uses the following procedure to detect connectivity of SRv6 locators advertised by BGP:

1. The initiator (local PE) sends an SBFD packet with the destination IP address as the network segment for the SID identified by an SRv6 locator.

2. Upon receiving the SBFD packet, the reflector (peer PE) identifies whether the discriminator in the packet is consistent with the local discriminator. If they are consistent, the reflector sends an SBFD response to the initiator through IPv6 routing. If they are inconsistent, the reflector discards the SBFD packet.

3. The initiator switches to the backup path if it does not receive an SBFD response before the timeout timer expires. If it receives an SBFD response before the timeout timer expires, the SRv6 locator is reachable.

Restrictions and guidelines

For this feature to take effect, perform the following tasks:

· Execute the sbfd destination ipv6 remote-discriminator command on the local PE to associate the destination IPv6 address of the detected path with the remote discriminator of the SBFD session for the initiator.

· Execute the sbfd local-discriminator command on the peer device of the main path to set the local discriminator for the reflector and make sure the discriminator is consistent on the local PE and peer PE.

Examples

# Enable SBFD for all SRv6 locators advertised by BGP.

<Sysname> system-view

[Sysname] segment-routing ipv6

[Sysname-segment-routing-ipv6] locator-sbfd enable

Related commands

sbfd destination ipv6 remote-discriminator (High Availability Command Reference)

sbfd local-discriminator (High Availability Command Reference)

nexthop interface (BGP IPv4 SR next hop view/BGP-VPN IPv4 SR next hop view/BGP-VPN IPv4 EVPN SR next hop view)

Use nexthop interface to specify a next hop to which an End.DX4 SID can be dynamically allocated and specify the output interface of the next hop.

Use undo nexthop to restore the default.

Syntax

nexthop nexthop-address interface interface-type interface-number

undo nexthop nexthop-address

Default

No End.DX4 SID is allocated to a next hop.

Views

BGP-VPN IPv4 SR next hop view

BGP-VPN IPv4 EVPN SR next hop view

BGP IPv4 SR next hop view

Predefined user roles

network-admin

Parameters

nexthop-address: Specifies a next hop by its IPv4 address.

interface-type interface-number: Specifies an output interface by its type and number.

Usage guidelines

This command is applicable to the IPv4 L3VPN over SRv6, IPv4 EVPN L3VPN over SRv6, or public network IPv4 over SRv6 scenario to accelerate traffic forwarding. This command allocates an End.DX4 SID to the specified next hop for BGP IPv4 routes and associates the next hop with an output interface.

Use one of the following methods to allocate End.DX4 SIDs to next hops:

· Use this command to dynamically allocate an End.DX4 SID to a next hop from the locator applied to the VPN instance or public instance.

Make sure the output interface specified for the next hop in this command is consistent with the output interface of that next hop in the routing table. If they are inconsistent, the device cannot dynamically allocate an End.DX4 SID to the next hop.

· Use the opcode end-dx4 vpn-instance command to manually configure an End.DX4 SID in the locator applied to the VPN instance or public instance.

Make sure the output interface specified for the next hop in the opcode end-dx4 vpn-instance command is consistent with the output interface of that next hop in the routing table. If they are inconsistent, the device cannot use the manually configured End.DX4 SID to forward traffic.

If both methods are used for the same next hop, the manually configured End.DX4 SID takes precedence over the dynamically allocated one.

You can specify only one output interface for one next hop. To change the output interface of a next hop, first use the undo nexthop command to remove the original next hop and output interface association.

The device might be unable to dynamically allocate SIDs to BGP IPv4 routes based on the route next hops when dynamic SID resources are insufficient. If the device does not have manually configured End.DX4 SIDs, it allocates the End.DT4 SID or End.DT46 SID of the VPN instance or public instance to the routes.

Examples

# In BGP IPv4 SR next hop view, allow the system to allocate an End.DX4 SID to next hop 10.1.1.2 and specify HundredGigE 1/0/1 as the output interface of the next hop.

<Sysname> system-view

[Sysname] bgp 100

[Sysname-bgp-default] address-family ipv4 unicast

[Sysname-bgp-default-ipv4] segment-routing ipv6 locator aaa

[Sysname-bgp-default-ipv4] segment-routing ipv6 apply-sid specify-nexthop

[Sysname-bgp-default-sid-np-ipv4] nexthop 10.1.1.2 interface hundredgige 1/0/1

Related commands

opcode

nexthop interface (BGP SRv6 next hop view/BGP-VPN SRv6 next hop view/BGP-VPN IPv6 EVPN SR next hop view)

Use nexthop interface to specify a next hop to which an End.DX6 SID can be dynamically allocated and specify the output interface of the next hop.

Use undo nexthop to restore the default.

Syntax

nexthop nexthop-ipv6-address interface interface-type interface-number

undo nexthop nexthop-ipv6-address

Default

No End.DX6 SID is allocated to a next hop.

Views

BGP-VPN SRv6 next hop view

BGP-VPN IPv6 EVPN SR next hop view

BGP SRv6 next hop view

Predefined user roles

network-admin

Parameters

nexthop-ipv6-address: Specifies a next hop by its IPv6 address.

interface-type interface-number: Specifies an output interface by its type and number.

Usage guidelines

This command is applicable to the IPv6 L3VPN over SRv6, IPv6 EVPN L3VPN over SRv6, or public network IPv6 over SRv6 scenario to accelerate traffic forwarding. This command allocates an End.DX6 SID to the specified next hop for BGP IPv6 routes and associates the next hop with an output interface.

Use one of the following methods to allocate End.DX6 SIDs to next hops:

· Use this command to dynamically allocate an End.DX6 SID to a next hop from the locator applied to the VPN instance or public instance.

· Use the opcode end-dx6 vpn-instance command to manually configure an End.DX6 SID in the locator applied to the VPN instance or public instance.

Make sure the output interface specified for the next hop in the opcode end-dx6 vpn-instance command is consistent with the output interface of that next hop in the routing table. If they are inconsistent, the device cannot use the manually configured End.DX6 SID to forward traffic.

If both methods are used for the same next hop, the manually configured End.DX6 SID takes precedence over the dynamically allocated one.

The device might be unable to dynamically allocate SIDs to BGP IPv6 routes based on the route next hops when dynamic SID resources are insufficient. If the device does not have manually configured End.DX6 SIDs, it allocates the End.DT6 SID or End.DT46 SID of the VPN instance or public instance to the routes.

Examples

# In BGP SRv6 next hop view, allow the system to allocate an End.DX6 SID to next hop 10::1:2 and specify HundredGigE 1/0/1 as the output interface of the next hop.

<Sysname> system-view

[Sysname] bgp 100

[Sysname-bgp-default] address-family ipv6 unicast

[Sysname-bgp-default-ipv6] segment-routing ipv6 locator aaa

[Sysname-bgp-default-ipv6] segment-routing ipv6 apply-sid specify-nexthop

[Sysname-bgp-default-sid-np-ipv6] nexthop 10::1:2 interface hundredgige 1/0/1

Related commands

opcode

peer advertise encap-type srv6

Use peer advertise encap-type srv6 to enable SRv6 encapsulation for the EVPN IP prefix advertisement routes advertised to a peer or peer group.

Use undo peer advertise encap-type srv6 to disable SRv6 encapsulation for the EVPN IP prefix advertisement routes advertised to a peer or peer group.

Syntax

peer { group-name | ipv6-address [ prefix-length ] } advertise encap-type srv6 [ anycast ]

undo peer { group-name | ipv6-address [ prefix-length ] } advertise encap-type srv6

Default

IP prefix advertisement routes use VXLAN encapsulation.

Views

BGP EVPN address family view

Predefined user roles

network-admin

Parameters

group-name: Specifies a peer group by its name, a case-sensitive string of 1 to 47 characters. The peer group must exist.

ipv6-address: Specifies a peer by its IPv6 address. The peer must exist.

prefix-length: Specifies a prefix length in the range of 0 to 128. To specify a subnet, you must specify both the ipv6-address and prefix-length arguments.

anycast: Uses EVPN routes to advertise the SRv6 SIDs in an anycast locator. To use EVPN routes to advertise the SRv6 SIDs in a normal locator, do not specify this keyword.

Usage guidelines

Use this command to enable the device to advertise EVPN IP prefix advertisement routes with SRv6 encapsulation in an EVPN L3VPN over SRv6 or EVPN VPWS over SRv6 network.

In an EVPN L3VPN over SRv6 network, execute this command on the edge nodes of the EVPN L3VPN network and RRs.

Examples

# Enable SRv6 encapsulation for the IP prefix advertisement routes advertised to peer 1::1.

<Sysname> system-view

[Sysname] bgp 100

[Sysname-bgp-default] address-family l2vpn evpn

[Sysname-bgp-default-evpn] peer 1::1 advertise encap-type srv6

peer prefix-sid

Use peer prefix-sid to enable BGP to exchange SRv6 SID information with an IPv6 peer or peer group.

Use undo peer prefix-sid to restore the default.

Syntax

peer { group-name | ipv6-address [ prefix-length ] } prefix-sid [ anycast ]

undo peer { group-name | ipv6-address [ prefix-length ] } prefix-sid

Default

BGP does not exchange SRv6 SID information with an IPv6 peer or peer group.

Views

BGP VPNv4 address family view

BGP VPNv6 address family view

BGP IPv4 unicast address family view

BGP IPv6 unicast address family view

Predefined user roles

network-admin

Parameters

group-name: Specifies a peer group by its name, a case-sensitive string of 1 to 47 characters. The peer group must exist.

ipv6-address: Specifies a peer by its IPv6 address. The peer must exist.

prefix-length: Specifies a prefix length in the range of 0 to 128. To specify a subnet, you must specify both the ipv6-address and prefix-length arguments.

anycast: Exchanges the SRv6 SIDs in an anycast locator with the specified peers. To exchange the SRv6 SIDs in a normal locator with the specified peers, do not specify this keyword.

Usage guidelines

Use this command to enable IPv6 peers in an SRv6 VPN network to exchange SRv6 SID information through BGP VPNv4, VPNv6, IPv4 unicast, or IPv6 unicast routes.

If you execute this command multiple times for the same peer or peer group, the most recent configuration takes effect.

Examples

# In BGP VPNv4 address family view, enable BGP to exchange SRv6 SID information with peer 2001:1::1.

<Sysname> system-view

[Sysname] bgp 100

[Sysname-bgp-default] address-family vpnv4

[Sysname-bgp-default-vpnv4] peer 2001:1::1 prefix-sid

peer srv6-vpn compatible

Use peer srv6-vpn compatible to enable SRv6 VPN compatibility for a peer or peer group.

Use undo peer srv6-vpn compatible to disable SRv6 VPN compatibility for a peer or peer group.

Syntax

peer { group-name | ipv6-address [ prefix-length ] } srv6-vpn compatible [ srv6-sid-transposition ]

undo peer { group-name | ipv6-address [ prefix-length ] } srv6-vpn compatible

Default

SRv6 VPN compatibility is disabled. The device uses the non-transposition scheme defined in draft-ietf-bess-srv6-services-07 to encapsulate the SRv6 SIDs carried in advertised BGP routes.

Views

BGP VPNv4 address family view

BGP VPNv6 address family view

BGP EVPN address family view

Predefined user roles

network-admin

Parameters

group-name: Specifies an existing peer group by its name, a case-sensitive string of 1 to 47 characters.

ipv6-address: Specifies an existing peer by its IPv6 address.

prefix-length: Specifies the prefix length, in the range of 0 to 128. If you specify this argument, you specify the dynamic peers in the specified network.

srv6-sid-transposition: Uses the transposition scheme defined in draft-ietf-bess-srv6-services-07 to encapsulate the SRv6 SIDs carried in advertised BGP routes. If you do not specify this keyword, the device encapsulates the SRv6 SIDs carried in advertised BGP routes in the format defined in draft-dawra-idr-srv6-vpn-04.

Usage guidelines

In an IP L3VPN over SRv6 network, the BGP VPNv4 or VPNv6 routes exchanged between PEs carry SRv6 SIDs. When the SRv6 SIDs are encapsulated in different formats, the BGP route advertisement fails. To resolve this issue, you can execute this command to configure the SRv6 SID encapsulation format to be the same as that supported by the peer device.

Examples

# Configure the device to use the format defined in draft-dawra-idr-srv6-vpn-04 to encapsulate the SRv6 SIDs in the BGP routes sent to peer 2::2.

<Sysname> system-view

[Sysname] bgp 1

[Sysname-bgp-default] address-family vpnv4

[Sysname-bgp-default-vpnv4] peer 2::2 srv6-vpn compatible

ping evpn vpls srv6

Use ping evpn vpls srv6 to test the connectivity of an SRv6 PW in an EVPN VPLS over SRv6 network by pinging a remote PE from the local PE.

Syntax

Views

Any view

Predefined user roles

network-admin

Parameters

vsi vsi-name: Specifies a VSI by its name, a case-sensitive string of 1 to 31 characters.

mac mac-address: Specifies a host attached to a remote PE by its MAC address in H-H-H format. Do not specify a broadcast MAC address, multicast MAC address, or all-zeros MAC address.

end-op endop: Specifies an End.OP SID to be added to MPLS echo requests. The End.OP SID is used to locate the destination node. If you do not specify an End.OP SID, the device does not add an End.OP SID to MPLS echo requests.

-a source-ipv6: Specifies the source IPv6 address of MPLS echo requests. The specified IPv6 address must be advertised to remote PEs through a routing protocol. If you do not specify a source IPv6 address, the source IPv6 address of MPLS echo requests is the IPv6 address specified by using the encapsulation source-address command.

-c count: Specifies the number of MPLS echo requests to be sent. The value range for the count argument is 1 to 4294967295, and the default value is 5.

-h hop-limit: Specifies the maximum number of hops allowed for an MPLS echo request. The value range for the hop-limit argument is 1 to 255, and the default value is 255.

-m interval: Specifies the interval at which an MPLS echo request is sent, in milliseconds. The value range for the interval argument is 1 to 10000, and the default value is 2000.

-r reply-mode: Specifies the reply mode used by the receiver (the remote PE) to reply to MPLS echo requests. The value for the reply-mode argument can be 2 or 4, and the default value is 2. If the mode is 2, the receiver searches the IP forwarding table for the destination IP address to forward MPLS echo replies. If the mode is 4, the receiver searches the IPv6 routing table for the source IPv6 address of the echo requests, encapsulates an SRH to the replies, and forwards them.

-s packet-size: Specifies the length of MPLS echo requests, in bytes. The value range for the packet-size argument is 80 to 1200, and the default value is 100. The specified packet length does not include the IPv6 header and UDP header length.

-t time-out: Specifies the timeout time of MPLS echo replies, in milliseconds. The value range for the time-out argument is 0 to 65535, and the default value is 2000. If the local PE does not receive an MPLS echo reply within the timeout time after sending an MPLS echo request, it determines that the MPLS echo reply times out.

-tc tc: Specifies the traffic class value in MPLS echo requests. The value range for the tc argument is 0 to 255 and the default value is 0.

Usage guidelines

In an EVPN VPLS over SRv6 network, a PE transmits data packets to a remote PE over an SRv6 PW. Use this command to test the connectivity of the SRv6 PW from the local PE to the remote PE when packet loss or traffic interruption occurs between the PEs.

Examples

# Test the connectivity of the SRv6 PW from the local PE to the remote PE attached to the host with MAC address 2-2-2 in VSI vpna.

<System> ping evpn vpls srv6 vsi vpna mac 2-2-2

Ping a remote PE in VSI vpna over SRv6 by reaching remote-MAC 0002-0002-0002: 100 data bytes.

Press CTRL+C to break.

100 bytes from 11::2: sequence=1 time=1 ms

100 bytes from 11::2: sequence=2 time=2 ms

100 bytes from 11::2: sequence=3 time=1 ms

100 bytes from 11::2: sequence=4 time=2 ms

100 bytes from 11::2: sequence=5 time=1 ms

--- Ping statistics for MAC 0002-0002-0002 ---

5 packets transmitted, 5 packets received, 0.0% packets lost

Round-trip min/avg/max = 1/1/2 ms

Table 9 Command output

Field	Description
Ping a remote PE in VSI vpna over SRv6 by reaching remote-MAC 0002-0002-0002: 100 data bytes	Ping a remote PE through an SRv6 PW in VSI vpna by reaching remote-MAC 0002-0002-0002. Each MPLS echo request contains 100 bytes.
Press CTRL+C to break	Press escape key Ctrl+C to abort the ping operation.
100 bytes from 11::2: sequence=1 time=1 ms	Received MPLS echo replies from the device whose IPv6 address is 11::2. · bytes—Number of bytes in the MPLS echo reply. · Sequence—Packet sequence, used to determine whether a segment is lost, disordered or repeated. · time—Response time. If no MPLS echo reply is received when the echo reply timeout time expires, the device displays Request time out.
Ping statistics for MAC 0002-0002-0002	Statistics on data received and sent in the ping operation.
5 packets transmitted	Number of MPLS echo requests sent.
5 packets received	Number of MPLS echo replies received.
0.0% packets lost	Percentage of unacknowledged packets to the total packets sent.
Round-trip min/avg/max = 1/1/2 ms	Minimum, average, or maximum response time, in milliseconds.

Related commands

tracert evpn vpls srv6

ping evpn vpws srv6

Use ping evpn vpws srv6 to test the connectivity of an SRv6 PW in an EVPN VPWS over SRv6 network by pinging a remote PE from the local PE.

Syntax

Views

Any view

Predefined user roles

network-admin

Parameters

xconnect-group group-name: Specifies a cross-connect group by its name, a case-sensitive string of 1 to 31 characters. The string cannot contain a hyphen (-).

local-service-id: Specifies a local service ID in the range of 1 to 16777215.

remote-service-id: Specifies a remote service ID in the range of 1 to 16777215.

end-op endop: Specifies an End.OP SID to be added to MPLS echo requests. The End.OP SID is used to locate the destination node. If you do not specify an End.OP SID, the local PE does not add an End.OP SID to MPLS echo requests.

-c count: Specifies the number of MPLS echo requests to be sent. The value range for the count argument is 1 to 4294967295, and the default value is 5.

-h hop-limit: Specifies the maximum number of hops allowed for an MPLS echo request. The value range for the hop-limit argument is 1 to 255 and the default value is 255.

-m interval: Specifies the interval at which an MPLS echo request is sent. The value range for the interval argument is 1 to 10000 milliseconds and the default value is 2000 milliseconds.

-tc tc: Specifies the traffic class value in MPLS echo requests. The value range for the tc argument is 0 to 255 and the default value is 0.

Usage guidelines

In an EVPN VPWS over SRv6 network, a PE transmits data packets to a remote PE over an SRv6 PW. Use this command to test the connectivity of the SRv6 PW from the local PE to the remote PE when packet loss or traffic interruption occurs between the PEs.

Examples

# Ping a remote PE through an SRv6 PW with local service ID 2 and remote service ID 1 in cross-connect group xcga.

<Sysname> ping evpn vpws srv6 xconnect-group xcga 2 1

Ping a remote PE over SRv6 through a PW with local service ID 2 and remote service ID 1 in cross-connect group xcga: 100 data bytes.

Press CTRL+C to break.

100 bytes from 111::100: sequence=1 time=2 ms

100 bytes from 111::100: sequence=2 time=2 ms

100 bytes from 111::100: sequence=3 time=1 ms

100 bytes from 111::100: sequence=4 time=1 ms

100 bytes from 111::100: sequence=5 time=2 ms

--- Ping statistics for the PW with local ID 2 and remote ID 1 ---

5 packets transmitted,5 packets received,0.00% packets lost

Round-trip min/avg/max = 1/1/2 ms

Table 10 Command output

Field	Description
Ping a remote PE over SRv6 through a PW with local service ID 2 and remote service ID 1 in cross-connect group xcga: 100 data bytes	Ping a remote PE through an SRv6 PW with local service ID 2 and remote service ID 1 in cross-connect group xcga. Each MPLS echo request contains 100 bytes.
Press CTRL+C to break	Press escape key Ctrl+C to abort the ping operation.
100 bytes from 111::100: sequence=5 time=1 ms	Received MPLS echo replies from the device whose IPv6 address is 111::100. · bytes—Number of bytes in the MPLS echo reply. · sequence—Packet sequence, used to determine whether a segment is lost, disordered or repeated. · time—Response time. If no MPLS echo reply is received when the echo reply timeout time expires, the device displays Request time out.
Ping statistics for the PW with local ID 2 and remote ID 1	Statistics on data received and sent in the ping operation.
5 packets transmitted	Number of MPLS echo requests sent.
5 packets received	Number of MPLS echo replies received.
0.0% packets lost	Percentage of unacknowledged packets to the total packets sent.
Round-trip min/avg/max = 1/1/2 ms	Minimum, average, or maximum response time, in milliseconds.

Related commands

tracert { evpn | static } vpws srv6

segment-routing ipv6

Use segment-routing ipv6 to specify a route recursion mode.

Use undo segment-routing ipv6 to restore the default.

Syntax

segment-routing ipv6 { best-effort | traffic-engineering | traffic-engineering best-effort }

undo segment-routing ipv6

Default

The device searches the IPv6 routing table based on the next hop of a matching route to forward traffic.

Views

EVPN instance view

Cross-connect group EVPN instance view

VSI EVPN instance view

Predefined user roles

network-admin

Parameters

best-effort: Specifies the SRv6 BE mode.

traffic-engineering: Specifies the SRv6 TE mode.

traffic-engineering best-effort: Specifies the SRv6 TE and SRv6 BE hybrid mode.

Usage guidelines

Use this command in an EVPN VPWS over SRv6 or EVPN VPLS over SRv6 network.

After the PE receives a customer packet destined for an End.DT2M, End.DT2U, End.DT2UL, End.DX2, or End.DX2L SID, it forwards the packet according to the route recursion mode.

· SRv6-BE mode—In this mode, the PE first encapsulates the SID into the packet. Then, the PE searches the IPv6 routing table based on the SID encapsulated in the packet to forward the packet.

· SRv6-TE mode—In this mode, when the PE forwards the packet, it first searches the tunnel policies for a matching SRv6 TE policy based on the color attribute or next hop of a matching route. Then, the PE adds an SRH to the packet. The SRH includes the End.DT2M, End.DT2U, End.DT2UL, End.DX2, or End.DX2L SID and the SID list of the SRv6 TE policy. Finally, the PE forwards the encapsulated packet through the SRv6 TE policy.

· SRv6-TE and SRv6-BE hybrid mode—In this mode, the PE preferentially uses the SRv6-TE mode to forward the packet. If no SRv6 TE policy is available for the packet, the PE forwards the packet in SRv6-BE mode.

Examples

# In VSI EVPN instance view, specify the SRv6 BE route recursion mode.

<Sysname> system-view

[Sysname] vsi aaa

[Sysname-vsi-aaa] evpn encapsulation srv6

[Sysname-vsi-aaa-mpls-srv6] segment-routing ipv6 best-effort

# In cross-connect group EVPN instance view, specify the SRv6 BE route recursion mode.

<Sysname> system-view

[Sysname] xconnect-group vpna

[Sysname-xcg-vpna] evpn encapsulation srv6

[Sysname-xcg-vpna-evpn-srv6] segment-routing ipv6 best-effort

segment-routing ipv6 apply-sid all-nexthop (BGP IPv4/IPv6 address family view)

Use segment-routing ipv6 apply-sid all-nexthop to dynamically allocate an End.DX4 or End.DX6 SID to each next hop of BGP IPv4 or IPv6 routes in the public network.

Use undo segment-routing ipv6 apply-sid all-nexthop to restore the default.

Syntax

segment-routing ipv6 apply-sid all-nexthop

undo segment-routing ipv6 apply-sid all-nexthop

Default

A PE allocates the End.DT4, End.DT6, or End.DT46 SID of the public instance to BGP IPv4 or IPv6 routes in the public network.

Views

BGP IPv4 unicast address family view

BGP IPv6 unicast address family view

Predefined user roles

network-admin

Usage guidelines

Use this command to forward an SRv6 decapsulated public network packet to the next hop without looking up the routing table of the public network.

This command is applicable to the public network IPv4 or IPv6 over SRv6 scenario. By default, a PE allocates the same SID to all BGP public network routes. When the PE removes the SRv6 encapsulation from a received packet, it looks up the routing table of the public network based on the SID for an optimal route. To forward the packet to the next hop without looking up the routing table, use this command.

This command dynamically allocates an End.DX4 or End.DX6 SID to each next hop for the BGP public network IPv4 or IPv6 routes. When forwarding a packet, the PE searches for the output interface and next hop based on the End.DX4 or End.DX6 SID of the packet. Then, the PE directly forwards the packet out of the output interface to the next hop.

Before you use this command in BGP IPv4 or IPv6 unicast address family view, execute the segment-routing ipv6 locator command in the same view to apply a locator to the view. This ensures successful dynamic End.DX4 or End.DX6 SID allocation.

In the same view, the segment-routing ipv6 apply-sid all-nexthop command is mutually exclusive with the segment-routing ipv6 apply-sid specify-nexthop command. Do not use both commands in the same view.

The device might be unable to dynamically allocate SIDs to BGP public network routes based on the route next hops when dynamic SID resources are insufficient. If the device does not have manually configured End.DX4 or End.DX6 SIDs, it allocates the End.DT4 SID, End.DT6 SID, or End.DT46 SID of the public instance to the routes.

The segment-routing ipv6 apply-sid all-nexthop command cannot allocate End.DX4 or End.DX6 SIDs to direct routes.

Examples

# In BGP IPv4 unicast address family view, enable the system to automatically allocate an End.DX4 SID to each next hop of BGP public network routes.

<Sysname> system-view

[Sysname] bgp 100

[Sysname-bgp-default] address-family ipv4 unicast

[Sysname-bgp-default-ipv4] segment-routing ipv6 locator aaa

[Sysname-bgp-default-ipv4] segment-routing ipv6 apply-sid all-nexthop

Related commands

segment-routing ipv6 apply-sid specify-nexthop

segment-routing ipv6 locator

segment-routing ipv6 apply-sid all-nexthop (BGP-VPN IPv4/IPv6 address family view)

Use segment-routing ipv6 apply-sid all-nexthop to dynamically allocate an End.DX4 or End.DX6 SID to each next hop of BGP private network routes.

Use undo segment-routing ipv6 apply-sid all-nexthop to restore the default.

Syntax

segment-routing ipv6 apply-sid all-nexthop [ evpn ]

undo segment-routing ipv6 apply-sid all-nexthop [ evpn ]

Default

VPN instance-based SID allocation is used for BGP private network routes.

Views

BGP-VPN IPv4 unicast address family view

BGP-VPN IPv6 unicast address family view

Predefined user roles

network-admin

Parameters

evpn: Allocates SIDs to private network routes based on the route next hops when the routes are converted to EVPN routes. If you do not specify this keyword, the command allocates SIDs to private network routes based on the route next hops when the routes are converted to BGP VPNv4 or VPNv6 routes.

Usage guidelines

Use this command to forward an SRv6 decapsulated VPN packet to the next hop without looking up the routing table of the matching VPN instance.

This command is applicable to IP L3VPN over SRv6 and EVPN L3VPN over SRv6 networks. By default, a PE allocates the same SID to all BGP private network routes of a VPN instance. When the PE removes the SRv6 encapsulation from a received packet, it looks up the routing table of the VPN instance based on the SID for an optimal route. Then, the PE forwards the packet to a CE. To forward the packet to the next hop without looking up the routing table, use this command.

This command dynamically allocates an End.DX4 or End.DX6 SID to each next hop of the BGP private network routes in a VPN instance based on the next hop addresses. When forwarding a packet, the PE searches for the output interface and next hop based on the End.DX4 or End.DX6 SID of the packet. Then, the PE directly forwards the packet out of the output interface to the next hop.

Before you use this command in BGP-VPN IPv4 or IPv6 unicast address family view, execute the segment-routing ipv6 locator command in the same view to apply a locator to the view. This ensures successful dynamic End.DX4 or End.DX6 SID allocation.

The device might be unable to dynamically allocate SIDs to BGP private network routes in a VPN instance based on the route next hops when dynamic SID resources are insufficient. If the device does not have manually configured End.DX4 or End.DX6 SIDs, it allocates the End.DT4 SID, End.DT6 SID, or End.DT46 SID of the VPN instance to the routes.

The segment-routing ipv6 apply-sid all-nexthop command cannot allocate End.DX4 or End.DX6 SIDs to direct routes.

Examples

# In BGP-VPN IPv4 unicast address family view, enable the device to dynamically allocate an End.DX4 or End.DX6 SID to each next hop of BGP private network routes.

<Sysname> system-view

[Sysname] bgp 100

[Sysname-bgp-default] ip vpn-instance vpn1

[Sysname-bgp-default-vpn1] address-family ipv4

[Sysname-bgp-default-ipv4-vpn1] segment-routing ipv6 locator aaa

[Sysname-bgp-default-ipv4-vpn1] segment-routing ipv6 apply-sid all-nexthop

Related commands

segment-routing ipv6 apply-sid specify-nexthop

segment-routing ipv6 locator

segment-routing ipv6 apply-sid specify-nexthop (BGP IPv4/IPv6 address family view)

Use segment-routing ipv6 apply-sid specify-nexthop to configure next hop-specific dynamic End.DX4 or End.DX6 SID allocation for BGP public network IPv4 or IPv6 routes, and create and enter BGP IPv4 SR or SRv6 next hop view. If the view already exists, the command directly places you in the view.

Use undo segment-routing ipv6 apply-sid specify-nexthop to restore the default.

Syntax

segment-routing ipv6 apply-sid specify-nexthop

undo segment-routing ipv6 apply-sid specify-nexthop

Default

A PE allocates the End.DT4, End.DT6, or End.DT46 SID of the public instance to BGP public network IPv4 or IPv6 routes.

Views

BGP IPv4 unicast address family view

BGP IPv6 unicast address family view

Predefined user roles

network-admin

Usage guidelines

This command is applicable to the public network IPv4 or IPv6 over SRv6 scenario.

By default, a PE allocates the same SID to all BGP public network routes. When a PE removes the SRv6 encapsulation from a received packet, it looks up the routing table of the public network based on the SID for an optimal route. To forward the packet to the next hop without looking up the routing table, use this command and the nexthop interface command.

This command and the nexthop interface command dynamically allocate an End.DX4 or End.DX6 SID to the specified next hop. When forwarding a packet, the PE searches for the output interface and next hop based on the End.DX4 or End.DX6 SID of the packet. Then, the PE directly forwards the packet out of the output interface to the next hop.

Before you use the segment-routing ipv6 apply-sid specify-nexthop command in BGP IPv4 or IPv6 unicast address family view, execute the segment-routing ipv6 locator command in the same view to apply a locator to the view. This ensures successful dynamic End.DX4 or End.DX6 SID allocation.

In the same view, the segment-routing ipv6 apply-sid specify-nexthop command is mutually exclusive with the segment-routing ipv6 apply-sid all-nexthop command. Do not use both commands in the same view.

The segment-routing ipv6 apply-sid specify-nexthop command cannot allocate End.DX4 or End.DX6 SIDs to direct routes.

Examples

# In BGP IPv4 unicast address family view, configure next hop-specific dynamic End.DX4 SID allocation for BGP public network IPv4 routes, and create and enter BGP IPv4 SR next hop view.

<Sysname> system-view

[Sysname] bgp 100

[Sysname-bgp-default] address-family ipv4 unicast

[Sysname-bgp-default-ipv4] segment-routing ipv6 locator aaa

[Sysname-bgp-default-ipv4] segment-routing ipv6 apply-sid specify-nexthop

[Sysname-bgp-default-sid-np-ipv4]

Related commands

nexthop interface

segment-routing ipv6 apply-sid all-nexthop

segment-routing ipv6 locator

segment-routing ipv6 apply-sid specify-nexthop (BGP-VPN IPv4/IPv6 address family view)

Use segment-routing ipv6 apply-sid specify-nexthop to configure next hop-specific dynamic End.DX4 or End.DX6 SID allocation for BGP private network IPv4 or IPv6 routes, and create and enter BGP-VPN IPv4 SR or SRv6 next hop view. If the view already exists, the command directly places you in the view.

Use undo segment-routing ipv6 apply-sid specify-nexthop to restore the default.

Syntax

segment-routing ipv6 apply-sid specify-nexthop [ evpn ]

undo segment-routing ipv6 apply-sid specify-nexthop [ evpn ]

Default

A PE allocates the End.DT4, End.DT6, or End.DT46 SID of a VPN instance to the BGP private network IPv4 or IPv6 routes of that VPN instance.

Views

BGP-VPN IPv4 unicast address family view

BGP-VPN IPv6 unicast address family view

Predefined user roles

network-admin

Parameters

evpn: Enables next hop-specific dynamic End.DX4 or End.DX6 SID allocation for private network routes when the routes are converted to BGP EVPN routes in an EVPN L3VPN over SRv6 network. If you do not specify this keyword, this command enables nexthop-specific dynamic End.DX4 or End.DX6 SID allocation for private network routes when the routes are converted to BGP VPNv4 or VPNv6 routes.

Usage guidelines

This command is applicable to the IP L3VPN over SRv6 and EVPN L3VPN over SRv6 scenarios.

By default, a PE allocates the same SID to all BGP routes of a VPN instance. When the PE removes the SRv6 encapsulation from a received packet, it looks up the routing table of the VPN instance based on the SID for an optimal route. Then, the PE forwards the packet to a CE. To forward the packet to the next hop without looking up the routing table, use this command and the nexthop interface command.

Before you use the segment-routing ipv6 apply-sid specify-nexthop command in BGP-VPN IPv4 or IPv6 unicast address family view, execute the segment-routing ipv6 locator command in the same view to apply a locator to the view. This ensures successful dynamic End.DX4 or End.DX6 SID allocation.

The segment-routing ipv6 apply-sid specify-nexthop command cannot allocate End.DX4 or End.DX6 SIDs to direct routes.

Examples

# In BGP-VPN IPv4 unicast address family view, configure next hop-specific dynamic End.DX4 SID allocation for BGP private network IPv4 routes, and create and enter BGP-VPN IPv4 SR next hop view.

<Sysname> system-view

[Sysname] bgp 100

[Sysname-bgp-default] ip vpn-instance vpn1

[Sysname-bgp-default-vpn1] address-family ipv4 unicast

[Sysname-bgp-default-ipv4-vpn1] segment-routing ipv6 locator aaa

[Sysname-bgp-default-ipv4-vpn1] segment-routing ipv6 apply-sid specify-nexthop

[Sysname-bgp-default-sid-np-ipv4]

Related commands

nexthop interface

segment-routing ipv6 apply-sid all-nexthop

segment-routing ipv6 locator

segment-routing ipv6 best-effort

Use segment-routing ipv6 best-effort to recurse routes to SRv6-BE tunnels.

Use undo segment-routing ipv6 best-effort to restore the default.

Syntax

In BGP-VPN IPv4 unicast address family view or BGP-VPN IPv6 unicast address family view:

segment-routing ipv6 best-effort [ evpn ]

undo segment-routing ipv6 best-effort [ evpn ]

In BGP IPv4 unicast address family view or BGP IPv6 unicast address family view:

segment-routing ipv6 best-effort

undo segment-routing ipv6 best-effort

Default

A PE searches the IPv6 routing table based on the next hop of a matching route to forward traffic.

Views

BGP-VPN IPv4 unicast address family view

BGP-VPN IPv6 unicast address family view

BGP IPv4 unicast address family view

BGP IPv6 unicast address family view

Predefined user roles

network-admin

Parameters

evpn: Recurses EVPN routes to SRv6-BE tunnels. If you do not specify this keyword, the device recurses BGP VPNv4 or VPNv6 routes to SRv6-BE tunnels.

Usage guidelines

This command is applicable to the IP L3VPN over SRv6, EVPN L3VPN over SRv6, and public network IP over SRv6 scenarios. This command enables a PE to forward packets by looking up the IPv6 routing table based on the SRv6 SIDs in the packets.

Use this command in different address family views according to your network scenario.

· In the IPv4 or IPv6 L3VPN over SRv6 network and the EVPN L3VPN over SRv6 network, use this command in BGP-VPN IPv4 unicast address family view or BGP-VPN IPv6 unicast address family view.

· In the public network IPv4 or IPv6 over SRv6 network, use this command in BGP IPv4 unicast address family view or BGP IPv6 unicast address family view.

Examples

# In BGP-VPN IPv4 unicast address family view, recurse private network routes to SRv6-BE tunnels.

<Sysname> system-view

[Sysname] bgp 100

[Sysname-bgp-default] ip vpn-instance vpn1

[Sysname-bgp-default-vpn1] address-family ipv4

[Sysname-bgp-default-ipv4-vpn1] segment-routing ipv6 best-effort

# In BGP-VPN IPv6 unicast address family view, recurse private network routes to SRv6-BE tunnels.

<Sysname> system-view

[Sysname] bgp 100

[Sysname-bgp-default] ip vpn-instance vpn1

[Sysname-bgp-default-vpn1] address-family ipv6

[Sysname-bgp-default-ipv6-vpn1] segment-routing ipv6 best-effort

Related commands

segment-routing ipv6 locator

Use segment-routing ipv6 locator to apply a locator to a BGP family.

Use undo segment-routing ipv6 locator to restore the default.

Syntax

In BGP-VPN IPv4 unicast address family view or BGP-VPN IPv6 unicast address family view:

segment-routing ipv6 locator locator-name [ evpn ] [ auto-sid-disable ]

undo segment-routing ipv6 locator [ evpn ]

In BGP IPv4 unicast address family view or BGP IPv6 unicast address family view:

segment-routing ipv6 locator locator-name [ auto-sid-disable ]

undo segment-routing ipv6 locator

Default

No locator is applied to a BGP family.

Views

BGP-VPN IPv4 unicast address family view

BGP-VPN IPv6 unicast address family view

BGP IPv4 unicast address family view

BGP IPv6 unicast address family view

Predefined user roles

network-admin

Parameters

locator-name: Specifies a locator by its name, a case-sensitive string of 1 to 31 characters. The specified locator must exist.

evpn: Adds the SID attribute to private network routes when the routes are converted to EVPN routes. If you do not specify this keyword, the command adds the SID attribute to private network routes when the routes are converted to BGP VPNv4 or VPNv6 routes.

auto-sid-disable: Disables automatic SRv6 SID allocation. If you do not specify this keyword, the device allows dynamically allocated SRv6 SIDs. If static SRv6 SIDs are configured when automatic SRv6 SID allocation is enabled, the static SRv6 SIDs take precedence. If no static SRv6 SIDs are configured when automatic SRv6 SID allocation is enabled, the system dynamically allocates SRv6 SIDs.

Usage guidelines

Use this command to enable a BGP family to use BGP routes to advertise SRv6 SIDs in the specified locator.

If you execute this command multiple times for the same address family, the most recent configuration takes effect.

Examples

# Apply locator abc to BGP-VPN IPv4 unicast address family view.

<Sysname> system-view

[Sysname] bgp 100

[Sysname-bgp-default] ip vpn-instance vpn1

[Sysname-bgp-default-vpn1] address-family ipv4

[Sysname-bgp-default-ipv4-vpn1] segment-routing ipv6 locator abc

# Apply locator abc to BGP-VPN IPv6 unicast address family view.

<Sysname> system-view

[Sysname] bgp 100

[Sysname-bgp-default] ip vpn-instance vpn1

[Sysname-bgp-default-vpn1] address-family ipv6

[Sysname-bgp-default-ipv6-vpn1] segment-routing ipv6 locator abc

# Apply locator abc to BGP-VPN IPv6 unicast address family view.

<Sysname> system-view

[Sysname] bgp 100

[Sysname-bgp-default] ip vpn-instance vpn1

[Sysname-bgp-default-vpn1] address-family ipv6

[Sysname-bgp-default-ipv6-vpn1] segment-routing ipv6 locator abc evpn

segment-routing ipv6 locator (cross-connect view, EVPN instance view, and VSI EVPN instance view)

Use segment-routing ipv6 locator to apply an SRv6 locator to a cross-connect or a VSI.

Use undo segment-routing ipv6 locator to remove the specified SRv6 locator from a cross-connect or a VSI.

Syntax

In cross-connect view:

segment-routing ipv6 locator locator-name [ dx2l-locator dx2l-locator-name ] [ auto-sid-disable ]

undo segment-routing ipv6 locator

In VSI EVPN instance view:

segment-routing ipv6 locator locator-name [ dt2u-locator dt2u-locator-name ] [ dt2ul-locator dt2ul-locator-name ] [ dx2-locator dx2-locator-name ] [ dx2l-locator dx2l-locator-name ] [ auto-sid-disable ]

undo segment-routing ipv6 locator

In EVPN instance view:

segment-routing ipv6 locator locator-name [ dt2u-locator dt2u-locator-name ] [ dt2ul-locator dt2ul-locator-name ] [ auto-sid-disable ]

undo segment-routing ipv6 locator

Default

No SRv6 locators are applied to a cross-connect or a VSI.

Views

Cross-connect view

EVPN instance view

VSI EVPN instance view

Predefined user roles

network-admin

Parameters

locator-name: Specifies a locator by its name, a case-sensitive string of 1 to 31 characters.

dx2l-locator dx2l-locator-name: Specifies the locator used to apply for End.DX2L SIDs. The dx2l-locator-name argument represents the locator name, a case-sensitive string of 1 to 31 characters.

dt2u-locator dt2u-locator-name: Specifies the locator used to apply for End.DT2U SIDs. The dt2u-locator-name argument represents the locator name, a case-sensitive string of 1 to 31 characters.

dt2ul-locator dt2ul-locator-name: Specifies the locator used to apply for End.DT2UL SIDs. The dt2ul-locator-name argument represents the locator name, a case-sensitive string of 1 to 31 characters.

dx2-locator dx2-locator-name: Specifies the locator used to apply for End.DX2 SIDs. The dx2-locator-name argument represents the locator name, a case-sensitive string of 1 to 31 characters.

auto-sid-disable: Disables automatic SID allocation. If no opcode is configured for the locator specified in this command when automatic SID allocation is disabled, SID application fails. If you do not specify this keyword, automatic SID allocation is enabled and static SRv6 SIDs and dynamic SRv6 SIDs can coexist. The static SRv6 SIDs take precedence over the dynamically allocated SRv6 SIDs.

Usage guidelines

Use this command to enable a cross-connect or VSI to apply for SRv6 SIDs from the specified locator.

In cross-connect view:

· If you specify the dx2l-locator dx2l-locator-name option, the locator-name argument applies for End.DX2 SIDs and the dx2l-locator-name argument applies for End.DX2L SIDs.

· If you do not specify the dx2l-locator dx2l-locator-name option, the locator-name argument applies for both End.DX2 SIDs and End.DX2L SIDs.

In VSI EVPN instance view:

· If you do not specify the dt2u-locator dt2u-locator-name, dt2ul-locator dt2ul-locator-name, dx2-locator dx2-locator-name, or dx2l-locator dx2l-locator-name option, the locator-name argument applies for End.DT2M, End.DT2U, End.DT2UL, End.DX2, and End.DX2L SIDs.

· If you specify the dt2u-locator dt2u-locator-name, dt2ul-locator dt2ul-locator-name, dx2-locator dx2-locator-name, or dx2l-locator dx2l-locator-name option, the option applies for End.DT2U, End.DT2UL, End.DX2, or End.DX2L SIDs and the locator-name argument applies for other SRv6 SIDs.

In EVPN instance view:

· If you do not specify the dt2u-locator dt2u-locator-name or dt2ul-locator dt2ul-locator-name option, the locator-name argument applies for End.DT2M, End.DT2U, and End.DT2UL SIDs.

· If you do not specify the dt2u-locator dt2u-locator-name or dt2ul-locator dt2ul-locator-name option, the option applies for End.DT2U or End.DT2UL SIDs and the locator-name argument applies for other SRv6 SIDs.

Examples

# Configure VSI aaa to use locator test1 to apply for End.DT2M, End.DT2UL, End.DX2, and End.DX2L SIDs and use locator test2 to apply for End.DT2U SIDs.

<Sysname> system-view

[Sysname] vsi aaa

[Sysname-vsi-aaa] evpn encapsulation srv6

[Sysname-vsi-aaa-evpn-srv6] segment-routing ipv6 locator test1 dt2u-locator test2

# Configure cross-connect aaa in cross-connect group bbb to use locator test3 to apply for End.DX2 and End.DX2L SIDs and disable automatic SID allocation.

<Sysname> system-view

[Sysname] xconnect-group bbb

[Sysname-xcg-bbb] evpn encapsulation srv6

[Sysname-xcg-bbb-evpn-srv6] quit

[Sysname-xcg-bbb] connection aaa

[Sysname-xcg-bbb-connection-aaa] segment-routing ipv6 locator test3 auto-sid-disable

segment-routing ipv6 locator anycast

Use segment-routing ipv6 locator anycast to apply an anycast locator to a BGP family.

Use undo segment-routing ipv6 locator anycast to restore the default.

Syntax

In BGP-VPN IPv4 unicast address family view or BGP-VPN IPv6 unicast address family view:

segment-routing ipv6 locator locator-name anycast [ evpn ]

undo segment-routing ipv6 locator anycast

In BGP IPv4 unicast address family view or BGP IPv6 unicast address family view:

segment-routing ipv6 locator locator-name anycast

undo segment-routing ipv6 locator anycast

Default

No locator is applied to a BGP family.

Views

BGP-VPN IPv4 unicast address family view

BGP-VPN IPv6 unicast address family view

BGP IPv4 unicast address family view

BGP IPv6 unicast address family view

Predefined user roles

network-admin

Parameters

locator-name: Specifies an anycast locator by its name, a case-sensitive string of 1 to 31 characters.

evpn: Uses EVPN routes to advertise the SRv6 SIDs in the anycast locator. If you do not specify this keyword, BGP uses VPNv4 or VPNv6 routes to advertise the SRv6 SIDs in the anycast locator.

Usage guidelines

Use this command to enable a BGP family to use BGP routes to advertise SRv6 SIDs in an anycast locator. Multiple IPv6 peers configured with the same locator can share load.

Before executing this command, you need to execute the anycast enable command in the locators of a group of PEs to ensure that the PEs use the same locator.

After you execute this command in an IP L3VPN over SRv6 network or public network IP over SRv6 network, execute the peer prefix-sid command with the anycast keyword, so the device can exchange the SRv6 SIDs in the anycast locator with the specified peer.

After you execute this command in an EVPN L3VPN over SRv6 network, you must also execute the peer advertise encap-type srv6 command with the anycast keyword in order to advertise the SRv6 SIDs in the anycast locator through EVPN routes.

This command applies only to the static SRv6 SIDs in the specified anycast locator.

If you execute this command multiple times for the same address family, the most recent configuration takes effect.

Examples

# Apply anycast locator abc to BGP-VPN IPv4 unicast address family.

<Sysname> system-view

[Sysname] bgp 100

[Sysname-bgp-default] ip vpn-instance vpn1

[Sysname-bgp-default-vpn1] address-family ipv4

[Sysname-bgp-default-ipv4-vpn1] segment-routing ipv6 locator abc anycast

# Apply anycast locator abc to BGP IPv4 unicast address family.

<Sysname> system-view

[Sysname] bgp 100

[Sysname-bgp-default] address-family ipv4

[Sysname-bgp-default-ipv4] segment-routing ipv6 locator abc anycast

Related commands

anycast enable

peer advertise encap-type srv6

peer prefix-sid

segment-routing ipv6 traffic-engineering

Use segment-routing ipv6 traffic-engineering to recurse routes to SRv6 TE policy tunnels.

Use undo segment-routing ipv6 traffic-engineering to restore the default.

Syntax

In BGP-VPN IPv4 unicast address family view or BGP-VPN IPv6 unicast address family view:

segment-routing ipv6 traffic-engineering [ best-effort | best-effort-backup ] [ evpn ]

undo segment-routing ipv6 traffic-engineering [ best-effort | best-effort-backup ] [ evpn ]

In BGP IPv4 unicast address family view or BGP IPv6 unicast address family view:

segment-routing ipv6 traffic-engineering [ best-effort | best-effort-backup ]

undo segment-routing ipv6 traffic-engineering [ best-effort | best-effort-backup ]

Default

A PE searches the IPv6 routing table based on the next hop of a matching route to forward traffic.

Views

BGP-VPN IPv4 unicast address family view

BGP-VPN IPv6 unicast address family view

BGP IPv4 unicast address family view

BGP IPv6 unicast address family view

Predefined user roles

network-admin

Parameters

best-effort: Switches to the SRv6-BE route recursion mode when the matching SRv6 TE policy tunnel fails for L3VPN traffic. With this keyword, a PE looks up the routing table for the End.DT4, End.DT6, or End.DT46 SID of a packet to forward that packet when the matching SRv6 TE policy tunnel fails. If you do not specify this keyword, the PE looks up the routing table based on the destination IP address of a packet to forward that packet when the matching SRv6 TE policy tunnel fails.

best-effort-backup: Implements FRR by using the SRv6 TE path (primary path) and SRv6 BE path (backup path). If the SRv6 TE path fails or does not exist, traffic is immediately switched to the SRv6 BE path to ensure service continuity. If multiple SRv6 BE paths exist between the source and destination nodes, the SRv6 BE path with the lowest next hop address is selected as the backup path.

evpn: Recurses the private network routes based on the SID attribute in EVPN routes. If you do not specify this keyword, the device recurses the private network routes based on the SID attribute in BGP VPNv4 or VPNv6 routes.

Usage guidelines

This command enables PEs to recurse routes to SRv6 TE policy tunnels and use the tunnels to forward L3VPN traffic between the PEs.

To improve high availability for L3VPN packet forwarding, specify the best-effort or best-effort-backup keyword. A PE forwards an L3VPN packet as follows:

1. The PE forwards the packet through the matching SRv6 TE policy tunnel.

2. If the matching SRv6 TE policy tunnel fails, the PE forwards the packet in SRv6-BE mode.

¡ If the best-effort keyword is specified, the device performs IPv6 routing table lookup based on the encapsulated SRv6 SID, and forwards the packet in SRv6 BE mode.

¡ If the best-effort-backup keyword is specified, the device quickly switches the packet to the SRv6 BE backup path.

¡ If the best-effort or best-effort-backup keyword is specified, the device only forwards the packet through the SRv6 BE path or SRv6 BE backup path. If SRv6 BE forwarding fails, the device will not forward the packet through other SRv6 TE policies.

3. If the packet forwarding still fails in SRv6-BE mode, the PE forwards the packet by looking up the routing table based on the destination IP address of the packet.

4. If the packet forwarding still fails, the PE drops the packet.

Use this command in different address family views according to your network scenario.

· In the IPv4 or IPv6 L3VPN over SRv6 network and the EVPN L3VPN over SRv6 network, use this command in BGP-VPN IPv4 unicast address family view or BGP-VPN IPv6 unicast address family view.

· In the public network IPv4 or IPv6 over SRv6 scenario, use this command in BGP IPv4 unicast address family view or BGP IPv6 unicast address family view.

This command is mutually exclusive with the segment-routing ipv6 best-effort command.

Examples

# In BGP IPv4 unicast address family view, recurse routes to SRv6 TE policy tunnels.

<Sysname> system-view

[Sysname] bgp 100

[Sysname-bgp-default] address-family ipv4

[Sysname-bgp-default-ipv4] segment-routing ipv6 traffic-engineering

Related commands

segment-routing ipv6 best-effort

srv6-pw-type

Use srv6-pw-type to configure the SRv6 PW data encapsulation type.

Use undo srv6-pw-type to restore the default.

Syntax

srv6-pw-type { ethernet | vlan }

undo srv6-pw-type

Default

No SRv6 PW data encapsulation type is specified.

Views

PW class view

SRv6-encapsulated VSI EVPN instance view

Predefined user roles

network-admin

Parameters

ethernet: Specifies the SRv6 PW data encapsulation type as Ethernet.

vlan: Specifies the SRv6 PW data encapsulation type as VLAN.

Usage guidelines

When the SRv6 PW data encapsulation type is Ethernet, traffic transmitted on the SRv6 PW cannot carry the P-tag assigned by the service provider.

· For a packet received from the CE:

¡ If the packet has the P-tag, the PE removes the P-tag and then adds a SID into the packet before forwarding it.

¡ If the packet does not have the P-tag, the PE adds a SID into the packet before forwarding it.

· For a packet to be sent to the CE:

¡ If the AC access mode (configured by using the ac interface command) is VLAN, the PE adds the P-tag and forwards the packet to the CE.

¡ If the AC access mode is Ethernet, the PE directly forwards the packet to the CE. The PE cannot modify or delete any existing tag in the packet.

When the SRv6 PW data encapsulation type is VLAN, traffic transmitted on the SRv6 PW must carry the P-tag assigned by the service provider.

· For a packet received from the CE:

¡ If the packet has the P-tag, the PE keeps the P-tag and adds a SID into the packet before forwarding it.

¡ If the packet does not have the P-tag, the PE adds a P-tag of 1 and then adds a SID into the packet before forwarding it.

· For a packet to be sent to the CE:

¡ If the AC access mode (configured by using the ac interface command) is VLAN, the PE modifies or keeps the P-tag and forwards the packet to the CE.

¡ If the AC access mode is Ethernet, the PE removes the P-tag and forwards the packet to the CE.

In an EVPN VPLS over SRv6 network, you can configure the SRv6 PW data encapsulation type by using the following methods:

· Configure the SRv6 PW data encapsulation type in PW class view, and then configure the EVPN instance to use the PW class.

· Configure the SRv6 PW data encapsulation type in SRv6-encapsulated VSI EVPN instance view.

If you configure the SRv6 PW data encapsulation type by using both methods, the setting in SRv6-encapsulated VSI EVPN instance view has a higher priority.

Examples

# In PW class view, configure the SRv6 PW data encapsulation type as Ethernet.

<Sysname> system-view

[Sysname] pw-class pw100

[Sysname-pw-pw100] srv6-pw-type ethernet

# In SRv6-encapsulated VSI EVPN instance view, configure the SRv6 PW data encapsulation type as Ethernet.

<Sysname> system-view

[Sysname] vsi vpna

[Sysname-vsi-vpna] evpn encapsulation srv6

[Sysname-vsi-vpna-evpn-srv6] srv6-pw-type ethernet

tracert evpn vpls srv6

Use tracert evpn vpls srv6 to trace the path of an SRv6 PW from the local PE to the remote PE in an EVPN VPLS over SRv6 network.

Syntax

tracert evpn vpls srv6 vsi vsi-name mac mac-address [ end-op endop ] [ -a source-ipv6 | -h hop-limit | -r reply-mode | -t time-out | -tc tc ] *

Views

Any view

Predefined user roles

network-admin

Parameters

vsi vsi-name: Specifies a VSI by its name, a case-sensitive string of 1 to 31 characters.

mac mac-address: Specifies a host attached to a remote PE by its MAC address in H-H-H format. Do not specify a broadcast MAC address, multicast MAC address, or all-zeros MAC address.

-a source-ipv6: Specifies the source IPv6 address of MPLS echo requests. If you do not specify a source IPv6 address, the IPv6 address of the traffic output interface is used as the source IPv6 address of MPLS echo requests.

-h hop-limit: Specifies the maximum number of hops allowed for an MPLS echo request. The value range for the hop-limit argument is 1 to 255, and the default value is 255.

-tc tc: Specifies the traffic class value in MPLS echo replies. The value range for the tc argument is 0 to 255 and the default value is 0.

Usage guidelines

In an EVPN VPLS over SRv6 network, a PE transmits data packets to a remote PE over an SRv6 PW. Use this command to trace the path of the SRv6 PW from the local PE to the remote PE when packet loss or traffic interruption occurs between the PEs. This command helps you locate the failed nodes on the path.

Examples

# Trace route to a remote PE through an SRv6 PW in VSI vpna by reaching remote-MAC 0002-0002-0002.

<Sysname> tracert evpn vpls srv6 vsi vpna mac 2-2-2

Trace route to a remote PE in VSI vpna over SRv6 by reaching remote-MAC 0002-0002-0002.

Press CTRL+C to break.

Hop Wait time Type Replier

0 0 ms Ingress

1 4 ms Transit 1111::2

2 5 ms Transit 2222::2

3 6 ms Transit 3333::2

4 6 ms Egress 4444::2

Table 11 Command output

Field	Description
Trace route to a remote PE in VSI vpna over SRv6 by reaching remote-MAC 0002-0002-0002	Trace route to a remote PE through an SRv6 PW in VSI vpna by reaching remote-MAC 0002-0002-0002.
Press CTRL+C to break	Press escape key Ctrl+C to abort the tracert operation.
Hop	Hop number.
Wait time	Interval between the time when an echo request was sent and the time when the reply of the echo request was received. The unit is millisecond.
Type	Node type: · Ingress. · Transit. · Egress.
Replier	IPv6 address of the node.
Request time out	This field is available if the local PE does not receive any MPLS echo reply to an MPLS echo request when the echo reply timeout time expires.

Related commands

ping evpn vpls srv6

tracert evpn vpws srv6

Use tracert evpn vpws srv6 to trace the path of an SRv6 PW from the local PE to the remote PE in an EVPN VPWS over SRv6 network.

Syntax

tracert evpn vpws srv6 xconnect-group group-name local-service-id remote-service-id [ end-op endop ] [ -a source-ip | -h hop-limit | -r reply-mode | -t time-out | -tc tc ] *

Views

Any view

Predefined user roles

network-admin

Parameters

xconnect-group group-name: Specifies a cross-connect group by its name, a case-sensitive string of 1 to 31 characters. The string cannot contain a hyphen (-).

local-service-id: Specifies a local service ID in the range of 1 to 16777215.

remote-service-id: Specifies a remote service ID in the range of 1 to 16777215.

-a source-ip: Specifies the source IPv6 address of MPLS echo requests. If you do not specify a source IPv6 address, the IPv6 address of the traffic output interface is used as the source IPv6 address of MPLS echo requests.

-h hop-limit: Specifies the maximum number of hops allowed for an MPLS echo request. The value range for the hop-limit argument is 1 to 255, and the default value is 255.

-r reply-mode: Specifies the reply mode used by the receiver (the remote PE) to reply to an MPLS echo request. The value for the reply-mode argument can be 2 or 4, and the default value is 2. If the mode is 2, the receiver searches the IP forwarding table for the destination IP address to forward MPLS echo replies. If the mode is 4, the receiver searches the IPv6 routing table for the source IPv6 address of the echo requests, encapsulates an SRH to the replies, and forwards them.

-tc tc: Specifies the traffic class value in MPLS echo replies. The value range for the tc argument is 0 to 255 and the default value is 0.

Usage guidelines

In an EVPN VPWS over SRv6 network, a PE transmits data packets to a remote PE over an SRv6 PW. Use this command to trace the path of the SRv6 PW from the local PE to the remote PE when packet loss or traffic interruption occurs between the PEs. This command helps you locate the failed nodes on the path.

Examples

# Trace the route that an SRv6 PW traverses from the local PE to the remote PE in an EVPN VPWS over SRv6 network. The SRv6 PW belongs to cross-connect group xcga, its local service ID is 2, and its remote service ID is 1.

<Sysname> tracert evpn vpws srv6 xconnect-group xcga 1 2

Trace route to a remote PE over SRv6 through a PW with local service ID 2 and remote service ID 1 in cross-connect group xcga.

Press CTRL+C to break.

Hop Wait time Type Replier

0 0 ms Ingress

1 4 ms Transit 1111::2

2 5 ms Transit 2222::2

3 6 ms Transit 3333::2

4 6 ms Egress 3333::2

Table 12 Command output

Field	Description
Trace route to a remote PE over SRv6 through a PW with local service ID 2 and remote service ID 1 in cross-connect group xcga	Trace route to a remote PE through an SRv6 PW with local service ID 2 and remote service ID 1 in cross-connect group xcga.
Hop	Hop number.
Wait time	Interval between the time when an echo request was sent and the time when the reply of the echo request was received. The unit is millisecond.
Press CTRL+C to break	Press escape key Ctrl+C to abort the tracert operation.
Type	Node type: · Ingress. · Transit. · Egress.
Replier	IPv6 address of the node.
Request time out	This field is available if the local PE does not receive any MPLS echo reply to an MPLS echo request when the echo reply timeout time expires.

Related commands

ping evpn vpws srv6

unicast-forwarding dx2-based

Use unicast-forwarding dx2-based to configure unicast traffic forwarding based on End.DX2 and End.DX2L SIDs in an EVPN VPLS over SRv6 network.

Use undo unicast-forwarding dx2-based to restore the default.

Syntax

unicast-forwarding dx2-based

undo unicast-forwarding dx2-based

Default

Unicast traffic is forwarded based on End.DT2U and End.DT2UL SIDs in an EVPN VPLS over SRv6 network.

Views

VSI EVPN instance view

Predefined user roles

network-admin

Usage guidelines

By default, when a PE receives a packet that includes an End.DT2U or End.DT2UL SID, it looks up the MAC address table of the SID's VSI to forward the packet.

To improve forwarding efficiency, use this command. This command enables the PE to allocate an End.DX2 or End.DX2L SID to each AC associated with a VSI and advertise the SIDs to remote PEs through MAC/IP advertisement routes. When the PE receives an SRv6 packet that contains a locally allocated End.DX2 or End.DX2L SID, it does not look up the MAC address table. The PE directly forwards the packet to the AC that is associated with the SID after removing the SRv6 encapsulation.

Examples

# Configure EVPN VPLS over SRv6 to forward unicast traffic based on End.DX2 and End.DX2L SIDs.

<Sysname> system-view

[Sysname] vsi aaa

[Sysname-vsi-aaa] evpn encapsulation srv6

[Sysname-vsi-aaa-evpn-srv6] unicast-forwarding dx2-based

Related commands

segment-routing ipv6 locator (cross-connect view and VSI EVPN instance view)

10-Segment Routing Command Reference

Application scenarios

Operating mechanism

Restrictions and guidelines

peer advertise encap-type srv6

segment-routing ipv6 apply-sid all-nexthop (BGP-VPN IPv4/IPv6 address family view)

Intelligent Terminal Products

Product Support Services

Technical Service Solutions

Resource Center

Policy

Online Help

Become a Partner

Partner Policy & Program

Global Learning

Partner Sales Resources

Service Business

News & Events

Contact Us