- Table of Contents
- Related Documents
-
Title | Size | Download |
---|---|---|
02-SR-MPLS TE policy commands | 483.18 KB |
default-color (public instance IPv4/IPv6 address family view)
default-color (VPN instance IPv4/IPv6 unicast address family view)
display bgp routing-table ipv4 sr-policy
display segment-routing te database
display segment-routing te forwarding
display segment-routing te policy
display segment-routing te policy last-down-reason
display segment-routing te policy statistics
display segment-routing te policy-group
display segment-routing te sbfd
display segment-routing te segment-list
forwarding statistics interval
reset segment-routing te forwarding statistics
snmp-agent trap enable sr-policy
sr-policy backup hot-standby enable
sr-policy bfd first-fail-timer
sr-policy bfd trigger path-down enable
sr-policy switch-delay delete-delay
SR-MPLS TE policy commands
address-family ipv4 sr-policy
Use address-family ipv4 sr-policy to create the BGP IPv4 SR policy address family and enter its view, or enter the view of the existing BGP IPv4 SR policy address family.
Use undo address-family ipv4 sr-policy to delete the BGP IPv4 SR policy address family and all the configuration in the BGP IPv4 SR policy address family.
Syntax
address-family ipv4 sr-policy
undo address-family ipv4 sr-policy
Default
The BGP IPv4 SR policy address family does not exist.
Views
BGP instance view
Predefined user roles
network-admin
Usage guidelines
The configuration in BGP IPv4 SR policy address family view applies only to routes and peers in the BGP IPv4 SR policy address family.
Examples
# In BGP instance view, create the BGP IPv4 SR policy address family and enter its view.
<Sysname> system-view
[Sysname] bgp 100
[Sysname-bgp-default] address-family ipv4 sr-policy
[Sysname-bgp-default-srpolicy-ipv4]
advertise ebgp enable
Use advertise ebgp enable to advertise BGP IPv4 SR policy routes to EBGP peers.
Use undo advertise ebgp enable to restore the default.
Syntax
advertise ebgp enable
undo advertise ebgp enable
Default
BGP IPv4 SR policy routes are not advertised to EBGP peers.
Views
BGP IPv4 SR policy address family view
Predefined user roles
network-admin
Usage guidelines
By default, only IBGP peers exchange BGP IPv4 SR policy routes. Execute this command to advertise BGP IPv4 SR policy routes to EBGP peers.
Examples
# Advertise BGP IPv4 SR policy routes to EBGP peers.
<Sysname> system-view
[Sysname] bgp 100
[Sysname-bgp-default] address ipv4 sr-policy
[Sysname-bgp-default-srpolicy-ipv4] advertise ebgp enable
backup hot-standby
Use backup hot-standby to configure hot standby for an SR-MPLS TE policy.
Use undo backup hot-standby to restore the default.
Syntax
backup hot-standby { disable | enable }
undo backup hot-standby
Default
Hot standby is not configured for an SR-MPLS TE policy.
Views
SR-MPLS TE policy view
Predefined user roles
network-admin
Parameters
disable: Disables hot standby for the SR-MPLS TE policy.
enable: Enables hot standby for the SR-MPLS TE policy.
Usage guidelines
The hot standby feature takes the candidate path with the greatest preference value in the SR-MPLS TE policy as the primary path and that with the second greatest preference value as the standby path. When the forwarding paths corresponding to all SID lists of the primary path fail, the standby path immediately takes over to minimize service interruption.
You can enable hot standby for all SR-MPLS TE policies globally in SR TE view or for a specific SR-MPLS TE policy in SR-MPLS TE policy view. The policy-specific configuration takes precedence over the global configuration. An SR-MPLS TE policy uses the global configuration only when it has no policy-specific configuration.
Examples
# Enable hot standby for SR-MPLS TE policy 1.
<Sysname> system-view
[Sysname] segment-routing
[Sysname-segment-routing] traffic-engineering
[Sysname-sr-te] policy 1
[Sysname-sr-te-policy-1] backup hot-standby enable
Related commands
sr-policy backup hot-standby enable
bfd trigger path-down
Use bfd trigger path-down to enable BFD session down events to trigger SR-MPLS TE policy path reselection.
Use undo bfd trigger path-down to restore the default.
Syntax
bfd trigger path-down { disable | enable }
undo bfd trigger path-down
Default
This feature is not configured for an SR-MPLS TE policy, and the configuration in SR TE view applies.
Views
SR-MPLS TE policy view
Predefined user roles
network-admin
Parameters
disable: Disables BFD session down events from triggering SR-MPLS TE policy path reselection.
enable: Enables BFD session down events to trigger SR-MPLS TE policy path reselection.
Usage guidelines
By default, when an SR-MPLS TE policy contains multiple valid candidate paths:
· If hot standby is not enabled, SBFD detects all the SID lists of the optimal candidate path and establishes an SBFD session for each of the SID lists. When all the SBFD sessions are down, the SR-MPLS TE policy does not reselect a candidate path and packets are no longer forwarded through the SR-MPLS TE policy.
· If hot standby is enabled, SBFD detects all the SID lists of the main and backup candidate paths and establishes an SBFD session for each of the SID lists.
¡ When all the SBFD sessions for the main path are down, the SR-MPLS TE policy switches traffic to the backup path and does not reselect a candidate path.
¡ When all the SBFD sessions for the main and backup paths are down, the SR-MPLS TE policy does not reselect a candidate path and packets are no longer forwarded through the SR-MPLS TE policy.
After you enable this feature (by executing the bfd trigger path-down enable command) for an SR-MPLS TE policy that contains multiple valid candidate paths:
· If hot standby is not enabled, SBFD detects all the SID lists of the optimal candidate path and establishes an SBFD session for each of the SID lists. When all the SBFD sessions are down, the SR-MPLS TE policy reselects a candidate path and uses the new candidate path to forward packets. If no valid candidate path is available during the resection, packets cannot be forwarded through the SR-MPLS TE policy.
· If hot standby is enabled, SBFD detects all the SID lists of the main and backup candidate paths and establishes an SBFD session for each of the SID lists.
¡ When all the SBFD sessions for the main path are down, the SR-MPLS TE policy switches traffic to the backup path and reselects the main and backup paths.
¡ When all the SBFD sessions for the main and backup paths are down, the SR-MPLS TE policy reselects the main and backup paths and forwards packets through the new main path.
¡ If no valid candidate path is available during the resection, packets cannot be forwarded through the SR-MPLS TE policy.
Before you enable this feature for an SR-MPLS TE policy, create an SBFD session for the policy first.
You can enable this feature for all SR-MPLS TE policies globally in SR TE view or for a specific SR-MPLS TE policy in SR-MPLS TE policy view. The policy-specific configuration takes precedence over the global configuration. An SR-MPLS TE policy uses the global configuration only when it has no policy-specific configuration.
Examples
# Enable BFD session down events to trigger candidate path reselection for SR-MPLS TE policy a1.
<Sysname> system-view
[Sysname] segment-routing
[Sysname-segment-routing] traffic-engineering
[Sysname-sr-te] policy a1
[Sysname-sr-te-policy-a1] bfd trigger path-down enable
Related commands
sbfd
sr-policy bfd trigger path-down enable
sr-policy sbfd enable
binding-sid
Use binding-sid to configure a BSID for an SR-MPLS TE policy.
Use undo binding-sid to delete the BSID.
Syntax
binding-sid mpls mpls-label
undo binding-sid
Default
No BSID is configured for an SR-MPLS TE policy.
Views
SR-MPLS TE policy view
Predefined user roles
network-admin
Parameters
mpls mpls-label: Specifies the BSID value, which is an MPLS label value in the range of 16 to 1048575.
Usage guidelines
You can use this command to manually configure a BSID for an SR-MPLS TE policy or leave the SR-MPLS TE policy to obtain a BSID automatically. If an SR-MPLS TE policy has only color and endpoint configuration, the SR-MPLS TE policy will automatically request a BSID.
The manually configured BSID has a higher priority over the automatically obtained BSID.
If you configure an MPLS label as the BSID but the label is not in the range of the SRLB or is already used by a protocol, the configuration does not take effect. For more information about SRLB, see SR-MPLS configuration in Segment Routing Configuration Guide.
If you execute this command multiple times, the most recent configuration takes effect.
The candidate paths of the same SR-MPLS TE policy have the same BSID.
Examples
# Set the BSID of SR-MPLS TE policy srpolicy to 82000.
<Sysname> system-view
[Sysname] segment-routing
[Sysname-segment-routing] traffic-engineering
[Sysname-sr-te] policy srpolicy
[Sysname-sr-te-policy-srpolicy] binding-sid mpls 82000
Related commands
color end-point
candidate-paths
Use candidate-paths to create and enter the candidate path view for an SR-MPLS TE policy, or enter the existing candidate path view.
Use undo candidate-paths to delete the candidate path view and all the configurations in the view.
Syntax
candidate-paths
undo candidate-paths
Default
The candidate path view for an SR-MPLS TE policy does not exist.
Views
SR-MPLS TE policy view
Predefined user roles
network-admin
Examples
# Create the SR-MPLS TE policy candidate paths instance and enter its view.
<Sysname> system-view
[Sysname] segment-routing
[Sysname-segment-routing] traffic-engineering
[Sysname-sr-te] policy srpolicy
[Sysname-sr-te-policy-srpolicy] candidate-paths
[Sysname-sr-te-policy-srpolicy-path]
color end-point
Use color end-point to configure the color and endpoint attributes of an SR-MPLS TE policy.
Use undo color to delete the color and endpoint settings of an SR-MPLS TE policy.
Syntax
color color-value end-point ipv4 ipv4-address
undo color
Default
The color and endpoint attributes of an SR-MPLS TE policy are not configured.
Views
SR-MPLS TE policy view
Predefined user roles
network-admin
Parameters
color-value: Specifies the color attribute value, in the range of 0 to 4294967295.
ipv4-address: Specifies the endpoint IP address.
Usage guidelines
An SR-MPLS TE policy is uniquely identified by the following items:
· BSID—SID of the ingress node.
· Color—Color attribute for the forwarding path. You can use the color attribute to distinguish an SR-MPLS TE policy from other SR-MPLS TE policies that are configured for the same source and destination nodes.
· Endpoint—IP address of the destination node.
If you execute this command multiple times, the most recent configuration takes effect.
Different SR-MPLS TE policies cannot have the same color and endpoint IP address combination.
Examples
# Configure the color as 20 and endpoint IP address as 10.0.0.1 for SR-MPLS TE policy srpolicy.
<Sysname> system-view
[Sysname] segment-routing
[Sysname-segment-routing] traffic-engineering
[Sysname-sr-te] policy srpolicy
[Sysname-sr-te-policy-srpolicy] color 20 end-point ipv4 10.0.0.1
Related commands
binding-sid
color match dscp
Use color match dscp to create color-to-DSCP mappings for an SR-MPLS TE policy group.
Use undo color match dscp to delete color-to-DSCP mappings for the SR-MPLS TE policy group.
Syntax
color color-value match dscp { ipv4 | ipv6 } dscp-value-list
undo color color-value match dscp { ipv4 | ipv6 } dscp-value-list
color color-value match dscp { ipv4 | ipv6 } default
undo color color-value match dscp { ipv4 | ipv6 } [ default ]
Default
No color-to-DSCP mappings are created for an SR-MPLS TE policy group.
Views
SR-MPLS TE policy group view
Predefined user roles
network-admin
Parameters
color-value: Specifies the color attribute value, in the range of 0 to 4294967295.
ipv4: Specifies DSCP values of IPv4 packets.
ipv6: Specifies DSCP values of IPv6 packets.
dscp-value-list: Specifies a space-separated list of up to 32 DSCP value items. Each item specifies a DSCP value in the range of 0 to 63 or a range of DSCP values in the form of dscp-value1 to dscp-value2. The value for the dscp-value2 argument must be greater than the value for the dscp-value1 argument.
default: Specifies a default color-to-DSCP mapping. Packets that do not match any mappings are steered to the default SR-MPLS TE policy for forwarding.
Usage guidelines
You can map the color values of only valid SR-MPLS TE policies to DSCP values.
You can configure color-to-DSCP mappings separately for the IPv4 address family and IPv6 address family. For a specific address family, a DSCP value can be mapped to only one color value.
Use the color match dscp default command to specify the default SR-MPLS TE policy for an address family. If no SR-MPLS TE policy in an SR-MPLS TE policy group matches a specific DSCP value, the default SR-MPLS TE policy is used to forward packets containing the DSCP value. Only one default SR-MPLS TE policy can be specified for an address family.
When the device receives an IPv4 or IPv6 packet that does not match any color-to-DSCP mapping, the device selects a valid SR-MPLS TE policy for the packet in the following order:
1. The default SR-MPLS TE policy specified for the same address family as the packet.
2. The default SR-MPLS TE policy specified for the other address family.
3. The SR-MPLS TE policy mapped to the smallest DSCP value in the same address family as the packet.
4. The SR-MPLS TE policy mapped to the smallest DSCP value in the other address family.
Examples
# Map DSCP value 30 to color value 20 for SR-MPLS TE policy group 10 so that IPv4 packets with DSCP value 30 are steered to the SR-MPLS TE policy with color value 20.
<Sysname> system-view
[Sysname] segment-routing
[Sysname-segment-routing] traffic-engineering
[Sysname-sr-te] policy-group 10
[Sysname-sr-te-policy-group-10] color 20 match dscp ipv4 30
default-color (public instance IPv4/IPv6 address family view)
Use default-color to configure a default color value for public route recursion to an SR-MPLS TE policy.
Use undo default-color to restore the default.
Syntax
default-color color-value
undo default-color
Default
No default color value is configured.
Views
Public instance IPv4 address family view
Public instance IPv6 address family view
Predefined user roles
network-admin
Parameters
color-value: Default color value in the range of 0 to 4294967295.
Usage guidelines
The local PE uses the default color value to match an SR-MPLS TE policy for a received public network route if the route does not carry a color extended community and no color is added to the route through a routing policy.
This command applies only to the public network routes learned from a remote PE.
The default color value configured by this command is used only for SR-MPLS TE policy traffic steering. It 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 SR-MPLS TE policy.
<Sysname> system-view
[Sysname] ip public-instance
[Sysname-public-instance] address-family ipv4
[Sysname-public-instance-ipv4] default-color 100
default-color (VPN instance IPv4/IPv6 unicast address family view)
Use default-color to configure a default color value for L3VPN route recursion to an SR-MPLS TE policy.
Use undo default-color to restore the default.
Syntax
default-color color-value [ evpn ]
undo default-color [ evpn ]
Default
No default color value is configured.
Views
VPN instance IPv4 unicast address family view
VPN instance IPv6 unicast address family view
Predefined user roles
network-admin
Parameters
color-value: Default color value in the range of 0 to 4294967295.
evpn: Specifies the EVPN L3VPN service. If you do not specify this keyword, the default color applies to all L3VPN services (including EVPN L3VPN and MPLS L3VPN) route recursion to an SR-MPLS TE policy.
Usage guidelines
The local PE uses the default color value to match an SR-MPLS TE policy for a received VPNv4, VPNv6, or EVPN IP prefix route if the route does not carry a color extended community and no color is added to the route through a routing policy.
This command applies only to the VPN routes learned from a remote PE.
The default color value configured by this command is used only for SR-MPLS TE policy traffic steering. It does not used in route advertisement.
If you execute this command multiple times, the most recent configuration takes effect.
Examples
# In IPv4 unicast address family view for VPN instance vpn1, set the default color to 100 for EVPN L3VPN route recursion to an SR-MPLS TE policy.
<Sysname> system-view
[Sysname] ip vpn-instance vpn1
[Sysname-vpn-instance-vpn1] address-family ipv4
[Sysname-vpn-ipv4-vpn1] default-color 100 evpn
display bgp routing-table ipv4 sr-policy
Use display bgp routing-table ipv4 sr-policy to display information about BGP IPv4 SR policy routes.
Syntax
display bgp [ instance instance-name ] routing-table ipv4 sr-policy [ sr-policy-prefix [ advertise-info ] ]
display bgp [ instance instance-name ] routing-table ipv4 sr-policy [ as-path-acl { as-path-acl-number | as-path-acl-name } | as-path-regular-expression regular-expression ]
display bgp [ instance instance-name ] routing-table ipv4 sr-policy [ color color-value [ end-point ipv4 ipv4-address ] | end-point ipv4 ipv4-address ]
display bgp [ instance instance-name ] routing-table ipv4 sr-policy [ peer { ipv4-address | ipv6-address } { advertised-routes | received-routes } [ sr-policy-prefix [ verbose ] | color color-value [ end-point ipv4 ipv4-address ] | end-point ipv4 ipv4-address | statistics [ color color-value [ end-point ipv4 ipv4-address ] | end-point ipv4 ipv4-address ] ] ]
display bgp [ instance instance-name ] routing-table ipv4 sr-policy [ statistics [ color color-value [ end-point ipv4 ipv4-address ] | end-point ipv4 ipv4-address ] ]
display bgp [ instance instance-name ] routing-table ipv4 sr-policy peer { ipv4-address | ipv6-address } { accepted-routes | not-accepted-routes }
display bgp [ instance instance-name ] routing-table ipv4 sr-policy time-range min-time max-time
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
instance instance-name: Specifies a BGP instance by its name, a case-sensitive string of 1 to 31 characters. If you do not specify a BGP instance, this command displays information about the default instance.
sr-policy-prefix: Specifies a BGP IPv4 SR policy route prefix, which is a case-insensitive string of 1 to 512 characters in the format of SR policy route/mask length.
verbose: Displays detailed route information. If you do not specify this keyword, the command displays brief route information.
as-path-acl as-path-acl-number: Specifies an AS path ACL by its number, in the range of 1 to 256.
as-path-acl as-path-acl-name: Specifies an AS path ACL by its name, a case-sensitive string of 1 to 51 characters. The AS path ACL name cannot contain only digits.
as-path-regular-expression regular-expression: Specifies an AS path regular expression, a case-sensitive string of 1 to 256 characters.
color color-value: Specifies the color of a BGP IPv4 SR policy route, in the range of 0 to 4294967295.
end-point ipv4 ip-address: Specifies the endpoint IPv4 address of a BGP IPv4 SR policy.
advertise-info: Displays advertisement information about BGP IPv4 SR policy routes.
peer { ipv4-address | ipv6-address }: Specifies a peer by its IPv4 or IPv6 address.
advertised-routes: Displays information about the routes advertised to the specified peer.
received-routes: Displays information about the routes received from the specified peer.
statistics: Displays route statistics.
accepted-routes: Displays information about the routes received from the specified peer and permitted by the route acceptance policy.
not-accepted-routes: Displays information about the routes received from the specified peer but not accepted by the route acceptance policy.
time-range min-time max-time: Specifies a time range. This command displays information for routes that have persisted for a duration within the specified range since the last update. The min-time argument represents the minimum duration, and the max-time argument represents the maximum duration. The min-time and max-time arguments are in the format of <0-10000>d<0-23>h<0-59>m<0-59>s, where d represents days, h represents hours, m represents minutes, and s represents seconds, and <0-10000>, <0-23>, <0-59>, and <0-59> represent the value ranges for days, hours, minutes, and seconds, respectively.
Usage guidelines
If you do not specify any parameters, this command displays brief information about all BGP IPv4 SR policy routes.
Examples
# Display brief information about all BGP IPv4 SR policy routes.
<Sysname> display bgp routing-table ipv4 sr-policy
Total number of routes: 1
BGP local router ID is 2.2.2.2
Status codes: * - valid, > - best, d - dampened, h - history
s - suppressed, S - stale, i - internal, e - external
a – additional-path
Origin: i - IGP, e - EGP, ? - incomplete
* >i Network : [10][1][9.9.9.9]/96
NextHop : 2.1.1.2 LocPrf : 100
PrefVal : 0 OutLabel : NULL
MED : 0
Path/Ogn: i
# Display information about all BGP IPv4 SR policy routes whose duration since the last route update is within the specified time range in the default BGP instance.
<Sysname> display bgp routing-table ipv4 sr-policy time-range 1d1h1m1s 7d3h1m1s
Total number of routes: 1
BGP local router ID is 2.2.2.2
Status codes: * - valid, > - best, d - dampened, h - history
s - suppressed, S - stale, i - internal, e - external
a – additional-path
Origin: i - IGP, e - EGP, ? - incomplete
* >i Network : [10][1][9.9.9.9]/96
NextHop : 2.1.1.2 LocPrf : 100
PrefVal : 0 OutLabel : NULL
MED : 0 Route age : 06d01h12m44s
Table 1 Command output
Field |
Description |
Status codes |
Status codes of the route. |
Origin |
Origin of the route: · i – IGP—Originated in the AS. · e – EGP—Learned through an EGP. · ? – incomplete—Unknown origin. |
Network |
BGP IPv4 SR policy route, comprised of the following elements: · SR-MPLS TE policy candidate path preference. · SR-MPLS TE policy color attribute value. · Endpoint IP address. |
NextHop |
Next hop IP address. |
LocPrf |
Local preference value. |
PrefVal |
Preferred value of the route. |
OutLabel |
Outgoing label of the route. |
MED |
Multi-Exit Discriminator attribute value. |
Path/Ogn |
AS_PATH and ORIGIN attributes of the route: · AS_PATH—Records the ASs the route has passed. · ORIGIN—Identifies the origin of the route. |
Route age |
Time elapsed since the most recent route update, in <0-10000>d<0-23>h<0-59>m<0-59>s format, where d, h, m, and s represent days, hours, minutes, and seconds, respectively, and <0-10000>, <0-23>, <0-59>, and <0-59> represent the value ranges for d, h, m, and s, respectively. |
# Display detailed information about BGP IPv4 SR policy route [102][2][5.6.7.8]/96.
<Sysname> display bgp routing-table ipv4 sr-policy [102][2][5.6.7.8]/96
BGP local router ID: 2.2.2.2
Local AS number: 1
Paths: 1 available, 1 best
BGP routing table information of [102][2][5.6.7.8]:
From : 3.1.1.2 (10.11.113.29)
Original nexthop: 3.1.1.2
Route age : 00h33m33s
OutLabel : NULL
Ext-Community : <RT: 3.3.3.9:100>
RxPathID : 0x0
TxPathID : 0x0
AS-path : 2
Origin : igp
Attribute value : MED 0, pref-val 0
State : valid, external, best
IP precedence : N/A
QoS local ID : N/A
Traffic index : N/A
Tunnel encapsulation info:
Type: 15 (SR Policy)
Preference: 102
Binding SID: 10485
Path: 1
Weight: 1
SIDs: {3}
Table 2 Command output
Field |
Description |
Paths |
Route information: · available—Number of valid routes. · best—Number of optimal routes. |
BGP routing table information of [102][2][5.6.7.8] |
Information of the BGP IPv4 SR policy route [102][2][5.6.7.8], where: · [102] is the SR-MPLS TE policy candidate path preference · [2] is the SR-MPLS TE policy color attribute value. · [5.6.7.8] is the endpoint IP address. |
From |
IP address of the BGP peer that advertised the route. |
Original nexthop |
Original nexthop IP address. If the route was obtained from a BGP update message, the original next hop is the nexthop IP address in the message. |
Route age |
Time elapsed since the last update for the route. |
OutLabel |
Outgoing label of the route. |
Ext-Community |
Extended community attribute of the BGP route. |
RxPathID |
Received Add-Path ID of the route. |
TxPathID |
Advertised Add-Path ID of the route. |
AS-path |
AS_PATH attribute of the route. |
Origin |
Origin of the route: · igp—Originated in the AS. · egp—Learned through an EGP. · incomplete—Unknown origin. |
Attribute value |
BGP path attributes: · MED—MED value. · localpref—Local preference value. · pref-val—Preferred value. · pre—Protocol preference. |
Originator |
Peer that generated the route. |
Cluster list |
CLUSTER_LIST attribute value of the route. This field is not available for a route if the route does not contain the CLUSTER_LIST attribute. |
State |
Current state of the route. Options include: · valid—Valid route. · internal—Internal route. · external—External route. · local—Locally generated route. · synchronize—Synchronized route. · best—Optimal route. · delay—Delayed route. The route will be delayed for optimal route selection. This value is available only in detailed information of the route. · not preferred for reason—Reason why the route is not selected as the optimal route. For more information, see Table 3. |
IP precedence |
IP precedence of the route, in the range of 0 to 7. N/A indicates that the route does not support this field. |
QoS local ID |
QoS local ID of the route, in the range of 1 to 4095. N/A indicates that the route does not support this field. |
Traffic index |
Traffic index in the range of 1 to 64. N/A indicates that the route does not support this field. |
Type: 15 (SR Policy) |
The tunnel encryption type is 15, which represents SR-MPLS TE policy. |
Preference |
Candidate path preference. |
Binding SID |
BSID value |
Path |
Candidate path. |
Weight |
Weight of the SID list. |
SIDs |
List of SIDs. |
Table 3 Reason why the route is not selected as the optimal route
Reason |
Description |
preferred-value |
Routes with larger preferred values exist. |
local-preference |
Routes with larger local preference values exist. |
as-path |
Routes with smaller AS_PATH attribute values exist. |
origin |
There are routes whose origin has a higher priority. The route origins are IGP, EGP, and INCOMPLETE in descending order of priority. |
med |
Routes with smaller MED values exist. |
remote-route |
There are routes whose remote-route attribute has a higher priority. BGP selects the optimal route from remote routes in this order: · Route learned from an EBGP peer. · Route learned from a confederation EBGP peer. · Route learned from a confederation IBGP peer. · Route learned from an IBGP peer. |
igp-cost |
Routes with smaller IGP metrics exist. |
relydepth |
Routes with smaller recursion depth values exist. |
rfc5004 |
A route received from an EBGP peer is the current optimal route. BGP does not change the optimal route when it receives routes from other EBGP peers. |
router-id |
Routes with smaller router IDs exist. If one of the routes is advertised by a route reflector, BGP compares the ORIGINATOR_ID of the route with the router IDs of other routes. Then, BGP selects the route with the smallest ID as the optimal route. |
cluster-list |
Routes with smaller CLUSTER_LIST attribute values exist. |
peer-address |
Routes advertised by peers with lower IP addresses exist. |
received |
Earlier learned routes exist. |
# Displays advertisement information about the BGP IPv4 SR policy route [102][2][5.6.7.8]/96.
<Sysname> display bgp routing-table ipv4 sr-policy [102][2][5.6.7.8]/96 advertise-info
BGP local router ID: 2.2.2.2
Local AS number: 1
Paths: 1 best
BGP routing table information of [102][2][5.6.7.8]/96(TxPathID:0):
Advertised to peers (2 in total):
2.1.1.2
3.3.3.3
Table 4 Command output
Field |
Description |
Paths |
Number of optimal paths to reach the destination network. |
BGP routing table information of [102][2][5.6.7.8]/96(TxPathID:0) |
Advertisement information about the BGP IPv4 SR policy route [102][2][5.6.7.8]/96. TxPathID represents the advertised Add-Path ID of the route. |
Advertised to peers (2 in total) |
Indicates the peers to which the route has been advertised. The number in the parentheses indicates the total number of the peers. |
# Display statistics about the BGP IPv4 SR policy routes advertised to peer 2.1.1.2.
<Sysname> display bgp routing-table ipv4 sr-policy peer 10.2.1.2 advertised-routes statistics
Advertised routes total: 2
# Display statistics about the BGP IPv4 SR policy routes received from peer 2.1.1.2.
<Sysname> display bgp routing-table ipv4 sr-policy peer 2.1.1.2 received-routes statistics
Received routes total: 1
Table 5 Command output
Field |
Description |
Advertised routes total |
Total number of routes advertised to the specified peer. |
Received routes total |
Total number of routes received from the specified peer. |
# Display statistics about BGP IPv4 SR policy routes.
<Sysname> display bgp routing-table ipv4 sr-policy statistics
Total number of routes: 3
display segment-routing te database
Use display segment-routing te database to display SR-MPLS TE policy database information.
Syntax
display segment-routing te database [ link | node | prefix ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
link: Displays the link information reported by the IGP to the SR-MPLS TE policy database.
node: Displays the node information reported by the IGP to the SR-MPLS TE policy database.
prefix: Displays the prefix information reported by the IGP to the SR-MPLS TE policy database.
Usage guidelines
If you do not specify a parameter, this command displays all information reported by the IGP to the SR-MPLS TE policy database.
Examples
# Display the link information reported by the IGP to the SR-MPLS TE policy database.
<Sysname> display segment-routing te database link
Link-state information: Link, count: 8
Public instance, MT-ID: 0, IS-IS instance ID: 0, Link count: 4
IS-IS to DIS:
Local node: System ID 0000.0000.0001.00, IS level: 1
Remote node: System ID 0000.0000.0002.01, IS level: 1
Topology ID: 0
Link source: ProcID 1, TLV type: wide-nbr, FragID: 0x0
IGP metric: 10
SR/SRv6 link maximum SID depths:
MPLS MSD : 5
IS-IS from DIS:
Local node: System ID 0000.0000.0002.01, IS-Level: 1
Remote node: System ID 0000.0000.0002.00, IS-Level: 1
Topology ID: 0
Link source: ProcID 1, TLV type: wide-nbr, FragID: 0x0
IGP metric: 0
Table 6 Command output
Field |
Description |
Link-state information: Link |
Link information. |
count |
Number of links reported by the IGP to the SR-MPLS TE policy database. |
Public instance |
Public network instance. |
MT-ID |
Topology information: · 0—Standard topology. · 2—IPv6 unicast topology. |
Link count |
Number of links in the IS-IS instance. |
IS-IS P2P |
IS-IS P2P link. |
IS-IS to DIS |
IS-IS link to the pseudonode. |
IS-IS from DIS |
IS-IS link from the pseudonode. |
Local node |
Local node of the link. |
Remote node |
Remote node of the link. |
System ID |
System ID of the node. |
IS level |
IS-IS level of the node. |
Topology ID |
Topology ID. |
Link source |
Advertisement source of the link. |
ProcID |
IS-IS process ID. |
FragID |
Fragment ID of the packet. |
SR/SRv6 link maximum SID depths |
Maximum SID Depths (MSD) information for the SR-MPLS or SRv6 link. |
MPLS MSD |
Maximum number of SIDs that SR-MPLS can encapsulate into a packet. |
# Display the node information reported by the IGP to the SR-MPLS TE policy database.
<Sysname> display segment-routing te database node
Link-state information: Node, count: 6
Public instance, MT-ID: 0, IS-IS instance ID: 0, Node count: 3
IS-IS node: System ID 0000.0000.0001.00, IS level: 1
Node source: ProcID 1, TLV type: none, FragID: 0x0
Node topology ID: 0
Node flag: 0x1
IS-IS area: 00.0001
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: 5
End Pop MSD : 5
H.Encaps MSD: 5
End D MSD : 5
SR flags (I/V/H): 1/0/0
SRGB base: 3000 SRGB range: 1001
Table 7 Command output
Field |
Description |
Link-state information: Node |
Node information. |
count |
Number of nodes reported by the IGP to the SR-MPLS TE policy database. |
Public instance |
Public network instance. |
MT-ID |
Topology information: · 0—Standard topology. · 2—IPv6 unicast topology. |
Node count |
Number of nodes in the IS-IS instance. |
System ID |
System ID of the node. |
IS level |
IS-IS level of the node. |
Node source |
Advertisement source of the node. |
ProcID |
IS-IS process ID. |
FragID |
Fragment ID of the packet. |
Node topology ID |
Topology ID of the 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 |
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. |
H.Encaps MSD |
Maximum number of SIDs that can be included as part of the H.Encaps behavior. |
End D MSD |
Maximum number of SIDs in the SRH when performing decapsulation associated with End.Dx behaviors. |
SR flags |
Segment routing capabilities sub-TLV information: · I—MPLS IPv4 flag. If set, it indicates that the node can process SR-MPLS encapsulated IPv4 packets on all interfaces. · V—MPLS IPv6 flag. If set, it indicates that the node can process SR-MPLS encapsulated IPv6 packets on all interfaces. (This flag is not supported in the current software version.) · H—SRv6 flag. If set, it indicates that the node can process packets encapsulated in SRv6 extended SRH headers on all interfaces. (This flag is not supported in the current software version.) |
SRGB base |
SRGB base value, which is the minimum label value in the SRGB. |
SRGB range |
Number of labels in the SRGB. |
# Display the prefix information reported by the IGP to the SR-MPLS TE policy database.
<Sysname> display segment-routing te database prefix
Link-state information: Prefix, count: 7
Public instance, MT-ID: 0, IS-IS instance ID: 0, Prefix count: 3
IS-IS prefix:
Local node: System ID 0000.0000.0001.00, IS level: 1
Prefix: 1.1.1.1/32, Topology ID: 0
Prefix source: ProcID 1, TLV type: ip-extended, FragID: 0x0
Prefix metric: 0
Prefix-SID: 333 Algorithm: 0
Prefix-SID flags (R/N/P/E/V/L): 0/1/0/0/0/0
IS-IS prefix:
Local node: System ID 0000.0000.0001.00, IS level: 1
Prefix: 10.0.0.0/24, Topology ID: 0
Prefix source: ProcID 1, TLV type: ip-extended, FragID: 0x0
Prefix metric: 10
Table 8 Command output
Field |
Description |
Link-state information: Prefix |
Prefix information. |
count |
Number of prefixes reported by the IGP to the SR-MPLS TE policy database. |
Public instance |
Public network instance. |
MT-ID |
Topology information: · 0—Standard topology. · 2—IPv6 unicast topology. |
Prefix count |
Number of prefixes in the IS-IS instance. |
Local node |
Local node information of the link. |
System ID |
System ID of the node. |
IS level |
IS-IS level of the node. |
Prefix |
Prefix address. |
Topology ID |
Topology ID. |
Prefix source |
Advertisement source of the prefix. |
FragID |
Fragment ID of the packet. |
Algorithm |
Algorithm associated with the prefix. Only the SPF algorithm is supported. |
Prefix-SID flags (R/N/P/E/V/L) |
Segment routing capabilities sub-TLV information: · R—Re-advertisement flag, set when the prefix SID has been leaked from one level to another or routes have been redistributed. · N—Node-SID flag, set when the prefix SID identifies the advertising node, that is, the prefix is a host prefix advertising a globally reachable address typically associated with a loopback address. · P—No-PHP flag, set when the penultimate hop is not allowed to pop the prefix SID. · E—Explicit null label flag, set when the upstream node must reset the prefix SID to an explicit null label. · V—Value/Index flag, set when the prefix SID is an absolute value. · L—Local/Global flag, set when the prefix SID is a locally significant prefix SID. |
display segment-routing te forwarding
Use display segment-routing te forwarding to display SR TE forwarding information.
Syntax
display segment-routing te forwarding [ policy { name policy-name | { color color-value | end-point ipv4 ip-address } * } ] [ verbose ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
policy: Displays SR TE forwarding information of the specified SR-MPLS TE policy. If you do not specify an SR-MPLS TE policy, this command displays SR TE forwarding information of all SR policies.
name policy-name: Specifies the name of an SR-MPLS TE policy, a string of 1 to 59 characters.
color color-value: Specifies the color of an SR-MPLS TE policy, in the range of 0 to 4294967295.
end-point ipv4 ip-address: Specifies the endpoint IPv4 address of an SR-MPLS TE policy.
verbose: Displays detailed SR TE forwarding information. If you do not specify this keyword, the command displays brief SR TE forwarding information.
Usage guidelines
To use this command to display SR TE traffic forwarding statistics, make sure SR TE traffic forwarding statistics is enabled.
Examples
# Display brief forwarding information of all SR policies.
<Sysname> display segment-routing te forwarding
Total forwarding entries: 1
Policy name/ID: p1/0
Binding SID: 15200
Policy NID: 1000
Main path:
Seglist ID: 1
Seglist NID: 2001
Weight: 50
Outgoing NID: 3012
OutLabels: 3
Interface: XGE3/1/1
NextHop: 1.2.0.2
Outgoing NID: 3210
OutLabels: 3
Interface: XGE3/1/2
NextHop: 1.2.1.2
Backup path:
Seglist ID: 1
Seglist NID: 2101
Weight: 100
Outgoing NID: 3560
OutLabels: 3
Interface: XGE3/1/1
NextHop: 1.2.0.2
Outgoing NID: 3958
OutLabels: 3
Interface: XGE3/1/2
NextHop: 1.2.1.2
# Display detailed forwarding information of all SR policies.
<Sysname> display segment-routing te forwarding verbose
Total forwarding entries: 1
Policy name/ID: p1/6
Binding SID: 1145
Policy NID: 20971527
Outbound statistics:
Total octets: 103079124844
Total packets: 937082894
Erroneous packets: 0
Dropped packets: 0
Output rate in the last 300 seconds:
0 bits/sec, 0 pkts/sec
Output rate in the last statistical period (5 sec):
0 bits/sec, 0 pkts/sec
Main path:
SegList ID: 7
SegList NID: 24117260
Weight: 1
Outbound statistics:
Total octets: 51539583322
Total packets: 468541637
Erroneous packets: 0
Dropped packets: 0
Output rate in the last 300 seconds:
0 bits/sec, 0 pkts/sec
Output rate in the last statistical period (5 sec):
0 bits/sec, 0 pkts/sec
Outgoing NID : 23068673
OutLabels: 16122
Interface: XGE3/1/1
NextHop: 121.11.1.1
Path Id: 0
Label stack: {16122}
SegList ID: 8
Seglist NID:24117261
Weight:1
Outbound statistics:
Total octets: 51539541522
Total packets: 468541257
Erroneous packets: 0
Dropped packets: 0
Output rate in last 300 seconds:
0 bits/sec, 0 pkts/sec
Output rate in the last statistical period (5 sec):
0 bits/sec, 0 pkts/sec
Outgoing NID : 23068674
OutLabels: 16122
Interface: XGE3/1/2
NextHop: 121.11.1.1
Path Id: 1
Label stack: {16122}
Table 9 Command output
Field |
Description |
Policy name/ID |
Name/ID of the SR-MPLS TE policy. |
Binding SID |
Label value of the ingress node. |
Policy NID |
NHLFE entry index of the SR-MPLS TE policy. |
Total octets |
Total number of forwarded bytes. |
Total packets |
Total number of forwarded packets. |
Erroneous packets |
Number of erroneous packets. |
Dropped packets |
Number of dropped packets. |
Outbound statistics |
Outbound traffic statistics. |
Output service-class |
Statistics on outbound traffic of a service class. A value of 255 indicates no service class is configured for the SR-MPLS TE policy, and the SR-MPLS TE policy has the lowest forwarding priority. |
Main path |
Main traffic forwarding path. |
Backup path |
Backup traffic forwarding path. |
Seglist ID |
SID list ID. |
Seglist NID |
NHLFE entry index of the SID list. |
Delay timer type |
Type of the delay timer: · LSP—Timer that delays to refresh LSPs. · SBFD—Timer that delays to clear the SBFD DOWN bit. |
Delay time |
Up delay time in milliseconds. |
Remaining time |
Remaining delay time for the up state. |
Outgoing NID |
NHLFE ID for the first address in the SID list. If ECMP-backup is carried, this field represents the NHLFE ID for the ECMP backup path. |
OutLabel |
Outgoing label value. |
Interface |
Brief name of the outgoing interface. |
Nexthop |
Nexthop IP address. |
PathID |
Path ID assigned to the SID list by the SR-MPLS TE policy. |
Weight |
Weight of the path. |
Label stack |
Stack of labels from top to bottom. |
display segment-routing te policy
Use display segment-routing te policy to display SR-MPLS TE policy information.
Syntax
display segment-routing te policy [ name policy-name | down | up | { color color-value | end-point ipv4 ip-address } * ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
name policy-name: Specifies an SR-MPLS TE policy by its name, a case-sensitive string of 1 to 59 characters.
down: Specifies the SR policies in down state.
up: Specifies the SR policies in up state.
color color-value: Specifies the color of an SR-MPLS TE policy, in the range of 0 to 4294967295.
end-point ipv4 ip-address: Specifies the endpoint IPv4 address of an SR-MPLS TE policy.
Usage guidelines
If you do not specify any parameters, this command displays information about all SR policies.
Examples
# Display information about all SR-MPLS TE policies.
<Sysname> display segment-routing te policy
Name/ID: abc/0
Color: 10
Endpoint: 4.4.4.4
Name from BGP: abc
BSID:
Mode: Explicit Type: Type_1 Request state: Succeeded
Current BSID: 15000 Explicit BSID: 15000 Dynamic BSID: -
Reference counts: 3
Flags: A/BS/NC
Status: Up
AdminStatus: Up
Up time: 2019-10-25 11:16:15
Down time: 2019-10-25 11:16:00
Hot-standby: Not configured
Statistics: Enabled
Statistics by service class: Enabled
SBFD: Not configured
BFD trigger path-down: Disabled
PolicyNid: 6201
Service-class: -
Candidate paths state: Configured
Candidate paths statistics:
CLI paths: 1 BGP paths: 0 PCEP paths: 0
Candidate paths:
Preference : 10
CPathName:
ProtoOrigin: CLI Discriminator: 10
Instance ID: 0 Node address: 0.0.0.0
Originator: 0, 0.0.0.0
Optimal: Y Flags: V/A
Explict SID list:
ID: 1 Name: abc
Weight: 1 Nid: 5
State: Up SBFD state: -
Table 10 Command output
Field |
Description |
Name/ID |
SR-MPLS TE policy name/ID. |
Color |
Color attribute of the SR-MPLS TE policy. A hyphen (-) means that the color attribute is not configured. |
Endpoint |
Endpoint IP address of the SR-MPLS TE policy. If the endpoint is not configured, this field displays None. |
Name from BGP |
SR-MPLS TE policy name obtained through BGP. The SR-MPLS TE policy name is not displayed if it is not obtained. |
BSID |
SID value of the ingress node. |
Mode |
BSID configuration mode: · Explicit—Manually configured. · Dynamic—Dynamically requested. · None—Not configured. |
Type |
BSID type: · None—Not configured. · Type_1—MPLS label. |
Request state |
BSID request state: · Conflicted. · Failed. · Succeeded. If the BSID is not generated, this field displays a hyphen (-). |
Explicit BSID |
Manually configured BSID. |
Dynamic BSID |
Dynamically requested BSID. If the BSID is not dynamically requested, this field displays a hyphen (-). |
Reference counts |
Number of times that the SR-MPLS TE policy has been referenced. |
Flags |
SR-MPLS TE policy flags: · A—Active SR-MPLS TE policy. · C—Optimal SR-MPLS TE policy. · N—In optimal SR-MPLS TE policy selection progress. · BA—Requesting BSID. · BS—Optimal BSID. · D—Deleted SR-MPLS TE policy. · CF—Conflicted with an existing BSID. · NC—Name from configuaration, which indicates a manually configured SR-MPLS TE policy. · NB—Name from BGP, which indicates an SR-MPLS TE policy obtained from a BGP route. |
Status |
SR-MPLS TE policy status: · Up—The policy is active. · Down—The policy is inactive. This down state is caused by reasons other than the BFD/SBFD session collaboration. · Down (BFD down)—This down state is set by BFD/SBFD when it detects that the forwarding paths corresponding to all SID lists in the candidate paths of the SR-MPLS TE policy are unreachable (the first hop on the forwarding paths corresponding to all SID lists is reachable, but subsequent hops on the forwarding paths are unreachable). |
AdminStatus |
Administrative status of the SR-MPLS TE policy: · Down—The policy is shut down by the shutdown command. · Up—The policy is not shut down by the shutdown command. |
Up time |
Time when the SR-MPLS TE policy came up. |
Down time |
Time when the SR-MPLS TE policy went down. |
Hot-standby |
Status of the hot standby feature: Enabled or Disabled. |
Statistics |
Status of the SR-MPLS TE policy traffic forwarding statistics: Enabled or Disabled. |
Statistics by service class |
Status of the service class based traffic statistics for the SR-MPLS TE policy: Enabled or Disabled. |
SBFD |
Status of the SBFD feature: Enabled or Disabled. |
Remote |
Remote discriminator of the e SBFD session. |
Template name |
Name of the SBFD template. |
Backup template name |
Name of the SBFD template for the backup SID list. |
BFD trigger path-down |
Whether to enable BFD session down events to trigger SR-MPLS TE policy path reselection: · Disabled. · Enabled. |
PolicyNid |
NHLFE entry index of the SR-MPLS TE policy. |
Service-class |
Service class value of the SR-MPLS TE policy. If the default service class is used, this field displays a hyphen (-). |
Candidate paths status |
Whether candidate paths are configured: · Configured. · Not configured. |
Candidate paths statistics |
Number of candidate paths. |
CLI paths |
Number of manually configured candidate paths. |
BGP paths |
Number of candidate paths obtained through BGP IPv4 SR policy routes. |
PCEP paths |
This field is not supported in the current software version. Number of candidate paths obtained through Path Computation Element Protocol (PCEP). |
Candidate paths |
SR-MPLS TE policy candidate path information. |
Preference |
SR-MPLS TE policy candidate path preference. |
CPathName |
Name of the candidate path obtained through BGP routes. This field is empty if the candidate path name is not obtained. |
ProtoOrigin |
Protocol used to obtain the SR-MPLS TE policy: · PCEP—The SR-MPLS TE policy was obtained through PCEP. (This value is not supported in the current software version.) · BGP—The SR-MPLS TE policy was obtained through BGP. · CLI—The SR-MPLS TE policy was locally configured. · Unknown—The source of the SR-MPLS TE policy is unknown. |
Instance ID |
BGP instance ID. A value of 0 indicates that the device does not obtain SR-MPLS TE policy information from BGP peers. |
Node address |
BGP node address. For a manually configured SR-MPLS TE policy, the node address is 0.0.0.0. For an SR-MPLS TE policy obtained from a BGP peer, the node address is the Router ID of the BGP peer. |
Originator: ASN, Peer-address |
Information of the SR-MPLS TE policy obtained through BGP, where: · ASN—AS number. A value of 0 indicates that the device does not obtain SR-MPLS TE policy information from BGP peers. · Peer-address—BGP node address. For a manually configured SR-MPLS TE policy, the peer address is 0.0.0.0. For an SR-MPLS TE policy obtained from a BGP peer, the peer address is the address of the BGP peer. |
Optimal |
Whether the path is the optimal path: · Y—Yes. · N—No. |
Flags |
Flags of the SR-MPLS TE policy candidate path: · V—Valid candidate path. · A—Active candidate path. · B—Backup candidate path. · S—Aging candidate path. · BN—Name from BGP, which indicates a candidate path obtained from the BGP route. · PN—Name from PCEP, which indicates a candidate path obtained from the PCE. · None—No candidate path. |
Explicit SID list |
Explicit SID list in the candidate path of the SR-MPLS TE policy. |
ID |
SID list index. |
Name |
SID list name. |
Weight |
Weight of the SID list in the candidate path. |
Nid |
NHLFE entry index of the SID list. |
State |
SID list state: · Up. · Down—This down state is caused by reasons other than the BFD/SBFD session collaboration. · Down (BFD down)—This state is set by BFD/SBFD when it detects that the first hop on the forwarding path indicated by the SID list is reachable but subsequent hops on the forwarding path is unreachable. |
State(type) |
The type attribute indicates the BFD session type, which is SBFD. SBFD state of the SID list: · Up—The SBFD session is up. · Down—The SBFD session is down. · Path inactive—No SID list is available in the candidate path. · Unknown—The SBFD detection result is unknown. If SBFD is not configured, this field displays a hyphen (-). |
SID list flags |
Flags for the SID list of the SR-MPLS TE policy: · O—The number of SIDs in the SID list exceeds the maximum label stack depth allowed on the device. · None—No flags. |
display segment-routing te policy last-down-reason
Use display segment-routing te policy last-down-reason to display information about the most recent down event for SR-MPLS TE policies.
Syntax
display segment-routing te policy last-down-reason [ binding-sid bsid | color color-value end-point ipv4 ipv4-address | policy-name policy-name ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
binding-sid bsid: Specifies an SR-MPLS TE policy by its BSID.
color color-value end-point ipv4 ipv4-address: Specifies an SR-MPLS TE policy by its color attribute value and endpoint IPv4 address. The value range for the color attribute value is 0 to 4294967295.
policy-name policy-name: Specifies an SR-MPLS TE policy by its name, a case-sensitive string of 1 to 59 characters.
Usage guidelines
If you do not specify any parameters, this command displays information about the most recent down event for all SR-MPLS TE policies.
Examples
# Display information about the most recent down event for all SR-MPLS TE policies.
<Sysname> display segment-routing te policy last-down-reason policy-name
Name/ID: p1/1
Color: 10
Endpoint: 4.4.4.4
BSID: 1023
Up time: 2021-12-23 15:42:14
Down time: 2021-12-23 15:41:15
Down reason: Candidate path invalid segment list
Candidate paths:
Preference : 10
CPathName:
Explicit SID list:
ID: 1 Name: s1
Up time: 2021-12-23 15:42:14
Down time: 2021-12-23 15:41:15
Down reason: No SID Out
Table 11 Command output
Field |
Description |
Name/ID |
Name/ID of an SR-MPLS TE policy. |
Color |
Color attribute value of the SR-MPLS TE policy. |
Endpoint |
Endpoint address of the SR-MPLS TE policy. If the endpoint address is not configured, this field displays None. |
BSID |
SID value of the ingress node. |
Up time |
Time when the SR-MPLS TE policy came up. |
Down time |
Time when the SR-MPLS TE policy went down. |
Down reason |
Reason for the down event of the SR-MPLS TE policy: · Admin down—The SR-MPLS TE policy has been shut down by the shutdown command. · No Endpoint. · No candidate path. · No valid candidate path. · Candidate path invalid segment list—All SID lists in the candidate path are down. · Policy unconfigured—The SR-MPLS TE policy is being deleted. · Unknown error. |
Candidate paths |
Candidate path information of the SR-MPLS TE policy. |
Preference |
Preference of the candidate path. |
CPathName |
Name of the candidate path. If no candidate path name is obtained from BGP, this field is empty. |
Explicit SID List |
SID list in the candidate path of the SR-MPLS TE policy. |
ID |
SID list index. |
Name |
SID list name. |
Up time |
Time when the SID list came up. |
Down time |
Time when the SID list went down. |
Down reason |
Reason for the down event of the SID list: · No SID list—The SID list does not exist. · No SID Out—The first SID in the SID list does not have an outgoing interface. · No output interface for the first SID—The first SID in the SID list does not have an outgoing interface. · Unknown error. · BFD Detect Down—BFD detected that the first hop on the forwarding path indicated by the SID list of the SR-MPLS TE policy is reachable but the next hops on the forwarding path are not reachable. |
display segment-routing te policy statistics
Use display segment-routing te policy statistics to display SR-MPLS TE policy statistics.
Syntax
display segment-routing te policy statistics
Views
Any view
Predefined user roles
network-admin
network-operator
Examples
# Display SR-MPLS TE policy statistics.
<Sysname> display segment-routing te policy statistics
TE Policy Database Statistics
Total policies: 1 (0 up 1 down)
Configured: 1 (0 up 1 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: 0
Configured: 0
From BGP: 0 (Added 0 deleted 0)
From ODN: 0 (Added 0 deleted 0)
From PCE: 0 (Added 0 deleted 0)
Total SID lists: 0 (0 up 0 down)
Configured: 0 (0 up 0 down)
From BGP: 0 (0 up 0 down)
From PCE: 0 (0 up 0 down)
Table 12 Command output
Field |
Description |
Total policies |
Total number of SR policies: · up—Number of SR policies in up state. · down—Number of SR policies in down or Down (BFD down) state. |
Configured |
Number of manually configured SR-MPLS TE policies. · up—Number of SR-MPLS TE policies in up state. · down—Number of SR-MPLS TE policies in down or Down (BFD down) state. |
From BGP |
Number of SR-MPLS TE policies learned from BGP. · Added—Number of BGP-added SR-MPLS TE policies. · deleted—Number of BGP-deleted SR-MPLS TE policies. · up—Number of SR-MPLS TE policies in up state. · down—Number of SR-MPLS TE policies in down or Down (BFD down) state. |
From ODN |
Number of SR-MPLS TE policies learned through ODN. · Added—Number of ODN-added SR-MPLS TE policies. · deleted—Number of ODN-deleted SR-MPLS TE policies. · up—Number of SR-MPLS TE policies in up state. · down—Number of SR-MPLS TE policies in down or Down (BFD down) state. |
From PCE |
Number of SR-MPLS TE policies generated through PCE. · Added—Number of PCE-added SR-MPLS TE policies. · deleted—Number of PCE-deleted SR-MPLS TE policies. · up—Number of SR-MPLS TE policies in up state. · down—Number of SR-MPLS TE policies in down or Down (BFD down) state. |
Total candidate paths |
Total number of SR-MPLS TE policy candidate paths. |
Total SID lists |
Total number of SID lists. |
display segment-routing te policy-group
Use display segment-routing te policy-group to display SR-MPLS TE policy group information.
Syntax
display segment-routing te policy-group [ group-id ] [ verbose ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
group-id: Specifies an SR-MPLS TE policy group by its ID in the range of 1 to 4294967295. If you do not specify this argument, the command displays information about all SR-MPLS TE policy groups.
verbose: Displays detailed SR-MPLS TE policy group information. If you do not specify this keyword, the command displays brief SR-MPLS TE policy group information.
Examples
# Display brief information about all SR-MPLS TE policy groups.
<Sysname> display segment-routing te policy-group
Total number of policy groups: 3
GroupID GroupState Endpoint UPMappings TotalMappings
1 Up 1.1.1.1 0 0
2 Up 2.2.2.2 0 0
3 Up 3.3.3.3 0 0
# Display detailed information about all SR-MPLS TE policy groups.
<Sysname> display segment-routing te policy-group verbose
Total number of policy groups: 3
GroupID: 1 GroupState: 0
GroupNID: 24117249 Referenced: 1
Flags: F
StateChangeTime: 2021-03-18 09:57:43
Endpoint: 1.1.1.1 Up/Total mappings: 0/0
Color Type DSCP
1 IPv4 3, 10~20, default
2 IPv4 30, 40, 60
1 IPv6 3, 10~20, default
2 IPv6 30, 40, 60
Table 13 Command output
Field |
Description |
Total number of policy groups |
Total number of SR-MPLS TE policy groups. |
GroupID |
SR-MPLS TE policy group ID. |
GroupState |
SR-MPLS TE policy group state: Down or Up. |
GroupNID |
NHLFE entry index of the SR-MPLS TE policy group. |
Referenced |
Number of times the SR-MPLS TE policy group has been used. |
Flags |
SR-MPLS TE policy group flags: · A—Assign the NHLFE entry index of the SR-MPLS TE policy group. · F—Issue the NHLFE entry of the SR-MPLS TE policy group. · W—Waiting for assigning the NHLFE entry index of the SR-MPLS TE policy group. · D—Delete the SR-MPLS TE policy group. · None—The SR-MPLS TE policy group is in initial state. |
StateChangeTime |
Time when the SR-MPLS TE policy group state changed. |
Endpoint |
Destination node IP address of the SR-MPLS TE policy group. None indicates not configured. |
UPMappings |
Number of valid color-to-DSCP mappings in the SR-MPLS TE policy group. |
TotalMappings |
Total number of color-to-DSCP mappings in the SR-MPLS TE policy group. |
Up/Total mappings |
Valid color-to-DSCP mappings/total number of color-to-DSCP mappings in the SR-MPLS TE policy group. |
Color |
Color value |
Type |
Packet type: IPv4 or IPv6. |
DSCP |
DSCP value. |
display segment-routing te sbfd
Use display segment-routing te sbfd to display SBFD information for SR-MPLS TE policies.
Syntax
display segment-routing te sbfd [ down | policy { { color color-value | end-point ipv4 ipv4-address } * | name policy-name } | up ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
down: Displays SBFD information for SR-MPLS TE policies in down state.
up: Displays SBFD information for SR-MPLS TE policies in up state.
policy: Displays SBFD information for the specified SR-MPLS TE policy.
color color-value: Specifies an SR-MPLS TE policy by its color attribute value in the range of 0 to 4294967295.
end-point ipv4 ipv4-address: Specifies an SR-MPLS TE policy by its endpoint IPv4 address.
name policy-name: Specifies an SR-MPLS TE policy by its name, a case-sensitive string of 1 to 59 characters.
Usage guidelines
If you do not specify any parameters, this command displays SBFD information for all SR-MPLS TE policies.
Examples
# Display SBFD information for all SR-MPLS TE policies.
<Sysname> display segment-routing te sbfd
Color: 10
Endpoint: 4.4.4.4
BSID: 15000
Policy name: p1
State: Down
NID: 24117249
Remote Discr: 67372036
State: Down
Timer: 30
Flush add time: 2022-12-22 17:01:48
Table 14 Command output
Field |
Description |
Color |
Color attribute value of the SR-MPLS TE policy. |
Endpoint |
Endpoint IPv4 address of the SR-MPLS TE policy. |
BSID |
SID value of the ingress node. |
Policy name |
Name of the SR-MPLS TE policy. |
State |
SBFD session state: · Up · Down |
NID |
Forwarding entry index for an SID list. |
Remote Discr |
Remote discriminator. This field displays a hyphen (-) if no remote discriminator is specified for the SBFD session. |
Timer |
SBFD session timer, in seconds. |
Flush add time |
Last time when the SR-MPLS TE policy delivers path information to SBFD. SBFD establishes an SBFD session according to the path information. If no SBFD session is established, this field displays a hyphen (-). |
display segment-routing te segment-list
Use display segment-routing te segment-list to display SR-TE SID list information.
Syntax
display segment-routing te segment-list [ name segment-list-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 SR-TE SID lists.
To view SID list ID information, execute the display segment-routing te policy command.
Examples
# Display information about all SR-TE SID lists.
<Sysname> display segment-routing te segment-list
Total SID lists: 1
Name/ID: abc/1
Origin: CLI
Status: Down
Nodes : 1
Flags : None
Index: 10 Label: 17401
Type : Type_1 Flags: None
Index: 20 Label: 18101
Type : Type_1 Flags: None
Table 15 Command output
Field |
Description |
Total SID lists |
Number of SID lists. |
Name/ID |
SID list name/ID. |
Origin |
Origin of the SID list. Options include: · CLI—Locally configured in the CLI. · BGP—Issued by BGP. · PCE—Issued by a PCE. (This option is not supported in the current software version.) If the SID list does not have a valid origin, this field displays a hyphen (-). |
Status |
SID list status, Down or Up. |
Nodes |
Number of nodes in the SID list. |
Flags |
SID list flags: · D—The SID list is being deleted. · None—The SID list is in normal state. |
Index |
Node index. |
Label |
Label value of the node. |
Type |
Label type of the node: · None—No label is configured. · Type_1—MPLS label. |
Flags |
Node flags, which are not defined and displayed as None. |
Related commands
display segment-routing te policy
distribute bgp-ls
Use distribute bgp-ls to enable the device to distribute SR-MPLS TE policy candidate path information to BGP-LS.
Use undo distribute bgp-ls to restore the default.
Syntax
distribute bgp-ls
undo distribute bgp-ls
Default
The device does not distribute SR-MPLS TE policy candidate path information to BGP-LS.
Views
SR TE view
Predefined user roles
network-admin
Usage guidelines
After this command is executed, the device distributes SR-MPLS TE policy candidate path information to BGP-LS. BGP-LS advertises the SR-MPLS TE policy candidate path information to meet application requirements.
Examples
# Enable the device to distribute SR-MPLS TE policy candidate path information to BGP-LS.
<Sysname> system-view
[Sysname] segment-routing
[Sysname-segment-routing] traffic-engineering
[Sysname-sr-te] distribute bgp-ls
end-point
Use end-point to configure the endpoint IP address for the SR-MPLS TE policy group.
Use undo end-point to delete the endpoint IP address of the SR-MPLS TE policy group.
Syntax
end-point ipv4 ipv4-address
undo end-point ipv4
Default
No endpoint IP address is configured for the SR-MPLS TE policy group.
Views
SR-MPLS TE policy group view
Predefined user roles
network-admin
Parameters
ipv4 ipv4-address: Specifies the endpoint IP address for the SR-MPLS TE policy group.
Usage guidelines
The SR-MPLS TE policies added to the SR-MPLS TE policy group must use the same endpoint IP address as the SR-MPLS TE policy group.
If you execute this command multiple times, the most recent configuration takes effect.
Examples
# Configure the endpoint IP address as 10.1.1.1 for SR-MPLS TE policy group 1.
<Sysname> system-view
[Sysname] segment-grouting
[Sysname-segment-grouting] traffic-engineering
[Sysname-sr-te] policy-group 1
[Sysname-sr-te-policy-group-1] end-point ipv4 10.1.1.1
explicit segment-list
Use explicit segment-list to specify an SID list for a candidate path.
Use undo explicit segment-list to delete an SID list of a candidate path.
Syntax
explicit segment-list segment-list-name [ weight weight-value ]
undo explicit segment-list segment-list-name [ weight ]
Default
No SID lists are specified for an SR-MPLS TE policy candidate path.
Views
Candidate path preference view
Predefined user roles
network-admin
Parameters
segment-list-name: Specifies an SID list name, a string of 1 to 128 characters.
weight weight-value: Specifies a weight for the SID list, in the range of 1 to 4294967295. The default weight is 1.
Usage guidelines
An SR-MPLS TE policy uses the SID list specified for the highest-preference candidate path as a traffic forwarding subpath.
An SR-MPLS TE policy candidate path can have multiple SID lists. All the SID lists can be used to forward traffic for load sharing based on their weights. Assume SID lists a, b, and c are assigned weights x, y, z, respectively. The load of SID list a is x/(x+y+z) of the total traffic.
If you assign weight values for the same SID list multiple times, the most recent configuration takes effect.
Examples
# Configure SID list abc for the SR-MPLS TE policy candidate path with preference 20, and the set the SID list weight to 20.
<Sysname> system-view
[Sysname] segment-routing
[Sysname-segment-routing] traffic-engineering
[Sysname-sr-te] policy a1
[Sysname-sr-te-policy-a1] candidate-paths
[Sysname-sr-te-policy-a1-path] preference 20
[Sysname-sr-te-policy-a1-path-pref-20] explicit segment-list abc weight 20
Related commands
segment-list
forwarding statistics
Use forwarding statistics to configure traffic forwarding statistics for an SR-MPLS TE policy.
Use undo forwarding statistics to restore the default.
Syntax
forwarding statistics { disable | [ service-class ] enable }
undo forwarding statistics
Default
An SR-MPLS TE policy uses the traffic forwarding statistics configuration in SR TE view.
Views
SR-MPLS TE policy view
Predefined user roles
network-admin
Parameters
disable: Disables the SR-MPLS TE policy forwarding statistics.
enable: Enables the SR-MPLS TE policy forwarding statistics.
service-class: Enables the SR-MPLS TE policy forwarding statistics by service class. This feature collects statistics on the total traffic as well as the traffic of each service class that are forwarded by the SR-MPLS TE policy tunnel. If you do not specify this keyword, the device only collects statistics on the total traffic forwarded by the SR-MPLS TE policy tunnel.
Usage guidelines
You can configure traffic forwarding statistics for all SR-MPLS TE policies globally in SR TE view or for a specific SR-MPLS TE policy in SR-MPLS TE policy view. The policy-specific configuration takes precedence over the global configuration. An SR-MPLS TE policy uses the global configuration only when it has no policy-specific configuration.
If you execute this command multiple times, the most recent configuration takes effect.
Examples
# Enable traffic forwarding statistics for SR-MPLS TE policy abc.
<Sysname> system-view
[Sysname] segment-routing
[Sysname-segment-routing] traffic-engineering
[Sysname-sr-te] policy abc
[Sysname-sr-te-policy-abc] forwarding statistics enable
Related commands
display segment-routing te forwarding verbose
forwarding statistics enable
forwarding statistics interval
reset segment-routing te forwarding statistics
forwarding statistics enable
Use forwarding statistics enable to enable traffic forwarding statistics for all SR-MPLS TE policies.
Use undo forwarding statistics enable to disable traffic forwarding statistics for all SR-MPLS TE policies.
Syntax
forwarding statistics [ service-class ] enable
undo forwarding statistics enable
Default
Traffic forwarding statistics is disabled for all SR-MPLS TE policies.
Views
SR TE view
Predefined user roles
network-admin
Parameters
service-class: Enables the SR-MPLS TE policy forwarding statistics by service class. This feature collects statistics on the total traffic as well as the traffic of each service class that are forwarded by SR-MPLS TE policies. If you do not specify this keyword, the device only collects statistics on the total traffic forwarded by SR-MPLS TE policies.
Usage guidelines
You can configure traffic forwarding statistics for all SR-MPLS TE policies globally in SR TE view or for a specific SR-MPLS TE policy in SR-MPLS TE policy view. The policy-specific configuration takes precedence over the global configuration. An SR-MPLS TE policy uses the global configuration only when it has no policy-specific configuration.
If you execute this command multiple times, the most recent configuration takes effect.
Examples
# Enable traffic forwarding statistics for all SR-MPLS TE policies.
<Sysname> system-view
[Sysname] segment-routing
[Sysname-segment-routing] traffic-engineering
[Sysname-sr-te] forwarding statistics enable
Related commands
display segment-routing te forwarding verbose
forwarding statistics
forwarding statistics interval
reset segment-routing te forwarding statistics
forwarding statistics interval
Use forwarding statistics interval to set the traffic forwarding statistics interval for all SR-MPLS TE policies.
Use undo forwarding statistics interval to restore the default.
Syntax
forwarding statistics interval interval
undo forwarding statistics interval
Default
The SR TE policy traffic forwarding statistics interval is 30 seconds.
Views
SR TE view
Predefined user roles
network-admin
Parameters
Interval: Sets the SR TE policy traffic forwarding statistics interval, in the range of 5 to 65535 seconds.
Examples
# Set the SR TE policy traffic forwarding statistics interval to 90 seconds.
<Sysname> system-view
[Sysname] segment-routing
[Sysname-segment-routing] traffic-engineering
[Sysname-sr-te] forwarding statistics interval 90
Related commands
display segment-routing te forwarding
forwarding statistics
forwarding statistics enable
reset segment-routing te forwarding statistics
import-route sr-policy
Use import-route sr-policy to enable BGP to redistribute routes from the SR-MPLS TE policy.
Use undo import-route sr-policy to restore the default.
import-route sr-policy
undo import-route sr-policy
Default
BGP does not redistribute BGP IPv4 SR policy routes.
Views
BGP IPv4 SR policy address family view
Predefined user roles
network-admin
Usage guidelines
After you execute this command, the system will redistribute the local BGP IPv4 SR policy routes to the BGP routing table and advertise the routes to IBGP peers. Then, the peers can forward traffic based on the SR-MPLS TE policy.
Examples
# In BGP IPv4 SR policy address family view, enable BGP to redistribute routes from the SR-MPLS TE policy.
<Sysname> system-view
[Sysname] bgp 100
[Sysname-bgp-default] address-family ipv4 sr-policy
[Sysname-bgp-default-srpolicy-ipv4] import-route sr-policy
index
Use index to add a node to a SID list.
Use undo index to delete a node from a SID list.
Syntax
index index-number mpls label label-value
undo index index-number
Default
No nodes exist in a SID list.
Views
SID list view
Predefined user roles
network-admin
Parameters
index-number: Specifies the node index, in the range of 1 to 65535.
mpls label label-value: Specifies the MPLS label value of the node, in the range of 0, 3, and 16 to 1048575.
Examples
# Add a node to SID list abc, and set the node index to 1 and MPLS label to 1000.
<Sysname> system-view
[Sysname] segment-routing
[Sysname-segment-routing] traffic-engineering
[Sysname-sr-te] segment-list abc
[Sysname-sr-te-sl-abc] index 1 mpls label 1000
policy
Use policy to create an SR-MPLS TE policy and enter its view, or enter the view of an existing SR-MPLS TE policy.
Use undo policy to delete an SR-MPLS TE policy and all the configuration in the SR-MPLS TE policy.
Syntax
policy policy-name
undo policy policy-name
Default
No SR-MPLS TE policies exist.
Views
SR TE view
Predefined user roles
network-admin
Parameters
policy-name: Specifies an SR-MPLS TE policy name, a case-sensitive string of 1 to 59 characters.
Examples
# Create an SR-MPLS TE policy named srpolicy and enter its view.
<Sysname> system-view
[Sysname] segment-routing
[Sysname-segment-routing] traffic-engineering
[Sysname-sr-te] policy srpolicy
[Sysname-sr-te-policy-srpolicy]
policy-group
Use policy-group to create an SR-MPLS TE policy group and enter its view, or enter the view of an existing SR-MPLS TE policy group.
Use undo policy-group to delete an SR-MPLS TE policy group and all the configuration in the SR-MPLS TE policy group.
Syntax
policy-group group-id
undo policy-group group-id
Default
No SR-MPLS TE policy groups exist.
Views
SR TE view
Predefined user roles
network-admin
Parameters
group-name: Specifies an SR-MPLS TE policy group by its ID in the range of 1 to 4294967295.
Usage guidelines
You can add SR-MPLS TE policies to an SR-MPLS TE policy group to implement SR-MPLS TE policy based forwarding according to DSCP values of packets.
Examples
# Create SR-MPLS TE policy group 1 and enter its view.
<Sysname> system-view
[Sysname] segment-grouting
[Sysname-segment-grouting] traffic-engineering
[Sysname-sr-te] policy-group 1
[Sysname-sr-te-policy-group-1]
preference
Use preference to set the preference for a candidate path and enter candidate path preference view, or enter an existing candidate path preference view.
Use undo preference to delete a candidate path preference and all the configuration in the candidate path preference view.
Syntax
preference preference-value
undo preference preference-value
Default
No candidate path preferences are set.
Views
Candidate path view
Predefined user roles
network-admin
Parameters
preference-value: Specifies a candidate path preference in the range of 1 to 65535. A bigger value represents a higher preference.
Usage guidelines
A preference represents a candidate path of an SR-MPLS TE policy.
Examples
# Set the preference of an SR-MPLS TE policy candidate path to 20, and enter candidate path preference view.
<Sysname> system-view
[Sysname] segment-routing
[Sysname-segment-routing] traffic-engineering
[Sysname-sr-te] policy a1
[Sysname-sr-te-policy-a1] candidate-paths
[Sysname-sr-te-policy-a1-path] preference 20
[Sysname-sr-te-policy-a1-path-pref-20]
reset segment-routing te forwarding statistics
Use reset segment-routing te forwarding statistics to clear SR TE forwarding statistics.
Syntax
reset segment-routing te forwarding statistics [ binding-sid binding-sid | color color-value endpoint endpoint-ipv4 | name name-value ]
Views
User view
Predefined user roles
network-admin
Parameters
binding-sid bsid: Specifies the BSID of an SR-MPLS TE policy.
color color-value endpoint endpoint-ipv4: Specifies the color value and end-point IPv4 address of an SR-MPLS TE policy. The value range for the color-value argument is 0 to 4294967295.
name policy-name: Specifies the name of an SR-MPLS 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 SR-MPLS TE policies.
Examples
# Clear forwarding statistics for all SR-MPLS TE policies.
<Sysname> reset segment-routing te forwarding statistics
Related commands
display segment-routing te forwarding verbose
forwarding statistics enable
forwarding statistics interval
router-id filter
Use router-id filter to enable BGP IPv4 SR policy route filtering by router ID.
Use undo router-id filter to disable BGP IPv4 SR policy route filtering by router ID.
Syntax
router-id filter [ bgp-rib-only ]
undo router-id filter
Default
BGP IPv4 SR policy route filtering by router ID is disabled.
Views
BGP IPv4 SR policy address family view
Predefined user roles
network-admin
Parameters
bgp-rib-only: When the device receives a BGP IPv4 SR policy route and the Route Target attribute of the route does not carry the local Router ID, it accepts the route but does not generate an SR-MPLS TE policy accordingly.
Usage guidelines
When a large number of BGP IPv4 SR policy routes exist in the network, execute this command to enable the device to process only specific BGP IPv4 SR policy routes.
This command enables the device to check the Route Target attribute of a received BGP IPv4 SR policy route.
· If the Route Target attribute contains the Router ID of the local device, the device accepts the route and generates an SR-MPLS TE policy accordingly.
· If the Route Target attribute does not contain the Router ID of the local device, the device processes the route as follows:
¡ If the bgp-rib-only keyword is not specified in the command, the device drops the route.
¡ If the bgp-rib-only keyword is specified in the command, the device accepts the route but does not generate the corresponding SR-MPLS TE policy.
When the controller advertises a BGP IPv4 SR policy route to the source node, the transit nodes between the controller and the source node only need to forward the BGP IPv4 SR policy route. They do not need to generate the SR-MPLS TE policy. In this case, you can execute the router-id filter bgp-rib-only command on the transit nodes. Then, when a transit node receives a BGP IPv4 SR policy route, it forwards the route even if the route's Route Target attribute does not contain the Router ID of the local device. Meanwhile, it does not generate an SR-MPLS TE policy in order to not affect packet forwarding.
If you execute this command multiple times, the most recent configuration takes effect.
To use Router ID filtering, make sure you add Route Target attributes to BGP IPv4 SR policy routes properly by using routing policy or other methods. Otherwise, Router ID filtering might learn or drop BGP IPv4 SR policy routes incorrectly.
Examples
# Enable BGP IPv4 SR policy route filtering by router ID.
<Sysname> system-view
[Sysname] bgp 100
[Sysname-bgp-default] address ipv4 sr-policy
[Sysname-bgp-default-srpolicy-ipv4] router-id filter
sbfd
Use sbfd to configure SBFD for an SR-MPLS TE policy.
Use undo sbfd to restore the default.
Syntax
sbfd { disable | enable [ remote remote-id ] [ template template-name ] [ backup-template backup-template-name ] }
undo sbfd { disable | enable }
Default
SBFD is disabled for an SR-MPLS TE policy.
Views
SR-MPLS TE policy view
Predefined user roles
network-admin
Parameters
disable: Disables SBFD for the SR-MPLS TE policy.
enable: Enables SBFD for the SR-MPLS 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 sr-policy sbfd enable command setting in SR TE view applies.
template template-name: Specifies an SBFD session parameter template by its name, a case-sensitive string of 1 to 63 characters. If you do not specify this option, the template specified in SR TE view applies.
backup-template backup-template-name: Specifies an SBFD session parameter template for the backup 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, the primary template applies. If the primary template is not specified either, the template specified in SR TE view applies.
Usage guidelines
This command enables an SR-MPLS TE policy to use SBFD to detect availability of SID lists. If all SID lists for the current candidate path are faulty, another candidate path takes over to minimize service interruption.
You can enable SBFD for all SR-MPLS TE policies globally in SR TE view or for a specific SR-MPLS TE policy in SR-MPLS TE policy view. The policy-specific configuration takes precedence over the global configuration. An SR-MPLS TE policy uses the global configuration only when it has no policy-specific configuration.
If you execute this command multiple times, the most recent configuration takes effect.
Examples
# Enable SBFD for SR-MPLS TE policy 1.
<Sysname> system-view
[Sysname] segment-grouting
[Sysname-segment-grouting] traffic-engineering
[Sysname-sr-te] policy 1
[Sysname-sr-te-policy-1] sbfd enable
Related commands
bfd template (High Availability Command Reference)
sr-policy sbfd enable
segment-list
Use segment-list to create a SID list and enter its view, or enter the view of an existing SID list.
Use undo segment-list to delete a SID list and all the configuration in the SID list.
Syntax
segment-list segment-list-name
undo segment-list segment-list-name
Default
No SID lists exist.
Views
SR TE view
Predefined user roles
network-admin
Parameters
segment-list-name: Specifies the SID list name, a case-sensitive string of 1 to 128 characters.
Examples
# Create a SID list named abc and enter its view.
<Sysname> system-view
[Sysname] segment-routing
[Sysname-segment-routing] traffic-engineering
[Sysname-sr-te] segment-list abc
[Sysname-sr-te-sl-abc]
service-class
Use service-class to set a service class value for an SR-MPLS TE policy.
Use undo service-class to restore the default.
Syntax
service-class service-class-value
undo service-class
Default
No service class value is set for an SR-MPLS TE policy. An SR-MPLS TE policy uses service class 255, which has the lowest forwarding priority.
Views
SR-MPLS TE policy view
Predefined user roles
network-admin
Parameters
service-class-value: Specifies a service class value in the range of 1 to 15. The smaller the service class value, the lower the SR-MPLS TE policy forwarding priority. An SR-MPLS TE policy that is not assigned a service class value uses service class 255, which has the lowest forwarding priority.
Usage guidelines
The device compares the service class value of the traffic with the service class values of SR-MPLS TE policies and forwards the traffic to a matching tunnel. The device uses the following rules to select an SR-MPLS TE policy to forward the traffic:
· If the traffic matches only one SR-MPLS TE policy, the device uses this SR-MPLS TE policy.
· If the traffic matches multiple SR-MPLS TE policies, the device selects an SR-MPLS TE policy based on the flow forwarding mode:
¡ If only one flow exists and flow-based forwarding is used, the device randomly selects a matching SR-MPLS TE policy for packets of the flow.
¡ If multiple flows exist or if one flow exists but packet-based forwarding is used, the device uses all matching SR-MPLS TE policies to load share the packets.
For more information about the flow identification and load sharing mode, see the ip load-sharing mode command.
· If the traffic does not match any SR-MPLS TE policy, the device randomly selects an SR-MPLS TE policy from all SR-MPLS TE policies with the lowest priority. (The smaller the service class value, the lower the SR-MPLS TE policy priority. An SR-MPLS TE policy that is not assigned a service class value has the lowest priority.)
To set a service class value for traffic, use the remark service-class command in traffic behavior view.
Examples
# Set the service class value to 5 for SR-MPLS TE policy.
<Sysname> system-view
[Sysname] segment-routing
[Sysname-segment-routing] traffic-engineering
[Sysname-sr-te] policy 1
[Sysname-sr-te-policy-1] service-class 5
Related commands
ip load-sharing mode (Layer 3—IP Services Command Reference)
remark service-class (ACL and QoS Command Reference)
shutdown
Use shutdown to shut down an SR-MPLS TE policy.
Use undo shutdown to bring up an SR-MPLS TE policy.
Syntax
shutdown
undo shutdown
Default
An SR-MPLS TE policy is not administratively shut down.
Views
SR-MPLS TE policy view
Predefined user roles
network-admin
Usage guidelines
If multiple SR-MPLS TE policies exist on the device, you can shut down unnecessary SR-MPLS TE policies to prevent them from affecting traffic forwarding.
Examples
# Shut down SR-MPLS TE policy 1.
<Sysname> system-view
[Sysname] segment-routing
[Sysname-segment-routing] traffic-engineering
[Sysname-sr-te] policy 1
[Sysname-sr-te-policy-1] shutdown
snmp-agent trap enable sr-policy
Use snmp-agent trap enable sr-policy to enable SNMP notifications for SR-MPLS TE policies.
Use undo snmp-agent trap enable sr-policy to disable SNMP notifications for SR-MPLS TE policies.
Syntax
snmp-agent trap enable sr-policy
undo snmp-agent trap enable sr-policy
Default
SNMP notifications for SR-MPLS 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 of SR-MPLS 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.
Examples
# Enable SNMP notifications for SR-MPLS TE policies.
<Sysname> system-view
[Sysname] snmp-agent trap enable sr-policy
sr-policy backup hot-standby enable
Use sr-policy backup hot-standby enable to enable hot standby for all SR-MPLS TE policies.
Use undo sr-policy backup hot-standby enable to disable hot standby for all SR-MPLS TE policies.
Syntax
sr-policy backup hot-standby enable
undo sr-policy backup hot-standby enable
Default
Hot standby is disabled for all SR-MPLS TE policies.
Views
SR TE view
Predefined user roles
network-admin
Usage guidelines
The hot standby feature takes the candidate path with the greatest preference value in the SR-MPLS TE policy as the primary path and that with the second greatest preference value as the standby path. When the forwarding paths corresponding to all SID lists of the primary path fails, the standby path immediately takes over to minimize service interruption.
You can enable hot standby for all SR-MPLS TE policies globally in SR TE view or for a specific SR-MPLS TE policy in SR-MPLS TE policy view. The policy-specific configuration takes precedence over the global configuration. An SR-MPLS TE policy uses the global configuration only when it has no policy-specific configuration.
Examples
# Enable hot standby for all SR-MPLS TE policies.
<Sysname> system-view
[Sysname] segment-routing
[Sysname-segment-routing] traffic-engineering
[Sysname-sr-te] sr-policy backup hot-standby enable
Related commands
backup hot-standby
sr-policy bfd first-fail-timer
Use sr-policy bfd first-fail-timer to configure the delay time for the device to notify an SR-MPLS TE policy of the BFD/SBFD session down event.
Use undo sr-policy bfd first-fail-timer to restore the default.
Syntax
sr-policy bfd first-fail-timer seconds
undo sr-policy bfd first-fail-timer
Default
The delay time for the device to notify an SR-MPLS TE policy of the BFD/SBFD session down event is 60 seconds.
Views
SR TE view
Predefined user roles
network-admin
Parameters
sessions: Specifies the delay time in the range of 1 to 600 seconds. The default delay time is 60 seconds. After the device detects a BFD/SBFD session setup failure for the first time for an SR-MPLS TE policy, it waits for the delay time for the BFD/SBFD session to be re-established. If the BFD/SBFD session cannot be established successfully after the delay time expires, the device notifies the SR-MPLS TE policy of the BFD/SBFD session down event.
Usage guidelines
When an SR-MPLS TE policy meets the following conditions, the device tries to establish a BFD/SBFD session for the SR-MPLS TE policy:
· The SR-MPLS TE policy is in up state.
· The SID list of the SR-MPLS TE policy is in up state.
· BFD or SBFD is enabled to detect connectivity of the SR-MPLS TE policy.
The device fails to establish the BFD/SBFD session if the session is not in up state when the session detection time expires. The device does not immediately notify the SR-MPLS TE policy of this event but wait for the specified delay time. If the BFD/SBFD session cannot be established successfully after the delay time expires, the device notifies the SR-MPLS TE policy of the BFD/SBFD session down event.
If you execute this command multiple times, the most recent configuration takes effect.
Examples
# Configure the delay time for the device to notify an SR-MPLS TE policy of the BFD/SBFD session down event to 30 seconds.
<Sysname> system-view
[Sysname] segment-routing
[Sysname-segment-routing] traffic-engineering
[Sysname-sr-te] sr-policy bfd first-fail-timer 30
sr-policy bfd trigger path-down enable
Use sr-policy bfd trigger path-down enable to globally enable BFD session down events to trigger SR-MPLS TE policy path reselection.
Use undo sr-policy bfd trigger path-down enable to globally disable BFD session down events from triggering SR-MPLS TE policy path reselection.
Syntax
sr-policy bfd trigger path-down enable
undo sr-policy bfd trigger path-down enable
Default
This feature disabled globally for all SR-MPLS TE policies.
Views
SR TE view
Predefined user roles
network-admin
Usage guidelines
By default, when an SR-MPLS TE policy contains multiple valid candidate paths:
· If hot standby is not enabled, BFD/SBFD detects all the SID lists of the optimal candidate path and establishes a BFD/SBFD session for each of the SID lists. When all the BFD/SBFD sessions are down, the SR-MPLS TE policy does not reselect a candidate path and packets are no longer forwarded through the SR-MPLS TE policy.
· If hot standby is enabled, BFD/SBFD detects all the SID lists of the main and backup candidate paths and establishes a BFD/SBFD session for each of the SID lists.
¡ When all the BFD/SBFD sessions for the main path are down, the SR-MPLS TE policy switches traffic to the backup path and does not reselect a candidate path.
¡ When all the BFD/SBFD sessions for the main and backup paths are down, the SR-MPLS TE policy does not reselect a candidate path and packets are no longer forwarded through the SR-MPLS TE policy.
After you enable this feature by executing this command for an SR-MPLS TE policy that contains multiple valid candidate paths:
· If hot standby is not enabled, BFD/SBFD detects all the SID lists of the optimal candidate path and establishes a BFD/SBFD session for each of the SID lists. When all the BFD/SBFD sessions are down, the SR-MPLS TE policy reselects a candidate path and uses the new candidate path to forward packets. If no valid candidate path is available during the resection, packets cannot be forwarded through the SR-MPLS TE policy.
· If hot standby is enabled, BFD/SBFD detects all the SID lists of the main and backup candidate paths and establishes a BFD/SBFD session for each of the SID lists.
¡ When all the BFD/SBFD sessions for the main path are down, the SR-MPLS TE policy switches traffic to the backup path and reselects the main and backup paths.
¡ When all the BFD/SBFD sessions for the main and backup paths are down, the SR-MPLS TE policy reselects the main and backup paths and forwards packets through the new main path.
¡ If no valid candidate path is available during the resection, packets cannot be forwarded through the SR-MPLS TE policy.
Before you enable this feature for an SR-MPLS TE policy, create an SBFD session for the policy first.
You can enable this feature for all SR-MPLS TE policies globally in SR TE view or for a specific SR-MPLS TE policy in SR-MPLS TE policy view. The policy-specific configuration takes precedence over the global configuration. An SR-MPLS TE policy uses the global configuration only when it has no policy-specific configuration.
Examples
# Enable BFD session down events to trigger candidate path reselection for SR-MPLS TE policies.
<Sysname> system-view
[Sysname] segment-routing
[Sysname-segment-routing] traffic-engineering
[Sysname-sr-te] sr-policy bfd trigger path-down enable
Related commands
bfd trigger path-down
sbfd
sr-policy sbfd enable
sr-policy log enable
Use sr-policy log enable to enable SR-MPLS TE policy logging.
Use undo sr-policy log enable to disable SR-MPLS TE policy logging.
Syntax
sr-policy log enable
undo sr-policy log enable
Default
SR-MPLS TE policy logging is disabled.
Views
SR TE view
Predefined user roles
network-admin
Usage guidelines
This feature enables the device to log SR-MPLS TE policy state changes to facilitate audit of SR-MPLS TE policy operations. The SR-MPLS TE policy log messages are sent to the information center and output as configured in the information center. For more information about information center, see Network Management and Monitoring Configuration Guide.
Examples
# Enable SR-MPLS TE policy logging.
<Sysname> system-view
[Sysname] segment-routing
[Sysname-segment-routing] traffic-engineering
[Sysname-sr-te] sr-policy log enable
sr-policy sbfd enable
Use sr-policy sbfd enable to enable SBFD for all SR-MPLS TE policies.
Use undo sr-policy sbfd enable to disable SBFD for all SR-MPLS TE policies.
Syntax
sr-policy sbfd enable [ remote remote-id ] [ template template-name ] [ backup-template backup-template-name ]
undo sr-policy sbfd enable
Default
SBFD is disabled for all SR-MPLS TE policies.
Views
SR 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 by using the sbfd destination ipv4 remote-discriminator command is used.
template template-name: Specifies an SBFD session parameter template by its name, a case-sensitive string of 1 to 63 characters. If you do not specify this option, SBFD uses the multihop SBFD session settings configured in system view.
backup-template backup-template-name: Specifies an SBFD session parameter template for the backup 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, the primary template applies. If the primary template is not specified either, SBFD uses the multihop SBFD session settings configured in system view.
Usage guidelines
This command enables SR-MPLS TE policies to use SBFD to detect availability of SID lists. If all SID lists for the current candidate path are faulty, another candidate path takes over to minimize service interruption.
You can enable SBFD for all SR-MPLS TE policies globally in SR TE view or for a specific SR-MPLS TE policy in SR-MPLS TE policy view. The policy-specific configuration takes precedence over the global configuration. An SR-MPLS TE policy uses the global configuration only when it has no policy-specific configuration.
If you execute this command multiple times, the most recent configuration takes effect.
Examples
# Enable SBFD for all SR-MPLS TE policies.
<Sysname> system-view
[Sysname] segment-routing
[Sysname-segment-routing] traffic-engineering
[Sysname-sr-te] sr-policy sbfd enable
Related commands
bfd template (High Availability Command Reference)
sbfd
sbfd destination ipv4 remote-discriminator (High Availability Command Reference)
sr-policy sbfd timer
Use sr-policy sbfd timer to configure SBFD detection timer parameters.
Use undo sr-policy sbfd timer to delete SBFD detection timer parameters.
Syntax
sr-policy sbfd timer { detect-multiplier multiplier-value | min-tx-interval transmit-interval }
undo sr-policy sbfd timer { detect-multiplier | min-tx-interval }
Default
The SBFD detection time multiplier is 5, and the minimum SBFD packet transmission interval is 10 milliseconds.
Views
SR TE view
Predefined user roles
network-admin
Parameters
detect-multiplier multiplier-value: Specifies the SBFD detection time multiplier, in the range of 3 to 50.
min-tx-interval transmit-interval: Specifies the minimum SBFD packet transmission interval, in the range of 3 to 10000 milliseconds.
Usage guidelines
Set the minimum SBFD packet transmission interval to prevent the SBFD control packet sending rate from exceeding the device capability. The actual SBFD control packet transmitting interval is the set minimum interval.
The detection time multiplier determines the maximum number of SBFD control packets that an initiator can discard continuously. The detection time is the detection time multiplier of the initiator multiplied by the minimum SBFD packet transmission interval of the initiator.
If you execute this command multiple times, the most recent configuration takes effect.
Examples
# Set the minimum SBFD packet transmission interval to 100 milliseconds.
<Sysname> system-view
[Sysname] segment-grouting
[Sysname-segment-grouting] traffic-engineering
[Sysname-sr-te] sr-policy sbfd timer min-tx-interval 100
sr-policy steering
Use sr-policy steering to configure the traffic steering mode for SR-MPLS 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 SR-MPLS 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 SR-MPLS TE policy. Tunnel policy-based traffic steering is allowed.
policy-based: Steers traffic to an SR-MPLS TE policy based on a tunnel policy if the BGP route does not contain the color extended community. After this keyword is specified, traffic is steered based on tunnel binding policy, color, and load sharing policy, in descending order of priority.
Usage guidelines
The following traffic steering modes are available for SR-MPLS TE policies:
· Based on color—The device searches for an SR-MPLS TE policy with the color value and end point that match the color extended community attribute and next hop address of a BGP route. If a matching SR-MPLS TE policy exists, the device recurses the BGP route to that SR-MPLS TE policy. Then, when the device receives packets that match the BGP route, it forwards the packets through the SR-MPLS TE policy.
· Based on tunnel policy—On the ingress PE of an MPLS L3VPN or EVPN L3VPN network, configure a tunnel policy that uses an SR-MPLS TE policy as the public tunnel to carry the VPN packets. For more information about the tunnel policy configuration, see MPLS Configuration Guide.
This command does not take effect in L2VPN networks.
Examples
# Configure the SR-TE traffic steering mode as tunnel policy.
<Sysname> system-view
[Sysname] bgp 100
[Sysname-bgp-default] sr-policy steering policy-based
sr-policy switch-delay delete-delay
Use sr-policy switch-delay delete-delay to configure the switchover delay time and deletion delay time for the SR-MPLS TE policy forwarding path.
Use undo sr-policy switch-delay to restore the default.
Syntax
sr-policy switch-delay switch-delay-time delete-delay delete-delay-time
undo sr-policy switch-delay
Default
The switchover delay time and deletion delay time for the SR-MPLS TE policy forwarding path is 5000 milliseconds and 20000 milliseconds, respectively.
Views
SR TE view
Predefined user roles
network-admin
Parameters
switch-delay-time: Sets the forwarding path switchover delay time, in the range of 0 to 600000 milliseconds.
delete-delay-time: Sets the forwarding path deletion delay time, in the range of 0 to 600000 milliseconds.
Usage guidelines
The switchover delay and deletion delay mechanism is used to avoid traffic forwarding interruption during a forwarding path switchover.
When updating an SR-MPLS TE policy forwarding path, the device first establishes the new forwarding path before it deletes the old one. During the new path setup process, the device uses the old path to forward traffic until the switchover delay timer expires. When the switchover delay timer expires, the device switches traffic to the new path. The old path is deleted when the deletion delay timer expires.
Examples
# Set the SR-MPLS TE policy forwarding path switchover delay time to 8000 milliseconds and the deletion delay time to 15000 milliseconds.
<Sysname> system-view
[Sysname] segment-grouting
[Sysname-segment-grouting] traffic-engineering
[Sysname-sr-te] sr-policy switch-delay 8000 delete-delay 15000
sr-policy up-delay
Use sr-policy up-delay to set the delay time for bringing up SR-MPLS TE policies.
Use undo sr-policy up-delay to restore the default.
Syntax
sr-policy up-delay delay-time
undo sr-policy up-delay
Default
The device does not delay bringing up SR-MPLS TE policies.
Views
SR TE view
Predefined user roles
network-admin
Parameters
delay-time: SR-MPLS TE policy-up delay time, in the range of 1 to 600000 milliseconds.
Usage guidelines
After an SR-MPLS TE policy recovers from a fault, the device waits for the delay time before bringing up the SR-MPLS TE policy. This is to ensure that the fault is completely removed so as to avoid packet loss caused by SR-MPLS TE policy flapping.
After this command is executed, the device starts different delay timers for an SR-MPLS TE policy according to the SBFD configuration for the SR-MPLS TE policy.
· If SBFD is not enabled, the device starts an LSP delay timer when the SID list state changes from Down to Up.
· If SBFD is enabled, the device starts an SBFD delay timer when the SBFD session state changes from Down to Up.
To view the SBFD configuration, SID list state, and SBFD session state, execute the display segment-routing te policy command.
Set a proper SR-MPLS TE policy-up delay time according to your network conditions. A very long delay time will cause an SR-MPLS TE policy to be unable to process user traffic for a long time.
You can set the delay time for all SR-MPLS TE policies globally in SR TE view or for a specific SR-MPLS TE policy in SR-MPLS TE policy view. The policy-specific configuration takes precedence over the global configuration. An SR-MPLS TE policy uses the global configuration only when it has no policy-specific configuration.
If you execute this command for multiple times, the most recent configuration takes effect. A new delay time setting does not apply to the SR-MPLS TE policies that are already in a delay process.
Examples
# Set the policy-up delay time to 10000 milliseconds for all SR-MPLS TE policies.
<Sysname> system-view
[Sysname] segment-routing
[Sysname-segment-routing] traffic-engineering
[Sysname-sr-te] sr-policy up-delay 10000
Related commands
display segment-routing te policy
up-delay
traffic-engineering
Use traffic-engineering to create and enter the SR TE view, or enter the existing SR TE view.
Use undo traffic-engineering to delete the SR TE view and all the configuration in the view.
Syntax
traffic-engineering
undo traffic-engineering
Default
The SR TE view does not exist.
Views
Segment routing view
Predefined user roles
network-admin
Examples
# Create and enter the SR TE view.
<Sysname> system-view
[Sysname] segment-routing
[Sysname-segment-routing] traffic-engineering
[Sysname-sr-te]
up-delay
Use up-delay to set the delay time for bringing up an SR-MPLS TE policy.
Use undo up-delay to restore the default.
Syntax
up-delay delay-time
undo up-delay
Default
No policy-up delay time is set for an SR-MPLS TE policy, and the policy-up delay time set in SR TE view applies.
Views
SR-MPLS TE policy view
Predefined user roles
network-admin
Parameters
delay-time: SR-MPLS TE policy-up delay time, in the range of 1 to 600000 milliseconds.
Usage guidelines
After an SR-MPLS TE policy recovers from a fault, the device waits for the delay time before bringing up the SR-MPLS TE policy. This is to ensure that the fault is completely removed so as to avoid packet loss caused by SR-MPLS TE policy flapping.
After this command is executed, the device starts different delay timers for an SR-MPLS TE policy according to the SBFD configuration for the SR-MPLS TE policy.
· If SBFD is not enabled, the device starts an LSP delay timer when the SID list state changes from Down to Up.
· If SBFD is enabled, the device starts an SBFD delay timer when the SBFD session state changes from Down to Up.
To view the SBFD configuration, SID list state, and SBFD session state, execute the display segment-routing te policy command.
Set a proper SR-MPLS TE policy-up delay time according to your network conditions. A very long delay time will cause an SR-MPLS TE policy to be unable to process user traffic for a long time.
You can set the delay time for all SR-MPLS TE policies globally in SR TE view or for a specific SR-MPLS TE policy in SR-MPLS TE policy view. The policy-specific configuration takes precedence over the global configuration. An SR-MPLS TE policy uses the global configuration only when it has no policy-specific configuration.
If you execute this command for multiple times, the most recent configuration takes effect. A new delay time setting does not apply to the SR-MPLS TE policies that are already in a delay process.
Examples
# Set the policy-up delay time to 10000 milliseconds for SR-MPLS TE policy p1.
<Sysname> system-view
[Sysname] segment-routing
[Sysname-segment-routing] traffic-engineering
[Sysname-sr-te ]policy p1
[Sysname-sr-te-policy-p1] up-delay 10000
Related commands
display segment-routing te policy
sr-policy up-delay
validation-check enable
Use validation-check enable to enable validity check for BGP IPv4 SR policy routes.
Use undo validation-check enable to disable validity check for BGP IPv4 SR policy routes.
Syntax
validation-check enable
undo validation-check enable
Default
Validity check for BGP IPv4 SR policy routes is disabled. The device does not check the validity of the BGP IPv4 SR policy routes received from the peer or peer group.
Views
BGP IPv4 SR policy address family
Predefined user roles
network-admin
Usage guidelines
After validity check is enabled for BGP IPv4 SR policy routes, the device determines that a BGP IPv4 SR policy route is invalid and will not select the route if the route does not contain the RT extended community attribute (IPv4 address format) or the NO_ADVERTISE community attribute.
You can configure this feature on the RR in networks where the controller and the RR establish BGP peer relationship and the RR establishes BGP peer relationship with the source nodes of multiple SR-MPLS TE policies.
The RR checks whether the SR policy routes issued by the controller carry the IPv4 address format RT extended community attribute or the NO_ADVERTISE community attribute. If yes, the RR accepts the routes and reflects the routes that do not carry the NO_ADVERTISE attribute to the source nodes of the SR-MPLS TE policies.
On the source nodes, you can use the router-id filter command to enable BGP IPv4 SR policy route filtering by router ID. After a source node receives a BGP IPv4 SR policy route, it compares the local router ID with the IPv4 address in the RT attribute of the route. If they are the same, the source node accepts the route. If they are different, the source node drops the route.
Examples
# Enable validity check for BGP IPv4 SR policy routes.
<Sysname> system-view
[Sysname] bgp 100
[Sysname-bgp-default] address ipv4 sr-policy
[Sysname-bgp-default-srpolicy-ipv4] validation-check enable
Related commands
router-id filter