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

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

Syntax

address-family ipv4 sr-policy

undo address-family ipv4 sr-policy

Default

The BGP IPv4 SR policy address family does not exist.

Views

BGP instance view

Predefined user roles

network-admin

Usage guidelines

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

Examples

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

<Sysname> system-view

[Sysname] bgp 100

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

[Sysname-bgp-default-srpolicy-ipv4]

advertise ebgp enable

Use advertise ebgp enable to advertise BGP IPv4 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 IPv4 SR policy routes are not advertised to EBGP peers.

Views

BGP IPv4 SR policy address family view

Predefined user roles

network-admin

Usage guidelines

By default, only IBGP peers exchange BGP IPv4 SR policy routes. Execute this command to advertise BGP IPv4 SR policy routes to EBGP peers.

Examples

# Advertise BGP IPv4 SR policy routes to EBGP peers.

<Sysname> system-view

[Sysname] bgp 100

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

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

affinity (SR-TE-ODN dynamic view)

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

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

Syntax

affinity { include-all | include-any | exclude-any }

undo affinity { include-all | include-any | exclude-any }

Default

The affinity attribute rule is not created for an SR-MPLS TE policy.

Views

SR-TE-ODN dynamic view

Predefined user roles

network-admin

Parameters

include-all: Uses the links that include all specific affinity attributes.

include-any: Uses the links that include any specific affinity attribute.

exclude-any: Uses none of the links that include any specific affinity attribute.

Examples

# Create the include-all affinity attribute rule and enter affinity attribute rule view.

<Sysname> system-view

[Sysname] segment-routing

[Sysname-segment-routing] traffic-engineering

[Sysname-sr-te] on-demand color 1

[Sysname-sr-te-odn-1] dynamic

[Sysname-sr-te-odn-1-dynamic] affinity include-all

[Sysname-sr-te-odn-1-dynamic-aff-include-all]

affinity (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 SR-MPLS TE policy.

Views

Constraints view

Predefined user roles

network-admin

Examples

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

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

SR TE view

Predefined user roles

network-admin

Examples

# Create the constraints mapping and enter its view

<Sysname> system-view

[Sysname] segment-routing

[Sysname-segment-routing] traffic-engineering

[Sysname-sr-te] affinity-map

[Sysname-sr-te-affinity-map]

backup hot-standby

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

Use undo backup hot-standby to restore the default.

Syntax

backup hot-standby { disable | enable [ multilevel-backup ] }

undo backup hot-standby

Default

Hot standby is not configured for an SR-MPLS TE policy.

Views

SR-MPLS TE policy view

Predefined user roles

network-admin

Parameters

disable: Disables hot standby for the SR-MPLS TE policy.

enable: Enables hot standby for the SR-MPLS TE policy.

multilevel-backup: Enables multilevel hot standby for the SR-MPLS TE policy. With this feature enabled, the candidate path with the third highest preference in the policy is used as the secondary backup path. If you do not specify this keyword, the SR-MPLS TE policy only has one main path and one backup path.

Usage guidelines

The hot standby feature takes the candidate path with the highest preference in the SR-MPLS TE policy as the main path and that with the second highest preference as the backup path. When all SID lists of the main path fails, the backup path immediately takes over to minimize service interruption.

If the multilevel hot standby feature is enabled with the multilevel-backup keyword, a secondary backup path is also provided for the main path besides the backup path. The secondary backup path is the candidate path with the third highest preference in the SR-MPLS TE policy. When all SID lists of the mail path fails, the backup path immediately takes over the service. If the backup path fails, too, the secondary backup path takes over the service to minimize service interruption.

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

Examples

# Enable hot standby for SR-MPLS TE policy 1.

<Sysname> system-view

[Sysname] segment-routing

[Sysname-segment-routing] traffic-engineering

[Sysname-sr-te] policy 1

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

Related commands

sr-policy backup hot-standby enable

best-effort default

Use best-effort default to enable SR-BE forwarding for packets that do not match a color-to-DSCP mapping.

Use undo best-effort default to restore the default.

Syntax

best-effort { ipv4 | ipv6 } default

undo best-effort { ipv4 | ipv6 } default

Default

The device does not perform SR-BE forwarding for packets that do not match a color-to-DSCP mapping.

Views

SR-MPLS TE policy group view

Predefined user roles

network-admin

parameters

ipv4: Enables SR-BE forwarding for IPv4 packets that do not match a color-to-DSCP mapping.

ipv6: Enables SR-BE forwarding for IPv6 packets that do not match a color-to-DSCP mapping.

Usage guidelines

Segment Routing Best Effort (SR-BE) uses IGP to calculate the optimal SRLSP to the destination by using the shortest path first algorithm. In networks that use DSCP-based traffic steering, you can execute this command to enable SR-BE forwarding for packets that do not match a color-to-DSCP mapping.

When the device receives a packet of an IPv4 or IPv6 address family that does not match a color-to-DSCP mapping, it forwards the packet as follows:

· If a default SR-MPLS TE policy is specified in the address family and the SR-MPLS TE policy is valid, the device uses this SR-MPLS TE policy to forward the packet.

· If SR-BE is enabled for packets that do not match a color-to-DSCP mapping in the address family and SR-BE is valid, the device uses SR-BE to forward the packet.

· If a default SR-MPLS TE policy is specified in the other address family and the SR-MPLS TE policy is valid, the device uses this SR-MPLS TE policy to forward the packet.

· If SR-BE is enabled for packets that do not match a color-to-DSCP mapping in the other address family and SR-BE is valid, the device uses SR-BE to forward the packet.

· If color-to-DSCP mappings exist in the address family, and the SR-MPLS TE policy mapped to the smallest DSCP value is valid, the device uses this SR-MPLS TE policy to forward the packet.

· If color-to-DSCP mappings exist in the other address family, and the SR-MPLS TE policy mapped to the smallest DSCP value is valid, the device uses this SR-MPLS TE policy to forward the packet.

Examples

# Enable SR-BE forwarding for IPv4 packets that do not match a color-to-DSCP mapping in SR-MPLS TE policy group 10.

<Sysname> system-view

[Sysname] segment-routing

[Sysname-segment-routing] traffic-engineering

[Sysname-sr-te] policy-group 10

[Sysname-sr-te-policy-group-10] best-effort ipv4 default

Related commands

color match dscp

bfd echo

Use bfd echo to configure the echo packet mode BFD (echo BFD) for an SR-MPLS TE policy.

Use undo bfd echo to restore the default.

Syntax

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

undo bfd echo

Default

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

Views

SR-MPLS TE policy view

Predefined user roles

network-admin

Parameters

disable: Disables the echo packet mode BFD for the SR-MPLS TE policy.

enable: Enables the echo packet mode BFD for the SR-MPLS TE policy.

source-ip ipv4-address: Specifies the source IPv4 address of the BFD session, which is a local IPv4 address on the device. If you do not specify this option, the configuration in SR TE view applies.

source-ip ipv6-address: Specifies the source IPv6 address of the BFD session, which is a local IPv6 address on the device. If you do not specify this option, the configuration in SR 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 SR TE view applies.

backup-template backup-template-name e: Specifies a BFD session parameter template for the backup candidate path. 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 template specified for the primary candidate path applies. If no template is specified for the primary candidate path either, the backup template specified in SR TE view applies.

Usage guidelines

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

If you do not specify the source-ip or source-ipv6 keyword in this command for an SR-MPLS TE policy, you must enable the echo packet mode BFD globally in SR TE view. Otherwise, the device cannot establish a BFD session for the SR-MPLS TE policy.

If you specify the source-ip or source-ipv6 keyword and the bfd echo-source-ip or bfd echo-source-ipv6 command is not executed in system view, both the source and destination IP addresses of BFD echo packets are the IP address specified by the source-ip or source-ipv6 keyword. To avoid being overwhelmed by ICMP redirects from the remote device, execute the bfd echo-source-ip or bfd echo-source-ipv6 command in system view to specify the source IP address for BFD echo packets as an IP address that does not belong to any subnet of a local interface.

To successfully establish a BFD session, the remote device must be able to reach the session source IP address specified by this command on the local device.

If both SBFD and echo BFD are enabled for an SR-MPLS TE policy, the device first establishes the SBFD session.

If both echo SBFD and echo BFD are enabled for an SR-MPLS TE policy, the device first establishes the echo SBFD session.

Examples

# Enable the echo packet mode BFD for SR-MPLS TE policy 1, and specify the source IP address of the BFD session as 1.2.3.4.

<Sysname> system-view

[Sysname] segment-routing

[Sysname-segment-routing] traffic-engineering

[Sysname-sr-te] policy 1

[Sysname-sr-te-policy-1] bfd echo enable source-ip 1.2.3.4

Related commands

bfd echo-source-ip (High Availability Command Reference)

display segment-routing te bfd

sr-policy bfd echo

bfd trigger path-down

Use bfd trigger path-down to enable BFD session down events to trigger SR-MPLS TE policy path reselection.

Use undo bfd trigger path-down to restore the default.

Syntax

bfd trigger path-down { disable | enable }

undo bfd trigger path-down

Default

This feature is not configured for an SR-MPLS TE policy, and the configuration in SR TE view applies.

Views

SR-MPLS TE policy view

Predefined user roles

network-admin

Parameters

disable: Disables BFD session down events from triggering SR-MPLS TE policy path reselection.

enable: Enables BFD session down events to trigger SR-MPLS TE policy path reselection.

Usage guidelines

By default, when an SR-MPLS TE policy contains multiple valid candidate paths:

· If hot standby is not enabled, BFD/SBFD detects all the SID lists of the optimal candidate path and establishes a BFD/SBFD session for each of the SID lists. When all the BFD/SBFD sessions are down, the SR-MPLS TE policy does not reselect a candidate path and packets are no longer forwarded through the SR-MPLS TE policy.

· If hot standby is enabled, BFD/SBFD detects all the SID lists of the main and backup candidate paths and establishes a BFD/SBFD session for each of the SID lists.

¡ When all the BFD/SBFD sessions for the main path are down, the SR-MPLS TE policy switches traffic to the backup path and does not reselect a candidate path.

¡ When all the BFD/SBFD sessions for the main and backup paths are down, the SR-MPLS TE policy does not reselect a candidate path and packets are no longer forwarded through the SR-MPLS TE policy.

After you enable this feature (by executing the bfd trigger path-down enable command) for an SR-MPLS TE policy that contains multiple valid candidate paths:

· If hot standby is not enabled, BFD/SBFD detects all the SID lists of the optimal candidate path and establishes a BFD/SBFD session for each of the SID lists. When all the BFD/SBFD sessions are down, the SR-MPLS TE policy reselects a candidate path and uses the new candidate path to forward packets. If no valid candidate path is available during the resection, packets cannot be forwarded through the SR-MPLS TE policy.

· If hot standby is enabled, BFD/SBFD detects all the SID lists of the main and backup candidate paths and establishes a BFD/SBFD session for each of the SID lists.

¡ When all the BFD/SBFD sessions for the main path are down, the SR-MPLS TE policy switches traffic to the backup path and reselects the main and backup paths.

¡ When all the BFD/SBFD sessions for the main and backup paths are down, the SR-MPLS TE policy reselects the main and backup paths and forwards packets through the new main path.

¡ If no valid candidate path is available during the resection, packets cannot be forwarded through the SR-MPLS TE policy.

Before you enable this feature for an SR-MPLS TE policy, create an SBFD session for the policy first.

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

Examples

# Enable BFD session down events to trigger candidate path reselection for SR-MPLS TE policy a1.

<Sysname> system-view

[Sysname] segment-routing

[Sysname-segment-routing] traffic-engineering

[Sysname-sr-te] policy a1

[Sysname-sr-te-policy-a1] bfd trigger path-down enable

Related commands

sbfd

sr-policy bfd trigger path-down enable

sr-policy sbfd enable

binding-sid

Use binding-sid to configure an BSID for an SR-MPLS TE policy.

Use undo binding-sid to delete the BSID.

Syntax

binding-sid mpls mpls-label

undo binding-sid

Default

No BSID is configured for an SR-MPLS TE policy.

Views

SR-MPLS TE policy view

Predefined user roles

network-admin

Parameters

mpls mpls-label: Specifies the BSID value, which is an MPLS label value in the range of 16 to 1048575.

Usage guidelines

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

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

If you configure an MPLS label as the BSID but the label is not in the range of the SRGB or SRLB or is already used by a protocol, the configuration does not take effect. For more information about SRGB or SRLB, see MPLS SR configuration in Segment Routing Configuration Guide.

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

The candidate paths of the same SR-MPLS TE policy have the same BSID.

Examples

# Set the BSID of SR-MPLS TE policy srpolicy to 82000.

<Sysname> system-view

[Sysname] segment-routing

[Sysname-segment-routing] traffic-engineering

[Sysname-sr-te] policy srpolicy

[Sysname-sr-te-policy-srpolicy] binding-sid mpls 82000

Related commands

color end-point

candidate-paths

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

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

Syntax

candidate-paths

undo candidate-paths

Default

The candidate path view for an SR-MPLS TE policy does not exist.

Views

SR-MPLS TE policy view

Predefined user roles

network-admin

Examples

# Create the SR-MPLS TE policy candidate paths instance and enter its view.

<Sysname> system-view

[Sysname] segment-routing

[Sysname-segment-routing] traffic-engineering

[Sysname-sr-te] policy srpolicy

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

[Sysname-sr-te-policy-srpolicy-path]

color end-point

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

Use undo color to delete the color and endpoint settings of an SR-MPLS TE policy.

Syntax

color color-value end-point { ipv4 ipv4-address | ipv6 ipv6-address }

undo color

Default

The color and endpoint attributes of an SR-MPLS TE policy are not configured.

Views

SR-MPLS TE policy view

Predefined user roles

network-admin

Parameters

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

ipv4 ipv4-address: Specifies the endpoint IPv4 address.

ipv6 ipv6-address: Specifies the endpoint IPv6 address.

Usage guidelines

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

Different SR-MPLS TE policies cannot have the same color and the same endpoint IP address.

An SR-MPLS TE policy and an SRv6 TE policy cannot have the same color, endpoint IPv6 address, and candidate path preferences.

Examples

# Configure the color as 20 and endpoint IP address as 10.0.0.1 for SR-MPLS TE policy srpolicy.

<Sysname> system-view

[Sysname] segment-routing

[Sysname-segment-routing] traffic-engineering

[Sysname-sr-te] policy srpolicy

[Sysname-sr-te-policy-srpolicy] color 20 end-point ipv4 10.0.0.1

Related commands

binding-sid

color match dscp

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

Use undo color match dscp to delete color-to-DSCP mappings for the SR-MPLS 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 SR-MPLS TE policy group.

Views

SR-MPLS TE policy group view

Predefined user roles

network-admin

Parameters

color-value: Specifies the color attribute value, 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 the value for the dscp-value1 argument.

default: Specifies a default color-to-DSCP mapping. Packets that do not match any mappings are steered to the default SR-MPLS TE policy for forwarding.

Usage guidelines

You can map the color values of only valid SR-MPLS TE policies to DSCP values.

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

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

If no default SR-MPLS TE policy is configured for a specific address family in a SR-MPLS TE policy group, the following conditions exist:

· If color-to-DSCP mappings are configured, the packets that fail to match any SR-MPLS TE policies are steered to the SR-MPLS TE policy associated with the smallest DSCP value.

· If all packets fail to match an SR-MPLS TE policy (for example, because no color-to-DSCP mappings are configured), the packets processed as follows:

¡ The packets are steered to the default SR-MPLS TE policy of the other address family.

¡ If neither address family is configured with the default SR-MPLS TE policy, the packets are steered to the SR-MPLS TE policy associated with the smallest DSCP value in the current address family.

Examples

# Map DSCP value 30 to color value 20 for SR-MPLS TE policy group 10 so that IPv4 packets with a matching DSCP value are steered to the associated SR-MPLS TE policy.

<Sysname> system-view

[Sysname] segment-routing

[Sysname-segment-routing] traffic-engineering

[Sysname-sr-te] policy-group 10

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

constraints

Use constraints to create SR-MPLS TE policy constraints and enter constraints view, or enter the view of the existing SR-MPLS TE policy constraints.

Use undo constraints to delete the SR-MPLS TE policy constraints view and all configurations in the view.

Syntax

constraints

undo constraints

Default

No SR-MPLS TE policy constraints exist.

Views

SR-MPLS TE policy preference view

Predefined user roles

network-admin

Usage guidelines

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

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

Examples

# Create SR-MPLS TE policy constraints and enter constraints 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]

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

Use default-color to configure a default color value for public route recursion to an SR-MPLS 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: Specifies a default color value in the range of 0 to 4294967295.

Usage guidelines

The local PE uses the default color value to match an SR-MPLS 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 SR-MPLS TE policy traffic steering. It is 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 SR-MPLS 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 unicast address family view)

