No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

Command Reference

S7700 and S9700 V200R011C10

This document describes all the configuration commands of the device, including the command function, syntax, parameters, views, default level, usage guidelines, examples, and related commands.
Rate and give feedback:
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).
MPLS compatible command

MPLS compatible command

explicit-path (upgrade-compatible command)

Function

Using the explicit-path command, you can configure an explicit path of a tunnel.

By default, no explicit path of a tunnel is configured.

Format

explicit-path path-name { enable | disable }

Parameters

Parameter Description Value
path-name Indicates the name of an explicit path. The value is a string of 1 to 31 characters.
enable Enables the explicit path of a tunnel. -
disable Disables the explicit path of a tunnel. -

Views

System view

Default Level

2: Configuration level

Usage Guidelines

You can configure an explicit path only after MPLS TE is enabled.

The addresses of the hops along the explicit path cannot overlap or loops cannot occur. If a loop occurs, CSPF detects the loop and fails to calculate the path.

When the explicit path is in use, you cannot perform the following operations:
  • Run the explicit-path path-name disable command to disable the explicit path.
  • Run the undo explicit-path command to delete the explicit path.

Example

# Create an explicit path named path1.

<HUAWEI> system-view
[HUAWEI] mpls
[HUAWEI-mpls] mpls te
[HUAWEI-mpls] quit
[HUAWEI] explicit-path path1 enable
[HUAWEI-explicit-path-path1] 

mpls rsvp-te authentication handshake (upgrade-compatible command)

Function

The mpls rsvp-te authentication handshake command configures the RSVP-TE handshake mechanism and sets a local password.

The undo mpls rsvp-te authentication handshake command deletes the RSVP-TE handshake mechanism configuration.

By default, no RSVP-TE handshake mechanism is configured.

Format

mpls rsvp-te authentication handshake local-secret

undo mpls rsvp-te authentication handshake

Parameters

Parameter Description Value
local-secret Specifies the local password. The value is a string of 8 to 40 characters without spaces. It has no default value.

Views

VLANIF interface view, Ethernet interface view, GE interface view, XGE interface view, 40GE interface view, Eth-trunk interface view, RSVP-TE neighbor view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

Enhanced RSVP authentication can be configured to improve the system security and the capability to authenticate users in the unfavorable environment such as network congestion. Enhanced RSVP authentication functions are as follows:
  • Sets the sliding window size for RSVP authentication messages.
  • Configures the RSVP-TE handshake mechanism and sets the local password.

Traditional RSVP authentication is used to prevent an unauthorized remote node from setting up a neighbor relationship with the local node. It also prevents attacks (such as maliciously reserving a large number of bandwidth resources) initiated by a remote node after the remote node constructs pseudo RSVP messages to set up an RSVP neighbor relationship with the local node. Traditional RSVP authentication, however, cannot prevent anti-replay attacks or prevent the problem of neighbor relationship termination due to RSVP message disorder.

In an unfavorable environment, the mpls rsvp-te authentication handshake command can be used to configure the RSVP-TE handshake mechanism and sets the local password to prevent anti-replay and improve network security.

Prerequisites

The RSVP authentication function must have been enabled by running the mpls rsvp-te authentication { { cipher | plain } auth-key | keychain keychain-name } command in the interface view or the MPLS RSVP-TE neighbor view.

Precautions

local-secret is valid only on the local device and can be different from local-secret configured on neighbors.

Example

# Configure the RSVP-TE handshake mechanism.
<HUAWEI> system-view
[HUAWEI] interface vlanif 100
[HUAWEI-Vlanif100] mpls
[HUAWEI-Vlanif100] mpls te
[HUAWEI-Vlanif100] mpls rsvp-te
[HUAWEI-Vlanif100] mpls rsvp-te authentication cipher beijing123
[HUAWEI-Vlanif100] mpls rsvp-te authentication handshake 12345678
# Configure the RSVP-TE handshake mechanism.
<HUAWEI> system-view
[HUAWEI] interface gigabitethernet 1/0/1
[HUAWEI-GigabitEthernet1/0/1] undo portswitch
[HUAWEI-GigabitEthernet1/0/1] mpls
[HUAWEI-GigabitEthernet1/0/1] mpls te
[HUAWEI-GigabitEthernet1/0/1] mpls rsvp-te
[HUAWEI-GigabitEthernet1/0/1] mpls rsvp-te authentication cipher beijing123
[HUAWEI-GigabitEthernet1/0/1] mpls rsvp-te authentication handshake 12345678

