lab guide to networking fundamental

Netwoking FundamentalLab Guide

October 2011NetworkMatics

Table of ContentTable of Content........................................................................................................................................ 2

Lab 1 : Configure VLANs on Catalyst switch.............................................................................................. 3

Lab 2 : VLAN Trunking ............................................................................................................................. 10

Lab 3 : Configuring Static Routes ............................................................................................................ 16

Lab 4 : Configuring RIP ............................................................................................................................ 20

Lab 5 : Configuring EIGRP Routing .......................................................................................................... 23

Lab 6 : Configuring OSPF Routing............................................................................................................ 27

Lab 7 : Configuring PPP & PPP Authentication........................................................................................ 33

Lab 8 : Configuring Frame-Relay Sub-Interfaces ...................................................................................... 36

Lab 1 : Configure VLANs on Catalyst switch

Objective

• Create a basic switch configuration and verify it.• Create two VLANs.• Name the VLANs and assign multiple member ports to them.• Test functionality by moving a workstation from one VLAN to another.• Delete VLANs• Understand why it is not possible to delete VLAN 1.

Step 1 Configure the switch

Configure the hostname, access and command mode passwords, as well as themanagement LAN settings. These values are shown in the chart. If problems occurwhile performing this configuration, refer to the Basic Switch Configuration lab.

Step 2 Configure the hosts attached to the switch

Configure the host to use the same subnet for the address, mask, and default gatewayas on the switch.

Step 3 Verify connectivity

a. To verify that the host and switch are correctly configured, ping the switch from thehost.

b. Was the ping successful?

c. If the answer is no, troubleshoot the host and switch configurations.

Step 4 Display the VLAN interface information

a. On Switch_A, type the command show vlan at the privileged EXEC prompt asfollows:

Switch_A#show vlan

b. Which ports belong to the default VLAN?

Step 5 Create and name two VLANs

Enter the following commands to create and name two VLANs:

Switch_A(config)#vlan 2Switch_A(config-vlan)# exitSwitch_A(config)# vlan 3Switch_A(config-vlan)#exitSwitch_A(config)#

Step 6 Assign ports to VLAN 2

Assigning ports to VLANs must be done from the interface mode. Enter the followingcommands to add ports 4,5 and 6 to VLAN 2.

Switch_A#configure terminalSwitch_A(config)#interface fastethernet 0/4Switch_A(config-if)#switchport mode accessSwitch_A(config-if)#switchport access vlan 2Switch_A(config-if)#interface fastethernet 0/5Switch_A(config-if)#switchport mode accessSwitch_A(config-if)#switchport access vlan 2Switch_A(config-if)#interface fastethernet 0/6Switch_A(config-if)#switchport mode accessSwitch_A(config-if)#switchport access vlan 2Switch_A(config-if)#end

Step7 Display the VLAN interface information


Switch_A#show vlan

b. Are ports 4 through 6 assigned to VLAN 2?

Step 8 Assign ports 7, 8, and 9 to VLAN 3

Enter the following commands to add prot 3 to VLAN 3:




Switch_A#show vlan

b. Are ports 7 through 9 assigned to VLAN 3?

Step 10 Test the VLANs

Ping from the host in port 0/4 to the host in port 0/1.

a. Was the ping successful?

b. Why?


c. Was the ping successful?

d. Why?

Ping from the host in port 0/4 to the switch IP 192.168.1.2.

e. Was the ping successful?

f. Why?


g. Was the ping successful?

h. Why?

Step 11 Move a host

Move the host in port 0/4 to port 0/3. Wait until the port LED goes green and then go tothe next step.




b. Why?




d. Was the ping successful?

Step 13 Move hosts

Move the hosts in port 0/3 to port 0/4 and the host in port 0/1 to port 0/5. Wait until theport LED goes green and then go to the next step.




b. Why?







f. Why?

Step 15 Move hosts

Move the hosts in port 0/4 to port 0/8. Wait until the port LED goes green and then go tothe next step.

Step 16 Test the VLANsPing from the host in port 0/4 to the host in port 0/8.


b. Why?







Step 17 Delete a Host from a VLAN

To remove a host from a VLAN, use the no form of the switchport commands in theport interface configuration mode.

