- Table of Contents
- Related Documents
-
Title | Size | Download |
---|---|---|
04-SRv6 VPN commands | 447.59 KB |
peer advertise encap-type srv6
peer re-originated (BGP EVPN address family view)
peer re-originated (BGP VPNv4/VPNv6 address family view)
segment-routing ipv6 best-effort
segment-routing ipv6 locator (cross-connect view and VSI EVPN instance view)
segment-routing ipv6 primary-path-detect sid-bfd
segment-routing ipv6 traffic-engineering
SRv6 VPN commands
bfd static evpn-vpws-srv6
Use bfd static evpn-vpws-srv6 to create a static BFD session for SRv6 PW connectivity detection in an EVPN VPWS over SRv6 network and enter static BFD session view, or enter the view of an existing static BFD session.
Use undo bfd static to delete a static BFD session and all settings in static BFD session view.
Syntax
bfd static session-name evpn-vpws-srv6 interface interface-type interface-number remote-peer remote-ipv6-address [ discriminator auto ]
undo bfd static session-name
Default
No static BFD sessions exist.
Views
System view
Predefined user roles
network-admin
Parameters
session-name: Specifies the name of the static BFD session, a case-sensitive string of 1 to 64 characters.
interface interface-type interface-number: Specifies a Layer 3 interface mapped to a cross-connect. The interface-type argument represents the interface type and the interface-number argument represents the interface number.
remote-peer remote-ipv6-address: Specifies a remote PE by its IPv6 address.
discriminator auto: Enables the device to automatically assign a local discriminator value to the static BFD session. If you do not specify the keywords, you must use the discriminator command to specify the local and remote discriminators for the session.
Usage guidelines
Enable BFD on both ends of an SRv6 PW for quick link connectivity detection. The PEs periodically send BFD control packets to each other out of the Layer 3 interfaces mapped to the cross-connect of the SRv6 PW. A PE sets the PW state to Down if it does not receive control packets from the remote end within a detection interval. To avoid packet forwarding failure, the PE switches packets to the backup SRv6 PW or an equal-cost SRv6 PW.
Make sure the static BFD session is in Asynchronous mode.
Use this command on both PEs at the two ends of an SRv6 PW.
In a primary/backup SRv6 PW scenario or an equal-cost SRv6 PW scenario, you must configure a static BFD session for each SRv6 PW to detect their connectivity.
Examples
# Create a static BFD session named abc to test the connectivity of the SRv6 PW associated with a cross-connect mapped to Ten-GigabitEthernet 2/0/0. The IPv6 address of the remote PE is 20::1.
<Sysname> system-view
[Sysname] bfd static abc evpn-vpws-srv6 interface ten-gigabitethernet 2/0/0 remote-peer 20::1
[Sysname-bfd-static-session-abc]
default color
Use default color to specify the default color.
Use undo default color to restore the default.
Syntax
default color color-value
undo default color
Default
No default color is specified.
Views
EVPN instance view
Predefined user roles
network-admin
Parameters
color-value: Specifies the default color, in the range of 0 to 4294967295.
Usage guidelines
In case of color-based traffic steering, the default color is used in the following scenarios:
· A BGP EVPN route does not have the color extended community attribute or match a routing policy to obtain a color.
Examples
# In VSI EVPN instance view, set the default color to 100.
<Sysname> system-view
[Sysname] vsi aaa
[Sysname-vsi-aaa] evpn encapsulation srv6
[Sysname-vsi-aaa-mpls-srv6] default color 100
# In cross-connect group EVPN instance view, set the default color to 100.
<Sysname> system-view
[Sysname] xconnect-group vpna
[Sysname-xcg-vpna] evpn encapsulation srv6
[Sysname-xcg-vpna-evpn-srv6] default color 100
display l2vpn forwarding srv6
Use display l2vpn forwarding srv6 to display L2VPN SRv6 forwarding information.
Syntax
display l2vpn forwarding srv6 [ vsi vsi-name | xconnect-group group-name ] [ verbose ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
vsi vsi-name: Specifies a VSI by its name, a case-sensitive string of 1 to 31 characters.
xconnect-group group-name: Specifies a cross-connect group by its name, a case-sensitive string of 1 to 31 characters. The group name cannot contain hyphens (-).
verbose: Displays detailed L2VPN SRv6 forwarding information. If you do not specify this keyword, the command displays only brief L2VPN SRv6 forwarding information.
Usage guidelines
If you do not specify a VSI or a cross-connect group, this command displays L2VPN SRv6 forwarding information for all VSIs and cross-connect groups.
Examples
# Display brief L2VPN SRv6 forwarding information.
<Sysname> display l2vpn forwarding srv6
Total number of cross-connections: 1
Total number of VSIs: 1
Total number of SRv6 tunnels: 2, 2 up, 0 blocked, 0 down
VSI Name : vpnb
Link ID : 0x9000000 Type: BE State: Up
In SID : 100::2
Out SID : 200::3
Xconnect-group Name : vpna
Connection Name : pw1
Link ID : 0x1 Type: BE State: Up
In SID : 100::1
Out SID : 200::1
Table 1 Command output
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 bakup 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. |
# Display detailed L2VPN SRv6 forwarding information.
<Sysname> display l2vpn forwarding srv6 verbose
VSI Name: vpnb
Link ID : 0x9000000
SRv6 Tunnel Type : Ethernet
SRv6 Tunnel State : Up
In SID : 200::3
Out SID : 100::2
MTU : 1500
SRv6 Tunnel Attributes : Main
SRv6 Forwarding IDs : -
Nexthop/interface : -
Remote Leaf Argument : -
Xconnect-group Name: vpna
Connection Name: pw1
Link ID : 0x1
SRv6 Tunnel Type : Ethernet
SRv6 Tunnel State : Up
In SID : 200::1
Out SID : 100::1
MTU : 1500
SRv6 Tunnel Attributes : Main
SRv6 Forwarding IDs : -
Nexthop/interface : -
Table 2 Command output
Field |
Description |
Link ID |
Link ID of the SRv6 tunnel on the VSI or cross-connect group. |
SRv6 Tunnel Type |
SRv6 PW data encryption type, Ethernet or VLAN. |
SRv6 Tunnel State |
SRv6 tunnel status: · Up—The SRv6 tunnel is up. · Down—The SRv6 tunnel is down. · Blocked—The SRv6 tunnel is a bakup 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 |
SRv6 forwarding entry IDs. If service traffic is not forwarded through SRv6, this field displays a hyphen (-). If SRv6 has been configured to forward service traffic but does not take effect yet, this field displays an asterisk (*). This field displays the equal-cost SRv6 policy forwarding entries that actually take effect, which are calculated by the device based on the information such as network topology and available path status. The number of IDs might be fewer than the configured value. For the specific value that actually takes effect, see the command output. |
Nexthop/interface |
Next hop and outgoing interface of each path included in SRv6 BE when service traffic is forwarded through SRv6 BE tunnels. |
Remote Leaf Argument |
Argument value used by the remote PE to identify leaf ACs. If no argument value exists, this field displays a hyphen (-). |
display l2vpn peer srv6
Use display l2vpn peer srv6 to display L2VPN SRv6 information.
Syntax
display l2vpn peer srv6 [ vsi vsi-name | xconnect-group group-name ] [ state-machine | verbose ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
vsi vsi-name: Specifies a VSI by its name, a case-sensitive string of 1 to 31 characters.
xconnect-group group-name: Specifies a cross-connect group by its name, a case-sensitive string of 1 to 31 characters.
state-machine: Displays L2VPN SRv6 state machine information.
verbose: Displays detailed L2VPN SRv6 information.
Usage guidelines
If you do not specify a VSI or a cross-connect group, this command displays L2VPN SRv6 information for all VSIs and cross-connect groups.
If you do not specify the state-machine or verbose keyword, this command displays brief information about L2VPN SRv6.
Examples
# Display brief information about L2VPN SRv6.
<Sysname> display l2vpn peer srv6
Total number of SRv6 Tunnels: 2
2 up, 0 blocked, 0 down
VSI Name: vpnb
Peer : 2::2
Flag : Main
State : Up
Xconnect-group Name: vpna
Peer : 2::2
Flag : Main
State : Up
Remote SrvID : 2
# Display detailed information about L2VPN SRv6.
<Sysname> display l2vpn peer srv6 verbose
VSI Name: vpnb
Peer: 2::2
Signaling Protocol : EVPN
Link ID : 0x9000000
SRv6 Tunnel State : Up
In SID : 100::2
Out SID : 200::3
Wait to Restore Time : 200
Remaining Time : 100
MTU : 1500
SRv6 Tunnel Attributes : Main
Tunnel Group ID : 0x1000000030000000
Tunnel NHLFEIDs : 2150629380
Nexthop/interface : FE80::64BA:7AFF:FE48:317/ XGE2/0/0
Color : -
Color-Only : -
Slice ID : -
Slice Prefix : -
Slice Encap Mode : -
Remote Leaf Argument : -
Recursion Mode : SID based
Output Statistics :
Octets : 0
Packets : 0
UcastPkt : 0
BrdcastPkt : 0
MuticastPkt : 0
Errors : 0
Discards : 0
Output Rate :
Bytes per second : 0
Packets per second : 0
Xconnect-group Name: vpna
Connection Name: pw1
Peer: 2::2
Remote Service ID : 2
Signaling Protocol : EVPN
Link ID : 0x1
SRv6 Tunnel State : Up
In SID : 100::1
Out SID : 200::1
Wait to Restore Time : 200
Remaining Time : 100
MTU : 1500
SRv6 Tunnel Attributes : Main
Tunnel Group ID : 0x1000000030000000
SRv6 Forwarding IDs : 0
Color : -
Color-Only : -
Slice ID : -
Slice Prefix : -
Slice Encap Mode : -
Recursion Mode : SID based
All Peer Input Statistics :
Octets : 0
Packets : 0
UcastPkt : 0
BrdcastPkt : 0
MuticastPkt : 0
Errors : 0
Discards : 0
Output Statistics :
Octets : 0
Packets : 0
UcastPkt : 0
BrdcastPkt : 0
MuticastPkt : 0
Errors : 0
Discards : 0
All Peer Input Rate :
Bytes per second : 0
Packets per second : 0
Output Rate :
Bytes per second : 0
Packets per second : 0
Table 3 Command output
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. |
Remote SrvID/Remote Service ID |
Remote service ID. |
Signaling Protocol |
Signaling protocol used to establish the SRv6 tunnel. Supported values: · EVPN. · Static SRv6. |
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. |
Wait to Restore Time |
Reversion delay, in seconds. If revertive switching is disabled, this field displays Infinite. This field is supported only when both primary and backup PWs exist and is displayed only for the primary PW. |
Remaining Time |
Reversion delay remainng time, in seconds. This field is displays only if the reversion delay timer is started. |
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 fowarding. |
Nexthop/interface |
Next hop and outgointg interface of the public tunnel that carries the SRv6 tunnel when SRv6 BE route recursion mode is used for traffic fowarding. |
Color |
Color attribute of the expected SRv6 TE policy for route recursion. If no color attribute is available, this field displays a hyphen (-). |
Color-Only |
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. |
Slice ID |
ID of the network slice instance. If no slice ID is mapped to the color, this field displays a hyphen (-). |
Slice Prefix |
Source IPv6 prefix carrying the slice ID. |
Slice Encap Mode |
Network slice type. Values include: · 1—HBH. · 2—Source prefix. A hyphen (-) represents an invalid value. |
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. |
All Peer Input Statistics |
Total SRv6 PW incoming traffic statistics: · Octets—Number of incoming bytes. · Packets—Number of incoming packets. · UcastPkt—Number of incoming unicast packets. · BrdcastPkt—Number of incoming broadcast packets. · MuticastPkt—Number of incoming multicast 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. · UcastPkt—Number of outgoing unicast packets. · BrdcastPkt—Number of outgoing broadcast packets. · MuticastPkt—Number of outgoing multicast packets. · Errors—Number of error packets. · Discards—Number of dropped packets. |
All Peer Input Rate |
Total 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. |
# Display state machine information about L2VPN SRv6.
<Sysname> display l2vpn peer srv6 state-machine
SRv6 tunnel group state:
Idle: Idle N: Normal UA: Unavailable PF: Protecting failure
P: Protection tunnel failure W: Working tunnel failure L: Local
Total number of SRv6 tunnels: 2
VSI Name: vpnb
SRv6 Group Link ID : 0x9000000
Main SRv6 Tunnel:
Peer : 2::2
Backup SRv6 Tunnel : -
Signaling Protocol : EVPN
Main SRv6 Defect State : No defect
Backup SRv6 Defect State : -
Switch Result : Working
Switch Reason : None
Remote Event : -
Local Event : SFCW
SRv6 Group Old State : Idle
SRv6 Group State : UA:P:L
Xconnect-group Name: vpna
Connection Name: pw1
SRv6 Group Link ID : 0x1
Main SRv6 Tunnel:
Peer : 2::2
Service ID : 2
Backup SRv6 Tunnel : -
Signaling Protocol : EVPN
Main SRv6 Defect State : No defect
Backup SRv6 Defect State : -
Switch Result : Working
Switch Reason : None
Remote Event : -
Local Event : SFCW
SRv6 Group Old State : Idle
SRv6 Group State : UA:P:L
Table 4 Command output
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. |
display l2vpn vsi
Use display l2vpn vsi to display L2VPN VSI information.
Syntax
display l2vpn vsi [ evpn-srv6 | name vsi-name ] [ count | verbose ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
evpn-srv6: Specifies VSIs in the EVPN VPLS over SRv6 network.
name vsi-name: Specifies a VSI by its name, a case-sensitive string of 1 to 31 characters.
count: Displays VSI statistics.
verbose: Displays detailed VSI information.
Usage guidelines
If you do not specify a VSI or the evpn-srv6 keyword, this command displays L2VPN VSI information for all VSIs.
If you do not specify the count or verbose keyword, this command displays brief VSI information.
Examples
# Display brief information about all VSIs in the EVPN VPLS over SRv6 network.
<Sysname> display l2vpn vsi evpn-srv6
Total number of VSIs: 1, 1 up, 0 down, 0 admin down
VSI Name VSI Index MTU State
vpnb 0 1500 Up
# Display statistics about all VSIs in the EVPN VPLS over SRv6 network.
<Sysname> display l2vpn vsi evpn-srv6 count
Total number of VSIs: 1, 1 up, 0 down, 0 admin down
Table 5 Command output
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. |
# Display detailed information about all VSIs in the EVPN VPLS over SRv6 network.
<Sysname> display l2vpn vsi evpn-srv6 verbose
VSI Name: vpnb
VSI Index : 0
VSI Description : vsi for vpnb
VSI State : Up
MTU : 1500
Diffserv Mode : -
Bandwidth : -
Broadcast Restrain : 5120 kbps
Multicast Restrain : 5120 kbps
Unknown Unicast Restrain: 5120 kbps
MAC Learning : Enabled
MAC Table Limit : -
MAC Learning rate : Unlimited
Local MAC aging time : 300 sec
Remote MAC aging time : 300 sec
Drop Unknown : Disabled
PW Redundancy Mode : Slave
DSCP : -
Flooding : Enabled
ESI : 0000.0000.0000.0000.0000
Redundancy Mode : All-active
Straight-fwd PW-to-AC : Disabled
Statistics : Disabled
EVPN MPLS BCR : -
EVPN MPLS MCR : -
EVPN MPLS UCR : -
EVPN SRV6 BCR : -
EVPN SRV6 MCR : -
EVPN SRV6 UCR : -
VXLAN ID : -
EVPN Encapsulation : SRv6
SRv6 SIDs:
Dt2U SID : 222::1(64/64/0)
Dt2UL SID : 222::2(64/64/0)
Dt2M SID : 222::3(64/64/0)
SRv6 tunnels:
Peer : 2::2
Link ID : 0x9000000
State : Up
ACs:
AC Link ID State
XGE2/0/0 0x0 Up
Statistics: Disabled
Table 6 Command output
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. |
DSCP |
DSCP of the VXLAN packets sent by the device. |
Flooding |
State of the VSI's flooding feature. This field is not supported by VPLS. |
ESI |
Ethernet segment identifier of the VSI. |
Redundancy Mode |
Redundancy backup mode: · All-active. · Single-active. |
Straight-fwd PW-to-AC |
This field is not supported in the current software version. Whether PW-to-AC straight forwarding has been enabled for the VSI. |
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. |
VXLAN ID |
VXLAN ID. This field is not supported by VPLS. |
EVPN Encapsulation |
EVPN encapsulation type: · VXLAN. · MPLS. · SRv6. |
EVPN MPLS BCR |
Broadcast suppression bandwidth value of EVPN MPLS, in kbps. |
EVPN MPLS MCR |
Multicast suppression bandwidth value of EVPN MPLS, in kbps. |
EVPN MPLS UCR |
Unknown unicast suppression bandwidth value of EVPN MPLS, in kbps. |
EVPN SRv6 BCR |
Broadcast suppression bandwidth value of EVPN SRv6, in kbps. |
EVPN SRv6 MCR |
Multicast suppression bandwidth value of EVPN SRv6, in kbps. |
EVPN SRv6 UCR |
Unknown unicast suppression bandwidth value of EVPN SRv6, in kbps. |
SRv6 SIDs |
SRv6 SIDs of the VSI. |
Dt2U SID |
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. |
Dt2Ul SID |
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. |
Dt2M SID |
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. |
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
XGE2/0/1 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 manullay 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. 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 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 : 0x1
Sub Link ID : 0x1
State : Up
ACs:
AC Link ID State
XGE2/0/0 0x0 Up
Statistics: Disabled
Xconnect-group Name: vpnb
Connection Name : pw2
Connection ID : 1
State : Up
MTU : 1500
PW Redundancy Mode : Slave
Diffserv Mode : -
Static SRv6 tunnels:
Peer : 11::9
Link ID : 0x0
Sub Link ID : 0x1
State : Up
ACs:
AC Link ID State
XGE2/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. |
Static SRv6 tunnels |
Information about static SRv6 PWs. |
Peer |
IPv6 address of the SRv6 PW remote PE. |
Link ID |
Link ID of the SRv6 PW on the cross-connect. |
Sub Link ID |
Sublink ID of the SRv6 PW on the cross-connect. The sublink ID of an SRv6 PW identifies the SRv6 PW among all SRv6 PWs with the same link ID. |
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. |
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. |
encapsulation source-address
Use encapsulation source-address to specify a source address for the outer IPv6 header of SRv6 VPN packets.
Use undo encapsulation source-address to restore the default.
Syntax
encapsulation source-address ipv6-address
undo encapsulation source-address
Default
No source address is specified for the outer IPv6 header of SRv6 VPN packets.
Views
SRv6 view
Predefined user roles
network-admin
Parameters
ipv6-address: Specifies a source IPv6 address. The IPv6 address cannot be a loopback address (0:0:0:0:0:0:0:0 or ::), link-local address, multicast address, or unspecified address.
Usage guidelines
To ensure correct VPN traffic forwarding in an SRv6 VPN network, you must specify a source address for the outer IPv6 header of SRv6 VPN packets.
You must specify an IPv6 address of the local device as the source IPv6 address, and make sure the IPv6 address has been advertised by a routing protocol. As a best practice, specify a loopback interface address of the local device as the source IPv6 address.
Examples
# Specify 1::1 as the source address of SRv6 VPN packets in the outer IPv6 header.
<Sysname> system-view
[Sysname] segment-routing ipv6
[Sysname-segment-routing-ipv6] encapsulation source-address 1::1
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
VSI view
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.
This command is mutually exclusive with the evpn encapsulation binding instance command. You cannot use them together on the same VSI.
Examples
# Create an EVPN instance and specify it to use SRv6 encapsulation on VSI aaa and enter its view.
<Sysname> system-view
[Sysname] vsi aaa
[Sysname-vsi-aaa] evpn encapsulation srv6
[Sysname-vsi-aaa-evpn-srv6]
export route-policy
Use export route-policy to apply an export routing policy to an EVPN instance.
Use undo export route-policy to restore the default.
Syntax
export route-policy route-policy
undo export route-policy
Default
No export routing policy is applied to an EVPN instance.
Views
EVPN instance view
Predefined user roles
network-admin
Parameters
route-policy: Specifies a routing policy by its name, a case-sensitive string of 1 to 63 characters.
Usage guidelines
You can specify an export routing policy to filter advertised routes or modify their route attributes for EVPN.
If you execute this command multiple times, the most recent configuration takes effect.
Examples
# Apply export routing policy poly-1 to the EVPN instance on VSI vpna.
<Sysname> system-view
[Sysname] vsi vpna
[Sysname-vsi-vpna] evpn encapsulation srv6
[Sysname-vsi-vpna-evpn-srv6] route-distinguisher 1:1
[Sysname-vsi-vpna-evpn-srv6] export route-policy poly-1
Related commands
route-policy (Layer 3—IP Routing Command Reference)
import route-policy
Use import route-policy to apply an import routing policy to an EVPN instance.
Use undo import route-policy to restore the default.
Syntax
import route-policy route-policy
undo import route-policy
Default
No import routing policy is applied to an EVPN instance. The EVPN instance accepts a route when the route targets of the route match local import route targets.
Views
EVPN instance view
Predefined user roles
network-admin
Parameters
route-policy: Specifies a routing policy by its name, a case-sensitive string of 1 to 63 characters.
Usage guidelines
You can specify an import routing policy to filter received routes or modify their route attributes for EVPN.
If you execute this command multiple times, the most recent configuration takes effect.
Examples
# Apply import routing policy poly-1 to the EVPN instance on VSI vpna.
<Sysname> system-view
[Sysname] vsi vpna
[Sysname-vsi-vpna] evpn encapsulation srv6
[Sysname-vsi-vpna-evpn-srv6] route-distinguisher 1:1
[Sysname-vsi-vpna-evpn-srv6] import route-policy poly-1
Related commands
route-policy (Layer 3—IP Routing Command Reference)
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 which are the recursive nexthops of routes.
Usage guidelines
Application scenarios
In the IP L3VPN over SRv6 BE or EVPN L3VPN 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 locator advertised by the peer PE (the SRv6 locator is the recursive nexthop address of 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 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)
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
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.
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 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 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
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.
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.
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
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.
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.
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.
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
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
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.
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 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.
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 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.
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.
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
Related commands
peer advertise original-route
peer suppress re-originated
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
BGP VPNv4 address family view/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
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 or EVPN L3VPN over SRv6 network, the BGP VPNv4, VPNv6, or EVPN 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
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.
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
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
ping evpn vpls srv6 vsi vsi-name mac mac-address [ force-match-slice ] [ -a source-ipv6 | -c count | -h hop-limit | -m interval | -r reply-mode | -s packet-size | { -service-class class-value | -te-class te-class-value } | -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.
force-match-slice: Enables force matching of network slice instance IDs. If source address slicing is used, you must specify this keyword. In addition, to have this keyword take effect, you must specify the strict-mode keyword when you execute the network-slice command to specify the NSI ID for an SRv6 TE policy candidate path. When this parameter is specified, if an MPLS echo request is forwarded by the SRv6 PW, the device adds a slice ID for the packet. The request can be sent successfully only if the slice ID in the request is the same as the network slice instance ID of the network slice channel on the packet output interface. If the IDs are inconsistent, the device discards the MPLS echo request, causing the ping to fail. If this parameter is not specified, the device does not check the slice ID in MPLS echo requests before sending the requests. For MPLS echo requests without a slice ID, this parameter does not take effect.
-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 replies using UDP. If the mode is 4, the receiver replies through the control channel of the application plane, where the reply packets are encapsulated with an SRH.
-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.
-service-class class-value: Specifies the service class value for MPLS echo requests. The value range for the class-value argument varies by device model. The default service class value is 255.
-te-class te-class-value: Specifies the TE class value for MPLS echo requests. The value range for the te-class-value argument is 1 to 65535, and the default value is 0.
-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% packet 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% packet 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
color network-slice
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
ping evpn vpws srv6 xconnect-group group-name local-service-id remote-service-id [ force-match-slice ] [ -a source-ipv6 | -c count | -h hop-limit | -m interval | -r reply-mode | -s packet-size | { -service-class class-value | -te-class te-class-value } | -t time-out | -tc tc ] *
Views
Any view
Predefined user roles
network-admin
Parameters
evpn: Specifies a dynamic SRv6 PW.
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.
force-match-slice: Enables force matching of network slice instance IDs. If source address slicing is used, you must specify this keyword. In addition, to have this keyword take effect, you must specify the strict-mode keyword when you execute the network-slice command to specify the NSI ID for an SRv6 TE policy candidate path. When this parameter is specified, if an MPLS echo request is forwarded by the SRv6 PW, the device adds a slice ID for the packet. The request can be sent successfully only if the slice ID in the request is the same as the network slice instance ID of the network slice channel on the packet output interface. If the IDs are inconsistent, the device discards the MPLS echo request, causing the ping to fail. If this parameter is not specified, the device does not check the slice IDs in MPLS echo requests before sending the requests. For MPLS echo requests without a slice ID, this parameter does not take effect.
-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. The value range for the interval argument is 1 to 10000 milliseconds and the default value is 2000 milliseconds.
-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 replies using UDP. If the mode is 4, the receiver replies through the control channel of the application plane, where the reply packets are encapsulated with an SRH.
-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.
-service-class class-value: Specifies the service class value for MPLS echo requests. The value range for the class-value argument varies by device model. The default service class value is 255.
-te-class te-class-value: Specifies the TE class value for MPLS echo requests. The value range for the te-class-value argument is 1 to 65535, and the default value is 0.
-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 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.0% packet 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% packet 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
revertive wtr
Use revertive wtr to configure the reversion delay (wait-to-restore time).
Use undo revertive to restore the default.
Syntax
revertive wtr wtr-time
undo revertive wtr
Default
The reversion delay time to 0, which means reversion delay is disabled.
Views
VSI EVPN instance view
Cross-connect view
Predefined user roles
network-admin
Parameters
wtr wtr-time: Specifies the reversion delay time (wait-to-restore time), in the range of 0 to 3600, in seconds.
Usage guidelines
In an EVPN VPLS over SRv6 multi-homing network, after the primary PE recovers from an access link failure or node failure, it generates AD Per EVI routes and advertise the routes to the remote PE through the BGP EVPN neighborhood. After receiving the AD Per EVI routes and generating forwarding entries, the remote PE switches traffic from the backup PE path to the primary PE path . At this time, the primary PE might experience some packet loss due to incomplete generation of forwarding entries. To avoid this situation, you can configure an appropriate reversion delay on the remote PE by using this command. After receiving an EVI AD route, the remote PE will delay generating the forwarding entry, waiting for the forwarding entries on the primary PE to stabilize. When the reversion delay times out, the remote PE generates a new forwarding entry, and then traffic will be switched to the primary PE.
In an EVPN VPWS over SRv6 multi-homing network, when the primary PW or primary PE recovers from a failure, service traffic will switch back to the primary PW for forwarding. At this time, however, packet loss might occur on the primary PE due to incomplete generation of forwarding entries. To prevent this situation, you can configure an appropriate reversion delay on the remote PE by using this command. The delay enables the remote PE to wait for the forwarding entries to stabilize on the primary PE before switching traffic back to the primary PE.
When you use this command in cross-connect view, you must also execute the route-select delay command.
Examples
# Set the reversion delay to 120 seconds.
<Sysname> system-view
[Sysname] vsi xxx
[Sysname-vsi-xxx] evpn encapsulation srv6
[Sysname-vsi-xxx-evpn-srv6] revertive wtr 120
segment-routing ipv6
Use segment-routing ipv6 to specify a route recursion mode.
Use undo segment-routing ipv6 to restore the default.
Syntax
In cross-connect group EVPN instance view or VSI EVPN instance view:
segment-routing ipv6 { best-effort | traffic-engineering [ track-bfd ] | traffic-engineering [ track-bfd ] best-effort [ local-preference ] }
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
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.
local-preference: For multilevel FRR formed by multiple SRv6 TE and SRv6 BE paths, this keyword makes the FRR primary path consist of one primary SRv6 TE path and one primary SRv6 BE path, and the FRR backup path consist of one backup SRv6 TE path and one backup SRv6 BE path. The device selects the traffic forwarding path in primary SRv6 TE path, primary SRv6 BE path, backup SRv6 TE path, and backup SRv6 BE path order. This keyword is applicable only to dual-homing scenarios.
track-bfd: Associates the SRv6 TE policy that contains paths between two PEs with the static BFD session specified for testing the IP connectivity between the PEs in SRv6 TE mode. For this purpose, you must specify this keyword and create a static BFD session to test the IP connectivity between the two PEs. If the static BFD session goes down, the state of the SRv6 TE policy also changes to down. This mechanism avoids traffic forwarding failure caused by path disconnectivity.
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.DX2, End.DT2M, or End.DT2U SID, it forwards the packet according to the route recursion mode.
· SRv6 BE mode—This mode is also called SID-based forwarding 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 packet.
· SRv6 TE mode—This mode is also called next hop-based forwarding 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 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.
· 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.
For multilevel FRR formed by multiple SRv6 TE and SRv6 BE paths in a dual-homing scenario, the local-preference keyword makes the FRR primary path consist of one primary SRv6 TE path and one primary SRv6 BE path, and the FRR backup path consist of one backup SRv6 TE path and one backup SRv6 BE path. The device selects the traffic forwarding path in primary SRv6 TE path, primary SRv6 BE path, backup SRv6 TE path, and backup SRv6 BE path order. If you do not specify the local-preference keyword, the device selects the traffic forwarding path in primary SRv6 TE path, backup SRv6 TE path, primary SRv6 BE path, and backup SRv6 BE path order.
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-mpls] segment-routing ipv6 best-effort
Related commands
bfd static (High Availability Command Reference)
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
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
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 MPLS L3VPN over SRv6 and EVPN L3VPN over SRv6 networks. This command enables a PE to forward packets by looking up the IPv6 routing table based on the SRv6 SIDs in the packets.
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 IPv4 unicast address family view or BGP IPv6 unicast address family view:
segment-routing ipv6 locator locator-name [ auto-sid-disable | auto-sid-dt46 ]
undo segment-routing ipv6 locator
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 | auto-sid-dt46 ]
undo segment-routing ipv6 locator [ evpn ]
In BGP VPNv4 address family view or BGP VPNv6 address family view:
segment-routing ipv6 locator locator-name
undo segment-routing ipv6 locator
In BGP EVPN address family view:
segment-routing ipv6 locator locator-name evpn
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 VPNv4 address family view
BGP VPNv6 address family view
BGP EVPN 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.
auto-sid-dt46: Specifies the type of dynamically allocated SRv6 SIDs as End.DT46. If you do not specify this keyword, the device dynamically allocates End.DT4 or End.DT6 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.
In L3VPN over SRv6 scenarios, PEs can dynamically allocate SRv6 SIDs for private network routes or public IPv4/IPv6 routes of the VPN instances within the referenced locator. By default, the device dynamically allocates End.DT4 SIDs for public or private IPv4 routes and End.DT6 SIDs for public or private IPv6 routes. When both IPv4 and IPv6 routes coexist in the public network or a specific VPN instance, you can specify the auto-sid-dt46 keyword to allocate only one End.DT46 SID for both IPv4 and IPv6 routes.
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 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
Default
No SRv6 locators are applied to a cross-connect or a VSI.
Views
Cross-connect 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 locate 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 locate 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 locate 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 locate 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.
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 primary-path-detect sid-bfd
Use segment-routing ipv6 primary-path-detect sid-bfd to enable using the static BFD session for the SRv6 SID to detect the reachability of the primary path for SRv6 VPN FRR.
Use undo segment-routing ipv6 primary-path-detect sid-bfd to restore the default.
Syntax
In BGP-VPN IPv4 unicast address family view or BGP-VPN IPv6 unicast address family view:
segment-routing ipv6 primary-path-detect sid-bfd [ evpn ]
undo segment-routing ipv6 primary-path-detect sid-bfd [ evpn ]
In BGP IPv4 unicast address family view or BGP IPv6 unicast address family view:
segment-routing ipv6 primary-path-detect sid-bfd
undo segment-routing ipv6 primary-path-detect sid-bfd
Default
The device uses the static BFD session for the locator to detect the reachability of the primary path for SRv6 VPN FRR.
Views
BGP IPv4 unicast address family view
BGP IPv6 unicast address family view
BGP-VPN IPv4 unicast address family view
BGP-VPN IPv6 unicast address family view
Predefined user roles
network-admin
Parameters
evpn: Applies the configuration only to BGP EVPN FRR. If you do not specify this keyword, the command applies to BGP VPNv4 or BGP VPNv6 FRR.
Usage guidelines
Application scenarios
In IP L3VPN over SRv6 or EVPN L3VPN over SRv6 networks that use the SRv6 BE route recursion mode, the public instance or VPN instance IP routing table does not have SRv6 SID route information by default. As a result, to use BFD to detect the primary path between PEs, FRR can only use the static BFD session for the locator network address.
If the address families of multiple VPN instances or those of the public instance have used the same locator, FRR in these address families might use the same static BFD session to detect the primary path. Once the BFD session detects that the path is not available, the BGP routes in all these address families will perform path switching simultaneously.
For refined FRR management, this command is provided to enable BFD for the primary path of SRv6 VPN FRR by using the static BFD session for the SRv6 SID.
Operating mechanism
After this command is executed, when the device adds a BGP IPv4/IPv6 unicast route, BGP VPNv4/VPNv6 route, or IP prefix route that contains an SRv6 SID to a VPN instance/public instance IP routing table, it adds the SRv6 SID as the next hop of the route. This allows FRR to automatically and preferentially associate the static BFD session for the SRv6 SID to detect the primary path. Once BFD detects that an SRv6 SID is not reachable, it triggers the BGP routes in only one address family or one VPN instance to perform path switching. This mechanism provides a smaller control granularity for FRR.
For example, the device has created two static BFD sessions, one for a locator and the other for an SRv6 SID.
· Before this command is executed, only BFD session frr1 can be used to detect the primary path's reachability for FRR.
<Sysname> display bfd session verbose
Total sessions: 2 Up sessions: 2 Init mode: Active
IPv6 session working in control packet mode:
Session name: frr
Local discr: 33793 Remote discr: 33793
Source IP: 1:2::106
Destination IP: 6:5::106
Destination port: 4784 Session state: Up
Interface: N/A
Min Tx interval: 500ms Actual Tx interval: 500ms
Min Rx interval: 500ms Detection time: 2500ms
Rx count: 30533 Tx count: 25954
Connection type: Indirect Up duration: 03:09:06
Hold time: 2257ms Auth mode: None
Detection mode: Async Slot: 0
Protocol: STATIC_IPv6
Version: 1
Diag info: No Diagnostic
Hardware mode: Disable
Session name: frr1
Local discr: 33794 Remote discr: 33794
Source IP: 1:2::
Destination IP: 6:5::
Destination port: 4784 Session state: Up
Interface: N/A
Min Tx interval: 500ms Actual Tx interval: 500ms
Min Rx interval: 500ms Detection time: 2500ms
Rx count: 30412 Tx count: 25948
Connection type: Indirect Up duration: 03:09:06
Hold time: 2332ms Auth mode: None
Detection mode: Async Slot: 0
Protocol: IPFRR/STATIC_IPv6
Version: 1
Diag info: No Diagnostic
Hardware mode: Disable
· After this command is executed, BFD session frr is used to detect the reachability of the primary path with SRv6 SID 6:5::106.
<Sysname> display bfd session verbose
Total sessions: 2 Up sessions: 2 Init mode: Active
IPv6 session working in control packet mode:
Session name: frr
Local discr: 33793 Remote discr: 33793
Source IP: 1:2::106
Destination IP: 6:5::106
Destination port: 4784 Session state: Up
Interface: N/A
Min Tx interval: 500ms Actual Tx interval: 500ms
Min Rx interval: 500ms Detection time: 2500ms
Rx count: 30533 Tx count: 25954
Connection type: Indirect Up duration: 03:09:06
Hold time: 2257ms Auth mode: None
Detection mode: Async Slot: 0
Protocol: IPFRR/STATIC_IPv6
Version: 1
Diag info: No Diagnostic
Hardware mode: Disable
Session name: frr1
Local discr: 33794 Remote discr: 33794
Source IP: 1:2::
Destination IP: 6:5::
Destination port: 4784 Session state: Up
Interface: N/A
Min Tx interval: 500ms Actual Tx interval: 500ms
Min Rx interval: 500ms Detection time: 2500ms
Rx count: 30412 Tx count: 25948
Connection type: Indirect Up duration: 03:09:06
Hold time: 2332ms Auth mode: None
Detection mode: Async Slot: 0
Protocol: STATIC_IPv6
Version: 1
Diag info: No Diagnostic
Hardware mode: Disable
Restrictions and guidelines
This command applies only to routes that use the SRv6 BE route recursion mode. If the route recursion mode is SRv6 TE and SRv6 BE hybrid, SRv6 TE/SRv6 BE FRR, or SRv6 TE and SRv6 BE multilevel FRR, this command takes effect only when the SRv6 TE path is not available.
Examples
# In BGP IPv4 unicast address family, enable using the BFD session for the SRv6 SID to detect the reachability of the primary path for SRv6 VPN FRR.
<Sysname> system-view
[Sysname] bgp 100
[Sysname-bgp-default] address-family ipv4 unicast
[Sysname-bgp-default-ipv4] segment-routing ipv6 primary-path-detect sid-bfd
Related commands
bfd static (High Availability Command Reference)
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
segment-routing ipv6 traffic-engineering [ best-effort [ local-preference ] ] [ evpn ]
undo segment-routing ipv6 traffic-engineering [ best-effort [ local-preference ] ] [ 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
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.
· For BGP IPv4 unicast routes, BGP IPv6 unicast routes, BGP-VPN IPv4 unicast routes, and BGP-VPN IPv6 unicast routes, if the BGP route can recurse to both an SRv6 TE policy (SRv6 TE path) and SRv6 BE tunnel (SRv6 BE path), then the SRv6 TE path and SRv6 BE path form an FRR relationship. Service traffic prefers to pass through the SRv6 TE path. When the SRv6 TE path encounters a fault or if it doesn't exist, you can quickly switch the service traffic to the SRv6 BE backup path for forwarding. This allows for quick protection and prevents long-term traffic loss.
When a BGP route can recurse to multiple SRv6 TE paths and multiple SRv6 BE paths, the SRv6 TE paths and SRv6 BE paths form multi-level FRR. The device calculates an FRR primary path and FRR backup path. The FRR primary path consists of one primary SRv6 TE path and one backup SRv6 TE path. The FRR backup path consists of one primary SRv6 BE path and one backup SRv6 BE path. The device selects the traffic forwarding path in primary SRv6 TE path, backup SRv6 TE path, primary SRv6 BE path, and backup SRv6 BE path order.
· When there is a fault in the SRv6 TE policy for a BGP VPNv4, BGP VPNv6, or BGP EVPN route, the BGP route recurses to another available SRv6 TE policy or SRv6 BE tunnel.
local-preference: For multilevel FRR formed by multiple SRv6 TE and SRv6 BE paths, this keyword makes the FRR primary path consist of one primary SRv6 TE path and one primary SRv6 BE path, and the FRR backup path consist of one backup SRv6 TE path and one backup SRv6 BE path. The device selects the traffic forwarding path in primary SRv6 TE path, primary SRv6 BE path, backup SRv6 TE path, and backup SRv6 BE path order.
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
Application scenarios
This command is applicable to the IP L3VPN over SRv6 and EVPN L3VPN over SRv6 scenarios. This command enables PEs to recurse routes to SRv6 TE policy tunnels and use the tunnels to forward traffic between the PEs.
Operating mechanism
To improve high availability for packet forwarding, specify the best-effort keyword in this command.
If the best-effort keyword is specified in this command, the device forwards a service packet as follows:
1. The device forwards the packet through the matching SRv6 TE policy tunnel.
2. If the matching SRv6 TE policy tunnel fails, the PE forwards the packet through another path.
¡ For service packets forwarded as instructed by a BGP IPv4 unicast route, BGP IPv6 unicast route, BGP-VPN IPv4 unicast route, or BGP-VPN IPv6 unicast route:
- In a single-homing scenario, the SRv6 BE tunnel (SRv6 BE path) acts as an FRR backup path for the SRv6 TE policy tunnel (SRv6 TE path). Service packets are switched to the SRv6 BE backup path for forwarding.
- In a dual-homing scenario, multiple SRv6 TE paths and multiple SRv6 BE paths form multi-level FRR. If the local-preference keyword is not specified, the device selects a forwarding path for the service packets in the following order: primary SRv6 TE path -> backup SRv6 TE path -> primary SRv6 BE path -> backup SRv6 BE path. If the local-preference keyword is specified, the device selects a forwarding path for the service packets in the following order: primary SRv6 TE path -> primary SRv6 BE path -> backup SRv6 TE path -> backup SRv6 BE path.
¡ For service packets forwarded as instructed by a BGP VPNv4 route, BGP VPNv6 route, or BGP EVPN route: The BGP route recurses to another available SRv6 TE policy or SRv6 BE tunnel.
3. If both the SRv6 TE policy tunnel and the SRv6 BE tunnel fail, the device forwards the packet by looking up the routing table based on the destination IP address of the packet.
4. If the routing table lookup fails, the device discards the packet.
If the best-effort keyword is not specified, when the matching SRv6 TE policy tunnel fails, the device forwards user service packets by looking up the routing table according to the destination IP address of the packets.
Restrictions and guidelines
This command is mutually exclusive with the segment-routing ipv6 best-effort command.
To implement multilevel FRR in dual-homing scenarios, if you do not specify the local-preference keyword in this command, you must also configure the bestroute nexthop-type tunnel command.
To implement multilevel FRR in dual-homing scenarios, if you specify the local-preference keyword in this command, you cannot configure the bestroute nexthop-type function.
In single-homing scenarios, the local-preference keyword does not take effect.
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-mpls-interworking enable
Use srv6-mpls-interworking enable to enable SRv6 and MPLS interworking.
Use undo srv6-mpls-interworking enable to disable SRv6 and MPLS interworking.
Syntax
srv6-mpls-interworking enable
undo srv6-mpls-interworking enable
Default
SRv6 and MPLS interworking is disabled.
Views
BGP VPNv4 address family view
BGP VPNv6 address family view
BGP EVPN address family view
Predefined user roles
network-admin
Usage guidelines
For intercommunication between an MPLS network in one AS and an SRv6 network in another AS, enable SRv6 and MPLS interworking on the ASBR in the SRv6 network. This feature enables End.T SID allocation and establishes mappings between End.T SIDs and MPLS labels.
With this feature, the ASBR in the SRv6 network allocates End.T SIDs based on FECs and advertises the SIDs to other SRv6 nodes through an IGP. An FEC is a destination IPv4 address/mask or destination IPv6 address/prefix length. The function of an End.T SID is removing the outer IPv6 header and looking up the IPv6 FIB table based on the End.T SID to forward packets.
For SRv6-to MPLS packets, the ingress node in the SRv6 network encapsulates an End.T SID to the packets when forwarding the packets to the ASBR in the SRv6 network. When the ASBR in the SRv6 network receives the packets, it looks up the IPv6 FIB table based on the End.T SID for a matching route. Then, the ASBR recurses the route to an LSP to forward the packets to the MPLS network.
For MPLS-to-SRv6 packets, the ASBR in the SRv6 network looks up the label forwarding table to forward the packets. The out label is an End.DT4, End.DT6, End.DT46, End.DX4, or End.DX6 SID in the SRv6 network. After the ASBR in the SRv6 network encapsulates the End.DT4, End.DT6, End.DT46, End.DX4, or End.DX6 SID to the packets, it forwards the packets in SRv6 BE or SRv6 TE mode.
Examples
# Enable SRv6 and MPLS interworking.
<Sysname> system-view
[Sysname] bgp 100
[Sysname-bgp-default] address-family vpnv4
[Sysname-bgp-default-vpnv4] srv6-mpls-interworking enable
srv6-pw-type
Use srv6-pw-type to specify the SRv6 PW data encryption type.
Use undo srv6-pw-type to restore the default.
Syntax
srv6-pw-type { ethernet | vlan }
undo srv6-pw-type
Default
The SRv6 PW data encryption type is VLAN.
Views
PW class view
Predefined user roles
network-admin
Parameters
ethernet: Specifies the SRv6 PW data encryption type as Ethernet.
vlan: Specifies the SRv6 PW data encryption type as VLAN.
Usage guidelines
With Ethernet specified as the SRv6 PW data encryption type, the frames transmitted on the SRv6 PW cannot carry P-Tags (service delimiters added to distinguish users as required by ISPs).
· If the PE receives a packet carrying a P-Tag from the CE, it removes the P-Tag, adds an SRv6 SID, and then forwards the packet.
· If the PE receives a packet without a P-Tag from the CE, it directly adds an SRv6 SID, and then forwards the packet.
· For a packet to be sent to the CE, if the access mode is specified as VLAN with the ac interface command, the PE adds the P-Tag and then forwards the packet to the CE. If the access mode is specified as Ethernet, the PE forwards the packet to the CE without adding a P-Tag. In addition, it does not rewrite or remove any tags.
With VLAN specified as the SRv6 PW data encryption type, the frames transmitted on the SRv6 PW must carry P-Tags.
· If the PE receives a packet carrying a P-Tag from the CE, it retains the P-Tag, adds an SRv6 SID, and then forwards the packet.
· If the PE receives a packet without a P-Tag from the CE, it adds an empty P-Tag with value 1, adds an SRv6 SID, and then forwards the packet.
· For a packet to be sent to the CE, if the access mode is specified as VLAN with the ac interface command, the PE rewrites or retains the P-Tag and then forwards the packet to the CE. If the access mode is specified as Ethernet, the PE removes the P-Tag and then forwards the packet to the CE.
Examples
# Specify the SRv6 PW data encryption type as Ethernet.
<Sysname> system-view
[Sysname] pw-class pw100
[Sysname-pw-pw100] 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 [ force-match-slice ] [ -a source-ipv6 | -h hop-limit | -r reply-mode | { -service-class class-value | -te-class te-class-value } | -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.
force-match-slice: Enables force matching of network slice instance IDs. If source address slicing is used, you must specify this keyword. In addition, to have this keyword take effect, you must specify the strict-mode keyword when you execute the network-slice command to specify the NSI ID for an SRv6 TE policy candidate path. When this parameter is specified, if an MPLS echo request is forwarded by the SRv6 PW, the device adds a slice ID for the packet. The request can be sent successfully only if the slice ID in the request is the same as the network slice instance ID of the network slice channel on the packet output interface. If the IDs are inconsistent, the device discards the MPLS echo request, causing the tracert to fail. If this parameter is not specified, the device does not check the slice IDs in MPLS echo requests before sending the requests. For MPLS echo requests without a slice ID, this parameter does not take effect.
-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.
-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 replies using UDP. If the mode is 4, the receiver replies through the control channel of the application plane, where the reply packets are encapsulated with an SRH.
-service-class class-value: Specifies the service class value for MPLS echo requests. The value range for the class-value argument varies by device model. The default service class value is 255.
-te-class te-class-value: Specifies the TE class value for MPLS echo requests. The value range for the te-class-value argument is 1 to 65535, and the default value is 0.
-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 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 [ force-match-slice ] [ -a source-ip | -h hop-limit | -r reply-mode | { -service-class class-value | -te-class te-class-value } | -t time-out | -tc tc ] *
Views
Any view
Predefined user roles
network-admin
Parameters
evpn: Specifies a dynamic SRv6 PW.
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.
force-match-slice: Enables force matching of network slice instance IDs. If source address slicing is used, you must specify this keyword. In addition, to have this keyword take effect, you must specify the strict-mode keyword when you execute the network-slice command to specify the NSI ID for an SRv6 TE policy candidate path. When this parameter is specified, if an MPLS echo request is forwarded by the SRv6 PW, the device adds a slice ID for the packet. The request can be sent successfully only if the slice ID in the request is the same as the network slice instance ID of the network slice channel on the packet output interface. If the IDs are inconsistent, the device discards the MPLS echo request, causing the tracert to fail. If this parameter is not specified, the device does not check the slice IDs in MPLS echo requests before sending the requests. For MPLS echo requests without a slice ID, this parameter does not take effect.
-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 replies using UDP. If the mode is 4, the receiver replies through the control channel of the application plane, where the reply packets are encapsulated with an SRH.
-service-class class-value: Specifies the service class value for MPLS echo requests. The value range for the class-value argument varies by device model. The default service class value is 255.
-te-class te-class-value: Specifies the TE class value for MPLS echo requests. The value range for the te-class-value argument is 1 to 65535, and the default value is 0.
-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 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 | static } vpws srv6