mpls rsvp-te send-message (upgrade-compatible command)

Function

The mpls rsvp-te send-message command configures the formats of objects in a sent message.

The undo mpls rsvp-te send-message command restores the default configuration.

By default, the formats of objects in the sent message are not configured.

Format

mpls rsvp-te send-message suggest-label exclude

undo mpls rsvp-te send-message suggest-label exclude

Parameters

Parameter Description Value
suggest-label exclude Indicates that an RSVP message does not carry the suggest-label object. -

Views

MPLS view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

The mpls rsvp-te send-message command controls the formats of objects in the messages sent by nodes. If required, you can use this command to adjust the transmission of messages so that downstream nodes can use the carried object format in processing.

Precautions

The modification takes effect only for new LSPs.

Configurations of the four formats of objects in a sent message can take effect simultaneously.

Example

# Exclude the suggest-label object from a message.
<HUAWEI> system-view
[HUAWEI] mpls
[HUAWEI-mpls] mpls rsvp-te send-message suggest-label exclude

mpls te max-reservable-bandwidth (upgrade-compatible command)

Function

The mpls te max-reservable-bandwidth command sets the maximum reservable bandwidth of a link.

The maximum reservable bandwidth of a link is not configured by default.

Format

mpls te max-reservable-bandwidth bw-value [ bc1 bc1-bw-value ]

Parameters

Parameter Description Value
bw-value Specifies the maximum reservable link bandwidth.

The value is an integer ranging from 0 to 40000000, in kbit/s. The default value is 0.

bc1 bc1-bw-value Specifies the maximum reservable bandwidth for a BC1 link.

The value is an integer ranging from 0 to 40000000, in kbit/s. The default value is 0.

Views

Interface view

Default Level

2: Configuration level

Usage Guidelines

This command is available to aid upgrade compatibility. It can only be run during the configuration restoration phase of the upgrade.

After an upgrade, this command is no longer supported, and it is replaced by the mpls te bandwidth max-reservable-bandwidth command.

mpls te bypass-tunnel bandwidth (upgrade-compatible command)

Function

Using the mpls te bypass-tunnel bandwidth command, you can configure the bypass LSP bandwidth.

By default, no bypass LSP bandwidth is configured.

Format

mpls te bypass-tunnel bandwidth { bandwidth | { bc0 | bc1 } { bandwidth | un-limited } }

Parameters

Parameter Description Value
bandwidth Specifies the bandwidth that the bypass tunnel can protect. The value is an integer that ranges from 1 to 32000000, in kbit/s.
bc0 Indicates the BC0 bandwidth (global bandwidth) that the bypass tunnel can protect. -
bc1 Indicates the BC1 bandwidth (subaddress pool bandwidth) that the bypass tunnel can protect. -
un-limited Indicates that there is no limit on the total bandwidth that can be protected. -

Views

Tunnel interface view

Default Level

2: Configuration level

Usage Guidelines

The total bandwidth of LSPs protected by the bypass tunnel is not more than the bandwidth of the primary tunnel. When multiple bypass tunnels exist, the system selects a single bypass tunnel through the best-fit algorithm.

The total bandwidth of all the LSPs protected by the bypass tunnel is not greater than the bandwidth of the primary tunnel. When multiple bypass tunnels exist, the system determines the bypass tunnel through the best-fit algorithm.

Example

# Configure Tunnel1 to protect the LSPs that use the BC0 bandwidth and set no limit on the bandwidth to be protected.

