Table of Contents

Related Documents

02-SRv6 VPN overview

Title	Size	Download
02-SRv6 VPN overview	290.39 KB

SRv6 VPN commands

Field	Description
Link ID	Link ID of the SRv6 tunnel in the VSI or cross-connect group.
Type	This field is not supported in the current software version. Route recursion mode. BE—SRv6-BE mode. In this mode, the PE first encapsulates the End.DX2 or End.DX2L 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.
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	Data encapsulation type of the SRv6 PW, which can be Ethernet or VLAN. If no SRv6 PW data encapsulation 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	This field is not supported in the current software version. 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	Data encapsulation type of the SRv6 PW, which can be Ethernet or VLAN. If no SRv6 PW data encapsulation 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 NHLFE IDs	This field is not supported in the current software version. NHLFE 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 (-).
Color	This field is not supported in the current software version. Color attribute of the expected SRv6 TE policy for route recursion. If no color attribute is available, this field displays a hyphen (-).
Color-Only	This field is not supported in the current software version. Color-Only flag, indicating that the Extended Color Community is used to steering traffic to an SRv6 TE policy or SR-MPLS TE policy. Values include: · 00—A BGP route can be recursed to an SRv6 TE policy/SR-MPLS TE policy when the route strictly matches both the endpoint and color of the policy. · 01—Besides the strictly matching BGP routes, the BGP routes with only matching color value can also be recursed to an SRv6 TE policy/SR-MPLS TE policy when the policy endpoint is 0.0.0.0 or 0::0. · 10—A BGP route can be recursed to an SRv6 TE policy or SR-MPLS TE policy when the route matches the color of the policy. The endpoint of the policy can be any IPv4 or IPv6 address. · 11—Undefined.
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.
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 dectected—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. · Admin 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.
ESI	ESI of the VSI.
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.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.

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

25GE1/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

25GE1/0/1 0x0 Up

Statistics: Disabled

# 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

25GE1/0/4 srv1 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	SRv6 tunnel information.
Peer	IPv6 address of the SRv6 tunnel remote PE.
Link ID	Link ID of the SRv6 tunnel on the cross-connect.
State	SRv6 tunnel 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, specify 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

VSI instance 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

# In a cross-connect group, create an EVPN instance that uses SRv6 encapsulation 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 obtained as next hops through route recursion.

Usage guidelines

Application scenarios

In the IP L3VPN over SRv6 BE, EVPN L3VPN over SRv6 BE, or 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 by the peer PE (the SRv6 locators are next hop addresses obtained through route recursion for private or public network routes).

Operating mechanism

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

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.

<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 VLAN-interface 10 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 vlan-interface 10

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 VLAN-interface 10 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 vlan-inteface 10

Related commands

opcode

peer advertise original-route

Use peer advertise original-route to enable the device to advertise original BGP VPNv4, VPNv6, or EVPN routes to a peer or peer group.

Use undo peer advertise original-route to restore the default.

Syntax

peer { group-name | ipv4-address [ mask-length ] | ipv6-address [ prefix-length ] } advertise original-route

undo peer { group-name | ipv4-address [ mask-length ] | ipv6-address [ prefix-length ] } advertise original-route

Default

The device advertises reoriginated BGP VPNv4, VPNv6, or EVPN routes to peers and peer groups after the peer re-originated command is executed.

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 a peer group by its name, a case-sensitive string of 1 to 47 characters. The peer group must exist.

ipv4-address: Specifies a peer by its IPv4 address. The peer must exist.

mask-length: Specifies a mask length in the range of 0 to 32. To specify a subnet, you must specify both the ipv4-address and mask-length arguments.

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.

Usage guidelines

For this command to take effect, you must execute the peer re-originated command.

The device configured with the peer re-originated command advertises only reoriginated BGP VPNv4, VPNv6, or EVPN routes. For the device to advertise both original and reoriginated BGP VPNv4, VPNv6, or EVPN routes to a peer or peer group, execute the peer advertise original-route command on the device.

Examples

# In BGP VPNv4 address family view, enable the device to advertise original BGP VPNv4 routes to peer 1.1.1.1.

<Sysname> system-view

[Sysname] bgp 100

[Sysname-bgp-default] address-family vpnv4

[Sysname-bgp-default-vpnv4] peer 1.1.1.1 advertise original-route

Related commands

peer re-originated

peer suppress re-originated

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 re-originated (BGP EVPN address family view)

Use peer re-originated to enable the device to reoriginate BGP EVPN routes based on the BGP EVPN routes received from a peer or peer group.

Use undo peer re-originated to disable the device from reoriginating BGP EVPN routes based on the BGP EVPN routes received from a peer or peer group.

