IERG3821 Lab3b

IEG3821 (2007-08)
Information Engineering Laboratory
Manual
Networking Technologies
Experiment N3:
Dynamic Routing Protocol
Department of Information Engineering

The Chinese University of Hong Kong
January 2008
IEG3821:Experiment N3, Dynamic Routing Protocol P.1
Introduction:
There are over 20K routes in the Internet. It is impossible to use static route because they cannot be
maintained manually. Dynamic routing protocol is used such that any route changes can be updated
dynamically. There are 3 types of routing protocol, namely, distance vector, link state and path vector. RIP,
OSPF and BGP is an example of distance vector, link state and path vector routing protocol respectively.
EIGRP has the property of both distance vector and link state routing protocol.
Interior Gateway Protocol (IGP) is used for exchanging routing information within an autonomous network.
RIP, OSPF and EIGRP are examples of IGP. They are suitable to maintain small amount of routes like LAN.
Border Gateway Protocol (BGP) is used for exchanging routing information in a network of autonomous
system like the Internet. It is suitable for handling large amount of routes.
Laboratory Equipment:
This laboratory can be done on PCs at IE Computing Laboratory or your PC at home having similar
hardware configurations. The Cisco router emulator called Dynamips have been installed in PCs at EBII
Rm1109. Dynagen, the front-end of Dynamips, uses INI-like configuration file to provision Dynamips
emulator networks, are also installed. You can download both freeware at: http://www.dynagen.org/. You
have to install Winpcap 4.0 before the installation of Dynamips package.
A network file will be provided. It describes the network infrastructure as shown in the Network Diagram.
You are permitted to modify any parameters that are not related to the connection between routers such as
the “Working Directory”, “IOS Image path” or “idlepc” value. Any changes to the virtual connections
between virtual routers so as to achieve the goal will be scored ZERO mark in this laboratory.
The Dynamips process is started by the script “0DynamipsServer0.cmd”. As before, if you are using Core2
CPU, you should lock the process into a particular CPU by setting the “affinity” in the task manager.
The console port of the virtual routers can be accessed by reverse telnet. You can read the provided network
file for the assignment of TCP port for each virtual router. Here is the summary:
NSP
Router Port
S1_PE 2001
S2_PE 2002
S3_PE 2003
S1_CE 2004
S2_CE 2005
S3_CE 2006
S1_R 2007
S2_R 2008
S3_R 2009
Pre-Laboratory studies:
- Tutorial section of Dynagen: http://dynagen.org/tutorial.htm
IEG3821 Information Engineering Laboratory (2007-2008)

- Visit Cisco Documentation Website: http://www.cisco.com/univercd/ related to RIPv2, EIGRP, OSPF

and BGP:
Cisco IOS Release 12.4
Î Cisco IOS Release 12.4 Configuration Guides
Î Cisco IOS IP Routing Protocols Configuration Guide, Release 12.4
Î RIP, EIGRP, OSPF, BGP
-
Instructions:
1. “MyDir.zip” will be provided. Unzip it and put it into your USB drive. It consists of the sample
Dynagen network file and pre-lab setup _nvram files.
2. The number N is the last 3rd and 2nd digits of your Student ID. For example, if your student ID is
87654321, then N will be 32. In case N=00, N=1.
3. The number N’ = N + 1. If N = 99, N’= 1
4. Please ask questions using the course newsgroup: news://news.erg.cuhk.edu.hk/cuhk.ie.3821 . The
newsgroup can also be accessed via IE Webmail system. To identify different lab, the subject of your
post should be prefixed by [LabX] where X is the labsheet number.
5. Each task requires you to configure routers. On your answer book, you should only record what you
have configured on each router in each task. Marks will be deducted for any irrelevant or default
command.
6. You can save your configurations on the emulator at any time by the command “copy running-
config startup-config”.
7. All captured text must be shown using “Courier New” fonts with text size of “10”.
8. After you finish your work, you should save your final configuration to the emulator. You need to
zip and submit the report, as well as “c3600_R?_nvram” files. Tutors will check your configuration
by recovering your work using these files.
Network Diagram:
Enlarged version can be found in Appendix 1.

