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

affinity (SRv6 TE policy constraints view)

Use affinity to create and enter the affinity attribute view, or enter the existing affinity attribute view.

Use undo affinity to delete the affinity attribute view and all the configurations in the view.

Syntax

affinity

undo affinity

Default

The affinity attribute is not created for an SRv6 TE policy.

Views

Constraints view

Predefined user roles

network-admin

Examples

# Enter affinity attribute 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 200

[Sysname-srv6-te-policy-a1-path-pref-200] constraints

[Sysname-srv6-te-policy-a1-path-pref-200-const] affinity

[Sysname-srv6-te-policy-a1-path-pref-200-const-aff]

affinity-map

Use affinity-map to create the constraints mapping and enter its view, or enter the view of the existing constraints mapping.

Use undo affinity-map to delete the constraints mapping view and all the configurations in the view.

Syntax

affinity-map

undo affinity-map

Default

No constraints mapping exists.

Views

SRv6 TE view

Predefined user roles

network-admin

Examples

# Create the constraints mapping and enter its view

<Sysname> system-view

[Sysname] segment-routing ipv6

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

[Sysname-srv6-te] affinity-map

[Sysname-srv6-te-affinity-map]

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 fail, 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 } [ preferred ]

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.

preferred: Increases the priority of packet encapsulation type in BGP route selection.

Usage guidelines

