3. path selection and loop-free topology according to a given
network design meeting
enterprise requirements.
LO5 Evaluate common network security and performance issues
and identify the tools
needed to control the path
INSTRUCTIONS
These instructions apply to the Project
Group Project (Weightage 20%) – The submissions should be
uploaded on the LMS by Session 12
This Project will focus on student’s ability to implement an
enterprise level network that runs multiple
routing protocols. The project should be conducted as a group
task by a group of 4 students. Upon the
implementation of the network, students should produce a
comprehensive report, which includes
screenshots of configuration of routers and other nodes, and
brief explanation of the screenshots.
Students should implement the network based on the given
scenario in a virtual environment using
GNS3. Please make sure to name the devices with the group
name.
If any third-party content is used. The citation of sources is
mandatory and should follow IEEE style.
8. routing process running in Router 1
ii. Re-distribute routes in XYZ Pty Ltd network into OSPF
routing process running in Router 1
Task 3: Configure BGP in the network
i. Configure eBGP Peering between Router 1 and ISP router
ii. Configure iBGP Peering between Router 1 and Router 2
Task 4: Securing routing table with Filtering Ingress Routes
i. Configure Ingress Filtering in ISP router
What to Submit.
During Session 3, students should present the member list and
one A4 page proposal on how they
would plan and implement the network.
During Session 5, students should demonstrate the initial
topology implementation on gns3 and
connectivity among the local sites. The configuration of Interior
Gateway Protocols is optional at this
stage.
During Session 10, students should demonstrate the
configuration of Interior Gateway Protocol and
connectivity between the two sites. Route re-distribution should
be configured for Interior Gateway
10. the final grade.
Task Decryption Marks
The Proposal 10
Proposal Layout
The proposal style, language and structure should be
appropriate.
The proposal should be written in A4 page (Except the cover
page)
The proposal must contain
i. Cover page with Unit Code, Group Name, Unit Name
and Student IDs
ii. Requirement
iii. Proposed
Solution
iv. Step Involved
v. Potential Obstacles
Final Report 60
11. Report Layout The report style, language and structure should
be
appropriate. All screenshots and descriptions need to be
compiled and in a single final report and any given suggestions
need to be incorporated.
The report must contain
i. Cover page with Unit Code, Group Name, Unit Name
and Student IDs
ii. Table of Contents
iii. Introduction
iv. Technical Discussion
v. Critical Analysis
vi. Conclusion
4
Introduction The students should include purpose of the report,
sections
covered which should convince the reader that the report is
worth reading. Word count limit – 125 words
12. 4
Technical
Discussion
This section should include the configurations done in the
virtualized network environment. You should break down this
section into four tasks and include at least 7 screen shots from
each of these tasks and a brief description
i. Successful configuration of task 1
ii. Successful configuration of task 2
iii. Successful configuration of task 3
iv. Successful configuration of task 4
14. iii. Compare and contrast OSPF vs EIGRP
iv. Analyse the configuration of passive interface
command in OSPF and EIGRP assure a secured network
v. Analyse the filtering of ingress router updates with
Route Maps, increase the security in the providers
network
vi. Evaluate WAN connection methods available for
connecting two sites
35
Conclusion Summarize your findings. Word count limit – 125
words
4
References Should follow IEEE style 3
15. Demonstrations 30
In class
demonstration
during Lesson 5
You are required to demonstrate in class
i. Initial topology implementation on gns3
ii. Connectivity among the local sites
10
In class
demonstration
during Lesson 9
You are required to demonstrate in class
i. The configuration of Interior Gateway Protocol
ii. Connectivity between the Melbourne and Sydney sites
iii. Route re-distribution should be configured for IGP