Hardware	SRv6 TE policy compatibility
MSR610	No
MSR810, MSR810-W, MSR810-W-DB, MSR810-LM, MSR810-W-LM, MSR810-10-PoE, MSR810-LM-HK, MSR810-W-LM-HK, MSR810-LM-CNDE-SJK, MSR810-CNDE-SJK, MSR810-EI, MSR810-LM-EA, MSR810-LM-EI	Yes
MSR810-LMS, MSR810-LUS	No
MSR810-SI, MSR810-LM-SI	No
MSR810-LMS-EA, MSR810-LME	Yes
MSR1004S-5G, MSR1004S-5G-CN	Yes
MSR1104S-W, MSR1104S-W-CAT6, MSR1104S-5G-CN, MSR1104S-W-5G-CN	Yes
MSR2600-6-X1, MSR2600-15-X1, MSR2600-15-X1-T	Yes
MSR2600-10-X1	Yes
MSR 2630	Yes
MSR3600-28, MSR3600-51	Yes
MSR3600-28-SI, MSR3600-51-SI	No
MSR3600-28-X1, MSR3600-28-X1-DP, MSR3600-51-X1, MSR3600-51-X1-DP	Yes
MSR3600-28-G-DP, MSR3600-51-G-DP	Yes
MSR3610-I-DP, MSR3610-IE-DP, MSR3610-IE-ES, MSR3610-IE-EAD, MSR-EAD-AK770, MSR3610-I-IG, MSR3610-IE-IG	Yes
MSR3610-X1, MSR3610-X1-DP, MSR3610-X1-DC, MSR3610-X1-DP-DC, MSR3620-X1, MSR3640-X1	Yes
MSR3610, MSR3620, MSR3620-DP, MSR3640, MSR3660	Yes
MSR3610-G, MSR3620-G	Yes
MSR3640-G	Yes
MSR3640-X1-HI	Yes

Hardware	SRv6 TE policy compatibility
MSR810-W-WiNet, MSR810-LM-WiNet	Yes
MSR830-4LM-WiNet	Yes
MSR830-5BEI-WiNet, MSR830-6EI-WiNet, MSR830-10BEI-WiNet	Yes
MSR830-6BHI-WiNet, MSR830-10BHI-WiNet	Yes
MSR2600-6-WiNet	Yes
MSR2600-10-X1-WiNet	Yes
MSR2630-WiNet	Yes
MSR3600-28-WiNet	Yes
MSR3610-X1-WiNet	Yes
MSR3610-WiNet, MSR3620-10-WiNet, MSR3620-DP-WiNet, MSR3620-WiNet, MSR3660-WiNet	Yes

Hardware	SRv6 TE policy compatibility
MSR860-6EI-XS	Yes
MSR860-6HI-XS	Yes
MSR2630-XS	Yes
MSR3600-28-XS	Yes
MSR3610-XS	Yes
MSR3620-XS	Yes
MSR3610-I-XS	Yes
MSR3610-IE-XS	Yes
MSR3620-X1-XS	Yes
MSR3640-XS	Yes
MSR3660-XS	Yes

Hardware	SRv6 TE policy compatibility
MSR810-LM-GL	Yes
MSR810-W-LM-GL	Yes
MSR830-6EI-GL	Yes
MSR830-10EI-GL	Yes
MSR830-6HI-GL	Yes
MSR830-10HI-GL	Yes
MSR1004S-5G-GL	Yes
MSR2600-6-X1-GL	Yes
MSR3600-28-SI-GL	No

address-family ipv6 sr-policy

Use address-family ipv6 sr-policy to create the BGP IPv6 SR policy address family and enter its view, or enter the view of the existing BGP IPv6 SR policy address family.

Use undo address-family ipv6 sr-policy to delete the BGP IPv6 SR policy address family and all the configuration in the BGP IPv6 SR policy address family.

Syntax

address-family ipv6 sr-policy

undo address-family ipv6 sr-policy

Default

The BGP IPv6 SR policy address family does not exist.

Views

BGP instance view

Predefined user roles

network-admin

Usage guidelines

The configuration in BGP IPv6 SR policy address family view applies only to routes and peers in the BGP IPv6 SR policy address family.

Examples

# In BGP instance view, create the BGP IPv6 SR policy address family and enter its view.

<Sysname> system-view

[Sysname] bgp 100

[Sysname-bgp-default] address-family ipv6 sr-policy

[Sysname-bgp-default-srpolicy-ipv6]

advertise ebgp enable

Use advertise ebgp enable to enable advertising BGP IPv6 SR policy routes to EBGP peers.

Use undo advertise ebgp enable to restore the default.

Syntax

advertise ebgp enable

undo advertise ebgp enable

Default

BGP IPv6 SR policy routes are not advertised to EBGP peers.

Views

BGP IPv6 SR policy address family

Predefined user roles

network-admin

Usage guidelines

By default, BGP IPv6 SR policy routes are advertised among IBGP peers. To advertise BGP IPv6 SR policy routes to EBGP peers, you must execute this command to enable the advertisement capability.

Examples

# Enable advertising BGP IPv6 SR policy routes to EBGP peers.

<Sysname> system-view

[Sysname] bgp 100

[Sysname-bgp-default] address ipv6 sr-policy

[Sysname-bgp-default-srpolicy-ipv6] advertise ebgp enable

autoroute enable

Use autoroute enable to enable automatic route advertisement for an SRv6 TE policy.

Use undo autoroute enable to disable automatic route advertisement for an SRv6 TE policy.

Syntax

autoroute enable [ isis | ospfv3 ]

undo autoroute enable

Default

Automatic route advertisement is disabled for an SRv6 TE policy.

Views

SRv6 TE policy view

Predefined user roles

network-admin

Parameters

isis: Enables automatic route advertisement for IPv6 IS-IS.

ospfv3: Enables automatic route advertisement for OSPFv3.

Usage guidelines

The automatic route advertisement feature advertises an SRv6 TE policy to IGP (IPv6 IS-IS or OSPFv3) for route computation.

An SRv6 TE policy supports only automatic route advertisement in IGP shortcut mode, which is also called autoroute announce. Autoroute announce regards the SRv6 TE policy tunnel as a link that connects the tunnel ingress and egress. The tunnel ingress includes the SRv6 TE policy tunnel in IGP route computation.

If you do not specify the isis or ospfv3 keyword, both OSPFv3 and IPv6 IS-IS will include the SRv6 TE policy tunnel in route computation.

Examples

# Enable automatic route advertisement for an SRv6 TE policy.

<Sysname> system-view

[Sysname] segment-routing ipv6

[Sysname-segment-routing-ipv6] traffic-engineering

[Sysname-srv6-te] policy srv6policy

[Sysname-srv6-te-policy-srv6policy] autoroute enable

Related commands

autoroute metric

Use autoroute metric to configure an autoroute metric for an SRv6 TE policy.

Use undo autoroute metric to restore the default.

Syntax

autoroute metric { absolute value | relative value }

undo autoroute metric

Default

The autoroute metric of an SRv6 TE policy equals its IGP metric.

Views

SRv6 TE policy view

Predefined user roles

network-admin

Parameters

absolute value: Specifies an absolute metric, an integer in the range of 1 to 65535.

relative value: Specifies a relative metric, an integer in the range of –10 to +10. The specified relative metric plus the IGP metric is the actual metric of the SRv6 TE policy.

Usage guidelines

After automatic route advertisement is enabled for an SRv6 TE policy, the policy is included in IGP route computation as a link. You can use this command to configure the metric of this link used for IGP route computation.

Examples

# Set an absolute metric of 15 for SRv6 TE policy srv6policy.

<Sysname> system-view

[Sysname] segment-routing ipv6

[Sysname-segment-routing-ipv6] traffic-engineering

[Sysname-srv6-te] policy srv6policy

[Sysname-srv6-te-policy-srv6policy] autoroute metric absolute 15

Related commands

autoroute enable

backup hot-standby

Use backup hot-standby to configure hot standby for an SRv6 TE policy.

Use undo backup hot-standby to restore the default.

Syntax

backup hot-standby { disable | enable }

undo backup hot-standby

Default

Hot standby is not configured for an SRv6 TE policy.

Views

SRv6 TE policy view

Predefined user roles

network-admin

Parameters

disable: Disables hot standby for the SRv6 TE policy.

enable: Enables hot standby for the SRv6 TE policy.

Usage guidelines

The hot standby feature takes the candidate path with the greatest preference value in the SRv6 TE policy as the primary path and that with the second greatest preference value as the standby path. When the forwarding paths corresponding to all SID lists of the primary path fails, the standby path immediately takes over to minimize service interruption.

You can enable hot standby for all SRv6 TE policies globally in SRv6 TE view or for a specific SRv6 TE policy in SRv6 TE policy view. The policy-specific configuration takes precedence over the global configuration. An SRv6 TE policy uses the global configuration only when it has no policy-specific configuration.

Examples

# Enable hot standby for SRv6 TE policy 1.

<Sysname> system-view

[Sysname] segment-routing ipv6

[Sysname-segment-routing-ipv6] traffic-engineering

[Sysname-srv6-te] policy 1

[Sysname-srv6-te-policy-1] backup hot-standby enable

Related commands

srv6-policy backup hot-standby enable

bestroute encap-type

Use bestroute encap-type to specify the packet encapsulation type preferred in optimal route selection.

Use undo bestroute encap-type to restore the default.

Syntax

bestroute encap-type { mpls | srv6 }

undo bestroute encap-type

Default

The device does not select optimal routes according to the packet encapsulation type.

Views

BGP-VPN instance view.

Predefined user roles

network-admin

Parameters

mpls: Prefers to use MPLS-encapsulated routes during optimal route selection.

srv6: Prefers to use SRv6-encapsulated routes during optimal route selection.

Usage guidelines

After this command is executed, BGP selects the optimal route in the VPN instance by using the following procedure:

1. Selects the route according to the NEXT_HOP, Preferred-value, and LOCAL_PREF attributes in turn.

2. Selects the route according to the encapsulation type specified by the bestroute encap-type command.

3. Proceeds the subsequent steps in the original BGP route select procedure.

For more information about BGP route selection, see BGP overview in Layer 3—IP Routing Configuration Guide.

If you execute this command multiple times, the most recent configuration takes effect.

Examples

# Configure BGP to prefer SRv6-encapsulated routes during optimal route selection.

<Sysname> system-view

[Sysname] bgp 100

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

[Sysname-bgp-default-vpn1] bestroute encap-type srv6

bfd echo

Use bfd echo to configure the echo packet mode BFD for an SRv6 TE policy.

Use undo bfd echo to restore the default.

Syntax

bfd echo { disable | enable [ source-ipv6 ipv6-address ] [ template template-name ] [ backup-template backup-template-name ] [ oam-sid sid ] }

undo bfd echo

Default

The echo packet mode BFD is not configured for an SRv6 TE policy. An SRv6 TE policy uses the echo BFD settings configured in SRv6 TE view.

Views

SRv6 TE policy view

Predefined user roles

network-admin

Parameters

disable: Disables the echo packet mode BFD for the SRv6 TE policy.

enable: Enables the echo packet mode BFD for the SRv6 TE policy.

source-ipv6 ipv6-address: Specifies the source IPv6 address of the BFD session. If you do not specify this option, the configuration in SRv6-TE view applies.

template template-name: Specifies a BFD session parameter template by its name, a case-sensitive string of 1 to 63 characters. If you do not specify this option, the template specified in SRv6 TE view applies.

backup-template backup-template-name e: Specifies a BFD session parameter template for the backup SID list. The backup-template-name argument indicates the template name, a case-sensitive string of 1 to 63 characters. If you do not specify this option, the backup template specified in SRv6 TE view applies.

oam-sid sid: Adds an OAM SID to BFD packets to identify the destination node. The sid argument represents the SRv6 SID of the destination node. If you do not specify this option, no OAM SID will be added to BFD packets. As a best practice, set the OAM SID to the End SID of the destination node.

Usage guidelines

You can configure the echo packet mode BFD for all SRv6 TE policies globally in SRv6 TE view or for a specific SRv6 TE policy in SRv6 TE policy view. The policy-specific configuration takes precedence over the global configuration. An SRv6 TE policy uses the global configuration only when it has no policy-specific configuration.

The device supports the echo packet mode BFD and the SBFD for an SRv6 TE policy. If both modes are configured for the same SRv6 TE policy, the SBFD takes effect.

Examples

# Enable the echo packet mode BFD for SRv6 TE policy 1, and specify the source IPv6 address of the BFD session as 11::11.

<Sysname> system-view

[Sysname] segment-routing ipv6

[Sysname-segment-routing-ipv6] traffic-engineering

[Sysname-srv6-te] policy 1

[Sysname-srv6-te-policy-1] bfd echo enable source-ipv6 11::11

Related commands

display segment-routing ipv6 te bfd

srv6-policy bfd echo

binding-sid

Use binding-sid to configure a BSID for an SRv6 TE policy.

Use undo binding-sid to delete the BSID.

Syntax

binding-sid ipv6 ipv6-address

undo binding-sid

Default

No BSID is configured for an SRv6 TE policy.

Views

SRv6 TE policy view

Predefined user roles

network-admin

Parameters

ipv6 ipv6-address: Specifies the BSID value, which is an IPv6 address.

Usage guidelines

You can use this command to manually configure a BSID for an SRv6 TE policy or leave the SRv6 TE policy to obtain a BSID automatically. If an SRv6 TE policy has only color and endpoint configuration, the SRv6 TE policy will automatically request a BSID.

The manually configured BSID has a higher priority over the automatically obtained BSID.

The BSID configured by this command must be on the locator specified for SRv6 TE policies in SRv6 TE view. Otherwise, the SRv6 TE policy cannot forward packets.

If you execute this command multiple times, the most recent configuration takes effect.

Examples

# Set the BSID of SRv6 TE policy srv6policy to 1000::1.

<Sysname> system-view

[Sysname] segment-routing ipv6

[Sysname-segment-routing-ipv6] traffic engineering

[Sysname-srv6-te] policy srv6policy

[Sysname-srv6-te-policy-srv6policy] binding-sid ipv6 1000::1

candidate-paths

Use candidate-paths to create and enter the candidate path view for an SRv6 TE policy, or enter the existing SRv6 TE policy candidate path view.

Use undo candidate-paths to delete the SRv6 TE policy candidate path view and all the configurations in the view.

Syntax

candidate-paths

undo candidate-paths

Default

The candidate path view for an SRv6 TE policy does not exist.

Views

SRv6 TE policy view

Predefined user roles

network-admin

Examples

# Create the SRv6 TE policy candidate paths instance and enter its view.

<Sysname> system-view

[Sysname] segment-routing ipv6

[Sysname-segment-routing-ipv6] traffic-engineering

[Sysname-srv6-te] policy srv6policy

[Sysname-srv6-te-policy-srv6policy] candidate-paths

[Sysname-srv6-te-policy-srv6policy-path]

color end-point

Use color end-point to configure the color and endpoint attributes of an SRv6 TE policy.