Configuration Tasks:
Task 0: Construct the Dynagen Network File and Basic router configuration
a) Construct the Dynagen Network File
- Visit the Tutorial section of Dynagen website: http://dynagen.org/tutorial.htm
- The sample Network File (Sample.net) is provided in the MyDir.zip as shown in Appendix 2. Copy it
into Lab3.net and fill in the XXXXXX according to the network diagram.
- Procedures:
- Start up the Dynamips process
- Run the modified network file using Dynagen
- Tune the parameter of “idlepc” as described by the tutorial section of Dynagen website.
- Start each router instances using the “start” command one by one in the “Dynagen management
console for Dynamips”. Do NOT use “start /all” as it may hang the emulator.
- “telnet R?” to each router. The port number can be found from the network file. (console = 200?)
- The pre-lab setup of each router has been configured in the c3600_*_nvram file. The content is
shown in Appendix 3.
b) Basic Router Configurations:
Start all routers one by one at the Dynagen management console
Configure the hostname to each router which the corresponding name found in the Dynagen network file.
Some IP addresses are missing from the pre-lab setup configurations. Configure the IP addresses of the
FastEthernet interface in S1_PE, S2_PE, S3_PE, S1_CE, S2_CE and S3_CE according to the network
diagram. After configuration, you will be able to PING to its neighbors.
Task 1: Core IGP in NSP network

On the NSP network (the network among routers S1_PE, S2_PE and S3_PE), configure OSPF Area 0 on the
interfaces between them such that their loopback 0 interface can be accessed by each other. Use the address
of loopback 0 interface as the OSPF Router ID. Note: You are NOT allowed to enable OSPF on interfaces
connecting to other AS through OSPF.
To ensure that the loopback 0 interface of routers can be accessed among each other, use PING test to the
loopback 0 interface of other routers by using its local loopback 0 interface as the source address.
e.g. ping X.X.X.X source lo 0
Task 2: Configuration of IGP on networks in each site

a) Configure RIP on networks in Site 1

Enable RIP on networks configured in interface S1_CE:F1/0, S1_R:F0/0 and S1_R:lo0.
Configure S1_CE such that S1_R will receive a default route via RIP. Verify your result by showing
their route tables.
b) Configure EIGRP on networks in Site 2
Enable EIGRP on networks configured in interface S2_CE:F1/0, S2_R:F0/0 and S2_R:lo0. Use the same
ASN as BGP.
Configure S2_CE such that S2_R will receive a default route via EIGRP type external. You are allowed
to create a default route at S2_CE but it cannot be pointed to its PE router. Verify your result by showing
their route tables.
c) Configure OSPF on networks in Site 3
Enable OSPF on networks configured in interface S3_CE:F1/0, S3_R:F0/0 and S3_R:lo0.
Configure S3_CE such that S3_R will receive a default route via OSPF external type 2. You are allowed
to create a default route at S3_CE but it cannot be pointed to its PE router. Verify your result by showing
their route tables.
Task 3: Core BGP in each NSP network

On the NSP network, configure BGP between PEs using loopback 0 interface as BGP peering address. The
AS number of NSP is shown in the Network Diagram. Use the address of loopback 0 interface as the BGP
Router ID. Note: You are NOT allowed to advertise any network originated from NSP routers.
Show the BGP neighborhood information on each router by “show ip bgp summary”.
Task 4: Configuration of eBGP between PE and CE of each Site

