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

Example: ATM2 IQ-Based Layer 2 Circuit Configuration

Figure 75: ATM2 IQ-Based Layer 2 Circuit Topology Diagram

Image g017217.gif

Figure 75 shows a similar network topology to our previous two examples. In this example, Routers PE1 and PE2 use ATM cell-relay mode on a CE-facing interface and ATM AAL5 mode on a second CE-facing interface.

On Router CE1, configure the ATM2 IQ interfaces to handle ATM traffic. Interface at-0/0/1 handles standard ATM traffic while interface at-0/0/2 handles AAL5 traffic.

Router CE1

[edit]
interfaces {
at-0/0/1 {
description "to PE1 at-0/1/0";
atm-options {
pic-type atm2; # Layer 2 circuits are compatible with
vpi 0; # ATM2 IQ interfaces.
}
unit 0 {
vci 32;
family inet {
address 10.1.1.1/30;
}
}
}
at-0/0/2 {
description "to PE1 at-1/2/0";
atm-options {
pic-type atm2; # Layer 2 circuits are compatible with
vpi 0; # ATM2 IQ interfaces.
}
unit 0 {
encapsulation atm-vc-mux;
vci 32;
family inet {
address 10.2.2.1/30;
}
}
}
}

On Router PE1, configure the ATM2 IQ-based CE-facing interfaces: one with ATM cell-relay mode CCC encapsulation and the other with ATM VC multiplexing CCC encapsulation. Also enable the corresponding Layer 2 circuit modes at the [edit chassis] hierarchy level. In this case, you must configure cell-relay mode on Physical Interface Card (PIC) 1 in Flexible PIC Concentrator (FPC) 0 and AAL5 mode on PIC 2 in FPC 1.

Establish your Layer 2 circuit with configuration of the l2circuit statement at the [edit protocols] hierarchy level. Remember to include in your Layer 2 circuit configuration the IP address of your remote PE neighbor (usually the loopback address of the neighbor), the interfaces connected to the CE router, and a virtual circuit identifier for each VC. In this case, you will establish one VC for cell-relay mode traffic and a second VC for AAL5 traffic. Then, configure MPLS, LDP, and an IGP (such as OSPF) to enable signaling for your Layer 2 circuit.

Router PE1

[edit]
chassis {
fpc 0 {
pic 1 {
atm-l2circuit-mode {
cell; # This dedicates FPC 0 PIC 1 to cell-relay mode.
}
}
}
fpc 1 {
pic 2 {
atm-l2circuit-mode {
aal5; # This dedicates FPC 1 PIC 2 to AAL5 mode.
}
}
}
}
interfaces {
at-0/1/0 {
description "to CE1 at-0/0/1";
encapsulation atm-ccc-cell-relay; # Cell-relay requires cell-relay encapsulation.
atm-options {
cell-bundle-size 4; # This sets the cell bundle size for the interface.
pic-type atm2; # Layer 2 circuits are compatible with
vpi 0; # ATM2 IQ interfaces.
}
unit 0 {
encapsulation atm-ccc-cell-relay; # Encapsulation for the logical interface.
vci 32;
cell-bundle-size 10; # The cell bundle size for the logical interface overrides
}       # the physical interface setting.
}
at-1/2/0 {
description "to CE1 at-0/0/2";
atm-options {
pic-type atm2; # Layer 2 circuits are compatible with
vpi 0; # ATM2 IQ interfaces.
}
unit 0 {
encapsulation atm-ccc-vc-mux; # AAL5 requires CCC VC MUX encapsulation.
vci 32;
}
}
so-0/1/0 {
description "to P0 so-0/0/0";
unit 0 {
family inet {
address 192.168.245.22/30;
}
family mpls; # Include the MPLS family on core-facing interfaces.
}
}
lo0 {
unit 0 {
family inet {
address 10.255.17.2/32;
}
}
}
}
protocols {
ospf {
traffic-engineering;
area 0.0.0.0 {
interface so-0/1/0.0;
interface lo0.0;
}
}
ldp { # LDP is required as the signaling protocol for Layer 2 circuits.
interface so-0/1/0.0;
interface lo0.0;
}
l2circuit {
neighbor 10.255.17.4 { # This points to the loopback of the PE neighbor.
interface at-0/1/0.32 { # Here you include the local CE-facing interface.
virtual-circuit-id 1; # Be sure this ID matches the ID of your PE neighbor.
}
}
neighbor 10.255.17.4 { # This points to the loopback of the PE neighbor.
interface at-1/2/0.32 { # Here you include the local CE-facing interface.
virtual-circuit-id 2; # Be sure this ID matches the ID of your PE neighbor.
}
}
}
}

On Router P0, configure LDP, MPLS, and OSPF on the interfaces connected to the PE routers. The core router provides the MPLS backbone needed to tunnel Layer 2 traffic from the ingress PR router to the egress PE router.

Router P0

