Contents

Tunnel policy commands· 1

display mpls tunnel 2

preferred-path· 3

select-seq load-balance-number 5

tunnel-policy (system view) 6

 

Tunnel policy commands

The following compatibility matrixes show the support of hardware platforms for tunnel policy:

 

Haredware	Tunnel policy compatibility
MSR810, MSR810-W, MSR810-W-DB, MSR810-LM, MSR810-W-LM, MSR810-10-PoE, MSR810-LM-HK, MSR810-W-LM-HK, MSR810-LM-CNDE-SJK, MSR810-CNDE-SJK	Yes
MSR810-LMS, MSR810-LUS	No
MSR810-LMS-EA, MSR810-LME	Yes
MSR2600-6-X1, MSR2600-10-X1	Yes
MSR 2630	Yes
MSR3600-28, MSR3600-51	Yes
MSR3600-28-SI, MSR3600-51-SI	No
MSR3600-28-X1, MSR3600-28-X1-DP, MSR3600-51-X1, MSR3600-51-X1-DP	Yes
MSR3610-I-DP, MSR3610-IE-DP, MSR3610-IE-ES, MSR3610-IE-EAD	Yes
MSR3610-X1, MSR3610-X1-DP, MSR3610-X1-DC, MSR3610-X1-DP-DC	Yes
MSR 3610, MSR 3620, MSR 3620-DP, MSR 3640, MSR 3660	Yes
MSR3610-G, MSR3620-G	Yes

‌

Haredware	Tunnel policy compatibility
MSR810-W-WiNet, MSR810-LM-WiNet	Yes
MSR830-4LM-WiNet	Yes
MSR830-5BEI-WiNet, MSR830-6EI-WiNet, MSR830-10BEI-WiNet	Yes
MSR830-6BHI-WiNet, MSR830-10BHI-WiNet	Yes
MSR2600-6-WiNet, MSR2600-10-X1-WiNet	Yes
MSR2630-WiNet	Yes
MSR3600-28-WiNet	Yes
MSR3610-X1-WiNet	Yes
MSR3610-WiNet, MSR3620-10-WiNet, MSR3620-DP-WiNet, MSR3620-WiNet, MSR3660-WiNet	Yes

‌

Haredware	Tunnel policy compatibility
MSR2630-XS	Yes
MSR3600-28-XS	Yes
MSR3610-XS	Yes
MSR3620-XS	Yes
MSR3610-I-XS	Yes
MSR3610-IE-XS	Yes

‌

Hardware	Tunnel policy compatibility
MSR810-LM-GL	Yes
MSR810-W-LM-GL	Yes
MSR830-6EI-GL	Yes
MSR830-10EI-GL	Yes
MSR830-6HI-GL	Yes
MSR830-10HI-GL	Yes
MSR2600-6-X1-GL	Yes
MSR3600-28-SI-GL	No

‌

display mpls tunnel

Use display mpls tunnel to display tunnel information.

Syntax

display mpls tunnel { all | statistics | [ vpn-instance vpn-instance-name ] destination { ipv4-address | ipv6-address } }

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

all: Displays all tunnels. GRE and MPLS TE tunnel information is displayed only when the network layer is up.

statistics: Displays tunnel statistics.

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 a VPN instance, this command displays tunnel information for the public network.

destination: Displays the tunnel destined for the specified address.

ipv4-address: Specifies the tunnel destination IPv4 address.

ipv6-address: Specifies the tunnel destination IPv6 address.

Examples

# Display information about all tunnels.

<Sysname> display mpls tunnel all

Destination      Type     Tunnel/NHLFE      VPN Instance

2.2.2.2          LSP      NHLFE1024         -

3.3.3.3          CRLSP    Tunnel2           -

Table 1 Command output

Field	Description
Destination	Tunnel destination address.
Type	Tunnel type: LSP, GRE, CRLSP, or SRLSP.
Tunnel/NHLFE	Tunnel, tunnel bundle, or NHLFE entry. NHLFEnumber represents the ingress LSP that matches the NHLFE entry with NID of number.
VPN Instance	VPN instance name. If the tunnel belongs to the public network, this field displays a hyphen (-).

 

# Display tunnel statistics.

<Sysname> display mpls tunnel statistics

LSP  :     1

GRE  :     0

