Lab 4.2.2.7 - Configuring Frame Relay and Subinterfaces (Our Routers Are F0/0, Substitute For "G0/0")

Lab 4.2.2.
7– Configuring Frame Relay and Subinterfaces

(our routers are F0/0, substitute for “G0/0”)
.
Topology
© 2013 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 1 of 11
Lab – Configuring Frame Relay and Subinterfaces
Addressing Table
Device Interface IPv4 and IPv6 Address Default Gateway
192.168.1.1/24
2001:DB8:ACAD:A::1/64
R1 G0/0 FE80::1 link-local N/A
10.1.1.1/30
2001:DB8:ACAD:B::1/64
S0/0/0 (DCE) FE80::1 link-local N/A
FR S0/0/0 N/A N/A
S0/0/1 (DCE) N/A N/A
192.168.3.1/24
2001:DB8:ACAD:C::3/64
R3 G0/0 FE80::3 link-local N/A
10.1.1.2/30
2001:DB8:ACAD:B::3/64
S0/0/1 FE80::3 link-local N/A
192.168.1.3/24 192.168.1.1
PC-A NIC 2001:DB8:ACAD:A::A/64 FE80::1
192.168.3.3/24 192.168.3.1
PC-C NIC 2001:DB8:ACAD:C::C/64 FE80::3
Objectives
Part 1: Build the Network and Configure Basic Device Settings
Part 2: Configure a Frame Relay Switch
Part 3: Configure Basic Frame Relay
Part 4: Troubleshoot Frame Relay
Part 5: Configure a Frame Relay Subinterface
Background / Scenario
Frame Relay is a high-performance WAN protocol that operates at the physical and data link layers of the OSI
reference model. Unlike leased lines, Frame Relay requires only a single access circuit to the Frame Relay
provider to communicate with multiple sites that are connected to the same provider.
Frame Relay was one of the most extensively used WAN protocols, primarily because it was relatively
inexpensive compared to dedicated lines. In addition, configuring user equipment in a Frame Relay network is
fairly simple. With the advent of broadband services such as DSL and cable modem, GigaMAN (point-to-point
Ethernet service over fiber-optic cable), VPN, and Multiprotocol Label Switching (MPLS), Frame Relay has
become a less desirable solution for accessing the WAN. However, some rural areas do not have access to
these alternative solutions and still rely on Frame Relay for connectivity to the WAN.
In this lab, you will configure Frame Relay encapsulation on serial links. You will also configure a router to
simulate a Frame Relay switch. You will review Cisco standards and open standards that apply to Frame
Relay. You will also configure Frame Relay point-to-point subinterfaces.
Note: The routers used with CCNA hands-on labs are Cisco 1941 Integrated Services Routers (ISRs) with
Cisco IOS Release 15.2(4)M3 (universalk9 image). Other routers and Cisco IOS versions can be used.
Depending on the model and Cisco IOS version, the commands available and output produced might vary
from what is shown in the labs. Refer to the Router Interface Summary Table at the end of this lab for the
correct interface identifiers.
Note: Make sure that the routers have been erased and have no startup configurations. If you are unsure,
contact your instructor.
Required Resources
 3 Routers (Cisco 1941 with Cisco IOS Release 15.2(4)M3 universal image or comparable)
 2 PCs (Windows 7, Vista, or XP with terminal emulation program, such as Tera Term)
 Console cables to configure the Cisco IOS devices via the console ports
 Ethernet and serial cables as shown in the topology
Part 1: Build the Network and Configure Basic Device Settings

In Part 1, you will set up the network topology and configure basic settings on the PC hosts and routers.
Step 1: Cable the network as shown in the topology.
Step 2: Initialize and reload the routers as necessary.
Step 3: Configure basic settings for each router.

a. Disable DNS lookup.
b. Configure device names as shown in the topology.
c. Assign class as the privileged EXEC mode password.
d. Assign cisco as the console and vty passwords and enable login.
e. Configure logging synchronous for the console line.
f. Encrypt the plain text passwords.
g. Configure a MOTD banner to warn users that unauthorized access is prohibited.
h. Set the clocking rate for all DCE serial interfaces to 128000.
i. Configure the IPv4 and IPv6 addresses listed in the Addressing Table for all interfaces. Do not activate
the serial interfaces at this time.
j. Copy the running configuration to the startup configuration.
Step 4: Configure PC hosts.

