Unit 3

Frame Relay ATM and VLAN

Overview

Frame Relay, ATM and VLAN Overview Rev 3.2 Page 3- 1

 Frame Relay and ATM Unit
Objectives
• Identify three ways to connect multiple virtual routers
across a single physical interface
• Describe basic Frame Relay characteristics
• Configure a serial interface on a CT3/CE1/CT1 controller
using Frame Relay and IP
• Use show commands to verify the Frame Relay
configuration
• Describe basic ATM characteristics
• Configure an OC3c interface using ATM and IP
• Use show commands to verify the ATM configuration
• Describe basic VLAN characteristics
• Configure a Fast Ethernet interface using VLANs and IP

Frame Relay, ATM and VLAN Overview Rev 3.2 Page 3- 2

 Connecting Virtual Routers
Will this work?

CT3

UT3F

UT3F

CT3
ISPA ISPA ISPA
ISPA
0 0
FR 192.168.9.1/24 192.168.9.1/24 FR

0 0
ISPB FR PPP FR ISPB
ISPB ISPB
1 1
1 1
ATM ATM
192.168.33.1/24 192.168.33.1/24

2 Default 2 2 Default 2
PPP 192.168.2.1/24 192.168.2.1/24 PPP

10.3.202.1/16 10.3.202.1/16
Customers 0 Customers
SRP 0 SRP

At this point, we have segmented our ERX into three separate and distinct virtual routers.
Now we need to connect the ERXes together. We would like to use the Unchannelized T3
(or E3) Frame Cards to accomplish this task. However, we only want to use a single port
on the UT3F cards.
Can we use a single PPP interface to accomplish this task?

Frame Relay, ATM and VLAN Overview Rev 3.2 Page 3- 3

 POS Interface uses 1 IP Address Which
pair of Virtual Routers will it connect?

CT3

UT3F

UT3F

CT3
ISPA ISPA ISPA
ISPA
0 192.168.10.0/32 0
FR 192.168.9.1/24 192.168.25.1/24 FR

PPP
0 0 PPP
ISPB FR PPP FR ISPB
ISPB ISPB
1 1

192.168.33.1/24 1 1 192.168.49.1/24

2 Default 2 2 Default 2
PPP 192.168.1.1/24 192.168.17.1/24 PPP

10.3.202.1/16 10.3.202.2/16
Customers 0 Customers
SRP 0 SRP

Remember that PPP is used for point-to-point connections. It is a single physical interface
with a single IP address assigned to it. Therefore, a single physical interface running PPP
would be capable of connecting only 1 pair of virtual routers together.
Which pair would we connect?
We need a new data link protocol that will allow us to build multiple logical connections
over a single physical interface. In this example, we need three logical connections over
the single UT3F interface.

Frame Relay, ATM and VLAN Overview Rev 3.2 Page 3- 4

 1 Physical Interface
Multiple Logical Connections

CT3

UT3F

UT3F

CT3
ISPA ISPA ISPA
ISPA
0 0
FR 192.168.9.1/24 192.168.25.1/24 FR

192.168.10.1/24 0 0 192.168.10.2/24
ISPB FR
Frame FR ISPB
1
ISPB Relay ISPB
1

192.168.33.1/24 1 1 192.168.49.1/24

2 Default 2 2 Default 2
PPP 192.168.1.1/24 192.168.17.1/24 PPP

10.3.202.1/16 10.3.202.2/16
Customers 0 Customers
SRP 0 SRP

Frame Relay, ATM and VLAN Overview Rev 3.2 Page 3- 5

 Frame Relay Basics

DLCI 16
Atlanta
DLCI 18
FR
Switch
Frame
DLCI 16
FR Relay
Boston Switch
DLCI 17
FR
Switch DLCI 18

San Francisco
DLCI 19

• 1 Physical Interface, Multiple Logical Connections (PVC)

• Each logical connection or PVC identified by a DLCI
• DLCIs are locally significant
• LMI - Management Protocol
• Encapsulation IETF 1490
• Variable Length Frames

Frame Relay, ATM and VLAN Overview Rev 3.2 Page 3- 6

 ERX Frame Relay Configuration

Frame Customer X
Relay DTE
Customer A POS ATM ERX
ERX Frame
DTE Customer Y
U U
Relay
DTE DTE
Customer B
Customer Z
DTE DTE
DCE DCE

Customer C
DTE
DTE
ISP A

