Lab 5.2.5 Configuring Frame Relay Subinterfaces – Instructor Version 1700

Lab 5.2.5 Configuring Frame Relay Subinterfaces – Instructor Version 1700 

Objective 

• Configure three routers in a full-mesh Frame Relay network. 

Background/Preparation 

An Adtran Atlas550 Frame Relay emulator is used to simulate the Frame Relay switch/cloud. 

Cable a network similar to the one in the diagram above. Any router that meets the interface 

requirements displayed on the above diagram may be used. This includes the following and any of 

their possible combinations: 

• 800 series routers 


• 1700 series routers 



Please refer to the chart at the end of the lab to correctly identify the interface identifiers to be used 

based on the equipment in the lab. The configuration output used in this lab is produced from 1721 

series routers. Any other router used may produce slightly different output. Conduct the following 

steps on each router unless specifically instructed otherwise. 

149 - 489 CCNA 4: WAN Technologies v 3.1 - Lab 5.2.5 Copyright © 2003, Cisco Systems, Inc.

Start a HyperTerminal session. 

Note: Refer to the erase and reload instructions at the end of this lab. Perform those steps on all 

routers in this lab assignment before continuing. 

Step 1 Configure the routers 

Configure the following according to the chart: 

• The hostname 

• The console password 

• The virtual terminal password 

• The enable secret password 

• The Fast Ethernet interface according to the chart 

If problems occur during this configuration, refer to Lab 1.1.4a Configuring NAT. 

Step 2 Configure the Serial 0 Interfaces 

a. First, the Frame Relay encapsulation type to be used on this link must be defined using the 

following commands: 

Amsterdam#configure terminal 

Amsterdam(config)#interface serial 0 

Amsterdam(config-if)#encapsulation frame-relay ietf 

Amsterdam(config-if)#frame-relay lmi-type ansi 

b. Use a description field to store relevant information, such as the circuit number in case a line 

fault has to be reported: 

Amsterdam(config-if)#description Circuit #KPN465555 

Amsterdam(config-if)#no shutdown 

c. The same commands are used to configure the Berlin and Paris routers: 

Paris(config)#interface serial 0 

Paris(config-if)#encapsulation frame-relay ietf 

Paris(config-if)#frame-relay lmi-type ansi 

Paris(config-if)#description Circuit #FRT372826 

Paris(config-if)#no shutdown 

Berlin(config)#interface serial 0 

Berlin(config-if)#encapsulation frame-relay ietf 

Berlin(config-if)#frame-relay lmi-type ansi 

Berlin(config-if)#description Circuit #DTK465866 

Berlin(config-if)#no shutdown 


Step 3 Create subinterfaces on the Amsterdam router 

For each of the permanent virtual circuits (PVCs), create a subinterface on the serial port. This 

subinterface will be a point-to-point configuration. For consistency and future troubleshooting, 

use the data-link connection identifier (DLCI) number as the subinterface number. The 

commands to create a subinterface are as follows: 

Amsterdam(config-if)#interface serial 0.102 point-to-point 

Amsterdam(config-if)#description PVC to Paris, DLCI 102, Contact Rick 

Voight(+33-1-5534-2234) Circuit #FRT372826 

Amsterdam(config-if)#ip address 192.168.4.1 255.255.255.0 

Amsterdam(config-if)#frame-relay interface-dlci 102 


Amsterdam(config-if)#description PVC to Berlin, DLCI 103, Contact P 

Wills(+49- 61 03 / 7 65 72 00) Circuit #DTK465866 



Step 4 Create subinterfaces on the Paris router 

To configure the subinterfaces on the Paris router, use the following commands: 

Paris(config-if)#interface Serial 0.201 point-to-point 

Paris(config-if)#description PVC to Amsterdam, DLCI 201, Contact Peter 

Muller (+31 20 623 32 67) Circuit #KPN465555 

Paris(config-if)#ip address 192.168.4.2 255.255.255.0 

Paris(config-if)#frame-relay interface-dlci 201 


Paris(config-if)#description PVC to Berlin, DLCI 203, Contact Peter 

Willis (+49- 61 03 / 7 66 72 00) Circuit #DTK465866 



Step 5 Create subinterfaces on the Berlin router 

To configure the subinterfaces on the Berlin router, use the following commands: 

Berlin(config-if)#interface Serial 0.301 point-to-point 

