Week 3 - Lab 2: Basic EIGRP Configuration Lab

Default
Device Interface IP Address Subnet Mask
Gateway
Fa0/0 [Link] [Link] N/A
R1 S0/0/0 [Link] [Link] N/A
S0/0/1 [Link] [Link] N/A
Fa0/0 [Link] [Link] N/A
S0/0/0 [Link] [Link] N/A
R2
S0/0/1 [Link] [Link] N/A
Lo0 [Link] [Link] N/A
Fa0/0 [Link] [Link] N/A
R3 S0/0/0 [Link] [Link] N/A
S0/0/1 [Link] [Link] N/A
PC1 NIC [Link] [Link] [Link]
PC2 NIC [Link] [Link] [Link]
PC3 NIC [Link] [Link] [Link]

Learning Objectives

Upon completion of this lab, you will be able to:

  Cable a network according to the Topology Diagram.
 Erase the startup configuration and reload a router to the default state.
 Perform basic configuration tasks on a router.
 Configure and activate interfaces.
 Configure EIGRP routing on all routers.
 Verify EIGRP routing using show commands.
 Disable automatic summarization.
 Configure manual summarization.
 Document the EIGRP configuration.

Scenario

In this lab activity, you will learn how to configure the routing protocol EIGRP using
the network shown in the Topology Diagram. A loopback address will be used on the
R2 router to simulate a connection to an ISP, where all traffic that is not destined for
the local network will be sent. Some segments of the network have been subnetted
using VLSM. EIGRP is a classless routing protocol that can be used to provide subnet
mask information in the routing updates. This will allow VLSM subnet information to
be propagated throughout the network.

Task 1: Prepare the Network.

Step 1: Cable a network that is similar to the one in the Topology Diagram.

You can use any current router in your lab as long as it has the required interfaces
shown in the topology.

Step 2: Clear any existing configurations on the routers.

Task 2: Perform Basic Router Configurations.

Perform basic configuration of the R1, R2, and R3 routers according to the following
guidelines:

1. Configure the router hostname.

2. Disable DNS lookup.
3. Configure an EXEC mode password.
4. Configure a message-of-the-day banner.
5. Configure a password for console connections.
6. Configure a password for VTY connections.

Task 3: Configure and Activate Serial and Ethernet Addresses.

Step 1: Configure the interfaces on the R1, R2, and R3 routers.

Configure the interfaces on the R1, R2, and R3 routers with the IP addresses from the
table under the Topology Diagram.

Step 2: Verify IP addressing and interfaces.

Use the show ip interface brief command to verify that the IP addressing is correct
and that the interfaces are active.
When you have finished, be sure to save the running configuration to the NVRAM of
the router.

Step 3: Configure Ethernet interfaces of PC1, PC2, and PC3.

Configure the Ethernet interfaces of PC1, PC2, and PC3 with the IP addresses and
default gateways from the table under the Topology Diagram.

Task 4: Configure EIGRP on the R1 Router.

Step 1: Enable EIGRP.

Use the router eigrp command in global configuration mode to enable EIGRP
on the R1 router. Enter a process ID of 1 for the autonomous-system parameter.
R1(config)#router eigrp 1

Step 2: Configure classful network [Link].

Once you are in the Router EIGRP configuration sub-mode, configure the classful
network [Link] to be included in the EIGRP updates that are sent out of R1.
R1(config-router)#network [Link]

The router will begin to send EIGRP update messages out each interface belonging to
the [Link] network. EIGRP updates will be sent out of the FastEthernet0/0 and
Serial0/0/0 interfaces because they are both on subnets of the [Link] network.

Step 3: Configure the router to advertise the [Link]/30 network attached to

the Serial0/0/1 interface.

Use the wildcard-mask option with the network command to advertise only the subnet
and not the entire [Link] classful network.
Note: Think of a wildcard mask as the inverse of a subnet mask. The inverse of the
subnet mask [Link] is [Link]. To calculate the inverse of the subnet mask,
subtract the subnet mask from [Link]:

[Link]
– [Link] Subtract the subnet mask
-------------------
0. 0. 0. 3 Wildcard mask

R1(config-router)# network [Link] [Link]

When you are finished with the EIGRP configuration for R1, return to privileged
EXEC mode and save the current configuration to NVRAM.

Task 5: Configure EIGRP on the R2 and R3 Routers.

Step 1: Enable EIGRP routing on the R2 router using the router eigrp command.

Use a process ID of 1.
R2(config)#router eigrp 1

Step 2: Use the classful address [Link] to include the network for the
FastEthernet0/0 interface.

R2(config-router)#network [Link]

Notice that DUAL sends a notification message to the console stating that a neighbor
relationship with another EIGRP router has been established.
What is the IP address of the EIGRP neighbor router?
________________________________________
What interface on the R2 router is the neighbor adjacent to?
________________________________________

Step 3: Configure the R2 router to advertise the [Link]/30 network

attached to the Serial0/0/1 interface.

1. Use the wildcard-mask option with the network command to advertise only the
subnet and not the entire [Link] classful network.
2. When you are finished, return to privileged EXEC mode.
R2(config-router)#network [Link] [Link]
R2(config-router)#end
Step 4: Configure EIGRP on the R3 router using the router eigrp and network
commands.