Switch_A#configure terminalSwitch_A(config)#interface fastethernet 0/4Switch_A(config-if)#no switchport mode accessSwitch_A(config-if)#no switchport access vlan 2

Step 18 Display the VLAN Interface Information

a. On Switch_A, type the command show vlan at the privileged EXEC prompt.

Switch_A#show vlan

b. Is port 0/4 removed from VLAN 2?

Step 19 Delete a VLAN

a. To remove an entire VLAN, enter the configuration mode and use the negative formof the command.

Switch_A(config)#no vlan 3Deleting VLAN 3

Step 20 Display the VLAN Interface Information

a. On Switch_A, type the command show vlan at the privileged EXEC prompt.

Switch_A#show vlan

b. Is VLAN 3 removed?

c. What happened to the ports that were released from the VLANs?

Step 21 Delete VLAN 1

a. Try to delete VLAN 1, which is the default VLAN, the same way that you deletedVLAN 3.

Switch_A(config)#no vlan 1A default VLAN may not be deleted.Switch_A(vlan)#exit

b. The default VLAN cannot be deleted.

Erasing and Reloading the Switch

1. Enter into the privileged EXEC mode by typing enable. If prompted for a password,enter class (if that does not work, ask the instructor).

Switch>enable

2. Remove the VLAN database information file.

Switch#delete flash:vlan.datDelete filename [vlan.dat]?[Enter]Delete flash:vlan.dat? [confirm] [Enter]If there was no VLAN file, this message is displayed.%Error deleting flash:vlan.dat (No such file or directory)

3. Remove the switch startup configuration file from NVRAM.

Switch#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

4. Check that VLAN information was deleted.

Verify that the VLAN configuration was deleted in Step 2 using the show vlancommand. If previous VLAN configuration information (other than the defaultmanagement VLAN 1) is still present it will be necessary to power cycle the switch(hardware restart) instead of issuing the reload command. To power cycle the switch,remove the power cord from the back of the switch or unplug it. Then plug it back in.If the VLAN information was successfully deleted in Step 2, go to Step 5 and restart theswitch using the reload command.

5. Software restart (using the reload command)

Note: This step is not necessary if the switch was restarted using the power cyclemethod.

a. At the privileged EXEC mode enter the command reload.

Switch(config)#reloadThe responding line prompt will be:System configuration has been modified. Save? [yes/no]:

b. Type n and then press Enter. Theresponding line prompt will be:Proceed with reload? [confirm] [Enter]The first line of the response will be:Reload requested by console.After the switch has reloaded, the line prompt will be:Would you like to enter the initial configuration dialog? [yes/no]:

c. Type n and then press Enter. Theresponding line prompt will be: PressRETURN to get started! [Enter]

Lab 2 : VLAN Trunking

Objective

• Create a basic switch configuration and verify it.• Create multiple VLANs, name them and assign multiple member ports to them.• Create an 802.1q trunk line between the two switches to allow communication

between paired VLANs.• Test the VLANs functionality by moving a workstation from one VLAN to another.

Step 1 Configure the switch

Configure the Hostname, access and command mode passwords, as well as themanagement LAN settings. These values are shown in the chart. If problems occurwhile performing this configuration, refer to the “Basic Switch Configuration lab”. Do notconfigure VLANs and trunking yet.

Step 2 Configure the hosts attached to the switch

Configure the host to use the same subnet for the address, mask, and default gatewayas on the switch.

Step 3 Verify connectivitya. To verify that the host and switch are correctly configured, ping the switch from thehosts.

b. Were the pings successful?

c. If the answer is no, troubleshoot the host and switches configurations.


On Switch_A, type the command show vlan at the privileged EXEC prompt as follows:

Switch_A#show vlan

Step 5 Create and name three VLANs

Enter the following commands to create and name three VLANs:

Switch_A#(config)#vlan 10Switch_A(config-vlan)#name AccountingSwitch_A(config-vlan)#vlan 20Switch_A(config-vlan)#name MarketingSwitch_A(config-vlan)#vlan 30Switch_A(config-vlan)#name Engineering

Step 6 Assign ports to a VLAN 10