CRLSP:     0

SRLSP:     0

Table 2 Command output

Field	Description
LSP	Number of LSP tunnels.
GRE	Number of GRE tunnels.
CRLSP	Number of CRLSP tunnels.
SRLSP	Number of SRLSP tunnels.

 

preferred-path

Use preferred-path to configure a tunnel or a tunnel bundle as a preferred tunnel.

Use undo preferred-path to remove the preferred tunnel setting for a tunnel or tunnel bundle.

Syntax

preferred-path { tunnel number | tunnel-bundle number }

undo preferred-path { tunnel number | tunnel-bundle number }

Default

No preferred tunnels are configured.

Views

Tunnel policy view

Predefined user roles

network-admin

Parameters

tunnel number: Specifies an MPLS TE tunnel or a GRE tunnel by its tunnel interface number. The value range for the tunnel interface number is 0 to 10239.

tunnel-bundle number: Specifies a tunnel bundle by its tunnel bundle interface number. The value range varies by device model.

The following compatibility matrixes show the support and value ranges for the tunnel bundle interface number:

 

Hardware	Parameter compatibility	Value range
MSR810, MSR810-W, MSR810-W-DB, MSR810-LM, MSR810-W-LM, MSR810-10-PoE, MSR810-LM-HK, MSR810-W-LM-HK, MSR810-LM-CNDE-SJK, MSR810-CNDE-SJK	Yes	0 to 1023
MSR810-LMS, MSR810-LUS	No	N/A
MSR810-LMS-EA, MSR810-LME	Yes	0 to 1023
MSR2600-6-X1, MSR2600-10-X1	Yes	0 to 1023
MSR 2630	Yes	0 to 1023
MSR3600-28, MSR3600-51	Yes	0 to 1023
MSR3600-28-SI, MSR3600-51-SI	No	N/A
MSR3600-28-X1, MSR3600-28-X1-DP, MSR3600-51-X1, MSR3600-51-X1-DP	Yes	0 to 1023
MSR3610-I-DP, MSR3610-IE-DP, MSR3610-IE-ES, MSR3610-IE-EAD	Yes	0 to 2047
MSR3610-X1, MSR3610-X1-DP, MSR3610-X1-DC, MSR3610-X1-DP-DC	Yes	0 to 2047
MSR 3610, MSR 3620, MSR 3620-DP, MSR 3640, MSR 3660	Yes	0 to 2047
MSR3610-G, MSR3620-G	Yes	0 to 2047

‌

Hardware	Parameter compatibility	Value range
MSR810-W-WiNet, MSR810-LM-WiNet	Yes	0 to 1023
MSR830-4LM-WiNet	Yes	0 to 1023
MSR830-5BEI-WiNet, MSR830-6EI-WiNet, MSR830-10BEI-WiNet	Yes	0 to 1023
MSR830-6BHI-WiNet, MSR830-10BHI-WiNet	Yes	0 to 1023
MSR2600-6-WiNet, MSR2600-10-X1-WiNet	Yes	0 to 1023
MSR2630-WiNet	Yes	0 to 1023
MSR3600-28-WiNet	Yes	0 to 1023
MSR3610-X1-WiNet	Yes	0 to 1023
MSR3610-WiNet, MSR3620-10-WiNet, MSR3620-DP-WiNet, MSR3620-WiNet, MSR3660-WiNet	Yes	0 to 1023

‌

Hardware	Parameter compatibility	Value range
MSR2630-XS	Yes	0 to 1023
MSR3600-28-XS	Yes	0 to 1023
MSR3610-XS	Yes	0 to 2047
MSR3620-XS	Yes	0 to 2047
MSR3610-I-XS	Yes	0 to 2047
MSR3610-IE-XS	Yes	0 to 2047

‌

Hardware	Parameter compatibility	Value range
MSR810-LM-GL	Yes	0 to 1023
MSR810-W-LM-GL	Yes	0 to 1023
MSR830-6EI-GL	Yes	0 to 1023
MSR830-10EI-GL	Yes	0 to 1023
MSR830-6HI-GL	Yes	0 to 1023
MSR830-10HI-GL	Yes	0 to 1023
MSR2600-6-X1-GL	Yes	0 to 1023
MSR3600-28-SI-GL	No	N/A

‌