1. Use a process ID of 1.
2. Use the classful network address for the network attached to the FastEthernet0/0
interface.
3. Include the wildcard masks for the subnets attached to the Serial0/0/0 and Serial
0/0/1 interfaces.
4. When you are finished, return to privileged EXEC mode.
R3(config)#router eigrp 1
R3(config-router)#network [Link]
R3(config-router)#network [Link] [Link]
R3(config-router)#

Notice that when the networks for the serial links from R3 to R1 and R3 to R2 are
added to the EIGRP configuration, DUAL sends a notification message to the console
stating that a neighbor relationship with another EIGRP router has been established.

Task 6: Verify EIGRP Operation.

Step 1: View neighbors.

On the R1 router, use the show ip eigrp neighbors command to view the neighbor
table and verify that EIGRP has established an adjacency with the R2 and R3 routers.
You should be able to see the IP address of each adjacent router and the interface that
R1 uses to reach that EIGRP neighbor.
R1#show ip eigrp neighbors

Step 2: View routing protocol information.

On the R1 router, use the show ip protocols command to view information about the
routing protocol operation. Notice that the information that was configured in Task 5,
such as protocol, process ID, and networks, is shown in the output. The IP addresses
of the adjacent neighbors are also shown.
R1#show ip protocols

Notice that the output specifies the process ID used by EIGRP. Remember, the
process ID must be the same on all routers for EIGRP to establish neighbor
adjacencies and share routing information.

Task7: Examine EIGRP Routes in the Routing Tables.

Step1: View the routing table on the R1 router.

EIGRP routes are denoted in the routing table with a D, which stands for DUAL
(Diffusing Update Algorithm), which is the routing algorithm used by EIGRP.
R1#show ip route

Notice that the [Link]/16 parent network is variably subnetted with three child
routes using either a /24 or /30 mask. Also notice that EIGRP has automatically
included a summary route to Null0 for the [Link]/16 network. The [Link]/16
route does not actually represent a path to reach the parent network, [Link]/16. If
a packet destined for [Link]/16 does not match one of the level 2 child routes, it is
sent to the Null0 interface.

The [Link]/24 Network is also variably subnetted and includes a Null0 route.

Step 2: View the routing table on the R3 router.

The routing table for R3 shows that both R1 and R2 are automatically summarizing
the [Link]/16 network and sending it as a single routing update. Because of
automatic summarization, R1 and R2 are not propagating the individual subnets.
Because R3 is getting two equal cost routes for [Link]/16 from both R1 and R2,
both routes are included in the routing table.

Task 8: Configure EIGRP Metrics.

Step 1: View the EIGRP metric information.

Use the show ip interface command to view the EIGRP metric information
for the Serial0/0/0 interface on the R1 router. Notice the values that are shown for the
bandwidth, delay, reliability, and load.
R1#show interface serial0/0/0

Step 2: Modify the bandwidth of the Serial interfaces.

On most serial links, the bandwidth metric will default to 1544 Kbits. If this is not the
actual bandwidth of the serial link, the bandwidth will need to be changed so that the
EIGRP metric can be calculated correctly.
For this lab, the link between R1 and R2 will be configured with a bandwidth of 64
kbps, and the link between R2 and R3 will be configured with a bandwidth of 1024
kbps. Use the bandwidth command to modify the bandwidth of the Serial interfaces of
each router.
R1 router:
R1(config)#interface serial0/0/0
R1(config-if)#bandwidth 64

R2 router:
R2(config)#interface serial0/0/0
R2(config-if)#bandwidth 64
R2(config)#interface serial0/0/1
R2(config-if)#bandwidth 1024

R3 router:
R3(config)#interface serial0/0/1
R3(config-if)#bandwidth 1024

Note: The bandwidth command only modifies the bandwidth metric used by routing
protocols, not the physical bandwidth of the link.

Step 3: Verify the bandwidth modifications.

Use the show ip interface command to verify that the bandwidth value of each
link has been changed.

Note: Use the interface configuration command no bandwidth to return the

bandwidth to its default value.

Task 9: Examine Successors and Feasible Distances.

Step 1: Examine the successors and feasible distances in the routing table on R2.

R2#show ip route

Step 2: Answer the following questions:

What is the best path to PC1?

_____________________________________________________________________
_______________

A successor is a neighboring router that is currently being used for packet forwarding.
A successor is the least-cost route to the destination network. The IP address of a
successor is shown in a routing table entry right after the word “via”.

What is the IP address and name of the successor router in this route?
________________________________________
Feasible distance (FD) is the lowest calculated metric to reach that destination. FD is
the metric listed in the routing table entry as the second number inside the brackets.

What is the feasible distance to the network that PC1 is on?

________________________________________

Task 10: Determine if R1 is a Feasible Successor for the Route from R2 to the
[Link] Network.

A feasible successor is a neighbor who has a viable backup path to the same network
as the successor. In order to be a feasible successor, R1 must satisfy the feasibility
condition. The feasibility condition (FC) is met when a neighbor’s reported distance
(RD) to a network is less than the local router’s feasible distance to the same
destination network.

Step 1: Examine the routing table on R1.

What is the reported distance to the [Link] network?