Use default-color to configure a default color value for L3VPN route recursion to an SR-MPLS 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 unicast address family view

VPN instance IPv6 unicast address family view

Predefined user roles

network-admin

Parameters

color-value: Specifies a 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 all L3VPN services (including EVPN L3VPN and MPLS L3VPN) route recursion to an SR-MPLS TE policy.

Usage guidelines

The local PE uses the default color value to match an SR-MPLS 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 SR-MPLS TE policy traffic steering. It is not used in route advertisement.

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

Examples

# In IPv4 unicast address family view for VPN instance vpn1, set the default color to 100 for EVPN L3VPN route recursion to an SR-MPLS 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

Use delete-delay to configure the delay timer for deleting SR-MPLS TE policies generated by ODN templates.

Use undo delete-delay to restore the default.

Syntax

delete-delay delay-time

undo delete-delay

Default

The delay timer for deleting SR-MPLS TE policies generated by ODN templates is 180000 milliseconds.

Views

SR-TE-ODN view

Predefined user roles

network-admin

Parameters

delay-time: Specifies the deletion delay timer in the range of 0 to 600000 milliseconds. A value of 0 means that the SR-MPLS TE policies generated by ODN templates are deleted immediately.

Usage guidelines

Deleting a BGP route also deletes the SR-MPLS TE policy automatically generated by ODN based on the BGP route. This might result in loss of packets forwarded through the BGP route. To avoid this issue, configure a delay timer for deleting the SR-MPLS TE policy. This configuration enables the device to delete the SR-MPLS TE policy when it has calculated a new forwarding path.

Examples

# Configure the delay timer as 300000 milliseconds for deleting SR-MPLS TE policies generated by ODN templates.

<Sysname> system-view

[Sysname] segment-routing

[Sysname-segment-routing] traffic-engineering

[Sysname-sr-te] on-demand color 1

[Sysname-sr-te-odn-1] delete-delay 30000

display bgp routing-table ipv4 sr-policy

Use display bgp routing-table ipv4 sr-policy to display route information of an BGP IPv4 SR-MPLS TE policy.

Syntax

display bgp [ instance instance-name ] routing-table ipv4 sr-policy [ sr-policy-prefix [ advertise-info | as-path | cluster-list | community | ext-community ] | { color color-value | end-point ipv4 ipv4-address } * | peer ipv4-address { advertised-routes | received-routes } [ statistics ] [ color color-value | end-point ipv4 ipv4-address ] * | statistics [ color color-value | end-point ipv4 ipv4-address ] * ]

display bgp [ instance instance-name ] routing-table ipv4 sr-policy [ statistics ] community [ community-number&<1-32> | aa:nn&<1-32> ] [ internet | no-advertise | no-export | no-export-subconfed ] [ whole-match ]

display bgp [ instance instance-name ] routing-table ipv4 sr-policy [ statistics ] community-list { basic-community-list-number | comm-list-name | adv-community-list-number } [ whole-match ]

display bgp [ instance instance-name ] routing-table ipv4 sr-policy [ statistics ] ext-community [ bandwidth link-bandwidth-value | color color | rt route-target | soo site-of-origin ]&<1-32> [ whole-match ]

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 IPv4 SR policy route prefix, which is a case-insensitive string of 1 to 512 characters in the format of SR policy route/mask length.

color color-value: Specifies the color of a BGP IPv4 SR policy route, in the range of 0 to 4294967295.

end-point ipv4 ip-address: Specifies the endpoint IPv4 address of a BGP IPv4 SR policy route.

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

as-path: Specifies the AS_PATH attribute information of the specified BGP IPv4 SR policy route.

cluster-list: Specifies the cluster ID list attribute information of the specified BGP IPv4 SR policy route.

community: Specifies the community attribute information of the specified BGP IPv4 SR policy route or the BGP IPv4 SR policy route information matching the specified community number.

ext-community: Specifies the extended community attribute information of the specified BGP IPv4 SR policy route or the BGP IPv4 SR policy route information matching the specified extended community attribute.

peer ipv4-address: Specifies a peer by its IP address.

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

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

statistics: Displays route statistics.

community-number&<1-32>: Specifies a list of up to 32 community sequence numbers. The value range for the community-number argument is 1 to 4294967295.

aa:nn&<1-32>: Specifies a list of up to 32 community numbers. The value range for the aa and nn arguments is 0 to 65535.

internet: Specifies the Internet community attribute. By default, all routes belong to the Internet community. Routes with this attribute can be advertised to all BGP peers.

no-advertise: Specifies the NO_ADVERTISE community attribute. Routes with this attribute cannot be advertised to other BGP peers.

no-export: Specifies the NO_EXPORT community attribute. Routes with this attribute cannot be advertised out of the local AS or out of the local confederation, but can be advertised to other sub-ASs in the confederation.

no-export-subconfed: Specifies the NO_EXPORT_SUBCONFED community attribute. Routes with this attribute cannot be advertised out of the local AS or other sub-ASs in the local confederation.

whole-match: Displays routes exactly matching the specified community list, community number, or extended community attribute. If you do not specify this keyword, the command displays routes whose community list, community number, or extended community attribute include the specified community list, community number, or extended community attribute.

community-list: Displays BGP IPv4 SR policy routes that match a community list.

basic-community-list-number: Specifies a basic community list by its number in the range of 1 to 99.

comm-list-name: Specifies a community list by its name, a case-sensitive string of 1 to 63 characters.

adv-community-list-number: Specifies an advanced community list by its number in the range of 100 to 199.

bandwidth link-bandwidth-value: Specifies a link bandwidth extended community attribute, a string of 3 to 16 characters, in the format of 16-bit AS number:32-bit user-defined number. For example, 100:3. The AS number is in the range of 0 to 65535, and the user-defined number is in the range of 0 to 4294967295.

color color-value: Specifies the color extended attribute, a string of 4 to 13 characters, in the format of Color-Only (CO) flag:color-value. For example: 10:3. The CO flag is a binary value in the range of 00 to 11, and the color value is in the range of 0 to 4294967295.

rt route-target: Specifies an RT, a string of 3 to 24 characters.

soo site-of-origin: Specifies the SoO attribute, a string of 3 to 24 characters. The SoO attribute has the following formats:

An RT or SoO has the following formats:

· 16-bit AS number:32-bit user-defined number. For example, 101:3. The AS number is in the range of 0 to 65535, and the user-defined number is in the range of 0 to 4294967295.

· 32-bit IP address:16-bit user-defined number. For example, 192.168.122.15:1. The user-defined number is in the range of 0 to 65535.

· 32-bit AS number:16-bit user-defined number. For example, 70000:1. The AS number is in the range of 65536 to 4294967295, and the user-defined number is in the range of 0 to 65535.

· 32-bit IP address/mask length:16-bit user-defined number. For example, 192.168.122.15/24:1.

· 32-bit dotted AS number:16-bit user-defined number. For example, 65535.65535:1.

&<1-32>: Indicates the argument before it can be entered up to 32 times.

Usage guidelines

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

If you do not specify the community-number, aa:nn, internet, no-advertise, no-export, or no-export-subconfed parameter, this command displays BGP IPv4 SR policy routes that carry any community attribute. In addition, the whole-match keyword does not take effect.

If you do not specify the bandwidth, color, rt, or soo keyword, this command displays BGP IPv4 SR policy routes that carry any extended community attribute. In addition, the whole-match keyword does not take effect.

Examples

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

<Sysname> display bgp routing-table ipv4 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 : [10][1][9.9.9.9]/96

NextHop : 2.1.1.2 LocPrf : 100

PrefVal : 0 OutLabel : NULL

MED : 0

Path/Ogn: i

# Display information about BGP IPv4 SR policy routes carrying community attributes.

<Sysname> display bgp routing-table ipv4 sr-policy community

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 : [10][1][9.9.9.9]/96

NextHop : 2.1.1.2 LocPrf : 100

PrefVal : 0 OutLabel : NULL

MED : 0

Community: <1:2>

# Display information about BGP IPv4 SR policy routes carrying extended community attributes.

<Sysname> display bgp routing-table ipv4 sr-policy community

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 : [10][1][9.9.9.9]/96

NextHop : 2.1.1.2 LocPrf : 100

PrefVal : 0 OutLabel : NULL

MED : 0

Ext-Community: <CO-Flag 1:2>

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 IPv4 SR policy route, comprised of the following elements: · SR-MPLS TE policy candidate path preference. · SR-MPLS TE policy color attribute value. · Endpoint IP address.
NextHop	Next hop IP address.
LocPrf	Local preference value.
PrefVal	Preferred value of the route.
OutLabel	Outgoing label 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.
Community	Community attribute value.
Ext-Community	Extended community attribute value.

‌

# Display detailed information about BGP IPv4 SR policy route [102][2][5.6.7.8]/96.

<Sysname> display bgp routing-table ipv4 sr-policy [102][2][5.6.7.8]/96

BGP local router ID: 2.2.2.2

Local AS number: 1

Paths: 1 available, 1 best

BGP routing table information of [102][2][5.6.7.8]:

From : 3.1.1.2 (10.11.113.29)

Rely nexthop : 0.0.0.0

Original nexthop: 3.1.1.2

Route age : 00h33m33s

OutLabel : NULL

RxPathID : 0x0

TxPathID : 0x0

AS-path : 2

Origin : igp

Attribute value : MED 0, pref-val 0

State : valid, external, best

IP precedence : N/A

QoS local ID : N/A

Traffic index : N/A

Tunnel encapsulation info:

Type: 15 (SR Policy)

Preference: 102

PolicyName: 2

Path: 1

Weight: 1

SIDs: {3}

# Display community attribute information for BGP IPv4 SR policy route [102][2][5.6.7.8]/96.

<Sysname> display bgp routing-table ipv4 sr-policy [102][2][5.6.7.8]/96 community

BGP local router ID: 1.1.1.9

Local AS number: 100

Paths: 1 available, 1 best

BGP routing table information of [102][2][5.6.7.8]/96:

Community: no-export

# Display extended community attribute information for BGP IPv4 SR policy route [102][2][5.6.7.8]/96.

<Sysname> display bgp routing-table ipv4 sr-policy [102][2][5.6.7.8]/96 ext-community

BGP local router ID: 1.1.1.9

Local AS number: 100

Paths: 1 available, 1 best

BGP routing table information of [102][2][5.6.7.8]/96:

Ext-Community: <RT: 1:1>

# Display AS_PATH attribute information for BGP IPv4 SR policy route [102][2][5.6.7.8]/96.

<Sysname> display bgp routing-table ipv4 sr-policy [102][2][5.6.7.8]/96 as-path

BGP local router ID: 1.1.1.9

Local AS number: 100

Paths: 1 available, 1 best

BGP routing table information of [102][2][5.6.7.8]/96:

As-path: 100

# Display cluster ID list attribute information for BGP IPv4 SR policy route [102][2][5.6.7.8]/96.

<Sysname> display bgp routing-table ipv4 sr-policy [102][2][5.6.7.8]/96 cluster-list

BGP local router ID: 1.1.1.9

Local AS number: 100

Paths: 1 available, 1 best

BGP routing table information of [102][2][5.6.7.8]/96:

Cluster list: 80

Table 2 Command output

Field	Description
Paths	Route information: · available—Number of valid routes. · best—Number of optimal routes.
BGP routing table information of [102][2][5.6.7.8]	Information of the BGP IPv4 SR policy route [102][2][5.6.7.8], where: · [102] is the SR-MPLS TE policy candidate path preference · [2] is the SR-MPLS TE policy color attribute value. · [5.6.7.8] is the endpoint IP address.
From	IP address of the BGP peer that advertised the route.
Rely Nexthop	Recursive nexthop IP address. If no next hop is found by route recursion, this field displays not resolved.
Original nexthop	Original nexthop IP address. If the route was obtained from a BGP update message, the original next hop is the nexthop IP address in the message.
Route age	Time elapsed since the last update for the route.
OutLabel	Outgoing label of the route.
RxPathID	Received Add-Path ID of the route.
TxPathID	Advertised Add-Path ID of the route.
AS-path	AS_PATH attribute of the route.
Community	Community attribute of the route.
Ext-Community	Extended community attribute of the route.
Cluster list	Cluster ID list attribute of the route.
Origin	Origin of the route: · igp—Originated in the AS. · egp—Learned through an EGP. · incomplete—Unknown origin.
Attribute value	BGP path attributes: · MED—MED value. · localpref—Local preference value. · pref-val—Preferred value. · pre—Protocol preference.
State	Current state of the route. Options include: · valid—Valid route. · internal—Internal route. · external—External route. · local—Locally generated route. · synchronize—Synchronized route. · best—Optimal route. · delay—Delayed route. The route will be delayed for optimal route selection. This value is available only in detailed information of the route. · not preferred for reason—Reason why the route is not selected as the optimal route. For more information, see Table 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-MPLS TE policy.
Preference	Candidate path preference.
PolicyName	Name of the SR-MPLS TE policy.
Path	Candidate path.
Weight	Weight of the SID list.
SIDs	List of SIDs.

‌

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 IPv4 SR policy route [102][2][5.6.7.8]/96.

<Sysname> display bgp routing-table ipv4 sr-policy [102][2][5.6.7.8]/96 advertise-info

BGP local router ID: 2.2.2.2

Local AS number: 1

Paths: 1 best

BGP routing table information of [102][2][5.6.7.8]/96(TxPathID:0):

Advertised to peers (2 in total):

2.1.1.2

3.3.3.3

Table 4 Command output

Field	Description
Paths	Number of optimal paths to reach the destination network.
BGP routing table information of [102][2][5.6.7.8]/96(TxPathID:0)	Advertisement information about the BGP IPv4 SR policy route [102][2][5.6.7.8]/96. 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 IPv4 SR policy routes advertised to peer 2.1.1.2.

<Sysname> display bgp routing-table ipv4 sr-policy peer 10.2.1.2 advertised-routes statistics

Advertised routes total: 2

# Display statistics about the BGP IPv4 SR policy routes received from peer 2.1.1.2.

<Sysname> display bgp routing-table ipv4 sr-policy peer 2.1.1.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 IPv4 SR policy routes.

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

Total number of routes: 3

# Display statistics about BGP IPv4 SR policy routes carrying community attributes.

<Sysname> display bgp routing-table ipv4 sr-policy statistics community

Total number of routes: 3

display pce segment-routing policy database

Use display pce segment-routing policy database to display SR-MPLS TE policy information stored in the PCE database.

Syntax

