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

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

Syntax

address-family ipv6 sr-policy

undo address-family ipv6 sr-policy

Default

The BGP IPv6 SR policy address family does not exist.

Views

BGP instance view

Predefined user roles

network-admin

Usage guidelines

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

Examples

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

<Sysname> system-view

[Sysname] bgp 100

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

[Sysname-bgp-default-srpolicy-ipv6]

advertise ebgp enable

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

Use undo advertise ebgp enable to restore the default.

Syntax

advertise ebgp enable

undo advertise ebgp enable

Default

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

Views

BGP IPv6 SR policy address family

Predefined user roles

network-admin

Usage guidelines

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

Examples

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

<Sysname> system-view

[Sysname] bgp 100

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

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

autoroute enable

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

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

Syntax

autoroute enable [ isis | ospfv3 ]

undo autoroute enable

Default

Automatic route advertisement is disabled for an SRv6 TE policy.

Views

SRv6 TE policy view

Predefined user roles

network-admin

Parameters

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

ospfv3: Enables automatic route advertisement for OSPFv3.

Usage guidelines

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

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

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

Examples

# Enable automatic route advertisement for an SRv6 TE policy.

<Sysname> system-view

[Sysname] segment-routing ipv6

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

[Sysname-srv6-te] policy srv6policy

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

Related commands

autoroute metric

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

Use undo autoroute metric to restore the default.

Syntax

autoroute metric { absolute value | relative value }

undo autoroute metric

Default

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

Views

SRv6 TE policy view

Predefined user roles

network-admin

Parameters

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

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

Usage guidelines

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

Examples

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

<Sysname> system-view

[Sysname] segment-routing ipv6

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

[Sysname-srv6-te] policy srv6policy

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

Related commands

autoroute enable

backup hot-standby

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

Use undo backup hot-standby to restore the default.

Syntax

backup hot-standby { disable | enable }

undo backup hot-standby

Default

Hot standby is not configured for an SRv6 TE policy.

Views

SRv6 TE policy view

Predefined user roles

network-admin

Parameters

disable: Disables hot standby for the SRv6 TE policy.

enable: Enables hot standby for the SRv6 TE policy.

Usage guidelines

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

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

Examples

# Enable hot standby for SRv6 TE policy 1.

<Sysname> system-view

[Sysname] segment-routing ipv6

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

[Sysname-srv6-te] policy 1

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

Related commands

srv6-policy backup hot-standby enable

bandwidth sample

Use bandwidth sample to configure bandwidth sampling for an SRv6 TE IPR policy.

Use undo bandwidth sample to restore the default.

Syntax

bandwidth sample { disable | enable }

undo bandwidth sample

Default

Bandwidth sampling is not configured for an SRv6 TE IPR policy. An SRv6 TE IPR policy uses the configuration in SRv6 TE view.

Views

SRv6 TE IPR policy view

Predefined user roles

network-admin

Parameters

enable: Enables bandwidth sampling.

disable: Disables bandwidth sampling.

Usage guidelines

Application scenarios

After you enable bandwidth sampling for an IPR policy, the device can use the policy to perform optimal SRv6 TE policy selection based on bandwidth usage. An SRv6 TE policy can participate in optimal SRv6 TE policy selection only when it meets the following requirements:

· The network quality (including delay, jitter, and packet loss) of the SRv6 TE policy complies with the SLA standards defined in the IPR policy.

· The bandwidth usage of the SRv6 TE policy does not exceed the upper threshold specified in the bandwidth-threshold upper command.

If bandwidth sampling is not enabled for an IPR policy, an SRv6 TE policy can participate in optimal SRv6 TE policy selection as long as its network quality (including delay, jitter, and packet loss) complies with the SLA standards defined in the IPR policy.

Operating mechanism

After you enable bandwidth sampling for an IPR policy, the device operates as follows:

1. Collects the egress interface bandwidth usage of each SRv6 TE policy at the interval specified in the srv6-policy bandwidth sample interval command.

2. Calculates the expected average bandwidth usage of each SRv6 TE policy.

3. Selects the optimal SRv6 TE policy.

An SRv6 TE policy can participate in optimal path selection if its expected average bandwidth usage does not exceed the upper limit specified in the bandwidth-threshold upper command. The device selects the SRv6 TE policy with the smallest path selection priority as the optimal policy. You can use the srv6-policy color priority command to configure the path selection priority of an SRv6 TE policy.

The expected average bandwidth usage of an SRv6 TE policy is the ratio of the sum of the bandwidth of the new service using this SRv6 TE policy and the bandwidth already used by the egress interface to the total bandwidth of the egress interface. The calculation method is as follows:

· If the optimal candidate path of the SRv6 TE policy contains only one SID list, and the first SID in that list has only one egress interface, the expected average bandwidth usage of the SRv6 TE policy = (expected service bandwidth + current bandwidth used by the egress interface) / total bandwidth of the egress interface. The expected service bandwidth is determined as follows:

¡ Use the real-time statistics of the SRv6 TE policy currently carrying the service as the expected service bandwidth.

¡ If the SRv6 TE policy is not carrying the specified service or no traffic statistics exists for the SRv6 TE policy, the SRv6 TE policy service expected bandwidth configured in the expect-bandwidth command in SRv6 TE policy view is used.

¡ If no service expected bandwidth is configured in the SRv6 TE policy view, the SRv6 TE IPR policy service expected bandwidth specified in the expect-bandwidth command in SRv6 TE IPR policy view is used.

· If the optimal candidate path of the SRv6 TE policy contains multiple SID lists or if the first SID in the SID list has multiple equal-cost egress interfaces, the calculation of the expected average bandwidth usage of the SRv6 TE policy is more complex. For the following SRv6 TE policy, the method to calculate the expected average bandwidth usage is as follows:

SRv6 TE Policy A

Candidate paths(Preference 200)

Segment List1(weight 10) interface1 bw1 30%

interface2 bw2 50%

Segment List2(weight 30) interface3 bw3 80%

For SRv6 TE policy A, the optimal candidate path contains SID list 1 with a weight of 10 and SID list 2 with a weight of 30. The first SID in SID list 1 has two equal-cost egress interfaces: interface1 (bandwidth = bw1) and interface2 (bandwidth = bw2). The first SID in SID list 2 has only one egress interface: interface3 (bandwidth = bw3). The current bandwidth usage of interface1, interface2, and interface3 is 30%, 50%, and 80%, respectively.

Based on the current bandwidth usage of the equal-cost egress interfaces, the average bandwidth usage of these interfaces is taken as the bandwidth usage of SID list 1, which is (30% + 50%)/2 = 40%.

The bandwidth usage of SID list 2 is the current bandwidth usage of egress interface3, which is 80%.

Based on the weights and bandwidth usage of different SID lists, use a weighted average approach to calculate the bandwidth usage of SRv6 TE policy A as (40% × 10 + 80% × 30)/(10 + 30) = 70%.

The expected average bandwidth usage of SRv6 TE policy A is calculated as follows:

(Expected service bandwidth + 70% × (bw1 + bw2 + bw3))/(bw1 + bw2 + bw3).

Restrictions and guidelines

· In scenarios where the optimal candidate path of an SRv6 TE policy contains multiple SID lists or the first SID in the SID list has multiple equal-cost egress interfaces, the calculation of the expected average bandwidth usage of the SRv6 TE policy cannot accurately reflect the bandwidth usage of each interface. Therefore, when you use IPR for SRv6 TE policy to select the optimal SRv6 TE policy based on bandwidth usage, make sure the optimal candidate path of the SRv6 TE policy contains only one SID list and that this SID list has only one egress interface.

· IPR for SRv6 TE policy uses the expect-bandwidth command to specify the expected service bandwidth to calculate the expected average bandwidth usage during only the first optimal SRv6 TE policy selection. After IPR selects the optimal SRv6 TE policy, it performs periodic path optimization (switching and reverting based on the quality and bandwidth of the SRv6 TE policy). At this time, the expected average bandwidth usage is calculated using the current optimal SRv6 TE policy's real-time service traffic bandwidth data as the expected service bandwidth. For example, if the real-time service traffic bandwidth of the current optimal SRv6 TE policy A is 100 Mbps, IPR calculates the expected average bandwidth usage of SRv6 TE policy B as (100 Mbps + the used bandwidth of the egress interface of SRv6 TE policy B)/the total bandwidth of the egress interface of SRv6 TE policy B. IPR determines whether SRv6 TE policy B meets the bandwidth usage requirement based on this calculation.

· When you use IPR for SRv6 TE policy to select the optimal SRv6 TE policy based on bandwidth usage, as a best practice, create SRv6 TE policies referenced by the IPR policy to carry only a single service, and do not reuse the same SRv6 TE policy among different services. For example, the service mapped to TE class ID 1000 should be forwarded through the preferred SRv6 TE policy A (color 100) in the IPR policy. Since IPR performs path optimization based on bandwidth usage by using the real-time traffic statistics of the preferred SRv6 TE policy A to calculate the expected average bandwidth usage of each SRv6 TE policy, if SRv6 TE policy A carries not only the service of TE class ID 1000 but also other services, the real-time traffic statistics will be inaccurate, leading to inaccurate expected average bandwidth usage calculations. SRv6 TE policies with different color values can be created between the ingress node and the egress node to carry other service traffic.

· You can execute the srv6-policy bandwidth sample command in SRv6 TE view to enable global bandwidth sampling, and execute the bandwidth sample command in SRv6 TE IPR policy view to enable bandwidth sampling. The configuration in SRv6 TE view applies to all IPR policies, while the configuration in SRv6 TE IPR policy view applies only to the IPR policy. For an IPR policy, the configuration in SRv6 TE IPR policy view takes precedence. The policy uses the configuration in SRv6 TE view only when the SRv6 TE IPR policy view does not have the configuration.

· Execute the forwarding statistics command or the srv6-policy forwarding statistics enable command to enable traffic forwarding statistics for all SRv6 TE policies associated with the IPR policy. This ensures that path optimization based on bandwidth usage by IPR for SRv6 TE policy is more accurate.

Examples

# Enable bandwidth sampling for SRv6 TE IPR policy ipr1.

<Sysname> system-view

[Sysname] segment-routing ipv6

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

[Sysname-srv6-te] intelligent-policy-route

[Sysname-srv6-ipr] ipr-policy ipr1

[Sysname-srv6-ipr-policy-ipr1] bandwidth sample enable

Related commands

bandwidth-threshold upper

expect-bandwidth

srv6-policy bandwidth sample

bandwidth-threshold switch-back

Use bandwidth-threshold switch-back to configure the bandwidth usage threshold that triggers service switchback for an IPR policy.

Use undo bandwidth-threshold switch-back to restore the default.

Syntax

bandwidth-threshold switch-back threshold-value

undo bandwidth-threshold switch-back

Default

The bandwidth usage threshold that triggers service switchback is 70% for an IPR policy.

Views

SRv6 TE IPR policy view

Predefined user roles

network-admin

Parameters

threshold-value: Specifies the bandwidth usage threshold that triggers service switchback, in the range of 1% to 100%.

Usage guidelines

Operating mechanism

When IPR performs path optimization at the interval specified in the refresh-period command, if it detects that one or more SRv6 TE policies have higher path selection priorities than the current SRv6 TE policy carrying the service traffic, and the following conditions are met:

· The expected average bandwidth usage of this SRv6 TE policy is less than or equal to Min (the bandwidth usage threshold for service switchback configured in the bandwidth-threshold switch-back command in the IPR policy, and the lower bandwidth threshold configured by the srv6-policy bandwidth-threshold lower command). Min(a, b) indicates the smaller value of a and b. If the srv6-policy bandwidth-threshold lower command is not configured, the value configured by the bandwidth-threshold switch-back command in the IPR policy is used.

· The quality indicators such as latency, jitter, and packet loss for the service traffic in this SRv6 TE policy meet the SLA standards defined in the IPR policy.

Then, after the switchback delay timer (specified by the wait-to-restore-period command) expires, the device will switch the service traffic from the current SRv6 TE policy back to the SRv6 TE policy with a higher path selection priority.

Restrictions and guidelines

When you execute this command, make sure the specified switchback bandwidth threshold does not exceed the upper bandwidth threshold of the IPR policy configured by the bandwidth-threshold upper command. As a best practice, configure a significant difference between the switchback bandwidth threshold and the upper bandwidth threshold of the IPR policy to prevent frequent service switching caused by bandwidth fluctuations on the interface.

Examples

# Configure the bandwidth usage threshold that triggers service switchback to 75% for IPR policy ipr1.

<Sysname> system-view

[Sysname] segment-routing ipv6

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

[Sysname-srv6-te] intelligent-policy-route

[Sysname-srv6-ipr] ipr-policy ipr1

[Sysname-srv6-ipr-policy-ipr1] bandwidth-threshold switch-back 75

Related commands

bandwidth-threshold upper

refresh-period

srv6-policy bandwidth-threshold lower

wait-to-restore-period

bandwidth-threshold upper

Use bandwidth-threshold upper to configure the upper limit of bandwidth usage for an IPR policy.

Use undo bandwidth-threshold upper to restore the default.

Syntax

bandwidth-threshold upper upper-value

undo bandwidth-threshold upper

Default

The upper limit of bandwidth usage is 90% for an IPR policy.

Views

SRv6 TE IPR policy view

Predefined user roles

network-admin

Parameters

upper-value: Specifies the upper limit of bandwidth usage, in the range of 1% to 100%.

Usage guidelines

Application scenarios

IPR for SRv6 TE policy can perform optimal SRv6 TE policy selection based on bandwidth usage.

An SRv6 TE policy can participate in optimal SRv6 TE policy selection only when it meets the following requirements:

· The network quality (including delay, jitter, and packet loss) of the SRv6 TE policy complies with the SLA standards defined in the IPR policy.

· The bandwidth usage of the SRv6 TE policy does not exceed the upper threshold specified in the bandwidth-threshold upper command.

Operating mechanism

· When IPR selects an SRv6 TE policy for the first time based on bandwidth usage, the expected average bandwidth usage of the SRv6 TE policy must be smaller than or equal to the upper bandwidth threshold configured in the bandwidth-threshold upper command. The expected average bandwidth usage of an SRv6 TE policy is (expected service bandwidth + currently used bandwidth on the egress interface)/total bandwidth of the egress interface. The expected service bandwidth is preferentially taken from the value specified by the expect-bandwidth command in SRv6 TE policy view. If the expected bandwidth is not configured in SRv6 TE policy view, the value specified by the expect-bandwidth command in SRv6 TE IPR policy view is used.

· When IPR performs path optimization periodically at the interval specified by the refresh-period command to select the optimal SRv6 TE policy. If the bandwidth usage of the current SRv6 TE policy carrying the service exceeds the upper bandwidth threshold specified by the bandwidth-threshold upper command, the device will wait for the switch timer specified by the switch-period command to expire, and then switch the service traffic to an SRv6 TE policy that meets all of the following conditions:

¡ The expected average bandwidth usage of the SRv6 TE policy does not exceed the upper bandwidth threshold specified by the bandwidth-threshold upper command.

¡ The quality indicators of the service traffic in this SRv6 TE policy (such as latency, jitter, and packet loss) meet the SLA standards defined in the IPR policy.

¡ The SRv6 TE policy has the highest path selection priority, that is, the lowest path selection priority value as specified by the srv6-policy color priority command.

If the current SRv6 TE policy carrying the service has only one SID list in the optimal candidate paths, and that SID list has only one egress interface, the bandwidth usage of the SRv6 TE policy is equal to the bandwidth usage of this egress interface.

Restrictions and guidelines

During path optimization, if multiple SRv6 TE policies meet the requirements and have the same path selection priority, the service traffic will be load balanced among these SRv6 TE policies.

If no SRv6 TE policy in the IPR policy meets all of the above conditions, the service traffic will be forwarded according to the default forwarding policy specified by the default match command.

Examples

# Configure the upper limit of bandwidth usage as 85% for IPR policy ipr1.

<Sysname> system-view

[Sysname] segment-routing ipv6

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

[Sysname-srv6-te] intelligent-policy-route

[Sysname-srv6-ipr] ipr-policy ipr1

[Sysname-srv6-ipr-policy-ipr1] bandwidth-threshold upper 85

Related commands

bandwidth sample

expect-bandwidth

refresh-period

srv6-policy bandwidth sample

switch-period

bestroute encap-type

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

Use undo bestroute encap-type to restore the default.

Syntax

bestroute encap-type { mpls | srv6 } [ preferred ]

undo bestroute encap-type

Default

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

Views

BGP-VPN instance view.

Predefined user roles

network-admin

Parameters

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

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

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

Usage guidelines

For more information about the priority order of the configuration in this command in BGP route selection, see BGP overview in Layer 3—IP Routing Configuration Guide.

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

Examples

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

<Sysname> system-view

[Sysname] bgp 100

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

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

bfd echo

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

Use undo bfd echo to restore the default.

Syntax

bfd echo { disable | enable [ source-ipv6 ipv6-address ] [ template template-name ] [ backup-template backup-template-name ] [ oam-sid sid ] [ encaps | insert ] [ reverse-path reverse-binding-sid ] }

undo bfd echo

Default

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

Views

SRv6 TE policy view

Predefined user roles

network-admin

Parameters

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

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

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

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

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

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

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

insert: Uses the insertion mode to encapsulate BFD packets.

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

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

Usage guidelines

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

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

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

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

By default, the BFD return packets used for SRv6 TE policy connectivity detection are forwarded based on the IP forwarding path. If a transit node fails, all the return packets will be discarded, and the BFD sessions will go down as a result. BFD thus will mistakenly determine that all the SID lists of the SRv6 TE policy are faulty. To resolve this issue, you can enable BFD return packets to be forwarded based on the specified SID list to implement BFD forward and reverse path consistency. After the reverse-path reverse-binding-sid parameters are configured, the source node will insert an SRH header into a BFD packet and encapsulate the reverse BSID to the SL=1 position in the SRH header. You can specify the reverse BSID by using the explicit segment-list or reverse-binding-sid command. Upon receiving the BFD packet, the endpoint node retrieves the reverse BSID. If the reverse BSID matches the local BSID of an SRv6 TE policy on the endpoint node, the endpoint node inserts a new SRH into the BFD packet and forwards the packet along the SID list of that SRv6 TE policy. (To specify a local BSID for an SRv6 TE policy, use the local-binding-sid command.)

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

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

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

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

Examples

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

<Sysname> system-view

[Sysname] segment-routing ipv6

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

[Sysname-srv6-te] policy 1

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

Related commands

bfd srv6-encapsulation-mode insert

explicit segment-list

display segment-routing ipv6 te bfd

srv6-policy bfd echo

bfd srv6-encapsulation-mode insert

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

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

Syntax

bfd srv6-encapsulation-mode insert

undo bfd srv6-encapsulation-mode insert

Default

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

Views

System view

Predefined user roles

network-admin

Usage guidelines

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

· Insert—Insertion mode. It inserts an SRH after the original IPv6 header. All SIDs in the SID list of the SRv6 TE policy are encapsulated in the SRH. If the length of the SID list is 0, the SRH is not inserted.

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

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

Examples

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

<Sysname> system-view

[Sysname] bfd srv6-encapsulation-mode insert

Related commands

bfd echo

sbfd

binding-sid (SRv6 TE policy group view)

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

Use undo binding-sid to delete the BSID of an SRv6 TE policy group.

Syntax

binding-sid ipv6 ipv6-address

undo binding-sid

Default

No BSID is configured for an SRv6 TE policy group.

Views

SRv6 TE policy group view

Predefined user roles

network-admin

Parameters

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

Usage guidelines

You can use only this command to manually configure a BSID for an SRv6 TE policy group. Traffic will be steered to the SRv6 TE policy group based on the BSID.

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

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

Examples

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