________________________________________

Step 2: Examine the routing table on R2.

What is the feasible distance to the [Link] network?

________________________________________

Would R2 consider R1 to be a feasible successor to the [Link] network?

_______

Task 11: Examine the EIGRP Topology Table.

Step 1: View the EIGRP topology table.

Use the show ip eigrp topology command to view the EIGRP topology table
on R2.

Step 2: View detailed EIGRP topology information.

Use the [network] parameter of the show ip eigrp topology command to

view detailed EIGRP topology information for the [Link] network.

R2#show ip eigrp topology [Link]

How many successors are there for this network?
________________________________________
What is the feasible distance to this network?
________________________________________
What is the IP address of the feasible successor?
________________________________________
What is the reported distance for [Link] from the feasible successor?
________________________________________
What would be the feasible distance to [Link] if R1 became the successor?
________________________________________

Task 12: Disable EIGRP Automatic Summarization.

Step 1: Examine the routing table of the R3 router.

Notice that R3 is not receiving individual routes for the [Link]/24, [Link]/24,
and [Link]/24 subnets. Instead, the routing table only has a summary route to the
classful network address of [Link]/16 through the R1 router. This will cause
packets that are destined for the [Link]/24 network to be sent through the R1
router instead of being sent straight to the R2 router.

Why is the R1 router ([Link]) the only successor for the route to the
[Link]/16 network?
_____________________________________________________________________
_______________
_____________________________________________________________________
_______________
_____________________________________________________________________
_______________

Notice that the reported distance from R2 is higher than the feasible distance from R1.
R3#show ip eigrp topology

Step 3: Disable automatic summarization on all three routers with the no

auto-summarycommand.

R1(config)#router eigrp 1
R1(config-router)#no auto-summary

R2(config)#router eigrp 1
R2(config-router)#no auto-summary
R3(config)#router eigrp 1
R3(config-router)#no auto-summary

Step 4: View the routing table on R1 again.

Notice that individual routes for the [Link]/24, [Link]/24, and [Link]/24
subnets are now present and the summary Null route is no longer listed.

Task 13: Configure Manual Summarization.

Step 1: Add loopback addresses to R3 router.

Add two loopback addresses, [Link]/24 and [Link]/24, to the R3 router.

These virtual interfaces will be used to represent networks to be manually summarized
along with the [Link]/24 LAN.
R3(config)#interface loopback1
R3(config-if)#ip address [Link] [Link]
R3(config-if)#interface loopback2
R3(config-if)#ip address [Link] [Link]

Step 2: Add the [Link] and [Link] networks to the EIGRP

configuration on R3.

R3(config)#router eigrp 1
R3(config-router)#network [Link]
R3(config-router)#network [Link]

Step 3: Verify new routes.

View the routing table on the R1 router to verify that the new routes are being sent out
in the EIGRP updates sent by R3.

Step 4: Apply manual summarization to outbound interfaces.

The routes to the [Link]/24, [Link]/24, and [Link]/24 networks can be

summarized in the single network [Link]/22. Use the ip summary-address eigrp
as-number network-address subnet-mask command to configure manual
summarization on each of the outbound interfaces connected to EIGRP neighbors.
R3(config)#interface serial0/0/0
R3(config-if)#ip summary-address eigrp 1 [Link]
[Link]
R3(config-if)#interface serial0/0/1
R3(config-if)#ip summary-address eigrp 1 [Link]
[Link]
R3(config-if)#

Step 5: Verify the summary route.

View the routing table on the R1 router to verify that the summary route is being sent
out in the EIGRP updates sent by R3.

Week 3 - Lab 3: Basic OSPF Configuration Lab.

Default Gateway
Device Interface IP Address Subnet Mask

Fa0/0 [Link] [Link] N/A

R1 S0/0/0 [Link] [Link] N/A
S0/0/1 [Link] [Link] N/A
Fa0/0 [Link] [Link] N/A
R2 S0/0/0 [Link] [Link] N/A
S0/0/1 [Link] [Link] N/A
Fa0/0 [Link] [Link] N/A
R3 S0/0/0 [Link] [Link] N/A
S0/0/1 [Link] [Link] N/A
PC1 NIC [Link] [Link] [Link]
PC2 NIC [Link] [Link] [Link]
PC3 NIC [Link] [Link] [Link]
Instructions:

Learn to Configure Basic OSPF

Learning Objectives
 Cable a network according to the Topology Diagram
 Erase the startup configuration and reload a router to the default state
 Perform basic configuration tasks on a router
 Configure and activate interfaces
 Configure OSPF routing on all routers
 Configure OSPF router IDs
 Verify OSPF routing using show commands
 Configure a static default route
 Propagate default route to OSPF neighbors
 Configure OSPF Hello and Dead Timers
 Configure OSPF on a Multiaccess network
 Configure OSPF priority
 Understand the OSPF election process
 Document the OSPF configuration

Task 2: Basic Router Configurations

Perform basic configuration of the R1, R2, and R3 routers according to the following guidelines:

 Configure the router hostname

 Disable DNS lookup
  Configure the EXEC mode password as class
 Configure a password for console connections as cisco (case sensitive)
 Configure a password for VTY connections as cisco (case sensitive)