Refer to the Addressing Table for PC host address information.
Step 5: Test connectivity.

At this point, the PCs will not be able to ping each other, but they should be able to ping their default gateway.
Test both protocols, IPv4 and IPv6. Verify and troubleshoot if necessary.
Part 2: Configure a Frame Relay Switch

In Part 2, you will configure a Frame Relay switch. You will create permanent virtual circuits (PVCs) and
assign Data Link Connection Identifiers (DLCIs). This configuration creates two PVCs: one from R1 to R3
(DLCI 103), and one from R3 to R1 (DLCI 301).
Step 1: Configure the FR router as a Frame Relay switch.

The frame-relay switching command enables Frame Relay switching globally on a router, allowing it to
forward frames based on the incoming DLCI rather than an IP address.
FR(config)# frame-relay switching
Step 2: Change the interface encapsulation on S0/0/0.

Change the interface encapsulation type to Frame Relay. Like HDLC or PPP, Frame Relay is a data-link layer
protocol that specifies the framing of Layer 2 traffic.
FR(config)# interface s0/0/0
FR(config-if)# encapsulation frame-relay
Step 3: Change the interface type to DCE.

Changing the interface type to DCE tells the router to send Local Management Interface (LMI) keepalives and
allows Frame Relay route statements to be applied.
Note: Frame Relay interface types do not need to match the underlying physical interface type. A physical
DTE serial interface can act as a Frame Relay DCE interface, and a physical DCE interface can act as a
logical Frame Relay DTE interface.
FR(config-if)# frame-relay intf-type dce
Step 4: Configure DLCI.

Configure the router to forward incoming traffic on interface S0/0/0 with DLCI 103 to S0/0/1 with an output of
DLCI of 301.
FR(config-if)# frame-relay route 103 interface s0/0/1 301
FR(config-if)# no shutdown
Step 5: Configure Frame Relay on S0/0/1.

FR(config-if)# encapsulation frame-relay
FR(config-if)# frame-relay intf-type dce
FR(config-if)# frame-relay route 301 interface s0/0/0 103
FR(config-if)# no shutdown
Step 6: Verify Frame Relay configuration.

a. Use the show frame-relay pvc command to verify that Frame Relay is configured correctly.
FR# show frame-relay pvc
PVC Statistics for interface Serial0/0/0 (Frame Relay DCE)
Active Inactive Deleted Static

Local 0 0 0 0
Switched 0 1 0 0
Unused 0 0 0 0
DLCI = 103, DLCI USAGE = SWITCHED, PVC STATUS = INACTIVE, INTERFACE = Serial0/0/0
input pkts 0 output pkts 0 in bytes 0

out bytes 0 dropped pkts 0 in pkts dropped 0
out pkts dropped 0 out bytes dropped 0
in FECN pkts 0 in BECN pkts 0 out FECN pkts 0
out BECN pkts 0 in DE pkts 0 out DE pkts 0
out bcast pkts 0 out bcast bytes 0
30 second input rate 0 bits/sec, 0 packets/sec
30 second output rate 0 bits/sec, 0 packets/sec
switched pkts 0
Detailed packet drop counters:
no out intf 0 out intf down 0 no out PVC 0
in PVC down 0 out PVC down 0 pkt too big 0
shaping Q full 0 pkt above DE 0 policing drop 0
connected to interface Serial0/0/1 301
pvc create time 00:00:53, last time pvc status changed 00:00:53
PVC Statistics for interface Serial0/0/1 (Frame Relay DCE)

Local 0 0 0 0
Switched 0 1 0 0
Unused 0 0 0 0
DLCI = 301, DLCI USAGE = SWITCHED, PVC STATUS = INACTIVE, INTERFACE = Serial0/0/1

30 second input rate 0 bits/sec, 0 packets/sec
30 second output rate 0 bits/sec, 0 packets/sec
switched pkts 0
Detailed packet drop counters:
no out intf 0 out intf down 0 no out PVC 0
in PVC down 0 out PVC down 0 pkt too big 0
shaping Q full 0 pkt above DE 0 policing drop 0
connected to interface Serial0/0/0 103
b. Issue the show frame-relay route command. This is the Layer 2 route that Frame Relay traffic takes
through the network. (Do not confuse this with Layer 3 IP routing.)
FR# show frame-relay route