Berlin(config-if)#description PVC to Amsterdam, DLCI 301, Contact Peter 


Berlin(config-if)#ip address 192.168.5.2 255.255.255.0 

Berlin(config-if)#frame-relay interface-dlci 301 


Berlin(config-if)#description PVC to Paris, DLCI 302, Contact Rick 

Voight (+33-1-5534-2234) Circuit #FRT372826 




Step 6 Configure IGRP routing 

To configure the routing protocol Interior Gateway Routing Protocol (IGRP) 100, use the following 

configuration syntax: 

Amsterdam(config-if)#router igrp 100 

Amsterdam(config-router)#network 192.168.1.0 



Paris(config-if)#router igrp 100 

Paris(config-router)#network 192.168.2.0 



Berlin(config-if)#router igrp 100 

Berlin(config-router)#network 192.168.3.0 



Note to instructor: The user should be in the global configuration mode when issuing the 

router igrp 100 command. In the online curricuclum, the prompt shows the interface mode, 

which is incorrect. 

Step 7 Verifying Frame Relay PVC 

a. On the Amsterdam router, issue the command show frame-relay pvc: 

Amsterdam#show frame-relay pvc 

b. How many active local PVCs are there? 2 

c. What is the interface value? Serial0.102, Serial0.103 

d. What is the PVC status? Active 

e. Which DLCI # is inactive? 104 

f. From this it can be seen that there are three DLCIs defined on this Frame Relay circuit, and only 

two of them are in use. This is the way the Adtran 550 emulator has been configured. It is useful 

output, as it shows what would be seen if a DLCI is defined on the Frame Relay switch, but not 

configured on the router. The other DLCIs, 102 and 103, are ACTIVE and associated with their 

respective subinterfaces. It also shows that some packets have actually passed across the PVC. 


PVC Statistics for interface Serial0 (Frame Relay DTE) 

Active Inactive Deleted Static 

Local 2 1 0 0 

Switched 0 0 0 0 

Unused 0 0 0 0 

DLCI = 102, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = 

Serial0.102 

input pkts 13 output pkts 14 in bytes 2180 

out bytes 2254 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 14 out bcast bytes 2254 

pvc create time 00:14:27, last time pvc status changed 00:02:59 


Serial0.103 








DLCI = 104, DLCI USAGE = LOCAL, PVC STATUS = INACTIVE, INTERFACE = 

Serial0 








Step 8 Show the Frame Relay maps 

a. Look at the frame relay maps by typing the command show frame-relay map at the 

privileged EXEC mode prompt: 

Amsterdam#show frame-relay map 

b. What is the status of the links? Up 

c. The DLCIs are defined as what type? Point-to-Point 

d. Are the DLCIs the same on the Paris router? No 


Serial0.103 (up): point-to-point dlci, dlci 103(0x67,0x1870), broadcast 

status defined, active 



Step 9 Show LMIs 

a. Look at the Local Management Interface (LMI) statistics using the show frame-relay lmi 

command: 

Amsterdam#show frame-relay lmi 

b. Which fields have non-zero counter values? Num Status Enq. Sent, Num Status msgs Rcvd 

c. What is the LMI type? ANSI 


LMI Statistics for interface Serial0 (Frame Relay DTE) LMI TYPE = ANSI 


Invalid Unnumbered info 0 Invalid Prot Disc 0 

Invalid dummy Call Ref 0 Invalid Msg Type 0 

Invalid Status Message 0 Invalid Lock Shift 0 

Invalid Information ID 0 Invalid Report IE Len 0 

Invalid Report Request 0 Invalid Keep IE Len 0 

Num Status Enq. Sent 55 Num Status msgs Rcvd 56 

Num Update Status Rcvd 0 Num Status Timeouts 0 

Step 10 Check routing protocol 

a. Use the show ip route command to verify that the PVCs are up and active: 

Amsterdam#show ip route 

b. Is the routing protocol working? Yes 

c. If not, troubleshoot the routers configurations. 

List the IGRP routes 

I 192.168.6.0/24 [100/10476] via 192.168.4.2, 00:01:06, Serial0.102 

[100/10476] via 192.168.5.2, 00:01:20, Serial0.103 

I 192.168.2.0/24 [100/8486] via 192.168.4.2, 00:01:06, Serial0.102 

I 192.168.3.0/24 [100/8486] via 192.168.5.2, 00:01:20, Serial0.103 


Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B – 