Use undo color to delete the color and endpoint settings of an SRv6 TE policy.

Syntax

color color-value end-point ipv6 ipv6-address

undo color

Default

The color and endpoint attributes of an SRv6 TE policy are not configured.

Views

SRv6 TE policy view

Predefined user roles

network-admin

Parameters

color-value: Specifies the color attribute value, in the range of 0 to 4294967295.

Ipv6-address: Specifies the endpoint IPv6 address.

Usage guidelines

If you execute this command multiple times, the most recent configuration takes effect.

Different SRv6 TE policies cannot have the same color or endpoint IP address.

Examples

# Configure the color as 20 and endpoint IPv6 address as 1000::1 for SRv6 TE policy srv6policy.

<Sysname> system-view

[Sysname] segment-routing ipv6

[Sysname-segment-routing-ipv6] traffic-engineering

[Sysname-srv6-te] policy srv6policy

[Sysname-srv6-te-policy-srv6policy] color 20 end-point ipv6 1000::1

color match dscp

Use color match dscp to create color-to-DSCP mappings for an SRv6 TE policy group.

Use undo color match dscp to delete color-to-DSCP mappings for the SRv6 TE policy group.

Syntax

color color-value match dscp { ipv4 | ipv6 } dscp-value-list

undo color color-value match dscp { ipv4 | ipv6 } dscp-value-list

color color-value match dscp { ipv4 | ipv6 } default

undo color color-value match dscp { ipv4 | ipv6 } [ default ]

Default

No color-to-DSCP mappings are created for an SRv6 TE policy group.

Views

SRv6 TE policy group view

Predefined user roles

network-admin

Parameters

color-value: Specifies the color attribute value of an SRv6 TE policy, in the range of 0 to 4294967295.

ipv4: Specifies DSCP values of IPv4 packets.

ipv6: Specifies DSCP values of IPv6 packets.

dscp-value-list: Specifies a space-separated list of up to 32 DSCP value items. Each item specifies a DSCP value in the range of 0 to 63 or a range of DSCP values in the form of dscp-value1 to dscp-value2. The value for the dscp-value2 argument must be greater than or equal to the value for the dscp-value1 argument.

default: Configures a default color-to-DSCP mapping. Packets that do not match any mappings are steered to the default SRv6 TE policy (the policy specified in the default mapping).

Usage guidelines

You can map the color values of only valid SRv6 TE policies to DSCP values.

You can configure color-to-DSCP mappings separately for the IPv4 address family and IPv6 address family. For a specific address family, a DSCP value can be mapped to only one color value.

Use the color match dscp default command to specify the default SRv6 TE policy for an address family. If no SRv6 TE policy in an SRv6 TE policy group matches a specific DSCP value, the default SRv6 TE policy is used to forward packets containing the DSCP value. Only one default SRv6 TE policy can be specified for an address family.

When the device receives an IPv4 or IPv6 packet that does not match any color-to-DSCP mapping, the device selects a valid SRv6 TE policy for the packet in the following order:

1. The default SRv6 TE policy specified for the same address family as the packet.

2. The default SRv6 TE policy specified for the other address family.

3. The SRv6 TE policy mapped to the smallest DSCP value in the same address family as the packet.

4. The SRv6 TE policy mapped to the smallest DSCP value in the other address family.

Examples

# In SRv6 TE policy group 10, map DSCP value 30 to color value 20 for IPv4 packets, so that IPv4 packets with a matching DSCP value are steered to the associated SRv6 TE policy.

<Sysname> system-view

[Sysname] segment-routing ipv6

[Sysname-segment-routing-ipv6] traffic-engineering

[Sysname-srv6-te] policy-group 10

[Sysname-srv6-te-policy-group-10] color 20 match dscp ipv4 30

default-color (public instance IPv4/IPv6 address family view)

Use default-color to configure a default color value for public route recursion to an SRv6 TE policy.

Use undo default-color to restore the default.

Syntax

default-color color-value

undo default-color

Default

No default color value is configured.

Views

Public instance IPv4 address family view

Public instance IPv6 address family view

Predefined user roles

network-admin

Parameters

color-value: Default color value in the range of 0 to 4294967295.

Usage guidelines

The local PE uses the default color value to match an SRv6 TE policy for a received public network route if the route does not carry a color extended community and no color is added to the route through a routing policy.

This command applies only to the public network routes learned from a remote PE.

The default color value configured by this command is used only for SRv6 TE policy traffic steering. It does not used in route advertisement.

If you execute this command multiple times, the most recent configuration takes effect.

Examples

# In public instance IPv4 address family view, set the default color to 100 for public network route recursion to an SRv6 TE policy.

<Sysname> system-view

[Sysname] ip public-instance

[Sysname-public-instance] address-family ipv4

[Sysname-public-instance-ipv4] default-color 100

default-color (VPN instance IPv4/IPv6 address family view)

Use default-color to configure a default color value for L3VPN route recursion to an SRv6 TE policy.

Use undo default-color to restore the default.

Syntax

default-color color-value [ evpn ]

undo default-color [ evpn ]

Default

No default color value is configured.

Views

VPN instance IPv4 address family view

VPN instance IPv6 address family view

Predefined user roles

network-admin

Parameters

color-value: Default color value in the range of 0 to 4294967295.

evpn: Specifies the EVPN L3VPN service. If you do not specify this keyword, the default color applies to MPLS L3VPN route recursion to an SRv6 TE policy.

Usage guidelines

The local PE uses the default color value to match an SRv6 TE policy for a received VPNv4, VPNv6, or EVPN IP prefix route if the route does not carry a color extended community and no color is added to the route through a routing policy.

This command applies only to the VPN routes learned from a remote PE.

The default color value configured by this command is used only for SRv6 TE policy traffic steering. It does not used in route advertisement.

If you execute this command multiple times, the most recent configuration takes effect.

Examples

# In IPv4 address family view for VPN instance vpn1, set the default color to 100 for EVPN L3VPN route recursion to an SRv6 TE policy.

<Sysname> system-view

[Sysname] ip vpn-instance vpn1

[Sysname-vpn-instance-vpn1] address-family ipv4

[Sysname-vpn-ipv4-vpn1] default-color 100 evpn

display bgp mirror remote-sid

Use display bgp mirror remote-sid to display remote SRv6 SIDs protected by mirror SIDs.

Syntax

