4000 Router Series MPLS Command Reference

Predefined user roles

network-admin

Parameters

associated reverse-lsp lsp-name lsp-name: Configures an associated bidirectional MPLS TE tunnel, and

specifies the associated reverse CRLSP. The lsp-name argument specifies the name of a static CRLSP (the

reverse CRLSP), a case-sensitive string of 1 to 15 characters.

associated reverse-lsp lsr-id ingress-lsr-id tunnel-id tunnel-id: Configures an associated bidirectional

MPLS TE tunnel, and specifies the associated reverse CRLSP. The ingress-lsr-id argument specifies the LSR

ID of the ingress node of the reverse CRLSP and the tunnel-id argument specifies the tunnel ID of the

reverse CRLSP.

co-routed: Configures a co-routed bidirectional MPLS TE tunnel.

active: Specifies the local end as the active end of the co-routed bidirectional MPLS TE tunnel.

passive reverse-lsp lsr-id ingress-lsr-id tunnel-id tunnel-id: Specifies the local end as the passive end of

the co-routed bidirectional MPLS TE tunnel, and specifies the associated reverse CRLSP. The ingress-lsr-id

argument specifies the LSR ID of the ingress node of the reverse CRLSP and the tunnel-id argument

specifies the tunnel ID of the reverse CRLSP. You must specify a reverse CRLSP on the passive end, so that

the CRLSP and the reverse CRLSP are associated to form a bidirectional MPLS TE tunnel.

Usage guidelines

A bidirectional MPLS TE tunnel can be established in co-routed mode or associated mode.

• Co-routed mode uses the extended RSVP-TE protocol to establish a bidirectional MPLS TE tunnel. To

establish a co-routed bidirectional MPLS TE tunnel, you must configure one end of the tunnel as the

active end and the other as the passive end.

• In associated mode, you establish a bidirectional MPLS TE tunnel by binding two unidirectional

CRLSPs in opposite directions. The two CRLSPs can be established in different modes and use

different paths. For example, one CR-LSP is established statically and the other CR-LSP is established

dynamically by RSVP-TE.

Follow these guidelines when you set up a bidirectional MPLS TE tunnel:

• To set up a bidirectional MPLS TE tunnel in co-routed mode, you must specify the signaling protocol

as RSVP-TE.

• To create a bidirectional MPLS TE tunnel, you must disable the PHP function on both ends of the

tunnel to assign non-null labels to the penultimate hop.

• A bidirectional MPLS TE tunnel established by using RSVP-TE always uses the resources reservation

style FF regardless of the resource reservation style configured by the mpls te resv-style command.

Examples

# Enable the MPLS TE bidirectional tunnel function on interface Tunnel0, and configure the local end as

the active end of the co-routed bidirectional tunnel.

<Sysname> system-view

[Sysname] interface tunnel 0 mode mpls-te

[Sysname-Tunnel0] destination 10.0.0.2

[Sysname-Tunnel0] mpls te bidirectional co-routed active

# Enable the MPLS TE bidirectional tunnel function on interface Tunnel0, configure the local end as the

passive end of the co-routed bidirectional tunnel, and specify the ingress node's LSR ID of the reverse

CR-LSP as 10.0.0.1 and the tunnel ID of the reverse CR-LSP as 1.

<Sysname> system-view