Syntax

peer { group-name | ipv4-address [ mask-length ] | ipv6-address [ prefix-length ] } re-originated [ ip-prefix ] [ replace-rt | stitch-l3vpn ]

peer { group-name | ipv6-address [ prefix-length ] } re-originated [ ip-prefix ] [ replace-rt ] replace-sid

undo peer { group-name | ipv4-address [ mask-length ] | ipv6-address [ prefix-length ] } re-originated [ ip-prefix ]

Default

The device does not reoriginate BGP EVPN routes based on received EVPN routes.

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.

ipv4-address: Specifies a peer by its IPv4 address. The peer must exist.

mask-length: Specifies a mask length in the range of 0 to 32. To specify a subnet, you must specify both the ipv4-address and mask-length arguments.

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.

ip-prefix: Modifies IP prefix advertisement routes.

replace-rt: Replaces the L3 VXLAN ID, RD, and route targets of EVPN IP prefix advertisement routes with those of the matching local VPN instance, and adds MPLS labels or SRv6 SIDs to the routes if the replace-sid keyword is not specified or reallocates SRv6 SIDs to the routes in the matching local VPN instance if the replace-sid keyword is specified. If you do not specify the replace-rt keyword, the device performs the same operations except that it does not replace the route targets.

replace-sid: Deletes the SRv6 SIDs carried in the received BGP EVPN routes and reallocates SRv6 SIDs to the routes in the matching local VPN instance. If you do not specify this keyword, the device does not replace the SRv6 SIDs of routes.

stitch-l3vpn: Reoriginates IP prefix advertisement routes as VPNv4/VPNv6 routes without modifying the RD and route targets of the routes.

Usage guidelines

Application scenarios

Use this command without the stitch-l3vpn keyword on an ASBR that connects the EVPN L3VPN and EVPN L3VPN over SRv6 networks. This command enables the ASBR to modify EVPN route information to realize intercommunication between the MPLS and SRv6 networks.

Use this command with the stitch-l3vpn keyword on an ASBR that connects the MPLS L3VPN and EVPN L3VPN over SRv6 networks or connects the EVPN L3VPN and IP L3VPN over SRv6 networks. This command enables conversion between EVPN routes and VPNv4/VPNv6 routes to realize intercommunication between the MPLS and SRv6 networks.

After you execute this command without the stitch-l3vpn keyword on an ASBR, the ASBR performs the following operations:

· After receiving BGP EVPN routes from the EVPN L3VPN network, the ASBR performs the following operations:

a. Matches the route targets of the routes with the import route targets of local VPN instances.

b. Replaces the RD and route targets of the routes with those of the matching local VPN instance. In addition, the ASBR adds an SRv6 SID to the routes and maps the SRv6 SID of the routes to the private label of the routes.

c. Advertises the reoriginated routes to the SRv6 network.

· After receiving BGP EVPN routes from the SRv6 network, the ASBR performs the following operations:

a. Matches the route targets of the routes with the import route targets of local VPN instances.

b. Replaces the RD and route targets of the routes with those of the matching local VPN instance. In addition, the ASBR adds MPLS labels to the routes and maps the private label of the routes to the SRv6 SID of the routes.

c. Advertises the reoriginated routes to the EVPN L3VPN network.

After you execute this command with the stitch-l3vpn keyword on an ASBR, the ASBR performs the following operations after receiving BGP EVPN routes from the SRv6 network or MPLS network:

1. Matches the route targets of the routes with the import route targets of local VPN instances.

2. Reoriginates the matching IP prefix advertisement routes as VPNv4 or VPNv6 routes without modifying the RD or route targets of the routes. In addition, the ASBR adds MPLS labels to the routes and maps the private label of the routes to the SRv6 SID of the routes.

3. Advertises the reoriginated routes to the MPLS L3VPN network.

To allow inter-AS communication in an inter-AS SRv6 VPN network with SRv6 deployed in each AS, inter-AS advertisement of the locator subnet route information is required. For example, you can redistribute the locator subnet routing information from an IGP into BGP for inter-AS route advertisement. After the locator subnet routing information is advertised across the ASs, PE devices in different ASs can establish inter-AS SRv6 forwarding paths. However, in some scenarios, locator subnet routing information should not be advertised across ASs due to security concerns. In this case, you can specify the replace-sid keyword in this command to replace the SRv6 SID carried in a route with an SRv6 SID of the matching local VPN instance. In this way, the locator subnet routing information is not advertised to other ASs and the PEs in different ASs can establish inter-AS SRv6 fowarding paths.

Restrictions and guidelines

This command enables the device to advertise only reoriginated routes to the specified peer or peer group. The original routes are not advertised.