For more information about the priority order of the configuration in this command in 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 ] [ encaps | insert ] [ reverse-path reverse-binding-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, use the End.SID of the destination node as the OAM SID.

encaps: Uses the normal encapsulation mode to encapsulate BFD packets.

insert: Uses the insertion mode to encapsulate BFD packets.

The following compatibility matrix shows the support of hardware platforms for the encaps and insert keywords:

Model	MPU	Keyword compatibility
RA5300, RA5300-X, RA5300-AC	RSU-400, RSU-400S	Yes
RA5300, RA5300-X, RA5300-AC	RSU-400-G	No

reverse-path: Specifies the reverse path for BFD packets. If you do not specify this keyword, the device forwards BFD packets back to the source node based on the IP forwarding path.

reverse-binding-sid: Uses the SID list associated with the reverse BSID as the reverse path for BFD packets.

Usage guidelines

To use echo BFD to detect an SRv6 TE policy, the device needs to encapsulate the SID list of the SRv6 TE policy for the BFD 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.

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

If you do not specify the encaps or insert keyword, the encapsulation mode configured by the bfd srv6-encapsulation-mode encap command applies.

By default, the BFD return packets used for SRv6 TE policy connectivity detection are forwarded based on the IP forwarding path. If a transit node fails, all the return packets will be discarded, and the BFD sessions will go down as a result. If multiple SRv6 TE policies exist between the source and endpoint nodes, BFD will mistakenly determine that the SID lists of all SRv6 TE policies are faulty. To resolve this issue, you can enable BFD return packets to be forwarded based on the specified SID list to implement BFD forward and reverse path consistency.

You can implement BFD forward and reverse path consistency by specifying a reverse BSID. After the reverse-path reverse-binding-sid parameters are configured, the source node will insert an SRH header into a BFD packet and encapsulate the reverse BSID to the SL=1 position in the SRH header. You can specify the reverse BSID by using the explicit segment-list or reverse-binding-sid command. Upon receiving the BFD packet, the endpoint node retrieves the reverse BSID. If the reverse BSID matches the local BSID of an SRv6 TE policy on the endpoint node, the endpoint node inserts a new SRH into the BFD packet and forwards the packet along the SID list of that SRv6 TE policy. (To specify a local BSID for an SRv6 TE policy, use the local-binding-sid command.)

After the reverse-path reverse-binding-sid keywords are specified, BFD packets can be encapsulated only in Insert mode. The encaps keyword does not take effect.

To encapsulate the BFD packets for SRv6 TE policy connectivity detection, the device uses the encapsulation mode configured for BFD packets. The encapsulation mode configured for the SRv6 TE policy in SRv6 TE view or SRv6 TE policy view does not take effect on BFD packets.

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

bfd srv6-encapsulation-mode encap

display segment-routing ipv6 te bfd

srv6-policy bfd echo

bfd srv6-encapsulation-mode encap

Use bfd srv6-encapsulation-mode encap to specify the Encap mode for the BFD or SBFD packets used for SRv6 forwarding paths connectivity detection.

Use undo bfd srv6-encapsulation-mode encap to restore the default.

Syntax

bfd srv6-encapsulation-mode encap

undo bfd srv6-encapsulation-mode encap

The following compatibility matrix shows the support of hardware platforms for this command:

Model	MPU	Command compatibility
RA5300, RA5300-X, RA5300-AC	RSU-400, RSU-400S	Yes
RA5300, RA5300-X, RA5300-AC	RSU-400-G	No

Default

The device uses the Insert mode to encapsulate the BFD or SBFD packets for SRv6 forwarding paths connectivity detection.

Views

System view

Predefined user roles

network-admin

Usage guidelines

To use BFD or SBFD to detect an SRv6 TE policy, the device needs to encapsulate the SID list of the SRv6 TE policy for the BFD or SBFD packets. The following encapsulation modes are available:

· 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. If the length of the SID list is 0, the SRH is not inserted.

· 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. If the length of the SID list is 0, the SRH is not inserted.

The encapsulation mode configured using this command cannot take effect immediately when a BFD or SBFD session has been established. You must first execute the bfd echo or sbfd command with the disable keyword specified to disable BFD or SBFD for the SRv6 TE policy and then enable BFD or SBFD for the SRv6 TE policy.

Examples

# Configure the device to use the Encap mode to encapsulate the BFD or SBFD packets for SRv6 forwarding paths connectivity detection.

<Sysname> system-view

[Sysname] bfd srv6-encapsulation-mode encap

Related commands

bfd echo

sbfd

binding-sid (SRv6 TE policy view)

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 static 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 be configured with the same pair of color and 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 dot1p

Use color match dot1p to create color-to-802.1p mappings for an SRv6 TE policy group.

Use undo color match dot1p to delete color-to-802.1p mappings for an SRv6 TE policy group.

Syntax

color color-value match dot1p dot1p-value-list

undo color color-value match dot1p dot1p-value-list

color color-value match dot1p default

undo color color-value match dot1p [ default ]

Default

No color-to-802.1p 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.

dot1p-value-list: Specifies a space-separated list of up to four 802.1p value items. Each item specifies an 802.1p value in the range of 0 to 7 or a range of 802.1p values in the form of dot1p-value1 to dot1p-value2. The value for the dot1p-value2 argument must be greater than or equal to the value for the dot1p-value1 argument.

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

Usage guidelines

To use this command, you must first use the forward-type dot1p command.

Use this command to create color-to-802.1p mappings for 802.1p-based traffic steering.

You can map the color values of only valid SRv6 TE policies to 802.1p values. For an SRv6 TE policy group, an 802.1p value can be mapped to only one color value.

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

When the device receives a packet that does not match any color-to-802.1p mapping, the device uses the following procedure to forward the packet:

1. Uses the default SRv6 TE policy to forward the packet if the default SRv6 TE policy is valid.

2. Uses the SRv6 TE policy mapped to the smallest 802.1p value to forward the packet in case that the SRv6 TE policy is valid.

3. Performs an IPv6 routing table lookup to forward the packet if the packet does not meet any of the previous conditions.

Examples

# In SRv6 TE policy group 1, map 802.1p value 3 to color value 20, so that packets with a matching 802.1p 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 1

[Sysname-srv6-te-policy-group-1] forward-type dot1p

[Sysname-srv6-te-policy-group-1] color 20 match dot1p 3

Related commands

forward-type dot1p

color match dscp (DSCP forward type view)

Use color match dscp to create color-to-DSCP mappings for the SRv6 TE policy group ODN template.

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

Syntax

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

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

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 the SRv6 TE policy group ODN template.

Views

DSCP forward type 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.

Usage guidelines

About this feature

Typically, an SRv6 TE policy group created by an ODN template has multiple SRv6 TE policy tunnels with the same endpoint address but different color attribute values. After traffic is steered to the SRv6 TE policy group, the device matches the DSCP value of the traffic with the color-to-DSCP mappings configured by using this command. If a match is found, the device will forward the traffic through the SRv6 TE policy associated with the color attribute value in the matching mapping.

Operating mechanism

After a packet is steered to an SRv6 TE policy group, the device searches for a matching forwarding policy for the packet based on the DSCP value in the packet. If the device finds a matching forwarding policy by a match criterion and the forwarding policy is valid, it uses the forwarding policy to forward the packet. If no matching forwarding policy is found or the matching forwarding policy is invalid, the device proceeds to use the next match criterion to find a matching forwarding policy. The procedure to find a matching forwarding policy is as follows:

1. Matches the DSCP value in the packet with the mappings configured by using the color match dscp command for the address family of the packet. If a match is found, the device uses the matching SRv6 TE policy to forward the packet.

2. Uses the default SRv6 TE policy specified by using the color match dscp default command for the address family of the packet to forward the packet.

3. Uses the default SRv6 TE policy specified by using the color match dscp default command for the other address family to forward the packet.

4. The device identifies whether the SRv6 TE policy group is configured with color-to-DSCP mappings. If yes, the device searches for a mapping with the smallest DSCP value and a valid SRv6 TE policy. The device will use that SRv6 TE policy to forward the packet.

5. The device performs a routing table lookup to forward the packet if the packet does not meet any of the previous conditions.

Restrictions and guidelines

In an SRv6 TE policy group, you can configure DSCP-based traffic steering separately for the IPv4 address family and IPv6 address family. For a specific address family, a DSCP value can be mapped to only one SRv6 TE policy.

Only one default SRv6 TE policy can be specified for an address family in an SRv6 TE policy group.

Examples

# In an SRv6 TE policy group ODN template, map DSCP value 30 to color value 20 for IPv4 packets, so that IPv4 packets with DSCP value 30 are steered to the SRv6 TE policy with color value 20.

<Sysname> system-view

[Sysname] segment-routing ipv6

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

[Sysname-srv6-te] on-demand-group color 1

[Sysname-srv6-te-odn-group-1] forward-type dscp

[Sysname-srv6-te-odn-group-1-dscp] color 20 match dscp ipv4 30

color match dscp (SRv6 TE policy group view)

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.

default: Configures a default color-to-DSCP mapping. Packets that do not match any mappings are steered to the SRv6 TE policy associated with the color attribute value in the default mapping. This SRv6 TE policy is used as the default SRv6 TE policy for packets in the specified address family. If you do not specify this keyword for the undo color match dscp command, the command deletes all color-to-DSCP mappings for the current SRv6 TE policy group.

Usage guidelines

About this feature

Typically, an SRv6 TE policy group has multiple SRv6 TE policy tunnels with the same endpoint address but different color attribute values. After traffic is steered to the SRv6 TE policy group, the device matches the DSCP value of the traffic with the color-to-DSCP mappings configured by using this command. If a match is found, the device will forward the traffic through the SRv6 TE policy associated with the color attribute value in the matching mapping.

Operating mechanism

2. Uses the default SRv6 TE policy specified by using the color match dscp default command for the address family of the packet to forward the packet.

3. Uses the default SRv6 TE policy specified by using the color match dscp default command for the other address family to forward the packet.

5. The device performs a routing table lookup to forward the packet if the packet does not meet any of the previous conditions.

Restrictions and guidelines

Only one default SRv6 TE policy can be specified for an address family in an SRv6 TE policy group.

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

constraints

Use constraints to create and enter SRv6 TE policy constraints view, or enter the existing SRv6 TE policy constraints view.

Use undo constraints to delete the SRv6 TE policy constraints view and all configurations in the view.

Syntax

constraints

undo constraints

Default

No SRv6 TE policy constraints exist.

Views

SRv6 TE policy path preference view

Predefined user roles

network-admin

Usage guidelines

In constraints view, you can configure the affinity attribute and segment constraints for an SRv6 TE policy for flexible forwarding path control.

When both affinity attribute and segment constraints are configured in constraints view, segment constraints apply.

Examples

# Create SRv6 TE policy constraints and enter constraints 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 200

[Sysname-srv6-te-policy-a1-path-pref-200] constraints

[Sysname-srv6-te-policy-a1-path-pref-200-const]

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

delete-delay (SRv6 TE ODN policy group view)

Use delete-delay to configure the deletion delay time for SRv6 TE policy groups generated by an ODN template.

Use undo delete-delay to restore the default.

Syntax

delete-delay delay-time

undo delete-delay

Default

The deletion delay time for SRv6 TE policies generated by an ODN template is 180000 milliseconds.

Views

SRv6 TE ODN policy group view

Predefined user roles

network-admin

Parameters

delay-time: Specifies the deletion delay time, in milliseconds. The value range is 0 to 600000.

Usage guidelines

ODN automatically creates an SRv6 TE policy group based on the specified BGP route. The SRv6 TE policy group is deleted immediately when the BGP route is deleted. To avoid packet loss before the new forwarding path is computed, you can use this command to configure a proper deletion delay time for the SRv6 TE policy group.

Examples

# Set the deletion delay time to 300000 milliseconds for SRv6 TE policy groups generated by an ODN template.

<Sysname> system-view

[Sysname] segment-routing ipv6

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

[Sysname-srv6-te] on-demand-group color 1

[Sysname-srv6-te-odn-group-1] delete-delay 300000

description

Use description to configure the description of the SRv6 TE policy group ODN template.

Use undo description to restore the default.

Syntax

description text

undo description

Default

The description of the SRv6 TE policy group ODN template is not configured.

Views

SRv6 TE ODN policy group view

Predefined user roles

network-admin

Parameters

text: Specifies the description of the SRv6 TE policy group ODN template, a case-sensitive string of 1 to 242 characters.

Usage guidelines

To facilitate management, use this command to configure the description of the SRv6 TE policy group ODN template.

Examples

# Configure the description of the SRv6 TE policy group ODN template.

<Sysname> system-view

[Sysname] segment-routing ipv6

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

[Sysname-srv6-te] on-demand-group color 1

[Sysname-srv6-te-odn-group-1] description abc

display bgp routing-table ipv6 sr-policy

Use display bgp routing-table ipv6 sr-policy to display route information of a BGP SRv6 TE 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 [ as-path-acl { as-path-acl-number | as-path-acl-name } | as-path-regular-expression regular-expression ]

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

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

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

display bgp [ instance instance-name ] routing-table ipv6 sr-policy peer { ipv4-address | ipv6-address } { accepted-routes | not-accepted-routes }

display bgp [ instance instance-name ] routing-table ipv6 sr-policy time-range start-time end-time

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.

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 SRv6 policy route/prefix length.

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

as-path-acl as-path-acl-number: Specifies an AS path ACL by its number, in the range of 1 to 256.

as-path-acl as-path-acl-name: Specifies an AS path ACL by its name, a case-sensitive string of 1 to 51 characters. The AS path ACL name cannot contain only digits.

as-path-regular-expression regular-expression: Specifies an AS path regular expression, a case-sensitive string of 1 to 256 characters.

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

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

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

peer { ipv4-address | ipv6-address }: Specifies a peer by its IPv4 or 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.

accepted-routes: Displays information about the routes received from the specified peer and permitted by the specified policy.

not-accepted-routes: Displays information about the routes received from the specified peer and not permitted by the specified policy.

time-range min-time max-time: Displays information for routes that have persisted for a duration within the specified range since the last update. The min-time argument represents the minimum duration, and the max-time argument represents the maximum duration. The min-time and max-time arguments are in the format of <0-10000>d<0-23>h<0-59>m<0-59>s, where d represents days, h represents hours, m represents minutes, and s represents seconds, and <0-10000>, <0-23>, <0-59>, and <0-59> represent the value ranges for days, hours, minutes, and seconds, respectively. The duration specified by using the max-time argument must be longer than the duration specified by using the min-time argument.

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

# Display information for BGP IPv6 SR policy routes that have persisted for a duration within the specified range since the last update in BGP instance default.

<Sysname> display bgp routing-table ipv6 sr-policy time-range 1d1h1m1s 7d3h1m1s

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

Route age: 06d01h12m44s

Table 1 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.
Route age	Duration that the route has persisted since the last time it was updated. The duration is in the format of <0-10000>d<0-23>h<0-59>m<0-59>s, where d represents days, h represents hours, m represents minutes, and s represents seconds, and <0-10000>, <0-23>, <0-59>, and <0-59> represent the value ranges for days, hours, minutes, and seconds, respectively.

‌

# 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

SRv6 Binding SID:

Binding SID: 3::6

Flags: 0/I/B/0/0/0/0/0

Endpoint Behavior: 0x1B

LB Length: 64

LN Length: 16

Function Length: 16

Args Length: 8

Preference: 100

Network slice ID: 10

Path: 1

Weight: 1

SIDs: {2::2}

Table 2 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.
Output interface	Outgoing interface information, which is the SRv6 TE policy name of the forwarding tunnel.
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.
Originator	Peer that generated the route.
Cluster list	CLUSTER_LIST attribute of the route. This field is not displayed if the CLUSTER_LIST attribute is not available.
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 3.
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
SRv6 Binding SID	SRv6 Binding SID Sub-TLV information: · Binding SID—BSID value of the SRv6 TE policy candidate path. · Flags (S/I/B)—BSID flags. ¡ S—Specified-BSID-only flag. The current software version does not support this flag. If this flag is set, the system takes restrictive Specified-BSID-only behaviors on the candidate path. The system does not bind a BSID to the candidate path and determines that it is invalid if it has an unspecified BSID or if the specified BSID is not available when it becomes active. ¡ I—Invalid flag. When this flag is set, the device discards traffic that matches an invalid SRv6 TE policy. ¡ B—Behavior flag. When this flag is set in a packet, the packet carries an SRv6 SID endpoint behavior. ¡ 0—Reserved flag bits. · Endpoint Behavior—Endpoint behavior for BSID-based traffic steering. ¡ 0xE—End.B6.Encaps, that is, normal encapsulation mode. ¡ 0x1B—End.B6.Encaps.Red, that is, reduced mode of the normal encapsulation mode. ¡ 0xD—End.B6.Insert, that is, insertion encapsulation mode. ¡ 0x1A—End.B6.Insert.Red, that is, reduced insertion encapsulation mode. · LB Length—Common prefix length, in bits. · LN Length—Node ID length, in bits. · Function Length—Function length, in bits. · Argument Length—Argument length, in bits.
Network slice ID	Network slice instance ID associated with the candidate path of the SRv6 TE policy.
Path	ID of the candidate path.
Weight	Weight of the SID list.
SIDs	List of SIDs. The format is {sid-value, flags}, where sid-value is the SID value and flags represents the flags carried in the SID. At present, only the V flag is supported, which means to verify the SID's validity during the SRv6 TE policy path verification. A G-SID is displayed in the format of {sid-value, coc32, prefix-length, flags }, where sid-value is the SID value, prefix-length is the common prefix length, and flags represents the flags carried in the SID. At present, only the V flag is supported, which means to verify the SID's validity during the SRv6 TE policy path verification.

‌

Table 3 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 4 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 5 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 bfd

Color: 10

Endpoint: 4::4

Policy name: p1

State: Up

Forwarding index: 2149580801

Encapsulation mode: Encaps

Source IPv6 address: 1::1

State: Up

Timer: 37

VPN index: 1

Template name: abc

Reverse path type: None

Reverse BSID: -

Flush add time: 2022-12-22 17:01:48

Table 6 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	BFD session state of the SRv6 TE policy: · Up. · Down.
Forwarding index	Forwarding entry index for an SID list.
Encapsulation mode	Encapsulation mode for BFD packets: · Encaps—Normal encapsulation mode. · Insert—Insertion encapsulation mode. If the encapsulation mode for BFD packets is not configured, this field displays a hyphen (-).
Source IPv6 address	Source IPv6 address of the BFD session.
State	BFD session state of the SID list: · Up. · Down.
Timer	BFD session timer, in seconds.
VPN index	Index of the VPN instance.
Template name	Name of the echo mode BFD template.
Reverse path type	Reverse path type for BFD packets: · Reverse BSID—Uses the SID list associated with the reverse BSID as the reverse path for BFD packets. · None—The reverse path for BFD packets is not configured.
Reverse BSID	Reverse BSID of the BFD session.
Flush add time	The most recent time when the SRv6 TE policy flushed path information to BFD. BFD establishes a detection session based on the path information. If no BFD session is established, this field displays a hyphen (-).

‌

display segment-routing ipv6 te database

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

Syntax

display segment-routing ipv6 te database [ link | node | prefix | srv6-sid ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

link: Displays the link information reported by the IGP to the SRv6 TE policy database.

node: Displays the node information reported by the IGP to the SRv6 TE policy database.

prefix: Displays the prefix information reported by the IGP to the SRv6 TE policy database.

srv6-sid: Displays the SRv6 SID information reported by the IGP to the SRv6 TE policy database.

Usage guidelines

If you do not specify any parameters, this command displays all information reported by the IGP to the SRv6 TE policy database.

Examples

# Display link information reported by the IGP to the SRv6 TE policy database.

<Sysname> display segment-routing ipv6 te database link

Link-state information: Link, count: 3

Public instance, MT-ID: 2, IS-IS instance ID: 0, Link count: 3

IS-IS P2P:

Local node: System ID 0000.0000.0020.00, IS level: 1

Remote node: System ID 0000.0000.0019.00, IS level: 1

Topology ID: 2

Link source: ProcID 100, TLV type: MT-IS-reach, FragID: 0x0

TE local router ID: 2.2.2.2

TE remote router ID: 1.2.3.4

IPv6 remote router ID: 1::1

IGP metric: 10

SR/SRv6 link maximum SID depths:

MPLS MSD : 5

SRLG: 0

SRLG: 1

SRv6 End.X SID

SID : 200::1:0:0

Function type : End.X (no PSP, no USP)

Algorithm : 0

Weight : 0

Flags (B/S/P/C): 0/0/0/0

SRv6 End.X SID

SID : 200::1:0:2

Function type : End.X with PSP

Algorithm : 0

Weight : 0

Flags (B/S/P/C): 0/0/0/0

IS-IS P2P:

Local node: System ID 0000.0000.0019.00, IS level: 1

Remote node: System ID 0000.0000.0020.00, IS level: 1

IPv6 local address: 2001:1::2

IPv6 remote address: 2001:1::16

Topology ID: 2

Link source: ProcID 100, TLV type: MT-IS-reach, FragID: 0x0

TE local router ID: 1.2.3.4

TE remote router ID: 2.2.2.2

IPv6 local router ID: 1::1

TE administrative group: 0x10

TE maximum bandwidth (kbits/sec): 0

TE maximum reservable bandwidth (kbits/sec): 0

TE class 0 unreserved bandwidth (kbits/sec): 0

TE class 1 unreserved bandwidth (kbits/sec): 0

TE class 2 unreserved bandwidth (kbits/sec): 0

TE class 3 unreserved bandwidth (kbits/sec): 0

TE class 4 unreserved bandwidth (kbits/sec): 0

TE class 5 unreserved bandwidth (kbits/sec): 0

TE class 6 unreserved bandwidth (kbits/sec): 0

TE class 7 unreserved bandwidth (kbits/sec): 0

TE class 8 unreserved bandwidth (kbits/sec): 0

TE class 9 unreserved bandwidth (kbits/sec): 0

TE class 10 unreserved bandwidth (kbits/sec): 0

TE class 11 unreserved bandwidth (kbits/sec): 0

TE class 12 unreserved bandwidth (kbits/sec): 0

TE class 13 unreserved bandwidth (kbits/sec): 0

TE class 14 unreserved bandwidth (kbits/sec): 0

TE class 15 unreserved bandwidth (kbits/sec): 0

TE metric: 10

IGP metric: 10

SR/SRv6 link maximum SID depths:

MPLS MSD : 5

SRv6 End.X SID

SID : 11::A

Function type : End.X with PSP

Algorithm : 0

Weight : 0

Flags (B/S/P/C): 0/0/0/0

SRv6 End.X SID

SID : 11::1:0:6

Function type : End.X (NO-FLAVOR)

Algorithm : 0

Weight : 0

Flags (B/S/P/C): 0/0/0/0

SRv6 End.X SID

SID : 12:1:2:3:0:A::

Function type : End.X (NO-FLAVOR)

Algorithm : 0

Weight : 0

Flags (B/S/P/C): 0/0/0/1

Common prefix length: 64

Node length : 26

Function length : 6

Args length : 0

SRv6 End.X SID

SID : 12:1:2:3:0:6::

Function type : End.X with PSP

Algorithm : 0

Weight : 0

Flags (B/S/P/C): 0/0/0/1

Common prefix length: 64

Node length : 26

Function length : 6

Args length : 0

SRv6 End.X SID

SID : 12:1:2:3:0:7::

Function type : End.X with PSP, USP & USD

Algorithm : 0

Weight : 0

Flags (B/S/P/C): 0/0/0/1

Common prefix length: 64

Node length : 26

Function length : 6

Args length : 0

IS-IS P2P:

Local node: System ID 0000.0000.0002.00, IS level: 1

Remote node: System ID 0000.0000.0001.00, IS level: 1

IPv6 local address: 1001::2

IPv6 remote address: 1001::1

Topology ID: 2

Link source: ProcID 1, TLV type: MT-IS-reach, FragID: 0x0

IGP metric: 10

Flag: 0, Average delay(us): 50

Application specific link attributes

SA-Length: 8, UDA-Length: 8

Standard applications: 0x100000000 Flex-Algo

User-defined applications: 0x100000000 Flex-Algo

Flag: 0, Average delay(us): 50

SRv6 End.X SID

SID : 2000::1:0:2

Function type : End.X (NO-FLAVOR)

Algorithm : 130

Weight : 0

Flags (B/S/P/C): 0/0/0/0

SRv6 End.X SID

SID : 2000::1:0:3

Function type : End.X with PSP

Algorithm : 130

Weight : 0

Flags (B/S/P/C): 0/0/0/0

SRv6 End.X SID

SID : 2000::1:0:4

Function type : End.X with PSP, USP & USD

Algorithm : 130

Weight : 0

Flags (B/S/P/C): 0/0/0/0

Table 7 Command output

Field	Description
Link-state information: Link	Link information.
count	Number of links reported by the IGP to the SRv6 TE policy database.
Public instance	Public network instance.
MT-ID	Topology information: · 0—Standard topology. · 2—IPv6 unicast topology.
Link count	Number of links in the IS-IS instance.
IS-IS P2P	IS-IS P2P link.
IS-IS to DIS	IS-IS link to the pseudonode.
IS-IS from DIS	IS-IS link from the pseudonode.
Local node	Local node of the link.
Remote node	Remote node of the link.
System ID	System ID of the node.
IS level	IS-IS level of the node.
Topology ID	Topology ID: · 0—IPv4 topology. · 2—IPv6 topology.
Link source	Advertisement source of the link.
ProcID	IS-IS process ID.
TLV type	TLV type: · none—Invalid TLV. · nbr—Neighbor TLV. · wide-nbr—Wide neighbor TLV. · ip-internal—IP internal reachability TLV. · ip-external—IP external reachability TLV. · router-id—Router ID TLV. · ip-extended—Extended IP reachability TLV. · ipv6-reach—IPv6 reachability TLV. · ipv6 router-id—IPv6 router ID TLV. · MT-IS-reach—Multi-topology IS reachability TLV. · MT-IP-reach—Multi-topology IP reachability TLV. · MT-ipv6-reach—Multi-topology IPv6 reachability TLV. · srlg—SRLG TLV. · locator—Locator TLV. · rtr-cap—Routing capability TLV. · unknown—Unknown TLV.
FragID	Fragment ID of the packet.
TE class XX unreserved bandwidth (kbits/sec)	Reservable bandwidth for the specified TE class.
Application specific link attributes	Information about application-specific link attributes.
SA-Length	Standard Application Identifier Bit Mask Length, in bytes.
UDA-Length	User Defined Application Identifier Bit Mask Length, in bytes.
Standard applications	The 0x10 Flex-Algo value represents Flexible Algorithm.
User-defined applications	The 0x10 Flex-Algo value represents Flexible Algorithm.
SR/SRv6 link maximum SID depths	Maximum SID Depths (MSD) information for the MPLS SR or IPv6 SR link.
MPLS MSD	Maximum number of SIDs that MPLS SR can encapsulate into a packet.
SRLG	Shared risk link group information.
SRv6 LAN End.X SID	IPv6 SR End.X SID sub TLV information about the LAN adjacency link.
SRv6 End.X SID	IPv6 SR End.X SID sub TLV information about the P2P adjacency link.
SID	SRv6 SID.
Function type	SID function type. If a SID function type contains NO-FLAVOR, for example, End.X (NO-FLAVOR) or End.X with COC (NO-FLAVOR), it indicates that the flavor attribute is canceled for the SID and the SID has only the USP flag.
Flags (B/S/P/C)	IPv6 SR flag information: · B—Backup flag. If set, it indicates link protection. · S—Collection flag. If set, it indicates a collection of neighbor devices. The SID can be assigned to multiple neighbors. · P—Permanent flag. If set, it indicates that the SID can be permanently assigned to the neighbor even if the neighbor relationship is reestablished. · C—SRv6 SID compression flag. If set, it indicates that the SID is compressed.
Common prefix length	Common prefix length of the compressed SID.
Node length	Node length of the compressed SID.
Function length	Function length of the compressed SID.
Args length	Args length of the compressed SID.

‌

# Display node information reported by the IGP to the SRv6 TE policy database.

<Sysname> display segment-routing ipv6 te database node

Link-state information: Node, count: 2

Public instance, MT-ID: 2, IS-IS instance ID: 0, Node count: 2

IS-IS node: System ID 0000.0000.0020.00, IS level: 1

Node source: ProcID 100, TLV type: none, FragID: 0x0

Node topology ID: 0 2

IS-IS area: 10

TE local router ID: 2.2.2.2

SRv6 capability flag (O/C): 0/0

SR/SRv6 node maximum SID depths:

MPLS MSD : 5

Segment Left: 11

End Pop MSD : 11

H.Encaps MSD: 11

End D MSD : 11

Flex-Algo: 130

Priority: 255

Metric type: 0

MFlag: 0

SRPLS node attribute Flex-Algo exclude-any

0x00000000 0x00000000

0x00000004

IS-IS node: System ID 0000.0000.0019.00, IS level: 1

Node source: ProcID 100, TLV type: none, FragID: 0x0

Node topology ID: 0 2

Node flag: 0x1

IS-IS area: 10

TE local router ID: 1.2.3.4

IPv6 local router ID: 1::1

SRv6 capability flag (O/C): 0/1

SR/SRv6 node maximum SID depths:

MPLS MSD : 5

Segment Left: 11

End Pop MSD : 11

H.Encaps MSD: 11

End D MSD : 11

Table 8 Command output

Field	Description
Link-state information: Node	Node information.
count	Number of nodes reported by the IGP to the SRv6 TE policy database.
Public instance	Public network instance.
MT-ID	Topology information: · 0—Standard topology. · 2—IPv6 unicast topology.
Node count	Number of nodes in the IS-IS instance.
System ID	System ID of the node.
IS level	IS-IS level of the node.
Node source	Advertisement source of the node.
ProcID	IS-IS process ID.
TLV type	TLV type: · none—Invalid TLV. · nbr—Neighbor TLV. · wide-nbr—Wide neighbor TLV. · ip-internal—IP internal reachability TLV. · ip-external—IP external reachability TLV. · router-id—Router ID TLV. · ip-extended—Extended IP reachability TLV. · ipv6-reach—IPv6 reachability TLV. · ipv6 router-id—IPv6 router ID TLV. · MT-IS-reach—Multi-topology IS reachability TLV. · MT-IP-reach—Multi-topology IP reachability TLV. · MT-ipv6-reach—Multi-topology IPv6 reachability TLV. · srlg—SRLG TLV. · locator—Locator TLV. · rtr-cap—Routing capability TLV. · unknown—Unknown TLV.
FragID	Fragment ID of the packet.
Node flag	Flag of the node. 0x01 indicates root node.
SRv6 capability flag	SRv6 capability flag: · O—O flag in the SRH. If set, it indicates that the node supports OAM. · C—SRv6 SID compression flag. If set, it indicates that the SID is compressed.
SR/SRv6 link maximum SID depths	MSD information for the MPLS SR or IPv6 SR link.
MPLS MSD	Maximum number of SIDs that MPLS SR can encapsulate into a packet.
Segment Left	Maximum value of the Segments Left field in the SRH.
End Pop MSD	Maximum number of SIDs in the SRH to which the node can apply PSP or USP behavior. For a packet destined to the local SID on the device, the device is the endpoint of the packet.
H.Encaps MSD	Maximum number of SIDs that can be included as part of the H.Encaps behavior.
End D MSD	Maximum number of SIDs in the SRH when performing decapsulation associated with End.Dx behaviors.
Flex-Algo	Flexible algorithm ID.
Priority	Flex-Algo priority.
Metric type	Metric type of the Flex-Algo: · 0—IS-IS link cost. · 1—Link latency. · 2—TE metric.
MFlag	Metric flag. A value of 2 indicates that the prefix uses the metric type of the Flex-Algo.
SRPLS node attribute Flex-Algo exclude-any	Flex-Algo excludes the links with any specific affinity attribute.
SRLG info	Shared Risk Link Group information.

‌

# Display prefix information reported by the IGP to the SRv6 TE policy database.

<Sysname> display segment-routing ipv6 te database prefix

Link-state information: Prefix, count: 21

Public instance, MT-ID: 2, IS-IS instance ID: 0, Prefix count: 7

IS-IS IPv6 prefix:

Local node: System ID 0000.0000.0001.00, IS level: 1

Prefix: 100::1/128, Topology ID: 2

Prefix source: ProcID 1, TLV type: ipv6-reach, FragID: 0x0

Route tag: 100

Prefix metric: 10

Locator information

Metric : 0

Algorithm : 0

Flags (D/A): 0/0

Admin tag : 20

Table 9 Command output

Field	Description
Link-state information: Prefix	Prefix information.
count	Number of prefixes reported by the IGP to the SRv6 TE policy database.
Public instance	Public network instance.
MT-ID	Topology information: · 0—Standard topology. · 2—IPv6 unicast topology.
Prefix count	Number of prefixes in the IS-IS instance.
Local node	Local node information of the link.
System ID	System ID of the node.
IS level	IS-IS level of the node.
Prefix	Prefix address.
Topology ID	Topology ID: · 0—IPv4 topology. · 2—IPv6 topology.
Prefix source	Advertisement source of the prefix.
ProcID	IS-IS process ID.
TLV type	TLV type: · none—Invalid TLV. · nbr—Neighbor TLV. · wide-nbr—Wide neighbor TLV. · ip-internal—IP internal reachability TLV. · ip-external—IP external reachability TLV. · router-id—Router ID TLV. · ip-extended—Extended IP reachability TLV. · ipv6-reach—IPv6 reachability TLV. · ipv6 router-id—IPv6 router ID TLV. · MT-IS-reach—Multi-topology IS reachability TLV. · MT-IP-reach—Multi-topology IP reachability TLV. · MT-ipv6-reach—Multi-topology IPv6 reachability TLV. · srlg—SRLG TLV. · locator—Locator TLV. · rtr-cap—Routing capability TLV. · unknown—Unknown TLV.
FragID	Fragment ID of the packet.
Route tag	Tag value of the interface associated with the prefix.
Locator information	Locator sub-TLV information carried in the prefix.
Algorithm	ID of the algorithm associated with the locator: · 0—SPF algorithm. · 128 to 288—Flex-Algo algorithm.
Flags (D/A)	Locator flag: · D—Leakage flag, set when the Locator TLV cannot be leaked from Level-1 to Level-2. · A—Anycast locator flag, set when the locator is an Anycast Locator.
Admin tag	Admin tag value of the SRv6 locator.

‌

# Display SRv6 SID information reported by the IGP to the SRv6 TE policy database.

<Sysname> display segment-routing ipv6 te database srv6-sid

Link-state information: SRv6 SID, count: 20

Public instance, MT-ID: 2, IS-IS instance ID: 0, SRv6 SID count: 1

IS-IS SRv6 SID:

Local node: System ID 0000.0000.0002.00, IS level: 1

SID: 300::2, Topology ID: 2

SID source: ProcID 1, TLV type: locator, FragID: 0x0

SRv6 endpoint function

Function type: End with PSP

Algorithm : 0

Flags : 0x01

IS-IS SRv6 SID:

Local node: System ID 0000.0000.0001.00, IS level: 1

SID: 100:200:DB8:ABCD:0:1::, Topology ID: 0

SID source: ProcID 1, TLV type: locator, FragID: 0x0

SRv6 endpoint function

Function type: End (NO-FLAVOR)

Algorithm : 0

Flags : 0x0

IS-IS SRv6 SID:

Local node: System ID 0000.0000.0001.00, IS level: 1

SID: 100:200:DB8:ABCD:0:2::, Topology ID: 0

SID source: ProcID 1, TLV type: locator, FragID: 0x0

SRv6 endpoint function

Function type: End with PSP, USP & USD

Algorithm : 0

Flags : 0x0

Table 10 Command output

Field	Description
Link-state information: SRv6 SID	SRv6 SID information.
count	Number of SRv6 SIDs reported by the IGP to the SRv6 TE policy database.
Public instance	Public network instance.
MT-ID	Topology information: · 0—Standard topology. · 2—IPv6 unicast topology.
SRv6 SID count	Number of SRv6 SIDs in the IS-IS instance.
IS-IS SRv6 SID	SRv6 SID advertised by IS-IS.
Local node	Local node information of the link.
System ID	System ID of the node.
IS level	IS-IS level of the node.
SID	SRv6 SID.
Topology ID	Topology ID: · 0—IPv4 topology. · 2—IPv6 topology.
SID source	Advertisement source of the SID.
ProcID	IS-IS process ID.
TLV type	TLV type: · none—Invalid TLV. · nbr—Neighbor TLV. · wide-nbr—Wide neighbor TLV. · ip-internal—IP internal reachability TLV. · ip-external—IP external reachability TLV. · router-id—Router ID TLV. · ip-extended—Extended IP reachability TLV. · ipv6-reach—IPv6 reachability TLV. · ipv6 router-id—IPv6 router ID TLV. · MT-IS-reach—Multi-topology IS reachability TLV. · MT-IP-reach—Multi-topology IP reachability TLV. · MT-ipv6-reach—Multi-topology IPv6 reachability TLV. · srlg—SRLG TLV. · locator—Locator TLV. · rtr-cap—Routing capability TLV. · unknown—Unknown TLV.
FragID	Fragment ID of the packet.
SRv6 endpoint function	SRv6 SID function.
SID	SRv6 SID.
Function type	SID function type. If a SID function type contains NO-FLAVOR, for example, End (NO-FLAVOR) or End.X (NO-FLAVOR), it indicates that the flavor attribute is canceled for the SID and the SID has only the USP flag.
Algorithm	Algorithm value.
Flags	Compression flag: · 0x01—End SID compression flag. · 0x10—End.X SID compression flag.

‌

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 [ binding-sid bsid | policy { name policy-name | { color color-value | end-point ipv6 ipv6-address } * } ] [ verbose ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

binding-sid bsid: Specifies a BSID by an IPv6 address.

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: XGE2/0/0

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

Discriminator: 100

Backup path:

Seglist ID: 2

Seglist forwarding index: 2149580802

Weight: 1

Outgoing forwarding index: 2148532226

Interface: XGE2/0/1

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

Discriminator: 100

# 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(policy binding-sid statistics):

Total octets: 525

Total packets: 1

Erroneous packets: 0

Dropped packets: 0

Input rate in last 300 seconds:

0 bits/sec, 0 pkts/sec

Input rate in last statistical period (20 sec):

0 bits/sec, 0 pkts/sec

Outbound statistics:

Total octets: 750

Total packets: 1

Erroneous packets: 0

Dropped packets: 0

Output rate in last 300 seconds:

0 bits/sec, 0 pkts/sec

Output rate in last statistical period (20 sec):

0 bits/sec, 0 pkts/sec

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

Output rate in last 300 seconds:

0 bits/sec, 0 pkts/sec

Output rate in last statistical period (20 sec):

0 bits/sec, 0 pkts/sec

Output service-class 4:

416 octets, 4 packets,

0 errors, 0 dropped packets

Output rate in last 300 seconds:

0 bits/sec, 0 pkts/sec

Output rate in last statistical period (20 sec):

0 bits/sec, 0 pkts/sec

Outgoing forwarding index: 2148532225

Interface: XGE2/0/0

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

Discriminator: 100

Path ID: 1

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

Outbound statistics:

Total octets: 750

Total packets: 1

Erroneous packets: 0

Dropped packets: 0

Output rate in last 300 seconds:

0 bits/sec, 0 pkts/sec

Output rate in last statistical period (20 sec):

0 bits/sec, 0 pkts/sec

Output service-class 4:

416 octets, 4 packets,

0 errors, 0 dropped packets

Output rate in last 300 seconds:

0 bits/sec, 0 pkts/sec

Output rate in last statistical period (20 sec):

0 bits/sec, 0 pkts/sec

Backup path:

Seglist ID: 2

Seglist forwarding index: 2149580802

Weight: 1

Outgoing forwarding index: 2148532226

Interface: XGE2/0/1

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

Discriminator: 100

Path ID: 2

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

Table 11 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(policy binding-sid statistics)	Statistics on the traffic received by the BSID, which records the total traffic received from the SRv6 TE policy with the specified 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.
Output service-class	Statistics on outbound traffic of the specified service class. A value of 255 means the SRv6 TE policy is not configured with a service class and has the lowest forwarding priority.
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.
Delay timer type	Delay timer type: · LSP—LSP refresh delay timer. · BFD—BFD DOWN flag bit clearing delay timer. · SBFD—SBFD DOWN flag bit clearing delay timer.
Delay time	Up delay time, in milliseconds.
Remaining time	Remaining up delay time, in milliseconds.
Outgoing forwarding index	The next hop forwarding entry index of the first address in the SID list. ECMP-backup indicates backup path for an ECMP route.
Interface	Brief name of the outgoing interface. If the outgoing interface is NULL0, it indicates that SRv6 TE FRR has been enabled and triggered.
Nexthop	Next hop IPv6 address.
Discriminator	Discriminator of the SRv6 forwarding path.
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 G-SID. If the next SID is a non-compressed SID, the common prefix length is 0.
G-SID length	Length of the next G-SID. If the next SID is a non-compressed SID, the SID length is 128.
Type	Whether the SID is compressed when it is encapsulated into the SRH: · Compressed—The SID is compressed when it is encapsulated into the SRH. · Normal—The SID is not compressed when it is encapsulated into the SRH.

‌

display segment-routing ipv6 te forwarding traffic-statistics

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

Syntax

display segment-routing ipv6 te forwarding traffic-statistics

Views

Any view

Predefined user roles

network-admin

network-operator

Examples

# Display SRv6 TE traffic statistics.

<Sysname> display segment-routing ipv6 te forwarding traffic-statistics

Policy name: p1

Policy ID: 0

Color: 10

Endpoint: 4::4

Binding SID: 1::1:0:1

Output rate within last 300 seconds: 0 bits/sec, 0 packets/sec

Output rate within last statistics interval (100 sec): 0 bits/sec, 0 packets/sec

Output: 0 bytes, 0 packets

Primary candidate path:

Preference: 20

Discriminator: 20

Protocol origin: CLI

Segment list name: s2

Segment list ID: 2

Output rate within last 300 seconds: 0 bits/sec, 0 packets/sec

Output rate within last statistics interval (100 sec): 0 bits/sec, 0 packets/sec

Output: 0 bytes, 0 packets

Backup candidate path:

Preference: 10

Discriminator: 10

Protocol origin: CLI

Segment list name: s1

Segment list ID: 1

Output rate within last 300 seconds: 0 bits/sec, 0 packets/sec

Output rate within last statistics interval (100 sec): 0 bits/sec, 0 packets/sec

Output: 0 bytes, 0 packets

Table 12 Command output

Field	Description
Policy name	Name of the SRv6 TE policy.
Policy ID	ID of the SRv6 TE policy.
Color	Color attribute of the SRv6 TE policy.
Endpoint	IPv6 address of the destination node for the SRv6 TE policy.
Binding SID	BSID value.
Output rate within last 300 seconds: 0 bits/sec, 0 packets/sec	Outbound traffic rate statistics within the most recent 300 seconds.
Output rate within last statistics interval (100 sec): 0 bits/sec, 0 packets/sec	Outbound traffic rate statistics within the most recent statistics interval. To set the statistics interval, use the srv6-policy forwarding statistics interval command.
Output: 0 bytes, 0 packets	Total bytes and total number of packets for outbound traffic.
Primary candidate path	Primary candidate path for forwarding traffic.
Backup candidate path	Backup candidate path for forwarding traffic.
Preference	Candidate path preference of the SRv6 TE policy.
Discriminator	Discriminator of the forwarding path.
Protocol origin	Protocol that obtained the candidate path: · PCEP. · BGP. · CLI—Locally configured. · Unknown—Unknown source.
Segment list name	Name of the SID list.
Segment list ID	ID of the SID list.

‌

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:

Name from PCE:

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: Up

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

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

Hot backup: Enabled

Statistics: Enabled

Statistics by service class: Enabled

Path verification: Enabled

Drop-upon-invalid: Enabled

BFD trigger path-down: Enabled

SBFD: Enabled

Remote: 1000

SBFD template name: abc

SBFD backup template name: -

OAM SID: -

Reverse path type: None

BFD Echo: Disabled

Forwarding index: 2150629377

Association ID: 1

Service-class: -

Rate-limit: 15000 kbps

PCE delegation: Disabled

PCE delegate report-only: Disabled

Reoptimization: Disabled

Encapsulation mode: -

Flapping suppression Remaining interval: -

Candidate paths state: Configured

Candidate paths statistics:

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

Candidate paths:

Preference : 20

Network slice ID: 1

B Flag: Set

CpathName:

CPathPolicyName:

ProtoOrigin: CLI Discriminator: 10

Instance ID: 0 Node address: 0.0.0.0

Originator: 0, ::

SRv6 Binding SID:

Binding SID: 100::1

Flags (S/I/B): 0/1/1

Endpoint Behavior: End.B6.Encaps

Locator Block Length: 64

Locator Node Length: 16

Function Length: 16

Argument Length: 8

SRv6 Binding SID:

Binding SID: 200::2

Flags (S/I/B): 0/1/1

Endpoint Behavior: End.B6.Encaps.Red

Locator Block Length: 64

Locator Node Length: 8

Function Length: 24

Argument Length: 16

Optimal: Y Flags: V/A

Dynamic: Not configured

PCEP: Not configured

Explicit SID list:

ID: 1 Name: Sl1

Weight: 1 Forwarding index: 2149580801

State: Up State(Echo BFD): Down

Verification State: -

Path MTU: 1500 Path MTU Reserved: 0

SID list flags: None

Local BSID: -

Reverse BSID: -

Table 13 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.
Name from PCE	Name of the SRv6 TE policy obtained from PCE. If no SRv6 TE policy was obtained from PCE, 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 (Name from configuaration)—Manually configured SRv6 TE policy. · NB (Name from BGP)—SRv6 TE policy obtained from a BGP route.
Status	SRv6 TE policy state. The SRv6 TE policy is up if a minimum of one SID list in the candidate paths of the SRv6 TE policy is up. The SRv6 TE policy is down if no SID list in the candidate paths of the SRv6 TE policy is up. · Up—Active state. · Down—Inactive state. The SRv6 TE policy went down because of reasons other than BFD or SBFD session collaboration. · Down (BFD down)—A BFD or SBFD session detected that the forwarding paths of all SID lists in the candidate paths of the SRv6 TE policy are not reachable. In this state, the first next hop in the forwarding path of each SID list is reachable, but the subsequent nodes are not reachable.
AdminStatus	Administrative state of the SRv6 TE policy: · Down—The policy is shut down by the shutdown command. · Up—The policy is not shut down by the shutdown command.
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.
Statistics	Traffic statistics status for the SRv6 TE policy: · Disabled. · Enabled.
Statistics by service class	Service class based traffic statistics status for the SRv6 TE policy: · Enabled. · Disabled.
Path verification	Status of the path verification feature: · Enabled—Verifies the validity of all SIDs in the segment list. · Specified SIDs—Verifies the validity of the specified SIDs in the segment list. · Disabled. · Not configured.
Drop-upon-invalid	Drops traffic when the SRv6 TE policy becomes invalid: · Disabled. · Enabled.
BFD trigger path-down	Whether to enable SRv6 TE policy path reselection when the BFD session for the SRv6 TE policy goes down: · Disabled. · Enabled.
SBFD	SBFD status for the SRv6 TE policy: · Enabled. · Disabled.
Encapsulation mode	Encapsulation mode for BFD or SBFD packets: · Encaps—Normal encapsulation mode. · Insert—Insertion encapsulation mode. If the encapsulation mode for BFD or SBFD packets is not configured, this field displays a hyphen (-).
Remote	Remote discriminator of the SBFD session. If the default value is used, this field displays a hyphen (-).
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.
Reverse path type	Reverse path type for SBFD packets: · Reverse BSID—Uses the SID list associated with the reverse BSID as the reverse path for SBFD packets. · None—The reverse path for SBFD packets is not configured. The SBFD packets are forwarded back to the source node through IP forwarding.
BFD echo	Echo packet mode BFD status for the SRv6 TE policy: · Enabled. · Disabled.
Source IPv6 address	Source IPv6 address of the echo packet mode BFD session.
Echo BFD template name	Name of the echo BFD template.
Echo BFD backup template name	Name of the echo BFD template for the backup SID list.
Reverse path type	Reverse path type for BFD echo packets: · Reverse BSID—Uses the SID list associated with the reverse BSID as the reverse path for BFD packets. · None—The reverse path for BFD packets is not configured.
Forwarding index	Forwarding entry index of the SRv6 TE policy.
Association ID	Association ID for the candidate path of the SRv6 TE policy. An association ID can identify an 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 (-).
PCE delegation	PCE delegation state for the SRv6 TE policy: · Disabled. · Enabled.
PCE delegate report-only	Only reports SRv6 TE policy information without delegating the SRv6 TE policy to the PCE: · Disabled. · Enabled.
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 (-).
Flapping suppression Remaining interval	Remaining interval for flapping suppression.
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 TE policy routes.
PCEP paths	Number of candidate paths obtained from PCEP.
ODN paths	Number of candidate paths created by ODN.
Candidate paths	SRv6 TE policy candidate path information.
Preference	SRv6 TE policy candidate path preference.
Network slice ID	Network slice ID of the SRv6 TE policy candidate path.
B Flag	First flag bit in the IPv6 Hop-by-Hop extension header: · If the fist flag bit is set (value 1), packets fail to match a network slice instance ID on the output interface can be forwarded through the output interface. · If the fist flag bit is not set (value 0), packets fail to match a network slice instance ID on the output interface will be discarded.
CPathName	Name of the candidate path obtained from a BGP route. If no path name was obtained, this field is empty.
CPathPolicyName	Name of the candidate path inherited from the SRv6 TE policy. If no path name was obtained, this field is empty.
ProtoOrigin	Protocol that obtained the SRv6 TE policy: · PCEP. · BGP. · CLI—Locally configured. · Unknown—Unknown source.
Discriminator	Discriminator of the SRv6 TE policy.
Instance ID	BGP instance ID. 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.
Originator: ASN, Peer-address	Information of the SRv6 TE policy obtained through BGP, where: · ASN—AS number. A value of 0 indicates that the device does not obtain SRv6 TE policy information from BGP peers. · Peer-address—BGP node address. For a manually configured SRv6 TE policy, the peer address is 0.0.0.0. For an SRv6 TE policy obtained from a BGP peer, the peer address is the address of the BGP peer.
SRv6 Binding SID	SRv6 Binding SID Sub-TLV information: · Binding SID—BSID value of the SRv6 TE policy candidate path. · Flags (S/I/B)—BSID flags. ¡ S—Specified-BSID-only flag. The current software version does not support this flag. If this flag is set, the system takes restrictive Specified-BSID-only behaviors on the candidate path. The system does not bind a BSID to the candidate path and determines that it is invalid if it has an unspecified BSID or if the specified BSID is not available when it becomes active. ¡ I—Invalid flag. When this flag is set, the device discards traffic that matches an invalid SRv6 TE policy. ¡ B—Behavior flag. When this flag is set in a packet, the packet carries an SRv6 SID endpoint behavior. · Endpoint Behavior—Endpoint behavior for BSID-based traffic steering. ¡ End.B6.Encaps—Normal encapsulation mode. ¡ End.B6.Encaps.Red—Reduced mode of the normal encapsulation mode. · Locator Block Length—Common prefix length, in bits. · Locator Node Length—Node ID length, in bits. · Function Length—Function length, in bits. · Argument Length—Argument length, in bits.
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. · B—Backup candidate path. · S—Stale candidate path. · BN (Name from BGP)—Candidate path obtained from a BGP route. · PN (Name from PCEP)—Candidate path obtained from PCE. · None—No candidate path.
Dynamic	Dynamic SID list computation: Configured or Not configured.
Last calculation started at	Time when the most recent dynamic calculation started.
Duration	Period of time that the most recent dynamic calculation lasted, in seconds.
Reason for last calculation failure	Failure reason for the most recent dynamic calculation: · Endpoint is 0.0.0.0. · The destination node does not exist. · The destination node is the same as the source node. · Flex-Algo is not configured. · Destination node is unreachable. · The topology information is incomplete. · The link has no adjacent SID. · Cannot get valid SIDs. · SID list exceeds the maximum SID depth. · Failed to create SID list. · Internal error.
PCEP	Configuration state of PCEP: Configured or Not configured.
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—The first next hop on the forwarding path of the SID list is reachable. · DOWN—The first next hop on the forwarding path of the SID list is not reachable. · Down(BFD down)—The first next hop on the forwarding path of the SID list is reachable. However, BFD detected that the subsequent nodes on the forwarding path are not reachable.
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. The type variable represents SBFD or echo BFD session or no BFD session. If SBFD or echo BFD is not configured, this field displays a hyphen (-) and (No BFD).
Verification state	Verification result of the SID list: · Down—The verification fails. · Up—The verification succeeds. If verification is not configured, this field displays a hyphen (-).
SID list flags	SID list flags of the SRv6 TE policy: · O—The number of SIDs in the SID list exceeds the maximum depth for the SID label stack on the device. · None—Stateless.
Local BSID	This value is specified by using the local-binding-sid parameter of the explicit segment-list command. If this value is not specified, this field displays a hyphen (-).
Reverse BSID	This value is specified by using the reverse-binding-sid parameter of the explicit segment-list command. If this value is not specified, this field displays a hyphen (-).

‌

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 14 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. · BFD Detect Down—The first next hop on the forwarding path of the SID list is reachable. However, BFD detected that the subsequent nodes on the forwarding path are not reachable.

‌

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)

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

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

Total candidate paths: 1

Configured: 1

From BGP: 0 (Added 0 deleted 0)

From ODN: 0 (Added 0 deleted 0)

From PCE: 0 (Added 0 deleted 0)

Total SID lists: 1 (1 up 0 down)

Configured: 1 (1 up 0 down)

Dynamic : 1 (1 up 0 down)

From BGP: 0 (0 up 0 down)

SRv6-TE policy group resource information:

Max resources: 1024

Used resources: 0

Upper threshold: 717 (70%)

Lower threshold: 102 (10%)

SRv6-TE policy resource information:

Max resources: 1024

Used resources: 1

Upper threshold: 512 (50%)

Lower threshold: 102 (10%)

SID list resource information:

Max resources: 4096

Used resources: 1

Upper threshold: 3277 (80%)

Lower threshold: 1638 (40%)

Forwarding path resource information:

Max resources: 65535

Used resources: 1

Upper threshold: 26214 (40%)

Lower threshold: 13107 (20%)

Table 15 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 or BFD down state.
Configured	Number of manually configured SRv6 TE policies. · up—Number of SRv6 TE policies in up state. · down—Number of SRv6 TE policies in down state or BFD down state.
Dynamic	Number of dynamically calculated SRv6 TE policies: · up—Number of SRv6 TE policies in up state. · down—Number of SRv6 TE policies in down state or BFD down state.
From BGP	Number of SRv6 TE 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 or BFD down state.
From ODN	Number of SRv6 TE policies created by ODN. · Added—Number of ODN-added SRv6 TE policies. · deleted—Number of ODN-deleted SRv6 TE policies. · up—Number of SRv6 TE policies in up state. · down—Number of SRv6 TE policies in down state or BFD down state.
From PCE	Number of SRv6 TE policies created by PCE. · Added—Number of PCE-added SRv6 TE policies. · deleted—Number of PCE-deleted SRv6 TE policies. · up—Number of SRv6 TE policies in up state. · down—Number of SRv6 TE policies in down state or BFD down state.
Total candidate paths	Total number of SRv6 TE policy candidate paths.
Total SID lists	Total number of SID lists.
Max resources	Total number of resources.
Upper threshold	Upper resource threshold.
Lower threshold	Lower resource threshold.

‌

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 16 Command output

Field	Description
Name/ID	Name/ID of an SRv6 TE policy.
Status	State of the SRv6 TE policy: · Up. · Down. · Down (BFD down)—A BFD or SBFD session detected that the forwarding paths of all SID lists in the candidate paths of the SRv6 TE policy are not reachable. In this state, the first next hop in the forwarding path of each SID list is reachable, but the subsequent nodes are not reachable.
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 [ odn ] [ group-id | { color color-value | end-point ipv6 ipv6-address } * ] [ verbose ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

odn: Specifies SRv6 TE policy groups automatically created by ODN. If you do not specify this keyword, the command displays information about both SRv6 TE policy groups automatically created by ODN and statically created SRv6 TE policy groups.

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

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

end-point ipv6 ipv6-address: Specifies an SRv6 TE policy group by its endpoint IPv6 address.

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

Usage guidelines

If you do not specify the group-id argument, the color color-value option, or the end-point ipv6 ipv6-address option, the command displays information about all SRv6 TE policy groups.

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: 5

GroupID: 10 GroupState: Up

GroupNID: 2151677953 Referenced: 1

Flags: A Group type: Static DSCP

Group color: 100

StateChangeTime: 2021-03-18 09:57:43

Endpoint: 4::4

Drop upon mismatch: Disabled

Delete delay time(ms) : 180000

Delete remain time(ms): -

UP/Total Mappings: 26/26

Color Type DSCP

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

GroupID: 20 GroupState: Down

GroupNID: 2151677953 Referenced: 1

Flags: None Group type: Static Dot1p

Group color: 100

StateChangeTime: 2021-10-27 10:09:22

Endpoint: 44::44

UP/Total Mappings: 0/5

Color Dot1p

20 4

30 5~7

Table 17 Command output

Field	Description
UPMappings	Number of the following mappings in up (valid) state in the SRv6 TE policy group: Color-to-802.1p mappings.
TotalMappings	Total number of the following mappings in the SRv6 TE policy group: · Color-to-DSCP mappings. · Color-to-802.1p mappings.
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 initial or stable state. · BA—Requesting a BSID. · BS—Preferred BSID. · BC—Conflicts with an existing BSID.
Group type	SRv6 TE policy group type: · Static DSCP—Statically created SRv6 TE policy group that uses DSCP-based traffic steering. · Static Dot1p—Statically created SRv6 TE policy group that uses 802.1p-based traffic steering. · Dynamic—Dynamically created SRv6 TE policy group. No forward type is configured. · Dynamic DSCP—Dynamically created SRv6 TE policy group that uses DSCP-based traffic steering.
Group color	Color value of the SRv6 TE policy group.
StateChangeTime	Time when the SRv6 TE policy group state changed.
Endpoint	Destination node IP address of the SRv6 TE policy group. None indicates that the endpoint is not configured.
BSID	BSID information of the SRv6 TE policy group: · Explicit BSID—BSID allocated by the system. · Request state—Request state of the BSID. Supported values: ¡ Succeeded. ¡ Failed.
Best-effort NID	NID for best effort forwarding.
Drop upon mismatch	Whether the feature of discarding packets that do not match any valid SRv6 TE policy or SRv6 BE path is enabled: · Disabled. · Enabled.
Delete delay time(ms)	Deletion delay time for the ODN template-created SRv6 TE policy group, in milliseconds.
Delete remain time(ms)	Remaining time of the deletion delay time for the SRv6 TE policy group, in milliseconds.
UP/Total Mappings	If 802.1p-based traffic steering is used, this field represents the number of valid color-to-802.1p mappings and the total number of configured color-to-802.1p mappings in the SRv6 TE policy group.
Color	Color value
Best-effort	SRv6 BE forwarding mode.
Type	Packet type: IPv4 or IPv6.
DSCP	DSCP value. This field displays default if the SRv6 TE policy or SRv6 BE mode is used as the default forwarding policy for the address family.
Dot1p	802.1p value.

‌

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

Use display segment-routing ipv6 te policy-group last-down-reason to display the reason why the specified or all SRv6 TE policy groups went down most recently.

Syntax

display segment-routing ipv6 te policy-group last-down-reason [ group-id | endpoint ipv6-address color color-value ]

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.

endpoint ipv6-address color color-value: Specifies the IPv6 address of the destination node and the color value in the range of 0 to 4294967295.

Examples

# Display the reason why SRv6 TE policy group 10 went down most recently.

<Sysname> display segment-routing ipv6 te policy-group last-down-reason 10

Group ID : 10 Group type : Static DSCP

Group color: 100 Endpoint : 4::4

Group NID : 2151677956

Create time: 2021-03-18 09:57:43

Up time : -

Down time : 2021-03-18 09:57:43

Down reason: No active SRv6-TE Policies

Color: 20 Address family: IPv4

Up time : 2021-03-18 01:52:20.785

Down time : 2021-03-18 09:59:23

Down reason: No endpoint

Table 18 Command output

Field	Description
Group type	SRv6 TE policy group type: · Static DSCP—Statically created SRv6 TE policy group that uses DSCP-based traffic steering. · Static Dot1p—Statically created SRv6 TE policy group that uses 802.1p-based traffic steering. · Static service-class—Statically created SRv6 TE policy group that uses service class-based traffic steering. · Static APN-ID—Statically created SRv6 TE policy group that uses APN ID-based traffic steering. · Static TE Class—Statically created SRv6 TE policy group that uses TE class ID-based traffic steering. · Dynamic—Dynamically created SRv6 TE policy group. No forward type is configured. · Dynamic APN-ID—Dynamically created SRv6 TE policy group that uses APN ID-based traffic steering. · Dynamic DSCP—Dynamically created SRv6 TE policy group that uses DSCP-based traffic steering. · Dynamic service-class—Dynamically created SRv6 TE policy group that uses service class-based traffic steering. · Dynamic TE Class—Dynamically created SRv6 TE policy group that uses TE class ID-based traffic steering.
Group color	Color value of the SRv6 TE policy group.
Endpoint	Destination node IP address of the SRv6 TE policy group.
Group NID	Index of the forwarding entry for the SRv6 TE policy group.
Create time	Time when the SRv6 TE policy group state was created.
Up time	Time when the SRv6 TE policy group came up.
Down time	Time when the SRv6 TE policy group went down.
Down reason	Reason why the SRv6 TE policy group went down: · No endpoint. · No color-DSCP mappings. · No active SRv6 TE policies. · No color-Dot1p mappings—No color-to-802.1p mappings are configured. · No color-service-class mappings—No color-to-service class mappings are configured. · No color-apn-id mappings—No color-to-APN ID mappings are configured. · No color-TE Class mappings—No color-to-TE class ID mappings are configured.
Color	Color value mapped to the DSCP/802.1p/service class/APN ID value.
Up time	Time when the color-to-DSCP/color-to-802.1p/color-to-service class/color-to-APN ID mapping came up.
Down time	Time when the color-to-DSCP/color-to-802.1p/color-to-service class/color-to-APN ID mapping went down.
Down reason	Reason why the color-to-DSCP/color-to-802.1p/color-to-service class/color-to-APN ID mapping went down. · No endpoint. · No color-DSCP mappings. · The SRv6-TE policy is used by another group. · SRv6-TE policy doesn't exist. · SRv6-TE policy down. · No color-Dot1p mappings. · No color-TE Class mappings. · No selected by intelligent route policy.

‌

display segment-routing ipv6 te policy-group statistics

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

Syntax

display segment-routing ipv6 te policy-group statistics

Views

Any view

Predefined user roles

network-admin

network-operator

Examples

# Display SRv6 TE policy group statistics.

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

Statistics type Total Up

Dynamic DSCP groups 0 0

Static DSCP groups 1 0

Color-DSCP mappings 0 0

SRv6-BE-DSCP mappings 0 0

Static Dot1p groups 0 0

Color-Dot1p mappings 0 0

Dynamic service-class groups 0 0

Static service-class groups 0 0

Color-service-class mappings 0 0

SRv6-BE-service-class mappings 0 0

Dynamic apn-id groups 0 0

Static apn-id groups 0 0

Color-apn-id mappings 0 0

SRv6-BE-apn-id mappings 0 0

Dynamic TE Class groups 0 0

Static TE Class groups 0 0

Color-TE Class mappings 0 0

IPR-TE Class mappings 0 0

SRv6-BE-TE Class mappings 0 0

Table 19 Command output

Field	Description
Statistics type	Statistics objects: · Static Dot1p groups—Statically created SRv6 TE policy groups that use 802.1p-based traffic steering. · Color-Dot1p mappings—Color-to-802.1p mappings in all SRv6 TE policy groups.
Total	Total number of statistics objects.
UP	Number of effective statistics objects.

‌

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 sbfd

Color: 10

Endpoint: 4::4

Policy name: p1

State: Down

Nid: 2149580801

BFD type: SBFD

Encapsulation mode: Encaps

Remote Discr: 100

State: Down

Timer: 30

VPN index: 0

Template name: abc

Reverse path type: None

Reverse BSID: -

Flush add time: 2022-12-22 17:01:48

Table 20 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.
Encapsulation mode	Encapsulation mode for SBFD packets: · Encaps—Normal encapsulation mode. · Insert—Insertion encapsulation mode. If the encapsulation mode for SBFD packets is not configured, this field displays a hyphen (-).
Remote Discr	Remote discriminator.
Timer	SBFD session timer, in seconds.
Reverse path type	Reverse path type for SBFD packets: · Reverse BSID—Uses the SID list associated with the reverse BSID as the reverse path for SBFD packets. · None—The reverse path for SBFD packets is not configured. The SBFD packets are forwarded back to the source node through IP forwarding.
Reverse BSID	Reverse BSID of the SBFD session.
Flush add time	The most recent time when the SRv6 TE policy flushed path information to SBFD. SBFD establishes a detection session based on the path information. If no SBFD session is established, this field displays a hyphen (-).

‌

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

Verification State: Down

Nodes: 1

Flags: None

Local BSID: -

Reverse BSID: -

Reference counts: 0

Index : 1 SID: 1::2

Status : Up TopoStatus: Nonexistent

Type : Type_2 Flags: V

Coc Type : - Common prefix length: 0

Function length : 0 Args length: 0

Endpoint Behavior: -

Table 21 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. · Dynamic—Dynamically calculated by the source node. If the SID list does not have a valid origin, this field displays a hyphen (-).
Status	SID list status, Down or Up.
Verification State	Verification result of the SID list: · Down—The verification fails. · Up—The verification succeeds.
Nodes	Number of nodes in the SID list.
Flags	Flags bit of the node. · None—No flags. · V—Verifies the validity of the SID during SRv6 TE policy path verification. · CF—The local BSID or reverse BSID conflicts with an existing BSID.
Index	Node index.
SID	SID value (IPv6 address) of the node.
TopoStatus	Whether the SID exists in the IGP topology: · Existent. · Nonexistent.
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.
Function length	Length of the SID function.
Args length	Args length for the specified SRv6 SID.
Endpoint Behavior	Endpoint behavior: · End (no PSP, no USP) · End with PSP · End with USP · End with PSP&USP · End.X (no PSP, no USP) · End.X with PSP · End.X with USP · End.X with PSP&USP · End.T (no PSP, no USP) · End.T with PSP · End.T with USP · End.T with PSP&USP · End with USD · End with PSP&USD · End with USP&USD · End with PSP&USP&USD · End.X with USD · End.X with PSP&USD · End.X with USP&USD · End.X with PSP&USP&USD · End.T with USD · End.T with PSP&USD · End.T with USP&USD · End.T with PSP&USP&USD · End with COC · End with PSP&COC · End with PSP&USP&COC · End.X with COC · End.X with PSP&COC · End.X with PSP&USP&COC · End.T with COC · End.T with PSP&COC · End.T with PSP&USP&COC · End with PSP&USD&COC · End with PSP&USP&USD&COC · End.X with PSP&USD&COC · End.X with PSP&USP&USD&COC · End.T with PSP&USD&COC · End.T with PSP&USP&USD&COC This field displays a hyphen (-) for an invalid endpoint behavior.

‌

display segment-routing ipv6 te source-sid

Use display segment-routing ipv6 te source-sid to display information about SRv6 SIDs collected from the LS database.

Syntax

display segment-routing ipv6 te source-sid [ end | end-x | sid ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

end: Displays End SID information.

end-x: Displays End.X SID information.

sid: Displays information about the specified SRv6 SID.

Usage guidelines

If you do not specify any parameters, this command displays information about all SRv6 SIDs collected from the LS database.

Examples

# Display information about all SRv6 SIDs collected from the LS database.

<Sysname> display segment-routing ipv6 te source-sid

SID : 11::1:0:8, Count: 1

Type : End.X(LAN), Topology ID: 0

Instance ID: 0

Source : IS-IS, ProcID 100, IS-Level-1

Node : 0000.0000.0019.00

Local : 0000.0000.0019.00

Peer : 0000.0000.0022.01

SID : 12:1:2:3:0:1::, Count: 2

Type : End, Topology ID: 0

Instance ID: 0

Source : IS-IS, ProcID 100, IS-Level-1

Node : 0000.0000.0019.00

Type : End, Topology ID: 2

Instance ID: 0

Source : IS-IS, ProcID 100, IS-Level-1

Node : 0000.0000.0019.00

SID : 12:1:2:3:0:6::, Count: 2

Type : End.X, Topology ID: 0

Instance ID: 0

Source : IS-IS, ProcID 100, IS-Level-1

Node : 0000.0000.0019.00

Local : 2001:1::2

Peer : 2001:1::16

Type : End.X, Topology ID: 2

Instance ID: 0

Source : IS-IS, ProcID 100, IS-Level-1

Node : 0000.0000.0019.00

Local : 2001:1::2

Peer : 2001:1::16

Table 22 Command output

Field	Description
SID	SRv6 SID.
Count	Number of advertising sources for the SID.
Type	SID type: · End. · End.X. · End.X (LAN).
ProcID	Process ID.
IS-Level-X	IS level on the node: IS-Level-1 or IS-Level-2.
Node	Node where the SID advertising source resides.
Local	For an End.X SID, this field displays the system ID of the IS-IS process to which the SID-associated local interface belongs. If the link type is P2P and the IPv6 link attribute is enabled for the IS-IS process, this field displays the IPv6 address of the SID-associated local interface.
Peer	For an End.X SID, this field displays the system ID of the IS-IS process to which the SID-associated neighbor interface belongs. If the link type is P2P and the IPv6 link attribute is enabled for the IS-IS process, this field displays the IPv6 address of the SID-associated neighbor interface.

‌

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

dynamic (SRv6 TE policy path preference view)

Use dynamic to create and enter SRv6 TE policy path preference dynamic view, or enter the existing SRv6 TE policy path preference dynamic view.

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

Syntax

dynamic

undo dynamic

Default

The SRv6 TE policy path preference dynamic view does not exist.

Views

SRv6 TE policy path preference view

Predefined user roles

network-admin

Usage guidelines

In SRv6 TE policy path preference dynamic view, you can enable the device to dynamically create SID lists for an SRv6 TE policy candidate path.

Examples

# Create and enter SRv6 TE policy path preference dynamic view.

<Sysname> system-view

[Sysname] segment-routing ipv6

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

[Sysname-srv6-te] policy 1

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

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

[Sysname-srv6-te-policy-1-path-pref-20] dynamic

[Sysname-srv6-te-policy-1-path-pref-20-dyna]

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

exclude-any

Use exclude-any to configure the exclude-any affinity attribute rule and enter affinity attribute rule view, or enter the view of the existing affinity attribute rule.

Use undo exclude-any to delete the affinity attribute rule view and all configurations in the view.

Syntax

exclude-any

undo exclude-any

Default

No affinity attribute rules exist.

Views

Affinity attribute view

Predefined user roles

network-admin

Usage guidelines

With the exclude-any affinity attribute rule configured, an SRv6 TE policy does not use a link if it contains any of the specific affinity attributes.

Examples

# Configure the exclude-any affinity attribute rule and enter affinity attribute rule 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 200

[Sysname-srv6-te-policy-a1-path-pref-200] constraints

[Sysname-srv6-te-policy-a1-path-pref-200-const] affinity

[Sysname-srv6-te-policy-a1-path-pref-200-const-aff] exclude-any

[Sysname-srv6-te-policy-a1-path-pref-200-const-aff-exclude-any]

Related commands

affinity (SRv6 TE policy constraints view)

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 and global path MTU of a SID list.

Syntax

explicit segment-list segment-list-name [ local-binding-sid ipv6 ipv6-address | path-mtu mtu-value | reverse-binding-sid ipv6 ipv6-address | weight weight-value ] *

undo explicit segment-list segment-list-name [ local-binding-sid | path-mtu | reverse-binding-sid | 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.

local-binding-sid ipv6 ipv6-address: Specifies a local BSID for BFD detection. If you do not specify this option, the local BSID configured for the SID list applies.

· The specified BSID cannot be the same as the BSID configured with the local-binding-sid command for the SID list.

· The BSID specified in this option takes precedence over the BSID configured with the local-binding-sid command for the SID list.

path-mtu mtu-value: Specifies the path MTU (in bytes) for the SID list. The value range for the path MTU varies by device model. If you do not specify this option, the global path MTU set in SRv6 view applies to the SID list.

reverse-binding-sid ipv6 ipv6-address: Specifies a reverse BSID for BFD or SBFD detection. If you do not specify this option, the reverse BSID configured for the SID list applies.

· The specified BSID cannot be the same as the BSID configured with the reverse-binding-sid command for the SID list.

· The BSID specified in this option takes precedence over the BSID configured with the reverse-binding-sid command for the SID list.

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.

You can configure the path MTU for all SRv6 TE candidate paths globally in SRv6 view or for a specific forwarding path in SRv6 TE policy path preference view. The path-specific configuration takes precedence over the global configuration. A forwarding path identified by a SID list of an SRv6 TE policy uses the global configuration only when it has no path-specific configuration.

Before forwarding an SRv6 packet encapsulated with the SID list specified by this command, the device can use the MTU of that SID list to control the SRv6 packet size. This approach avoids packet loss caused by the fact that IPv6 packets do not support fragmentation. If this command specifies a path MTU for the SID list, the device takes the smaller value out of the path MTU of the SID list and the IPv6 MTU of the output interface. Then, the device uses the following formula to calculate the a ctive MTU, which is used for real packet forwarding:

Active MTU = Smaller value - global reserved path MTU

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

path-mtu

segment-list

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

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

forward-type (SRv6 TE ODN policy group view)

Use forward-type to create a forward type and enter its view, or enter the view of an existing forward type.

Use undo forward-type to restore the default.

Syntax

forward-type dscp

undo forward-type dscp

Default

No forward type is created. Traffic cannot be steered to the SRv6 TE policy group automatically created by the ODN template.

Views

SRv6 TE ODN policy group view

Predefined user roles

network-admin

Parameters

dscp: Specifies the DSCP forward type, which achieves DSCP-based traffic steering.

Usage guidelines

Use this command to specify the method for steering traffic in to the SRv6 TE policy group automatically created by the ODN template. In the current software version, SRv6 TE policy groups automatically created by an ODN template only support DSCP-based traffic steering.

When the forward type is DSCP, the device steers traffic by using the following procedure:

1. Matches the DSCP value in a packet with the mappings configured by using the color match dscp command.

2. If the DSCP value matches a color-to-DSCP mapping configured by using the color match dscp command and the SRv6 TE policy specified by the color attribute value in the mapping is valid, the device uses that SRv6 TE policy to forward the packet.

Examples

# Create the DSCP forward type and enter DSCP forward type view.

<Sysname> system-view

[Sysname] segment-routing ipv6

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

[Sysname-srv6-te] on-demand-group color 1

[Sysname-srv6-te-odn-group-1] forward-type dscp

[Sysname-srv6-te-odn-group-1-dscp]

Related commands

color match dscp (DSCP forward type view)

forward-type (SRv6 TE policy group view)

Use forward-type to configure the forward type for an SRv6 TE policy group.

Use undo forward-type to restore the default.

Syntax

forward-type dot1p

undo forward-type dot1p

Default

DSCP-based traffic steering is used for packets that match an SRv6 TE policy group.

Views

SRv6 TE policy group view

Predefined user roles

network-admin

Parameters

dot1p: Specifies the Dot1p forward type, that is, 802.1p-based traffic steering.

Usage guidelines

Use this command to specify the method for steering traffic in to a statically created SRv6 TE policy group. Statically created SRv6 TE policy groups only support DSCP-based and 802.1p-based traffic steering in the current software version.

When the forward type is Dot1p, the device steers traffic by using the following procedure:

1. Identifies the color attribute based on the 802.1p value of the packet.

2. Locates an SRv6 TE policy in the SRv6 TE policy group based on the color attribute of the packet.

3. Forwards the packet with the 802.1p value through the specified SRv6 TE policy.

Examples

# Specify 802.1p-based traffic steering for SRv6 TE policy group 1.

<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] forward-type dot1p

Related commands

color match dscp (SRv6 TE policy group view)

group-color

Use group-color to configure the color value for an SRv6 TE policy group.

Use undo group-color to restore the default.

Syntax

group-color color-value

undo group-color

Default

The color value is not configured 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, in the range of 0 to 4294967295.

Usage guidelines

You can use the color value specified in this command to perform color-based traffic steering to the specified SRv6 TE policy group.

You can specify the same color value for an SRv6 TE policy group and an SRv6 TE policy in it. The color values do not affect each other.

Examples

# Configure the color value as 1 for the SRv6 TE policy group.

<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] group-color 1

import-route sr-policy

Use import-route sr-policy to enable BGP to redistribute routes from the SRv6 TE 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 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 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 SRv6 TE policy.

<Sysname> system-view

[Sysname] bgp 100

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

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

include-all

Use include-all to configure the include-all affinity attribute rule and enter affinity attribute rule view, or enter the view of the existing affinity attribute rule.

Use undo include-all to delete the affinity attribute rule view and all configurations in the view.

Syntax

include-all

undo include-all

Default

No affinity attribute rules exist.

Views

Affinity attribute view

Predefined user roles

network-admin

Usage guidelines

With the include-all affinity attribute rule configured, an SRv6 TE policy uses a link only if it contains all of the specific affinity attributes.

Examples

# Configure the include-all affinity attribute rule and enter affinity attribute rule 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 200

[Sysname-srv6-te-policy-a1-path-pref-200] constraints

[Sysname-srv6-te-policy-a1-path-pref-200-const] affinity

[Sysname-srv6-te-policy-a1-path-pref-200-const-aff] include-all

[Sysname-srv6-te-policy-a1-path-pref-200-const-aff-include-all]

Related commands

affinity (constraints view)

include-any

Use include-any to configure the include-any affinity attribute rule and enter affinity attribute rule view, or enter the view of the existing affinity attribute rule.

Use undo include-any to delete the affinity attribute rule view and all configurations in the view.

Syntax

include-any

undo include-any

Default

No affinity attribute rules exist.

Views

Affinity attribute view

Predefined user roles

network-admin

Usage guidelines

With the include-any affinity attribute rule configured, an SRv6 TE policy uses a link only if it contains any of the specific affinity attributes.

Examples

# Configure the include-any affinity attribute rule and enter affinity attribute rule view.

<Sysname> system-view

[Sysname] segment-routing

[Sysname-segment-routing] traffic-engineering

[Sysname-sr-te] policy a1

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

[Sysname-sr-te-policy-a1-path] preference 200

[Sysname-sr-te-policy-a1-path-pref-200] constraints

[Sysname-sr-te-policy-a1-path-pref-200-const] affinity

[Sysname-sr-te-policy-a1-path-pref-200-const-aff] include-any

[Sysname-sr-te-policy-a1-path-pref-200-const-aff-rule]

Related commands

affinity (constraints view)

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 [ verification ]

index index-number coc32 ipv6 ipv6-address common-prefix-length [ verification ]

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.

verification: Enables SID validity verification. A SID is valid if the SID exists in the topology and the associated locator network route is routable. If you do not specify this keyword, path verification does not verify the validity of the SID. Do not specify this keyword for the BSID or a SID not in the local AS. If you do so, path verification will determine that the segment list has failed, affecting packet forwarding.

Usage guidelines

When you add a G-SID to the SID list, the common prefix length configured by this command must be the same as that of the locator where the next node belongs.

When you add a G-SID to the SID list, make sure the following requirements are met:

· The SRv6 SID previous to the G-SID is an End(COC32) SID or End.X(COC32) SID.

· The last SRv6 SID in the SID list does not carry the COC flavor.

If multiple SRv6 TE policies have a common path, you can configure the common path as an SRv6 TE policy. When you configure the SRv6 TE policies, you can add the BSID of the common SRv6 TE policy to the SID lists of the SRv6 TE policies. In this way, you recurse the SRv6 TE policies to the common SRv6 TE policy, simplifying the SID list configuration.

If the first SID in the SID list of an SRv6 TE policy is a BSID, note the following restrictions and guidelines:

· Nested SRv6 TE policy recursions are not supported, that is, the first SID in the SID list of the recursion SRv6 TE policy (the SRv6 TE policy with that BSID) cannot be a BSID.

· The first SID cannot be the BSID of this SRv6 TE policy itself.

· Do not configure path connectivity verification for this SRv6 TE policy.

· The BSID cannot be configured as a local BSID or a reverse BSID.

· The traffic statistics, BFD, and SBFD features of this SRv6 TE policy are not affected by the status of those features for the recursion SRv6 TE policy.

· The BFD/SBFD detection time of this SRv6 TE policy cannot be shorter than that of the recursion SRv6 TE policy.

· The path MTU of this SRv6 TE policy cannot be smaller than that of the recursion SRv6 TE policy.

After path connectivity verification is enabled for an SRv6 TE policy, the device verifies the validity of all SIDs in the SID list. If the SID list contains an inter-AS SID (for example, the BGP Peer SID allocated by BGP EPE) or contains the BSID of another SRv6 TE policy, the path connectivity verification will fail. This is because a BSID or BGP Peer SID cannot be flooded in the IGP topology.

To resolve this issue, you can execute the following commands to configure the path connectivity verification only verifies the validity of specific SIDs:

· Use the index command to specify the verification keyword for the SIDs to be verified. Do not specify this keyword for a BSID or BGP EPE SID in the SID list.

· Specify the specified-sid keyword when you execute the path verification command in SRv6 TE policy view or the srv6-policy path verification enable command in SRv6 TE view.

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

path verification

srv6 compress enable

srv6-policy path verification enable

local-binding-sid

Use local-binding-sid to configure a local BSID.

Use undo local-binding-sid to restore the default.

Syntax

local-binding-sid ipv6 ipv6-address

undo local-binding-sid

Default

No local BSID exists.

Views

SID list view

Predefined user roles

network-admin

Parameters

ipv6 ipv6-address: Specifies a local BSID by an IPv6 address.

Usage guidelines

By default, the returning BFD echo or SBFD packets used for SRv6 TE policy connectivity detection are forwarded based on the IP forwarding path. If a transit node fails, the returning packets will be discarded, the BFD or SBFD session will go down, and the SID list will be mistakenly considered as faulty.

To resolve this issue, you can enable the returning BFD or SBFD packets to be forwarded based on the specified SID list to ensure connectivity as follows:

1. Configure a reverse BSID in SID list view on the ingress node, and configure a local BSID with the same value in SID list view on the egress node.

2. When the ingress node forwards a BFD or SBFD packet, it performs the following operations:

¡ For a BFD packet, it encapsulates an SID list in the SRH. In addition, it encapsulates the reverse BSID associated with the SID list to the SL=1 location.

¡ For an SBFD packet, it encapsulates the Aux Path TLV to the packet. This TLV contains the reverse BSID.

3. When the egress node receives the BFD or SBFD packet, it compares the reverse BSID in the packet with the configured local BSID. If the values are the same, the egress node encapsulates an SRH for the returning BFD or SBFD packet and forwards the packet based on the SID list associated with the local BSID.

The BSID specified in this command cannot be the same as the BSID of the SRv6 TE policy. If they are the same, the SID list becomes invalid and cannot be used to forward packets.

The BSID specified in this command must be within the static length of the locator specified in SRv6 TE view. If this condition is not met, the SID list associated with the BSID cannot be used to forward packets.

Examples

# Configure the local BSID for SID list s1 as 1::1.

<Sysname> system-view

[Sysname] segment-routing ipv6

[Sysname-segment-routing] traffic-engineering

[Sysname-srv6-te] segment-list s1

[Sysname-srv6-te-sl-s1] local-binding-sid ipv6 1::1

Related commands

reverse-binding-sid

metric

Use metric to create a metric type and enter its view, or enter the view of an existing metric type.

Use undo metric to delete the metric type view and all the configuration in the view.

Syntax

metric

undo metric

Default

No metric types exist.

Views

SRv6 TE policy path preference dynamic view

Predefined user roles

network-admin

Usage guidelines

Use this command to specify the method for implementing dynamic path calculation for SRv6 TE policies.

Examples

# In SRv6 TE policy path preference dynamic view, create a metric type and enter metric type view.

<Sysname> system-view

[Sysname] segment-routing ipv6

[Sysname-segment-routing] traffic-engineering

[Sysname-srv6-te] policy 1

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

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

[Sysname-srv6-te-policy-1-path-pref-20] dynamic

[Sysname-srv6-te-policy-1-path-pref-20-dyna] metric

[Sysname-srv6-te-policy-1-path-pref-20-dyna-metric]

name

Use name to specify an affinity attribute for an affinity attribute rule.

Use undo name to restore the default.

Syntax

name name

undo name name

Default

No affinity attribute is specified for an affinity attribute rule.

Views

Affinity attribute rule view

Predefined user roles

network-admin

Parameters

name: Specifies an affinity attribute by its name, a case-sensitive string of 1 to 32 characters.

Usage guidelines

This command enables the SRv6 TE policy to select links containing the bit values associated with the specified affinity attribute as required by the affinity attribute rule.

· Link attribute—A 32-bit binary number. Each bit represents an attribute with a value of 0 or 1.

· Affinity attribute bit position—The value range is 0 to 32. When the affinity attribute value is N, it is compared with the N+1 bit of the link attribute. The affinity attribute applies to the link only if the N+1 bit value of the link attribute is 1.

For example, for affinity attribute names blue and red, if you configure the name blue bit-position 1 and name red bit-position 5 commands, the link selection varies by affinity attribute rule type:

· For the include-any affinity attribute rule, a link is available for use if the link attribute has the second bit (associated with affinity attribute blue) or sixth bit (associated with affinity attribute red) set to 1.

· For the include-all affinity attribute rule, a link is available for use if the link attribute has both the second bit (associated with affinity attribute blue) and sixth bit (associated with affinity attribute red) set to 1.

· For the exclude-any affinity attribute rule, a link is not available for use if the link attribute has the second bit (associated with affinity attribute blue) or sixth bit (associated with affinity attribute red) set to 1.

Examples

# In affinity attribute rule view, specify affinity attribute red for the include-any affinity attribute rule.

<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 200

[Sysname-srv6-te-policy-a1-path-pref-200] constraints

[Sysname-srv6-te-policy-a1-path-pref-200-const] affinity

[Sysname-srv6-te-policy-a1-path-pref-200-const-aff] include-any

[Sysname-srv6-te-policy-a1-path-pref-200-const-aff-include-any] name red

Related commands

mpls te link-attribute (MPLS Command Reference)

name bit-position

Use name bit-position to create a name-to-bit mapping for an affinity attribute.

Use undo name bit-position to restore the default.

Syntax

name name bit-position bit-position-number

undo name name bit-position

Default

No name-to-bit mapping is configured for an affinity attribute.

Views

Constraints mapping view

Predefined user roles

network-admin

Parameters

name: Specifies an affinity attribute by its name, a case-sensitive string of 1 to 32 characters.

bit-position-number: Specifies a bit by its position value in the range of 0 to 31.

Usage guidelines

This command enables the SRv6 TE policy to select links containing the bit values associated with the specified affinity attribute as required by the affinity attribute rule.

· Link attribute—A 32-bit binary number. Each bit represents an attribute with a value of 0 or 1.

For example, for affinity attribute names blue and red, if you configure the name blue bit-position 1 and name red bit-position 5 commands, the link selection varies by affinity attribute rule type:

Examples

# Map affinity attribute red to bit 3 in the affinity attribute.

<Sysname> system-view

[Sysname] segment-routing ipv6

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

[Sysname-srv6-te] affinity-map

[Sysname-srv6-te-affinity-map] name red bit-position 3

Related commands

mpls te link-attribute (MPLS Command Reference)

name

on-demand-group

Use on-demand-group to create an ODN template for creating SRv6 TE policy groups and enter SRv6 TE ODN policy group view, or enter the SRv6 TE ODN policy group view of an existing ODN template.

Use undo on-demand-group to delete an ODN template and all the configuration in the view.

Syntax

on-demand-group color color-value

undo on-demand-group color color-value

Default

No SRv6 TE policy group ODN templates exist.

Views

SRv6 TE view

Predefined user roles

network-admin

Parameters

color color-value: Specifies the color value for the ODN template, in the range of 0 to 4294967295.

Usage guidelines

When the device receives a BGP route, it compares the color extended attribute value of the BGP route with the color value of the ODN template. If the color values match, the device automatically generates an SRv6 TE policy group. The device will assign the smallest ID that are not in use to the SRv6 TE policy group.

After an SRv6 TE policy group is automatically generated, you must configure color-to-DSCP mappings for the template for DSCP-based traffic steering.

Examples

# Create an SRv6 TE policy group ODN template with color value 1 and enter SRv6 TE ODN policy group view.

<Sysname> system-view

[Sysname] segment-routing ipv6

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

[Sysname-srv6-te] on-demand-group color 1

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

path verification

Use path verification to configure path connectivity verification for an SRv6 TE policy.

Use undo path verification to restore the default.

Syntax

path verification { disable | [ specified-sid ] enable }

undo path verification

Default

Path connectivity verification is not configured for an SRv6 TE policy. The setting configured in SRv6 TE view applies.

Views

SRv6 TE policy view

Predefined user roles

network-admin

Parameters

disable: Disables path connectivity verification for the SRv6 TE policy.

enable: Enables path connectivity verification for the SRv6 TE policy.

specified-sid: Enables path connectivity verification only for the SIDs specified with the verification keyword in the index command. If you do not specify the specified-sid keyword, the path verification command verifies the validity for all SIDs in the SID list.

Usage guidelines

To configure path verification for an SRv6 TE policy, you must configure this command on the source node of the SRv6 TE policy. Even if you configure this feature on the controller and the controller deploys the BGP IPv6 SR policy route to the device, you still need to configure this feature on the source node of the SRv6 TE policy.

Typically, the controller deploys the SID list of an SRv6 TE policy. Without BFD configured, the source node cannot immediately detect path failures in the SRv6 TE policy. It only changes the SID list of the SRv6 TE policy as instructed by the controller that completes path recalculation upon detecting a topology change. If the controller or the link to the controller fails, the source node will be unable to detect failures and change SID lists, resulting in traffic loss.

For fast traffic switchover and high availability, you can enable path connectivity verification for the source node of the SRv6 TE policy. This feature enables the source node to collect network topology information, and verify all SID lists in the SRv6 TE policy as follows:

· If all SRv6 SIDs exist in the topology and the associated locator prefixes are routable, the SID list is valid.

· If any SRv6 SIDs do not exist in the topology or any of the associated locator prefixes are not routable, the SID list is invalid.

Upon detecting an invalid SID list (SID list failure), the source node changes paths as follows:

· If the valid candidate paths of the SRv6 TE policy contain multiple SID lists, and one of the SID list fails, traffic is distributed to other valid SID lists.

· If the SRv6 TE policy has valid primary and backup candidate paths, and all SID lists for the primary candidate path fail, traffic is distributed to the backup candidate path.

· If all valid candidate paths of the SRv6 TE policy fail, the SRv6 TE policy is faulty and an associated protection action is taken (for example, MPLS L3VPN FRR).

You can configure SRv6 TE policy path connectivity verification in both SRv6 TE view and SRv6 TE policy view. The configuration in SRv6 TE policy view takes precedence over the configuration in SRv6 TE view. If path connectivity verification is not configured for an SRv6 TE policy, the configuration in SRv6 TE applies.

The source node must have all SRv6 SIDs and routes in the IGP domain to detect their status through the following settings:

· Enable the IGP domain to forward routing information through IPv6 IS-IS.

· Configure the distribute link-state command in IS-IS view for the source node to report link status.

If a BSID exists in the segment list path, path connectivity verification will fail because the BSID cannot be flooded in the IGP topology. Do not configure this command in the scenario where BSID is deployed.

To resolve this issue, you can execute the following commands to configure the path connectivity verification only verifies the validity of specific SIDs:

· Use the index command to specify the verification keyword for the SIDs to be verified. Do not specify this keyword for a BSID or BGP EPE SID in the SID list.

· Specify the specified-sid keyword when you execute the path verification command in SRv6 TE policy view or the srv6-policy path verification enable command in SRv6 TE view.

If the first SID in a segment list is the local End SID of the source node in the SRv6 TE policy, the segment list will fail the verification. As a best practice, do not enable this feature in such a situation. To enable this feature, you must specify the specified-sid keyword to verify only the SIDs specified with the verification keyword in the index command.

Examples

# Enable path connectivity verification 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] path verification enable

Related commands

distribute (Layer 3—IP Routing Command Reference)

index

srv6-policy path verification enable

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

The preference is not 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]

reset segment-routing ipv6 te forwarding statistics

Use reset segment-routing ipv6 te forwarding statistics to clear forwarding statistics for 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

reverse-binding-sid

Use reverse-binding-sid to configure a reverse BSID.

Use undo reverse-binding-sid to restore the default.

Syntax

reverse-binding-sid ipv6 ipv6-address

undo reverse-binding-sid

Default

No reverse BSID exists.

Views

SID list view

Predefined user roles

network-admin

Parameters

ipv6 ipv6-address: Specifies a reverse BSID by an IPv6 address.

Usage guidelines

To resolve this issue, you can enable the returning BFD or SBFD packets to be forwarded based on the specified SID list to ensure connectivity as follows:

1. Configure a reverse BSID in SID list view on the ingress node, and configure a local BSID with the same value in SID list view on the egress node.

2. When the ingress node forwards a BFD or SBFD packet, it performs the following operations:

¡ For a BFD packet, it encapsulates an SID list in the SRH. In addition, it encapsulates the reverse BSID associated with the SID list to the SL=1 location.

¡ For an SBFD packet, it encapsulates the Aux Path TLV to the packet. This TLV contains the reverse BSID.

The BSID specified in this command cannot be the same as the BSID of the SRv6 TE policy. If they are the same, the SID list becomes invalid and cannot be used to forward packets.

Examples

# Configure the reverse BSID for SID list s1 as 1::1.

<Sysname> system-view

[Sysname] segment-routing ipv6

[Sysname-segment-routing] traffic-engineering

[Sysname-srv6-te] segment-list s1

[Sysname-srv6-te-sl-s1] reverse-binding-sid ipv6 1::1

Related commands

local-binding-sid

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: When the device receives a BGP IPv6 SR policy route and the Route Target attribute of the route does not carry the local Router ID, it accepts the route but does not generate an SRv6 TE policy accordingly.

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 ] [ encaps | insert ] [ reverse-path reverse-binding-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 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 but a primary template is specified, the primary template applies. If neither the primary nor the backup template is specified in this command, 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 SBFD packets. As a best practice, use the End.SID of the destination node as the OAM SID.

encaps: Uses the normal encapsulation mode to encapsulate SBFD packets.

insert: Uses the insertion mode to encapsulate SBFD packets.

The following compatibility matrix shows the support of hardware platforms for the encaps and insert keywords:

Model	MPU	Keyword compatibility
RA5300, RA5300-X, RA5300-AC	RSU-400, RSU-400S	Yes
RA5300, RA5300-X, RA5300-AC	RSU-400-G	No

reverse-path: Specifies a reverse path for SBFD packets. If you do not specify this keyword, the egress node looks up the IP forwarding table based on the source address of the received SBFD packets and forwards the returning SBFD packets back to the ingress node.

reverse-binding-sid: Uses the SID list associated with the reverse BSID as the reverse path for SBFD packets.

Usage guidelines

To use SBFD to detect an SRv6 TE policy, the device needs to encapsulate the SID list of the SRv6 TE policy for the SBFD 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.

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

If you do not specify the encaps or insert keyword, the encapsulation mode configured by the bfd srv6-encapsulation-mode encap command applies.

To encapsulate the SBFD packets for SRv6 TE policy connectivity detection, the device uses the encapsulation mode configured for SBFD packets. The encapsulation mode configured for the SRv6 TE policy in SRv6 TE view or SRv6 TE policy view does not take effect on SBFD packets.

If you specify the reverse-path reverse-binding-sid option, the ingress node encapsulates the Aux Path TLV that contains the reverse BSID in SBFD packets. The reverse BSID can be specified by using the explicit segment-list or reverse-binding-sid command. When the egress node receives the SBFD packets, it parses the Aux Path TLV to obtain the reverse BSID. If the reverse BSID is the same as the local BSID of an SRv6 TE policy on the egress node, the egress node encapsulates an SRH in the SBFD packets and forwards the packets along the SID list of the SRv6 TE policy to which the local BSID belongs. To configure a local BSID, you can use the local-binding-sid command.

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

bfd srv6-encapsulation-mode encap

display segment-routing ipv6 te sbfd

explicit segment-list

local-binding-sid

reverse-binding-sid

sbfd local-discriminator (High Availability Command Reference)

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]

segments

Use segments to create the segment constraints and enter its view, or enter the existing segment constraints view.

Use undo segments to delete the segment constraints view and all its configurations.

Syntax

segments

undo segments

Default

No segment constraints exist.

Views

Constraints view

Predefined user roles

network-admin

Examples

# Create the segment constraints and enter its 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 200

[Sysname-srv6-te-policy-a1-path-pref-200] constraints

[Sysname-srv6-te-policy-a1-path-pref-200-const] segments

[Sysname-srv6-te-policy-a1-path-pref-200-const-seg]

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

sid-limit

Use sid-limit to configure the maximum number of SIDs in an SID list.

Use undo sid-limit to restore the default.

Syntax

sid-limit limit-value

undo sid-limit

Default

The maximum number of SIDs in an SID list is not configured.

Views

Metric type view

Predefined user roles

network-admin

Parameters

limit-value: Specifies the maximum number of SIDs in an SID list, in the range of 1 to 255.

Usage guidelines

If the number of SIDs for the calculated paths exceeds the specified value, path calculation based on the specified metric (in the type command) fails for the SRv6 TE policy. The SRv6 TE policy cannot be used to forward traffic.

The effective maximum number of SIDs takes the smaller value among the following settings:

· Maximum number of SIDs configured in this command.

· Default setting for this command.

Examples

# Specify the maximum number of SIDs in the SID list as 10.

<Sysname> system-view

[Sysname] segment-routing ipv6

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

[Sysname-srv6-te] policy p1

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

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

[Sysname-srv6-te-policy-a1-path-pref-200] dynamic

[Sysname-srv6-te-policy-a1-path-pref-200-dyna] metric

[Sysname-srv6-te-policy-a1-path-pref-200-dyna-metric] sid-limit 10

snmp-agent trap enable srv6-policy

Use snmp-agent trap enable srv6-policy to enable SNMP notifications for SRv6 TE policies.

Use undo snmp-agent trap enable srv6-policy to disable SNMP notifications for SRv6 TE policies.

Syntax

snmp-agent trap enable srv6-policy

undo snmp-agent trap enable srv6-policy

Default

SNMP notifications for SRv6 TE policies are disabled.

Views

System view

Predefined user roles

network-admin

Usage guidelines

This command enables the device to send SNMP notifications about state changes and resource usage anomalies of SRv6 TE policies. For SNMP notifications to be sent correctly, you must also configure SNMP on the device. For more information about SNMP configuration, see the network management and monitoring configuration guide for the device.

SRv6 TE policy resources include the following:

· Number of SRv6 TE policy forwarding paths.

· Number of forwarding entry IDs of SRv6 TE policy groups.

· Number of forwarding entry IDs of SRv6 TE policies.

· Number of forwarding entry IDs of SID lists.

Examples

# Enable SNMP notifications for SRv6 TE policies.

<Sysname> system-view

[Sysname] snmp-agent trap enable srv6-policy

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 the color-based mode. The tunnel policy-based mode is enabled. The device selects a tunnel policy from the following tunnel policies (listed in descending order of priority) for traffic steering:

1. Tunnel binding policy configured by using the binding-destination command.

2. Preferred tunnel policy configured by using the preferred-path command.

3. Tunnel load sharing policy configured by using the select-seq load-balance-number command.

policy-based: Enables both the tunnel policy-based mode and the color-based mode.

· If the BGP route contains a color extended community, the device selects a traffic steering method from the following methods (listed in descending order of priority):

a. Tunnel binding policy configured by using the binding-destination command.

b. Tunnel load sharing policy configured by using the select-seq load-balance-number command.

If this method is selected, the device will preferentially select the tunnel that matches the color extended community of the BGP route, and then perform route recursion accordingly. The device looks up a tunnel in the configured tunnel selection order only if it cannot find a tunnel that matches the color extended community of the BGP route.

c. Color-based traffic steering.

· If the BGP route does not contain a color extended community, the device selects a traffic steering method from the following methods (listed in descending order of priority):

a. Tunnel binding policy configured by using the binding-destination command.

b. Preferred tunnel policy configured by using the preferred-path command.

c. Tunnel load sharing policy configured by using the select-seq load-balance-number command.

Usage guidelines

SRv6 TE policies support color-based traffic steering and tunnel policy-based traffic steering. The two traffic steering modes function as follows:

· Based on color—The device searches for an SRv6 TE policy with the color value and end-point that match the color extended community attribute and nexthop address of a BGP route. If a matching SRv6 TE policy exists, the device recurse 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—The device looks up the configured tunnel policies for a matching SRv6 TE policy, and then uses that policy as the public-network tunnel to forward packets that match the BGP route. Tunnel policies can be further divided into tunnel binding policies, preferred tunnel policies, and tunnel load sharing policies. If multiple of them are configured, their priorities are different during tunnel policy selection. For more information about the tunnel policy configuration, see tunnel policy configuration in MPLS Configuration Guide.

This command does not take effect in L2VPN networks.

Examples

# Enable both color-based traffic steering and tunnel policy-based traffic steering to SRv6 TE policies.

<Sysname> system-view

[Sysname] bgp 100

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

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

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.

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 ] [ reverse-path reverse-binding-sid ]

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.