Input Intf Input Dlci Output Intf Output Dlci Status
Serial0/0/0 103 Serial0/0/1 301 inactive
Serial0/0/1 301 Serial0/0/0 103 inactive
Part 3: Configure Basic Frame Relay

In Part 3, you will configure Frame Relay on routers R1 and R3. After Frame Relay is configured, you will
enable the EIGRP routing protocol to provide end-to-end connectivity.
Step 1: Configure R1 for Frame Relay.

Inverse ARP allows distant ends of a Frame Relay link to discover each other dynamically, and provides a
dynamic method of mapping IP addresses to DLCIs. Although Inverse ARP is useful, it is not always reliable.
The best practice is to map IP addresses to DLCIs statically and disable Inverse ARP.
a. Change the encapsulation on S0/0/0 to Frame Relay.
R1(config)# interface s0/0/0
R1(config-if)# encapsulation frame-relay
b. Use the no frame-relay inverse-arp command to disable Inverse ARP.
R1(config-if)# no frame-relay inverse-arp
c. Use the frame-relay map command to map an IP address to a DLCI statically. In addition to mapping an
IP to a DLCI, Cisco IOS software allows several other Layer 3 protocol addresses to be mapped. In the
following command, the broadcast keyword sends any multicast or broadcast traffic destined for this link
over the DLCI. Most routing protocols require the broadcast keyword to function properly over Frame
Relay. You can use the broadcast keyword on multiple DLCIs on the same interface. The traffic is
replicated to all PVCs.
Note: The IPv6 Frame Relay map to a global unicast address does not include the broadcast keyword.
However, the broadcast keyword is used in the mapping to the link-local address. IPv6 routing protocols
use link-local addresses for multicast routing updates; therefore, only the link-local address map requires
the broadcast keyword to forward multicast packets.
R1(config-if)# frame-relay map ip 10.1.1.2 103 broadcast
R1(config-if)# frame-relay map ipv6 2001:db8:acad:b::3 103
R1(config-if)# frame-relay map ipv6 fe80::3 103 broadcast
d. For the router to ping its own interface, the DLCI must be created to map to the local interface.
R1(config-if)# frame-relay map ip 10.1.1.1 103
e. Use the no shutdown command to activate S0/0/0.
R1(config-if)# no shutdown
Step 2: Configure R3 for Frame Relay.

R3(config-if)# encapsulation frame-relay
R3(config-if)# no frame-relay inverse-arp
R3(config-if)# frame-relay map ip 10.1.1.1 301 broadcast

R3(config-if)# frame-relay map ipv6 fe80::1 301 broadcast
R3(config-if)# frame-relay map ip 10.1.1.2 301
R3(config-if)# no shutdown
Why is the no shutdown command used after the no frame-relay inverse-arp command?
_______________________________________________________________________________________
_______________________________________________________________________________________
_______________________________________________________________________________________
If you type the no shutdown command first, Inverse ARP may cause Frame Relay to learn Layer 2 to Layer 3
mappings that you may not want. By turning off the Frame Relay Inverse ARP before issuing the no
shutdown command, you ensure that only the statically mapped connections that you want are part of the
Frame Relay maps.
Step 3: Verify that Frame Relay is active.

a. You should now be able to ping R3 from R1. It may take several seconds after bringing up the interfaces
for the PVCs to become active.
R1# ping 10.1.1.2
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.1.1.2, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 28/30/40 ms
R1# ping 2001:db8:acad:b::3
Sending 5, 100-byte ICMP Echos to 2001:DB8:ACAD:B::3, timeout is 2 seconds:
!!!!!
b. Ping R1 from R3.
R3# ping 10.1.1.1
Sending 5, 100-byte ICMP Echos to 10.1.1.1, timeout is 2 seconds:
!!!!!
R3# ping 2001:db8:acad:b::1
Sending 5, 100-byte ICMP Echos to 2001:DB8:ACAD:B::1, timeout is 2 seconds:
!!!!!
c. Issue the show frame-relay pvc command to display PVC status information on R1 and R3.
R1# show frame-relay pvc
PVC Statistics for interface Serial0/0/0 (Frame Relay DTE)
Local 1 0 0 0
Switched 0 0 0 0
Unused 0 0 0 0
DLCI = 103, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial0/0/0