If the RD of a received BGP EVPN route is identical to the RD of the matching local VPN instance, a device does not modify the route or reoriginate the route. As a result, the device does not advertise the route. As a best practice, assign unique RDs to VPN instances on different devices if you use this command.

Examples

# In BGP EVPN address family view, replace the RD and route targets of the EVPN routes received from peer 1.1.1.1 and add an MPLS label or SRv6 SID to the routes.

<Sysname> system-view

[Sysname] bgp 100

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

[Sysname-bgp-default-evpn] peer 1.1.1.1 re-originated replace-rt

Related commands

peer advertise original-route

peer suppress re-originated

peer re-originated (BGP VPNv4/VPNv6 address family view)

Use peer re-originated to enable the device to reoriginate BGP VPNv4 or VPNv6 routes based on the BGP VPNv4 or VPNv6 routes received from a peer or peer group.

Use undo peer re-originated to disable the device from reoriginating BGP VPNv4 or VPNv6 routes based on the BGP VPNv4 or VPNv6 routes received from a peer or peer group.

Syntax

peer { group-name | ipv4-address [ mask-length ] | ipv6-address [ prefix-length ] } re-originated [ replace-rt | stitch-evpn ]

peer { group-name | ipv6-address [ prefix-length ] } re-originated [ replace-rt ] replace-sid

undo peer { group-name | ipv4-address [ mask-length ] | ipv6-address [ prefix-length ] } re-originated

Default

The device does not reoriginate BGP VPNv4 or VPNv6 routes based on received BGP VPNv4 or VPNv6 routes.

Views

BGP VPNv4 address family view

BGP VPNv6 address family view

Predefined user roles

network-admin

mdc-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.

ipv4-address: Specifies a peer by its IPv4 address. The peer must exist.

mask-length: Specifies a mask length in the range of 0 to 32. To specify a subnet, you must specify both the ipv4-address and mask-length arguments.

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.

replace-rt: Replaces the RD and route targets of VPNv4 or VPNv6 routes with those of the matching local VPN instance, and adds MPLS labels or SRv6 SIDs to the routes if the replace-sid keyword is not specified or reallocates SRv6 SIDs to the routes in the matching local VPN instance if the replace-sid keyword is specified. If you do not specify the replace-rt keyword, the device performs the same operations except that it does not replace the route targets.

replace-sid: Deletes the SRv6 SIDs carried in the received BGP VPNv4 or VPNv6 routes and reallocates SRv6 SIDs to the routes in the matching local VPN instance. If you do not specify this keyword, the device does not replace the SRv6 SIDs of routes.

stitch-evpn: Reoriginates VPNv4/VPNv6 routes as EVPN IP prefix advertisement routes without modifying the RD and route targets of the routes.

Usage guidelines

Application scenarios

Use this command without the stitch-evpn keyword on an ASBR that connects the MPLS L3VPN and IP L3VPN over SRv6 networks. This command enables the ASBR to modify VPNv4 or VPNv6 route information to realize intercommunication between the MPLS and SRv6 networks.

Use this command with the stitch-evpn keyword on an ASBR that connects the EVPN L3VPN and IP L3VPN over SRv6 networks or connects the MPLS L3VPN and EVPN L3VPN over SRv6 networks. This command enables conversion between VPNv4/VPNv6 routes and EVPN routes to realize intercommunication between the MPLS and SRv6 networks.

After you execute this command without the stitch-evpn keyword on an ASBR, the ASBR performs the following operations:

· After receiving BGP VPNv4 or VPNv6 routes from the MPLS L3VPN network, the ASBR performs the following operations:

a. Matches the route targets of the routes with the import route targets of local VPN instances.

c. Advertises the reoriginated routes to the SRv6 network.

· After receiving BGP VPNv4 or VPNv6 routes from the SRv6 network, the ASBR performs the following operations:

a. Matches the route targets of the routes with the import route targets of local VPN instances.

c. Advertises the reoriginated routes to the MPLS L3VPN network.

After you execute this command with the stitch-evpn keyword on an ASBR, the ASBR performs the following operations after receiving BGP VPNv4 or VPNv6 routes from the SRv6 network or MPLS network:

1. Matches the route targets of the routes with the import route targets of local VPN instances.

2. Reoriginates the matching BGP VPNv4 or VPNv6 routes as EVPN IP prefix advertisement routes without modifying the RD or route targets of the routes. In addition, the ASBR adds MPLS labels to the routes and maps the private label of the routes to the SRv6 SID of the routes.

3. Advertises the reoriginated routes to the EVPN L3VPN network.

Restrictions and guidelines

This command enables the device to advertise only reoriginated routes to the specified peer or peer group. The original routes are not advertised.