Task 3: Configure and Activate Serial and Ethernet Addresses

Step 1 Configure the interfaces on the R1, R2, and R3 routers with the IP addresses from the table

Task 4: Configure OSPF on the R1 Router

Step 1 Configure OSPF with a process ID number of 1, advertise all networks.

Task 5: Configure OSPF on the R2 and R3 Routers

Step 1 Configure OSPF with a process ID number of 1, advertise all networks.

Task 6: Configure OSPF Router IDs

Step 1 Configure R1 with a Loopback0 interface of [Link] [Link]
Step 2 Configure R2 with a Loopback0 interface of [Link] [Link]
Step 3 Configure R3 with a Loopback0 interface of [Link] [Link]
Step 4 Copy all running-configs to the NVRAM and reload routers

Task 7: Verify OSPF Operation

Step 1 Use the show ip ospf neighbor command to verify information about other routers was learned
Step 2 Use the show ip protocols command to view information about the routing protocol

Task 8: Examine OSPF Routes in the Routing Tables

Step 1 Use the show ip route command to view all learned networks via OSPF

Task 9: Configure OSPF Cost

Step 1 Configure R1 serial interfaces with a bandwidth of 64
Step 2 Configure R1 serial interfaces with a bandwidth of 64
Step 3 Configure R1 serial interfaces with a cost of 1562

Task 10: Redistribute an OSPF Default Route

Step 1 Configure a loopback address on the R1 router to simulate a link to an ISP.
Step 2 Create the loopback 1 [Link] [Link] on the R1 router
Step 3 Create a Default route directing traffic to the loopback interface.
Step 4 Redistribute the default route using OSPF

Task 11: Verifying OSPF

Step 1 Using the show ip route command verify that the default route was learned.

Week 3 - Lab 5:
Configuring Traditional Inter-VLAN Routing

Addressing Table

Default
Device Interface IP Address Subnet Mask
Gateway
Fa0/0 [Link] [Link] N/A
R1
Fa0/1 [Link] [Link] N/A
PC1 NIC [Link] [Link] [Link]
PC2 NIC [Link] [Link] [Link]
Learning Objectives

 Test connectivity without inter-VLAN routing

 Add VLANs to a switch
 Configure IP addressing on a router
 Test connectivity with inter-VLAN routing

Introduction

In this activity, you will configure traditional inter-VLAN routing simply by

configuring two Fast Ethernet interfaces on a router. R1 has two connections to S1,
one for each of the two VLANs. S1 and R1 already have basic configurations. The
user EXEC password is cisco, and the privileged EXEC password is class. You will
complete the configuration by adding VLANs to S1 and assigning VLANs to the
correct ports. Then you will configure R1 with IP addressing. In traditional inter-
VLAN routing, there are no additional, VLAN-related configurations needed on R1.

Task 1: Test Connectivity Without Inter-VLAN Routing

Step 1. Ping between PC1 and PC3.

Wait for switch convergence. The link lights on the switch connecting to PC1 and
PC3 change from amber to green. When the link lights are green, ping between PC1
and PC3. Because the two PCs are on separate networks and the router is not
configured, they cannot communicate with one another, so the ping fails.

Step 2. Switch to simulation mode to monitor pings.

 Switch to simulation mode by clicking the Simulation tab or pressing Shift+S.

 Click Capture/Forward to see the steps the ping takes between PC1 and PC3.
 Notice how the ping cannot even cross the switch.

Your completion percentage should be 0%.

Task 2: Add VLANs

Step 1. Create VLANs on S1.

Create two VLANs on S1, one for PC1 and one for PC3. PC1 belongs to VLAN 10,
and PC3 belongs to VLAN 30. To create the VLANs, issue the vlan 10 and vlan
30 commands in global configuration mode.
S1#configure terminal
S1(config)#vlan 10
S1(config-vlan)#vlan 30

To check whether the VLANs were created, issue the show vlan brief command from
the privileged EXEC prompt.
S1#show vlan brief
VLAN Name Status Ports
---- -------------------------------- --------- -----------------------------
--
1 default active Fa0/1, Fa0/2, Fa0/3, Fa0/4
Fa0/5, Fa0/6, Fa0/7, Fa0/8
Fa0/9, Fa0/10, Fa0/11, Fa0/12
Fa0/13, Fa0/14, Fa0/15,
Fa0/16
Fa0/17, Fa0/18, Fa0/19,
Fa0/20
Fa0/21, Fa0/22, Fa0/23,
Fa0/24
Gig1/1, Gig1/2
10 VLAN0010 active
30 VLAN0030 active
1002 fddi-default active
1003 token-ring-default active
1004 fddinet-default active
1005 trnet-default active

Step 2. Assign the VLANs to ports.

Each port on the switch is assigned to a VLAN to allow for inter-VLAN

communication.

Assign the switch ports as follows:

 Assign the Fa0/8 and Fa0/11 interfaces to VLAN 10.

 Assign the Fa0/5 and Fa0/6 interfaces to VLAN 30.

To assign a VLAN to a port, enter the interface configuration. For Fa0/8, the
command is interface fa0/8. The switchport mode access command sets the port to
access [Link] switchport access vlan 10 command assigns VLAN 10 to that port.
S1(config)#interface fa0/8
S1(config-if)#switchport mode access
S1(config-if)#switchport access vlan 10

