Lab 9‐1: Build a Network Challenge - AidanP017/Aidan-NET-330 GitHub Wiki
Purpose
In this lab, we used Cisco Packet Tracer to configure part of a workspace including the Foster 202 Company Network, interfaces, VLANs, and OSPF routing.
Assignments
The following table was used for assigning IPs in the Foster network.
| Network Name | Network Address | Default Gateway |
|---|---|---|
| BTV-MTL Link | 172.16.0.0/30 | 172.16.0.1 |
| BTV Users | 172.16.5.0/24 | 172.16.5.1 |
| BTV Data Center | 172.16.6.0/24 | 172.16.6.1 |
| BTV Core | 172.16.10.0/24 | 172.16.10.1 |
| MTL Network | 172.16.20.0/24 | 172.16.20.1 |
BTV Router Configuration
First, we configured the routers in the network starting with the BTV Router.
Starting with the configuration of FastEthernet0/1, which was configured for the BTV Core network.
Then with the configuration of Serial0/1/0, which was configured for the BTV-MTL Link network.
Lastly, we configured OSPF routing for the two configured networks.
MTL Router Configuration
Next, we configured the MTL Router in a similar manner.
This time, OSPF routing was set up for the MTL network as well as the BTV-MTL Link network.
BTV-Dist-Multi-Layer Switch Configuration
The last network device configured was the BTV-Dist-Multi-Layer Switch, which would also be used to host VLANs.
VLANs 5, 6, and 10 were created in relation to the networks in the table.
FastEthernet0/2 and 0/6 were assigned as access ports for VLANs 5 and 6, respectively.
FastEthernet0/1 was assigned as an access port for VLAN 10 to connect to the BTV-Router.
OSPF routing was also configured for the networks in the VLANs. Running the command sh run should show its existence.
Troubleshooting
After attempting to establish connectivity between the User and Montreal laptops, I had to double check my configurations to make sure they were correct.
The first thing that I noticed was that 172.16.10.1 was configured on FastEthernet0/1 instead of 0/0, the former of which is for a port on a separate network. So I fixed the configuration.
I also found that the IP address on VLAN 10 was configured as the default gateway for the network (172.16.10.1) instead of being a separate IP. I changed it to 172.16.10.2 to avoid confusion.
Lastly, I found that specifying VLAN 1 to be configured for the Montreal network (172.16.20.1) was not necessary and likely confusing the Burlington multi-layer switch for where to send packets. I removed the IP address configured for this VLAN.
Then I rebooted all of the routers and switches into the workspace to ensure that the OSPF routing tables were fresh and updated.
Connectivity Testing
From there, it should now have been possible to ping between the User and Montreal laptops.
In addition, running the command
sh ip route on the Burlington and Montreal routers should output appropriate results.
I also ran this command on the Burlington multi-layer switch for further verification.