Configuring VLAN TCC Encapsulation
VLAN TCC encapsulation allows circuits to have different media on either side of the forwarding path. VLAN TCC encapsulation supports TPID 0x8100 only. You must include configuration statements at the logical and physical interface hierarchy levels.
To configure VLAN TCC encapsulation, include the encapsulation statement and specify the vlan-tcc option:
You can 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]
Additionally, configure the logical interface by including the proxy and remote statements:
You can include these statements at the following hierarchy levels:
[edit interfaces interface-name unit logical-unit-number family tcc]
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number family tcc]
The proxy address is the IP address of the non-Ethernet TCC neighbor for which the TCC router is acting as a proxy.
The remote address is the IP or MAC address of the remote router. The remote statement provides ARP capability from the TCC switching router to the Ethernet neighbor. The MAC address is the physical Layer 2 address of the Ethernet neighbor.
When VLAN TCC encapsulation is configured on the logical interface, you also must specify flexible Ethernet services on the physical interface. To specify flexible Ethernet services, include the encapsulation statement at the [edit interfaces interface-name] hierarchy level and specify the flexible-ethernet-services option:
Extended VLAN TCC encapsulation supports TPIDs 0x8100 and 0x9901. Extended VLAN TCC is specified at the physical interface level. When configured, all units on that interface must use VLAN TCC encapsulation, and no explicit configuration is needed on logical interfaces.
One-port Gigabit Ethernet, 2-port Gigabit Ethernet, and 4-port Fast Ethernet PICs with VLAN tagging enabled can use VLAN TCC encapsulation. To configure the encapsulation on a physical interface, include the encapsulation statement at the [edit interfaces interface-name] hierarchy level and specify the extended-vlan-tcc option:
For VLAN TCC encapsulation, all VLAN IDs from 1 through 1024 are valid. VLAN ID 0 is reserved for tagging the priority of frames.
Extended VLAN TCC is not supported on 4-port Gigabit Ethernet PICs.