Repeat the above steps for Fa0/5, Fa0/6, and Fa0/11, assigning the correct VLANs to
each interface.

Step 3. Test connectivity between PC1 and PC3.

Now issue a ping between PC1 and PC3. The ping should still fail.

Step 4. Check results.

Your completion percentage should be 45%. If not, click Check Results to see which
required components are not yet completed.

Task 3: Configure IP Addressing

Step 1. Configure IP addressing on R1.

Configure the Fa0/0 interface of R1 with the IP address [Link] and subnet mask
[Link].

Configure the Fa0/1 interface with the IP address [Link] and subnet mask
[Link].

Issue the no shutdown command on both interfaces to bring them up.

R1(config)#interface fa0/0
R1(config-if)#ip address [Link] [Link]
R1(config-if)#no shutdown
R1(config-if)#interface fa0/1
R1(config-if)#ip address [Link] [Link]
R1(config-if)#no shutdown

Step 2. Check results.

Your completion percentage should be 100%. If not, click Check Results to see
which required components are not yet completed.

Task 4: Test Connectivity Again

Step 1. Ping between PC1 and PC3.

Wait for STP to converge. Then ping from PC1 to PC3. The ping should succeed.

Step 2. Switch to simulation mode to monitor pings.

 Switch to simulation mode by clicking the Simulation tab or pressing Shift+S.

 Click Capture/Forward to see the steps the ping takes between PC1 and PC3.
 Watch as the ping goes from PC1 through S1, then to R1, then back to S1, and
finally to the PC3.
Week 3 - Lab 6:
Configuring Router-on-a-Stick Inter-VLAN Routing

Addressing Table

Default
Device Interface IP Address Subnet Mask
Gateway
Fa0/1.10 [Link] [Link] N/A
R1
Fa0/1.30 [Link] [Link] N/A
PC1 NIC [Link] [Link] [Link]
PC2 NIC [Link] [Link] [Link]

Learning Objectives

 Test connectivity without inter-VLAN routing

 Add VLANs to a switch
 Configure IP addressing on a router
 Test connectivity with inter-VLAN routing

Introduction

In this activity, you will configure Router-on-a-Stick inter-VLAN routing. R1 has one
connection to S1. S1 and R1 already have basic configurations. The user EXEC
password is cisco, and the privileged EXEC password is class. You will complete the
configuration by adding VLANs to S1 and assigning VLANs to the correct ports.
Then you will configure R1 with subinterfaces, 802.1Q encapsulation, and IP
addressing.

Task 1: Test Connectivity Without Inter-VLAN Routing

Step 1. Ping between PC1 and PC3.

Wait for switch convergence. The link lights on the switch connecting to PC1 and
PC3 change from amber to green. When the link lights are green, ping between PC1
and PC3. Because the two PCs are on separate networks and the router is not
configured, they cannot communicate with one another, so the ping fails.

Step 2. Switch to simulation mode to monitor pings.

 Switch to simulation mode by clicking the Simulation tab or pressing Shift+S.

 Click Capture/Forward to see the steps the ping takes between PC1 and PC3.
 Notice how the ping cannot even cross the switch.

Your completion percentage should be 0%.

Task 2: Add VLANs

Step 1. Create VLANs on S1.

Create VLAN 10 and VLAN 30 on S1. PC1 belongs to VLAN 10, and PC3 belongs to
VLAN 30. To create the VLANs, issue the vlan 10 and vlan 30 commands in global
configuration mode.
S1#configure terminal
S1(config)#vlan 10
S1(config-vlan)#vlan 30

To check whether the VLANs were created, issue the show vlan brief command from
the privileged EXEC prompt.
S1#show vlan brief

VLAN Name Status Ports

---- -------------------------------- --------- -----------------------------
--
1 default active Fa0/1, Fa0/2, Fa0/3, Fa0/4
Fa0/5, Fa0/6, Fa0/7, Fa0/8
Fa0/9, Fa0/10, Fa0/11, Fa0/12
Fa0/13, Fa0/14, Fa0/15,
Fa0/16
 Fa0/17, Fa0/18, Fa0/19,
Fa0/20
Fa0/21, Fa0/22, Fa0/23,
Fa0/24
Gig1/1, Gig1/2
10 VLAN0010 active
30 VLAN0030 active
1002 fddi-default active
1003 token-ring-default active
1004 fddinet-default active
1005 trnet-default active

Step 2. Assign the VLANs to ports.

Each port on the switch is assigned to a VLAN to allow for inter-VLAN

communication. The Fa0/11 interface belongs to VLAN 10, and the Fa0/6 interface
belongs to VLAN 30.

To assign a VLAN to a port, enter the interface configuration. For Fa0/11, the
command is interface fa0/11. The switchport mode access command sets the port to
access mode. The switchport access vlan 10 command assigns VLAN 10 to that port.
S1(config)#interface fa0/11
S1(config-if)#switchport mode access
S1(config-if)#switchport access vlan 10

Repeat the steps for the Fa0/6 interface for VLAN 30.
S1(config)#interface fa0/6
S1(config-if)#switchport mode access
S1(config-if)#switchport access vlan 30