Assigning ports to VLANs must be done from the interface mode. Enter the followingcommands to add ports 0/4 to 0/6 to VLAN 10:



Switch_A#configure terminalSwitch_A(config)#interface fastethernet 0/7Switch_A(config-if)#switchport mode accessSwitch_A(config-if)#switchport access vlan 20Switch_A(config-if)#interface fastethernet 0/8Switch_A(config-if)#switchport mode accessSwitch_A(config-if)#switchport access vlan 20Switch_A(config-if)#interface fastethernet 0/9

Switch_A(config-if)#switchport mode accessSwitch_A(config-if)#switchport access vlan 20Switch_A(config-if)#end


Enter the following commands to add ports 0/7 to 0/9 to VLAN 20:


Step 9 Create VLANs on Switch_B

Repeat Steps 5 through 9 on Switch_B to create its VLANs


a. On both switches, type the command show vlan at the privileged EXEC prompt asfollows:

Switch_A#show vlan

b. Are ports 0/10 through 0/12 assigned to VLAN 30?


Ping from the host in Switch_A port 0/12 to the host in Switch_B port 0/12.


b. Why?

Ping from the host in Switch_A port 0/12 to the switch IP 192.168.1.2.


d. Why?

Step 12 Create the trunk

On both switches, Switch_A and Switch_B, type the following command at thefastethernet 0/1 interface command prompt. Note that it is not necessary to specify theencapsulation on a 2950, since it only supports 802.1Q.

Switch_A(config)#interface fastethernet 0/1Switch_A(config-if)#switchport mode trunkSwitch_A(config-if)#endSwitch_B(config)#interface fastethernet 0/1Switch_B(config-if)#switchport mode trunkSwitch_B(config-if)#end

2900:

Switch_A(config)#interface fastethernet0/1Switch_A(config-if)#switchport mode trunkSwitch_A(config-if)#switchport trunk encapsulation dot1qSwitch_A(config-if)#endSwitch_B(config)#interface fastethernet0/1Switch_B(config-if)#switchport mode trunkSwitch_B(config-if)#switchport trunk encapsulation dot1qSwitch_B(config-if)#end

Step 13 Verify the trunk

a. To verify that port Fast Ethernet 0/1 has been established as a trunk port, type showinterface fastethernet 0/1 switchport at the privileged EXEC mode prompt.

b. What type of trunking encapsulation is shown on the output results?

c. According to the output with show interface fastethernet 0/1 switchport onSwitch_B, is there a difference from the Administrative Trunking Encapsulation from theOperational Trunking Encapsulation?

d. On the fragment “Trunking VLANs Enable” from the output, what does the word “ALL”mean?

e. What would happen if the two ports of the trunk were using different encapsulation?

f. Explain

Step 14 Test the VLANS and the trunkPing from the host in Switch_A port 0/12 to the host in Switch_B port 0/12.


b. Why?



d. Why?

Step 15 Move host.

Move the host in Switch_A from port 0/12 to port 0/8. Wait until the port LED goes greenand then go to the next step.

Step 16 Test the VLANS and the trunk



b. Why?



d. Why?

Step 17 Move host

Move the host in Switch_B from port 0/12 to port 0/7. Wait until the port LED goes greenand then go to the next step.




b. Why?



d. Why?

Step 19 Move hosts

Move the host in Switch_A from port 0/8 to port 0/2. Wait until the port LED goes greenand then go to the next step.






c. Why?

Step 21 Move host

Move the host in Switch_B from port 0/7 to port 0/3. Wait until the port LED goes greenand then go to the next step.




b. Why?

Ping from the host in Switch_B port 0/3 to the switch IP 192.168.1.2.


d. Why?

Ping from the host in Switch_B port 0/3 to the switch IP 192.168.1.3.


f. Why?

g. What conclusions can be drawn from the testing that was just performed in regards toVLAN membership and VLANs across a trunk?

Once the steps are complete, logoff by typing exit, and turn all the devices off. Thenremove and store the cables and adapter.

Lab 3 : Configuring Static Routes

Objective

Configure static routes between routers to allow data transfer between routerswithout the use of dynamic routing protocols.

Step 1 Configure both routers