display pce segment-routing policy database [ color color-value endpoint { ipv4 ipv4-address | ipv6 ipv6-address } | policyname policy-name ] [ verbose ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

color color-value end-point { ipv4 ipv4-address | ipv6 ipv6-address }: Specifies an SR-MPLS TE policy by its color attribute value, end-point IPv4 address, and end-point IPv6 address. The value range for the color attribute value is 0 to 4294967295.

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

verbose: Displays detailed SR-MPLS TE policy information in the PCE database. If you do not specify this keyword, the command displays brief SR-MPLS TE policy information in the PCE database.

Usage guidelines

If you do not specify the color color-value endpoint option or the policyname policy-name option, this command displays information about all SR-MPLS TE policies in the PCE database.

Examples

# Display brief SR-MPLS TE policy information in the PCE database.

<Sysname> display pce segment-routing policy database

Color Endpoint PLSP-ID Preference Delegated address State

1 2.2.2.2 262145 100 192.168.56.1 Up

2 2.2.2.2 262146 10 192.168.56.2 Up

Table 6 Command output

Field	Description
Color	Color attribute value of the SR-MPLS TE policy.
Endpoint	Endpoint IPv4 address of the SR-MPLS TE policy.
PLSP-ID	PCEP LSP ID of the SR-MPLS TE policy. It uniquely identifies a candidate path and is assigned by the PCC.
Preference	Preference of the candidate path of the SR-MPLS TE policy.
Delegated address	IP address of the delegated PCE. If the candidate path is not delegated or the delegation fails, this field displays a hyphen (-).
State	Candidate path state: · Up—The candidate path has been established. · Down—The candidate path has not been established or the establishment fails.

‌

# Display detailed SR-MPLS TE policy information in the PCE database.

<Sysname> display pce segment-routing policy database verbose

PLSP ID: 65536

Color: 10 Endpoint: 2.2.2.2

Policy name: p1

Association ID: 1 Association type: SRPAG

Association source: 1.1.1.1

Candidate path ID:

Protocol origin: CLI BGP instance: 0

Originator ASN: 0 Node address: 0.0.0.0

Discriminator: 10

Candidate path name: -

Symbolic path name: 10_2.2.2.2._10

Binding SID: 15000

IPv6 Binding SID: -

PCE setup type: Segment Routing

SRP ID: 0

Delegatable: Yes Delegated address: -

PCE initiated: No Speaker address: -

Path role: Primary

Operational state: Up PCEP status: State reverted

Segment list ID: 3

SID list state: Up Path weight: 1

SR-EROs: 1

SID type: SID without NAI Strict

SID: 16020 NAI: N/A

SR-RROs: 1

SID type: SID without NAI Strict

SID: 16020 NAI: N/A

Table 7 Command output

Field	Description
PLSP ID	The PLSP ID uniquely identifies a candidate path.
Policy name	Name of the SR-MPLS TE policy.
Color	Color attribute value of the SR-MPLS TE policy.
Endpoint	Endpoint IPv4 address of the SR-MPLS TE policy.
Association ID	Association group ID of the SR-MPLS TE policy. As defined in draft-ietf-pce-segment-routing-policy-cp, this ID is 1.
Association type	Association group type of the SR-MPLS TE policy. As defined in draft-ietf-pce-segment-routing-policy-cp, this type value is 6, which represents the SRPAG type.
Association source	Association group source address, which is the source IPv4 or IPv6 address of the SR-MPLS TE policy.
Candidate path ID	Candidate path ID information.
Protocol Original	Candidate path origin: · PCE—PCE created. · BGP—BGP created. · CLI—Command created.
BGP Instance	Number of the BGP instance that is created by BGP. This field displays a hyphen (-) if the candidate path is not created by BGP.
Originator ASN	AS number. A value of 0 means that the device has not obtained SR-MPLS TE policy information from a BGP peer.
Node address	BGP node address. This field displays the router ID of the BGP peer when the SR-MPLS TE policy information was obtained from a BGP peer, and it displays 0.0.0.0 when the SR-MPLS TE policy information was obtained by using other methods.
Discriminator	Discriminator of the candidate path.
Candidate path name	Name of the candidate path.
Symbolic path name	PCEP-defined symbolic-name of the candidate path.
Binding SID	BSID of the SR-MPLS TE policy. If the SR-MPLS TE policy does not have a BSID, this field displays a hyphen (-).
IPv6 binding SID	IPv6 BSID of the SR-MPLS TE policy. If the SR-MPLS TE policy does not have an IPv6 BSID, this field displays a hyphen (-).
PCE setup type	Type of the protocol that created the candidate path. The value can be Segment-Routing, which represents SR-MPLS TE policy.
SRP ID	ID of the stateful PCE request parameter.
Delegatable	Whether the candidate path is delegable: Yes or No.
Delegated address	IP address of the delegated PCE. If the candidate path is not delegated or the delegation fails, this field displays a hyphen (-).
PCE initiated	Whether the candidate path is initiated by PCE: Yes or No.
Speaker address	IP address of the PCE.
Path role	Role of the candidate path: · Primary. · Backup. · Other.
Operational state	Candidate path state: · Up—The candidate path has been established. · Down—The candidate path has not been established or the establishment fails.
PCEP status	Candidate path delegation state: · Delegated—The candidate path has been delegated to the PCE. · Updated—The PCE has updated the candidate path. · Redelegating—The device is redelegating the candidate path to another PCE. · Report-only—The device has only reported the candidate path's information to the PCE but it does not delegate the candidate path to the PCE. · State reverted—The candidate path has restored to the state prior to the delegation.
Segment list ID	ID of the SID list used by the candidate path.
SID list state	State of the SID list: · Up—The SID list has been established. · Down—The SID list has not been established or the establishment fails.
Path weight	Load sharing weight of the SID list.
SR-EROs	Number of Segment Routing Explicit Route Objects (SR-EROs) and the SR-ERO information.
SID type	SID and NAI information contained in the ERO or RRO. The value can be SID without NAI.
Strict	The current node is a strict node.
SID	SID of the node.
NAI	This field is not supported in the current software version. Node or Adjacency Identifier.
SR-RROs	Number of Segment Routing Record Route Objects (SR-RROs) and the SR-RRO information.

‌

display pce segment-routing policy initiate-cache

Use display pce segment-routing policy initiate-cache to display information about the SR-MPLS TE policy Initiate messages cached in the PCE process.

Syntax

display pce segment-routing policy initiate-cache

Views

Any view

Predefined user roles

network-admin

network-operator

Usage guidelines

After a PCE and a PCC establishes an active-stateful PCEP session, the PCE sends Initiate messages to the PCC to create candidate paths. This command displays the cached unprocessed Initiate messages.

Examples

# Displays SR-MPLS TE policy Initiate messages cached in the PCE process.

<Sysname> display pce segment-routing policy initiate-cache

Policy name: 111111

SR policy association group ID: 1

Color: 17

Endpoint: 2.2.2.2

Preference: 17

Originator: -

Binding SID: 15001

SRP ID: 1 PCE initiated: Yes

Operational state: Down

Candiate path/0: path state: Down

SR-EROs: 1

SID type: SID without NAI Strict

SID: 16030 NAI: N/A

Table 8 Command output

Field	Description
Policy name	Name of an SR-MPLS TE policy. If an SR-MPLS TE policy does not have a name, this field displays a hyphen (-).
SR policy association group ID	Association group ID of the SR-MPLS TE policy.
Color	Color attribute value of the SR-MPLS TE policy.
Endpoint	Endpoint IPv4 address of the SR-MPLS TE policy.
Preference	Preference of the candidate path of the SR-MPLS TE policy.
Originator	BGP node address. This field displays the router ID of the BGP peer when the SR-MPLS TE policy information was obtained from a BGP peer, and it displays 0.0.0.0 when the SR-MPLS TE policy information was obtained by using other methods.
Binding SID	BSID of the SR-MPLS TE policy. If the SR-MPLS TE policy does not have a BSID, this field displays a hyphen (-).
SRP ID	ID of the stateful PCE request parameter.
PCE initiated	Whether the candidate path is initiated by PCE: Yes or No.
Operational state	Candidate path state: · Up—The candidate path has been established. · Down—The candidate path has not been established or the establishment fails.
Candidate path/path-id	SID list used by the candidate path. The path-id is the ID of the SID list.
path state	State of the SID list: · Up—The SID list has been established. · Down—The SID list has not been established or the establishment fails.
SR-EROs	Number of SR-EROs and the SR-ERO information.
SID Type	SID and NAI information contained in the ERO or RRO. The value can be SID without NAI.
Strict	The current node is a strict node.
SID	SID of the node.
NAI	This field is not supported in the current software version. Node or Adjacency Identifier.

‌

display segment-routing te bfd

Use display segment-routing te bfd to display BFD information for SR-MPLS TE policies.

Syntax

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

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

down: Displays BFD information for SR-MPLS TE policies in down state.

policy: Displays BFD information for the specified SR-MPLS TE policy.

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

end-point { ipv4 ipv4-address | ipv6 ipv6-address }: Specifies the IPv4 or IPv6 address of the end-point of an SR-MPLS TE policy.

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

up: Displays BFD information for SR-MPLS TE policies in up state.

Usage guidelines

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

Examples

# Display BFD information for all SR-MPLS TE policies.

<Sysname> display segment-routing te bfd

Color: 10

Endpoint: 1.2.3.4

BSID: 15000

Policy name: p1

State: Up

NID: 2149580801

BFD type: ECHO

Source IP: 1.2.3.4

Source-address: 2::2

State: Up

Timer: 37

Template name: abc

Table 9 Command output

Field	Description
Color	Color attribute value of an SR-MPLS TE policy.
Endpoint	End-point IP address of the SR-MPLS TE policy.
Policy name	Name of the SR-MPLS TE policy.
State	State of the SR-MPLS TE policy: · Up · Down
NID	Forwarding entry index for an SID list.
BFD type	The current software version supports only the BFD echo mode.
Source IP	Source IP address of the BFD session.
Source-address	Valid source address for BFD packets configured using the source-address command. This field displays a hyphen (-) if the source address is not configured or the configured source address does not take effect. The specified source address does not take effect if it is an IPv4 source address specified in an IPv6 network or an IPv6 address specified in an IPv4 network.
State	BFD session state: · Up · Down · Delete
Timer	BFD session timer, in seconds.
Template name	Name of the echo mode BFD template. If no template is specified, this field display a hyphen (-).

‌

display segment-routing te database

Use display segment-routing te database to display SR-MPLS TE policy database information.

Syntax

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

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

link: Displays the link information reported by the IGP to the SR-MPLS TE policy database.

node: Displays the node information reported by the IGP to the SR-MPLS TE policy database.

prefix: Displays the prefix information reported by the IGP to the SR-MPLS TE policy database.

Usage guidelines

If you do not specify a parameter, this command displays all information reported by the IGP to the SR-MPLS TE policy database.

Examples

# Display link information reported by the IGP to the SR-MPLS TE policy database.

<Sysname> display segment-routing te database link

Link-state information: Link, count: 2

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

IS-IS P2P:

Local node: System ID 0000.0000.0011.00, IS level: 1

Remote node: System ID 0000.0000.0012.00, IS level: 1

Local address: 10.0.0.1

Remote address: 10.0.0.2

Topology ID: 0

Link source: ProcID 1, TLV type: wide-nbr, FragID: 0x0

TE local router ID: 1.1.1.1

TE remote router ID: 2.2.2.2

TE administrative group: 0x80000000

TE maximum bandwidth (kbits/sec): 1000

TE maximum reservable bandwidth (kbits/sec): 1000

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

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

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

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

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

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

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

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

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

SRLG:11

ADJ-SID: 2303, Weight: 0

SID flags (F/B/V/L/S): 0/0/1/1/0

Flag: 0, Average delay(us): 1000

Flag: 0, Min delay(us): 500, Max delay(us): 1500

Delay variation(us): 400

Remaining Bandwidth (bytes/sec): 100

Avaliable Bandwidth (bytes/sec): 100

Utilized Bandwidth (bytes/sec): 100

SR/SRv6 link maximum SID depths:

MPLS MSD : 5

Application Specific Link Attributes

SA-Length: 1, UDA-Length: 1

Standard Applications: 0x10 Flex-Algo

User Defined Applications: 0x10 Flex-Algo

Ext Admin Group:

0x00000004 0x00000000 0x00000000 0x00000000

0x00000000 0x00000000 0x00000000 0x80000000

TE metric: 10

TE administrative group: 0x80000000

TE maximum bandwidth (kbits/sec): 1000

TE maximum reservable bandwidth (kbits/sec): 1000

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

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

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

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

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

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

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

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

Flag: 0, Average delay(us): 1000

Flag: 0, Min delay(us): 500, Max delay(us): 1500

Delay variation(us): 400

Remaining bandwidth (bytes/sec): 100

Avaliable bandwidth (bytes/sec): 100

Utilized bandwidth (bytes/sec): 100

SRLG: 11

SRv6 End.X SID

SID : 1111::104

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 : 1111::105

Function type : End.X with PSP

Algorithm : 0

Weight : 0

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

IGP metric: 0

Table 10 Command output

Field	Description
Link-state information: Link	Link information.
count	Number of links reported by the IGP to the SR-MPLS 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.
Link source	Advertisement source of the link.
ProcID	IS-IS process ID.
FragID	Fragment ID of the packet.
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.

‌

# Display node information reported by the IGP to the SR-MPLS TE policy database.

<Sysname> display segment-routing te database node

Link-state information: Node, count: 3

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

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

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

Node topology ID: 0

Node flag: 0x1

Node name: isis1

IS-IS area: 00.0000

TE local router ID: 1.1.1.1

Segment routing

Algorithm: 0x0

Algorithm: 0x80

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

SR flags (I/V/H): 1/0/0

SRGB base: 16000 SRGB range: 8001

SRLB flags: 0x00

SRLB base: 16000 SRLB range: 8000

Flex-Algo: 128

Priority: 254

MetricType: 1

MFlag: 0

SRPLS_NODE_ATTR_FLEXALGO ExAny

0x00000002

SRPLS_NODE_ATTR_FLEXALGO InAll

0x00000004

SRPLS_NODE_ATTR_FLEXALGO InAny

0x00000000 0x00000000 0x00000000 0x00000000

0x00000000 0x00000000 0x00000000 0x80000000

SRLGInfo: 1

Table 11 Command output

Field	Description
Link-state information: Node	Node information.
count	Number of nodes reported by the IGP to the SR-MPLS 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.
FragID	Fragment ID of the packet.
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	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.
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.
SR flags	Segment routing capabilities sub-TLV information: · I—MPLS IPv4 flag. If set, it indicates that the node can process MPLS SR encapsulated IPv4 packets on all interfaces. · V—MPLS IPv6 flag. If set, it indicates that the node can process MPLS SR encapsulated IPv6 packets on all interfaces. (This flag is not supported in the current software version.) · H—IPv6 SR flag. If set, it indicates that the node can process packets encapsulated in IPv6 SR extended SRH headers on all interfaces. (This flag is not supported in the current software version.)
SRGB base	SRGB base value, which is the minimum label value in the SRGB.
SRGB range	Number of labels in the SRGB.
SRLB flags	Segment routing local block sub-TLV information. The value is fixed at 0x00.
SRLB base	SRLB base value, which is the minimum label value in the SRLB.
SRLB range	Number of labels in the SRLB.

‌

# Display prefix information reported by the IGP to the SR-MPLS TE policy database.

<Sysname> display segment-routing te database prefix

Link-state information: Prefix, count: 11

Public instance, MT-ID: 0, IS-IS instance ID: 0, Prefix count: 11

IS-IS prefix:

Local node: System ID 0000.0000.0011.00, IS level: 1

Prefix: 1.1.1.1/32, Topology ID: 0

Prefix source: ProcID 1, TLV type: ip-extended, FragID: 0x0

Prefix metric: 0

Prefix-SID: 10 Algorithm: 0

Prefix-SID flags (R/N/P/E/V/L): 0/1/0/0/0/0

Prefix-SID: 11 Algorithm: 128

Prefix-SID flags (R/N/P/E/V/L): 0/1/0/0/0/0

Table 12 Command output

Field	Description
Link-state information: Prefix	Prefix information.
count	Number of prefixes reported by the IGP to the SR-MPLS 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.
Prefix source	Advertisement source of the prefix.
FragID	Fragment ID of the packet.
Algorithm	Algorithm associated with the prefix. Only the SPF algorithm is supported.
Prefix-SID flags (R/N/P/E/V/L)	Segment routing capabilities sub-TLV information: · R—Re-advertisement flag, set when the prefix SID has been leaked from one level to another or routes have been redistributed. · N—Node-SID flag, set when the prefix SID identifies the advertising node, that is, the prefix is a host prefix advertising a globally reachable address typically associated with a loopback address. · P—No-PHP flag, set when the penultimate hop is not allowed to pop the prefix SID. · E—Explicit null label flag, set when the upstream node must reset the prefix SID to an explicit null label. · V—Value/Index flag, set when the prefix SID is an absolute value. · L—Local/Global flag, set when the prefix SID is a locally significant prefix SID.

‌

display segment-routing te forwarding

Use display segment-routing te forwarding to display SR TE forwarding information.

Syntax

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

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

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

name policy-name: Specifies the name of an SR-MPLS TE policy, a string of 1 to 59 characters.

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

end-point { ipv4 ipv4-address | ipv6 ipv6-address }: Specifies the endpoint IPv4 or IPv6 address of an SR-MPLS TE policy.

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

Usage guidelines

To use this command to display SR TE traffic forwarding statistics, make sure SR TE traffic forwarding statistics is enabled.

Examples

# Display brief forwarding information of all SR policies.

<Sysname> display segment-routing te forwarding

Total forwarding entries: 1

Policy name/ID: p1/0

Binding SID: 15200

Policy NID: 1000

Forwarding status: Active

Main path:

Seglist Name/ID: a/1

Seglist NID: 2001

Weight: 50

Forwarding status: Active

Outgoing NID: 3012

OutLabels: 3

Interface: HGE1/0/1

NextHop: 1.2.0.2

Outgoing NID: 3210

OutLabels: 3

Interface: HGE1/0/2

NextHop: 1.2.1.2

Backup path:

Seglist Name/ID: b/1

Seglist NID: 2101

Weight: 100

Forwarding status: Active

Outgoing NID: 3560

OutLabels: 3

Interface: HGE1/0/1

NextHop: 1.2.0.2

Outgoing NID: 3958

OutLabels: 3

Interface: HGE1/0/2

NextHop: 1.2.1.2

# Display detailed forwarding information of all SR policies.

<Sysname> display segment-routing te forwarding verbose

Total forwarding entries: 1

Policy name/ID: p1/0

Binding SID: 15200

Forwarding status: Active

Policy NID: 1000

Inbound statistics:

Total octets: 1500

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 Name/ID: a/1

Seglist NID: 2001

Weight: 50

Forwarding status: Active

Outgoing NID: 3012

OutLabels: 3

Interface: HGE1/0/1

NextHop: 1.2.0.2

PathID: 1

Label stack: {16300, 16400, 16500}

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 NID: 3210

OutLabels: 3

Interface: HGE1/0/2

NextHop: 1.2.1.2

PathID: 1

Label stack: {16300, 16400, 16500}

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 Name/ID: a/1

Seglist NID: 2101

Weight: 100

Forwarding status: Active

Outgoing NID: 3560

OutLabels: 3

Interface: HGE1/0/1

NextHop: 1.2.0.2

PathID: 1

Label stack: {16300, 16400, 16500}

Outgoing NID: 3958

OutLabels: 3

Interface: HGE1/0/2

NextHop: 1.2.1.2

PathID: 1

Label stack: {16300, 16400, 16500}

Table 13 Command output

Field	Description
Policy name/ID	Name/ID of the SR-MPLS TE policy.
Binding SID	Label value of the ingress node.
Policy NID	Index of the NHLFE entry for the SR-MPLS TE policy.
Forwarding status	Forwarding status of the SR-MPLS TE policy: · Active—The SR-MPLS TE policy is available to forward traffic. · Inactive—The SR-MPLS TE policy cannot forward traffic.
Inbound statistics	Inbound traffic statistics, that is, the traffic statistics about the BSID.
Total octets	Total number of forwarded bytes.
Total packets	Total number of forwarded packets.
Erroneous packets	Number of erroneous packets.
Dropped packets	Number of dropped packets.
Input rate in last 300 seconds	Inbound traffic rate statistics in the most recent 300 seconds.
Input rate in last statistical period (20 sec)	Inbound traffic rate statistics in the most recent statistical period. The statistical period is set by the forwarding statistics interval command.
Outbound statistics	Outbound traffic statistics.
Output rate in last 300 seconds	Outbound traffic rate statistics in the most recent 300 seconds.
Output rate in last statistical period (20 sec)	Outbound traffic rate statistics in the most recent statistical period. The statistical period is set by the forwarding statistics interval command.
Output service-class	Outbound traffic rate statistics for a service class. A value of 255 indicates no service class is configured for the SR-MPLS TE policy, and the SR-MPLS TE policy has the lowest forwarding priority.
octets	Number of bytes.
packets	Number of packets.
errors	Number of erroneous packets.
dropped packets	Number of dropped packets.
Main path	Main path for traffic forwarding.
Backup path	Backup path for traffic forwarding.
Secondary backup path	Secondary backup path for traffic forwarding.
Seglist Name/ID	SID list name and ID.
Seglist NID	NHLFE entry index of the SID list.
Delay timer type	Type of the delay timer: · LSP—Timer that delays to refresh LSPs. · BFD—Timer that delays to clear the BFD/SBFD DOWN bit.
Delay time	Up delay time in milliseconds.
Remaining time	Remaining delay time for the up state.
OutLabel	Outgoing label value. If the outgoing label is invalid, this field displays a hyphen (-).
Interface	Brief name of the outgoing interface.
Nexthop	Nexthop IP address.
PathID	Path ID assigned to the SID list by the SR-MPLS TE policy.
Weight	Weight of the path.
Label stack	Stack of labels from top to bottom.

‌

display segment-routing te policy

Use display segment-routing te policy to display SR-MPLS TE policy information.

Syntax

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

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

odn: Specifies the SR-MPLS TE policies generated by ODN.

pce: Specifies the SR-MPLS TE policies whose SID lists are computed by a PCE.

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

down: Specifies the SR-MPLS TE policies in down state.

up: Specifies the SR-MPLS TE policies in up state.

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

end-point { ipv4 ipv4-address| ipv6 ipv6-address }: Specifies the endpoint IPv4 or IPv6 address of an SR-MPLS TE policy.

Usage guidelines

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

Examples

# Display information about all SR-MPLS TE policies.

<Sysname> display segment-routing te policy

Name/ID: abc/0

Color: 10

Endpoint: 4.4.4.4

Name from BGP: abc

Name from PCE:

BSID:

Mode: Explicit Type: Type_1 Request state: Succeeded

Current BSID: 15000 Explicit BSID: 15000 Dynamic BSID: -

Reference counts: 3

Flags: A/BS

Status: Up

AdminStatus: Up

Forwarding status: Active

Up time: 2019-10-25 11:16:15

Down time: 2019-10-25 11:16:00

Hot-standby: Not configured

Statistics: Not configured

Statistics by service class: Not configured

Source-address: 1.1.1.1

SBFD: Not configured

BFD echo: Not configured

Drop-upon-invalid: Disabled

BFD trigger path-down: Disabled

PolicyNID: 23068673

Service-class: -

PCE delegation: Not configured

PCE delegate report-only: Not configured

Reoptimization: Not configured

Candidate paths state: Configured

Candidate paths statistics:

CLI paths: 2 BGP paths: 0

PCEP paths: 0 ODN paths: 0

Candidate paths:

Preference : 10

CPathName: abc

ProtoOrigin: CLI Discriminator: 10

Instance ID: 0 Node address: 0.0.0.0

Originator: 0, 0.0.0.0

Optimal: Y Flags: V/A

Dynamic: Not configured

PCEP: Not configured

Explict SID list:

ID: 1 Name: abc

Weight: 1 Nid: 22020097

State: Up State(-): -

Table 14 Command output

Field	Description
Name/ID	SR-MPLS TE policy name/ID.
Color	Color attribute of the SR-MPLS TE policy.
Endpoint	Endpoint IP address of the SR-MPLS TE policy. If the endpoint is not configured, this field displays None.
Name from BGP	SR-MPLS TE policy name obtained through BGP. The SR-MPLS TE policy name is not displayed if it is not obtained.
Name from PCE	SR-MPLS TE policy name obtained through PCE. The SR-MPLS TE policy name is not displayed if it is not obtained.
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_1—MPLS label.
Request state	BSID request state: · Failed. · Succeeded.
Explicit BSID	Manually configured BSID.
Dynamic BSID	Dynamically requested BSID. If the BSID is not dynamically requested, this field displays a hyphen (-).
Request failure reason	Reason for BSID request failure: · Label conflict. · Exhausted label resources. · The LSM process not started. · The BSID is out of SRLB. This field is available only when the BSID request state is Failed.
Reference counts	Number of times that the SR-MPLS TE policy has been referenced.
Flags	SR-MPLS TE policy flags: · A—Active SR-MPLS TE policy. · C—Optimal SR-MPLS TE policy. · N—In optimal SR-MPLS TE policy selection progress. · BA—Requesting BSID. · BS—Optimal BSID. · D—Deleted SR-MPLS TE policy. · CF—Conflicted with an existing BSID. · NC—Manually configured SR-MPLS TE policy. · NB—SR-MPLS TE policy obtained from a BGP route.
Status	SR-MPLS TE policy status: · Up—Active state. · Down—Inactive state. The SRv6 TE policy is down because of a reason other than BFD or SBFD detection. · Down (BFD down)—A BFD or SBFD session detects that the forwarding paths of all SID lists in the candidate paths of the SRv6 TE policy are not available. The state of the SRv6 policy is set to down. In this state, the first next hop on the forwarding paths of all the SID lists is available. However, the subsequent paths are not available.
AdminStatus	Administrative status of the SR-MPLS TE policy: · Down—The policy is shut down by the shutdown command. · Up—The policy is not shut down by the shutdown command.
Forwarding status	Forwarding status of the SR-MPLS TE policy: · Active—The SR-MPLS TE policy is available to forward traffic. · Inactive—The SR-MPLS TE policy cannot forward traffic.
Up time	Time when the SR-MPLS TE policy came up.
Down time	Time when the SR-MPLS TE policy went down.
Hot-standby	Status of the hot standby feature: · Enabled. · Disabled. · Multilevel-backup—A secondary backup path exists. · Not configured.
Statistics	Traffic statistics status for the SR-MPLS TE policy: · Disabled. · Enabled. · Not configured.
Statistics by service class	Service class based traffic statistics status for the SR-MPLS TE policy: · Enabled. · Disabled. · Not configured.
Source-address	Source address of the SR-MPLS TE policy. If no source address is configured, this field displays None.
SBFD	Status of the SBFD feature: SBFD Enabled, SBFD Disabled, SBFD Echo Enabled, SBFD Echo Disabled, or Not configured.
Encapsulation mode	SBFD encapsulation mode: · IPv4 · IPv6 This field displays a hyphen (-) if no SBFD encapsulation mode is configured.
Proxy reflector	Status of the SBFD proxy reflector: · Enabled · Disabled This field displays a hyphen (-) if no SBFD proxy reflector is configured.
BFD echo	Echo packet mode BFD status for the SR-MPLS TE policy: · Enabled. · Disabled. · Not configured.
Source IPv4 address	Source IPv4 address of the BFD session.
Echo template name	Name of the BFD template.
Echo backup-template name	Name of the BFD template for the backup candidate path.
Template name	Name of the SBFD template.
Backup template name	Name of the SBFD template for the backup SID list.
Drop-upon-invalid	Drops traffic when the SR-MPLS TE policy becomes invalid: · Disabled. · Enabled.
BFD trigger path-down	Enables BFD session down events to trigger SR-MPLS TE policy path reselection: · Disabled. · Enabled. · Not configured.
PolicyNID	NHLFE entry index of the SR-MPLS TE policy.
Service-class	Service class value for the SR-MPLS TE policy. If the default value is used, this field displays a hyphen (-).
PCE delegation	PCE delegation state for the SR-MPLS TE policy: · Disabled. · Enabled. · Not configured.
PCE delegate report-only	Only reports SR-MPLS TE policy information without delegating the SR-MPLS TE policy to the PCE: · Disabled. · Enabled. · Not configured.
Reoptimization	Configuration status of candidate path reoptimization for the SR-MPLS TE policy: · Disabled. · Enabled. · Not configured.
Frequency	Time interval (in seconds) at which the device reoptimizes the candidate paths for the SR-MPLS TE policy.
Candidate paths status	Whether candidate paths are configured: · Configured. · Not configured.
Candidate paths statistics	Number of candidate paths.
CLI paths	Number of manually configured candidate paths.
BGP paths	Number of candidate paths obtained through BGP IPv4 SR policy routes.
PCEP paths	This field is not supported in the current software version. Number of candidate paths obtained through Path Computation Element Protocol (PCEP).
ODN paths	Number of automatically created candidate paths in the SR-MPLS TE policies created by the ODN.
Candidate paths	SR-MPLS TE policy candidate path information.
Preference	SR-MPLS TE policy candidate path preference.
CPathName	Name of the candidate path obtained through BGP routes. This field displays N/A if the candidate path name is not obtained.
ProtoOrigin	Protocol that obtained the SR-MPLS TE policy: · PCEP (not supported in the current software version). · BGP. · CLI (local configuration). · Unknown.
Discriminator	Discriminator of the SR-MPLS TE policy.
Instance ID	BGP instance ID. A value of 0 indicates that the device does not obtain SR-MPLS TE policy information from BGP peers.
Node address	BGP node address. For a manually configured SR-MPLS TE policy, the node address is 0.0.0.0. For an SR-MPLS TE policy obtained from a BGP peer, the node address is the Router ID of the BGP peer.
Originator: ASN, Peer-address	The SR-MPLS TE policy was obtained from BGP. · ASN: AS number. A value of 0 indicates that the device does not obtain the SR-MPLS TE policy from BGP. · Peer-address: BGP peer address. For a manually configured SR-MPLS TE policy, the peer address is 0.0.0.0. For an SR-MPLS TE policy obtained from a BGP peer, the peer address is the router ID of the BGP peer.
Optimal	Whether the path is the optimal path: · Y—Yes. · N—No.
Flags	Flags of the SR-MPLS TE policy candidate path: · V—Valid candidate path. · A—Active candidate path. · B—Backup candidate path. · S—Aging candidate path. · T—Secondary backup candidate path. · BN—Candidate path obtained from BGP. · PN—Candidate path obtained from PCE. · None—No candidate path.
Dynamic	Dynamically calculated SID list: · Configured. · Not configured.
PCEP	Whether PCEP is configured: · Configured. · Not configured.
Last calculation started at	Time when the most recent dynamic calculation started.
duration(s)	Duration of the most recent dynamic calculation, in seconds.
Reason for last calculation failure	Failure reason of 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. · The flexalgo 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 segment list. · Internal error.
Explict SID list	Explicit SID list in the candidate path of the SR-MPLS TE policy.
ID	SID list index.
Name	SID list name.
Weight	Weight of the SID list in the candidate path.
NID	NHLFE entry index of the SID list.
State	SID list state: · Up. · Down. · Down (BFD down)—The first next hop on the forwarding path of the SID list is available, but BFD detects that the subsequent path is not available.
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. · Address family mismatch—The BFD session cannot be established, because the source IP address of echo BFD session is in a different address family than that of the endpoint of the SR-MPLS TE policy. If SBFD or echo BFD is not configured, this field displays a hyphen (-).

‌

display segment-routing te policy last-down-reason

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

Syntax

display segment-routing te policy last-down-reason [ binding-sid bsid | color color-value end-point { ipv4 ipv4-address | ipv6 ipv6-address } | policy-name policy-name ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

binding-sid bsid: Specifies an SR-MPLS TE policy by its BSID.

color color-value end-point { ipv4 ipv4-address | ipv6 ipv6-address }: Specifies an SR-MPLS TE policy by its color attribute value and endpoint IPv4 or IPv6 address. The value range for the color attribute value is 0 to 4294967295.

policy-name policy-name: Specifies an SR-MPLS 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 SR-MPLS TE policies.

Examples

# Display information about the most recent down event for all SR-MPLS TE policies.

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

Name/ID: p1/1

Color: 10

Endpoint: 4.4.4.4

BSID: 1023

Up time: 2021-12-23 15:42:14

Down time: 2021-12-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: 2021-12-23 15:42:14

Down time: 2021-12-23 15:41:15

Down reason: No SID Out

Table 15 Command output

Field	Description
Name/ID	Name/ID of an SR-MPLS TE policy.
Color	Color attribute value of the SR-MPLS TE policy.
Endpoint	Endpoint address of the SR-MPLS 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 SR-MPLS TE policy came up.
Down time	Time when the SR-MPLS TE policy went down.
Down reason	Reason for the down event of the SR-MPLS TE policy: · Admin down—The SR-MPLS 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 SR-MPLS TE policy is being deleted. · Unknown error.
Candidate paths	Candidate path information of the SR-MPLS 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 SR-MPLS 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 output interface for the first SID—The first SID in the SID list has no outgoing interface. · Unknown error. · BFD Detect Down—The first next hop on the forwarding path of the SID list is available, but BFD detects that the subsequent path is not available.

‌

display segment-routing te policy statistics

Use display segment-routing te policy statistics to display SR-MPLS TE policy statistics.

Syntax

display segment-routing te policy statistics

Views

Any view

Predefined user roles

network-admin

network-operator

Examples

# Display SR-MPLS TE policy statistics.

<Sysname> display segment-routing te policy statistics

TE Policy Database Statistics

Total policies: 2 (0 up 2 down)

Endpoint IPv4 Configured: 2 (0 up 1 down)

Endpoint IPv6 Configured: 5 (2 up 3 down)

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

Endpoint IPv6 From BGP: 5 (Added 5 deleted 0 3 up 2 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 (0 up 1 down)

Configured: 1 (0 up 1 down)

Dynamic : 0 (0 up 0 down)

From BGP: 0 (0 up 0 down)

From PCE: 0 (0 up 0 down)

Table 16 Command output

Field	Description
TE Policy Database Statistics	SR-MPLS TE policy statistics.
Total policies	Total number of SR-MPLS TE policies: · up—Number of SR-MPLS TE policies in up state. · down—Number of SR-MPLS TE policies in down and Down (BFD down) states.
Endpoint IPv4 Configured	Number of manually configured SR-MPLS TE policies with endpoint IPv4 addresses. · up—Number of SR-MPLS TE policies in up state. · down—Number of SR-MPLS TE policies in down and Down (BFD down) states.
Endpoint IPv6 Configured	Number of manually configured SR-MPLS TE policies with endpoint IPv6 addresses. · up—Number of SR-MPLS TE policies in up state. · down—Number of SR-MPLS TE policies in down and Down (BFD down) states.
Dynamic	Number of SR-MPLS TE policies generated through dynamic calculation. · up—Number of SR-MPLS TE policies in up state. · down—Number of SR-MPLS TE policies in down and Down (BFD down) states.
Endpoint IPv4 From BGP	Number of SR-MPLS TE policies generated through ODN with endpoint IPv4 addresses. · Added—Number of BGP-added SR-MPLS TE policies. · deleted—Number of BGP-deleted SR-MPLS TE policies. · up—Number of SR-MPLS TE policies in up state. · down—Number of SR-MPLS TE policies in down and Down (BFD down) states.
Endpoint IPv6 From BGP	Number of SR-MPLS TE policies generated through ODN with endpoint IPv6 addresses. · Added—Number of BGP-added SR-MPLS TE policies. · deleted—Number of BGP-deleted SR-MPLS TE policies. · up—Number of SR-MPLS TE policies in up state. · down—Number of SR-MPLS TE policies in down and Down (BFD down) states.
From ODN	Number of SR-MPLS TE policies learned through BGP. · Added—Number of ODN-added SR-MPLS TE policies. · deleted—Number of ODN-deleted SR-MPLS TE policies. · up—Number of SR-MPLS TE policies in up state. · down—Number of SR-MPLS TE policies in down and Down (BFD down) states.
From PCE	This field is not supported in the current software version. Number of SR-MPLS TE policies generated through PCE. · Added—Number of PCE-added SR-MPLS TE policies. · deleted—Number of PCE-deleted SR-MPLS TE policies. · up—Number of SR-MPLS TE policies in up state. · down—Number of SR-MPLS TE policies in down and Down (BFD down) states.
Total candidate paths	Total number of SR-MPLS TE policy candidate paths.
Total SID lists	Total number of SID lists.

‌

display segment-routing te policy-group

Use display segment-routing te policy-group to display SR-MPLS TE policy group information.

Syntax

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

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

group-id: Specifies an SR-MPLS 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 SR-MPLS TE policy groups.

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

Examples

# Display brief information about all SR-MPLS TE policy groups.

<Sysname> display segment-routing te policy-group

Total number of policy groups: 3

GroupID GroupState Endpoint UPMappings TotalMappings

1 Up 1.1.1.1 0 0

2 Up 2.2.2.2 0 0

3 Up 3.3.3.3 0 0

# Display detailed information about all SR-MPLS TE policy groups.

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

Total number of policy groups: 3

GroupID: 1 GroupState: 0

GroupNID: 24117249 Referenced: 1

Flags: F

Endpoint: 1.1.1.1 Up/Total mappings: 0/0

Color Type DSCP

1 IPv4 3, 10-20, default

2 IPv4 30, 40, 60

1 IPv6 3, 10-20, default

2 IPv6 30, 40, 60

Table 17 Command output

Field	Description
Total number of policy groups	Total number of SR-MPLS TE policy groups.
GroupID	SR-MPLS TE policy group ID.
GroupState	SR-MPLS TE policy group state: Down or Up.
GroupNID	NHLFE entry index of the SR-MPLS TE policy group.
Referenced	Number of times the SR-MPLS TE policy group has been used.
Flags	SR-MPLS TE policy group flags: · A—Assign the NHLFE entry index of the SR-MPLS TE policy group. · F—Issue the NHLFE entry of the SR-MPLS TE policy group. · W—Waiting for assigning the NHLFE entry index of the SR-MPLS TE policy group. · D—Delete the SR-MPLS TE policy group. · None—The SR-MPLS TE policy group is in initial state.
Endpoint	Destination node IP address of the SR-MPLS TE policy group. None indicates not configured.
UPMappings	Number of valid color-to-DSCP mappings in the SR-MPLS TE policy group.
TotalMappings	Total number of color-to-DSCP mappings in the SR-MPLS TE policy group.
Up/Total mappings	Valid color-to-DSCP mappings/total number of color-to-DSCP mappings in the SR-MPLS TE policy group.
Color	Color value
Type	Packet type: IPv4 or IPv6.
DSCP	DSCP value.

‌

display segment-routing te sbfd

Use display segment-routing te sbfd to display SBFD information for SR-MPLS TE policies.

Syntax

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

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

down: Displays SBFD information for SR-MPLS TE policies in down state.

up: Displays SBFD information for SR-MPLS TE policies in up state.

policy: Displays SBFD information for the specified SR-MPLS TE policy.

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

end-point { ipv4 ipv4-address | ipv6 ipv6-address }: Specifies an SR-MPLS TE policy by its endpoint IPv4 or IPv6 address.

name policy-name: Specifies an SR-MPLS 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 SBFD information for all SR-MPLS TE policies.

Examples

# Display SBFD information for all SR-MPLS TE policies.

<Sysname> display segment-routing te sbfd

Color: 10

Endpoint: 4.4.4.4

BSID: 15000

Policy name: p1

State: Down

NID: 24117249

SBFD type: SBFD Echo

Remote Discr: 67372036

Source-address: 1.1.1.1

State: Down

Timer: 30

Table 18 Command output

Field	Description
Color	Color attribute value of the SR-MPLS TE policy.
Endpoint	Endpoint IPv4 address of the SR-MPLS TE policy.
BSID	SID value of the ingress node.
Policy name	Name of the SR-MPLS TE policy.
State	SBFD session state: · Up · Down
NID	Forwarding entry index for an SID list.
SBFD type	SBFD type: SBFD or SBFD Echo.
Remote Discr	Remote discriminator.
Source-address	Active source address of BFD packets, which is configured by using the source-address command. This field displays a hyphen (-) if no source address is configured or the configured source address of BFD packets cannot take effect. If you specify a source IPv4 address in an IPv6 network or specify a source IPv6 address in an IPv4 network, the source IP address cannot take effect.
Timer	SBFD session timer, in seconds.
Template name	Name of the SBFD session template.

‌

distribute bgp-ls

Use distribute bgp-ls to enable the device to distribute SR-MPLS 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 SR-MPLS TE policy candidate path information to BGP-LS.

Views

SR TE view

Predefined user roles

network-admin

Usage guidelines

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

Examples

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

<Sysname> system-view

[Sysname] segment-routing

[Sysname-segment-routing] traffic-engineering

[Sysname-sr-te] distribute bgp-ls

dynamic (SR-MPLS TE policy path preference view)

Use dynamic to enable dynamic path calculation and create and enter SR-MPLS TE policy path preference dynamic view, or enter the existing SR-MPLS TE policy path preference dynamic view.

Use undo dynamic to disable dynamic path calculation, and delete SR-MPLS TE policy path preference dynamic view and all the configurations in the view.

Syntax

dynamic

undo dynamic

Default

Dynamic path calculation is disabled.

Views

SR-MPLS TE policy path preference view

Predefined user roles

network-admin

Usage guidelines

In SR-MPLS TE policy path preference dynamic view, you can configure the SID lists for the candidate paths of dynamically generated SR-MPLS TE policies.

Examples

# Enable dynamic path calculation and create and enter SR-MPLS TE policy path preference dynamic view.

<Sysname> system-view

[Sysname] segment-routing

[Sysname-segment-routing] traffic-engineering

[Sysname-sr-te] policy 1

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

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

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

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

dynamic (SR-TE-ODN view)

Use dynamic to enable dynamic path calculation and create and enter SR-TE-ODN dynamic view, or enter the existing SR-TE-ODN dynamic view.

Use undo dynamic to disable dynamic path calculation, and delete SR-TE-ODN dynamic view and all the configurations in the view.

Syntax

dynamic

undo dynamic

Default

Dynamic path calculation is disabled.

Views

SR-TE-ODN view

Predefined user roles

network-admin

Usage guidelines

In SR-TE-ODN dynamic view, you can configure the SR-MPLS TE policy generation policy and the method for dynamically generating the SID lists for the candidate paths of SR-MPLS TE policies.

Examples

# Enable dynamic path calculation and create and enter SR-TE-ODN dynamic view.

<Sysname> system-view

[Sysname] segment-routing

[Sysname-segment-routing] traffic-engineering

[Sysname-sr-te] on-demand color 1

[Sysname-sr-te-odn-1] dynamic

[Sysname-sr-te-odn-1-dynamic]

end-point

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

Use undo end-point to delete the endpoint IP address of the SR-MPLS TE policy group.

Syntax

end-point ipv4 ipv4-address

undo end-point ipv4

Default

No endpoint IP address is configured for the SR-MPLS TE policy group.

Views

SR-MPLS TE policy group view

Predefined user roles

network-admin

Parameters

ipv4 ipv4-address: Specifies the endpoint IP address for the SR-MPLS TE policy group.

Usage guidelines

The SR-MPLS TE policies added to the SR-MPLS TE policy group must use the same endpoint IP address as the SR-MPLS TE policy group.

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

Examples

# Configure the endpoint IP address as 10.1.1.1 for SR-MPLS TE policy group 1.

<Sysname> system-view

[Sysname] segment-grouting

[Sysname-segment-grouting] traffic-engineering

[Sysname-sr-te] policy-group 1

[Sysname-sr-te-policy-group-1] end-point ipv4 10.1.1.1

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

[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] exclude-any

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

Related commands

affinity (constraints view)

explicit segment-list

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

Use undo explicit segment-list to delete an SID list of a candidate path.

Syntax

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

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

Default

No SID lists are specified for an SR-MPLS TE policy candidate path.

Views

Candidate path preference view

Predefined user roles

network-admin

Parameters

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

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

Usage guidelines

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

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

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

Examples

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

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

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

Related commands

segment-list

forwarding statistics

Use forwarding statistics to configure traffic forwarding statistics for an SR-MPLS TE policy.

Use undo forwarding statistics enable to restore the default.

Syntax

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

undo forwarding statistics

Default

An SR-MPLS TE policy uses the traffic forwarding statistics configuration in SR TE view.

Views

SR-MPLS TE policy view

Predefined user roles

network-admin

Parameters

disable: Disables the SR-MPLS TE policy forwarding statistics.

enable: Enables the SR-MPLS TE policy forwarding statistics.

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

Usage guidelines

You can configure traffic forwarding statistics for all SR-MPLS TE policies globally in SR TE view or for a specific SR-MPLS TE policy in SR-MPLS TE policy view. The policy-specific configuration takes precedence over the global configuration. An SR-MPLS 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 SR-MPLS TE policy abc.

<Sysname> system-view

[Sysname] segment-routing

[Sysname-segment-routing] traffic-engineering

[Sysname-sr-te] policy abc

[Sysname-sr-te-policy-abc] forwarding statistics enable

Related commands

display segment-routing te forwarding

forwarding statistics enable

forwarding statistics interval

reset segment-routing te forwarding statistics

forwarding statistics enable

Use forwarding statistics enable to enable traffic forwarding statistics for all SR-MPLS TE policies.

Use undo forwarding statistics enable to disable traffic forwarding statistics for all SR-MPLS TE policies.

Syntax

forwarding statistics [ service-class ] enable

undo forwarding statistics enable

Default

Traffic forwarding statistics is disabled for all SR-MPLS TE policies.

Views

SR TE view

Predefined user roles

network-admin

Parameters

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

Usage guidelines

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

Examples

# Enable traffic forwarding statistics for all SR-MPLS TE policies.

<Sysname> system-view

[Sysname] segment-routing

[Sysname-segment-routing] traffic-engineering

[Sysname-sr-te] forwarding statistics enable

Related commands

display segment-routing te forwarding verbose

forwarding statistics interval

reset segment-routing te forwarding statistics

forwarding statistics interval

Use forwarding statistics interval to set the SR TE forwarding statistics interval.

Use undo forwarding statistics interval to restore the default.

Syntax

forwarding statistics interval interval

undo forwarding statistics interval

Default

The SR TE forwarding statistics interval is 30 seconds.

Views

SR TE view

Predefined user roles

network-admin

Parameters

Interval: Sets the SR TE forwarding statistics interval, in the range of 5 to 65535 seconds.

Examples

# Set the SR TE forwarding statistics interval to 90 seconds.

<Sysname> system-view

[Sysname] segment-routing

[Sysname-segment-routing] traffic-engineering

[Sysname-sr-te] forwarding statistics interval 90

Related commands

display segment-routing te forwarding verbose

forwarding statistics enable

reset segment-routing te forwarding statistics

import-route sr-policy

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

Views

BGP IPv4 SR policy address family view

Predefined user roles

network-admin

Usage guidelines

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

Examples

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

<Sysname> system-view

[Sysname] bgp 100

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

[Sysname-bgp-default-srpolicy-ipv4] 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 SR-MPLS 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

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

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

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 SR-MPLS 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 mpls label label-value

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.

mpls label label-value: Specifies the MPLS label value of the node, in the range of 0, 2, 3, and 16 to 1048575.

Examples

# Add a node to SID list abc, and set the node index to 1 and MPLS label to 1000.

<Sysname> system-view

[Sysname] segment-routing

[Sysname-segment-routing] traffic-engineering

[Sysname-sr-te] segment-list abc

[Sysname-sr-te-sl-abc] index 1 mpls label 1000

maximum-sid-depth

Use maximum-sid-depth to configure the maximum depth for the SID label stack.

Use undo maximum-sid-depth to restore the default.

Syntax

maximum-sid-depth value

undo maximum-sid-depth

Default

No maximum depth is set for the SID label stack.

Views

SR-TE ODN view

Predefined user roles

network-admin

Parameters

value: Specifies the maximum depth for the SID label stack, in the range of 1 to 255.

Usage guidelines

To implement dynamic path calculation for ODN-generated SR-MPLS TE policies, use this command to control the number of SIDs in the SID lists for the candidate paths of the SR-MPLS TE policies.

The actual effective SID label stack depth takes the smaller value among the following settings:

· Maximum depth of the SID label stack configured in this command.

· Default setting for this command.

Examples

# Configure the maximum depth of the SID label stack as 10.

<Sysname> system-view

[Sysname] segment-routing

[Sysname-segment-routing] traffic-engineering

[Sysname-sr-te] on-demand color 1

[Sysname-sr-te-odn-1] maximum-sid-depth 10

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

SR-MPLS TE policy path preference dynamic view

SR-TE-ODN dynamic view

Predefined user roles

network-admin

Usage guidelines

Use this command to specify the method for implementing dynamic path calculation for SR-MPLS TE policies.

Examples

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

<Sysname> system-view

[Sysname] segment-routing

[Sysname-segment-routing] traffic-engineering

[Sysname-sr-te] policy 1

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

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

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

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

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

# In SR-TE-ODN dynamic view, create a metric type and enter metric type view.

<Sysname> system-view

[Sysname] segment-routing

[Sysname-segment-routing] traffic-engineering

[Sysname-sr-te] on-demand color 1

[Sysname-sr-te-odn-1] dynamic

[Sysname-sr-te-odn-1-dynamic] metric

[Sysname-sr-te-odn-1-dynamic-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

SR-TE-ODN dynamic 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 SR-MPLS 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

[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] name red

# In SR-TE-ODN dynamic affinity attribute rule view, specify affinity attribute red for the include-any affinity attribute rule.

<Sysname> system-view

[Sysname] segment-routing

[Sysname-segment-routing] traffic-engineering

[Sysname-sr-te] on-demand color 1

[Sysname-sr-te-odn-1] dynamic

[Sysname-sr-te-odn-1-dynamic] affinity include-any

[Sysname-sr-te-odn-1-dynamic-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 SR-MPLS 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

[Sysname-segment-routing] traffic-engineering

[Sysname-sr-te] affinity-map

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

Related commands

mpls te link-attribute (MPLS Command Reference)

name

on-demand

Use on-demand to create an on-demand next-hop (ODN) template for creating SR-MPLS TE policies and enter SR-TE-ODN view, or enter the SR-TE-ODN view of an existing ODN template.

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

Syntax

on-demand color color-value

undo on-demand color color-value

Default

No SR-MPLS TE policy ODN templates exist.

Views

SR 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 SR-MPLS TE policy and two candidate paths for the policy.

· The policy uses the BGP route's next hop address as the end-point address and the ODN template's color value as the color attribute value of the policy.

· The candidate paths use preferences 100 and 200. You need to configure the SID lists for the candidate path with preference 200 through dynamic calculation based on affinity attribute or Flex-Algo, and use PCE to compute the SID lists for the candidate path with preference 100.

You can also manually create candidate paths for an ODN-created SR-MPLS TE policy.

Examples

# Create an SR-MPLS TE policy ODN template with color value 1 and enter SR-TE-ODN view.

<Sysname> system-view

[Sysname] segment-routing

[Sysname-segment-routing] traffic-engineering

[Sysname-sr-te] on-demand color 1

[Sysname-sr-te-odn-1]

pce capability segment-routing

Use pce capability segment-routing to enable the SR capability for a PCC device.

Use undo pce capability segment-routing to disable the SR capability for a PCC device.

Syntax

pce capability segment-routing

undo pce capability segment-routing

Default

A PCC device does not have the SR capability.

Views

PCC view

Predefined user roles

network-admin

Usage guidelines

To establish an SR-capable PCEP session, you need to enable the SR capability on both peers of the PCEP session. An SR-capable active PCEP session supports computation, report, delegation, and update of SR-based LSPs.

In the current software version, a PCE device does not have the SR capability.

Examples

# Enable the SR capability for the PCC device.

<Sysname> system-view

[Sysname] pce-client

[Sysname-pcc] pce capability segment-routing

pce delegation

Use pce delegation to enable PCE delegation for an SR-MPLS TE policy.

Use undo pce delegation to restore the default.

Syntax

pce delegation { enable | disable }

undo pce delegation

Default

An SR-MPLS TE policy uses the PCE delegation configuration in SR TE view.

Views

SR-MPLS TE policy view

Predefined user roles

network-admin

Parameters

enable: Enables PCE delegation for the SR-MPLS TE policy.

disable: Disables PCE delegation for the SR-MPLS TE policy.

Usage guidelines

After PCE delegation for an SR-MPLS TE policy is enabled, the PCC delegates the policy's candidate paths to a PCE. The PCC creates or updates candidate paths according to the creation or update requests received from the PCE.

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

If you execute both the pce delegation command and the pce passive-delegate report-only command for an SR-MPLS TE policy, the pce passive-delegate report-only command takes effect.

Examples

# Enable PCE delegation for an SR-MPLS TE policy.

<Sysname> system-view

[Sysname] segment-routing

[Sysname-segment-routing] traffic-engineering

[Sysname-sr-te] policy 1

[Sysname-sr-te-policy-1] pce delegation enable

Related commands

pce passive-delegate report-only

sr-policy pce delegation enable

pce passive-delegate report-only

Use pce passive-delegate report-only to enable the device to report candidate path information of an SR-MPLS TE policy to the PCE without delegating the policy to the PCE.

Use undo pce passive-delegate report-only to restore the default.

Syntax

pce passive-delegate report-only { enable | disable }

undo pce passive-delegate report-only

Default

An SR-MPLS TE policy uses the passive delegation report only setting configured in SR TE view.

Views

SR-MPLS TE policy view

Predefined user roles

network-admin

Parameters

enable: Enables the passive delegation report only feature for the SR-MPLS TE policy.

disable: Disables the passive delegation report only feature for the SR-MPLS TE policy.

Usage guidelines

When the device delegates only part of its SR-MPLS TE policies to a PCE, the PCE does not have complete SR-MPLS TE policy candidate path information to calculate global bandwidth information. You can enable the device to report information about the undelegated SR-MPLS TE policies to the PCE without using the PCE to compute candidate paths for the policies.

You can configure the passive delegation report only feature for all SR-MPLS TE policies globally in SR TE view or for a specific SR-MPLS TE policy in SR-MPLS TE policy view. The policy-specific configuration takes precedence over the global configuration. An SR-MPLS TE policy uses the global configuration only when it has no policy-specific configuration.

If you execute both the pce delegation command and the pce passive-delegate report-only command for an SR-MPLS TE policy, the pce passive-delegate report-only command takes effect.

Examples

# Enable the device to report an SR-MPLS TE policy's candidate path information to the PCE without delegating the policy to the PCE.

<Sysname> system-view

[Sysname] segment-routing

[Sysname-segment-routing] traffic-engineering

[Sysname-sr-te] policy 1

[Sysname-sr-te-policy-1] pce passive-delegate report-only enable

Related commands

pce delegation

sr-policy pce passive-delegate report-only enable

pcep (SR-TE-ODN dynamic view)

Use pcep to enable path computation using PCE.

Use undo pcep to disable path computation using PCE.

Syntax

pcep

undo pcep

Default

Dynamic path computation using PCE is disabled.

Views

SR-TE-ODN dynamic view

Predefined user roles

network-admin

Usage guidelines

The SID lists for ODN-created SR-MPLS TE policy candidate path 100 can only be computed by PCE. For this candidate path, you must execute this command to enable path computation using PCE. The path computation procedure is as follows:

1. The device that acts as a PCC sends a path computation request to the PCE.

2. The PCE computes paths after it receives the request.

3. The PCE replies the PCC with the computed path information.

4. The PCC creates SID lists for candidate path 100 according to the path information computed by PCE.

Examples

# Enable dynamic path computation using PCE.

<Sysname> system-view

[Sysname] segment-routing

[Sysname-segment-routing] traffic-engineering

[Sysname-sr-te] on-demand color 1

[Sysname-sr-te-odn-1] dynamic

[Sysname-sr-te-odn-1-dynamic] pcep

pcep (SR-MPLS TE policy path preference dynamic view)

Use pcep to enable an SR-MPLS TE policy candidate path to use PCE to compute the SID lists.

Use undo pcep to restore the default.

Syntax

pcep

undo pcep

Default

An SR-MPLS TE policy candidate path does not use PCE to compute SID lists. You need to manually configure the SID lists for the candidate path.

Views

SR-MPLS TE policy path preference dynamic view

Predefined user roles

network-admin

Usage guidelines

The device uses PCE to compute SID lists for a manually created SR-MPLS TE policy candidate path in the following procedure:

1. The device that acts as a PCC sends a path computation request to the PCE.

2. The PCE computes paths after it receives the request.

3. The PCE replies the PCC with the computed path information.

4. The PCC creates SID lists for the SR-MPLS TE policy candidate path according to the path information computed by PCE.

Examples

# Enable an SR-MPLS TE policy candidate path to use PCE to compute the SID lists.

<Sysname> system-view

[Sysname] segment-routing

[Sysname-segment-routing] traffic-engineering

[Sysname-sr-te] policy 1

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

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

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

[Sysname-sr-te-policy-1-path-pref-20-dyna] pcep

policy

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

Use undo policy to delete an SR-MPLS TE policy and all the configuration in the SR-MPLS TE policy.

Syntax

policy policy-name

undo policy policy-name

Default

No SR policies exist.

Views

SR TE view

Predefined user roles

network-admin

Parameters

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

Examples

# Create an SR-MPLS TE policy named srpolicy and enter its view.

<Sysname> system-view

[Sysname] segment-routing

[Sysname-segment-routing] traffic-engineering

[Sysname-sr-te] policy srpolicy

[Sysname-sr-te-policy-srpolicy]

policy-group

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

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

Syntax

policy-group group-id

undo policy-group group-id

Default

No SR-MPLS TE policy groups exist.

Views

SR TE view

Predefined user roles

network-admin

Parameters

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

Usage guidelines

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

Examples

# Create SR-MPLS TE policy group 1 and enter its view.

<Sysname> system-view

[Sysname] segment-grouting

[Sysname-segment-grouting] traffic-engineering

[Sysname-sr-te] policy-group 1

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

preference

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

Use undo preference to delete a candidate path preference and all the configuration in the candidate path preference view.

Syntax

preference preference-value

undo preference preference-value

Default

No candidate path preferences are set.

Views

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 SR-MPLS TE policy.

Examples

# Set the preference of an SR-MPLS TE policy candidate path to 20, and enter candidate path preference 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 20

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

reoptimization

Use reoptimization to configure candidate path reoptimization for an SR-MPLS TE policy.

Use undo reoptimization to restore the default.

Syntax

reoptimization { disable | enable [ frequency seconds ] }

undo reoptimization

Default

Candidate path reoptimization is not configured for an SR-MPLS TE policy and the configuration in SR TE view applies.

Views

SR-MPLS TE policy view

Predefined user roles

network-admin

Parameters

disable: Disables candidate path reoptimization for an SR-MPLS TE policy.

enable: Enables candidate path reoptimization for an SR-MPLS TE policy.

frequency seconds: Sets the candidate path reoptimization frequency, in the range of 1 to 604800 seconds. The default frequency is 3600 seconds. If you set a frequency smaller than 60 seconds, the device performs reoptimization every 60 seconds.

Usage guidelines

This feature enables the PCE to periodically compute paths and notify the PCC to update path information, so that the SR-MPLS TE policy can use the optimal path to establish the candidate path.

For example, an SR-MPLS TE policy uses a path other than the optimal path to establish the candidate path because the optimal path does not have sufficient link bandwidth. This feature enables the SR-MPLS TE policy to switch the candidate path to the optimal path when the link bandwidth becomes sufficient.

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

Examples

# Enable candidate path reoptimization for SR-MPLS TE policy p1.

<Sysname> system-view

[Sysname] segment-routing

[Sysname-segment-routing] traffic-engineering

[Sysname-sr-te] policy p1

[Sysname-sr-te-policy-p1] reoptimization enable

Related commands

sr-policy reoptimization

reset segment-routing te forwarding statistics

Use reset segment-routing te forwarding statistics to clear SR TE forwarding statistics.

Syntax

reset segment-routing te forwarding statistics [ binding-sid binding-sid | color color-value end-point { ipv4 ipv4-address | ipv6 ipv6-address } | name policy-name ]

Views

User view

Predefined user roles

network-admin

Parameters

binding-sid binding-sid: Specifies an SR-MPLS TE policy by its BSID. The value range for the BSID is 16 to 1048575.

name policy-name: Specifies an SR-MPLS 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 clears forwarding statistics for all SR-MPLS TE policies.

Examples

# Clear SR TE forwarding statistics.

<Sysname> reset segment-routing te forwarding statistics

Related commands

display segment-routing te forwarding verbose

forwarding statistics enable

forwarding statistics interval

restrict

Use restrict to configure the ODN SR-MPLS TE policy generation policy.

Use undo restrict to restore the default.

Syntax

restrict prefix-list-name

undo restrict

Default

A BGP route can trigger ODN to create an SR-MPLS TE policy when the route's color attribute value is the same as the ODN color value.

Views

SR-TE-ODN view

Predefined user roles

network-admin

Parameters

prefix-list-name: Specifies an IP prefix list by its name, a case-sensitive string of 1 to 63 characters.

Usage guidelines

You can specify an IP prefix list to filter BGP routes. The BGP routes permitted by the specified IP prefix list can trigger ODN to create SR-MPLS TE policies. The BGP routes denied by the specified IP prefix list cannot trigger ODN to create SR-MPLS TE policies.

Examples

# Permit the BGP routes in subnet 10.1.1.0/24 to trigger ODN to create SR-MPLS TE policies.

<Sysname> system-view

[Sysname] ip prefix-list policy permit 10.1.1.0 24

[Sysname] segment-routing

[Sysname-segment-routing] traffic-engineering

[Sysname-sr-te] on-demand color 1

[Sysname-sr-te-odn-1] restrict policy

Related commands

ip prefix-list (Layer 3—IP Routing Command Reference)

router-id filter

Use router-id filter to enable SR-MPLS TE policy route filtering by router ID.

Use undo router-id filter to disable SR-MPLS TE policy route filtering by router ID.

Syntax

router-id filter

undo router-id filter

Default

SR-MPLS TE policy route filtering by router ID is disabled.

Views

BGP IPv4 SR policy address family view

Predefined user roles

network-admin

Usage guidelines

When a large number of SR-MPLS TE policy routes exist in the network, execute this command to enable the device to process only specific SR-MPLS TE policy routes.

Upon receiving SR-MPLS TE policy routes, the device checks the Route Target (RT) attribute in received SR-MPLS TE policy routes. Only the routes containing the local router ID in the RT attribute are accepted.

To avoid incorrect route learning or filtering, configure a routing policy to add an appropriate RT attribute to SR-MPLS TE policy routes before executing this command.

Examples

# Enable SR-MPLS TE policy route filtering by router ID.

<Sysname> system-view

[Sysname] bgp 100

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

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

sbfd

Use sbfd to configure SBFD for an SR-MPLS TE policy.

Use undo sbfd to restore the default.

Syntax

sbfd { disable | enable [ encapsulation-mode { ipv4 | ipv6 } ] [ proxy-reflector [ disable ] ] [ remote remote-id ] [ template template-name ] [ backup-template backup-template-name ] }

sbfd echo { disable | enable [ template template-name ] [ backup-template backup-template-name ] }

undo sbfd [ echo ] { disable | enable }

Default

SBFD is disabled for an SR-MPLS TE policy. The configuration in SR-TE view applies.

Views

SR-MPLS TE policy view

Predefined user roles

network-admin

Parameters

echo: Specifies echo packet mode SBFD (echo SBFD). If you do not specify this keyword, the control packet mode of SBFD is used.

disable: Disables SBFD for the SR-MPLS TE policy.

enable: Enables SBFD for the SR-MPLS TE policy.

encapsulation-mode: Specifies the SBFD packet encapsulation mode for the SR-MPLS TE policy. For an SBFD session that has been established, the session will be deleted and established again if this keyword changes the SBFD packet encapsulation mode.

· For an SR-MPLS TE policy with an IPv6 endpoint address, the configuration of this command applies if this keyword is specified. If this keyword is not specified, the configuration of the sr-policy sbfd enable command in SR-TE view applies.

· For an SR-MPLS TE policy with an IPv4 endpoint address, SBFD packets use the IPv4 encapsulation mode and this keyword does not take effect.

ipv4: Specifies the IPv4 encapsulation mode for SBFD packets.

ipv6: Specifies the IPv6 encapsulation mode for SBFD packets.

proxy-reflector: Enables the SBFD proxy reflector feature. Specify this keyword if the end-point node of an SR-MPLS TE policy cannot act as the reflector of the SBFD session. If the SBFD proxy reflector feature is enabled, the reflector specified by the source node of the SR-MPLS TE policy acts as the reflector of the SBFD session. Use this keyword in combination with the peer egress-engineering link-down relate-bfd-state or egress-engineering peer-set link-down relate-bfd-state command in BGP instance view. If this keyword is not specified, the configuration of the sr-policy sbfd enable command in SR-TE view applies.

disable: Disables the SBFD proxy reflector.

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 sr-policy sbfd enable command setting in SR TE view applies.

template template-name: Specifies an SBFD 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 SR TE view applies.

backup-template backup-template-name: Specifies an SBFD session parameter template for the backup candidate path. 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 template specified by the template template-name option applies. If neither the template template-name nor the backup-template backup-template-name option is specified, the backup template specified in SR TE view applies.

Usage guidelines

This command enables an SR-MPLS TE policy to use SBFD to detect availability of SID lists. If all SID lists for the current candidate path are faulty, another candidate path takes over to minimize service interruption.

You can enable SBFD for all SR-MPLS TE policies globally in SR TE view or for a specific SR-MPLS TE policy in SR-MPLS TE policy view. The policy-specific configuration takes precedence over the global configuration. An SR-MPLS TE policy uses the global configuration only when it does not have policy-specific configuration.

You cannot enable echo SBFD for SR-MPLS TE policies with endpoint IPv6 addresses.

If both SBFD and echo BFD are enabled for an SR-MPLS TE policy, the device first establishes the SBFD session.

If both echo SBFD and echo BFD are enabled for an SR-MPLS TE policy, the device first establishes the echo SBFD session.

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

Examples

# Enable SBFD for SR-MPLS TE policy 1.

<Sysname> system-view

[Sysname] segment-grouting

[Sysname-segment-grouting] traffic-engineering

[Sysname-sr-te] policy 1

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

Related commands

bfd template (High Availability Command Reference)

egress-engineering peer-set

peer egress-engineering

sr-policy sbfd enable

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

SR 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

[Sysname-segment-routing] traffic-engineering

[Sysname-sr-te] segment-list abc

[Sysname-sr-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

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

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

service-class

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

Use undo service-class to restore the default.

Syntax

service-class service-class-value

undo service-class

Default

No service class value is set for an SR-MPLS TE policy. The default service class value is 255 for the SR-MPLS TE policy, which means the SR-MPLS TE policy has the lowest forwarding priority.

Views

SR-MPLS TE policy view

Predefined user roles

network-admin

Parameters

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

Usage guidelines

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

· If the traffic matches only one SR-MPLS TE policy, the device uses this SR-MPLS TE policy.

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

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

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

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

· If the traffic does not match any SR-MPLS TE policy, the device randomly selects an SR-MPLS TE policy from all SR-MPLS TE policies with the lowest priority.

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

Examples

# Set the service class value to 5 for SR-MPLS TE policy 1.

<Sysname> system-view

[Sysname] segment-routing

[Sysname-segment-routing] traffic-engineering

[Sysname-sr-te] policy 1

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

Related commands

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

remark service-class (ACL and QoS Command Reference)

shutdown

Use shutdown to shut down an SR-MPLS TE policy.

Use undo shutdown to bring up an SR-MPLS TE policy.

Syntax

shutdown

undo shutdown

Default

An SR-MPLS TE policy is not administratively shut down.

Views

SR-MPLS TE policy view

Predefined user roles

network-admin

Usage guidelines

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

Examples

# Shut down SR-MPLS TE policy 1.

<Sysname> system-view

[Sysname] segment-routing

[Sysname-segment-routing] traffic-engineering

[Sysname-sr-te] policy 1

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

sid-algorithm

Use sid-algorithm to specify a Flex-Algo for an SR-MPLS TE policy.

Use undo sid-algorithm to restore the default.

Syntax

sid-algorithm algorithm-id

undo sid-algorithm

Default

No Flex-Algo is associated with an SR-MPLS TE policy.

Views

Segment constraints view

SR-TE-ODN dynamic view

Predefined user roles

network-admin

Parameters

algorithm-id: Specifies a Flex-Algo by its ID in the range of 128 to 255.

Usage guidelines

The SR-MPLS TE policy will use the specified Flex-Algo to calculate forwarding paths.

Examples

# In segment constraints view, specify Flex-Algo 128 for the SR-MPLS TE policy.

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

[Sysname-sr-te-policy-a1-path-pref-200-const-seg] sid-algorithm 128

# In SR-TE-ODN dynamic view, specify Flex-Algo 128 for the SR-MPLS TE policy.

<Sysname> system-view

[Sysname] segment-routing

[Sysname-segment-routing] traffic-engineering

[Sysname-sr-te] on-demand color 1

[Sysname-sr-te-odn-1] dynamic

[Sysname-sr-te-odn-1-dynamic] sid-algorithm 128

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

No SID limit is set in an SID list

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 SR-MPLS TE policy. The SR-MPLS 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

[Sysname-segment-routing] traffic-engineering

[Sysname-sr-te] policy p1

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

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

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

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

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

source-address

Use source-address to specify a source address for an SR-MPLS TE policy.

Use undo source-address to remove the source address configuration from an SR-MPLS TE policy.

Syntax

source-address { ipv4 ipv4-address | ipv6 ipv6-address }

undo source-address

Default

No source address is specified for an SR-MPLS TE policy.

Views

SR-MPLS TE policy view

Predefined user roles

network-admin

Parameters

ipv4 ipv4-address: Specifies an IPv4 address.

ipv6 ipv6-address: Specifies an IPv6 address.

Usage guidelines

Use this command to specify a source address only for BFD echo and SBFD packets in the SR-MPLS TE policy scenario.

In the SR-MPLS TE policy scenario, when BFD in echo packet mode is enabled, you must use the bfd echo or sr-policy bfd echo command to specify the source address of the BFD session on the source node of the SR-MPLS TE policy. The specified address is also the destination address of BFD echo packets.

In system view, you can use the bfd echo-source-ip or bfd echo-source-ipv6 command to specify the source address of BFD echo packets for all BFD sessions in echo packet mode on the device. If you do not use the bfd echo-source-ip or bfd echo-source-ipv6 command, the device will use the BFD session source address specified by using the bfd echo or sr-policy bfd echo command as the source address of BFD echo packets. In this case, the same address is used as both the source and destination addresses of BFD echo packets. BFD echo session establishment will fail if the network is deployed with security devices that have features such as uRPF, because the features falsely treat the BFD echo packets as illegal packets and intercept them.

To resolve the above issue, use this command to specify a packet source address for each SR-MPLS TE policy.

When SBFD or BFD in echo packet mode is enabled for an SR-MPLS TE policy, you can use this command to specify a source address for BFD or SBFD session packets.

For a BFD session in echo packet mode, the device selects a source address for BFD echo packets in the following order:

1. The packet source address specified by using the source-address command.

2. The packet source address specified by using the bfd echo-source-ip or bfd echo-source-ipv6 command.

3. The BFD session source address specified by using the bfd echo command.

4. The BFD session source address specified by using the sr-policy bfd echo command.

For an SBFD session, the device selects a source address for SBFD packets in the following order:

5. The packet source address specified by using the source-address command.

6. The address specified by using the mpls lsr-id or sbfd source-ipv6 command.

In an IPv6 network, you must specify a source IPv6 address for BFD and SBFD packets in an SR-MPLS TE policy. If you do not specify a source IPv6 address, the specified source address cannot take effect.

In an IPv4 network, you must specify a source IPv4 address for BFD and SBFD packets in an SR-MPLS TE policy. If you do not specify a source IPv4 address, the specified source address cannot take effect.

Examples

# Specify source address 1.2.3.4 for BFD and SBFD session packets in an SR-MPLS TE policy.

<Sysname> system-view

[Sysname] segment-routing

[Sysname-segment-routing] traffic-engineering

[Sysname-sr-te] policy 1

[Sysname-sr-te-policy-1] source-address ipv4 1.2.3.4

Related commands

bfd echo-source-ip (High Availability Command Reference)

bfd echo-source-ipv6 (High Availability Command Reference)

bfd echo

sbfd

sr-policy bfd echo

sr-policy backup hot-standby enable

Use sr-policy backup hot-standby enable to enable hot standby for all SR-MPLS TE policies.

Use undo sr-policy backup hot-standby enable to disable hot standby for all SR-MPLS TE policies.

Syntax

sr-policy backup hot-standby enable [ multilevel-backup ]

undo sr-policy backup hot-standby enable

Default

Hot standby is disabled for all SR-MPLS TE policies.

Views

SR TE view

Predefined user roles

network-admin

Parameters

multilevel-backup: Enables multilevel hot standby for SR-MPLS TE policies. With this feature enabled, the candidate path with the third highest preference in an SR-MPLS TE policy is used as the secondary backup path. If you do not specify this keyword, the SR-MPLS TE policy only has one main path and one backup path.

Usage guidelines

Examples

# Enable hot standby for all SR-MPLS TE policies.

<Sysname> system-view

[Sysname] segment-routing

[Sysname-segment-routing] traffic-engineering

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

Related commands

backup hot-standby

sr-policy bfd echo

Use sr-policy bfd echo to enable the echo packet mode BFD for all SR-MPLS TE policies.

Use undo sr-policy bfd echo to disable the echo packet mode BFD for all SR-MPLS TE policies.

Syntax

sr-policy bfd echo { source-ip ipv4-address | source-ipv6 ipv6-address } [ template template-name ] [ backup-template backup-template-name ]

undo sr-policy bfd echo

Default

The echo packet mode BFD is disabled for all SR-MPLS TE policies.

Views

SR TE view

Predefined user roles

network-admin

Parameters

source-ip ipv4-address: Specifies the source IPv4 address of the BFD session.

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.

backup-template backup-template-name: Specifies a BFD session parameter template for the backup candidate path. 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 template specified for the primary candidate path applies. If no template specified is for the primary candidate path either, the multihop BFD session settings configured in system view applies to the backup candidate path.

Usage guidelines

If you do not specify the source-ip or source-ipv6 keyword in the bfd echo command for an SR-MPLS TE policy, you must enable the echo packet mode BFD globally in SR TE view. Otherwise, the device cannot establish a BFD session for the SR-MPLS TE policy.

If you specify the source-ip or source-ipv6 keyword and the bfd echo-source-ip or bfd echo-source-ipv6 command is not executed in system view, both the source and destination IP addresses of BFD echo packets are the IP address specified by the source-ip keyword. To avoid being overwhelmed by ICMP redirects from the remote device, execute the bfd echo-source-ip or bfd echo-source-ipv6 command in system view to specify the source IP address for BFD echo packets as an IP address that does not belong to any subnet of a local interface.

To successfully establish a BFD session, the remote device must be able to reach the session source IP address specified by this command on the local device.

If both SBFD and echo BFD are enabled for an SR-MPLS TE policy, the device first establishes the SBFD session.

If both echo SBFD and echo BFD are enabled for an SR-MPLS TE policy, the device first establishes the echo SBFD session.

Examples

# Enable the echo packet mode BFD for all SR-MPLS TE policies, and specify the source IP address of the BFD session as 1.2.3.4.

<Sysname> system-view

[Sysname] segment-routing

[Sysname-segment-routing] traffic-engineering

[Sysname-sr-te] sr-policy bfd echo source-ip 1.2.3.4

Related commands

bfd echo

bfd echo-source-ip (High Availability Command Reference)

display segment-routing te bfd

sr-policy bfd first-fail-timer

Use sr-policy bfd first-fail-timer to configure the delay time for the device to notify an SR-MPLS TE policy of the BFD/SBFD session down event.

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

Syntax

sr-policy bfd first-fail-timer seconds

undo sr-policy bfd first-fail-timer

Default

The delay time for the device to notify an SR-MPLS TE policy of the BFD/SBFD session down event is 60 seconds.

Views

SR TE view

Predefined user roles

network-admin

Parameters

sessions: Specifies the delay time in the range of 1 to 600 seconds. The default delay time is 60 seconds. After the device detects a BFD/SBFD session setup failure for the first time for an SR-MPLS TE policy, it waits for the delay time for the BFD/SBFD session to be re-established. If the BFD/SBFD session cannot be established successfully after the delay time expires, the device notifies the SR-MPLS TE policy of the BFD/SBFD session down event.

Usage guidelines

When an SR-MPLS TE policy meets the following conditions, the device will tries to establish a BFD/SBFD session for the SR-MPLS TE policy:

· The SR-MPLS TE policy is in up state.

· The SID list of the SR-MPLS TE policy is in up state.

· BFD or SBFD is enabled to detect connectivity of the SR-MPLS TE policy.

The device fails to establish the BFD/SBFD session if the session is not in up state when the session detection time expires. The device does not immediately notify the SR-MPLS TE policy of this event but wait for the specified delay time. If the BFD/SBFD session cannot be established successfully after the delay time expires, the device notifies the SR-MPLS TE policy of the BFD/SBFD session down event.

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

Examples

# Configure the delay time for the device to notify an SR-MPLS TE policy of the BFD/SBFD session down event to 30 seconds.

<Sysname> system-view

[Sysname] segment-routing

[Sysname-segment-routing] traffic-engineering

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

sr-policy bfd trigger path-down enable

Use sr-policy bfd trigger path-down enable to globally enable BFD session down events to trigger SR-MPLS TE policy path reselection.

Use undo sr-policy bfd trigger path-down enable to restore the default.

Syntax

sr-policy bfd trigger path-down enable

undo sr-policy bfd trigger path-down enable

Default

This feature is disabled.

Views

SR TE view

Predefined user roles

network-admin

Usage guidelines

By default, when an SR-MPLS TE policy contains multiple valid candidate paths:

· If hot standby is enabled, BFD/SBFD detects all the SID lists of the main and backup candidate paths and establishes a BFD/SBFD session for each of the SID lists.

¡ When all the BFD/SBFD sessions for the main path are down, the SR-MPLS TE policy switches traffic to the backup path and does not reselect a candidate path.

¡ When all the BFD/SBFD sessions for the main and backup paths are down, the SR-MPLS TE policy does not reselect a candidate path and packets are no longer forwarded through the SR-MPLS TE policy.

After you enable this feature by executing this command for an SR-MPLS TE policy that contains multiple valid candidate paths:

· If hot standby is not enabled, BFD/SBFD detects all the SID lists of the optimal candidate path and establishes a BFD/SBFD session for each of the SID lists. When all the BFD/SBFD sessions are down, the SR-MPLS TE policy reselects a candidate path and uses the new candidate path to forward packets. If no valid candidate path is available during the resection, packets cannot be forwarded through the SR-MPLS TE policy.

· If hot standby is enabled, BFD/SBFD detects all the SID lists of the main and backup candidate paths and establishes a BFD/SBFD session for each of the SID lists.

¡ When all the BFD/SBFD sessions for the main path are down, the SR-MPLS TE policy switches traffic to the backup path and reselects the main and backup paths.

¡ When all the BFD/SBFD sessions for the main and backup paths are down, the SR-MPLS TE policy reselects the main and backup paths and forwards packets through the new main path.

¡ If no valid candidate path is available during the resection, packets cannot be forwarded through the SR-MPLS TE policy.

Before you enable this feature for an SR-MPLS TE policy, create an SBFD session for the policy first.

Examples

# Globally enable BFD session down events to trigger candidate path reselection for SR-MPLS TE policies.

<Sysname> system-view

[Sysname] segment-routing

[Sysname-segment-routing] traffic-engineering

[Sysname-sr-te] sr-policy bfd trigger path-down enable

Related commands

bfd trigger path-down

sbfd

sr-policy sbfd enable

sr-policy calc-schedule-interval

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

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

Syntax

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

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

SR 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 SR-MPLS TE policy flappings. If you do not specify this keyword, in case of SR-MPLS TE policy flappings, the maximum interval applies for three consecutive times, and then the minimum interval applies. If no SR-MPLS 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 SR-MPLS TE policy, the minimum-interval setting applies.

· For the nth (n > 1) path calculation triggered for the SR-MPLS 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 SR-MPLS TE policy flapping condition to adjust the path calculation intervals:

· If the conservative keyword is specified:

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

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

· If the conservative keyword is not specified:

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

¡ If no SR-MPLS 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

[Sysname-segment-routing] traffic-engineering

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

sr-policy immediate-reoptimization

Use sr-policy immediate-reoptimization to immediately reoptimize all SR-MPLS TE policies enabled with candidate path optimization.

Syntax

sr-policy immediate-reoptimization

Views

User view

Predefined user roles

network-admin

Usage guidelines

After an SR-MPLS TE policy is enabled with candidate path optimization, you can execute this command to trigger an immediate optimization to switch the candidate path of the SR-MPLS TE policy to the optimal path.

Examples

# Immediately reoptimize all SR-MPLS TE policies enabled with candidate path optimization.

<Sysname> sr-policy immediate-reoptimization

sr-policy log enable

Use sr-policy log enable to enable SR-MPLS TE policy logging.

Use undo sr-policy log enable to disable SR-MPLS TE policy logging.

Syntax

sr-policy log enable

undo sr-policy log enable

Default

SR-MPLS TE policy logging is disabled.

Views

SR TE view

Predefined user roles

network-admin

Usage guidelines

This feature enables the device to log SR-MPLS TE policy state changes to facilitate audit of SR-MPLS TE policy operations. The SR-MPLS TE policy log messages are sent to the information center and output as configured in the information center. For more information about information center, see Network Management and Monitoring Configuration Guide.

Examples

# Enable SR-MPLS TE policy logging.

<Sysname> system-view

[Sysname] segment-routing

[Sysname-segment-routing] traffic-engineering

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

sr-policy pce delegation enable

Use sr-policy pce delegation enable to enable PCE delegation for SR-MPLS TE policies globally.

Use undo sr-policy pce delegation enable to disable PCE delegation for SR-MPLS TE policies globally.

Syntax

sr-policy pce delegation enable

undo sr-policy pce delegation enable

Default

PCE delegation for SR-MPLS TE policies is disabled globally.

Views

SR TE view

Predefined user roles

network-admin

Usage guidelines

If you execute both the sr-policy pce delegation enable command and the sr-policy pce passive-delegate report-only enable command in SR TE view, the sr-policy pce passive-delegate report-only enable command takes effect.

Examples

# Enable PCE delegation for SR-MPLS TE policies globally.

<Sysname> system-view

[Sysname] segment-routing

[Sysname-segment-routing] traffic-engineering

[Sysname-sr-te] sr-policy pce delegation enable

Related commands

pce delegation

sr-policy pce passive-delegate report-only enable

Use sr-policy pce passive-delegate report-only enable to enable the passive delegation report only feature globally.

Use undo sr-policy pce passive-delegate report-only enable to disable the passive delegation report only feature globally.

Syntax

sr-policy pce passive-delegate report-only enable

undo sr-policy pce passive-delegate report-only enable

Default

The passive delegation report only feature is disabled globally.

Views

SR TE view

Predefined user roles

network-admin

Usage guidelines

The passive delegation report only feature enables the device to report candidate path information of an SR-MPLS TE policy to the PCE without delegating the policy to the PCE.

Examples

# Enable the passive delegation report only feature globally for all SR-MPLS TE policies.

<Sysname> system-view

[Sysname] segment-routing

[Sysname-segment-routing] traffic-engineering

[Sysname-sr-te] sr-policy pce passive-delegate report-only enable

Related commands

pce passive-delegate report-only

sr-policy pce delegation enable

sr-policy reoptimization

Use sr-policy reoptimization to enable candidate path reoptimization for SR-MPLS TE policies globally.

Use undo sr-policy reoptimization to disable candidate path reoptimization for SR-MPLS TE policies globally.

Syntax

sr-policy reoptimization [ frequency seconds ]

undo sr-policy reoptimization

Default

Candidate path reoptimization for SR-MPLS TE policies is globally disabled.

Views

SR-MPLS TE policy view

Predefined user roles

network-admin

Parameters

Usage guidelines

This feature enables the PCE to periodically compute paths and notify the PCC to update path information, so that SR-MPLS TE policies can use the optimal path to establish the candidate path.

Examples

# Enable candidate path reoptimization for SR-MPLS TE policies globally.

<Sysname> system-view

[Sysname] segment-routing

[Sysname-segment-routing] traffic-engineering

[Sysname-sr-te] sr-policy reoptimization

Related commands

reoptimization

sr-policy sbfd enable

Use sr-policy sbfd enable to enable SBFD for all SR-MPLS TE policies.

Use undo sr-policy sbfd enable to disable SBFD for all SR-MPLS TE policies.

Syntax

sr-policy sbfd enable [ encapsulation-mode ipv4 ] [ proxy-reflector ] [ remote remote-id ] [ template template-name ] [ backup-template backup-template-name ]

sr-policy sbfd echo enable [ template template-name ] [ backup-template backup-template-name ]

undo sr-policy sbfd [ echo ] enable

Default

SBFD is disabled for all SR-MPLS TE policies.

Views

SR TE view

Predefined user roles

network-admin

Parameters

· For an SR-MPLS TE policy with an IPv4 endpoint address, SBFD packets use the IPv4 encapsulation mode and this keyword does not take effect.

ipv4: Specifies the IPv4 encapsulation mode for SBFD packets.

echo: Specifies the echo packet mode SBFD (echo SBFD).

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 remote discriminator configured by using the sbfd destination ipv4 remote-discriminator command is used.

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

backup-template backup-template-name: Specifies an SBFD session parameter template for the backup candidate path. 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 template specified by the template template-name option applies. If neither the template template-name nor the backup-template backup-template-name option is specified, SBFD uses the multihop SBFD session settings configured in system view for the backup candidate path.

Usage guidelines

This command enables SR-MPLS TE policies to use SBFD to detect availability of SID lists. If all SID lists for the current candidate path are faulty, another candidate path takes over to minimize service interruption.

You cannot enable echo SBFD for SR-MPLS TE policies with endpoint IPv6 addresses.

If both SBFD and echo BFD are enabled for an SR-MPLS TE policy, the device first establishes the SBFD session.

If both echo SBFD and echo BFD are enabled for an SR-MPLS TE policy, the device first establishes the echo SBFD session.

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

Examples

# Enable SBFD for all SR-MPLS TE policies.

<Sysname> system-view

[Sysname] segment-routing

[Sysname-segment-routing] traffic-engineering

[Sysname-sr-te] sr-policy sbfd enable

Related commands

bfd template (High Availability Command Reference)

egress-engineering peer-set

peer egress-engineering

sbfd

sbfd destination ipv4 remote-discriminator (High Availability Command Reference)

sr-policy sbfd timer

Use sr-policy sbfd timer to configure SBFD detection timer parameters.

Use undo sr-policy sbfd timer to delete SBFD detection timer parameters.

Syntax

sr-policy sbfd timer { detect-multiplier multiplier-value | min-tx-interval transmit-interval }

undo sr-policy sbfd timer { detect-multiplier | min-tx-interval }

Default

No SBFD detection timer parameters are configured.

Views

SR TE view

Predefined user roles

network-admin

Parameters

detect-multiplier multiplier-value: Specifies the SBFD detection time multiplier in the range of 3 to 50.

min-tx-interval transmit-interval: Specifies the minimum SBFD packet transmission interval in the range of 3 to 1000 milliseconds.

Usage guidelines

Set the minimum SBFD packet transmission interval to prevent the SBFD control packet sending rate from exceeding the device capability. The actual SBFD control packet transmitting interval is the set minimum interval.

The detection time multiplier determines the maximum number of SBFD control packets that an initiator can discard continuously. The detection time is the detection time multiplier of the initiator multiplied by the minimum SBFD packet transmission interval of the initiator.

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

Examples

# Set the minimum SBFD packet transmission interval to 100 milliseconds.

<Sysname> system-view

[Sysname] segment-grouting

[Sysname-segment-grouting] traffic-engineering

[Sysname-sr-te] sr-policy sbfd timer min-tx-interval 100

sr-policy switch-delay delete-delay

Use sr-policy switch-delay delete-delay to configure the switchover delay time and deletion delay time for the SR-MPLS TE policy forwarding path.

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

Syntax

sr-policy switch-delay switch-delay-time delete-delay delete-delay-time

undo sr-policy switch-delay

Default

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

Views

SR TE view

Predefined user roles

network-admin

Parameters

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

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

Usage guidelines

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

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

Examples

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

<Sysname> system-view

[Sysname] segment-grouting

[Sysname-segment-grouting] traffic-engineering

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

sr-policy up-delay

Use sr-policy up-delay to set the delay time for bringing up SR-MPLS TE policies.

Use undo sr-policy up-delay to restore the default.

Syntax

sr-policy up-delay delay-time

undo sr-policy up-delay

Default

The device does not delay bringing up SR-MPLS TE policies.

Views

SR TE view

Predefined user roles

network-admin

Parameters

delay-time: SR-MPLS TE policy-up delay time, in the range of 1 to 600000 milliseconds.

Usage guidelines

After an SR-MPLS TE policy recovers from a fault, the device waits for the delay time before bringing up the SR-MPLS TE policy. This is to ensure that the fault is completely removed so as to avoid packet loss caused by SR-MPLS TE policy flapping.

After this command is executed, the device starts different delay timers for an SR-MPLS TE policy according to the BFD/SBFD configuration for the SR-MPLS TE policy.

· If BFD/SBFD is not enabled, the device starts an LSP delay timer when the SID list state changes from Down to Up.

· If BFD/SBFD is enabled, the device starts a BFD delay timer when the BFD/SBFD session state changes from Down to Up.

To view the BFD/SBFD configuration, SID list state, and BFD/SBFD session state, execute the display segment-routing te policy command.

Set a proper SR-MPLS TE policy-up delay time according to your network conditions. A very long delay time will cause an SR-MPLS TE policy to be unable to process user traffic for a long time.

You can set the delay time for all SR-MPLS TE policies globally in SR TE view or for a specific SR-MPLS TE policy in SR-MPLS TE policy view. The policy-specific configuration takes precedence over the global configuration. An SR-MPLS TE policy uses the global configuration only when it has no policy-specific configuration.

If you execute this command for multiple times, the most recent configuration takes effect. A new delay time setting does not apply to the SR-MPLS TE policies that are already in a delay process.

Examples

# Set the policy-up delay time to 10000 milliseconds for all SR-MPLS TE policies.

<Sysname> system-view

[Sysname] segment-routing

[Sysname-segment-routing] traffic-engineering

[Sysname-sr-te] sr-policy up-delay 10000

Related commands

display segment-routing te policy

up-delay

strict-sid-only enable

Use strict-sid-only enable to enable strict SID encapsulation for SID lists.

Use undo strict-sid-only enable to disable strict SID encapsulation for SID lists.

Syntax

strict-sid-only enable

undo strict-sid-only enable

Default

Strict SID encapsulation is disabled for SID lists.

Views

SR-MPLS TE policy path preference dynamic view

SR-TE-ODN dynamic view

Predefined user roles

network-admin

Parameters

delay-time: SR-MPLS TE policy-up delay time, in the range of 1 to 600000 milliseconds.

Usage guidelines

Configure this command on the source node of an SR-MPLS TE policy.

The SID list of an SR-MPLS TE policy can be formed by prefix SIDs and adjacency SIDs. A prefix SID cannot uniquely identify a link. When the links in the network flap frequently, the forwarding paths of the SR-MPLS TE policy might change. To ensure stability of forwarding paths, use this command to enable the SR-MPLS TE policy to include only adjacency SIDs in the calculated SID lists.

Examples

# In SR-MPLS TE policy path preference dynamic view, enable strict SID encapsulation for SID lists.

<Sysname> system-view

[Sysname] segment-routing

[Sysname-segment-routing] traffic-engineering

[Sysname-sr-te] policy 1

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

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

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

[Sysname-sr-te-policy-1-path-pref-20-dyna] strict-sid-only enable

# In SR-TE-ODN dynamic view, enable strict SID encapsulation for SID lists.

<Sysname> system-view

[Sysname] segment-routing

[Sysname-segment-routing] traffic-engineering

[Sysname-sr-te] on-demand color 1

[Sysname-sr-te-odn-1] dynamic

[Sysname-sr-te-odn-1-dyna] strict-sid-only enable

traffic-engineering

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

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

Syntax

traffic-engineering

undo traffic-engineering

Default

The SR TE view does not exist.

Views

Segment routing view

Predefined user roles

network-admin

Examples

# Create and enter the SR TE view.

<Sysname> system-view

[Sysname] segment-routing

[Sysname-segment-routing] traffic-engineering

[Sysname-sr-te]

type

Use type to specify a metric for the SR-MPLS TE policy to perform dynamic path calculation.

Use undo type to restore the default.

Syntax

type { hopcount | igp | latency | te }

undo type

Default

No metric is specified. The SR-MPLS TE policy cannot perform dynamic path calculation.

Views

Metric type view

SR-TE-ODN dynamic metric type view

Predefined user roles

network-admin

Parameters

hopcount: Specifies the hop count metric to select the link with minimum hops.

igp: Specifies the IGP link cost metric to select the link with minimum IGP link cost.

latency: Specifies the lowest interface latency metric to select the link with the lowest interface latency.

te: Specifies the TE cost metric to select the link with minimum TE cost.

Examples

# Specify the hop count metric in metric type view.

<Sysname> system-view

[Sysname]segment-routing

[Sysname-segment-routing] traffic-engineering

[Sysname-sr-te] policy p1

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

[Sysname-sr-te-policy-p1-path] preference 10

[Sysname-sr-te-policy-p1-path-pref-10] dynamic

[Sysname-sr-te-policy-p1-path-pref-10-dyna] metric

[Sysname-sr-te-policy-p1-path-pref-10-dyna-metric] type hopcount

# Specify the hop count metric in SR-TE-ODN dynamic metric type view.

<Sysname> system-view

[Sysname] segment-routing

[Sysname-segment-routing] traffic-engineering

[Sysname-sr-te] on-demand color 1

[Sysname-sr-te-odn-1] dynamic

[Sysname-sr-te-odn-1-dynamic] metric

[Sysname-sr-te-odn-1-dynamic-metric] type hopcount

up-delay

Use up-delay to set the delay time for bringing up an SR-MPLS TE policy.

Use undo up-delay to restore the default.

Syntax

up-delay delay-time

undo up-delay

Default

No policy-up delay time is set for an SR-MPLS TE policy, and the policy-up delay time set in SR TE view applies.

Views

SR-MPLS TE policy view

Predefined user roles

network-admin

Parameters

delay-time: SR-MPLS TE policy-up delay time, in the range of 1 to 600000 milliseconds.

Usage guidelines

After this command is executed, the device starts different delay timers for an SR-MPLS TE policy according to the BFD/SBFD configuration for the SR-MPLS TE policy.

· If BFD/SBFD is not enabled, the device starts an LSP delay timer when the SID list state changes from Down to Up.

· If BFD/SBFD is enabled, the device starts a BFD delay timer when the BFD/SBFD session state changes from Down to Up.

To view the BFD/SBFD configuration, SID list state, and BFD/SBFD session state, execute the display segment-routing te policy command.

Set a proper SR-MPLS TE policy-up delay time according to your network conditions. A very long delay time will cause an SR-MPLS TE policy to be unable to process user traffic for a long time.

If you execute this command for multiple times, the most recent configuration takes effect. A new delay time setting does not apply to the SR-MPLS TE policies that are already in a delay process.

Examples

# Set the policy-up delay time to 10000 milliseconds for SR-MPLS TE policy p1.

<Sysname> system-view

[Sysname] segment-routing

[Sysname-segment-routing] traffic-engineering

[Sysname-sr-te ]policy p1

[Sysname-sr-te-policy-p1] up-delay 10000

Related commands

display segment-routing te policy

sr-policy up-delay

10-Segment Routing Command Reference

address-family ipv4 sr-policy

affinity (SR-TE-ODN dynamic view)

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

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

display bgp routing-table ipv4 sr-policy

display pce segment-routing policy database

dynamic (SR-MPLS TE policy path preference view)

import-route sr-policy

pcep (SR-TE-ODN dynamic view)

pcep (SR-MPLS TE policy path preference dynamic view)

Intelligent Terminal Products

Product Support Services

Technical Service Solutions

Resource Center

Policy

Online Help

Become a Partner

Partner Policy & Program

Global Learning

Partner Sales Resources

Service Business

News & Events

Contact Us