<HUAWEI> system-view
[HUAWEI] interface tunnel 1
[HUAWEI-Tunnel1] tunnel-protocol mpls te
[HUAWEI-Tunnel1] destination 2.2.2.2
[HUAWEI-Tunnel1] mpls te tunnel-id 100
[HUAWEI-Tunnel1] mpls te bypass-tunnel bandwidth bc0 un-limited
[HUAWEI-Tunnel1] mpls te commit

mpls te protect-switch manual (upgrade-compatible command)

Function

The mpls te protect-switch manual command sends a manual switchover request to a specified tunnel.

By default, no manual switching request for a specified tunnel is configured.

Format

mpls te protect-switch manual [ work-lsp | protect-lsp ]

Parameters

Parameter Description Value
work-lsp Switches traffic manually to the primary tunnel. -
protect-lsp Switches traffic manually to a protection tunnel. -

Views

Tunnel interface view

Default Level

2: Configuration level

Usage Guidelines

This command is available to aid upgrade compatibility. It can only be run during the configuration restoration phase of the upgrade.

After an upgrade, this command is no longer supported, and it is replaced by the mpls te protect-switch manual command.

mpls te retry (upgrade-compatible command)

Function

The mpls te retry command sets the number of times for reattempting to set up a tunnel.

The undo mpls te retry command restores the default setting.

The default number of times for reattempting to set up a tunnel is 5.

Format

mpls te retry times

undo mpls te retry

Parameters

Parameter Description Value
times Specifies the number of times for reattempting to set up a tunnel. An integer ranging from 0 to 4294967295.

Views

Tunnel interface view

Default Level

2: Configuration level

Usage Guidelines

After a TE tunnel is established, it is kept Up by periodically sending a Path message from the local node to its neighbor and receiving a Resv message reply from the neighbor. If no Resv message is received after the specified interval at which a tunnel is re-established, the local node considers the tunnel Down and then reattempts to establish the tunnel.

Example

# Set the times for attempting to set up a tunnel to 1.

<HUAWEI> system-view
[HUAWEI] interface tunnel 1
[HUAWEI-Tunnel1] tunnel-protocol mpls te
[HUAWEI-Tunnel1] mpls te retry 1

mpls te reverse-lsp (upgrade-compatible command)

Function

Using the mpls te reverse-lsp command, you can configure a reverse LSP for a tunnel on a specified tunnel interface. The reverse LSP and the forward LSP form a bidirectional LSP.

By default, no reverse LSP is configured on a tunnel interface.

Format

mpls te reverse-lsp lsp-name lsp-name

Parameters

Parameter Description Value
lsp-name lsp-name Specifies the name of a reverse LSP on a specified tunnel. The value is a string of 1 to 19 characters, spaces not supported.

Views

Tunnel interface view

Default Level

2: Configuration level

Usage Guidelines

On a tunnel interface, the configured incoming interface of the reverse LSP and the configured outgoing interface of the forward LSP must be the same. Otherwise, the configuration is incorrect.

Example

# Set a reverse LSP named lsp1 on Tunnel 1.

<HUAWEI> system-view
[HUAWEI] interface tunnel 1
[HUAWEI-Tunnel1] mpls te reverse-lsp lsp-name lsp1
[HUAWEI-Tunnel1] mpls te commit

snmp-agent trap enable (MPLS) (upgrade-compatible command)

Function

The snmp-agent trap enable command enables SNMP traps with a related parameter.

The undo snmp-agent trap enable command disables SNMP traps with a related parameter.

Format

snmp-agent trap enable { static-lsp | ldp | lsp [ mplsxcup | mplsxcdown ] | tunnel-ps | te { tunnel-reop | te-frr [ private ] | hot-standby | ordinary | bandwidth-change } | [ te ] tunnel | mpls-oam }

undo snmp-agent trap enable { static-lsp | ldp | lsp [ mplsxcup | mplsxcdown ] | tunnel-ps | te { tunnel-reop | te-frr [ private ] | hot-standby | ordinary | bandwidth-change } | [ te ] tunnel | mpls-oam }

Parameters