Enter the global configuration mode and configure the hostname as shown in the chart.Then configure the console, virtual terminal, and enable passwords. If there are anydifficulties, refer to the Configuring router passwords lab. Configure interfaces and IPhost tables. If there are any difficulties, refer to the Configuring Host Tables lab.

Step 2 Configure the workstations

Configure the workstations with the proper IP address, subnet mask, and defaultgateway.

a. Check connectivity between the workstations using ping.

C:\>ping 192.168.16.2Pinging 192.168.16.2 with 32 bytes of data:Request timed out.Request timed out.Request timed out.Request timed out.

Ping statistics for 192.168.16.2:Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),Approximate round trip times in milli-seconds:Minimum = 0ms, Maximum = 0ms, Average = 0ms


c. Why did the ping fail?

Step 3 Check interface status

a. Check the interfaces on both routers with the command show ip interface brief.

b. Are all the necessary interfaces up?

Step 4 Check the routing table entries

a. Using the command show ip route, view the IP routing table for GAD.

GAD>show ip routeoutput eliminatedGateway of last resort is not setC 192.168.14.0/24 is directly connected, FastEthernet0C 192.168.15.0/24 is directly connected, Serial0b. Use the command show ip route, view the IP routing table for BHM.

BHM>show ip routeOutput eliminated.Gateway of last resort is not setC 192.168.15.0/24 is directly connected, Serial0C 192.168.16.0/24 is directly connected, FastEthernet0

c. Are all of the routes needed in the routing tables?

d. Can a host on subnet 192.168.16.0 see a host on network 192.168.14.0?

If a route is not in the routers to which the host is connected, the host cannot reach thedestination host.

Step 5 Adding static routes

a. How can this situation be changed so that the hosts can ping each other?Add static routes to each router or run a routing protocol.

b. In global configuration mode, add a static route on Router1 to network 192.168.16.0and on Router2 to network 192.168.14.0.

GAD(config)#ip route 192.168.16.0 255.255.255.0 192.168.15.2BHM(config)#ip route 192.168.14.0 255.255.255.0 192.168.15.1

c. Why is a static route needed on both routers?

Step 6 Verify the new routes

a. Use the command show ip route, view the IP routing table for GAD.

GAD>show ip routeoutput eliminatedGateway of last resort is not setC 192.168.14.0/24 is directly connected, FastEthernet0C 192.168.15.0/24 is directly connected, Serial0S 192.168.16.0/24 [1/0] via 192.168.15.2

b. Using the command show ip route, view the IP routing table for BHM.

BHM>show ip routeOutput eliminated.Gateway of last resort is not setS 192.168.14.0/24 [1/0] via 192.168.15.1C 192.168.15.0/24 is directly connected, Serial0C 192.168.16.0/24 is directly connected, FastEthernet0

c. Are all of the routes needed in the routing tables?

d. Can a host on subnet 192.168.16.0 see a host on network 192.168.14.0?

Step 7 ping host to host again

a. Check connectivity between the workstations using ping.

C:\>ping 192.168.16.2Pinging 192.168.16.2 with 32 bytes of data:Reply from 192.168.16.2: bytes=32 time=20ms TTL=254Reply from 192.168.16.2: bytes=32 time=20ms TTL=254Reply from 192.168.16.2: bytes=32 time=20ms TTL=254Reply from 192.168.16.2: bytes=32 time=20ms TTL=254Ping statistics for 192.168.16.2:Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:Minimum = 20ms, Maximum = 20ms, Average = 20ms

b. If the ping was not successful, check routing table to make sure static routes areentered correctly. Upon completion of the previous steps, logoff by typing exit. Turn therouter off.

Lab 4 : Configuring RIP

Objective

• Setup an IP addressing scheme using class B networks.

• Configure the RIP dynamic routing protocol on routers.

• Observe routing activity using the debug ip rip command.

Step 1 Configure the routersFrom the global configuration mode, configure the hostname as shown in the chart.Then configure the console, virtual terminal, and enable passwords. If there is aproblem doing this, refer to the configuring router passwords lab. Next, configure theinterfaces according to the chart. Refer to the Configuring Host Tables lab forassistance.

Step 2 Check the routing table entriesa. Using the command show ip route, view the IP routing table for GAD.

