[Contents] [Prev] [Next] [Index] [Report an Error]

Defining the Encapsulation for Layer 2 TCC Switching

To begin implementation of Layer 2 TCC switching, configure TCC encapsulation on the desired interfaces of the router that is acting as the switch (Router B in Figure 84).

Note: You cannot configure standard protocol families on TCC or CCC interfaces. Only the CCC family is allowed on CCC-encapsulated interfaces. Likewise, only the TCC family is allowed on TCC-encapsulated interfaces.

For ATM connections, specify the encapsulation type when configuring ATM virtual circuits (VCs) at the [edit interfaces interface-name unit unit-number] hierarchy level. For each VC, you configure whether it is a circuit or a regular logical interface. The default interface type is point-to-point.



[edit]
interfaces {


at-fpc/pic/port {


atm-options {
vpi vpi-identifier  maximum-vcs maximum-vcs;
}




unit logical-unit-number {
point-to-point; # This is the default interface type.
encapsulation (atm-tcc-vc-mux | atm-tcc-snap);
vci vpi-identifier.vci-identifier;
}


}


}

For Cisco HDLC and PPP circuits, specify the encapsulation in the encapsulation statement at the [edit interfaces interface-name] hierarchy level. This statement configures the entire physical device. Also, you must configure the logical interface unit 0 .



[edit]
interfaces {



type-fpc/pic/port {
encapsulation (cisco-hdlc-tcc | ppp-tcc);
unit 0;
}


}

You can specify the encapsulation for Frame Relay circuits at the [edit interfaces interface-name] hierarchy level and the [edit interfaces interface-name unit unit-number] hierarchy level. For TCC and CCC interfaces, the DLCI value must be configured in the range of 512 through 1022. The default interface type is point-to-point.



[edit]
interfaces {



type-fpc/pic/port                {
encapsulation frame-relay-tcc;


unit logical-unit-number {
point-to-point; # This is the default interface type.
encapsulation frame-relay-tcc;
dlci dlci-identifier;
}


}


}

Configuring Ethernet Encapsulation with Remote and Proxy ARP Addresses

For Ethernet TCC circuits, specify the encapsulation with the encapsulation ethernet-tcc statement. This statement configures the entire physical device.

To provide Address Resolution Protocol (ARP) functionality for an Ethernet-based neighbor, configure the remote statement at the [edit interfaces interface-name unit unit-number family tcc] hierarchy level and specify either the MAC address or IP address of the TCC router’s Ethernet neighbor. To complete the setup of ARP, configure the proxy statement at the [edit interfaces interface-name unit unit-number family tcc] hierarchy level and specify the IP address of the TCC router’s non-Ethernet neighbor.



[edit]
interfaces 

EthernetType-fpc/pic/port {
encapsulation ethernet-tcc;


unit 0 {


family tcc {


remote { # Addresses associated with the Ethernet TCC neighbor.
mac-address mac-address;
# Select a MAC or IP address.
inet-address inet-address;
}




proxy { # Addresses belonging to the non-Ethernet TCC neighbor.
inet-address inet-address;
}


}


}


}

Configuring Extended VLAN Encapsulation with Remote and Proxy ARP Addresses

Specify the encapsulation for extended VLAN circuits with the encapsulation extended-vlan-tcc statement. This statement configures the entire physical device.

You must also enable VLAN tagging. Ethernet interfaces in VLAN mode can have multiple logical interfaces. For encapsulation type extended-vlan-tcc, all VLAN IDs from 0 through 4094 are valid, up to a maximum of 1024 VLANs.

To enable ARP functionality, configure the remote statement at the [edit interfaces interface-name unit unit-number family tcc] hierarchy level with either the MAC address or IP address of your Ethernet TCC neighbor. To complete the ARP setup, configure the proxy statement at the [edit interfaces interface-name unit unit-number family tcc] hierarchy level and specify the IP address of the non-Ethernet TCC neighbor.



[edit]
interfaces {



EthernetType-fpc/pic/port {
vlan-tagging;
encapsulation extended-vlan-tcc;


unit 0 {
vlan-id 600;


family tcc {


remote { # Addresses associated with the Ethernet TCC neighbor.
mac-address mac-address;
# Select a MAC or IP address.
inet-address inet-address;
}




proxy { # Addresses belonging to the non-Ethernet TCC neighbor.
inet-address inet-address;
}


}


}


}


}

Option: Configuring Static ARP on the Ethernet Neighbor Instead of Proxy ARP

If you do not use the proxy statement in the Ethernet TCC and extended VLAN TCC encapsulation hierarchies shown earlier, you must use another method to allow ARP to continue to function. To retain the functionality of ARP for Ethernet networks, you must configure static ARP on the Ethernet neighbor. Use of static ARP assumes that you have already configured the remote statement on the TCC router (see Configuring Ethernet Encapsulation with Remote and Proxy ARP Addresses and Configuring Extended VLAN Encapsulation with Remote and Proxy ARP Addresses).

You configure the arp statement on the Ethernet neighbor at the [edit interfaces interface-number unit unit-number family inet address ip-address] hierarchy level. Your static ARP statement must contain the IP address of the non-Ethernet neighbor on the opposite side of the TCC router and the Ethernet interface MAC address of the TCC router. This static ARP configuration enables return path ARP functionality and complements the remote statement previously set on the TCC router.

In Figure 86, you would configure an ARP statement on the fe-0/0/0 interface of Router C. The ARP statement would contain the IP address for interface so-0/1/0.600 on Router A and the MAC address of the fe-1/0/0 interface of Router B.

Configure static ARP on an Ethernet neighbor at the [edit interfaces interface-name unit unit-number family inet address ip-address] hierarchy level.



[edit]
interfaces

EthernetType-fpc/pic/port {


unit 0 {


family inet {


address ip-address { # The
local IP address.
arp ip-address mac mac-address; # IP address of the non-Ethernet
}         
# TCC neighbor and MAC address  of the TCC


}         
# router's Ethernet interface.


}


}

[Contents] [Prev] [Next] [Index] [Report an Error]