Parameter Description Value
static-lsp Enables the trap of static LSPs. -
ldp Enables LDP traps. -
lsp mplsxcup Enables the mplsXCUp trap. -
lsp mplsxcdown Enables the mplsXCDown trap. -
tunnel-ps Enables the TE protection switching trap. -
te tunnel-reop Enables trap of the TE route re-optimization. -
te te-frr Enables the public trap of TE FRR. -
te-frr private Enables the private trap of TE FRR. -
te hot-standby Enables the trap of the hot-standby CR-LSP. -
te ordinary Enables the trap of the ordinary CR-LSP. -
bandwidth-change Enables the system to send related private traps when the tunnel bandwidth changes. -
tunnel Enables the trap of the tunnel. -
mpls-oam Enables the trap of MPLS OAM. -

Views

System view

Default Level

2: Configuration level
NOTE:

If mpls-oam is specified, the default level is management level.

Usage Guidelines

By default, the trap function is disabled in the process of the MPLS LSP establishment.

To check the status of an LSP, run the snmp-agent trap enable lsp { mplsxcup | mplsxcdown } command when mplsXCUp or mplsXCDown is enabled.

After the undo snmp-agent trap enable command is run, information about mplsXCUp or mplsXCDown is not displayed, and the status of the trap is unchanged. When you run the snmp-agent trap enable command again, information about the restored trap is displayed.

Example

# Enable the private trap of TE FRR.

<HUAWEI> system-view
[HUAWEI] snmp-agent trap enable te te-frr private

# Enable the mplsXCUp trap.

<HUAWEI> system-view
[HUAWEI] snmp-agent trap enable lsp mplsxcup
 Warning: Enabling the alarm function will lead to the generation of excessive a
larms. Continue? [Y/N]

snmp-agent trap enable feature-name ldp (upgrade-compatible command)

Function

The snmp-agent trap enable feature-name ldp command enables the trap for the MPLS LDP module.

The undo snmp-agent trap enable feature-name ldp command disables the trap for the MPLS LDP module.

By default, the trap is disabled for the MPLS LDP module.

Format

snmp-agent trap enable feature-name ldp trap-name { session-down | session-up }

undo snmp-agent trap enable feature-name ldp trap-name { session-down | session-up }

Parameters

Parameter Description Value
trap-name Enables the trap of MPLS LDP events of a specified type. -
session-down Enables the trap of the event that an LDP session goes Down in the MIB. -
session-up Enables the trap of the event that an LDP session goes Up in the MIB. -

Views

System view

Default Level

2: Configuration level

Usage Guidelines

Run the snmp-agent trap enable feature-name ldp command to enable the LDP session trap. Currently, all traps of the MPLS LDP module are non-excessive trap. The frequent LDP session status changes do not trigger a large number of traps.

Example

# Enable the trap of the event that an LDP session is reestablished.

<HUAWEI> system-view
[HUAWEI] snmp-agent trap enable feature-name ldp trap-name session-up

static-cr-lsp ingress bandwidth (upgrade-compatible command)

Function

Using the static-cr-lsp ingress bandwidth command, you can configure a static CR-LSP and specify its bandwidth on the ingress LSR.

By default, no static CR-LSP on the ingress LSR is configured.

Format

static-cr-lsp ingress { tunnel-interface tunnel interface-number | tunnel-name } destination destination-address { nexthop next-hop-address | outgoing-interface interface-type interface-number } * out-label out-label bandwidth { bc0 | bc1 } bandwidth

Parameters