reverse-path: Specifies the reverse path for BFD packets. If you do not specify this keyword, the device forwards BFD packets back to the source node based on the IP forwarding path.

reverse-binding-sid: Uses the SID list associated with the reverse BSID as the reverse path for BFD packets.

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 bfd first-fail-timer

Use srv6-policy bfd first-fail-timer to configure the timer that delays reporting the first BFD or SBFD session establishment failure to an SRv6 TE policy.

Use undo srv6-policy bfd first-fail-timer to restore the default.

Syntax

srv6-policy bfd first-fail-timer seconds

undo srv6-policy bfd first-fail-timer

Default

The timer that delays reporting the first BFD or SBFD session establishment failure to an SRv6 TE policy is 60 seconds.

Views

SRv6 TE view

Predefined user roles

network-admin

Parameters

seconds: Specifies the timeout time that reports the first BFD or SBFD session establishment failure to an SRv6 TE policy. The value range for this argument is 1 to 600 seconds. The default value is 60.

Usage guidelines

The device attempts to establish a BFD or SBFD session to detect an SRv6 TE policy when all the following conditions exist:

· The SRv6 TE policy is in up state.

· The SID list of the SRv6 TE policy is in up state.

· BFD or SBFD is enabled for the SRv6 TE policy.

When the BFD/SBFD session detection timer expires, if the BFD or SBFD session is not in up state, the device considers that the BFD or SBFD session establishment fails. The device does not immediately report the failure to the SRv6 TE policy. You can configure this command to set a delay timer for reporting the session establishment failure. The device will report the session establishment failure to the SRv6 TE policy upon expiration of the delay timer.

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