<Sysname> system-view

[Sysname] segment-routing ipv6

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

[Sysname-srv6-te] policy-group 1

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

binding-sid (SRv6 TE policy view)

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

Use undo binding-sid to delete the BSID.

Syntax

binding-sid ipv6 ipv6-address

undo binding-sid

Default

No BSID is configured for an SRv6 TE policy.

Views

SRv6 TE policy view

Predefined user roles

network-admin

Parameters

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

Usage guidelines

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

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

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

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

Examples

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

<Sysname> system-view

[Sysname] segment-routing ipv6

[Sysname-segment-routing-ipv6] traffic engineering

[Sysname-srv6-te] policy srv6policy

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

bypass enable

Use bypass enable to enable the bypass feature for an SRv6 TE policy.

Use undo bypass enable to disable the SRv6 TE policy bypass feature.

Syntax

bypass enable

undo bypass enable

Default

The SRv6 TE policy bypass feature is disabled.

Views

SRv6 TE policy view

Predefined user roles

network-admin

Usage guidelines

If the first SID in the SID list of an SRv6 TE policy is unreachable, the source node of the SRv6 TE policy will place the policy to down state. The device cannot forward packets through the SRv6 TE policy or trigger SRv6 TE FRR.

To resolve this issue, you can enable the bypass feature for the SRv6 TE policy on the source node. This feature enables the source node to generate a route that uses the first SID as the destination address and the NULL0 interface as the outgoing interface. The route ensures that the SRv6 TE policy is in up state when the first SID is unreachable, so as to trigger SRv6 TE FRR.

Examples

# Enable the bypass feature for an SRv6 TE policy.

<Sysname> system-view

[Sysname] segment-routing ipv6

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

[Sysname-srv6–te] policy 1

[Sysname-srv6–te-policy-1] bypass enable

Related commands

sr-te frr enable

candidate-paths

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

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

Syntax

candidate-paths

undo candidate-paths

Default

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

Views

SRv6 TE policy view

Predefined user roles

network-admin

Examples

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

<Sysname> system-view

[Sysname] segment-routing ipv6

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

[Sysname-srv6-te] policy srv6policy

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

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

cmi threshold

Use cmi threshold to set the Composite Measure Indicator (CMI) threshold in an IPR policy.

Use undo cmi threshold to restore the default.

Syntax

cmi threshold threshold-value

undo cmi threshold

Default

The CMI threshold in an IPR policy is 9000.

Views

SRv6 TE IPR policy view

Predefined user roles

network-admin

Parameters

threshold-value: Specifies a CMI threshold value in the range of 0 to 9000.

Usage guidelines

CMI is a comprehensive indicator for measuring service quality. The CMI of a service = delay (milliseconds) + jitter (milliseconds) + packet loss rate (‰). The smaller the CMI value, the higher the link quality requirements.

An SRv6 TE policy can participate in optimal SRv6 TE policy selection as a candidate forwarding path only when the sum of the iFIT packet loss rate, delay, and jitter detected for that SRv6 TE policy do not cross the CMI threshold set by this command.

Examples

# Set the CMI threshold to 300 in IPR policy ipr1.

<Sysname> system-view

[Sysname] segment-routing ipv6

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

[Sysname-srv6-te] intelligent-policy-route

[Sysname-srv6-ipr] ipr-policy ipr1

[Sysname-srv6-ipr-policy-ipr1] cmi threshold 300

color end-point

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

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

Syntax

color color-value end-point ipv6 ipv6-address

undo color

Default

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

Views

SRv6 TE policy view

Predefined user roles

network-admin

Parameters

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

Ipv6-address: Specifies the endpoint IPv6 address.

Usage guidelines

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

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

Examples

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

<Sysname> system-view

[Sysname] segment-routing ipv6

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

[Sysname-srv6-te] policy srv6policy

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

color match dscp (DSCP forward type view)

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

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

Syntax

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

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

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

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

Default

No color-to-DSCP mappings are created for the SRv6 TE policy group ODN template.

Views

DSCP forward type view

Predefined user roles

network-admin

Parameters

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

ipv4: Specifies DSCP values of IPv4 packets.

ipv6: Specifies DSCP values of IPv6 packets.

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

default: Configures a default color-to-DSCP mapping. Packets that do not match any mappings are steered to the SRv6 TE policy associated with the color attribute value in the default mapping. This SRv6 TE policy is used as the default SRv6 TE policy for packets in the specified address family.

Usage guidelines

About this task

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

Operating mechanism

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

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

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

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

4. Handles the packet according to whether the drop-upon-mismatch enable command is used.

¡ If the drop-upon-mismatch enable command is used, the device discards the packet.

¡ If the drop-upon-mismatch enable command is not used, the device identifies whether the SRv6 TE policy group is configured with color-to-DSCP mappings in the current address family:

- If yes, the device searches the current address family for a mapping with the smallest DSCP value and a valid SRv6 TE policy. The device will use that SRv6 TE policy to forward the packet.

- If not, the device turns to other address families (where the SRv6 TE policy group is configured with color-to-DSCP mappings) for a mapping with the smallest DSCP value and a valid SRv6 TE policy. The device will use that SRv6 TE policy to forward the packet.

Restrictions and guidelines

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

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

Examples

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

<Sysname> system-view

[Sysname] segment-routing ipv6

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

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

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

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

Related commands

drop-upon-mismatch enable

color match dscp (SRv6 TE policy group view)

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

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

Syntax

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

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

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

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

Default

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

Views

SRv6 TE policy group view

Predefined user roles

network-admin

Parameters

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

ipv4: Specifies DSCP values of IPv4 packets.

ipv6: Specifies DSCP values of IPv6 packets.

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

Usage guidelines

About this task

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

Operating mechanism

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

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

4. Handles the packet according to whether the drop-upon-mismatch enable command is used.

¡ If the drop-upon-mismatch enable command is used, the device discards the packet.

¡ If the drop-upon-mismatch enable command is not used, the device identifies whether the SRv6 TE policy group is configured with color-to-DSCP mappings in the current address family:

- If yes, the device searches the current address family for a mapping with the smallest DSCP value and a valid SRv6 TE policy. The device will use that SRv6 TE policy to forward the packet.

Restrictions and guidelines

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

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

Examples

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

<Sysname> system-view

[Sysname] segment-routing ipv6

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

[Sysname-srv6-te] policy-group 10

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

Related commands

drop-upon-mismatch enable

default match (TE class ID-based traffic steering)

Use default match to configure the default forwarding policy for TE class ID-based traffic steering.

Use undo default match to remove a default forwarding policy setting for TE class ID-based traffic steering.

Syntax

default match best-effort

undo default match best-effort

default match { ipr-policy ipr-name | srv6-policy color color-value }

undo default match { ipr-policy ipr-name | srv6-policy color color-value }

Default

No default forwarding policy is configured for TE class ID-based traffic steering.

Views

SRv6 TE policy group view

TE class forward type view

Predefined user roles

network-admin

Parameters

best-effort: Specifies SRv6 BE mode in the default forwarding policy. In this mode, the device adds a new IPv6 header to original packets and performs an IPv6 routing table lookup to forward the packets.

ipr-policy ipr-name: Specifies an IPR policy by its name in the default forwarding policy. The ipr-name argument represents the name of the IPR policy, which is a case-sensitive string of 1 to 31 characters.

srv6-policy color color-value: Specifies an SRv6 TE policy by its color attribute value in the default forwarding policy. The value range for the color-value argument is 0 to 4294967295.

Usage guidelines

This command can take effect on an SRv6 TE policy group only when the forward type of the SRv6 TE policy group is TE class. To configure the forward type, you can use the forward-type te-class command in SRv6 TE policy group view.

The device uses the default forwarding policy to forward the following packets after the packets are steered to the SRv6 TE policy group for forwarding:

· The packets that do not have a TE class ID.

· The packets that have a TE class ID not mapped to any forwarding policy specified by using the index te-class match command.

· The packets that have a TE class ID mapped to an invalid forwarding policy.

You can configure a maximum of two forwarding methods in the default forwarding policy. However, IPR forwarding and SRv6 TE policy forwarding cannot coexist. When packets are forwarded according to the default forwarding policy, the device selects a forwarding method in the following order:

1. If a color attribute value or an IPR policy is specified in the default forwarding policy and the SRv6 TE policy used to forward the packets are valid, the device steers the traffic to that SRv6 TE policy for forwarding.

2. If the SRv6 BE mode is specified in the default forwarding policy and the SRv6 BE mode is valid, the device encapsulates a new IPv6 header to the packets and looks up the IPv6 routing table to forward the packets.

3. If the default match command is not executed or the forwarding policy specified in the command is invalid, the device handles the packet depending on whether the drop-upon-mismatch enable command is used.

¡ If the drop-upon-mismatch enable command is used, the device discards the packet.

¡ If the drop-upon-mismatch enable command is not used and the index te-class match command is used, the device searches for the TE class ID-to-forwarding policy mapping with the smallest index value and a valid forwarding policy. The device will use the SRv6 TE policy pointed by the mapping to forward the packet or forward the packet in SRv6 BE mode.

Examples

# In an SRv6 TE policy group, specify the SRv6 TE policy associated with color attribute value 8 in the default forwarding policy for TE class ID-based traffic forwarding.

<Sysname> system-view

[Sysname] segment-routing ipv6

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

[Sysname-srv6-te] policy-group 1

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

[Sysname-srv6-te-policy-group-1] default match srv6-policy color 8

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

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

Use undo default-color to restore the default.

Syntax

default-color color-value

undo default-color

Default

No default color value is configured.

Views

Public instance IPv4 address family view

Public instance IPv6 address family view

Predefined user roles

network-admin

Parameters

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

Usage guidelines

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

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

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

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

Examples

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

<Sysname> system-view

[Sysname] ip public-instance

[Sysname-public-instance] address-family ipv4

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

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

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

Use undo default-color to restore the default.

Syntax

default-color color-value [ evpn ]

undo default-color [ evpn ]

Default

No default color value is configured.

Views

VPN instance IPv4 address family view

VPN instance IPv6 address family view

Predefined user roles

network-admin

Parameters

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

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

Usage guidelines

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

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

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

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

Examples

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

<Sysname> system-view

[Sysname] ip vpn-instance vpn1

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

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

delay threshold

Use delay threshold to set the delay threshold in an IPR policy.

Use undo delay threshold to restore the default.

Syntax

delay threshold time-value

undo delay threshold

Default

The delay threshold is 5000 milliseconds in an IPR policy.

Views

SRv6 TE IPR policy view

Predefined user roles

network-admin

Parameters

time-value: Specifies a delay threshold value in the range of 0 to 5000, in milliseconds.

Usage guidelines

An SRv6 TE policy can be used as a candidate forwarding path and participate in optimal SRv6 TE policy selection only when the iFIT delay and jitter measurement feature detects that the delay of the SRv6 TE policy do not cross the delay threshold set by this command.

If the optimal candidate path of an SRv6 TE policy has multiple valid SID lists with weight values, the device uses the weighted sum of the iFIT delays of all of these valid SID lists as the delay value of that SRv6 TE policy when intelligent policy routing computes whether the delay of that SRv6 TE policy crosses the threshold.

Examples

# Set the delay threshold to 50 milliseconds in IPR policy ipr1.

<Sysname> system-view

[Sysname] segment-routing ipv6

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

[Sysname-srv6-te] intelligent-policy-route

[Sysname-srv6-ipr] ipr-policy ipr1

[Sysname-srv6-ipr-policy-ipr1] delay threshold 50

description

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

Use undo description to restore the default.

Syntax

description text

undo description

Default

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

Views

SRv6 TE ODN policy group view

Predefined user roles

network-admin

Parameters

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

Usage guidelines

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

Examples

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

<Sysname> system-view

[Sysname] segment-routing ipv6

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

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

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

display bgp mirror remote-sid

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

Syntax

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

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

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

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

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

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

sid: Specifies a remote SRv6 SID.

Usage guidelines

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

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

Examples

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

<Sysname> display bgp mirror remote-sid

Remote SID: 3001::1:0:0

Remote SID type: End.DT4

Mirror locator: 3001::1/64

VPN instance name: vrf1

Remote SID: 3001::1:0:1

Remote SID type: End.DT6

Mirror locator: 3001::1/64

VPN instance name: vrf2

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

Remote SID type: End.DT6

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

VPN instance name: vrf1

Table 1 Command output

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

‌

display bgp routing-table ipv6 sr-policy

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

Syntax

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

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

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

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

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

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

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

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

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

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

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

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

statistics: Displays route statistics.

Usage guidelines

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

Examples

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

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

Total number of routes: 1

BGP local router ID is 2.2.2.2

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

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

a – additional-path

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

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

NextHop : 1::2 LocPrf : 100

PrefVal : 0 MED : 0

Path/Ogn: i

Table 2 Command output

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

‌

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

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

BGP local router ID: 5.5.5.1

Local AS number: 100

Paths: 1 available, 1 best

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

Imported route.

Original nexthop: ::

Output interface: p1

Route age : 19h45m02s

OutLabel : NULL

RxPathID : 0x0

TxPathID : 0x0

AS-path : (null)

Origin : igp

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

State : valid, local, best

IP precedence : N/A

QoS local ID : N/A

Traffic index : N/A

Tunnel encapsulation info:

Type: 15 (SR policy)

Policy name: p1

Binding SID: 2::6

Preference: 100

Path: 1

Weight: 1

SIDs: {2::2}

Table 3 Command output

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

‌

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

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

‌

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

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

BGP local router ID: 2.2.2.2

Local AS number: 1

Paths: 1 best

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

Advertised to peers (2 in total):

1::1

3::3

Table 5 Command output

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

‌

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

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

Advertised routes total: 2

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

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

Received routes total: 1

Table 6 Command output

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

‌

# Display statistics about BGP IPv6 SR policy routes.

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

Total number of routes: 3

display segment-routing ipv6 te bfd

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

Syntax

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

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

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

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

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

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

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

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

Usage guidelines

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

Examples

# Display BFD information for all SRv6 TE policies.

<Sysname> display segment-routing ipv6 te policy bfd

Color: 10

Endpoint: 4::4

Policy name: p1

State: Up

Nid: 2149580801

BFD type: ECHO

Source IPv6: 1::1

State: Up

Timer: 37

VPN index: 1

Template name: abc

Table 7 Command output

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

‌

display segment-routing ipv6 te forwarding

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

Syntax

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

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

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

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

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

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

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

Examples

# Display brief information about all SRv6 TE policies.

<Sysname> display segment-routing ipv6 te forwarding

Total forwarding entries: 1

Policy name/ID: p1/0

Binding SID: 8000::1

Forwarding index: 2150629377

Main path:

Seglist ID: 1

Seglist forwarding index: 2149580801

Weight: 1

Outgoing forwarding index: 2148532225

Interface: GE1/0

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

Backup path:

Seglist ID: 2

Seglist forwarding index: 2149580802

Weight: 1

Outgoing forwarding index: 2148532226

Interface: GE2/0

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

# Display detailed information about all SRv6 TE policies.

<Sysname> display segment-routing ipv6 te forwarding verbose

Total forwarding entries: 1

Policy name/ID: p1/0

Binding SID: 8000::1

Forwarding index: 2150629377

Inbound statistics:

Total octets: 525

Total packets: 1

Erroneous packets: 0

Dropped packets: 0

Outbound statistics:

Total octets: 750

Total packets: 1

Erroneous packets: 0

Dropped packets: 0

Main path:

Seglist ID: 1

Seglist forwarding index: 2149580801

Weight: 1

Outbound statistics:

Total octets: 750

Total packets: 1

Erroneous packets: 0

Dropped packets: 0

Outgoing forwarding index: 2148532225

Interface: GE1/0

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

Path ID: 1

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

Outbound statistics:

Total octets: 750

Total packets: 1

Erroneous packets: 0

Dropped packets: 0

Backup path:

Seglist ID: 2

Seglist forwarding index: 2149580802

Weight: 1

Outgoing forwarding index: 2148532226

Interface: GE2/0

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

Path ID: 2

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

Table 8 Command output

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

‌

display segment-routing ipv6 te ipr

Use display segment-routing ipv6 te ipr to display information about IPR policies.

Syntax

