Supported Platforms
Defining the Encapsulation for Switching Cross-Connects
To configure Layer 2 or Layer 2.5 switching cross-connects, configure the CCC or TCC encapsulation on the router that is acting as the switch (Router B in Layer 2 Switching Circuit Cross-Connect).
 | Note: When you use CCC encapsulation, you can configure the ccc family only. Likewise, when you use TCC encapsulation, you can configure the tcc family only. |
This section contains the following topics:
Configuring PPP or Cisco HDLC Circuits
For PPP or Cisco HDLC circuits, specify the encapsulation by including the encapsulation statement at the [edit interfaces interface-name] hierarchy level. This statement configures the entire physical device. For these circuits to work, you must configure a logical interface unit 0.
Configuring ATM Circuits
For ATM circuits, include the vpi statement [edit interfaces interface-name atm-options] hierarchy level:
On the logical interface, include the following statements:
You can include the logical interface statements at the following hierarchy levels:
- [edit interfaces at-fpc/pic/port unit logical-unit-number]
- [edit logical-systems logical-system-name interfaces at-fpc/pic/port unit logical-unit-number]
For each VC, configure whether it is a circuit or a regular logical interface. The default interface type is point-to-point.
Configuring Frame Relay Circuits
For Frame Relay circuits, include the encapsulation statement at the [edit interfaces interface-name] hierarchy level:
On the logical interface, include the following statements:
You can include the logical interface statements 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]
The encapsulation type can be one of the following:
- Flexible Frame Relay (flexible-frame-relay)—Intelligent queuing (IQ) interfaces can use flexible Frame Relay encapsulation. You use flexible Frame Relay encapsulation when you want to configure multiple per-unit Frame Relay encapsulations. This encapsulation type allows you to configure any combination of TCC, CCC, and standard Frame Relay encapsulations on a single physical port. Also, each logical interface can have any DLCI value from 1 through 1022.
- Frame Relay CCC version (frame-relay-ccc)—For E1, E3, SONET/SDH, T1, and T3 interfaces, this encapsulation type is the same as standard Frame Relay for DLCIs 0 through 511. DLCIs 512 through 1022 are dedicated to CCC. The logical interface must also have frame-relay-ccc encapsulation. When you use this encapsulation type, you can configure the ccc family only.
- Frame Relay TCC version (frame-relay-tcc)—Similar to Frame Relay CCC and has the same configuration restrictions, but used for circuits with different media on either side of the connection.
- Extended CCC version (extended-frame-relay-ccc)—This encapsulation type allows you to dedicate DLCIs 1 through 1022 to CCC. The logical interface must have frame-relay-ccc encapsulation. When you use this encapsulation type, you can configure the ccc family only.
- Extended TCC version (extended-frame-relay-tcc)—Similar to extended Frame Relay CCC, this encapsulation type allows you to dedicate DLCIs 1 through 1022 to TCC, which is used for circuits with different media on either side of the connection.
- Port CCC version (frame-relay-port-ccc)—Defined in the IETF document Frame Relay Encapsulation over Pseudo-Wires (expired December 2002). This encapsulation type allows you to transparently carry all the DLCIs between two customer edge (CE) routers without explicitly configuring each DLCI on the two provider edge (PE) routers with Frame Relay transport. The connection between the two CE routers can be either user-to-network interface (UNI) or network-to-network interface (NNI); this is completely transparent to the PE routers. The logical interface does not require an encapsulation statement. When you use this encapsulation type, you can configure the ccc family only.
For each DLCI, configure whether it is a circuit or a regular logical interface. The DLCI for regular interfaces must be from 1 through 511. For CCC and TCC interfaces, it must be from 512 through 1022. This restriction does not apply to IQ interfaces. The default interface type is point to point.
Configuring Ethernet CCC Circuits
You can configure Ethernet CCC encapsulation on Fast Ethernet, Gigabit Ethernet, and aggregated Ethernet interfaces.
| Note: CCC over aggregated Ethernet requires an M Series Enhanced Flexible PIC Concentrator (FPC). |
For Ethernet CCC circuits, specify the encapsulation by including the encapsulation statement at the [edit interfaces interface-name] hierarchy level. This statement configures the entire physical device.
Configuring Ethernet VLAN Circuits
You can configure Ethernet virtual local area network (VLAN) circuits on Fast Ethernet, Gigabit Ethernet, and aggregated Ethernet interfaces. For Ethernet VLAN circuits, specify the encapsulation by including the encapsulation statement at the [edit interfaces interface-name] hierarchy level. This statement configures the entire physical device. You must also enable VLAN tagging. To do this, include the following statements:
On the logical interface, include the following statements:
You can include the logical interface statements 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]
Ethernet interfaces in VLAN mode can have multiple logical interfaces. For encapsulation type vlan-ccc, VLAN IDs 1 through 511 are reserved for normal VLANs, and VLAN IDs 512 through 1023 are reserved for CCC VLANs. For encapsulation type extended-vlan-ccc, VLAN IDs 1 through 4094 are valid. VLAN ID 0 is reserved for tagging the priority of frames.