The ERX can be configured to support Frame Relay in two different modes of operation. It
can be configured to act as Data Terminal Equipment (DTE) in a Frame Relay network, in
other words, to act as a frame relay customer router. When an ERX interface is configured
for Frame Relay in DTE mode the ERX will be responsible for polling the service providers
switch using some management protocol (Annex A, Annex D, or LMI) to determine the status
of its pvcs.
The ERX can also be configured to act as Data Communications Equipment (DCE) in a
frame relay network. When acting as DCE the ERX will respond to polls and status enquiries
from customer DTE routers. It is important to not that the even when configured to act as
DCE the ERX is still an IP router and will not forward Frame Relay frames.

Frame Relay, ATM and VLAN Overview Rev 3.2 Page 3- 7

 A Different Way of Viewing Things -
IP/FR/CT3
IP Interface
IP Interface IP Interface IP Interface
192.168.11.1
192.168.9.1 192.168.10.1 192.168.12.1

Frame Relay Frame Relay Frame Relay Frame Relay

Subinterface 4/0:1/1.1 Subinterface 4/0:2/1.1 Subinterface 4/0:3/1.1 Subinterface 4/0:3/1.2
PVC DLCI 16 PVC DLCI 16 PVC DLCI 16 PVC DLCI 17

Frame Relay Frame Relay Frame Relay

Major Interface Major Interface Major Interface

HDLC Channel HDLC Channel HDLC Channel

Serial 4/0:1/1 Serial 4/0:2/1 Serial 4/0:3/1

T1 #1 T1 #2 T1 #3
DS0 1-24 DS0 1-24 DS0 1-4
1/1 2/1 3/1

CT3
4/0

Frame Relay, ATM and VLAN Overview Rev 3.2 Page 3- 8

 ERX CT3 Configuration
Config

Controller

E1 T1 E3 T3

Interface Interface
Slot/Port Slot/Port
4/0 4/1

Clocking Clocking
Shutdown Shutdown
Framing Framing
Cable length Cable length
Loopback Loopback
T1 T1

Bert Bert
Loopback Loopback
Remote Loopback Remote Loopback
Shutdown Shutdown

Channel/Subchannel Channel/Subchannel Channel/Subchannel Channel/Subchannel

1/1 1/2 1/1 1/2

Timeslot 1-4 Timeslot 5-8 Timeslot 1-12 Timeslot 13-24

Speed 64K Speed 64K Speed 56K Speed 56K
Shutdown Shutdown Shutdown Shutdown

RX-0-9-D0(config)#controller ?
RX-0-9-D0(config-controll)#t1 ?
e1 Configure a channelized E1 controller
e3 Configure a E3 controller <1 - 28> The T1 channel number
sonet Configure a Sonet controller CHANNEL/SUBCHANNEL The FT1 interface
t1 Configure a channelized T1 controller
t3 Configure a T3 controller RX-0-9-D0(config-controll)#t1 1 ?
bert Initiate sending of BERT test patterns
RX-0-9-D0(config)#controller t3 ?
clock Configure the DS1 transmit clock source
INTERFACE The T3 interface identifier
framing Configure DS1 line framing
RX-0-9-D0(config)#controller t3 4/0 lineCoding Configure DS1 line coding
RX-0-9-D0(config-controll)#? loopback Configure DS1 loopback
cablelength Configure the cable length remote-loopback Enable remote ability to configure interface loopback
clock Configure the transmit clock source shutdown Disable the interface
exit Exit from the current command mode snmp Configure SNMP parameters
framing Configure DS3 line framing
help Describe the interactive help system RX-0-9-D0(config-controll)#t1 1/1 ?
loopback Configure loopback
shutdown Disable the interface
no Negate a command or restore its default(s)
shutdown Disable a interface snmp Configure SNMP parameters
sleep Make the Command Interface pause for a timeslots Specify time slot configuration
snmp Configure SNMP parameters
support Enter Support mode RX-0-9-D0(config-controll)#t1 1/1 timeslot 1-4 ?
t1 Configure T1 parameters
speed Specify DS0 mode
<cr>
RX-0-9-D0(config-controll)#no shutdown
RX-0-9-D0(config-controll)#clock source internal chassis
RX-0-9-D0(config-controll)#t1 1/1 timeslot 1-4 speed 64 ?
<cr>

RX-0-9-D0(config-controll)#t1 1/1 timeslot 1-4 speed 64

RX-0-9-D0(config-controll)#exit

Frame Relay, ATM and VLAN Overview Rev 3.2 Page 3- 9

 ERX Serial Interface / FR / IP
