A GMPLS UNI tunnel is unidirectional. A forward GMPLS UNI tunnel and a reverse GMPLS UNI tunnel must be established to implement bidirectional traffic transmission. The ingress EN initiates tunnel establishment requests containing tunnel attributes. Therefore, basic tunnel attributes and functions must be configured on the ingress EN.
Forward and reverse UNI-LSPs are established for bidirectional GMPLS UNI tunnels and have the same requirements on traffic engineering. A GMPLS UNI tunnel is established using extended RSVP-TE. The ingress EN initiates tunnel establishment requests containing tunnel attributes by sending Path messages. Therefore, tunnel attributes and functions need to be configured on the ingress EN and do not need to be configured on the egress EN for a reverse GMPLS UNI tunnel.
The system view is displayed.
A GMPLS UNI tunnel is established, and the tunnel view is displayed.
The tunnel ID is configured.
A destination IP address is set for the GMPLS UNI tunnel. Generally, the LSR ID of the sink C node is set as the destination IP address.
The bandwidth is configured for the GMPLS UNI tunnel.
Explicit path constraints are configured.
A data switching type is set for a GMPLS UNI tunnel.
A GMPLS UNI tunnel interface is bound to a service interface.
Only a local GMPLS UNI can function as a service interface.
The link protection function is configured for the GMPLS UNI tunnel.
If PCE path calculation is configured, this command does not need to be run. This is because the device forcibly sets the protection type to rerouting for PCE path calculation.
The configuration is committed.