5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
R3# show frame-relay pvc
PVC Statistics for interface Serial0/0/1 (Frame Relay DTE)

Local 1 0 0 0
Switched 0 0 0 0
Unused 0 0 0 0
DLCI = 301, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial0/0/1

5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
d. Issue the show frame-relay route command on FR to verify that status of the Frame Relay map
statements.
FR# show frame-relay route
Input Intf Input Dlci Output Intf Output Dlci Status
Serial0/0/0 103 Serial0/0/1 301 active
Serial0/0/1 301 Serial0/0/0 103 active
e. Issue the show frame-relay map command on R1 and R3 to display a summary of the static and
dynamic mappings of Layer 3 addresses to DLCIs. Because Inverse ARP has been turned off, there are
only static maps.
R1# show frame-relay map
Serial0/0/0 (up): ipv6 FE80::3 dlci 103(0x67,0x1870), static,
broadcast,
CISCO, status defined, active

Serial0/0/0 (up): ipv6 2001:DB8:ACAD:B::1 dlci 103(0x67,0x1870), static,
Serial0/0/0 (up): ip 10.1.1.1 dlci 103(0x67,0x1870), static,
Serial0/0/0 (up): ipv6 2001:DB8:ACAD:B::3 dlci 103(0x67,0x1870), static,
Serial0/0/0 (up): ip 10.1.1.2 dlci 103(0x67,0x1870), static,
broadcast,
R3# show frame-relay map

Serial0/0/1 (up): ipv6 FE80::1 dlci 301(0x12D,0x48D0), static,
broadcast,
Serial0/0/1 (up): ipv6 2001:DB8:ACAD:B::3 dlci 301(0x12D,0x48D0), static,
Serial0/0/1 (up): ip 10.1.1.2 dlci 301(0x12D,0x48D0), static,
Serial0/0/1 (up): ipv6 2001:DB8:ACAD:B::1 dlci 301(0x12D,0x48D0), static,
Serial0/0/1 (up): ip 10.1.1.1 dlci 301(0x12D,0x48D0), static,
broadcast,
Note: The FR router acts as a Layer 2 device, so there is no need to map Layer 3 addresses to Layer 2
DLCIs.
Step 4: Configure EIGRP on R1 and R3.

a. Enable IPv6 routing on R1 and R3.
R1(config)# ipv6 unicast-routing
R3(config)# ipv6 unicast-routing

b. Using AS 1, enable EIGRP for IPv4 and IPv6 on R1 and R3 for all networks. Set the router ID for R1 as
1.1.1.1 and 3.3.3.3 for R3.
R1(config)# router eigrp 1
R1(config-router)# no auto-summary
R1(config-router)# eigrp router-id 1.1.1.1
R1(config-router)# network 10.1.1.0 0.0.0.3
R1(config-router)# network 192.168.1.0
R1(config-rtr)# no shutdown
R1(config-router)# ipv6 router eigrp 1

R1(config-rtr)# router-id 1.1.1.1
R1(config-rtr)# interface g0/0
R1(config-if)# ipv6 eigrp 1
R1(config-if)# interface s0/0/0
R3(config)# router eigrp 1

R3(config-router)# no auto-summary
R3(config-router)# eigrp router-id 3.3.3.3
R3(config-router)# network 10.1.1.0 0.0.0.3
R3(config-router)# network 192.168.3.0
R3(config-router)# ipv6 router eigrp 1
R3(config-rtr)# router-id 3.3.3.3
R3(config-rtr)# no shutdown
R3(config-rtr)# interface g0/0
R3(config-if)# interface s0/0/1
Step 5: Verify end-to-end connectivity.