Configuration
Config

Interface

FastEthernet ATM Loopback Serial POS

Interface Interface Interface

Slot/Port:Channel/Subchannel Slot/Port:Channel/Subchannel Slot/Port:Channel/Subchannel
4/0:1/1 4/0:1/2 4/0:1/3

Encapsulation Encapsulation Encapsulation

PPP PPP PPP

Frame Relay Frame Relay Frame Relay
Frame Relay Frame Relay Frame Relay

Interface Type Interface Type Interface Type

LMI Type LMI Type LMI Type
Interface Serial Interface Serial Interface Serial

Frame Relay Frame Relay Frame Relay Frame Relay

Subinterface Subinterface Subinterface Subinterface
4/0:1/1.1 4/0:1/2.1 4/0:1/3.1 4/0:1/3.2

IP Address IP Address IP Address IP Address

192.168.9.1/24 192.168.10.1/24 192.168.11.1/24 192.168.12.1/24

erx4:vr2(config)#interface serial 4/0:3/1

erx4:vr2(config-if)#encapsulation frame-relay ietf
erx4:vr2(config-if)#frame-relay ?
intf-type Specify the frame relay interface type
keepalive Set the Local Management Interface keepalive interval
lmi-n391dte Specify the full status polling counter
lmi-n392dce Specify the Local Management Interface error threshold
lmi-n392dte Specify the Local Management Interface error threshold
lmi-n393dce Specify the Local Management Interface monitored event count
lmi-n393dte Specify the Local Management Interface monitored event count
lmi-t391dte Specify the Data Terminal Equipment polling timer
lmi-t392dce Specify Data Circuit Terminating Equipment polling verification timer
lmi-type Specify the Local Management Interface mode
erx3:vr1(config-if)#frame-relay intf-type ?
dce Specify frame relay Data Circuit Terminating Equipment mode
dte Specify frame relay Data Terminal Equipment mode
nni Specify frame relay Network to Network Interface mode
erx4:vr2(config-if)#frame-relay intf-type dte
erx4:vr2(config-if)#interface serial 4/0:3/1.1
erx4:vr2(config-subif)#frame-relay interface-dlci 16 ietf
erx4:vr2(config-subif)#ip address 192.168.9.2 255.255.255.0
erx4:vr2(config-subif)#

Frame Relay, ATM and VLAN Overview Rev 3.2 Page 3- 10

 How can I tell if Frame Relay is
working?
• Think in Layers!
• Network
- ping
- show ip int brief
- show ip int serial 4/0:3/1 IP

- show ip route
• Data Link
- show fr interface 4/0:3/1 FR

- show fr interface pvc 4/0:3/1

- show fr pvc brief
- show fr subinterface T1 #1
DS0 1-4
- show fr summary
• Physical
- show interface serial 4/0:3/1 CT3 Port

- show controller t3 4/0

• Logging
- frameRelay

erx4:vr2#show frame interface serial 4/0:3/1

Frame relay interface 4/0:3/1, status is up
Number of interface down transitions is 0
Time since last status change 00:01:35
Number of configured circuits: 1
In bytes: 166 Out bytes: 150
In frames: 10 Out frames: 10
In errors: 0 Out errors: 0
In discards: 0 Out discards: 0
In unknown protos: 0
erx4:vr2#show frame pvc interface serial 4/0:3/1
PVC information for frame relay DTE interface 4/0:3/1
DLCI 16 in sub-interface 4/0:3/1.1, status is active
Number of circuit status inactive transitions is 0
Time since creation 00:25:08, last status change 00:04:01
In pkts: 0 Out pkts: 0
In bytes: 0 Out bytes: 0
In FECN pkts: 0 Out FECN pkts: 0
In BECN pkts: 0 Out BECN pkts: 0
In DE pkts: 0 Out DE pkts: 0
Dropped pkts: 0

Frame Relay, ATM and VLAN Overview Rev 3.2 Page 3- 11

 Connecting Virtual Routers
Will this work?

CT3

OC3c

OC3c

CT3
ISPA ISPA ISPA
ISPA
0 0
FR 192.168.9.1/24 192.168.9.1/24 FR

0 0
ISPB FR POS FR ISPB
ISPB ISPB
1 1
1 1
192.168.33.1/24 192.168.33.1/24

2 Default Default 2
PPP 192.168.2.1/24 192.168.2.1/24 PPP