[edit]
interfaces {
so-0/0/0 {
description "to PE1 so-0/1/0";
unit 0 {
family inet {
address 192.168.245.21/30;
}
family mpls; # Include the MPLS family on core interfaces.
}
}
so-0/2/1 {
description "to PE2 so-1/1/0";
unit 0 {
family inet {
address 192.168.245.17/30;
}
family mpls; # Include the MPLS family on core interfaces.
}
}
lo0 {
unit 0 {
family inet {
address 10.255.17.3/32;
}
}
}
}
protocols {
ospf {
traffic-engineering;
area 0.0.0.0 {
interface so-0/0/0.0;
interface so-0/2/1.0;
}
}
ldp { # LDP is required as the signaling protocol for Layer 2 circuits.
interface so-0/0/0.0;
interface so-0/2/1.0;
}
}

On Router PE2, complete the Layer 2 circuit by configuring statements to match those previously set on Router PE1.

Configure the ATM2 IQ-based CE-facing interfaces: one with ATM cell-relay mode CCC encapsulation and the other with ATM VC multiplexing CCC encapsulation. Also enable the corresponding Layer 2 circuit modes at the [edit chassis] hierarchy level. In this case, you must configure cell-relay mode on PIC 1 in FPC 0 and AAL5 mode on PIC 2 in FPC 1.

Complete your Layer 2 circuit with configuration of the l2circuit statement at the [edit protocols] hierarchy level. Remember to include in your Layer 2 circuit configuration the IP address of your remote PE neighbor (Router PE1), the interfaces connected to the CE router, and a virtual circuit identifier for each VC. In this case, you will establish one VC for cell-relay mode traffic and a second VC for AAL5 traffic. Then, configure MPLS, LDP, and an IGP (such as OSPF) to enable signaling for your Layer 2 circuit.

Router PE2

[edit]
chassis {
fpc 0 {
pic 1 {
atm-l2circuit-mode {
cell; # This dedicates FPC 0 PIC 1 to cell-relay mode.
}
}
}
fpc 1 {
pic 2 {
atm-l2circuit-mode {
aal5; # This dedicates FPC 1 PIC 2 to AAL5 mode.
}
}
}
}
interfaces {
at-0/1/1 {
description "to CE2 at-1/0/1";
encapsulation atm-ccc-cell-relay; # Cell-relay requires cell-relay encapsulation.
atm-options {
cell-bundle-size 4; # This sets the cell bundle size for the physical interface.
pic-type atm2; # Layer 2 circuits are compatible with
vpi 0; # ATM2 IQ interfaces.
}
unit 0 {
encapsulation atm-ccc-cell-relay; # Also configure the encapsulation
vci 32; # on the logical interface.
cell-bundle-size 10; # The cell bundle size for the logical interface overrides
}          # the physical interface setting.
}
at-1/2/1 {
description "to CE2 at-1/0/2";
atm-options {
pic-type atm2; # Layer 2 circuits are compatible with
vpi 0; # ATM2 IQ interfaces.
}
unit 0 {
encapsulation atm-ccc-vc-mux; # AAL5 requires CCC VC MUX encapsulation.
vci 32;
}
}
so-1/1/0 {
description "to P0 so-0/2/1";
unit 0 {
family inet {
address 192.168.245.18/30;
}
family mpls; # Include the MPLS family on core-facing interfaces.
}
}
lo0 {
unit 0 {
family inet {
address 10.255.17.4/32;
}
}
}
}
protocols {
ospf {
traffic-engineering;
area 0.0.0.0 {
interface so-1/1/0.0;
interface lo0.0;
}
}
ldp {    # LDP is required as the signaling protocol for Layer 2 circuits.
interface so-1/1/0.0;
interface lo0.0;
}
l2circuit {
neighbor 10.255.17.2 { # This points to the loopback of the PE neighbor.
interface at-0/1/1.32 { # Here you include the local CE-facing interface.
virtual-circuit-id 1; # Be sure this ID matches the ID of your PE neighbor.
}
}
neighbor 10.255.17.2 { # This points to the loopback of the PE neighbor.
interface at-1/2/1.32 { # Here you include the local CE-facing interface.
virtual-circuit-id 2; # Be sure this ID matches the ID of your PE neighbor.
}
}
}
}

On Router CE2, configure the ATM2 IQ interfaces to handle ATM traffic. Interface at-1/0/1 handles standard ATM traffic while interface at-1/0/2 handles AAL5 traffic.

Router CE2

[edit]
interfaces {
at-1/0/1 {
description "to PE2 at-0/1/1";
atm-options {
pic-type atm2; # Layer 2 circuits are compatible with
vpi 0;    # ATM2 IQ interfaces.
}
unit 0 {
vci 32;
family inet {
address 10.1.1.2/30;
}
}
}
at-1/0/2 {
description "to PE2 at-1/2/1";
atm-options {
pic-type atm2; # Layer 2 circuits are compatible with
vpi 0;   # ATM2 IQ interfaces.
}
unit 0 {
encapsulation atm-vc-mux;
vci 32;
family inet {
address 10.2.2.2/30;
}
}
}
}
[Contents] [Prev] [Next] [Index] [Report an Error]

Copyright © 2008, Juniper Networks, Inc. All rights reserved. Trademark Notice.