No relevant resource is found in the selected language.
Your browser version is too early. Some functions of the website may be unavailable. To obtain better user experience, upgrade the browser to the latest version.
This document describes MPLS configurations supported by the switch, including the principle and configuration procedures of static LSPs, MPLS LDP, MPLS QoS, MPLS TE, and MPLS common features, and provides configuration examples.
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document.
Note: Even the most advanced machine translation cannot match the quality of professional translators.
Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
(Optional) Referencing the CR-LSP Attribute Template to Set
Up a CR-LSP
(Optional) Referencing the CR-LSP Attribute Template to Set
Up a CR-LSP
Context
You can create a CR-LSP by using the following methods:
Creating a CR-LSP without using a CR-LSP attribute template
Creating a CR-LSP by using a CR-LSP attribute template
It is recommended to use a CR-LSP attribute template to set up a
CR-LSP because this method has the following advantages:
A CR-LSP attribute template can greatly simplify the configurations
of CR-LSPs.
A maximum of three CR-LSP attribute templates can be created
for a hot-standby CR-LSP or an ordinary backup CR-LSP. You can set
up a hot-standby CR-LSP or an ordinary backup CR-LSP with different
path options. (Among the three attribute templates, the template with
the smallest sequence number is first used. If the setup fails, the
template with a greater sequence number is used.)
If configurations of a CR-LSP attribute template are modified,
configurations of the CR-LSPs established by using the CR-LSP attribute
template are automatically updated, which makes the configurations
of CR-LSPs more flexible.
The preceding two methods can be used together.
If the TE attribute configured in the tunnel interface view and the
TE attribute configured through a CR-LSP attribute template coexist,
the former takes precedence over the latter.
Perform
the following configurations on the ingress node of an MPLS TE tunnel.
You can use a CR-LSP attribute template to set up the primary
CR-LSP, hot-standby CR-LSP, and ordinary backup CR-LSP.
Procedure
Configure a CR-LSP attribute template.
Run system-view
The system view is displayed.
Run lsp-attributelsp-attribute-name
A CR-LSP attribute template
is created and the LSP attribute view is displayed.
A CR-LSP attribute template can be deleted only
when it is not used by any tunnel interface.
(Optional) Run bandwidth { ct0ct0-bandwidth | ct1ct1-bandwidth }
The bandwidth is set for the CR-LSP
attribute template.
Perform this step to provide bandwidth protection
for services transmitted on a TE tunnel established using this template.
(Optional) Run explicit-pathpath-name
An explicit path
is configured for the CR-LSP attribute template.
Perform this
step to control the path over which a TE tunnel is established.
(Optional) Run affinity propertyaffinity-value [ maskmask-value ]
The affinity attribute
is set for the CR-LSP attribute template.
By default, both the
affinity value and the affinity mask are 0x0.
This step helps
you control the path over which a TE tunnel is established.
(Optional) Run prioritysetup_priority_value [ hold_priority_value ]
The setup
priority and hold priority are set for the CR-LSP attribute template.
By default, both the setup priority and the hold priority are
7.
If resources are insufficient, setting the setup
and hold priority values helps a device release resources used by
LSPs with lower priorities and use the released resources to establish
LSPs with higher priorities.
(Optional) Run hop-limithop-limit
The hop limit is set for the CR-LSP
attribute template.
By default, the hop limit is 32.
(Optional) Run fast-reroute [ bandwidth ]
FRR is enabled for the CR-LSP
attribute template.
By default, FRR is disabled.
FRR is
recommended for networks requiring high reliability.
Before enabling or disabling FRR for the CR-LSP attribute template,
note the following:
After FRR is enabled, the system automatically records routes
for the CR-LSP.
After FRR is disabled, attributes of the bypass tunnel are automatically
deleted.
The undo mpls te record-route command can take effect
only when FRR is disabled.
(Optional) Run record-route [ label ]
The system is configured to record
routes for the CR-LSP attribute template.
By default, the system
does not record routes for the CR-LSP attribute template.
Perform
this step to view label information and the number of hops on a path
over which a TE tunnel is established.
The bypass tunnel attributes are configured for the CR-LSP attribute
template.
By default, the bypass tunnel attributes are not configured.
Run commit
Configurations of the CR-LSP attribute template are committed.
When the CR-LSP attribute template is used to set up a CR-LSP:
The CR-LSP is removed and a new CR-LSP is created if the Break-Before-Make
attribute (the priority attribute) of the CR-LSP attribute template
is modified.
The CR-LSP is removed after an eligible CR-LSP is created and
traffic switches to the new CR-LSP if the Make-Before-Break attribute
of the CR-LSP attribute template is modified.
Set up a CR-LSP by using a CR-LSP attribute template.
Run system-view
The system view is displayed.
Run interface tunnelinterface-number
The tunnel interface
view is displayed.
Run mpls te primary-lsp-constraint { dynamic | lsp-attributelsp-attribute-name }
The primary CR-LSP
is set up through the specified CR-LSP attribute template.
If dynamic is used, it indicates that when a CR-LSP attribute
template is used to set up a primary CR-LSP, all attributes in the
template use the default values.
(Optional) Run mpls te hotstandby-lsp-constraintnumber { dynamic | lsp-attributelsp-attribute-name }
The hot-standby CR-LSP is set up by using the specified
CR-LSP attribute template.
A maximum of three CR-LSP attribute
templates can be used to set up a hot-standby CR-LSP. The hot-standby
CR-LSP must be consistent with the primary CR-LSP in the attributes
of the setup priority, hold priority, and bandwidth type. To set up
a hot-standby CR-LSP, you should keep on attempting to use CR-LSP
attribute templates one by one in ascending order of the number of
the attribute templates until the hot-standby CR-LSP is set up.
If dynamic is used, it indicates that
the hot-standby CR-LSP is assigned the same bandwidth and priority
as the primary CR-LSP, but specified with a different path from the
primary CR-LSP.
(Optional) Run mpls te backup hotstandby-lsp-constraintwtrinterval
The Wait to Restore (WTR) time is set for the traffic
to switch back from the hot-standby CR-LSP to the primary CR-LSP.
By default, the WTR time for the traffic to switch back from the
hot-standby CR-LSP to the primary CR-LSP is 10 seconds.
The hot-standby CR-LSP specified in the mpls te backup hotstandby-lsp-constraintwtr command must be an existing one established
by running the mpls te hotstandby-lsp-constraint command.
(Optional) Run mpls te ordinary-lsp-constraintnumber { dynamic | lsp-attributelsp-attribute-name }
The ordinary backup CR-LSP is set up by using the specified
CR-LSP attribute template.
A maximum of three CR-LSP attribute
templates can be used to set up an ordinary backup CR-LSP. The ordinary
backup CR-LSP must be consistent with the primary CR-LSP in the attributes
of the setup priority, hold priority, and bandwidth type. To set up
an ordinary backup CR-LSP, you should keep on attempting to use CR-LSP
attribute templates one by one in ascending order of the number of
the attribute template until the ordinary backup CR-LSP is set up.
If dynamic is used, it indicates that
the ordinary backup CR-LSP is assigned the same bandwidth and priority
as the primary CR-LSP.
(Optional) Run mpls te backup ordinary-lsp-constraintlock
The attribute
template of the ordinary backup CR-LSP is locked.
By default, the attribute template of the ordinary backup CR-LSP
is not locked.
Before running this command, you
must run the mpls te ordinary-lsp-constraint command to reference the CR-LSP attribute template to set
up an ordinary backup CR-LSP.
