1. Preamble
This Case Study provides an opportunity for students to practice their network design, implementation and troubleshooting skills gained mainly from studying the subject LANs and Routing.
The Case Study is organised in a way to assist groups complete the whole project progressively so that it can benefit students’ learning experience. The Scenario describes your project in general terms and explains why the network is to be built. After that, the Case Study is
oken into a number of tasks, each having detailed requirements guiding your group through several steps.
Completing this Case Study properly is not a trivial task. It is important that you read and understand each requirement and complete tasks on a weekly basis as your study progresses.
2. Assessment
IPv4 Addressing Milestone Submission (group submission, 20%)
Each group as a team is required to submit their IPv4 subnetting and addressing scheme, i.e., Tables A1, B and C on Page 9 of this book, to your lab instructor in a hardcopy at your Week 5 class. Feedback will be given in the following class.
3. Scenario
This Case Study presents a scenario in which a training organisation, the Arcadia Institute of Technology (AIT), has recently taken the ownership of another training centre and relocated its main site to the centre of the city, and hence wishes to re-design and implement its whole network. The AIT group has hired your group as their ICT consultants to design and implement a new network for them. The solution will be evaluated by a demonstration of a prototype network using Packet Tracer.
The network that the AIT Group is implementing is dual stack, composed of various networks. A partial logical Topology Diagram has been provided (see Fig. 1). The task is to design and implement the networks at the four sites (including the ISP). The AIT Group would like to see a prototype of the network built, before it is fully implemented, to verify that it will meet the AIT Group’s needs.
Fig. 1. Basic network topology
The AIT which you are required to design a network for has locations in two campuses. On the City Campus there are three major sites distributed in the Main building, West Tower, and East Tower respectively. The Branch Campus is located in a subu
and will be connected via leased line serial connection because of the cost consideration.
The West Tower site is mainly for the AIT Teaching and Learning division. All user groups will each have employees located in two adjoining buildings, i.e., Thomas Street and Jones Street. Due to the size and complexity of LANs, the company wants to create VLANs to control
oadcasts, enhance security and logically organise user groups because these VLANs are essential for the organisation’s operations.
The Main Building site has two exit links for access to the Internet and external services. Main Building connects to the West Tower and East Tower sites using Leased Line serial connections.
The East Tower site houses the AIT’s private Backup sites, and intranet services, used by external and internal users from AIT.
A private MetroEthernet service (simulated by FastEthernet) is purchased for connecting the sites on West Tower and East Tower.
AIT has previously used RIP version 2 in the Branch Campus site and wishes to continue using it for now. AIT also wants to use private IPv4 addresses for the entire IPv4 network. NAT for IPv4 will be implemented on Main router for all traffic leaving the company’s network.
Although private addresses will be used, the company appreciates efficiency and address conservation in their design. To minimise wasted address spaces, they have requested CIDR and hierarchical VLSM to be used whenever appropriate.
IPv6 has been considered and at this stage, dual-stacking will be implemented everywhere to support both IPv4 and IPv6.
4. Objectives and General Assessment Criteria
Objectives
· Design hierarchical IPv4 and IPv6 addressing schemes to meet addressing requirements.
· Configure RIP with simple route redistribution for IPv4
· Configure static, default static, summary static routing and floating static routing for IPv6.
· Configure floating static default routes for conditional redundancy at the ISP.
· Configure switching networks for management, VLANs and 802.1q trunking.
· Implement dynamic and static Network Address Translation (NAT) for IPv4.
· Design and implement standard Access Control Lists (ACLs) to restrict SSH access and for NAT Implementation.
· Verify the functionality and troubleshoot the network when necessary.
General Assessment Criteria
· Requirements met.
· Co
ectness of implementation.
· Functionality of the design.
32524 LANs and Routing 2018 Spring Case Study
The task shown at next page
Page 1 of 1
Task One: Addressing the Network
The ISP links:
The ISP has allocated XXXXXXXXXX/29, which needs to be subnetted into two /30 address spaces, for being used on the two ISP links.
For IPv6, 2001:50:80:120::/64 and 2001:50:80:121::/64 are used to address the two ISP links.
The Internal Network:
As part of the network redesign, the AIT has allocated XXXXXXXXXX/19 and 2001:DB8:CA5E::/52 for addressing the internal network.
The expected numbers of users for each of the user groups (each on its unique IP network) are:
For the West switching network (this will be implemented in VLANs):
· 1000 hosts for the Students
· 120 host for Academic Staff
· 55 hosts for Support Staff
On the East site:
· 30 hosts on the Server Farm LAN.
On the Branch Campus site:
· 250 hosts in the Students (as shown in Appendix: Partial Topology Diagram)
· 500 hosts in a spare LAN for the life of the design (simulating with a loopback interface)
The AIT requires that:
· The use of hierarchical VLSM design to maximise the use of IPv4 addresses, and account for CIDR and route aggregation between the main sites.
· All networking devices (including switches) must have IPv4 addresses and the PC hosts’ gateways will use the first usable address in each subnet.
· The ISP links will be allocated a subnet mask of /30 for IPv4 and a prefix of /64 for IPv6.
· All IPv6 addressed networks will have a network prefix of /64.
· The Management/Native VLAN for the switching network at the West site will have two extra hosts for potential administration usage (this subnet will need to have four host addresses).
· The network administrator host will have the last usable address on the Management/Native VLAN subnet at the West site.
At this stage, the AIT agrees that it is enough to assign all hosts with an IP address statically.
Submission: Tables A1, B and C
1) IPv4 Network subnetting tables A1, which show possible subnets that meet the design requirements; Subnets that are not used are to be clearly identified in each table.
2) Detailed IPv4 addressing tables (Tables B and C) showing all networking devices’ names and interface details.
Please fill in the tables below.
Table A1 - IPv4 Subnetting Table
Subnet Numbe
Subnet Address
Subnet Mask
Hosts Required
Maximum Hosts in Subnet
In Use
(Yes or No)
Network Name
Table A2 IPv6 Subnetting Table
Subnet Numbe
Subnet Address
Subnet Mask
Hosts Required
Maximum Hosts in Subnet
In Use
(Yes or No)
Network Name
Table B Device Interface IP Addressing Table
Device
Interface
IPv4 address
Subnet Mask
IPv6 Address/Prefix Length
ISP
GLEBE_SW
Management (& Native) VLAN
N/A
Table C Host Addressing Table
Host
IPv4 Address
Gateway
Subnet Mask
IPv6 Address/Prefix Length
Table D Switch Table
Switch Name: Switch Management IP Address: Location:
Interface type & Port Numbe
Description of Purpose
Port Bandwidth
Network Name
Subnet Address
Subnet Mask
VLAN
ID & Name
Switch Port Mode
Layer 2 Encapsulation
Table E VLAN Table
Switch Name
Number of Ports
Location
IP Address
Gateway
VLAN ID & Name
Page 4 of 7
Page 6 of 7