The opcode end-dt6 command configures a static SRv6 End.DT6 SID opcode.
The undo opcode end-dt6 command deletes a static SRv6 End.DT6 SID opcode.
By default, no static SRv6 End.DT6 SID opcode is configured.
| Parameter | Description | Value |
|---|---|---|
| func-opcode |
Specifies a static SRv6 End.DT6 SID opcode. |
The value is a 32-digit hexadecimal number, in the format of X:X:X:X:X:X:X:X. |
| vpn-instance vpn-instance-name |
Displays information about local SRv6 SID tables based on a specified VPN instance name. If this parameter is not configured, it means that the End.DT6 SID is configured for the public network instance. |
The value is a string of 1 to 31 case-sensitive characters, spaces not supported. When double quotation marks are used around the string, spaces are allowed in the string. |
| evpn |
Indicates the EVPN protocol. |
- |
| evpn-l3vpn |
Indicates the EVPN and L3VPN protocols. |
- |
Usage Scenario
An SRv6 SID is a 128-bit IPv6 address expressed in the Locator:Function:Args format. The Function field is also called Opcode, and different operation codes define different functions. Operation codes can be dynamically assigned using a BGP or be configured using the opcode command.
Static operation codes must be configured within the static operation code segment to prevent conflicts with dynamically assigned operation codes. The length of a static operation code segment is configured through the static static-length parameter in the locator command to determine the number of static operation codes that can be configured in a specified locator range. After you run the opcode command to configure various types of operation codes, the Locator, Opcode, and Args fields form a unique SRv6 SID. The SRv6 SID is then added to the local SID table on the device and also advertised externally through a routing protocol. In forwarding, the Locator field in the SRv6 SID instructs other nodes to find the SRv6 SID generation node through addressing and forward SRv6 packets to the node; the Opcode field instructs the SRv6 SID generation node to implement corresponding functions. End.DT6 (short for decapsulation and specific IPv6 table lookup) supports packet decapsulation and lookup in a specified IPv6 routing table for packet forwarding. End.DT6 SIDs are mainly used in L3VPNv6 scenarios as per-VPN SIDs. End.DT6 can be disassembled into End + D + T6, where D indicates decapsulation and T6 indicates IPv6 table lookup for forwarding. Therefore, each End.DT6 SID needs to be bound to an IPv6 routing table, which can be either the IPv6 routing table of a VPN instance or a common IPv6 routing table. The End.DT6 SID instruction includes the following operations:Precautions
To ensure proper forwarding, the configured static SIDs cannot conflict with the IPv6 addresses configured on interfaces.
<HUAWEI> system-view [~HUAWEI] segment-routing ipv6 [*HUAWEI-segment-routing-ipv6] locator test1 ipv6-prefix 2001:DB8:100:: 64 static 32 [*HUAWEI-segment-routing-ipv6-locator] opcode ::300 end-dt6
<HUAWEI> system-view [~HUAWEI] ip vpn-instance vpn1 [*HUAWEI-vpn-instance-vpn1] quit [*HUAWEI] segment-routing ipv6 [*HUAWEI-segment-routing-ipv6] locator test1 ipv6-prefix 2001:DB8:100:: 64 static 32 [*HUAWEI-segment-routing-ipv6-locator] opcode ::303 end-dt6 vpn-instance vpn1 evpn