Login
- Table of Contents
- Related Documents
-
| Title | Size | Download |
|---|---|---|
| 02-SRv6 TE policy commands | 1.50 MB |
affinity (SRv6 TE ODN dynamic view)
affinity (SRv6 TE policy constraints view)
best-effort match service-class (service class forward type view)
best-effort match service-class (SRv6 TE policy group view)
binding-sid (SRv6 TE policy group view)
binding-sid (SRv6 TE policy view)
color match dscp (DSCP forward type view)
color match dscp (SRv6 TE policy group view)
color match service-class (service class forward type view)
color match service-class (SRv6 TE policy group view)
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 evpn srv6 mirror remote-sid
display pce segment-routing ipv6 policy database
display pce segment-routing ipv6 policy initiate-cache
display segment-routing ipv6 te database
display segment-routing ipv6 te bfd
display segment-routing ipv6 te forwarding
display segment-routing ipv6 te forwarding traffic-statistics
display segment-routing ipv6 te policy
display segment-routing ipv6 te policy ifit
display segment-routing ipv6 te policy last-down-reason
display segment-routing ipv6 te policy statistics
display segment-routing ipv6 te policy status
display segment-routing ipv6 te policy-group
display segment-routing ipv6 te policy-group last-down-reason
display segment-routing ipv6 te policy-group statistics
display segment-routing ipv6 te sbfd
display segment-routing ipv6 te segment-list
display segment-routing ipv6 te source-sid
display segment-routing ipv6 te ipr
dynamic (SRv6 TE policy path preference view)
encapsulation-mode encaps include local-end.x
encapsulation-mode insert include local-end.x
fast-reroute mirror delete-delay
forward-type (SRv6 TE ODN policy group view)
forward-type (SRv6 TE policy group view)
mirror remote-sid delete-delay
pce capability segment-routing ipv6
pce passive-delegate report-only
pcep (SRv6 TE policy path preference dynamic view)
pcep (SRv6-TE-ODN dynamic view)
reset segment-routing ipv6 te forwarding statistics
snmp-agent trap enable srv6-policy
srv6-policy backup hot-standby enable
srv6-policy bfd first-fail-timer
srv6-policy bfd trigger path-down enable
srv6-policy calc-schedule-interval
srv6-policy drop-upon-invalid enable
srv6-policy encapsulation-mode
srv6-policy encapsulation-mode encaps include local-end.x
srv6-policy encapsulation-mode insert include local-end.x
srv6-policy forwarding ignore-last-sid
srv6-policy forwarding statistics enable
srv6-policy forwarding statistics interval
srv6-policy ifit delay-measure enable
srv6-policy ifit loss-measure enable
srv6-policy immediate-reoptimization
srv6-policy path verification enable
srv6-policy pce delegation enable
srv6-policy pce passive-delegate report-only enable
srv6-policy suppress-flapping disable
srv6-policy switch-delay delete-delay
SRv6 TE policy commands
address-family ipv6 sr-policy
Use address-family ipv6 sr-policy to create the BGP IPv6 SR policy address family and enter its view, or enter the view of the existing BGP IPv6 SR policy address family.
Use undo address-family ipv6 sr-policy to delete the BGP IPv6 SR policy address family and all the configuration in the BGP IPv6 SR policy address family.
Syntax
address-family ipv6 sr-policy
undo address-family ipv6 sr-policy
Default
The BGP IPv6 SR policy address family does not exist.
Views
BGP instance view
Predefined user roles
network-admin
Usage guidelines
The configuration in BGP IPv6 SR policy address family view applies only to routes and peers in the BGP IPv6 SR policy address family.
Examples
# In BGP instance view, create the BGP IPv6 SR policy address family and enter its view.
<Sysname> system-view
[Sysname] bgp 100
[Sysname-bgp-default] address-family ipv6 sr-policy
[Sysname-bgp-default-srpolicy-ipv6]
advertise ebgp enable
Use advertise ebgp enable to enable advertising BGP IPv6 SR policy routes to EBGP peers.
Use undo advertise ebgp enable to restore the default.
Syntax
advertise ebgp enable
undo advertise ebgp enable
Default
BGP IPv6 SR policy routes are not advertised to EBGP peers.
Views
BGP IPv6 SR policy address family view
Predefined user roles
network-admin
Usage guidelines
By default, BGP IPv6 SR policy routes are advertised among IBGP peers. To advertise BGP IPv6 SR policy routes to EBGP peers, you must execute this command to enable the advertisement capability.
Examples
# Enable advertising BGP IPv6 SR policy routes to EBGP peers.
<Sysname> system-view
[Sysname] bgp 100
[Sysname-bgp-default] address ipv6 sr-policy
[Sysname-bgp-default-srpolicy-ipv6] advertise ebgp enable
affinity (SRv6 TE ODN dynamic view)
Use affinity to create the affinity attribute rule and enter its view, or enter the view of the existing affinity attribute rule.
Use undo affinity to delete the affinity attribute rule view and all the configurations in the view.
Syntax
affinity { include-all | include-any | exclude-any }
undo affinity { include-all | include-any | exclude-any }
Default
The affinity attribute rule is not created for an SRv6 TE policy.
Views
SRv6 TE ODN dynamic view
Predefined user roles
network-admin
Parameters
include-all: Uses the links that include all specific affinity attributes.
include-any: Uses the links that include any specific affinity attribute.
exclude-any: Uses the links that do not include any specific affinity attribute.
Examples
# Create the include-all affinity attribute rule and enter affinity attribute rule view.
<Sysname> system-view
[Sysname] segment-routing ipv6
[Sysname-segment-routing-ipv6] traffic-engineering
[Sysname-srv6-te] on-demand color 1
[Sysname-srv6-te-odn-1] dynamic
[Sysname-srv6-te-odn-1-dynamic] affinity include-all
[Sysname-srv6-te-odn-1-dynamic-aff-include-all]
affinity (SRv6 TE policy constraints view)
Use affinity to create and enter the affinity attribute view, or enter the existing affinity attribute view.
Use undo affinity to delete the affinity attribute view and all the configurations in the view.
Syntax
affinity
undo affinity
Default
The affinity attribute is not created for an SRv6 TE policy.
Views
Constraints view
Predefined user roles
network-admin
Examples
# Enter affinity attribute view.
<Sysname> system-view
[Sysname] segment-routing-ipv6
[Sysname-segment-routing-ipv6] traffic-engineering
[Sysname-srv6-te] policy a1
[Sysname-srv6-te-policy-a1] candidate-paths
[Sysname-srv6-te-policy-a1-path] preference 200
[Sysname-srv6-te-policy-a1-path-pref-200] constraints
[Sysname-srv6-te-policy-a1-path-pref-200-const] affinity
[Sysname-srv6-te-policy-a1-path-pref-200-const-aff]
affinity-map
Use affinity-map to create the constraints mapping and enter its view, or enter the view of the existing constraints mapping.
Use undo affinity-map to delete the constraints mapping view and all the configurations in the view.
Syntax
affinity-map
undo affinity-map
Default
No constraints mapping exists.
Views
SRv6 TE view
Predefined user roles
network-admin
Examples
# Create the constraints mapping and enter its view
<Sysname> system-view
[Sysname] segment-routing ipv6
[Sysname-segment-routing-ipv6] traffic-engineering
[Sysname-srv6-te] affinity-map
[Sysname-srv6-te-affinity-map]
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
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
When the hot standby feature is enabled, the candidate path with the greatest preference value in the SRv6 TE policy is the main path and that with the second greatest preference value is the backup path. When all SID lists of the main path fail, the backup path immediately takes over to minimize service interruption.
You can enable hot standby for all SRv6 TE policies globally in SRv6 TE view or for a specific SRv6 TE policy in SRv6 TE policy view. The policy-specific configuration takes precedence over the global configuration. An SRv6 TE policy uses the global configuration only when it has no policy-specific configuration.
Examples
# Enable hot standby for SRv6 TE policy 1.
<Sysname> system-view
[Sysname] segment-routing ipv6
[Sysname-segment-routing-ipv6] traffic-engineering
[Sysname-srv6-te] policy 1
[Sysname-srv6-te-policy-1] backup hot-standby enable
Related commands
srv6-policy backup hot-standby enable
bestroute encap-type
Use bestroute encap-type to specify the packet encapsulation type preferred in optimal route selection.
Use undo bestroute encap-type to restore the default.
Syntax
bestroute encap-type { mpls | srv6 } [ preferred ]
undo bestroute encap-type
Default
The device does not select optimal routes according to the packet encapsulation type.
Views
BGP-VPN instance view.
Predefined user roles
network-admin
Parameters
mpls: Prefers to use MPLS-encapsulated routes during optimal route selection.
srv6: Prefers to use SRv6-encapsulated routes during optimal route selection.
preferred: With this keyword specified, the optimal route selection rule configured by this command is used after the rule of preferring the route with the highest Preferred-value and before the rule of preferring the route with the highest LOCAL_PREF value. If you do not specify this keyword, the rule configured by this command is used after the rule of preferring the route with the highest LOCAL_PREF value and before the rule of selecting a route in descending order of route generated by the network command, route redistributed by the import-route command, and aggregate route.
Usage guidelines
If you configure both the bestroute encap-type preferred command and the bestroute nexthop-type preferred command, BGP selects the optimal route in the VPN instance by using the following procedure:
1. Drops the route with an unreachable NEXT_HOP.
2. Selects the route with the highest Preferred-value.
3. Uses the optimal route selection rule configured by the bestroute encap-type command: prefers to use an MPLS-encapsulated or SRv6-encapsulated route.
4. Uses the optimal route selection rule configured by the bestroute nexthop-type command: prefers to use a route whose next hop is an IP address or a tunnel.
5. Selects the route with the highest LOCAL_PREF.
6. Proceeds with the subsequent steps in the original BGP route select procedure.
For more information about BGP route selection, see BGP overview in Layer 3—IP Routing Configuration Guide.
If you execute this command multiple times, the most recent configuration takes effect.
Examples
# Configure BGP to prefer SRv6-encapsulated routes during optimal route selection.
<Sysname> system-view
[Sysname] bgp 100
[Sysname-bgp-default] ip vpn-instance vpn1
[Sysname-bgp-default-vpn1] bestroute encap-type srv6
Related commands
bestroute nexthop-type (Layer 3—IP Routing Command Reference)
best-effort match service-class (service class forward type view)
Use best-effort match service-class to specify service class values with which traffic will be forwarded in SRv6 BE mode in an SRv6 TE policy group ODN template.
Use undo best-effort match service-class to remove the service class values specified for forwarding traffic in SRv6 BE mode in an SRv6 TE policy group ODN template.
Syntax
best-effort match service-class service-class-value-list
undo best-effort match service-class service-class-value-list
best-effort match service-class default
undo best-effort match service-class [ default ]
Default
No service class values are specified for the device to forward traffic in SRv6 BE mode in an SRv6 TE policy group ODN template.
Views
Service class forward type view
Predefined user roles
network-admin
Parameters
service-class-value-list: Specifies a space-separated list of up to eight service class value items. Each item specifies a service class value or a range of service class values in the form of service-class-value1 to service-class-value2. The value range for service class values is 0 to 15.The value for the service-class-value2 argument must be greater than or equal to the value for the service-class-value1 argument.
default: Forwards packets that do not match any SRv6 BE-to-service class mapping in SRv6 BE mode.
Usage guidelines
About this command
Use this command to configure traffic with the specified service class values to be forwarded in SRv6 BE mode after the traffic is steered to an SRv6 TE policy group for forwarding. When the device forwards packets in SRv6 BE mode, it encapsulates the original packets with a new IPv6 header. The destination address in the new IPv6 header is the VPN SID assigned to public or private network routes by the egress node of the SRv6 TE policy group. Then, the device performs an IPv6 routing table lookup to forward the encapsulated packets. If the VPN SID is unreachable, the SRv6 BE mode is invalid.
The service class is a type of local ID on the device. You can use the remark service-class command to mark the service class of traffic. For more information about the remark service-class command, see QoS commands in ACL and QoS Command Reference.
Operating mechanism
When service class-based traffic steering is used, the device uses the following process to forward a packet:
1. Matches the service class value in the packet with the mappings configured by using the color match service-class and best-effort match service-class commands. If a match is found, the device uses the matching SRv6 TE policy to forward the packet or forwards the packet in SRv6 BE mode.
2. Uses the default SRv6 TE policy specified by using the color match service-class default command to forward the packet in the following situations:
¡ The service class value in the packet does not match an SRv6 TE policy or the SRv6 BE mode.
¡ The service class value in the packet matches an SRv6 TE policy or the SRv6 BE mode. However, the matching SRv6 TE policy or the SRv6 BE mode is invalid.
3. Forwards the packet in SRv6 BE mode if both of the following requirements are met:
¡ No default SRv6 TE policy is specified by using the color match service-class default command, or the default SRv6 TE policy is invalid.
¡ The best-effort match service-class default command is used and the SRv6 BE mode is valid.
4. Handles the packet according to whether the drop-upon-mismatch enable command is used if the best-effort match service-class default command is not used or the SRv6 BE path is invalid.
¡ 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 uses the SRv6 TE policy mapped to the smallest service class value to forward the packet in case that the SRv6 TE policy is valid.
5. The device performs an IPv6 routing table lookup to forward the packet if the packet does not meet any of the previous conditions.
Restrictions and guidelines
For an SRv6 TE policy group, a service class value can be mapped only to the SRv6 BE mode or to one SRv6 TE policy.
Examples
# In SRv6 TE policy group ODN template, steer packets with service class 5 to the 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] forward-type service-class
[Sysname-srv6-te-odn-group-1-service-class] best-effort match service-class 6
Related commands
color match service-class (service class forward type view)
drop-upon-mismatch enable
forward-type (SRv6 TE ODN policy group view)
best-effort match service-class (SRv6 TE policy group view)
Use best-effort match service-class to specify service class values with which traffic will be forwarded in SRv6 BE mode.
Use undo best-effort match service-class to remove the service class values specified for forwarding traffic in SRv6 BE mode.
Syntax
best-effort match service-class service-class-value-list
undo best-effort match service-class service-class-value-list
best-effort match service-class default
undo best-effort match service-class [ default ]
Default
No service class values are specified for the device to forward traffic in SRv6 BE mode.
Views
SRv6 TE policy group view
Predefined user roles
network-admin
Parameters
service-class-value-list: Specifies a space-separated list of up to eight service class value items. Each item specifies a service class value or a range of service class values in the form of service-class-value1 to service-class-value2. The value range for service class values is 0 to 15.The value for the service-class-value2 argument must be greater than or equal to the value for the service-class-value1 argument.
default: Forwards packets that do not match any SRv6 BE-to-service class mapping in SRv6 BE mode.
Usage guidelines
Prerequisites
Execute the forward-type service-class command before using this command.
About this command
Use this command to configure traffic with the specified service class values to be forwarded in SRv6 BE mode after the traffic is steered to an SRv6 TE policy group for forwarding. When the device forwards packets in SRv6 BE mode, it encapsulates the original packets with a new IPv6 header. The destination address in the new IPv6 header is the VPN SID assigned to public or private network routes by the egress node of the SRv6 TE policy group. Then, the device performs an IPv6 routing table lookup to forward the encapsulated packets. If the VPN SID is unreachable, the SRv6 BE mode is invalid.
The service class is a type of local ID on the device. You can use the remark service-class command to mark the service class of traffic. For more information about the remark service-class command, see QoS commands in ACL and QoS Command Reference.
Operating mechanism
When service class-based traffic steering is used, the device uses the following process to forward a packet:
1. Matches the service class value in the packet with the mappings configured by using the color match service-class and best-effort match service-class commands. If a match is found, the device uses the matching SRv6 TE policy to forward the packet or forwards the packet in SRv6 BE mode.
2. Uses the default SRv6 TE policy specified by using the color match service-class default command to forward the packet in the following situations:
¡ The service class value in the packet does not match an SRv6 TE policy or the SRv6 BE mode.
¡ The service class value in the packet matches an SRv6 TE policy or the SRv6 BE mode. However, the matching SRv6 TE policy or the SRv6 BE mode is invalid.
3. Forwards the packet in SRv6 BE mode if both of the following requirements are met:
¡ No default SRv6 TE policy is specified by using the color match service-class default command, or the default SRv6 TE policy is invalid.
¡ The best-effort match service-class default command is used and the SRv6 BE mode is valid.
4. Handles the packet according to whether the drop-upon-mismatch enable command is used if the best-effort match service-class default command is not used or the SRv6 BE path is invalid.
¡ 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 uses the SRv6 TE policy mapped to the smallest service class value to forward the packet in case that the SRv6 TE policy is valid.
5. The device performs an IPv6 routing table lookup to forward the packet if the packet does not meet any of the previous conditions.
Restrictions and guidelines
For an SRv6 TE policy group, a service class value can be mapped only to the SRv6 BE mode or to one SRv6 TE policy.
Examples
# In SRv6 TE policy group, steer packets with service class 5 to the 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] forward-type service-class
[Sysname-srv6-te-policy-group-10] best-effort match service-class 5
Related commands
color match service-class (SRv6 TE policy group view)
drop-upon-mismatch enable
forward-type (SRv6 TE policy group view)
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, set the OAM SID to the End SID of the destination node.
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 must 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. The destination IPv6 address in the new IPv6 header is the first IPv6 address in the SID list of the SRv6 TE policy. The source IPv6 address is the IPv6 address specified using the encapsulation source-address command in SRv6 view.
· 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 destination IPv6 address in the original IPv6 header changes to the first IPv6 address in the SID list of the SRv6 TE policy. The source IPv6 address in the original BFD echo packet does not change.
If you do not specify the encaps or insert keyword, the encapsulation mode configured by the bfd srv6-encapsulation-mode encap command applies.
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 echo 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.
If you do not specify the source-ipv6 ipv6-address option in this command for an SRv6 TE policy, you must enable the echo packet mode BFD globally in SRv6 TE view. Otherwise, the device cannot establish a BFD session for the SRv6 TE policy.
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.
Before you execute this command, execute the bfd echo-source-ipv6 command on the local device to specify the source IPv6 address for echo packets.
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 encaps (High Availability Command Reference)
bfd echo-source-ipv6 (High Availability Command Reference)
display segment-routing ipv6 te bfd
srv6-policy bfd echo
bfd srv6-encapsulation-mode
Use bfd srv6-encapsulation-mode encap to configure the encapsulation mode for the BFD or SBFD packets used for SRv6 forwarding paths connectivity detection.
Use undo bfd srv6-encapsulation-mode to restore the default.
Syntax
bfd srv6-encapsulation-mode insert [ no-endpoint ]
undo bfd srv6-encapsulation-mode insert [ no-endpoint ]
Default
The Encap mode is used to encapsulate BFD or SBFD packets. A new IPv6 header and an SRH are added to the original packets. The SRH contains the SID list of an SRv6 TE policy. If the length of the SID list is 0, no SRH is added to the original packets.
Views
System view
Predefined user roles
network-admin
Parameters
insert: Encapsulates BFD or SBFD packets in Insert mode.
no-endpoint: Encapsulates SBFD packets in Insert no-endpoint mode. In this mode, the SID list inserted into the SRH does not contain the endpoint in an SRv6 TE policy. If you do not specify this keyword, SBFD packets are encapsulated in Insert with endpoint mode. This keyword takes effect only on SBFD packets encapsulated in Insert mode.
Usage guidelines
To use echo BFD to detect the connectivity of 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:
· Insert—Insertion mode. It inserts an SRH between the basic IPv6 header and the BFD packet. The SRH contains the SID list of the SRv6 TE policy. If the SID list length is 0, no SRH will be inserted.
· Encap—Normal encapsulation mode. It adds a new IPv6 header and an SRH to the original packets. The SRH contains the SID list of the SRv6 TE policy. If the SID list length is 0, no SRH will be inserted.
To use SBFD to detect the connectivity of an SRv6 TE policy, the device must encapsulate the SID list of the SRv6 TE policy for the SBFD packets. The following encapsulation modes are available:
· Insert with endpoint—This mode inserts an SRH between the basic IPv6 header and the SBFD packet. The SRH contains the SID list and endpoint of the SRv6 TE policy.
· Insert no-endpoint—This mode inserts an SRH between the basic IPv6 header and the SBFD packet. The SRH contains the SID list but not the endpoint of the SRv6 TE policy.
· Encap—Normal encapsulation mode. It adds a new IPv6 header and an SRH to the original packets. The SRH contains the SID list of the SRv6 TE policy. If the SID list length is 0, no SRH will be 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 for SBFD for the SRv6 TE policy and then enable BFD for SBFD for the SRv6 TE policy.
Examples
# Configure the device to use the Encap mode to encapsulate the BFD or SBFD packets for SRv6 forwarding paths connectivity detection.
<Sysname> system-view
[Sysname] bfd srv6-encapsulation-mode encap
Related commands
bfd echo
sbfd
bfd trigger path-down
Use bfd trigger path-down to enable BFD session down events to trigger SRv6 TE policy path switchover.
Use undo bfd trigger path-down to disable BFD session down events from triggering SRv6 TE policy path switchover.
Syntax
bfd trigger path-down { disable | enable }
undo bfd trigger path-down
Default
The feature for triggering SRv6 TE policy path switchover by BFD session down events is not configured. The configuration in SRv6 TE view applies.
Views
SRv6 TE policy view
Predefined user roles
network-admin
Parameters
disable: Disables BFD session down events from triggering SRv6 TE policy path switchover.
enable: Enables BFD session down events to trigger SRv6 TE policy path switchover.
Usage guidelines
By default, when the SRv6 TE policy has multiple valid candidate paths, the following conditions exist:
· If the hot standby feature is disabled, BFD or SBFD detects all SID lists for only the optimal valid candidate path of the SRv6 TE policy. The device establishes a BFD or SBFD session for each SID list. When all BFD or SBFD sessions go down, the SRv6 TE policy will not select other valid candidate paths, and the device will not forward packets through the SRv6 TE policy.
· If the hot standby feature is enabled, BFD or SBFD detects all SID lists for the primary and backup paths of the SRv6 TE policy. The device establishes a BFD or SBFD session for each SID list.
¡ If all BFD or SBFD sessions for the primary path go down, the SRv6 TE policy will use the backup path to forward packets without reselecting other valid candidate paths.
¡ If all BFD or SBFD sessions for the primary and backup paths go down, the SRv6 TE policy will not select other valid candidate paths, and the device will not forward packets through the SRv6 TE policy.
If you enable BFD session down events to trigger SRv6 TE policy path switchover, the following conditions exist when the SRv6 TE policy has multiple valid candidate paths:
· If the hot standby feature is disabled, BFD or SBFD detects all SID lists for only the optimal valid candidate path of the SRv6 TE policy. The device establishes a BFD or SBFD session for each SID list. When all BFD or SBFD sessions go down, the SRv6 TE policy will reselect other valid candidate paths for packet forwarding. If no valid candidate paths are available for the SRv6 TE policy, the device cannot forward packets through the SRv6 TE policy.
· If the hot standby feature is enabled, BFD or SBFD detects all SID lists for the primary and backup paths of the SRv6 TE policy. The device establishes a BFD or SBFD session for each SID list.
¡ If all BFD or SBFD sessions for the primary path go down, the SRv6 TE policy will use the backup path to forward packets, and reselect the primary and backup paths.
¡ If all BFD or SBFD sessions for the primary and backup paths go down, the SRv6 TE policy will reselect other valid candidate paths as the primary and backup paths. The device will forward packets through the new primary path of the SRv6 TE policy.
· During optimal path reselection, if no valid candidate paths are available for the SRv6 TE policy, the device cannot forward packets through the SRv6 TE policy.
Before you enable this feature for an SRv6 TE policy, create a BFD or SBFD session for the policy first.
You can configure BFD session down events to trigger SRv6 TE policy path switchover 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 BFD session down events to trigger path switchover for SRv6 TE policy a1.
<Sysname> system-view
[Sysname] segment-routing ipv6
[Sysname-segment-routing-ipv6] traffic-engineering
[Sysname-srv6-te] policy a1
[Sysname-srv6-te-policy-a1] bfd trigger path-down enable
Related commands
bfd echo
sbfd
srv6-policy bfd echo
srv6-policy 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 does not cross the specified CMI threshold.
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 dot1p
Use color match dot1p to create color-to-802.1p mappings for an SRv6 TE policy group.
Use undo color match dot1p to delete color-to-802.1p mappings for an SRv6 TE policy group.
Syntax
color color-value match dot1p dot1p-value-list
undo color color-value match dot1p dot1p-value-list
color color-value match dot1p default
undo color color-value match dot1p [ default ]
Default
No color-to-802.1p mappings are created for an SRv6 TE policy group.
Views
SRv6 TE policy group view
Predefined user roles
network-admin
Parameters
color-value: Specifies the color attribute value of an SRv6 TE policy, in the range of 0 to 4294967295.
dot1p-value-list: Specifies a space-separated list of up to four 802.1p value items. Each item specifies an 802.1p value in the range of 0 to 7 or a range of 802.1p values in the form of dot1p-value1 to dot1p-value2. The value for the dot1p-value2 argument must be greater than or equal to the value for the dot1p-value1 argument.
default: Configures a default color-to-802.1p mapping. Packets that do not match any color-to-802.1p mappings are steered to the default SRv6 TE policy (the policy specified in the default mapping).
Usage guidelines
To use this command, you must first use the forward-type dot1p command.
Use this command to create color-to-802.1p mappings for 802.1p-based traffic steering.
You can map the color values of only valid SRv6 TE policies to 802.1p values. For an SRv6 TE policy group, an 802.1p value can be mapped to only one color value.
Use the color match dot1p default command to specify the default SRv6 TE policy for an SRv6 TE policy group. If no SRv6 TE policy in an SRv6 TE policy group matches a specific 802.1p value, the default SRv6 TE policy is used to forward packets containing the 802.1p value. Only one default SRv6 TE policy can be specified for an SRv6 TE policy group.
When the device receives a packet that does not match any color-to-802.1p mapping, the device uses the following procedure to forward the packet:
1. Uses the default SRv6 TE policy to forward the packet if the default SRv6 TE policy is valid.
2. 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, the device uses the SRv6 TE policy mapped to the smallest 802.1p value to forward the packet in case that the SRv6 TE policy is valid.
3. The device performs an IPv6 routing table lookup to forward the packet if the packet does not meet any of the previous conditions.
Examples
# In SRv6 TE policy group 1, map 802.1p value 3 to color value 20, so that packets with a matching 802.1p value are steered to the associated SRv6 TE policy.
<Sysname> system-view
[Sysname] segment-routing ipv6
[Sysname-segment-routing-ipv6] traffic-engineering
[Sysname-srv6-te] policy-group 1
[Sysname-srv6-te-policy-group-1] forward-type dot1p
[Sysname-srv6-te-policy-group-1] color 20 match dot1p 3
Related commands
forward-type dot1p
color match dscp (DSCP forward type view)
Use color match dscp to create color-to-DSCP mappings for the SRv6 TE policy group ODN template.
Use undo color match dscp to delete color-to-DSCP mappings from the SRv6 TE policy group ODN template.
Syntax
color color-value match dscp { ipv4 | ipv6 } dscp-value-list
undo color color-value match dscp { ipv4 | ipv6 } 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 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 default SRv6 TE policy (the policy specified in the default mapping).
Usage guidelines
After creating an SRv6 TE policy group through the ODN template, you can configure this command to implement DSCP-based traffic steering.
You can map the color values of only valid SRv6 TE policies to DSCP values.
You can configure color-to-DSCP mappings separately for the IPv4 address family and IPv6 address family. For a specific address family, a DSCP value can be mapped to only one color value.
Use the color match dscp default command to specify the default SRv6 TE policy for an address family. If no SRv6 TE policy in an SRv6 TE policy group matches a specific DSCP value, the default SRv6 TE policy is used to forward packets containing the DSCP value. Only one default SRv6 TE policy can be specified for an address family.
When the device receives an IPv4 or IPv6 packet that does not match any color-to-DSCP mapping, the device selects a valid SRv6 TE policy for the packet in the following order:
1. The default SRv6 TE policy specified for the same address family as the packet.
2. The default SRv6 TE policy specified for the other address family.
3. 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 but color-to-DSCP mappings are configured in the same address family as the packet, the device searches for the color-to-DSCP mapping with the smallest DSCP value that is mapped to a valid SRv6 TE policy. The device will use that SRv6 TE policy to forward the packet.
¡ If the drop-upon-mismatch enable command is not used but color-to-DSCP mappings are configured in the other address family, the device searches for the color-to-DSCP mapping with the smallest DSCP value that is mapped to a valid SRv6 TE policy. The device will use that SRv6 TE policy to forward the packet.
4. The device performs an IPv6 routing table lookup to forward the packet that does not match any of the previous SRv6 TE policies.
Examples
# For the SRv6 TE policy group ODN template, map DSCP value 30 to color value 20 for IPv4 packets, so that IPv4 packets with DSCP value 30 are steered to the SRv6 TE policy with color value 20.
<Sysname> system-view
[Sysname] segment-routing ipv6
[Sysname-segment-routing-ipv6] traffic-engineering
[Sysname-srv6-te] on-demand-group color 1
[Sysname-srv6-te-odn-group-1] forward-type dscp
[Sysname-srv6-te-odn-group-1-dscp] color 20 match dscp ipv4 30
color match dscp (SRv6 TE policy group view)
Use color match dscp to create color-to-DSCP mappings for an SRv6 TE policy group.
Use undo color match dscp to delete color-to-DSCP mappings for the SRv6 TE policy group.
Syntax
color color-value match dscp { ipv4 | ipv6 } dscp-value-list
undo color color-value match dscp { ipv4 | ipv6 } dscp-value-list
color color-value match dscp { ipv4 | ipv6 } default
undo color color-value match dscp { ipv4 | ipv6 } [ default ]
Default
No color-to-DSCP mappings are created for an SRv6 TE policy group.
Views
SRv6 TE policy group view
Predefined user roles
network-admin
Parameters
color-value: Specifies the color attribute value of an SRv6 TE policy, in the range of 0 to 4294967295.
ipv4: Specifies DSCP values of IPv4 packets.
ipv6: Specifies DSCP values of IPv6 packets.
dscp-value-list: Specifies a space-separated list of up to 32 DSCP value items. Each item specifies a DSCP value in the range of 0 to 63 or a range of DSCP values in the form of dscp-value1 to dscp-value2. The value for the dscp-value2 argument must be greater than or equal to the value for the dscp-value1 argument.
default: Configures a default color-to-DSCP mapping. Packets that do not match any mappings are steered to the default SRv6 TE policy (the policy specified in the default mapping). If you do not specify this keyword for the undo color match dscp command, the command deletes all color-to-DSCP mappings for the current SRv6 TE policy group.
Usage guidelines
You can map the color values of only valid SRv6 TE policies to DSCP values.
You can configure color-to-DSCP mappings separately for the IPv4 address family and IPv6 address family. For a specific address family, a DSCP value can be mapped to only one color value.
Use the color match dscp default command to specify the default SRv6 TE policy for an address family. If no SRv6 TE policy in an SRv6 TE policy group matches a specific DSCP value, the default SRv6 TE policy is used to forward packets containing the DSCP value. Only one default SRv6 TE policy can be specified for an address family.
When the device receives an IPv4 or IPv6 packet that does not match any color-to-DSCP mapping, the device selects a valid SRv6 TE policy for the packet in the following order:
1. The default SRv6 TE policy specified for the same address family as the packet.
2. The default SRv6 TE policy specified for the other address family.
3. 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 but color-to-DSCP mappings are configured in the same address family as the packet, the device searches for the color-to-DSCP mapping with the smallest DSCP value that is mapped to a valid SRv6 TE policy. The device will use that SRv6 TE policy to forward the packet.
¡ If the drop-upon-mismatch enable command is not used but color-to-DSCP mappings are configured in the other address family, the device searches for the color-to-DSCP mapping with the smallest DSCP value that is mapped to a valid SRv6 TE policy. The device will use that SRv6 TE policy to forward the packet.
4. The device performs an IPv6 routing table lookup to forward the packet that does not match any of the previous SRv6 TE policies.
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
color match service-class (service class forward type view)
Use color match service-class to create color-to-service class mappings for an SRv6 TE policy group ODN template.
Use undo color match service-class to delete color-to-service class mappings from an SRv6 TE policy group ODN template.
Syntax
color color-value match service-class service-class-value-list
undo color color-value match service-class service-class-value-list
color color-value match service-class default
undo color color-value match service-class [ default ]
Default
No color-to-service class mappings are created for an SRv6 TE policy group ODN template.
Views
Service class 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.
service-class-value-list: Specifies a space-separated list of up to eight service class value items. Each item specifies a service class value or a range of service class values in the form of service-class-value1 to service-class-value2. The value range for service class values is 0 to 15.The value for the service-class-value2 argument must be greater than or equal to the value for the service-class-value1 argument.
default: Configures a default color-to-service class mapping. Packets that do not match any color-to-service class mappings are steered to the default SRv6 TE policy (the policy with the color attribute value specified in the default mapping).
Usage guidelines
About this command
After traffic is steered to an SRv6 TE policy group for forwarding, the device matches the service class value of the traffic with the color-to-service class mappings specified by using this command. If a matching mapping is found, the device forwards the traffic through the SRv6 TE policy with the color attribute value mapped to the service class value.
Operating mechanism
When service class-based traffic steering is used, the device uses the following process to forward a packet:
1. Matches the service class value in the packet with the mappings configured by using the color match service-class and best-effort match service-class commands. If a match is found, the device uses the matching SRv6 TE policy to forward the packet or forwards the packet in SRv6 BE mode.
2. Uses the default SRv6 TE policy specified by using the color match service-class default command to forward the packet in the following situations:
¡ The service class value in the packet does not match an SRv6 TE policy or the SRv6 BE mode.
¡ The service class value in the packet matches an SRv6 TE policy or the SRv6 BE mode. However, the matching SRv6 TE policy or the SRv6 BE mode is invalid.
3. Forwards the packet in SRv6 BE mode if both of the following requirements are met:
¡ No default SRv6 TE policy is specified by using the color match service-class default command, or the default SRv6 TE policy is invalid.
¡ The best-effort match service-class default command is used and the SRv6 BE mode is valid.
4. Handles the packet according to whether the drop-upon-mismatch enable command is used if the best-effort match service-class default command is not used or the SRv6 BE path is invalid.
¡ 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 uses the SRv6 TE policy mapped to the smallest service class value to forward the packet in case that the SRv6 TE policy is valid.
5. The device performs an IPv6 routing table lookup to forward the packet if the packet does not meet any of the previous conditions.
Restrictions and guidelines
Only one default SRv6 TE policy can be specified for an SRv6 TE policy group.
For an SRv6 TE policy group, a service class value can be mapped only to the SRv6 BE mode or to one SRv6 TE policy.
Examples
# In SRv6 TE policy group ODN template, map service class value 3 to color value 20 for packets, so that packets with service class value 3 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 service-class
[Sysname-srv6-te-odn-group-1-service-class] color 20 match service-class 3
Related commands
best-effort match service-class (service class forward type view)
drop-upon-mismatch enable
forward-type (SRv6 TE ODN policy group view)
color match service-class (SRv6 TE policy group view)
Use color match service-class to create color-to-service class mappings for an SRv6 TE policy group.
Use undo color match service-class to delete color-to-service class mappings for an SRv6 TE policy group.
Syntax
color color-value match service-class service-class-value-list
undo color color-value match service-class service-class-value-list
color color-value match service-class default
undo color color-value match service-class [ default ]
Default
No color-to-service class 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.
service-class-value-list: Specifies a space-separated list of up to eight service class value items. Each item specifies a service class value or a range of service class values in the form of service-class-value1 to service-class-value2. The value range for service class values is 0 to 15.The value for the service-class-value2 argument must be greater than or equal to the value for the service-class-value1 argument.
default: Configures a default color-to-service class mapping. Packets that do not match any color-to-service class mappings are steered to the default SRv6 TE policy (the policy with the color attribute value specified in the default mapping).
Usage guidelines
Prerequisites
Execute the forward-type service-class command in SRv6 TE policy group view before using this command.
About this command
After traffic is steered to an SRv6 TE policy group for forwarding, the device matches the service class value of the traffic with the color-to-service class mappings specified by using this command. If a matching mapping is found, the device forwards the traffic through the SRv6 TE policy with the color attribute value mapped to the service class value.
Operating mechanism
When service class-based traffic steering is used, the device uses the following process to forward a packet:
1. Matches the service class value in the packet with the mappings configured by using the color match service-class and best-effort match service-class commands. If a match is found, the device uses the matching SRv6 TE policy to forward the packet or forwards the packet in SRv6 BE mode.
2. Uses the default SRv6 TE policy specified by using the color match service-class default command to forward the packet in the following situations:
¡ The service class value in the packet does not match an SRv6 TE policy or the SRv6 BE mode.
¡ The service class value in the packet matches an SRv6 TE policy or the SRv6 BE mode. However, the matching SRv6 TE policy or the SRv6 BE mode is invalid.
3. Forwards the packet in SRv6 BE mode if both of the following requirements are met:
¡ No default SRv6 TE policy is specified by using the color match service-class default command, or the default SRv6 TE policy is invalid.
¡ The best-effort match service-class default command is used and the SRv6 BE mode is valid.
4. Handles the packet according to whether the drop-upon-mismatch enable command is used if the best-effort match service-class default command is not used or the SRv6 BE path is invalid.
¡ 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 uses the SRv6 TE policy mapped to the smallest service class value to forward the packet in case that the SRv6 TE policy is valid.
5. The device performs an IPv6 routing table lookup to forward the packet if the packet does not meet any of the previous conditions.
Restrictions and guidelines
Only one default SRv6 TE policy can be specified for an SRv6 TE policy group.
For an SRv6 TE policy group, a service class value can be mapped only to the SRv6 BE mode or to one SRv6 TE policy.
Examples
# In SRv6 TE policy group 10, map service class value 3 to color value 20 for packets, so that packets with a matching service class 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] forward-type service-class
[Sysname-srv6-te-policy-group-10] color 20 match service-class 3
Related commands
best-effort match service-class (SRv6 TE policy group view)
drop-upon-mismatch enable
forward-type (SRv6 TE policy group view)
constraints
Use constraints to create and enter SRv6 TE policy constraints view, or enter the existing SRv6 TE policy constraints view.
Use undo constraints to delete the SRv6 TE policy constraints view and all configurations in the view.
Syntax
constraints
undo constraints
Default
No SRv6 TE policy constraints exist.
Views
SRv6 TE policy path preference view
Predefined user roles
network-admin
Usage guidelines
In constraints view, you can configure the affinity attribute and segment constraints for an SRv6 TE policy for flexible forwarding path control.
When both affinity attribute and segment constraints are configured in constraints view, segment constraints apply.
Examples
# Create SRv6 TE policy constraints and enter constraints view.
<Sysname> system-view
[Sysname] segment-routing ipv6
[Sysname-segment-routing-ipv6] traffic-engineering
[Sysname-srv6-te] policy a1
[Sysname-srv6-te-policy-a1] candidate-paths
[Sysname-srv6-te-policy-a1-path] preference 200
[Sysname-srv6-te-policy-a1-path-pref-200] constraints
[Sysname-srv6-te-policy-a1-path-pref-200-const]
default match
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 is 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. Performs an IPv6 routing table lookup to forward the packets if the packets do not meet any of the previous conditions.
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: Specifies a default color value in the range of 0 to 4294967295.
Usage guidelines
The local PE uses the default color value to match an 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: Specifies a default color value in the range of 0 to 4294967295.
evpn: Specifies the EVPN L3VPN service. If you do not specify this keyword, the default color applies to 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 does not exceed 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
delete-delay
Use delete-delay to configure the deletion delay time for SRv6 TE policies generated by ODN templates.
Use undo delete-delay to restore the default.
Syntax
delete-delay delay-time
undo delete-delay
Default
The deletion delay time for SRv6 TE policies generated by ODN templates is 180000 milliseconds.
Views
SRv6-TE-ODN view
Predefined user roles
network-admin
Parameters
delay-time: Specifies the deletion delay time, in the range of 0 to 600000 milliseconds.
Usage guidelines
ODN automatically creates an SRv6 TE policy based on the specified BGP route. The SRv6 TE policy is deleted immediately when the BGP route is deleted. To avoid packet loss before the new forwarding path is computed, you can use this command to configure a proper deletion delay time for the SRv6 TE policy.
Examples
# Set the deletion delay time to 300000 milliseconds for SRv6 TE policies generated by ODN templates.
<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] delete-delay 300000
description
Use description to configure the description of the SRv6 TE policy group ODN template.
Use undo description to restore the default.
Syntax
description text
undo description
Default
The description of the SRv6 TE policy group ODN template is not configured.
Views
SRv6 TE ODN policy group view
Predefined user roles
network-admin
Parameters
text: Specifies the description of the SRv6 TE policy group ODN template, a case-sensitive string of 1 to 242 characters.
Usage guidelines
To facilitate management, use this command to configure the description of the SRv6 TE policy group ODN template.
Examples
# Configure the description of the SRv6 TE policy group ODN template.
<Sysname> system-view
[Sysname] segment-routing ipv6
[Sysname-segment-routing-ipv6] traffic-engineering
[Sysname-srv6-te] on-demand-group color 1
[Sysname-srv6-te-odn-group-1] description abc
display bgp 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 IP L3VPN over SRv6, EVPN L3VPN over SRv6, or IP public network over SRv6 networks.
If you do not specify any parameters, this command displays all remote SRv6 SIDs protected by mirror SIDs.
Examples
# Display all remote SRv6 SIDs protected by mirror SIDs.
<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. |
|
Public instance |
Name of the public instance. |
display bgp routing-table ipv6 sr-policy
Use display bgp routing-table ipv6 sr-policy to display route information of a BGP BGP IPv6 SR policy.
Syntax
display bgp [ instance instance-name ] routing-table ipv6 sr-policy [ sr-policy-prefix [ advertise-info | as-path | cluster-list | community | ext-community ] | { color color-value | end-point ipv6 ipv6-address } * | peer ipv6-address { advertised-routes | received-routes } [ statistics ] [ color color-value | end-point ipv6 ipv6-address ] * | statistics [ color color-value | end-point ipv6 ipv6-address ] * ]
display bgp [ instance instance-name ] routing-table ipv6 sr-policy [ statistics ] community [ community-number&<1-32> | aa:nn&<1-32> ] [ internet | no-advertise | no-export | no-export-subconfed ] [ whole-match ]
display bgp [ instance instance-name ] routing-table ipv6 sr-policy [ statistics ] community-list { basic-community-list-number | comm-list-name | adv-community-list-number } [ whole-match ]
display bgp [ instance instance-name ] routing-table ipv6 sr-policy [ statistics ] ext-community [ bandwidth link-bandwidth-value | color color | rt route-target | soo site-of-origin ]&<1-32> [ whole-match ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
instance instance-name: Specifies a BGP instance by its name, a case-sensitive string of 1 to 31 characters. If you do not specify a BGP instance, this command displays information about the default instance.
sr-policy-prefix: Specifies a BGP IPv6 SR policy route prefix, which is a case-insensitive string of 1 to 512 characters in the format of SRv6 TE policy route/prefix length.
color color-value: Specifies the color attribute value of a BGP IPv6 SR policy, in the range of 0 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.
as-path: Specifies the AS_PATH attribute information of the specified BGP IPv6 SR policy route.
cluster-list: Specifies the cluster ID list attribute information of the specified BGP IPv6 SR policy route.
community: Specifies the community attribute information of the specified BGP IPv6 SR policy route or the BGP IPv6 SR policy route information matching the specified community number.
ext-community: Specifies the extended community attribute information of the specified BGP IPv6 SR policy route or the BGP IPv6 SR policy route information matching the specified extended community attribute.
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.
community-number&<1-32>: Specifies a list of up to 32 community sequence numbers. The value range for the community-number argument is 1 to 4294967295.
aa:nn&<1-32>: Specifies a list of up to 32 community numbers. The value range for the aa and nn arguments is 0 to 65535.
internet: Specifies the Internet community attribute. By default, all routes belong to the Internet community. Routes with this attribute can be advertised to all BGP peers.
no-advertise: Specifies the NO_ADVERTISE community attribute. Routes with this attribute cannot be advertised to other BGP peers.
no-export: Specifies the NO_EXPORT community attribute. Routes with this attribute cannot be advertised out of the local AS or out of the local confederation, but can be advertised to other sub-ASs in the confederation.
no-export-subconfed: Specifies the NO_EXPORT_SUBCONFED community attribute. Routes with this attribute cannot be advertised out of the local AS or other sub-ASs in the local confederation.
whole-match: Displays routes exactly matching the specified community list, community number, or extended community attribute. If you do not specify this keyword, the command displays routes whose community list, community number, or extended community attribute include the specified community list, community number, or extended community attribute.
community-list: Displays BGP IPv6 SR policy routes that match a community list.
basic-community-list-number: Specifies a basic community list by its number in the range of 1 to 99.
comm-list-name: Specifies a community list by its name, a case-sensitive string of 1 to 63 characters.
adv-community-list-number: Specifies an advanced community list by its number in the range of 100 to 199.
bandwidth link-bandwidth-value: Specifies a link bandwidth extended community attribute, a string of 3 to 16 characters, in the format of 16-bit AS number:32-bit user-defined number. For example, 100:3. The AS number is in the range of 0 to 65535, and the user-defined number is in the range of 0 to 4294967295.
color color-value: Specifies the color extended attribute, a string of 4 to 13 characters, in the format of Color-Only (CO) flag:color-value. For example: 10:3. The CO flag is a binary value in the range of 00 to 11, and the color value is in the range of 0 to 4294967295.
rt route-target: Specifies an RT, a string of 3 to 24 characters.
soo site-of-origin: Specifies the SoO attribute, a string of 3 to 24 characters. The SoO attribute has the following formats:
An RT or SoO has the following formats:
· 16-bit AS number:32-bit user-defined number. For example, 101:3. The AS number is in the range of 0 to 65535, and the user-defined number is in the range of 0 to 4294967295.
· 32-bit IP address:16-bit user-defined number. For example, 192.168.122.15:1. The user-defined number is in the range of 0 to 65535.
· 32-bit AS number:16-bit user-defined number. For example, 70000:1. The AS number is in the range of 65536 to 4294967295, and the user-defined number is in the range of 0 to 65535.
· 32-bit IP address/mask length:16-bit user-defined number. For example, 192.168.122.15/24:1.
· 32-bit dotted AS number:16-bit user-defined number. For example, 65535.65535:1.
&<1-32>: Indicates the argument before it can be entered up to 32 times.
Usage guidelines
If you do not specify any parameters, this command displays brief information about all BGP IPv6 SR policy routes.
If you do not specify the community-number, aa:nn, internet, no-advertise, no-export, or no-export-subconfed parameter, this command displays BGP IPv6 SR policy routes that carry any community attribute. In addition, the whole-match keyword does not take effect.
If you do not specify the bandwidth, color, rt, or soo keyword, this command displays BGP IPv6 SR policy routes that carry any extended community attribute. In addition, the whole-match keyword does not take effect.
Examples
# Display brief information about all BGP IPv6 SR policy routes.
<Sysname> display bgp routing-table ipv6 sr-policy
Total number of routes: 1
BGP local router ID is 2.2.2.2
Status codes: * - valid, > - best, d - dampened, h - history
s - suppressed, S - stale, i - internal, e - external
a – additional-path
Origin: i - IGP, e - EGP, ? - incomplete
>i Network : [46][46][8::8]/192
NextHop : 1::2 LocPrf : 100
PrefVal : 0 MED : 0
Path/Ogn: i
# Display information about BGP IPv6 SR policy routes carrying community attributes.
<Sysname> display bgp routing-table ipv6 sr-policy community
Total number of routes: 1
BGP local router ID is 2.2.2.2
Status codes: * - valid, > - best, d - dampened, h - history
s - suppressed, S - stale, i - internal, e - external
a – additional-path
Origin: i - IGP, e - EGP, ? - incomplete
>i Network : [46][46][8::8]/192
NextHop : 1::2 LocPrf : 100
PrefVal : 0 MED : 0
Community: <1:2>
# Display information about BGP IPv6 SR policy routes carrying extended community attributes.
<Sysname> display bgp routing-table ipv6 sr-policy ext-community
Total number of routes: 1
BGP local router ID is 2.2.2.2
Status codes: * - valid, > - best, d - dampened, h - history
s - suppressed, S - stale, i - internal, e - external
a – additional-path
Origin: i - IGP, e - EGP, ? - incomplete
>i Network : [46][46][8::8]/192
NextHop : 1::2 LocPrf : 100
PrefVal : 0 MED : 0
Ext-Community: <CO-Flag 1:2>
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. |
|
Community |
Community attribute value. |
|
Ext-Community |
Extended community attribute value. |
# 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}
# Display community attribute information for BGP IPv6 SR policy route [46][46][8::8]/192.
<Sysname> display bgp routing-table ipv6 sr-policy [46][46][8::8]/192 community
BGP local router ID: 1.1.1.9
Local AS number: 100
Paths: 1 available, 1 best
BGP routing table information of [46][46][8::8]/192:
Community: no-export
# Display extended community attribute information for BGP IPv6 SR policy route [46][46][8::8]/192.
<Sysname> display bgp routing-table ipv6 sr-policy [46][46][8::8]/192 ext-community
BGP local router ID: 1.1.1.9
Local AS number: 100
Paths: 1 available, 1 best
BGP routing table information of [46][46][8::8]/192:
Ext-Community: <RT 1:1>
# Display AS_PATH attribute information for BGP IPv6 SR policy route [46][46][8::8]/192.
<Sysname> display bgp routing-table ipv6 sr-policy [46][46][8::8]/192 as-path
BGP local router ID: 1.1.1.9
Local AS number: 100
Paths: 1 available, 1 best
BGP routing table information of [46][46][8::8]/192:
As-path: 100
# Display cluster ID list attribute information for BGP IPv6 SR policy route [46][46][8::8]/192.
<Sysname> display bgp routing-table ipv6 sr-policy [46][46][8::8]/192 cluster-list
BGP local router ID: 1.1.1.9
Local AS number: 100
Paths: 1 available, 1 best
BGP routing table information of [46][46][8::8]/192:
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. |
|
Output interface |
Output interface information, which displays the name of the SRv6 TE policy of the forwarding tunnel. |
|
Route age |
Time elapsed since the last update for the route. |
|
OutLabel |
Outgoing label of the route. |
|
RxPathID |
Received Add-Path ID of the route. |
|
TxPathID |
Advertised Add-Path ID of the route. |
|
AS-path |
AS_PATH attribute of the route. |
|
Community |
Community attribute of the route. |
|
Ext-Community |
Extended community attribute of the route. |
|
Cluster list |
Cluster ID list attribute of the route. |
|
Origin |
Origin of the route: · igp—Originated in the AS. · egp—Learned through an EGP. · incomplete—Unknown origin. |
|
Attribute value |
BGP path attributes: · MED—MED value. · localpref—Local preference value. · pref-val—Preferred value. · pre—Protocol preference. |
|
State |
Current state of the route. Options include: · valid—Valid route. · internal—Internal route. · external—External route. · local—Locally generated route. · synchronize—Synchronized route. · best—Optimal route. · delay—Delayed route. The route will be delayed for optimal route selection. This value is available only in detailed information of the route. · not preferred for reason—Reason why the route is not selected as the optimal route. For more information, see Table 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 |
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. The format is {sid-value, flags}, where sid-value is the SID value and flags represents the flags carried in the SID. At present, only the V flag is supported, which means to verify the SID's validity during the SRv6 TE policy path verification. A G-SID is displayed in the format of {sid-value, coc32, prefix-length, flags }, where sid-value is the SID value, prefix-length is the common prefix length, and flags represents the flags carried in the SID. At present, only the V flag is supported, which means to verify the SID's validity during the SRv6 TE policy path verification. |
Table 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 statistics about BGP IPv6 SR policy routes carrying community attributes.
<Sysname> display bgp routing-table ipv6 sr-policy statistics community
Total number of routes: 3
display evpn srv6 mirror remote-sid
Use display evpn srv6 mirror remote-sid to display remote SRv6 SIDs protected by mirror SIDs on EVPN VPWS/VPLS over SRv6 networks.
Syntax
display evpn srv6 mirror remote-sid [ sid | type { end-dt2u | end-dx2 } ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
sid: Specifies a remote SRv6 SID.
type: Specifies a type of remote SRv6 SIDs.
end-dt2u: Specifies the End.DT2U type.
end-dx2: Specifies the End.DX2 type.
Usage guidelines
If you do not specify any parameters, this command displays all remote SRv6 SIDs protected by mirror SIDs on EVPN VPWS/VPLS over SRv6 networks.
Examples
# Display all remote SRv6 SIDs protected by mirror SIDs on EVPN VPWS/VPLS over SRv6 networks.
<Sysname> display evpn srv6 mirror remote-sid
Total number of SIDs: 2
End.DT2U SID : 111::100
Mirror locator : 111::/64
VSI name : svpls
End.DX2 SID : 111::200
Mirror locator : 111::/64
Xconnect group name : svpws
Connection name : pw1
Table 7 Command output
|
Field |
Description |
|
End.DT2U SID |
Remote End.DT2U SID. |
|
End.DX2 SID |
Remote End.DX2 SID. |
|
Mirror locator |
IPv6 prefix and prefix length of the locator for the remote SRv6 SID. |
|
VSI name |
Name of the VSI associated with the remote SRv6 SID. |
|
Xconnect group name |
Name of the cross-connect group associated with the remote SRv6 SID. |
|
Connection name |
Name of the cross-connect associated with the remote SRv6 SID. |
display pce segment-routing ipv6 policy database
Use display pce segment-routing ipv6 policy database to display SRv6 TE policy information stored in the PCE database.
Syntax
display pce segment-routing ipv6 policy database [ color color-value endpoint ipv6 ipv6-address | policyname policy-name] [ verbose ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
color color-value endpoint ipv6 ipv6-address: Specifies an SRv6 TE policy by its color attribute value and end-point IPv6 address. The value range for the color attribute value is 0 to 4294967294.
policyname policy-name: Specifies an SRv6 TE policy by its name, a case-sensitive string of 1 to 59 characters.
verbose: Displays detailed SRv6 TE policy information in the PCE database. If you do not specify this keyword, the command displays brief SRv6 TE policy information in the PCE database.
Usage guidelines
If you do not specify the color color-value endpoint ipv6 ipv6-address option or the policyname policy-name option, this command displays information about all SRv6 TE policies in the PCE database.
Examples
# Display brief SRv6 TE policy information in the PCE database.
<Sysname> display pce segment-routing ipv6 policy database
Color Preference Association Delegated address State Endpoint
1 100 1 192.168.56.1 Up 4:4::4:4
2 10 2 192.168.56.2 Up 4:4::4:4
Table 8 Command output
|
Field |
Description |
|
Color |
Color attribute value of the SRv6 TE policy. |
|
Preference |
Preference of the candidate path of the SRv6 TE policy. |
|
Association ID |
Association ID for the candidate path of the SRv6 TE policy. The PCE database uses an association ID to identify an SRv6 TE policy. |
|
Delegated address |
IP address of the delegated PCE. If the candidate path is not delegated or the delegation fails, this field displays a hyphen (-). |
|
State |
Candidate path state: · Up—The candidate path has been established. · Down—The candidate path has not been established or the establishment fails. |
|
Endpoint |
Endpoint IPv6 address of the SRv6 TE policy. |
# Display detailed SRv6 TE policy information in the PCE database.
<Sysname> display pce segment-routing ipv6 policy database verbose
PLSP ID: 1046537 Policy name: p1
Color: 10
Endpoint: 4:4::4:4
Preference: 10
Protocol Original: 30
BGP Instance: 0
ASN: 0 Node address: 0.0.0.0
Binding SID: 8::1
Association ID: 1
Protection type: Unprotected
Path role: Primary
SRP ID: 0 PCE initiated: No
PCE-setup-type: SRv6-TE Policy
Delegatable: Yes Delegated address: 192.168.56.1
Operational state: Up Speaker address: 192.168.56.1
PCEP status: -
Candidate path/4: path state: Up
SRv6-EROs: 3
SID type: SID without NAI Strict
SID: 6000::1 NAI: N/A
SID type: SID without NAI Strict
SID: 7000::1 NAI: N/A
SID type: SID without NAI Strict
SID: 8000::1 NAI: N/A
SRv6-RROs: 3
SID type: SID without NAI Strict
SID: 6000::1 NAI: N/A
SID type: SID without NAI Strict
SID: 7000::1 NAI: N/A
SID type: SID without NAI Strict
SID: 8000::1 NAI: N/A
Table 9 Command output
|
Field |
Description |
|
PLSP ID |
The PLSP ID uniquely identifies a candidate path. |
|
Policy name |
Name of the SRv6 TE policy. |
|
Color |
Color attribute value of the SRv6 TE policy. |
|
Endpoint |
Endpoint IPv6 address of the SRv6 TE policy. |
|
Preference |
Preference of the candidate path of the SRv6 TE policy. |
|
Protocol Original |
Candidate path source: · 10—PCE created. · 20—BGP created. · 30—Command created. |
|
BGP Instance |
Number of the BGP instance that is created by BGP. This field displays a hyphen (-) if the candidate path is not created by BGP. |
|
ASN |
AS number. A value of 0 means that the device has not obtained SRv6 TE policy information from a BGP peer. |
|
Node address |
BGP node address. This field displays the router ID of the BGP peer when the SRv6 TE policy information was obtained from a BGP peer, and it displays 0.0.0.0 when the SRv6 TE policy information was obtained by using other methods. |
|
Binding SID |
BSID of the SRv6 TE policy. If the SRv6 TE policy does not have a BSID, this field displays a hyphen (-). |
|
Association ID |
Association ID for the candidate path of the SRv6 TE policy. The PCE database uses an association ID to identify an SRv6 TE policy. |
|
Protection type |
Protection type for the candidate path: · Unprotected. · (Full)Rerouting—Normal backup. · Rerouting without Extra-Traffic—Hot-standby backup. · 1:N Protection with Extra-Traffic. · 1+1 Unidirectional Protection. · 1+1 Bidirectional Protection. |
|
Path role |
Role of the candidate path: · Primary. · Backup. · Other. |
|
SRP ID |
ID of the stateful PCE request parameter. |
|
PCE initiated |
Whether the candidate path is initiated by PCE: Yes or No. |
|
PCE-setup-type |
Type of the protocol that created the candidate path. The value can be SRv6-TE Policy. |
|
Delegatable |
Whether the candidate path is delegable: Yes or No. |
|
Delegated address |
IP address of the delegated PCE. If the candidate path is not delegated or the delegation fails, this field displays a hyphen (-). |
|
Operational state |
Candidate path state: · Up—The candidate path has been established. · Down—The candidate path has not been established or the establishment fails. |
|
Speaker address |
IP address of the PCE. |
|
PCEP status |
Candidate path delegation state: · Delegated—The candidate path has been delegated to the PCE. · Updated—The PCE has updated the candidate path. · Redelegating—The device is redelegating the candidate path to another PCE. · Report-only—The device has only reported the candidate path's information to the PCE but it does not delegate the candidate path to the PCE. · State reverted—The candidate path has restored to the state prior to the delegation. |
|
Candidate path/path-id |
SID list used by the candidate path. The path-id is the ID of the SID list. |
|
path state |
State of the SID list: · Up—The SID list has been established. · Down—The SID list has not been established or the establishment fails. |
|
SRv6-EROs |
Number of Segment Routing IPv6 Explicit Route Objects (SR-EROs) and the SR-ERO information. |
|
SID Type |
SID and NAI information contained in the ERO or RRO. The value can be SID without NAI. |
|
Strict |
The current node is a strict node. |
|
SID |
SRv6 SID of the node. |
|
NAI |
This field is not supported in the current software version. Node or Adjacency Identifier. |
|
SRv6-RROs |
Number of Segment Routing IPv6 Record Route Objects (SRv6-RROs) and the SRv6-RRO information. |
display pce segment-routing ipv6 policy initiate-cache
Use display pce segment-routing ipv6 policy initiate-cache to display information about the SRv6 TE policy Initiate messages cached in the PCE process.
Syntax
display pce segment-routing ipv6 policy initiate-cache
Views
Any view
Predefined user roles
network-admin
network-operator
Usage guidelines
After a PCE and a PCC establishes an active-stateful PCEP session, the PCE sends Initiate messages to the PCC to create candidate paths. This command displays the cached unprocessed Initiate messages.
Examples
# Displays SRv6 TE policy Initiate messages cached in the PCE process.
<Sysname> display pce segment-routing ipv6 policy initiate-cache
Policy name: 111111
Color: 17
Endpoint: 3::3
Preference: 17
Originator: -
Binding SID: 8::17
Association ID: 17
Protection type: Unprotected
SRP ID: 1 PCE initiated: Yes
Operational state: Down
Candidate path/0: path state: Down
SRv6-EROs: 1
SID type: SID without NAI Strict
SID: 2::2 NAI: N/A
SRv6-RROs: 0
Table 10 Command output
|
Field |
Description |
|
Policy name |
Name of an SRv6 TE policy. If an SRv6 TE policy does not have a name, this field displays a hyphen (-). |
|
Color |
Color attribute value of the SRv6 TE policy. |
|
Endpoint |
Endpoint IPv6 address of the SRv6 TE policy. |
|
Preference |
Preference of the candidate path of the SRv6 TE policy. |
|
Originator |
BGP node address. This field displays the router ID of the BGP peer when the SRv6 TE policy information was obtained from a BGP peer, and it displays 0.0.0.0 when the SRv6 TE policy information was obtained by using other methods. |
|
Binding SID |
BSID of the SRv6 TE policy. If the SRv6 TE policy does not have a BSID, this field displays a hyphen (-). |
|
Association ID |
Association ID for the candidate path of the SRv6 TE policy. The PCE database uses an association ID to identify an SRv6 TE policy. |
|
Protection type |
Protection type for the candidate path: · Unprotected. · (Full)Rerouting—Normal backup. · Rerouting without Extra-Traffic—Hot-standby backup. · 1:N Protection with Extra-Traffic. · 1+1 Unidirectional Protection. · 1+1 Bidirectional Protection. |
|
SRP ID |
ID of the stateful PCE request parameter. |
|
PCE initiated |
Whether the candidate path is initiated by PCE: Yes or No. |
|
Operational state |
Candidate path state: · Up—The candidate path has been established. · Down—The candidate path has not been established or the establishment fails. |
|
Candidate path/path-id |
SID list used by the candidate path. The path-id is the ID of the SID list. |
|
path state |
State of the SID list: · Up—The SID list has been established. · Down—The SID list has not been established or the establishment fails. |
|
SRv6-EROs |
Number of SR-EROs and the SR-ERO information. |
|
SID Type |
SID and NAI information contained in the ERO or RRO. The value can be SID without NAI. |
|
Strict |
The current node is a strict node. |
|
SID |
SRv6 SID (IPv6 address) of the node. |
|
NAI |
Node or Adjacency Identifier. |
|
SRv6-RROs |
Number of SRv6-RROs and the SRv6-RRO information. |
display segment-routing ipv6 te database
Use display segment-routing ipv6 te database to display SRv6 TE policy database information.
Syntax
display segment-routing ipv6 te database [ link | node | prefix | srv6-sid ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
link: Displays the link information reported by the IGP to the SRv6 TE policy database.
node: Displays the node information reported by the IGP to the SRv6 TE policy database.
prefix: Displays the prefix information reported by the IGP to the SRv6 TE policy database.
srv6-sid: Displays the SRv6 SID information reported by the IGP to the SRv6 TE policy database.
Usage guidelines
If you do not specify any parameters, this command displays all information reported by the IGP to the SRv6 TE policy database.
Examples
# Display link information reported by the IGP to the SRv6 TE policy database.
<Sysname> display segment-routing ipv6 te database link
Link-state information: Link, count: 2
IS-IS P2P:
Local node: System ID 0000.0000.0011.00, IS level: 1
Remote node: System ID 0000.0000.0012.00, IS level: 1
IPv6 local address: 100::1
IPv6 remote address: 100::2
Topology ID: 2
Link source: ProcID 1, TLV type: MT-IS-reach, FragID: 0x0
TE local router ID: 1.1.1.1
TE remote router ID: 2.2.2.2
IPv6 remote router ID: 1::1
IGP metric: 10
SR/SRv6 link maximum SID depths:
MPLS MSD : 5
SRv6 End.X SID
SID : 200::1:0:0
Function type : End.X (no PSP, no USP)
Algorithm : 0
Weight : 0
Flags (B/S/P/C): 0/0/0/0
SRv6 End.X SID
SID : 200::1:0:2
Function type : End.X with PSP
Algorithm : 0
Weight : 0
Flags (B/S/P/C): 0/0/0/0
IS-IS P2P:
Local node: System ID 0000.0000.0019.00, IS level: 1
Remote node: System ID 0000.0000.0020.00, IS level: 1
IPv6 local address: 2001:1::2
IPv6 remote address: 2001:1::16
Topology ID: 2
Link source: ProcID 100, TLV type: MT-IS-reach, FragID: 0x0
TE local router ID: 1.2.3.4
TE remote router ID: 2.2.2.2
IPv6 local router ID: 1::1
TE administrative group: 0x80000000
TE maximum bandwidth (kbits/sec): 1000
TE maximum reservable bandwidth (kbits/sec): 1000
TE class 0 unreserved bandwidth (kbits/sec): 1000
TE class 1 unreserved bandwidth (kbits/sec): 1000
TE class 2 unreserved bandwidth (kbits/sec): 1000
TE class 3 unreserved bandwidth (kbits/sec): 1000
TE class 4 unreserved bandwidth (kbits/sec): 1000
TE class 5 unreserved bandwidth (kbits/sec): 1000
TE class 6 unreserved bandwidth (kbits/sec): 1000
TE class 7 unreserved bandwidth (kbits/sec): 1000
TE class 8 unreserved bandwidth (kbits/sec): 0
TE class 9 unreserved bandwidth (kbits/sec): 0
TE class 10 unreserved bandwidth (kbits/sec): 0
TE class 11 unreserved bandwidth (kbits/sec): 0
TE class 12 unreserved bandwidth (kbits/sec): 0
TE class 13 unreserved bandwidth (kbits/sec): 0
TE class 14 unreserved bandwidth (kbits/sec): 0
TE class 15 unreserved bandwidth (kbits/sec): 0
TE metric: 10
IGP metric: 10
SR/SRv6 link maximum SID depths:
MPLS MSD : 5
SRLG:11
Flag: 0, Average delay(us): 1000
Flag: 0, Min delay(us): 500, Max delay(us): 1500
Delay variation(us): 400
Remaining Bandwidth (bytes/sec): 0
Avaliable Bandwidth (bytes/sec): 0
Utilized Bandwidth (bytes/sec): 0
SR/SRv6 link maximum SID depths:
MPLS MSD : 5
MPLS MSD : 5
Application Specific Link Attributes
SA-Length: 1, UDA-Length: 1
Standard Applications: 0x10 Flex-Algo
User Defined Applications: 0x10 Flex-Algo
Ext Admin Group:
0x00000004 0x00000000 0x00000000 0x00000000
0x00000000 0x00000000 0x00000000 0x80000000
TE metric: 10
TE administrative group: 0x80000000
TE maximum bandwidth (kbits/sec): 1000
TE maximum reservable bandwidth (kbits/sec): 1000
TE class 0 unreserved bandwidth (kbits/sec): 1000
TE class 1 unreserved bandwidth (kbits/sec): 1000
TE class 2 unreserved bandwidth (kbits/sec): 1000
TE class 3 unreserved bandwidth (kbits/sec): 1000
TE class 4 unreserved bandwidth (kbits/sec): 1000
TE class 5 unreserved bandwidth (kbits/sec): 1000
TE class 6 unreserved bandwidth (kbits/sec): 1000
TE class 7 unreserved bandwidth (kbits/sec): 1000
Flag: 0, Average delay(us): 1000
Flag: 0, Min delay(us): 500, Max delay(us): 1500
Delay variation(us): 400
Remaining bandwidth (bytes/sec): 0
Utilized bandwidth (bytes/sec): 0
SRLG: 11
SRv6 End.X SID
SID : 1111::104
Function type : End.X (NO-FLAVOR)
Algorithm : 0
Weight : 0
Flags (B/S/P/C): 0/0/0/0
SRv6 End.X SID
SID : 1111::105
Function type : End.X with PSP
Algorithm : 0
Weight : 0
Flags (B/S/P/C): 0/0/0/0
SRv6 End.X SID
SID : 12:1:2:3:0:6::
Function type : End.X with PSP
Algorithm : 0
Weight : 0
Flags (B/S/P/C): 0/0/0/1
Common prefix length: 64
Node length : 26
Function length : 6
Args length : 0
Table 11 Command output
|
Field |
Description |
|
Link-state information: Link |
Link information. |
|
count |
Number of links reported by the IGP to the SRv6 TE policy database. |
|
Public instance |
Public network instance. |
|
MT-ID |
Topology information: · 0—Standard topology. · 2—IPv6 unicast topology. |
|
Link count |
Number of links in the IS-IS instance. |
|
IS-IS P2P |
IS-IS P2P link. |
|
IS-IS to DIS |
IS-IS link to the pseudonode. |
|
IS-IS from DIS |
IS-IS link from the pseudonode. |
|
Local node |
Local node of the link. |
|
Remote node |
Remote node of the link. |
|
System ID |
System ID of the node. |
|
IS level |
IS-IS level of the node. |
|
Topology ID |
Topology ID: · 0—IPv4 topology. · 2—IPv6 topology. |
|
Link source |
Advertisement source of the link. |
|
ProcID |
IS-IS process ID. |
|
TLV type |
TLV type: · none—Invalid TLV. · nbr—Neighbor TLV. · wide-nbr—Wide neighbor TLV. · ip-internal—IP internal reachability TLV. · ip-external—IP external reachability TLV. · router-id—Router ID TLV. · ip-extended—Extended IP reachability TLV. · ipv6-reach—IPv6 reachability TLV. · ipv6 router-id—IPv6 router ID TLV. · MT-IS-reach—Multi-topology IS reachability TLV. · MT-IP-reach—Multi-topology IP reachability TLV. · MT-ipv6-reach—Multi-topology IPv6 reachability TLV. · srlg—SRLG TLV. · locator—Locator TLV. · rtr-cap—Routing capability TLV. · unknown—Unknown TLV. |
|
FragID |
Fragment ID of the packet. |
|
TE class XX unreserved bandwidth (kbits/sec) |
Reservable bandwidth for the specified TE class. |
|
SR/SRv6 link maximum SID depths |
Maximum SID Depths (MSD) information for the SR-MPLS or SRv6 link. |
|
MPLS MSD |
Maximum number of SIDs that SR-MPLS can encapsulate into a packet. |
|
SRv6 LAN End.X SID |
SRv6 End.X SID sub TLV information about the LAN adjacency link. |
|
SRv6 End.X SID |
SRv6 End.X SID sub TLV information about the P2P adjacency link. |
|
SID |
SRv6 SID. |
|
Function type |
SID function type. If a SID function type contains NO-FLAVOR, for example, End.X (NO-FLAVOR) or End.X with COC (NO-FLAVOR), it indicates that the flavor attribute is canceled for the SID and the SID has only the USP flag. |
|
Flags (B/S/P/C) |
SRv6 flag information: · B—Backup flag. If set, it indicates link protection. · S—Collection flag. If set, it indicates a collection of neighbor devices. The SID can be assigned to multiple neighbors. · P—Permanent flag. If set, it indicates that the SID can be permanently assigned to the neighbor even if the neighbor relationship is reestablished. · C—SRv6 SID compression flag. If set, it indicates that the SID is compressed. |
|
Common prefix length |
Common prefix length of the compressed SID. |
|
Node length |
Node length of the compressed SID. |
|
Function length |
Function length of the compressed SID. |
|
Args length |
Args length of the compressed SID. |
# Display node information reported by the IGP to the SRv6 TE policy database.
<Sysname> display segment-routing ipv6 te database node
Link-state information: Node, count: 2
Public instance, MT-ID: 2, IS-IS instance ID: 0, Node count: 2
IS-IS node: System ID 0000.0000.0011.00, IS level: 1
Node source: ProcID 1, TLV type: none, FragID: 0x0
Node topology ID: 0 2
Node flag: 0x1
Node name: isis1
IS-IS area: 00.0000
TE local router ID: 1.1.1.1
SRv6 capability flag (O/C): 0/0
SR/SRv6 node maximum SID depths:
MPLS MSD : 5
Segment Left: 11
End Pop MSD : 11
H.Encaps MSD: 11
End D MSD : 11
Flex-Algo: 128
Priority: 254
MetricType: 1
MFlag: 0
IS-IS node: System ID 0000.0000.0019.00, IS level: 1
Node source: ProcID 100, TLV type: none, FragID: 0x0
Node topology ID: 0 2
Node flag: 0x1
IS-IS area: 10
TE local router ID: 1.2.3.4
IPv6 local router ID: 1::1
SRv6 capability flag (O/C): 0/1
SR/SRv6 node maximum SID depths:
MPLS MSD : 5
Segment Left: 11
End Pop MSD : 11
H.Encaps MSD: 11
End D MSD : 11
Table 12 Command output
|
Field |
Description |
|
Link-state information: Node |
Node information. |
|
count |
Number of nodes reported by the IGP to the SRv6 TE policy database. |
|
Public instance |
Public network instance. |
|
MT-ID |
Topology information: · 0—Standard topology. · 2—IPv6 unicast topology. |
|
Node count |
Number of nodes in the IS-IS instance. |
|
System ID |
System ID of the node. |
|
IS level |
IS-IS level of the node. |
|
Node source |
Advertisement source of the node. |
|
ProcID |
IS-IS process ID. |
|
TLV type |
TLV type: · none—Invalid TLV. · nbr—Neighbor TLV. · wide-nbr—Wide neighbor TLV. · ip-internal—IP internal reachability TLV. · ip-external—IP external reachability TLV. · router-id—Router ID TLV. · ip-extended—Extended IP reachability TLV. · ipv6-reach—IPv6 reachability TLV. · ipv6 router-id—IPv6 router ID TLV. · MT-IS-reach—Multi-topology IS reachability TLV. · MT-IP-reach—Multi-topology IP reachability TLV. · MT-ipv6-reach—Multi-topology IPv6 reachability TLV. · srlg—SRLG TLV. · locator—Locator TLV. · rtr-cap—Routing capability TLV. · unknown—Unknown TLV. |
|
FragID |
Fragment ID of the packet. |
|
Node flag |
Flag of the node. 0x01 indicates root node. |
|
SRv6 capability flag |
SRv6 capability flag: · O—O flag in the SRH. If set, it indicates that the node supports OAM. · C—SRv6 SID compression flag. If set, it indicates that the SID is compressed. |
|
SR/SRv6 link maximum SID depths |
MSD information for the SR-MPLS or SRv6 link. |
|
MPLS MSD |
Maximum number of SIDs that SR-MPLS can encapsulate into a packet. |
|
Segment Left |
Maximum value of the Segments Left field in the SRH. |
|
End Pop MSD |
Maximum number of SIDs in the SRH to which the node can apply PSP or USP behavior. For a packet destined to the local SID on the device, the device is the endpoint of the packet. |
|
H.Encaps MSD |
Maximum number of SIDs that can be included as part of the H.Encaps behavior. |
|
End D MSD |
Maximum number of SIDs in the SRH when performing decapsulation associated with End.Dx behaviors. |
|
Flex-Algo |
Flexible algorithm ID. |
|
Priority |
Flex-Algo priority. |
|
Metric type |
Metric type of the Flex-Algo: · 0—IS-IS link cost. · 1—Link latency. · 2—TE metric. |
|
MFlag |
Metric flag. A value of 2 indicates that the prefix uses the metric type of the Flex-Algo. |
|
SRPLS node attribute Flex-Algo exclude-any |
Flex-Algo excludes the links with any specific affinity attribute. |
|
SRLG info |
Shared Risk Link Group information. |
# Display prefix information reported by the IGP to the SRv6 TE policy database.
<Sysname> display segment-routing ipv6 te database prefix
Link-state information: Prefix, count: 11
Public instance, MT-ID: 2, IS-IS instance ID: 0, Prefix count: 10
IS-IS IPv6 prefix:
Local node: System ID 0000.0000.0011.00, IS level: 1
Prefix: 1111::/64, Topology ID: 2
Prefix source: ProcID 1, TLV type: ipv6-reach, FragID: 0x0
Route tag: 100
Prefix metric: 0
Locator information
Metric : 0
Algorithm : 0
Flags (D/A): 0/0
IS-IS IPv6 prefix:
Local node: System ID 0000.0000.0011.00, IS level: 1
Prefix: 1112::/64, Topology ID: 2
Prefix source: ProcID 1, TLV type: locator, FragID: 0x0
Locator information
Metric : 0
Algorithm : 128
Flags (D/A): 0/0
Table 13 Command output
|
Field |
Description |
|
Link-state information: Prefix |
Prefix information. |
|
count |
Number of prefixes reported by the IGP to the SRv6 TE policy database. |
|
Public instance |
Public network instance. |
|
MT-ID |
Topology information: · 0—Standard topology. · 2—IPv6 unicast topology. |
|
Prefix count |
Number of prefixes in the IS-IS instance. |
|
Local node |
Local node information of the link. |
|
System ID |
System ID of the node. |
|
IS level |
IS-IS level of the node. |
|
Prefix |
Prefix address. |
|
Topology ID |
Topology ID: · 0—IPv4 topology. · 2—IPv6 topology. |
|
Prefix source |
Advertisement source of the prefix. |
|
ProcID |
IS-IS process ID. |
|
TLV type |
TLV type: · none—Invalid TLV. · nbr—Neighbor TLV. · wide-nbr—Wide neighbor TLV. · ip-internal—IP internal reachability TLV. · ip-external—IP external reachability TLV. · router-id—Router ID TLV. · ip-extended—Extended IP reachability TLV. · ipv6-reach—IPv6 reachability TLV. · ipv6 router-id—IPv6 router ID TLV. · MT-IS-reach—Multi-topology IS reachability TLV. · MT-IP-reach—Multi-topology IP reachability TLV. · MT-ipv6-reach—Multi-topology IPv6 reachability TLV. · srlg—SRLG TLV. · locator—Locator TLV. · rtr-cap—Routing capability TLV. · unknown—Unknown TLV. |
|
FragID |
Fragment ID of the packet. |
|
Route tag |
Tag value of the interface associated with the prefix. |
|
Locator information |
Locator sub-TLV information carried in the prefix. |
|
Algorithm |
ID of the algorithm associated with the locator: · 0—SPF algorithm. · 128 to 288—Flex-Algo algorithm. |
|
Flags (D/A) |
Locator flag: · D—Leakage flag, set when the Locator TLV cannot be leaked from Level-1 to Level-2. · A—Anycast locator flag, set when the locator is an Anycast Locator. |
# Display SRv6 SID information reported by the IGP to the SRv6 TE policy database.
<Sysname> display segment-routing ipv6 te database srv6-sid
Link-state information: SRv6 SID, count: 6
Public instance, MT-ID: 2, IS-IS instance ID: 0, SRv6 SID count: 5
IS-IS SRv6 SID:
Local node: System ID 0000.0000.0011.00, IS level: 1
SID: 1111::1, Topology ID: 2
SID source: ProcID 1, TLV type: locator, FragID: 0x0
SRv6 endpoint function
Function type: End with PSP
Algorithm : 0
Flags : 0x0
Table 14 Command output
|
Field |
Description |
|
Link-state information: SRv6 SID |
SRv6 SID information. |
|
count |
Number of SRv6 SIDs reported by the IGP to the SRv6 TE policy database. |
|
Public instance |
Public network instance. |
|
MT-ID |
Topology information: · 0—Standard topology. · 2—IPv6 unicast topology. |
|
SRv6 SID count |
Number of SRv6 SIDs in the IS-IS instance. |
|
IS-IS SRv6 SID |
SRv6 SID advertised by IS-IS. |
|
Local node |
Local node information of the link. |
|
System ID |
System ID of the node. |
|
IS level |
IS-IS level of the node. |
|
SID |
SRv6 SID. |
|
Topology ID |
Topology ID: · 0—IPv4 topology. · 2—IPv6 topology. |
|
SID source |
Advertisement source of the SID. |
|
ProcID |
IS-IS process ID. |
|
TLV type |
TLV type: · none—Invalid TLV. · nbr—Neighbor TLV. · wide-nbr—Wide neighbor TLV. · ip-internal—IP internal reachability TLV. · ip-external—IP external reachability TLV. · router-id—Router ID TLV. · ip-extended—Extended IP reachability TLV. · ipv6-reach—IPv6 reachability TLV. · ipv6 router-id—IPv6 router ID TLV. · MT-IS-reach—Multi-topology IS reachability TLV. · MT-IP-reach—Multi-topology IP reachability TLV. · MT-ipv6-reach—Multi-topology IPv6 reachability TLV. · srlg—SRLG TLV. · locator—Locator TLV. · rtr-cap—Routing capability TLV. · unknown—Unknown TLV. |
|
FragID |
Fragment ID of the packet. |
|
SRv6 endpoint function |
SRv6 SID function. |
|
Algorithm |
Algorithm value. |
|
Flags |
Compression flag: · 0x01—End SID compression flag. · 0x10—End.X SID compression flag. |
display segment-routing ipv6 te bfd
Use display segment-routing ipv6 te bfd to display BFD information for SRv6 TE policies.
Syntax
display segment-routing ipv6 te bfd [ down | policy { { color color-value | end-point ipv6 ipv6-address } * | name policy-name } | up ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
down: Displays BFD information for SRv6 TE policies in down state.
policy: Displays BFD information for the specified SRv6 TE policy.
color color-value: Specifies the color attribute value of an SRv6 TE policy, in the range of 0 to 4294967295.
end-point ipv6 ipv6-address: Specifies the IPv6 address of the endpoint of an SRv6 TE policy.
name policy-name: Specifies the name of an SRv6 TE policy, a case-sensitive string of 1 to 59 characters.
up: Displays BFD information for SRv6 TE policies in up state.
Usage guidelines
If you do not specify any parameters, this command displays BFD information for all SRv6 TE policies.
Examples
# Display BFD information for all SRv6 TE policies.
<Sysname> display segment-routing ipv6 te bfd
Color: 10
Endpoint: 4::4
Policy name: p1
State: Up
Forwarding index: 2149580801
BFD type: ECHO
Encapsulation mode: Encaps
Source IPv6: 1::1
Source-address: 2::2
State: Up
Timer: 37
VPN index: 1
Template name: abc
Reverse path type: None
Reverse BSID: -
Table 15 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 |
|
Forwarding index |
Forwarding entry index for an SID list. |
|
Nid |
Forwarding entry index for an SID list. |
|
BFD type |
The current software version supports only the BFD echo mode. |
|
Encapsulation mode |
Encapsulation mode for BFD packets: · Encaps—Normal encapsulation mode. · Insert—Insertion encapsulation mode. If the encapsulation mode for BFD packets is not configured, this field displays a hyphen (-). |
|
Source IPv6 |
Source IPv6 address of the BFD session. |
|
Source-address |
Source IP address of BFD packets, which is configured by using the source-address command. If not configured, this field displays a hyphen (-). |
|
Timer |
BFD session timer, in seconds. |
|
VPN index |
Index of the VPN instance. |
|
Template name |
Name of the echo mode BFD template. |
|
Reverse path type |
Reverse path type for BFD packets: · Reverse BSID—Uses the SID list associated with the reverse BSID as the reverse path for BFD packets. · None—The reverse path for BFD packets is not configured. |
|
Reverse BSID |
Reverse BSID of the BFD session. |
display segment-routing ipv6 te forwarding
Use display segment-routing ipv6 te forwarding to display SRv6 TE forwarding information.
Syntax
display segment-routing ipv6 te forwarding [ binding-sid bsid | policy { name policy-name | { color color-value | end-point ipv6 ipv6-address } * } ] [ verbose ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
binding-sid bsid: Specifies a BSID by an IPv6 address.
policy: Displays forwarding information of the specified SRv6 TE policy. If you do not specify an SRv6 TE policy, this command displays forwarding information of all SRv6 TE policies.
name policy-name: Specifies the name of an SRv6 TE policy, a case-sensitive string of 1 to 59 characters.
color color-value: Specifies the color of an SRv6 TE policy, in the range of 0 to 4294967295.
end-point ipv6 ip-address: Specifies the endpoint IPv6 address of an SRv6 TE policy.
verbose: Displays detailed SRv6 TE forwarding information. If you do not specify this keyword, the command displays brief SRv6 TE forwarding information.
Examples
# Display brief information about all SRv6 TE policies.
<Sysname> display segment-routing ipv6 te forwarding
Total forwarding entries: 1
Policy name/ID: p1/0
Binding SID: 8000::1
Forwarding index: 2150629377
Main path:
Seglist Name/ID: 1
Seglist forwarding index: 2149580801
Weight: 1
Outgoing forwarding index: 2148532225
Interface: GE1/0/1
Nexthop: FE80::6CCE:CBFF:FE91:206
Discriminator: 100
Backup Seglist Name/ID: 3
Seglist forwarding index: 2149580803
Weight: 1
Outgoing forwarding index: 2148532227
Interface: GE1/0/3
Nexthop: FE80::6CCE:CBFF:FE91:208
Discriminator: 100
Backup path:
Seglist Name/ID: 2
Seglist forwarding index: 2149580802
Weight: 1
Outgoing forwarding index: 2148532226
Interface: GE1/0/2
Nexthop: FE80::6CCE:CBFF:FE91:207
Secondary backup path:
Seglist Name/ID: 2
Seglist forwarding index: 2149580811
Weight: 1
Outgoing forwarding index: 2148532235
Interface: GE1/0/3
Nexthop: FE80::6CCE:CBFF:FE91:209
# 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
Input rate in last 300 seconds:
0 bits/sec, 0 pkts/sec
Input rate in last statistical period (20 sec):
0 bits/sec, 0 pkts/sec
Outbound statistics:
Total octets: 750
Total packets: 1
Erroneous packets: 0
Dropped packets: 0
Output rate in last 300 seconds:
0 bits/sec, 0 pkts/sec
Output rate in last statistical period (20 sec):
0 bits/sec, 0 pkts/sec
Main path:
Seglist Name/ID: 1
Seglist forwarding index: 2149580801
Weight: 1
Outbound statistics:
Total octets: 750
Total packets: 1
Erroneous packets: 0
Dropped packets: 0
Output rate in last 300 seconds:
0 bits/sec, 0 pkts/sec
Output rate in last statistical period (20 sec):
0 bits/sec, 0 pkts/sec
Output service-class 4:
416 octets, 4 packets,
0 errors, 0 dropped packets
Outgoing forwarding index: 2148532225
Interface: GE1/0/1
Nexthop: FE80::6CCE:CBFF:FE91:206
Path ID: 1
SID list: {44::44, 45::45}
Outbound statistics:
Total octets: 750
Total packets: 1
Erroneous packets: 0
Dropped packets: 0
Output rate in last 300 seconds:
0 bits/sec, 0 pkts/sec
Output rate in last statistical period (20 sec):
0 bits/sec, 0 pkts/sec
Output service-class 4:
416 octets, 4 packets,
0 errors, 0 dropped packets
Backup Seglist Name/ID: 3
Seglist forwarding index: 2149580803
Weight: 1
Outbound statistics:
Total octets: 0
Total packets: 0
Erroneous packets: 0
Dropped packets: 0
Output rate in last 300 seconds:
0 bits/sec, 0 pkts/sec
Output rate in last statistical period (20 sec):
0 bits/sec, 0 pkts/sec
Output service-class 4:
0 octets, 0 packets,
0 errors, 0 dropped packets
Outgoing forwarding index: 2148532227
Interface: GE1/0/3
Nexthop: FE80::6CCE:CBFF:FE91:208
Path ID: 1
SID list: {103::3}
Outbound statistics:
Total octets: 0
Total packets: 0
Erroneous packets: 0
Dropped packets: 0
Output rate in last 300 seconds:
0 bits/sec, 0 pkts/sec
Output rate in last statistical period (20 sec):
0 bits/sec, 0 pkts/sec
Output service-class 4:
0 octets, 4 packets,
0 errors, 0 dropped packets
Backup path:
Seglist Name/ID: 2
Seglist forwarding index: 2149580802
Weight: 1
Outgoing forwarding index: 2148532226
Interface: GE1/0/2
Nexthop: FE80::6CCE:CBFF:FE91:207
Path ID: 2
SID list: {44::44, 45::47}
Secondary backup path:
SegList Name/ID: s1/1
Seglist forwarding index: 2150629382
Weight: 1
Outgoing forwarding index: 2149580804
Interface: GE1/0/3
Nexthop: FE80::A0E1:E0FF:FE6D:5DE1
Path ID: 3
SID list: {103::3}
Table 16 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. |
|
Output service-class |
Statistics on outbound traffic with a specific service class. Service class 255 means that the SRv6 TE policy is not configured with a service class and thus has the lowest forwarding priority. |
|
Main path |
Main path for traffic forwarding. |
|
Backup path |
Backup path for traffic forwarding. |
|
Secondary backup path |
Secondary backup path for traffic forwarding. |
|
Seglist Name/ID |
Name or ID of the SID list. |
|
Backup Seglist Name/ID |
Name or ID of the backup SID list. |
|
Seglist forwarding index |
Forwarding entry index of the SID list. |
|
Weight |
Weight of the SID list. |
|
Delay timer type |
Type of the delay timer: · LSP—Timer that delays to refresh LSPs. · BFD—Timer that delays to clear the BFD/SBFD DOWN bit. |
|
Delay time |
Up delay time in milliseconds. |
|
Remaining time |
Remaining delay time for the up state. |
|
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. |
|
Discriminator |
Discriminator of the SRv6 forwarding path. |
|
Path ID |
ID of the SRv6 TE policy candidate path. |
|
SID list |
List of SIDs. |
|
SID |
SID of the node, which is an IPv6 address. |
|
Common prefix length |
Common prefix length of the next G-SID. If the next SID is a non-compressed SID, the common prefix length is 0. |
|
G-SID length |
Length of the next G-SID. If the next SID is a non-compressed SID, the SID length is 128. |
display segment-routing ipv6 te forwarding traffic-statistics
Use display segment-routing ipv6 te forwarding traffic-statistics to display SRv6 TE traffic statistics.
Syntax
display segment-routing ipv6 te forwarding traffic-statistics
Views
Any view
Predefined user roles
network-admin
network-operator
Examples
# Display SRv6 TE traffic statistics.
<Sysname> display segment-routing ipv6 te forwarding traffic-statistics
Policy name: p1
Policy ID: 0
Color: 10
Endpoint: 4::4
Binding SID: 1::1:0:1
Output rate within last 300 seconds: 0 bits/sec, 0 packets/sec
Output rate within last statistics interval (100 sec): 0 bits/sec, 0 packets/sec
Output: 0 bytes, 0 packets
Primary candidate path:
Preference: 20
Discriminator: 20
Protocol origin: CLI
Segment list name: s2
Segment list ID: 2
Output rate within last 300 seconds: 0 bits/sec, 0 packets/sec
Output rate within last statistics interval (100 sec): 0 bits/sec, 0 packets/sec
Output: 0 bytes, 0 packets
Backup candidate path:
Preference: 10
Discriminator: 10
Protocol origin: CLI
Segment list name: s1
Segment list ID: 1
Output rate within last 300 seconds: 0 bits/sec, 0 packets/sec
Output rate within last statistics interval (100 sec): 0 bits/sec, 0 packets/sec
Output: 0 bytes, 0 packets
Table 17 Command output
|
Field |
Description |
|
Policy name |
Name of the SRv6 TE policy. |
|
Policy ID |
ID of the SRv6 TE policy. |
|
Color |
Color attribute of the SRv6 TE policy. |
|
Endpoint |
IPv6 address of the destination node for the SRv6 TE policy. |
|
Binding SID |
BSID value. |
|
Output rate within last 300 seconds: 0 bits/sec, 0 packets/sec |
Outbound traffic rate statistics within the most recent 300 seconds. |
|
Output rate within last statistics interval (100 sec): 0 bits/sec, 0 packets/sec |
Outbound traffic rate statistics within the most recent statistics interval. To set the statistics interval, use the srv6-policy forwarding statistics interval command. |
|
Output: 0 bytes, 0 packets |
Total bytes and total number of packets for outbound traffic. |
|
Primary candidate path |
Primary candidate path for forwarding traffic. |
|
Backup candidate path |
Backup candidate path for forwarding traffic. |
|
Preference |
Candidate path preference of the SRv6 TE policy. |
|
Discriminator |
Discriminator of the forwarding path. |
|
Protocol origin |
Protocol that obtained the candidate path: · PCEP. · BGP. · CLI—Locally configured. · Unknown—Unknown source. |
|
Segment list name |
Name of the SID list. |
|
Segment list ID |
ID of the SID list. |
display segment-routing ipv6 te policy
Use display segment-routing ipv6 te policy to display SRv6 TE policy information.
Syntax
display segment-routing ipv6 te policy [ odn | pce ] [ name policy-name | down | up | { color color-value | end-point ipv6 ipv6-address } * ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
odn: Specifies SRv6 TE policies created by ODN.
pce: Specifies SRv6 TE policies whose SID lists are computed by a PCE.
name policy-name: Specifies an SRv6 TE policy by its name, a case-sensitive string of 1 to 59 characters.
down: Specifies the SRv6 TE policies in down state.
up: Specifies the SRv6 TE policies in up state.
color color-value: Specifies the color of an SRv6 TE policy, in the range of 0 to 4294967295.
end-point ipv6 ipv6-address: Specifies the endpoint IPv6 address of an SRv6 TE policy.
Usage guidelines
If you do not specify any parameters, this command displays information about all SRv6 TE policies.
Examples
# Display information about all SRv6 TE policies.
<Sysname> display segment-routing ipv6 te policy
Name/ID: p1/0
Color: 10
Endpoint: 1000::1
Name from BGP:
Name from PCE:
BSID:
Mode: Dynamic Type: Type_2 Request state: Succeeded
Current BSID: 8000::1 Explicit BSID: - Dynamic BSID: 8000::1
Reference counts: 3
Flags: A/BS/NC
Status: Up
AdminStatus: Up
Up time: 2020-03-09 16:09:40
Down time: 2020-03-09 16:09:13
Hot backup: Enabled
Statistics: Enabled
Statistics by service class: Enabled
Path verification: Enabled
Forwarding ignore last SID: Enabled
Drop-upon-invalid: Enabled
BFD trigger path-down: Enabled
Source-address: 1::1
SBFD: Enabled
Encapsulation mode: Encaps
Remote: 1000
SBFD template name: abc
SBFD backup-template name: -
OAM SID: -
Reverse path type: Reverse BSID
BFD Echo: Enabled
Encapsulation mode: Encaps
Source IPv6 address: 1::1
Echo template name: -
Echo backup-template name: -
OAM SID: -
Reverse path type: Reverse BSID
Forwarding index: 2150629377
Association ID: 1
Service-class: -
Rate-limit: 15000 kbps
PCE delegation: Not configured
PCE delegate report-only: Enabled
Encaps reduced: Not configured
Encaps include local End.X: Not configured
Flapping suppression Remaining interval: -
Candidate paths state: Configured
Candidate paths statistics:
CLI paths: 1 BGP paths: 0 PCEP paths: 0 ODN paths: 0
Candidate paths:
Preference : 20
Network slice ID: 1
CpathName:
ProtoOrigin: CLI Discriminator: 30
Instance ID: 0 Node address: 0.0.0.0
Originator: 0, ::
SRv6 Binding SID:
Binding SID: 100::1
Flags(S/I/B): 0/1/1
Endpoint Behavior: End.B6.Encaps
Locator Block Length: 64
Locator Node Length: 16
Function Length: 16
Argument Length: 8
SRv6 Binding SID:
Binding SID: 200::2
Flags(S/I/B): 0/1/1
Endpoint Behavior: End.B6.Encaps.Red
Locator Block Length: 64
Locator Node Length: 8
Function Length: 24
Argument Length: 16
Optimal: Y Flags: V/A
Dynamic: Not configured
PCEP: Not configured
Explicit SID list:
ID: 1 Name: Sl1
Weight: 1 Forwarding index: 2149580801
State: Up State(-): -
Verification State: -
Active path MTU: 1600 bytes
Backup ID: 2 Name: s2
Weight: 1 Forwarding index: 2149580802
State: Up State(-): -
Verification State: -
Active path MTU: 1280 bytes
Local BSID: -
Reverse BSID: -
Table 18 Command output
|
Field |
Description |
|
Name/ID |
SRv6 TE policy name/ID. |
|
Color |
Color attribute of the SRv6 TE policy. |
|
Endpoint |
Endpoint IPv6 address of the SRv6 TE policy. If the endpoint is not configured, this field displays None. |
|
Name from BGP |
Name of the SRv6 TE policy obtained from BGP. If no SRv6 TE policy was obtained from BGP, this field is empty. |
|
Name from PCE |
Name of the SRv6 TE policy obtained from PCE. If no SRv6 TE policy was obtained from PCE, this field is empty. |
|
BSID |
SID value of the ingress node. |
|
Mode |
BSID configuration mode: · Explicit—Manually configured. · Dynamic—Dynamically requested. · None—Not configured. |
|
Type |
BSID type: · None—Not configured. · Type_2—IPv6 address. |
|
Request state |
BSID request state: · Conflicted. · Failed. · Succeeded. |
|
Explicit BSID |
Manually configured BSID. |
|
Dynamic BSID |
Dynamically requested BSID. |
|
Request failure reason |
Reason for BSID request failure: · The specified locator does not exist. · Exhausted SID resources. · Memory threshold reached. · The associated locator is being deleted. · Invalid SID. · The segrt process is smoothing. · The specified static BSID already exists. · The SRMS process is not started. This field is displayed only when the BSID request state is Failed. |
|
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. The SRv6 TE policy is up if a minimum of one SID list in the candidate paths of the SRv6 TE policy is up. The SRv6 TE policy is down if no SID list in the candidate paths of the SRv6 TE policy is up. · Up—Active state. · Down—Inactive state. The SRv6 TE policy is down because of a reason other than BFD or SBFD detection. In this state, the first next hop on the forwarding paths of all the SID lists is unreachable. · Down (BFD down)—A BFD or SBFD session detects that the forwarding paths of all SID lists in the candidate paths of the SRv6 TE policy are not available. The state of the SRv6 policy is set to down. In this state, the first next hop on the forwarding paths of all the SID lists is available. However, the subsequent paths are not available. |
|
AdminStatus |
Administrative state of the SRv6 TE policy: · Down—The policy is shut down by the shutdown command. · Up—The policy is not shut down by the shutdown command. |
|
Up time |
Date and time when the SRv6 TE policy became up. |
|
Down time |
Date and time when the SRv6 TE policy became down. |
|
Hot backup |
Hot standby status for the SRv6 TE policy: · Enabled. · Disabled. · Multilevel-backup—Hot backup is enabled and the secondary backup path is configured. |
|
Statistics |
Traffic statistics status for the SRv6 TE policy: · Disabled. · Enabled. |
|
Statistics by service class |
Service class based traffic statistics status for the SRv6 TE policy: · Enabled. · Disabled. |
|
Path verification |
Status of the path verification feature: · Enabled—Verifies the validity of all SIDs in the segment list. · Specified SIDs—Verifies the validity of the specified SIDs in the segment list. · Disabled. · Not configured. |
|
Forwarding ignore last SID |
Whether or not to ignore the last SID in the SID list of the SRv6 TE policy: · Enabled. · Disabled. |
|
Drop-upon-invalid |
Drops traffic when the SRv6 TE policy becomes invalid: · Disabled. · Enabled. |
|
BFD trigger path-down |
Whether to enable SRv6 TE policy path switchover when the BFD session for the SRv6 TE policy goes down: · Disabled. · Enabled. |
|
Source-address |
Source address of the SRv6 TE policy. If no source address is configured, this field displays None. |
|
SBFD |
SBFD status for the SRv6 TE policy: · Enabled. · Disabled. |
|
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. |
|
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. |
|
Encapsulation mode |
Encapsulation mode for the SRv6 TE policy: · Encaps. · Insert. · Insert no endpoint. If the encapsulation mode is not configured for the SRv6 TE policy, this field displays a hyphen (-). |
|
Reverse path type |
Reverse path type for BFD echo packets: · Reverse BSID—Uses the SID list associated with the reverse BSID as the reverse path for BFD packets. · None—The reverse path for BFD packets is not configured. |
|
Forwarding index |
Forwarding entry index of the SRv6 TE policy. |
|
Association ID |
Association ID for the candidate path of the SRv6 TE policy. An association ID can identify an SRv6 TE policy. |
|
Service-class |
Service class value of the SRv6 TE policy. If the default service class is used, this field displays a hyphen (-). |
|
Rate-limit |
Rate limit for the SRv6 TE policy. If no rate limit is configured, this field displays a hyphen (-). |
|
PCE delegation |
PCE delegation state for the SRv6 TE policy: · Disabled. · Enabled. · Not configured. |
|
PCE delegate report-only |
Only reports SRv6 TE policy information without delegating the SRv6 TE policy to the PCE: · Disabled. · Enabled. · Not configured. |
|
Encaps reduced |
Encaps.Red encapsulation mode for the SRv6 TE policy: · Disabled. · Enabled. · Not configured. |
|
Encaps include local End.X |
Local End.X SID encapsulation for the SRv6 TE policy: · Disabled. · Enabled. · Not configured. |
|
Flapping suppression Remaining interval |
Remaining interval for flapping suppression. |
|
Candidate paths state |
Whether candidate paths are configured: · Configured. · Not configured. |
|
Candidate paths statistics |
Candidate paths statistics by path origin. |
|
CLI paths |
Number of manually configured candidate paths. |
|
BGP paths |
Number of candidate paths obtained from BGP SRv6 Policy routes. |
|
PCEP paths |
This field is not supported in the current software version. Number of candidate paths obtained from PCEP. |
|
ODN paths |
Number of candidate paths created by ODN. |
|
Candidate paths |
SRv6 TE policy candidate path information. |
|
Preference |
SRv6 TE policy candidate path preference. |
|
Network slice ID |
Network slice ID of the SRv6 TE policy candidate path. |
|
CPathName |
Name of the candidate path obtained from a BGP route. If no path name was obtained, this field is empty. |
|
ProtoOrigin |
Protocol that obtained the SRv6 TE policy: · PCEP—The SRv6 TE policy was obtained through PCEP. (This value is not supported in the current software version.) · BGP—The SRv6 TE policy was obtained through BGP. · CLI—The SRv6 TE policy was locally configured. · Unknown—The SRv6 TE policy origin is unknown. |
|
Discriminator |
Discriminator of the SRv6 TE policy. |
|
Instance ID |
BGP instance ID. A value of 0 indicates that the device does not obtain SRv6 TE policy information from BGP peers. |
|
Node address |
BGP node address. For an SRv6 TE policy obtained from a BGP peer, the node address is the Router ID of the BGP peer. For an SRv6 TE policy obtained in other methods, the node address is 0.0.0.0. |
|
Originator: ASN, Peer-address |
The SRv6 TE policy was obtained through BGP. · ASN—AS number. A value of 0 indicates that the device does not obtain SRv6 TE policy information from BGP peers. · Peer-address—BGP peer address, which is the router ID of the BGP peer for an SRv6 TE policy obtained from a BGP peer. For a manually configured SRv6 TE policy, the peer address is ::. |
|
SRv6 Binding SID |
SRv6 Binding SID Sub-TLV information: · Binding SID—BSID value of the SRv6 TE policy candidate path. · Flags (S/I/B)—BSID flags. ¡ S—Specified-BSID-only flag. The current software version does not support this flag. If this flag is set, the system takes restrictive Specified-BSID-only behaviors on the candidate path. The system does not bind a BSID to the candidate path and determines that it is invalid if it has an unspecified BSID or if the specified BSID is not available when it becomes active. ¡ I—Invalid flag. This flag has the same effect as the drop-upon-invalid enable command. When this flag is set, the device discards traffic that matches an invalid SRv6 TE policy. ¡ B—Behavior flag. When this flag is set in a packet, the packet carries an SRv6 SID endpoint behavior. · Endpoint Behavior—Endpoint behavior for BSID-based traffic steering. ¡ End.B6.Encaps—Normal encapsulation mode. ¡ End.B6.Encaps.Red—Reduced mode of the normal encapsulation mode. · Locator Block Length—Common prefix length, in bits. · Locator Node Length—Node ID length, in bits. · Function Length—Function length, in bits. · Argument Length—Argument length, in bits. |
|
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. · T—Secondary backup path. |
|
Dynamic |
Dynamic SID list computation: Configured or Not configured. |
|
Last calculation started at |
Time when the most recent dynamic calculation started. |
|
Duration |
Period of time that the most recent dynamic calculation lasted, in seconds. |
|
Reason for last calculation failure |
Failure reason for the most recent dynamic calculation: · Endpoint is 0.0.0.0. · The destination node does not exist. · The destination node is the same as the source node. · Flex-Algo is not configured. · Destination node is unreachable. · The topology information is incomplete. · The link has no adjacent SID. · Cannot get valid SIDs. · SID list exceeds the maximum SID depth. · Failed to create SID list. Internal error. |
|
PCEP |
Configuration state of PCEP: Configured or Not configured. |
|
Explicit SID list |
Explicit SID list in the candidate path of the SRv6 TE policy. |
|
ID |
SID list ID. |
|
Backup ID |
Index of the backup SID list. |
|
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. The SID list is up if its first next hop is reachable. The SID list is down if its first next hop is unreachable. · UP. · DOWN. · Down (BFD down)—The first next hop on the forwarding path of the SID list is available, but BFD detects that the subsequent path is not available. |
|
State(type) |
SBFD or echo BFD session state for the SID list: · Up. · Down. · Path Inactive—The candidate path contains no available SID list. · Unknown—The SBFD or echo BFD result is unknown. 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 (-). |
|
Active path MTU |
Active path MTU of the SID list, which equals the SRv6 path MTU minus the reserved path MTU. |
|
Local BSID |
Local BSID used for BFD. |
|
Reverse BSID |
Reverse BSID used for BFD. |
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 | { 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.
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 : 10 s
Measurement values :
One-Way Delay(ms) : 10
One-Way Jitter(ms) : 100
One-Way Loss(per-thousand) : 123
Two-Way Delay(ms) : 12
Two-Way Jitter(ms) : 111
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
Two-Way Delay(ms) : 0
Two-Way Jitter(ms) : 0
Table 19 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 |
iFIT measurement interval, in seconds. |
|
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 (‰). |
|
Two-Way Delay(ms) |
Two-way iFIT delay weight value of all SID lists in the optimal candidate path of the SRv6 TE policy, measured in milliseconds. |
|
Two-Way Jitter(ms) |
Two-way iFIT jitter weight value of all SID lists in the optimal candidate path of the SRv6 TE policy, measured in milliseconds. |
|
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 (‰). |
|
Two-Way Delay(ms) |
The most recent five two-way iFIT delay values of the SID list, measured in milliseconds. |
|
Two-Way Jitter(ms) |
The most recent five two-way iFIT jitter values of the SID list, measured in milliseconds. |
Related commands
ifit delay-measure
ifit interval
ifit loss-measure
srv6-policy ifit delay-measure enable
srv6-policy ifit interval
srv6-policy ifit loss-measure enable
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
Backup ID: 2 Name: s2
Up time: 2020-06-23 15:42:14
Down time: 2020-06-23 15:41:15
Down reason: No SRv6 SID Out
Table 20 Command output
|
Field |
Description |
|
Name/ID |
Name/ID of an SRv6 TE policy. |
|
Color |
Color attribute value of the SRv6 TE policy. |
|
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. |
|
Backup ID |
Index of the backup SID list. |
|
Name |
SID list name. |
|
Up time |
Time when the SID list came up. |
|
Down time |
Time when the SID list went down. |
|
Down reason |
Reason for the down event of the SID list: · No SID list—The SID list does not exist. · No SRv6 SID Out—The first SID in the SID list has no outgoing interface. · Internal error. · Bfd Detect Down—The first next hop on the forwarding path of the SID list is available, but BFD detects that the subsequent path is not available. |
display segment-routing ipv6 te policy statistics
Use display segment-routing ipv6 te policy statistics to display SRv6 TE policy statistics.
Syntax
display segment-routing ipv6 te policy statistics
Views
Any view
Predefined user roles
network-admin
network-operator
Examples
# Display SRv6 TE policy statistics.
<Sysname> display segment-routing ipv6 te policy statistics
IPv6 TE Policy Database Statistics
Total policies: 1 (1 up 0 down)
Configured: 1 (1 up 0 down)
From BGP: 0 (Added 0 deleted 0 0 up 0 down)
From ODN: 0 (Added 0 deleted 0 0 up 0 down)
From PCE: 0 (Added 0 deleted 0 0 up 0 down)
Total candidate paths: 1
Configured: 1
From BGP: 0 (Added 0 deleted 0)
From ODN: 0 (Added 0 deleted 0)
From PCE: 0 (Added 0 deleted 0)
Total SID lists: 1 (1 up 0 down)
Configured: 1 (1 up 0 down)
Dynamic : 1 (1 up 0 down)
From BGP: 0 (0 up 0 down)
From PCE: 0 (0 up 0 down)
SRv6-TE policy group resource information:
Max resources: 1024
Used resources: 0
Upper threshold: 717 (70%)
Lower threshold: 102 (10%)
SRv6-TE policy resource information:
Max resources: 1024
Used resources: 1
Upper threshold: 512 (50%)
Lower threshold: 102 (10%)
SID list resource information:
Max resources: 4096
Used resources: 1
Upper threshold: 3277 (80%)
Lower threshold: 1638 (40%)
Forwarding path resource information:
Max resources: 65535
Used resources: 1
Upper threshold: 26214 (40%)
Lower threshold: 13107 (20%)
Table 21 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 or Down (BFD 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 or Down (BFD down) state. |
|
Dynamic |
Number of dynamically calculated SRv6 TE policies: · up—Number of SRv6 TE policies in up state. · down—Number of SRv6 TE policies in down state. |
|
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 or Down (BFD down) state. |
|
From ODN |
Number of SRv6 TE policies created by ODN. · Added—Number of ODN-added SRv6 TE policies. · deleted—Number of ODN-deleted SRv6 TE policies. · up—Number of SRv6 TE policies in up state. · down—Number of SRv6 TE policies in down or Down (BFD down) state. |
|
From PCE |
Number of SRv6 TE policies created by PCE. · Added—Number of PCE-added SRv6 TE policies. · deleted—Number of PCE-deleted SRv6 TE policies. · up—Number of SRv6 TE policies in up state. · down—Number of SRv6 TE policies in down or Down (BFD down) state. |
|
Total candidate paths |
Total number of SRv6 TE policy candidate paths. |
|
Total SID lists |
Total number of SID lists. |
|
Max resources |
Total number of resources. |
|
Upper threshold |
Upper resource threshold. |
|
Lower threshold |
Lower resource threshold. |
display segment-routing ipv6 te policy status
Use display segment-routing ipv6 te policy status to display status information about SRv6 TE policies.
Syntax
display segment-routing ipv6 te policy status [ policy-name policy-name ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
policy-name policy-name: Specifies an SRv6 TE policy by its name, a case-sensitive string of 1 to 59 characters. If you do not specify this option, the command displays status information about all SRv6 TE policies.
Usage guidelines
The device executes the check items for an SRv6 TE policy one by one.
If the result for a check item is Passed, it means that the SRv6 TE policy passed the check for this item and the next item check starts.
If the result for a check item is Failed, the subsequent items will not be checked and the check result for those items is displayed as a hyphen (-).
Examples
# Display status information about all SRv6 TE policies.
<Sysname> display segment-routing ipv6 te policy status
Name/ID: p1/0
Status: Up
Check admin status : Passed
Check for endpoint & color : Passed
Check for segment list : Passed
Check valid candidate paths : Passed
Check for BSIDs : Passed
Table 22 Command output
|
Field |
Description |
|
Name/ID |
Name/ID of an SRv6 TE policy. |
|
Status |
State of the SRv6 TE policy: · Up—Active state. · Down—Inactive state. The SRv6 TE policy is down because of a reason other than BFD or SBFD detection. · Down (BFD down)—A BFD or SBFD session detects that the forwarding paths of all SID lists in the candidate paths of the SRv6 TE policy are not available. The state of the SRv6 policy is set to down. In this state, the first next hop on the forwarding paths of all the SID lists is available. However, the subsequent paths are not available. |
|
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: Up
GroupNID: 2151677953 Best-effort NID: 2156920837
Referenced: 1 Flags: A
Group type: Static DSCP
Group color: 10
StateChangeTime: 2022-08-10 01:50:17
Endpoint: 4::4
BSID:
Explicit BSID: 8000::12 Request state: Succeeded
Drop upon mismatch: Enabled
UP/Total Mappings: 6/6
IPv4 Best-effort: Not configured IPv6 Best-effort: Not configured
Color Type DSCP
10 IPv4 10, 12, 14, 16, 18, 20
GroupID: 11 GroupState: Up
GroupNID: 2151677963 Best-effort NID: 2156920832
Referenced: 1 Flags: A
Group type: Static TE Class
Group color: 10
StateChangeTime: 2022-08-10 01:50:17
Endpoint: 4::4
UP/Total Mappings: 6/6
Default Match Type: IPR Policy/SRv6 BE
Default SRv6 TE Policy Color: -
Default IPR Policy : Ipr1
Color : 1 Priority : 1
Color : 2 Priority : 1
Index : 1 TE Class : 3
Match Type : IPR Policy(active)
SRv6 TE Policy Color : -
IPR Policy : ipr1
Color : 10 Priority : 1
Color : 20 Priority : 1
Index : 2 TE Class : 1
Match Type : SRv6 TE Policy
SRv6 TE Policy Color : 1
IPR Policy : -
Index : 3 TE Class : 2
Match Type : SRv6 BE
SRv6 TE Policy Color : -
IPR Policy : -
Table 23 Command output
|
Field |
Description |
|
UPMappings |
Number of up (valid) mappings 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. |
|
Best-effort NID |
Index of the forwarding entry for SRv6 BE. |
|
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. · BA—Requesting a BSID. · BS—Preferred BSID. · BC—Conflicts with an existing BSID. · 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. · Static service-class—Statically created SRv6 TE policy group that uses service class-based traffic steering. · Static Dot1p—Statically created SRv6 TE policy group that uses 802.1p-based traffic steering. · Dynamic—Dynamically created SRv6 TE policy group. No forward type is configured. · Dynamic DSCP—Dynamically created SRv6 TE policy group that uses DSCP-based traffic steering. · Dynamic TE Class—Dynamically created SRv6 TE policy group that use TE class ID-based traffic steering. · Dynamic service-class—Dynamically created SRv6 TE policy group that use service class-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. |
|
UP/Total Mappings |
· If DSCP-based traffic steering is used, this field represents the number of valid color-to-DSCP mappings/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. · If 802.1p-based traffic steering is used, this field represents the number of valid color-to-802.1p mappings and the total number of configured color-to-802.1p mappings in the SRv6 TE policy group. · If service class-based traffic steering is used, this field represents the number of valid service class-to-forwarding policy mappings and the total number of configured service class-to-forwarding policy mappings in the SRv6 TE policy group. |
|
IPv4 Best-effort |
Status of SRv6 BE forwarding for IPv4 packets that do not match a color-to-DSCP mapping: · Configured. · Not configured. |
|
IPv6 Best-effort |
Status of SRv6 BE forwarding for IPv6 packets that do not match a color-to-DSCP mapping: · Configured. · Not configured. |
|
Color |
Color value |
|
Type |
Packet type: IPv4 or IPv6. |
|
DSCP |
DSCP value. |
|
Dot1p |
802.1p value. |
|
Service-class |
Service class 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 24 Command output
|
Field |
Description |
|
Group type |
SRv6 TE policy group type: · Static DSCP—Statically created SRv6 TE policy group that uses DSCP-based traffic steering. · Static Dot1p—Statically created SRv6 TE policy group that uses 802.1p-based traffic steering. · Static service-class—Statically created SRv6 TE policy group that uses service class-based traffic steering. · Static 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. · Dynamic service-class—Dynamically created SRv6 TE policy group that use service class-based traffic steering. |
|
Group color |
Color value of the SRv6 TE policy group. |
|
Endpoint |
Destination node IP address of the SRv6 TE policy group. |
|
Group NID |
Index of the forwarding entry for the SRv6 TE policy group. |
|
Create time |
Time when the SRv6 TE policy group state was created. |
|
Up time |
Time when the SRv6 TE policy group came up. |
|
Down time |
Time when the SRv6 TE policy group went down. |
|
Down reason |
Reason why the SRv6 TE policy group went down: · No endpoint. · No color-DSCP mappings. · No active SRv6 TE policies. · No color-Dot1p mappings—No color-to-802.1p mappings are configured. · No color-service-class mappings—No color-to-service class mappings are configured. · No color-TE Class mappings—No color-to-TE class ID mappings are configured. |
|
Color |
Color value mapped to the DSCP, 802.1p, service class, or APN ID value. |
|
Up time |
Time when the color-to-DSCP, color-to-802.1p, color-to-service class, or color-to-APN ID mapping came up. |
|
Down time |
Time when the color-to-DSCP, color-to-802.1p, color-to-service class, or color-to-APN ID mapping went down. |
|
Down reason |
Reason why the color-to-DSCP, color-to-802.1p, color-to-service class, or color-to-APN ID mapping went down. · No endpoint. · No color-DSCP mappings. · The SRv6-TE policy is used by another group. · SRv6-TE policy doesn't exist. · SRv6-TE policy down. · No color-Dot1p mappings. · No color-service-class mappings. · No color-TE Class mappings. · No selected by intelligent route policy. |
display segment-routing ipv6 te policy-group statistics
Use display segment-routing ipv6 te policy-group statistics to display SRv6 TE policy group statistics.
Syntax
display segment-routing ipv6 te policy-group statistics
Views
Any view
Predefined user roles
network-admin
network-operator
Examples
# Display SRv6 TE policy group statistics.
<Sysname> display segment-routing ipv6 te policy-group statistics
Statistics type Total Up
Dynamic DSCP groups 3 1
Static DSCP groups 2 1
Color-DSCP mappings 2 2
Static Dot1p groups 0 0
Color-Dot1p mappings 0 0
Dynamic service-class groups 0 0
Static service-class groups 1 0
Color-service-class mappings 1 0
Dynamic TE Class groups 3 1
Static TE Class groups 1 1
Color-TE Class mappings 1 1
IPR-TE Class mappings 3 2
Table 25 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. · 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. · 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. |
|
Total |
Total number of statistics objects. |
|
UP |
Number of effective statistics objects. |
display segment-routing ipv6 te sbfd
Use display segment-routing ipv6 te sbfd to display SBFD information for SRv6 TE policies.
Syntax
display segment-routing ipv6 te sbfd [ down | policy { { color color-value | end-point ipv6 ipv6-address } * | name policy-name } | up ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
down: Displays SBFD information for SRv6 TE policies in down state.
policy: Displays SBFD information for the specified SRv6 TE policy.
color color-value: Specifies the color attribute value of an SRv6 TE policy, in the range of 0 to 4294967295.
end-point ipv6 ipv6-address: Specifies the IPv6 address of the endpoint of an SRv6 TE policy.
name policy-name: Specifies the name of an SRv6 TE policy, a case-sensitive string of 1 to 59 characters.
up: Displays SBFD information for SRv6 TE policies in up state.
Usage guidelines
If you do not specify any parameters, this command displays SBFD information for all SRv6 TE policies.
Examples
# Display SBFD information for all SRv6 TE policies.
<Sysname> display segment-routing ipv6 te sbfd
Color: 10
Endpoint: 4::4
Policy name: p1
State: Up
Encapsulation mode: -
NID: 2150629378
RemoteDiscr: 1000011
Source-address: 1::1
State: Up
TimerFd: -
TimerLeftTime: -
VPNindex: 0
Templatename: -
Table 26 Command output
|
Field |
Description |
|
Color |
Color attribute value of an SRv6 TE policy. |
|
Endpoint |
Endpoint IP address of the SRv6 TE policy. |
|
Policy name |
Name of the SRv6 TE policy. |
|
State |
SBFD session state: · Up. · Down. · Delete. |
|
Nid |
Forwarding entry index for an SID list. |
|
BFD type |
The current software version supports only the SBFD type. |
|
Encapsulation mode |
Encapsulation mode for SBFD packets: · Encaps—Normal encapsulation mode. · Insert—Insertion encapsulation mode. · Insert no endpoint—Insertion without endpoint encapsulation mode If the encapsulation mode for SBFD packets is not configured, this field displays a hyphen (-). |
|
Remote Discr |
Remote discriminator. |
|
Source-address |
Source address of BFD packets, which is configured by using the source-address command. This field displays a hyphen (-) if no source address is configured. |
|
Timer |
SBFD session timer, in seconds. |
|
State |
SRv6 TE policy state: · Up. · Down. · Delete. |
|
BFD type |
The current software version supports only the SBFD type. |
|
Encapsulation mode |
Encapsulation mode for SBFD packets: · Encaps—Normal encapsulation mode. · Insert—Insertion encapsulation mode. · Insert no endpoint—Insertion without endpoint encapsulation mode If the encapsulation mode for SBFD packets is not configured, this field displays a hyphen (-). |
|
NID |
Forwarding entry index for an SID list. |
|
Remote Discr |
Remote discriminator. |
|
Source-address |
Source address of BFD packets, which is configured by using the source-address command. This field displays a hyphen (-) if no source address is configured. |
|
State |
SBFD session state: · Up. · Down. · Delete. |
|
TimerFd |
SBFD session timer, in seconds. |
|
TimerLeftTime |
Remaining time of the SBFD session timer, in seconds. |
|
VPN index |
VPN instance index. |
|
Template name |
SBFD template name. |
display segment-routing ipv6 te segment-list
Use display segment-routing ipv6 te segment-list to display SRv6-TE SID list information.
Syntax
display segment-routing ipv6 te segment-list [ name seglist-name | id id-value ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
name segment-list-name: Specifies a SID list by its name, a case-sensitive string of 1 to 128 characters.
id id-value: Specifies a SID list by its ID. The value range for the SID list ID is 1 to 4294967295.
Usage guidelines
If you do not specify a SID list name or ID, this command displays information about all SRv6-TE SID lists.
To view SID list ID information, execute the display segment-routing ipv6 te policy command.
Examples
# Display information about all SRv6-TE SID lists.
<Sysname> display segment-routing ipv6 te segment-list
Total Segment lists: 1
Name/ID: A/1
Origin: CLI
Status: Up
Verification State: Down
Nodes: 1
Flags: None
Local BSID: -
Reverse BSID: -
Reference counts: 0
Index : 1 SID: 1::2
Status : Up TopoStatus: Nonexistent
Type : Type 2 Flags: None
Coc Type : - Common prefix length: 0
Table 27 Command output
|
Field |
Description |
|
Total Segment lists |
Number of SID lists. |
|
Name/ID |
SID list name/ID. |
|
Origin |
Origin of the SID list. Options include: · CLI—Locally configured in the CLI. · BGP—Issued by BGP. · PCE—Issued by a PCE. · Dynamic—Dynamically calculated by the source node. If the SID list does not have a valid origin, this field displays a hyphen (-). |
|
Status |
SID list status, Down or Up. |
|
Verification State |
Verification result of the SID list: · Down—The verification fails. · Up—The verification succeeds. |
|
Nodes |
Number of nodes in the SID list. |
|
Flags |
Flags bit of the node. · None—No flags. · V—Verifies the validity of the SID during SRv6 TE policy path verification. |
|
Reference counts |
Number of times that the SID list has been referenced. |
|
Index |
Node index. |
|
SID |
SID value (IPv6 address) of the node. |
|
Status |
SID list status: Down, Up, or unknown (-). |
|
TopoStatus |
Whether the SID exists in the IGP topology: · Existent. · Nonexistent. |
|
Type |
SID type of the node: · None—Not configured. · Type 2—IPv6 address. |
|
Flags |
Node flags, which are not defined and displayed as None. |
|
COC type |
Compression type of the SID, which is COC32, representing the 32-bit compression. If the SID is not compressed, this field displays a hyphen (-). |
|
Common prefix length |
Common prefix length of the G-SID. |
|
Function length |
Length of the SID function. |
|
Args length |
Args length for the specified SRv6 SID. |
|
Endpoint Behavior |
Endpoint behavior: · End (no PSP, no USP) · End with PSP · End with USP · End with PSP&USP · End.X (no PSP, no USP) · End.X with PSP · End.X with USP · End.X with PSP&USP · End.T (no PSP, no USP) · End.T with PSP · End.T with USP · End.T with PSP&USP · End with USD · End with PSP&USD · End with USP&USD · End with PSP&USP&USD · End.X with USD · End.X with PSP&USD · End.X with USP&USD · End.X with PSP&USP&USD · End.T with USD · End.T with PSP&USD · End.T with USP&USD · End.T with PSP&USP&USD · End with COC · End with PSP&COC · End with PSP&USP&COC · End.X with COC · End.X with PSP&COC · End.X with PSP&USP&COC · End.T with COC · End.T with PSP&COC · End.T with PSP&USP&COC · End with PSP&USD&COC · End with PSP&USP&USD&COC · End.X with PSP&USD&COC · End.X with PSP&USP&USD&COC · End.T with PSP&USD&COC · End.T with PSP&USP&USD&COC This field displays a hyphen (-) for an invalid endpoint behavior. |
display segment-routing ipv6 te source-sid
Use display segment-routing ipv6 te source-sid to display information about SRv6 SIDs collected from the LS database.
Syntax
display segment-routing ipv6 te source-sid [ end | end-x | sid ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
end: Displays End SID information.
end-x: Displays End.X SID information.
sid: Displays SRv6 SID information.
Usage guidelines
If you do not specify any parameters, this command displays information about all SRv6 SIDs collected from the LS database.
Examples
# Display information about all SRv6 SIDs collected from the LS database.
<Sysname> display segment-routing ipv6 te source-sid
SID : 11::1:0:8, Count: 1
Type : End.X(LAN), Topology ID: 0
Instance ID: 0
Source : IS-IS, ProcID 100, IS-Level-1
Node : 0000.0000.0019.00
Local : 0000.0000.0019.00
Peer : 0000.0000.0022.01
SID : 12:1:2:3:0:1::, Count: 2
Type : End, Topology ID: 0
Instance ID: 0
Source : IS-IS, ProcID 100, IS-Level-1
Node : 0000.0000.0019.00
Type : End, Topology ID: 2
Instance ID: 0
Source : IS-IS, ProcID 100, IS-Level-1
Node : 0000.0000.0019.00
SID : 12:1:2:3:0:6::, Count: 2
Type : End.X, Topology ID: 0
Instance ID: 0
Source : IS-IS, ProcID 100, IS-Level-1
Node : 0000.0000.0019.00
Local : 2001:1::2
Peer : 2001:1::16
Type : End.X, Topology ID: 2
Instance ID: 0
Source : IS-IS, ProcID 100, IS-Level-1
Node : 0000.0000.0019.00
Local : 2001:1::2
Peer : 2001:1::16
Table 28 Command output
|
Field |
Description |
|
SID |
SRv6 SID. |
|
Count |
Number of advertising sources for the SID. |
|
Type |
SID type: · End. · End.X. · End.X (LAN). |
|
ProcID |
Process ID. |
|
IS-Level-X |
IS level on the node: IS-Level-1 or IS-Level-2. |
|
Node |
Node where the SID advertising source resides. |
|
Local |
For an End.X SID, this field displays the system ID of the IS-IS process to which the SID-associated local interface belongs. If the link type is P2P and the IPv6 link attribute is enabled for the IS-IS process, this field displays the IPv6 address of the SID-associated local interface. |
|
Peer |
For an End.X SID, this field displays the system ID of the IS-IS process to which the SID-associated neighbor interface belongs. If the link type is P2P and the IPv6 link attribute is enabled for the IS-IS process, this field displays the IPv6 address of the SID-associated neighbor interface. |
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
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 29 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, |
|
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
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
Use drop-upon-invalid to configure the device to drop traffic when an SRv6 TE policy becomes invalid.
Use undo drop-upon-invalid to restore the default.
Syntax
drop-upon-invalid { disable | enable }
undo drop-upon-invalid
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
Parameters
disable: Disables dropping traffic when the SRv6 TE policy becomes invalid.
enable: Enables dropping traffic when the SRv6 TE policy becomes invalid.
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 if 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.
The drop-upon-invalid command configured on the remote device does not affect an SRv6 TE policy generated based on a BGP SRv6 TE policy route. The SRv6 TE policy is controlled by only the drop-upon-invalid command configured on the local device.
You can enable the drop-upon-invalid feature 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 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
Related commands
srv6-policy drop-upon-invalid
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
best-effort match service-class (service class forward type view)
best-effort match service-class (SRv6 TE policy group view)
color match dscp (DSCP forward type view)
color match dscp (SRv6 TE policy group view)
color match dot1p
color match service-class (service class forward type view)
color match service-class (SRv6 TE policy group view)
forward-type (SRv6 TE ODN policy group view)
forward-type (SRv6 TE policy group view)
dynamic (SRv6 TE policy path preference view)
Use dynamic to create and enter SRv6 TE policy path preference dynamic view, or enter the existing SRv6 TE policy path preference dynamic view.
Use undo dynamic to delete the SRv6 TE policy path preference dynamic view and all the configuration in the view.
Syntax
dynamic
undo dynamic
Default
The SRv6 TE policy path preference dynamic view does not exist.
Views
SRv6 TE policy path preference view
Predefined user roles
network-admin
Usage guidelines
In SRv6 TE policy path preference dynamic view, you can enable the device to dynamically create SID lists for an SRv6 TE policy candidate path.
Examples
# Create and enter SRv6 TE policy path preference dynamic view.
<Sysname> system-view
[Sysname] segment-routing ipv6
[Sysname-segment-routing-ipv6] traffic-engineering
[Sysname-srv6-te] policy 1
[Sysname-srv6-te-policy-1] candidate-paths
[Sysname-srv6-te-policy-1-path] preference 20
[Sysname-srv6-te-policy-1-path-pref-20] dynamic
[Sysname-srv6-te-policy-1-path-pref-20-dyna]
dynamic (SRv6-TE-ODN view)
Use dynamic to create and enter SRv6-TE-ODN dynamic view, or enter the existing SRv6-TE-ODN dynamic view.
Use undo dynamic to delete the SRv6-TE-ODN dynamic view and all the configuration in the view.
Syntax
dynamic
undo dynamic
Default
The SRv6-TE-ODN dynamic view does not exist.
Views
SRv6-TE-ODN view
Predefined user roles
network-admin
Usage guidelines
In SRv6-TE-ODN dynamic view, you can enable dynamic generation of SRv6 TE policies and dynamic generation of SID lists for SRv6 TE policy candidate paths.
Examples
# Create and enter SRv6-TE-ODN dynamic 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] dynamic
[Sysname-srv6-te-odn-1-dynamic]
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
When the device forwards a packet through an SRv6 TE policy, it must encapsulate that packet with the SID list of the SRv6 TE policy. Supported encapsulation modes include:
· 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. 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.
· 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. 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.
· 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 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.
· 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. 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.
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, 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. If you do not specify this keyword, the local End.X SID will be encapsulated into the SRH of the packets.
Usage guidelines
If traffic is steered to an SRv6 TE policy 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 does not have policy-specific configuration.
If you configure the local End.X SID encapsulation and also enable the reduced encapsulation mode by using the encapsulation-mode encaps reduced command in SRv6 TE policy view, the local End.X SID encapsulation applies.
Examples
# Include the End.X SID in the SRH of the packets forwarded by 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] 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 traffic is steered to an SRv6 TE policy 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 alternately for an SRv6 TE policy, the most recent configuration takes effect.
In SRv6 TE policy view, if you execute both the encapsulation-mode insert include local-end.x command and the encapsulation-mode encaps reduced command, 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
exclude-any
Use exclude-any to configure the exclude-any affinity attribute rule and enter affinity attribute rule view, or enter the view of the existing affinity attribute rule.
Use undo exclude-any to delete the affinity attribute rule view and all configurations in the view.
Syntax
exclude-any
undo exclude-any
Default
No affinity attribute rules exist.
Views
Affinity attribute view
Predefined user roles
network-admin
Usage guidelines
With the exclude-any affinity attribute rule configured, an SRv6 TE policy does not use a link if it contains any of the specific affinity attributes.
Examples
# Configure the exclude-any affinity attribute rule and enter affinity attribute rule view.
<Sysname> system-view
[Sysname] segment-routing ipv6
[Sysname-segment-routing-ipv6] traffic-engineering
[Sysname-srv6-te] policy a1
[Sysname-srv6-te-policy-a1] candidate-paths
[Sysname-srv6-te-policy-a1-path] preference 200
[Sysname-srv6-te-policy-a1-path-pref-200] constraints
[Sysname-srv6-te-policy-a1-path-pref-200-const] affinity
[Sysname-srv6-te-policy-a1-path-pref-200-const-aff] exclude-any
[Sysname-srv6-te-policy-a1-path-pref-200-const-aff-exclude-any]
Related commands
affinity (SRv6 TE policy constraints view)
explicit segment-list
Use explicit segment-list to specify a SID list for a candidate path.
Use undo explicit segment-list to delete a SID list of a candidate path or restore the default weight and global path MTU of a SID list.
Syntax
explicit segment-list segment-list-name [ local-binding-sid ipv6 ipv6-address | path-mtu mtu-value | reverse-binding-sid ipv6 ipv6-address | weight weight-value ] *
undo explicit segment-list segment-list-name [ local-binding-sid | path-mtu | reverse-binding-sid | weight ] *
Default
No SID lists are specified for an SRv6 TE policy candidate path.
Views
SRv6 TE policy path preference view
Predefined user roles
network-admin
Parameters
segment-list-name: Specifies a primary SID list name, a case-sensitive string of 1 to 128 characters.
local-binding-sid ipv6 ipv6-address: Specifies a local BSID for BFD detection. If you do not specify this option, the local BSID configured for the SID list applies.
· The specified BSID cannot be the same as the BSID configured with the local-binding-sid command for the SID list.
· The BSID specified in this option takes precedence over the BSID configured with the local-binding-sid command for the SID list.
path-mtu mtu-value: Specifies the path MTU (in bytes) for the primary SID list. The value range for the path MTU is 1280 to 9600. If you do not specify this option, the global path MTU set in SRv6 view applies to the SID list.
reverse-binding-sid ipv6 ipv6-address: Specifies a reverse BSID for BFD or SBFD detection. If you do not specify this option, the reverse BSID configured for the SID list applies.
· The specified BSID cannot be the same as the BSID configured with the reverse-binding-sid command for the SID list.
· The BSID specified in this option takes precedence over the BSID configured with the reverse-binding-sid command for the SID list.
weight weight-value: Specifies a weight for the primary SID list, in the range of 1 to 4294967295. The default weight is 1.
Usage guidelines
An SRv6 TE policy uses the SID list specified for the highest-preference candidate path as a traffic forwarding subpath.
An SRv6 TE policy candidate path can have multiple SID lists. All the SID lists can be used to forward traffic for load sharing based on their weights. Assume SID lists a, b, and c are assigned weights x, y, z, respectively. The load of SID list a is x/(x+y+z) of the total traffic.
If you assign weight values for the same SID list multiple times, the most recent configuration takes effect.
You can configure the path MTU for all SRv6-TE candidate paths globally in SRv6 view or for a specific forwarding path in SRv6 TE policy path preference view. The path-specific configuration takes precedence over the global configuration. A forwarding path identified by a SID list of an SRv6 TE policy uses the global configuration only when it has no path-specific configuration.
The path MTU of a SID list minus the global reserved path MTU is the active MTU of the SID list. The source node uses the active MTU of the SID list or the IPv6 MTU of the physical interface, whichever is smaller, as the actual MTU to send packets. The active MTU of a SID list must be greater than or equal to 1280 bytes.
Examples
# Configure SID list abc for the SRv6 TE policy candidate path with preference 20, and the set the SID list weight to 20.
<Sysname> system-view
[Sysname] segment-routing ipv6
[Sysname-segment-routing-ipv6] traffic-engineering
[Sysname-srv6-te] policy a1
[Sysname-srv6-te-policy-a1] candidate-paths
[Sysname-srv6-te-policy-a1-path] preference 20
[Sysname-srv6-te-policy-a1-path-pref-20] explicit segment-list abc weight 20
Related commands
path-mtu
segment-list
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
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
After enabling 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
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 | service-class | te-class }
undo forward-type { dscp | service-class | 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.
service-class: Specifies the service class forward type, that is, service class-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 DSCP-, TE class ID-, and service class-based traffic steering in the current software version.
When the forward type is DSCP, the device steers traffic by using the following procedure:
1. Identifies the color attribute associated with the DSCP value of the packet.
2. Locates an SRv6 TE policy in the SRv6 TE policy group based on the color attribute of the packet.
3. Forwards the packet with the DSCP value through that SRv6 TE policy.
When the forward type is service class, the device steers traffic by using the following procedure:
1. Matches the service class value in the traffic with the mappings configured by using the color match service-class and best-effort match service-class commands.
2. Forwards the traffic based on the matching result.
¡ If the service class value matches a color-to-service class mapping, the device uses the SRv6 TE policy with the color attribute value mapped to the service class value to forward the traffic in case that the SRv6 TE policy is valid.
¡ If the service class value is found among the service class values specified in the best-effort match service-class command, the device forwards the traffic in SRv6 BE mode. In this mode, the device encapsulates a new IPv6 header to packets and performs an IPv6 routing table lookup to forward the encapsulated packets.
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 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. You can also use the remark service-class command in a QoS policy to mark the service class 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
remark service-class (ACL and QoS Command Reference)
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-type { dot1p | service-class | te-class }
undo forward-type { dot1p | service-class | te-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
dot1p: Specifies the Dot1p forward type, that is, 802.1p-based traffic steering.
service-class: Specifies the service class forward type, that is, service class-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 a statically created SRv6 TE policy group. Statically created SRv6 TE policy groups only support DSCP-, TE class ID-, 802.1p-, and service class-based traffic steering in the current software version.
On the source node of the SRv6 TE policy group, you can 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. You can also use the remark service-class command in a QoS policy to mark the service class value for traffic that matches rules in the QoS policy.
When the forward type is DSCP or Dot1p, the device steers traffic by using the following procedure:
1. Identifies the color attribute based on the DSCP value or 802.1p value of the packet.
2. Locates an SRv6 TE policy in the SRv6 TE policy group based on the color attribute of the packet.
3. Forwards the packet with the DSCP value or 802.1p value through the specified SRv6 TE policy.
When the forward type is service class, the device steers traffic by using the following procedure:
1. Matches the service class value in the traffic with the mappings configured by using the color match service-class and best-effort match service-class commands.
2. Forwards the traffic based on the matching result.
¡ If the service class value matches a color-to-service class mapping, the device uses the SRv6 TE policy with the color attribute value mapped to the service class value to forward the traffic in case that the SRv6 TE policy is valid.
¡ If the service class value is found among the service class values specified in the best-effort match service-class command, the device forwards the traffic in SRv6 BE mode. In this mode, the device encapsulates a new IPv6 header to packets and performs an IPv6 routing table lookup to forward the encapsulated packets.
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.
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
# Specify Dot1p-based traffic steering for SRv6 TE policy group 1.
<Sysname> system-view
[Sysname] segment-routing ipv6
[Sysname-segment-routing-ipv6] traffic-engineering
[Sysname-srv6-te] policy-group 1
[Sysname-srv6-te-policy-group-1] forward-type dot1p
Related commands
remark service-class (ACL and QoS Command Reference)
remark te-class (ACL and QoS Command Reference)
forwarding ignore-last-sid
Use forwarding ignore-last-sid to enable the SRv6 TE policy to forward packets without using the last SID in the SID list.
Use undo forwarding ignore-last-sid to restore the default.
Syntax
forwarding ignore-last-sid { disable | enable }
undo forwarding ignore-last-sid
Default
The feature is not configured. The configuration in SRv6 TE view applies.
Views
SRv6 TE policy view
Predefined user roles
network-admin
Parameters
disable: Disables the feature of forwarding packets without using the last SID in the SID list of the SRv6 TE policy.
enable: Enables the SRv6 TE policy to forward packets without using the last SID in the SID list.
Usage guidelines
In an SRv6 VPN scenario, to forward a public network packet through the SRv6 TE policy, the device encapsulates an SRH into the packet. The SRH contains the SID list of the SRv6 TE policy and the SID assigned to the VPN instance or public network instance (End.DT4 SID, for example). Both the last SID in the SID list and the End.DT4 SID are used to identify the egress node. To reduce the SRv6 packet size, you can configure this command to use only the End.DT4 SID to identify the egress node.
You can configure this feature 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 SRv6 TE policy 1 to forward packets without using the last SID in the SID list.
<Sysname> system-view
[Sysname] segment-routing ipv6
[Sysname-segment-routing-ipv6] traffic-engineering
[Sysname-srv6-te] policy 1
[Sysname-srv6-te-policy-1] forwarding ignore-last-sid enable
Related commands
srv6-policy forwarding ignore-last-sid
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
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 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 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.
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 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 the ifit measure mode command is executed in SRv6 TE policy view and the srv6-policy ifit measure mode command is executed 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] 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 BGP IPv6 SR 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
include-all
Use include-all to configure the include-all affinity attribute rule and enter affinity attribute rule view, or enter the view of the existing affinity attribute rule.
Use undo include-all to delete the affinity attribute rule view and all configurations in the view.
Syntax
include-all
undo include-all
Default
No affinity attribute rules exist.
Views
Affinity attribute view
Predefined user roles
network-admin
Usage guidelines
With the include-all affinity attribute rule configured, an SRv6 TE policy uses a link only if it contains all of the specific affinity attributes.
Examples
# Configure the include-all affinity attribute rule and enter affinity attribute rule view.
<Sysname> system-view
[Sysname] segment-routing ipv6
[Sysname-segment-routing-ipv6] traffic-engineering
[Sysname-srv6-te] policy a1
[Sysname-srv6-te-policy-a1] candidate-paths
[Sysname-srv6-te-policy-a1-path] preference 200
[Sysname-srv6-te-policy-a1-path-pref-200] constraints
[Sysname-srv6-te-policy-a1-path-pref-200-const] affinity
[Sysname-srv6-te-policy-a1-path-pref-200-const-aff] include-all
[Sysname-srv6-te-policy-a1-path-pref-200-const-aff-include-all]
Related commands
affinity (SRv6 TE policy constraints view)
include-any
Use include-any to configure the include-any affinity attribute rule and enter affinity attribute rule view, or enter the view of the existing affinity attribute rule.
Use undo include-any to delete the affinity attribute rule view and all configurations in the view.
Syntax
include-any
undo include-any
Default
No affinity attribute rules exist.
Views
Affinity attribute view
Predefined user roles
network-admin
Usage guidelines
With the include-any affinity attribute rule configured, an SRv6 TE policy uses a link only if it contains any of the specific affinity attributes.
Examples
# Configure the include-any affinity attribute rule and enter affinity attribute rule view.
<Sysname> system-view
[Sysname] segment-routing
[Sysname-segment-routing] traffic-engineering
[Sysname-sr-te] policy a1
[Sysname-sr-te-policy-a1] candidate-paths
[Sysname-sr-te-policy-a1-path] preference 200
[Sysname-sr-te-policy-a1-path-pref-200] constraints
[Sysname-sr-te-policy-a1-path-pref-200-const] affinity
[Sysname-sr-te-policy-a1-path-pref-200-const-aff] include-any
[Sysname-sr-te-policy-a1-path-pref-200-const-aff-rule]
Related commands
affinity (SRv6 TE policy constraints view)
index
Use index to add a node to a SID list.
Use undo index to delete a node from a SID list.
Syntax
index index-number ipv6 ipv6-address [ verification ]
index index-number coc32 ipv6 ipv6-address common-prefix-length [ verification ]
index index-number ipv6 ipv6-address flavor flavor-number lb-length ln-length function-length args-length [ verification ]
undo index index-number
Default
No nodes exist in a SID list.
Views
SID list view
Predefined user roles
network-admin
Parameters
index-number: Specifies the node index, in the range of 1 to 65535.
ipv6 ipv6-address: Specifies the IPv6 address of the node.
coc32: Adds the COC flavor. It indicates that the next node of the current node is a 32-bit G-SID.
common-prefix-length: Specifies the length of the common prefix of the next G-SID. The value range for this argument is 1 to 94.
verification: Enables SID validity verification. A SID is valid if the SID exists in the topology and the associated locator network route is routable. If you do not specify this keyword, path verification does not verify the validity of the SID. Do not specify this keyword for the BSID or a SID not in the local AS. If you do so, path verification will determine that the segment list has failed, affecting packet forwarding.
flavor flavor-number: Specifies an SRv6 SID type and flavor. The flavor-number argument represents the number of the SRv6 SID type and flavor, which is defined by RFC. The value range for this argument is 0 to 65535. For more information about SRv6 SID types and flavors, see Table 30.
Table 30 SRv6 SID types and flavors
|
Value |
SRv6 SID type and flavor |
|
1 |
End |
|
2 |
End with PSP |
|
3 |
End with USP |
|
4 |
End with PSP&USP |
|
5 |
End.X |
|
6 |
End.X with PSP |
|
7 |
End.X with USP |
|
8 |
End.X with PSP&USP |
|
9 |
End.T |
|
10 |
End.T with PSP |
|
11 |
End.T with USP |
|
12 |
End.T with PSP&USP |
|
14 |
End.B6.Encaps |
|
15 |
End.BM |
|
16 |
End.DX6 |
|
17 |
End.DX4 |
|
18 |
End.DT6 |
|
19 |
End.DT4 |
|
20 |
End.DT46 |
|
21 |
End.DX2 |
|
22 |
End.DX2V |
|
23 |
End.DT2U |
|
24 |
End.DT2M |
|
27 |
End.B6.Encaps.Red |
|
28 |
End with USD |
|
29 |
End with PSP&USD |
|
30 |
End with USP&USD |
|
31 |
End with PSP,USP&USD |
|
32 |
End.X with USD |
|
33 |
End.X with PSP&USD |
|
34 |
End.X with USP&USD |
|
35 |
End.X with PSP,USP&USD |
|
36 |
End.T with USD |
|
37 |
End.T with PSP&USD |
|
38 |
End.T with USP&USD |
|
39 |
End.T with PSP,USP&USD |
|
101 |
End with COC |
|
102 |
End with PSP&COC |
|
104 |
End with PSP&USP&COC |
|
105 |
End.X with COC |
|
106 |
End.X with PSP&COC |
|
108 |
End.X with PSP&USP&COC |
|
109 |
End.T with COC |
|
110 |
End.T with PSP&COC |
|
112 |
End.T with PSP&USP&COC |
|
130 |
End with PSP&USD&COC |
|
131 |
End with PSP&USP&USD&COC |
|
133 |
End.X with PSP&USD&COC |
|
135 |
End.X with PSP&USP&USD&COC |
|
137 |
End.T with PSP&USD&COC |
|
139 |
End.T with PSP&USP&USD&COC |
|
32767 |
Real-time transport protocol |
|
Others |
Reserved or not specified |
lb-length: Specifies the common prefix length of the SRv6 G-SID, in the range of 0 to 128 bits.
ln-length: Specifies the node ID length of the SRv6 G-SID, in the range of 0 to 128 bits.
function-length: Specifies the length of the Function field in the SRv6 G-SID. The value range for this argument is 0 to 128, in bits. The length of the Function field equals to the sum of the length of the dynamic portion and the length of the static portion.
args-length: Specifies the Arguments length of the SRv6 G-SID, in the range of 0 to 64 bits.
Usage guidelines
Operating mechanism
After you execute this command to add SID nodes to a SID list, the SID nodes form an explicit path for traffic forwarding. That is, traffic matching the SID list must pass through all the SID nodes in sequence.
To use a controller to deploy an SID list that contains G-SID nodes to a forwarding device, perform the following operations on the controller:
· Use the index index-number ipv6 ipv6-address flavor flavor-number lb-length ln-length function-length args-length command on the controller to add the G-SID nodes to the SID list to form an explicit path.
· Deploy the path to the forwarding device through a BGP IPv6 SR policy route.
Then, traffic matching the SID list on the forwarding device will be forwarded to the G-SID nodes in the SID list in sequence.
Restrictions and guidelines
When you add G-SIDs to a SID list, the value for the common-prefix-length or lb-length argument configured by this command must be the same as that of the locator where the next node belongs.
When you add G-SIDs to a SID list, make sure the following conditions are met:
· The SRv6 SID for the previous node of the G-SID must be End(COC32) SID or End.X(COC32) SID.
· The SRv6 SID for the last node does not contain the COC flavor.
If multiple SRv6 TE policies have a common path, you can configure the common path as an SRv6 TE policy. When you configure the SRv6 TE policies, you can add the BSID of the common SRv6 TE policy to the SID lists of the SRv6 TE policies. In this way, you recurse the SRv6 TE policies to the common SRv6 TE policy, simplifying the SID list configuration.
If the first SID in the SID list of an SRv6 TE policy is a BSID, note the following restrictions and guidelines:
· Nested SRv6 TE policy recursions are not supported, that is, the first SID in the SID list of the recursion SRv6 TE policy (the SRv6 TE policy with that BSID) cannot be a BSID.
· The first SID cannot be the BSID of this SRv6 TE policy itself.
· Do not configure path connectivity verification for this SRv6 TE policy.
· The BSID cannot be configured as a local BSID or a reverse BSID.
· The traffic statistics, BFD, and SBFD features of this SRv6 TE policy are not affected by the status of those features for the recursion SRv6 TE policy.
· The BFD/SBFD detection time of this SRv6 TE policy cannot be shorter than that of the recursion SRv6 TE policy.
· The path MTU of this SRv6 TE policy cannot be smaller than that of the recursion SRv6 TE policy.
After path connectivity verification is enabled for an SRv6 TE policy, the device verifies the validity of all SIDs in the SID list. If the SID list contains an inter-AS SID (for example, the BGP Peer SID allocated by BGP EPE) or contains the BSID of another SRv6 TE policy, the path connectivity verification will fail. This is because a BSID or BGP Peer SID cannot be flooded in the IGP topology.
To resolve this issue, you can execute the following commands to configure the path connectivity verification only verifies the validity of specific SIDs:
· Use the index command to specify the verification keyword for the SIDs to be verified. Do not specify this keyword for a BSID or BGP EPE SID in the SID list.
· Specify the specified-sid keyword when you execute the path verification command in SRv6 TE policy view or the srv6-policy path verification enable command in SRv6 TE view.
Examples
# Add a node to SID list abc, and set the node index to 1 and IPv6 address to 1000::1.
<Sysname> system-view
[Sysname] segment-routing ipv6
[Sysname-segment-routing-ipv6] traffic-engineering
[Sysname-srv6-te] segment-list abc
[Sysname-srv6-te-sl-abc] index 1 ipv6 1000::1
# Add nodes to SID list text as follows:
· Add a node whose index is 10, IPv6 address is 100::1, next node as 32-bit G-SID, and the common prefix length of the G-SID is 64.
· Add a node whose index is 20, IPv6 address is 200::1:0:0, next node as 32-bit G-SID, and the common prefix length of the G-SID is 64.
· Add a node whose index is 30, IPv6 address is 200::2:0:0, next node as 32-bit G-SID, and the common prefix length of the G-SID is 64.
· Add a node whose index is 40, IPv6 address is 200::3:0:0, next node as 32-bit G-SID, and the common prefix length of the G-SID is 64.
· Add a node whose index is 50 and IPv6 address is 200::4:0:0.
· Add a node whose index is 60 and IPv6 address is 300::3.
<Sysname> system-view
[Sysname] segment-routing ipv6
[Sysname-segment-routing-ipv6] traffic-engineering
[Sysname-srv6-te] segment-list text
[Sysname-srv6-te-sl-abc] index 10 coc32 ipv6 100::1 64
[Sysname-srv6-te-sl-abc] index 20 coc32 ipv6 200::1:0:0 64
[Sysname-srv6-te-sl-abc] index 30 coc32 ipv6 200::2:0:0 64
[Sysname-srv6-te-sl-abc] index 40 coc32 ipv6 200::3:0:0: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
srv6 compress enable
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.
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 is 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. 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, 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. If no mappings are configured between TE class IDs and SRv6 TE policies or IPR policies or between TE class IDs and the SRv6 BE mode in the SRv6 TE policy group, or the mapping with the smallest index value is invalid, the device proceeds to the next step.
4. Performs an IPv6 routing table lookup to forward the packet if the packet does not meet any of the previous conditions.
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
maximum-sid-depth
Use maximum-sid-depth to configure the maximum depth for the SID label stack.
Use undo maximum-sid-depth to restore the default.
Syntax
maximum-sid-depth value
undo maximum-sid-depth
Default
The maximum depth for the SID label stack is not configured.
Views
SRv6 TE ODN view
Predefined user roles
network-admin
Parameters
value: Specifies the maximum depth for the SID label stack, in the range of 1 to 255.
Usage guidelines
To implement dynamic path calculation for ODN-generated SRv6 TE policies, use this command to control the number of SIDs in the SID lists for the candidate paths of the SRv6 TE policies.
The actual effective SID label stack depth takes the smaller value among the following settings:
· Maximum depth of the SID label stack configured in this command.
· Default setting for this command.
Examples
# Configure the maximum depth of the SID label stack as 10.
<Sysname> system-view
[Sysname] segment-routing ipv6
[Sysname-segment-routing-ipv6] traffic-engineering
[Sysname-srv6-te] on-demand color 1
[Sysname-srv6-te-odn-1] maximum-sid-depth 10
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
The echo BFD or SBFD detection feature detects the state of the SRv6 TE policy forwarding path. Using the echo BFD or SBFD protocol packets for an SRv6 TE policy, iFIT measurement can obtain network quality parameters from the source node to the endpoint node of the SRv6 TE policy, and the return trip of the endpoint node to the source node.
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 from the SRv6 TE policy source node to the endpoint node as the measurement of network quality data.
· Two-way mode—IPR uses the average of round-trip iFIT data collected from the SRv6 TE policy source node to the endpoint node and from the endpoint node back to the source node as the measurement of network quality data.
If the two-way mode is specified, iFIT cannot accurately measure the packet loss rate of the SRv6 TE policy tunnel. Therefore, the packet loss rate data still uses the measurement results of the one-way mode.
Examples
# Specify the two-way data calculation mode for IPR.
[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
metric
Use metric to create a metric type and enter its view, or enter the view of an existing metric type.
Use undo metric to delete the metric type view and all the configuration in the view.
Syntax
metric
undo metric
Default
No metric types exist.
Views
SRv6 TE policy path preference dynamic view
SRv6 TE ODN dynamic view
Predefined user roles
network-admin
Usage guidelines
Use this command to specify the method for implementing dynamic path calculation for SRv6 TE policies.
Examples
# In SRv6 TE policy path preference dynamic view, create a metric type and enter metric type view.
<Sysname> system-view
[Sysname] segment-routing ipv6
[Sysname-segment-routing] traffic-engineering
[Sysname-srv6-te] policy 1
[Sysname-srv6-te-policy-1] candidate-paths
[Sysname-srv6-te-policy-1-path] preference 20
[Sysname-srv6-te-policy-1-path-pref-20] dynamic
[Sysname-srv6-te-policy-1-path-pref-20-dyna] metric
[Sysname-srv6-te-policy-1-path-pref-20-dyna-metric]
# In SRv6 TE ODN dynamic view, create a metric type and enter metric type view.
<Sysname> system-view
[Sysname] segment-routing ipv6
[Sysname-segment-routing] traffic-engineering
[Sysname-srv6-te] on-demand color 1
[Sysname-srv6-te-odn-1] dynamic
[Sysname-srv6-te-odn-1-dynamic] metric
[Sysname-srv6-te-odn-1-dynamic-metric]
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
name
Use name to specify an affinity attribute for an affinity attribute rule.
Use undo name to restore the default.
Syntax
name name
undo name name
Default
No affinity attribute is specified for an affinity attribute rule.
Views
Affinity attribute rule view
SRv6 TE ODN dynamic affinity attribute rule view
Predefined user roles
network-admin
Parameters
name: Specifies an affinity attribute by its name, a case-sensitive string of 1 to 32 characters.
Usage guidelines
This command enables the SRv6 TE policy to select links containing the bit values associated with the specified affinity attribute as required by the affinity attribute rule.
· Link attribute—A 32-bit binary number. Each bit represents an attribute with a value of 0 or 1.
· Affinity attribute bit position—The value range is 0 to 32. When the affinity attribute value is N, it is compared with the N+1 bit of the link attribute. The affinity attribute applies to the link only if the N+1 bit value of the link attribute is 1.
For example, for affinity attribute names blue and red, if you configure the name blue bit-position 1 and name red bit-position 5 commands, the link selection varies by affinity attribute rule type:
· For the include-any affinity attribute rule, a link is available for use if the link attribute has the second bit (associated with affinity attribute blue) or sixth bit (associated with affinity attribute red) set to 1.
· For the include-all affinity attribute rule, a link is available for use if the link attribute has both the second bit (associated with affinity attribute blue) and sixth bit (associated with affinity attribute red) set to 1.
· For the exclude-any affinity attribute rule, a link is not available for use if the link attribute has the second bit (associated with affinity attribute blue) or sixth bit (associated with affinity attribute red) set to 1.
Examples
# In affinity attribute rule view, specify affinity attribute red for the include-any affinity attribute rule.
<Sysname> system-view
[Sysname] segment-routing-ipv6
[Sysname-segment-routing-ipv6] traffic-engineering
[Sysname-srv6-te] policy a1
[Sysname-srv6-te-policy-a1] candidate-paths
[Sysname-srv6-te-policy-a1-path] preference 200
[Sysname-srv6-te-policy-a1-path-pref-200] constraints
[Sysname-srv6-te-policy-a1-path-pref-200-const] affinity
[Sysname-srv6-te-policy-a1-path-pref-200-const-aff] include-any
[Sysname-srv6-te-policy-a1-path-pref-200-const-aff-include-any] name red
# In SRv6 TE ODN dynamic affinity attribute rule view, specify affinity attribute red for the include-any affinity attribute rule.
<Sysname> system-view
[Sysname] segment-routing-ipv6
[Sysname-segment-routing-ipv6] traffic-engineering
[Sysname-srv6-te] on-demand color 1
[Sysname-srv6-te-odn-1] dynamic
[Sysname-srv6-te-odn-1-dynamic] affinity include-any
[Sysname-srv6-te-odn-1-dynamic-aff-include-any] name red
Related commands
mpls te link-attribute (MPLS Command Reference)
name bit-position
name bit-position
Use name bit-position to create a name-to-bit mapping for an affinity attribute.
Use undo name bit-position to restore the default.
Syntax
name name bit-position bit-position-number
undo name name bit-position
Default
No name-to-bit mapping is configured for an affinity attribute.
Views
Constraints mapping view
Predefined user roles
network-admin
Parameters
name: Specifies an affinity attribute by its name, a case-sensitive string of 1 to 32 characters.
bit-position-number: Specifies a bit by its position value in the range of 0 to 31.
Usage guidelines
This command enables the SRv6 TE policy to select links containing the bit values associated with the specified affinity attribute as required by the affinity attribute rule.
· Link attribute—A 32-bit binary number. Each bit represents an attribute with a value of 0 or 1.
· Affinity attribute bit position—The value range is 0 to 32. When the affinity attribute value is N, it is compared with the N+1 bit of the link attribute. The affinity attribute applies to the link only if the N+1 bit value of the link attribute is 1.
For example, for affinity attribute names blue and red, if you configure the name blue bit-position 1 and name red bit-position 5 commands, the link selection varies by affinity attribute rule type:
· For the include-any affinity attribute rule, a link is available for use if the link attribute has the second bit (associated with affinity attribute blue) or sixth bit (associated with affinity attribute red) set to 1.
· For the include-all affinity attribute rule, a link is available for use if the link attribute has both the second bit (associated with affinity attribute blue) and sixth bit (associated with affinity attribute red) set to 1.
· For the exclude-any affinity attribute rule, a link is not available for use if the link attribute has the second bit (associated with affinity attribute blue) or sixth bit (associated with affinity attribute red) set to 1.
Examples
# Map affinity attribute red to bit 3 in the affinity attribute.
<Sysname> system-view
[Sysname] segment-routing ipv6
[Sysname-segment-routing-ipv6] traffic-engineering
[Sysname-srv6-te] affinity-map
[Sysname-srv6-te-affinity-map] name red bit-position 3
Related commands
mpls te link-attribute (MPLS Command Reference)
name
on-demand
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
When the device receives a BGP route, it compares the color extended attribute value of the BGP route with the color value of the ODN template. If the color values match, the device automatically generates an SRv6 TE policy group. The device will assign the smallest ID that are not in use to the SRv6 TE policy group.
After an SRv6 TE policy group is automatically generated, you 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]
path verification
Use path verification to configure path connectivity verification for an SRv6 TE policy.
Use undo path verification to restore the default.
Syntax
path verification { [ specified-sid ] enable [ rib-check-only ] | disable }
undo path verification
Default
Path connectivity verification is not configured for an SRv6 TE policy. The setting configured in SRv6-TE view applies.
Views
SRv6 TE policy view
Predefined user roles
network-admin
Parameters
specified-sid: Enables path connectivity verification only for the SIDs specified with the verification keyword in the index command. If you do not specify the specified-sid keyword, the path verification command verifies the validity for all SIDs in the SID list.
enable: Enables path connectivity verification for the SRv6 TE policy.
rib-check-only: Checks the reachability of locator prefixes associated with all SRv6 SIDs in the SID list without checking the existence of the SRv6 SIDs in the topology. If you do not specify this keyword, the device checks the reachability of locator prefixes associated with all SRv6 SIDs in the SID list and the existence of the SRv6 SIDs in the topology.
disable: Disables path connectivity verification for the SRv6 TE policy.
Usage guidelines
You must configure this command on the first node of the SRv6 TE policy.
Typically, the controller deploys the SID list of an SRv6 TE policy. Without BFD configured, the first node cannot immediately detect path failures in the SRv6 TE policy. It only changes the SID list of the SRv6 TE policy as instructed by the controller that completes path recalculation upon detecting a topology change. If the controller or the link to the controller fails, the first node will be unable to detect failures and change SID lists, resulting in traffic loss.
For fast traffic switchover and high availability, you can enable path connectivity verification for the first node of the SRv6 TE policy. This feature enables the first node to collect network topology information, and verify all SID lists in the SRv6 TE policy as follows:
· If all SRv6 SIDs exist in the topology and the associated locator prefixes are routable, the SID list is valid.
· If any SRv6 SIDs do not exist in the topology or any of the associated locator prefixes are not routable, the SID list is invalid.
Upon detecting an invalid SID list (SID list failure), the first node changes paths as follows:
· If the valid candidate paths of the SRv6 TE policy contain multiple SID lists, and one of the SID list fails, traffic is distributed to other valid SID lists.
· If the SRv6 TE policy has valid primary and backup candidate paths, and all SID lists for the primary candidate path fail, traffic is distributed to the backup candidate path.
· If all valid candidate paths of the SRv6 TE policy fail, the SRv6 TE policy is faulty and an associated protection action is taken (for example, MPLS L3VPN FRR).
You can configure SRv6 TE policy path connectivity verification in both SRv6 TE view and SRv6 TE policy view. The configuration in SRv6 TE policy view takes precedence over the configuration in SRv6 TE view. If path connectivity verification is not configured for an SRv6 TE policy, the configuration in SRv6 TE applies.
The first node must have all SRv6 SIDs and routes in the IGP domain to detect their status through the following settings:
· Enable the IGP domain to forward routing information through IPv6 IS-IS.
· Configure the distribute link-state command in IS-IS view for the first node to report link status.
If a BSID exists in the segment list path, path connectivity verification will fail because the BSID cannot be flooded in the IGP topology. Do not configure this command in the scenario where BSID is deployed.
After path connectivity verification is enabled for an SRv6 TE policy, the device verifies the validity of all SIDs in the SID list. If the SID list contains an inter-AS SID (for example, the BGP Peer SID allocated by BGP EPE) or contains the BSID of another SRv6 TE policy, the path connectivity verification will fail. This is because a BSID or BGP Peer SID cannot be flooded in the IGP topology.
To resolve this issue, you can execute the following commands to configure the path connectivity verification only verifies the validity of specific SIDs:
· Use the index command to specify the verification keyword for the SIDs to be verified. Do not specify this keyword for a BSID or BGP EPE SID in the SID list.
· Specify the specified-sid keyword when you execute the path verification command in SRv6 TE policy view or the srv6-policy path verification enable command in SRv6 TE view.
Examples
# Enable path connectivity verification for SRv6 TE policy 1.
<Sysname> system-view
[Sysname] segment-routing ipv6
[Sysname-segment-routing-ipv6] traffic-engineering
[Sysname-srv6-te] policy 1
[Sysname-srv6-te-policy-1] path verification enable
Related commands
distribute (Layer 3—IP Routing Command Reference)
index
srv6-policy path verification enable
pce capability segment-routing ipv6
Use pce capability segment-routing ipv6 to enable the SRv6 capability for a PCC device.
Use undo pce capability segment-routing ipv6 to disable the SRv6 capability for a PCC device.
Syntax
pce capability segment-routing ipv6
undo pce capability segment-routing ipv6
Default
A PCC device does not have the SR capability.
Views
PCC view
Predefined user roles
network-admin
Usage guidelines
To establish an SRv6-capable PCEP session, you need to enable the SRv6 capability on both peers of the PCEP session. An SRv6-capable active PCEP session supports computation, report, delegation, and update of SR-based LSPs.
In the current software version, a PCE device does not have the SRv6 capability.
Examples
# Enable the SRv6 capability for the PCC device.
<Sysname> system-view
[Sysname] pce-client
[Sysname-pcc] pce capability segment-routing ipv6
pce delegation
Use pce delegation to enable PCE delegation for an SRv6 TE policy.
Use undo pce delegation to restore the default.
Syntax
pce delegation { enable | disable }
undo pce delegation
Default
An SRv6 TE policy uses the PCE delegation configuration in SRv6 TE view.
Views
SRv6 TE policy view
Predefined user roles
network-admin
Parameters
enable: Enables PCE delegation for the SRv6 TE policy.
disable: Disables PCE delegation for the SRv6 TE policy.
Usage guidelines
After PCE delegation for an SRv6 TE policy is enabled, the PCC delegates the policy's candidate paths to a PCE. The PCC creates or updates candidate paths according to the creation or update requests received from the PCE.
You can configure PCE delegation for all 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 both the pce delegation command and the pce passive-delegate report-only command for an SRv6 TE policy, the pce passive-delegate report-only command takes effect.
Examples
# Enable PCE delegation 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] pce delegation enable
Related commands
pce passive-delegate report-only
srv6-policy pce delegation enable
pce passive-delegate report-only
Use pce passive-delegate report-only to enable the device to report candidate path information of an SRv6 TE policy to the PCE without delegating the policy to the PCE.
Use undo pce passive-delegate report-only to restore the default.
Syntax
pce passive-delegate report-only { enable | disable }
undo pce passive-delegate report-only
Default
An SRv6 TE policy uses the passive delegation report only setting configured in SRv6 TE view.
Views
SRv6 TE policy view
Predefined user roles
network-admin
Parameters
enable: Enables the passive delegation report only feature for the SRv6 TE policy.
disable: Disables the passive delegation report only feature for the SRv6 TE policy.
Usage guidelines
When the device delegates only part of its SRv6 TE policies to a PCE, the PCE does not have complete SRv6 TE policy candidate path information to calculate global bandwidth information. You can enable the device to report information about the undelegated SRv6 TE policies to the PCE without using the PCE to compute candidate paths for the policies.
You can configure the passive delegation report only feature for all 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 both the pce delegation command and the pce passive-delegate report-only command for an SRv6 TE policy, the pce passive-delegate report-only command takes effect.
Examples
# Enable the device to report an SRv6 TE policy's candidate path information to the PCE without delegating the policy to the PCE.
<Sysname> system-view
[Sysname] segment-routing ipv6
[Sysname-segment-routing-ipv6] traffic-engineering
[Sysname-srv6-te] policy 1
[Sysname-srv6-te-policy-1] pce passive-delegate report-only enable
Related commands
pce delegation
srv6-policy pce passive-delegate report-only enable
pcep (SRv6 TE policy path preference dynamic view)
Use pcep to enable an SRv6 TE policy candidate path to use PCE to compute the SID lists.
Use undo pcep to restore the default.
Syntax
pcep
undo pcep
Default
An SRv6 TE policy candidate path does not use PCE to compute SID lists. You need to manually configure the SID lists for the candidate path.
Views
SRv6 TE policy path preference dynamic view
Predefined user roles
network-admin
Usage guidelines
The device uses PCE to compute SID lists for a manually created SRv6 TE policy candidate path in the following procedure:
1. The device that acts as a PCC sends a path computation request to the PCE.
2. The PCE computes paths after it receives the request.
3. The PCE replies the PCC with the computed path information.
4. The PCC creates SID lists for the SRv6 TE policy candidate path according to the path information computed by PCE.
Examples
# Enable an SRv6 TE policy candidate path to use PCE to compute the SID lists.
<Sysname> system-view
[Sysname] segment-routing ipv6
[Sysname-segment-routing-ipv6] traffic-engineering
[Sysname-srv6-te] policy 1
[Sysname-srv6-te-policy-1] candidate-paths
[Sysname-srv6-te-policy-1-path] preference 20
[Sysname-srv6-te-policy-1-path-pref-20] dynamic
[Sysname-srv6-te-policy-1-path-pref-20-dyna] pcep
pcep (SRv6-TE-ODN dynamic view)
Use pcep to enable path computation using PCE.
Use undo pcep to disable path computation using PCE.
Syntax
pcep
undo pcep
Default
Dynamic path computation using PCE is disabled.
Views
SRv6-TE-ODN dynamic view
Predefined user roles
network-admin
Usage guidelines
The SID lists for ODN-created SRv6 TE policy candidate path 100 can only be computed by PCE. For this candidate path, you must execute this command to enable path computation using PCE. The path computation procedure is as follows:
1. The device that acts as a PCC sends a path computation request to the PCE.
2. The PCE computes paths after it receives the request.
3. The PCE replies the PCC with the computed path information.
4. The PCC creates SID lists for candidate path 100 according to the path information computed by PCE.
Examples
# Enable dynamic path computation using PCE.
<Sysname> system-view
[Sysname] segment-routing ipv6
[Sysname-segment-routing-ipv6] traffic-engineering
[Sysname-srv6-te] on-demand color 1
[Sysname-srv6-te-odn-1] dynamic
[Sysname-srv6-te-odn-1-dynamic] pcep
policy
Use policy to create an SRv6 TE policy and enter its view, or enter the view of an existing SRv6 TE policy.
Use undo policy to delete an SRv6 TE policy and all the configuration in the SRv6 TE policy.
Syntax
policy policy-name
undo policy policy-name
Default
No SRv6 TE policies exist.
Views
SRv6 TE view
Predefined user roles
network-admin
Parameters
policy-name: Specifies an SRv6 TE policy name, a case-sensitive string of 1 to 59 characters.
Examples
# Create an SRv6 TE policy named srv6policy and enter its view.
<Sysname> system-view
[Sysname] segment-routing ipv6
[Sysname-segment-routing-ipv6] traffic-engineering
[Sysname-srv6-te] policy p1
[Sysname-srv6-te-policy-p1]
policy-group
Use policy-group to create an SRv6 TE policy group and enter its view, or enter the view of an existing SRv6 TE policy group.
Use undo policy-group to delete an SRv6 TE policy group and all the configuration in the SRv6 TE policy group.
Syntax
policy-group group-id
undo policy-group group-id
Default
No SRv6 TE policy groups exist.
Views
SRv6 TE view
Predefined user roles
network-admin
Parameters
group-name: Specifies an SRv6 TE policy group by its ID in the range of 1 to 4294967295.
Usage guidelines
You can add SRv6 TE policies to an SRv6 TE policy group to implement SRv6 TE policy based forwarding according to DSCP values of packets.
Examples
# Create SRv6 TE policy group 1 and enter its view.
<Sysname> system-view
[Sysname] segment-routing ipv6
[Sysname-segment-routing-ipv6] traffic-engineering
[Sysname-srv6-te] policy-group 1
[Sysname-srv6-te-policy-group-1]
preference
Use preference to set the preference for an SRv6 TE policy candidate path and enter SRv6 TE policy path preference view, or enter an existing SRv6 TE policy path preference view.
Use undo preference to delete an SRv6 TE policy candidate path preference and all the configuration in the SRv6 TE policy path preference view.
Syntax
preference preference-value
undo preference preference-value
Default
No preference is set for an SRv6 TE policy candidate path.
Views
SRv6 TE policy candidate path view
Predefined user roles
network-admin
Parameters
preference-value: Specifies a candidate path preference in the range of 1 to 65535. A bigger value represents a higher preference.
Usage guidelines
A preference represents a candidate path of an SRv6 TE policy.
Examples
# Set the preference of an SRv6 TE policy candidate path to 20, and enter SRv6 TE policy path preference view.
<Sysname> system-view
[Sysname] segment-routing ipv6
[Sysname-segment-routing-ipv6] traffic-engineering
[Sysname-srv6-te] policy a1
[Sysname-srv6-te-policy-a1] candidate-paths
[Sysname-srv6-te-policy-a1-path] preference 20
[Sysname-srv6-te-policy-a1-path-pref-20]
rate-limit
Use rate-limit to set a rate limit for an SRv6 TE policy.
Use undo rate-limit to restore the default.
Syntax
rate-limit kbps
undo rate-limit
Default
No rate limit is set for an SRv6 TE policy.
Views
SRv6 TE policy view
Predefined user roles
network-admin
Parameters
kbps: Specifies the rate limit, in the range of 1 to 4294967295, in kbps.
Usage guidelines
When the rate of the packets forwarded by an SRv6 TE policy exceeds the rate limit, the device drops the packets that exceed the rate limit.
If you execute this command multiple times, the most recent configuration takes effect.
Examples
# Set the rate limit for SRv6 TE policy aaa to 15000 kbps.
<Sysname> system-view
[Sysname] segment-routing ipv6
[Sysname-segment-routing-ipv6] traffic-engineering
[Sysname-srv6-te] policy aaa
[Sysname-srv6-te-policy-aaa] rate-limit 15000
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
reoptimization
Use reoptimization to configure candidate path reoptimization for an SRv6 TE policy.
Use undo reoptimization to restore the default.
Syntax
reoptimization { disable | enable [ frequency seconds ] }
undo reoptimization
Default
Candidate path reoptimization is not configured for an SRv6 TE policy and the configuration in SRv6 TE view applies.
Views
SRv6 TE policy view
Predefined user roles
network-admin
Parameters
disable: Disables candidate path reoptimization for an SRv6 TE policy.
enable: Enables candidate path reoptimization for an SRv6 TE policy.
frequency seconds: Sets the candidate path reoptimization frequency, in the range of 1 to 604800 seconds. The default frequency is 3600 seconds. If you set a frequency smaller than 60 seconds, the device performs reoptimization every 60 seconds.
Usage guidelines
This feature enables the PCE to periodically compute paths and notify the PCC to update path information, so that the SRv6 TE policy can use the optimal path to establish the candidate path.
For example, an SRv6 TE policy uses a path other than the optimal path to establish the candidate path because the optimal path does not have sufficient link bandwidth. This feature enables the SRv6 TE policy to switch the candidate path to the optimal path when the link bandwidth becomes sufficient.
You can configure candidate path reoptimization for all 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 candidate path reoptimization for SRv6 TE policy p1.
<Sysname> system-view
[Sysname] segment-routing ipv6
[Sysname-segment-routing-ipv6] traffic-engineering
[Sysname-srv6-te] policy p1
[Sysname-srv6-te-p1] reoptimization enable
Related commands
srv6-policy reoptimization
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 binding-sid: Specifies the BSID of an SRv6 TE policy.
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 name-value: 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
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 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
undo router-id filter
Default
Router ID filtering is disabled.
Views
BGP IPv6 SR policy address family.
Predefined user roles
network-admin
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. The device accepts the route only if the Route Target attribute contains the Router ID of the local device.
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 [ no-endpoint ] ] }
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.
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: 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 a backup template but a primary template is specified, the primary template applies. If neither the primary nor the backup template is specified in this command, the backup template specified in SRv6 TE view applies.
oam-sid sid: Adds an OAM SID to SBFD packets to identify the destination node. The sid argument represents the SRv6 SID of the endpoint destination node. If you do not specify this option, no OAM SID will be added to BFD packets. As a best practice, set the OAM SID to the End SID of the destination node.
encaps: Uses the normal encapsulation mode to encapsulate SBFD packets.
insert: Uses the insertion mode to encapsulate SBFD packets.
no-endpoint: Uses the insertion with no endpoint mode to encapsulate SBFD packets. In this mode, the SID list inserted into the SRH does not contain the endpoint in an SRv6 TE policy. If you do not specify this keyword, SBFD packets are encapsulated in insertion with endpoint mode.
Usage guidelines
To use SBFD to detect an SRv6 TE policy, the device must 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.
¡ The destination IPv6 address in the new IPv6 header is the first IPv6 address in the SID list of the SRv6 TE policy. The source IPv6 address is the IPv6 address specified using the encapsulation source-address command in SRv6 view.
¡ 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.
¡ The destination IPv6 address in the original IPv6 header of the SBFD packets changes to the first IPv6 address in the SID list of the SRv6 TE policy. The source IPv6 address does not change.
¡ All SIDs in the SID list of the SRv6 TE policy and the endpoint of the SRv6 TE policy are encapsulated in the SRH. The endpoint is the last one in the SID list.
· Insert no-endpoint—Insert no-endpoint mode. It inserts an SRH without an endpoint after the original IPv6 header. The last SID in the SID list and the endpoint in the SRv6 TE policy represent the same node.
¡ The destination IPv6 address in the original IPv6 header of the SBFD packets changes to the first IPv6 address in the SID list of the SRv6 TE policy. The source IPv6 address does not change.
¡ All SIDs in the SID list of the SRv6 TE policy are encapsulated in the SRH. The endpoint of the SRv6 TE policy is not encapsulated in the SRH.
If you do not specify the encaps or insert keyword, the encapsulation mode configured by the bfd srv6-encapsulation-mode encap command applies.
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 encaps (High Availability Command Reference)
display segment-routing ipv6 te sbfd
sbfd local-discriminator (High Availability Command Reference)
srv6-policy sbfd
segments
Use segments to create the segment constraints and enter its view, or enter the existing segment constraints view.
Use undo segments to delete the segment constraints view and all its configurations.
Syntax
segments
undo segments
Default
No segment constraints exist.
Views
Constraints view
Predefined user roles
network-admin
Examples
# Create the segment constraints and enter its view.
<Sysname> system-view
[Sysname] segment-routing-ipv6
[Sysname-segment-routing-ipv6] traffic-engineering
[Sysname-srv6-te] policy a1
[Sysname-srv6-te-policy-a1] candidate-paths
[Sysname-srv6-te-policy-a1-path] preference 200
[Sysname-srv6-te-policy-a1-path-pref-200] constraints
[Sysname-srv6-te-policy-a1-path-pref-200-const] segments
[Sysname-srv6-te-policy-a1-path-pref-200-const-seg]
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. The value range for this argument is 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 load sharing 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 load sharing 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 lowest forwarding priority.
To set a service class value for traffic, use the remark service-class command in traffic behavior view.
Examples
# Set the service class value to 5 for 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
sid-algorithm
Use sid-algorithm to specify a Flex-Algo for an SRv6 TE policy.
Use undo sid-algorithm to restore the default.
Syntax
sid-algorithm algorithm-id
undo sid-algorithm
Default
No Flex-Algo is associated with an SRv6 TE policy.
Views
Segment constraints view
SRv6 TE ODN dynamic view
Predefined user roles
network-admin
Parameters
algorithm-id: Specifies a Flex-Algo by its ID in the range of 128 to 255.
Usage guidelines
The SRv6 TE policy will use the specified Flex-Algo to calculate forwarding paths.
Examples
# In segment constraints view, specify Flex-Algo 128 for the SRv6 TE policy.
<Sysname> system-view
[Sysname] segment-routing-ipv6
[Sysname-segment-routing-ipv6] traffic-engineering
[Sysname-srv6-te] policy a1
[Sysname-srv6-te-policy-a1] candidate-paths
[Sysname-srv6-te-policy-a1-path] preference 200
[Sysname-srv6-te-policy-a1-path-pref-200] constraints
[Sysname-srv6-te-policy-a1-path-pref-200-const] segments
[Sysname-srv6-te-policy-a1-path-pref-200-const-seg] sid-algorithm 128
# In SRv6 TE ODN dynamic view, specify Flex-Algo 128 for the SRv6 TE policy.
<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] dynamic
[Sysname-srv6-te-odn-1-dynamic] sid-algorithm 128
sid-limit
Use sid-limit to configure the maximum number of SIDs in an SID list.
Use undo sid-limit to restore the default.
Syntax
sid-limit limit-value
undo sid-limit
Default
The maximum number of SIDs in an SID list is not configured.
Views
Metric type view
Predefined user roles
network-admin
Parameters
limit-value: Specifies the maximum number of SIDs in an SID list, in the range of 1 to 255.
Usage guidelines
If the number of SIDs for the calculated paths exceeds the specified value, path calculation based on the specified metric (in the type command) fails for the SRv6 TE policy. The SRv6 TE policy cannot be used to forward traffic.
The effective maximum number of SIDs takes the smaller value among the following settings:
· Maximum number of SIDs configured in this command.
· Default setting for this command.
Examples
# Specify the maximum number of SIDs in the SID list as 10.
<Sysname> system-view
[Sysname] segment-routing ipv6
[Sysname-segment-routing-ipv6] traffic-engineering
[Sysname-srv6-te] policy p1
[Sysname-srv6-te-policy-a1] candidate-paths
[Sysname-srv6-te-policy-a1-path] preference 200
[Sysname-srv6-te-policy-a1-path-pref-200] dynamic
[Sysname-srv6-te-policy-a1-path-pref-200-dyna] metric
[Sysname-srv6-te-policy-a1-path-pref-200-dyna-metric] sid-limit 10
snmp-agent trap enable srv6-policy
Use snmp-agent trap enable srv6-policy to enable SNMP notifications for SRv6 TE policies.
Use undo snmp-agent trap enable srv6-policy to disable SNMP notifications for SRv6 TE policies.
Syntax
snmp-agent trap enable srv6-policy
undo snmp-agent trap enable srv6-policy
Default
SNMP notifications for SRv6 TE policies are disabled.
Views
System view
Predefined user roles
network-admin
Usage guidelines
This command enables the device to send SNMP notifications about state changes and resource usage anomalies of SRv6 TE policies. For SNMP notifications to be sent correctly, you must also configure SNMP on the device. For more information about SNMP configuration, see the network management and monitoring configuration guide for the device.
SRv6 TE policy resources include the following:
· Number of SRv6 TE policy forwarding paths.
· Number of forwarding entry IDs of SRv6 TE policy groups.
· Number of forwarding entry IDs of SRv6 TE policies.
· Number of forwarding entry IDs of SID lists.
Examples
# Enable SNMP notifications for SRv6 TE policies.
<Sysname> system-view
[Sysname] snmp-agent trap enable srv6-policy
source-address
Use source-address to specify a source address for an SRv6 TE policy.
Use undo source-address to remove the source address configuration from an SRv6 TE policy.
Syntax
source-address ipv6 ipv6-address
undo source-address
Default
No source address is specified for an SRv6 TE policy.
Views
SRv6 TE policy view
Predefined user roles
network-admin
Usage guidelines
Use this command to specify a source address only for BFD echo and SBFD packets in the SRv6 TE policy scenario.
In the SRv6 TE policy scenario, when BFD in echo packet mode is enabled, you must use the bfd echo or srv6-policy bfd echo command to specify the source address of the BFD session on the source node of the SRv6 TE policy. The specified address is also the destination address of BFD echo packets.
In system view, you can use the bfd echo-source-ipv6 command to specify the source address of BFD echo packets for all BFD sessions in echo packet mode on the device. If you do not use the bfd echo-source-ipv6 command, the device will use the BFD session source address specified by using the bfd echo or srv6-policy bfd echo command as the source address of BFD echo packets. In this case, the same address is used as both the source and destination addresses of BFD echo packets. BFD echo session establishment will fail if the network is deployed with security devices that have features such as uRPF, because the features falsely treat the BFD echo packets as illegal packets and intercept them.
To resolve the above issue, use this command to specify a packet source address for each SRv6 TE policy.
When SBFD or BFD in echo packet mode is enabled for an SRv6 TE policy, you can use this command to specify a source address for BFD or SBFD session packets.
For a BFD session in echo packet mode, the device selects a source address for BFD echo packets in the following order:
1. The packet source address specified by using the source-address command.
2. The packet source address specified by using the bfd echo-source-ipv6 command.
3. The BFD session source address specified by using the bfd echo command.
4. The BFD session source address specified by using the srv6-policy bfd echo command.
For an SBFD session, the device selects a source address for SBFD packets in the following order:
5. The packet source address specified by using the source-address command.
6. The address specified by using the sbfd source-ipv6 command.
Examples
# Specify source address 1::.2 for BFD and SBFD session packets in 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] source-address ipv6 1::2
Related commands
bfd echo-source-ipv6 (High Availability Command Reference)
bfd echo
sbfd
srv6-policy bfd echo
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 a tunnel policy. If you specify this keyword, the device steers traffic based on the bound policy, color, and tunnel load sharing 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 next hop address of a BGP route. If a matching SRv6 TE policy exists, the device recurses the BGP route to that SRv6 TE policy. Then, when the device receives packets that match the BGP route, it forwards the packets through the SRv6 TE policy.
· Based on tunnel policy—On an IP L3VPN over SRv6 or EVPN L3VPN over SRv6 network, configure a tunnel policy that uses the SRv6 TE policy as the public tunnel to carry the packets of a VPN instance. 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 [ downgrade ]
undo sr-te frr enable
Default
SRv6 TE FRR is disabled.
Views
SRv6 view
Predefined user roles
network-admin
Parameters
downgrade: Enables SRv6 BE FRR. If you specify this keyword, the proxy forwarding node uses the last SRv6 SID in the SID list as the destination address, and forwards packets to the destination node in SRv6 BE mode.
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.
Transit node failure protection might fail if SRv6 compression is also enabled. Traffic cannot bypass the SRv6 SID of the faulty node, because the SRv6 SIDs in the SID list of the SRv6 TE policy are related with each another. To address this issue, configure the sr-te frr enable command with the downgrade keyword specified, and make sure the last SRv6 SID in the SID list is not compressed. The proxy forwarding node can then use the last SRv6 SID in the SID list as the destination address for forwarding to implement transit node failure protection.
Suppose you configure the sr-te frr enable command with the downgrade keyword specified for the transit node. Then, a transit node failure occurs and triggers transit node failure protection. To enable echo packet mode BFD for the SRv6 TE policy, you must specify the encaps keyword (normal encapsulation mode) when executing the bfd echo command.
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
In IS-IS IPv6 address family view:
srv6-policy autoroute enable [ level-1 | level-2 ]
undo srv6-policy autoroute enable
In OSPFv3 view:
srv6-policy autoroute enable
undo srv6-policy autoroute enable
Default
Automatic route advertisement for SRv6 TE policies is disabled.
Views
IS-IS IPv6 address family view
OSPFv3 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 or OSPFv3) 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.
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.
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
# Enable automatic route advertisement for SRv6 TE policies of OSPFv3 process 1.
<Sysname> system-view
[Sysname] ospfv3 1
[Sysname-ospfv3-1] 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
When the hot standby feature is enabled, the candidate path with the greatest preference value in the SRv6 TE policy is the main path and that with the second greatest preference value is the backup path. When all SID lists of the main path fail, the backup path immediately takes over the service 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 all SRv6 TE policies.
<Sysname> system-view
[Sysname] segment-routing ipv6
[Sysname-segment-routing-ipv6] traffic-engineering
[Sysname-srv6-te] srv6-policy backup hot-standby enable
Related commands
backup hot-standby
srv6-policy bfd echo
Use srv6-policy bfd echo to enable the echo packet mode BFD for all SRv6 TE policies.
Use undo srv6-policy bfd echo to disable the echo packet mode BFD for all SRv6 TE policies.
Syntax
srv6-policy bfd echo source-ipv6 ipv6-address [ template template-name ] [ backup-template backup-template-name ] [ reverse-path reverse-binding-sid ]
undo srv6-policy bfd echo
Default
The echo packet mode BFD is disabled for all SRv6 TE policies.
Views
SRv6 TE view
Predefined user roles
network-admin
Parameters
source-ipv6 ipv6-address: Specifies the source IPv6 address of the BFD session.
template template-name: Specifies a BFD session parameter template by its name, a case-sensitive string of 1 to 63 characters. If you do not specify this option, the BFD session uses multihop BFD session settings configured in system view.
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 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
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.
If you do not specify the source-ipv6 ipv6-address option in the bfd echo command for an SRv6 TE policy, you must enable the echo packet mode BFD globally in SRv6 TE view. Otherwise, the device cannot establish a BFD session for the SRv6 TE policy.
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.
Before you execute this command, execute the bfd echo-source-ipv6 command on the local device to specify the source IPv6 address for echo packets.
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
bfd echo-source-ipv6 (High Availability Command Reference)
display segment-routing ipv6 te bfd
srv6-policy bfd first-fail-timer
Use srv6-policy bfd first-fail-timer to configure the timer that delays reporting the first BFD or SBFD session establishment failure to an SRv6 TE policy.
Use undo srv6-policy bfd first-fail-timer to restore the default.
Syntax
srv6-policy bfd first-fail-timer seconds
undo srv6-policy bfd first-fail-timer
Default
The timer that delays reporting the first BFD or SBFD session establishment failure to an SRv6 TE policy is 60 seconds.
Views
SRv6 TE view
Predefined user roles
network-admin
Parameters
seconds: Specifies the timeout time that reports the first BFD or SBFD session establishment failure to an SRv6 TE policy. The value range for this argument is 1 to 600 seconds. The default value is 60.
Usage guidelines
The device attempts to establish a BFD or SBFD session to detect an SRv6 TE policy when all the following conditions exist:
· The SRv6 TE policy is in up state.
· The SID list of the SRv6 TE policy is in up state.
· BFD or SBFD is enabled for the SRv6 TE policy.
When the BFD/SBFD session detection timer expires, if the BFD or SBFD session is not in up state, the device considers that the BFD or SBFD session establishment fails. The device does not immediately report the failure to the SRv6 TE policy. You can configure this command to set a delay timer for reporting the session establishment failure. The device will report the session establishment failure to the SRv6 TE policy upon expiration of the delay timer.
If you execute this command multiple times, the most recent configuration takes effect.
Examples
# Configure the timer that delays reporting the first BFD or SBFD session establishment failure to an SRv6 TE policy as 30 seconds.
<Sysname> system-view
[Sysname] segment-routing ipv6
[Sysname-segment-routing-ipv6] traffic-engineering
[Sysname-srv6-te] srv6-policy bfd first-fail-timer 30
srv6-policy bfd trigger path-down enable
Use srv6-policy bfd trigger path-down enable to enable BFD session down events to trigger SRv6 TE policy path switchover globally.
Use undo srv6-policy bfd trigger path-down enable to disable BFD session down events to trigger SRv6 TE policy path switchover globally.
Syntax
srv6-policy bfd trigger path-down enable
undo srv6-policy bfd trigger path-down enable
Default
The feature for triggering SRv6 TE policy path switchover with BFD session down events is disabled globally.
Views
SRv6 TE view
Predefined user roles
network-admin
Usage guidelines
By default, when the SRv6 TE policy has multiple valid candidate paths, the following conditions exist:
· If the hot standby feature is disabled, BFD or SBFD detects all SID lists for only the optimal valid candidate path of the SRv6 TE policy. The device establishes a BFD or SBFD session for each SID list. When all BFD or SBFD sessions go down, the SRv6 TE policy will not select other valid candidate paths, and the device will not forward packets through the SRv6 TE policy.
· If the hot standby feature is enabled, BFD or SBFD detects all SID lists for the primary and backup paths of the SRv6 TE policy. The device establishes a BFD or SBFD session for each SID list.
¡ If all BFD or SBFD sessions for the primary path go down, the SRv6 TE policy will use the backup path to forward packets without reselecting other valid candidate paths.
¡ If all BFD or SBFD sessions for the primary and backup paths go down, the SRv6 TE policy will not select other valid candidate paths, and the device will not forward packets through the SRv6 TE policy.
If you enable BFD session down events to trigger SRv6 TE policy path switchover, the following conditions exist when the SRv6 TE policy has multiple valid candidate paths:
· If the hot standby feature is disabled, BFD or SBFD detects all SID lists for only the optimal valid candidate path of the SRv6 TE policy. The device establishes a BFD or SBFD session for each SID list. When all BFD or SBFD sessions go down, the SRv6 TE policy will reselect other valid candidate paths for packet forwarding. If no valid candidate paths are available for the SRv6 TE policy, the device cannot forward packets through the SRv6 TE policy.
· If the hot standby feature is enabled, BFD or SBFD detects all SID lists for the primary and backup paths of the SRv6 TE policy. The device establishes a BFD or SBFD session for each SID list.
¡ If all BFD or SBFD sessions for the primary path go down, the SRv6 TE policy will use the backup path to forward packets, and reselect the primary and backup paths.
¡ If all BFD or SBFD sessions for the primary and backup paths go down, the SRv6 TE policy will reselect other valid candidate paths as the primary and backup paths. The device will forward packets through the new primary path of the SRv6 TE policy.
· During optimal path reselection, if no valid candidate paths are available for the SRv6 TE policy, the device cannot forward packets through the SRv6 TE policy.
Before you enable this feature for an SRv6 TE policy, create a BFD or SBFD session for the policy first.
You can configure BFD session down events to trigger SRv6 TE policy path switchover 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 BFD session down events to trigger path switchover for SRv6 TE policies globally.
<Sysname> system-view
[Sysname] segment-routing ipv6
[Sysname-segment-routing-ipv6] traffic-engineering
[Sysname-srv6-te] srv6-policy bfd trigger path-down enable
Related commands
bfd echo
bfd trigger path-down
sbfd
srv6-policy bfd echo
srv6-policy sbfd
srv6-policy calc-schedule-interval
Use srv6-policy calc-schedule-interval to configure the dynamic path calculation timers.
Use undo srv6-policy calc-schedule-interval to restore the default.
Syntax
srv6-policy calc-schedule-interval { maximum-interval [ minimum-interval [ incremental-interval [ conservative ] ] ] | millisecond interval }
undo srv6-policy calc-schedule-interval
Default
The maximum, minimum, and incremental intervals for dynamic path calculation are 5 seconds, 50 milliseconds, and 200 milliseconds, respectively.
Views
SRv6 TE view
Predefined user roles
network-admin
Parameters
maximum-interval: Specifies the maximum dynamic path calculation interval in the range of 1 to 60 seconds. The default value is 5.
minimum-interval: Specifies the minimum dynamic path calculation interval in the range of 10 to 60000 milliseconds. The default value is 50.
incremental-interval: Specifies the incremental dynamic path calculation interval in the range of 10 to 60000 milliseconds. The default value is 200.
conservative: Uses the maximum dynamic path calculation interval in case of SRv6 TE policy flappings. If you do not specify this keyword, in case of SRv6 TE policy flappings, the maximum interval applies for three consecutive times, and then the minimum interval applies. If no SRv6 TE policy flappings occur, the maximum dynamic interval applies for once, and then the minimum interval applies, regardless of whether the conservative keyword is specified.
millisecond interval: Specifies a fixed dynamic path calculation interval in the range of 0 to 10000 milliseconds.
Usage guidelines
Use this command to avoid excessive resource consumption caused by frequent network changes.
If you specify the maximum-interval, minimum-interval, and incremental-interval settings for the command, the following situations will occur:
· For the first path calculation triggered for the SRv6 TE policy, the minimum-interval setting applies.
· For the nth (n > 1) path calculation triggered for the SRv6 TE policy, the device adds a value of incremental-interval × 2n-2 based on the minimum-interval setting. The total value does not exceed the maximum-interval setting.
If the value of minimum-interval + incremental-interval × 2n-2 is larger than or equal to the value of maximum-interval, the device uses the conservative keyword and SRv6 TE policy flapping condition to adjust the path calculation intervals:
· If the conservative keyword is specified:
¡ If SRv6 TE policy flappings occur, the maximum-interval setting applies.
¡ If no SRv6 TE policy flappings occur, the maximum interval applies for once, and then the minimum interval applies.
· If the conservative keyword is not specified:
¡ If SRv6 TE policy flappings occur, the maximum interval applies for three consecutive times, and then the minimum interval applies.
¡ If no SRv6 TE policy flappings occur, the maximum interval applies for once, and then the minimum interval applies.
The value of the minimum-interval or incremental-interval argument cannot be greater than the maximum-interval argument.
To increase path calculation frequency for faster path calculation, configure a fixed interval.
Examples
# Configure the maximum, minimum, and incremental intervals for dynamic path calculation as 10 seconds, 500 milliseconds, and 300 milliseconds, respectively.
<Sysname> system-view
[Sysname] segment-routing ipv6
[Sysname-segment-routing-ipv6] traffic-engineering
[Sysname-srv6-te] srv6-policy calc-schedule-interval 10 500 300
srv6-policy 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 drop-upon-invalid enable
Use srv6-policy drop-upon-invalid enable to globally enable the feature of dropping traffic when SRv6 TE policies become invalid.
Use undo srv6-policy drop-upon-invalid enable to globally disable the drop-upon-invalid feature.
Syntax
srv6-policy drop-upon-invalid enable
undo srv6-policy drop-upon-invalid enable
Default
The drop-upon-invalid feature is disabled globally.
Views
SRv6 TE 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 command does not take effect if 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.
The drop-upon-invalid command configured on the remote device does not affect an SRv6 TE policy generated based on a BGP IPv6 SR-TE policy route. The SRv6 TE policy is controlled by only the drop-upon-invalid command configured on the local device.
You can configure the drop-upon-invalid feature 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
# Globally enable the feature of dropping traffic when SRv6 TE policies become invalid.
<Sysname> system-view
[Sysname] segment-routing ipv6
[Sysname-segment-routing-ipv6] traffic-engineering
[Sysname-srv6-te] srv6-policy drop-upon-invalid enable
Related commands
drop-upon-invalid
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
When the device forwards a packet through an SRv6 TE policy, it must encapsulate that packet with the SID list of the SRv6 TE policy. Supported encapsulation modes include:
· 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. 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.
· 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. 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.
· 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 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.
· 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. 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 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.
In SRv6 TE view, 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.
In SRv6 TE view, 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 globally.
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.
Views
SRv6 TE view
Predefined user roles
network-admin
Usage guidelines
If traffic is steered to an SRv6 TE policy 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.
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 configure the local End.X SID encapsulation and also enable the reduced encapsulation mode by using the srv6-policy encapsulation-mode encaps reduced command in SRv6 TE view, the local End.X SID encapsulation applies.
Examples
# Configure the device to include the local End.X SID in the SRH of the packets forwarded by SRv6 TE policies.
<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 traffic is steered to an SRv6 TE policy 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.
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 srv6-policy encapsulation-mode encaps include local-end.x command and the srv6-policy encapsulation-mode insert include local-end.x command for an SRv6 TE policy, the most recent configuration takes effect.
In SRv6 TE view, 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
# 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 ignore-last-sid
Use srv6-policy forwarding ignore-last-sid to enable all SRv6 TE policies to forward packets without using the last SID in the SID list.
Use undo srv6-policy forwarding ignore-last-sid to restore the default.
Syntax
srv6-policy forwarding ignore-last-sid
undo srv6-policy forwarding ignore-last-sid
Default
The feature is disabled.
Views
SRv6 TE view
Predefined user roles
network-admin
Usage guidelines
In an SRv6 VPN scenario, to forward a public network packet through the SRv6 TE policy, the device encapsulates an SRH into the packet. The SRH contains the SID list of the SRv6 TE policy and the SID assigned to the VPN instance or public network instance (End.DT4 SID, for example). Both the last SID in the SID list and the End.DT4 SID are used to identify the egress node. To reduce the SRv6 packet size, you can configure this command to use only the End.DT4 SID to identify the egress node.
You can configure this feature 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 all SRv6 TE policies to forward packets without using the last SID in the SID list.
<Sysname> system-view
[Sysname] segment-routing ipv6
[Sysname-segment-routing-ipv6] traffic-engineering
[Sysname-srv6-te] srv6-policy forwarding ignore-last-sid
Related commands
forwarding ignore-last-sid
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
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 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
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 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 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
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 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.
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
# 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
mdc-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 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
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 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 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
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 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.
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
# 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
· 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 the ifit measure mode command is executed in SRv6 TE policy view and the srv6-policy ifit measure mode command is executed 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 immediate-reoptimization
Use srv6-policy immediate-reoptimization to immediately reoptimize all SRv6 TE policies enabled with candidate path optimization.
Syntax
srv6-policy immediate-reoptimization
Views
User view
Predefined user roles
network-admin
Usage guidelines
After an SRv6 TE policy is enabled with candidate path optimization, you can execute this command to trigger an immediate optimization to switch the candidate path of the SRv6 TE policy to the optimal path.
Examples
# Immediately reoptimize all SRv6 TE policies enabled with candidate path optimization.
<Sysname> srv6-policy immediate-reoptimization
srv6-policy locator
Use srv6-policy locator to specify a locator for SRv6 TE.
Use undo srv6-policy locator to cancel the locator configuration.
Syntax
srv6-policy locator locator-name
undo srv6-policy locator
Default
No locator is specified for SRv6 TE.
Views
SRv6 TE view
Predefined user roles
network-admin
Parameters
locator-name: Specifies a locator by its name, a case-sensitive string of 1 to 31 characters.
Usage guidelines
The locator specified in SRv6 TE view restricts the BSID range. Only BSIDs within the range of the locator can take effect.
You cannot change the locator for SRv6 TE by repeatedly executing this command. To change the locator, first execute the undo srv6-policy locator command to remove the specified locator and then execute the srv6-policy locator command to specify a new locator.
Examples
# Specify locator test1 in SRv6 TE view.
<Sysname> system-view
[Sysname] segment-routing ipv6
[Sysname-segment-routing-ipv6] traffic-engineering
[Sysname-srv6-te] srv6-policy locator test1
srv6-policy log enable
Use srv6-policy log enable to enable SRv6 TE policy logging.
Use undo srv6-policy log enable to disable SRv6 TE policy logging.
Syntax
srv6-policy log enable
undo srv6-policy log enable
Default
SRv6 TE policy logging is disabled.
Views
SRv6 TE view
Predefined user roles
network-admin
Predefined user roles
This command enables the device to generate logs for SRv6 TE policy state changes and resource usage anomalies. The administrator can use the logging information to audit SRv6 TE policies. The device delivers logs to its information center. The information center processes the logs according to user-defined output rules (whether to output logs and where to output). For more information about the information center, see System Management Configuration Guide.
Examples
# Enable SRv6 TE policy logging.
<Sysname> system-view
[Sysname] segment-routing ipv6
[Sysname-segment-routing-ipv6] traffic-engineering
[Sysname-srv6-te] srv6-policy log enable
srv6-policy path verification enable
Use srv6-policy path verification enable to enable path connectivity verification for all SRv6 TE policies.
Use undo srv6-policy path verification enable to disable path connectivity verification for all SRv6 TE policies.
Syntax
srv6-policy path verification [ specified-sid ] enable [ rib-check-only ]
undo srv6-policy path verification enable
Default
Path connectivity verification is disabled for all SRv6 TE policies.
Views
SRv6 TE view
Predefined user roles
network-admin
Parameters
specified-sid: Enables path connectivity verification only for the SIDs specified with the verification keyword in the index command. If you do not specify the specified-sid keyword, all SIDs in the SID list will be verified.
rib-check-only: Checks the reachability of locator prefixes associated with all SRv6 SIDs in the SID list without checking the existence of the SRv6 SIDs in the topology. If you do not specify this keyword, the device checks the reachability of locator prefixes associated with all SRv6 SIDs in the SID list and the existence of the SRv6 SIDs in the topology.
Usage guidelines
You must configure this command on the first node of the SRv6 TE policy.
Typically, the controller deploys the SID list of an SRv6 TE policy. Without BFD configured, the first node cannot immediately detect path failures in the SRv6 TE policy. It only changes the SID list of the SRv6 TE policy as instructed by the controller that completes path recalculation upon detecting a topology change. If the controller or the link to the controller fails, the first node will be unable to detect failures and change SID lists, resulting in traffic loss.
For fast traffic switchover and high availability, you can enable path connectivity verification for the first node of the SRv6 TE policy. This feature enables the first node to collect network topology information, and verify all SID lists in the SRv6 TE policy as follows:
· If all SRv6 SIDs exist in the topology and the associated locator prefixes are routable, the SID list is valid.
· If any SRv6 SIDs do not exist in the topology or any of the associated locator prefixes are not routable, the SID list is invalid.
Upon detecting an invalid SID list (SID list failure), the first node changes paths as follows:
· If the valid candidate paths of the SRv6 TE policy contain multiple SID lists, and one of the SID list fails, traffic is distributed to other valid SID lists.
· If the SRv6 TE policy has valid primary and backup candidate paths, and all SID lists for the primary candidate path fail, traffic is distributed to the backup candidate path.
· If all valid candidate paths of the SRv6 TE policy fail, the SRv6 TE policy is faulty and an associated protection action is taken (for example, MPLS L3VPN FRR).
You can configure SRv6 TE policy path connectivity verification in both SRv6 TE view and SRv6 TE policy view. The configuration in SRv6 TE policy view takes precedence over the configuration in SRv6 TE view. If path connectivity verification is not configured for an SRv6 TE policy, the configuration in SRv6 TE applies.
The first node must have all SRv6 SIDs and routes in the IGP domain to detect their status through the following settings:
· Enable the IGP domain to forward routing information through IPv6 IS-IS.
· Configure the distribute link-state command in IS-IS view for the first node to report link status.
If a BSID exists in the segment list path, path connectivity verification will fail because the BSID cannot be flooded in the IGP topology. Do not configure this command in the scenario where BSID is deployed.
After path connectivity verification is enabled for an SRv6 TE policy, the device verifies the validity of all SIDs in the SID list. If the SID list contains an inter-AS SID (for example, the BGP Peer SID allocated by BGP EPE) or contains the BSID of another SRv6 TE policy, the path connectivity verification will fail. This is because a BSID or BGP Peer SID cannot be flooded in the IGP topology.
To resolve this issue, you can execute the following commands to configure the path connectivity verification only verifies the validity of specific SIDs:
· Use the index command to specify the verification keyword for the SIDs to be verified. Do not specify this keyword for a BSID or BGP EPE SID in the SID list.
· Specify the specified-sid keyword when you execute the path verification command in SRv6 TE policy view or the srv6-policy path verification enable command in SRv6 TE view.
Examples
# Enable path connectivity verification for all SRv6 TE policies.
<Sysname> system-view
[Sysname] segment-routing ipv6
[Sysname-segment-routing-ipv6] traffic-engineering
[Sysname-srv6-te] srv6-policy path verification enable
Related commands
distribute (Layer 3—IP Routing Command Reference)
path verification
srv6-policy pce delegation enable
Use srv6-policy pce delegation enable to enable PCE delegation for SRv6 TE policies globally.
Use undo srv6-policy pce delegation enable to disable PCE delegation for SRv6 TE policies globally.
Syntax
srv6-policy pce delegation enable
undo srv6-policy pce delegation enable
Default
PCE delegation for SRv6 TE policies is disabled globally.
Views
SRv6 TE view
Predefined user roles
network-admin
Usage guidelines
After PCE delegation for an SRv6 TE policy is enabled, the PCC delegates the policy's candidate paths to a PCE. The PCC creates or updates candidate paths according to the creation or update requests received from the PCE.
You can configure PCE delegation for all 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 both the srv6-policy pce delegation enable command and the srv6-policy pce passive-delegate report-only enable command in SRv6 TE view, the srv6-policy pce passive-delegate report-only enable command takes effect.
Examples
# Enable PCE delegation for SRv6 TE policies globally.
<Sysname> system-view
[Sysname] segment-routing ipv6
[Sysname-segment-routing-ipv6] traffic-engineering
[Sysname-srv6-te] srv6-policy pce delegation enable
Related commands
pce delegation
srv6-policy pce passive-delegate report-only enable
srv6-policy pce passive-delegate report-only enable
Use srv6-policy pce passive-delegate report-only enable to enable the passive delegation report only feature globally.
Use undo srv6-policy pce passive-delegate report-only enable to disable the passive delegation report only feature globally.
Syntax
srv6-policy pce passive-delegate report-only enable
undo srv6-policy pce passive-delegate report-only enable
Default
The passive delegation report only feature is disabled globally.
Views
SRv6 TE view
Predefined user roles
network-admin
Usage guidelines
The passive delegation report only feature enables the device to report candidate path information of an SRv6 TE policy to the PCE without delegating the policy to the PCE.
When the device delegates only part of its SRv6 TE policies to a PCE, the PCE does not have complete SRv6 TE policy candidate path information to calculate global bandwidth information. You can enable the device to report information about the undelegated SRv6 TE policies to the PCE without using the PCE to compute candidate paths for the policies.
You can configure the passive delegation report only feature for all 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 both the srv6-policy pce delegation enable command and the srv6-policy pce passive-delegate report-only enable command in SRv6 TE view, the srv6-policy pce passive-delegate report-only enable command takes effect.
Examples
# Enable the passive delegation report only feature globally for all SRv6 TE policies.
<Sysname> system-view
[Sysname] segment-routing ipv6
[Sysname-segment-routing-ipv6] traffic-engineering
[Sysname-srv6-te] srv6-policy pce passive-delegate report-only enable
Related commands
pce passive-delegate report-only
srv6-policy pce delegation enable
srv6-policy reoptimization
Use srv6-policy reoptimization to enable candidate path reoptimization for SRv6 TE policies globally.
Use undo srv6-policy reoptimization to disable candidate path reoptimization for SRv6 TE policies globally.
Syntax
srv6-policy reoptimization [ frequency seconds ]
undo srv6-policy reoptimization
Default
Candidate path reoptimization for SRv6 TE policies is globally disabled.
Views
SRv6 TE policy view
Predefined user roles
network-admin
Parameters
frequency seconds: Sets the candidate path reoptimization frequency, in the range of 1 to 604800 seconds. The default frequency is 3600 seconds. If you set a frequency smaller than 60 seconds, the device performs reoptimization every 60 seconds.
Usage guidelines
This feature enables the PCE to periodically compute paths and notify the PCC to update path information, so that SRv6 TE policies can use the optimal path to establish the candidate path.
For example, an SRv6 TE policy uses a path other than the optimal path to establish the candidate path because the optimal path does not have sufficient link bandwidth. This feature enables the SRv6 TE policy to switch the candidate path to the optimal path when the link bandwidth becomes sufficient.
You can configure candidate path reoptimization for all 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 candidate path reoptimization for SRv6 TE policies globally.
<Sysname> system-view
[Sysname] segment-routing ipv6
[Sysname-segment-routing-ipv6] traffic-engineering
[Sysname-srv6-te] srv6-policy reoptimization
Related commands
reoptimization
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. If you do not specify this option, the remote discriminator configured with the sbfd destination ipv6 remote-discriminator command 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 SBFD uses the multihop BFD session settings configured in system view.
backup-template backup-template-name: Specifies a BFD session parameter template for the backup SID list. The backup-template-name argument indicates the template name, a case-sensitive string of 1 to 63 characters. If you do not specify this option, the SBFD uses the multihop BFD session settings configured in system view.
Predefined user roles
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 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 destination ipv4 remote-discriminator (High Availability Command Reference)
sbfd local-discriminator (High Availability Command Reference)
srv6-policy suppress-flapping
Use srv6-policy suppress-flapping to configure flapping suppression parameters for SRv6 TE policies.
Use undo srv6-policy suppress-flapping to restore the default.
Syntax
srv6-policy suppress-flapping { detect-interval detect-interval | threshold threshold | resume-interval resume-interval } *
undo srv6-policy suppress-flapping { detect-interval | threshold | resume-interval } *
Default
The SRv6 TE policy flapping detection interval is 60 seconds, the flapping suppression threshold is 10, and the flapping detection resumption interval is 120 seconds.
Views
SRv6 TE view
Predefined user roles
network-admin
Parameters
detect-interval detect-interval: Specifies the flapping detection interval, in the range of 1 to 300 seconds. The default detection interval is 60 seconds.
threshold threshold: Specifies the flapping suppression threshold, in the range of 1 to 1000. The default threshold value is 10.
resume-interval resume-interval: Specifies the resumption interval for flapping suppression, in the range of 2 to 1000 seconds. The default resumption interval is 120 seconds.
Usage guidelines
After SRv6 TE policy flapping suppression is enabled, the device starts a counter for an SRv6 TE policy to count the SID list flapping events for the policy.
· If the state of a SID list changes from down to up within the flapping detection interval, an SID list flapping event occurs, and the flapping count increases by 1.
· If the time for a SID list to change from down to up is longer than the resumption interval, the flapping counter is cleared.
· If the flapping count exceeds the flapping suppression threshold, the SRv6 TE policy enters flapping suppression state. In this state, the SRv6 TE policy does not update the SID list state but keep the SID list in down state, and the flapping counter is not cleared.
· When the suppression state lasts for the resumption interval, the device ends the suppression state of the SRv6 TE policy and clears the flapping counter.
The resumption interval (set by resume-interval) must be greater than the flapping detection interval (set by detect-interval).
Examples
# Configure flapping suppression parameters for SRv6 TE policies.
<Sysname> system-view
[Sysname] segment-routing ipv6
[Sysname-segment-routing-ipv6] traffic-engineering
[Sysname-srv6-te] srv6-policy suppress-flapping detect-interval 70 threshold 5 resume-interval 130
Related commands
srv6-policy suppress-flapping disable
srv6-policy suppress-flapping disable
Use srv6-policy suppress-flapping disable to disable flapping suppression for SRv6 TE policies globally.
Use undo srv6-policy suppress-flapping disable to enable flapping suppression for SRv6 TE policies globally.
Syntax
srv6-policy suppress-flapping disable
undo srv6-policy suppress-flapping disable
Default
Flapping suppression for SRv6 TE policies is enabled globally.
Views
SRv6 TE view
Predefined user roles
network-admin
Usage guidelines
When SRv6 TE polices flap frequently, you can enable this feature to reduce the impact of the flappings on traffic forwarding.
After SRv6 TE policy flapping suppression is enabled, the device starts a counter for an SRv6 TE policy to count the SID list flapping events for the policy.
· If the state of a SID list changes from down to up within the flapping detection interval, an SID list flapping event occurs, and the flapping count increases by 1.
· If the time for a SID list to change from down to up is longer than the resumption interval, the flapping counter is cleared.
· If the flapping count exceeds the flapping suppression threshold, the SRv6 TE policy enters flapping suppression state. In this state, the SRv6 TE policy does not update the SID list state but keep the SID list in down state, and the flapping counter is not cleared.
· When the suppression state lasts for the resumption interval, the device ends the suppression state of the SRv6 TE policy and clears the flapping counter.
Examples
# Disable flapping suppression for SRv6 TE policies globally.
<Sysname> system-view
[Sysname] segment-routing ipv6
[Sysname-segment-routing-ipv6] traffic-engineering
[Sysname-srv6-te] srv6-policy suppress-flapping disable
Related commands
srv6-policy suppress-flapping
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
srv6-policy up-delay
Use srv6-policy up-delay to set the delay time for bringing up SRv6 TE policies.
Use undo srv6-policy up-delay to restore the default.
Syntax
srv6-policy up-delay delay-time
undo srv6-policy up-delay
Default
The device does not delay bringing up SRv6 TE policies.
Views
SRv6 TE view
Predefined user roles
network-admin
Parameters
delay-time: SRv6 TE policy up delay time, in the range of 1 to 600000 milliseconds.
Usage guidelines
After an SRv6 TE policy recovers from a fault, the device waits for the delay time before bringing up the SRv6 TE policy. This is to ensure that the fault is completely removed so as to avoid packet loss caused by SRv6 TE policy flapping.
After this command is executed, the device starts different delay timers for an SRv6 TE policy according to the BFD/SBFD configuration for the SRv6 TE policy.
· If BFD/SBFD is not enabled, the device starts an LSP delay timer when the SID list state changes from Down to Up.
· If BFD/SBFD is enabled, the device starts a BFD delay timer when the BFD/SBFD session state changes from Down to Up.
To view the BFD/SBFD configuration, SID list state, and BFD/SBFD session state, execute the display segment-routing ipv6 te policy command.
Set a proper SRv6 TE policy-up delay time according to your network conditions. A very long delay time will cause an SRv6 TE policy to be unable to process user traffic for a long time.
You can set the delay time 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 for multiple times, the most recent configuration takes effect. A new delay time setting does not apply to the SRv6 TE policies that are already in a delay process.
Examples
# Set the policy-up delay time to 10000 milliseconds for all SRv6 TE policies.
<Sysname> system-view
[Sysname] segment-routing ipv6
[Sysname-segment-routing-ipv6] traffic-engineering
[Sysname-srv6-te] srv6-policy up-delay 10000
Related commands
display segment-routing ipv6 te policy
up-delay
strict-sid-only enable
Use strict-sid-only enable to enable strict SID encapsulation for SID lists.
Use undo strict-sid-only enable to disable strict SID encapsulation for SID lists.
Syntax
strict-sid-only enable
undo strict-sid-only enable
Default
Strict SID encapsulation is disabled for SID lists.
Views
SRv6 TE policy path preference dynamic view
SRv6 TE ODN dynamic view
Predefined user roles
network-admin
Usage guidelines
Configure this command on the source node of an SRv6 TE policy.
The SID list of an SRv6 TE policy can be formed by End SIDs and End.X SIDs. An End SID cannot uniquely identify a link. When the links in the network flap frequently, the forwarding paths of the SRv6 TE policy might change. To ensure stability of forwarding paths, use this command to enable the SRv6 TE policy to include only End.X SIDs in the calculated SID lists.
Examples
# In SRv6 TE policy path preference dynamic view, enable strict SID encapsulation for SID lists.
<Sysname> system-view
[Sysname] segment-routing ipv6
[Sysname-segment-routing-ipv6] traffic-engineering
[Sysname-srv6-te] policy a1
[Sysname-srv6-te-policy-a1] candidate-paths
[Sysname-srv6-te-policy-a1-path] preference 200
[Sysname-srv6-te-policy-a1-path-pref-200] dynamic
[Sysname-srv6-te-policy-a1-path-pref-200-dyna] strict-sid-only enable
# In SRv6 TE ODN dynamic view, enable strict SID encapsulation for SID lists.
<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] dynamic
[Sysname-srv6-te-odn-1-dyna] strict-sid-only enable
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 SRv6 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.
Usage guidelines
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 TTL field of 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
type
Use type to specify a metric for the SRv6 TE policy to perform dynamic path calculation.
Use undo type to restore the default.
Syntax
type { hopcount | igp | latency | te }
undo type
Default
No metric is specified. The SRv6 TE policy cannot perform dynamic path calculation.
Views
Metric type view
SRv6 TE ODN dynamic metric type view
Predefined user roles
network-admin
Parameters
hopcount: Specifies the hop count metric to select the link with minimum hops.
igp: Specifies the IGP link cost metric to select the link with minimum IGP link cost.
latency: Specifies the interface latency metric to select the link with the minimum interface latency.
te: Specifies the TE cost metric to select the link with minimum TE cost.
Examples
# Specify the hop count metric in metric type view.
<Sysname> system-view
[Sysname] segment-routing ipv6
[Sysname-segment-routing-ipv6] traffic-engineering
[Sysname-srv6-te] policy p1
[Sysname-srv6-te-policy-p1] candidate-paths
[Sysname-srv6-te-policy-p1-path] preference 10
[Sysname-srv6-te-policy-p1-path-pref-10] dynamic
[Sysname-srv6-te-policy-p1-path-pref-10-dyna] metric
[Sysname-srv6-te-policy-p1-path-pref-10-dyna-metric] type hopcount
# Specify the hop count metric in SRv6 TE ODN dynamic metric type 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] dynamic
[Sysname-srv6-te-odn-1-dynamic] metric
[Sysname-srv6-te-odn-1-dynamic-metric] type hopcount
up-delay
Use up-delay to set the delay time for bringing up an SRv6 TE policy.
Use undo up-delay to restore the default.
Syntax
up-delay delay-time
undo up-delay
Default
No policy-up delay time is set for an SRv6 TE policy, and the policy-up delay time set in SRv6 TE view applies.
Views
SRv6 TE policy view
Predefined user roles
network-admin
Parameters
delay-time: SRv6 TE policy-up delay time, in the range of 1 to 600000 milliseconds.
Usage guidelines
After an SRv6 TE policy recovers from a fault, the device waits for the delay time before bringing up the SRv6 TE policy. This is to ensure that the fault is completely removed so as to avoid packet loss caused by SRv6 TE policy flapping.
After this command is executed, the device starts different delay timers for an SRv6 TE policy according to the BFD/SBFD configuration for the SRv6 TE policy.
· If BFD/SBFD is not enabled, the device starts an LSP delay timer when the SID list state changes from Down to Up.
· If BFD/SBFD is enabled, the device starts a BFD delay timer when the BFD/SBFD session state changes from Down to Up.
To view the BFD/SBFD configuration, SID list state, and BFD/SBFD session state, execute the display segment-routing te policy command.
Set a proper SRv6 TE policy-up delay time according to your network conditions. A very long delay time will cause an SRv6 TE policy to be unable to process user traffic for a long time.
You can set the delay time 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 for multiple times, the most recent configuration takes effect. A new delay time setting does not apply to the SRv6 TE policies that are already in a delay process.
Examples
# Set the policy-up delay time to 10000 milliseconds for SRv6 TE policy p1.
<Sysname> system-view
[Sysname] segment-routing
[Sysname-segment-routing] traffic-engineering
[Sysname-sr-te ]policy p1
[Sysname-sr-te-policy-p1] up-delay 10000
Related commands
display segment-routing te policy
sr-policy up-delay
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] switch-period 3
