CCNA2 Lab 3 2 7 en
CCNA2 Lab 3 2 7 en
Objective
• Create IP host tables that allow a router to use names to identify all of the attached interfaces on
that router. These names can be used in place of an IP addresses in commands that use IP
addresses to identify a location.
• Set up a network similar to the one in the above diagram.
Background/Preparation
IP host tables allow a router to use names to identify all of the attached interfaces on that router.
These names can be used in place of an IP address in commands that use IP addresses to identify a
location such as ping or Telnet.
Any router that meets the interface requirements may be used. Possible routers include 800, 1600,
1700, 2500, 2600 routers, or a combination. 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. The following steps are intended to be executed on each router unless
specifically instructed otherwise.
Start a HyperTerminal session as performed in the Establishing a HyperTerminal session lab.
Note: Go to the erase and reload instructions at the end of this lab. Perform those steps on all
routers in this lab assignment before continuing.
1-6 CCNA 2: Routers and Routing Basics v 3.1 - Lab 3.2.7 Copyright 2003, Cisco Systems, Inc.
Step 1 Configure the hostname and passwords on the GAD router
a. On the router, enter the global configuration mode. Configure the hostname as shown in the
chart. Then configure the console, virtual terminal and enable passwords. If there are any
difficulties, refer to the Configuring Router Passwords lab.
Step 2 Configure the interfaces and routing protocol on the GAD router
a. Go to the proper command mode and enter the following text:
GAD(config)#interface fastethernet 0
GAD(config-if)#ip address 172.16.0.1 255.255.0.0
GAD(config-if)#no shutdown
GAD(config-if)#exit
GAD(config)#interface serial 0
GAD(config-if)#ip address 172.17.0.1 255.255.0.0
GAD(config-if)#clock rate 56000
GAD(config-if)#no shutdown
GAD(config-if)#exit
GAD(config)#router rip
GAD(config-router)#network 172.16.0.0
GAD(config-router)#network 172.17.0.0
GAD(config-router)#exit
GAD(config)#exit
Step 5 Configure the interfaces and routing protocol on the BHM router
a. Go to the proper command mode and enter the following:
BHM(config)#interface fastethernet 0
BHM(config-if)#ip address 172.18.0.1 255.255.0.0
BHM(config-if)#no shutdown
BHM(config-if)#exit
BHM(config)#interface serial 0
BHM(config-if)#ip address 172.17.0.2 255.255.0.0
BHM(config-if)#no shutdown
BHM(config-if)#exit
BHM(config)#router rip
BHM(config-router)#network 172.17.0.0
BHM(config-router)#network 172.18.0.0
BHM(config-router)#exit
BHM(config)#exit
2-6 CCNA 2: Routers and Routing Basics v 3.1 - Lab 3.2.7 Copyright 2003, Cisco Systems, Inc.
Step 6 Save the BHM router configuration
b. From the global configuration mode, enter the command ip host followed by the name of each
router in the network, as well as all of the IP addresses of the interfaces on each of the routers.
For example to name the GAD router accessible from BHM by the name “G”, enter:
3-6 CCNA 2: Routers and Routing Basics v 3.1 - Lab 3.2.7 Copyright 2003, Cisco Systems, Inc.
e. Now ping the other router by host name. From the enable prompt type ping host. The “host” is
the ip host name that was configured in the previous steps. For example for a host name of “G”,
enter:
BHM#ping G
BHM#G
Upon completion of the previous steps, logoff by typing exit. Turn the router off.
4-6 CCNA 2: Routers and Routing Basics v 3.1 - Lab 3.2.7 Copyright 2003, Cisco Systems, Inc.
Erasing and reloading the router
Enter into the privileged EXEC mode by typing enable.
If prompted for a password, enter class. If “class” does not work, ask the instructor for assistance.
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#reload
The responding line prompt will be:
System configuration has been modified. Save? [yes/no]:
Type n and then press Enter.
The responding line prompt will be:
Proceed with reload? [confirm]
Press Enter to 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]:
Type n and then press Enter.
The responding line prompt will be:
Press RETURN to get started!
Press Enter.
The router is ready for the assigned lab to be performed.
5-6 CCNA 2: Routers and Routing Basics v 3.1 - Lab 3.2.7 Copyright 2003, Cisco Systems, Inc.
Router Interface Summary
Router Ethernet Ethernet Serial Serial Interface
Model Interface #1 Interface #2 Interface #1 Interface #2 #5
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)
2500 Ethernet 0 (E0) Ethernet 1 (E1) Serial 0 (S0) Serial 1 (S1)
2600 FastEthernet 0/0 FastEthernet 0/1 (FA0/1) Serial 0/0 (S0/0) Serial 0/1
(FA0/0) (S0/1)
In order to find out exactly how the router is configured, look at the interfaces. This will identify the type of router
as well as 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 IOS command to represent the interface.
6-6 CCNA 2: Routers and Routing Basics v 3.1 - Lab 3.2.7 Copyright 2003, Cisco Systems, Inc.