Configure TCC Encapsulation on Interfaces

Translation cross-connect (TCC) encapsulation types allow you to configure a different encapsulation type at the ingress and egress of a Layer 2 VPN. For example, a CE router at the ingress of a Layer 2 VPN circuit can send traffic as Frame Relay. A CE router at the egress of that circuit can receive the traffic as ATM.

The configuration for TCC encapsulation types is similar to the configuration for CCC encapsulation types. Specify a TCC encapsulation type for each PE-router-to-CE-router interface running a Layer 2 VPN. This encapsulation type should match the encapsulation type configured under the routing instance. See Configure the Encapsulation Type for information about how to configure the encapsulation type under the routing instance.

To configure the TCC encapsulation type, include the following statements at the [edit interfaces] hierarchy level:

[edit]

interfaces {

    interface name {

        encapsulation tcc-encapsulation-type;

        unit unit number {

            encapsulation tcc-encapsulation-type;

        }

    }

}

You configure the encapsulation type at the [edit interfaces] hierarchy level differently from the [edit routing-instance] hierarchy level. For example, you specify the encapsulation as frame-relay at the [edit routing-instances] hierarchy level and as frame-relay-tcc at the [edit interfaces] hierarchy level.

For more information on how to configure interfaces and interface encapsulations, see the JUNOS Internet Software Configuration Guide: Interfaces and Class of Service.