The BFD detection time multiplier is not set for SRLSPs. The BFD detection time multiplier set by the bfd multi-hop detect-multiplier command applies.

Views

Segment Routing view

Predefined user roles

network-admin

Parameters

value: Specifies a detection time multiplier, which is the maximum number of consecutive BFD packets that can be discarded. The value range for this argument is 3 to 50.

Usage guidelines

The device sends BFD packets to a peer periodically. If the device does not receive BFD packets from the peer within the actual detection interval, it determines that the session is down. The actual detection interval of the sender is the detection time multiplier of the receiver × the actual sending interval of the receiver.

This command takes effect only on BFD sessions created by the bfd enable command.

Examples

# Set the BFD detection time multiplier to 3 for SRLSPs.

<Sysname> system-view

[Sysname] segment-routing

[Sysname-segment-routing] bfd detect-multiplier 3

Related commands

bfd enable

bfd multi-hop detect-multiplier (High Availability Command Reference)

bfd enable

Use bfd enable to enable BFD for SRLSPs.

Use undo bfd enable to restore the default.

Syntax

bfd enable [ prefix-list prefix-list-name ] [ echo | nil-fec ]

undo bfd enable

Default

BFD for SRLSPs is not enabled.

Views

Segment routing view

Predefined user roles

network-admin

Parameters

prefix-list prefix-list-name: Specifies an IPv4 prefix list by the prefix list name, a case-sensitive string of 1 to 63 characters. The device can create BFD sessions only for the SRLSPs permitted by the specified IPv4 prefix list. If you do not specify an IPv4 prefix list, the device can create BFD sessions for all SRLSPs.

echo: Specifies the BFD echo packet mode. If you do not specify this keyword, the BFD control packet mode is used to verify SRLSP connectivity.

nil-fec: Encapsulates the Nil FEC in MPLS echo request packets when BFD control packet mode is used to detect SRLSPs. In SR to LDP interworking mode, the ingress node (source node) cannot determine whether the LDP LSP is connected to the SRLSP. When the ingress node uses MPLS BFD to detect LSPs, it encapsulates LDP FEC in MPLS echo request packets, which will fail the FEC type verification on the egress node (end-point node). Then, the BFD session will go down. To resolve this issue, specify the nil-fec keyword to enable the ingress node to encapsulate the Nil FEC in MPLS echo request packets. The egress node will not check the FEC type of packets encapsulated with the Nil FEC.

Usage guidelines

This command enables the device to create a BFD session for each primary SRLSP to verify the connectivity of the primary SRLSP. When a primary SRLSP fails, BFD can quickly detect the failure and switches traffic to the backup SRLSP to reduce packet loss.

Before you execute this command, enable MPLS BFD by using the mpls bfd enable command.

If you execute both the bfd enable command and the mpls bfd command for SRLSPs, the mpls bfd command takes effect on the SRLSPs.

In segment routing view, if you execute the bfd enable command and the sbfd enable command multiple times, the most recent configuration takes effect.

Examples

# Enable BFD for SRLSPs.

<Sysname> system-view

[Sysname] segment-routing

[Sysname-segment-routing] bfd enable

Related commands

mpls bfd (for LSP) (MPLS Command Reference)

mpls bfd enable (MPLS Command Reference)

sbfd enable

bfd min-echo-receive-interval

Use bfd min-echo-receive-interval to set the minimum interval for receiving BFD echo packets for SRLSP BFD.

Use undo bfd min-echo-receive-interval to restore the default.

Syntax

bfd min-echo-receive-interval interval

undo bfd min-echo-receive-interval

Default

The minimum interval for receiving BFD echo packets is not set for SRLSP BFD. The interval set by the bfd multi-hop min-echo-receive-interval command applies.

Views

Segment routing view

Predefined user roles

network-admin

Parameters

interval: Specifies the minimum interval for receiving BFD echo packets, in milliseconds. The value range is 3 to 10000.

Usage guidelines

The interval for receiving BFD echo packets is also the interval for sending BFD echo packets. By executing this command, you can control both the receiving interval and sending interval for BFD echo packets.

This command takes effect only on the echo mode BFD sessions created by the bfd enable command.

Examples

# Set the minimum BFD echo packet receiving interval for SRLSP BFD to 450 milliseconds.

<Sysname> system-view

[Sysname] segment-routing

[Sysname-segment-routing] bfd min-echo-receive-interval 450

Related commands

bfd enable

bfd multi-hop min-echo-receive-interval (High Availability Command Reference)

bfd min-receive-interval

Use bfd min-receive-interval to set the minimum BFD packet receiving interval for SRLSP BFD.

Use undo bfd min-receive-interval to restore the default.

Syntax

bfd min-receive-interval interval

undo bfd min-receive-interval

Default

The minimum interval for receiving BFD packets is not set for SRLSP BFD. The interval set by the bfd multi-hop min-receive-interval command applies.

Views

Segment routing view

Predefined user roles

network-admin

Parameters

interval: Specifies the minimum interval for receiving BFD packets, in milliseconds. The value range is 3 to 10000.

Usage guidelines

Use this command to prevent the packet sending rate of the peer end from exceeding the packet receiving rate of the local end. If the receiving rate is exceeded, the peer end dynamically adjusts the BFD packet transmitting interval to the minimum receiving interval of the local end.

This command takes effect only on BFD sessions created by the bfd enable command.

Examples

# Set the minimum BFD packet receiving interval for SRLSP BFD to 550 milliseconds.

<Sysname> system-view

[Sysname] segment-routing

[Sysname-segment-routing] bfd min-receive-interval 550

Related commands

bfd enable

bfd multi-hop min-receive-interval (High Availability Command Reference)

bfd min-transmit-interval

Use bfd min-transmit-interval to set the minimum BFD packet transmitting interval for SRLSP BFD.

Use undo bfd min-transmit-interval to restore the default.

Syntax

bfd min-transmit-interval interval

undo bfd min-transmit-interval

Default

The minimum interval for transmitting BFD packets is not set for SRLSP BFD. The interval set by the bfd multi-hop min-transmit-interval command applies.

Views

Segment routing view

Predefined user roles

network-admin

Parameters

interval: Specifies the minimum interval for transmitting BFD packets, in milliseconds. The value range is 3 to 10000.

Usage guidelines

Use this command to prevent the BFD packet sending rate from exceeding the packet receiving rate of the peer end.

The actual BFD packet transmitting interval on the local end is the greater value between the following values:

· Minimum interval for transmitting BFD packets on the local end.

· Minimum interval for receiving BFD packets on the peer end.

This command takes effect only on BFD sessions created by the bfd enable command.

Examples

# Set the minimum BFD packet transmitting interval for SRLSP BFD to 450 milliseconds.

<Sysname> system-view

[Sysname] segment-routing

[Sysname-segment-routing] bfd min-transmit-interval 450

Related commands

bfd enable

bfd multi-hop min-transmit-interval (High Availability Command Reference)

display bgp egress-engineering ipv4

Use display bgp egress-engineering ipv4 to display BGP-EPE information.

Syntax

display bgp [ instance instance-name ] egress-engineering ipv4 [ ipv4-address ] [ verbose ]

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 this option, the command displays information about the default BGP instance.

ipv4-address: Specifies the IPv4 address of an existing peer. If you do not specify this argument, the command displays information about all peers and peer groups.

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

Examples

# Display brief BGP-EPE information.

<Sysname> display bgp egress-engineering ipv4

PeerSet : 192.168.1.2

Local ASNumber : 1

Remote ASNumber : 2

Local RouterID : 1.1.1.3

Remote RouterID : 1.1.1.4

OriginNextHop : 192.168.1.2

RelyNextHop : 192.168.1.2

Interface : XGE3/1/1

# Display brief BGP-EPE information for a peer.

<Sysname> display bgp egress-engineering ipv4 192.168.1.5

BGP peering segment type: Node-Adjacency

PeerNodeAdj : 192.168.1.5

Local ASNumber : 1

Remote ASNumber : 2

Local RouterID : 1.1.1.3

Remote RouterID : 1.1.1.5

OriginalNextHop : 192.168.1.5

RelyNextHop : 192.168.1.5

Interface : XGE3/1/5

# Display detailed BGP-EPE information for a peer.

<Sysname> display bgp egress-engineering ipv4 1.1.1.1 verbose

BGP peering segment type : Node

PeerAdj Num : 2

PeerNode : 1.1.1.1

Local ASNumber : 1

Remote AsNumber : 2

Local RouterID : 1.1.1.3

Remote RouterID : 1.1.1.4

Local Interface Address : 2.2.2.2

Remote Interface Address : 1.1.1.1

OriginalNextHop : 1.1.1.1

RelyNextHop : 100.0.27.7

Interface : XGE3/1/1

OriginalNextHop : 1.1.1.1

RelyNextHop : 100.0.28.7

Label : 15000

TunnelPolicy : abc

BGP peering segment type : Adjacency

PeerAdj : 100.0.27.7

Local ASNumber : 1

Remote ASNumber : 2

Local RouterID : 1.1.1.1

Remote RouterID : 2.2.2.2

OriginalNextHop : 100.0.27.7

RelyNextHop : 100.0.27.7

Local Interface Address : 100.0.27.2

Remote Interface Address : 100.0.27.7

Interface : XGE3/1/1

Label : 24001

TunnelPolicy : abc

TE Administrative group: 0x0

TE Maximum link bandwidth(kbits/sec): 100000

TE Maximum reservable link bandwidth(kbits/sec): 9999

TE Maximum Unreserved bandwidth(kbits/sec): 999 999 999 999 999 999 999 999

TE Metric: 1

TE SRLG: 100

Delay flag: 0, Average delay(us): 100

Delay range flag: 0, Min delay(us): 100, Max delay(us): 200

Delay variation(us): 200

Remaining bandwidth(bytes/sec): 200

Available bandwidth(bytes/sec): 100

Utilized bandwidth(bytes/sec): 50

Link loss flag: 0, Link loss rate: 50.331624%

BGP peering segment type : Adjacency

PeerAdj : 100.0.28.7

Local ASNumber : 1

Remote ASNumber : 2

Local RouterID : 1.1.1.1

Remote RouterID : 2.2.2.2

OriginalNextHop : 100.0.28.7

RelyNextHop : 100.0.28.7

Local Interface Address : 100.0.28.2

Remote Interface Address : 100.0.28.7

Interface : XGE3/1/2

Label : 24002

TunnelPolicy : abc

TE Administrative group: 0x0

TE Maximum link bandwidth(kbits/sec): 100000

TE Maximum reservable link bandwidth(kbits/sec): 9999

TE Maximum Unreserved bandwidth(kbits/sec): 999 999 999 999 999 999 999 999

TE Metric: 1

TE SRLG: 100

Delay flag: 0, Average delay(us): 100

Delay range flag: 0, Min delay(us): 100, Max delay(us): 200

Delay variation(us): 200

Remaining bandwidth(bytes/sec): 200

Available bandwidth(bytes/sec): 100

Utilized bandwidth(bytes/sec): 50

Link loss flag: 0, Link loss rate: 50.331624%

Table 1 Command output

Field	Description
BGP peering segment type	Type of the BGP peering segments to the specified peer: · Node. · Adjacency. · Set. · Node-Adjacency.
PeerAdj Num	Number of peering adjacencies.
Local ASNumber	Local AS number.
Remote ASNumber	Remote AS number.
Interface	Interface on which the neighborship is established.
OriginalNextHop	Original next hop.
RelyNextHop	Recursive next hop.
TE Administrative Group	Administrative group of the link, a link attribute.
Delay flag	Flag that indicates whether the average, minimum, or maximum delay has exceeded 16777215 microseconds. · 0—The measured average, minimum, or maximum delay of the link is equal to or less than 16777215 microseconds, indicating that the link is stable. · 1—The measured average, minimum, or maximum delay of the link is greater than 16777215 microseconds.
Remaining/available/utilized bandwidth(bytes/sec)	Remaining bandwidth, available bandwidth, or used bandwidth of the link, in bytes per second.
Link loss flag	Flag that indicates whether the packet loss rate has exceeded 50.331642%. · 0—The measured packet loss rate of the link is smaller than 50.331642%, indicating that the link is stable. · 1—The measured packet loss rate of the link is equal to or greater than 50.331642%. The current link performance is poor.
Link loss rate	Packet loss rate in percentage.

‌

display bgp egress-engineering peer-set

Use display bgp egress-engineering peer-set to display BGP-EPE peer set information.

Syntax

display bgp [ instance instance-name ] egress-engineering peer-set [ peer-set-name ]

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 BGP-EPE peer set information for the default BGP instance.

peer-set-name: Specifies a BGP-EPE peer set by its name, a case-sensitive string of 1 to 63 characters. If you do not specify a peer set, this command displays information about all BGP-EPE peer sets.

Examples

# Display information about all BGP-EPE peer sets.

<Sysname> display bgp egress-engineering peer-set

BGP egress peering segment peer-set: a

PeerSet label : 2172

Members: 0

BGP egress peering segment peer-set: b

PeerSet label : 5555

Members: 1

BGP PeerNodeAdj : 3.3.3.3

BGP egress peering segment peer-set: c

PeerSet label: 65001

Label : 65001

Members: 2

BGP PeerNode: 1.1.1.1

BGP PeerAdj : 10.1.1.1

PeerSet name: d

PeerSet label: 65002

Members: 2

BGP PeerNode: 2.2.2.2

BGP PeerAdj : 11.1.1.1

Table 2 Command output

Field	Description
BGP egress peering segment peer-set	Name of a BGP-EPE peer set.
PeerSet label	SID used by the BGP-EPE peer set.
Label	SID assigned to the BGP-EPE peer set.
Members	Number of peers in the BGP-EPE peer set.
BGP PeerNode	Address of the node peer.
BGP PeerAdj	Address of the adjacency peer.
BGP PeerNodeAdj	Address of the node-adjacency peer.

‌

display bgp segment-routing label-range

Use display bgp segment-routing label-range to display BGP SR label ranges.

Syntax

display bgp [ instance instance-name ] segment-routing label-range

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

Examples

# Display BGP SR label ranges.

<Sysname> display bgp segment-routing label-range

BGP peering segment labels:

2048-15999

24001-599999

Prefix labels:

16000-24000

display bgp segment-routing prefix-sid-map

Use display bgp segment-routing prefix-sid-map to display BGP SR prefix-SID mappings.

Syntax

display bgp [ instance instance-name ] segment-routing prefix-sid-map [ ip-address mask-length | verbose ]

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 this option, the command displays BGP SR prefix-SID mappings of the default BGP instance.

ip-address mask-length: Specifies a range of prefixes by an IP address and a mask length. The mask-length argument is in the range of 1 to 32.

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

Examples

# Display the BGP SR prefix-SID mapping for prefix 1.1.1.1/32.

<Sysname> display bgp segment-routing prefix-sid-map 1.1.1.1 32

Prefix SID index

1.1.1.1/32 10

# Display brief information about BGP SR prefix-SID mappings for all prefixes.

<Sysname> display bgp segment-routing prefix-sid-map

Number of mappings: 2

Prefix SID index Range

1.1.1.1/32 10 100

2.2.2.2/32 256 520

# Display detailed information about BGP SR prefix-SID mappings for all prefixes.

<Sysname> display bgp segment-routing prefix-sid-map verbose

Number of mappings: 2

Prefix: 1.1.1.1/32

SID index : 10

Range : 100

Last prefix : 1.1.1.100/32

Last SID index: 109

Prefix: 2.2.2.2/32

SID index : 256

Range : 520

Last prefix : 2.2.4.9/32

Last SID index: 775

Table 3 Command output

Field	Description
SID index	Start SID index value.
Range	Number of consecutive SIDs assigned.

‌

display isis segment-routing adjacency

Use display isis segment-routing adjacency to display IS-IS SR adjacency SID information.

Syntax

display isis [ process-id ] segment-routing adjacency [ sid sid-value | vpn-instance vpn-instance-name ] *

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

process-id: Specifies an IS-IS process ID in the range of 1 to 65535. If you do not specify this argument, the command displays SR adjacency SID information about all IS-IS processes.

sid sid-value: Specifies an adjacency SID by its value. The value range is 1024 to 1010152.

vpn-instance vpn-instance-name: Specifies an MPLS L3VPN instance by its name, a case-sensitive string of 1 to 31 characters.

Usage guidelines

If you do not specify the sid sid-value option, this command displays information about all IS-IS SR adjacency SIDs.

If you do not specify the vpn-instance vpn-instance-name option, this command displays SR adjacency SID information on the public network.

Examples

# Display SR adjacency SID information about IS-IS process 1.

<Sysname> display isis 1 segment-routing adjacency

Adjacency SID: 15020 Type: Non-member-port Request result: Init

SystemID Interface NextHop State ProcessID

0000.0000.0000.00 XGE3/1/1 2.2.2.2 Inactive 1

Table 4 Command output