BGP 

D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area 

N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2 

E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP 

i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS 

inter area 

* - candidate default, U - per-user static route, o - ODR 

P - periodic downloaded static route 

Gateway of last resort is not set 

C 

C 

I 

C 

I 

I 

192.168.4.0/24 is directly connected, Serial0.102 


192.168.6.0/24 [100/10476] via 192.168.4.2, 00:01:06, Serial0.102 

[100/10476] via 192.168.5.2, 00:01:20, Serial0.103 

192.168.1.0/24 is directly connected, FastEthernet0 

192.168.2.0/24 [100/8486] via 192.168.4.2, 00:01:06, Serial0.102 

192.168.3.0/24 [100/8486] via 192.168.5.2, 00:01:20, Serial0.103 

Step 11 Verify connectivity 

a. Ping the fastethernet interfaces. 

b. Were the pings successful? Yes 

c. If the pings were not successful, troubleshoot the router configurations and repeat this step. 

Amsterdam#ping 192.168.1.1 

Type escape sequence to abort. 

Sending 5, 100-byte ICMP Echos to 192.168.1.1, timeout is 2 seconds: 

!!!!! 

Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/4 ms 





!!!!! 





!!!!! 


Upon completion of the previous steps, finish the lab by doing the following: 

• Logoff by typing exit 

• Turn the router off 

• Remove and store the cables and adapter 


Amsterdam 

Router#configure terminal 

Router(config)#hostname Amsterdam 

Amsterdam(config)#enable password cisco 

Amsterdam(config)#enable secret class 

Amsterdam(config)#line con 0 

Amsterdam(config-line)#password cisco 

Amsterdam(config-line)#login 

Amsterdam(config-line)#line vty 0 4 



Amsterdam(config-line)#interface fastethernet 0 



Amsterdam(config-if)#exit 

Amsterdam(config)#exit 

Amsterdam#copy running-config startup-config 

Amsterdam Frame Relay and IGRP Configuration 








Amsterdam(config-subif)#description PVC to Paris, DLCI 102, contact Rick 


Amsterdam(config-subif)#ip address 192.168.4.1 255.255.255.0 

Amsterdam(config-subif)#frame-relay interface-dlci 102 

Amsterdam(config-fr-dlci)#interface serial 0.103 point-to-point 

Amsterdam(config-subif)#description PVC to Berlin, DLCI 103, Contact P 

Wills (+49- 61 03 / 7 65 72 00) Circuit #DTK465866 



Amsterdam(config-fr-dlci)#router igrp 100 




Amsterdam(config-router)#exit 



Paris 


Router(config)#hostname Paris 

Paris(config)#enable password cisco 

Paris(config)#enable secret class 

Paris(config)#line con 0 

Paris(config-line)#password cisco 

Paris(config-line)#login 

Paris(config-line)#line vty 0 4 



Paris(config-line)#interface fastethernet 0 



Paris(config-if)#exit 


Paris(config)#exit 

Paris#copy running-config startup-config 

Paris Frame Relay and IGRP Configuration 

Paris#configure terminal 







Paris(config-subif)#description PVC to Amsterdam, DLCI 201, Contact Peter 


Paris(config-subif)#ip address 192.168.4.2 255.255.255.0 

Paris(config-subif)#frame-relay interface-dlci 201 

Paris(config-fr-dlci)#interface Serial 0.203 point-to-point 

Paris(config-subif)#description PVC to Berlin, DLCI 203, Contact Peter 




Paris(config-fr-dlci)#router igrp 100 




Paris(config-router)#exit 



Berlin 


Router(config)#hostname Berlin 

Berlin(config)#enable password cisco 

Berlin(config)#enable secret class 

Berlin(config)#line con 0 

Berlin(config-line)#password cisco 

Berlin(config-line)#login 

Berlin(config-line)#line vty 0 4 



Berlin(config-line)#interface fastethernet 0 



Berlin(config-if)#exit 

Berlin(config)#exit 

Berlin#copy running-config startup-config 

Berlin Frame Relay and IGRP Configuration 

Berlin#configure terminal 

Enter configuration commands, one per line. End with CNTL/Z. 








Berlin(config-subif)#description PVC to Amsterdam, DLCI 301, Contact Peter 


Berlin(config-subif)#ip address 192.168.5.2 255.255.255.0 

Berlin(config-subif)#frame-relay interface-dlci 301 

