The match-tunnel command binds a reverse GMPLS UNI tunnel to a forward GMPLS UNI tunnel.
The undo match-tunnel command deletes the binding between a reverse GMPLS UNI tunnel and a forward GMPLS UNI tunnel.
By default, a reverse GMPLS UNI tunnel is not bound to a forward GMPLS UNI tunnel.
| Parameter | Description | Value |
|---|---|---|
| ingress-lsr-id ingress-lsr-id |
Specifies the source IP address of a forward tunnel. The source IP address is the LSR ID of the ingress EN. |
The value is in dotted decimal notation. |
| tunnel-id tunnel-id |
Specifies the tunnel ID of a forward tunnel. |
The value is an integer ranging from 1 to 65535. |
Usage Scenario
GMPLS UNI uses Resource Reservation Protocol-Traffic Engineering (RSVP-TE) to set up a bidirectional GMPLS UNI LSP. Both the forward and reverse UNI LSPs have the same TE requirements. After a forward GMPLS UNI LSP is configured on the ingress EN, a reverse GMPLS UNI LSP must be configured on the egress EN. After the forward and reverse GMPLS UNI LSPs are configured, the system will automatically establish a bidirectional LSP based on configuration data.
There are two steps to configure a reverse tunnel: 1.Run the passive command to configure a GMPLS UNI tunnel as a reverse tunnel. 2.Run the match-tunnel command to bind the reverse tunnel to a forward tunnel.Prerequisites
The established GMPLS UNI tunnel has been configured as a reverse tunnel using the passive command.
Precautions
Running the undo passive command will delete the match-tunnel command configuration.
<HUAWEI> system-view [~HUAWEI] mpls [*HUAWEI-mpls] mpls te [*HUAWEI-mpls] quit [*HUAWEI] gmpls-tunnel toRt2 [*HUAWEI-gmpls-tunnel-toRt2] passive [*HUAWEI-gmpls-tunnel-toRt2] match-tunnel ingress-lsr-id 1.1.1.1 tunnel-id 1