The NSP has three sites. Each site has a CE router.
Configure eBGP between PE and CE. At CE, use the IP address of F0/0 as the router ID and advertise all
networks received from IGP to BGP. Other networks are not allowed to be advertised to BGP.
After configuration, CE should receive networks advertised from CE of other sites in the NSP. This can be
verified by the command “show ip bgp” in the CE router.
Perform PING tests at S1_R to make sure that networks in its loopback 0 interface can access networks at
loopback 0 of R in the other sites.
E.g. At S1_R:
ping 200.12.1.254 source lo 0
ping 200.13.1.254 source lo 0

Task 5: Implementation of RFC 1918 in PE Router

In PE routers, it is found that private network addresses from CEs are advertised into BGP. Private network
addresses should not be allowed to advertise into an AS. Configure in PE routers so that these private
network addresses are not accepted and advertised to other AS by BGP. Use minimum amount of commands
to achieve this task.
--- END ---

Please zip all “c3600_R?_nvram” files and “Lab3.net”
in the working directory, as well as your report,
and submit to course tutors

Appendix 1: Network Diagram

Appendix 2: Network File (Sample.net)

# IEG3821 – Lab3
autostart = false
ghostios = true
ghostsize = 64
mmap = true
sparsemem = true
[127.0.0.1]
# “workingdir” stores all files needed by Dynamips
# This Network File is stored in the “workingdir”
# “workingdir” can be pointed to a USB flash disk but not a Samba drive
# e.g. workingdir = F:\MyDir\IEG3821\Lab3\
workingdir = XXXXXX:\MyDir\IEG3821\Lab3\
[[ETHSW SW]]
# SW is the switch connecting Ethernet interface of S1_PE,
# S2_PE and S3_PE
#
# Connection:
#
# Port 1 dot1q [VLAN 12 + VLAN 13] => S1_PE:F0/0
#
# Example:
# Port 88 is connected to [VLAN 98 + VLAN 99]
# Configuration:
# 88 = dot1q
#
# READ_THE_NETWORK_DIAGRAM_AND
# FILL_IN_THE_CONFIGURATION_OF_SW_BELOW
1 = XXXXXX
2 = XXXXXX
3 = XXXXXX
[[3640]]
# idlepc depends on machine.
# Read the tutorial website on how to evaluate a good value
# idlepc = 0x6103dca4
Idlepc = XXXXXX
# “F:\MyDir\IEG3821\images” is the path where the IOS image is put into
image = XXXXXX:\MyDir\IEG3821\images\c3640-telco-mz.124-13.image
ram = 64
#### S1_PE ####

[[ROUTER S1_PE]]
console = 2001
model = 3640
F0/0 = XXXXXX

#### S2_PE ####

[[ROUTER S2_PE]]
console = 2002
model = 3640
F0/0 = XXXXXX
#### S3_PE ####

[[ROUTER S3_PE]]
console = 2003
model = 3640
F0/0 = XXXXXX
#### S1_CE ####

[[ROUTER S1_CE]]
console = 2004
model = 3640
F0/0 = XXXXXX
#### S2_PE ####

[[ROUTER S2_CE]]
console = 2005
model = 3640
F0/0 = XXXXXX
#### S3_PE ####

[[ROUTER S3_CE]]
console = 2006
model = 3640
F0/0 = XXXXXX
#### S1_R ####

[[ROUTER S1_R]]
console = 2007
model = 3640
F0/0 = XXXXXX
#### S2_R ####

[[ROUTER S2_R]]
console = 2008
model = 3640
F0/0 = XXXXXX
#### S3_R ####

[[ROUTER S3_R]]
console = 2009
model = 3640
F0/0 = XXXXXX

Appendix 3: Pre-lab setup (pre-configured in c3600_R?_nvram file)