Examples

# Configure the timer that delays reporting the first BFD or SBFD session establishment failure to an SRv6 TE policy as 30 seconds.

<Sysname> system-view

[Sysname] segment-routing ipv6

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

[Sysname-srv6-te] srv6-policy bfd first-fail-timer 30

srv6-policy calc-schedule-interval

Use srv6-policy calc-schedule-interval to configure the dynamic path calculation timers.

Use undo srv6-policy calc-schedule-interval to restore the default.

Syntax

srv6-policy calc-schedule-interval { maximum-interval [ minimum-interval [ incremental-interval [ conservative ] ] ] | millisecond interval }

undo srv6-policy calc-schedule-interval

Default

The maximum, minimum, and incremental intervals for dynamic path calculation are 5 seconds, 50 milliseconds, and 200 milliseconds, respectively.

Views

SRv6 TE view

Predefined user roles

network-admin

Parameters

maximum-interval: Specifies the maximum dynamic path calculation interval in the range of 1 to 60 seconds. The default value is 5.

minimum-interval: Specifies the minimum dynamic path calculation interval in the range of 10 to 60000 milliseconds. The default value is 50.

incremental-interval: Specifies the incremental dynamic path calculation interval in the range of 10 to 60000 milliseconds. The default value is 200.

conservative: Uses the maximum dynamic path calculation interval in case of SRv6 TE policy flappings. If you do not specify this keyword, in case of SRv6 TE policy flappings, the maximum interval applies for three consecutive times, and then the minimum interval applies. If no SRv6 TE policy flappings occur, the maximum dynamic interval applies for once, and then the minimum interval applies, regardless of whether the conservative keyword is specified.