Field	Description
Adjacency SID	Adjacency SID value.
Type	‌ Type of the adjacency SID assigned to the adjacency link: · Member-port—Adjacency SID assigned to a Layer 3 aggregation group member interface. · Non-member-port—Adjacency SID assigned to a Layer 3 Ethernet interface that is not an aggregation group member interface.
Request result	Adjacency SID application result: · Succeeded—The application succeeded. · Conflicting—The adjacency SID is already used. · Init—The application is in progress or the adjacency SID allocation feature is not enabled. · Out-of-range—The adjacency SID is not the in the range of the SRLB.
SystemID	System ID of the neighbor.
Interface	Interface connected to the neighbor.
Nexthop	Next hop of the adjacency SID.
State	SID status: · Active—The SID is effective and is available for use. · Inactive—The SID is not effective and is not available for use.
ProcessID	IS-IS process ID.

‌

display isis segment-routing global-block

Use display isis segment-routing global-block to display IS-IS SRGB information.

Syntax

display isis segment-routing global-block [ level-1 | level-2 ] [ process-id ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

level-1: Specifies Level-1 SRGB.

level-2: Specifies Level-2 SRGB.

process-id: Specifies an IS-IS process ID in the range of 1 to 65535. If you do not specify this argument, the command displays the SRGBs of all IS-IS processes.

Usage guidelines

If you do not specify the level-1 or level-2 keyword, the command displays information about both the Level-1 SRGB and Level-2 SRGB.

Examples

# Display information about the SRGBs for IS-IS process 1.

<Sysname> display isis segment-routing global-block 1

Segment routing global block information for IS-IS(1)

-----------------------------------------------------

Level-1 SRGB

-------------------------

System ID Base Range

-------------------------------------------------------------------------------

0000.0000.0011 16666 5557

0000.0000.0012 18012 4001

Table 5 Command output

Field	Description
System ID	System ID of the neighbor.
Base	Minimum label value of the SRGB.
Range	Number of labels in the SRGB.

‌

Related commands

segment-routing global-block

display isis segment-routing prefix-sid-map

Use display isis segment-routing prefix-sid-map to display IS-IS SR prefix-SID mappings.

Syntax

display isis segment-routing prefix-sid-map [ active-policy | backup-policy ] [ process-id ] [ verbose ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

active-policy: Displays active prefix-SID mappings.

backup-policy: Displays inactive prefix-SID mappings.

process-id: Specifies an IS-IS process ID in the range of 1 to 65535. If you do not specify this argument, the command displays information about all IS-IS processes.

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

Usage guidelines

If you do not specify the active-policy or backup-policy keyword, the command displays information about both active and inactive prefix-SID mappings.

Examples

# Display active IS-IS SR prefix-SID mappings.

<Sysname> display isis segment-routing prefix-sid-map active-policy

ISIS 1 - Active policy

Number of mappings: 5

Prefix SID index Range Flags

2.2.2.2/32 10 10 -

3.3.3.3/32 300 1 -

8.8.8.8/32 600 20 -

11.11.11.11/32 100 10 -

12.12.12.1/32 44 3 -

# Display detailed information about active IS-IS SR prefix-SID mappings.

<Sysname> display isis segment-routing prefix-sid-map active-policy verbose

ISIS 1 - Active policy

Number of mappings: 2

Prefix 1.1.1.1 32

Source : Local

Router ID : 1010.1020.1030

Level : Not set

SID index : 100

Range : 1

Last prefix : 1.1.1.1/32

Last SID index: 100

Flags : -

Prefix 2.2.2.2 32

Source : Remote

Router ID : 1010.1020.1040

Level : L1

SID index : 200

Range : 1

Last prefix : 2.2.2.2/32

Last SID index: 200

Flags : -

# Display inactive IS-IS SR prefix-SID mappings.

<Sysname> display isis segment-routing prefix-sid-map backup-policy

ISIS 1 - Backup policy

Number of mappings: 4

Prefix SID index Range Flags

2.2.2.2/32 200 30 -

12.12.12.1/32 44 3 -

8.8.8.8/32 600 20 -

2.2.2.2/32 10 10 -

# Display all IS-IS SR prefix-SID mappings.

<Sysname> display isis segment-routing prefix-sid-map

ISIS 1 – Both active policy and backup policy

Number of mappings: 9

Prefix SID index Range Flags

2.2.2.2/32 10 10 -

2.2.2.2/32 200 30 -

3.3.3.3/32 300 1 -

8.8.8.8/32 600 20 -

11.11.11.11/32 100 10 -

12.12.12.1/32 44 3 -

Table 6 Command output

Field	Description
ISIS 1 – Active policy	Active prefix-SID mappings in IS-IS process 1.
ISIS 1 – Backup policy	Inactive prefix-SID mappings in IS-IS process 1.
ISIS 1 – Both active policy and backup policy	All prefix-SID mappings in IS-IS process 1.
SID index	Start SID index value.
Range	Number of consecutive SIDs assigned.
Flags	Mapping flags. The A flag indicates that the peer specified by the prefix is directly connected to the device. If no flags are set, this field displays a hyphen (-).
Source	Source of the prefix-SID mapping: · Local—The mapping is configured on the local device. · Remote—The mapping is configured on the remote device.
Router ID	ID of the route advertiser.
Level	Level of the route advertiser: · L1—Level-1 IS-IS route. · L2—Level-2 IS-IS route. · Not set—The route was locally advertised.

‌

display isis segment-routing routing-table

Use display isis segment-routing routing-table to display IS-IS SR routing information.

Syntax

display isis segment-routing routing-table [ vpn-instance vpn-instance-name ] [ ip ip-address { mask-length | mask } ] [ flex-algo flex-algo-id ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

vpn-instance vpn-instance-name: Specifies an MPLS L3VPN instance by its name, a case-sensitive string of 1 to 31 characters. If you do not specify an MPLS L3VPN instance, this command displays IS-IS SR routing information on the public network.

ip ip-address { mask-length | mask }: Specifies a destination IP address. The ip-address represents the network address in dotted decimal notation. The mask argument represents the network address mask. The mask-length argument represents the mask length in the range of 0 to 32. If you do not specify a destination address, this command displays IS-IS SR routing information for all destination addresses.

flex-algo flex-algo-id: Specifies a Flex-Algo by its ID, in the range of 128 to 255. If you do not specify a Flex-Algo, this command displays IS-IS SR routing information calculated by algorithm 0 (SPF algorithm).

Examples

# Display IS-IS SR routing information for all destination addresses on the public network.

<Sysname> display isis segment-routing routing-table

Segment-routing routing-table information

-----------------------------------

Flags : D-Delete C-On change list

Outlabel flags : E-Explicit-Null I-Implicit-Null

N-Normal

Total number of routes: 1

Destination: 14.159.100.2/32

Flags: -/-

SourceCount: 1

ProcessID : 1 Active : True InLabel : 17234

Pref : 3 SubProtocolID: 1 Metric : 0

Route type : Learnt OutLabel cnt : 1

NextHop : 0.0.0.0 VrfIndex : 0 Interface : XGE3/1/1

OutLabel : 17234 Selected : True OutLabel flag: E

LDPLabel : 2173

BkNextHop : 13.0.0.2 BkVrfIndex: 4 BkInterface : XGE3/1/2

BkOutLabel: 16021 BkOutLabel flag: N

BkLDPLabel: 4294967295

Table 7 Command output

Field	Description
Flags	Flags in the routing entry: · D—The routing entry has been deleted. · C—The routing entry has changed. · Hyphen (-)—The routing entry has no change.
SourceCount	Number of route advertisement sources.
ProcessID	IS-IS process ID.
Active	State of the route source: · True—The device is directly connected to the route source and has the outgoing label for the route source. · False—The device is not directly connected to the route source and does not have the outgoing label for the route source.
InLabel	Incoming label.
Pref	Route preference.
SubProtocolID	Routing subprotocol ID.
Metric	Metric of the route:
Route type	Type of the route: · Direct · Learnt · Redist (redistributed route) · Summary · Attached · Invalid
OutLabel cnt	Number of outgoing labels.
NextHop	Nexthop address.
VrfIndex	VRF index.
Interface	Brief name of the outgoing interface.
OutLabel	Outgoing label.
Selected	Whether the outgoing label for the next hop has been selected: · True · False
OutLabel flag	Flag of the outgoing label: · E—Explicit null label. The upstream neighbor of the SID node must change the SID to the explicit null label before forwarding packets to the SID node. · I—Implicit null label. The upstream neighbor of the SID node must change the SID to the implicit null label before forwarding packets to the SID node. · N—Normal label.
BkNextHop	Backup next hop address.
BkVrfIndex	Backup VRF index
BkInterface	Brief outgoing interface name.
BkOutLabel	Backup outgoing label.
BkOutLabel flag	Flag of the backup outgoing label: · E—Explicit null label. The upstream neighbor of the SID node must change the SID to the explicit null label before forwarding packets to the SID node. · I—Implicit null label. The upstream neighbor of the SID node must change the SID to the implicit null label before forwarding packets to the SID node. · N—Normal label.
BkLDPLabel	Backup LDP label.

‌

display mpls static-sr-mpls

Use display mpls static-sr-mpls to display static SRLSP and adjacency segment information.

Syntax

display mpls static-sr-mpls { lsp [ lsp-name ] | adjacency [ adjacency-path-name ] }

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

lsp: Displays static SRLSP information.

lsp-name: Specifies a static SRLSP by its name, a case-sensitive string of 1 to 67 characters. If you do not specify this argument, the command displays information about all static SRLSPs.

adjacency: Displays static adjacency segment information.

adjacency-path-name: Specifies a static adjacency segment by its name, a case-sensitive string of 1 to 67 characters. If you do not specify this argument, the command displays information about all static adjacency segments.

Examples

# Display information about all static SRLSPs.

<Sysname> display mpls static-sr-mpls lsp lsp1

Name : lsp1

Type : LSP

In-Label : -

Out-Label : 60,70,80

Out-Interface : -

Nexthop : -

State : Up

Table 8 Command output

Field	Description
Name	Name of the static SRLSP or adjacency segment.
Type	Information type: · LSP—Static SRLSP information. · Adjacency—Adjacency segment information.
In-Label	Incoming label.
Out-Label	Outgoing label.
Out-Interface	Output interface.
Nexthop	Next hop address.
State	Status of the static SRLSP or adjacency segment: · Down—The static SRLSP or adjacency segment is not available. · Up—The static SRLSP or adjacency segment is available.

‌

Related commands

static-sr-mpls adjacency

static-sr-mpls lsp

display mpls static-sr-mpls prefix

Use display mpls static-sr-mpls prefix to display static prefix segment information.

Syntax

display mpls static-sr-mpls prefix [ path lsp-name | destination ip-address [ mask | mask-length ] ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

path lsp-name: Displays static prefix segment information for the specified static SRLSP. The lsp-name argument specifies a static SRLSP by its name, a case-sensitive string of 1 to 67 characters.

destination ip-address: Displays static prefix segment information for the specified destination address. The ip-address argument specifies a destination address.

mask: Specifies the destination address mask.

mask-length: Specifies the mask length, in the range of 0 to 32.

Usage guidelines

If you do not specify any parameters, this command displays information about all static prefix segments.

Examples

# Display information about all static prefix segments.

<Sysname> display mpls static-sr-mpls prefix

Prefix Name : prefixname

Destination : 2.2.2.2/32

In-Label : 1024

Active : Yes(1)

Out-Interface : XGE3/1/1

Nexthop : 10.0.0.2

Out-Label : 600000

Status : up

Out-Interface : XGE3/1/2

Nexthop : 11.0.0.2

Out-Label : 600002

Status : down(No Route)

Out-Interface : XGE3/1/3

Nexthop : 12.0.0.2

Out-Label : 600001

Status : down(MPLS not enabled)

Table 9 Command output

Field	Description
Prefix Name	Name of the prefix segment.
Destination	Destination IP address of the prefix segment.
In-Label	Incoming label of the prefix segment.
Active	Status of the prefix segment: · Yes(count)—The prefix segment is active. The value of count represents the number of egresses in up status. · No—The prefix segment is inactive.
Out-Interface	Outgoing interface of the prefix segment.
Nexthop	Next hop of the prefix segment.
Out-Label	Outgoing label of the prefix segment.
Status	Status of the egress: · down—The egress is inactive. The cause is displayed in brackets. Possible causes include: ¡ No Route—The device does not have a route to reach the destination IP address through the outgoing interface. ¡ MPLS not enabled—MPLS is disabled on the outgoing interface. ¡ No main route—The device does not have the main route to reach the destination IP address through the outgoing interface. ¡ Static SRLSP not supported—The outgoing interface cannot be a tunnel interface that uses a static SRLSP. · up—The egress is active. · duplicate—An egress conflict has occurred because the output interface is already used by another prefix segment.

‌

Related commands

static-sr-mpls prefix

display mpls te tunnel lsp-down-info

Use display mpls te tunnel lsp-down-info to display information about the most recent five SRLSP down events for MPLS TE tunnels.

Syntax

display mpls te tunnel lsp-down-info [ tunnel number ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

tunnel number: Specifies an existing MPLS TE tunnel by the tunnel interface number. If you do not specify an MPLS TE tunnel, this command displays information about the most recent five SRLSP down events for all MPLS TE tunnels.

Examples

# Display information about the most recent five SRLSP down events for all MPLS TE tunnels.

<Sysname> display mpls te tunnel lsp-down-info

Tunnel ID : 1

Down Event Number : 1

LSP ID: 100 LSP Type: Backup

Tunnel Signaling : Segment Routing

Down Time : 2020-3-14 14:30:29.734

Down Info : No out segment

Status After Down : Tunnel went down

Down Event Number : 2

LSP ID: 100 LSP Type: Main

Tunnel Signaling : Segment Routing

Down Time : 2020-3-14 14:30:28.621

Down Info : Configuration changed

Detailed Info : mpls te bandwidth

Status After Down : Tunnel went down

Table 10 Command output

Field	Description
Down Event Number: number	Reverse ordinal number of the SRLSP down event. Events are displayed from the most recent to the oldest. The most recent event is displayed as number 1.
LSP ID	LSP ID
LSP Type	LSP type: · Main—Primary LSP. · Backup—Backup LSP.
Tunnel Signaling	Tunnel signaling protocol. The value is Segment Routing.
Down Time	Time when the SRLSP went down.
Down Info	Reason why the SRLSP went down: · No out segment. · IGP calculated path failed. · SRLG check failed. · Configuration changed. · PCE state recover.
Detailed Info	More detailed information about the down event. This field is displayed only when the Down Info value is Configuration changed to provide the key configuration commands that caused the SRLSP down event.
Status After Down	Tunnel status after the SRLSP went down: · Tunnel went down. · Main LSP MBB succeeded. · Main LSP failed, switched to backup LSP. · Backup LSP failed, hot-standby disabled. · Backup LSP MBB succeeded. · Backup LSP is same as main LSP.

‌

display mpls te tunnel lsp-event switch

Use display mpls te tunnel lsp-event switch to display information about the most recent five SRLSP path switching events for MPLS TE tunnels.

Syntax

display mpls te tunnel lsp-event switch [ tunnel number ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

tunnel number: Specifies an existing MPLS TE tunnel by the tunnel interface number. If you do not specify an MPLS TE tunnel, this command displays the most recent five SRLSP switching events for all MPLS TE tunnels.

Examples

# Display information about the most recent five SRLSP path switching events for all MPLS TE tunnels.

<Sysname> display mpls te tunnel lsp-event switch

Tunnel ID : 1

Tunnel Signaling : Static

Switch Event Number : 1

Switch Type : Backup LSP inused

Switch Reason : Main LSP down

Switch Time : 2021-8-14 14:30:29.734

Path Detail :

Old path : [15001](10.0.0.1/10.0.0.2) - [16041](4.4.4.4)

New path : [16030](3.3.3.3) - [16041](4.4.4.4)

Table 11 Command output

Field	Description
Tunnel Signaling	Tunnel signaling protocol. The value is Static or Segment Routing.
Switch Event Number: number	Reverse ordinal number of the SRLSP path switching event. Events are displayed from the most recent to the oldest. The most recent event is displayed as number 1.
Switch Type	Path switching type: · Backup LSP inused—Traffic has been switched to the backup path because the primary path failed. · Main LSP recovered—Traffic has been switched back to the primary path because the primary path recovered. · Main LSP make-before-break—Primary path MBB caused by configuration change or other reasons. · Backup LSP make-before-break—Backup path MBB caused by configuration change or other reasons.
Switch Reason	Reason why a path switching occurs: · Main LSP down. · Main LSP up. · Main LSP BFD down. · Main LSP BFD up. · Main LSP BFD deleted. · Configuration changed. · PCE updated. · PCE state recovered. · Topology recalculated.
Switch Time	Time when the SRLSP switched its path.
Path Detail	Detailed information of the path.
Old path	Path before switching, which is displayed as a stack of labels from top to bottom and the next hop address.
New path	Path after switching, which is displayed as a stack of labels from top to bottom and the next hop address.

‌

display ospf segment-routing adjacency

Use display ospf segment-routing adjacency to display OSPF SR adjacency SID information.

Syntax

display ospf [ process-id ] segment-routing adjacency [ sid sid-value ] [ vpn-instance vpn-instance-name ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

process-id: Specifies an OSPF process ID in the range of 1 to 65535. If you do not specify this argument, the command displays SR adjacency SID information about all OSPF processes.

sid sid-value: Specifies an adjacency SID in the range of 1024 to 1010152. If you do not specify an adjacency SID, this command displays information about all OSPF SR adjacency SIDs.

vpn-instance vpn-instance-name: Specifies an MPLS L3VPN instance by its name, a case-sensitive string of 1 to 31 characters. If you do not specify an MPLS L3VPN instance, this command displays SR adjacency SID information on the public network.

Examples

# Display SR adjacency SID information about OSPF process 1.

<Sysname> display ospf 1 segment-routing adjacency

Adjacency SID: 15040 Type: Non-member-port Request result: Init

NbrID Interface NextHop State ProcessID

2.2.2.2 XGE3/1/1 10.1.1.1 Inactive 1

Table 12 Command output

Field	Description
Adjacency SID	Adjacency SID value.
Type	‌ Type of the adjacency SID assigned to the adjacency link: · Non-member-port—Adjacency SID assigned to a Layer 3 Ethernet interface that is not an aggregation group member interface. · Member-port—Adjacency SID assigned to a Layer 3 aggregation group member interface.
Request result	Adjacency SID application result: · Succeeded—The application succeeded. · Conflicting—The adjacency SID is already used. · Init—The application is in progress or the adjacency SID allocation feature is not enabled. · Out-of-range—The adjacency SID is not the in the range of the SRLB.
NbrID	ID of the neighbor.
Interface	Interface connected to the neighbor.
NextHop	Next hop of the adjacency SID.
State	SID status: · Active—The SID is effective and is available for use. · Inactive—The SID is not effective and is not available for use.
ProcessID	OSPF process ID.

‌

display ospf segment-routing global-block

Use display ospf segment-routing global-block to display OSPF SRGB information.

Syntax

display ospf [ process-id ] [ area area-id ] segment-routing global-block

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

process-id: Specifies an OSPF process ID in the range of 1 to 65535. If you do not specify this argument, the command displays the SRGBs of all OSPF processes.

area area-id: Specifies an area by its ID. The area ID can be a value in dotted decimal notation or a decimal value in the range of 0 to 4294967295. If you specify a decimal value, the system automatically transforms it to a value in dotted decimal notation. If you do not specify this option, the command displays the SRGBs of all areas.

Examples

# Display the SRGBs of all OSPF processes.

<Sysname> display ospf segment-routing global-block

OSPF Process 1 with Router ID 1.1.1.1

Segment Routing Global Block

Area: 0.0.0.0

Router ID Min SID Max SID Total

1.1.1.1 16000 24000 8001

2.2.2.2 18000 18999 1000

3.3.3.3 16000 24000 8001

4.4.4.4 17000 17999 1000

5.5.5.5 16000 16999 1000

Table 13 Command output

Field	Description
Router ID	Router ID of the device or the neighbor.
Min SID	Minimum label value of the SRGB.
Max SID	Maximum label value of the SRGB.
Total	Number of labels in the SRGB.

‌

Related commands

segment-routing global-block

display ospf segment-routing prefix-sid-map

Use display ospf segment-routing prefix-sid-map to display OSPF SR prefix-SID mappings.

Syntax

display ospf segment-routing prefix-sid-map [ active-policy | backup-policy ] [ process-id ] [ verbose ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

active-policy: Displays active prefix-SID mappings.

backup-policy: Displays inactive prefix-SID mappings.

process-id: Specifies an OSPF process ID in the range of 1 to 65535. If you do not specify this argument, the command displays information about all OSPF processes.

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

Usage guidelines

If you do not specify the active-policy or backup-policy keyword, the command displays information about both active and inactive prefix-SID mappings.

Examples

# Display active OSPF SR prefix-SID mappings.

<Sysname> display ospf segment-routing prefix-sid-map active-policy

OSPF 1 - Active policy

Flags: IA - Inter-Area, L – Local, R - Remote

Number of mappings: 2

Prefix SID index Range Flags

1.1.1.11/32 10 10 L/-

1.1.1.22/32 20 20 R/-

# Display detailed information about active OSPF SR prefix-SID mappings.

<Sysname> display ospf segment-routing prefix-sid-map active-policy verbose

OSPF 1 - Active policy

Number of mappings: 2

Prefix 1.1.1.11

Source : Local

Router ID : 10.1.1.1

Area ID : Not set

LS ID : Not set

SID index : 10

Range : 10

Last prefix : 1.1.1.20

Last SID index: 19

Flags : -

Prefix 1.1.1.22

Source : Remote

Router ID : 10.2.1.1

Area ID : 0.0.0.1

LS ID : 7.0.0.0

SID index : 20

Range : 20

Last prefix : 1.1.1.41

Last SID index: 39

Flags : -

# Display inactive OSPF SR prefix-SID mappings.

<Sysname> display ospf segment-routing prefix-sid-map backup-policy

OSPF 1 - Backup policy

Flags: IA - Inter-Area, L – Local, R - Remote

Number of mappings: 1

Prefix SID index Range Flags

1.1.1.33/32 30 30 R/IA

# Display all OSPF SR prefix-SID mappings.

<Sysname> display ospf segment-routing prefix-sid-map

OSPF 1 - Both active policy and backup policy

Flags: IA - Inter-Area, L – Local, R - Remote

Number of mappings: 3

Prefix SID index Range Flags

1.1.1.11/32 10 10 L/-

1.1.1.22/32 20 20 R/-

1.1.1.33/32 30 30 R/IA

Table 14 Command output

Field	Description
OSPF 1 – Active policy	Active prefix-SID mappings in OSPF process 1.
OSPF 1 – Backup policy	Inactive prefix-SID mappings in OSPF process 1.
OSPF 1 – Both active policy and backup policy	All prefix-SID mappings in OSPF process 1.
SID index	Start SID index value.
Range	Number of consecutive SIDs assigned.
Flags	Mapping flags: · IA—The prefix was from another area. · L—The mapping is a local mapping. · R—The mapping is a remote mapping. If no flags are set, this field displays a hyphen (-).
Source	Source of the prefix-SID mapping: · Local—The mapping is configured on the local device. · Remote—The mapping is configured on the remote device.
Router ID	ID of the route advertiser.
Area ID	Area ID. If the mapping is a local mapping, this field displays Not set.
LS ID	Link state ID. If the mapping is a local mapping, this field displays Not set.

‌

display ospf segment-routing routing-table

Use display ospf segment-routing routing-table to display OSPF SR routing information.

Syntax

display ospf segment-routing routing-table [ vpn-instance vpn-instance-name ] [ ip ip-address { mask-length | mask } ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

ip ip-address { mask-length | mask }: Specifies a destination IP address. The ip-address represents the network address in dotted decimal notation. The mask argument represents the network address mask. The mask-length argument represents the mask length in the range of 0 to 32. If you do not specify a destination address, this command displays OSPF SR routing information for all destination addresses.

Examples

# Display OSPF SR routing information for all destination addresses on the public network.

<Sysname> display ospf segment-routing routing-table

Segment-routing routing-table information

-----------------------------------

Flags : D-Delete C-On change list

Outlabel flags : E-Explicit-Null I-Implicit-Null

N-Normal P-SR label prefer

Total number of routes: 1

Destination: 1.1.1.1/32

Flags: -/-/-

SrouceCount: 1

ProcessID : 1 Active : True InLabel : 18555

Pref : 10 SubProtocolID: 1 Metric : 1

Route type : Stub OutLabel cnt : 1

NextHop : 12.0.0.2 VrfIndex : 1 Interface : XGE3/1/1

OutLabel : 17555 Selected : True OutLabel flag : I

LDPLabel : 4294967295

BkNextHop : 13.0.0.2 BkVrfIndex : 4 BkInterface : XGE3/1/2

BkOutLabel: 16021 BkOutLabel flag: N

BkLDPLabel: 4294967295

Table 15 Command output

Field	Description
Flags	Flags in the routing entry: · D—The routing entry has been deleted. · C—The routing entry has changed. · Hyphen (-)—The routing entry has no change.
SourceCount	Number of route advertisement sources.
ProcessID	OSPF process ID.
Active	State of the route source: · True—The device is directly connected to the route source and has the outgoing label for the route source. · False—The device is not directly connected to the route source and does not have the outgoing label for the route source.
InLabel	Incoming label.
Pref	Route preference.
SubProtocolID	Routing subprotocol ID.
Metric	Metric of the route:
Route type	Type of the route: · Transit · Stub · Inter · Type1 · Type2
OutLabel cnt	Number of outgoing labels.
NextHop	Nexthop address.
VrfIndex	VRF index.
Interface	Brief name of the outgoing interface.
OutLabel	Outgoing label.
Selected	Whether the outgoing label for the next hop has been selected: · True · False
OutLabel flag	Flag of the outgoing label: · E—Explicit null label. The upstream neighbor of the SID node must change the SID to the explicit null label before forwarding packets to the SID node. · I—Implicit null label. The upstream neighbor of the SID node must change the SID to the implicit null label before forwarding packets to the SID node. · N—Normal label. · P—SR label preferred.
LDPLabel	LDP label.
BkNextHop	Backup next hop address.
BkVrfIndex	Backup VRF index
BkInterface	Brief outgoing interface name.
BkOutLabel	Backup outgoing label.
BkOutLabel flag	Flag of the backup outgoing label: · E—Explicit null label. The upstream neighbor of the SID node must change the SID to the explicit null label before forwarding packets to the SID node. · I—Implicit null label. The upstream neighbor of the SID node must change the SID to the implicit null label before forwarding packets to the SID node. · N—Normal label. · P—SR label preferred.
BkLDPLabel	Backup LDP outgoing label.

‌

display segment-routing label-block

Use display segment-routing label-block to display SR label block information.

Syntax

display segment-routing label-block [ protocol { isis | ospf } ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

protocol: Specifies a protocol. If you do not specify this keyword, the command displays SR label block information about all protocols.

isis: Displays IS-IS SR label block information.

ospf: Displays OSPF SR label block information.

Examples

# Display SR label block information about all protocols.

<Sysname> display segment-routing label-block

Default label block:

SRLB: 15000-15999

SRGB: 16000-55999

Configurate label block:

SRLB: 200000-210000

SRGB: 16000-17000

Type Protocol Process-ID Label range State

SRLB Global - 200000-210000 Active

SRGB Global - 16000-17000 Active

Table 16 Command output

Field	Description
Type	Label block type, SRGB or SRLB.
Protocol	Protocol to which the label block belongs: · ISIS—A IS-IS process. · OSPF—An OSPF process. · Global—The label block is the global SRGB or SRLB, which is configured in segment routing view..
Process-ID	ID of the protocol process that owns the label block. If label block is the global SRGB or SRLB, this field displays a hyphen (-).
State	Whether the label block is available for use: · Active—The label block is available for use. · Inactive—The label block is not available for use.

‌

display segment-routing mapping-server prefix-sid-map

Use display segment-routing mapping-server prefix-sid-map to display prefix-SID mappings.

Syntax

display segment-routing mapping-server prefix-sid-map [ ip-address mask-length | verbose ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

ip-address: Specifies an IPv4 address prefix in dotted decimal notation.

mask-length: Specifies the mask length, in the range of 1 to 32.

verbose: Displays detailed information about all configured prefix-SID mappings.

Usage guidelines

If you do not specify any parameters, this command displays brief information about all configured prefix-SID mappings.

Examples

# Display the prefix-SID mapping for prefix 1.1.1.1.

<Sysname> display segment-routing mapping-server prefix-sid-map 1.1.1.1 32

SRMS mappings

Prefix SID index Flags

1.1.1.1/32 10 A

# Display all configured prefix-SID mappings.

<Sysname> display segment-routing mapping-server prefix-sid-map

SRMS mappings

Number of mappings: 2

Prefix SID index Range Flags

1.1.1.1/32 10 100 A

2.2.2.2/32 256 520 -

# Display detailed information about all configured prefix-SID mappings.

<Sysname> display segment-routing mapping-server prefix-sid-map verbose

SRMS mappings

Number of mappings: 2

Prefix 1.1.1.1/32

SID index : 10

Range : 100

Last prefix : 1.1.1.100/24

Last SID index: 109

Flags : A

Prefix 2.2.2.2/32

SID index : 256

Range : 520

Last prefix : 2.2.4.9/24

Last SID index: 775

Flags : -

Table 17 Command output

Field	Description
SID index	Start SID index value.
Range	Number of consecutive SIDs assigned.
Flags	Mapping flags. The A flag indicates that the peer specified by the prefix is directly connected to the device. If no flags are set, this field displays a hyphen (-).
Last Prefix	Final prefix.
Last SID index	SID assigned to the final prefix.

‌

egress-engineering label delete-delay

Use egress-engineering label delete-delay to configure a deletion delay for dynamic SIDs.

Use undo egress-engineering label delete-delay to restore the default.

Syntax

egress-engineering label delete-delay time-value

undo egress-engineering label delete-delay

Default

The dynamic SID deletion delay time is 1800 seconds.

Views

BGP instance view

Predefined user roles

network-admin

Parameters

time-value: Specifies the deletion delay time, in the range of 0 to 3600 seconds. A value of 0 means no delay and the device deletes the SRv6 SIDs allocated by BGP immediately after the BGP session is down.

Usage guidelines

Application scenarios

To make sure BGP allocates the same SRv6 SID before and after a BGP session down-up event, use this command to set a proper dynamic SID deletion delay.

Operating mechanism

With this feature configured, the device does not delete the BGP-allocated SRv6 SID when the BGP session is down before the delay timer expires.

· If the BGP session becomes up before the delay timer expires, the original SRv6 SID is used.

· If the BGP session is down after the delay timer expires, the BGP-allocated SRv6 SID is deleted.

Restrictions and guidelines

If an active/standby MPU switchover occurs before the delay timer expires, the device does not delete the dynamically allocated SRv6 SIDs when the neighbors are disconnected and deletes them until after the timer expires.

If you delete the BGP configuration actively, the device immediately deletes the SRv6 SIDs dynamically allocated by BGP without a delay.

Examples

# Configure the dynamic SID deletion delay time as 120 seconds.

<Sysname> system-view

[Sysname] bgp 100

[Sysname-bgp-default] egress-engineering label delete-delay 120

Related commands

peer egress-engineering

egress-engineering link-delay

Use egress-engineering link-delay to configure the link delay information to be reported by BGP to the controller.

Use undo egress-engineering link-delay to restore the default.

Syntax

egress-engineering link-delay { average average-delay-value | min min-delay-value max max-delay-value | variation variation-value } * interface interface-type interface-number

undo egress-engineering link-delay { average | min | variation } * interface interface-type interface-number

Default

No link delay information is configured.

Views

BGP instance view

Predefined user roles

network-admin

Parameters

average average-delay-value: Specifies the average delay time of the interface, in the range of 1 to 16777215, in microseconds. The average delay is the average value of all delays for the IP data packets sent from the local interface to the BGP neighbor. If you do not specify this option, BGP uses the average delay advertised by the interface.

min min-delay-value max max-delay-value: Specifies the minimum and maximum delay time of the interface, in the range of 1 to 16777215, in microseconds. The minimum and maximum delays are the minimum and maximum delays among all delays for the IP data packets sent from the local interface to the BGP neighbor. If you do not specify this option, BGP uses the minimum and maximum delays advertised by the interface.

variation variation-value: Specifies the delay variation of the interface, in the range of 1 to 16777215, in microseconds. The delay variation refers to the difference between average delays. If you do not specify this option, BGP uses the delay variation advertised by the interface.

interface interface-type interface-number: Specifies the interface to be configured with the delay information. Only physical interfaces are supported.

Usage guidelines

BGP can obtain delay information of interfaces in the following methods:

· Static configuration—Use this command to configure the interface delay information for BGP.

· Dynamic obtaining—Use the test-session bind interface command to bind a TWAMP-light test session to an interface. TWAMP-light sends the collected delay information to the bound interface, which then reports the delay information to BGP.

If BGP obtains delay information in both methods, it uses the statically configured delay information.

If you execute this command multiple times for the same interface, the most recent configuration for each delay parameter takes effect.

The minimum delay value must be smaller than the maximum delay value.

Examples

# Configure the average delay, minimum delay, maximum delay, and delay variation of interface Ten-GigabitEthernet 3/1/1 as 100, 10, 1000, and 20 microseconds, respectively.

<Sysname> system-view

[Sysname] bgp 100

[Sysname-bgp-default] egress-engineering link-delay average 100 min 10 max 1000 variation 20 interface ten-gigabitethernet 3/1/1

Related commands

test-session bind interface (Network Management and Monitoring Command Reference)

egress-engineering link-loss

Use egress-engineering link-loss to configure the packet loss rate for a BGP-EPE interface.

Use undo egress-engineering link-loss to restore the default.

Syntax

egress-engineering link-loss loss-value interface interface-type interface-number

undo egress-engineering link-loss interface interface-type interface-number

Default

No packet loss rate is configured for a BGP-EPE interface.

Views

BGP instance view

Predefined user roles

network-admin

Parameters

loss-value: Specifies the packet loss rate of the interface, in the range of 0 to 16777214, in a unit of 0.000003%.

interface interface-type interface-number: Specifies the interface to be configured with the packet loss rate. Only physical interfaces are supported.

Usage guidelines

BGP can obtain packet loss information of BGP-EPE interfaces in the following methods:

· Static configuration—Use this command to configure the packet loss rate for a BGP-EPE interface.

· Dynamic obtaining—Use the test-session bind interface command to bind a TWAMP-light test session to an interface. TWAMP-light sends the collected packet loss rate to the bound interface, which then reports the packet loss rate to BGP. For more information about TWAMP-light, see NQA TWAMP-light configuration in Network Management and Monitoring Configuration Guide.

If BGP obtains packet loss information in both methods, it uses the statically configured packet loss rate.

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

Examples

# Configure the packet loss rate of interface Ten-GigabitEthernet 3/1/1 as 1000*0.000003%.

<Sysname> system-view

[Sysname] bgp 100

[Sysname-bgp-default] egress-engineering link-loss 1000 interface ten-gigabitethernet 3/1/1

egress-engineering metric-bandwidth advertisement enable

Use egress-engineering metric-bandwidth advertisement enable to enable bandwidth advertisement.

Use undo egress-engineering metric-bandwidth advertisement enable to disable bandwidth advertisement.

Syntax

egress-engineering metric-bandwidth advertisement enable

undo egress-engineering metric-bandwidth advertisement enable

Default

Bandwidth advertisement is disabled.

Views

BGP instance view

Predefined user roles

network-admin

Usage guidelines

In scenarios where BGP-LS reports link states to a controller for path computation, configure this feature on BGP-EPE devices to enable BGP to collect and propagate intra-AS link bandwidth information and report the information to the controller through BGP-LS. The controller then uses the bandwidth information to compute paths to ensure that the optimal path has the most bandwidth.

Examples

# Enable bandwidth advertisement for a BGP instance.

<Sysname> system-view

[Sysname] bgp 100

[Sysname-bgp-default] egress-engineering metric-bandwidth advertisement enable

egress-engineering metric-bandwidth suppression

Use egress-engineering metric-bandwidth suppression to enable bandwidth advertisement suppression for BGP and set the suppression parameters.

Use undo egress-engineering metric-bandwidth suppression to disable bandwidth advertisement suppression for BGP.

Syntax

egress-engineering metric-bandwidth suppression timer time-value

undo egress-engineering metric-bandwidth suppression

Default

Bandwidth advertisement suppression of BGP is enabled, and the bandwidth advertisement suppression timer is 120 seconds.

Views

BGP instance view

Predefined user roles

network-admin

Parameters

timer time-value: Sets the bandwidth advertisement suppression timer, in the range of 0 to 600 seconds. A value of 0 means to disable bandwidth advertisement suppression.

Usage guidelines

When bandwidth changes frequently, BGP will frequently process, advertise, and report the bandwidth information, occupying too many device resources. To resolve this issue, you can enable the bandwidth advertisement suppression feature.

After this feature is enabled, interfaces report bandwidth information to BGP at intervals of the bandwidth advertisement suppression time. BGP advertises and reports bandwidth information at intervals of the bandwidth advertisement suppression time. It cannot advertise or report bandwidth information before the suppression timer expires.

This command takes effect only after the egress-engineering metric-bandwidth advertisement enable command is enabled.

Examples

# Enable bandwidth advertisement suppression and set the suppression timer to 100 seconds.

<Sysname> system-view

[Sysname] bgp 100

[Sysname-bgp-default] egress-engineering metric-bandwidth suppression timer 100

Related commands

egress-engineering metric-bandwidth advertisement enable

egress-engineering metric-delay advertisement enable

Use egress-engineering metric-delay advertisement enable to enable delay advertisement for BGP.

Use undo egress-engineering metric-delay advertisement enable to disable delay advertisement for BGP.

Syntax

egress-engineering metric-delay advertisement enable

undo egress-engineering metric-delay advertisement enable

Default

Delay advertisement is disabled.

Views

BGP instance view

Predefined user roles

network-admin

Usage guidelines

In scenarios where BGP-LS reports link states to a controller for path computation, configure this feature on BGP-EPE devices to enable BGP to collect and propagate intra-AS link delay information and report the information to the controller through BGP-LS. The controller then uses the delay information to compute paths to ensure that the optimal path has the least delay.

Examples

# Enable delay advertisement in a BGP instance.

<Sysname> system-view

[Sysname] bgp 100

[Sysname-bgp-default] egress-engineering metric-delay advertisement enable

egress-engineering metric-delay suppression

Use egress-engineering metric-delay suppression to enable delay advertisement suppression for BGP and set the suppression parameters.

Use undo egress-engineering metric-delay suppression to disable delay advertisement suppression for BGP.

Syntax

egress-engineering metric-delay suppression timer time-value percent-threshold percent-value absolute-threshold absolute-value

undo egress-engineering metric-delay suppression

Default

Delay advertisement suppression is enabled, and the suppression timer is 120 seconds, the delay change percentage threshold is 10%, and the delay change absolute value threshold is 1000 microseconds.

Views

BGP instance view

Predefined user roles

network-admin

Parameters

timer time-value: Specifies the delay advertisement suppression timer, in the range of 0 to 600 seconds. A value of 0 means to disable delay advertisement suppression.

percent-threshold percent-value: Specifies the delay change percentage threshold, in the range of 0 to 100. A value of 0 means not to concern the delay change percentage during suppression.

absolute-threshold absolute-value: Specifies the delay change absolute value threshold, in the range of 0 to 10000. A value of 0 means not to concern the delay change absolute value during suppression.

Usage guidelines

When delay changes frequently, BGP will frequently process, advertise, and report the delay information, occupying too many device resources. To resolve this issue, you can enable the delay advertisement suppression feature.

Delay advertisement suppression operates as follows:

1. After this feature is enabled, interfaces report delay information to BGP at intervals of the delay advertisement suppression time.

2. BGP advertises and reports delay information at intervals of the delay advertisement suppression time. It cannot advertise or report delay information before the suppression timer expires except in the following cases:

¡ If the percentage of the change between two consecutive delays reported by an interface reaches or exceeds the threshold set by percent-value, BGP advertises and reports the delay information regardless of whether the suppression timer has expired or not.

¡ If the absolute value of change between two consecutive delays reported by an interface reaches or exceeds the threshold set by absolute-value, BGP advertises and reports the delay information regardless of whether the suppression timer has expired or not.

This command takes effect only after the egress-engineering metric-delay advertisement enable command is enabled.

If a suppression parameter is set to 0, the corresponding suppression function is disabled. If all the suppression parameters are set to 0, the entire delay advertisement suppression feature is disabled.

Examples

# Enable delay advertisement suppression for BGP, set the suppression timer to 100 seconds, the delay change percentage threshold to 50%, and delay change absolute value threshold to 200 microseconds.

<Sysname> system-view

[Sysname] bgp 100

[Sysname-bgp-default] egress-engineering metric-delay suppression timer 100 percent-threshold 50 absolute-threshold 200

Related commands

egress-engineering metric-delay advertisement enable

egress-engineering metric-link-loss advertisement enable

Use egress-engineering metric-link-loss advertisement enable to enable packet loss rate advertisement for BGP-EPE.

Use undo egress-engineering metric-link-loss advertisement enable to disable packet loss rate advertisement for BGP-EPE.

Syntax

egress-engineering metric-link-loss advertisement enable

undo egress-engineering metric-link-loss advertisement enable

Default

Packet loss rate advertisement is disabled for BGP-EPE.

Views

BGP instance view

Predefined user roles

network-admin

Usage guidelines

BGP can obtain packet loss information of BGP-EPE interfaces in the following methods:

· Static configuration—Use the egress-engineering link-loss command to configure the packet loss rate for a BGP-EPE interface.

In scenarios where BGP-LS reports link states to a controller for path computation, configure the packet loss rate advertisement feature on BGP-EPE devices. Then, BGP can collect packet loss information locally and from the BGP-EPE neighbors and report the information to the controller through BGP-LS. The controller then uses the packet loss information to compute paths to ensure that the optimal path has the smallest packet loss rate.

NQA can collect packet loss rate statistics only from physical interfaces. As a best practice, use directly connected physical interfaces to establish BGP-EPE neighbor relationships to avoid packet loss rate collection failure.

Examples

# Enable packet loss rate advertisement in a BGP instance.

<Sysname> system-view

[Sysname] bgp 100

[Sysname-bgp-default] egress-engineering metric-link-loss advertisement enable

Related commands

egress-engineering link-delay advertisement enable

egress-engineering link-loss

egress-engineering metric-link-loss suppression

test-session bind interface (Network Management and Monitoring Command Reference)

egress-engineering metric-link-loss suppression

Use egress-engineering metric-link-loss suppression to enable packet loss rate advertisement suppression for BGP-EPE and set the suppression parameters.

Use undo egress-engineering metric-link-loss suppression to disable packet loss rate advertisement suppression for BGP-EPE.

Syntax

egress-engineering metric-link-loss suppression timer time-value percent-threshold percent-value absolute-threshold absolute-value

undo egress-engineering metric-link-loss suppression

Default

Packet loss rate advertisement suppression is enabled. The suppression timer is 120 seconds. The percentage threshold of the packet loss rate change is 10%. The absolute value threshold of the packet loss rate change is 0.01%.

Views

BGP instance view

Predefined user roles

network-admin

Parameters

timer time-value: Specifies the packet loss rate advertisement suppression timer, in the range of 0 to 600 seconds. A value of 0 means to disable packet loss rate advertisement suppression.

percent-threshold percent-value: Specifies the packet loss rate change percentage threshold, in the range of 0 to 100. A value of 0 means not to concern the packet loss rate change percentage during suppression. The packet loss rate change percentage = the absolute value of the difference between two consecutive packet loss rates / previous packet loss rate.

absolute-threshold absolute-value: Specifies the packet loss rate change absolute value threshold, in the range of 0 to 10000, in a unit of 0.00001%. A value of 0 means not to concern the packet loss rate change absolute value during suppression. The packet loss rate change absolute value is the absolute value of the difference between two consecutive packet loss rates.

Usage guidelines

When packet loss rate changes frequently, BGP will frequently process, advertise, and report the packet loss rate information, occupying too many device resources. To resolve this issue, you can enable the packet loss rate advertisement suppression feature.

Packet loss rate advertisement suppression operates as follows:

1. After this feature is enabled, interfaces report packet loss rate information to BGP at intervals of the packet loss rate advertisement suppression time.

2. BGP advertises and reports packet loss rate information at intervals of the packet loss rate advertisement suppression time. It cannot advertise or report packet loss rate information before the suppression timer expires except in the following cases:

¡ If the percentage of the change between two consecutive packet loss rates reported by an interface reaches or exceeds the threshold set by percent-value, BGP advertises and reports the packet loss rate information regardless of whether the suppression timer has expired or not.

¡ If the absolute value of the change between two consecutive packet loss rates reported by an interface reaches or exceeds the threshold set by absolute-value, BGP advertises and reports the packet loss rate information regardless of whether the suppression timer has expired or not.

This command takes effect only after the egress-engineering metric-link-loss advertisement enable command is enabled.

If a suppression parameter is set to 0, the corresponding suppression function is disabled. If all the suppression parameters are set to 0, the entire packet loss rate advertisement suppression feature is disabled.

If you execute both the egress-engineering metric-link-loss suppression command and the egress-engineering metric-delay suppression command, NQA uses the smaller value of the suppression timers set by the two commands as the time interval for advertising packet loss rate and delay information.

As a best practice, set the packet loss rate advertisement suppression timer greater than or equal to the NQA TWAMP-light packet loss rate test interval. For more information about TWAMP-light, see NQA TWAMP-light configuration in Network Management and Monitoring Configuration Guide.

Examples

# Enable packet loss rate advertisement suppression for BGP-EPE, set the suppression timer to 300 seconds, the percentage threshold of the packet loss rate change to 20%, and the absolute value threshold of the packet loss rate change to 0.02%.

<Sysname> system-view

[Sysname] bgp 100

[Sysname-bgp-default] egress-engineering metric-link-loss suppression timer 300 percent-threshold 20 absolute-threshold 2000

Related commands

egress-engineering metric-delay suppression

egress-engineering metric-link-loss advertisement enable

egress-engineering peer-set

Use egress-engineering peer-set to create a BGP-EPE peer set.

Use undo egress-engineering peer-set to delete a BGP-EPE peer set.

Syntax

egress-engineering peer-set peer-set-name [ label label-value ]

undo egress-engineering peer-set peer-set-name

Default

No BGP-EPE peer sets exist.

Views

BGP instance view

Predefined user roles

network-admin

Parameters

peer-set-name: Specifies a BGP-EPE peer set name, a case-sensitive string of 1 to 63 characters.

label label-value: Specifies a SID for the BGP EPE peer set. The value range for the label-value argument is 16 to 1010152. If you do not specify a SID, this command dynamically assigns a SID for the BGP EPE peer set.

Usage guidelines

BGP-EPE assigns BGP peering SIDs to segments across ASs. The device sends BGP peering SIDs to the controller through BGP-LS extensions. The controller orchestrates IGP SIDs and BGP peering SIDs for inter-AS forwarding over optimal paths.

You can add multiple BGP peers into a BGP-EPE peer set and assign a PeerSet SID to the set. A PeerSet SID corresponds to multiple outgoing interfaces.

Before assigning BGP-EPE SIDs, execute the display mpls label command to display the usage status of the labels that you want to assign as BGP-EPE SIDs. Make sure the labels are in Idle state. A label that is not in Idle state is being used by another protocol. If you assign it to a peer or peer group as a BGP-EPE SID, the BGP-EPE SID is not available even if the status of the label changes to Idle later. To use the BGP-EPE SID, you must remove the BGP-EPE SID assignment and assign the BGP-EPE SID again.

Examples

# Create a BGP-EPE peer set named bgpepe, and assign SID 5555 to the set.

<Sysname> system-view

[Sysname] bgp 100

[Sysname-bgp-default] egress-engineering peer-set bgpepe label 5555

Related commands

display mpls label

peer egress-engineering

peer peer-set

fast-reroute microloop-avoidance enable

Use fast-reroute microloop-avoidance enable to enable FRR microloop avoidance.

Use undo fast-reroute microloop-avoidance enable to disable FRR microloop avoidance.

Syntax

In IS-IS IPv4 unicast address family view:

fast-reroute microloop-avoidance enable [ level-1 | level-2 ]

undo fast-reroute microloop-avoidance enable [ level-1 | level-2 ]

In OSPF view:

fast-reroute microloop-avoidance enable

undo fast-reroute microloop-avoidance enable

Default

FRR microloop avoidance is disabled.

Views

IS-IS IPv4 unicast address family view

OSPF view

Predefined user roles

network-admin

Parameters

level-1: Specifies FRR microloop avoidance for IS-IS Level-1.

level-2: Specifies FRR microloop avoidance for IS-IS Level-2.

Usage guidelines

Use this command only on the source node.

On a network configured with TI-LFA FRR, if a node or link fails, traffic will be switched to the backup path calculated by TI-LFA. However, if a device along the backup path has not finished route convergence, traffic might be looped between the device and the source node. The source node is the node prior to the node or link that failed. The loop will exist until the device finishes route convergence.

To resolve this issue, configure microloop avoidance on the source node enabled with TI-LFA FRR. Then, when a node or link on the optimal path fails, traffic will be switched to the backup path calculated by TI-LFA. The source node starts a delay timer for other devices to finish route convergence. After the delay timer expires, the source node installs the converged path to the FIB and switches traffic from the TI-LFA-calculated backup path to the converged path.

If you configure both FRR microloop avoidance and SR microloop avoidance, both timers are started and FRR microloop avoidance takes effect.

· The value of the delay timer of FRR microloop avoidance is greater than or equal to the value of the delay timer of SR microloop avoidance, the device switches to the converged path immediately after the delay timer of the latter expires.

· The value of the delay timer of FRR microloop avoidance is smaller than or equal to the value of the delay timer of SR microloop avoidance, the device switches to the converged path after the delay timer of the former expires.

If you do not specify the level-1 or level-2 keyword, the command enables or disables FRR microloop avoidance on all IS-IS levels.

Examples

# Enable FRR microloop avoidance for IS-IS process 1.

<Sysname> system-view

[Sysname] isis 1

[Sysname-isis-1] address-family ipv4

[Sysname-isis-1-ipv4] fast-reroute microloop-avoidance enable

# Enable FRR microloop avoidance for OSPF process 1.

<Sysname> system-view

[Sysname] ospf 1

[Sysname-ospf-1] fast-reroute microloop-avoidance enable

Related commands

fast-reroute microloop-avoidance rib-update-delay

segment-routing microloop-avoidance enable

fast-reroute microloop-avoidance rib-update-delay

Use fast-reroute microloop-avoidance rib-update-delay to set the FRR microloop avoidance RIB-update-delay time.

Use undo fast-reroute microloop-avoidance rib-update-delay to restore the default.

Syntax

In IS-IS IPv4 unicast address family view:

fast-reroute microloop-avoidance rib-update-delay delay-time [ level-1 | level-2 ]

undo fast-reroute microloop-avoidance rib-update-delay [ level-1 | level-2 ]

In OSPF view:

fast-reroute microloop-avoidance rib-update-delay delay-time

undo fast-reroute microloop-avoidance rib-update-delay

Default

The FRR microloop avoidance RIB-update-delay time is 5000 ms.

Views

IS-IS IPv4 unicast address family view

OSPF view

Predefined user roles

network-admin

Parameters

delay-time: Specifies the FRR microloop avoidance RIB-update-delay time in milliseconds. The value range is 1 to 60000.

level-1: Specifies the FRR microloop avoidance RIB-update-delay time for IS-IS Level-1.

level-2: Specifies the FRR microloop avoidance RIB-update-delay time for IS-IS Level-2.

Usage guidelines

Use this command only on the source node.

If you do not specify the level-1 or level-2 keyword, the command sets the FRR microloop avoidance RIB-update-delay time for all IS-IS levels.

Examples

# Set the FRR microloop avoidance RIB-update-delay time to 6000 ms for Level-1 of IS-IS process 1.

<Sysname> system-view

[Sysname] isis 1

[Sysname-isis-1] address-family ipv4

[Sysname-isis-1-ipv4] fast-reroute microloop-avoidance rib-update-delay 6000 level-1

# Set the FRR microloop avoidance RIB-update-delay time to 6000 ms for OSPF process 1.

<Sysname> system-view

[Sysname] ospf 1

[Sysname-ospf-1] fast-reroute microloop-avoidance rib-update-delay 6000

Related commands

fast-reroute microloop-avoidance

fast-reroute ti-lfa

Use fast-reroute ti-lfa to enable Topology-Independent Loop-Free Alternate Fast Re-Route (TI-LFA FRR).

Use fast-reroute ti-lfa to disable TI-LFA FRR.

Syntax

In IS-IS IPv4 unicast address family view:

fast-reroute ti-lfa [ per-prefix ] [ route-policy route-policy-name | host ] [ level-1 | level-2 ]

undo fast-reroute ti-lfa [ level-1 | level-2 ]

In OSPF view:

fast-reroute ti-lfa [ per-prefix ] [ route-policy route-policy-name | host ]

undo fast-reroute ti-lfa

Default

TI-LFA FRR is disabled.

Views

IS-IS IPv4 unicast address family view

OSPF view

Predefined user roles

network-admin

Parameters

level-1: Specifies TI-LFA FRR for IS-IS Level-1.

level-2: Specifies TI-LFA FRR for IS-IS Level-2.

per-prefix: Calculates backup information for each advertising source of a route. Specify this keyword only if routes are advertised by multiple sources. If you do not specify this keyword, the device calculates backup information for each route.

route-policy route-policy-name: Enables TI-LFA FRR for prefixes identified by the routing policy. The route-policy-name argument specifies a routing policy by its name, a case-sensitive string of 1 to 63 characters.

host: Enables TI-LFA for host routes.

Usage guidelines

TI-LFA FRR provides link and node protection for SR tunnels. When a link or node fails, TI-LFA FRR switches the traffic to the backup path to ensure continuous data forwarding.

Before configuring TI-LFA FRR, you must execute the following commands in IS-IS IPv4 unicast address family view or OSPF view:

· segment-routing mpls

· fast-reroute lfa

TI-LFA FRR takes effect only after you enable LFA FRR.

TI-LFA FRR operates in a level only after you enable LFA FRR for the level.

If you do not specify the level-1 or level-2 keyword, the command enables or disables TI-LFA FRR for all IS-IS levels.

If you do not specify the route-policy route-policy-name option or the host keyword, the device calculates backup information for all routes.

Examples

# Enable TI-LFA FRR for IS-IS process 1.

<Sysname> system-view

[Sysname] isis 1

[Sysname-isis-1] address-family ipv4

[Sysname-isis-1-ipv4] fast-reroute ti-lfa

# Enable TI-LFA FRR for OSPF process 1.

<Sysname> system-view

[Sysname] ospf 1

[Sysname-ospf-1] fast-reroute ti-lfa

Related commands

fast-reroute (Layer 3—IP Routing Command Reference)

route-policy (Layer 3—IP Routing Command Reference)

segment-routing mpls

global-block

Use global-block to configure the global MPLS SRGB.

Use undo global-block to restore the default.

Syntax

global-block minimum-value maximum-value

undo global-block

Default

The global MPLS SRGB is from 16000 to 24000.

Views

Segment routing view

Predefined user roles

network-admin

Parameters

minimum-value: Specifies the minimum label value, in the range of 1024 to 1010151.

maximum-value: Specifies the maximum label value, in the range of 1025 to 1010152.

Usage guidelines

The global MPLS SRGB is used for prefix segments and BGP prefix SIDs. If no MPLS SRGB is configured for a protocol process, the process uses the global MPLS SRGB.

If you have configured prefix SIDs when you configure the global MPLS SRGB, the global MPLS SRGB must contain the configured prefix SIDs.

Before executing this command, use the display mpls label command to display MPLS label usage information. Make sure that all labels in the specified SRGB range are idle. If a label in the range is not idle, the SRGB cannot be configured.

Examples

# Configure the global MPLS SRGB to be from 200000 to 220000.

<Sysname> system-view

[Sysname] segment-routing

[Sysname-segment-routing] global-block 200000 220000

Related commands

segment-routing global-block

isis adjacency-sid

Use isis adjacency-sid to assign an IS-IS adjacency SID to an IS-IS adjacency.

Use undo isis adjacency-sid to reclaim an IS-IS adjacency SID.

Syntax

isis adjacency-sid { absolute absolute-value | index index-value } [ nexthop nexthop-address ]

undo isis adjacency-sid { absolute absolute-value | index index-value } [ nexthop nexthop-address ]

Default

An IS-IS adjacency does not have an adjacency SID.

Views

Interface view

Predefined user roles

network-admin

Parameters

absolute absolute-value: Specifies an absolute value as the adjacency SID. The value range for the absolute-value argument is 1024 to 1010152.

index index-value: Specifies an adjacency SID index value in the range of 0 to 1009128.

nexthop nexthop-address: Specifies a next hop by its IP address. If the network type of the interface is broadcast, you must specify this option. If the network type of the interface is P2P, you cannot specify this option.

Usage guidelines

After you enable IS-IS adjacency SID allocation, the device randomly allocates adjacency SIDs to the links to its IS-IS neighbors. If the link to an IS-IS neighbor flaps, the adjacency SID of the link keeps changing. For a link to always use the same adjacency SID, use this command to assign a specific adjacency SID to the link.

You can assign adjacency SIDs by using absolute values or index values. If you use index values, the adjacency SID of a link is the base value of the SRLB plus the index value for the link.

Before assigning adjacency SIDs, execute the display mpls label command to display the usage status of the labels that you want to assign as adjacency SIDs. Make sure the labels are in Idle state. A label that is not in Idle state is being used by another protocol. If you assign it to a link as an adjacency SID, the adjacency SID is not available even if the status of the label changes to Idle later. To use the adjacency SID, you must remove the adjacency SID assignment and assign the adjacency SID again.

Before executing the isis adjacency-sid command on an interface, you must complete the following tasks:

· Enable IS-IS on the interface.

· Execute the segment-routing mpls and segment-routing adjacency enable commands.

You can assign the same adjacency SID on multiple interfaces.

If you execute the isis adjacency-sid command multiple times on an interface of the P2P network type, the most recent configuration takes effect.

If you execute the isis adjacency-sid command multiple times on an interface of the broadcast network type, the effective configuration varies depending on how you specify the next hop address:

· If you specify a different next hop address each time, all configurations take effect.

· If you specify the same next hop address each time, the most recent configuration takes effect.

To change the network type of an interface, execute the isis circuit-type p2p command before executing the isis adjacency-sid command on the interface. To change the network type of an interface after assigning an adjacency SID to the interface, you must remove the assignment first.

Examples

# Set the absolute value of the adjacency SID to 20000 on interface Ten-GigabitEthernet 3/1/1. Specify 1.1.1.1 as the next hop.

<Sysname> system-view

[Sysname] interface ten-gigabitethernet 3/1/1

[Sysname-Ten-GigabitEthernet3/1/1] isis enable 1

[Sysname-Ten-GigabitEthernet3/1/1] isis adjacency-sid absolute 20000 nexthop 1.1.1.1

Related commands

display mpls label (MPLS Command Reference)

isis circuit-type p2p (Layer 3—IP Routing Command Reference)

isis enable (Layer 3—IP Routing Command Reference)

segment-routing adjacency enable

segment-routing mpls

isis fast-reroute ti-lfa disable

Use isis fast-reroute ti-lfa disable to disable an IS-IS interface from participating in TI-LFA calculation.

Use undo isis fast-reroute ti-lfa disable to enable an IS-IS interface to participate in TI-LFA calculation.

Syntax

isis fast-reroute ti-lfa disable [ level-1 | level-2 ]

undo isis fast-reroute ti-lfa disable [ level-1 | level-2 ]

Default

An IS-IS interface participates in TI-LFA calculation.

Views

Interface view

Predefined user roles

network-admin

Parameters

level-1: Specifies TI-LFA calculation on IS-IS Level-1.

level-2: Specifies TI-LFA calculation on IS-IS Level-2.

Usage guidelines

Disable the output interface to the primary next hop from participating in TI-LFA calculation.

If you do not specify the level-1 or level-2 keyword, the command disables or enables the interface to participate in TI-LFA calculation in any level.

Examples

# Disable interface Ten-GigabitEthernet 3/1/1 from participating in TI-LFA calculation.

<Sysname> system-view

[Sysname] interface ten-gigabitethernet 3/1/1

[Sysname-Ten-GigabitEthernet3/1/1] isis enable 1

[Sysname-Ten-GigabitEthernet3/1/1] isis fast-reroute ti-lfa disable

Related commands

fast-reroute ti-lfa

isis prefix-sid

Use isis prefix-sid to configure an IS-IS prefix SID.

Use undo isis prefix-sid to restore the default.

Syntax

isis [ process-id process-id ] prefix-sid [ algorithm algorithm-id ] { absolute absolute-value | index index-value } [ n-flag-clear | { explicit-null | no-php } ] *

undo isis [ process-id process-id ] prefix-sid [ algorithm algorithm-id ]

Default

No IS-IS prefix SID is configured.

Views

Loopback interface view

Predefined user roles

network-admin

Parameters

process-id process-id: Specifies an IS-IS process by its process ID in the range of 1 to 65535. To configure an IS-IS prefix SID for a traditional IS-IS process, do not specify this option.

algorithm algorithm-id: Specifies a Flex-Algo for the prefix SID. The algorithm-id argument represents the Flex-Algo ID, in the range of 128 to 255. If you do not specify a Flex-Algo, IS-IS uses the SPF algorithm to calculate the shortest path to the prefix SID.

absolute absolute-value: Specifies an absolute value as the prefix SID. The value range for the absolute-value argument is 1024 to 1010152.

index index-value: Specifies an index value as the adjacency SID. The value range for the index-value argument is 0 to 1009128.

n-flag-clear: Sets the Node-SID flag bit of the prefix SID to 0 to use the prefix SID for a group of SR nodes. If you do not specify this keyword, the flag bit is 1 and the prefix SID is used for a single SR node.

explicit-null: Sets the Explicit-null flag bit of the prefix SID to 1. This setting requires that the upstream neighbor uses an explicit null label to replace the prefix SID. If you do not specify this keyword, the flag bit is 0 and the upstream neighbor continues to forward the packet based on the prefix SID. For more information about the explicit null label, see MPLS basics configuration in MPLS Configuration Guide.

no-php: Sets the P-flag bit of the prefix SID to 1 so the penultimate hop does not pop out the SID. If you do not specify this keyword, the P-flag bit is 0 and the penultimate hop pops out the SID.

Usage guidelines

An absolute value used as the prefix SID takes effect only if it is in the SRGB of the node.

If you specify an index value, the sum of the index value and the SRGB base value is used as the prefix SID. The prefix SID takes effect only if it is in the SRGB of the node.

To use a prefix SID for a group of SR nodes in anycast scenarios, specify the n-flag-clear keyword to set the Node-SID flag bit of the prefix SID to 0.

To configure an IS-IS prefix SID, you must enable an IS-IS process on the loopback interface.

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

Examples

# Set the IS-IS prefix SID index value to 20 on loopback interface 1.

<Sysname> system-view

[Sysname] interface loopback 1

[Sysname-LoopBack1] isis enable 1

[Sysname-LoopBack1] isis prefix-sid index 20

local-block

Use local-block to configure the SRLB.

Use undo local-block to restore the default.

Syntax

local-block minimum-value maximum-value [ ignore-conflict ]

undo local-block

Default

The SRLB is from 15000 to 15999.

Views

Segment routing view

Predefined user roles

network-admin

Parameters

minimum-value: Specifies the minimum label value, in the range of 1024 to 1010151.

maximum-value: Specifies the maximum label value, in the range of 1025 to 1010152.

ignore-conflict: Ignores the conflicts between the SRLB and allocated adjacency SIDs. With this keyword specified, this command can be executed but does not take effect if an allocated adjacency SID is not within the configured SRLB range. Without this keyword specified, this command cannot be executed if an allocated adjacency SID is not within the configured SRLB range.

Usage guidelines

CAUTION:

With the ignore-conflict keyword specified, this command can be executed but does not take effect if an allocated SR-MPLS adjacency SID is not within the configured SRLB range. To make the configured SRLB take effect, you must restart the device. Meanwhile, you must also change the allocated SID to be within the SRLB. Otherwise, the SRLSP using that SID cannot forward packets normally.

‌

Application scenarios

The segment routing local block (SRLB) is the range of local labels dedicated for SR-MPLS adjacency SIDs.

The device has a default reserved SRLB, which can neither be edited or deleted nor be used by other protocols. If you do not configure this command, the device allocates SR-MPLS adjacency SIDs from the reserved SRLB. In addition to the reserved SRLB, you can also use this command to allocate an additional label range as the SRLB to the device. The device will allocate SR-MPLS adjacency SIDs from the configured SRLB.

Restrictions and guidelines

If adjacency SIDs have been allocated from the reserved or configured SRLB, do not change the minimum label value in the SRLB when you configure this command. If you change the minimum label value, adjacency SIDs generated by using index values will be affected.

When you use this command to change the configured SRLB, follow these restrictions and guidelines:

· If you reduce the configured SRLB range, make sure the labels to be released in the SRLB are not in inuse state. You must first release the labels.

· If you expand the configured SRLB range, make sure the labels to be added in the SRLB are not in inuse or alloc state. You must first release the labels.

Before executing this command, use the display mpls label command to display MPLS label usage information.

Examples

# Configure the SRLB to be from 200000 to 220000.

<Sysname> system-view

[Sysname] segment-routing

[Sysname-segment-routing] local-block 200000 220000

Related commands

display mpls label

display mpls summary (MPLS Command Reference)

mapping-server prefix-sid-map

Use mapping-server prefix-sid-map to configure a prefix-SID mapping.

Use undo mapping-server prefix-sid-map to delete a prefix-SID mapping.

Syntax

mapping-server prefix-sid-map ip-address mask-length start-value [ range range-value ] [ attached ]

undo mapping-server prefix-sid-map ip-address mask-length

Default

No prefix-SID mappings exist.

Views

Segment routing view

Predefined user roles

network-admin

Parameters

ip-address: Specifies an IPv4 address prefix to be mapped or specifies the start IP prefix for a range of prefix-SID mappings, in dotted decimal notation.

mask-length: Specifies the mask length, in the range of 1 to 32.

start-value: Specifies the index value of the SID to be mapped to the specified prefix, or specifies the index value of the start SID for a range of prefix-SID mappings. The value range for this argument is 0 to 1009127.

range range-value: Specifies the number of prefix-SID mappings, in the range of 1 to 1009128.

attached: Specifies that the specified prefixes represent local networks.

Usage guidelines

The specified prefixes must not belong to any existing prefix-SID mappings.

Before you configure prefix-SID mappings in bulk, plan the number of mappings. Make sure there are enough mappings to use.

If you specify a value greater than 65535 for the range-value argument, the prefix-SID mappings cannot be advertised through IS-IS or OSPF.

Examples

# Map prefix 1.1.1.1/32 to SID index value 100.

<Sysname> system-view

[Sysname] segment-routing

[Sysname-segment-routing] mapping-server prefix-sid-map 1.1.1.1 32 100

# Configure two prefix-SID mappings, starting from prefix 10.1.1.1/32 and SID index value 200.

<Sysname> system-view

[Sysname] segment-routing

[Sysname-segment-routing] mapping-server prefix-sid-map 10.1.1.1 32 200 range 2

In the first mapping, the prefix is 10.1.1.1/32 and the SID is 200. In the second mapping, the prefix is 10.1.1.2/32 and the SID is 201.

mpls te path-selection adjacency-sid

Use mpls te path-selection adjacency-sid to configure a tunnel interface to perform CSPF calculation strictly based on adjacency SID information when establishing an SRLSP for an MPLS TE tunnel.

Use undo mpls te path-selection adjacency-sid to restore the default.

Syntax

mpls te path-selection adjacency-sid

undo mpls te path-selection adjacency-sid

Default

A tunnel interface does not perform CSPF calculation strictly based on adjacency SID information when establishing an SRLSP for an MPLS TE tunnel.

Views

Tunnel interface view

Predefined user roles

network-admin

Usage guidelines

This command takes effect only on an MPLS TE tunnel established by using SR.

Before executing this command, you must enable SR-MPLS and SR-MPLS adjacency SID allocation on each node that the TE tunnel might traverse.

If an MPLS TE tunnel is already established when you execute this command, the tunnel interface calculates a new SRLSP based on adjacency SID information.

· If the new SRLSP is successfully established, the tunnel interface removes the old SRLSP and uses the new SRLSP to establish a new MPLS TE tunnel.

· If the new SRLSP fails to be established, the tunnel interface continues to use the old SRLSP.

Examples

# Configure a tunnel interface to perform CSPF calculation strictly based on adjacency SID information when establishing an SRLSP for an MPLS TE tunnel.

<Sysname> system-view

[Sysname] interface tunnel 1 mode mpls-te

[Sysname-Tunnel1] mpls te path-selection adjacency-sid

mpls te static-sr-mpls

Use mpls te static-sr-mpls to bind a static SRLSP to an MPLS TE tunnel interface.

Use undo mpls te static-sr-mpls to unbind a static SRLSP from an MPLS TE tunnel interface.

Syntax

mpls te static-sr-mpls lsp-name [ backup ]

undo mpls te static-sr-mpls lsp-name

Default

An MPLS TE tunnel interface does not use any static SRLSPs.

Views

Tunnel interface view

Predefined user roles

network-admin

Parameters

lsp-name: Specifies a static SRLSP by its name, a case-sensitive string of 1 to 67 characters. The specified static SRLSP must be already created by using the static-sr-mpls lsp command.

backup: Specifies the backup static SRLSP. If you do not specify this keyword, this command specifies the main static SRLSP.

Usage guidelines

Execute this command only on the ingress node of a static SRLSP.

This command takes effect only if you have configured the mpls te signaling static command in tunnel interface view.

You can specify the backup keyword to bind a backup static SRLSP only if both the main and backup SRLSPs are established by using the adjacency segment method.

If you execute both the mpls te static-sr-mpls and mpls te static-cr-lsp commands on the device, only the mpls te static-cr-lsp command takes effect. For the mpls te static-sr-mpls command to take effect, execute the undo mpls te static-cr-lsp command.

Examples

# Bind static SRLSP static-sr-3 to MPLS TE tunnel interface 0.

<Sysname> system-view

[Sysname] interface tunnel 0 mode mpls-te

[Sysname-Tunnel0] mpls te static-sr-mpls static-sr-3

Related commands

display mpls te tunnel-interface (MPLS Command Reference)

mpls te signaling (MPLS Command Reference)

mpls te static-cr-lsp (MPLS Command Reference)

static-sr-mpls lsp

ospf adjacency-sid

Use ospf adjacency-sid to assign an OSPF adjacency SID to an OSPF adjacency.

Use undo ospf adjacency-sid to reclaim an OSPF adjacency SID.

Syntax

ospf adjacency-sid { absolute absolute-value | index index-value } [ nexthop nexthop-address ]

undo ospf adjacency-sid { absolute absolute-value | index index-value } [ nexthop nexthop-address ]

Default

An OSPF adjacency does not have an adjacency SID.

Views

Interface view

Predefined user roles

network-admin

Parameters

absolute absolute-value: Specifies an absolute value as the adjacency SID. The value range for the absolute-value argument is 1024 to 1010152.

index index-value: Specifies an adjacency SID index value as the adjacency SID. The value range for the index-value argument is 0 to 1009128.

nexthop nexthop-address: Specifies a next hop by its IP address. If the network type of the interface is not P2P, you must specify this option. If the network type of the interface is P2P, you cannot specify this option.

Usage guidelines

After you enable OSPF adjacency SID allocation, the device randomly allocates adjacency SIDs to the links to its OSPF neighbors. If the link to an OSPF neighbor flaps, the adjacency SID of the link keeps changing. For a link to always use the same adjacency SID, use this command to assign a specific adjacency SID to the link.

You can assign adjacency SIDs by using absolute values or index values. If you use index values, the adjacency SID of a link is the base value of the SRLB plus the index value for the link.

The ospf adjacency-sid command takes effect only after you execute the segment-routing mpls and segment-routing adjacency enable commands.

You can assign the same adjacency SID on multiple interfaces.

If you execute the ospf adjacency-sid command multiple times on an interface of the P2P network type, the most recent configuration takes effect.

If you execute the ospf adjacency-sid command multiple times on an interface of the broadcast network type, the effective configuration varies depending on how you specify the next hop address:

· If you specify a different next hop address each time, all configurations take effect.

· If you specify the same next hop address each time, the most recent configuration takes effect.

To change the network type of an interface, execute the ospf network-type command.

Examples

# Set the absolute value of the adjacency ID to 20000 on interface Ten-GigabitEthernet 3/1/1. Specify 1.1.1.1 as the next hop.

<Sysname> system-view

[Sysname] interface ten-gigabitethernet 3/1/1

[Sysname-Ten-GigabitEthernet3/1/1] ospf adjacency-sid absolute 20000 nexthop 1.1.1.1

Related commands

display mpls label (MPLS Command Reference)

ospf network-type (Layer 3—IP Routing Command Reference)

segment-routing adjacency enable

segment-routing mpls

ospf fast-reroute ti-lfa disable

Use ospf fast-reroute ti-lfa disable to disable an OSPF interface from participating in TI-LFA calculation.

Use undo ospf fast-reroute ti-lfa disable to enable an OSPF interface to participate in TI-LFA calculation.

Syntax

ospf fast-reroute ti-lfa disable

undo ospf fast-reroute ti-lfa disable

Default

An OSPF interface participates in TI-LFA calculation.

Views

Interface view

Predefined user roles

network-admin

Usage guidelines

On the source node, the route's output interface to the primary next hop might not be on the backup path calculated by TI-LFA. Disable TI-LFA on the interface to prevent it from participating in TI-LFA calculation.

Examples

# Disable interface Ten-GigabitEthernet 3/1/1 from participating in TI-LFA calculation.

<Sysname> system-view

[Sysname] interface ten-gigabitethernet 3/1/1

[Sysname-Ten-GigabitEthernet3/1/1] ospf fast-reroute ti-lfa disable

Related commands

fast-reroute ti-lfa (OSPF view)

ospf prefix-sid

Use ospf prefix-sid to configure an OSPF prefix SID.

Use undo ospf prefix-sid to restore the default.

Syntax

ospf process-id prefix-sid { absolute absolute-value | index index-value } [ n-flag-clear | { explicit-null | no-php } ] *

undo ospf process-id prefix-sid

Default

No OSPF prefix SID is configured.

Views

Loopback interface view

Predefined user roles

network-admin

Parameters

process-id: Specifies an OSPF process ID in the range of 1 to 65535.

absolute absolute-value: Specifies an absolute value as the prefix SID. The value range for the absolute-value argument is 1024 to 1010152.

index index-value: Specifies an index value as the prefix SID. The value range for the index-value argument is 0 to 1009128.

no-php: Sets the P-flag bit of the prefix SID to 1 so the penultimate hop does not pop out the SID. If you do not specify this keyword, the P-flag bit is 0 and the penultimate hop pops out the SID.

Usage guidelines

An absolute value used as the prefix SID takes effect only if it is in the SRGB of the node.

If you specify an index value, the sum of the index value and the SRGB base value is used as the prefix SID. The prefix SID takes effect only if it is in the SRGB of the node.

To use a prefix SID for a group of SR nodes in anycast scenarios, specify the n-flag-clear keyword to set the Node-SID flag bit of the prefix SID to 0.

The configured OSPF prefix SID takes effect only if the OSPF process enabled on the loopback interface is the same as the OSPF process associated with the prefix SID.

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

Examples

# Set the OSPF prefix SID index value to 20 on loopback interface 1.

<Sysname> system-view

[Sysname] interface loopback 1

[Sysname-LoopBack1] ospf 1 prefix-sid index 20

peer egress-engineering

Use peer egress-engineering to enable BGP-EPE for a peer or peer group and assign a label (SID) to the peer or peer group.

Use undo peer egress-engineering to restore the default for a peer or peer group.

Syntax

peer { group-name | ipv4-address [ mask-length ] } egress-engineering [ adjacency | node-adjacency | set ] [ label label-value | route-policy policy-name ]

undo peer { group-name | ipv4-address [ mask-length ] } egress-engineering

Default

BGP-EPE is disabled.

Views

BGP instance view

Predefined user roles

network-admin

Parameters

group-name: Specifies an existing peer group by its name, a case-sensitive string of 1 to 47 characters.

ipv4-address: Specifies the IPv4 address of an existing peer.

mask-length: Specifies the mask length, in the range of 0 to 32. This argument and the ipv4-address argument together specify a subnet. If you specify this argument, the command applies to dynamic peers on the specified subnet.

adjacency: Assigns a PeerAdj SID.

node-adjacency: Assigns both a PeerNode SID and a PeerAdj SID.

set: Assigns a PeerSet SID.

label label-value: Specifies the SID value, in the range of 16 to 1010152.

route-policy route-policy-name: Specifies a routing policy to a assign a SID. The route-policy-name argument represents the routing policy name, a case-sensitive string of 1 to 63 characters.

Usage guidelines

If you do not specify the adjacency, node-adjacency, or set keyword, the device assigns a PeerNode SID.

If you enable BGP-EPE without specifying an SID (by using the label or route-policy option), the device randomly assigns an SID to the specified peer or peer group.

When you use BGP-EPE to apply a routing policy to a peer or peer group, follow these restrictions and guidelines:

· You can use the apply label-value command to set an SID value and cannot use the apply label-index command to set a label index value.

· You cannot apply a routing policy to assign the same label to multiple BGP peers or peer groups when you assign a PeerNode SID, PeerAdj SID, or PeerNode-Adj SID to the BGP peers or peer groups.

· You can apply a routing policy to assign the same label to multiple BGP peers or peer groups only when you assign a PeerSet SID to the BGP peers or peer groups.

· You can use if-match interface as a filtering condition only when you assign a PeerAdj SID to a BGP peer or peer group.

· If you apply a routing policy to a peer group, BGP-EPE assigns a SID to only one of the peers in the peer group.

If you use the label keyword to assign a static SID to a peer group, BGP-EPE assigns a SID to only one of the peers in the peer group.

If the specified peer group contains two or more peers, you cannot assign other types but the set type of SID by using the following methods:

· Assign a SID by using the label label-value option.

· Specify a routing policy to assign a SID by using the route-policy route-policy-name option.

Examples

# Enable BGP-EPE for peer 1.1.1.1 and assign a PeerNode SID to the peer.

<Sysname> system-view

[Sysname] bgp 100

[Sysname-bgp-default] peer 1.1.1.1 egress-engineering

Related commands

display bgp egress-engineering ipv4

display mpls label (MPLS Command Reference)

peer peer-set

Use peer peer-set to add a peer or peer group to a BGP-EPE peer set.

Use undo peer peer-set to remove a peer or peer group from its BGP-EPE peer set.

Syntax

peer { group-name | ipv4-address [ mask-length ] } peer-set peer-set-name

undo peer { group-name | ipv4-address [ mask-length ] } peer-set

Default

A peer or peer group does not belong to a BGP-EPE peer set.

Views

BGP instance view

Predefined user roles

network-admin

Parameters

group-name: Specifies an existing peer group by its name, a case-sensitive string of 1 to 47 characters.

ipv4-address: Specifies an existing peer by its IPv4 address.

mask-length: Specifies a mask length in the range of 0 to 32. The IPv4 address and the mask length together specify a network segment. This command applies to the dynamic peers in the specified network segment.

peer-set-name: Specifies the name of the BGP-EPE peer set to which the specified BGP peers will be added. The peer set name is a case-sensitive string of 1 to 63 characters.

Usage guidelines

Before you execute this command, make sure BGP-EPE is enabled.

If a peer or peer group is assigned a PeerSet SID (by using the peer egress-engineering set command), the peer or peer group cannot be added to a BGP-EPE peer set, and vice versa.

Examples

# Add peer 10.1.1.1 to BGP-EPE peer set abc.

<Sysname> system-view

[Sysname] bgp 100

[Sysname-bgp-default] peer 10.1.1.1 peer-set abc

Related commands

egress-engineering peer-set

peer egress-engineering

sbfd detect-multiplier

Use sbfd detect-multiplier to set the SBFD detection time multiplier for SRLSPs.

Use undo sbfd detect-multiplier to restore the default.

Syntax

sbfd detect-multiplier value

undo sbfd detect-multiplier

Default

The SBFD detection time multiplier is not set for SRLSPs. The BFD detection time multiplier set by the bfd multi-hop detect-multiplier command applies.

Views

Segment routing view

Predefined user roles

network-admin

Parameters

value: Specifies a detection time multiplier, which is the maximum number of consecutive SBFD packets that can be discarded. The value range for this argument is 3 to 50.

Usage guidelines

The device sends SBFD packets to a peer periodically. If the device does not receive SBFD packets from the peer within the actual detection interval, it determines that the session is down. The actual detection interval of the sender is the detection time multiplier of the receiver × the actual sending interval of the receiver.

This command takes effect only on SBFD sessions created by the sbfd enable command.

Examples

# Set the SBFD detection time multiplier to 3 for SRLSPs.

<Sysname> system-view

[Sysname] segment-routing

[Sysname-segment-routing] sbfd enable

[Sysname-segment-routing] sbfd detect-multiplier 3

Related commands

bfd multi-hop detect-multiplier (High Availability Command Reference)

sbfd enable

Use sbfd enable to enable SBFD for SRLSPs.

Use undo sbfd enable to restore the default.

Syntax

sbfd enable [ prefix-list prefix-list-name ]

undo sbfd enable

Default

SBFD for SRLSPs is not enabled.

Views

Segment routing view

Predefined user roles

network-admin

Parameters

prefix-list prefix-list-name: Specifies an IPv4 prefix list by the prefix list name, a case-sensitive string of 1 to 63 characters. The device can create SBFD sessions only for the SRLSPs permitted by the specified IPv4 prefix list. If you do not specify an IPv4 prefix list, the device can create SBFD sessions for all SRLSPs.

Usage guidelines

This command enables the device to create an SBFD session for each primary SRLSP to verify the connectivity of the primary SRLSP. When a primary SRLSP fails, SBFD can quickly detect the failure and switches traffic to the backup SRLSP to reduce packet loss.

Before you execute this command, enable MPLS BFD by using the mpls bfd enable command.

After you execute this command, the local end uses the destination address of an SRLSP as the remote discriminator to establish an SBFD session for the SRLSP. Make sure you specify the local discriminator of the SBFD session on the remote end as the SRLSP's destination address by using the sbfd local-discriminator command.

If you execute both the sbfd enable command and the mpls sbfd command for SRLSPs, the mpls sbfd command takes effect on the SRLSPs.

In segment routing view, if you execute the bfd enable command and the sbfd enable command multiple times, the most recent configuration takes effect.

Examples

# Enable SBFD for SRLSPs.

<Sysname> system-view

[Sysname] segment-routing

[Sysname-segment-routing] sbfd enable

Related commands

bfd enable

mpls bfd enable (MPLS Command Reference)

mpls sbfd (for LSP) (MPLS Command Reference)

sbfd local-discriminator (MPLS Command Reference)

sbfd min-receive-interval

Use sbfd min-receive-interval to set the minimum interval for receiving SBFD packets for SRLSP SBFD.

Use undo sbfd min-receive-interval to restore the default.

Syntax

sbfd min-receive-interval interval

undo sbfd min-receive-interval

Default

The minimum interval for receiving SBFD packets is not set for SRLSP SBFD. The interval set by the bfd multi-hop min-receive-interval command applies.

Views

Segment routing view

Predefined user roles

network-admin

Parameters

interval: Specifies the minimum interval for receiving SBFD packets, in milliseconds. The value range is 3 to 10000.

Usage guidelines

This command takes effect only on SBFD sessions created by the sbfd enable command.

Examples

# Set the minimum SBFD packet receiving interval for SRLSP SBFD to 450 milliseconds.

<Sysname> system-view

[Sysname] segment-routing

[Sysname-segment-routing] sbfd enable

[Sysname-segment-routing] sbfd min-receive-interval 450

Related commands

bfd multi-hop min-receive-interval (High Availability Command Reference)

sbfd enable

sbfd min-transmit-interval

Use sbfd min-transmit-interval to set the minimum interval for transmitting SBFD packets for SRLSP SBFD.

Use undo sbfd min-transmit-interval to restore the default.

Syntax

sbfd min-transmit-interval interval

undo sbfd min-transmit-interval

Default

The minimum interval for transmitting SBFD packets is not set for SRLSP SBFD. The interval set by the bfd multi-hop min-transmit-interval command applies.

Views

Segment routing view

Predefined user roles

network-admin

Parameters

interval: Specifies the minimum interval for transmitting SBFD packets, in milliseconds. The value range is 3 to 10000.

Usage guidelines

Use this command to prevent the SBFD packet sending rate from exceeding the packet receiving rate of the peer end.

The actual SBFD packet transmitting interval on the local end is the greater value between the following values:

· Minimum interval for transmitting SBFD packets on the local end.

· Minimum interval for receiving SBFD packets on the peer end.

This command takes effect only on SBFD sessions created by the sbfd enable command.

Examples

# Set the minimum SBFD packet transmitting interval for SRLSP SBFD to 450 milliseconds.

<Sysname> system-view

[Sysname] segment-routing

[Sysname-segment-routing] sbfd enable

[Sysname-segment-routing] sbfd min-transmit-interval 450

Related commands

bfd multi-hop min-transmit-interval (High Availability Command Reference)

sbfd enable

segment-routing

Use segment-routing to enable segment routing and enter segment routing view.

Use undo segment-routing to disable segment routing.

Syntax

segment-routing

undo segment-routing

Default

Segment routing is disabled.

Views

System view

Predefined user roles

network-admin

Usage guidelines

To configure the Segment Routing Mapping Server (SRMS) features, you must execute this command on the SRMS. The SRMS is an entity that advertises prefix-SID mappings in an IGP. By deploying an SRMS, you can allocate SIDs to devices that do not support SR-MPLS, allowing for SR-MPLS and LDP interworking.

Examples

# Enable segment routing and enter segment routing view.

<Sysname> system-view

[Sysname] segment-routing

[Sysname-segment-routing]

segment-routing adjacency enable

Use segment-routing adjacency enable to enable SR-MPLS adjacency SID allocation.

Use undo segment-routing adjacency enable to disable SR-MPLS adjacency SID allocation.

Syntax

segment-routing adjacency enable

undo segment-routing adjacency enable

Default

SR-MPLS adjacency SID allocation is disabled.

Views

IS-IS IPv4 unicast address family view

OSPF view

Predefined user roles

network-admin

Usage guidelines

For this command to take effect, you must enable SR-MPLS.

Examples

# Enable SR-MPLS adjacency SID allocation for IS-IS process 1.

<Sysname> system-view

[Sysname] isis 1

[Sysname-isis-1] address-family ipv4

[Sysname-isis-1-ipv4] segment-routing adjacency enable

<Sysname> system-view

[Sysname] isis 1

[Sysname-isis-1] address-family ipv4

[Sysname-isis-1-ipv4] segment-routing adjacency enable

# Enable SR-MPLS adjacency SID allocation for OSPF process 1.

<Sysname> system-view

[Sysname] ospf 1

[Sysname-ospf-1] segment-routing adjacency enable

<Sysname> system-view

[Sysname] ospf 1

[Sysname-ospf-1] segment-routing adjacency enable

Related commands

segment-routing mpls

segment-routing adjacency-sid delete-delay

Use segment-routing adjacency-sid delete-delay to enable dynamic adjacency SID deletion delay and set the delay timer.

Use undo segment-routing adjacency-sid delete-delay to restore the default.

Syntax

segment-routing adjacency-sid delete-delay [ time-value ]

undo segment-routing adjacency-sid delete-delay

Default

Dynamic adjacency SID deletion delay is enabled. The delay timer is 1800 seconds.

Views

IS-IS IPv4 address family view

OSPF view

Predefined user roles

network-admin

Parameters

time-value: Sets the dynamic adjacency SID deletion delay timer in seconds, in the range of 1 to 2592000. The default value is 1800 value is 1800. A value of 0 disables dynamic adjacency SID deletion.

Usage guidelines

Packet loss occurs between OSPF or IS-IS neighbors if the neighbors frequently delete and request dynamically allocated adjacency SIDs for the links between them because of neighbor flapping. To resolve this issue, set a delay timer for deleting dynamically allocated adjacency SIDs when the neighbors are disconnected. If the neighbors are still disconnected when the delay timer expires, the device deletes the dynamically allocated adjacency SIDs.

Examples

# Enable dynamic adjacency SID deletion delay and set the delay timer to 360 seconds.

<Sysname> system-view

[Sysname] isis 1

[Sysname-isis-1] address-family ipv4

[Sysname-isis-1-ipv4] segment-routing adjacency-sid delete-delay 360

<Sysname> system-view

Sysname-isis-1-ipv4] segment-routing adjacency-sid delete-delay 360

# Enable dynamic adjacency SID deletion delay and set the delay timer to 360 seconds.

<Sysname> system-view

[Sysname] ospf 1

[Sysname-ospf-1] segment-routing adjacency-sid delete-delay 360

Sysname-ospf-1] segment-routing adjacency-sid delete-delay 360

segment-routing global-block

Use segment-routing global-block to configure the MPLS SRGB.

Use undo segment-routing global-block to restore the default.

Syntax

segment-routing global-block minimum-value maximum-value

undo segment-routing global-block

Default

The MPLS SRGB is from 16000 to 24000.

Views

IS-IS view

OSPF view

Predefined user roles

network-admin

Parameters

minimum-value: Specifies the minimum label value, in the range of 1024 to 1010151.

maximum-value: Specifies the maximum label value, in the range of 1025 to 1010152.

Usage guidelines

The global MPLS SRGB is used for static prefix segments and BGP prefix SIDs. If no MPLS SRGB is configured for a protocol process, the process uses the global MPLS SRGB.

If you have configured prefix SIDs when you configure the SRGB, the SRGB must contain the configured prefix SIDs.

In the following situations, the configured SRGB takes effect after a device reboot:

· The SRGB contains a label that is already used by another protocol. For example, the SRGB contains a label that is already used by LDP.

· The SRGB overlaps with the label range of another protocol. For example, the SRGB for OSPF process 1 overlaps with the SRGB for IS-IS process 1.

Examples

# Configure the MPLS SRGB to be from 17000 to 22000 for IS-IS process 1.

<Sysname> system-view

[Sysname] isis 1

[Sysname-isis-1] segment-routing global-block 17000 22000

# Configure the MPLS SRGB to be from 17000 to 22000 for OSPF process 1.

<Sysname> system-view

[Sysname] ospf 1

[Sysname-ospf-1] segment-routing global-block 17000 22000

Related commands

global-block

segment-routing label-advertise

Use segment-routing label-advertise to specify the type of label for the device to advertise to the penultimate hop when the device acts as the egress in an SR-MPLS network.

Use undo segment-routing label-advertise to restore the default.

Syntax

segment-routing label-advertise { explicit-null | non-null }

undo segment-routing label-advertise

Default

As egress, the device advertises an implicit null label of 3 to the penultimate hop.

Views

BGP IPv4 unicast address family view

BGP IPv4 labeled unicast address family view

Predefined user roles

network-admin

Parameters

explicit-null: Advertises an explicit null label of 0 to the penultimate hop.

non-null: Advertises a non-null label to the penultimate hop.

Usage guidelines

As a best practice, configure the egress node to advertise an implicit null label to the penultimate hop if the penultimate hop supports PHP.

If you want to simplify packet forwarding on egress but keep labels to determine QoS policies, configure the egress node to advertise an explicit null label to the penultimate hop.

Use non-null labels only in particular scenarios. For example, when OAM is configured on the egress node, the egress node can get the OAM function entity status only through non-null labels. In this case, the egress node assigns an SID to the penultimate hop based on the prefix SID information in the BGP IPv4 unicast route.

If you change the type of label for the device to advertise to the penultimate hop, the device will close all SRLSPs established based on BGP IPv4 unicast routes. Then, the device will re-establish SRLSPs, using the new label type.

Before executing the command, you must execute the segment-routing mpls command to enable SR-MPLS.

Examples

# Configure the device to advertise an explicit null label to the penultimate hop.

<Sysname> system-view

[Sysname] bgp 100

[Sysname-bgp-default] address-family ipv4 unicast

[Sysname-bgp-default-ipv4] segment-routing label-advertise explicit-null

Related commands

segment-routing mpls

segment-routing lsp-trigger

Use segment-routing lsp-trigger to configure the SRLSP establishment triggering policy.

Use undo segment-routing lsp-trigger to restore the default.

Syntax

segment-routing lsp-trigger { host | none | prefix-list prefix-name }

undo segment-routing lsp-trigger

Default

The device allows all FECs to trigger SRLSP establishment.

Views

OSPF view

Predefined user roles

network-admin

Parameters

host: Allows host FECs to trigger SRLSP establishment.

none: Allows no FECs to trigger SRLSP establishment.

prefix-list prefix-name: Allows FECs permitted by a prefix list to trigger SRLSP establishment. The prefix-name argument is a case-sensitive string of 1 to 63 characters.

Usage guidelines

To save system resources, you can configure the SRLSP establishment triggering policy to allow only certain FECs to trigger SRLSP establishment.

Examples

# Configure the SRLSP establishment triggering policy to allow only host FECs to trigger SRLSP establishment.

<Sysname> system-view

[Sysname] ospf 1

[Sysname-ospf-1] segment-routing lsp-trigger host

segment-routing mapping-server advertise-local

Use segment-routing mapping-server advertise-local to enable advertisement of locally configured prefix-SID mappings.

Use undo segment-routing mapping-server advertise-local to disable advertisement of locally configured prefix-SID mappings.

Syntax

segment-routing mapping-server advertise-local

undo segment-routing mapping-server advertise-local

Default

Advertisement is disabled for locally configured prefix-SID mappings.

Views

IS-IS IPv4 unicast address family view

OSPF view

Predefined user roles

network-admin

Usage guidelines

In an SR to LDP interworking scenario, you must execute this command on the SRMS so the device advertises locally configured prefix-SID mappings to neighbors.

Examples

# Enable IS-IS to advertise locally configured prefix-SID mappings for IS-IS process 1.

<Sysname> system-view

[Sysname] isis 1

[Sysname-isis-1] address-family ipv4

[Sysname-isis-1-ipv4] segment-routing mapping-server advertise-local

# Enable OSPF to advertise locally configured prefix-SID mappings for OSPF process 1.

<Sysname> system-view

[Sysname] ospf 1

[Sysname-ospf-1] segment-routing mapping-server advertise-local

Related commands

mapping-server prefix-sid-map

segment-routing mapping-server receive

Use segment-routing mapping-server receive to enable reception of prefix-SID mappings.

Use undo segment-routing mapping-server receive to disable reception of prefix-SID mappings.

Syntax

segment-routing mapping-server receive

undo segment-routing mapping-server receive

Default

Reception of prefix-SID mappings is enabled.

Views

IS-IS IPv4 unicast address family view

OSPF view

Predefined user roles

network-admin

Usage guidelines

In an SR to LDP interworking scenario, you must execute this command on the SRMCs so they can identify the prefix-SID mappings advertised by the SRMS.

Examples

# Disable reception of prefix-SID mappings for IS-IS process 1.

<Sysname> system-view

[Sysname] isis 1

[Sysname-isis-1] address-family ipv4

[Sysname-isis-1-ipv4] undo segment-routing mapping-server receive

# Disable reception of prefix-SID mappings for OSPF process 1.

<Sysname> system-view

[Sysname] ospf 1

[Sysname-ospf-1] undo segment-routing mapping-server receive

Related commands

mapping-server prefix-sid-map

mapping-server prefix-sid-map advertise-local

segment-routing microloop-avoidance enable

Use segment-routing microloop-avoidance enable to enable SR microloop avoidance.

Use undo segment-routing microloop-avoidance enable to disable SR microloop avoidance.

Syntax

In IS-IS IPv4 unicast address family view:

segment-routing microloop-avoidance enable [ level-1 | level-2 ]

undo segment-routing microloop-avoidance enable [ level-1 | level-2 ]

In OSPF view:

segment-routing microloop-avoidance enable

undo segment-routing microloop-avoidance enable

Default

SR microloop avoidance is disabled.

Views

IS-IS IPv4 unicast address family view

OSPF view

Predefined user roles

network-admin

Parameters

level-1: Specifies SR microloop avoidance for IS-IS Level-1.

level-2: Specifies SR microloop avoidance for IS-IS Level-2.

Usage guidelines

After a network failure occurs or recovers, route convergence occurs on relevant network devices. Because of non-simultaneous convergence on network devices, microloops might be formed. After you configure SR microloop avoidance, the devices will forward traffic along the specified path before route convergence is finished on all the relevant network devices. Because the forwarding path is independent of route convergence, microloops are avoided.

The specific process is as follows:

· After a network failure occurs, the device installs the calculated forwarding path to the FIB and switches to the forwarding path after a delay time. During the delay time, the device still uses the TI-LFA FRR backup path.

· After a network failure recovers, the device calculates an active path and a backup path with a SID. During the delay time, the device still uses the backup path.

If you configure both FRR microloop avoidance and SR microloop avoidance, both timers are started and FRR microloop avoidance takes effect.

If you do not specify the level-1 or level-2 keyword, the segment-routing microloop-avoidance enable command enables or disables SR microloop avoidance on all IS-IS levels.

Examples

# Enable SR microloop avoidance for IS-IS process 1.

<Sysname> system-view

[Sysname] isis 1

[Sysname-isis-1] address-family ipv4

[Sysname-isis-1-ipv4] segment-routing microloop-avoidance enable

# Enable SR microloop avoidance for OSPF process 1.

<Sysname> system-view

[Sysname] ospf 1

[Sysname-ospf-1] segment-routing microloop-avoidance enable

Related commands

fast-reroute microloop-avoidance enable

segment-routing microloop-avoidance rib-update-delay

Use segment-routing microloop-avoidance rib-update-delay to set the SR microloop avoidance RIB-update-delay time.

Use undo segment-routing microloop-avoidance rib-update-delay to restore the default.

Syntax

In IS-IS IPv4 unicast address family view:

segment-routing microloop-avoidance rib-update-delay delay-time [ level-1 | level-2 ]

undo segment-routing microloop-avoidance rib-update-delay [ level-1 | level-2 ]

In OSPF view:

segment-routing microloop-avoidance rib-update-delay delay-time

undo segment-routing microloop-avoidance rib-update-delay

Default

The SR microloop avoidance RIB-update-delay time is 5000 ms.

Views

IS-IS IPv4 unicast address family view

OSPF view

Predefined user roles

network-admin

Parameters

delay-time: Specifies the SR microloop avoidance RIB-update-delay time in milliseconds. The value range is 1 to 60000.

level-1: Specifies the SR microloop avoidance RIB-update-delay time for IS-IS Level-1.

level-2: Specifies the SR microloop avoidance RIB-update-delay time for IS-IS Level-2.

Usage guidelines

To leave sufficient time for IGP to finish route convergence, specify a proper value for the SR microloop avoidance RIB-update-delay timer. Before the timer expires, failure relevant devices will forward traffic along the specified path. After the timer expires, traffic will traverse the usual path.

If you do not specify the level-1 or level-2 keyword, this command sets the SR microloop avoidance RIB-update-delay time for all IS-IS levels.

Examples

# Set the SR microloop avoidance RIB-update-delay time to 6000 ms for IS-IS process 1.

<Sysname> system-view

[Sysname] isis 1

[Sysname-isis-1] address-family ipv4

[Sysname-isis-1-ipv4] segment-routing microloop-avoidance rib-update-delay 6000

# Set the SR microloop avoidance RIB-update-delay time to 6000 ms for OSPF process 1.

<Sysname> system-view

[Sysname] ospf 1

[Sysname-ospf-1] segment-routing microloop-avoidance rib-update-delay 6000

Related commands

segment-routing microloop-avoidance enable

segment-routing microloop-avoidance strict-sid-only

Use segment-routing microloop-avoidance strict-sid-only to configure SR microloop avoidance to encapsulate only strict SIDs in the SID list.

Use undo segment-routing microloop-avoidance strict-sid-only to restore the default.

Syntax

segment-routing microloop-avoidance strict-sid-only

undo segment-routing microloop-avoidance strict-sid-only

Default

The strict-SID-only feature is not configured for SR microloop avoidance.

Views

IS-IS IPv4 unicast address family view

Predefined user roles

network-admin

Usage guidelines

By default, SR microloop avoidance first calculates the prefix SID to the P node, and then calculates the adjacency SIDs from the P node to the destination node, and then encapsulates the list of prefix and adjacency SIDs into the packet.

If multi-point failure exists and the forwarding path is frequently switched, there might be a microloop on the path to the P node identified by the prefix SID. To avoid the microloop, you can strictly constrain the path to the P node. This command strictly constrains the path to the P node by calculating an adjacency SID to reach the P node. Then, the SID list encapsulated into the packet consists of the adjacency SID to the P node and adjacency SIDs from the P node to the destination node.

Examples

# Configure SR microloop avoidance in IS-IS process 1 to encapsulate strict SIDs in the SID list.

<Sysname> system-view

[Sysname] isis 1

[Sysname-isis-1] address-family ipv4

[Sysname-isis-1-ipv4] segment-routing microloop-avoidance strict-sid-only

segment-routing mpls

Use segment-routing mpls to enable SR-MPLS.

Use undo segment-routing mpls to disable SR-MPLS.

Syntax

segment-routing mpls

undo segment-routing mpls

Default

SR-MPLS is disabled.

Views

IS-IS IPv4 unicast address family view

OSPF view

BGP IPv4 unicast address family view

BGP IPv4 labeled unicast address family view

Predefined user roles

network-admin

Usage guidelines

For SR-MPLS to take effect, perform the following tasks before configuring the IGP to support SR-MPLS:

· If the IGP is IS-IS, set the cost style to wide, compatible, or wide-compatible. For more information about the cost style, see IS-IS configuration in Layer 3—IP Routing Configuration Guide.

· If the IGP is OSPF, enable opaque LSA reception and advertisement capability. For more information about the capability, see OSPF configuration in Layer 3—IP Routing Configuration Guide.

Examples

# Enable SR-MPLS in IS-IS IPv4 unicast address family view of IS-IS process 1.

<Sysname> system-view

[Sysname] isis 1

[Sysname-isis-1] cost-style wide

[Sysname-isis-1] address-family ipv4

[Sysname-isis-1-ipv4] segment-routing mpls

# Enable SR-MPLS for OSPF process 1.

<Sysname> system-view

[Sysname] ospf 1

[Sysname-ospf-1] segment-routing mpls

# Enable SR-MPLS for the BGP IPv4 unicast address family.

<Sysname> system-view

[Sysname] bgp 100

[Sysname-bgp-default] address-family ipv4 unicast

[Sysname-bgp-default-ipv4] segment-routing mpls

Related commands

cost-style (Layer 3—IP Routing Command Reference)

opaque-capability enable (Layer 3—IP Routing Command Reference)

segment-routing prefix-sid-map

Use segment-routing prefix-sid-map to enable prefix-SID mappings.

Use undo segment-routing prefix-sid-map to disable prefix-SID mappings.

Syntax

segment-routing prefix-sid-map

undo segment-routing prefix-sid-map

Default

Prefix-SID mappings are disabled.

Views

BGP IPv4 unicast address family view

BGP IPv4 labeled unicast address family view

Predefined user roles

network-admin

Usage guidelines

After you execute this command on the SRMCs, the device will assign SIDs to prefixes based on prefix-SID mappings when it receives BGP IPv4 unicast routes or BGP IPv4 labeled unicast routes from neighbors. The prefix-SID mappings are configured by using the mapping-server prefix-sid-map command.

If a BGP route contains an SID but there is a prefix-SID mapping for the prefix, the device assigns the SID in the mapping to the prefix.

Before executing this command, execute the segment-routing mpls command to enable SR-MPLS.

Examples

# Enable prefix-SID mappings in BGP IPv4 unicast address family view.

<Sysname> system-view

[Sysname] bgp 100

[Sysname-bgp-default] address-family ipv4 unicast

[Sysname-bgp-default-ipv4] segment-routing prefix-sid-map

Related commands

mapping-server prefix-sid-map

segment-routing mpls

segment-routing sr-prefer

Use segment-routing sr-prefer to configure the device to prefer SRLSPs in traffic forwarding.

Use undo segment-routing sr-prefer to restore the default.

Syntax

segment-routing sr-prefer [ prefix-list prefix-list-name ]

undo segment-routing sr-prefer

Default

The device prefers LDP LSPs in traffic forwarding.

Views

IS-IS IPv4 unicast address family view

OSPF view

Predefined user roles

network-admin

Parameters

prefix-list prefix-list-name: Specifies an IP address prefix list by its name, a case-sensitive string of 1 to 63 characters. The device preferentially uses SRLSPs to forward traffic destined for addresses on the prefix list, and preferentially uses LDP LSPs to forward traffic destined for other addresses. If you do not specify an IP address prefix list, the device preferentially uses SRLSPs to forward all traffic.

Usage guidelines

This command determines whether the device prefers SRLSPs or LDP LSPs when both SRLSPs and LDP LSPs are available for traffic forwarding.

This command takes effect only when SR-MPLS is enabled and the SRLSPs use prefix SIDs.

Examples

# Configure the device to preferentially use SRLSPs established by OSPF to forward all traffic.

<Sysname> system-view

[Sysname] ospf 1

[Sysname-ospf-1] segment-routing sr-prefer

# Configure the device to preferentially use SRLSPs established by OSPF to forward traffic that is identified by prefix list 8.

<Sysname> system-view

[Sysname] ip prefix-list 8 permit 4.4.4.4 32

[Sysname] ospf 1

[Sysname-ospf-1] segment-routing sr-prefer prefix-list 8

Related commands

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

segment-routing mpls

static-sr-mpls adjacency

Use static-sr-mpls adjacency to configure an adjacency segment for static SR-MPLS.

Use undo static-sr-mpls adjacency to delete an adjacency segment.

Syntax

static-sr-mpls adjacency adjacency-path-name in-label label-value { nexthop ip-address | outgoing-interface interface-type interface-number }

undo static-sr-mpls adjacency adjacency-path-name

Default

No adjacency segments exist.

Views

System view

Predefined user roles

network-admin

Parameters

adjacency-path-name: Specifies the adjacency segment name, a case-sensitive string of 1 to 67 characters.

in-label label-value: Specifies the incoming label, in the range of 16 to 1010152.

nexthop ip-address: Specifies the next hop address.

outgoing-interface interface-type interface-number: Specifies an output interface by its type and number. The output interface must be a P2P interface.

Usage guidelines

Execute this command on all nodes of a static SRLSP.

If you specify the next hop address, make sure the following requirements are met:

· The device has a route to reach the next hop address.

· MPLS is enabled on the output interface of the route.

If you specify an output interface, make sure the following requirements are met:

· The interface is up.

· The interface can receive direct routes.

· MPLS is enabled on the interface.

The incoming label specified by this command must be different than existing static LSPs, static PWs, and static CRLSPs. If not, the configured adjacency segment is unavailable. The adjacency segment cannot become available even if you change the incoming label of the static LSP, static PW, or static CRLSP. To resolve this problem, you must delete the existing adjacency segment and configure a new one with a different incoming label.

Examples

# Configure an adjacency segment named adj1. Set the incoming label to 100 and the next hop address to 12.2.1.2.

<Sysname> system-view

[Sysname] static-sr-mpls adjacency adj1 in-label 100 nexthop 12.2.1.2

Related commands

display static-sr-mpls

static-sr-mpls lsp

Use static-sr-mpls lsp to configure a static SRLSP.

Use undo static-sr-mpls lsp to delete a static SRLSP.

Syntax

static-sr-mpls lsp lsp-name out-label out-label-value&<1-14>

undo static-sr-mpls lsp lsp-name

Default

No static SRLSPs exist.

Views

System view

Predefined user roles

network-admin

Parameters

lsp-name: Specifies the static SRLSP name, a case-sensitive string of 1 to 67 characters.

out-label out-label-value&<1-14>: Specifies a space-separated list of up to 14 outgoing labels, corresponding to the labels from top to bottom in the label stack. The value range for the out-label-value argument is 0, 3, and 16 to 1048575.

Usage guidelines

Execute this command only on the ingress node of a static SRLSP.

The outgoing labels represent an ordered list of labels allocated for the adjacencies or nodes that a static SRLSP traverses. The top label is the label that the ingress node allocates for the adjacency or destination prefix.

Examples

# Configure a static SRLSP named lsp1. Specify outgoing labels 100 and 200 for the SRLSP.

<Sysname> system-view

[Sysname] static-sr-mpls lsp lsp1 out-label 100 200

Related commands

static-sr-mpls adjacency

static-sr-mpls prefix

Use static-sr-mpls prefix to configure a prefix segment for static SR-MPLS.

Use undo static-sr-mpls prefix to delete a prefix segment.

Syntax

static-sr-mpls prefix prefix-path-name destination ip-address { mask | mask-length } in-label in-label-value [ { nexthop ip-address | outgoing-interface interface-type interface-number } out-label out-label-value ]

undo static-sr-mpls prefix prefix-path-name [ destination ip-address { mask | mask-length } in-label in-label-value [ nexthop ip-address | outgoing-interface interface-type interface-number ] ]

Default

No prefix segments exist.

Views

System view

Predefined user roles

network-admin

Parameters

prefix-path-name: Specifies the prefix segment name, a case-sensitive string of 1 to 67 characters.

destination ip-address: Specifies the destination IP address.

mask: Specifies the mask.

mask-length: Specifies the mask length, in the range of 0 to 32.

in-label label-value: Specifies the incoming label, in the range of 16000 to 24000.

nexthop ip-address: Specifies the next hop address.

outgoing-interface interface-type interface-number: Specifies an output interface by its type and number. The output interface must be a P2P interface.

out-label out-label-value: Specifies the outgoing label, in the range of 0, 3, and 16 to 1048575.

Usage guidelines

Execute this command on all nodes of a static SRLSP.

A prefix segment must use the next hop or output interface of the optimal route (non-BGP route) to the destination address of the prefix segment. You can configure multiple prefix segments to the destination address for load sharing if the optimal route has more than one next hops or output interfaces. To avoid configuration failure, make sure all prefix segments use the same prefix segment name, and incoming label.

If you specify only the prefix-path-name argument, the undo static-sr-mpls prefix command deletes all prefix segments with the specified name. If you specify all parameters, only the prefix segment that matches the specified name, destination IP address, and next hop or output interface is deleted.

Examples

# Configure a prefix segment named prefix1. Set the destination IP address, incoming label, outgoing label, and next hop to 2.2.2.2, 16000, 16001, and 10.0.0.2, respectively.

<Sysname> system-view

[Sysname] static-sr-mpls prefix prefix1 destination 2.2.2.2 32 in-label 16000 nexthop 10.0.0.2 out-label 16001

Related commands

display mpls static-sr-mpls prefix

tunnel-bfd detect-multiplier

Use tunnel-bfd detect-multiplier to set the tunnel BFD detection time multiplier for SRLSPs.

Use undo tunnel-bfd detect-multiplier to restore the default.

Syntax

tunnel-bfd detect-multiplier value

undo tunnel-bfd detect-multiplier

Default

The tunnel BFD detection time multiplier is not set for SRLSPs and the setting for the bfd multi-hop detect-multiplier command applies.

Views

Segment routing view

Predefined user roles

network-admin

Parameters

value: Specifies a detection time multiplier, which is the maximum number of consecutive BFD packets that can be discarded. The value range for this argument is 3 to 50.

Usage guidelines

The device sends BFD packets periodically to a peer. If the device does not receive BFD packets from the peer within the detection time, it determines that the BFD session with the peer has gone down.

The actual detection time is the detection time multiplier of the receiver multiplied by the actual BFD packet transmitting interval of the receiver.

This command takes effect only on the BFD sessions created by the tunnel-bfd enable command.

Examples

# Set the BFD detection time multiplier to 3.

<Sysname> system-view

[Sysname] segment-routing

[Sysname-segment-routing] tunnel-bfd detect-multiplier 3

Related commands

bfd multi-hop detect-multiplier (High Availability Command Reference)

tunnel-bfd enable

Use tunnel-bfd enable to enable tunnel BFD for all SRLSPs.

Use undo tunnel-bfd enable to restore the default.

Syntax

tunnel-bfd enable [ prefix-list prefix-list-name ] [ echo | nil-fec ]

undo tunnel-bfd enable

Default

Tunnel BFD is not enabled to verify the connectivity of SRLSPs.

Views

Segment routing view

Predefined user roles

network-admin

Parameters

prefix-list prefix-list-name: Specifies an IPv4 prefix list by the prefix list name, a case-sensitive string of 1 to 63 characters. The device can create tunnel BFD sessions only for the SRLSPs permitted by the specified IPv4 prefix list. If you do not specify an IPv4 prefix list, the device can create tunnel BFD sessions for all SRLSPs.

echo: Specifies the BFD echo packet mode. If you do not specify this keyword, the BFD control packet mode is used to verify SRLSP connectivity.

nil-fec: Encapsulates the Nil FEC in MPLS echo request packets when BFD control packet mode is used to detect SRLSPs. In LDP to SR interworking mode, the ingress node (source node) cannot determine whether the LDP LSP is connected to the SRLSP. When the ingress node uses MPLS BFD to detect LSPs, it encapsulates LDP FEC in MPLS echo request packets, which will fail the FEC type verification on the egress node (end-point node). Then, the BFD session will go down. To resolve this issue, specify the nil-fec keyword to enable the ingress node to encapsulate the Nil FEC in MPLS echo request packets. The egress node will not check the FEC type of packets encapsulated with the Nil FEC.

Usage guidelines

This command establishes tunnel BFD sessions to verify the connectivity of all SRLSPs.

A tunnel BFD session is a BFD session established for the primary and backup SRLSPs of a specific FEC (destination IP/mask). The BFD session is up as long as an SRLSP is available for the FEC. If both the primary and backup SRLSPs for the FEC are faulty, the BFD session goes down. BFD then quickly triggers a protection measure (such as MPLS L3VPN FRR) to switch traffic to other forwarding paths to reduce traffic loss.

If you configure both the mpls tunnel-bfd command for an SRLSP and the tunnel-bfd enable command for all SRLSPs, the mpls tunnel-bfd command takes effect for that SRLSP.

Examples

# Enable tunnel BFD to verify the connectivity of all SRLSPs.

<Sysname> system-view

[Sysname] segment-routing

[Sysname-segment-routing] tunnel-bfd enable

Related commands

mpls tunnel-bfd (for LSP) (MPLS Command Reference)

tunnel-bfd min-echo-receive-interval

Use tunnel-bfd min-echo-receive-interval to set the minimum interval for receiving BFD echo packets for SRLSP tunnel BFD.

Use undo tunnel-bfd min-echo-receive-interval to restore the default.

Syntax

tunnel-bfd min-echo-receive-interval interval

undo tunnel-bfd min-echo-receive-interval

Default

The minimum interval for receiving BFD echo packets is not set for SRLSP tunnel BFD. The interval set by the bfd multi-hop min-echo-receive-interval command applies.

Views

Segment routing view

Predefined user roles

network-admin

Parameters

interval: Specifies the minimum interval for receiving BFD echo packets, in milliseconds. The value range is 3 to 10000.

Usage guidelines

This command takes effect only on the echo mode BFD sessions created by the tunnel-bfd enable command.

Examples

# Set the minimum BFD echo packet receiving interval for SRLSP tunnel BFD to 450 milliseconds.

<Sysname> system-view

[Sysname] segment-routing

[Sysname-segment-routing] tunnel-bfd min-echo-receive-interval 450

Related commands

bfd multi-hop min-echo-receive-interval (High Availability Command Reference)

tunnel-bfd enable

tunnel-bfd min-receive-interval

Use tunnel-bfd min-receive-interval to set the minimum BFD packet receiving interval for SRLSP tunnel BFD.

Use undo tunnel-bfd min-receive-interval to restore the default.

Syntax

tunnel-bfd min-receive-interval interval

undo tunnel-bfd min-receive-interval

Default

The minimum interval for receiving BFD packets is not set for SRLSP tunnel BFD. The setting for the bfd multi-hop min-receive-interval command applies.

Views

Segment routing view

Predefined user roles

network-admin

Parameters

interval: Specifies the minimum interval for receiving BFD packets, in milliseconds. The value range is 3 to 10000.

Usage guidelines

Use this command to prevent the packet sending rate of the peer end from exceeding the packet receiving rate of the local end.

The actual BFD packet transmitting interval on the peer end is the greater value between the following values:

· Minimum interval for transmitting BFD packets on the peer end.

· Minimum interval for receiving BFD packets on the local end.

This command takes effect only on the BFD sessions created by the tunnel-bfd enable command.

Examples

# Set the minimum BFD packet receiving interval to 30 milliseconds for SRLSP tunnel BFD.

<Sysname> system-view

[Sysname] segment-routing

[Sysname-segment-routing] tunnel-bfd min-receive-interval 30

Related commands

bfd multi-hop min-receive-interval (High Availability Command Reference)

tunnel-bfd enable

tunnel-bfd min-transmit-interval

Use tunnel-bfd min-transmit-interval to set the minimum BFD packet transmitting interval for SRLSP tunnel BFD.

Use undo tunnel-bfd min-transmit-interval to restore the default.

Syntax

tunnel-bfd min-transmit-interval interval

undo tunnel-bfd min-transmit-interval

Default

The minimum interval for transmitting BFD packets is not set for tunnel BFD. The setting for the bfd multi-hop min-transmit-interval command applies.

Views

Segment routing view

Predefined user roles

network-admin

Parameters

interval: Specifies the minimum interval for transmitting BFD packets, in milliseconds. The value range is 3 to 10000.

Usage guidelines

Use this command to prevent the BFD packet sending rate from exceeding the packet receiving rate of the peer end.

The actual BFD packet transmitting interval on the local end is the greater value between the following values:

· Minimum interval for transmitting BFD packets on the local end.

· Minimum interval for receiving BFD packets on the peer end.

This command takes effect only on the BFD sessions created by the tunnel-bfd enable command.

Examples

# Set the minimum BFD packet transmitting interval to 30 milliseconds for SRLSP tunnel BFD.

<Sysname> system-view

[Sysname] segment-routing

[Sysname-segment-routing] tunnel-bfd min-transmit-interval 30

Related commands

bfd multi-hop min-transmit-interval (High Availability Command Reference)

tunnel-bfd enable

10-Segment Routing Command Reference

display bgp egress-engineering ipv4

display isis segment-routing routing-table

Application scenarios

Operating mechanism

Restrictions and guidelines

fast-reroute microloop-avoidance rib-update-delay

fast-reroute ti-lfa

global-block

local-block

Application scenarios

Restrictions and guidelines

peer egress-engineering

segment-routing mapping-server advertise-local

static-sr-mpls lsp

Intelligent Terminal Products

Product Support Services

Technical Service Solutions

Resource Center

Policy

Online Help

Become a Partner

Partner Policy & Program

Global Learning

Partner Sales Resources

Service Business

News & Events

Contact Us