GAD>show ip routeoutput eliminatedGateway of last resort is not setC 172.16.0.0/24 is directly connected, FastEthernet0C 172.17.0.0/24 is directly connected, Serial0

b. Using the command show ip route, view the IP routing table for BHM.

BHM>show ip routeoutput eliminatedGateway of last resort is not setC 172.17.0.0/24 is directly connected, Serial0

C 172.18.0.0/24 is directly connected, FastEthernet0

Step 3 Configure the routing protocol on the Gadsden routerFrom the global configuration mode, enter the following:

GAD(config)#router ripGAD(config-router)#network 172.16.0.0GAD(config-router)#network 172.17.0.0GAD(config-router)#exit

Step 4 Save the Gadsden router configurationGAD#copy running-config startup-config

Step 5 Configure the routing protocol on the Birmingham routera. From the global configuration mode, enter the following:

BHM(config)#router ripBHM(config-router)#network 172.17.0.0BHM(config-router)#network 172.18.0.0BHM(config-router)#exitBHM(config)#exit

Step 6 Save the Birmingham router configurationBHM#copy running-config startup-config

Step 7 Configure the hosts with the proper IP address, subnet mask and defaultgateway

Step 8 Verify that the internetwork is functioning by pinging the FastEthernetinterface of the other routera. From the host attached to GAD, is it possible to ping the BHM router FastEthernetinterface?

b. From the host attached to BHM, is it possible to ping the GAD router FastEthernetinterface?

c. If the answer is no for either question, troubleshoot the router configurations to findthe error. Then do the pings again until the answer to both questions is yes.

Step 9 Make sure that routing updates are being senta. Type the command debug ip rip and the privileged EXEC mode prompt. Wait for atleast 45 seconds.

b. Was there any output from the debug command?

c. What did the output show ?

d. To turn off specific debug commands type the no option, for example no debug ip ripevents. To turn off all debug commands type undebug all.

Step 10 Show the routing tables for each routera. From the enable or privileged EXEC mode, examine the routing table entries usingthe show ip route command on each router.

b. What are the entries in the GAD routing table?

c. What are the entries in the BHM routing table?

Upon completion of the previous steps, log off by typing exit and turn the router off.

Lab 5 : Configuring EIGRP Routing

Objective

• Setup an IP addressing scheme for the network.• Configure and verify Enhanced Interior Gateway Routing Protocol (EIGRP)

routing.

Step 1 Configure the routers

On the routers, enter the global configuration mode and configure the hostname asshown in the chart. Then configure the console, virtual terminal and enable passwords.Next configure the interfaces according to the chart. Finally, configure the IPhostnames. Do not configure the routing protocol until specifically told to.

Step 2 Save the configuration information from the privileged EXEC commandmode

Paris#copy running-config startup-configDestination filename [startup-config]? [Enter]


a. Each workstation should be able to ping the attached router. Troubleshoot asnecessary.

Remember to assign a specific IP address and default gateway to the workstation.Using the ipconfig command in a DOS window.

b. At this point the workstations will not be able to communicate with each other. Thefollowing steps will demonstrate the process required to get communication workingusing EIGRP as the routing protocol.Step 4 View the routers configuration and interface information

a. At the privileged EXEC mode prompt type:

Paris#show running-config

b. Using the show ip interface brief command, check the status of each interface.

c. What is the state of the interfaces on each router?

Paris:FastEthernet 0:Serial 0:Warsaw:FastEthernet 0:Serial 0:

d. Ping from one of the connected serial interfaces to the other.

e. What the ping successful?

f. If the ping was not successful, troubleshoot the routers configuration until the ping issuccessful.

Step 5 Configure EIGRP routing on router Paris

a. Enable the EIGRP routing process on Paris, and configure the networks it willadvertise. Use EIGRP autonomous system number 101.

Paris(config)#router eigrp 101Paris(config-router)#network 192.168.3.0Paris(config-router)#network 192.168.2.0Paris(config-router)#end

b. Show the routing table for the Paris router.

Paris#show ip route

c. Are there any entries in the routing table?

d. Why?