Berlin(config-fr-dlci)#interface Serial 0.302 point-to-point 

Berlin(config-subif)#$ description PVC to Paris, DLCI 302, Contact Rick 




Berlin(config-subif)#exit 


Berlin(config)#router igrp 100 




Berlin(config-router)#exit 




Erasing and reloading the router 

Enter into the privileged EXEC mode by typing enable. 

If prompted for a password, enter class (if that does not work, ask the instructor). 

Router>enable 

At the privileged EXEC mode, enter the command erase startup-config. 

Router#erase startup-config 

The responding line prompt will be: 

Erasing the nvram filesystem will remove all files! Continue? [confirm] 

Press Enter to confirm. 

The response should be: 

Erase of nvram: complete 

Now at the privileged EXEC mode, enter the command reload. 

Router(config)#reload 


System configuration has been modified. Save? [yes/no]: 

Type n and then press Enter. 


Proceed with reload? [confirm] 


In the first line of the response will be: 

Reload requested by console. 

After the router has reloaded the line prompt will be: 

Would you like to enter the initial configuration dialog? [yes/no]: 



Press RETURN to get started! 

Press Enter. 

Now the router is ready for the assigned lab to be performed. 


Router Interface Summary 

Router 

Model 

Ethernet 

Interface #1 

Ethernet 

Interface #2 

Serial 

Interface #1 

Serial 

Interface #2 

800 (806) Ethernet 0 (E0) Ethernet 1 (E1) 

1600 Ethernet 0 (E0) Ethernet 1 (E1) Serial 0 (S0) Serial 1 (S1) 

1700 FastEthernet 0 (FA0) FastEthernet 1 (FA1) Serial 0 (S0) Serial 1 (S1) 


2600 FastEthernet 0/0 (FA0/0) FastEthernet 0/1 (FA0/1) Serial 0/0 (S0/0) Serial 0/1 (S0/1) 

In order to find out exactly how the router is configured, look at the interfaces. This will identify what type and how 

many interfaces the router has. There is no way to effectively list all of the combinations of configurations for each 

router class. What is provided are the identifiers for the possible combinations of interfaces in the device. This 

interface chart 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 an IOS command to represent the interface. 


Lab 5.2.5 Configuring Frame Relay Subinterfaces – Instructor Version 2500 

Objective 














































































































c. What is the interface value? Serial0.102, Serial0.103 









PVC Statistics for interface Serial0 (Frame Relay DTE) 


Local 2 1 0 0 




Serial0.102 










Serial0.103 






















command: 





LMI Statistics for interface Serial0 (Frame Relay DTE) LMI TYPE = ANSI 












. Is the routing protocol working? Yes 


d. List the IGRP routes 

I 192.168.6.0/24 [100/10476] via 192.168.4.2, 00:01:06, Serial0.102 

[100/10476] via 192.168.5.2, 00:01:20, Serial0.103 

I 192.168.2.0/24 [100/8486] via 192.168.4.2, 00:01:06, Serial0.102 

I 192.168.3.0/24 [100/8486] via 192.168.5.2, 00:01:20, Serial0.103 



BGP 





inter area 




C 

C 

I 

C 

I 

I 



192.168.6.0/24 [100/10476] via 192.168.4.2, 00:01:06, Serial0.102 

[100/10476] via 192.168.5.2, 00:01:20, Serial0.103 

192.168.1.0/24 is directly connected, Ethernet0 

192.168.2.0/24 [100/8486] via 192.168.4.2, 00:01:06, Serial0.102 

192.168.3.0/24 [100/8486] via 192.168.5.2, 00:01:20, Serial0.103 








!!!!! 





!!!!! 





!!!!! 








Amsterdam 





Amsterdam(config)#line console 0 



Amsterdam(config-line)#line vty 0 4 



Amsterdam(config-line)#exit 

Amsterdam(config-line)#interface ethernet 0 


















Amsterdam(config-fr-dlci)#interface serial 0.103 point-to-point 





Amsterdam(config-fr-dlci)#router igrp 100 







Paris 





Paris(config)#line console 0 



Paris(config-line)#exit 

Paris(config)#line vty 0 4 




Paris(config)#interface ethernet 0 















Paris(config)#interface Serial 0.201 point-to-point 





Paris(config-fr-dlci)#interface Serial 0.203 point-to-point 