Ping PC-C from PC-A. If your pings were unsuccessful, troubleshoot until you have end-to-end connectivity.
Note: It may be necessary to disable the PC firewall for pings to be successful.
Reflection
1. What is a PVC and how is it used?
_______________________________________________________________________________________
_______________________________________________________________________________________
_______________________________________________________________________________________
2. What is the purpose of a DLCI?
_______________________________________________________________________________________
Router Interface Summary Table
Router Interface Summary
Router Model Ethernet Interface #1 Ethernet Interface #2 Serial Interface #1 Serial Interface #2
1800 Fast Ethernet 0/0 Fast Ethernet 0/1 Serial 0/0/0 (S0/0/0) Serial 0/0/1 (S0/0/1)
(F0/0) (F0/1)
1900 Gigabit Ethernet 0/0 Gigabit Ethernet 0/1 Serial 0/0/0 (S0/0/0) Serial 0/0/1 (S0/0/1)
(G0/0) (G0/1)
(F0/0) (F0/1)
(F0/0) (F0/1)
2900 Gigabit Ethernet 0/0 Gigabit Ethernet 0/1 Serial 0/0/0 (S0/0/0) Serial 0/0/1 (S0/0/1)
(G0/0) (G0/1)
Note: To find out how the router is configured, look at the interfaces to identify the type of router and how many
interfaces the router has. There is no way to effectively list all the combinations of configurations for each router
class. This table includes identifiers for the possible combinations of Ethernet and Serial interfaces in the device.
The table does not include any other type of interface, even though a specific router may contain one. An
example of this might be an ISDN BRI interface. The string in parenthesis is the legal abbreviation that can be
used in Cisco IOS commands to represent the interface.

Lab 4.2.2.7 - Configuring Frame Relay and Subinterfaces (Our Routers Are F0/0, Substitute For "G0/0")

Uploaded by

Copyright:

Available Formats

Lab 4.2.2.7 - Configuring Frame Relay and Subinterfaces (Our Routers Are F0/0, Substitute For "G0/0")

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Lab 4.2.2.7 - Configuring Frame Relay and Subinterfaces (Our Routers Are F0/0, Substitute For "G0/0")

Uploaded by

Copyright:

Available Formats

Lab 4.2.2.

7– Configuring Frame Relay and Subinterfaces

Device Interface IPv4 and IPv6 Address Default Gateway

Part 1: Build the Network and Configure Basic Device Settings

Step 1: Cable the network as shown in the topology.

Step 2: Initialize and reload the routers as necessary.

Step 3: Configure basic settings for each router.

Step 4: Configure PC hosts.

Step 5: Test connectivity.

Part 2: Configure a Frame Relay Switch

Step 1: Configure the FR router as a Frame Relay switch.

Step 2: Change the interface encapsulation on S0/0/0.

Step 3: Change the interface type to DCE.

Step 4: Configure DLCI.

Step 5: Configure Frame Relay on S0/0/1.

Step 6: Verify Frame Relay configuration.

PVC Statistics for interface Serial0/0/0 (Frame Relay DCE)

Active Inactive Deleted Static

input pkts 0 output pkts 0 in bytes 0

PVC Statistics for interface Serial0/0/1 (Frame Relay DCE)

Active Inactive Deleted Static

input pkts 0 output pkts 0 in bytes 0

FR# show frame-relay route

Part 3: Configure Basic Frame Relay

Step 1: Configure R1 for Frame Relay.

Step 2: Configure R3 for Frame Relay.

R3(config-if)# frame-relay map ip 10.1.1.1 301 broadcast

Step 3: Verify that Frame Relay is active.

PVC Statistics for interface Serial0/0/0 (Frame Relay DTE)

Active Inactive Deleted Static

input pkts 22 output pkts 154 in bytes 2240

R3# show frame-relay pvc

PVC Statistics for interface Serial0/0/1 (Frame Relay DTE)

Active Inactive Deleted Static

input pkts 158 output pkts 22 in bytes 11156

CISCO, status defined, active

R3# show frame-relay map

Step 4: Configure EIGRP on R1 and R3.

R3(config)# ipv6 unicast-routing

R1(config-router)# ipv6 router eigrp 1

R1(config-if)# ipv6 eigrp 1

R3(config)# router eigrp 1

Step 5: Verify end-to-end connectivity.

Router Interface Summary Table

Router Interface Summary

You might also like