Step 6 Configure EIGRP routing on router Warsawa. Enable the EIGRP routing process on Warsaw, and configure the networks it willadvertise. Use EIGRP autonomous system number 101.

Warsaw(config)#router eigrp 101Warsaw(config-router)#network 192.168.2.0Warsaw(config-router)#network 192.168.1.0Warsaw(config-router)#end

b. Show the routing table for the Warsaw router.

Warsaw#show ip route

c. Are there any EIGRP entries in the routing table now?

d. What is the address type in the EIGRP 192.168.2.0 route?

e. What does the D mean in the first column of the routing table?

Step 7 Show EIGRP neighbors

a. From the Paris router show any neighbors connected using the show ip eigrpneighbors command at the privileged EXEC mode prompt.

b. Are any neighbors shown?

Step 8 Test network connectivity

a. Ping the Paris host from the Warsaw host. Was it successful?

b. If not troubleshoot as necessary.

Step 9 View the topology table

a. To view the topology table, issue the show ip eigrp topology all-links command.

b. How many routes are in passive mode?

c. To view more specific information about a topology table entry, use an IP addresswith this command:

Paris#show ip eigrp topology 192.168.1.0

d. Based on the output of this command, does it tell what external protocol originatedthis route to 192.168.2.0?

e. Does it tell which router originated the route?

f. Finally, use show commands to view key EIGRP statistics. On the Paris router, issuethe show ip eigrp traffic command.

g. How many hello packets has the Paris router received?

h. How many has it sent?

Once the previous steps are completed, log off by typing exit, and turn the router off.Then remove and store the cables and adapter.

Lab 6 : Configuring OSPF Routing

Objective

• Setup an IP addressing scheme for Open Shortest Path First (OSPF) area.• Configure and verify OSPF routing.• Modify OSPF cost metric on an interface.


On the routers, enter the global configuration mode and configure the hostname,console, virtual terminal, and enable passwords. Next configure the interfaces and IPhostnames according to the chart. Do not configure the routing protocol until specificallytold to.

Step 2 Save the configuration information from the privileged EXEC commandmode

Cairo#copy running-config startup-configDestination filename [startup-config]?[Enter]

Moscow#copy running-config startup-configDestination filename [startup-config]?[Enter]

Why save the running configuration to the startup configuration?


a. Each workstation should be able to ping the attached router. Troubleshoot asnecessary.Remember to assign a specific IP address and default gateway to the workstation.Using the ipconfig command in a Command Prompt window.

b. At this point the workstations will not be able to communicate with each other. Thefollowing steps will demonstrate the process required to get communication workingusing OSPF as the routing protocol.

Step 4 View the routers configuration and interface information

a. At the privileged EXEC mode type:

Cairo#show running-config

b. Using the show ip interface brief command, check the status of each interface.

c. What is the state of the interfaces on each router?

Cairo:

FastEthernet 0:

Serial 0:

Moscow:

FastEthernet 0:

Serial 0:

d. On a router, ping the serial interface of the other router.


f. If the ping was not successful, troubleshoot the router configuration, until the ping issuccessful.

Step 5. Configure OSPF routing on router Cairo

a. Configure OSPF routing on each router. Use OSPF process number 1 and ensure allnetworks are in area 0.

Cairo(config)#router ospf 1Cairo(config-router)#network 192.168.1.128 0.0.0.63 area 0Cairo(config-router)#network 192.168.1.0 0.0.0.3 area 0Cairo(config-router)#end

b. Examine the running configuration file.

c. Did the IOS version automatically add any lines under router OSPF 1?

d. What did it add?

e. If there were no changes to the running configuration, type the following commands:

Cairo(config)#router ospf 1Cairo(config-router)#log-adjacency-changesCairo(config-router)#end

f. Show the routing table for the Cairo router.

Cairo#show ip route

g. Are there any entries in the routing table?

h. Why?

Step 6 Configure OSPF routing on router Moscow

a. Configure OSPF routing on each router. Use OSPF process number 1 and ensure allnetworks are in area 0.

Moscow(config)#router ospf 1Moscow(config-router)#network 192.168.0 .0 0.0.0.255 area 0Moscow(config-router)#network 192.168.1.0 0.0.0.3 area 0Moscow(config-router)#end

