A GMPLS UNI tunnel is unidirectional. After a forward GMPLS UNI tunnel is configured, a reverse GMPLS UNI tunnel must be configured on the egress EN.
A GMPLS UNI tunnel is bound to the physical interface of the data channel or VLAN sub-interface of the physical interface to carry data services on the ingress EN and egress EN. 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. A reverse GMPLS UNI tunnel only needs to be matched with its corresponding forward GMPLS UNI tunnel and bound to the service bearer interface.
The system view is displayed.
A GMPLS UNI tunnel is established, and the tunnel view is displayed.
The established tunnel is configured as a reverse 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 name and node ID of the ingress are configured for the forward GMPLS UNI tunnel.
The ingress-lsr-id parameter is set to the LSR ID of the ingress EN. The tunnel-id parameter is set to the forward tunnel ID.
The configuration is committed.
After the preceding configurations are complete, a GMPLS UNI tunnel is established, and the service bearer interface bound to the tunnel goes Up. IP and MPLS services can be configured on the interface. Configurations are the same as those of other interfaces that are not bound to the GMPLS UNI tunnel. Detailed configuration procedures are not mentioned here.