IGRP SCENARIO
for BTEGITIM REMOTE LAB v1.0
1. SCENARIO: ACME COMPANY – ISTANBUL HEADQUARTERS
Purpose: This lab is designed to improve your practical skills on the following
Cisco Networking Academy Program topics:
- Basic Router Configuration Tasks
- IGRP
Description: Acme Inc.
is a multinational company, whose headquarters are located in MANAGEMENT. The Istanbul
office is subdivided into three departments:
- Management Department
- Sales Department
- Engineering Department
It is your
duty to provide end-to-end connectivity through the intranet. As an executive
decision, IGRP is chosen as Routing Protocol.
Objective: Fulfill
the basic configuration tasks on MANAGEMENT, ENGINEERING and SALES Routers.
Provide end-to-end connectivity inside the company’s network using IGRP.
Tasks:
1. Erase initial router configurations
2. Configure Hostname; enable, vty and console
passwords.
3. a. Configure interfaces by assigning them
the appropriate IP Addresses given in the topology
b. Check whether the serial interfaces are DCE or DTE. Set clock rate if
required.
4. (Optional) Use the ping
command to check the connectivity with neighboring router’s serial interface.
5. a. Configure IGRP to
provide end-to-end connectivity, use AS Number 100
b. Check end-to-end connectivity
6. Observe debug command
outputs
7. Save your configurations
into router’s NVRAM
2.
TOPOLOGY
3. CONFIGURATION
Note: Before you
start the lab, make sure that you are familiar with the commands listed below.
|
Basic
Commands |
Line
Commands |
Interface
Commands |
Routing
protocol configuration commands |
Show
Commands |
Debug
Commands |
|
erase
start |
line vty |
interface |
router igrp |
show
controllers |
Debug ip igrp
events |
|
copy run
start |
line
console |
ip
address |
network |
show ip
route |
Debug ip igrp transactionns |
|
reload |
login |
shutdown |
|
|
|
|
enable |
password |
clock
rate |
|
|
|
|
conf t |
|
|
|
|
|
|
hostname |
|
|
|
|
|
|
end |
|
|
|
|
|
|
ping |
|
|
|
|
|
|
telnet |
|
|
|
|
|
Task: Erase
initial router configurations.
Task: Configure
Hostname; enable, vty and console passwords. All passwords will be set to
‘btegitim’
Task a: Configure
interfaces by assigning them the appropriate IP Addresses given in the
topology. In order to save time you can use the table below as a shortcut:
|
ENGINEERING |
|
|
MANAGEMENT |
|
|
SALES |
|
|
Serial 0 |
192.168.1.2/24 |
|
Serial
0/0 |
192.168.1.1/24 |
|
Serial 0 |
192.168.2.1/24 |
|
Ehernet 0 |
192.168.11.1/24 |
|
Serial
0/1 |
192.168.2.1/24 |
|
Ehernet 0 |
192.168.13.1/24 |
|
|
|
|
Ethernet
0/0 |
192.168.12.1/24 |
|
|
|
Task b: Check whether the serial interfaces are DCE or DTE. It is required to
set the clock rate on DCE interfaces.
Note: Before making any further
configurations, it’s a good idea to check connectivity between routers by
sending icmp echo request (ping) packets to serial interfaces. However, before
any tests can be made you should configure the first three steps on MANAGEMENT
and SALES. You may wish to skip this step and configure each router
individually.
Task: Use the ping command to check the
connectivity with neighboring router’s serial interface.
Task
a: Configure IGRP
to provide end-to-end connectivity
Task
b: Check
end-to-end connectivity. At ENGINEERING, display the routing table using the
appropriate command. Then ping to SALES’s
ethernet 0 interface (192.168.13.1).
Task: Observe the outputs of debug ip igrp transactions and debug ip igrp events commands.
Task: Save your configurations into
router’s NVRAM (Repeat this step on each Router)
4. SOLUTIONS
Router#
Router#erase start
Erasing the nvram filesystem will remove all files!
Continue? [confirm]
[OK]
Erase of nvram: complete
Router#reload
System configuration has been modified. Save?
[yes/no]: n
Proceed with reload? [confirm]
System Bootstrap, Version 5.2(8a), RELEASE SOFTWARE
Copyright (c) 1986-1995 by cisco Systems
Router>enable
Router#conf t
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)#hostname ENGINEERING
ENGINEERING(config)#enable
secret btegitim
ENGINEERING(config)#line vty 0
4
ENGINEERING(config-line)#password
btegitim
ENGINEERING(config-line)#line
console 0
ENGINEERING(config-line)#login
ENGINEERING(config-line)#password
btegitim
ENGINEERING(config-line)#end
ENGINEERING(config)#int serial
0
ENGINEERING(config-if)#ip
address 192.168.1.2 255.255.255.0
ENGINEERING(config-if)#no shut
ENGINEERING(config-if)#int
ethernet 0
ENGINEERING(config-if)#ip
address 201.1.1.1 255.255.255.0
ENGINEERING(config-if)#no shut
ENGINEERING#sh controllers serial 0
HD unit 0, idb = 0x9F514, driver structure
at 0xA31C0
buffer size 1524 HD unit 0, V.35 DCE cable
cpb = 0x21, eda = 0x4940, cda = 0x4800
RX ring with 16 entries at 0x214800
00 bd_ptr=0x4800 pak=0x106648 ds=0x21EC68
status=80 pak_size=0
!Output Omitted for simplicity
ENGINEERING#conf t
Enter configuration
commands, one per line. End with CNTL/Z.
ENGINEERING(config)#int serial 0
ENGINEERING(config-if)#clock rate 64000
ENGINEERING(config-if)#end
%SYS-5-CONFIG_I:
Configured from console by console
ENGINEERING#sh controllers s 0
HD unit 0, idb =
0x9F514, driver structure at 0xA31C0
buffer size 1524 HD unit 0, V.35 DCE cable, clockrate 64000
cpb = 0x21, eda =
0x4940, cda = 0x4800
RX ring with 16
entries at 0x214800
00 bd_ptr=0x4800
pak=0x106648 ds=0x21EC68 status=80 pak_size=0
!Output Omitted for simplicity
Note: Do not set
clock rate on DTE interdfaces.
On ENGINEERING:
ENGINEERING#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 = 28/30/32 ms
On MANAGEMENT
MANAGEMENT#ping 192.168.1.2
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.1.2, timeout
is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip
min/avg/max = 28/29/32 ms
MANAGEMENT#ping 172.16.1.2
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 172.16.1.2, timeout
is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip
min/avg/max = 28/29/32 ms
On SALES
SALES#ping 172.16.1.1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 172.16.1.1, timeout
is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip
min/avg/max = 28/29/32 ms
Note: Considering our lab environment,
failure of a ping request indicates most probably a faulty cable or an unset
clock rate value. In real production networks however, there may be other
reasons which influence connectivity like misconfigured access-lists, etc.
On ENGINEERING:
ENGINEERING(config)#router igrp
100
ENGINEERING(config-router)#network
192.168.1.0
ENGINEERING(config-router)#network
201.1.1.0
On
Router 2:
MANAGEMENT(config)#router igrp
100
MANAGEMENT(config-router)#network
192.168.1.0
MANAGEMENT(config-router)#network
202.1.1.0
MANAGEMENT(config-router)#network
172.16.0.0 !See the note below
On
Router 3:
SALES(config)#router igrp 100
SALES(config-router)#network
172.16.0.0 !See the note below
SALES(config-router)#network
203.1.1.0
ENGINEERING#sh ip route
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, * - candidate default
U -
per-user static route, o - ODR
Gateway of last resort is not set
I
192.168.12.0/24 [100/8576] via 192.168.1.1, 00:00:04, Serial0
I
192.168.13.0/24 [100/10576] via 192.168.1.1, 00:00:05, Serial0
C
192.168.11.0/24 is directly connected, Ethernet0
C
192.168.1.0/24 is directly connected, Serial0
I
192.168.2.0/24 [100/10476] via 192.168.1.1, 00:00:05, Serial0
ENGINEERING#ping 192.168.11.1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.11.1,
timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip
min/avg/max = 56/57/60 ms
!!! Important Note: It’s a common mistake to write this command as:
MANAGEMENT(config-router)#network
172.16.1.0
Your router will accept this command and indicate no error message.
Furthermore, you won’t encounter any problems in connectivity. However look at
the output of show run:
!
router igrp
network 172.16.0.0
network
192.168.1.0
network
202.1.1.0
!
172.16 is a B class IP address and the network command is classless, so
the last two octets of the IP address 172.16 will be neglected.
Solution for Step 6
ENGINEERING#copy
running-config startup-config
Destination filename [startup-config]?
Building configuration...
[OK]
MANAGEMENT#debug ip igrp ?
events IGRP protocol events
transactions IGRP protocol
transactions
MANAGEMENT#debug ip igrp transactions
IGRP protocol debugging is on
MANAGEMENT#
00:15:52: IGRP: sending update to 255.255.255.255 via
Ethernet0 (192.168.12.1)
00:15:52:
network 192.168.13.0, metric=8576
00:15:52:
network 192.168.11.0, metric=8576
00:15:52:
network 192.168.1.0, metric=8476
00:15:52:
network 192.168.2.0, metric=8476
00:15:52: IGRP: sending update to 255.255.255.255 via
Serial0 (192.168.1.1)
00:15:52:
network 192.168.12.0, metric=1100
00:15:52:
network 192.168.13.0, metric=8576
00:15:52:
network 192.168.2.0, metric=8476
00:15:53: IGRP: sending update to 255.255.255.255 via
Serial1 (192.168.2.1)
00:15:53:
network 192.168.12.0, metric=1100
00:15:53: network 192.168.11.0, metric=8576
00:15:53:
network 192.168.1.0, metric=8476
00:16:21: IGRP: received update from 192.168.2.2 on
Serial1
00:16:21:
network 192.168.13.0, metric 8576 (neighbor 1100)
MANAGEMENT#no debug all
All possible debugging has been turned off
The line 00:15:52:
IGRP: sending update to 255.255.255.255 via Ethernet0 (192.168.12.1) states that IGRP broadcasts routing
updates from Management Router’s Ethernet0 interface. Following lines are the
contents of the updates: Network addresses and their metrics.
MANAGEMENT#debug ip igrp events
IGRP event debugging is on
MANAGEMENT#
00:17:06: IGRP: sending update to 255.255.255.255 via
Ethernet0 (192.168.12.1)
00:17:06: IGRP: Update contains 0 interior, 4 system,
and 0 exterior routes.
00:17:06: IGRP: Total routes in update: 4
00:17:06: IGRP: sending update to 255.255.255.255 via
Serial0 (192.168.1.1)
00:17:06: IGRP: Update contains 0 interior, 3 system,
and 0 exterior routes.
00:17:06: IGRP: Total routes in update: 3
00:17:06: IGRP: sending update to 255.255.255.255 via
Serial1 (192.168.2.1)
00:17:06: IGRP: Update contains 0 interior, 3 system,
and 0 exterior routes.
00:17:06: IGRP: Total routes in update: 3
MANAGEMENT#
The debug ip igrp events command provides a less detailed information.
The first line resembles the output from the debug ip igrp transactions command and states that IGRP process is
broadcasting updates from Interface Ethernet0. Following that line, the number
of interior, system and exterior routes are indicated. The third line states
that there are 4 routes in the update. In fact, the output the debug ip igrp transactions command for
Ethernet0 interface shows 4 routes.
5. COMPLETE CONFIGURATIONS
Note: If you can’t fulfill the required
tasks by following the step-by-step instructions, you can upload the
configurations listed below to the appropriate routers and provide
connectivity. To do this:
1.
Copy the configurations
to the clipboard.
2.
Paste the configuration
while the Router is in global config mode.
ENGINEERING(2501)
!
version 12.0
service timestamps debug uptime
service timestamps log uptime
no service password-encryption
!
hostname ENGINEERING
!
enable secret 5 $1$56AM$rhB5dH1DVpK7/UnDPiyTj1
!
ip subnet-zero
!
!
!
interface Ethernet0
ip address 192.168.11.1
255.255.255.0
no ip
directed-broadcast
no shutdown
!
interface Serial0
ip address
192.168.1.2 255.255.255.0