b. Examine the running configuration file.

c. Did the IOS version automatically add any lines under router OSPF 1?

d. If there were no changes to the running configuration, type the following commands:

Moscow(config)#router ospf 1Moscow(config-router)#log-adjacency-changesMoscow(config-router)#end

Step 7 Show the routing table entries

a. Show the routing table entries for the Cairo router.Cairo#show ip route

b. Are there any OSPF entries in the routing table now?

c. What is the metric value of the OSPF route?

d. What is the VIA address in the OSPF route?

e. Are routes to all networks shown in the routing table?

f. What does the O mean in the first column of the routing table?

Step 8 Test network connectivity

a. Ping the Cairo host from the Moscow host. Was it successful?

b. If not troubleshoot as necessary.

Step 9 Look at the OSPF cost on the Cairo router interfaces

a. Show the properties of the Cairo router serial and FastEthernet interfaces using theshow interfaces command.

b. What is the default bandwidth of the interfaces?

c. Serial Interface:

d. FastEthernet Interface:

e. Calculate the OSPF cost.

f. Serial Interface:

g. FastEthernet Interface:

Step 10 Record the OSPF cost of the serial and FastEthernet interfaces

a. Using the show ip ospf interface command, record the OSPF cost of the serial andFast Ethernet interfaces.b. OSPF cost of Serial Interface:

c. OSPF cost of Ethernet Interface:

d. Do these agree with the calculations?

e. The clock rate set for the interface should have been 64000.

Step 11 Manually set the cost on the serial interface

On the Serial interface of the Cairo router, set the OSPF cost to 1562 by typing IP ospfcost 1562 at the serial interface configuration mode prompt.

Step 12. Verify cost

a. Note that it is essential that all connected links agree about the cost for consistentcalculation of the shortest path first algorithm (SPF) in an area.

b. Verify that the interface OSPF cost was successfully modified.

Link Bandwidth Default OSPF Cost56 Kbps 1785T1 6510-Mbps 1016-Mbps Token-ring 6FDDI/Fast Ethernet 1

c. Reverse the effect of this command by entering in interface configuration mode thecommand no ip ospf cost.

d. Verify that the default cost for the interface has returned.

e. Enter the command bandwidth 2000 at the serial 0 interface configuration mode.

f. Record the new OSPF cost of the Serial interface.

g. Can the OSPF cost of an Ethernet interface be modified in this way?

h. The speed can be set on an Ethernet interface. Will this affect the OSPF cost of thatinterface?

i. Verify or explain the above answer.

j. Reset the bandwidth on the serial interface using the no bandwidth 2000 at the serial0 interface configuration mode.

Once completion previous steps are completed, log off by typing exit, and turn therouter off. Then remove and store the cables and adapters.

Lab 7 : Configuring PPP & PPP Authentication

Objective

Configure PPP authentication using CHAP on two routers.


Configure all of the following according to the chart:• The hostname• The console• The virtual terminal• The enable passwordsIf problems occur during this configuration, refer to Lab 1.1.4a Configuring NAT.

Step 2 Configure the Tokyo interface as shownConfigure the Tokyo router serial interface as follows:

Tokyo(config)#interface serial 0Tokyo(config-if)#ip address 192.168.15.2 255.255.255.0Tokyo(config-if)#encapsulation pppTokyo(config-if)#no shutdownTokyo(config-if)#exitTokyo(config)#exit

Step 3 Configure the Madrid interface as shownConfigure the Madrid router serial interface as follows:

Madrid(config)#interface serial 0Madrid(config-if)#ip address 192.168.15.1 255.255.255.0Madrid(config-if)#clockrate 64000Madrid(config-if)#encapsulation pppMadrid(config-if)#no shutdownMadrid(config-if)#exit

Madrid(config)#exit

Step 4 Save the configurationMadrid#copy running-config startup-configTokyo#copy running-config startup-config

Step 5 Enter the command show interface serial 0 on MadridMadrid#show interface serial 0Encapsulation

Step 6 Enter the command show interface serial 0 on TokyoTokyo#show interface serial 0Encapsulation