The Fa0/5 port on S1 is set to trunk, which allows it to carry information from both
VLAN 10 and VLAN 30. From the Fa0/5 interface, issue the switchport mode
trunk command to set the port to trunk.

Packet Tracer does not grade this command, but it is necessary in configuring inter-
VLAN routing.
S1(config-if)#interface fa0/5
S1(config-if)#switchport mode trunk

Step 3. Test connectivity between PC1 and PC3.

Now issue a ping between PC1 and PC3. The ping should still fail.

Step 4. Check results.

Your completion percentage should be 27%. If not, click Check Results to see which
required components are not yet completed.

Task 3: Configure IP Addressing

Step 1: Configure subinterfaces with 802.1Q encapsulation.

Create two subinterfaces on R1: Fa0/1.10 and Fa0/1.30. These subinterfaces are
assigned to VLANs. To create the first subinterface, enter subinterface configuration
mode for Fa0/1.10 by issuing theinterface fa0/1.10 command. Notice that the router
prompt changes.

While in subinterface configuration mode, issue the encapsulation dot1Q

10 command to set the encapsulation type to 802.1Q and assign VLAN 10 to the
virtual interface.

Assign the correct IP address to the port. For Fa0/1.10, it is [Link] with a subnet
mask of [Link]. Repeat these steps for the Fa0/1.30 interface using the correct
IP address and VLAN ID.
R1(config)#interface fa0/1.10
R1(config-subif)#encapsulation dot1Q 10
R1(config-subif)#ip address [Link] [Link]
R1(config-subif)#interface fa0/1.30
R1(config-subif)#encapsulation dot1Q 30
R1(config-subif)#ip address [Link] [Link]

Step 2. Check results.

Your completion percentage should be 100%. If not, click Check Results to see
which required components are not yet completed.

Task 4: Test Connectivity Again

Step 1. Ping between PC1 and PC3.

Ping from PC1 to PC3. The ping should succeed.

Step 2. Switch to simulation mode to monitor pings.

 Switch to simulation mode by clicking the Simulation tab or pressing Shift+S.

 Click Capture/Forward to see the steps the ping takes between PC1 and PC3.
 Watch how the ping goes from PC1 through S1 first, then to R1, then back to
S1, and finally to the PC3.
Week 3 - Lab 7:
Basic Inter-VLAN Routing

Addressing Table

Default
Device Interface IP Address Subnet Mask
Gateway
VLAN
S1 [Link] [Link] [Link]
99
VLAN
S2 [Link] [Link] [Link]
99
VLAN
S3 [Link] [Link] [Link]
99
See Interface Configuration
Fa0/0 N/A
R1 Table
Fa0/1 [Link] [Link] N/A
PC1 NIC [Link] [Link] [Link]
PC2 NIC [Link] [Link] [Link]
 PC3 NIC [Link] [Link] [Link]
Server NIC [Link] [Link] [Link]

Port Assignments - S2

Ports Assignment Network

Fa0/1 - 0/5 802.1q Trunks (Native VLAN 99) [Link] /24
Fa0/6 - 0/10 VLAN 30 - Guest (Default) [Link] /24
Fa0/11 - 0/17 VLAN 10 - Faculty/Staff [Link] /24
Fa0/18 - 0/24 VLAN 20 - Students [Link] /24

Subinterface Configuration Table - R1

Interface Assignment IP Address

Fa0/0.1 VLAN 1 [Link] /24
[Link]
Fa0/0.10 VLAN 10
/24
[Link]
Fa0/0.20 VLAN 20
/24
[Link]
Fa0/0.30 VLAN 30
/24
[Link]
Fa0/0.99 VLAN 99
/24

Learning Objectives

 Perform basic switch configurations

 Configure the Ethernet interfaces on the host PCs
 Configure VTP on the switches
 Configure the router and the remote server LAN

Introduction

In this activity, you will perform basic switch configurations, configure addressing on
PCs, configure VTP and inter-VLAN routing.

Task 1: Perform Basic Switch Configurations

Configure the S1, S2, and S3 switches according to the addressing table and the
following guidelines:
  Configure the switch hostname.
 Disable DNS lookup.
 Configure the default gateway.
 Configure an EXEC mode password of class.
 Configure a password of cisco for console connections.
 Configure a password of cisco for vty connections.
 Configure the default gateway on each switch.
Switch>enable
Switch#config term
Enter configuration commands, one per line. End with CNTL/Z.
Switch(config)#hostname S1
S1(config)#enable secret class
S1(config)#no ip domain-lookup
S1(config)#ip default-gateway [Link]
S1(config)#line console 0
S1(config-line)#password cisco
S1(config-line)#login
S1(config-line)#line vty 0 15
S1(config-line)#password cisco
S1(config-line)#login
S1(config-line)#end
%SYS-5-CONFIG_I: Configured from console by console
S1#copy running-config startup-config
Destination filename [startup-config]? [enter]
Building configuration...

Task 2: Configure the Ethernet Interfaces on the Host PCs

Configure the Ethernet interfaces of PC1, PC2 and PC3 with the IP addresses from the
addressing table.

Task 3: Configure VTP on the Switches

Step 1. Enable the user ports on S2 in access mode.