millisecond interval: Specifies a fixed dynamic path calculation interval in the range of 0 to 10000 milliseconds.

Usage guidelines

Use this command to avoid excessive resource consumption caused by frequent network changes.

If you specify the maximum-interval, minimum-interval, and incremental-interval settings for the command, the following situations will occur:

· For the first path calculation triggered for the SRv6 TE policy, the minimum-interval setting applies.

· For the nth (n > 1) path calculation triggered for the SRv6 TE policy, the device adds a value of incremental-interval × 2n-2 based on the minimum-interval setting. The total value does not exceed the maximum-interval setting.

If the value of minimum-interval + incremental-interval × 2n-2 is larger than or equal to the value of maximum-interval, the device uses the conservative keyword and SRv6 TE policy flapping condition to adjust the path calculation intervals:

· If the conservative keyword is specified:

¡ If SRv6 TE policy flappings occur, the maximum-interval setting applies.

¡ If no SRv6 TE policy flappings occur, the maximum interval applies for once, and then the minimum interval applies.

· If the conservative keyword is not specified:

¡ If SRv6 TE policy flappings occur, the maximum interval applies for three consecutive times, and then the minimum interval applies.

¡ If no SRv6 TE policy flappings occur, the maximum interval applies for once, and then the minimum interval applies.