Parameter Description Value
tunnel-interface tunnel interface-number Specifies the tunnel interface of a static CR-LSP. interface-number indicates the tunnel interface number. -
tunnel-name Specifies the name of a CR-LSP. The name is a string of 1 to 19 case-sensitive characters, spaces and abbreviation not supported. If you use the interface Tunnel 2 command to create a tunnel interface for a static CR-LSP, the tunnel name in the static-cr-lsp ingress command must be formatted as "Tunnel2", otherwise, the tunnel cannot be created. There is no such a limit for the transit node and egress node.
destination destination-address Specifies the destination IP address of a static CR-LSP. -
nexthop next-hop-address Specifies the next-hop IP address of a static CR-LSP. -
outgoing-interface interface-type interface-number Specifies the type and number of an outgoing interface. This parameter is only applicable to a P2P link. -
out-label out-label Specifies the value of an outgoing label. out-label is an integer ranging from 16 to 1048575.
bc0 Specifies BC0 bandwidth of a static CR-LSP. -
bc1 Specifies BC1 bandwidth of a static CR-LSP. -
bandwidth Specifies the bandwidth required by a CR-LSP. The value ranges from 0 to 4000000000, in kbit/s. The default value is 0.

Views

System view

Default Level

2: Configuration level

Usage Guidelines

Before setting up an MPLS TE tunnel through a static CR-LSP, configure a static route or an IGP to ensure connectivity between LSRs, and enable basic MPLS and MPLS TE functions.

Example

# Configure the static CR-LSP named Tunnel1, with the destination IP address being 10.1.3.1, the next-hop address being 10.1.1.2, the outgoing label being 237, and the required bandwidth being 20 kbit/s from BC0 on the ingress.

<HUAWEI> system-view
[HUAWEI] static-cr-lsp ingress tunnel-interface Tunnel 1 destination 10.1.3.1 nexthop 10.1.1.2 out-label 237 bandwidth bc0 20

static-cr-lsp transit bandwidth (upgrade-compatible command)

Function

Using the static-cr-lsp transit bandwidth command, you can configure a static CR-LSP and specify its bandwidth on a transit LSR.

By default, no static CR-LSP on a transit LSR is configured.

Format

static-cr-lsp transit lsp-name [ incoming-interface interface-type interface-number ] in-label in-label { nexthop next-hop-address | outgoing-interface interface-type interface-number } * out-label out-label bandwidth { bc0 | bc1 } bandwidth [ description description ]

Parameters

Parameter Description Value
lsp-name Specifies the CR-LSP name. The name is a string of 1 to 19 case-sensitive characters, spaces not supported.
incoming-interface interface-type interface-number Specifies the name of an incoming interface. -
in-label in-label Specifies the value of an incoming label. An integer ranging from 16 to 1023
nexthop next-hop-address Specifies the next-hop address. -
outgoing-interface interface-type interface-number Specifies the name of an outgoing interface. -
out-label out-label Specifies the value of an outgoing label. An integer ranging from 16 to 1048575.
bc0 Obtains the bandwidth from BC0. -
bc1 Obtains the bandwidth from BC1. -
bandwidth Specifies the bandwidth required by a CR-LSP. The value ranges from 0 to 4000000000, in kbit/s. The default value is 0.
description description Specifies the description information. -

Views

System view

Default Level

2: Configuration level

Usage Guidelines

Before setting up an MPLS TE tunnel through a static CR-LSP, configure a static route or an IGP to ensure connectivity between LSRs, and enable basic MPLS and MPLS TE functions.

Example

# Configure the static CR-LSP named tunnel34, with the incoming interface being VLANIF10, the incoming label being 123, the outgoing interface being VLANIF20, the outgoing label as 253, the required BC0 bandwidth being 20 kbit/s on the transit node.

<HUAWEI> system-view
[HUAWEI] static-cr-lsp transit tunnel34 incoming-interface vlanif 10 in-label 123 outgoing-interface vlanif 20 out-label 253 bandwidth bc0 20

undo mpls te auto-frr (upgrade-compatible command)

Function

The undo mpls te auto-frr command disables MPLS TE Auto FRR in the interface view.

Format

undo mpls te auto-frr

Parameters

None

Views

Interface view

Default Level

2: Configuration level

Usage Guidelines

This command is available to aid upgrade compatibility. It can only be run during the configuration restoration phase of the upgrade.

After the upgrade, this command is no longer supported, and it is replaced by the mpls te auto-frr block command.

Translation
Download
Updated: 2019-10-18

Document ID: EDOC1000178288

Views: 25494

Downloads: 109

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next