S2(config)#interface fa0/6
S2(config-if)#switchport mode access
S2(config-if)#no shutdown
S2(config-if)#interface fa0/11
S2(config-if)#switchport mode access
S2(config-if)#no shutdown
S2(config-if)#interface fa0/18
S2(config-if)#switchport mode access
S2(config-if)#no shutdown

Step 2. Configure VTP.

Configure VTP on the three switches using the following table. Remember that VTP
domain names and passwords are case-sensitive.

VTP
Switch Name VTP Operating Mode VTP Domain
Password
S1 Server Lab6 cisco
S2 Client Lab6 cisco
S3 Client Lab6 cisco
S1(config)#vtp mode server
Device mode already VTP SERVER.
S1(config)#vtp domain Lab6
Changing VTP domain name from NULL to Lab6
S1(config)#vtp password cisco
Setting device VLAN database password to cisco
S1(config)#end

S2(config)#vtp mode client

Setting device to VTP CLIENT mode
S2(config)#vtp domain Lab6
Changing VTP domain name from NULL to Lab6
S2(config)#vtp password cisco
Setting device VLAN database password to cisco
S2(config)#end

S3(config)#vtp mode client

Setting device to VTP CLIENT mode
S3(config)#vtp domain Lab6
Changing VTP domain name from NULL to Lab6
S3(config)#vtp password cisco
Setting device VLAN database password to cisco
S3(config)#end

Step 3. Configure trunking ports and designate the native VLAN for the trunks.

Configure Fa0/1 through Fa0/5 as trunking ports, and designate VLAN 99 as the
native VLAN for these trunks. When this activity was started, these ports were
disabled and must be re-enabled now using theno shutdown command.

Only the commands for the FastEthernet0/1 interface on each switch are shown, but
the commands should be applied up to the FastEthernet0/5 interface.
S1(config)#interface fa0/1
S1(config-if)#switchport mode trunk
S1(config-if)#switchport trunk native vlan 99
S1(config-if)#no shutdown
S1(config)#end

S2(config)#interface fa0/1
S2(config-if)#switchport mode trunk
S2(config-if)#switchport trunk native vlan 99
S2(config-if)#no shutdown
S2(config-if)#end