10.3.202.1/16 10.3.202.1/16
Customers 0 Customers
SRP 0 SRP

In this configuration, we would like to use a single port on an OC3c line module to connect
our Virtual Routers together.
Can we use a single POS interface to accomplish this task?

Frame Relay, ATM and VLAN Overview Rev 3.2 Page 3- 12

 POS Interface uses 1 IP Subnet Address
Which pair of Virtual Routers will it connect?

CT3

OC3c
OC3c

CT3
ISPA ISPA ISPA
ISPA
0 192.168.10.0/32 0
FR 192.168.9.1/24 192.168.25.1/24 FR

PPP
0 0 PPP
ISPB FR POS FR ISPB
ISPB ISPB
1 1

192.168.33.1/24 1 1 192.168.49.1/24

2 Default Default 2
PPP 192.168.1.1/24 192.168.17.1/24 PPP

10.3.202.1/16 10.3.202.2/16
Customers 0 Customers
SRP 0 SRP

Remember that POS is simply PPP over Sonet/SDH. It is used for point-to-point
connections. It is a single physical interface with a single IP address assigned to it.
Therefore, a single physical interface running POS would be capable of connecting only 1
pair of virtual routers together.
Which pair would we connect?
We need a new data link protocol that will allow us to build multiple logical connections
over a single physical interface. In this example, we need three logical connections over
the single OC3c interface.

Frame Relay, ATM and VLAN Overview Rev 3.2 Page 3- 13

 Connecting Virtual Routers using ATM

OC3
CT3

OC3

CT3
ISPA ISPA ISPA
ISPA
0 0
FR 192.168.9.1/24 192.168.25.1/24 FR

192.168.10.1/24 0 0 192.168.10.2/24
ISPB FR ATM FR ISPB
ISPB ISPB
1 1

192.168.33.1/24 1 1 192.168.49.1/24

2 Default Default 2
PPP 192.168.1.1/24 192.168.17.1/24 PPP

10.3.202.1/16 10.3.202.2/16
Customers 0 Customers
SRP 0 SRP

ATM is a data link that allows a single, physical interface to support multiple logical
connections.

Frame Relay, ATM and VLAN Overview Rev 3.2 Page 3- 14

 ATM Basics

U U

VPI 0
ISP A
VCI 33 ISP A
VCI 34
ISP B ISP B
VCI 35
default default

• 1 Physical Interface, Multiple Logical Connections

ERX supports PVCs
-
• Each PVC identified by a
- Virtual Path Identifier (VPI)
- Virtual Circuit Identifier (VCI)
- Virtual Circuit Descriptor (VCD)
• ERX specific configuration parameter
• Unique (per interface) number that identifies a virtual circuit

In an ATM environment, one physical connection can support multiple logical interfaces.
These logical connections are known as Permanent Virtual Circuits or PVCs. They are
statically configured and always available. No call setup occurs to establish connectivity.
A PVC is identified by a Virtual Path Identifier (VPI) and a Virtual Circuit Identifier (VCI). A
Virtual Path (VP) can contain many Virtual Circuits (VCs). In this example, VP 0 contains
3 VCs. The combination of VPI/VCI uniquely identifies a connection on a physical
interface. In this example, the following logical connections exist: 0/33, 0/34 and 0/35.
The ERX also adds an extra identifier to each VC known as the Virtual Circuit Descriptor
(VCD). The VCD must be unique on an interface. It is used to obtain statistics about a
particular VPI/VCI on the ERX.

Frame Relay, ATM and VLAN Overview Rev 3.2 Page 3- 15

 A Different Way of Viewing Things -
IP/ATM/OC3 or UT3A/UE3A

IP Address IP Interface IP Interface IP Interface

Subnet Mask 192.168.33.1 192.168.34.1 192.168.35.1

ATM Subinterface ATM Subinterface ATM Subinterface

Slot/Port.Subinterface
2/0.33 2/0.34 2/0.3
PVC VCD VPI/VCI
pvc 33 0/33 pvc 34 0/34 pvc 3 0/103

Slot/Port
ATM Interface
Framing
2/0
# VC per VP

Clocking OC3
Framing UT3A/E3A
Shutdown 2/0

erx3(config)#interface atm 2/0

