mpls te bidirectional

Use mpls te bidirectional to enable the bidirectional tunnel feature on an MPLS TE tunnel interface.

Use undo mpls te bidirectional to disable the bidirectional tunnel feature on an MPLS TE tunnel interface.

Syntax

mpls te bidirectional { associated reverse-lsp { lsp-name lsp-name | lsr-id ingress-lsr-id tunnel-id tunnel-id } | co-routed { active | passive reverse-lsp lsr-id ingress-lsr-id tunnel-id tunnel-id } }

undo mpls te bidirectional

Default

The bidirectional tunnel feature is disabled on an MPLS TE tunnel interface. A tunnel established on an MPLS TE tunnel interface is a unidirectional MPLS TE tunnel.

Views

Tunnel interface view

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 on the reverse CRLSP and the tunnel-id argument specifies the tunnel ID of the reverse CRLSP. The value range for the tunnel-id argument is 0 to 65535.

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 on the reverse CRLSP and the tunnel-id argument specifies the tunnel ID of the reverse CRLSP. The value range for the tunnel-id argument is 0 to 65535. 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 perform the following tasks:
- Specify the signaling protocol as RSVP-TE.
- 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 CRLSP is established statically and the other CRLSP is established dynamically by RSVP-TE.

To create a bidirectional MPLS TE tunnel, you must disable the PHP feature on both ends of the tunnel to assign non-null labels to the penultimate hop.

If the mpls te bidirectional command is configured together with one of the following commands, only the mpls te bidirectional command takes effect:

mpls te backup
mpls te reoptimization
mpls te fast-reroute

Examples

Configure an MPLS TE bidirectional tunnel between Device A and Device B in co-routed mode:
# Configure Device A as follows:
- Enable the MPLS TE bidirectional tunnel feature on tunnel interface Tunnel 0.
- Configure Device A as the active end of the co-routed bidirectional tunnel.
```
<DeviceA> system-view
[DeviceA] interface tunnel 0 mode mpls-te
[DeviceA-Tunnel0] destination 10.0.0.2
[DeviceA-Tunnel0] mpls te bidirectional co-routed active
```
# Configure Device B as follows:
- Enable the MPLS TE bidirectional tunnel feature on tunnel interface Tunnel 1.
- Configure Device B as the passive end of the co-routed bidirectional tunnel.
- Specify the ingress node's LSR ID of the reverse CRLSP as 10.0.0.1—the LSR ID of Sysname1.
- Specify the tunnel ID of the reverse CRLSP as 0—the tunnel ID configured on Device A.
```
<DeviceB> system-view
[DeviceB] interface tunnel 1 mode mpls-te
[DeviceB-Tunnel1] destination 10.0.0.1
[DeviceB-Tunnel1] mpls te bidirectional co-routed passive reverse-lsp lsr-id 10.0.0.1 tunnel-id 0
```
Configure an MPLS TE bidirectional tunnel between Device A and Device B in associated mode:
# Configure Device A as follows:
- Enable the MPLS TE bidirectional tunnel feature on tunnel interface Tunnel 0.
- Configure the tunnel establishment mode as associated.
- Specify the ingress node's LSR ID of the reverse CRLSP as 10.0.0.2—the LSR ID of Device B.
- Specify the tunnel ID of the reverse CRLSP as 1—the tunnel ID configured on Device B.
```
<DeviceA> system-view
[DeviceA] interface tunnel 0 mode mpls-te
[DeviceA-Tunnel0] destination 10.0.0.2
[DeviceA-Tunnel0] mpls te bidirectional associated reverse-lsp lsr-id 10.0.0.2 tunnel-id 1
```
# Configure Device B as follows:
- Enable the MPLS TE bidirectional tunnel feature on tunnel interface Tunnel 1.
- Configure the tunnel establishment mode as associated.
- Specify the ingress node's LSR ID of the reverse CRLSP as 10.0.0.1—the LSR ID of Device A.
- Specify the tunnel ID of the reverse CRLSP as 0—the tunnel ID configured on Device A.
```
<DeviceB> system-view
[DeviceB] interface tunnel 1 mode mpls-te
[DeviceB-Tunnel1] destination 10.0.0.1
[DeviceB-Tunnel1] mpls te bidirectional associated reverse-lsp lsr-id 10.0.0.1 tunnel-id 0
```

Related commands

display mpls te tunnel-interface

prev	up	next
mpls te bandwidth change thresholds	home	mpls te enable (interface view)