display segment-routing ipv6 te ipr [ name ipr-name ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

name ipr-name: Specifies an IPR policy by its name, a case-sensitive string of 1 to 31 characters. If you do not specify an IPR policy, this command displays information about all IPR policies.

Examples

# Display information about IPR policy ipr1.

<Sysname> display segment-routing ipv6 te ipr name ipr1

IPR policy name: ipr1

Delay threshold : 1000 Jitter threshold : 1000

Packet loss threshold : 300 CMI threshold : 5000

Bandwidth sample : Enabled Bandwidth upper : 80

Bandwidth lower : 30 Bandwidth switchback : 60

Expect bandwidth : 10000 Schedule priority :10

Switch period : 6 WTR period : 6

Color : 1 Priority : 1

Color : 2 Priority : 2

Color : 3 Priority : 1

Color : 4 Priority : 2

Instance:

Group ID : 1 Endpoint : 1::1

Selected color : 2 3 4

Group ID : 2 Endpoint : 2::2

Selected color : 2 3

Table 9 Command output

Field	Description
IPR Policy Name	Name of an IPR policy.
Delay threshold	Delay threshold in the IPR policy, in milliseconds.
Jitter threshold	Jitter threshold in the IPR policy, in milliseconds.
Packet loss threshold	Packet loss rate threshold in the IPR policy, in ‰.
CMI threshold	CMI threshold in the IPR policy,
Bandwidth sample	Enabling state of the bandwidth sampling feature.
Bandwidth upper	Upper limit of bandwidth usage for the IPR policy, in percentage.
Bandwidth lower	Lower limit of bandwidth usage, in percentage.
Bandwidth switchback	Bandwidth usage threshold that triggers service switchback for the IPR policy, in percentage.
Expect bandwidth	Expected bandwidth in kbps. If no expected bandwidth is configured, this field displays a hyphen (-).
Schedule priority	Switchover scheduling priority of the IPR policy. If no priority is configured, this field displays a hyphen (-).
Switch period	Switchover period between different SRv6 TE policies in the IPR policy, measured in seconds.
WTR period	WTR period in the IPR policy, in seconds.
Color	Color attribute value of an SRv6 TE policy in the IPR policy.
Priority	Path selection priority for the color attribute value of the SRv6 TE policy.
Instance	Instance information about the SRv6 TE policy groups to which the IPR policy is applied.
Group ID	SRv6 TE policy group to which the IPR policy is applied.
Endpoint	Endpoint address of the SRv6 TE policy group.
Selected color	Color attribute value of the optimal SRv6 TE policy obtained by computation based on the IPR policy.

‌

Related commands

ipr-policy

display segment-routing ipv6 te ipr bandwidth interface

Use display segment-routing ipv6 te ipr bandwidth interface to display bandwidth usage information about an SRv6 TE policy egress interface.

Syntax

display segment-routing ipv6 te ipr bandwidth interface [ interface-type interface-number ] [ verbose ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

interface-type interface-number: Specifies an interface by its type and number. If you do not specify this option, the command displays information about all SRv6 TE policy egress interfaces.

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

Examples

# Display brief bandwidth usage information about all SRv6 TE policy egress interfaces.

<Sysname> display segment-routing ipv6 te ipr bandwidth interface

Configured sample period(s) : 16

Actual sample period (s) : 20

Total interface number : 1

Interface : GigabitEthernet1/0/1

Maximum bandwidth(bytes/sec) : 125000000

Remaining bandwidth(bytes/sec) : 24908259

Used bandwidth(bytes/sec) : 91741

# Display detailed bandwidth usage information about all SRv6 TE policy egress interfaces.

<Sysname> display segment-routing ipv6 te ipr bandwidth interface verbose

Configured sample period(s) : 16

Actual sample period (s) : 20

Total interface number : 2

Interface : GigabitEthernet1/0/1

Maximum bandwidth(bytes/sec) : 125000000

Remaining bandwidth(bytes/sec) : 24908259

Used bandwidth(bytes/sec) : 91741

RefPolicy:

Color: 1 Endpoint: 3::3

ProtoOrigin: CLI Discriminator: 100

Instance ID: 0 Priginator: 0, ::

Segment list ID: 1

Nexthop: FE80::4463:9BFF:FE17:216

Nexthop: FE80::4463:9BFF:FE17:220

Segment list ID: 2

Nexthop: FE80::4463:9BFF:FE17:216

Color: 2 Endpoint: 3::3

ProtoOrigin: CLI Discriminator: 100

Instance ID: 0 Priginator: 0, ::

Segment list ID: 1

Nexthop: FE80::4463:9BFF:FE17:216

Interface : GigabitEthernet 1/0/2

Maximum bandwidth(bytes/sec) : 125000000

Remaining bandwidth(bytes/sec) : 2124908259

Used bandwidth(bytes/sec) : 91741

RefPolicy:

Color: 1 Endpoint: 3::3

ProtoOrigin: CLI Discriminator: 100

Instance ID: 0 Originator: 0, ::

Segment list ID: 1

Nexthop: FE80::4463:9BFF:FE17:216

Table 10 Command output

Field	Description
Configured sample period(s)	Configured bandwidth usage sampling interval.
Actual sample period (s)	Actual bandwidth usage sampling interval that takes effect.
Total interface number	Total number of SRv6 TE policy egress interfaces.
Interface	Egress interface of the SRv6 TE policy.
Maximum bandwidth(bytes/sec)	Total bandwidth of the tunnel interface or physical egress interface, in bytes/seconds.
Remaining bandwidth(bytes/sec)	Remaining bandwidth of the tunnel interface or physical egress interface, in bytes/seconds.
Used bandwidth(bytes/sec)	Used bandwidth of the tunnel interface or physical egress interface, in bytes/seconds.
RefPolicy	SRv6 TE policy that uses the interface as egress interface.
Color	Color attribute of the SRv6 TE policy.
Endpoint	Destination node IPv6 address of the SRv6 TE policy.
ProtoOrigin	SRv6 TE policy protocol: · PCEP. · BGP. · CLI—Locally configured.
Discriminator	SRv6 TE policy ID.
Instance ID	BGP instance ID. 0 indicates that no SRv6 TE policy information is obtained from the BGP peer.
Originator: ASN, Peer-address	SRv6 TE policy information obtained from BGP: · ASN—AS number. 0 indicates that no SRv6 TE policy information is obtained from BGP. · Peer-address—BGP node address. For a manually configured SRv6 TE policy, the peer address is 0.0.0.0. For SRv6 TE policy information obtained from a BGP peer, this field displays the router ID of the BGP peer.
Segment list ID	SID list ID in the optimal candidate path of the SRv6 TE policy.
Nexthop	Next hop address of the SID list.

‌

display segment-routing ipv6 te policy

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

Syntax

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

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

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

down: Specifies the SRv6 TE policies in down state.

up: Specifies the SRv6 TE policies in up state.

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

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

Usage guidelines

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

Examples

# Display information about all SRv6 TE policies.

<Sysname> display segment-routing ipv6 te policy

Name/ID: p1/0

Color: 10

Endpoint: 1000::1

Name from BGP:

BSID:

Mode: Dynamic Type: Type_2 Request state: Succeeded

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

Reference counts: 3

Flags: A/BS/NC

Status: Up

AdminStatus: Not configured

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

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

Hot backup: Not configured

Statistics: Not configured

Statistics by service class: Not configured

Path verification: Not configured

Drop-upon-invalid: Disabled

BFD trigger path-down: Disabled

SBFD: Enabled

Encapsulation mode: -

Remote: 1000

SBFD template name: abc

SBFD backup-template name: -

OAM SID: -

Reverse path type: None

BFD Echo: Not configured

Encapsulation mode: -

Source IPv6 address: 1::1

Echo BFD template name: -

Echo BFD backup template name: -

OAM SID: -

Reverse path type: Reverse BSID

Forwarding index: 2150629377

Association ID: 0

Service-class: -

Rate-limit: -

Encapsulation mode: -

Flapping suppression Remaining interval: -

Expect bandwidth(kbps): 20000

Candidate paths state: Configured

Candidate paths statistics:

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

Candidate paths:

Preference : 20

CpathName:

Instance ID: 0 ASN: 0 Node address: 0.0.0.0

Peer address: ::

Optimal: Y Flags: V/A

Explicit SID list:

ID: 1 Name: Sl1

Weight: 1 Forwarding index: 2149580801

State: Up State(SBFD): -

Verification State: -

Path MTU: 1500 Path MTU Reserved: 72

SID list flags: None

Local BSID: -

Reverse BSID: 100:1:2:3::10

Table 11 Command output

Field	Description
Name/ID	SRv6 TE policy name/ID.
Color	Color attribute of the SRv6 TE policy.
Endpoint	Endpoint IPv6 address of the SRv6 TE policy. If the endpoint is not configured, this field displays None.
Name from BGP	Name of the SRv6 TE policy obtained from BGP. If no SRv6 TE policy was obtained from BGP, this field is empty.
BSID	SID value of the ingress node.
Mode	BSID configuration mode: · Explicit—Manually configured. · Dynamic—Dynamically requested. · None—Not configured.
Type	BSID type: · None—Not configured. · Type_2—IPv6 address.
Request state	BSID request state: · Conflicted. · Failed. · Succeeded.
Explicit BSID	Manually configured BSID.
Dynamic BSID	Dynamically requested BSID.
Reference counts	Number of times that the SRv6 TE policy has been referenced.
Flags	SRv6 TE policy flags: · A—Active SRv6 TE policy. · C—Optimal SRv6 TE policy. · N—In optimal SRv6 TE policy selection progress. · BA—Requesting BSID. · BS—Optimal BSID. · D—Deleted SRv6 TE policy. · CF—Conflicted with an existing BSID. · NC—Manually configured SRv6 TE policy. · NB—SRv6 TE policy obtained from a BGP route.
Status	SRv6 TE policy state: · Up—A minimum of one SID list in the candidate paths of the SRv6 TE policy is up. · Down—No SID list in the candidate paths of the SRv6 TE policy is up.
AdminStatus	Whether the shutdown command has been configured for the SRv6 TE policy: · Configured—The policy is administratively down. · Not configured—The policy is administratively up.
Up time	Date and time when the SRv6 TE policy became up.
Down time	Date and time when the SRv6 TE policy became down.
Hot backup	Hot standby status for the SRv6 TE policy: · Enabled. · Disabled. · Not configured.
Statistics	Traffic statistics status for the SRv6 TE policy: · Disabled. · Enabled. · Not configured.
Statistics by service class	Service class based traffic statistics status for the SRv6 TE policy: · Enabled. · Not configured.
Path verification	Status of the path verification feature: · Enabled—Verifies the validity of all SIDs in the segment list. · Specified SIDs—Verifies the validity of the specified SIDs in the segment list. · Disabled. · Not configured.
Drop-upon-invalid	Drops traffic when the SRv6 TE policy becomes invalid: · Disabled. · Enabled.
BFD trigger path-down	Places the SRv6 TE policy to down state when the BFD session for the SRv6 TE policy goes down: · Disabled. · Enabled.
SBFD	SBFD status for the SRv6 TE policy: · Enabled. · Disabled. · Not configured.
Encapsulation mode	Encapsulation mode for BFD or SBFD packets: · Encaps—Normal encapsulation mode. · Insert—Insertion encapsulation mode. If the encapsulation mode for BFD or SBFD packets is not configured, this field displays a hyphen (-).
Remote	Remote discriminator of the SBFD session.
SBFD template name	Name of the SBFD template for the main path.
SBFD backup-template name	Name of the SBFD template for the backup SID list.
OAM SID	OAM SID added to SBFD packets or Echo BFD packets.
Reverse path type	Reverse path type for SBFD packets: · Reverse BSID—Uses the SID list associated with the reverse BSID as the reverse path for SBFD packets. · None—The reverse path for SBFD packets is not configured. The SBFD packets are forwarded back to the source node through IP forwarding.
BFD Echo	Echo packet mode BFD status for the SRv6 TE policy: · Enabled. · Disabled. · Not configured.
Source IPv6 address	Source IPv6 address of the echo packet mode BFD session.
Echo template name	Name of the echo BFD template.
Echo backup-template name	Name of the echo BFD template for the backup SID list.
Reverse path type	Reverse path type for BFD echo packets: · Reverse BSID—Uses the SID list associated with the reverse BSID as the reverse path for BFD packets. · None—The reverse path for BFD packets is not configured.
Forwarding index	Forwarding entry index of the SRv6 TE policy.
Association ID	Association ID for the candidate path of the SRv6 TE policy. An association ID can identify an SRv6 TE policy.
Service-class	Service class value of the SRv6 TE policy. If the default service class is used, this field displays a hyphen (-).
Rate-limit	Rate limit for the SRv6 TE policy. If no rate limit is configured, this field displays a hyphen (-).
Encapsulation mode	Encapsulation mode for the SRv6 TE policy: · Encaps. · Encaps Reduced. · Encaps include local End.X. · Insert. · Insert Reduced. · Insert include local End.X. If the encapsulation mode is not configured for the SRv6 TE policy, this field displays a hyphen (-).
Flapping suppression Remaining interval	Remaining interval for flapping suppression.
Expect bandwidth(kbps)	Expected bandwidth of the SRv6 TE policy, in kbps. If no expected bandwidth is configured, this field displays a hyphen (-).
Candidate paths state	Whether candidate paths are configured: · Configured. · Not configured.
Candidate paths statistics	Candidate paths statistics by path origin.
CLI paths	Number of manually configured candidate paths.
BGP paths	Number of candidate paths obtained from BGP SRv6 Policy routes.
PCEP paths	This field is not supported in the current software version. Number of candidate paths obtained from PCEP.
Candidate paths	SRv6 TE policy candidate path information.
Preference	SRv6 TE policy candidate path preference.
CPathName	Name of the candidate path obtained from a BGP route. If no path name was obtained, this field is empty.
Instance ID	BGP instance ID. A value of 0 indicates that the device does not obtain SRv6 TE policy information from BGP peers.
ASN	AS number. A value of 0 indicates that the device does not obtain SRv6 TE policy information from BGP peers.
Node address	BGP node address. For an SRv6 TE policy obtained from a BGP peer, the node address is the Router ID of the BGP peer. For an SRv6 TE policy obtained in other methods, the node address is 0.0.0.0.
Peer address	BGP peer address. For a manually configured SRv6 TE policy, the peer address is ::. For an SRv6 TE policy obtained from a BGP peer, the peer address is the address of the BGP peer.
Optimal	Whether the path is the optimal path: · Y—Yes. · N—No.
Flags	Flags of the SRv6 TE policy candidate path: · V—Valid candidate path. · A—Active candidate path. · None—No candidate path.
Explicit SID list	Explicit SID list in the candidate path of the SRv6 TE policy.
ID	SID list ID.
Name	SID list name.
Weight	Weight of the SID list in the candidate path.
Forwarding index	Forwarding entry index of the SID list.
State	SID list state: · UP—The first hop on the forwarding path of the SID list is available. · DOWN—The first hop on the forwarding path of the SID list 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. If SBFD or echo BFD is not configured, this field displays a hyphen (-).
Verification state	Verification result of the SID list: · Down—The verification fails. · Up—The verification succeeds. If verification is not configured, this field displays a hyphen (-).
Path MTU	Path MTU.
Path MTU Reserved	Reserved path MTU.
SID list flags	SID list flags of the SRv6 TE policy: · O—The number of SIDs in the SID list exceeds the maximum depth for the SID label stack on the device. · None—Stateless.
Local BSID	This value is specified by using the explicit segment-list command with the local-binding-sid parameter. If this value is not specified, this field displays a hyphen (-).
Reverse BSID	This value is specified by using the explicit segment-list command with the reverse-binding-sid parameter. If this value is not specified, this field displays a hyphen (-).

‌

display segment-routing ipv6 te policy ifit

Use display segment-routing ipv6 te policy ifit to display iFIT measurement information for SRv6 TE policies.

Syntax

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

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

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

down: Specifies SRv6 TE policies in down state.

up: Specifies SRv6 TE policies in up state.

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

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

Usage guidelines

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

Examples

# Display iFIT measurement information for all SRv6 TE policies.

<Sysname> display segment-routing ipv6 te policy ifit

SRv6 TE policy name/ID: p1/0

Color: 10

End-point : 1000::1

Status : Up AdminStatus : Up

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

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

IFIT loss measure : Enabled IFIT delay measure : Enabled

IFIT interval(s) : 10 IFIT measure mode : e2e

Measurement values :

One-Way Delay(ms) : 10

One-Way Jitter(ms) : 100

One-Way Loss(per-thousand) : 123

Candidate paths state: Configured

Candidate paths statistics:

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

Candidate paths:

Preference : 20

CpathName :

ProtoOrigin : CLI Discriminator : 30

Instance ID : 0 Node address : 0.0.0.0

Originator : 0, ::

Explicit SID list:

ID: 1 Name: Sl1

Weight: 1 Forwarding index: 2149580801

Global segment list ID: 1

State: Up State(-): -

Latest measurement values:

One-Way Delay(ms) : 10

One-Way Jitter(ms) : 100

One-Way Loss(per-thousand) : 122

Table 12 Command output

Field	Description
Name/ID	Name and ID of an SRv6 TE policy.
Color	Color attribute value of the SRv6 TE policy.
Endpoint	Endpoint IPv6 address of the SRv6 TE policy. If no endpoint IPv6 address is configured, this field displays none.
Status	State of the SRv6 TE policy: · Up—Active state. · Down—Inactive state. The SRv6 TE policy went down because of reasons other than BFD or SBFD session collaboration. · Down (BFD down)—A BFD or SBFD session detected that the forwarding paths of all SID lists in the candidate paths of the SRv6 TE policy are not reachable. In this state, the first next hop in the forwarding path of each SID list is reachable, but the subsequent nodes are not reachable.
AdminStatus	Administrative state of the SRv6 TE policy: · Down—The SRv6 TE policy is shut down by using the shutdown command. · Up—The SRv6 TE policy is not shut down by using the shutdown command.
Up time	Date and time when the SRv6 TE policy came up.
Down time	Date and time when the SRv6 TE policy went down.
IFIT loss measure	State of iFIT packet loss measurement in the SRv6 TE policy: · Enabled. · Disabled.
IFIT delay measure	State of iFIT delay measurement in the SRv6 TE policy: · Enabled. · Disabled.
IFIT interval(s)	iFIT measurement interval, in seconds.
IFIT measure mode	iFIT measurement mode: · e2e. · trace.
Measurement values	iFIT measurement values.
One-Way Delay(ms)	One-way iFIT delay weight value of all SID lists in the optimal candidate path of the SRv6 TE policy, measured in milliseconds.
One-Way Jitter(ms)	One-way iFIT jitter weight value of all SID lists in the optimal candidate path of the SRv6 TE policy, measured in milliseconds.
One-Way Loss(per-thousand)	Weight value of the one-way iFIT packet loss rate of all SID lists in the optimal candidate path of the SRv6 TE policy, measured in per mille (‰).
Candidate paths state	Configuration state of candidate paths: · Configured. · Not configured.
Candidate paths statistics	Source statistics for candidate paths in the SRv6 TE policy.
CLI paths	Number of manually configured candidate paths.
BGP paths	Number of candidate paths obtained from BGP SRv6 policy routes.
PCEP paths	This field is not supported in the current software version. Number of candidate paths obtained by PCEP.
ODN paths	Number of candidate paths created by ODN.
Candidate paths	Candidate path information of the SRv6 TE policy.
Preference	Preference of a candidate path.
CPathName	Name of the candidate path obtained from a BGP route. If the name is not obtained, this field is empty.
ProtoOrigin	Protocol obtained the SRv6 TE policy information: · PCEP—Obtained by PCEP. This value is not supported in the current software version. · BGP—Obtained by BGP. · CLI—Local configured. · Unknown—Source unknown.
Discriminator	Discriminator of the SRv6 TE policy.
Instance ID	BGP instance ID. This field displays 0 if SRv6 TE policy information is not obtained from a BGP peer.
Node address	BGP node address. If SRv6 TE policy information is obtained from a BGP peer, the node address is the router ID of the BGP peer. If SRv6 TE policy information is not obtained from a BGP peer, the node address is 0.0.0.0.
Originator: ASN, Peer-address	Originator information: · ASN—AS number. The value of 0 indicates that the SRv6 TE policy information is not obtained from BGP. · Peer-address—BGP node address. If the SRv6 TE policy is manually configured, the peer address is ::. If the SRv6 TE policy information is obtained from a BGP peer, the peer address is the router ID of the BGP peer.
Explicit SID list	Explicit SID list in the candidate path of the SRv6 TE policy.
ID	SID list ID. When creating an SID list, the system automatically assigns an ID to it. Different SRv6 TE policies referencing the same SID list will maintain the same ID for the SID list.
Name	SID list name.
Weight	Weight value of the SID list in the candidate path.
Global segment list ID	Global unique ID of the SID list. When the SID list is applied to the SRv6 TE policy, the system automatically assigns a global unique ID to the SID list. Each iFIT flow corresponds to one global SID list ID.
Forwarding index	Forwarding 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 reachable. However, BFD detected that the subsequent nodes on the forwarding path are not reachable.
State(type)	State of the SBFD or echo BFD session in the SID list: · Up. · Down. · Path Inactive—The SID list is not available in the candidate path. · Unknown—No results from SBFD or echo BFD detection. If SBFD or echo BFD is not configured, this field displays a hyphen (-) for the state. The type variable represents the BFD session type. Supported values: · SBFD. · Echo BFD. · If SBFD or echo BFD is not configured, this field displays a hyphen (-) for the type.
Latest measurement values	The most recent five iFIT measurement results of the SID list. If the number of iFIT measurements is less than 5, this field displays all iFIT measurement results. If iFIT cannot correctly measure data, this field is not displayed.
One-Way Delay(ms)	The most recent five one-way iFIT delay values of the SID list, measured in milliseconds.
One-Way Jitter(ms)	The most recent five one-way iFIT jitter values of the SID list, measured in milliseconds.
One-Way Loss(per-thousand)	The most recent five one-way iFIT packet loss rate values of the SID list, measured in per mille (‰).

‌

Related commands

ifit delay-measure

ifit interval

ifit loss-measure

srv6-policy ifit delay-measure enable

srv6-policy ifit interval

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

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

Syntax

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

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

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

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

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

Usage guidelines

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

Examples

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

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

Name/ID: p1/1

Color: 10

Endpoint: 4::4

BSID: 5000::2

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

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

Down reason: Candidate path invalid segment list

Candidate paths:

Preference : 10

CPathName:

Explicit SID list:

ID: 1 Name: s1

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

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

Down reason: No SRv6 SID Out

Table 13 Command output

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

‌

display segment-routing ipv6 te policy statistics

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

Syntax

display segment-routing ipv6 te policy statistics

Views

Any view

Predefined user roles

network-admin

network-operator

Examples

# Display SRv6 TE policy statistics.

<Sysname> display segment-routing ipv6 te policy statistics

IPv6 TE Policy Database Statistics

Total policies: 1 (1 up 0 down)

Configured: 1 (1 up 0 down)

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

Total candidate paths: 1

Configured: 1

From BGP: 0 (Added 0 deleted 0)

Total SID lists: 1 (1 up 0 down)

Configured: 1 (1 up 0 down)

From BGP: 0 (0 up 0 down)

Table 14 Command output

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

‌

display segment-routing ipv6 te policy status

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

Syntax

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

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

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

Usage guidelines

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

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

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

Examples

# Display status information about all SRv6 TE policies.

<Sysname> display segment-routing ipv6 te policy status

Name/ID: p1/0

Status: Up

Check admin status : Passed

Check for endpoint & color : Passed

Check for segment list : Passed

Check valid candidate paths : Passed

Check for BSIDs : Passed

Table 15 Command output

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

‌

display segment-routing ipv6 te policy-group

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

Syntax

display segment-routing ipv6 te policy-group [ odn ] [ group-id | { color color-value | end-point ipv6 ipv6-address } * ] [ verbose ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

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

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

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

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

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

Examples

# Display brief information about all SRv6 TE policy groups.

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

Total number of policy groups: 1

GroupID GroupState UPMappings TotalMappings

10 Up 26 26

# Display detailed information about all SRv6 TE policy groups.

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

Total number of policy groups: 2

GroupID: 10 GroupState: Down

GroupNID: 0 Referenced: 1

Flags: None Group type: Static TE Class

Group color: -

StateChangeTime: 2024-05-27 10:30:14

Endpoint: None

BSID:

Explicit BSID: - Request state: -

Drop upon mismatch: Enabled

UP/Total Mappings: 0/3

Default Match Type: None

Default SRv6 TE Policy Color: -

Default IPR Policy : -

Index: 10 TE Class: 10

Match Type : IPR Policy

SRv6 TE Policy Color: -

IPR Policy : ipr1

Index: 20 TE Class: 20

Match Type : SRv6 TE Policy

SRv6 TE Policy Color: 20

IPR Policy : -

Index: 30 TE Class: 30

Match Type : SRv6 BE

SRv6 TE Policy Color: -

IPR Policy : -

GroupID: 20 GroupState: Up

GroupNID: 2151677953 Referenced: 1

Flags: A Group type: Static DSCP

Group color: -

StateChangeTime: 2024-05-27 10:30:14

Endpoint: 4::4

BSID:

Explicit BSID: - Request state: -

Best-effort NID: 0

Drop upon mismatch: Disabled

UP/Total Mappings: 0/0

IPv4 Best-effort: Not configured IPv6 Best-effort: Not configured

Table 16 Command output

Field	Description
UPMappings	Number of mappings in up (valid) state in the SRv6 TE policy group.
TotalMappings	Total number of mappings in the SRv6 TE policy group.
GroupNID	Index of the forwarding entry for the SRv6 TE policy group.
Referenced	Number of times that the SRv6 TE policy group has been used.
Flags	Flags of the SRv6 TE policy group: · A—Assign the forwarding entry index of the SRv6 TE policy group. · F—Issue the forwarding entry of the SRv6 TE policy group. · W—Waiting for assigning the forwarding entry index of the SRv6 TE policy group. · D—Delete the SRv6 TE policy group. · None—The SRv6 TE policy group is in initialized or stable state.
Group type	SRv6 TE policy group type: · Static DSCP—Statically created SRv6 TE policy group that uses DSCP-based traffic steering. · Static TE Class —Statically created SRv6 TE policy group that uses TE class ID-based traffic steering. · Dynamic—Dynamically created SRv6 TE policy group. No forward type is configured. · Dynamic DSCP—Dynamically created SRv6 TE policy group that uses DSCP-based traffic steering. · Dynamic TE Class—Dynamically created SRv6 TE policy group that use TE class ID-based traffic steering.
Group color	Color value of the SRv6 TE policy group.
StateChangeTime	Time when the SRv6 TE policy group state changed.
Endpoint	Destination node IP address of the SRv6 TE policy group. None indicates that the endpoint is not configured.
BSID	BSID information of the SRv6 TE policy group: · Explicit BSID—BSID allocated by the system. · Request state—Request state of the BSID. Supported values: ¡ Succeeded. ¡ Failed.
Best-effort NID	NID for best effort forwarding.
Drop upon mismatch	Whether the feature of discarding packets that do not match any valid SRv6 TE policy or SRv6 BE path is enabled: · Disabled. · Enabled.
UP/Total Mappings	· If DSCP-based traffic steering is used, this field represents the number of valid color-to-DSCP mappings and the total number of configured color-to-DSCP mappings in the SRv6 TE policy group. · If TE class ID-based traffic steering is used, this field represents the number of valid TE class ID-to-forwarding policy mappings and the total number of configured TE class ID-to-forwarding policy mappings in the SRv6 TE policy group.
Color	Color value
Type	Packet type: IPv4 or IPv6.
DSCP	DSCP value.
Default MatchType	Default forwarding policy for TE class ID-based traffic steering: · IPR Policy. · SRv6 TE Policy. · SRv6 BE.
Default SRv6 TE Policy Color	If the default forwarding policy is SRv6 TE policy forwarding, this field represents the color attribute value of an SRv6 TE policy. If the default forwarding policy is not SRv6 TE policy forwarding, this field displays a hyphen (-).
Default IPR Policy	If the default forwarding policy is IPR policy forwarding, this field represents the name of an IPR policy. If the default forwarding policy is not IPR policy forwarding, this field displays a hyphen (-).
Color	Color attribute value of the optimal SRv6 TE policy in the IPR policy. This field is not displayed if no TE class ID is mapped to the IPR policy.
Priority	Priority of the optimal SRv6 TE policy in the IPR policy. This field is not displayed if no TE class ID is mapped to the IPR policy.
Index	Index of a mapping between a TE class ID and a forwarding policy.
TE Class	TE class ID.
Match Type	Mapping between the TE class ID and an SRv6 TE policy, an IPR policy, or the SRv6 BE mode. Supported values: · IPR Policy—Traffic identified by the TE class ID is forwarded through the forwarding method defined in an IPR policy. If the forwarding method takes effect, this field displays active in a pair of brackets. If the forwarding method does not take effect, this field does not display active. · SRv6 TE Policy—Traffic identified by the TE class ID is forwarded through an SRv6 TE policy. · SRv6 BE—Traffic identified by the TE class ID is forwarded in SRv6 BE mode.
SRv6 TE Policy Color	Color attribute value of the SRv6 TE policy mapped to the TE class ID.
IPR Policy	Name of the IPR policy mapped to the TE class ID.

‌

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

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

Syntax

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

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

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

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

Examples

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

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

Group ID : 10 Group type : Static DSCP

Group color: 100 Endpoint : 4::4

Group NID : 2151677956

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

Up time : -

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

Down reason: No active SRv6-TE Policies

Color: 20 Address family: IPv4

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

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

Down reason: No endpoint

Table 17 Command output

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

‌

display segment-routing ipv6 te policy-group statistics

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

Syntax

display segment-routing ipv6 te policy-group statistics

Views

Any view

Predefined user roles

network-admin

network-operator

Examples

# Display SRv6 TE policy group statistics.

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

Statistics type Total Up

Dynamic DSCP groups 0 0

Static DSCP groups 1 0

Color-DSCP mappings 0 0

SRv6-BE-DSCP mappings 0 0

Static Dot1p groups 0 0

Color-Dot1p mappings 0 0

Dynamic service-class groups 0 0

Static service-class groups 0 0

Color-service-class mappings 0 0

SRv6-BE-service-class mappings 0 0

Dynamic apn-id groups 0 0

Static apn-id groups 0 0

Color-apn-id mappings 0 0

SRv6-BE-apn-id mappings 0 0

Dynamic TE Class groups 0 0

Static TE Class groups 0 0

Color-TE Class mappings 0 0

IPR-TE Class mappings 0 0

SRv6-BE-TE Class mappings 0 0

Table 18 Command output

Field	Description
Statistics type	Statistics objects: · Dynamic DSCP groups—Dynamically created SRv6 TE policy groups that use DSCP-based traffic steering. · Static DSCP groups—Statically created SRv6 TE policy groups that use DSCP-based traffic steering. · Color-DSCP mappings—Color-to-DSCP mappings in all SRv6 TE policy groups. · SRv6-BE-DSCP mappings—SRv6 BE-to-DSCP mappings in all SRv6 TE policy groups. · Static Dot1p groups—Statically created SRv6 TE policy groups that use 802.1p-based traffic steering. · Color-Dot1p mappings—Color-to-802.1p mappings in all SRv6 TE policy groups. · Dynamic service-class groups—Dynamically created SRv6 TE policy groups that use service class-based traffic steering. · Static service-class groups—Statically created SRv6 TE policy groups that use service class-based traffic steering. · Color-service-class mappings—Color-to-service class mappings in all SRv6 TE policy groups. · SRv6-BE-service-class mappings—SRv6 BE-to-service class mappings in all SRv6 TE policy groups. · Dynamic APN ID groups—Dynamically created SRv6 TE policy groups that use APN ID-based traffic steering. · Static APN ID groups—Statically created SRv6 TE policy groups that use APN ID-based traffic steering. · Color-APN ID mappings—Color-to-APN ID mappings in all SRv6 TE policy groups. · SRv6-BE-APN ID mappings—SRv6 BE-to-APN ID mappings in all SRv6 TE policy groups. · Dynamic TE Class groups—Dynamically created SRv6 TE policy groups that use TE class ID-based traffic steering. · Static TE Class groups—Statically created SRv6 TE policy groups that use TE class ID-based traffic steering. · Color-TE Class mappings—Color-to-TE class ID mappings in all SRv6 TE policy groups. · IPR-TE Class mappings—All IPR policy-to-TE class ID mappings. · SRv6-BE-TE Class mappings —SRv6 BE-to-TE class ID mappings in all SRv6 TE policy groups.
Total	Total number of statistics objects.
UP	Number of effective statistics objects.

‌

display segment-routing ipv6 te sbfd

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

Syntax

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

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

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

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

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

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

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

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

Usage guidelines

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

Examples

# Display SBFD information for all SRv6 TE policies.

<Sysname> display segment-routing ipv6 te policy sbfd

Color: 10

Endpoint: 4::4

Policy name: p1

State: Down

Nid: 2149580801

BFD type: SBFD

Remote Discr: 100

State: Down

Timer: 30

VPN index: 0

Template name: abc

Table 19 Command output

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

‌

display segment-routing ipv6 te segment-list

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

Syntax

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

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

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

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

Usage guidelines

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

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

Examples

# Display information about all SRv6-TE SID lists.

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

Total Segment lists: 2

Name/ID: A/1

Origin: CLI

Status: Up

Nodes: 1

Index : 10 SID: 101::1

Type : Type_2 Flags: None

Coc Type : - Common prefix length: 0

Function length : 0 Args length: 0

Endpoint Behavior: -

Index : 2 SID: 101::2

Type : Type_13 Flags: None

Coc Type : COC32 Common prefix length: 72

Function length : 64 Args length: 0

Endpoint Behavior: End with COC

Table 20 Command output

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

‌

distribute bgp-ls

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

Use undo distribute bgp-ls to restore the default.

Syntax

distribute bgp-ls

undo distribute bgp-ls

Default

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

Views

SRv6 TE view

Predefined user roles

network-admin

Usage guidelines

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

Examples

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

<Sysname> system-view

[Sysname] segment-routing-ipv6

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

[Sysname-srv6-te] distribute bgp-ls

drop-upon-invalid enable

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

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

Syntax

drop-upon-invalid enable

undo drop-upon-invalid enable

Default

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

Views

SRv6 TE policy view

Predefined user roles

network-admin

Usage guidelines

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

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

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

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

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

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

Examples

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

<Sysname> system-view

[Sysname] segment-routing ipv6

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

[Sysname-srv6-te] policy a1

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

drop-upon-mismatch enable

Use drop-upon-mismatch enable to enable the feature of discarding packets that do not match any valid SRv6 TE policy or SRv6 BE path.

Use undo drop-upon-mismatch enable to disable the feature of discarding packets that do not match any valid SRv6 TE policy or SRv6 BE path.

Syntax

drop-upon-mismatch enable

undo drop-upon-mismatch enable

Default

The device disables the feature of discarding packets that do not match any valid SRv6 TE policy or SRv6 BE path.

Views

SRv6 TE ODN policy group view

SRv6 TE policy group view

Predefined user roles

network-admin

Usage guidelines

Use this command if you want to forward traffic only through SRv6 TE policies based on color-to-DSCP, color-to-802.1p, and color-to-service class mappings, through the default SRv6 TE policy, or in SRv6 BE mode.

Examples

# In SRv6 TE policy group 10, enable the feature of discarding packets that do not match any valid SRv6 TE policy or SRv6 BE path.

<Sysname> system-view

[Sysname] segment-routing ipv6

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

[Sysname-srv6-te] policy-group 10

[Sysname-srv6-te-policy-group-10] drop-upon-mismatch enable

# In SRv6 TE ODN policy group view, enable the feature of discarding packets that do not match any valid SRv6 TE policy or SRv6 BE path.

<Sysname> system-view

[Sysname] segment-routing ipv6

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

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

[Sysname-srv6-te-odn-group-1] drop-upon-mismatch enable

Related commands

color match dscp (SRv6 TE policy group view)

forward-type (SRv6 TE ODN policy group view)

forward-type (SRv6 TE policy group view)

encapsulation-mode

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

Use undo encapsulation-mode to restore the default.

Syntax

encapsulation-mode encaps reduced [ disable ]

undo encapsulation-mode encaps reduced

encapsulation-mode insert

undo encapsulation-mode insert

encapsulation-mode insert reduced [ disable ]

undo encapsulation-mode insert reduced

Default

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

Views

SRv6 TE policy view

Predefined user roles

network-admin

Parameters

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

insert: Specifies the encapsulation mode as insertion mode.

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

disable: Disables the specified encapsulation mode.

Usage guidelines

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

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

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

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

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

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

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

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

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

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

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

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

Examples

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

<Sysname> system-view

[Sysname] segment-routing ipv6

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

[Sysname-srv6-te] policy 1

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

Related commands

encapsulation source-address

srv6-policy encapsulation-mode

encapsulation-mode encaps include local-end.x

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

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

Syntax

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

undo encapsulation-mode encaps include local-end.x

Default

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

Views

SRv6 TE policy view

Predefined user roles

network-admin

Parameters

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

Usage guidelines

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

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

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

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

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

Examples

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

<Sysname> system-view

[Sysname] segment-routing ipv6

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

[Sysname-srv6-te] policy 1

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

Related commands

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

encapsulation-mode insert include local-end.x

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

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

Syntax

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

undo encapsulation-mode insert include local-end.x

Default

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

Views

SRv6 TE policy view

Predefined user roles

network-admin

Parameters

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

Usage guidelines

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

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

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

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

Examples

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

<Sysname> system-view

[Sysname] segment-routing ipv6

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

[Sysname-srv6-te] policy 1

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

Related commands

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

end-point

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

Use undo end-point to restore the default.

Syntax

end-point ipv6 ipv6-address

undo end-point ipv6

Default

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

Views

SRv6 TE policy group view

Predefined user roles

network-admin

Parameters

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

Usage guidelines

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

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

Examples

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

<Sysname> system-view

[Sysname] segment-routing ipv6

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

[Sysname-srv6-te] policy-group 10

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

expect-bandwidth

Use expect-bandwidth to configure the expected service bandwidth for an SRv6 TE policy or SRv6 TE IPR policy.

Use undo expect-bandwidth to restore the default.

Syntax

expect-bandwidth bandwidth-value

undo expect-bandwidth

Default

The expected service bandwidth is 0 kbps for an SRv6 TE policy or SRv6 TE IPR policy.

Views

SRv6 TE policy view

SRv6 TE IPR policy view

Predefined user roles

network-admin

Parameters

bandwidth-value: Specifies the expected service bandwidth in the range of 1 to 400000000 kbps.

Usage guidelines

Application scenarios

When IPR for SRv6 TE policy selects the optimal path based on bandwidth usage, you can configure the expected service bandwidth as the initial trigger value for selecting the appropriate SRv6 TE policy, preventing congestion and packet loss caused by excessive bandwidth usage on the egress interface of the selected SRv6 TE policy. When no traffic statistics are collected for the SRv6 TE policy, the expected service bandwidth is used to calculate the expected average bandwidth usage of the SRv6 TE policy.

The expected bandwidth configured by the expect-bandwidth command indicates the estimated bandwidth value for the service based on experience, rather than the actual bandwidth used by the service.

Operating mechanism

When IPR for SRv6 TE policy selects the optimal path based on bandwidth usage, it calculates the expected average bandwidth usage of the SRv6 TE policies. The expected average bandwidth usage of the SRv6 TE policy = (expected service bandwidth + current bandwidth used by the egress interface) / total bandwidth of the egress interface. The expected service bandwidth is determined as follows:

· Use the real-time statistics of the SRv6 TE policy currently carrying the service as the expected service bandwidth.

· If the SRv6 TE policy is not carrying the specified service or no traffic statistics exists for the SRv6 TE policy, the SRv6 TE policy service expected bandwidth configured in the expect-bandwidth command in SRv6 TE policy view is used.

· If no service expected bandwidth is configured in SRv6 TE policy view, the SRv6 TE IPR policy service expected bandwidth specified in the expect-bandwidth command in SRv6 TE IPR policy view is used.

Recommended configuration

When you configure this feature, estimate the bandwidth required for the services to be carried by the SRv6 TE policy or SRv6 TE IPR policy according to the actual situation and experience. For example, the expected bandwidth for a video conferencing service can be estimated as 200 Mbps, and the video conferencing service is forwarded through the IPR policy. The IPR policy contains a high-priority SRv6 TE policy A and a low-priority SRv6 TE policy B, whose egress interfaces are Gigabit Interface A and Gigabit Interface B, respectively. Interface A and Interface B are already using 800 Mbps and 300 Mbps of bandwidth. If the expect-bandwidth command is not configured, the expected bandwidth is 0 kbps, and the upper threshold for bandwidth usage in the IPR policy is 90%. Both SRv6 TE policy A and SRv6 TE policy B meet the bandwidth usage requirement. Therefore, IPR will preferentially select the high-priority SRv6 TE policy A as the preferred path to forward the video conferencing traffic. However, in reality, the combined bandwidth of the video conferencing traffic and Interface A not only exceeds the upper bandwidth usage threshold of the IPR policy, but also reaches the maximum bandwidth of the interface. Therefore, you must configure the expected service bandwidth to avoid such issues.

Restrictions and guidelines

Execute the forwarding statistics command or the srv6-policy forwarding statistics enable command to enable traffic forwarding statistics for all SRv6 TE policies associated with the IPR policy. This ensures that path optimization based on bandwidth usage by IPR for SRv6 TE policy is more accurate.

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

Examples

# Configure the expected service bandwidth for SRv6 TE policy 1 as 30000 kbps.

<Sysname> system-view

[Sysname] segment-routing ipv6

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

[Sysname-srv6-te] policy 1

[Sysname-srv6-te-policy-1] expect-bandwidth 30000

# Configure the expected service bandwidth for SRv6 TE IPR policy ipr1 as 30000 kbps.

<Sysname> system-view

[Sysname] segment-routing ipv6

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

[Sysname-srv6-te] intelligent-policy-route

[Sysname-srv6-ipr] ipr-policy ipr1

[Sysname-srv6-ipr-policy-ipr1] expect-bandwidth 30000

Related commands

bandwidth sample

expect-bandwidth

srv6-policy bandwidth sample

explicit segment-list

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

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

Syntax

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

undo explicit segment-list segment-list-name [ local-binding-sid | local-xsid | reverse-binding-sid | weight ]

Default

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

Views

SRv6 TE policy path preference view

Predefined user roles

network-admin

Parameters

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

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

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

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

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

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

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

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

Usage guidelines

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

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

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

Examples

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

<Sysname> system-view

[Sysname] segment-routing ipv6

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

[Sysname-srv6-te] policy a1

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

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

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

Related commands

segment-list

fast-reroute mirror delete-delay

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

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

Syntax

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

undo fast-reroute mirror delete-delay

Default

The mirror FRR deletion delay time is 60 seconds.

Views

IS-IS IPv6 unicast address family view

OSPFv3 view

Predefined user roles

network-admin

Parameters

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

Usage guidelines

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

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

Examples

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

<Sysname> system-view

[Sysname] isis 1

[Sysname-isis-1] address-family ipv6

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

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

<Sysname> system-view

[Sysname] ospfv3 1

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

Related commands

fast-reroute mirror enable

Use fast-reroute mirror enable to enable egress protection.

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

Syntax

fast-reroute mirror enable

undo fast-reroute mirror enable

Default

Egress protection is disabled.

Views

IS-IS IPv6 unicast address family view

OSPFv3 view

Predefined user roles

network-admin

Usage guidelines

Operating mechanism

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

Restrictions and guidelines

To enable egress protection in a view on a transit node, you must also enable TI-LFA FRR in that view for the transit node to compute a backup path.

Examples

# Enable IS-IS egress protection.

<Sysname> system-view

[Sysname] isis 1

[Sysname-isis-1] address-family ipv6

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

# Enable OSPFv3 egress protection.

<Sysname> system-view

[Sysname] ospfv3 1

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

forwarding statistics

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

Use undo forwarding statistics to restore the default.

Syntax

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

undo forwarding statistics

Default

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

Views

SRv6 TE policy view

Predefined user roles

network-admin

Parameters

disable: Disables the SRv6 TE policy forwarding statistics.

enable: Enables the SRv6 TE policy forwarding statistics.

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

Usage guidelines

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

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

Examples

# Enable traffic forwarding statistics for SRv6 TE policy 1.

<Sysname> system-view

[Sysname] segment-routing ipv6

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

[Sysname-srv6-te] policy 1

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

Related commands

display segment-routing ipv6 te forwarding

reset segment-routing ipv6 te forwarding statistics

srv6-policy forwarding statistic enable

srv6-policy forwarding statistic interval

forward-type (SRv6 TE ODN policy group view)

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

Use undo forward-type to restore the default.

Syntax

forward-type { dscp | te-class }

undo forward-type { dscp | te-class }

Default

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

Views

SRv6 TE ODN policy group view

Predefined user roles

network-admin

Parameters

dscp: Specifies the DSCP forward type, that is, DSCP-based traffic steering.

te-class: Specifies the TE class forward type, that is, TE class ID-based traffic steering.

Usage guidelines

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

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

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

2. If the DSCP value matches a color-to-DSCP mapping and the SRv6 TE policy assigned the color attribute value in the mapping is valid, the device uses that SRv6 TE policy to forward the packet.

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

1. Matches the TE class ID in packets with the TE class ID and forwarding policy mappings configured in the SRv6 TE policy group.

2. Forwards the packets based on the matching result.

¡ If the TE class ID is mapped to a color attribute value, the device steers the packets to the SRv6 TE policy with that color attribute value for forwarding.

¡ If the TE class ID is mapped to an IPR policy, the device steers the packets to the optimal SRv6 TE policy for forwarding according to the path selection policy defined in that IPR policy.

¡ If the TE class ID is mapped to SRv6 BE mode, the device forwards the packets in SRv6 BE mode. In this mode, the device encapsulates a new IPv6 header to the packets and looks up the IPv6 routing table to forward the packets.

3. If the TE class ID of the packets is not mapped to any forwarding policy, the device forwards the packets according to the default forwarding policy configured by using the default match command.

On the source node of the SRv6 TE policy group, you can perform the following tasks:

· Use the remark te-class command in a QoS policy to mark the TE class ID value for traffic that matches rules in the QoS policy.

Examples

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

<Sysname> system-view

[Sysname] segment-routing ipv6

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

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

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

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

# Specify the TE class forward type and enter TE class forward type view.

<Sysname> system-view

[Sysname] segment-routing ipv6

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

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

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

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

Related commands

color match dscp (DSCP forward type view)

default match (TE class ID-based traffic steering)

remark te-class (ACL and QoS Command Reference)

forward-type (SRv6 TE Policy group view)

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

Use undo forward-type to restore the default.

Syntax

forward-typete-class

undo forward-typete-class

Default

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

Views

SRv6 TE policy group view

Predefined user roles

network-admin

Parameters

te-class: Sets the forward type to TE class, which represents TE class ID-based traffic steering.

Usage guidelines

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

On the source node of the SRv6 TE policy group, you can perform the following tasks:

· Use the remark te-class command in a QoS policy to mark the TE class ID value for traffic that matches rules in the QoS policy. The TE class ID only holds local significance.

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

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

2. If the DSCP value matches a color-to-DSCP mapping and the SRv6 TE policy assigned the color attribute value in the mapping is valid, the device uses that SRv6 TE policy to forward the packet.

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

1. Matches the TE class ID in packets with the TE class ID and forwarding policy mappings configured in the SRv6 TE policy group.

2. Forwards the packets based on the matching result.

¡ If the TE class ID is mapped to a color attribute value, the device steers the packets to the SRv6 TE policy with that color attribute value for forwarding.

¡ If the TE class ID is mapped to an IPR policy, the device steers the packets to the optimal SRv6 TE policy for forwarding according to the path selection policy defined in that IPR policy.

3. If the TE class ID of the packets is not mapped to any forwarding policy, the device forwards the packets according to the default forwarding policy configured by using the default match command.

Examples

# Specify TE class ID-based traffic steering for SRv6 TE policy group 1.

<Sysname> system-view

[Sysname] segment-routing ipv6

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

[Sysname-srv6-te] policy-group 1

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

Related commands

color match dscp (SRv6 TE policy group view)

default match (TE class ID-based traffic steering)

remark te-class (ACL and QoS Command Reference)

group-color

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

Use undo group-color to restore the default.

Syntax

group-color color-value

undo group-color

Default

The color value is not configured for an SRv6 TE policy group.

Views

SRv6 TE policy group view

Predefined user roles

network-admin

Parameters

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

Usage guidelines

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

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

Examples

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

<Sysname> system-view

[Sysname] segment-routing ipv6

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

[Sysname-srv6-te] policy-group 1

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

ifit delay-measure

Use ifit delay-measure to configure iFIT delay and jitter measurement in an SRv6 TE policy.

Use undo ifit delay-measure to restore the default.

Syntax

ifit delay-measure { disable | enable }

undo ifit delay-measure

Default

iFIT delay and jitter measurement is not configured for an SRv6 TE policy. The SRv6 TE policy uses the configuration in SRv6 TE view.

Views

SRv6 TE policy view

Predefined user roles

network-admin

Parameters

disable: Disables iFIT delay and jitter measurement.

enable: Enable iFIT delay and jitter measurement.

Usage guidelines

Prerequisites

For this command to take effect on an SRv6 TE policy, you must complete the following tasks:

· On the source node of the SRv6 TE policy, enable iFIT, configure the iFIT device ID, set the iFIT operating mode to analyzer, and execute the service-type srv6-segment-list command.

· On the egress node or transit nodes of the SRv6 TE policy, enable iFIT, set the iFIT operating mode to collector, and execute the service-type srv6-segment-list command.

Application scenarios

In-situ Flow Information Telemetry (iFIT) is a type of in-situ flow OAM measurement technology. This technology measures the actual packet loss, delay, and jitter of services in the network by directly encapsulating the measurement interval, packet loss indicator, and delay indicator information in the iFIT option field of service packets. For more information about iFIT, see Network Management and Monitoring Configuration Guide.

When service packets are steered to an SRv6 TE policy group for forwarding and the SRv6 TE policy group uses TE class ID-based traffic forwarding, the device can select an SRv6 TE policy to forward the service packets with a specific TE class ID according to the path selection policy defined in an IPR policy.

When the iFIT delay and jitter measurement feature is enabled for the SRv6 TE policy, the device performs the following operations:

1. Measures the delay and jitter of the SRv6 TE policy through iFIT.

2. Compares the measured delay and jitter values with the delay and jitter thresholds defined in the IPR policy. The measured delay and jitter values of the SRv6 TE policy are used as conditions for optimal SRv6 TE policy selection. If the measured values cross the delay and jitter thresholds, it cannot be used as a traffic forwarding path.

Operating mechanism

After iFIT delay and jitter measurement is enabled on the source node of an SRv6 TE policy, the source node and egress node of the SRv6 TE policy will measure the end-to-end delay and jitter for packets forwarded through the SRv6 TE policy. The measurement procedure is as follows:

1. The source node automatically creates an iFIT instance and assigns a flow ID to the iFIT instance.

2. As the data sender, the source node encapsulates the original packets with the DOH header that carries the iFIT option field and the SRH header when it forwards the packets through the SRv6 TE policy. In addition, the source node records the timestamps when the packets are forwarded through the SRv6 TE policy within an iFIT measurement interval.

3. As the data receiver, the egress node decodes the iFIT option field of the packets to obtain the iFIT measurement interval of the SRv6 TE policy, and records the timestamps when the packets are received through the SRv6 TE policy within the iFIT measurement interval.

4. The egress node uses the source address of the received packets to establish a UDP session with the source node and returns the packet timestamps recorded within the iFIT measurement interval to the source node. The source address can be configured by using the encapsulation source-address command on the source node.

5. The source node analyzes and calculates the delay and jitter for the packets forwarded through the SRv6 TE policy.

Restrictions and guidelines

iFIT can measure the delay and jitter of an SRv6 TE policy only when data traffic is being forwarded through that SRv6 TE policy.

If both the ifit delay-measure command and the srv6-policy ifit delay-measure enable command in SRv6 TE view are used, the ifit delay-measure command takes effect.

If the egress node is not an H3C device, enable iFIT and set the iFIT operating mode to collector on the penultimate hop (an H3C device along the forwarding path). This H3C device will act as the data receiver, record timestamps, establish a UDP session, and provide the timestamps back to the source node to fulfill the functions of the egress node.

If multiple nodes feed back measurement data to the source node, the source node handles the data as follows:

· If the egress node and multiple other nodes feed back measurement data to the source node, the source node prefers the data fed back from the egress node for calculating delay and jitter.

· If multiple non-egress nodes feed back measurement data to the source node, the source node prefers the data fed back from the node closest to the egress node for calculating delay and jitter.

To ensure that iFIT measurement can correctly operate, make sure the clock on all devices participating in iFIT measurement has been synchronized. A violation causes the iFIT calculation results to be inaccurate. You can use NTP and PTP to synchronize clock between devices.

Examples

# Enable iFIT delay and jitter measurement in SRv6 TE policy 1.

<Sysname> system-view

[Sysname] segment-routing ipv6

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

[Sysname-srv6-te] policy 1

[Sysname-srv6-te-policy-1]ifit delay-measure enable

Related commands

ifit enable (Network Management and Monitoring Command Reference)

ifit interval

service-type srv6-segment-list (Network Management and Monitoring Command Reference)

srv6-policy ifit delay-measure enable

srv6-policy ifit interval

work-mode analyzer (Network Management and Monitoring Command Reference)

work-mode collector (Network Management and Monitoring Command Reference)

ifit interval

Use ifit interval to set the iFIT measurement interval in an SRv6 TE policy.

Use undo ifit interval to restore the default.

Syntax

ifit interval time-value

undo ifit interval

Default

No iFIT measurement interval is set for an SRv6 TE policy. The SRv6 TE policy uses the configuration in SRv6 TE view.

Views

SRv6 TE policy view

Predefined user roles

network-admin

Parameters

time-value: Specifies an iFIT measurement interval, in seconds. The value can be 10, 30, 60, or 300.

Usage guidelines

Use this command only on the source node of an SRv6 TE policy.

After you set the iFIT measurement interval, the source node of the SRv6 TE policy incorporates the measurement interval into iFIT packets and uses this measurement interval to perform the following operations:

1. Counts the number of packets forwarded through the SRv6 TE policy and the timestamps of the packets at measurement intervals.

2. Calculates the delay, jitter, and packet loss rate of the SRv6 TE policy at measurement intervals.

The egress node of the SRv6 TE policy obtains the measurement interval from iFIT packets and uses this interval to perform the following operations:

1. Counts the number of packets forwarded through the SRv6 TE policy and the timestamps of the packets at measurement intervals.

2. Provides feedback on the count and timestamps of packets to the source node of the SRv6 TE policy at measurement intervals.

If you execute both this command and the srv6-policy ifit interval command in SRv6 TE view, this command has higher priority.

Examples

# Set the iFIT measurement interval to 60 seconds for SRv6 TE policy 1.

<Sysname> system-view

[Sysname] segment-routing ipv6

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

[Sysname-srv6-te] policy 1

[Sysname-srv6-te-policy-1] ifit interval 60

Related commands

ifit delay-measure

ifit loss-measure

srv6-policy ifit delay-measure enable

srv6-policy ifit interval

srv6-policy ifit loss-measure enable

ifit loss-measure

Use ifit loss-measure to configure iFIT packet loss measurement in an SRv6 TE policy.

Use undo ifit loss-measure to restore the default.

Syntax

ifit loss-measure { disable | enable }

undo ifit loss-measure

Default

iFIT packet loss measurement is not configured in an SRv6 TE policy. The SRv6 TE policy uses the configuration in SRv6 TE view.

Views

SRv6 TE policy view

Predefined user roles

network-admin

Parameters

disable: Disables iFIT packet loss measurement.

enable: Enables iFIT packet loss measurement.

Usage guidelines

Prerequisites

For this command to take effect on an SRv6 TE policy, you must complete the following tasks:

· On the source node of the SRv6 TE policy, enable iFIT, configure the iFIT device ID, set the iFIT operating mode to analyzer, and execute the service-type srv6-segment-list command.

· On the egress node or transit nodes of the SRv6 TE policy, enable iFIT, set the iFIT operating mode to collector, and execute the service-type srv6-segment-list command.

Application scenarios

In-situ Flow Information Telemetry (iFIT) is a type of in-situ flow OAM measurement technology. This technology measures the actual packet loss, delay, and jitter of services in the network by directly encapsulating the measurement interval, packet loss flag, and delay flag information in the iFIT option field of service packets. For more information about iFIT, see Network Management and Monitoring Configuration Guide.

When the iFIT packet loss measurement feature is enabled for the SRv6 TE policy, the device performs the following operations:

1. Measures the packet loss rate of the SRv6 TE policy through iFIT.

2. Compares the measured packet loss rate with the packet loss rate threshold defined in the IPR policy. The measured packet loss rate of the SRv6 TE policy is used as a condition for optimal SRv6 TE policy selection. If the measured value crosses the packet loss rate threshold, it cannot be used as a traffic forwarding path.

Operating mechanism

After iFIT packet loss measurement is enabled on the source node of an SRv6 TE policy, the source node and egress node of the SRv6 TE policy will measure the end-to-end packet loss rate for packets forwarded through the SRv6 TE policy. The measurement procedure is as follows:

1. The source node automatically creates an iFIT instance and assigns a flow ID to the iFIT instance.

2. As the data sender, the source node encapsulates the original packets with the DOH header that carries the iFIT option field and the SRH header when it forwards the packets through the SRv6 TE policy. In addition, the source node counts the number of packets forwarded through the SRv6 TE policy within an iFIT measurement interval.

3. As the data receiver, the egress node decodes the iFIT option field of the packets to obtain the iFIT measurement interval of the SRv6 TE policy, and counts the number of packets received through the SRv6 TE policy within the iFIT measurement interval.

4. The egress node uses the source address of the received packets to establish a UDP session with the source node and returns the packet count statistics within the iFIT measurement interval to the source node. The source address can be configured by using the encapsulation source-address command on the source node.

5. The source node analyzes and calculates the packet loss rate for the packets forwarded through the SRv6 TE policy.

Restrictions and guidelines

iFIT can measure the packet loss rate of an SRv6 TE policy only when data traffic is being forwarded through that SRv6 TE policy.

If both the ifit loss-measure command and the srv6-policy ifit loss-measure enable command in SRv6 TE view are used, the ifit loss-measure command takes effect.

If the egress node is not an H3C device, enable iFIT and set the iFIT operating mode to collector on the penultimate hop (an H3C device along the forwarding path). This H3C device will act as the data receiver to collect packet statistics, establish a UDP session with the source node, and provide the packet statistics back to the source node to fulfill the functions of the egress node.

If multiple nodes feed back measurement data to the source node, the source node handles the data as follows:

· If the egress node and multiple other nodes feed back measurement data to the source node, the source node prefers the data fed back from the egress node for calculating packet loss rate.

· If multiple non-egress nodes feed back measurement data to the source node, the source node prefers the data fed back from the node closest to the egress node for calculating packet loss rate.

Examples

# Enable iFIT packet loss measurement in SRv6 TE policy aaa.

<Sysname> system-view

[Sysname] segment-routing ipv6

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

[Sysname-srv6-te] policy aaa

[Sysname-srv6-te-policy-aaa] ifit loss-measure enable

Related commands

ifit enable (Network Management and Monitoring Command Reference)

ifit interval

service-type srv6-segment-list (Network Management and Monitoring Command Reference)

srv6-policy ifit interval

srv6-policy ifit loss-measure enable

work-mode analyzer (Network Management and Monitoring Command Reference)

work-mode collector (Network Management and Monitoring Command Reference)

ifit measure mode

Use ifit measure mode to specify an iFIT measurement mode for an SRv6 TE policy.

Use undo ifit measure mode to restore the default.

Syntax

ifit measure mode { e2e | trace }

undo ifit measure mode

Default

No iFIT measurement mode is specified for an SRv6 TE policy. The SRv6 TE policy uses the configuration in SRv6 TE view.

Views

SRv6 TE policy view

Predefined user roles

network-admin

Parameters

e2e: Specifies the end-to-end mode. In this mode, only the egress node of the SRv6 TE policy feeds back iFIT measurement results to the source node for calculating the network quality of the SRv6 TE policy.

trace: Specifies the hop-by-hop mode. In this mode, a node along the forwarding path of a target flow feeds back measurement results to the source node of the SRv6 TE policy for calculating the network quality of the SRv6 TE policy as long as iFIT is enabled and iFIT packets are detected on that node.

Usage guidelines

Prerequisites

For this command to take effect on an SRv6 TE policy, you must complete the following tasks:

· On the source node of the SRv6 TE policy, enable iFIT, configure the iFIT device ID, set the iFIT operating mode to analyzer, and execute the service-type srv6-segment-list command.

· On the egress node or transit nodes of the SRv6 TE policy, enable iFIT, set the iFIT operating mode to collector, and execute the service-type srv6-segment-list command.

Recommended configuration

· If the egress node of an SRv6 TE policy is not an H3C device, you must set the iFIT measurement mode to hop-by-hop mode. In this case, enable iFIT and set the iFIT operating mode to collector on the penultimate hop (an H3C device along the forwarding path). This H3C device will act as the data receiver to collect packet statistics, establish a UDP session with the source node, and provide the packet statistics back to the source node to fulfill the functions of the egress node. Typically, hop-by-hop mode is applicable to scenarios where the egress node of an SRv6 TE policy is not an H3C device.

· If both the source and egress nodes of an SRv6 TE policy are H3C devices, set the iFIT measurement mode to end-to-end mode as a best practice. In this mode, the egress node feeds back the iFIT measurement results to the source node of the SRv6 TE policy for calculating the network quality of the SRv6 TE policy. Even if the transit nodes along the forwarding path of a target flow have enabled iFIT and detected iFIT packets, they will not feed back the iFIT measurement results to the source node of the SRv6 TE policy. This mechanism reduces the complexity of device processing.

Operating mechanism

After you specify an iFIT measurement mode for an SRv6 TE policy, the source node of the SRv6 TE policy includes the iFIT measurement mode in the iFIT option field of packets. The packets notify the devices along the forwarding path of the iFIT measurement mode during the forwarding process.

When the iFIT measurement mode of an SRv6 TE policy is set to end-to-end mode, only the egress node that has enabled iFIT and detected iFIT packets feeds back measurement data to the source node through a UDP session. Transit nodes do not feed back measurement data to the source node.

When the iFIT measurement mode of an SRv6 TE policy is set to hop-by-hop mode, all nodes along the forward path of a target flow that have enabled iFIT and detected iFIT packets feed back measurement data to the source node through UDP sessions. The source node selects measurement data for calculating network quality. If multiple non-egress nodes feed back data to the source node, the source node prefers the data fed back from the node closest to the egress node of the SRv6 TE policy for calculating network quality.

Restrictions and guidelines

If both the ifit measure mode command in SRv6 TE policy view and the srv6-policy ifit measure mode command in SRv6 TE view, the ifit measure mode command in SRv6 TE policy view takes effect.

Examples

# Set the iFIT measurement mode to hop-by-hop mode for SRv6 TE policy 1.

<Sysname> system-view

[Sysname] segment-routing ipv6

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

[Sysname-srv6-te] policy 1

[Sysname-srv6-te-policy-1] ifit measure mode trace

Related commands

ifit enable (Network Management and Monitoring Command Reference)

srv6-policy ifit measure mode

service-type srv6-segment-list (Network Management and Monitoring Command Reference)

work-mode analyzer (Network Management and Monitoring Command Reference)

work-mode collector (Network Management and Monitoring Command Reference)

import-route sr-policy

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

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

Syntax

import-route sr-policy

undo import-route sr-policy

Default

BGP does not redistribute BGP IPv6 SR policy routes.

Views

BGP IPv6 SR policy address family

Predefined user roles

network-admin

Usage guidelines

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

Examples

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

<Sysname> system-view

[Sysname] bgp 100

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

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

index

Use index to add a node to a SID list.

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

Syntax

index index-number ipv6 ipv6-address

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

undo index index-number

Default

No nodes exist in a SID list.

Views

SID list view

Predefined user roles

network-admin

Parameters

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

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

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

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

Usage guidelines

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

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

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

· The SRv6 SID corresponding to the last node in the SID list cannot carry the COC flavor.

Examples

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

<Sysname> system-view

[Sysname] segment-routing ipv6

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

[Sysname-srv6-te] segment-list abc

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

# Add nodes to SID list text as follows:

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

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

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

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

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

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

<Sysname> system-view

[Sysname] segment-routing ipv6

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

[Sysname-srv6-te] segment-list text

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

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

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

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

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

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

Related commands

locator

index te-class match

Use index te-class match to configure a mapping between a TE class ID and an SRv6 TE policy, an IPR policy, or the SRv6 BE mode.

Use undo index te-class match to delete a mapping between a TE class ID and an SRv6 TE policy, an IPR policy, or the SRv6 BE mode.

Syntax

index index-value te-class te-class-id match { best-effort | ipr-policy ipr-name | srv6-policy color color-value }

undo index index-value

Default

No mapping is configured between a TE class ID and an SRv6 TE policy, an IPR policy, or the SRv6 BE mode.

Views

SRv6 TE policy group view

TE class forward type view

Predefined user roles

network-admin

Parameters

index-value: Specifies an index for the mapping, in the range of 0 to 4294967294.

te-class-id: Specifies a TE class ID in the range of 1 to 65535.

best-effort: Specifies the SRv6 BE mode. In this mode, the device encapsulates a new IPv6 header in original packets and looks up the IPv6 routing table to forward the packets.

ipr-policy ipr-name: Specifies an IPR policy by its name, a case-sensitive string of 1 to 31 characters.

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

Usage guidelines

Prerequisites

For this command to take effect on an SRv6 TE policy, you must use the forward-type te-class command to enable TE class ID-based traffic steering for that SRv6 TE policy.

Application scenarios

When service packets are steered to an SRv6 TE policy group configured with the index te-class match command, the device matches the TE class ID in the packets with the mappings between TE class IDs and forwarding policies. If a matching mapping is found, the device forwards the packets according to the matching forwarding policy.

Operating mechanism

The device selects a matching forwarding policy for traffic as follows:

· If the TE class ID in a packet is mapped to a color attribute value, the device steers the packet to the SRv6 TE policy containing the color attribute value.

· If the TE class ID in a packet is mapped to an IPR policy, the device uses the path selection policy defined in the IPR policy to steer the packet to the optimal SRv6 TE policy for forwarding.

· If the TE class ID in a packet is mapped to the SRv6 BE mode, the device forwards the packet in SRv6 BE mode. In this mode, the device encapsulates a new IPv6 header in the packet and looks up the IPv6 routing table to forward the packet.

· The device uses the default forwarding policy to forward the following packets after the packets are steered to the SRv6 TE policy group for forwarding:

¡ The packets that do not have a TE class ID.

¡ The packets that have a TE class ID not mapped to any forwarding policy specified by using the index te-class match command.

¡ The packets that have a TE class ID mapped to an invalid forwarding policy.

After traffic is steered to an SRv6 TE policy group for forwarding, when the device forwards a packet according to the default forwarding policy, the device selects a forwarding method in the following order:

1. If a color attribute value or an IPR policy is specified in the default forwarding policy and the SRv6 TE policy used to forward the packet is valid, the device steers the packet to that SRv6 TE policy for forwarding.

2. If the SRv6 BE mode is specified in the default forwarding policy and the SRv6 BE mode is valid, the device encapsulates a new IPv6 header to the packet and looks up the IPv6 routing table to forward the packet.

¡ If the drop-upon-mismatch enable command is used, the device discards the packet.

¡ If the drop-upon-mismatch enable command is not used, the device searches for the TE class ID-to-forwarding policy mapping with the smallest index value and a valid forwarding policy. The device will use the SRv6 TE policy pointed by the mapping to forward the packet or forward the packet in SRv6 BE mode.

Restrictions and guidelines

One TE class ID can be associated only with one index value.

If you execute the index te-class match command multiple times to configure mappings with the same index value, only the most recent configuration takes effect.

One TE class ID can be mapped only to one forwarding policy. For example, if TE class ID 10 has been mapped to IPR policy ipr1, it cannot be mapped to any other IPR policy, an SRv6 TE policy, or the SRv6 BE mode. If you map one TE class ID to multiple forwarding policies, only the most recent configuration takes effect.

As a best practice, configure different endpoint addresses for different SRv6 TE policy groups. If you configure the same endpoint address for multiple SRv6 TE policy groups, SRv6 TE policies with that endpoint address will belong to multiple SRv6 TE policy groups.

Examples

# Map TE class ID 100 to IPR policy ipr1 for traffic forwarding.

<Sysname> system-view

[Sysname] segment-routing ipv6

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

[Sysname-srv6-te] policy-group 1

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

[Sysname-srv6-te-policy-group-1] index 10 te-class 100 match ipr-policy ipr1

Related commands

default match (TE class ID-based traffic steering)

drop-upon-mismatch enable

forward-type (SRv6 TE policy group view)

forward-type (SRv6 TE ODN policy group view)

intelligent-policy-route

Use intelligent-policy-route to enable Intelligent Policy Route (IPR) and enter SRv6 TE IPR view.

Use undo intelligent-policy-route to disable IPR and delete all settings in SRv6 TE IPR view.

Syntax

intelligent-policy-route

undo intelligent-policy-route

Default

IPR is disabled.

Views

SRv6 TE view

Predefined user roles

network-admin

Usage guidelines

IPR dynamically selects the optimal SRv6 TE policy from the SRv6 TE policies in an SRv6 TE policy group based on the iFIT measurements results of these SRv6 TE policies.

By defining different IPR policies, you can configure different network quality thresholds, priority orders of SRv6 TE policies, and switchover policies. Different IPR policies are used to meet the network quality requirements of different services.

To dynamically select the optimal SRv6 TE policy, IPR must collaborate with the iFIT packet loss, delay, and jitter measurements of SRv6 TE policies.

Examples

# Enable IPR and enter SRv6 TE IPR view.

<Sysname> system-view

[Sysname] segment-routing ipv6

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

[Sysname-srv6-te] intelligent-policy-route

[Sysname-srv6-te-ipr]

ipr-policy

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

Use undo ipr-policy to delete the IPR policy and its settings.

Syntax

ipr-policy ipr-name

undo ipr-policy

Default

No IPR policy exists.

Views

SRv6 TE IPR view

Predefined user roles

network-admin

Parameters

ipr-name: Specifies a name for the IPR policy, a case-sensitive string of 1 to 31 characters.

Usage guidelines

Application scenarios

When service packets are steered to an SRv6 TE policy group configured with TE class ID-based traffic steering, the device matches the TE class ID in the packets with the mappings between TE class IDs and IPR policies in the SRv6 TE policy group. To configure the mappings, use the index te-class match command. If a matching mapping is found, the device selects an SRv6 TE policy to forward the packets according to the path selection policy defined in the matching IPR policy.

Operating mechanism

You can create multiple IPR policies in SRv6 TE IPR view. Each IPR policy is an SLA-based policy for selecting the optimal SRv6 TE policy. You can define the following contents in an IPR policy:

· SLA thresholds for service traffic, including the delay threshold, packet loss rate threshold, jitter threshold, and Composite Measure Indicator (CMI) threshold.

· Mappings between color attribute values of SRv6 TE policies and path selection priority values.

· Switchover period between SRv6 TE policies and WTR period.

An IPR policy must cooperate with the iFIT packet loss measurement and iFIT delay and jitter measurement features of SRv6 TE policies for intelligent forwarding path selection. The cooperative mechanism between an IPR policy and the iFIT measurement features of SRv6 TE policies is as follows:

1. iFIT measures the network quality.

You can enable iFIT packet loss measurement and iFIT delay and jitter measurement for SRv6 TE policies on the source node of an SRv6 TE policy group. iFIT then performs the following operations:

a. Measures the link quality of different SRv6 TE policies in the SRv6 TE policy group.

b. Sends the SLA measurement data to IPR on the source node for path calculation and selection according to the iFIT measurement interval.

2. The source node calculates candidate paths.

The source node of SRv6 TE policies calculates the optimal SRv6 TE policy based on the optimal path calculation period set by using the refresh-period command. If the source node finds that any value of the delay, packet loss rate, jitter, and CMI values obtained from the most recent iFIT measurement data for an SRv6 TE policy crosses a threshold set in an IPR policy, that SRv6 TE policy does not comply with the SLA requirements. As a result, the source node does not use that SRv6 TE policy as a candidate path for service traffic forwarding. If iFIT fails to measure the delay, packet loss rate, jitter, and CMI values of an SRv6 TE policy, but the SRv6 TE policy is valid, the source node still uses this SRv6 TE policy as a candidate path for service traffic forwarding.

3. The source node selects the optimal path.

The source node selects the SRv6 TE policy with the highest priority as the optimal forwarding path according to the priority order defined in the IPR policy, and steers service traffic to this SRv6 TE policy. When multiple SRv6 TE policies have the same priority, traffic can be load-balanced among these SRv6 TE policies.

Restrictions and guidelines

To delete an IPR policy that has been mapped to a TE class ID, you must first delete the mapping between the IPR policy and the TE class ID.

Examples

# Create IPR policy ipr1 and enter SRv6 TE IPR policy view.

<Sysname> system-view

[Sysname] segment-routing ipv6

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

[Sysname-srv6-te] intelligent-policy-route

[Sysname-srv6-te-ipr] ipr-policy ipr1

[Sysname-srv6-ipr-policy-ipr1]

Related commands

index te-class match

jitter threshold

Use jitter threshold to set the jitter threshold in an IPR policy.

Use undo jitter threshold to restore the default.

Syntax

jitter threshold time-value

undo jitter threshold

Default

The jitter threshold is 3000 milliseconds in an IPR policy.

Views

SRv6 TE IPR policy view

Predefined user roles

network-admin

Parameters

time-value: Specifies a jitter threshold value in the range of 0 to 3000, in milliseconds.

Usage guidelines

An SRv6 TE policy can be used as a candidate forwarding path and participate in optimal SRv6 TE policy selection only when the iFIT delay and jitter measurement feature detects that the jitter of the SRv6 TE policy does not cross the jitter threshold set by this command.

If the optimal candidate path of an SRv6 TE policy has multiple valid SID lists with weight values, the device uses the weighted sum of the iFIT jitters of all of these valid SID lists as the jitter value of that SRv6 TE policy when intelligent policy routing computes whether the jitter of that SRv6 TE policy crosses the threshold.

Examples

# Set the jitter threshold to 20 milliseconds in IPR policy ipr1.

<Sysname> system-view

[Sysname] segment-routing ipv6

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

[Sysname-srv6-te] intelligent-policy-route

[Sysname-srv6-ipr] ipr-policy ipr1

[Sysname-srv6-ipr-policy-ipr1] jitter threshold 20

local-binding-sid

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

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

Syntax

local-binding-sid ipv6 ipv6-address

undo local-binding-sid

Default

No local BSID exists.

Views

SID list view

Predefined user roles

network-admin

Parameters

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

Usage guidelines

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

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

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

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

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

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

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

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

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

Examples

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

<Sysname> system-view

[Sysname] segment-routing ipv6

[Sysname-segment-routing] traffic-engineering

[Sysname-srv6-te] segment-list s1

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

Related commands

reverse-binding-sid

loss threshold

Use loss threshold to set the packet loss rate threshold in an IPR policy.

Use undo loss threshold to restore the default.

Syntax

loss threshold threshold-value

undo loss threshold

Default

The packet loss rate threshold is 1000‰ in an IPR policy.

Views

SRv6 TE IPR policy view

Predefined user roles

network-admin

Parameters

threshold-value: Specifies a packet loss threshold value in the range of 0 to 1000, in per mille (‰).

Usage guidelines

An SRv6 TE policy can be used as a candidate forwarding path and participate in optimal SRv6 TE policy selection only when the iFIT packet loss measurement feature detects that the packet loss rate of the SRv6 TE policy does not cross the packet loss rate threshold set by this command.

If the optimal candidate path of an SRv6 TE policy has multiple valid SID lists with weight values, the device uses the weighted sum of the iFIT packet loss rates of all of these valid SID lists as the packet loss rate of that SRv6 TE policy when intelligent policy routing computes whether the packet loss rate of that SRv6 TE policy crosses the threshold.

Examples

# Set the packet loss threshold to 5‰ in IPR policy ipr1.

<Sysname> system-view

[Sysname] segment-routing ipv6

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

[Sysname-srv6-te] intelligent-policy-route

[Sysname-srv6-ipr] ipr-policy ipr1

[Sysname-srv6-ipr-policy-ipr1] loss threshold 5

measure count

Use measure count to set the data calculation mode for IPR.

Use undo measure count to restore the default.

Syntax

measure count { one-way | two-way-average }

undo measure count

Default

IPR uses the one-way data calculation mode.

Views

SRv6 TE IPR view

Predefined user roles

network-admin

Parameters

one-way: Specifies the one-way data calculation mode for IPR.

two-way-average: Specifies the two-way data calculation mode for IPR.

Usage guidelines

By using the service packets forwarded by an SRv6 TE policy, iFIT measurement can obtain network quality of the following paths:

· Forward path from the source node to the endpoint node of the SRv6 TE policy.

· Return path from the endpoint node to the source node of the SRv6 TE policy.

IPR supports the following data calculation modes for SRv6 TE policy network quality measurement through iFIT:

· One-way mode—IPR uses the one-way iFIT data collected for the source-to-endpoint path to measure the network quality.

· Two-way mode—IPR uses the average of round-trip iFIT data collected for the source-to-endpoint path and the endpoint-to-source path to measure the network quality.

If the two-way mode is specified, iFIT cannot accurately measure the packet loss rate of the SRv6 TE policy tunnel. Therefore, the device still uses the measurement results of the one-way mode as the packet loss rate data.

Examples

# Specify the two-way data calculation mode for IPR.

<Sysname> system-view

[Sysname] segment-routing ipv6

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

[Sysname-srv6-te] intelligent-policy-route

[Sysname-srv6-te-ipr] measure count two-way-average

mirror remote-sid delete-delay

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

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

Syntax

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

undo mirror remote-sid delete-delay

Default

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

Views

SRv6 view

Predefined user roles

network-admin

Parameters

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

Usage guidelines

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

Examples

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

<Sysname> system-view

[Sysname] segment-routing ipv6

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

on-demand

Use on-demand to create an on-demand next-hop (ODN) template for creating SRv6 TE policies and enter SRv6 TE ODN view, or enter the SRv6 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 SRv6 TE policy ODN templates exist.

Views

SRv6 TE view

Predefined user roles

network-admin

Parameters

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

Usage guidelines

When the device receives a BGP route, it compares the color extended attribute value of the BGP route with the color value of the ODN template. If the color values match, the device automatically generates an SRv6 TE policy 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 manually configure the SID lists for the candidate path with preference 200, 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 SRv6 TE policy.

Examples

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

<Sysname> system-view

[Sysname] segment-routing ipv6

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

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

[Sysname-srv6-te-odn-1]

on-demand-group

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

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

Syntax

on-demand-group color color-value

undo on-demand-group color color-value

Default

No SRv6 TE policy group ODN templates exist.

Views

SRv6 TE view

Predefined user roles

network-admin

Parameters

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

Usage guidelines

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

Examples

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

<Sysname> system-view

[Sysname] segment-routing ipv6

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

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

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

policy

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

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

Syntax

policy policy-name

undo policy policy-name

Default

No SRv6 TE policies exist.

Views

SRv6 TE view

Predefined user roles

network-admin

Parameters

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

Examples

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

<Sysname> system-view

[Sysname] segment-routing ipv6

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

[Sysname-srv6-te] policy p1

[Sysname-srv6-te-policy-p1]

policy-group

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

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

Syntax

policy-group group-id

undo policy-group group-id

Default

No SRv6 TE policy groups exist.

Views

SRv6 TE view

Predefined user roles

network-admin

Parameters

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

Usage guidelines

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

Examples

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

<Sysname> system-view

[Sysname] segment-routing ipv6

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

[Sysname-srv6-te] policy-group 1

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

preference

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

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

Syntax

preference preference-value

undo preference preference-value

Default

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

Views

SRv6 TE policy candidate path view

Predefined user roles

network-admin

Parameters

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

Usage guidelines

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

Examples

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

<Sysname> system-view

[Sysname] segment-routing ipv6

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

[Sysname-srv6-te] policy a1

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

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

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

refresh-period

Use refresh-period to set the interval at which IPR calculates the optimal path.

Use undo refresh-period to restore the default.

Syntax

refresh-period time-value

undo refresh-period

Default

IPR calculates the optimal path at intervals of 60 seconds.

Views

SRv6 TE IPR view

Predefined user roles

network-admin

Parameters

time-value: Specifies an interval for IPR to calculate the optimal path, in the range of 2 to 60 seconds.

Usage guidelines

If the source node of an SRv6 TE policy group has mappings between TE class IDs and IPR policies (configured by using the index te-class match command), it will calculate the optimal SRv6 TE policy according to the period set by using the refresh-period command. Then, it will forward traffic through this optimal SRv6 TE policy.

Periodically calculating the optimal path can ensure that services are always forwarded through an SRv6 TE policy that meets the SLA requirements and has the highest priority. You can set the period for calculating the optimal path as needed. The shorter the period, the higher the system overhead.

Examples

# Set the interval at which IPR calculates the optimal path to 20 seconds.

<Sysname> system-view

[Sysname] segment-routing ipv6

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

[Sysname-srv6-te] intelligent-policy-route

[Sysname-srv6-te-ipr] refresh-period 20

reset segment-routing ipv6 te forwarding statistics

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

Syntax

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

Views

User view

Predefined user roles

network-admin

Parameters

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

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

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

Usage guidelines

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

Examples

# Clear forwarding statistics for all SRv6 TE policies.

<Sysname> reset segment-routing ipv6 te forwarding statistics

Related commands

display segment-routing ipv6 te forwarding

forwarding statistics

srv6-policy forwarding statistics enable

srv6-policy forwarding statistics interval

restrict

Use restrict to configure the ODN SRv6 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 SRv6 TE policy when the route's color attribute value is the same as the ODN color value.

Views

SRv6 TE ODN view

Predefined user roles

network-admin

Parameters

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

Usage guidelines

You can specify an IPv6 prefix list to filter BGP routes. The BGP routes permitted by the specified IPv6 prefix list can trigger ODN to create SRv6 TE policies. The BGP routes denied by the specified IPv6 prefix list cannot trigger ODN to create SRv6 TE policies.

Examples

# Permit the BGP routes in subnet 1000::/96 to trigger ODN to create SRv6 TE policies.

<Sysname> system-view

[Sysname] ipv6 prefix-list policy permit 1000:: 96

[Sysname] segment-routing ipv6

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

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

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

Related commands

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

reverse-binding-sid

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

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

Syntax

reverse-binding-sid ipv6 ipv6-address

undo reverse-binding-sid

Default

No reverse BSID exists.

Views

SID list view

Predefined user roles

network-admin

Parameters

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

Usage guidelines

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

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

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

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

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

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

Examples

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

<Sysname> system-view

[Sysname] segment-routing ipv6

[Sysname-segment-routing] traffic-engineering

[Sysname-srv6-te] segment-list s1

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

Related commands

local-binding-sid

router-id filter

Use router-id filter to enable Router ID filtering.

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

Syntax

router-id filter [ bgp-rib-only ]

undo router-id filter

Default

Router ID filtering is disabled.

Views

BGP IPv6 SR policy address family.

Predefined user roles

network-admin

Parameters

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

Usage guidelines

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

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

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

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

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

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

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

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

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

Examples

# Enable Router ID filtering.

<Sysname> system-view

[Sysname] bgp 100

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

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

sbfd

Use sbfd to configure SBFD for an SRv6 TE policy.

Use undo sbfd to restore the default.

Syntax

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

undo sbfd

Default

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

Views

SRv6 TE policy view

Predefined user roles

network-admin

Parameters

disable: Disables SBFD for the SRv6 TE policy.

enable: Enables SBFD for the SRv6 TE policy.

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

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

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

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

insert: Uses the insertion mode to encapsulate SBFD packets.

Usage guidelines

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

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

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

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

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

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

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

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

Examples

# Enable SBFD for SRv6 TE policy 1.

<Sysname> system-view

[Sysname] segment-routing ipv6

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

[Sysname-srv6-te] policy 1

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

Related commands

· bfd srv6-encapsulation-mode insert

display segment-routing ipv6 te sbfd

explicit segment-list

sbfd local-discriminator (High Availability Command Reference)

srv6-policy sbfd

schedule-priority

Use schedule-priority to configure the switchover scheduling priority for an IPR policy.

Use undo schedule-priority to restore the default.

Syntax

schedule-priority priority-value

undo schedule-priority

Default

The switchover scheduling priority is 0 for an IPR policy.

Views

SRv6 TE IPR policy view

Predefined user roles

network-admin

Parameters

priority-value: Specifies the switchover scheduling priority in the range of 1 to 65535. A larger value represents a higher priority.

Usage guidelines

Operating mechanism

When different service traffic is forwarded through multiple SRv6 TE policies in different IPR policies, several SRv6 TE policies might share the same egress interface. If the bandwidth usage of this interface exceeds the upper threshold specified by the bandwidth-threshold upper command, traffic optimization must be performed at the interval defined by the refresh-period command, by sequentially switching the service traffic carried by the IPR policies with the lowest switchover scheduling priority to be forwarded by other SRv6 TE policies, thereby avoiding the use of the same egress interface for forwarding.

For example, on the ingress node, traffic identified by TE class ID 100 is forwarded through the optimal path SRv6 TE policy 1 in IPR policy A, traffic identified by TE class ID 200 is forwarded through the optimal path SRv6 TE policy 2 in IPR policy B, and traffic identified by TE class ID 300 is forwarded through the optimal path SRv6 TE policy 3 in IPR policy C. SRv6 TE policy 1, SRv6 TE policy 2, and SRv6 TE policy 3 all use Interface X as the egress interface. If the actual bandwidth usage of Interface X exceeds the upper threshold specified by the bandwidth-threshold upper command, the switchover scheduling priorities of IPR policy A, IPR policy B, and IPR policy C are compared, and the service traffic carried by the IPR policy with the lowest switchover scheduling priority is switched first. This process continues until the actual bandwidth usage of Interface X is less than or equal to the upper threshold specified by the bandwidth-threshold upper command.

Restrictions and guidelines

If multiple IPR policies have the same switchover scheduling priority, the traffic carried by all IPR policies with the same priority will be switched. As a best practice, configure different switchover scheduling priorities for different IPR policies.

Examples

# Configure the switchover scheduling priority as 30000 for the IPR policy.

<Sysname> system-view

[Sysname] segment-routing ipv6

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

[Sysname-srv6-te] intelligent-policy-route

[Sysname-srv6-ipr] ipr-policy ipr1

[Sysname-srv6-ipr-policy-ipr1] schedule-priority 30000

segment-list

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

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

Syntax

segment-list segment-list-name

undo segment-list segment-list-name

Default

No SID lists exist.

Views

SRv6 TE view

Predefined user roles

network-admin

Parameters

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

Examples

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

<Sysname> system-view

[Sysname] segment-routing ipv6

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

[Sysname-srv6-te] segment-list abc

[Sysname-srv6-te-sl-abc]

service-class

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

Use undo service-class to restore the default.

Syntax

service-class service-class-value

undo service-class

Default

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

Views

SRv6 TE policy view

Predefined user roles

network-admin

Parameters

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

Usage guidelines

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

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

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

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

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

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

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

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

Examples

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

<Sysname> system-view

[Sysname] segment-routing ipv6

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

[Sysname-srv6-te] policy 1

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

Related commands

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

remark service-class (ACL and QoS Command Reference)

shutdown

Use shutdown to shut down an SRv6 TE policy.

Use undo shutdown to bring up an SRv6 TE policy.

Syntax

shutdown

undo shutdown

Default

An SRv6 TE policy is not administratively shut down.

Views

SRv6 TE policy view

Predefined user roles

network-admin

Usage guidelines

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

Examples

# Shut down SRv6 TE policy 1.

<Sysname> system-view

[Sysname] segment-routing ipv6

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

[Sysname-srv6-te] policy 1

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

sr-policy steering

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

Use undo sr-policy steering to restore the default.

Syntax

sr-policy steering { disable | policy-based }

undo sr-policy steering

Default

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

Views

BGP instance view

Predefined user roles

network-admin

Parameters

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

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

Usage guidelines

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

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

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

This command does not take effect on L2VPN networks.

Examples

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

<Sysname> system-view

[Sysname] bgp 100

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

sr-te frr enable

Use sr-te frr enable to enable SRv6 TE FRR.

Use undo sr-te frr enable to disable SRv6 TE FRR.

Syntax

sr-te frr enable

undo sr-te frr enable

Default

SRv6 TE FRR is disabled.

Views

SRv6 view

Predefined user roles

network-admin

Usage guidelines

After SRv6 TE FRR is enabled, when a transit node of an SRv6 TE policy fails, the upstream node of the faulty node can take over to forward packets. The upstream node is called a proxy forwarding node.

After SRv6 TE FRR is enabled on a node, upon receiving a packet that contains an SRH and the SL in the SRH is greater than 1 (SL>1), the node will act as a proxy forwarding node in any of the following scenarios:

· The node does not find a matching forwarding entry in the IPv6 FIB.

· The next hop address of the packet is the destination address of the packet, and the outgoing interface for the destination address is in DOWN state.

· The matching local SRv6 SID is an END.X SID, and the outgoing interface for the END.X SID is in DOWN state.

· The outgoing interface in the matching route is NULL0.

A proxy forwarding node forwards packets as follows:

· Decrements the SL value in the SRH of a packet by 1.

· Copies the next SID to the DA field in the outer IPv6 header, so as to use the SID as the destination address of the packet.

· Looks up the forwarding table by the destination address and then forwards the packet.

In this way, the proxy forwarding node bypasses the faulty node. This transit node failure protection technology is referred to as SRv6 TE FRR.

In a complex network, any node might act as a transit node. As a best practice to improve the whole network security, enable SRv6 TE FRR on all nodes.

Examples

# Enable SRv6 TE FRR.

<Sysname> system-view

[Sysname] segment-routing ipv6

[Sysname-segment-routing-ipv6] sr-te frr enable

Related commands

bfd echo

srv6-policy autoroute enable

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

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

Syntax

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

undo srv6-policy autoroute enable

Default

Automatic route advertisement for SRv6 TE policies is disabled.

Views

IS-IS IPv6 address family view

Predefined user roles

network-admin

Parameters

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

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

Usage guidelines

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

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

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

Examples

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

<Sysname> system-view

[Sysname] isis 1

[Sysname-isis-1] address-family ipv6

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

Related commands

autoroute enable

srv6-policy backup hot-standby enable

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

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

Syntax

srv6-policy backup hot-standby enable

undo srv6-policy backup hot-standby enable

Default

Hot standby is disabled for all SRv6 TE policies.

Views

SRv6 TE view

Predefined user roles

network-admin

Usage guidelines

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

Examples

# Enable hot standby for all SRv6 TE policies.

<Sysname> system-view

[Sysname] segment-routing ipv6

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

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

Related commands

backup hot-standby

srv6-policy bandwidth sample

Use srv6-policy bandwidth sample to enable global bandwidth sampling.

Use undo srv6-policy bandwidth sample to disable global bandwidth sampling.

Syntax

srv6-policy bandwidth sample enable

undo srv6-policy bandwidth sample enable

Default

Global bandwidth sampling is disabled.

Views

SRv6 TE view

Predefined user roles

network-admin

Usage guidelines

Application scenarios

· The network quality (including delay, jitter, and packet loss) of the SRv6 TE policy complies with the SLA standards defined in the IPR policy.

· The bandwidth usage of the SRv6 TE policy does not exceed the upper threshold specified in the bandwidth-threshold upper command.

Operating mechanism

After you enable bandwidth sampling for an IPR policy, the device operates as follows:

1. Collects the egress interface bandwidth usage of each SRv6 TE policy at the interval specified in the srv6-policy bandwidth sample interval command.

2. Calculates the expected average bandwidth usage of each SRv6 TE policy.

3. Selects the optimal SRv6 TE policy.

¡ Use the real-time statistics of the SRv6 TE policy currently carrying the service as the expected service bandwidth.

SRv6 TE Policy A

Candidate paths(Preference 200)

Segment List1(weight 10) interface1 bw1 30%

interface2 bw2 50%

Segment List2(weight 30) interface3 bw3 80%

Based on the current bandwidth usage of the equal-cost egress interfaces, the average bandwidth usage of these interfaces is taken as the bandwidth usage of SID list 1, which is (30% + 50%)/2 = 40%.

The bandwidth usage of SID list 2 is the current bandwidth usage of egress interface3, which is 80%.

Based on the weights and bandwidth usage of different SID lists, use a weighted average approach to calculate the bandwidth usage of SRv6 TE policy A as (40% × 10 + 80% × 30)/(10 + 30) = 70%.

The expected average bandwidth usage of SRv6 TE policy A is calculated as follows:

(Expected service bandwidth + 70% × (bw1 + bw2 + bw3))/(bw1 + bw2 + bw3).

Restrictions and guidelines

Examples

# Enable global bandwidth sampling.

<Sysname> system-view

[Sysname] segment-routing ipv6

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

[Sysname-srv6-te] srv6-policy bandwidth sample enable

Related commands

bandwidth-threshold upper

expect-bandwidth

bandwidth sample

srv6-policy bandwidth sample interval

Use srv6-policy bandwidth sample interval to configure the bandwidth usage sampling interval for SRv6 TE policy egress interfaces.

Use undo srv6-policy bandwidth sample interval to restore the default.

Syntax

srv6-policy bandwidth sample interval time-value

undo srv6-policy bandwidth sample interval

Default

The bandwidth usage sampling interval is 30 seconds for SRv6 TE policy egress interfaces.

Views

SRv6 TE view

Predefined user roles

network-admin

Parameters

time-value: Specifies the bandwidth usage sampling interval for SRv6 TE policy egress interfaces, in the range of 1 to 1800 seconds.

Usage guidelines

Operating mechanism

After you execute the bandwidth sample command to enable bandwidth sampling or execute the srv6-policy bandwidth sample command, you can use the srv6-policy bandwidth sample interval command to configure the bandwidth usage sampling interval for SRv6 TE policy egress interfaces.

This command takes effect on all IPR policies.

Restrictions and guidelines

A certain difference exists between the configured and actual SRv6 TE policy egress interface bandwidth usage sampling intervals:

· When the configured value for the time-value argument is in the range of 1 to 10, the actual interval that takes effect can only be 1, 2, 5, or 10.

· When the configured value for the time-value argument is in the range of 10 to 60, the actual interval that takes effect is 10+5n, where n is an integer smaller than or equal to 10.

· When the configured value for the time-value argument is in the range of 60 to 180, the actual interval that takes effect is 60+10n, where n is an integer smaller than or equal to 12.

· When the configured value for the time-value argument is in the range of 180 to 300, the actual interval that takes effect is 180+30n, where n is an integer smaller than or equal to 4.

· When the configured value for the time-value argument is in the range of 300 to 900, the actual interval that takes effect is 300+60n, where n is an integer smaller than or equal to 10.

· When the configured value for the time-value argument is in the range of 900 to 1800, the actual interval that takes effect is 900+300n, where n is an integer smaller than or equal to 3.

If the configured value falls between two actual effective values, the actual effective value will be the larger of the two. For example, if the configured value is 3, the actual effective value is 5. If the configured value is 22, the actual effective value is 25.

Examples

# Configure the bandwidth usage sampling interval as 100 seconds for SRv6 TE policy egress interfaces.

<Sysname> system-view

[Sysname] segment-routing ipv6

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

[Sysname-srv6-te] srv6-policy bandwidth sample interval 100

Related commands

bandwidth sample

srv6-policy bandwidth sample

srv6-policy bandwidth-threshold lower

Use srv6-policy bandwidth-threshold lower to configure the lower bandwidth limit.

Use undo srv6-policy bandwidth-threshold lower to restore the default.

Syntax

srv6-policy bandwidth-threshold lower lower-value

undo srv6-policy bandwidth-threshold lower

Default

The lower bandwidth limit is not configured.

Views

SRv6 TE view

Predefined user roles

network-admin

Parameters

lower-value: Specifies the lower bandwidth limit in the range of 1% to 100%.

Usage guidelines

Operating mechanism

· The quality indicators such as latency, jitter, and packet loss for the service traffic in this SRv6 TE policy meet the SLA standards defined in the IPR policy.

Restrictions and guidelines

This command takes effect on all IPR policies. The bandwidth-threshold switch-back command takes effect only on a specific IPR policy.

Examples

# Configure the lower bandwidth limit as 30%.

<Sysname> system-view

[Sysname] segment-routing ipv6

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

[Sysname-srv6-te] srv6-policy bandwidth-threshold lower 30

Related commands

bandwidth-threshold upper

refresh-period

bandwidth-threshold switch-back

wait-to-restore-period

srv6-policy bfd echo

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

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

Syntax

srv6-policy bfd echo source-ipv6 ipv6-address [ template template-name ] [ backup-template backup-template-name ] [ reverse-path reverse-binding-sid ]

undo srv6-policy bfd echo

Default

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

Views

SRv6 TE view

Predefined user roles

network-admin

Parameters

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

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

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

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

Usage guidelines

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

Examples

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

<Sysname> system-view

[Sysname] segment-routing ipv6

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

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

Related commands

bfd echo

display segment-routing ipv6 te bfd

srv6-policy color priority

Use srv6-policy color priority to configure a mapping between the color attribute value of an SRv6 TE policy and a path selection priority in an IPR policy.

Use undo srv6-policy color to delete a mapping between the color attribute value of an SRv6 TE policy and a path selection priority in an IPR policy.

Syntax

srv6-policy color color-value priority priority-value

undo srv6-policy color color-value

Default

No mapping is configured between the color attribute value of an SRv6 TE policy and a path selection priority in an IPR policy.

Views

SRv6 TE IPR policy view

Predefined user roles

network-admin

Parameters

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

priority-value: Specifies a path selection priority in the range of 1 to 8. The smaller the value, the higher the priority.

Usage guidelines

Operating mechanism

Multiple SRv6 TE policies in an SRv6 TE policy group are distinguished by their color attribute values. You can use this command to establish a mapping between the color attribute value of each SRv6 TE policy and a path selection priority. In this way, these SRv6 TE policies are associated with different path selection priorities. If the network quality of multiple SRv6 TE policies meets the SLA requirements defined in the IPR policy, the SRv6 TE policy with the smallest priority value will be selected as the optimal forwarding path.

A valid SRv6 TE policy can be used for packet forwarding and be used as a candidate optimal forwarding path even if the following conditions exist:

· iFIT fails to measure the network quality of that SRv6 TE policy.

· The source node of the SRv6 TE policy group fails to obtain the network quality of that SRv6 TE policy due to reasons such as absence of traffic in the SRv6 TE policy.

Restrictions and guidelines

If different color attribute values are mapped to the same priority and the SRv6 TE policies associated with this priority all meet the SLA requirements defined in the IPR policy, the traffic will be load-balanced among the SRv6 TE policies identified by these color attribute values.

You can specify a maximum of eight color attribute values in one IPR policy, meaning that you can specify a maximum of eight different SRv6 TE policies in a single IPR policy.

Examples

# Map the color attribute value of 1 to priority 1 in IPR policy ipr1.

<Sysname> system-view

[Sysname] segment-routing ipv6

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

[Sysname-srv6-te] intelligent-policy-route

[Sysname-srv6-ipr] ipr-policy ipr1

[Sysname-srv6-ipr-policy-ipr1] srv6-policy color 1 priority 1

srv6-policy encapsulation-mode

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

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

Syntax

srv6-policy encapsulation-mode encaps reduced

undo srv6-policy encapsulation-mode encaps reduced

srv6-policy encapsulation-mode insert

undo srv6-policy encapsulation-mode insert

srv6-policy encapsulation-mode insert reduced

undo srv6-policy encapsulation-mode insert reduced

Default

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

Views

SRv6 TE view

Predefined user roles

network-admin

Parameters

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

insert: Specifies the encapsulation mode as insertion mode.

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

Usage guidelines

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

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

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

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

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

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

Examples

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

<Sysname> system-view

[Sysname] segment-routing ipv6

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

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

Related commands

encapsulation source-address

encapsulation-mode

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

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

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

Syntax

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

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

Default

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

Views

SRv6 TE view

Predefined user roles

network-admin

Usage guidelines

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

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

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

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

Examples

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

<Sysname> system-view

[Sysname] segment-routing ipv6

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

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

Related commands

encapsulation-mode encaps include local-end.x

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

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

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

Syntax

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

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

Default

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

Views

SRv6 TE view

Predefined user roles

network-admin

Usage guidelines

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

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

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

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

Examples

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

<Sysname> system-view

[Sysname] segment-routing ipv6

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

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

Related commands

encapsulation-mode insert include local-end.x

srv6-policy forwarding statistics enable

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

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

Syntax

srv6-policy forwarding statistics [ service-class ] enable

undo srv6-policy forwarding statistics enable

Default

Traffic forwarding statistics is disabled for all SRv6 TE policies.

Views

SRv6 TE view

Predefined user roles

network-admin

Parameters

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

Usage guidelines

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

Examples

# Enable traffic forwarding statistics for all SRv6 TE policies.

<Sysname> system-view

[Sysname] segment-routing ipv6

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

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

Related commands

display segment-routing ipv6 te forwarding

forwarding statistic

reset segment-routing ipv6 te forwarding statistics

srv6-policy forwarding statistics interval

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

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

Syntax

srv6-policy forwarding statistics interval interval

undo srv6-policy forwarding statistics interval

Default

The SRv6 TE policies forwarding statistics interval is 30 seconds.

Views

SRv6 TE view

Predefined user roles

network-admin

Parameters

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

Predefined user roles

This command takes effect only all SRv6 TE policies.

Examples

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

<Sysname> system-view

[Sysname] segment-routing ipv6

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

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

Related commands

display segment-routing ipv6 te forwarding

forwarding statistic

reset segment-routing ipv6 te forwarding statistics

srv6-policy forwarding statistics enable

srv6-policy ifit delay-measure enable

Use srv6-policy ifit delay-measure enable to globally enable iFIT delay and jitter measurement for SRv6 TE policies.

Use undo srv6-policy ifit delay-measure enable to restore the default.

Syntax

srv6-policy ifit delay-measure enable

undo srv6-policy ifit delay-measure enable

Default

iFIT delay and jitter measurement is globally disabled for SRv6 TE policies.

Views

SRv6 TE view

Predefined user roles

network-admin

Usage guidelines

Prerequisites

For this command to take effect on an SRv6 TE policy, you must complete the following tasks:

· On the source node of the SRv6 TE policy, enable iFIT, configure the iFIT device ID, set the iFIT operating mode to analyzer, and execute the service-type srv6-segment-list command.

· On the egress node or transit nodes of the SRv6 TE policy, enable iFIT, set the iFIT operating mode to collector, and execute the service-type srv6-segment-list command.

Application scenarios

In-situ Flow Information Telemetry (iFIT) is a type of in-situ flow OAM measurement technology. This technology measures the actual packet loss, delay, and jitter of services in the network by directly encapsulating the measurement interval, packet loss flag, and delay flag information in the iFIT option field of service packets. For more information about iFIT, see Network Management and Monitoring Configuration Guide.

When the iFIT delay and jitter measurement feature is enabled for SRv6 TE policies, the device performs the following operations:

1. Measures the delay and jitter of an SRv6 TE policy through iFIT.

2. Compares the measured delay and jitter values with the delay and jitter thresholds defined in the IPR policy where the SRv6 TE policy is specified. The measured delay and jitter values of the SRv6 TE policy are used as conditions for optimal SRv6 TE policy selection. If the measured values cross the delay and jitter thresholds, it cannot be used as a traffic forwarding path.

Operating mechanism

1. The source node automatically creates an iFIT instance and assigns a flow ID to the iFIT instance.

5. The source node analyzes and calculates the delay and jitter for the packets forwarded through the SRv6 TE policy.

Restrictions and guidelines

iFIT can measure the delay and jitter of an SRv6 TE policy only when data traffic is being forwarded through that SRv6 TE policy.

If both the srv6-policy ifit delay-measure enable command in SRv6 TE view and the ifit delay-measure command in SRv6 TE policy view are used, the ifit delay-measure command takes effect.

If the egress node is not an H3C device, enable iFIT and set the iFIT operating mode to collector on the penultimate hop (an H3C device along the forwarding path). This H3C device will act as the data receiver to record timestamps, establish a UDP session, and provide the timestamps back to the source node to fulfill the functions of the egress node.

If multiple nodes feed back measurement data to the source node, the source node handles the data as follows:

· If the egress node and multiple other nodes feed back measurement data to the source node, the source node prefers the data fed back from the egress node for calculating delay and jitter.

· If multiple non-egress nodes feed back measurement data to the source node, the source node prefers the data fed back from the node closest to the egress node for calculating delay and jitter.

Examples

# Globally enable iFIT delay and jitter measurement for SRv6 TE policies.

<Sysname> system-view

[Sysname] segment-routing ipv6

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

[Sysname-srv6-te] srv6-policy ifit delay-measure enable

Related commands

ifit delay-measure enable

ifit enable (Network Management and Monitoring Command Reference)

ifit interval

service-type srv6-segment-list (Network Management and Monitoring Command Reference)

srv6-policy ifit interval

work-mode analyzer (Network Management and Monitoring Command Reference)

work-mode collector (Network Management and Monitoring Command Reference)

srv6-policy ifit interval

Use srv6-policy ifit interval to globally set the iFIT measurement interval for SRv6 TE policies.

Use undo srv6-policy ifit interval to restore the default.

Syntax

srv6-policy ifit interval time-value

undo srv6-policy ifit interval

Default

The global iFIT measurement interval is 30 seconds for SRv6 TE policies.

Views

SRv6 TE view

Predefined user roles

network-admin

Parameters

time-value: Specifies an iFIT measurement interval, in seconds. The value can be 1, 10, 30, 60, or 300.

Usage guidelines

Use this command only on the source node of an SRv6 TE policy.

1. Counts the number of packets forwarded through the SRv6 TE policy and the timestamps of the packets at measurement intervals.

2. Calculates the delay, jitter, and packet loss rate of the SRv6 TE policy at measurement intervals.

The egress node of the SRv6 TE policy obtains the measurement interval from iFIT packets and uses this interval to perform the following operations:

1. Counts the number of packets forwarded through the SRv6 TE policy and the timestamps of the packets at measurement intervals.

2. Provides feedback on the count and timestamps of packets to the source node of the SRv6 TE policy at measurement intervals.

If you execute both this command and the ifit interval command in SRv6 TE policy view, the ifit interval command in SRv6 TE policy view takes effect.

Examples

# Globally set the iFIT measurement interval to 60 seconds for SRv6 TE policies.

<Sysname> system-view

[Sysname] segment-routing ipv6

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

[Sysname-srv6-te] srv6-policy ifit interval 60

Related commands

ifit delay-measure

ifit interval

ifit loss-measure

srv6-policy ifit delay-measure enable

srv6-policy ifit loss-measure enable

Use srv6-policy ifit loss-measure enable to globally enable iFIT packet loss measurement for SRv6 TE policies.

Use undo srv6-policy ifit loss-measure enable to restore the default.

Syntax

srv6-policy ifit loss-measure enable

undo srv6-policy ifit loss-measure enable

Default

iFIT packet loss measurement is disabled globally for SRv6 TE policies.

Views

SRv6 TE view

Predefined user roles

network-admin

Usage guidelines

Prerequisites

For this command to take effect on an SRv6 TE policy, you must complete the following tasks:

· On the source node of the SRv6 TE policy, enable iFIT, configure the iFIT device ID, set the iFIT operating mode to analyzer, and execute the service-type srv6-segment-list command.

· On the egress node or transit nodes of the SRv6 TE policy, enable iFIT, set the iFIT operating mode to collector, and execute the service-type srv6-segment-list command.

Application scenarios

In-situ Flow Information Telemetry (iFIT) is a type of in-situ flow OAM measurement technology. This technology measures the actual packet loss, delay, and jitter of services in the network by directly encapsulating the measurement interval, packet loss flag, and delay flag information in the iFIT option field of service packets. For more information about iFIT, see Network Management and Monitoring Configuration Guide.

When the iFIT packet loss measurement feature is enabled for SRv6 TE policies, the device performs the following operations:

1. Measures the packet loss rate of an SRv6 TE policy through iFIT.

2. Compares the measured packet loss rate with the packet loss rate threshold defined in the IPR policy where the SRv6 TE policy is specified. The measured packet loss rate of the SRv6 TE policy is used as a condition for optimal SRv6 TE policy selection. If the measured packet loss rate crosses the packet loss rate threshold, it cannot be used as a traffic forwarding path.

Operating mechanism

1. The source node automatically creates an iFIT instance and assigns a flow ID to the iFIT instance.

2. As the data sender, the source node encapsulates the original packets with the DOH header that carries the iFIT option field and the SRH header when it forwards the packets through the SRv6 TE policy. In addition, the source node counts the number of packets forwarded through the SRv6 TE policy within an iFIT measurement interval.

5. The source node analyzes and calculates the packet loss rate for the packets forwarded through the SRv6 TE policy.

Restrictions and guidelines

iFIT can measure the packet loss rate of an SRv6 TE policy only when data traffic is being forwarded through that SRv6 TE policy.

If both the srv6-policy ifit loss-measure enable command in SRv6 TE view and the ifit loss-measure command in SRv6 TE policy view are used, the ifit loss-measure command takes effect.

If the egress node is not an H3C device, enable iFIT and set the iFIT operating mode to collector on the penultimate hop (an H3C device along the forwarding path). This H3C device will act as the data receiver to collect packet statistics, establish a UDP session with the source node, and provide the packet statistics back to the source node to fulfill the functions of the egress node.

If multiple nodes feed back measurement data to the source node, the source node handles the data as follows:

· If the egress node and multiple other nodes feed back measurement data to the source node, the source node prefers the data fed back from the egress node for calculating packet loss rate.

· If multiple non-egress nodes feed back measurement data to the source node, the source node prefers the data fed back from the node closest to the egress node for calculating packet loss rate.

Examples

# Globally enable iFIT packet loss measurement for SRv6 TE policies.

<Sysname> system-view

[Sysname] segment-routing ipv6

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

[Sysname-srv6-te] srv6-policy ifit loss-measure enable

Related commands

ifit enable (Network Management and Monitoring Command Reference)

ifit interval

ifit loss-measure enable

service-type srv6-segment-list (Network Management and Monitoring Command Reference)

srv6-policy ifit interval

work-mode analyzer (Network Management and Monitoring Command Reference)

work-mode collector (Network Management and Monitoring Command Reference)

srv6-policy ifit measure mode

Use srv6-policy ifit measure mode to globally specify an iFIT measurement mode for SRv6 TE policies.

Use undo srv6-policy ifit measure mode to restore the default.

Syntax

srv6-policy ifit measure mode { e2e | trace }

undo srv6-policy ifit measure mode

Default

The iFIT measurement mode is end-to-end mode for SRv6 TE policies.

Views

SRv6 TE view

Predefined user roles

network-admin

Parameters

e2e: Specifies the end-to-end mode. In this mode, only the egress node of an SRv6 TE policy feeds back iFIT measurement results to the source node for calculating the network quality of the SRv6 TE policy.

trace: Specifies the hop-by-hop mode. In this mode, a node along the forwarding path of a target flow feeds back measurement results to the source node of an SRv6 TE policy for calculating the network quality of the SRv6 TE policy as long as iFIT is enabled and iFIT packets are detected on that node.

Usage guidelines

Prerequisites

For this command to take effect on an SRv6 TE policy, you must complete the following tasks:

· On the source node of the SRv6 TE policy, enable iFIT, configure the iFIT device ID, set the iFIT operating mode to analyzer, and execute the service-type srv6-segment-list command.

· On the egress node or transit nodes of the SRv6 TE policy, enable iFIT, set the iFIT operating mode to collector, and execute the service-type srv6-segment-list command.

Recommended configuration

Operating mechanism

Restrictions and guidelines

If both the ifit measure mode command in SRv6 TE policy view and the srv6-policy ifit measure mode command in SRv6 TE view, the ifit measure mode command in SRv6 TE policy view takes effect.

Examples

# Globally set the iFIT measurement mode to hop-by-hop mode for SRv6 TE policies.

<Sysname> system-view

[Sysname] segment-routing ipv6

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

[Sysname-srv6-te] srv6-policy ifit measure mode trace

Related commands

ifit enable (Network Management and Monitoring Command Reference)

ifit measure mode

service-type srv6-segment-list (Network Management and Monitoring Command Reference)

work-mode analyzer (Network Management and Monitoring Command Reference)

work-mode collector (Network Management and Monitoring Command Reference)

srv6-policy locator

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

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

Syntax

srv6-policy locator locator-name

undo srv6-policy locator

Default

No locator is specified for SRv6 TE.

Views

SRv6 TE view

Predefined user roles

network-admin

Parameters

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

Usage guidelines

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

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

Examples

# Specify locator test1 in SRv6 TE view.

<Sysname> system-view

[Sysname] segment-routing ipv6

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

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

srv6-policy sbfd

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

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

Syntax

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

undo srv6-policy sbfd

Default

SBFD for all SRv6 TE policies is disabled.

Views

SRv6 TE view

Predefined user roles

network-admin

Parameters

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

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

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

Predefined user roles

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

Examples

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

<Sysname> system-view

[Sysname] segment-routing ipv6

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

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

Related commands

display segment-routing ipv6 te sbfd

sbfd

sbfd local-discriminator (High Availability Command Reference)

srv6-policy switch-delay delete-delay

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

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

Syntax

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

undo srv6-policy switch-delay

Default

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

Views

SRv6 TE view

Predefined user roles

network-admin

Parameters

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

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

Predefined user roles

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

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

Examples

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

<Sysname> system-view

[Sysname] segment-routing ipv6

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

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

switch-period

Use switch-period to set the switchover period between SRv6 TE policies in an IPR policy.

Use undo switch-period to restore the default.

Syntax

switch-period time-value

undo switch-period

Default

The switchover period between SRv6 TE policies is 6 seconds in an IPR policy.

Views

SRv6 TE IPR policy view

Predefined user roles

network-admin

Parameters

time-value: Specifies a switchover period in the range of 1 to 7200, in seconds.

Usage guidelines

If the source node of an SRv6 TE policy group calculates that the optimal SRv6 TE policy for a service differs from the one currently used by that service, and the path selection priority of the optimal SRv6 TE policy is lower than that of the currently used SRv6 TE policy, iFIT has detected that the packet loss, delay, or jitter of the currently used SRv6 TE policy does not meet the SLA requirements in the IPR policy. The traffic of that service needs to be switched over to the lower-priority SRv6 TE policy for forwarding. The device will then initiate a switchover delay timer, with the delay configured by using this command. Before the switchover delay timer times out, if the iFIT measurement result of the currently used SRv6 TE policy does not cross the SLA thresholds, the switchover delay timer will be reset. If the iFIT measurement result of the currently used SRv6 TE policy has crossed the SLA thresholds, the traffic of that service will be switched over to the optimal SRv6 TE policy calculated by IPR for forwarding after the switchover delay timer expires.

You can reasonably set the switchover delay based on the characteristics of services. For example, voice services require high real-time performance. When the network quality of SRv6 TE policy downgrades, voice services require timely switchover of forwarding paths to ensure the real-time performance of voice service traffic. In this case, a shorter switchover delay can be set to achieve rapid service switchover.

Examples

# Set the switchover period between SRv6 TE policies to 3 seconds in IPR policy ipr1.

<Sysname> system-view

[Sysname] segment-routing ipv6

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

[Sysname-srv6-te] intelligent-policy-route

[Sysname-srv6-ipr] ipr-policy ipr1

[Sysname-srv6-ipr-policy-ipr1] switch-period 3

traffic-engineering

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

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

Syntax

traffic-engineering

undo traffic-engineering

Default

The SRv6 TE view does not exist.

Views

SRv6 view

Predefined user roles

network-admin

Examples

# Create and enter the SRv6 TE view.

<Sysname> system-view

[Sysname] segment-routing ipv6

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

[Sysname-srv6-te]

ttl-mode

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

Use undo ttl-mode to restore the default.

Syntax

ttl-mode { pipe | uniform }

undo ttl-mode

Default

The TTL processing mode of SRv6 TE policies is pipe.

Views

SRv6 view

Predefined user roles

network-admin

Parameters

pipe: Specifies the pipe TTL processing mode.

uniform: Specifies the uniform TTL processing mode.

Predefined user roles

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

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

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

Examples

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

<Sysname> system-view

[Sysname] segment-routing ipv6

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

validation-check enable

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

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

Syntax

validation-check enable

undo validation-check enable

Default

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

Views

BGP IPv6 SR policy address family view

Predefined user roles

network-admin

Usage guidelines

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

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

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

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

Examples

# Enable validity check for BGP IPv6 SR policy routes.

<Sysname> system-view

[Sysname] bgp 100

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

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

wait-to-restore-period

Use wait-to-restore-period to set the WTR period in an IPR policy.

Use undo wait-to-restore-period to restore the default.

Syntax

wait-to-restore-period time-value

undo wait-to-restore-period

Default

The WTR period is 6 seconds in an IPR policy.

Views

SRv6 TE IPR policy view

Predefined user roles

network-admin

Parameters

time-value: Specifies a WTR period in the range of 1 to 259200, in seconds.

Usage guidelines

If the source node of an SRv6 TE policy group calculates that the optimal SRv6 TE policy for a service differs from the one currently used by that service, and the path selection priority of the optimal SRv6 TE policy is higher than that of the currently used SRv6 TE policy, iFIT has detected that the packet loss, delay, or jitter of the high-priority SRv6 TE policy has returned to a value that does not cross the corresponding SLA threshold. The traffic of that service needs to be switched back to the high-priority SRv6 TE policy for forwarding. At this point, the device will initiate a WTR delay timer, and the WTR delay is configured by using this command. Before the WTR delay timer times out, if the iFIT measurement result of the high-priority SRv6 TE policy crosses the SLA thresholds, the WTR delay timer will be reset. If the iFIT measurement result of this high-priority SRv6 TE policy consistently meets the SLA threshold requirements, the traffic of that service will be switched back to the optimal SRv6 TE policy calculated by IPR for forwarding after the WTR delay timer expires.

If you do not set the WTR period, the device immediately switches service traffic back to the high-priority SRv6 TE policy for forwarding. The switchback might result in packet loss or jitter due to link quality instability of the high-priority SRv6 TE policy.

Examples

# Set the WTR period to 30 seconds in IPR policy ipr1.

<Sysname> system-view

[Sysname] segment-routing ipv6

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

[Sysname-srv6-te] intelligent-policy-route

[Sysname-srv6-ipr] ipr-policy ipr1

[Sysname-srv6-ipr-policy-ipr1] wait-to-restore-period 30

20-Segment Routing Command Reference

SRv6 TE policy commands

address-family ipv6 sr-policy

Application scenarios

Operating mechanism

Restrictions and guidelines

Operating mechanism

Restrictions and guidelines

Application scenarios

Operating mechanism

Restrictions and guidelines

bfd srv6-encapsulation-mode insert

color match dscp (DSCP forward type view)

About this task

Operating mechanism

Restrictions and guidelines

color match dscp (SRv6 TE policy group view)

About this task

Operating mechanism

Restrictions and guidelines

default match (TE class ID-based traffic steering)

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

default-color (VPN instance IPv4/IPv6 address family view)

display bgp routing-table ipv6 sr-policy

display segment-routing ipv6 te policy-group statistics

display segment-routing ipv6 te segment-list

Application scenarios

Operating mechanism

Recommended configuration

Restrictions and guidelines

Operating mechanism

Restrictions and guidelines

forward-type (SRv6 TE ODN policy group view)

forward-type (SRv6 TE Policy group view)

Prerequisites

Application scenarios

Operating mechanism

Restrictions and guidelines

Prerequisites

Application scenarios

Operating mechanism

Restrictions and guidelines

Prerequisites

Recommended configuration

Operating mechanism

Restrictions and guidelines

Prerequisites

Application scenarios

Operating mechanism

Restrictions and guidelines

Application scenarios

Operating mechanism

Restrictions and guidelines

Operating mechanism

Restrictions and guidelines

Application scenarios

Operating mechanism

Restrictions and guidelines

Operating mechanism

Restrictions and guidelines

Operating mechanism

Restrictions and guidelines

Operating mechanism

Restrictions and guidelines