Rate and give feedback:  Feedback Received. Thank You!

Rate and give feedback: 

X

This document helped resolve my issue

Yes No

Additional Comments

800 characters remaining

May we contact you if necessary?

Name:  

E-mail: 

Enter a valid Email ID

Need product assistance? Contact Juniper Support

Submit

This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply.

English  

English

Configuring TCC

This section describes how to configure translational cross-connect (TCC). Extensive examples on how to configure TCC for interface switching and for Layer 2.5 VPNs are available in the Junos OS Feature Guides.

To configure TCC, you must perform the following tasks on the router that is acting as the switch:

Configuring the Encapsulation for Layer 2 Switching TCCs

To configure a Layer 2 switching TCC, specify the TCC encapsulation on the desired interfaces of the router that is acting as the switch.

Note: You cannot configure standard protocol families on TCC or CCC interfaces. Only the CCC family is allowed on CCC interfaces, and only the TCC family is allowed on TCC interfaces. For Ethernet circuits and Ethernet extended VLAN circuits, you must also configure the Address Resolution Protocol (ARP). See Configuring ARP for Ethernet and Ethernet Extended VLAN Encapsulations.

• Configuring PPP and Cisco HDLC Encapsulation for Layer 2 Switching TCCs
• Configuring ATM Encapsulation for Layer 2 Switching TCCs
• Configuring Frame Relay Encapsulation for Layer 2 Switching TCCs
• Configuring Ethernet Encapsulation for Layer 2 Switching TCCs
• Configuring Ethernet Extended VLAN Encapsulation for Layer 2 Switching TCCs
• Configuring ARP for Ethernet and Ethernet Extended VLAN Encapsulations

Configuring PPP and Cisco HDLC Encapsulation for Layer 2 Switching TCCs

You can include these statements at the following hierarchy levels:

• [edit interfaces interface-name]
• [edit logical-systems logical-system-name interfaces interface-name]

Configuring ATM Encapsulation for Layer 2 Switching TCCs

You can include these statements at the following hierarchy levels:

• [edit interfaces at-fpc/pic/port]
• [edit logical-systems logical-system-name interfaces at-fpc/pic/port]

Configuring Frame Relay Encapsulation for Layer 2 Switching TCCs

For Frame Relay circuits, configure the encapsulation type by specifying the value frame-relay-tcc for the encapsulation statement when configuring the data-link connection identifier (DLCI). You configure each DLCI as a circuit or a regular logical interface. The DLCI for regular interfaces must be in the range from 1 through 511, but for TCC and CCC interfaces it must be in the range from 512 through 1022.

You can include these statements at the following hierarchy levels:

• [edit interfaces interface-name]
• [edit logical-systems logical-system-name interfaces interface-name]

Configuring Ethernet Encapsulation for Layer 2 Switching TCCs

For Ethernet TCC circuits, configuring the encapsulation type for the entire physical device by specifying the value ethernet-tcc for the encapsulation statement.

You must also specify static values for a remote address and a proxy address at the [edit interfaces interface-name unit unit-number family tcc] or [edit logical-systems logical-system-name interfaces interface-name unit unit-number family tcc] hierarchy level.

The remote address is associated with the TCC switching router’s Ethernet neighbor; in the remote statement you must specify both the IP address and the media access control (MAC) address of the Ethernet neighbor. The proxy address is associated with the TCC router’s other neighbor connected by the unlike link; in the proxy statement you must specify the IP address of the non-Ethernet neighbor.

You can configure Ethernet TCC encapsulation for the interfaces on 1-port Gigabit Ethernet, 2-port Gigabit Ethernet, 4-port Fast Ethernet, and 4-port Gigabit Ethernet PICs.

You can include these statements at the following hierarchy levels:

• [edit interfaces (fe | ge)-fpc/pic/port]
• [edit logical-systems logical-system-name interfaces (fe | ge)-fpc/pic/port]

Note: For Ethernet circuits, you must also configure the Address Resolution Protocol (ARP). See Configuring ARP for Ethernet and Ethernet Extended VLAN Encapsulations.

Configuring Ethernet Extended VLAN Encapsulation for Layer 2 Switching TCCs

For Ethernet extended VLAN circuits, configure the encapsulation type for the entire physical device by specifying the value extended-vlan-tcc for the encapsulation statement.

You must also enable VLAN tagging. Ethernet interfaces in VLAN mode can have multiple logical interfaces. With encapsulation type extended-vlan-tcc, all VLAN IDs from 0 through 4094 are valid, up to a maximum of 1024 VLANs. As with Ethernet circuits, you must also specify a proxy address and a remote address at the [edit interfaces interface-name unit logical-unit-number family tcc] or [edit logical-systems logical-system-name interfaces interface-name unit unit-number family tcc] hierarchy level (see Configuring Ethernet Encapsulation for Layer 2 Switching TCCs).

You can configure these statements at the following hierarchy levels:

• [edit interfaces interface-name]
• [edit logical-systems logical-system-name interfaces interface-name]

Note: For Ethernet extended VLAN circuits, you must also configure the Address Resolution Protocol (ARP). See Configuring ARP for Ethernet and Ethernet Extended VLAN Encapsulations.

Configuring ARP for Ethernet and Ethernet Extended VLAN Encapsulations

For Ethernet and Ethernet extended VLAN circuits with TCC encapsulation, you must also configure ARP. Because TCC simply removes one Layer 2 header and adds another, the default form of dynamic ARP is not supported; you must configure static ARP.

Because remote and proxy addresses are specified on the router performing TCC switching, you must apply the static ARP statement to the Ethernet-type interfaces of the routers that connect to the TCC-switched router. The arp statement must specify the IP address and the MAC address of the remotely connected neighbor by use of the unlike Layer 2 protocol on the far side of the TCC switching router.

You can include this statement at the following hierarchy levels:

• [edit interfaces interface-name unit logical-unit-number family inet address ip-address]
• [edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number family inet address ip-address]

Configuring the Connection for Layer 2 Switching TCCs

You must configure the connection between the two circuits of the Layer 2 switching TCC on the router acting as the switch. The connection joins the interface coming from the circuit’s source to the interface leading to the circuit’s destination. When you specify the interface names, include the logical portion of the name, which corresponds to the logical unit number. The cross-connect is bidirectional, so packets received on the first interface are transmitted from the second interface, and those received on the second interface are transmitted from the first.

To configure a connection for a local interface switch, include the following statements:

You can include these statements at the following hierarchy levels:

• [edit protocols connections]
• [edit logical-systems logical-system-name protocols connections]

To configure a connection for a remote interface switch, include the following statements:

You can include these statements at the following hierarchy levels:

• [edit protocols connections]
• [edit logical-systems logical-system-name protocols connections]

Configuring MPLS for Layer 2 Switching TCCs

For a Layer 2 switching TCC to work, you must enable MPLS on the router by including at least the following statements. This minimum configuration enables MPLS on a logical interface for the switching cross-connect.

Include the family mpls statement:

You can configure 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 can then specify this logical interface in the MPLS protocol configuration:

You can configure these statements at the following hierarchy levels:

• [edit protocols]
• [edit logical-systems logical-system-name protocols]

Note: MPLS LSP link protection does not support TCC.