Subnet Design - tmansfield42/Tech-Journal GitHub Wiki

Subnet Design 1/30/25

This lab covers creating subnets for a network, adding vlans to switch's vlan database and routing between core switches though CLI.


Step 1: First you need to create a subnet for a network with the following vlans:

1 Management 250      
100 FacStaff 200      
110 Student 450      
130 StuLab1 35      
140 StuLab2 35      
200 StuWireless 900      
210 FSWireless 650

For my network, it looked like this:

VLAN VLAN_NAME Hosts Needed Network Netmask Router Address
200 StuWireless 900 10.9.0.0/22 255.255.252.0 10.9.0.1
210 FSWireless 650 10.9.4.0/22 255.255.252.0 10.9.4.1
110 Student 450 10.9.8.0/23 255.255.254.0 10.9.8.1
1 Management 250 10.9.10.0/24 255.255.255.0 10.9.10.1
100 FacStaff 200 10.9.11.0/24 255.255.255.0 10.9.11.1
130 StuLab1 35 10.9.12.0/26 255.255.255.192 10.9.12.1/26
140 StuLab2 35 10.9.12.64/26 255.255.255.192 10.9.12.65/26

Step 2: On all switches, add vlans 100 and 110. Switches that have Lab PCs along with core switches should have 100, 110, 130 and 140 in their vlan database.

Step 3: Assign IP addresses to the clients (PCs and Laptops) with the correct default gateway (router) as per the 2nd subnet sheet above.

Step 4: All clients should be connected to the switches through copper wire cables, all switches connect through cross-over cables. Connect the two core switches using the gigabit interface.

Step 5: For the Fa0/x ports on the switches, they should be on trunk so that way the switches can communicate across vlans.

Step 6: In order to enable routing between the two core switches, go into their CLI and type these commands:

ip routing

interface vlan 100

ip address 10.9.11.1 255.255.255.0

After typing these commands, redo until you're finished with all vlans (interface vlan 110, interface vlan 130, etc.) IP address and subnet mask will change per vlan, reference the subnet sheet above.

⚠️ **GitHub.com Fallback** ⚠️