erx3(config-if)#atm ?
clock Specify ATM transmit clock source
ilmi-keepalive Specify the Integrated Local Management Interface keepalive
oam Configure Operations, Administration, and Management parameters
pvc Configure a Permanent Virtual Circuit
sonet Configure SONET mode
uni-version The User to Network Interface version
vc-per-vp Configure the number of Virtual Circuit Identifiers per Virtual Path Identifier
vp-tunnel Configure a Virtual Path Tunnel
erx3(config-if)#atm clock internal chassis
erx3(config-if)#atm sonet stm-1
erx3(config-if)#interface atm 2/0.33
erx3(config-if)#atm pvc 33 0 33 ?
aal5mux The AAL5 and VC MUX Encapsulation
aal5snap The AAL5 and LLC/SNAP Encapsulation
ilmi The Integrated Local Management Interface Encapsulation
erx3(config-if)#atm pvc 33 0 33 aal5snap
erx3(config-if)#ip address 192.168.33.1 255.255.255.0
erx3(config-if)#
erx3(config-if)#

Frame Relay, ATM and VLAN Overview Rev 3.2 Page 3- 16

 ATM Traffic Management
U U
Outbound Traffic

VPI 0
ISP A
VCI 33 ISP A
VCI 34
ISP B ISP B
VCI 35
default default

• OC3c (2 port)
- Unspecified Bit Rate (UBR) only
• UT3A/UE3A
- UBR
- UBR with Peak Cell Rate (PCR)
- Non-realtime (nrt) Variable Bit Rate (VBR)
- Shaping done on an individual VC
- Outbound traffic shaping
• OC3c (4 port), OC12c (1 port)
- Constant Bit Rate (CBR)

