0% found this document useful (0 votes)
24 views3 pages

CS3211 Network Design Assignment 2

CS310 Assignment 2

Uploaded by

sanil.prasad
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
24 views3 pages

CS3211 Network Design Assignment 2

CS310 Assignment 2

Uploaded by

sanil.prasad
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

CS310 Assignment 2: Network Design and Configuration

Weight: 15%
Group work: You may choose to work in groups of no more than 4 members
Submission: GNS3 project file complete with all startup config scripts.

In this assignment you will be designing and configuring a network for a university
environment, which has been allocated [Link]/16 IP address space. There are two
faculties namely Faculty of Arts and Faculty of Science. Each faculty has two subnets;
staff subnet and student subnet.

Part 1
Divide the allocated address space between faculty subnets such that the staff subnet in
each faculty gets 256 IP addresses and the student subnet in each faculty gets 512 IP
addresses (inclusive of network and broadcast address). In other words each faculty gets
256 + 512 = 768 IP addresses. Be sure to avoid addressing conflicts with other existing
subnets such as subnet linking routers (Fig. 1)

Part 2
Construct the following network topology in GNS3 simulator. Ensure that all the
hostnames and network addresses are well labeled. Use Cisco 3725 routers.

Fig. 1. Network design


Part 3

Configure all the routers using the assigned hostnames and IP address. Configure the routers to
use RIP to automatically update the routing tables.
You should be able to ping the Default_Gateway from Router02 and Router03.
[Hint Use RIP version 2 with no auto-summary]

Part 4

Setup Virtual PC (VPC) in each of the three subnets as shown above. The virtual PC’s provide
lightweight PC environment to execute tools such as ping, and trace route.
Each VPC should be able to ping the others.

Part 5

The staff subnet in each faculty will be hosting services meant for access by university staff
only. Configure the access control list (ACL) on Router02 and Router03 such that any traffic
from the student subnets are blocked from entering the staff subnets. Traffic to and from other
subnets should pass through.

Pinging FA1 (VPC in the Faculty of Arts staff subnet) from FAS1 (VPC in the Faculty of Arts
student subnet) should fail. Likewise pinging FS1 (VPC in the Faculty of Science staff subnet)
from FAS1 (VPC in the Faculty of Arts student subnet) should fail.
On the other hand you should succeed in pinging the Default_Gateway from any PC on any
subnet.

Execute trace route (tracert [Link]) command on FA1 and FSS1. Paste the results next to
the respective subnet on your network topology

Part 6

Configure DHCP services on Router02 and Router03 such that the all VPCs can get IP
addresses dynamically assigned.
Part 7
Use the following checklist to ensure you network is configured correctly.

Test ✔
Router02 can ping Router01
Router03 can ping Router01
Router02 can ping Default_Gateway
Router03 can ping Default_Gateway
FAS1 cannot ping FA1
FAS1 cannot ping FS1
FSS1 cannot ping FS1
FSS1 cannot ping FA1
FAS1 can ping FSS1
FSS1 can ping FAS1
FA1 can ping FS1
FS1 can ping FA1
FA1 can ping Default_Gateway
FAS1 can ping Default_Gateway
FS1 can ping Default_Gateway
FSS1 can ping Default_Gateway

For each of your routers make sure to save your running configuration using the command
write mem
For the VPCs use the save filename command to save the configurations to a file.
Finally save the GNS3 project, i.e. the topology together with the startup configs.
Export the complete GNS3 project, and submit it on moodle. Only one submission is necessary
from each group. Make sure your submission is complete and has all the necessary files to run
the simulation.

Common questions

Powered by AI

Network testing procedures must include checking connectivity using ping tests between routers and subnets, ensuring ACLs function as intended by verifying blocked and allowed traffic, as specified. Additionally, DHCP functionality should be tested by ensuring dynamic IP allocation on all VPCs. Successfully completing these tests ensures the network meets the assignment's specifications and functions reliably according to the checklist.

Using ACLs to block student subnet traffic to staff subnets ensures network security by restricting access to sensitive resources. This control prevents instances of unauthorized access to staff services by effectively segmenting traffic between subnets. Additionally, it creates a controlled environment where only designated traffic can flow, allowing for better management of network policies.

Saving the running configurations on routers and VPCs is critical because unsaved changes are lost upon shutdown or reboot, leading to potential configuration discrepancies across sessions. This impacts project submission because an incomplete or incorrect configuration would fail to demonstrate the assignment's requirements, affecting the assessment outcome. Therefore, saving ensures consistency and allows submissions to accurately represent the functioning network.

To allocate the IP addresses without conflicts, each faculty must receive 768 IP addresses, composed of a 256-address staff subnet and a 512-address student subnet. This allocation must avoid overlap with existing subnets, particularly those linking routers. For efficient allocation, subnetting techniques should be used to achieve the needed addresses while ensuring no IP range overlaps with other technical infrastructure.

Clear and well-labeled network documentation is critical for correct implementation and troubleshooting. In the assignment, proper labeling assists in configuring devices accurately, ensuring subnets are correctly identified, and supporting the identification of routing paths and ACL rules. This accuracy is essential for effective communication among network engineers and for maintaining the network over time.

Strategic measures for successful group collaboration include clear delegation of tasks to match strengths and areas of expertise, regularly scheduled meetings to review progress and solve issues, and using collaborative tools for version control of configuration files. Establishing channels for open communication and resolving conflicts promptly helps maintain team cohesion, ensuring efficient progression towards completing the project objectives.

Challenges in segmenting the network may include IP address conflicts, incorrect ACL configurations leading to unwanted traffic flow, and complexity in routing due to increased routes. These can be mitigated by carefully planning the IP addressing scheme, testing and verifying ACLs, and using routing protocols efficiently to manage routes. Proper documentation and using network simulation tools to preview the configuration before deployment also help mitigate potential issues.

GNS3 allows for the simulation of complex network topologies by modeling real-world network devices and configurations. In this assignment, constructing the topology in GNS3 involves setting up all prescribed connections, appropriately labeling hostnames and network addresses, and configuring devices to emulate desired behaviors, such as routing and ACLs. Testing involves running diagnostic tools like ping and traceroute to verify connectivity and configuration function according to requirements.

RIP version 2 can be configured on each router to automatically update routing tables by enabling RIP with the appropriate network statements for each subnet. Ensuring 'no auto-summary' is set prevents summarization that could lead to improper routing updates. Each router's RIP configuration should include network statements that match the subnets local to each router, facilitating the correct propagation of routing information.

Configuring DHCP on routers streamlines network management by automating the assignment of IP addresses to VPCs. This eliminates the need for manual configuration of each host, reducing the likelihood of configuration errors and ensuring that the IP addresses are efficiently used. DHCP configuration facilitates scalability and simplifies network management in environments with a high number of connected devices.

You might also like