om

Free Lab Friday

l.c
Implementing
IP Addressing Schemes
ba
(Subnetting Exercise)
om
db
vi
da
Free Lab Friday – Part 6 Implementing IP Addressing Schemes.

Packet Tracer File: Free Lab Friday – Implementing IP Addressing Schemes.pkt

Access Credentials:
User Exec: cisco
Privilege Exec: cisco

Tyrell Corporation’s Network troubleshooting training sessions have assisted the onsite IT

om
team with greater understanding of the enterprise network design. The network had been
functioning well since the implementation of the Layer 2 features and the completion of the
First Hop Redundancy Protocol - HSRP.
In this challenge, you are tasked with designing and implementing an IP Addressing scheme
in the Distribution and Core network areas to establish a scalable, fast converging design.

l.c
The IP Addressing design will utilise the 10.2.0.0/24 and 10.3.0.0/ 24 IP address space
initially.
The Distribution to Core and Core to Data Centre Switch addressing will use the 10.2.0.0/24
ba
space, while the Data Centre server network will use the 10.3.103.0/24 space in VLAN 103.
The Data Centre Server network requires enough space to hold a potential 60 client devices
on the Network. The network will use the 2nd available IP Subnet from the allocated
om

addressing space, as the first subnet has provisionally been allocated for another Server
LAN in planning. The Server network devices should have a gateway configured to be the
first available IP Address within the range of the newly created scope.
You must ensure that the DCSW1 device has connectivity with all Servers in the new Data
Centre network after completion of the tasks. The ports facing the Servers should be
db

configured as access VLANS.

Distribution to Core and Core to DCSW1 networks will utilise the 10.2.0.0 /24 IP space:
All links between Core and Distribution switches and the Core and Data Centre switch are to
vi

routed links. All potential routed links are disabled. Layer 3 EtherChannels are to be created
between DSW1-DSW2, CSW1-CSW2, CSW1-DCSW1 and CSW2-DCSW1 where dual links
da

exist in the topology using standards based protocols. All switches should actively attempt to
create the EtherChannels.
EtherChannels are to be numbered in the following way:
Switch Channel No. Switch Channel No.
1. 1DSW1 3 1DSW2 3
2. 1CSW1 3 1CSW2 3
3. 1CSW1 1 DCSW1 1
4. 1CSW2 2 DCSW1 2
Subnets created within the 10.2.0.0/24 range should minimise any wastage of address
space on the point-to-point links between the switches.
The following point should be noted when implementing the IP Addressing scheme
5. 1DSW1 – 1DSW2 link = 1st available subnet
1DSW1 should have the lowest address assigned.
6. 1DSW1 – 1CSW1 link = 2nd available subnet
7. 1DSW1 – 1CSW2 link = 3rd available subnet
CSW switches should have the lowest address assigned.
8. 1DSW2 – 1CSW2 link = 4th available subnet
9. 1DSW2 – 1CSW1 link = 5th available subnet
CSW switches should have the lowest address assigned.
10. 1CSW1 – 1CSW2 link = 6th available subnet
CSW1 switches should have the lowest address assigned.
11. 1CSW1 – DCSW1 link = 7th available subnet

om
12. 1CSW2 – DCSW1 link = 8th available subnet
CSW switches should have the lowest address assigned.
When you have completed the tasks, you will be able to compare your configurations with
the completed switch configuration files in the zip file download. Packet Tracer did not
save the channel-group commands on reload of the Switches where EtherChannels were

l.c
configured. Therefore, an assessment file exam could not be created to score this lab on.
In each of the completed switch configs.txt files there are:
ba
1. Completed config files
2. Verification ping tests for directly connected devices
3. Verification tests for the EtherChannels
4. Verification tests for the IP addressing on interfaces.
om

Good luck!
db
vi
da