Paris(config-subif)#exit 



Paris(config)#router igrp 100 







Berlin 





Berlin(config)#line console 0 



Berlin(config-line)#line vty 0 4 



Berlin(config-line)#exit 

Berlin(config-line)#interface ethernet 0 










Router>enable 























Press Enter. 




Router 

Model 

Ethernet 

Interface #1 

Ethernet 

Interface #2 

Serial 

Interface #1 

Serial 

Interface #2 













Lab 5.2.5 Configuring Frame Relay Subinterfaces – Instructor Version 2600 

Objective 














































































































c. What is the interface value? Serial0/0.102, Serial0/0.103 









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


Local 2 1 0 0 




Serial0/0.102 










Serial0/0.103 








DLCI = 104, DLCI USAGE = LOCAL, PVC STATUS = INACTIVE, INTERFACE = 

Serial0/0 
















Serial0/0.103 (up): point-to-point dlci, dlci 103(0x67,0x1870), 

broadcast 


Serial0/0.102 (up): point-to-point dlci, dlci 102(0x66,0x1860), 

broadcast 




command: 





LMI Statistics for interface Serial0/0 (Frame Relay DTE) LMI TYPE = 

ANSI 












b. Is the routing protocol working? Yes 


d. List the IGRP routes 

I 192.168.6.0/24 [100/10476] via 192.168.4.2, 00:01:06, 

Serial0/0.102 

[100/10476] via 192.168.5.2, 00:01:20, 

Serial0/0.103 

I 192.168.2.0/24 [100/8486] via 192.168.4.2, 00:01:06, Serial0/0.102 

I 192.168.3.0/24 [100/8486] via 192.168.5.2, 00:01:20, Serial0/0.103 



BGP 





inter area 




C 192.168.4.0/24 is directly connected, Serial0/0.102 

C 192.168.5.0/24 is directly connected, Serial0/0.103 

I 192.168.6.0/24 [100/10476] via 192.168.4.2, 00:01:06, 

Serial0/0.102 

[100/10476] via 192.168.5.2, 00:01:20, 

Serial0/0.103 

C 192.168.1.0/24 is directly connected, FastEthernet0/0 

I 192.168.2.0/24 [100/8486] via 192.168.4.2, 00:01:06, Serial0/0.102 

I 192.168.3.0/24 [100/8486] via 192.168.5.2, 00:01:20, Serial0/0.103 








!!!!! 






!!!!! 





!!!!! 







Amsterdam 





Amsterdam(config)#line console 0 




Amsterdam(config)#line vty 0 4 




Amsterdam(config)#interface fastethernet 0/0 








Amsterdam(config)#interface serial 0/0 






Amsterdam(config-if)#interface serial 0/0.102 point-to-point 





Amsterdam(config-fr-dlci)#interface serial 0/0.103 point-to-point 





Amsterdam(config-subif)#exit 


Amsterdam(config)#router igrp 100 







Paris 





Paris(config)#line console 0 



Paris(config-line)#line vty 0 4 





Paris(config-line)#interface fastethernet 0/0 








Paris(config)#interface serial 0/0 






Paris(config)#interface Serial 0/0.201 point-to-point 





Paris(config-fr-dlci)#interface Serial 0/0.203 point-to-point 





Paris(config-subif)#exit 


Paris(config)#router igrp 100 







Berlin 





Berlin(config)#line console 0 




Berlin(config)#line vty 0 4 




Berlin(config)#interface fastethernet 0/0 






Berlin Frame Relay and IGRP Configuration 

Berlin#configure terminal 

Berlin(config)#interface serial 0/0 






Berlin(config)#interface Serial 0/0.301 point-to-point 

Berlin(config-subif)#description PVC to Amsterdam, DLCI 301, Contact Peter 




Berlin(config-fr-dlci)#interface Serial 0/0.302 point-to-point 

Berlin(config-subif)#$ description PVC to Paris, DLCI 302, Contact Rick 




Berlin(config-subif)#exit 


Berlin(config)#router igrp 100 




Berlin(config-router)#exit 







Router>enable 























Press Enter. 




Router 

Model 

Ethernet 

Interface #1 

Ethernet 

Interface #2 

Serial 

Interface #1 

Serial 

Interface #2

Lab 5.2.5 Configuring Frame Relay Subinterfaces – Instructor Version 1700

Create successful ePaper yourself

Delete template?

Save as template?