S1_PE:
no ip domain lookup
interface Loopback0
ip address 10.1.1.1 255.255.255.255
line con 0
exec-timeout 0 0
logging synchronous
exit
S2_PE:
no ip domain lookup
interface Loopback0
ip address 10.1.1.2 255.255.255.255
line con 0
exec-timeout 0 0
logging synchronous
exit
S3_PE:
no ip domain lookup
interface Loopback0
ip address 10.1.1.3 255.255.255.255
line con 0
exec-timeout 0 0
logging synchronous
exit
S1_CE:
no ip domain lookup
interface FastEthernet1/0
ip address 10.0.11.254 255.255.255.0
line con 0
exec-timeout 0 0
logging synchronous
exit
S2_CE:
no ip domain lookup
ip address 172.16.12.254 255.255.255.0
line con 0
exec-timeout 0 0
logging synchronous
exit
S3_CE:
no ip domain lookup
ip address 192.168.13.254 255.255.255.0
line con 0
exec-timeout 0 0
logging synchronous
exit
S1_R:
no ip domain lookup
interface Loopback0
ip address 200.11.1.254 255.255.255.0
ip address 200.11.2.254 255.255.255.0 secondary


ip address 10.0.11.1 255.255.255.0
line con 0
exec-timeout 0 0
logging synchronous
exit
S2_R:
no ip domain lookup
interface Loopback0
ip address 200.12.1.254 255.255.255.0
ip address 172.16.12.1 255.255.255.0
line con 0
exec-timeout 0 0
logging synchronous
exit
S3_R:
no ip domain lookup
interface Loopback0
ip address 200.13.1.254 255.255.255.0

ip address 192.168.13.1 255.255.255.0

line con 0
exec-timeout 0 0
logging synchronous
exit

IERG3821 Lab3b

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

IERG3821 Lab3b

Hochgeladen von

Copyright:

Verfügbare Formate

IEG3821 (2007-08)

Information Engineering Laboratory

Dynamic Routing Protocol

Department of Information Engineering

IEG3821 Information Engineering Laboratory (2007-2008)

- Visit Cisco Documentation Website: http://www.cisco.com/univercd/ related to RIPv2, EIGRP, OSPF

Enlarged version can be found in Appendix 1.

IEG3821 Information Engineering Laboratory (2007-2008)

- Visit the Tutorial section of Dynagen website: http://dynagen.org/tutorial.htm

b) Basic Router Configurations:

Start all routers one by one at the Dynagen management console

Task 1: Core IGP in NSP network

Task 2: Configuration of IGP on networks in each site

IEG3821 Information Engineering Laboratory (2007-2008)

Enable RIP on networks configured in interface S1_CE:F1/0, S1_R:F0/0 and S1_R:lo0.

b) Configure EIGRP on networks in Site 2

c) Configure OSPF on networks in Site 3

Enable OSPF on networks configured in interface S3_CE:F1/0, S3_R:F0/0 and S3_R:lo0.

Task 3: Core BGP in each NSP network

Task 4: Configuration of eBGP between PE and CE of each Site

IEG3821 Information Engineering Laboratory (2007-2008)

Task 5: Implementation of RFC 1918 in PE Router

--- END ---

IEG3821 Information Engineering Laboratory (2007-2008)

Appendix 1: Network Diagram

IEG3821 Information Engineering Laboratory (2007-2008)

Appendix 2: Network File (Sample.net)

#### S1_PE ####

IEG3821 Information Engineering Laboratory (2007-2008)

#### S2_PE ####

#### S3_PE ####

#### S1_CE ####

#### S2_PE ####

#### S3_PE ####

#### S1_R ####

#### S2_R ####

#### S3_R ####

IEG3821 Information Engineering Laboratory (2007-2008)

Appendix 3: Pre-lab setup (pre-configured in c3600_R?_nvram file)

IEG3821 Information Engineering Laboratory (2007-2008)

ip address 200.11.3.254 255.255.255.0 secondary

IEG3821 Information Engineering Laboratory (2007-2008)

ip address 192.168.13.1 255.255.255.0

IEG3821 Information Engineering Laboratory (2007-2008)

Das könnte Ihnen auch gefallen