display bgp [ instance instance-name ] mirror remote-sid [ end-dt4 | end-dt46 | end-dt6 ] [ sid ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

instance instance-name: Specifies a BGP instance by its name, a case-sensitive string of 1 to 31 characters. If you do not specify a BGP instance, this command displays information about the default instance.

end-dt4: Specifies remote SRv6 SIDs of the End.DT4 type.

end-dt46: Specifies remote SRv6 SIDs of the End.DT46 type.

end-dt6: Specifies remote SRv6 SIDs of the End.DT6 type.

sid: Specifies a remote SRv6 SID.

Usage guidelines

This command can display information about remote SRv6 SIDs protected by mirror SIDs on MPLS L3VPN over SRv6 or EVPN L3VPN over SRv6 networks.

If you do not specify any parameters, this command displays all remote SRv6 SIDs protected by mirror SIDs.

Examples

# Display remote SRv6 SIDs protected by mirror SIDs on L3VPN over SRv6 networks.

<Sysname> display bgp mirror remote-sid

Remote SID: 3001::1:0:0

Remote SID type: End.DT4

Mirror locator: 3001::1/64

VPN instance name: vrf1

Remote SID: 3001::1:0:1

Remote SID type: End.DT6

Mirror locator: 3001::1/64

VPN instance name: vrf2

Remote SID: 1111:2222:3333:4444::1

Remote SID type: End.DT6

Mirror locator: 1111:2222:3333:4444:5555:6666:7777:8888/64

VPN instance name: vrf1

Table 1 Command output

Field	Description
Remote SID	Remote SRv6 SID.
Remote SID type	Type of the remote SRv6 SID: · End.DT4. · End.DT6. · End.DT46.
Mirror locator	IPv6 prefix and prefix length of the locator for the remote SRv6 SID.
VPN instance name	Name of the VPN instance associated with the remote SRv6 SID.
Remaining retention time	Remaining time before the mapping of the remote SRv6 SID and the VPN instance is deleted.

‌

display bgp routing-table ipv6 sr-policy

Use display bgp routing-table ipv6 sr-policy to display route information of a BGP IPv6 SR policy.

Syntax

display bgp [ instance instance-name ] routing-table ipv6 sr-policy [ sr-policy-prefix [ advertise-info ]

display bgp [ instance instance-name ] routing-table ipv6 sr-policy [ peer ipv6-address { advertised-routes | received-routes } ] [ sr-policy-prefix [ advertise-info ]

display bgp [ instance instance-name ] routing-table ipv6 sr-policy [ peer ipv6-address { advertised-routes | received-routes } ] [ statistics | color color-value | end-point ipv6 ipv6-address ] *

display bgp [ instance instance-name ] routing-table ipv6 sr-policy color color-value end-point ipv6 ipv6-address

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

sr-policy-prefix: Specifies a BGP IPv6 SR policy route prefix, which is a case-insensitive string of 1 to 512 characters in the format of BGP IPv6 SR policy route/prefix length.

color color-value: Specifies the color attribute value of a BGP IPv6 SR policy, in the range of 1 to 4294967295.

end-point ipv6 ipv6-address: Specifies the endpoint IPv6 address of a BGP IPv6 SR policy.

advertise-info: Displays advertisement information about BGP IPv6 SR policy routes.

peer ipv6-address: Specifies a peer by its IPv6 address.

advertised-routes: Displays detailed information about the BGP IPv6 SR policy routes advertised to the specified peer.

received-routes: Displays detailed information about the BGP IPv6 SR policy routes received from the specified peer.

statistics: Displays route statistics.

Usage guidelines

If you do not specify any parameters, this command displays brief information about all BGP IPv6 SR policy routes.

Examples

# Display brief information about all BGP IPv6 SR policy routes.

<Sysname> display bgp routing-table ipv6 sr-policy

Total number of routes: 1

BGP local router ID is 2.2.2.2

Status codes: * - valid, > - best, d - dampened, h - history

s - suppressed, S - stale, i - internal, e - external

a – additional-path

Origin: i - IGP, e - EGP, ? - incomplete

>i Network : [46][46][8::8]/192

NextHop : 1::2 LocPrf : 100

PrefVal : 0 MED : 0

Path/Ogn: i

Table 2 Command output

Field	Description
Status codes	Status codes of the route.
Origin	Origin of the route: · i – IGP—Originated in the AS. · e – EGP—Learned through an EGP. · ? – incomplete—Unknown origin.
Network	BGP IPv6 SR policy route, comprised of the following elements: · SRv6 TE policy candidate path preference. · SRv6 TE policy color attribute value. · Endpoint IPv6 address.
NextHop	Next hop IP address.
LocPrf	Local preference value.
PrefVal	Preferred value of the route.
MED	Multi-Exit Discriminator attribute value.
Path/Ogn	AS_PATH and ORIGIN attributes of the route: · AS_PATH—Records the ASs the route has passed. · ORIGIN—Identifies the origin of the route.

‌

# Display detailed information about BGP IPv6 SR policy route [46][46][8::8]/192.

<Sysname> display bgp routing-table ipv6 sr-policy [46][46][8::8]/192

BGP local router ID: 5.5.5.1

Local AS number: 100

Paths: 1 available, 1 best

BGP routing table information of [46][46][8::8]/192

Imported route.

Original nexthop: ::

Output interface: p1

Route age : 19h45m02s

OutLabel : NULL

RxPathID : 0x0

TxPathID : 0x0

AS-path : (null)

Origin : igp

Attribute value : MED 0, localpref 100, pref-val 32768

State : valid, local, best

IP precedence : N/A

QoS local ID : N/A

Traffic index : N/A

Tunnel encapsulation info:

Type: 15 (SR policy)

Policy name: p1

Binding SID: 2::6

Preference: 100

Path: 1

Weight: 1

SIDs: {2::2}

Table 3 Command output

Field	Description
Paths	Route information: · available—Number of valid routes. · best—Number of optimal routes.
BGP routing table information of [46][46][8::8]/192	Information of the BGP IPv6 SR policy route [46][46][8::8]/192, where: · [46] is the SRv6 TE policy candidate path preference · [46] is the SRv6 TE policy color attribute value. · [8::8] is the endpoint IPv6 address.
From	IP address of the BGP peer that advertised the route.
Rely Nexthop	Recursive nexthop IP address. If no next hop is found by route recursion, this field displays not resolved.
Original nexthop	Original nexthop IP address. If the route was obtained from a BGP update message, the original next hop is the nexthop IP address in the message.
Route age	Time elapsed since the last update for the route.
OutLabel	Outgoing label of the route.
RxPathID	Received Add-Path ID of the route.
TxPathID	Advertised Add-Path ID of the route.
AS-path	AS_PATH attribute of the route.
Origin	Origin of the route: · igp—Originated in the AS. · egp—Learned through an EGP. · incomplete—Unknown origin.
Attribute value	BGP path attributes: · MED—MED value. · localpref—Local preference value. · pref-val—Preferred value. · pre—Protocol preference.
State	Current state of the route. Options include: · valid—Valid route. · internal—Internal route. · external—External route. · local—Locally generated route. · synchronize—Synchronized route. · best—Optimal route. · delay—Delayed route. The route will be delayed for optimal route selection. This value is available only in detailed information of the route. · not preferred for reason—Reason why the route is not selected as the optimal route. For more information, see Table 4.
IP precedence	IP precedence of the route, in the range of 0 to 7. N/A indicates that the route does not support this field.
QoS local ID	QoS local ID of the route, in the range of 1 to 4095. N/A indicates that the route does not support this field.
Traffic index	Traffic index in the range of 1 to 64. N/A indicates that the route does not support this field.
Type: 15 (SR Policy)	The tunnel encryption type is 15, which represents SR policy.
Preference	Candidate path preference.
Binding SID	BSID value.
Path	Candidate path.
Weight	Weight of the SID list.
SIDs	List of SIDs. A G-SID is displayed in the format of {sid-value, coc32, prefix-length}, where sid-value is the SID value and prefix-length is the common prefix length.

‌

Table 4 Reason why the route is not selected as the optimal route

Reason	Description
preferred-value	Routes with larger preferred values exist.
local-preference	Routes with larger local preference values exist.
as-path	Routes with smaller AS_PATH attribute values exist.
origin	There are routes whose origin has a higher priority. The route origins are IGP, EGP, and INCOMPLETE in descending order of priority.
med	Routes with smaller MED values exist.
remote-route	There are routes whose remote-route attribute has a higher priority. BGP selects the optimal route from remote routes in this order: · Route learned from an EBGP peer. · Route learned from a confederation EBGP peer. · Route learned from a confederation IBGP peer. · Route learned from an IBGP peer.
igp-cost	Routes with smaller IGP metrics exist.
relydepth	Routes with smaller recursion depth values exist.
rfc5004	A route received from an EBGP peer is the current optimal route. BGP does not change the optimal route when it receives routes from other EBGP peers.
router-id	Routes with smaller router IDs exist. If one of the routes is advertised by a route reflector, BGP compares the ORIGINATOR_ID of the route with the router IDs of other routes. Then, BGP selects the route with the smallest ID as the optimal route.
cluster-list	Routes with smaller CLUSTER_LIST attribute values exist.
peer-address	Routes advertised by peers with lower IP addresses exist.
received	Earlier learned routes exist.

‌

# Displays advertisement information about the BGP IPv6 SR policy route [46][46][8::8]/192.

<Sysname> display bgp routing-table ipv6 sr-policy [46][46][8::8]/192 advertise-info

BGP local router ID: 2.2.2.2

Local AS number: 1

Paths: 1 best

BGP routing table information of [46][46][8::8]/192(TxPathID:0):

Advertised to peers (2 in total):

1::1

3::3

Table 5 Command output

Field	Description
Paths	Number of optimal paths to reach the destination network.
BGP routing table information of [46][46][8::8]/192(TxPathID:0)	Advertisement information about the BGP IPv6 SR policy route [46][46][8::8]/192. TxPathID represents the advertised Add-Path ID of the route.
Advertised to peers (2 in total)	Indicates the peers to which the route has been advertised. The number in the parentheses indicates the total number of the peers.

‌

# Display statistics about the BGP IPv6 SR policy routes advertised to peer 2::2.

<Sysname> display bgp routing-table ipv6 sr-policy peer 2::2 advertised-routes statistics

Advertised routes total: 2

# Display statistics about the BGP IPv6 SR policy routes received from peer 2::2.

<Sysname> display bgp routing-table ipv6 sr-policy peer 2::2 received-routes statistics

Received routes total: 1

Table 6 Command output

Field	Description
Advertised routes total	Total number of routes advertised to the specified peer.
Received routes total	Total number of routes received from the specified peer.

‌

# Display statistics about BGP IPv6 SR policy routes.

<Sysname> display bgp routing-table ipv6 sr-policy statistics

Total number of routes: 3

display segment-routing ipv6 te bfd

Use display segment-routing ipv6 te bfd to display BFD information for SRv6 TE policies.

Syntax

display segment-routing ipv6 te bfd [ down | policy { { color color-value | end-point ipv6 ipv6-address } * | name policy-name } | up ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

down: Displays BFD information for SRv6 TE policies in down state.

policy: Displays BFD information for the specified SRv6 TE policy.

color color-value: Specifies the color attribute value of an SRv6 TE policy, in the range of 0 to 4294967295.

end-point ipv6 ipv6-address: Specifies the IPv6 address of the endpoint of an SRv6 TE policy.

name policy-name: Specifies the name of an SRv6 TE policy, a case-sensitive string of 1 to 59 characters.

up: Displays BFD information for SRv6 TE policies in up state.

Usage guidelines

If you do not specify any parameters, this command displays BFD information for all SRv6 TE policies.

Examples

# Display BFD information for all SRv6 TE policies.

<Sysname> display segment-routing ipv6 te policy bfd

Color: 10

Endpoint: 4::4

Policy name: p1

State: Up

Nid: 2149580801

BFD type: ECHO

Source IPv6: 1::1

State: Up

Timer: 37

VPN index: 1

Template name: abc

Table 7 Command output

Field	Description
Color	Color attribute value of an SRv6 TE policy.
Endpoint	Endpoint IP address of the SRv6 TE policy.
Policy name	Name of the SRv6 TE policy.
State	SBFD session state: · Up · Down · Delete
Nid	Forwarding entry index for an SID list.
BFD type	The current software version supports only the BFD echo mode.
Source IPv6	Source IPv6 address of the BFD session.
Timer	BFD session timer, in seconds.
VPN index	Index of the VPN instance.
Template name	Name of the echo mode BFD template.

‌

display segment-routing ipv6 te forwarding

Use display segment-routing ipv6 te forwarding to display SRv6 TE forwarding information.

Syntax

display segment-routing ipv6 te forwarding [ policy { name policy-name | { color color-value | end-point ipv6 ipv6-address } * } ] [ verbose ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

policy: Displays forwarding information of the specified SRv6 TE policy. If you do not specify an SRv6 TE policy, this command displays forwarding information of all SRv6 TE policies.

name policy-name: Specifies the name of an SRv6 TE policy, a case-sensitive string of 1 to 59 characters.

color color-value: Specifies the color of an SRv6 TE policy, in the range of 0 to 4294967295.

end-point ipv6 ip-address: Specifies the endpoint IPv6 address of an SRv6 TE policy.

verbose: Displays detailed SRv6 TE forwarding information. If you do not specify this keyword, the command displays brief SRv6 TE forwarding information.

Examples

# Display brief information about all SRv6 TE policies.

<Sysname> display segment-routing ipv6 te forwarding

Total forwarding entries: 1

Policy name/ID: p1/0

Binding SID: 8000::1

Forwarding index: 2150629377

Main path:

Seglist ID: 1

Seglist forwarding index: 2149580801

Weight: 1

Outgoing forwarding index: 2148532225

Interface: GE1/0/1

Nexthop: FE80::6CCE:CBFF:FE91:206

Backup path:

Seglist ID: 2

Seglist forwarding index: 2149580802

Weight: 1

Outgoing forwarding index: 2148532226

Interface: GE1/0/2

Nexthop: FE80::6CCE:CBFF:FE91:207

# Display detailed information about all SRv6 TE policies.

<Sysname> display segment-routing ipv6 te forwarding verbose

Total forwarding entries: 1

Policy name/ID: p1/0

Binding SID: 8000::1

Forwarding index: 2150629377

Inbound statistics:

Total octets: 525

Total packets: 1

Erroneous packets: 0

Dropped packets: 0

Outbound statistics:

Total octets: 750

Total packets: 1

Erroneous packets: 0

Dropped packets: 0

Main path:

Seglist ID: 1

Seglist forwarding index: 2149580801

Weight: 1

Outbound statistics:

Total octets: 750

Total packets: 1

Erroneous packets: 0

Dropped packets: 0

Outgoing forwarding index: 2148532225

Interface: GE1/0/1

Nexthop: FE80::6CCE:CBFF:FE91:206

Path ID: 1

SID list: {44::44, 45::45}

Outbound statistics:

Total octets: 750

Total packets: 1

Erroneous packets: 0

Dropped packets: 0

Backup path:

Seglist ID: 2

Seglist forwarding index: 2149580802

Weight: 1

Outgoing forwarding index: 2148532226

Interface: GE1/0/2

Nexthop: FE80::6CCE:CBFF:FE91:207

Path ID: 2

SID list: {44::44, 45::47}

Table 8 Command output

Field	Description
Total forwarding entries	Total number of SRv6 TE forwarding entries.
Policy name/ID	Name/ID of an SRv6 TE policy.
Binding SID	SID value of the ingress node.
Forwarding index	Index of the SRv6 TE policy forwarding entry.
Inbound statistics	Statistics on inbound traffic (the traffic received by the BSID).
Total octets	Total number of octets forwarded.
Total packets	Total number of packets forwarded.
Erroneous packets	Number of erroneous packets.
Dropped packets	Number of dropped packets.
Outbound statistics	Statistics on outbound traffic.
Main path	Main path for traffic forwarding.
Backup path	Backup path for traffic forwarding.
Seglist ID	ID of the SID list.
Seglist forwarding index	Forwarding entry index of the SID list.
Weight	Weight of the SID list.
Outgoing forwarding index	The nexthop forwarding entry index of the first address in the SID list.
Interface	Brief name of the outgoing interface.
Nexthop	Next hop IPv6 address.
Path ID	ID of the SRv6 TE policy candidate path.
SID list	List of SIDs.
SID	SID of the node, which is an IPv6 address.
Common prefix length	Common prefix length of the next SID. If the next SID is not compressed, the value for this field is 0.
G-SID length	Length of the next G-SID. If the next SID is not compressed, the value for this field is 128.

‌

display segment-routing ipv6 te policy

Use display segment-routing ipv6 te policy to display SRv6 TE policy information.

Syntax

display segment-routing ipv6 te policy [ name policy-name | down | up | { color color-value | end-point ipv6 ipv6-address } * ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

name policy-name: Specifies an SRv6 TE policy by its name, a case-sensitive string of 1 to 59 characters.

down: Specifies the SRv6 TE policies in down state.

up: Specifies the SRv6 TE policies in up state.

color color-value: Specifies the color of an SRv6 TE policy, in the range of 0 to 4294967295.

end-point ipv6 ipv6-address: Specifies the endpoint IPv6 address of an SRv6 TE policy.

Usage guidelines

If you do not specify any parameters, this command displays information about all SRv6 TE policies.

Examples

# Display information about all SRv6 TE policies.

<Sysname> display segment-routing ipv6 te policy

Name/ID: p1/0

Color: 10

Endpoint: 1000::1

Name from BGP:

BSID:

Mode: Dynamic Type: Type 2 Request state: Succeeded

Current BSID: 8000::1 Explicit BSID: - Dynamic BSID: 8000::1

Reference counts: 3

Flags: A/BS/NC

Status: Up

AdminStatus: Not configured

Up time: 2020-03-09 16:09:40

Down time: 2020-03-09 16:09:13

Hot backup: Not configured

Statistics: Not configured

Statistics by service class: Not configured

Drop-upon-invalid: Disabled

BFD trigger path-down: Disabled

SBFD: Enabled

Remote: 1000

SBFD template name: abc

SBFD backup-template name: -

OAM SID: -

BFD Echo: Not configured

Forwarding index: 2150629377

Service-class: -

Rate-limit: -

Service-class: -

Encapsulation mode: -

Candidate paths state: Configured

Candidate paths statistics:

CLI paths: 1 BGP paths: 0 PCEP paths: 0

Candidate paths:

Preference : 20

CpathName:

Instance ID: 0 ASN: 0 Node address: 0.0.0.0

Peer address: ::

Optimal: Y Flags: V/A

Explicit SID list:

ID: 1 Name: Sl1

Weight: 1 Forwarding index: 2149580801

State: Up State(SBFD): -

Active path MTU: 1428 bytes

Table 9 Command output

Field	Description
Name/ID	SRv6 TE policy name/ID.
Color	Color attribute of the SRv6 TE policy.
Endpoint	Endpoint IPv6 address of the SRv6 TE policy. If the endpoint is not configured, this field displays None.
Name from BGP	Name of the SRv6 TE policy obtained from BGP. If no SRv6 TE policy was obtained from BGP, this field is empty.
BSID	SID value of the ingress node.
Mode	BSID configuration mode: · Explicit—Manually configured. · Dynamic—Dynamically requested. · None—Not configured.
Type	BSID type: · None—Not configured. · Type 2—IPv6 address.
Request state	BSID request state: · Conflicted. · Failed. · Succeeded.
Explicit BSID	Manually configured BSID.
Dynamic BSID	Dynamically requested BSID.
Reference counts	Number of times that the SRv6 TE policy has been referenced.
Flags	SRv6 TE policy flags: · A—Active SRv6 TE policy. · C—Optimal SRv6 TE policy. · N—In optimal SRv6 TE policy selection progress. · BA—Requesting BSID. · BS—Optimal BSID. · D—Deleted SRv6 TE policy. · CF—Conflicted with an existing BSID. · NC—Manually configured SRv6 TE policy. · NB—SRv6 TE policy obtained from a BGP route.
Status	SRv6 TE policy state: · Up · Down
AdminStatus	Whether the shutdown command has been configured for the SRv6 TE policy: · Configured—The policy is administratively down. · Not configured—The policy is administratively up.
Up time	Date and time when the SRv6 TE policy became up.
Down time	Date and time when the SRv6 TE policy became down.
Hot backup	Hot standby status for the SRv6 TE policy: · Enabled. · Disabled. · Not configured.
Statistics	Traffic statistics status for the SRv6 TE policy: · Disabled. · Enabled. · Not configured.
Statistics by service class	Service class based traffic statistics status for the SRv6 TE policy: · Enabled. · Not configured.
Drop-upon-invalid	Drops traffic when the SRv6 TE policy becomes invalid: · Disabled. · Enabled.
BFD trigger path-down	Places the SRv6 TE policy to down state when the BFD session for the SRv6 TE policy goes down: · Disabled. · Enabled.
SBFD	SBFD status for the SRv6 TE policy: · Enabled. · Disabled. · Not configured.
Remote	Remote discriminator of the SBFD session.
SBFD template name	Name of the SBFD template for the main path.
SBFD backup-template name	Name of the SBFD template for the backup SID list.
OAM SID	OAM SID added to SBFD packets or Echo BFD packets.
BFD Echo	Echo packet mode BFD status for the SRv6 TE policy: · Enabled. · Disabled. · Not configured.
Source IPv6 address	Source IPv6 address of the echo packet mode BFD session.
Echo template name	Name of the echo BFD template.
Echo backup-template name	Name of the echo BFD template for the backup SID list.
Forwarding index	Forwarding entry index of the SRv6 TE policy.
Service-class	Service class value of the SRv6 TE policy. If the default service class is used, this field displays a hyphen (-).
Rate-limit	Rate limit for the SRv6 TE policy. If no rate limit is configured, this field displays a hyphen (-).
Encapsulation mode	Encapsulation mode for the SRv6 TE policy: · Encaps. · Encaps Reduced. · Encaps include local End.X. · Insert. · Insert Reduced. · Insert include local End.X. If the encapsulation mode is not configured for the SRv6 TE policy, this field displays a hyphen (-).
Candidate paths state	Whether candidate paths are configured: · Configured. · Not configured.
Candidate paths statistics	Candidate paths statistics by path origin.
CLI paths	Number of manually configured candidate paths.
BGP paths	Number of candidate paths obtained from BGP SRv6 Policy routes.
PCEP paths	This field is not supported in the current software version. Number of candidate paths obtained from PCEP.
Candidate paths	SRv6 TE policy candidate path information.
Preference	SRv6 TE policy candidate path preference.
CPathName	Name of the candidate path obtained from a BGP route. If no path name was obtained, this field is empty.
Instance ID	BGP instance ID. A value of 0 indicates that the device does not obtain SRv6 TE policy information from BGP peers.
ASN	AS number. A value of 0 indicates that the device does not obtain SRv6 TE policy information from BGP peers.
Node address	BGP node address. For an SRv6 TE policy obtained from a BGP peer, the node address is the Router ID of the BGP peer. For an SRv6 TE policy obtained in other methods, the node address is 0.0.0.0.
Peer address	BGP peer address. For a manually configured SRv6 TE policy, the peer address is ::. For an SRv6 TE policy obtained from a BGP peer, the peer address is the address of the BGP peer.
Optimal	Whether the path is the optimal path: · Y—Yes. · N—No.
Flags	Flags of the SRv6 TE policy candidate path: · V—Valid candidate path. · A—Active candidate path. · None—No candidate path.
Explicit SID list	Explicit SID list in the candidate path of the SRv6 TE policy.
ID	SID list ID.
Name	SID list name.
Weight	Weight of the SID list in the candidate path.
Forwarding index	Forwarding entry index of the SID list.
State	SID list state: · UP. · DOWN.
State(type)	SBFD or echo BFD session state for the SID list: · Up. · Down. · Path Inactive—The candidate path contains no available SID list. · Unknown—The SBFD or echo BFD result is unknown. If SBFD or echo BFD is not configured, this field displays a hyphen (-).
Active path MTU	Active path MTU of the SID list, which equals the SRv6 path MTU minus the reserved path MTU.

‌

display segment-routing ipv6 te policy last-down-reason

Use display segment-routing ipv6 te policy last-down-reason to display information about the most recent down event for SRv6 TE policies.

Syntax

display segment-routing ipv6 te policy last-down-reason [ binding-sid bsid | color color-value endpoint ipv6 ipv6-address | policy-name policy-name ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

binding-sid bsid: Specifies an SRv6 TE policy by its BSID, which is an IPv6 address.

color color-value endpoint ipv6 ipv6-address: Specifies an SRv6 TE policy by its color attribute value and endpoint IPv6 address. The value range for the color attribute value is 0 to 4294967295.

policy-name policy-name: Specifies an SRv6 TE policy by its name, a case-sensitive string of 1 to 59 characters.

Usage guidelines

If you do not specify any parameters, this command displays information about the most recent down event for all SRv6 TE policies.

Examples

# Display information about the most recent down event for SRv6 TE policy abc.

<Sysname> display segment-routing ipv6 te policy last-down-reason policy-name abc

Name/ID: p1/1

Color: 10

Endpoint: 4::4

BSID: 5000::2

Up time: 2020-06-23 15:42:14

Down time: 2020-06-23 15:41:15

Down reason: Candidate path invalid segment list

Candidate paths:

Preference : 10

CPathName:

Explicit SID list:

ID: 1 Name: s1

Up time: 2020-06-23 15:42:14

Down time: 2020-06-23 15:41:15

Down reason: No SRv6 SID Out

Table 10 Command output

Field	Description
Name/ID	Name/ID of an SRv6 TE policy.
Color	Color attribute value of the SRv6 TE policy. If the color attribute is not configured, this field displays 0.
Endpoint	Endpoint address of the SRv6 TE policy. If the endpoint address is not configured, this field displays None.
BSID	SID value of the ingress node.
Up time	Time when the SRv6 TE policy came up.
Down time	Time when the SRv6 TE policy went down.
Down reason	Reason for the down event of the SRv6 TE policy: · Admin down—The SRv6 TE policy has been shut down by the shutdown command. · No Endpoint. · No candidate path. · No valid candidate path. · Candidate path invalid segment list—All SID lists in the candidate path are down. · Policy unconfigured—The SRv6 TE policy is being deleted. · Internal error.
Candidate paths	Candidate path information of the SRv6 TE policy.
Preference	Preference of the candidate path.
CPathName	Name of the candidate path. If no candidate path name is obtained from BGP, this field is empty.
Explicit SID List	SID list in the candidate path of the SRv6 TE policy.
ID	SID list index.
Name	SID list name.
Up time	Time when the SID list came up.
Down time	Time when the SID list went down.
Down reason	Reason for the down event of the SID list: · No SID list—The SID list does not exist. · No SRv6 SID Out—The first SID in the SID list has no outgoing interface. · Internal error.

‌

display segment-routing ipv6 te policy statistics

Use display segment-routing ipv6 te policy statistics to display SRv6 TE policy statistics.

Syntax

display segment-routing ipv6 te policy statistics

Views

Any view

Predefined user roles

network-admin

network-operator

Examples

# Display SRv6 TE policy statistics.

<Sysname> display segment-routing ipv6 te policy statistics

IPv6 TE Policy Database Statistics

Total policies: 1 (1 up 0 down)

Configured: 1 (1 up 0 down)

From BGP: 0 (Added 0 deleted 0 0 up 0 down)

Total candidate paths: 1

Configured: 1

From BGP: 0 (Added 0 deleted 0)

Total SID lists: 1 (1 up 0 down)

Configured: 1 (1 up 0 down)

From BGP: 0 (0 up 0 down)

Table 11 Command output

Field	Description
Total policies	Total number of SRv6 TE policies: · up—Number of SRv6 TE policies in up state. · down—Number of SRv6 TE policies in down state.
Configured	Number of manually configured SR policies. · up—Number of SRv6 TE policies in up state. · down—Number of SRv6 TE policies in down state.
From BGP	Number of SR policies learned through BGP. · Added—Number of BGP-added SRv6 TE policies. · deleted—Number of BGP-deleted SRv6 TE policies. · up—Number of SRv6 TE policies in up state. · down—Number of SRv6 TE policies in down state.

‌

display segment-routing ipv6 te policy status

Use display segment-routing ipv6 te policy status to display status information about SRv6 TE policies.

Syntax

display segment-routing ipv6 te policy status [ policy-name policy-name ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

policy-name policy-name: Specifies an SRv6 TE policy by its name, a case-sensitive string of 1 to 59 characters. If you do not specify this option, the command displays status information about all SRv6 TE policies.

Usage guidelines

The device executes the check items for an SRv6 TE policy one by one.

If the result for a check item is Passed, it means that the SRv6 TE policy passed the check for this item and the next item check starts.

If the result for a check item is Failed, the subsequent items will not be checked and the check result for those items is displayed as a hyphen (-).

Examples

# Display status information about all SRv6 TE policies.

<Sysname> display segment-routing ipv6 te policy status

Name/ID: p1/0

Status: Up

Check admin status : Passed

Check for endpoint & color : Passed

Check for segment list : Passed

Check valid candidate paths : Passed

Check for BSIDs : Passed

Table 12 Command output

Field	Description
Name/ID	Name/ID of an SRv6 TE policy.
Status	State of the SRv6 TE policy: · Up. · Down.
Check admin status	Check the administrative status of the SRv6 TE policy: · Passed—The SRv6 TE policy is administratively up. · Failed—The SRv6 TE policy is administratively shut down by using the shutdown command.
Check for endpoint & color	Check for the endpoint and color configuration for the SRv6 TE policy: · Passed—The endpoint address and color are configured. · Failed—The endpoint address or color is not configured.
Check for segment lists	Check for valid SID lists in the candidate paths of the SRv6 TE policy: · Passed—A valid SID list exists. · Failed—No valid SID list exists.
Check valid candidate paths	Check for an up candidate path in the SRv6 TE policy: · Passed—An up candidate path exists. · Failed—No up candidate path exists.
Check for BSIDs	Check for the binding SID configuration for the SRv6 TE policy: · Passed—A BSID is specified for the SRv6 TE policy. · Failed—No BSID is specified for the SRv6 TE policy.

‌

display segment-routing ipv6 te policy-group

Use display segment-routing ipv6 te policy-group to display information about SRv6 TE policy groups.

Syntax

display segment-routing ipv6 te policy-group [ group-id ] [ verbose ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

group-id: Specifies an SRv6 TE policy group by its ID in the range of 1 to 4294967295. If you do not specify this argument, the command displays information about all SRv6 TE policy groups.

verbose: Displays detailed SRv6 TE policy information. If you do not specify this keyword, the command displays brief SRv6 TE policy information.

Examples

# Display brief information about all SRv6 TE policy groups.

<Sysname> display segment-routing ipv6 te policy-group

Total number of policy groups: 1

GroupID GroupState UPMappings TotalMappings

10 Up 26 26

# Display detailed information about all SRv6 TE policy groups.

<Sysname> display segment-routing ipv6 te policy-group verbose

Total number of policy groups: 1

GroupID: 10 GroupState: Up

GroupNID: 2151677953 Referenced: 1

Flags: A

Endpoint: 4::4

UP/Total Mappings: 26/26

Color Type DSCP

10 IPv4 10, 12, 14, 16, 18, 20

Table 13 Command output

Field	Description
UPMappings	Number of up (valid) color-to-DSCP mappings in the SRv6 TE policy group.
TotalMappings	Total number of color-to-DSCP mappings in the SRv6 TE policy group.
GroupNID	Index of the forwarding entry for the SRv6 TE policy group.
Referenced	Number of times that the SRv6 TE policy group has been used.
Flags	Flags of the SRv6 TE policy group: · A—Assign the forwarding entry index of the SRv6 TE policy group. · F—Issue the forwarding entry of the SRv6 TE policy group. · W—Waiting for assigning the forwarding entry index of the SRv6 TE policy group. · D—Delete the SRv6 TE policy group. · None—The SRv6 TE policy group is in initialized or stable state.
Endpoint	Destination node IP address of the SRv6 TE policy group. None indicates that the endpoint is not configured.
UP/Total Mappings	Number of valid color-to-DSCP mappings/total number of configured color-to-DSCP mappings in the SRv6 TE policy group.
Color	Color value
Type	Packet type: IPv4 or IPv6.
DSCP	DSCP value.

‌

display segment-routing ipv6 te sbfd

Use display segment-routing ipv6 te sbfd to display SBFD information for SRv6 TE policies.

Syntax

display segment-routing ipv6 te sbfd [ down | policy { { color color-value | end-point ipv6 ipv6-address } * | name policy-name } | up ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

down: Displays SBFD information for SRv6 TE policies in down state.

policy: Displays SBFD information for the specified SRv6 TE policy.

color color-value: Specifies the color attribute value of an SRv6 TE policy, in the range of 0 to 4294967295.

end-point ipv6 ipv6-address: Specifies the IPv6 address of the endpoint of an SRv6 TE policy.

name policy-name: Specifies the name of an SRv6 TE policy, a case-sensitive string of 1 to 59 characters.

up: Displays SBFD information for SRv6 TE policies in up state.

Usage guidelines

If you do not specify any parameters, this command displays SBFD information for all SRv6 TE policies.

Examples

# Display SBFD information for all SRv6 TE policies.

<Sysname> display segment-routing ipv6 te policy sbfd

Color: 10

Endpoint: 4::4

Policy name: p1

State: Down

Nid: 2149580801

BFD type: SBFD

Remote Discr: 100

State: Down

Timer: 30

VPN index: 0

Template name: abc

Table 14 Command output

Field	Description
Color	Color attribute value of an SRv6 TE policy.
Endpoint	Endpoint IP address of the SRv6 TE policy.
Policy name	Name of the SRv6 TE policy.
State	SBFD session state: · Up. · Down. · Delete.
Nid	Forwarding entry index for an SID list.
BFD type	The current software version supports only the SBFD type.
Remote Discr	Remote discriminator.
Timer	SBFD session timer, in seconds.

‌

display segment-routing ipv6 te segment-list

Use display segment-routing ipv6 te segment-list to display SRv6-TE SID list information.

Syntax

display segment-routing ipv6 te segment-list [ name seglist-name | id id-value ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

name segment-list-name: Specifies a SID list by its name, a case-sensitive string of 1 to 128 characters.

id id-value: Specifies a SID list by its ID. The value range for the SID list ID is 1 to 4294967295.

Usage guidelines

If you do not specify a SID list name or ID, this command displays information about all SRv6-TE SID lists.

To view SID list ID information, execute the display segment-routing ipv6 te policy command.

Examples

# Display information about all SRv6-TE SID lists.

<Sysname> display segment-routing ipv6 te segment-list

Total Segment lists: 1

Name/ID: A/1

Origin: CLI

Status: Up

Nodes: 1

Index : 1 SID: 1::2

Type : Type 2 Flags: None

Coc Type : - Common prefix length: 0

Table 15 Command output

Field	Description
Total Segment lists	Number of SID lists.
Name/ID	SID list name/ID.
Origin	Origin of the SID list. Options include: · CLI—Locally configured in the CLI. · BGP—Issued by BGP. · PCE—Issued by a PCE. (This option is not supported in the current software version.) If the SID list does not have a valid origin, this field displays a hyphen (-).
Status	SID list status, Down or Up.
Nodes	Number of nodes in the SID list.
Index	Node index.
SID	SID value (IPv6 address) of the node.
Type	SID type of the node: · None—Not configured. · Type 2—IPv6 address.
Flags	Node flags, which are not defined and displayed as None.
Coc Type	Compression type of the SID, which is COC32, representing the 32-bit compression. If the SID is not compressed, this field displays a hyphen (-).
Common prefix length	Common prefix length of the G-SID.

‌

distribute bgp-ls

Use distribute bgp-ls to enable the device to distribute SRv6 TE policy candidate path information to BGP-LS.

Use undo distribute bgp-ls to restore the default.

Syntax

distribute bgp-ls

undo distribute bgp-ls

Default

The device does not distribute SRv6 TE policy candidate path information to BGP-LS.

Views

SRv6 TE view

Predefined user roles

network-admin

Usage guidelines

After this command is executed, the device distributes SRv6 TE policy candidate path information to BGP-LS. BGP-LS advertises the SRv6 TE policy candidate path information in routes to meet application requirements.

Examples

# Enable the device to distribute SRv6 TE policy candidate path information to BGP-LS.

<Sysname> system-view

[Sysname] segment-routing-ipv6

[Sysname-segment-routing-ipv6] traffic-engineering

[Sysname-srv6-te] distribute bgp-ls

drop-upon-invalid enable

Use drop-upon-invalid enable to enable the device to drop traffic when an SRv6 TE policy becomes invalid.

Use undo drop-upon-invalid enable to disable the drop-upon-invalid feature for an SRv6 TE policy.

Syntax

drop-upon-invalid enable

undo drop-upon-invalid enable

Default

The drop-upon-invalid feature is disabled for an SRv6 TE policy. The device does not drop traffic when the SRv6 TE policy becomes invalid.

Views

SRv6 TE policy view

Predefined user roles

network-admin

Usage guidelines

Enable this feature for an SRv6 TE policy if you want to use only the SRv6 TE policy to forward traffic.

By default, if all forwarding paths of an SRv6 TE policy become invalid, the device forwards the packets through IPv6 routing table lookup based on the packet destination IPv6 addresses.

After you execute the drop-upon-invalid enable command, the device drops the packets if all forwarding paths of the SRv6 TE policy become invalid.

The drop-upon-invalid enable command does not take effect in the following cases:

· BSID request failed or BSID conflict occurred for the SRv6 TE policy. To view the BSID request state, see the Request state field in the display segment-routing ipv6 te policy command output.

· The SRv6 TE policy is invalid. To check the SRv6 TE policy validity, see the Forwarding index field in the display segment-routing ipv6 te policy command output. If the value is 0, the SRv6 TE policy is invalid.

Examples

# Enable the device to drop traffic when SRv6 TE policy a1 becomes invalid.

<Sysname> system-view

[Sysname] segment-routing ipv6

[Sysname-segment-routing-ipv6] traffic-engineering

[Sysname-srv6-te] policy a1

[Sysname-srv6-te-policy-a1] drop-upon-invalid enable

encapsulation-mode

Use encapsulation-mode to configure the encapsulation mode for an SRv6 TE policy.

Use undo encapsulation-mode to restore the default.

Syntax

encapsulation-mode encaps reduced [ disable ]

undo encapsulation-mode encaps reduced

encapsulation-mode insert

undo encapsulation-mode insert

encapsulation-mode insert reduced [ disable ]

undo encapsulation-mode insert reduced

Default

The encapsulation mode is not configured for an SRv6 TE policy, and the encapsulation mode configured in SRv6 TE view applies.

Views

SRv6 TE policy view

Predefined user roles

network-admin

Parameters

encaps reduced: Specifies the encapsulation mode as reduced encapsulation mode.

insert: Specifies the encapsulation mode as insertion mode.

insert reduced: Specifies the encapsulation mode as reduced insertion mode.

disable: Disables the specified encapsulation mode.

Usage guidelines

If the traffic steering mode is BSID, packets whose destination IPv6 address is the same as the BSID of an SRv6 TE policy will be forwarded by the SRv6 TE policy. In this case, the device needs to encapsulate the SID list of the SRv6 TE policy into the packets. The following encapsulation modes are available:

· Encaps—Normal encapsulation mode. It adds a new IPv6 header and an SRH to the original packets. All SIDs in the SID list of the SRv6 TE policy are encapsulated in the SRH.

· Encaps.Red—Reduced mode of the normal encapsulation mode. It adds a new IPv6 header and an SRH to the original packets. The first SID in the SID list of the SRv6 TE policy is not encapsulated in the SRH to reduce the SRH length. All other SIDs in the SID list are encapsulated in the SRH.

· Insert—Insertion mode. It inserts an SRH after the original IPv6 header. All SIDs in the SID list of the SRv6 TE policy are encapsulated in the SRH.

· Insert.Red—Reduced insertion mode. It inserts an SRH after the original IPv6 header. The first SID in the SID list of the SRv6 TE policy is not encapsulated in the SRH to reduce the SRH length. All other SIDs in the SID list are encapsulated in the SRH.

In Encaps or Encaps.Red encapsulation mode, the destination IPv6 address in the new IPv6 header is the first SID in the SID list of the SRv6 TE policy. The source IPv6 address is the IPv6 address specified by using the encapsulation source-address command.

In Insert or Insert.Red encapsulation mode, the destination IPv6 address in the original IPv6 header is changed to the first SID in the SID list of the SRv6 TE policy. The source IPv6 address in the original IPv6 header does not change.

You can configure the encapsulation mode for all SRv6 TE policies globally in SRv6 TE view or for a specific SRv6 TE policy in SRv6 TE policy view. The policy-specific configuration takes precedence over the global configuration. An SRv6 TE policy uses the global configuration only when it has no policy-specific configuration.

The normal encapsulation modes are exclusive with the insertion modes. If you configure a normal encapsulation mode and an insertion mode for an SRv6 TE policy, the most recent configuration takes effect.

If you configure the Insert or Insert.Red mode for an SRv6 TE policy, it uses the Encaps mode to encapsulate received IPv4 packets.

If you execute both the encapsulation-mode encaps reduced command and the encapsulation-mode encaps include local-end.x command for an SRv6 TE policy, the encapsulation-mode encaps include local-end.x command takes effect.

If you execute both the encapsulation-mode insert reduced command and the encapsulation-mode insert include local-end.x command for an SRv6 TE policy, the encapsulation-mode insert include local-end.x command takes effect.

Examples

# Configure SRv6 TE policy 1 to use the Encaps.Red encapsulation.

<Sysname> system-view

[Sysname] segment-routing ipv6

[Sysname-segment-routing-ipv6] traffic-engineering

[Sysname-srv6-te] policy 1

[Sysname-srv6-te-policy-1] encapsulation-mode encaps reduced

Related commands

encapsulation source-address

srv6-policy encapsulation-mode

encapsulation-mode encaps include local-end.x

Use encapsulation-mode encaps include local-end.x to configure local End.X SID encapsulation in the SRH of the packets forwarded by an SRv6 TE policy with a normal encapsulation mode.

Use undo encapsulation-mode encaps include local-end.x to restore the default.

Syntax

encapsulation-mode encaps include local-end.x [ disable ]

undo encapsulation-mode encaps include local-end.x

Default

The local End.X SID encapsulation is not configured for an SRv6 TE policy with a normal encapsulation mode, and the local End.X SID encapsulation setting configured in SRv6 TE view applies.

Views

SRv6 TE policy view

Predefined user roles

network-admin

Parameters

disable: Disables encapsulating the local End.X SID into the SRH header of packets forwarded by an SRv6 TE policy with a normal encapsulation mode. If you do not specify this keyword, the local End.X SID will be encapsulated into the SRH of the packets.

Usage guidelines

If the traffic steering mode is BSID and the SRv6 SID of the ingress node is an End.X SID, the device does not encapsulate the End.X SID into the SRH by default.

To obtain complete SRv6 forwarding path information from the SRH of packets, use this command to configure the device to encapsulate the local End.X SID in the SRH.

You can configure the local End.X SID encapsulation for all SRv6 TE policies globally in SRv6 TE view or for a specific SRv6 TE policy in SRv6 TE policy view. The policy-specific configuration takes precedence over the global configuration. An SRv6 TE policy uses the global configuration only when it has no policy-specific configuration.

If you execute the encapsulation-mode encaps include local-end.x command and the encapsulation-mode insert include local-end.x command for an SRv6 TE policy, the most recent configuration takes effect.

Examples

# Include the End.X SID in the SRH of the packets forwarded by an SRv6 TE policy with a normal encapsulation mode.

<Sysname> system-view

[Sysname] segment-routing ipv6

[Sysname-segment-routing-ipv6] traffic-engineering

[Sysname-srv6-te] policy 1

[Sysname-srv6-te-policy-1] encapsulation-mode encaps include local-end.x

Related commands

srv6-policy encapsulation-mode encaps include local-end.x

encapsulation-mode insert include local-end.x

Use encapsulation-mode insert include local-end.x to configure local End.X SID encapsulation in the SRH of the packets forwarded by an SRv6 TE policy with an insertion encapsulation mode.

Use undo encapsulation-mode insert include local-end.x to restore the default.

Syntax

encapsulation-mode insert include local-end.x [ disable ]

undo encapsulation-mode insert include local-end.x

Default

The local End.X SID encapsulation is not configured for an SRv6 TE policy with an insertion encapsulation mode, and the local End.X SID encapsulation setting configured in SRv6 TE view applies.

Views

SRv6 TE policy view

Predefined user roles

network-admin

Parameters

disable: Disables encapsulating the local End.X SID into the SRH header inserted into the packets forwarded by an SRv6 TE policy with an insertion encapsulation mode. If you do not specify this keyword, the local End.X SID will be encapsulated into the SRH of the packets.

Usage guidelines

If the traffic steering mode is BSID and the SRv6 SID of the ingress node is an End.X SID, the device does not encapsulate the End.X SID into the SRH by default.

To obtain complete SRv6 forwarding path information from the SRH of packets, use this command to configure the device to encapsulate the local End.X SID in the SRH.

If you execute the encapsulation-mode encaps include local-end.x command and the encapsulation-mode insert include local-end.x command alternately for an SRv6 TE policy, the most recent configuration takes effect.

Examples

# Include the End.X SID in the SRH of the packets forwarded by an SRv6 TE policy with an insertion encapsulation mode.

<Sysname> system-view

[Sysname] segment-routing ipv6

[Sysname-segment-routing-ipv6] traffic-engineering

[Sysname-srv6-te] policy 1

[Sysname-srv6-te-policy-1] encapsulation-mode insert include local-end.x

Related commands

srv6-policy encapsulation-mode insert include local-end.x

end-point

Use end-point to configure the endpoint IP address for the SRv6 TE policy group.

Use undo end-point to restore the default.

Syntax

end-point ipv6 ipv6-address

undo end-point ipv6

Default

No endpoint address is configured for the SRv6 TE policy group.

Views

SRv6 TE policy group view

Predefined user roles

network-admin

Parameters

ipv6 ipv6-address: Specifies the endpoint IPv6 address for the SRv6 TE policy group.

Usage guidelines

The SRv6 TE policies added to the SRv6 TE policy group must use the same endpoint IPv6 address as the SRv6 TE policy group.

If you execute this command multiple times, the most recent configuration takes effect.

Examples

# Configure the endpoint address as 100::2 for SRv6 TE policy group 10.

<Sysname> system-view

[Sysname] segment-routing ipv6

[Sysname-segment-routing-ipv6] traffic-engineering

[Sysname-srv6-te] policy-group 10

[Sysname-srv6-te-policy-group-10] end-point ipv6 100::2

explicit segment-list

Use explicit segment-list to specify a SID list for a candidate path.

Use undo explicit segment-list to delete a SID list of a candidate path or restore the default weight of a SID list.

Syntax

explicit segment-list segment-list-name [ weight weight-value ]

undo explicit segment-list segment-list-name [ weight ]

Default

No SID lists are specified for an SRv6 TE policy candidate path.

Views

SRv6 TE policy path preference view

Predefined user roles

network-admin

Parameters

segment-list-name: Specifies an SID list name, a case-sensitive string of 1 to 128 characters.

weight weight-value: Specifies a weight for the SID list, in the range of 1 to 4294967295. The default weight is 1.

Usage guidelines

An SRv6 TE policy uses the SID list specified for the highest-preference candidate path as a traffic forwarding subpath.

An SRv6 TE policy candidate path can have multiple SID lists. All the SID lists can be used to forward traffic for load sharing based on their weights. Assume SID lists a, b, and c are assigned weights x, y, z, respectively. The load of SID list a is x/(x+y+z) of the total traffic.

If you assign weight values for the same SID list multiple times, the most recent configuration takes effect.

Examples

# Configure SID list abc for the SRv6 TE policy candidate path with preference 20, and the set the SID list weight to 20.

<Sysname> system-view

[Sysname] segment-routing ipv6

[Sysname-segment-routing-ipv6] traffic-engineering

[Sysname-srv6-te] policy a1

[Sysname-srv6-te-policy-a1] candidate-paths

[Sysname-srv6-te-policy-a1-path] preference 20

[Sysname-srv6-te-policy-a1-path-pref-20] explicit segment-list abc weight 20

Related commands

segment-list

fast-reroute mirror delete-delay

Use fast-reroute mirror delete-delay to configure the mirror FRR deletion delay time.

Use undo fast-reroute mirror delete-delay to restore the default.

Syntax

fast-reroute mirror delete-delay delete-delay-time

undo fast-reroute mirror delete-delay

Default

The mirror FRR deletion delay time is 60 seconds.

Views

IS-IS IPv6 unicast address family view

OSPFv3 view

Predefined user roles

network-admin

Parameters

delete-delay-time: Specifies the deletion delay time, in the range of 1 to 21845 seconds.

Usage guidelines

In an egress protection scenario, the transit node deletes the mirror FRR path after completing route convergence. If the deletion occurs before the ingress node switches traffic back from the mirror FRR path, the traffic will be dropped because of no mirror FRR path.

To resolve this issue, you can configure a proper mirror FRR deletion delay time on the transit node to delay the deletion of the mirror FRR route. So, packets can be forwarded over the mirror FRR path before the ingress finishes the path switchover.

Examples

# In IS-IS process 1, set the mirror FRR deletion delay time to 100 seconds.

<Sysname> system-view

[Sysname] isis 1

[Sysname-isis-1] address-family ipv6

[Sysname-isis-1-ipv6] fast-reroute mirror delete-delay 100

# In OSPFv3 process 1, set the mirror FRR deletion delay time to 100 seconds.

<Sysname> system-view

[Sysname] ospfv3 1

[Sysname-ospfv3-1] fast-reroute mirror delete-delay 100

Related commands

fast-reroute mirror enable

Use fast-reroute mirror enable to enable egress protection.

Use undo fast-reroute mirror enable to disable egress protection.

Syntax

fast-reroute mirror enable

undo fast-reroute mirror enable

Default

Egress protection is disabled.

Views

IS-IS IPv6 unicast address family view

OSPFv3 view

Predefined user roles

network-admin

Usage guidelines

Egress protection enables an SRv6 node to compute a backup path (mirror FRR path) for the egress node based on the End.M SID carried in a received IPv6 IS-IS route or OSPFv3 route. When the egress node fails, the transit node can forward traffic to the node that protects the egress node according to the End.M SID.

Examples

# Enable IS-IS egress protection.

<Sysname> system-view

[Sysname] isis 1

[Sysname-isis-1] address-family ipv6

[Sysname-isis-1-ipv6] fast-reroute mirror enable

# Enable OSPFv3 egress protection.

<Sysname> system-view

[Sysname] ospfv3 1

[Sysname-ospfv3-1] fast-reroute mirror enable

forwarding statistics

Use forwarding statistics to configure traffic forwarding statistics for an SRv6 TE policy.

Use undo forwarding statistics to restore the default.

Syntax

forwarding statistics { disable | [ service-class ] enable }

undo forwarding statistics

Default

An SRv6 TE policy uses the traffic forwarding statistics configuration in SRv6 TE view.

Views

SRv6 TE policy view

Predefined user roles

network-admin

Parameters

disable: Disables the SRv6 TE policy forwarding statistics.

enable: Enables the SRv6 TE policy forwarding statistics.

service-class: Enables the SRv6 TE policy forwarding statistics by service class. This feature collects statistics on the total traffic as well as the traffic of each service class that are forwarded by the SRv6 TE policy tunnel. If you do not specify this keyword, the device only collects statistics on the total traffic forwarded by the SRv6 TE policy tunnel.

The following compatibility matrixes show the support of hardware platforms for the service-class keyword:

Hardware	Parameter compatibility
MSR610	No
MSR810, MSR810-W, MSR810-W-DB, MSR810-LM, MSR810-W-LM, MSR810-10-PoE, MSR810-LM-HK, MSR810-W-LM-HK, MSR810-LM-CNDE-SJK, MSR810-CNDE-SJK, MSR810-EI, MSR810-LM-EA, MSR810-LM-EI	Yes
MSR810-LMS, MSR810-LUS	No
MSR810-SI, MSR810-LM-SI	No
MSR810-LMS-EA, MSR810-LME	Yes
MSR1004S-5G, MSR1004S-5G-CN	Yes
MSR1104S-W, MSR1104S-W-CAT6, MSR1104S-5G-CN, MSR1104S-W-5G-CN	Yes
MSR2600-6-X1, MSR2600-15-X1, MSR2600-15-X1-T	Yes
MSR2600-10-X1	Yes
MSR 2630	Yes
MSR3600-28, MSR3600-51	Yes
MSR3600-28-SI, MSR3600-51-SI	No
MSR3600-28-X1, MSR3600-28-X1-DP, MSR3600-51-X1, MSR3600-51-X1-DP	Yes
MSR3600-28-G-DP, MSR3600-51-G-DP	Yes
MSR3610-I-DP, MSR3610-IE-DP, MSR3610-IE-ES, MSR3610-IE-EAD, MSR-EAD-AK770, MSR3610-I-IG, MSR3610-IE-IG	Yes
MSR3610-X1, MSR3610-X1-DP, MSR3610-X1-DC, MSR3610-X1-DP-DC, MSR3620-X1, MSR3640-X1	Yes
MSR3610, MSR3620, MSR3620-DP, MSR3640, MSR3660	Yes
MSR3610-G, MSR3620-G	Yes
MSR3640-G	Yes
MSR3640-X1-HI	Yes

Hardware	Parameter compatibility
MSR810-W-WiNet, MSR810-LM-WiNet	Yes
MSR830-4LM-WiNet	Yes
MSR830-5BEI-WiNet, MSR830-6EI-WiNet, MSR830-10BEI-WiNet	Yes
MSR830-6BHI-WiNet, MSR830-10BHI-WiNet	Yes
MSR2600-6-WiNet	Yes
MSR2600-10-X1-WiNet	Yes
MSR2630-WiNet	Yes
MSR3600-28-WiNet	Yes
MSR3610-X1-WiNet	Yes
MSR3610-WiNet, MSR3620-10-WiNet, MSR3620-DP-WiNet, MSR3620-WiNet, MSR3660-WiNet	Yes

Hardware	Parameter compatibility
MSR860-6EI-XS	Yes
MSR860-6HI-XS	Yes
MSR2630-XS	Yes
MSR3600-28-XS	Yes
MSR3610-XS	Yes
MSR3620-XS	Yes
MSR3610-I-XS	Yes
MSR3610-IE-XS	Yes
MSR3620-X1-XS	Yes
MSR3640-XS	Yes
MSR3660-XS	Yes

Hardware	Parameter compatibility
MSR810-LM-GL	Yes
MSR810-W-LM-GL	Yes
MSR830-6EI-GL	Yes
MSR830-10EI-GL	Yes
MSR830-6HI-GL	Yes
MSR830-10HI-GL	Yes
MSR1004S-5G-GL	Yes
MSR2600-6-X1-GL	Yes
MSR3600-28-SI-GL	No

Usage guidelines

You can configure traffic forwarding statistics for all SRv6 TE policies globally in SRv6 TE view or for a specific SRv6 TE policy in SRv6 TE policy view. The policy-specific configuration takes precedence over the global configuration. An SRv6 TE policy uses the global configuration only when it has no policy-specific configuration.

If you execute this command multiple times, the most recent configuration takes effect.

Examples

# Enable traffic forwarding statistics for SRv6 TE policy 1.

<Sysname> system-view

[Sysname] segment-routing ipv6

[Sysname-segment-routing-ipv6] traffic-engineering

[Sysname-srv6-te] policy 1

[Sysname-srv6-te-policy-1] forwarding statistics enable

Related commands

display segment-routing ipv6 te forwarding

reset segment-routing ipv6 te forwarding statistics

srv6-policy forwarding statistic enable

srv6-policy forwarding statistic interval

import-route sr-policy

Use import-route sr-policy to enable BGP to redistribute routes from the BGP IPv6 SR policy.

Use undo import-route sr-policy to restore the default.

Syntax

import-route sr-policy

undo import-route sr-policy

Default

BGP does not redistribute BGP IPv6 SR policy routes.

Views

BGP IPv6 SR policy address family

Predefined user roles

network-admin

Usage guidelines

After you execute this command, the system will redistribute the local BGP IPv6 SR policy routes to the BGP routing table and advertise the routes to IBGP peers. Then, the peers can forward traffic based on the SRv6 TE policy.

Examples

# In BGP IPv6 SR policy address family view, enable BGP to redistribute routes from the BGP IPv6 SR policy.

<Sysname> system-view

[Sysname] bgp 100

[Sysname-bgp-default] address-family ipv6 sr-policy

[Sysname-bgp-default-srpolicy-ipv6] import-route sr-policy

index

Use index to add a node to a SID list.

Use undo index to delete a node from a SID list.

Syntax

index index-number ipv6 ipv6-address

index index-number coc32 ipv6 ipv6-address common-prefix-length

undo index index-number

Default

No nodes exist in a SID list.

Views

SID list view

Predefined user roles

network-admin

Parameters

index-number: Specifies the node index, in the range of 1 to 65535.

ipv6 ipv6-address: Specifies the IPv6 address of the node.

coc32: Adds the COC flavor. It indicates that the next node of the current node is a 32-bit G-SID.

common-prefix-length: Specifies the length of the common prefix of the next G-SID. The value range for this argument is 1 to 94.

Usage guidelines

When you add a G-SID to the SID list, follow these restrictions and guidelines:

· The common prefix length configured by this command must be the same as that of the locator where the next node belongs.

· The SRv6 SID corresponding to the previous node of the G-SID must be an End(COC32) SID or End.X(COC32) SID.

· The SRv6 SID corresponding to the last node in the SID list cannot carry the COC flavor. You cannot use the index index-number coc32 ipv6 command to specify the SRv6 SID for the penultimate node.

Examples

# Add a node to SID list abc, and set the node index to 1 and IPv6 address to 1000::1.

<Sysname> system-view

[Sysname] segment-routing ipv6

[Sysname-segment-routing-ipv6] traffic-engineering

[Sysname-srv6-te] segment-list abc

[Sysname-srv6-te-sl-abc] index 1 ipv6 1000::1

# Add nodes to SID list text as follows:

· Add a node whose index is 10, IPv6 address is 100::1, next node as 32-bit G-SID, and the common prefix length of the G-SID is 64.

· Add a node whose index is 20, IPv6 address is 200::1:0:0, next node as 32-bit G-SID, and the common prefix length of the G-SID is 64.

· Add a node whose index is 30, IPv6 address is 200::2:0:0, next node as 32-bit G-SID, and the common prefix length of the G-SID is 64.

· Add a node whose index is 40, IPv6 address is 200::3:0:0, next node as 32-bit G-SID, and the common prefix length of the G-SID is 64.

· Add a node whose index is 50 and IPv6 address is 200::4:0:0.

· Add a node whose index is 60 and IPv6 address is 300::3.

<Sysname> system-view

[Sysname] segment-routing ipv6

[Sysname-segment-routing-ipv6] traffic-engineering

[Sysname-srv6-te] segment-list text

[Sysname-srv6-te-sl-abc] index 10 coc32 ipv6 100::1 64

[Sysname-srv6-te-sl-abc] index 20 coc32 ipv6 200::1:0:0 64

[Sysname-srv6-te-sl-abc] index 30 coc32 ipv6 200::2:0:0 64

[Sysname-srv6-te-sl-abc] index 40 coc32 ipv6 200::3:0:0:0 64

[Sysname-srv6-te-sl-abc] index 50 ipv6 200::4:0:0

[Sysname-srv6-te-sl-abc] index 60 ipv6 300::3

Related commands

locator

mirror remote-sid delete-delay

Use mirror remote-sid delete-delay to configure the deletion delay time for remote SRv6 SID mappings with VPN instances/cross-connects/VSIs.

Use undo mirror remote-sid delete-delay to restore the default.

Syntax

mirror remote-sid delete-delay delete-delay-time

undo mirror remote-sid delete-delay

Default

The deletion delay time for remote SRv6 SID and VPN instance/cross-connect/VSI mappings is 60 seconds.

Views

SRv6 view

Predefined user roles

network-admin

Parameters

delete-delay-time: Specifies the deletion delay time, in the range of 1 to 21845 seconds.

Usage guidelines

In an egress protection scenario, if the egress node and the egress node's protection node are disconnected, the protection node will delete the BGP routes received from the egress node. The remote SRv6 SID and VPN instance/cross-connect/VSI mappings will then be deleted as a result. To avoid this issue, you can configure the mappings deletion delay time on the protection node. This ensures that traffic is forwarded through the protection node before the ingress detects the egress failure and computes a new forwarding path.

Examples

# Set the deletion delay time for remote SRv6 SID and VPN instance/cross-connect/VSI mappings to 100 seconds.

<Sysname> system-view

[Sysname] segment-routing ipv6

[Sysname-segment-routing-ipv6] mirror remote-sid delete-delay 100

policy

Use policy to create an SRv6 TE policy and enter its view, or enter the view of an existing SRv6 TE policy.

Use undo policy to delete an SRv6 TE policy and all the configuration in the SRv6 TE policy.

Syntax

policy policy-name

undo policy policy-name

Default

No SRv6 TE policies exist.

Views

SRv6 TE view

Predefined user roles

network-admin

Parameters

policy-name: Specifies an SRv6 TE policy name, a case-sensitive string of 1 to 59 characters.

Examples

# Create an SRv6 TE policy named srv6policy and enter its view.

<Sysname> system-view

[Sysname] segment-routing ipv6

[Sysname-segment-routing-ipv6] traffic-engineering

[Sysname-srv6-te] policy p1

[Sysname-srv6-te-policy-p1]

policy-group

Use policy-group to create an SRv6 TE policy group and enter its view, or enter the view of an existing SRv6 TE policy group.

Use undo policy-group to delete an SRv6 TE policy group and all the configuration in the SRv6 TE policy group.

Syntax

policy-group group-id

undo policy-group group-id

Default

No SRv6 TE policy groups exist.

Views

SRv6 TE view

Predefined user roles

network-admin

Parameters

group-name: Specifies an SRv6 TE policy group by its ID in the range of 1 to 4294967295.

Usage guidelines

You can add SRv6 TE policies to an SRv6 TE policy group to implement SRv6 TE policy based forwarding according to DSCP values of packets.

Examples

# Create SRv6 TE policy group 1 and enter its view.

<Sysname> system-view

[Sysname] segment-routing ipv6

[Sysname-segment-routing-ipv6] traffic-engineering

[Sysname-srv6-te] policy-group 1

[Sysname-srv6-te-policy-group-1]

preference

Use preference to set the preference for an SRv6 TE policy candidate path and enter SRv6 TE policy path preference view, or enter an existing SRv6 TE policy path preference view.

Use undo preference to delete an SRv6 TE policy candidate path preference and all the configuration in the SRv6 TE policy path preference view.

Syntax

preference preference-value

undo preference preference-value

Default

No preference is set for an SRv6 TE policy candidate path.

Views

SRv6 TE policy candidate path view

Predefined user roles

network-admin

Parameters

preference-value: Specifies a candidate path preference in the range of 1 to 65535. A bigger value represents a higher preference.

Usage guidelines

A preference represents a candidate path of an SRv6 TE policy.

Examples

# Set the preference of an SRv6 TE policy candidate path to 20, and enter SRv6 TE policy path preference view.

<Sysname> system-view

[Sysname] segment-routing ipv6

[Sysname-segment-routing-ipv6] traffic-engineering

[Sysname-srv6-te] policy a1

[Sysname-srv6-te-policy-a1] candidate-paths

[Sysname-srv6-te-policy-a1-path] preference 20

[Sysname-srv6-te-policy-a1-path-pref-20]

rate-limit

Use rate-limit to set a rate limit for an SRv6 TE policy.

Use undo rate-limit to restore the default.

Syntax

rate-limit kbps

undo rate-limit

Default

No rate limit is set for an SRv6 TE policy.

Views

SRv6 TE policy view

Predefined user roles

network-admin

Parameters

kbps: Specifies the rate limit, in the range of 1 to 4294967295, in kbps.

Usage guidelines

When the rate of the packets forwarded by an SRv6 TE policy exceeds the rate limit, the device drops the packets that exceed the rate limit.

If you execute this command multiple times, the most recent configuration takes effect.

Examples

# Set the rate limit for SRv6 TE policy aaa to 15000 kbps.

<Sysname> system-view

[Sysname] segment-routing ipv6

[Sysname-segment-routing-ipv6] traffic-engineering

[Sysname-srv6-te] policy aaa

[Sysname-srv6-te-policy-aaa] rate-limit 15000

reset segment-routing ipv6 te forwarding statistics

Use reset segment-routing ipv6 te forwarding statistics to clear forwarding statistics for all SRv6 TE policies.

Syntax

reset segment-routing ipv6 te forwarding statistics [ binding-sid binding-sid | color color-value endpoint endpoint-ipv6 | name name-value ]

Views

User view

Predefined user roles

network-admin

Parameters

binding-sid bsid: Specifies the BSID of an SRv6 TE policy, which is an IPv6 address.

color color-value endpoint endpoint-ipv6: Specifies the color value and end-point IPv6 address of an SRv6 TE policy. The value range for the color-value argument is 0 to 4294967295.

name policy-name: Specifies the name of an SRv6 TE policy, a case-sensitive string of 1 to 59 characters.

Usage guidelines

If you do not specify any parameters, this command clears forwarding statistics for all SRv6 TE policies.

Examples

# Clear forwarding statistics for all SRv6 TE policies.

<Sysname> reset segment-routing ipv6 te forwarding statistics

Related commands

display segment-routing ipv6 te forwarding

forwarding statistics

srv6-policy forwarding statistics enable

srv6-policy forwarding statistics interval

router-id filter

Use router-id filter to enable Router ID filtering.

Use undo router-id filter to disable Router ID filtering.

Syntax

router-id filter [ bgp-rib-only ]

undo router-id filter

Default

Router ID filtering is disabled.

Views

BGP IPv6 SR policy address family.

Predefined user roles

network-admin

Parameters

bgp-rib-only: Enables the device to accept the route without generating an SRv6 TE policy accordingly when it receives a BGP IPv6 SR policy route and the Route Target attribute of the route does not carry the local router ID.

Usage guidelines

For the device to process only part of the received BGP IPv6 SR policy routes, you can execute this command to enable filtering the routes by Router ID.

This command enables the device to check the Route Target attribute of a received BGP IPv6 SR policy route.

· If the Route Target attribute contains the Router ID of the local device, the device accepts the route and generates an SRv6 TE policy accordingly.

· If the Route Target attribute does not contain the Router ID of the local device, the device processes the route as follows:

¡ If the bgp-rib-only keyword is not specified in the command, the device drops the route.

¡ If the bgp-rib-only keyword is specified in the command, the device accepts the route but does not generate the corresponding SRv6 TE policy.

When the controller advertises a BGP IPv6 SR policy route to the source node, the transit nodes between the controller and the source node only need to forward the BGP IPv6 SR policy route. They do not need to generate the SRv6 TE policy. In this case, you can execute the router-id filter bgp-rib-only command on the transit nodes. Then, when a transit node receives a BGP IPv6 SR policy route, it forwards the route even if the route's Route Target attribute does not contain the Router ID of the local device. Meanwhile, it does not generate an SRv6 TE policy in order to not affect packet forwarding.

If you execute this command multiple times, the most recent configuration takes effect.

To use Router ID filtering, make sure you add Route Target attributes to BGP IPv6 SR policy routes properly by using routing policy or other methods. Otherwise, Router ID filtering might learn or drop BGP IPv6 SR policy routes incorrectly.

Examples

# Enable Router ID filtering.

<Sysname> system-view

[Sysname] bgp 100

[Sysname-bgp-default] address-family ipv6 sr-policy

[Sysname-bgp-default-srpolicy-ipv6] router-id filter

sbfd

Use sbfd to configure SBFD for an SRv6 TE policy.

Use undo sbfd to restore the default.

Syntax

sbfd { disable | enable [ remote remote-id ] [ template template-name ] [ backup-template backup-template-name ] [ oam-sid sid ] }

undo sbfd

Default

SBFD is disabled for an SRv6 TE policy. An SRv6 TE policy uses the SBFD configuration in SRv6 TE view.

Views

SRv6 TE policy view

Predefined user roles

network-admin

Parameters

disable: Disables SBFD for the SRv6 TE policy.

enable: Enables SBFD for the SRv6 TE policy.

remote remote-id: Specifies the remote discriminator of the SBFD session, in the range of 1 to 4294967295. If you do not specify this option, the configuration in SRv6 TE view applies.

backup-template backup-template-name: Specifies as SBFD session parameter template for the backup SID list. The backup-template-name argument indicates the template name, a case-sensitive string of 1 to 63 characters. If you do not specify this option, the backup template specified in SRv6 TE view applies.

oam-sid sid: Adds an OAM SID to SBFD packets to identify the destination node. The sid argument represents the SRv6 SID of the endpoint destination node. If you do not specify this option, no OAM SID will be added to BFD packets. As a best practice, set the OAM SID to the End SID of the destination node.

Usage guidelines

You can configure SBFD for all SRv6 TE policies globally in SRv6 TE view or for a specific SRv6 TE policy in SRv6 TE policy view. The policy-specific configuration takes precedence over the global configuration. An SRv6 TE policy uses the global configuration only when it has no policy-specific configuration.

The remote discriminator specified in this command must be the same as that specified in the sbfd local-discriminator command on the reflector. Otherwise, the reflector will not send responses to the initiator.

The device supports the echo packet mode BFD and the SBFD for an SRv6 TE policy. If both modes are configured for the same SRv6 TE policy, the SBFD takes effect.

Examples

# Enable SBFD for SRv6 TE policy 1.

<Sysname> system-view

[Sysname] segment-routing ipv6

[Sysname-segment-routing-ipv6] traffic-engineering

[Sysname-srv6-te] policy 1

[Sysname-srv6-te-policy-1] sbfd enable

Related commands

display segment-routing ipv6 te sbfd

sbfd local-discriminator (High Availability Command Reference/BFD)

srv6-policy sbfd

segment-list

Use segment-list to create a SID list and enter its view, or enter the view of an existing SID list.

Use undo segment-list to delete a SID list and all the configuration in the SID list.

Syntax

segment-list segment-list-name

undo segment-list segment-list-name

Default

No SID lists exist.

Views

SRv6 TE view

Predefined user roles

network-admin

Parameters

segment-list-name: Specifies the SID list name, a case-sensitive string of 1 to 128 characters.

Examples

# Create a SID list named abc and enter its view.

<Sysname> system-view

[Sysname] segment-routing ipv6

[Sysname-segment-routing-ipv6] traffic-engineering

[Sysname-srv6-te] segment-list abc

[Sysname-srv6-te-sl-abc]

service-class

Use service-class to set a service class value for an SRv6 TE policy.

Use undo service-class to restore the default.

Syntax

service-class service-class-value

undo service-class

Default

No service class value is set for an SRv6 TE policy.

Views

SRv6 TE policy view

Predefined user roles

network-admin

Parameters

service-class-value: Specifies a service class value in the range of 0 to 127. The smaller the service class value, the lower the SRv6 TE policy priority. An SRv6 TE policy that is not assigned a service class value has the lowest priority.

Usage guidelines

The device compares the service class value of the traffic with the service class values of SRv6 TE policies and forwards the traffic to a matching tunnel. The device uses the following rules to select an SRv6 TE policy to forward the traffic:

· If the traffic matches only one SRv6 TE policy, the device uses this SRv6 TE policy.

· If the traffic matches multiple SRv6 TE policies, the device selects an SRv6 TE policy based on the flow forwarding mode:

¡ If there is only one flow and flow-based forwarding is used, the device randomly selects a matching SRv6 TE policy for packets of the flow.

¡ If there are multiple flows or if there is one flow but packet-based forwarding is used, the device uses all matching SRv6 TE policies to load share the packets.

For more information about the flow identification and load sharing mode, see the ip load-sharing mode command.

· If the traffic does not match any SRv6 TE policy, the device randomly selects an SRv6 TE policy from all SRv6 TE policies with the smallest service class value.

To set a service class value for traffic, use the remark service-class command in traffic behavior view.

Examples

# Set the service class value to 5 for SRv6 TE policy.

<Sysname> system-view

[Sysname] segment-routing ipv6

[Sysname-segment-routing-ipv6] traffic-engineering

[Sysname-srv6-te] policy 1

[Sysname-srv6-te-policy-1] service-class 5

Related commands

ip load-sharing mode (Layer 3—IP Services Command Reference)

remark service-class (ACL and QoS Command Reference)

shutdown

Use shutdown to shut down an SRv6 TE policy.

Use undo shutdown to bring up an SRv6 TE policy.

Syntax

shutdown

undo shutdown

Default

An SRv6 TE policy is not administratively shut down.

Views

SRv6 TE policy view

Predefined user roles

network-admin

Usage guidelines

If multiple SRv6 TE policies exist on the device, you can shut down unnecessary SRv6 TE policies to prevent them from affecting traffic forwarding.

Examples

# Shut down SRv6 TE policy 1.

<Sysname> system-view

[Sysname] segment-routing ipv6

[Sysname-segment-routing-ipv6] traffic-engineering

[Sysname-srv6-te] policy 1

[Sysname-srv6-te-policy-1] shutdown

sr-policy steering

Use sr-policy steering to configure the traffic steering mode for SRv6 TE policies.

Use undo sr-policy steering to restore the default.

Syntax

sr-policy steering { disable | policy-based }

undo sr-policy steering

Default

The device steering data packets to SRv6 TE policies based on colors of the packets.

Views

BGP instance view

Predefined user roles

network-admin

Parameters

disable: Disables color-based traffic steering to an SRv6 TE policy.

policy-based: Steers traffic to an SRv6 TE policy based on the bound policy, color, and load sharing tunnel policy in a descending order of priority.

Usage guidelines

The following traffic steering modes are available for SRv6 TE policies:

· Based on color—The device searches for an SRv6 TE policy that has the same color and endpoint address as the color and nexthop address of a BGP route. If a matching SRv6 TE policy exists, the device recurses the BGP route to that SRv6 TE policy. Then, when the device receives packets that match the BGP route, it forwards the packets through the SRv6 TE policy.

· Based on tunnel policy—On an IPv6 L3VPN over SRv6 network or EVPN L3VPN over SRv6 network, deploy a tunnel policy that uses an SRv6 TE policy. In this way, the SRv6 TE policy will be used as the public tunnel to carry the packets of the VPN. For more information about the tunnel policy configuration, see MPLS Configuration Guide.

This command does not take effect on L2VPN networks.

Examples

# Configure the SRv6-TE traffic steering mode as tunnel policy.

<Sysname> system-view

[Sysname] bgp 100

[Sysname-bgp-default] sr-policy steering policy-based

srv6-policy autoroute enable

Use srv6-policy autoroute enable to enable automatic route advertisement for SRv6 TE policies.

Use undo srv6-policy autoroute enable to disable automatic route advertisement for SRv6 TE policies.

Syntax

srv6-policy autoroute enable [ level-1 | level-2 ]

undo srv6-policy autoroute enable

Default

Automatic route advertisement for SRv6 TE policies is disabled.

Views

IS-IS IPv6 address family view

Predefined user roles

network-admin

Parameters

level-1: Enables automatic route advertisement for Level-1 IS-IS SRv6 TE policies.

level-2: Enables automatic route advertisement for Level-2 IS-IS SRv6 TE policies.

Usage guidelines

This command advertises SRv6 TE policies to IGP (IPv6 IS-IS) for route computation.

If you do not specify the level-1 or level-2 keyword in IS-IS IPv6 address family view, this command enables automatic route advertisement for all levels of IS-IS SRv6 TE policies.

For this command to take effect on an SRv6 TE policy, you must also execute the autoroute enable command in the view of the SRv6 TE policy.

Examples

# Enable automatic route advertisement for SRv6 TE policies of IS-IS process 1.

<Sysname> system-view

[Sysname] isis 1

[Sysname-isis-1] address-family ipv6

[Sysname-isis-1-ipv6] srv6-policy autoroute enable

Related commands

autoroute enable

srv6-policy backup hot-standby enable

Use srv6-policy backup hot-standby enable to enable hot standby for all SRv6 TE policies.

Use undo srv6-policy backup hot-standby enable to disable hot standby for all SRv6 TE policies.

Syntax

srv6-policy backup hot-standby enable

undo srv6-policy backup hot-standby enable

Default

Hot standby is disabled for all SRv6 TE policies.

Views

SRv6 TE view

Predefined user roles

network-admin

Usage guidelines

Examples

# Enable hot standby for all SRv6 TE policies.

<Sysname> system-view

[Sysname] segment-routing ipv6

[Sysname-segment-routing-ipv6] traffic-engineering

[Sysname-srv6-te] srv6-policy backup hot-standby enable

Related commands

backup hot-standby

srv6-policy bfd echo

Use srv6-policy bfd echo to enable the echo packet mode BFD for all SRv6 TE policies.

Use undo srv6-policy bfd echo to disable the echo packet mode BFD for all SRv6 TE policies.

Syntax

srv6-policy bfd echo source-ipv6 ipv6-address [ template template-name ] [ backup-template backup-template-name ]

undo srv6-policy bfd echo

Default

The echo packet mode BFD is disabled for all SRv6 TE policies.

Views

SRv6 TE view

Predefined user roles

network-admin

Parameters

source-ipv6 ipv6-address: Specifies the source IPv6 address of the BFD session.

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

Usage guidelines

The device supports the echo packet mode BFD and the SBFD for an SRv6 TE policy. If both modes are configured for the same SRv6 TE policy, the SBFD takes effect.

Examples

# Enable the echo packet mode BFD for all SRv6 TE policies, and specify the source IPv6 address of the BFD session as 11::11.

<Sysname> system-view

[Sysname] segment-routing ipv6

[Sysname-segment-routing-ipv6] traffic-engineering

[Sysname-srv6-te] srv6-policy bfd echo source-ipv6 11::11

Related commands

bfd echo

display segment-routing ipv6 te bfd

srv6-policy encapsulation-mode

Use srv6-policy encapsulation-mode to enable the reduced encapsulation mode for all SRv6 TE policies globally.

Use undo srv6-policy encapsulation-mode to restore the default.

Syntax

srv6-policy encapsulation-mode encaps reduced

undo srv6-policy encapsulation-mode encaps reduced

srv6-policy encapsulation-mode insert

undo srv6-policy encapsulation-mode insert

srv6-policy encapsulation-mode insert reduced

undo srv6-policy encapsulation-mode insert reduced

Default

An SRv6 TE policy uses the normal encapsulation (Encaps) mode.

Views

SRv6 TE view

Predefined user roles

network-admin

Parameters

encaps reduced: Specifies the encapsulation mode as reduced encapsulation mode.

insert: Specifies the encapsulation mode as insertion mode.

insert reduced: Specifies the encapsulation mode as reduced insertion mode.

Usage guidelines

· Encaps—Normal encapsulation mode. It adds a new IPv6 header and an SRH to the original packets. All SIDs in the SID list of the SRv6 TE policy are encapsulated in the SRH.

· Insert—Insertion mode. It inserts an SRH after the original IPv6 header. All SIDs in the SID list of the SRv6 TE policy are encapsulated in the SRH.

The normal encapsulation modes are exclusive with the insertion modes. If you configure a normal encapsulation mode and an insertion mode alternately, the most recent configuration takes effect.

If you configure the Insert or Insert.Red mode for an SRv6 TE policy, it uses the Encaps mode to encapsulate received IPv4 packets.

If you execute both the srv6-policy encapsulation-mode encaps reduced command and the srv6-policy encapsulation-mode encaps include local-end.x command, the srv6-policy encapsulation-mode encaps include local-end.x command takes effect.

If you execute both the srv6-policy encapsulation-mode insert reduced command and the srv6-policy encapsulation-mode insert include local-end.x command, the srv6-policy encapsulation-mode insert include local-end.x command takes effect.

Examples

# Configure the Encaps.Red mode for all SRv6 TE policies globally.

<Sysname> system-view

[Sysname] segment-routing ipv6

[Sysname-segment-routing-ipv6] traffic-engineering

[Sysname-srv6-te] srv6-policy encapsulation-mode encaps reduced

Related commands

encapsulation source-address

encapsulation-mode

srv6-policy encapsulation-mode encaps include local-end.x

Use srv6-policy encapsulation-mode encaps include local-end.x to configure local End.X SID encapsulation for all SRv6 TE policies using a normal encapsulation mode.

Use undo srv6-policy encapsulation-mode encaps include local-end.x to restore the default.

Syntax

srv6-policy encapsulation-mode encaps include local-end.x

undo srv6-policy encapsulation-mode encaps include local-end.x

Default

The device does not encapsulate the local End.X SID into the SRH of the packets forwarded by an SRv6 TE policy using a normal encapsulation mode.

Views

SRv6 TE view

Predefined user roles

network-admin

Usage guidelines

If the traffic steering mode is BSID and the SRv6 SID of the ingress node is an End.X SID, the device does not encapsulate the End.X SID into the SRH by default.

To obtain complete SRv6 forwarding path information from the SRH of packets, use this command to configure the device to encapsulate the local End.X SID into the SRH.

If you execute the srv6-policy encapsulation-mode encaps include local-end.x command and the srv6-policy encapsulation-mode insert include local-end.x command, the most recent configuration takes effect.

Examples

# Configure the device to include the local End.X SID in the SRH of the packets forwarded by SRv6 TE policies using a normal encapsulation mode.

<Sysname> system-view

[Sysname] segment-routing ipv6

[Sysname-segment-routing-ipv6] traffic-engineering

[Sysname-srv6-te] srv6-policy encapsulation-mode encaps include local-end.x

Related commands

encapsulation-mode encaps include local-end.x

srv6-policy encapsulation-mode insert include local-end.x

Use srv6-policy encapsulation-mode insert include local-end.x to configure local End.X SID encapsulation for all SRv6 TE policies with an insertion encapsulation mode.

Use undo srv6-policy encapsulation-mode insert include local-end.x to restore the default.

Syntax

srv6-policy encapsulation-mode insert include local-end.x

undo srv6-policy encapsulation-mode insert include local-end.x

Default

The device does not encapsulate the local End.X SID into the SRH of the packets forwarded by an SRv6 TE policy with an insertion encapsulation mode.

Views

SRv6 TE view

Predefined user roles

network-admin

Usage guidelines

If the traffic steering mode is BSID and the SRv6 SID of the ingress node is an End.X SID, the device does not encapsulate the End.X SID into the SRH by default.

To obtain complete SRv6 forwarding path information from the SRH of packets, use this command to configure the device to encapsulate the local End.X SID into the SRH.

If you execute the srv6-policy encapsulation-mode encaps include local-end.x command and the srv6-policy encapsulation-mode insert include local-end.x command multiple times, the most recent configuration takes effect.

Examples

# Enable the device to include the local End.X SID in the SRH of the packets forwarded by SRv6 TE policies with an insertion encapsulation mode.

<Sysname> system-view

[Sysname] segment-routing ipv6

[Sysname-segment-routing-ipv6] traffic-engineering

[Sysname-srv6-te] srv6-policy encapsulation-mode insert include local-end.x

Related commands

encapsulation-mode insert include local-end.x

srv6-policy forwarding statistics enable

Use srv6-policy forwarding statistics enable to enable traffic forwarding statistics for all SRv6 TE policies.

Use undo srv6-policy forwarding statistics enable to disable traffic forwarding statistics for all SRv6 TE policies.

Syntax

srv6-policy forwarding statistics [ service-class ]enable

undo srv6-policy forwarding statistics enable

Default

Traffic forwarding statistics is disabled for all SRv6 TE policies.

Views

SRv6 TE view

Predefined user roles

network-admin

Parameters

service-class: Enables the SRv6 TE policy forwarding statistics by service class. This feature collects statistics on the total traffic as well as the traffic of each service class that are forwarded by SRv6 TE policies. If you do not specify this keyword, the device only collects statistics on the total traffic forwarded by SRv6 TE policies.

The following compatibility matrixes show the support of hardware platforms for the service-class keyword:

Hardware	Parameter compatibility
MSR610	No
MSR810, MSR810-W, MSR810-W-DB, MSR810-LM, MSR810-W-LM, MSR810-10-PoE, MSR810-LM-HK, MSR810-W-LM-HK, MSR810-LM-CNDE-SJK, MSR810-CNDE-SJK, MSR810-EI, MSR810-LM-EA, MSR810-LM-EI	Yes
MSR810-LMS, MSR810-LUS	No
MSR810-SI, MSR810-LM-SI	No
MSR810-LMS-EA, MSR810-LME	Yes
MSR1004S-5G, MSR1004S-5G-CN	Yes
MSR1104S-W, MSR1104S-W-CAT6, MSR1104S-5G-CN, MSR1104S-W-5G-CN	Yes
MSR2600-6-X1, MSR2600-15-X1, MSR2600-15-X1-T	Yes
MSR2600-10-X1	Yes
MSR 2630	Yes
MSR3600-28, MSR3600-51	Yes
MSR3600-28-SI, MSR3600-51-SI	No
MSR3600-28-X1, MSR3600-28-X1-DP, MSR3600-51-X1, MSR3600-51-X1-DP	Yes
MSR3600-28-G-DP, MSR3600-51-G-DP	Yes
MSR3610-I-DP, MSR3610-IE-DP, MSR3610-IE-ES, MSR3610-IE-EAD, MSR-EAD-AK770, MSR3610-I-IG, MSR3610-IE-IG	Yes
MSR3610-X1, MSR3610-X1-DP, MSR3610-X1-DC, MSR3610-X1-DP-DC, MSR3620-X1, MSR3640-X1	Yes
MSR3610, MSR3620, MSR3620-DP, MSR3640, MSR3660	Yes
MSR3610-G, MSR3620-G	Yes
MSR3640-G	Yes
MSR3640-X1-HI	Yes

Hardware	Parameter compatibility
MSR810-W-WiNet, MSR810-LM-WiNet	Yes
MSR830-4LM-WiNet	Yes
MSR830-5BEI-WiNet, MSR830-6EI-WiNet, MSR830-10BEI-WiNet	Yes
MSR830-6BHI-WiNet, MSR830-10BHI-WiNet	Yes
MSR2600-6-WiNet	Yes
MSR2600-10-X1-WiNet	Yes
MSR2630-WiNet	Yes
MSR3600-28-WiNet	Yes
MSR3610-X1-WiNet	Yes
MSR3610-WiNet, MSR3620-10-WiNet, MSR3620-DP-WiNet, MSR3620-WiNet, MSR3660-WiNet	Yes

Hardware	Parameter compatibility
MSR860-6EI-XS	Yes
MSR860-6HI-XS	Yes
MSR2630-XS	Yes
MSR3600-28-XS	Yes
MSR3610-XS	Yes
MSR3620-XS	Yes
MSR3610-I-XS	Yes
MSR3610-IE-XS	Yes
MSR3620-X1-XS	Yes
MSR3640-XS	Yes
MSR3660-XS	Yes

Hardware	Parameter compatibility
MSR810-LM-GL	Yes
MSR810-W-LM-GL	Yes
MSR830-6EI-GL	Yes
MSR830-10EI-GL	Yes
MSR830-6HI-GL	Yes
MSR830-10HI-GL	Yes
MSR1004S-5G-GL	Yes
MSR2600-6-X1-GL	Yes
MSR3600-28-SI-GL	No

Usage guidelines

If you execute this command multiple times, the most recent configuration takes effect.

Examples

# Enable traffic forwarding statistics for all SRv6 TE policies.

<Sysname> system-view

[Sysname] segment-routing ipv6

[Sysname-segment-routing-ipv6] traffic-engineering

[Sysname-srv6-te] srv6-policy forwarding statistics enable

Related commands

display segment-routing ipv6 te forwarding

forwarding statistic

reset segment-routing ipv6 te forwarding statistics

srv6-policy forwarding statistics interval

Use srv6-policy forwarding statistics interval to configure the traffic forwarding statistics interval for all SRv6 TE policies.

Use undo srv6-policy forwarding statistics interval to restore the default.

Syntax

srv6-policy forwarding statistics interval interval

undo srv6-policy forwarding statistics interval

Default

The SRv6 TE policies forwarding statistics interval is 30 seconds.

Views

SRv6 TE view

Predefined user roles

network-admin

Parameters

interval: Specifies the SRv6 TE policy traffic forwarding statistics interval in the range of 5 to 65535, in seconds.

Predefined user roles

This command takes effect only all SRv6 TE policies.

Examples

# Set the SRv6 TE policy traffic forwarding statistics interval to 90 seconds.

<Sysname> system-view

[Sysname] segment-routing ipv6

[Sysname-segment-routing-ipv6] traffic-engineering

[Sysname-srv6-te] srv6-policy forwarding statistics interval 90

Related commands

display segment-routing ipv6 te forwarding

forwarding statistic

reset segment-routing ipv6 te forwarding statistics

srv6-policy forwarding statistics enable

srv6-policy locator

Use srv6-policy locator to specify a locator for SRv6 TE.

Use undo srv6-policy locator to cancel the locator configuration.

Syntax

srv6-policy locator locator-name

undo srv6-policy locator

Default

No locator is specified for SRv6 TE.

Views

SRv6 TE view

Predefined user roles

network-admin

Parameters

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

Usage guidelines

The locator specified in SRv6 TE view restricts the BSID range. Only BSIDs within the range of the locator can take effect.

You cannot change the locator for SRv6 TE by repeatedly executing this command. To change the locator, first execute the undo srv6-policy locator command to remove the specified locator and then execute the srv6-policy locator command to specify a new locator.

Examples

# Specify locator test1 in SRv6 TE view.

<Sysname> system-view

[Sysname] segment-routing ipv6

[Sysname-segment-routing-ipv6] traffic-engineering

[Sysname-srv6-te] srv6-policy locator test1

srv6-policy sbfd

Use srv6-policy sbfd to enable SBFD for all SRv6 TE policies and configure the SBFD session parameters.

Use undo srv6-policy sbfd to disable SBFD for all SRv6 TE policies.

Syntax

srv6-policy sbfd remote remote-id [ template template-name ] [ backup-template backup-template-name ]

undo srv6-policy sbfd

Default

SBFD for all SRv6 TE policies is disabled.

Views

SRv6 TE view

Predefined user roles

network-admin

Parameters

remote remote-id: Specifies the remote discriminator of the SBFD session, in the range of 1 to 4294967295.

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

backup-template backup-template-name: Specifies an SBFD session parameter template for the backup SID list. The backup-template-name argument indicates the template name, a case-sensitive string of 1 to 63 characters. If you do not specify this option, SBFD uses the multihop BFD session settings configured in system view.

Predefined user roles

The device supports the echo packet mode BFD and the SBFD for an SRv6 TE policy. If both modes are configured for the same SRv6 TE policy, the SBFD takes effect.

Examples

# Enable SBFD for all SRv6 TE policies, and specify the SBFD session remote discriminator as 1000001.

<Sysname> system-view

[Sysname] segment-routing ipv6

[Sysname-segment-routing-ipv6] traffic-engineering

[Sysname-srv6-te] srv6-policy sbfd remote 1000001

Related commands

display segment-routing ipv6 te sbfd

sbfd

sbfd local-discriminator (High Availability Command Reference)

srv6-policy switch-delay delete-delay

Use srv6-policy switch-delay delete-delay to configure the switchover delay time and deletion delay time for the SRv6 TE policy forwarding path.

Use undo srv6-policy switch-delay to restore the default.

Syntax

srv6-policy switch-delay switch-delay-time delete-delay delete-delay-time

undo srv6-policy switch-delay

Default

The switchover delay time and deletion delay time for the SRv6 TE policy forwarding path is 5000 milliseconds and 20000 milliseconds, respectively.

Views

SRv6 TE view

Predefined user roles

network-admin

Parameters

switch-delay-time: Sets the forwarding path switchover delay time in the range of 0 to 600000 milliseconds.

delete-delay-time: Sets the forwarding path deletion delay time in the range of 0 to 600000 milliseconds.

Predefined user roles

The switchover delay and deletion delay mechanism is used to avoid traffic forwarding interruption during a forwarding path switchover.

When updating an SRv6 TE policy forwarding path, the device first establishes the new forwarding path before it deletes the old one. During the new path setup process, the device uses the old path to forward traffic until the switchover delay timer expires. When the switchover delay timer expires, the device switches traffic to the new path. The old path is deleted when the deletion delay timer expires.

Examples

# Set the SRv6 TE policy forwarding path switchover delay time to 8000 milliseconds and the deletion delay time to 15000 milliseconds.

<Sysname> system-view

[Sysname] segment-routing ipv6

[Sysname-segment-routing-ipv6] traffic-engineering

[Sysname-srv6-te] srv6-policy switch-delay 8000 delete-delay 15000

traffic-engineering

Use traffic-engineering to create and enter the SRv6 TE view, or enter the existing SR TE view.

Use undo traffic-engineering to delete the SRv6 TE view and all the configuration in the view.

Syntax

traffic-engineering

undo traffic-engineering

Default

The SRv6 TE view does not exist.

Views

SRv6 view

Predefined user roles

network-admin

Examples

# Create and enter the SRv6 TE view.

<Sysname> system-view

[Sysname] segment-routing ipv6

[Sysname-segment-routing-ipv6] traffic-engineering

[Sysname-srv6-te]

ttl-mode

Use ttl-mode to configure the TTL processing mode of SRv6 TE policies.

Use undo ttl-mode to restore the default.

Syntax

ttl-mode { pipe | uniform }

undo ttl-mode

Default

The TTL processing mode of SRv6 TE policies is pipe.

Views

SRv6 view

Predefined user roles

network-admin

Parameters

pipe: Specifies the pipe TTL processing mode.

uniform: Specifies the uniform TTL processing mode.

Predefined user roles

An SRv6 TE policy used as a public tunnel supports the following TTL processing modes:

· Uniform—When the ingress node adds a new IPv6 header to an IP packet, it copies the TTL value of the original IP packet to the Hop Limit field of the new IPv6 header. Each node on the SRv6 TE policy forwarding path decreases the Hop Limit value in the new IPv6 header by 1. The node that de-encapsulates the packet copies the remaining Hop Limit value back to the original IP packet when it removes the new IPv6 header. The TTL value can reflect how many hops the packet has traversed in the public network. The tracert facility can show the real path along which the packet has traveled.

· Pipe—When the ingress node adds a new IPv6 header to an IP packet, it does not copy the TTL value of the original IP packet to the Hop Limit field of the new IPv6 header. It sets the Hop Limit value in the new IPv6 header to 255. Each node on the SRv6 TE policy forwarding path decreases the Hop Limit value in the new IPv6 header by 1. The node that de-encapsulates the packet does not change the IPv6 Hop Limit value according to the remaining Hop Limit value in the new IPv6 header. Therefore, the public network nodes are invisible to user networks, and the tracert facility cannot show the real path in the public network.

Examples

# Configure the TTL processing mode of SRv6 TE policies to uniform.

<Sysname> system-view

[Sysname] segment-routing ipv6

[Sysname-segment-routing-ipv6] ttl-mode uniform

validation-check enable

Use validation-check enable to enable validity check for BGP IPv6 SR policy routes.

Use undo validation-check enable to disable validity check for BGP IPv6 SR policy routes.

Syntax

validation-check enable

undo validation-check enable

Default

Validity check for BGP IPv6 SR policy routes is disabled. The device does not check the validity of the BGP IPv6 SR policy routes received from peers or peer groups.

Views

BGP IPv6 SR policy address family view

Predefined user roles

network-admin

Usage guidelines

After validity check is enabled for BGP IPv6 SR policy routes, the device determines that a BGP IPv6 SR policy route is invalid and will not select the route if the route does not contain the IPv4 address format RT extended community attribute or the NO_ADVERTISE community attribute.

You can configure this feature on the RR in networks where the controller and the RR establish a BGP peer relationship and the RR establishes BGP peer relationships with the source nodes of multiple SRv6 TE policies.

The RR checks whether the BGP IPv6 SR policy routes issued by the controller carry the IPv4 address format RT attribute or the NO_ADVERTISE attribute. If yes, the RR accepts the routes and reflects the routes that do not carry the NO_ADVERTISE attribute to the source nodes of the SRv6 TE policies.

On the source nodes, you can use the router-id filter command to enable BGP IPv6 SR policy route filtering by router ID. After a source node receives a BGP IPv6 SR policy route, it compares the local router ID with the IPv4 address in the RT attribute of the route. If they are the same, the source node accepts the route. If they are different, the source node drops the route.

Examples

# Enable validity check for BGP IPv6 SR policy routes.

<Sysname> system-view

[Sysname] bgp 100

[Sysname-bgp-default] address ipv6 sr-policy

[Sysname-bgp-default-srpolicy-ipv6] validation-check enable

23-Segment Routing Command References

SRv6 TE policy commands

address-family ipv6 sr-policy

default-color (public instance IPv4/IPv6 address family view)

default-color (VPN instance IPv4/IPv6 address family view)

display bgp routing-table ipv6 sr-policy

display segment-routing ipv6 te segment-list

Cloud & AI

InterConnect

Intelligent Terminal Products

Product Support Services

Technical Service Solutions

Resource Center

Policy

Online Help

Become a Partner

Partner Resources

Partner Business Management

Company Information

News & Events

Contact Us