The value of the minimum-interval or incremental-interval argument cannot be greater than the maximum-interval argument.

To increase path calculation frequency for faster path calculation, configure a fixed interval.

Examples

# Configure the maximum, minimum, and incremental intervals for dynamic path calculation as 10 seconds, 500 milliseconds, and 300 milliseconds, respectively.

<Sysname> system-view

[Sysname] segment-routing ipv6

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

[Sysname-srv6-te] srv6-policy calc-schedule-interval 10 500 300

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

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 log enable

Use srv6-policy log enable to enable SRv6 TE policy logging.

Use undo srv6-policy log enable to disable SRv6 TE policy logging.

Syntax

srv6-policy log enable

undo srv6-policy log enable

Default

SRv6 TE policy logging is disabled.

Views

SRv6 TE view

Predefined user roles

network-admin

Predefined user roles

This command enables the device to generate logs for SRv6 TE policy state changes and resource usage anomalies. The administrator can use the logging information to audit SRv6 TE policies. The device delivers logs to its information center. The information center processes the logs according to user-defined output rules (whether to output logs and where to output). For more information about the information center, see the network management and monitoring configuration guide for the device.

Examples

# Enable SRv6 TE policy logging.

<Sysname> system-view

[Sysname] segment-routing ipv6

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

[Sysname-srv6-te] srv6-policy log enable

srv6-policy path verification enable

Use srv6-policy path verification enable to enable path connectivity verification for all SRv6 TE policies.

Use undo srv6-policy path verification enable to disable path connectivity verification for all SRv6 TE policies.

Syntax

srv6-policy path verification [ specified-sid ] enable

undo srv6-policy path verification enable

Default

Path connectivity verification is disabled for all SRv6 TE policies.

Views

SRv6 TE view

Predefined user roles

network-admin

Parameters

Usage guidelines

You must configure this command on the source node of the SRv6 TE policy.