The ERX supports limited ATM traffic management capabilities, otherwise known as traffic
shaping. Traffic shaping is only relevant to outbound traffic. Different ERX line cards
support different capabilities, depending on the configuration.
The 2 port OC3 line module only supports Unspecified Bit Rate (UBR). UBR traffic is not
rate limited in any way. The physical line rate is the only limiting factor.
The UT3A and UE3A supports UBR as well as UBR with Peak Cell Rate (PCR) and Non-
Real-Time (nrt) Variable Bit Rate (VBR).
The new ASIC-based 4 port OC3 and 1 port OC12 support the traffic management
capabilities listed above as well as Constant Bit Rate (CBR).
Using UBR with PCR, only the peak cell rate is configured on the VC. Bursts above PCR
will be absorbed by the UT3A/UE3A’s egress queuing. Sustained traffic above PCR will
result in packets, not cells, being discarded. The amount of queuing available per VC
depends upon a variety of factors including overall traffic rates and packet sizes. The
maximum number of buffers available per VC is 37, where each buffer is approximately
348 bytes. Therefore, the ERX would be able to buffer or queue 9 - 1500 byte packets (37
buffers / (round-up(1500/384)). Use the show ip interface command to determine if
packets are being discarded. The counters out scheduler drop packets and bytes will
increment if packets are being discarded.
With nrt VBR, the following parameters are configured: Peak Cell Rate, Average
(sustained) cell rate, and burst size. The average cell rate is the sustained average rate to
which the VC will be restricted. The Peak Cell Rate identifies the peak rate at which the
VC will be allowed to burst for the configured burst size, in terms of a number of cells.
After one burst, the rate must fall below the Average Cell Rate before a subsequent burst
is permitted.
With CBR, only a constant bit rate is configured per PVC.

Frame Relay, ATM and VLAN Overview Rev 3.2 Page 3- 17

 ATM Configuration
U U
Outbound Traffic
VPI 0
ISP A VCI 33 ISP A
VCI 34
ISP B ISP B
VCI 35
default default

• interface atm slot/port.subinterface

erx2(config)# interface atm 5/0.33
• atm pvc vcd vpi vci encapsulation peak average
burst
• atm pvc vcd vpi vci encapsulation cbr cbr-rate
- encapsulation
• aal5snap or aal5mux ip
- Peak, Average and cbr-rate in 1 Kbps chunks, burst in cells
• UBR No peak, average or burst configured
• UBR with PCR Peak Configured
• nrt-VBR Peak, Average, and Burst Configured
erx2(config-if)# atm pvc 33 0 33 aal5snap 256 128 100

To configure ATM PVCs on the ERX, it is necessary to configure a slot, port and
subinterface. The subinterface refers to the logical connection or PVC. Often
administrators will use the same number for ATM Subinterface, Virtual Circuit Descriptor,
and Virtual Circuit Identifier, as is the case with this example.
In older software versions (<1.2.x), the peak and average cell rate were configured in 64K
chunks. Now, the peak and average can be configure in 1K chunks. The burst size is in
terms of cells, not a traffic rate.
Remember that VC traffic shaping can NOT be used on the 2 port OC3 card.

Frame Relay, ATM and VLAN Overview Rev 3.2 Page 3- 18

 ATM Traffic Shaping - VP Tunnels
Outbound Traffic

VPI 0 5 Mbps U
ISP A

VPI 1 10 Mbps
ISP B

VPI 2 30 Mbps
Customers

• Allocate bandwidth to a Virtual Path

• All PVCs within VP contend for tunnel bandwidth
• Traffic shaping relevant to outbound traffic only
• VP Tunnels supported on all ATM line modules

It is also possible to configure traffic shaping at the Virtual Path level using ATM VP
Tunnels. This allows the segregation of traffic for different customers. In this example,
the carrier is providing service to multiple ISPs and they all share the same ATM link.
Assigning a VP tunnel to each ISP allows each to have its own virtually separate pipe. In
this example, the carrier is offering services to other ISPs over the UT3A interface. ISP A
has been allocated 5 Mbps and ISP B has been allocated 10 Mbps. The remaining 30
Mbps is being used by the carrier.
With ATM VP Tunnels, bandwidth is allocated in a round-robin fashion to all PVCs within
a Virtual Path for traffic shaping purposes. Remember that traffic shaping is only relevant
to outbound traffic. If a VP Tunnel has been configured, it is not possible to traffic shape at
the VC level. In other words, one can shape at the VC level or shape at the VP level, not
both from the ATM layer.
If VP shaping and VC shaping is desired, first configure the tunnel to perform VP-Shaping
and configure the VC for UBR. Next, configure a traffic-shape-profile and include this
profile in a policy. Finally, associate this policy with the IP interface on the ATM VC. This
approach is only possible with ASIC based line modules (4 port OC3 and 1 port OC12).
ATM VP Tunnels are supported on all ATM line modules.

Frame Relay, ATM and VLAN Overview Rev 3.2 Page 3- 19

 Configuring VP Tunnels
Outbound Traffic
VPI 0 5 Mbps U
ISP A

VPI 1 10 Mbps
ISP B

VPI 2 30 Mbps
Customers

• Configure the ATM interface

erx2(config)# interface atm 5/0
• Configure ATM vc-per-vp to allow additional VPs (UT3A/UE3A)
erx2(config-if)# atm vc-per-vp 32768
• Configure the ATM VP tunnels (OC3c, UT3A/UE3A)
- Configurable in Kbps
erx2(config-if)# atm vp-tunnel 0 5000
• Configure ATM Subinterface and PVCs

First configure the number of VCs per VP to allow additional VPs, if necessary. By
default, UT3/UE3 cards allow 4 VPS (VPI 0-3) with 65,536 VCs (older cards support fewer
VCs) and 4 port OC3c cards support 16 VPS (VPI 0-15). If additional VPs are required,
fewer VCs are supported per VP. To increase the number of VPs, use the the vc-per-vp
command and the following information:
T3/E3 #VPs 4 port OC3 VPs vc-per-vp
4 16 65536
8 32 32768
16 64 16384
32 128 8192
64 256 4096
128 256 2048
256 256 1024
256 256 512
256 256 256
NOTE: Carefully plan how many VPs will be required in your network. If additional VPs
are needed later, one must first delete any PVC and VP tunnel configurations BEFORE
the vc-per-vp can be executed.
NOTE: The 2 port OC3c line module does not support the vc-per-vp command.
To configure VP Tunnels, perform the following steps:
•Configure the ATM interface
•Configure the VCs-per-VPs, if necessary
•Configure the ATM VP tunnel, specifying the VPI and the tunnel’s traffic rate in 1Kbps
chunks.
•Configure the ATM Subinterface and PVCs in the VP Tunnel.

Frame Relay, ATM and VLAN Overview Rev 3.2 Page 3- 20

 How can I tell if ATM is working?
Think Layers!
• Network
- ping IP

- traceroute
- show ip int brief
- show ip int atm 2/0.33 ATM
- show ip route
• Data Link
- show atm int atm 5/0
- show atm vc Sonet/SDH

- show atm vc atm 5/0 33

- baseline interface atm 5/0 33 OC3
- show atm vc atm 5/0 33 delta UT3A/UE3A

- show atm vp-tunnels

- ping atm int atm 5/0.33 0 33 count 5 <end-Loopback> <seg-loopback>
<timeout>
• Physical
- show atm int atm 2/0

Ask yourself the following questions when initially troubleshooting a Routed 1483
configuration:
•Can I ping the peer router? If I can’t ping, start at the physical layer and work your way
up the stack to determine where the problem may be.
•Am I transmitting and receiving frames on the entire ATM interface?
•Am I receiving errors on the ATM interface?
•Am I transmitting and receiving frames on the specific ATM PVC?
•Am I receiving errors on the ATM PVC? Verify the encapsulation method being used. Is
it the same at each end of the PVC.
•Am I transmitting and receiving frames at the IP layer?
•Am I dropping packets?

Frame Relay, ATM and VLAN Overview Rev 3.2 Page 3- 21

 Connecting Virtual Routers using a single
Ethernet Interface - Will this work?

CT3

DPFE

DPFE

CT3
ISPA ISPA ISPA
ISPA
0 0
FR 192.168.9.1/24 192.168.9.1/24 FR

0 0
ISPB FR Ethernet FR ISPB
ISPB ISPB
1 1
1 1
192.168.33.1/24 192.168.33.1/24

2 Default Default 2
PPP 192.168.2.1/24 192.168.2.1/24 PPP

10.3.202.1/16 10.3.202.1/16
Customers 0 Customers
SRP 0 SRP

In this configuration, we would like to use a single port on an Dual Port Fast Ethernet
(DPFE) line module to connect our Virtual Routers together.
Can we use a single Fast Ethernet interface to accomplish this task?
No. Traditional Fast Ethernet connections only allow for 1 IP address per interface. Using
this simple approach, we could only connect 1 pair of Virtual Routers. To connect all
virtual router pairs, we would need 3 physical ports with 1 IP address per port.

Frame Relay, ATM and VLAN Overview Rev 3.2 Page 3- 22

 Connecting Virtual Routers using a
single Ethernet Interface and VLANs

DPFE
DPFE
CT3

CT3
ISPA ISPA ISPA
ISPA
0 0
FR 192.168.9.1/24 192.168.25.1/24 FR
VLAN id= 21
192.168.21.1/24 0 0 VLAN id = 21
192.168.21.2/24
ISPB FR Ethernet FR ISPB
ISPB ISPB
1 VLAN id = 31 VLAN id = 31 1
192.168.31.1/24 192.168.31.2/24

192.168.33.1/24 1 1 192.168.49.1/24

2 VLAN id = 41 VLAN id = 41
192.168.41.1/24
2
PPP 192.168.41.2/24 PPP
Default0 Default0
10.3.202.1/16 10.3.202.2/16
Customers 0 Customers
SRP 0 SRP

To connect multiple virtual routers using a single Ethernet (FE or GE)connection, one
must use Virtual LANs, or VLANs. As of software release 3.x.x, the ERX supports VLANS
using the 802.1q standard. Using this standard, each logical connection is assigned a
unique VLAN Subinterface and VLAN-id (0-4094).

Frame Relay, ATM and VLAN Overview Rev 3.2 Page 3- 23

 Ethernet Frame with IEEE 802.1q
Tag

7 1 6 6 4 2 4
S C
Source Destination
Preamble F TAG PID Data R
Address Address
D C

16 Bits 3 1 12 Bits
User
Tag Protocol ID Pri. CFI VLAN ID

In the 802.1q standard the IEEE introduced an optional tag field that can be inserted into an 802.x frame.
The Tag field is four bytes long and is inserted between the Destination MAC Address and the Protocol ID
fields. The Tag itself consists of a two byte Tag Protocol ID, located where the PID field would be in an
untagged frame. When a VLAN Tag is included in a frame the TPID is set to 0x8100. The TPID is followed
by a three bit User Priority field, a Canonical Format Identifier (CFI) for use in source routed environments
when a RIF field is present, and finally the 12 bit VLAN ID. The twelve bit field allows support for up to 4095
VLAN’s per interface.

Support for IEEE 802.1q allows the ERX to support three different interface modes on an Ethernet interface;

Single Protocol Non VLAN- Essentially the same service that has been configurable in earlier
versions, one IP interface per Ethernet interface.
Single Protocol VLAN - Allows us to configure multiple logical interfaces on an single physical
interface. Used to allow multiple virtual routers to have IP interfaces on a single Ethernet port.
Multi Protocol VLAN - Allows the configuration of multiple upper layer interfaces one a VLAN
interface. Used to configure a mix of IP and PPPoE interfaces on an Ethernet port.

Frame Relay, ATM and VLAN Overview Rev 3.2 Page 3- 24

 Configuring Single Protocol
Non VLAN Ethernet Interfaces

ERX1(config)#interface FastEthernet 3/0

IP Interface
ERX1(config-if)#ip address 192.168.11.1 255.255.255.0 192.168.11.1
ERX1(config-if)#desc single mode interface

• Once an interface is configured to support a

single protocol in non-VLAN mode, VLANs
cannot be added. The original IP interface must
FE/GE
first be deleted.

Single Mode Non VLAN Ethernet interface configuration is unchanged from earlier
versions of ERX software. From Global Configuration mode of the command line interface
use the interface command to build the Ethernet interface then assign an IP address the
to interface. Once an interface is configured to support this mode, VLANs can not be
added unless the original IP configuration is deleted.
ERX1(config)#interface FastEthernet 3/0
ERX1(config-if)#ip address 192.168.11.1 255.255.255.0
ERX1(config-if)#desc single mode interface
ERX1(config-if)#encap vlan
% Add VLAN major interface failed (interface already bound to ethernet
interface)
ERX1(config-if)#int fast 3/0.11
^
% Can't create Ethernet sub-interface (not in sub-interface mode)
ERX1(config)#int fast 3/0
ERX1(config-if)#no ip add 192.168.11.1 255.255.255.0
ERX1(config-if)#encap vlan
ERX1(config-if)#int fast 3/0.21
ERX1(config-if)#ip add 192.168.21.1 255.255.255.0
ERX1(config-if)#vlan id 21

Frame Relay, ATM and VLAN Overview Rev 3.2 Page 3- 25

 Configuring Single Protocol VLAN
Ethernet Interfaces
IP Interface IP Interface IP Interface
192.168.21.1 192.168.31.1 192.168.41.1

VLAN Subinterface VLAN Subinterface VLAN Subinterface

VLAN id 21 VLAN id 31 VLAN id 41

ERX1:ispa0(config)#int fast 3/0

ERX1:ispa0(config-if)#encap vlan
ERX1:ispa0(config-if)#int fast 3/0.21 FE/GE
ERX1:ispa0(config-if)#vlan id 21
ERX1:ispa0(config-if)#ip add 192.168.21.1 255.255.255.0
ERX1:ispa0(config-if)#vir ispb0
Proceed with new virtual-router creation? [confirm]
ERX1:ispb0(config)#int fast 3/0.31
ERX1:ispb0(config-if)#vlan id 31
ERX1:ispb0(config-if)#ip add 192.168.31.1 255.255.255.0
• To transmit untagged frames, use the command vlan id 0 untagged

To emulate ATM or Frame Relay functionality on an Ethernet Interface, use Single

Protocol VLAN configuration on the ERX. This mode allows us to configure multiple
logical connections or VLANs on a single physical interface. To configure this service, we
will specify a new encapsulation method on the Ethernet interface using the
encapsulation vlan configuration command. This command allows us to configure
multiple subinterfaces per physical port. Each subinterface is then assigned a unique
VLAN id. This VLAN id allows us to put the IP interfaces in separate Virtual Routers in the
ERX. Remember that the layer 1 and layer 2 assignments are global in nature and the
VLAN id does not get bound to a virtual router until an IP address is assigned to the
subinterface.
ERX1(config)#vir ispa0
ERX1:ispa0(config)#int fast 3/0
ERX1:ispa0(config-if)#encap vlan
ERX1:ispa0(config-if)#int fast 3/0.21
ERX1:ispa0(config-if)#vlan id 21
ERX1:ispa0(config-if)#ip add 192.168.21.1 255.255.255.0
ERX1:ispa0(config-if)#vir ispb0
Proceed with new virtual-router creation? [confirm]
ERX1:ispb0(config)#int fast 3/0.31
ERX1:ispb0(config-if)#vlan id 31
ERX1:ispb0(config-if)#ip add 192.168.31.1 255.255.255.0
ERX1:ispb0(config-if)#int fast 3/0.41
ERX1:ispb0(config-if)#vir default0
Proceed with new virtual-router creation? [confirm]
ERX1:default0(config)#int fast 3/0.41
ERX1:default0(config-if)#vlan id 41
ERX1:default0(config-if)#ip add 192.168.41.1 255.255.255.0
ERX1:default0(config-if)#int loop 1
ERX1:default0(config-if)#ip add 192.168.42.1 255.255.255.0

Frame Relay, ATM and VLAN Overview Rev 3.2 Page 3- 26