Usage guidelines

As a best practice for an MPLS VPN, configure a preferred tunnel and make sure the destination address of the tunnel/tunnel bundle interface identifies the peer PE. In this method, the local PE forwards traffic destined for the peer PE over the preferred MPLS TE tunnel, GRE tunnel, or tunnel bundle.

For a tunnel policy to solely use a tunnel or tunnel bundle, do not configure the tunnel or tunnel bundle as the preferred tunnel in other tunnel policies.

If you configure multiple preferred tunnels that have the same destination address in a tunnel policy, only the first configured tunnel takes effect. If the first tunnel is not available, the second tunnel is used, and so forth. No load balancing will be performed on these tunnels.

You can configure a maximum of 128 preferred tunnels in a tunnel policy.

Examples

# Configure tunnel 1 and tunnel 2 as preferred tunnels for tunnel policy policy1.

<Sysname> system-view

[Sysname] tunnel-policy policy1

[Sysname-tunnel-policy-policy1] preferred-path tunnel 1

[Sysname-tunnel-policy-policy1] preferred-path tunnel 2

select-seq load-balance-number

Use select-seq load-balance-number to configure the tunnel selection order and set the number of tunnels for load balancing.

Use undo select-seq to restore the default.

Syntax

select-seq [ strict ] { cr-lsp | gre | lsp | sr-lsp } * load-balance-number number

undo select-seq

Default

The device selects only one tunnel in LSP-GRE-CRLSP-SRLSP order.

Views

Tunnel policy view

Predefined user roles

network-admin

Parameters

strict: Uses the same type of tunnels for load balancing.

cr-lsp: Uses CRLSP tunnels.

gre: Uses GRE tunnels.

lsp: Uses LSP tunnels.

sr-lsp: Uses SRLSP tunnels.

load-balance-number number: Specifies the number of tunnels for load balancing. The value range for the number argument is 1 to 32.

Usage guidelines

A tunnel type closer to the select-seq keyword has a higher priority. The strict keyword determines whether VPN can use a hybrid of the specified types of tunnels for load balancing.

For example, the select-seq lsp cr-lsp load-balance-number 3 command specifies three tunnels for load balancing and gives LSP tunnels higher priority over CRLSP tunnels.

·     If you do not specify the strict keyword, VPN can use CRLSP tunnels to remedy the deficiency of LSP tunnels.

·     If you specify the strict keyword, VPN uses only one type of tunnels. It uses CRLSP tunnels only if no LSP tunnels are available.

Tunnels selected by this method are not fixed, making it hard to plan VPN traffic. As a best practice, do not use this method.

When you configure both the select-seq load-balance-number and preferred-path commands for a tunnel policy, the tunnel policy selects tunnels in the following steps:

1.     If the destination address of the preferred tunnel identifies a peer PE, the tunnel policy uses the preferred tunnel to forward traffic destined for the peer PE.

2.     If not, the tunnel policy selects tunnels as configured by the select-seq load-balance-number command.

Examples

# Configure tunnel policy policy1 to use only CRLSP tunnels, and set the load balancing number to 2.

<Sysname> system-view

[Sysname] tunnel-policy policy1

[Sysname-tunnel-policy-policy1] select-seq cr-lsp load-balance-number 2

tunnel-policy (system view)

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

Use undo tunnel-policy to delete a tunnel policy.

Syntax

tunnel-policy tunnel-policy-name [ default ]

undo tunnel-policy tunnel-policy-name

Default

No tunnel policies exist.

Views

System view

Predefined user roles

network-admin

Parameters

tunnel-policy-name: Specifies a name for the tunnel policy, a case-sensitive string of 1 to 19 characters.

default: Uses the policy as the global tunnel policy.

Usage guidelines

The device supports only one global tunnel policy.

By default, a tunnel policy selects only one tunnel in LSP—GRE—CRLSP—SRLSP order.

An MPLS VPN uses the global tunnel policy if it is not bound with a specific tunnel policy or the bound policy does not exist. If the bound policy exists but is null, the MPLS VPN selects only one tunnel in LSP—GRE—CRLSP—SRLSP order.

Examples

# Create tunnel policy policy1 and enter its view.

<Sysname> system-view

[Sysname] tunnel-policy policy1

[Sysname-tunnel-policy-policy1]