S3(config)#interface fa0/1
S3(config-if#switchport mode trunk
S3(config-if)#switchport trunk native vlan 99
S3(config-if)#no shutdown
S3(config-if-#end

Step 4. Configure the VTP server with VLANs.

Configure the following VLANS on the VTP server:

VLAN VLAN Name

VLAN 99 management
VLAN 10 faculty-staff
VLAN 20 students
VLAN 30 guest
S1(config)#vlan 99
S1(config-vlan)#name management
S1(config)#vlan 10
S1(config-vlan)#name faculty-staff
S1(config)#vlan 20
S1(config-vlan)#name students
S1(config)#vlan 30
S1(config-vlan)#name guest
S1(config-vlan)#end

Verify that the VLANs have been created on S1 with the show vlan brief command.

Step 5. Verify that the VLANs created on S1 have been distributed to S2 and S3.

Use the show vlan brief command on S2 and S3 to verify that all four VLANs have
been distributed to the client switches.
S2#show vlan brief

VLAN Name Status Ports

---- -------------------------------- --------- -----------------------------
1 default active Fa0/1, Fa0/2, Fa0/4, Fa0/5
Fa0/6, Fa0/7, Fa0/8, Fa0/9
Fa0/10, Fa0/11, Fa0/12,Fa0/13
Fa0/14, Fa0/15, Fa0/16,Fa0/17
Fa0/18, Fa0/19, Fa0/20,Fa0/21
Fa0/22, Fa0/23, Fa0/24, Gi0/1
Gi0/2
10 faculty/staff active
20 students active
30 guest active
99 management active

S3#show vlan brief

VLAN Name Status Ports

---- -------------------------------- --------- -----------------------------
--
1 default active Fa0/5, Fa0/6, Fa0/7, Fa0/8
Fa0/9, Fa0/10, Fa0/11, Fa0/12
Fa0/13, Fa0/14, Fa0/15,
Fa0/16
Fa0/17, Fa0/18, Fa0/19,
Fa0/20
Fa0/21, Fa0/22, Fa0/23,
Fa0/24
Gig1/1, Gig1/2
10 faculty-staff active
20 students active
30 guest active
99 management active
1002 fddi-default active
1003 token-ring-default active
1004 fddinet-default active
1005 trnet-default active

Step 6. Configure the management interface address on all three switches.

S1(config)#interface vlan99
S1(config-if)#ip address [Link] [Link]

S2(config)#interface vlan99
S2(config-if)#ip address [Link] [Link]

S3(config)#interface vlan99
S3(config-if)#ip address [Link] [Link]

Verify that the switches are correctly configured by pinging between them. From S1,
ping the management interface on S2 and S3. From S2, ping the management
interface on S3.

Were the pings successful? If not, troubleshoot the switch configurations and try
again.

Step 7. Assign switch ports to VLANs on S2.

Port assignments are listed in the table at the beginning of the activity. However, since
Packet Tracer 4.11 does not support the interface range command, only assign the
first port from each range.
S2(config)#interface fa0/6
S2(config-if)#switchport access vlan 30
S2(config-if)#interface fa0/11
S2(config-if)#switchport access vlan 10
S2(config-if)#interface fa0/18
S2(config-if)#switchport access vlan 20
S2(config-if)#end
S2#copy running-config startup-config
Destination filename [startup-config]? [enter]
Building configuration...
[OK]
S2#

Step 8. Check connectivity between VLANs.

Open the Command Prompt on the three PCs.

 Ping from PC1 to PC2 ([Link])

 Ping from PC2 to PC3 ([Link])
 Ping from PC3 to PC1 ([Link])

Are the pings successful?

If not, why do these pings fail?

Task 4: Configure the Router and the Remote Server LAN

Step 1. Create a basic configuration on the router.

 Configure the router with hostname R1.

 Disable DNS lookup.
 Configure an EXEC mode password of class.
 Configure a password of cisco for console connections.
 Configure a password of cisco for vty connections.

Step 2. Configure the trunking interface on R1.

You have demonstrated that connectivity between VLANs requires routing at the
network layer, exactly like connectivity between any two remote networks. There are
a couple of options for configuring routing between VLANs.

The first is something of a brute force approach. An L3 device, either a router or a

Layer 3 capable switch, is connected to a LAN switch with multiple connections--a
separate connection for each VLAN that requires inter-VLAN connectivity. Each of
the switch ports used by the L3 device are configured in a different VLAN on the
switch. After IP addresses are assigned to the interfaces on the L3 device, the routing
table has directly connected routes for all VLANs, and inter-VLAN routing is
enabled. The limitations to this approach are the lack of sufficient Fast Ethernet ports
on routers, under-utilization of ports on L3 switches and routers, and excessive wiring
and manual configuration. The topology used in this lab does not use this approach.

An alternative approach is to create one or more Fast Ethernet connections between

the L3 device (the router) and the distribution layer switch, and to configure these
connections as dot1q trunks. This allows all inter-VLAN traffic to be carried to and
from the routing device on a single trunk. However, it requires that the L3 interface be
configured with multiple IP addresses. This can be done by creating virtual interfaces,
called subinterfaces, on one of the router Fast Ethernet ports and configuring them to
bedot1q aware.

Using the subinterface configuration approach requires these steps:

 Enter subinterface configuration mode

 Establish trunking encapsulation
 Associate a VLAN with the subinterface
 Assign an IP address from the VLAN to the subinterface

The commands are as follows:

R1(config)#interface fastethernet 0/0
R1(config-if)#no shutdown
R1(config-if)#interface fastethernet 0/0.1
R1(config-subif)#encapsulation dot1q 1
R1(config-subif)#ip address [Link] [Link]
R1(config-if)#interface fastethernet 0/0.10
R1(config-subif)#encapsulation dot1q 10
R1(config-subif)#ip address [Link] [Link]
R1(config-if)#interface fastethernet 0/0.20
R1(config-subif)#encapsulation dot1q 20
R1(config-subif)#ip address [Link] [Link]
R1(config-if)#interface fastethernet 0/0.30
R1(config-subif)#encapsulation dot1q 30
R1(config-subif)#ip address [Link] [Link]
R1(config-if)#interface fastethernet 0/0.99
R1(config-subif)#encapsulation dot1q 99 native
R1(config-subif)#ip address [Link] [Link]

Note the following points in this configuration:

 The physical interface is enabled using the no shutdown command, because

router interfaces are down by default. The subinterface will then be up by
default.
 The subinterface can use any number that can be described with 32 bits, but it
is good practice to assign the number of the VLAN as the interface number, as
has been done here.
  The native VLAN is specified on the L3 device so that it is consistent with the
switches. Otherwise, VLAN 1 is native by default, and there is no
communication between the router and the management VLAN on the
switches.

Step 3. Configure the server LAN interface on R1.

R1(config)#interface FastEthernet0/1
R1(config-if)#ip address [Link] [Link]
R1(config-if)#description server interface
R1(config-if)#no shutdown
R1(config-if)#end

There are now six networks configured. Verify that you can route packets to all six by
checking the routing table on R1.
R1#show ip route
<output omitted>

Gateway of last resort is not set

[Link]/24 is subnetted, 6 subnets

C [Link] is directly connected, FastEthernet0/0.1
C [Link] is directly connected, FastEthernet0/0.10
C [Link] is directly connected, FastEthernet0/0.20
C [Link] is directly connected, FastEthernet0/0.30
C [Link] is directly connected, FastEthernet0/1
C [Link] is directly connected, FastEthernet0/0.99

If your routing table does not show all six networks, troubleshoot your configuration
and resolve the problem before proceeding.

Step 4. Verify Inter-VLAN routing.

From PC1, verify that you can ping the remote server ([Link]) and the other
two hosts ([Link] and [Link]). It may take a couple of pings before the
end-to-end path is established.

These pings should be successful. If not, troubleshoot your configuration. Check to

make sure that the default gateways have been set on all PCs and all switches.

Task 5: Reflection

In Task 4, you configured VLAN 99 as the native VLAN in the router Fa0/0.99
interface configuration. Why would packets from the router or hosts fail when trying
to reach the switch management interfaces if the native VLAN were left in default?