Step 7 Verify that the serial connection is functioning by pinging the serialinterface of the other routerMadrid#ping 192.168.15.2Tokyo#ping 192.168.15.1If the pings are unsuccessful, troubleshoot the router configurations to find the error.Then do the pings again until both pings are successful.

Step 8 Configure PPP authenticationConfigure usernames and password on the Madrid router. The passwords must be thesame on both routers. The username must reflect the other routers hostname exactly.The password and user names are case sensitive:

Madrid(config)#username Tokyo password ciscoMadrid(config)#interface serial 0Madrid(config-if)#ppp authentication chap

Step 9 Verify that the serial connection is functioninga. Verify that the serial connection is functioning by pinging the serial interface of theother router:Madrid#ping 192.168.15.2

b. Is the ping successful?

c. Why?

Step 10 Configure PPP authentication

Configure usernames and password on the Tokyo router. The passwords must be thesame on both routers. The username must reflect the other routers hostname exactly.The password and user names are case sensitive:

Tokyo(config)#username Madrid password cisco

Tokyo(config)#interface serial 0Tokyo(config-if)#ppp authentication chap

Step 11 Verify that the serial connection is functioning

a. Verify that the serial connection is functioning by pinging the serial interface of theother router:Tokyo#ping 192.168.15.1

b. Is the ping successful?

c. Why?

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

Lab 8 : Configuring Frame-Relay Sub-Interfaces

10.10.10.1/24FR Switch

200.2.2.17/30 200.2.2.18/30 172.16.1.1/24

S0

London

S1

ParisDLCI 102 DLCI 201

Objective

• Create a basic router configuration.

• Frame-Relay Switch configuration.

• Configure two routers in a point-to-point Frame Relay network.

• Configure RIPv2 routing

Step 1: Configure the routersConfigure all of the following according to the figure:

1. The hostname

2. The interfaces ip address

Steps 2: Frame-Relay Switch configurationReference Activity 6-2

Step 3: Configure two routers in a point-to-point Frame Relay network1. First, the Frame Relay encapsulation type to be used on this link must be defined

using the following commands:

London#configure terminal

London(config)#interface serial 0London(config-if)#encapsulation frame-relay ietfLondon(config-if)#frame-relay lmi-type ciscoLondon(config-if)#no shutdown

2. The same commands are used to configure the Paris routers:

Paris#configure terminal

Paris(config)#interface serial 0Paris(config-if)#encapsulation frame-relay ietfParis(config-if)#frame-relay lmi-type ansiParis(config-if)#no shutdown

3. Create subinterfaces on the London and Paris 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 futuretroubleshooting, use the data-link connection identifier (DLCI) number as thesubinterface number. The commands to create a subinterface are as follows:

London(config-if)#interface serial 0.102 point-to-pointLondon(config-if)#description PVC to Paris, DLCI 102London(config-if)#ip address 200.2.2.17 255.255.255.252London(config-if)#frame-relay interface-dlci 102To configure the subinterfaces on the Paris router, use the following commands:

Paris(config-if)#interface Serial 0.201 point-to-pointParis(config-if)#description PVC to London, DLCI 201Paris(config-if)#ip address 200.2.2.18 255.255.255.252Paris(config-if)#frame-relay interface-dlci 201Step 4: Configure RIPv2 routing

1. To configure the routing protocol RIPv2, use the following configuration syntax:

London(config-if)#router ripLondon(config-router)#network 10.0.0.0London(config-router)#network 200.2.2.0London(config-router)#version 2

Paris(config-if)#router ripParis(config-router)#network 172.16.0.0Paris(config-router)#network 200.2.2.0Paris(config-router)#version 2

2. Verifying Frame Relay connection

On the London router, issue the command show frame-relay pvc:

London#show frame-relay pvc

How many active local PVCs are there?

What is the interface value?

What is the PVC status?

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

London#show frame-relay map

What is the status of the links?

The DLCIs are defined as what type?

Are the DLCIs the same on the Paris router?

Look at the LMI statistics using the show frame-relay lmi command:

London#show frame-relay lmi

Which fields have non-zero counter values?

What is the LMI type?

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

London#show ip route

Is the routing protocol working?

If not, troubleshoot the routers configurations.

List the RIPv2 routes