If the RD of a received BGP VPNv4 or VPNv6 route is identical to the RD of the matching local VPN instance, a device does not modify the route or reoriginate the route. As a result, the device does not advertise the route. As a best practice, assign unique RDs to VPN instances on different devices if you use this command.

Examples

# In BGP VPNv4 address family view, replace the RD and route targets of the BGP VPNv4 routes received from peer 1.1.1.1 and add an MPLS label or SRv6 SID to the routes.

<Sysname> system-view

[Sysname] bgp 100

[Sysname-bgp-default] address-family vpnv4

[Sysname-bgp-default-vpnv4] peer 1.1.1.1 re-originated replace-rt

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

In BGP VPNv4 address family view or BGP VPNv6 address family view:

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

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

In BGP EVPN address family view:

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 RFC 9252 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 RFC 9252 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.

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 Transposition Scheme format defined in RFC 9252 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 srv6-sid-transposition

peer suppress re-originated

Use peer suppress re-originated to suppress advertisement of reoriginated BGP EVPN, BGP VPNv6, or BGP VPNv4 routes to a peer or peer group.

Use undo peer suppress re-originated to restore the default.

Syntax

In BGP VPNv4 address family view/BGP VPNv6 address family view:

peer { group-name | ipv4-address [ mask-length ] | ipv6-address [ prefix-length ] } suppress re-originated

undo peer { group-name | ipv4-address [ mask-length ] | ipv6-address [ prefix-length ] } suppress re-originated

In BGP EVPN address family view:

peer { group-name | ipv4-address [ mask-length ] | ipv6-address [ prefix-length ] } suppress re-originated ip-prefix

undo peer { group-name | ipv4-address [ mask-length ] | ipv6-address [ prefix-length ] } suppress re-originated ip-prefix

Default

The device advertises reoriginated BGP EVPN, BGP VPNv6, or BGP VPNv4 routes to peers and peer groups after the peer re-originated command is executed.

Views

BGPN VPNv4 address family view

BGPN VPNv6 address family view

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.

ipv4-address: Specifies a peer by its IPv4 address. The peer must exist.

mask-length: Specifies a mask length in the range of 0 to 32. To specify a subnet, you must specify both the ipv4-address and mask-length arguments.

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.

ip-prefix: Suppresses advertisement of reoriginated IP prefix advertisement routes.

Usage guidelines

The device configured with the peer re-originated and peer advertise original-route commands advertises both original and reoriginated BGP EVPN, BGP VPNv6, or BGP VPNv4 routes. For the device to advertise only original BGP EVPN, BGP VPNv6, or BGP VPNv4 routes to a peer or peer group, execute the peer suppress re-originated command on the device.

Examples

# In BGP VPNv4 address family view, suppress advertisement of reoriginated BGP VPNv4 routes to peer 1.1.1.1.

<Sysname> system-view

[Sysname] bgp 100

[Sysname-bgp-default] address-family vpnv4

[Sysname-bgp-default-vpnv4] peer 1.1.1.1 suppress re-originated

Related commands

peer advertise original-route

peer re-originated

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 VPNv4 address family view or BGP VPNv6 address family view:

segment-routing ipv6 best-effort

undo segment-routing ipv6 best-effort

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

BGP EVPN address family view:

segment-routing ipv6 best-effort evpn

undo segment-routing ipv6 best-effort evpn

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

BGP VPNv4 address family view

BGP VPNv6 address family view

BGP EVPN 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.

· In the inter-AS option B VPN scenario, use this command in BGP VPNv4 address family view, BGP VPNv6 address family view, or BGP EVPN address family view.

This command is mutually exclusive with the segment-routing ipv6 traffic-engineering command.

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 VPNv4 address family view, BGP VPNv6 address family view, 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

In BGP EVPN address family view:

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

undo segment-routing ipv6 locator evpn

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

BGP VPNv4 address family view

BGP VPNv6 address family view

BGP EVPN 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

Related commands

locator

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 VPNv4 address family view or BGP VPNv6 address family view:

segment-routing ipv6 locator locator-name anycast

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

In BGP EVPN address family view:

segment-routing ipv6 locator locator-name anycast evpn

undo segment-routing ipv6 locator anycast evpn

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 VPNv4 address family view

BGP VPNv6 address family view

BGP IPv4 unicast address family view

BGP IPv6 unicast address family view

BGP EVPN 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

11-Segment Routing Command Reference

evpn encapsulation srv6

Application scenarios

Operating mechanism

Restrictions and guidelines

Application scenarios

Restrictions and guidelines

peer re-originated (BGP VPNv4/VPNv6 address family view)

Application scenarios

Restrictions and guidelines

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