Configuring TCC Encapsulation for Layer 2 VPNs and Layer 2 Circuits
Also known as Layer 2.5 VPNs, the translation cross-connect (TCC) encapsulation types allow you to configure different encapsulation types at the ingress and egress of a Layer 2 VPN or the ingress and egress of a Layer 2 circuit. For example, a CE router at the ingress of a Layer 2 VPN path can send traffic in a Frame Relay encapsulation. A CE router at the egress of that path can receive the traffic in an ATM encapsulation.
The EX9200 switches only use ethernet and ethernet-vlan encapsulation types.
For information about how to configure encapsulations for Layer 2 circuits, see Configuring the Interface Encapsulation Type for Layer 2 Circuits
The configuration for TCC encapsulation types is similar to the configuration for CCC encapsulation types. For Layer 2 VPNs, you specify a TCC encapsulation type for each PE-router-to-CE-router interface. The encapsulation type configured for the interface should match the encapsulation type configured under the routing instance. For information about how to configure the encapsulation type under the routing instance, see Configuring the Encapsulation Type.
Some platform and FPC combinations can not pass TCC encapsulated ISO traffic. See Platforms/FPCs That Cannot Forward TCC Encapsulated ISO Traffic for details.
You need to configure the TCC encapsulation on both the physical
and logical interfaces. To configure the TCC encapsulation type, include
the encapsulation-type statement:
encapsulation-type tcc-encapsulation-type;
On the EX9200 switches, replace encapsulation-type with the encapsulation statement:
encapsulation tcc-encapsulation;
To configure the TCC encapsulation type on the physical interface, include this statement at the following hierarchy levels:
[edit interfaces interface-name][edit logical-systems logical-system-name interfaces interface-name]
To configure the TCC encapsulation type on the logical interface, include this statement at the following hierarchy levels:
[edit interfaces interface-name unit logical-unit-number][edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number]
You configure the encapsulation type at the [edit interfaces] hierarchy level differently than at the [edit routing-instances] 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 Layer 2.5 VPNs employing an Ethernet interface as the TCC router, you can configure an Ethernet TCC or an extended VLAN TCC.
To configure an Ethernet TCC or an extended VLAN TCC,
include the proxy and remote statements:
proxy inet-address; remote (inet-address | mac-address);
You can include these statements at the following hierarchy levels:
[edit interfaces interface-name unit logical-unit-number family tcc][edit logical-interfaces logical-interface-name interfaces interface-name unit logical-unit-number family tcc]
The proxy inet-address address statement defines
the IP address for which the TCC router is acting as proxy.
The remote (inet-address | mac-address) statement
defines the location of the remote router.
Ethernet TCC is supported on interfaces that carry IP version 4 (IPv4) traffic only. However, Ethernet TCC encapsulation is not supported on 8-port, 12-port, and 48-port Fast Ethernet PICs.