The document describes configuring a basic Frame Relay network with three routers and two PCs. It involves:
1) Building the network topology and configuring basic settings on routers and PCs like IP addresses but not activating serial interfaces.
2) Configuring one router as a Frame Relay switch by enabling switching, changing encapsulation to Frame Relay, and configuring two PVCs between router interfaces with DLCIs.
3) Verifying the Frame Relay configuration using show commands.
The document describes configuring a basic Frame Relay network with three routers and two PCs. It involves:
1) Building the network topology and configuring basic settings on routers and PCs like IP addresses but not activating serial interfaces.
2) Configuring one router as a Frame Relay switch by enabling switching, changing encapsulation to Frame Relay, and configuring two PVCs between router interfaces with DLCIs.
3) Verifying the Frame Relay configuration using show commands.
The document describes configuring a basic Frame Relay network with three routers and two PCs. It involves:
1) Building the network topology and configuring basic settings on routers and PCs like IP addresses but not activating serial interfaces.
2) Configuring one router as a Frame Relay switch by enabling switching, changing encapsulation to Frame Relay, and configuring two PVCs between router interfaces with DLCIs.
3) Verifying the Frame Relay configuration using show commands.
The document describes configuring a basic Frame Relay network with three routers and two PCs. It involves:
1) Building the network topology and configuring basic settings on routers and PCs like IP addresses but not activating serial interfaces.
2) Configuring one router as a Frame Relay switch by enabling switching, changing encapsulation to Frame Relay, and configuring two PVCs between router interfaces with DLCIs.
3) Verifying the Frame Relay configuration using show commands.
Objectives Part 1: Build the Network and Configure Basic Device Settings Part 2: Configure a Frame Relay Switch Part 3: Configure Basic Frame Relay
Page 1 of 8 Lab – Configuring Frame Relay
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. Note: Make sure that the routers have been erased and have no startup configurations. If you are unsure, contact your instructor.
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. Router#Enable Router#CONFIG T Router(config)# no ip domain lookup b. Configure device names as shown in the topology. Router(config)#hostname R1 Router(config)#hostname FR Router(config)#hostname R3 c. Assign class as the privileged EXEC mode password. Branch1(config)# enable secret class d. Encrypt the plain text passwords. Branch1(config)#service password-encryption e. Configure a MOTD banner to warn users that unauthorized access is prohibited. Branch1(config)#service password-encryption f. Set the clocking rate for all DCE serial interfaces to 128000. g. Configure the IPv4 addresses listed in the Addressing Table for all interfaces. Do not activate the serial interfaces at this time. R1(config)#interface s0/0/0 Lab – Configuring Frame Relay
Refer to the Addressing Table for PC host address information. Lab – Configuring Frame Relay
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 . 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)# interface s0/0/0 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
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)
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 Lab – Configuring Frame Relay
connected to interface Serial0/0/0 103
pvc create time 00:00:16, last time pvc status changed 00:00:16
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.
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. a. Change the encapsulation on S0/0/0 to Frame Relay. R1(config)# interface s0/0/0 R1(config-if)# encapsulation frame-relay
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 !!!!!
b. Ping R1 from R3.
R3# ping 10.1.1.1 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 10.1.1.1, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 28/28/28 ms
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)
out bytes 10860 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 134 out bcast bytes 8780 5 minute input rate 0 bits/sec, 0 packets/sec 5 minute output rate 0 bits/sec, 0 packets/sec pvc create time 01:59:40, last time pvc status changed 01:55:14
R3# show frame-relay pvc
PVC Statistics for interface Serial0/0/1 (Frame Relay DTE)
out bytes 2240 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 2 out bcast bytes 160 5 minute input rate 0 bits/sec, 0 packets/sec 5 minute output rate 0 bits/sec, 0 packets/sec pvc create time 01:57:20, last time pvc status changed 01:56:19
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
Step 4: Verify end-to-end connectivity.
Ping PC-C from PC-A. If your pings were unsuccessful, troubleshoot until you have end-to-end connectivity. Lab – Configuring Frame Relay
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? A PVC is a permanent virtual circuit. This is a Layer 2 connection created between endpoints through a Frame Relay cloud. There can be multiple PVCs per physical interface, allowing multiple point-to- point connections or point-to-multipoint connection. 2. What is the purpose of a DLCI? DTE device will identify VC from DLCI number. Whatever number (usually 17 to 1000) we use here, we must have to use the same number at DTE. DLCI number must be unique for a frame relay interface. 3. What purpose does the Local Management Interface (LMI) serve in a Frame Relay network? The LMI is a signaling protocol that exchanges information between a router and a Frame Relay switch. The LMI exchanges information on keepalives, PVC status (active, inactive, deleted, unused), and IP addresses (when Inverse ARP is enabled). This information is used as a status mechanism between the router (DTE) and the Frame Relay switch (DCE).
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) 2801 Fast Ethernet 0/0 Fast Ethernet 0/1 Serial 0/1/0 (S0/1/0) Serial 0/1/1 (S0/1/1) (F0/0) (F0/1) 2811 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) 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.
