CSC8600

Advanced ICT Professional Project

University network design and implementation

Final Project Report

Version No.: 1.1

Document ID: 2

June 2, 2018

Team Name: GigaBytes

Team Members:

Ankitkumar Patel (U1091133)

Bold-erdene Lkhagvasuren(U1092857)

Ragetha Rajasekharan nair(U1088242)

Aditya reddy banapuram(U1090669)

Supervisor: Dr. Ron Addie

Final Project Report Version 1.1

Version History

Version Change Date

1.1 Final copy 2/06/2018

Contents
01 Executive Summary 4

GigaBytes Page 2
Final Project Report Version 1.1
2 Methodology Report 6
2.1 Methodology Statement 6
2.2 Justifications 7
2.3 Discussions 7
3 Technology Report 8
3.1 Technology Statement 8
Tools used in planning and designing phase 8
Tools used in implementation 8
Devices used in Project 8
Protocols and technology used in project 9
3.2 Justifications 9
3.3 Discussions 12
4 Project Report 13
4.1 Project Outcome 13
4.2 Cost of the Project 28
4.2.2 Labor cost 31
4.2.3 Comment on actual cost and estimated cost 32
4.2.4 Comment on what we have learnt about project cost estimation 32
5 Team Management Report 33
5.1 Team Organization 33
5.2 Team structure and roles 33
5.3 Team management 35
Problems encountered 35
Important strategies to adopt in future and essential points we learned 35
5.4 Other team-work related issues 36
6 Communication report 36
6.1 Communication and meetings 36
6.2 Documentation 38
6.3 Other Discussions 39
7 Contribution Distribution 39
8 Conclusion 41
References 42
Appendix A 43

GigaBytes Page 3
Final Project Report Version 1.1
Appendix B 45
Appendix C 46
Appendix D 47
Appendix E 48
Appendix F 66

01 Executive Summary
Network is very important for daily communication Every organization requires network to
communicate. In our project, university is our client who requires network to be setup. The cabling
part is already done in the buildings for the network to join. So, our task is to find out particular
devices and join them together with using some advanced protocol that makes network very
secure and it should have load balancing and backup plan for every devices so network cannot
go down at any time. So, we made the project plan and we divided the tasks to each team
members, appendix D refers to the tasks assigned to each team members. This project is created
in packet tracer as simulation. So, we attached some of the screenshot from simulation in outcome
and we made design in draw.io as well which is only the pictorial representation of network part.

GigaBytes Page 4
Final Project Report Version 1.1
Some of the figures generated from draw.io is included in this project. We have attached the
meeting minutes in appendix E and activity log sheets of all team members in appendix F. Refer
Appendix A for all abbreviation used in this report. This report will cover methodology report,
technology report, project outcome, cost of the project, team management report, communication
report and contribution report for each member. Appendixes are used to refer detailed information.

GigaBytes Page 5
Final Project Report Version 1.1

2 Methodology Report

2.1 Methodology Statement

In this project we used different methodology to finish. We did not use only one particular
methodology. We started with waterfall but sooner shifted to agile development model. At some
point we used some of the other methodology as well such as scrum and sprint with the agile.
The figure 1 shows the methodology with respect to our project.

Figure 1: Methodology used in this project

GigaBytes Page 6
Final Project Report Version 1.1
2.2 Justifications

Our project is concerned with network design and implementation. We cannot stick to particular
method such as waterfall only. Sometimes the network for one building may have dependency
with the core network which is implemented in first phase. So, if our building network topology is
not able to communicate with the core network topology, then we have to make changes in core
network topology. For that purpose, we have to go back to the work which was done in phase one
and we have to edit. Sometimes we have to change the core network, if the performance is not
achieved in layer below that network, which cannot be assumed in the starting phase. Because
sometimes theoretical concepts do not work same as in practical implementation. So, we had to
be very flexible in methodology selection. In Figure 1, you can see that some of the arrows are
going back to the previous steps, that means we had to choose agile, which gave us the flexibility
to iterate through the process for the better quality of the network.

The biggest plus point would definitely be the adaptability of the model, which gave us the free
hand to iterate and get a better output. This would also help us to examine after each stage about
the various aspects like quality, cost, etc. This approach helped us to understand the core
networks problems before being presented it to the client. The approach at each stage where we
tested for errors was beneficial.

The drawback which we observed in this model is that, irrespective of the model, a project which
is large like ours would be difficult to implement because of the complexity of the network. And
only known the design issues after implementation and testing. By which the time frame and the
money involved would go up. Which is chances of the project going side-track is high, only if we
did not give enough importance to the logical presentation of the network.

2.3 Discussions

The agile model for the project enhanced our capability to reiterate to the design phase for two
times for the quality purpose. However, the need to recheck the quality was essential in the overall
implementation of the project. The methodology of the agile model for our project was started with
the requirement collection from the client. Which is then followed by the analysis or understanding
the need for having a network. This led us to get the required tools, protocols, equipment for the
next phase which is designing.

The designing phase was very critical for our project because it needed a thorough understanding
of the concept of protocols and network and if we fail here then we would only know that after
implementation, which would make us fall behind. So, a lot of work went into designing phase,
from meeting experts, supervisors in that field to taking practical examples of the university
networks. Tools like draw.io came into the picture once again to create a design before
implementing it. Then after having our design, we started with implementing the core network

GigaBytes Page 7
Final Project Report Version 1.1
which connects all the building networks and the internet. For this purpose, we had to use packet
tracer. And after that, we built department wise networks and then tested it.

Testing phase is another crucial phase to detect errors and improve overall efficiency of the
network. While doing testing, our design issues were identified and we had to go to the drawing
board once again to improve the core network for better throughput. After rectifying the errors and
re-designing and implementing, we tested it again. This time, everything went according to the
plan and then came the very important phase of presenting the model to the client. The client was
very much satisfied with the working, design and implementation of the project. The last phase
was documentation phase, where we had to present the project in words.

Methodology in future
The agile model when implemented with SCRUM model would give better results for any project,
however, it would only be decided on the type, the importance, time and cost of the project which
you are undertaking. Said that, our team when presented with an opportunity, would suggest agile
model within a time frame. But, the most important aspect would be that after each phase we
have to check the quality, cost, time duration of the product, so as to make sure that we are not
going off the track which was set during the project plan.

3 Technology Report

3.1 Technology Statement

Tools used in planning and designing phase

1. Microsoft office: We have use Microsoft word for documentation and then we used
Microsoft Project for Project Plan (Schedule).
2. Draw.io: This tool is very good for any diagram making. It is free with Google Suite
subscription. So, all our network diagrams are made in Draw.io

Tools used in implementation

1. Packet tracer: we have used packet tracer 7.1.1 to create network part and simulated it
and then we implemented in real life.

Devices used in Project

The devices used for the practical purpose of the project have been described in the cost
estimation section because we are using packet tracer for simulation purpose and for showing
the performance of the network. The devices which are suitable for the real world have been
described with the cost in the table 5 in cost estimation section.

GigaBytes Page 8
Final Project Report Version 1.1
Protocols and technology used in project
1. OSPF (Open Shortest Path First): OSPF is dynamic routing protocol. It has three
versions (cite-Hogg 2018). We have used v2
2. HSRP (Hot Standby Router Protocol): HSRP is protocol to make redundant backup
router. It can be implemented per vlan base and it can be supported in layer 3 switches
and routers. It is cisco proprietary protocol.
3. SSH (Secure Shell): SSH is secure shell protocol that makes remote session encrypted.
4. IPSEC (Internet Protocol Security): IPSEC is the protocol to establish tunnel between
site to site or client to site via internet.
5. Frame Relay: Frame relay is the protocol that connects one site to another site via leased
lines between sites.
6. ACL (Access Control-List): ACL used to provide list of rules which can be used in router,
firewall to manage access to network.
7. NAT (Network Address Translation): NAT provides the translation for public address to
private address. So, users from outside network can use network
8. SNMP (Simple Network Management Protocol): SNMP is the protocol to monitor
network devices. It sends the trap messages to SNMP clients if any specified activity
happens in SNMP enabled device. And network monitoring staff can set some of the
values in devices such as description, contact and even shutdown the particular interface.
9. Telephony Services: This protocol enables communication between IP-phones.
10. Syslog: This technology sends specified log messages from network device to syslog
server. So, network monitoring staff can get detail of what is going on that device.
11. AAA (Authenticate, Authorize, Account): AAA is the protocol to authenticate, authorize
and account any user on network who want to login.
12. 802.11a: In simple words this is the WIFI technology that we are providing in our network.
13. STP (Spanning Tree Protocol): STP is the protocol that makes the tree from root in
network where there is a loop formed. We have used rapid pvst+ variant of STP.
14. DHCP (Dynamic Host Configuration Protocol): This protocol gives the IP to the
requested host after checking criteria specified in DHCP server.
15. DNS (Domain Name Server): This protocol translates domain name to IP address.
16. NetFlow: This technology is useful for tracking packets to any interface.

3.2 Justifications

Microsoft office is used in this project for documentation and planning purpose. Microsoft office
has products such as word, excel, project which were much useful in this project.
Microsoft word is good enough to store requirement in section wise. It is good enough to make
all communication plan and code of conduct. So, we used Microsoft word product of Microsoft
office.

GigaBytes Page 9
Final Project Report Version 1.1
We used Microsoft excel to make IP plan. Excel was right for us because we want table structure
for IP plan and our IP plan was building wise so it requires different sheets building wise in one
document so we can navigate from one sheet to another sheet easily.
We used Microsoft Project in our project for scheduling of tasks. So, we can follow tasks on daily
basis on that tool. Even we can assign persons to do that tasks. We can set milestone and we
can generate different report from that such as cost, hours taken by different task. We can
generate critical path. So, this tool is very popular and met our requirement so we used Microsoft
Project in our project. Overall other reason for using Microsoft product is that we had full
subscription of whole packages. So, we can save cost of licenses.

Packet Tracer: We used packet tracer to simulate part of network first in it before implementing
it. Packet tracer has capacity that we can use same command in it which we supposed to use in
real device and other advantage is that we can use config files from simulation to real device so
we do not need to configure real device. Just we need to put that config file and run device.
OSPF: We used OSPF protocol for routing with version 2 because OSPF is open standard. So,
it is universal protocol. So, every device can support. Other thing why we used version 2
because we want to take advantage of multiarea feature. Multi areas are supported in version 2
so it limits the LSA flood. In simple words we can save bandwidth (En.wikipedia.org 2018)

HSRP: We have used HSRP protocol which is cisco proprietary. This protocol we used because
we want to have back up router to function if primary router goes down (Tools.ietf.org 2018)

SSH: We used SSH for secure remote session to network devices such as router, switches and
firewall. We had other option to use telnet but telnet does everything in plain text so it is not
secure.
IPSEC: We used IPSEC in our project because it is the tunneling protocol with security. Other
alternative is available such as GRE but that does every communication in plain text. So, we
chose IPSEC for security purpose to make tunnel between sites. In simple words we can say
secure VPN (Virtual private network) between sites

Frame Relay: We used frame relay in project because we want to have back up site to site
VPN if primary VPN goes down. Primary VPN is running on internet with IPSEC protocol.
Internet can go down if they have problem in ISP network so we providing leased line other
connection between site to site with frame relay so staff cannot feel cut over if primary VPN
goes down.

ACL: We used ACL in this project because we want to control access on every subnets i.e.
students should not have access to private servers of finance, marketing or HR department.
Students should not have access to subnets of IP camera, IP-phone, or any other security
subnets such as door swipe subnets. ACL is very good protocol which filters access from one
subnet to other.

NAT: We used NAT protocol in our project because we want to have access to the public
servers of university from outside. So, we are translating public address of servers to the private

GigaBytes Page 10
Final Project Report Version 1.1
address i.e. 58.179.1.196 is translated with 10.100.60.10. So, whenever someone requests
58.179.1.196, its request will be translated to private address 10.100.60.10. This NAT example
is real which we used in our project.

SNMP: We used SNMP protocol in this project because we want to give flexibility to monitoring
staff that they can manage all devices from one monitoring room. They can shut down any
interface on device from SNMP client. We enabled SNMP on all devices so all devices can be
managed remotely. Other advantage is that SNMP is configured to send trap messages as well,
which will send information about the specified event which happens on network device to
SNMP receiver and monitoring staff can alerted.

Telephony services: We are using telephony services on Call Manager Express(CME) server.
So, whenever IP-phones boots up they will go to the CME to get IP and line number. Once it
gets line number it can call other phone by line number.

Syslog: We are using syslog protocol on network devices. So, they all can send all the logging
messages to one syslog receiver. That log messages will be used to troubleshoot devices.

AAA: We are using AAA on our network devices because we want to authenticate all user who
want to login on network devices, who want to join Wi-Fi, who want to do client to site VPN. We
are using authorization feature to limit access for the authenticated user on devices by adding
one more authorization checking. We are using accounting feature of AAA because we want to
have record that how many users has logged in past and how many users are on the logged in
on the device and we can track the user id and time when they logged in and logged out.

802.11a: We are using this technology in the project because we want to provide wireless access
in network. So, users who have Wi-Fi enabled devices can join our network. We are providing
Radius authentication for Wi-Fi user. Radius is the central server who has database of all user.

STP: In access layer, we want to provide redundancy. If we put redundancy it will create loop in
network. If the loop is created then it is not good for packets. Packets will go round and round in
loop until their TTL (Time to live expires) which consumes unnecessary bandwidth. So, we are
using Rapid-pvst+ which is the variant of STP which breaks the loop dynamically.

DHCP: We are using DHCP server because we want to have IP assigned dynamically to the
devices who boots up and their IP address is DHCP enabled. With the DHCP server we don’t
need to set up IP address statically on all devices.
DNS: We are using DNS server in network so users in network can resolve domain names to IP
address. So, user doesn't need to remember IP addresses, but they can remember domain
names assigned to IP address.
NetFlow: We are using the NetFlow feature of cisco devices. This feature enables us to track the
packets to particular interface. That could help us in troubleshooting purpose i.e. if our device is
not getting dynamic route then we can set NetFlow on the interfaces which are connected routers.
And that NetFlow will send all the packets which comes to that interface to the NetFlow receiver

GigaBytes Page 11
Final Project Report Version 1.1
and monitoring staff can monitor that is it getting LSA updates or not . If not getting LSA packets
then they have found the problem is in routing protocol.

3.3 Discussions
Our team has divided this technology to equal share to each member. So, each member was
responsible for four technical technology. And we divided the documentation technology also to
each member.
Below is the table for the person responsible for that technology to implement.

Technology Responsible Person

OSPF ANKIT

HSRP ANKIT

SSH ANKIT

IPSEC ANKIT

Frame Relay BOLD

ACL BOLD

NAT ADITYA

SNMP BOLD

Telephony services RAGETHA

Syslog RAGETHA

AAA BOLD

802.11a RAGETHA

STP ADITYA

DHCP ADITYA

DNS ADITYA

NetFlow RAGETHA

GigaBytes Page 12
Final Project Report Version 1.1
We all had to install the basic tool such as Microsoft office with subscription. So, all packages
were available from Microsoft. We installed packet tracer 7.1.1, so we can implement protocols
assigned to us. After implementing protocol, our team documented that work in weekly sheet. Our
team was following plan from project plan and the tasks decided in meeting minutes.

In future, our team will do same thing but we will exchange roles for technical implementation so
all person can know all protocols. All person, can use their knowledge in rotation base and they
get more and more expertise in each protocol. So, any member gets sick in future project, other
member can do work of that person.

4 Project Report

4.1 Project Outcome

Below are the outcomes of this project with details

Student lab network

In project definition, we committed to provide network for students. So, they can go to the internet
and access servers inside network as well.

We have created the lab network for all buildings. Below is the IP plan for lab network for the
buildings.

LAB-IP PLAN

Secondary
Abbreviatio vlan- Primary- Core
n Buildings subnet id Core switch Switch
BC Business and commerce 10.100.50.0/26 2 CR1 CR2
ED Education 10.100.50.64/26 3 CR1 CR2
HC Health and Community 10.100.50.128/26 4 CR1 CR2
IT Information Technology 10.100.50.192/26 5 CR1 CR2
SC Sciences 10.100.51.0/26 6 CR2 CR3
PP Pathways programs 10.100.51.64/26 7 CR2 CR3
CA Creative arts and media 10.100.51.128/26 8 CR2 CR3

EB Engineering and Built environment 10.100.51.192/26 9 CR2 CR3

HM Humanities and communications 10.100.52.0/26 10 CR3 CR4

LJ Law and justice 10.100.52.64/26 11 CR3 CR4
EL English Language 10.100.52.128/26 12 CR3 CR4

GigaBytes Page 13
Final Project Report Version 1.1
PD Professional development 10.100.52.192/26 13 CR3 CR4
LB Library 10.100.53.0/25 14 CR4 CR3

unallocated 10.100.53.128/25 15
Reserved 10.100.54.0/24 16
Reserved 10.100.55.0/24 17

Table 1: Subnets for lab for each building

Here we assigned subnets for lab for each building. Each subnet is assigned to their respective
core switch. We have backup core switch connection as well for each building. The diagram is
looks like below for BC building lab network

Figure 1: BC LAB network

Here CR1 and CR2 are the core layer 3 switches which can do switching and routing. We are
making CR1 as primary gateway for BC (Business & Commerce) lab and CR2 as secondary
gateway for BC lab. We are running HSRP protocol on CR1 and CR2 so it will handle the primary
and secondary candidate. At the time only one device will be active as HSRP protocol but we
added static route to CR2. So, it would do load balancing as well. So as quality purpose we are
using both core L3 switch (CR1 and CR2) at same time and we will get high throughput. This lab
network is much more reliable from user perspective because they will not get network down.
They are getting network available all the time. As from network management perspective this
Lab network is easy to manage and troubleshoot. Because if CR1 goes down then CR2 will switch
over as active. So, this lab network is reliable from user perspective and management
perspective.

For other building the diagram is same as figure 1 but primary and secondary L3 switches
changes according to table 1. General diagram of whole network is shown in Appendix B.

GigaBytes Page 14
Final Project Report Version 1.1
Academic staff network
We have made academic staff network for all the academic building. We gave them shared line
from access switch to staff pc which connects first IP-Phone and then pc. So, in one cable that
carries two traffic. For all the building below is the general diagram for Staff network. Where you
can replace X with primary gateway, Y with secondary gateway and Z with access switch
respective to building. Refer appendix c to replace X and Y and Z with respect to building.

Figure 2: Staff network, general diagram for all building

ACADEMIC-STAFF-IP-PLAN
BUILDING vlan
BC 10.100.6.0/27 65
ED 10.100.6.32/27 66
HC 10.100.6.64/27 67
IT 10.100.6.96/27 68
SC 10.100.6.128/27 69
PP 10.100.6.160/27 70
CA 10.100.6.192/27 71
EB 10.100.6.224/27 72
HM 10.100.7.0/27 73
LJ 10.100.7.32/27 74
EL 10.100.7.64/27 75
PD 10.100.7.96/27 76

Unallocated 80

GigaBytes Page 15
Final Project Report Version 1.1
Unallocated 81

Table 2: Academic staff IP plan

Network designed for academic staff is very effective. Because it has primary and secondary
gateway and both gateway is load sharing. So, reliability perspective we can say that this
network is on all the time. Links from core layer 3 switch to access switches is 10g link so it will
give high throughput. Rapid-pvst+ protocol is running between access layer switches that will
break the loop and will activate the redundant link if active link fails.

So, from the maintenance perspective. You have time to repair the failed device. Because
network designed in way that it has always backup link. And we left some unallocated subnets
for academic staff, if in future university add more academic building.

Administration staff network

In our project we made administration staff network. Our administration staff is finance,
marketing, HR (Human Resources) and others. So, in our case all staff has one building on
separate floor. The diagram is same for finance, marketing, HR and other staff as figure 2,
where we have to replace X with CR3 and Y with CR4 and Z with FMHO.
This network has also load sharing and backup gateway as other two mentioned network
above. In access layer they are also running Rapid-pvst+. So, access layer also has back-up
link.

IP plan for administration staff is as below

NAME Address VLAN ID

Finance 10.100.62.0 267

Marketing 10.100.63.0 268

HR 10.100.64.0 269

Others 10.100.65.0 270

Table 3: Ip plan for administration work

As we talk about quality and maintenance, it is same as other network mentioned before
administration staff network. Because we used same backup protocol and load sharing
technique.

Monitoring staff network

Monitoring staff network has same topology as mentioned above networks (Administration
network, student lab network). The difference is that, this network user is supposed to monitor
and manage network. So, in firewall rules they are allowed to pass to do remote login on any

GigaBytes Page 16
Final Project Report Version 1.1
network devices. On network devices syslog is configured so every network device will send log
messages to Syslog receiver. SNMP is also enabled on all network devices to send all trap
messages to this monitoring network device. Monitoring network has much more flexibility in
firewall. Monitoring network receives IP camera traffic as well, they are allowed to access IP
camera of any building.
As Quality wise, this network is designed in a way that monitoring staff will get informed even if
small activity happens on network devices. In network devices, AAA is enabled so every user is
authenticated to login in network devices. Network is designed in way that authenticated user’s
activity is also accounted. Authentication, authorization and accounting servers are in PrivServ
Building which is in different network.

Below is the IP plan for monitoring staff

Subnet NAME VLAN

10.105.4.0/22 On site management 100

10.100.74.0/24 Remote management 272

Table 4: Ip plan for monitoring staff

Subnet 10.100.74.0/24 is for the management staff who want to manage network from home.
Our network has facility to do remote VPN from home so they can manage network from home
as well.

Wireless network
We have created wireless network for university users and visitors. University user can join
regular Wi-Fi where they have to input university provided username and password. To connect
to visitor network user has to register his/her self and they will get limited time access. Persons
who connects to visitor Wi-Fi has no internal network access. Means they will be assigned
public DNS, not private DNS. So, they will use network as ordinary person not as university
user. Our network provides the Wi-Fi access to the university user. Below is the screen shot
from simulation where user has entered his credential to connect to Wi-Fi.

GigaBytes Page 17
Final Project Report Version 1.1

Figure 3: Input user credential to connect to Wi-Fi

And he/she is the registered user of university so, his/her device connected to Wi-Fi after
authentication.

GigaBytes Page 18
Final Project Report Version 1.1
Figure 4: User connected to access point

Now he/she can access the network

Figure 4: User can access the network

Here in above figure 4 we want show that user can access the university website. Here in our
case we assumed that our university name is usq and we assigned web address to
www.usq.edu.au in DNS record with private address 10.100.60.10

As we talk about the quality, the quality of Wi-Fi is good from network administrator perspective
because we are using the wireless controller from cisco which can manage all access point. Our
chosen wireless controller has capacity to serve 250 wireless access point. But our university
requires 170 which is less than its max capacity. So, it handles all access point effectively.

As we talk about quality from user perspective than it has very good quality. Because we are
giving link to access point which has speed of 10gbps. So, user will get high speed at any time.
And from the network administrative view, this Wi-Fi is very good because authenticated users
only can connect to Wi-Fi network and they can track each user’s activity on network for
surveillance purpose.

VPN network from site to site

GigaBytes Page 19
Final Project Report Version 1.1

We are providing VPN from one campus to other. So, all three campuses are connected with
each other and they can access each other’s private network. Suppose if our university has
address 10.100.60.10 then outside user from our campus cannot use that address to browse
university website. So, our private address is attached with 58.179.1.193 public address. So,
user from outside campus can use that address to browse our website. But with the VPN
service user can browse our website by entering private address. Below is the screenshot of
site 1, site 2, and site 3 where we setup site to site VPN between all three sites .

Figure 5: All three sites screenshot

So, we have setup VPN between all three sites so from site 2 we should able to browse
university website by private address. In below picture we choose pc0 from site 2 and entered
private address in browser and we succeeded to browse site 1 private address.

GigaBytes Page 20
Final Project Report Version 1.1

Figure 6: User from site 2 can access site 1 by private address

This site to site VPN is very helpful for site to site communication. If there is no site to site VPN
then university has to buy a lot public addresses and if private servers are assigned public
address then it would be vulnerable to cyber-attack every day and that could end up with much
more security cost.
Network administrator has to be very careful while managing site to site VPN. Small mistake
can terminate site to site connection. So, we are providing back up VPN with the frame relay
service. So even first goes down we have second which will handle all site to site traffic. From
user perspective this is good quality feature because they will not fill cutover if primary VPN
goes down.

VPN network from client to site

We are providing VPN service for home user as well. Home user has to put credential in VPN
client software and they will connect to our university network. They also have to specify public
address of VPN server in client software. Below is the screenshot where we put the credential
with public address of VPN server.

GigaBytes Page 21
Final Project Report Version 1.1

Figure 7: Inserted user credential in VPN client

Here in above figure we put username and password of user which we already inserted in our
radius server. We are using radius server wherever we want to authenticate user. So, we don't
need to have many radius servers. Noe let’s hit enter and we got message like below

GigaBytes Page 22
Final Project Report Version 1.1

Figure 8: VPN connected

So now we are connected to VPN and we should able to use network with private address.
Which we can see in below figure that user connected to home is able to browse our private
network because he/she is connected to VPN server

GigaBytes Page 23
Final Project Report Version 1.1

Figure 9: Network accessible with private address from home user connected through VPN

This function is very helpful to the university because they have users such as network
administrator, professors who want to work from home as well. So, they do not need to travel to
the university to access network. This feature saves time and money to user.

This feature is implemented with IPSEC so it provides the best security. No illegitimate user can
sniff packets because they will be encrypted. It is reliable as well because IPSEC protocol is
much stronger in reliability purpose.

Network for IP-phones

Ip-phone network is now common to all organization. All organization want Ip-phone network.
So, employee can call internal to other staff by just short extension. We are provided IP-phone
network where we used extension range starting from 1001. In below picture it shows that IP-
phone from one building has extension of 1001 and other building phone has extension 1002.

GigaBytes Page 24
Final Project Report Version 1.1

Figure 10: Phone with extension 1001

Figure 11: Phone with extension 1002

Now let’s create call from 1001 to 1002 and capture screenshot on phone with extension 1002

GigaBytes Page 25
Final Project Report Version 1.1

Figure 12: Call from 1001 to 1002

So, our Ip-phone network works effectively. This network will be used to connect as many as Ip-
phones. The quality of voice would be very nice because all the network devices used in project
are from cisco and with latest hardware. From network administrator perspective call quality
would be very nice because link speed selection is done effectively and all links in network
except those which connects to end devices are fiber with 10gbps speed.

Network for Printers

Every organization have printers. Some of them don’t put them on network. Some put them on
network so we can print from remote pc as well. Our client has also had requirement of printer
network. We made printer network building wise. Here is the diagram where printer is connected
to network and got IP.

GigaBytes Page 26
Final Project Report Version 1.1

Figure 13: Printer connected to network and got IP from DHCP server

This is much beneficial to user that they can print on any printer they want. Because all are
connected in network. So, user has choice to select printer to print. These printers are also
connected to two default gateways. So, they will have load sharing with two default gateway and
they are getting high availability.

Network for security and safety devices such as fire sprinkler, door swipe,
temperature sensor, speaker, camera
Every organization have fire sensor, sprinkler, camera, door swipe and speaker but not all
organization have all on network. We are providing client a network for all above devices.
The benefit to the university is that they can put device on network and they can manage that
device with IP. So, for example, if fire happened in particular room and sprinkler started to stop
fire, but not all sprinkler started which also can help to stop fire. So, network administrator can
manage those other sprinklers with IP and start them. So those also will help to extinguish fire.
Another example is camera. We are providing network for Ip camera as well. So, administrator
can manage particular camera whichever he/she want.

We are providing network for door swipe. So, user whenever want to access secure room they
have to swipe the card. Swipe device is connected in network. So, it can send all information
such as who has swiped recently, who tries multiple time and failed, who succeeded in daily,
weekly or monthly basis.

GigaBytes Page 27
Final Project Report Version 1.1

We are providing network for speaker. So, speaker can connect to network. Announcer can
select the IP to whom it wants to broadcast the announcement. This is very helpful because if
university chancellor wants to announce some message to IT building then he will select IP
addresses of speakers which are in IT building. This speaker network is reliable because this
network has also redundant gateway. So, if one fails other will be active and announcement will
not interrupt.

4.2 Cost of the Project

4.2.1 Hardware cost

Every network project has hardware cost. Our project has also used hardware. Which are
mentioned with description and price in below table.

[Marker Note: In project plan, we did not include the hardware cost and we had feedback that
even if you are making network in simulation software you have to include hardware cost. So,
we attached hardware cost. So, our overall cost would differ to the estimated cost in project
plan]

DEVICE PRICE QUAN TOTAL

TITY

Cisco Firepower 4110 Network Security 57,681.62 2 115363.24

Description:
This is the firewall which we are using at the
endpoint of our network which connects to the
internet. So incoming traffic from outside world and
outgoing traffic from inside network to outside will
be filtered.
(Pcnation.com 2018)

GigaBytes Page 28
Final Project Report Version 1.1

Cisco Catalyst 3850-24XS-S (core) 6293.85 4 25175.4

Description:
This is the device which is working as core router.
Refer Appendix B where CR1, CR2, CR3, CR4 are
these devices
(CNET 2018)

cisco Catalyst 3560E-48TD (layer-2 purpose) 1112.0 49 54488

Description:
These devices are Layer 3 devices but we are not
using layer 3 feature of it. We are using layer 2
purpose only. In Appendix B refer devices which
are in pink color.

(CNET 2018)

25,468.70 1 25468
AIR-CT5508-250-K9 (WLC-controller)
Description
This controller will be used for controlling Wi-Fi
access points.
(Router-switch.com 2018)

GigaBytes Page 29
Final Project Report Version 1.1

180 206638.2
Cisco Aironet 3802I – (wireless access point) 1147.99
Description:
This is the access point which will be used for
distributing wireless network.
(Cisco License Store | Cisco ASA licenses | Cisco
ISR licenses 2018)

2300 9 20700
Cisco CISCO3925/K9 3925 Integrated Service
(servers)
Description:
We are using this device as private server.
(Amazon.com 2018)

3328 3 9984
Cisco UCS C240 M5 Rack Server(servers)

Description:

We are using this device for private server

(Ferranti 2018)

GigaBytes Page 30
Final Project Report Version 1.1

38000 1 38000
Cisco Catalyst 6800 - switch - 8 ports
Description:
This switch we are using in public server room
where all public server will connect.

(PC-Canada.com 2018)

Cisco Small Business SG350XG-24F 2320.18 1 2320.18

(Switch for private server)
Description:
This switch we are using for private servers
(CNET 2018)

Total 498137.02

Table 5: Hardware cost

4.2.2 Labor cost

Name Hours Spent Hours Spent Total Cost/hour Total cost
(individual) (Group)

GigaBytes Page 31
Final Project Report Version 1.1
Ankit 81 39 120 30 3600

Aditya 73 39 112 30 3360

Bold 67 39 106 30 3180

Ragetha 61 39 100 30 3000

Total 282 156 438 30 13140

Table 5.1: Labor cost

All team-meetings took 17 hours, which are not added in the activity log sheets.

The total meeting cost:

17 hours x number of team members x cost/hour= 17x4x30 = 68 x 30 = 2040

So, the total labor cost = 13140 + 2040 = 15,180 AUD.

4.2.3 Comment on actual cost and estimated cost

The hardware cost was not included in the project proposal plan because we were showing the
output as a simulation in the packet tracer and we did not thought that the cost for the hardware
was needed. However, we are adding it to the project report for having a practical approach for
the implementation of the network. And the labor cost varied by 2800 AUD because the part of
the design needed to be changed for the quality of the network. As a team, we did not compromise
on the quality, and that is the reason the hours have been increased and due to the reason, the
cost went up by 2800.

4.2.4 Comment on what we have learnt about project cost estimation

We have learnt that we need to have a reserve budget for bigger projects and the practical cost
like hardware needed to be included, even though it is not implemented here. With the reserve
budget, we can easily afford the labor cost.

GigaBytes Page 32
Final Project Report Version 1.1

5 Team Management Report

5.1 Team Organization
A team organization or project team (Mymanagementguide.com 2018) “is a group which is
organized into a team to perform different individual/distributed tasks of a particular project to
obtain desired results”. The group consists of a leader, who is generally below a manager or
supervisor.

The general duties of a team are:

· Respecting the work and the team.

· To follow the plan laid out to achieve the expected outcome.
· Work should be understood from a professional point of view.
· Taking care of the expectations such as time, money and quality.
· Communicating and preparing weekly minutes.
· Reporting the issues and following the development plan which was decided, which is,
agile development plan.
· Working with others and communicating any problems.

The approach we used here is a whole-team based approach or team-based approach. The
definition (SearchSoftwareQuality 2018) for team-based approach “is considered has a type of
project management in which each person on the team is responsible equally for the quality and
desired outcome of the project”.

This kind of approach made us to know the importance of each individual and we understood that
we have to work together but not in isolation. Appreciating each other’s skills and using them in
the project was another advantage of it. And has we have known each other’s skills, we could
easily switch roles when needed. As, all the team members have a good amount of exposure to
the methodologies which we have used and the experience which they brought to the table helped
not only the overall project but also each individual.

5.2 Team structure and roles

The structure which was used is whole team-based approach. By this, we were able to achieve
the common goals which we set at the start of the project by having a distribution of project and
roles. The co-operation from each individual was crucial in development of the project. There is
no hierarchical structure because we all communicate and have equal roles while deciding about
various aspects of the project. Due to this, we had the flexibility when any problem occurred or
when any decision needed to be taken. This made working easy with the supervisor/client
because we were able to know and communicate about various aspects and stages of the project.

GigaBytes Page 33
Final Project Report Version 1.1

Fig 5.1: Representing Structure of the team

Roles (Technical and management):

Implemented by Ankit:
1) Protocols: OSPF (open shortest path first), HSRP (Hot standby router protocol), SSH
(Secure shell), IPSEC (Internet protocol security).
2) Documentation: Technology report, Cost report.
3) Implementation: Configuring routers.
4) Setting up team meetings and agendas.
5) Supervising all works.
6) Helping all team members with technical difficulties
7) Time management, Cost management
Implemented by Aditya:
1) Protocols: DHCP (Dynamic host configuration protocol), DNS (Domain name system), NAT
(Network address translation), STP (Spanning-tree protocol).
2) Documentation: Team management report, Risk management plan
3) Implementation: Configuring Switches.
4) Recording and feedbacks for the meetings.
5) Risk management

Implemented by Bold:
1) Protocols: Frame-relay, ACL (Access control-list), SNMP (Simple network management
protocol), AAA (Authenticate, Authorize and account).
2) Documentation: Executive summary, Contribution distribution.
3) Implementation: Configuring the hosts.
4) Quality assurance
Implemented by Ragetha:
1) Protocols: 802.11a Wi-Fi, Syslog, Telephony services.
2) Documentation: Methodology report, Conclusion.
3) Implementation: IP-plan.
4) Communication management

GigaBytes Page 34
Final Project Report Version 1.1
5.3 Team management
We have used Tuckman’s Team development model to understand the tasks and each team
member in order to build trust among each other and to be progressive. We have gone through
different stages of this model and we feel; the model might have solved individual issues which
were raised while developing the design. The forming stage itself we made it clear that what we
would expect of the team project and mentioned our skills, which made it easier to attract the right
individuals. The next stage, where we stormed through ideas, designs were different to each
other’s view. However, making points and analyzing them paved the way to solve creative
differences. The stage where we analyzed and negotiated is known as norming. And then came
the crucial stage where we performed collectively to get a shared output is known as performing
stage. The last stage is the adjourning stage where we could discuss the outcome and various
aspects related to the project.

In this model, each step depended on the previous step i.e., we could not finish performing if we
could not complete norming stage.

Problems encountered
1. Individual may not get the credit he/she deserves: This doubt was in every team
member’s mind because maximum credit is for team’s performance. However, this doubt
was cleared in storming stage, where we raised this doubt and were satisfied by
understanding the criteria and thought of working genuinely to give credit to those who
deserved more.
2. Design difficulties: The problem with not accepting each other’s basic idea of design
was present for two meetings. However, talking to supervisor, communicating with each
other and following universities basic model helped us to overcome this issue.
3. Various design issues: Different designs were introduced by different team members,
but we accepted the best possible design. However, if deep research and practical
experience would enhance the understanding in choosing a model/design.
4. Absence of a team member: When anyone could not be able to attend to a meeting, we
acted professionally by letting the team know in advance. Absence of any team member
did not go past one week, and it did not raise any problems because the person who was
absent communicated the problem.

Important strategies to adopt in future and essential points we learned

● An important strategy is to have a plan/model to follow before the commencement of the

project because it will help you to know where you are and what more/ at what stage you
need to perform.
● Tuckman’s development model can be used in different projects of different scales also.
And it helped us to understand each other and helped us to progress has a team by
evaluating at each stage. We would recommend this model for future projects as well.
● Team-based approach was important to our project, but it won’t be the same for future
projects, but it can be preferred if any team prefers equal importance of each individual.
● By helping each other, we learned different skills from each other and as a team
understood, how important is working like a team rather than in an isolated way.

GigaBytes Page 35
Final Project Report Version 1.1

5.4 Other team-work related issues

● Differences in understanding each other: As our group was quite diverse, it was difficult
at the start to understand each other but after three meetings, we became comfortable
with each other. However, we could not completely understand certain point of views of
each other because the duration of the project was short. But, we made sure that did not
come in the way to complete the project and to mitigate this issue, we had planned certain
team building activities like paintball and became more social.

6 Communication report
6.1 Communication and meetings
Communication plan is an important aspect to the project which ensures that all the stakeholders
are in regular touch and are collective, analyzing and developing the project from previous
meetings. We have identified the stakeholders and there are as follows:

Name Role Email Phone

Ron Addie Supervisor/sponsor [email protected] 0746315520

Ankit Team leader [email protected] 0401412452

GigaBytes Page 36
Final Project Report Version 1.1
Aditya Team member [email protected] 0424707515

Bold Team member [email protected] 0415200962

Ragetha Team member [email protected] 0415525353

Table 6: Stakeholder

The team was professional enough to follow a disciplined way in communicating with each other.
Our journey started with a kick-off meeting and this was organized by communicating through
finding team member forum post. The meeting laid a foundation to the plan which we would follow.
And in this we briefly described the frequency of meetings and roles. We only got the clarity in the
first few meetings when we agreed upon weekly team meetings and supervisor meetings, when
needed.

There were few weeks where we could not meet but we made sure we made a zoom meeting,
through which we updated on each other’s status and analyzed. Below is the schedule of the
different types of meetings we had throughout the project duration and we have attached all other
subsequent meetings to these meetings in meeting minutes sheets.

Commu Objective Way to How Stakehold Outcome Outcome

nication Communica Frequent ers stored
Type te involved

Kick-off Introduction Face-to-face Only once All the Plan, Google

Meeting define the team meeting drive
project, roles members minutes
has been
identified

Team- Discussed Zoom calls weekly All the Plans, Google

meeting roles, status, and face-to- team schedules, drive
s other issues face members outcome
and
meeting
minutes

GigaBytes Page 37
Final Project Report Version 1.1
Design Technical Face-to-face When All the Plans, Google
Meeting aspects and required team schedule drive
s design issues members and
were meeting
discussed minutes

Supervi Status, plans, Face-to-face When All the Status, Google

sor suggestions required stakeholde schedule, drive
meeting were rs plans
discussed

Status- Final status Face-to-face End of All the status Google

report the stakeholde drive
project rs

Table 7: Main meetings with outcome and other details

The meeting minutes will provide the information of how successful and the improvements we
made regarding the team meetings.

The mode of communications was as follows

● Face-to-face
● Zoom online meetings
● Google drive shared service
● WhatsApp for timely discussions
● Email service

Problems encountered
1. After three team meetings, we realized the need for each person to assign a role in the meeting.
That is, we assigned a recorder, who will record the meetings and would provide feedback to
improve the meetings in any other way. The other role was a time keeper, who would set time
limits for the meetings and he would let the presenter know about the time limits.
2. The other important aspect was agenda for next meetings. We did not give in advance the
agendas for next week or meeting at the start but started giving it at the meeting itself or the
following day.
3. Health issue for a team member, this problem was not severe because we had beforehand
knowledge and we distributed the work among other team members.

6.2 Documentation
● The documents such as meeting minutes helped us to handle the weekly meetings in an
efficient manner. The agenda in that section made us define practical short aims for next
week and the division of work among team members made the task much easier.

GigaBytes Page 38
Final Project Report Version 1.1
● Activity log sheets helped us to calculate the time involved and thereby, we would calculate
the labor cost and how much time does each task took. With this we can handle future
projects with an estimated time in a much practical way.
● We made IP plan in excel sheet and told every team member to refer that plan to
implement technical thing using that sheet. If someone find error then he/she will request
change to project manager(Ankit). Who would change it if that error confirmed.
● We made diagram in draw.io which has integration with google drive and we would able
to save diagram in google drive and each member could refer that diagram from shared
folder.
● Distribution of the work, especially in documentation made our work simpler and a shared
drive helped us to edit the documents easily because of the shared features.
● We used many technical articles and documentations for understanding which protocol
suits the correct environment of our network.
● Meeting minutes sheet are attached in appendix E and activity log sheets of all team
members is attached in appendix F.

So overall our team find all document helpful which were shared in shared folder so they can
retrieve that document whenever they want. That made implementation very easy.

6.3 Other Discussions

● There were no issues related with communication, except when one of our team member
had health problems. However, the person involved was professional enough to inform
the rest of the team and the team was co-operative enough to take care of the work.
● The technology helped us in a great way when there were holidays such as Easter
holidays or semester-break because we used ZOOM (video conferencing tool) to have a
meeting and we also had other platforms to share our ideas.

7 Contribution Distribution

Main Task Ankit (%) Aditya (%) Bold (%) Ragetha (%)

Initiation phase 37.8 24.8 25.3 11.9

GigaBytes Page 39
Final Project Report Version 1.1
Design-Phase 25.4 23.5 25.4 25.4

Implementation 34.7 32.9 22.3 22.3

Monitoring 28.9 26.1 18.3 26.5

Closing 21.8 23.3 32.1 22.6

Team-meeting 25 25 25 25

Total 28.4 25.8 23.5 22.3

(out of 100) (out of 100) (out of 100) (out of 100)

Table 8: Contribution table

The above table for contribution was distributed according to the activity log sheets which are
attached to the bottom of the document. The allocation of work was difficult to distribute
individually at the start of the project because the whole project was inter-linked together in such
a way that dividing it would lead to disastrous results and we could only distribute the work when
everyone really understood the concept. When everyone spend time to understand each other
and the concept, then only we started working as a team. Then we came to conclusion to find out
the each other’s management skill and technical skill, and some of the members had similar
technical skill and management skill. Then we discussed with each other, to find a suitable role.
And finally, we decided each other’s responsibility, and it is attached in Appendix D.

Assigning each other the tasks does not mean that one person did the entire task, but it means
that at every point we needed each other’s help, for example, to configure the cost, we have to
know the cost of all the equipment, which is distributed and we all need to contribute and help
each other for completion of each task. Even with the documentation, the person writing the roles

GigaBytes Page 40
Final Project Report Version 1.1
contribution and other roles should coordinate with the meeting minutes person, which means
everyone, because we made sure everyone in the group has the chance to do meeting minutes.
And if we talk about technical tasks, then everyone performed well because we assigned
according to each other’s specialty. So, our execution went very smoothly.

8 Conclusion
This report has discussed different aspects of the project. It has described methodology used in
this project with justification and phases of methodology with diagrams. It also has described the
technology which is used with details and the justification of why that technology is used.
Furthermore, detailed explanation of project outcome with working proof of network simulation
has been presented. And, cost of hardware and labor has been calculated very realistically and
practically. Team structure has been laid out with roles and management plan for organizing
and running successfully. To add to that, how well we communicated with the team and detailed
discussion has been presented in the meeting minutes. Also, the contribution has been
presented thoroughly, according to each team member’s assigned work and all the necessary
documents have been attached.

Everyone was excited to put their knowledge and skill into the project. At the initial stage, we
had to face some difficulties in understanding others view because of our cultural differences.
However, we worked together to overcome the challenge because every was eager to learn
from each other and professional enough to overcome the challenges. The design phase raised
many conflicting ideas in terms of design, but we overcame it by having consultations with
supervisor and the network manager ( Toran Matherson ) of USQ network. We were happy with
the advice from the experts, as it is related to real-life data. The implementation phase was
pretty challenging because we could not predict the few dependencies at the designing phase,
which were only identified during implementation. However, our project methodology was quite
capable to adapt to the changes occurred during the implementation phase. We were delighted
when the network worked according to the plan in the testing phase, even after adapting to the
changes during the implementation phase.

As each other had different work-experience, it was a great learning experience in terms of
different technical aspects and management skills. We learned, how to work with a team, how to
improve the working skills, how to run effective meetings and how to overcome challenges
during the project. The essential thing to any project is the plan at the initial stage, and we
learned the importance of it.

The essential aspect is the proposal plan, so, spending quality of time in it to assess different
risks, costs, quality, communication and change management. Another important aspect is the
design phase for any project, so spending required time to analyze the risks involved is
important.

GigaBytes Page 41
Final Project Report Version 1.1

References
1. Pcnation.com. (2018). Cisco FirePOWER 4110 Network | Networking FPR4110-ASA-K9
| PCNation.com. [online] Available at:
https://www.pcnation.com/web/details/3M8543/Cisco-Firepower-4110-Network-Security-
Firewall-Appliance-FPR4110-ASA-K9 [Accessed 31 May 2018].

2. CNET. (2018). Cisco Catalyst 3850-24XS-S - switch - 24 ports - managed - rack-

mountable Prices. [online] Available at: https://www.cnet.com/products/cisco-
catalyst-3850-24xs-s-switch-24-ports-managed-rack-mountable/prices/
[Accessed 28 May 2018].
3. CNET. (2018).Cisco Catalyst 3560E-48TD - switch - 48 ports - managed - rack-
mountable Series Prices. [online] Available at:
https://www.cnet.com/products/cisco-catalyst-3560e-48td-switch-48-ports-
managed-rack-mountable-series/prices/ [Accessed 28 May 2018].

4. Router-switch.com. (2018). AIR-CT5508-250-K9 Cisco Wireless Controller AIR-

CT5508-250-K9 Price for Cisco 5500. [online] Available at: http://www.router-
switch.com/air-ct5508-250-k9-p-3543.html [Accessed 30 May 2018].
5. Cisco License Store | Cisco ASA licenses | Cisco ISR licenses. (2018). Cisco
Aironet 3802I - wireless access point price $1147. [online] Available at:
https://turbo-networks.com/shop/cisco-aironet-3802i-wireless-access-point/
[Accessed 30 May 2018].
6. Amazon.com. (2018). [online] Available at: https://www.amazon.com/Cisco-
CISCO3925-K9-Integrated-Service/dp/B008TSLYC8 [Accessed 27 May 2018].
7. Ferranti, M. (2018). Cisco's M5 UCS servers take intent-based approach to data
center. [online] Network World. Available at:
https://www.networkworld.com/article/3207688/data-center/ciscos-m5-ucs-
servers-take-intent-based-approach-to-data-center.html [Accessed 28 May
2018].

8. PC-Canada.com. (2018). Catalyst 6800 8 Port 40ge Integrated Dfc4. [online]

Available at: https://www.pc-canada.com/item/C6800-8P40G.html [Accessed 31
May 2018].

9. CNET. (2018). Cisco Small Business SG350XG-24F - switch - 24 ports -

managed - rack-mountable Prices. [online] Available at:
https://www.cnet.com/products/cisco-small-business-sg350xg-24f-switch-24-
ports-managed-rack-mountable/prices/ [Accessed 26 May 2018].

GigaBytes Page 42
Final Project Report Version 1.1
10. Mymanagementguide.com. (2018). Project Team Organization – Team
Definition, Roles & Responsibilities, Organizational Chart. [online] Available at:
http://www.mymanagementguide.com/basics/project-team-organization-project-
team-definition-responsibilities-and-roles-and-project-team-organization-chart/
[Accessed 23 May 2018].
11. SearchSoftwareQuality. (2018). What is whole-team approach (team-based
approach)? - Definition from WhatIs.com. [online] Available at:
https://searchsoftwarequality.techtarget.com/definition/Whole-team-approach
[Accessed 27 May 2018].

12. Hogg, S. (2018). OSPFv3 for IPv4 and IPv6. [online] Network World. Available
at:https://www.networkworld.com/article/2225270/cisco-subnet/ospfv3-for-ipv4-
and-ipv6.html [Accessed 26 May 2018].
13. En.wikipedia.org. (2018). Link-state advertisement. [online] Available at:
https://en.wikipedia.org/wiki/Link-state_advertisement [Accessed 28 may. 2018].
14. Tools.ietf.org. (2018). [online] Available at: https://tools.ietf.org/pdf/rfc2281.pdf
[Accessed 26 May 2018].

Appendix A
Full form of abbreviation used in project

BC Business and commerce

ED Education
HC Health and Community
IT Information Technology
SC Sciences
PP Pathways programs
CA Creative arts and media

EB Engineering and Built environment

GigaBytes Page 43
Final Project Report Version 1.1

HM Humanities and communications

LJ Law and justice
EL English Language
PD Professional development
LB Library
L3 Layer 3
CR1 Core L3 1
CR2 Core L3 2
CR3 Core L3 3
CR4 Core L3 4
FIR Firewall
FMHO Finance, Marketing, HR, Others
PrivServ Private servers
PubServ Public servers
AAA Accounting Authorization Authentication
VPN Virtual Private Network

GigaBytes Page 44
Final Project Report Version 1.1

Appendix B

Figure 1a: whole network without end devices

GigaBytes Page 45
Final Project Report Version 1.1

Appendix C

Switch Primary-Core switch Secondary Core Switch

BC CR1 CR2
ED CR1 CR2
HC CR1 CR2
IT CR1 CR2
SC CR2 CR3
PP CR2 CR3
CA CR2 CR3
EB CR2 CR3
HM CR3 CR4
LJ CR3 CR4
EL CR3 CR4
PD CR3 CR4
LB CR4 CR3
FMHO CR4 CR3
MON CR4 CR3
PriveServ CR4 CR3
PubServ FIR2 FIR1

GigaBytes Page 46
Final Project Report Version 1.1

Appendix D

Main Task Ankit Aditya Bold Ragetha

Proposal Plan Introduction, Specification, Risk Quality Communication

Design plan, management, management management
Time and Cost Code of conduct plan plan
management

Design-Phase Plan for core DHCP pool Plan for backup Plan for NetFlow,
and distribution design, plan for site to site VPN plan for Wi-Fi
layer design, DNS entries, plan protocol, plan implementation,
Routing for NAT, plan for for SNMP plan for syslog
protocol STP protocol, protocol, plan implementation,
selection, plan for firewall for AAA, plan for plan for
Backup design ACL, plan for telephony
gateway access layer services, design
protocol design of IP plan for
selection, whole network
Selection of
primary VPN
protocol,
Selection of
remote session
protocol to
devices

Implementation Implement the Implement the Implement the Implement the

design plan design plan made design plan design plan
made by him by him made by him made by her.

Team-meetings Setting agenda Record meetings Time Schedule

for meetings and analyze to management for meeting and
improve next meeting remind everyone
meeting by adapted
communication
channel

Documentation Technology Team Executive Communication

for final report report, cost management summary, report,
report report, contribution conclusion
Methodology distribution
report

GigaBytes Page 47
Final Project Report Version 1.1
Testing Making sure Making sure Making sure Make sure
routing protocol firewall rules backup VPN is NetFlow works
and HSRP works as stated, working, making fine, make sure
works as stated Making sure STP sure monitoring all areas are
loops are not device gets covered with
formed, making proper SNMP wireless access
sure end devices traps generated point. Make sure
getting IP from by network all access points
DHCP server, device. Making have connectivity
making sure that sure monitoring to internet and
DNS server device can internal network.
responds to the access to SNMP Make sure all
DNS query as MIB database. telephones are
stated Making sure all getting extension
the clients are number and they
inserted in AAA are able to
server and AAA communicate
servers are with each other.
responding to Make sure ip
the requested plan is well
party. Making all documented.
ACL are
functioning as
should be. Test
whole network

Appendix E
Meeting minutes and work done by previous week and assigned to particular week

Week 1
We do not have any meeting in week 1

Week 2

Minutes (Week 2- 05/03/2018)

Deciding Topic
Title

GigaBytes Page 48
Final Project Report Version 1.1
Attendees Ankit Patel, Bold, Aditya, Ragetha
Apologies
Location Refectory Level 1

● Introduce each other and share contact detail

Agenda ● Meet the Dr Tao and explain the situation
● Look for supervisor
● Make the brief of self-chosen project and send to Dr Tao.

● Decision made that meet the Dr Tao. Explain him situation. if

he is agree with our own project then look for supervisor.
● If he does not agree than choose project from list.
Decisions and ● End of the day project topic should be chosen and start to
Memos think about planning phase.
● Make required tools ready for future use.
● Instruct all members to join WhatsApp group.
● Make all sheets handy to be filled in online environment.
● Instruct members to download Zoom for future meetings.
Table 1.E: Meeting sheet for week 2

Task Check for Last Week

Tas Wh
Criteria Due Completed (Y/N)
k o
<--------No team formed----->

Table 2.E: Task check for week 1

GigaBytes Page 49
Final Project Report Version 1.1

New Tasks Allocation in This Week

Tas
Description Who Due
k
1 Make project charter All 11/3/18
2 Install required tools All 11/3/18
Table 3.E: Task check for week 2

Week 3

Minutes (Week 3- 12/3/18)

Make project plan

Title
Attendees All
Apologies
USQ R Block Level 1
Location
Discuss the project plan
Agenda Divide project plan topics to each member
Discuss about network design

● At least end of the week 80 % of project plan should

be completed.
● Rough design of network should be created.
● Meeting with ICT head should be completed.

Decisions and
Memos

GigaBytes Page 50
Final Project Report Version 1.1

Table 4.E: Meeting sheet for week 3

New Tasks Allocation in last Week

Tas
Description Who Due Completed?
k
1 Make project charter All 11/3/18 yes
2 Install required tools All 11/3/18 yes
Table 5.E: Task check for week 2

New Tasks Allocation in This Week

Tas
Description Who Due
k
1 Document scope Ankit 16/3/2018
2 Document WBS Ankit 16/3/2018
3 Document communication plans Ragetha 16/3/2018
4 Document scheduling Ankit 16/3/2018
5 Document risk management plans Aditya 16/3/2018
6 Make quality management plan Bold 16/3/2018
7 Cost estimation Ankit 16/3/2018
8 Team Contract (Code of Conduct) Aditya 16/3/2018
9 Final project plan All 18/3/2018
Table 6.E: Task check for week 3
Week 4
We did not have any meeting

Week 5

GigaBytes Page 51
Final Project Report Version 1.1

Minutes (Week 5 26/03/2018- 1/4/2018)

Title
Designing phase meeting

Attendees Bold, Ragetha, Ankit, Aditya

Apologies
Ankit home
Location
Discuss about the design of overall network
Discuss design of sub network
Assign different design responsibility
Agenda Make individuals design in packet tracer

Everyone will participate in group work to do design. End of

the week rough design should be ready in packet tracer.
● Aditya’s is responsible for design of firewall ,DHCP
pool, DNS, NAT, STP
● Ankit’s is responsible for core and distribution protocol,
backup gateway, selection of primary VPN, selection of
remote session.
Decisions and ● Bold’s responsibility: Plan for backup VPN, Plan for
Memos SNMP, access layer design, AAA, ACL.
● Ragetha’s responsibility: Plan for NetFlow, Wi-Fi, Syslog,
telephony services and whole IP-plan.

Table 7.E: Meeting sheet for week 5

Task Check for Last Week

Task Criteria Who Due Completed (Y/N)

1 Document scope Ankit 16/3/2018 Y
2 Document WBS Ankit 16/3/2018 Y
3 Document communication plans Ragetha 16/3/2018 Y

GigaBytes Page 52
Final Project Report Version 1.1
4 Document scheduling Ankit 16/3/2018 Y
5 Document risk management plans Aditya 16/3/2018 Y
6 Make quality management plan Bold 16/3/2018 Y
7 Cost estimation Ankit 16/3/2018 Y
8 Team Contract (Code of Conduct) Aditya 16/3/2018 Y
9 Final project plan All 18/3/2018 Y
Table 8.E: Task check for week 3

New Tasks Allocation in This Week

Tas Wh
Description Due
k o
1 Design on paper All 01/04/2018
2 Design in packet All 01/04/2018
tracer
Table 9.E: Task check for week 5

Week 6

Minutes (Week 6 02/04/2018)

Title Finalizing design

Attendees All
Apologies
Ankit-home
Location
Making final design of the network allocated to each
other after updating
Agenda

We have to have a final design ready by end of the week.

Decisions and
Memos We have to make the design in the packet tracer.

GigaBytes Page 53
Final Project Report Version 1.1
We need to get the design approval from the supervisor.

Table 10.E: Meeting sheet for week 6

Task Check for Last Week

Tas Wh
Criteria Due Completed (Y/N)
k o
1 Design on paper All 01/04/2018 Y
2 Design in packet All 01/04/2018 Y
tracer

Table 11.E: Task check for week 5

New Tasks Allocation in This Week

Tas Wh
Description Due
k o
1 Final design deciding All 08/04/2018
2 Design the final design in packet tracer All 08/04/2018

GigaBytes Page 54
Final Project Report Version 1.1
3 Get the approval for design from All 08/04/2018
supervisor

Table 12.E: Task check for week 6

Week 7
Minutes (Week 7 09/04/2018)

Configuring starting phase

Title
All
Attendees

Apologies

Ankit-home
Location
To configure Core layer-3 switch
To configure access layer switch
Agenda To configure firewall
To configure WLC

Ankit’s responsibility is core layer-3 switch

implementation

Bold’s responsibility for access layer switch

Decisions and Memos
Aditya’s responsibility is to configure firewall

Ragetha’s responsibility to configure WLC

GigaBytes Page 55
Final Project Report Version 1.1

Table 13.E: Meeting sheet for week 7

Task Check for Last Week

Tas Wh Completed
Criteria Due
k o (Y/N)
1 Final design deciding All 08/04/2018 Y
2 Design the final design in packet tracer All 08/04/2018 Y
3 Get the approval for design from All 08/04/2018 Y
supervisor

Table 14.E: Task check for week 6

New Tasks Allocation in This Week

GigaBytes Page 56
Final Project Report Version 1.1
Tas
Description Who Due
k
1 Core-layer-3 switch configuration Ankit 22/04/2018
2 Access-layer switch configuration Bold 22/04/2018
3 Firewall configuration Aditya 22/04/2018
4 WLC configuration Ragetha 22/04/2018
5 Monitor schedule Ankit 22/04/2018
6 Team management Aditya 22/04/2018
7 Quality assurance Bold 22/04/2018
8 Communication management Ragetha 22/04/2018
Table 15.E: Task check for week 7

Week 8

Minutes (Week 8 16/04/2018)

Title Configuration of protocols

All
Attendees

Apologies

R-block-level-1
Location

Agenda ● Configure the protocols on all the required devices

● Assign the protocols to each member

● Ankit will do OSPF, HSRP, SSH, IPSEC protocols on

Decisions and network.
Memos ● Aditya will do DHCP, DNS, STP, NAT protocols on
network.
● Bold will do AAA, ACL, SNMP, Frame-relay protocols
on network.

GigaBytes Page 57
Final Project Report Version 1.1
● Rageths will do NetFlow, Wi-Fi, syslog, telephony
services protocols on network.

Table 16.E: Meeting sheet for week 8

Task Check for Last Week

Task Criteria Who Due Completed (Y/N)

1 Core-layer-3 switch configuration Ankit 22/04/2018 Y
2 Access-layer switch configuration Bold 22/04/2018 Y
3 Firewall configuration Aditya 22/04/2018 Y
4 WLC configuration Ragetha 22/04/2018 Y
5 Monitor schedule Ankit 22/04/2018 Y
6 Team management Aditya 22/04/2018 Y
7 Quality assurance Bold 22/04/2018 Y
8 Communication management Ragetha 22/04/2018 Y
Table 17.E: Task check for week 7

New Tasks Allocation in This Week

GigaBytes Page 58
Final Project Report Version 1.1
Tas
Description Who Due
k
1 Implement OSPF, HSRP, SSH, IPSEC protocols on Ankit 22/04/20
network. 18
2 Implement DHCP, DNS, STP, NAT protocols on network Aditya 22/04/20
18
3 Implement AAA, ACL, SNMP, Frame-relay protocols on Bold 22/04/20
network 18
4 Implement Netflow, WiFi, syslog, telephony services Ragetha 22/04/20
protocols on network 18
5 Monitor schedule Ankit 22/04/20
18
6 Team management Aditya 22/04/20
18
7 Quality assurance Bold 22/04/20
18
8 Communication management Ragetha 22/04/20
18
Table 18.E: Task check for week 8

Week 9

Minutes (Week 9 23/04/2018)

Title
Checking the progress of the project
Attendees All
Apologies
Location R-block-level-1

Checking with each other about individual’s progress

Cost confirmation and other management like quality, risk
Agenda
and communication.

GigaBytes Page 59
Final Project Report Version 1.1
We are on schedule according to the project plan.
Decisions and
Some tasks took little longer than expected.
Memos
Finishing the implementation at the end of the week.
Table 19.E: Meeting sheet for week 9

Task Check for Last Week

Tas Complet
Criteria Who Due
k ed (Y/N)
1 Implement OSPF, HSRP, SSH, IPSEC Ankit 22/04/2018 Y
protocols on network.
2 Implement DHCP, DNS, STP, NAT Aditya 22/04/2018 Y
protocols on network
3 Implement AAA, ACL, SNMP, Frame-relay Bold 22/04/2018 Y
protocols on network
4 Implement NetFlow, Wi-Fi, syslog, Ragetha 22/04/2018 Y
telephony services protocols on network
5 Monitor schedule Ankit 22/04/2018 Y
6 Team management Aditya 22/04/2018 Y
7 Quality assurance Bold 22/04/2018 Y
8 Communication management Ragetha 22/04/2018 Y
Table 20.E: Task check for week 8

New Tasks Allocation in This Week

Tas
Description Who Due
k
1 Finish the final implementation for testing All 29/04/2018
2 Predict the risk Aditya 29/04/2018
3 Update the schedule Ankit 29/04/20018
4 Monitor schedule Ankit 22/04/2018
5 Team management Aditya 22/04/2018
6 Quality assurance Bold 22/04/2018
7 Communication management Ragetha 22/04/2018

GigaBytes Page 60
Final Project Report Version 1.1

Table 21.E: Task check for week 9

Week 10

Minutes (Week 10 30/04/2018)

Title Testing the individual network part

Attendees All
Apologies
Location Ankit-home
Test the network done by own self
Agenda
Quality assurance
Ankit will test routing protocol and HSRP

Bold will do Quality Assurance of the complete network and

Decisions and also his work.
Memos
Aditya will test STP, DHCP, DNS is working or not.

Ragetha will test telephone services, are working or not.

Table 22.E: Meeting sheet for week 10

Task Check for Last Week

Completed
Task Criteria Who Due
(Y/N)
1 Finish the final implementation for All 29/04/2018 Y
testing
2 Predict the risk Aditya 29/04/2018 Y
3 Update the project schedule Ankit 29/04/2018 Y
Table 23.E: Task check for week 9

New Tasks Allocation in This Week

GigaBytes Page 61
Final Project Report Version 1.1
Task Description Who Due
1 Test routing protocol and HSRP, SSH and IPSEC Ankit 06/05/2018
2 Test Quality Assurance of the complete network and also Bold 06/05/2018
his work
3 Test STP, DHCP, DNS is working or not Aditya 06/05/2018
4 Test telephone services, are working or not Ragetha 06/05/2018
5 Evaluating code of conduct Aditya 06/05/2018

Table 24.E: Task check for week 10

Week 11

Minutes (Week 11 07/05/2018)

Title Updating of network after testing

Attendees All
Apologies
Location R-block
Agenda Update the network after testing.

● Everyone will update the network which is done by

Decisions and
themselves according to the testing result.
Memos
● Make the product ready by the end of the week to
demonstrate to the client.

Table 25.E: Meeting sheet for week 11

Task Check for Last Week

Completed
Task Criteria Who Due
(Y/N)

GigaBytes Page 62
Final Project Report Version 1.1
1 Test routing protocol and HSRP Ankit 06/05/2018 Y
2 Test Quality Assurance of the complete Bold 06/05/2018 Y
network and also his work
3 Test STP, DHCP, DNS is working or not Aditya 06/05/2018 Y
4 Test telephone services, are working or Ragetha 06/05/2018 Y
not
5 Aditya 06/05/2018 Y
Evaluating code of conduct

Table 26.E: Task check for week 10

New Tasks Allocation in This Week

Tas
Description Who Due
k
1 Update The core design Ankit 13/05/2018
2 Update access-layer switch implementation Bold 13/05/2018
3 Update the firewall rules Aditya 13/05/2018
4 Update the wireless network Ragetha 13/05/2018
5 Update the schedule Ankit 13/05/2018
Table 27.E: Task check for week 11

Week 12

Minutes (Week 12 14/05/2018)

Title Demonstration to the client

Attendees All
Apologies
Location R-block-level-1
demonstrating to the client
Agenda
Divide the responsibility to individual
Decisions and Aditya will demonstrate firewall, DHCP, DNS, STP.
Memos

GigaBytes Page 63
Final Project Report Version 1.1
Ankit will demonstrate VPN, routing, HSRP, SSH.

Bold will demonstrate SNMP, AAA, ACL.

Ragetha will demonstrate syslog, telephone service and IP

plan.

Update the network after client’s comment.

Table 28.E: Meeting sheet for week 12

Task Check for Last Week

Completed
Task Criteria Who Due
(Y/N)
1 Update The core design Ankit 13/05/2018 Y
2 Update access-layer switch Bold 13/05/2018 Y
implementation
3 Update the firewall rules Aditya 13/05/2018 Y
4 Update the wireless network Ragetha 13/05/2018 Y
5 Update the schedule Ankit 13/05/2018 Y
Table 29.E: Task check for week 11

New Tasks Allocation in This Week

Tas
Description Who Due
k
1 demonstrate VPN, routing, HSRP, SSH. Ankit 20/05/2018

2 demonstrate firewall, DHCP, DNS, STP Aditya 20/05/2018

3 demonstrate SNMP, AAA, ACL Bold 20/05/2018
4 demonstrate syslog, telephone service and IP plan. Ragetha 20/05/2018

GigaBytes Page 64
Final Project Report Version 1.1
Table 30.E: Task check for week 12

Week 13

Minutes (Week 13 21/05/2018)

Title Documentation
Attendees All
Apologies
Location R-block-level-1
Documenting each person’s task
Agenda Update the cost table.
make the lesson learnt note.
Ankit will do Documentation of cost and technology report.

Bold will do Documentation of executive summary and

contribution distribution.

Aditya will do Documentation of team management and

methodology report.
Decisions and
Memos Ragetha will do Documentation of communication report and
conclusion.

Table 31.E: Meeting sheet for week 13

Task Check for Last Week

Completed
Task Criteria Who Due
(Y/N)
1 Demonstrate VPN, routing, HSRP, SSH. Ankit 20/05/2018 Y

2 Demonstrate firewall, DHCP, DNS, STP Aditya 20/05/2018 Y

GigaBytes Page 65
Final Project Report Version 1.1
3 Demonstrate SNMP, AAA, ACL Bold 20/05/2018 Y
4 Demonstrate syslog, telephone service Ragetha 20/05/2018 Y
and IP plan.

Table 32.E: Task check for week 12

New Tasks Allocation in This Week

Task Description Who Due

1 Documentation of cost and technology report. Ankit 27/05/2018

2 Documentation of executive summary and contribution Bold 27/05/2018

distribution.

3 Documentation of team management and methodology Aditya 27/05/2018

report.

4 Documentation of communication report and conclusion. Ragetha 27/05/2018

5 Make final report All 28/05/2018

Table 33.E: Task check for week 13

Appendix F
Ankit’s log sheets
Week 1
No work done on week one
Week 2

ACTIVITY LOG SHEET

Name Ankit Week 1
Activity Type (G/I) Date Start Time End Time Group Individual
Group meeting G 5/3/18 10:00 AM 11:00 AM 1
Make project charter G 6/3/18 10:00 AM 1:00 PM 3
Install required tools G 7/3/18 12:00 AM 1:00 PM 1

GigaBytes Page 66
Final Project Report Version 1.1

Total 5 0
Table 4.F: Activity log sheet

Task
Summary
Sheet Ankit patel Week: 2
Estimated Work
Remaining at Start of Hours Spent New
Stage Task Week this Week Estimate
Group team
Initiation meeting 100% 1
Make project
Initiation charter 100% 3
Install
Initiation required tools 100% 1

Cumulative Total: Total: 5

Table 5.F: Task summary log sheet

Activity Log
Summary Sheet for: Ankit Patel

Group Work Individual Work

Stage (total time) (total time)
initiation 5 0

GigaBytes Page 67
Final Project Report Version 1.1
Project Total
Time
Total Time 5 0 5
Table 6.F: Activity log summary sheet

Week 3
ACTIVITY LOG SHEET
Name ankit
Activity type date Group Individual
Document scope I 17/3/18 3
Document WBS I 17/3/18 3
Document scheduling I 17/3/18 4
Cost estimation I 16/2/18 3
Final project plan G 18/3/18 4
Total 4 13
Table 7.F: Activity log sheet

Task
Summary
Sheet Week: 3
Estimated Work
Remaining at Start of Hours Spent New
Stage Task Week this Week Estimate
Document
planning scope 3 3
Document
WBS 3 3
Document
scheduling 4 4
Cost estimation 3 3
Final project
plan 4 4

Cumulative Total: Total: 17

Table 8.F: Task summary log sheet

GigaBytes Page 68
Final Project Report Version 1.1
Activity Log
Summary Sheet for: Ankit week 3

Group Work Individual Work

Stage (total time) (total time)
planning 4 13

Project Total
Time
Total Time 4 13 17
Table 9.F: Activity log summary sheet

Week 5
ACTIVITY LOG SHEET
Name Ankit Week 5
Type Start End Grou
Activity Date Individual
(G/I) Time Time p
28/03/201
I 10:00 14:00 0 4
Design on paper 8
29/03/201
Design in packet I 15:00 17:30 0 2.5
tracer 8

Total 0 6.5
Table 10.F: Activity log sheet

GigaBytes Page 69
Final Project Report Version 1.1
Task
Summary
Sheet Ankit Week: 5
Estimated Work
Remaining at Start of Hours Spent New
Stage Task Week this Week Estimate
Design on
Design paper 4 4 0
Design in
Design packet tracer 2.5 2.5 0

Cumulative Total: Total: 6.5

Table 11.F: Task summary log sheet

Activity Log
Summary Sheet for: Ankit week 5

Group Work Individual Work

Stage (total time) (total time)
Design 0 6.5
initiation 0 0

Project Total
Time
Total Time 0 6.5 6.5
Table 12.F: Activity log summary sheet

Week 6
ACTIVITY LOG SHEET
Name Ankit Week 6

GigaBytes Page 70
Final Project Report Version 1.1
Type Start End
Activity Date Group Individual
(G/I) Time Time
5-
decide final design G 11:00 13:00 2
Apr
6-
final design in packet tracer G 16:00 20:00 4 0
Apr
Design approval from 7-
G 16:00 17:00 1 0
supervisor Apr

Total 7 0
Table 13.F: Activity log sheet

Task
Summary
Sheet Ankit Week: 6
Estimated Work
Remaining at Start of Hours Spent New
Stage Task Week this Week Estimate
Design decide final design 2 2 0
final design in
packet tracer 4 4
Design approval
from supervisor 1 1

Cumulative Total: Total: 7

GigaBytes Page 71
Final Project Report Version 1.1
Table 14.F: Task summary log sheet

Activity Log
Summary Sheet for: Ankit week 6

Group Work Individual Work

Stage (total time) (total time)
Design 7 0

Project Total
Time
Total Time 7 0 7
Table 15.F: Activity log summary sheet

Week 7
ACTIVITY LOG SHEET
Name ankit Week 7
Type Start End
Activity Date Group Individual
(G/I) Time Time
Core layer 3 switch
I 10/04/2018 12:00 19:00 8
configuration
Monitor schedule I 12/04/2018 12:00 16:00 4

Total 0 12
Table 16.F: Activity log sheet

GigaBytes Page 72
Final Project Report Version 1.1
Task
Summary
Sheet Ankit Week: 7
Estimated Work
Remaining at Start of Hours Spent New
Stage Task Week this Week Estimate
Layer 3 core switch
Implementation configuration 8 8 0
Monitor and update
Monitoring schedule 4 4

Cumulative Total: Total: 12

Table 17.F: Task summary log sheet

Activity Log
Summary Sheet for: Ankit week 2

Group Work Individual Work

Stage (total time) (total time)
Implementation 0 8
Monitoring 4

Project Total
Time
Total Time 0 12 12
Table 18.F: Activity log summary sheet

Week 8
ACTIVITY LOG SHEET

GigaBytes Page 73
Final Project Report Version 1.1
Name Ankit Week 8
Activity Type (G/I) Date Start Time End Time Group Individual
I 18/04/2018 10:00 18:00 0 8
Implement OSPF, HSRP
Implement SSH, IPSEC I 19/04/2018 12:00 20:00 0 8
Monitor schedule I 20/4/2018 13:00 18:00 4

Total 0 20
Table 19.F: Activity log sheet

Task
Summary
Sheet ankit Week: 8
Estimated Work
Remaining at Start of Hours Spent New
Stage Task Week this Week Estimate
Implement OSPF,
Implantation HSRP 8 8 0
Implement SSH,
Implantation IPSEC 8 8 0
Update and
Monitoring monitor schedule 4 4 0

Cumulative Total: Total: 20

Table 20.F: Task summary log sheet

GigaBytes Page 74
Final Project Report Version 1.1
Activity Log
Summary Sheet for: Ankit week 8

Group Work Individual Work

Stage (total time) (total time)
Implementation 0 16
Monitoring and controlling 4

Project Total
Time
Total Time 0 20 20
Table 21.F: Activity log summary sheet

Week 9
ACTIVITY LOG SHEET
Name Ankit Week 9
Type Start End
Activity Date Group Individual
(G/I) Time Time
Implement final
I 24/4/2018 12:00 4:00 0 4
configuration
Update the schedule I 26/4/2018 10:00 16:00 0 6

Total 0 10
Table 22.F: Activity log sheet

GigaBytes Page 75
Final Project Report Version 1.1
Task
Summary
Sheet Ankit Week: 9
Estimated Work
Remaining at Start of Hours Spent New
Stage Task Week this Week Estimate
Implement final
configuration assigned
Implementation to me 4 4 0
update the project
Monitoring schedule 6 6 0

Cumulative
Total: Total: 10
Table 23.F: Task summary log sheet

Activity Log
Summary Sheet for: Ankit 9

Group Work Individual Work

Stage (total time) (total time)
Implementation 0 4
Monitoring 0 6

Project Total
Time
Total Time 0 10 10
Table 24.F: Activity log summary sheet

GigaBytes Page 76
Final Project Report Version 1.1
Week 10
ACTIVITY LOG SHEET
Name Ankit Week 10
Type Start End
Activity Date Group Individual
(G/I) Time Time
Test Routing, HSRP, IPSEC,
I 01/05/2018 12:00 19:00 0 7
SSH

Total 0 7
Table 25.F: Activity log sheet

Task
Summary
Sheet Ankit Week: 10
Estimated Work
Remaining at Start of Hours Spent New
Stage Task Week this Week Estimate
Test Routing, HSRP,
Testing IPSEC, SSH 7 7 0

GigaBytes Page 77
Final Project Report Version 1.1
Cumulative
Total: Total: 7
Table 26.F: Task summary log sheet

Activity Log
Summary Sheet for: Ankit week 10

Group Work Individual Work

Stage (total time) (total time)
Testing 0 7

Project Total
Time
Total Time 0 7 7
Table 27.F: Activity log summary sheet

Week 11
ACTIVITY LOG SHEET
Name Ankit Week 11
Activity Type (G/I) Date Start Time End Time Group Individual
Update the core design I 8/5 12:00 15:30 0 3.5
Update schedule I 13/5 12:00 13:00 0 1

Total 0 4.5
Table 28.F: Activity log sheet

GigaBytes Page 78
Final Project Report Version 1.1
Task
Summary
Sheet Ankit Week: 11
Estimated Work
Remaining at Start of Hours Spent New
Stage Task Week this Week Estimate
Update the core
Monitoring and design and
controlling dependency 3.5 3.5 0
Monitoring and
controlling update schedule 1 1 0

Cumulative Total: Total: 4.5

Table 29.F: Task summary log sheet

Activity Log
Summary Sheet for: Ankit week 11

Group Work Individual Work

Stage (total time) (total time)
Monitoring and controlling 0 4.5

Project Total
Time
Total Time 0 4.5 4.5
Table 30.F: Activity log summary sheet

Week 12
ACTIVITY LOG SHEET

GigaBytes Page 79
Final Project Report Version 1.1
Name Ankit Week 12
Type Start End
Activity Date Group Individual
(G/I) Time Time
Demonstrate IPSEC, SSH,
I 15/5/2018 16:00 18:00 2
routing protocol and HSRP

Total 2 0
Table 31.F: Activity log sheet

Task
Summary
Sheet Ankit Week: 12
Estimated Work Hours
Remaining at Start Spent this New
Stage Task of Week Week Estimate
Demonstration of IPSEC,
Closing HSRP, SSH and routing 2 2 0

Cumulative
Total: Total: 2
Table 32.F: Task summary log sheet

GigaBytes Page 80
Final Project Report Version 1.1

Activity Log
Summary Sheet for: Ankit week 12

Group Work Individual Work

Stage (total time) (total time)
Closing 2 0

Project Total
Time
Total Time 2 0 2
Table 33.F: Activity log summary sheet

Week 13
ACTIVITY LOG SHEET
Name Ankit Week 13
Type Start End
Activity Date Group Individual
(G/I) Time Time
Documentation of cost and
I 24/5/2018 12:00 19:00 8
technology used
Document final report G 28/5/2018 10:00 12:00 4

Total 4 8
Table 34.F: Activity log sheet

GigaBytes Page 81
Final Project Report Version 1.1
Task
Summary
Sheet Ankit Week: 13
Estimated Work
Remaining at Start of Hours Spent New
Stage Task Week this Week Estimate
Document the cost
Closing and technology used 8 8 0
Document final
Closing report 4 4

Cumulative Total: Total: 12

Table 35.F: Task summary log sheet

Activity Log
Summary Sheet for: Ankit week 13

Group Work Individual Work

Stage (total time) (total time)
closing 4 8

Project Total
Time
Total Time 4 8 12
Table 36.F: Activity log summary sheet

Bold’s log sheets

Week 1

GigaBytes Page 82
Final Project Report Version 1.1
There is no work done in week 1

Week 2

ACTIVITY LOG SHEET

Name Bold
Activity type date Group Individual
Group team meeting G 17/3/18 1
Make project charter G 17/3/18 2
Install required tools G 17/3/18 2

Total 5
Table 40.F: Activity log sheet

Task
Summary
Sheet Bold Week: 2
Estimated Work
Remaining at Start of Hours Spent New
Stage Task Week this Week Estimate
Group team
Initiation meeting 100% 1
Make project
Initiation charter 100% 3
Install
Initiation required tools 100% 1

Cumulative Total: Total: 5

Table 41.F: Task summary log sheet

Activity Log
Summary Sheet for: Bold

Group Work Individual Work

Stage (total time) (total time)
initiation 5 0

GigaBytes Page 83
Final Project Report Version 1.1

Project Total
Time
Total Time 5 0 5
Table 42.F: Activity log summary sheet

Week 3

ACTIVITY LOG SHEET

Name Bold
Activity type date Group Individual
Make quality management plan I 3/12/2018 0 8.5

Final project plan G 3/18/2018 4

Total 4 8.5
Table 43.F: Activity log sheet

Task
Summary
Sheet Bold Week: 3
Estimated Work
Remaining at Start of Hours Spent New
Stage Task Week this Week Estimate
Make quality
planning management plan 8.5 8.5

Final project plan 4 4

Cumulative Total: Total: 12.5

Table 44.F: Task summary log sheet

GigaBytes Page 84
Final Project Report Version 1.1
Activity Log
Summary Sheet for: Bold week 3

Group Work Individual Work

Stage (total time) (total time)
planning 4 8.5

Project Total
Time
Total Time 4 8.5 12.5
Table 45.F: Activity log summary sheet

Week 5
ACTIVITY LOG SHEET
Name Bold Week 5
Type Start End Grou Individua
Activity Date
(G/I) Time Time p l
28/03/201
I 10:00 14:00 0 4
Design on paper 8
29/03/201
Design in packet I 15:00 17:30 0 2.5
tracer 8

Total 0 6.5
Table 46.F: Activity log sheet

GigaBytes Page 85
Final Project Report Version 1.1
Task
Summary
Sheet Bold Week: 5
Estimated Work
Remaining at Start of Hours Spent New
Stage Task Week this Week Estimate
Design on
Design paper 4 4 0
Design in
Design packet tracer 2.5 2.5 0

Cumulative Total: Total: 6.5

Table 47.F: Task summary log sheet

Activity Log
Summary Sheet for: Bold week 5

Group Work Individual Work

Stage (total time) (total time)
Design 0 6.5
initiation 0 0

Project Total
Time
Total Time 0 6.5 6.5
Table 48.F: Activity log summary sheet

Week 6
ACTIVITY LOG SHEET
Name Bold Week 6

GigaBytes Page 86
Final Project Report Version 1.1
Type Start End
Activity Date Group Individual
(G/I) Time Time
5-
decide final design G 11:00 13:00 2
Apr
6-
final design in packet tracer G 16:00 20:00 4 0
Apr
Design approval from 7-
G 16:00 17:00 1 0
supervisor Apr

Total 7 0
Table 49.F: Activity log sheet

Task
Summary
Sheet Bold Week: 6
Estimated Work
Remaining at Start of Hours Spent New
Stage Task Week this Week Estimate
Design decide final design 2 2 0
final design in
packet tracer 4 4
Design approval
from supervisor 1 1

Cumulative Total: Total: 7

GigaBytes Page 87
Final Project Report Version 1.1
Table 50.F: Task summary log sheet

Activity Log
Summary Sheet for: Bold week 6

Group Work Individual Work

Stage (total time) (total time)
Design 7 0

Project Total
Time
Total Time 7 0 7
Table 51.F: Activity log summary sheet

Week 7
ACTIVITY LOG SHEET
Name Bold Week 7
Type Start End
Activity Date Group Individual
(G/I) Time Time
Access-layer switch
I 19/04/2018: 12:00 18:00 6
configuration
Quality assurance I 21/04/2018: 12:00 15:00 3

Total 0 9
Table 52.F: Activity log sheet

GigaBytes Page 88
Final Project Report Version 1.1
Task
Summary
Sheet Bold Week: 7
Estimated Work
Remaining at Start of Hours Spent New
Stage Task Week this Week Estimate
Access-layer switch
Implementation configuration 6 6 0
Monitoring Quality assurance 3 3

Cumulative Total: Total: 9

Table 53.F: Task summary log sheet

Activity Log
Summary Sheet for: Bold week 7

Group Work Individual Work

Stage (total time) (total time)
Implementation 0 6
Monitoring 3

Project Total
Time
Total Time 0 9 9
Table 54.F: Activity log summary sheet

Week 8
ACTIVITY LOG SHEET
Name Bold Week 8

GigaBytes Page 89
Final Project Report Version 1.1
Type Start End
Activity Date Group Individual
(G/I) Time Time
Implement AAA, ACL, SNMP,
Frame-relay protocols on I 17/04/2018: 10:00 16:00 0 6
network
Quality assurance I 17/04/2018: 16:00 19:00 0 3

Total 0 9
Table 55.F: Activity log sheet

Task
Summary
Sheet Bold Week: 8
Estimated Work Hours
Remaining at Start Spent this New
Stage Task of Week Week Estimate
Implement AAA, ACL,
SNMP, Frame-relay
Implantation protocols on network 6 6 0
Monitoring Quality assurance 3 3 0

Cumulative
Total: Total: 9

GigaBytes Page 90
Final Project Report Version 1.1
Table 56.F: Task summary log sheet

Activity Log
Summary Sheet for: Bold week 8

Group Work Individual Work

Stage (total time) (total time)
Implementation 0 6
Monitoring and controlling 3

Project Total
Time
Total Time 0 9 9
Table 57.F: Activity log summary sheet

Week 9
ACTIVITY LOG SHEET
Name Bold Week9
Activity Type (G/I) Date Start Time End Time Group Individual
Quality assurance I 21/04/2018: 12:00 6:00 0 6

Total 0 6
Table 58.F: Activity log sheet

GigaBytes Page 91
Final Project Report Version 1.1
Task
Summary
Sheet Bold Week: 9
Estimated Work
Remaining at Start of Hours Spent New
Stage Task Week this Week Estimate
Quality
Monitoring assurance 6 6 0

Cumulative Total: Total: 6

Table 59.F: Task summary log sheet

Activity Log
Summary Sheet for: Bold week 9

Group Work Individual Work

Stage (total time) (total time)

Monitoring 0 6

Project Total
Time
Total Time 0 6 6
Table 60.F: Activity log summary sheet

Week 10
ACTIVITY LOG SHEET
Name Bold Week10

GigaBytes Page 92
Final Project Report Version 1.1
Type Start End
Activity Date Group Individual
(G/I) Time Time
Test Quality Assurance of the
complete network and also his I 5/01/2018: 12:00 18:00 0 6
work

Total 0 6
Table 61.F: Activity log sheet

Task
Summary
Sheet Bold Week: 10
Estimated Work
Remaining at Start Hours Spent New
Stage Task of Week this Week Estimate
test Quality Assurance of
the complete network and
Testing also his work 6 6 0

Cumulative
Total: Total: 6

GigaBytes Page 93
Final Project Report Version 1.1
Table 62.F: Task summary log sheet

Activity Log
Summary Sheet for: Bold week 10

Group Work Individual Work

Stage (total time) (total time)
Testing 0 6

Project Total
Time
Total Time 0 6 6
Table 63.F: Activity log summary sheet

Week 11
ACTIVITY LOG SHEET
Week
Name Bold 11
11
Type Start End
Activity Date Group Individual
(G/I) Time Time
Update access-layer switch
I 10/05/18: 10:00 16:00 0 6
implementation

Total 0 6
Table 64.F: Activity log sheet

GigaBytes Page 94
Final Project Report Version 1.1
Task
Summary
Sheet Bold Week: 11
Estimated Work
Remaining at Start of Hours Spent New
Stage Task Week this Week Estimate
Update access-layer
Implementation switch implementation 6 6 0

Cumulative
Total: Total: 6
Table 65.F: Task summary log sheet

Activity Log
Summary Sheet for: Bold week 11

Group Work Individual Work

Stage (total time) (total time)
Monitoring and controlling 0 6

Project Total
Time
Total Time 0 6 6
Table 66.F: Activity log summary sheet

Week 12
ACTIVITY LOG SHEET
Name Bold Week 12

GigaBytes Page 95
Final Project Report Version 1.1
Type Start End
Activity Date Group Individual
(G/I) Time Time
demonstrate SNMP,
I 16/05/2018: 10:00 18:00 8
AAA,ACL

Total 0 8
Table 67.F: Activity log sheet

Task
Summary
Sheet Bold Week: 12
Estimated Work
Remaining at Start of Hours Spent New
Stage Task Week this Week Estimate
demonstrate
Closing SNMP, AAA, ACL 8 8 0

Cumulative Total: Total: 8

Table 68.F: Task summary log sheet

GigaBytes Page 96
Final Project Report Version 1.1
Activity Log
Summary Sheet for: Bold week 12

Group Work Individual Work

Stage (total time) (total time)
Closing 0 8

Project Total
Time
Total Time 0 8 8
Table 69.F: Activity log summary sheet

Week 13
ACTIVITY LOG SHEET
Name Bold Week 13
Type Start End
Activity Date Group Individual
(G/I) Time Time
Documentation of executive
summary and contribution I 24/05/2018: 10:00 18:00 8
distribution.
Document final report G 28/5/2018 10:00 12:00 4

Total 4 8
Table 70.F: Activity log sheet

GigaBytes Page 97
Final Project Report Version 1.1
Task
Summary
Sheet Bold Week: 13
Estimated Work Hours
Remaining at Start Spent this New
Stage Task of Week Week Estimate
Documentation of executive
summary and contribution
Closing distribution. 8 8 0
Closing Document final report 4 4

Cumulative
Total: Total: 12
Table 71.F: Task summary log sheet

Activity Log
Summary Sheet for: Bold week 13

Group Work Individual Work

Stage (total time) (total time)
closing 4 8

Project Total
Time
Total Time 4 8 12
Table 72.F: Activity log summary sheet

GigaBytes Page 98
Final Project Report Version 1.1

Ragetha’s log sheets

Week 1
There is no work done in week 1

Week 2

ACTIVITY LOG SHEET

Name Week 2
Activity Type (G/I) Date Start Time End Time Group Individual
Group meeting G 5/3/18 10:00 AM 11:00 AM 1
Make project charter G 6/3/18 10:00 AM 1:00 PM 3
Install required tools G 7/3/18 12:00 AM 1:00 PM 1

Total 5 0
Table 73.F: Activity log sheet

Task
Summary
Sheet Ragetha Week: 2
Estimated Work
Remaining at Start of Hours Spent New
Stage Task Week this Week Estimate
Group team
Initiation meeting 100% 1
Make project
Initiation charter 100% 3
Install
Initiation required tools 100% 1

GigaBytes Page 99
Final Project Report Version 1.1
Cumulative Total: Total: 5
Table 74.F: Task summary log sheet

Activity Log
Summary Sheet for: Ragetha

Group Work Individual Work

Stage (total time) (total time)
initiation 5 0

Project Total
Time
Total Time 5 0 5
Table 75.F: Activity log summary sheet

Week 3
ACTIVITY LOG SHEET
Name Ragetha
Activity type date Group Individual
Document communication plans I 3/13/2018 4

Final project plan G 18/3/18 4

Total 4 4
Table 79.F: Activity log sheet

Task
Summary
Sheet Ragetha Week: 3
Estimated Work
Remaining at Start of Hours Spent New
Stage Task Week this Week Estimate

GigaBytes Page 100

Final Project Report Version 1.1
Document
planning communication plans 4 4

Final project plan 4 4

Cumulative Total: Total: 8

Table 80.F: Task summary log sheet

Activity Log Ragetha week

Summary Sheet for: 3

Group Work Individual Work

Stage (total time) (total time)
planning 4 4

Project Total
Time
Total Time 4 4 8
Table 81.F: Activity log summary sheet

Week 5
ACTIVITY LOG SHEET
Name Ragetha Week 5
Activity Type (G/I) Date Start Time End Time Group Individual
Design on paper I 28/03/2018 10:00 14:00 0 4
Design in packet tracer I 29/03/2018 15:00 17:30 0 2.5

GigaBytes Page 101

Final Project Report Version 1.1

Total 0 6.5
Table 82.F: Activity log sheet

Task
Summary
Sheet Ragetha Week: 5
Estimated Work
Remaining at Start of Hours Spent New
Stage Task Week this Week Estimate
Design on
Design paper 4 4 0
Design in
Design packet tracer 2.5 2.5 0

Cumulative Total: Total: 6.5

Table 83.F: Task summary log sheet

Activity Log Ragetha week

Summary Sheet for: 5

Group Work Individual Work

Stage (total time) (total time)
Design 0 6.5
initiation 0 0

GigaBytes Page 102

Final Project Report Version 1.1

Project Total
Time
Total Time 0 6.5 6.5
Table 84.F: Activity log summary sheet

Week 6
ACTIVITY LOG SHEET
Name Ragetha Week 6
Type Start End
Activity Date Group Individual
(G/I) Time Time
5-
decide final design G 11:00 13:00 2
Apr
6-
final design in packet tracer G 16:00 20:00 4 0
Apr
Design approval from 7-
G 16:00 17:00 1 0
supervisor Apr

Total 7 0
Table 85.F: Activity log sheet

Task
Summary
Sheet Ragetha Week: 6
Estimated Work
Remaining at Start of Hours Spent New
Stage Task Week this Week Estimate
Design decide final design 2 2 0
final design in
packet tracer 4 4
Design approval
from supervisor 1 1

GigaBytes Page 103

Final Project Report Version 1.1

Cumulative Total: Total: 7

Table 86.F: Task summary log sheet

Activity Log Ragetha week

Summary Sheet for: 6

Group Work Individual Work

Stage (total time) (total time)
Design 7 0

Project Total
Time
Total Time 7 0 7
Table 87.F: Activity log summary sheet

Week 7
ACTIVITY LOG SHEET
Name Ragetha Week 7
Type Start End
Activity Date Group Individual
(G/I) Time Time
WLC configuration I 17/04/2018: 12:00 20:00 8
Communication
I 17/04/2018: 12:00 16:00 4
management

GigaBytes Page 104

Final Project Report Version 1.1

Total 0 12
Table 88.F: Activity log sheet

Task
Summary
Sheet Ragetha Week: 7
Estimated Work
Remaining at Start of Hours Spent New
Stage Task Week this Week Estimate
Implementation WLC configuration 8 8 0
Communication
Monitoring management 4 4

Cumulative Total: Total: 12

Table 89.F: Task summary log sheet

Activity Log Ragetha week

Summary Sheet for: 7

Group Work Individual Work

Stage (total time) (total time)
Implementation 0 8
Monitoring 4

Project Total
Time
Total Time 0 12 12

GigaBytes Page 105

Final Project Report Version 1.1
Table 90.F: Activity log summary sheet

Week 8
ACTIVITY LOG SHEET
Name Ragetha Week 8
Type Start End
Activity Date Group Individual
(G/I) Time Time
Implement Netflow, WiFi, syslog,
telephony services protocols on
I 18/04/2018 10:00 18:00 0 8
network
Implement OSPF, HSRP
Communication management I 19/04/2018 10:00 18:00 0 8

Total 0 16
Table 91.F: Activity log sheet

Task
Summary
Sheet Ragetha Week: 8
Estimated Work Hours
Remaining at Start Spent this New
Stage Task of Week Week Estimate
Implement Netflow, WiFi,
syslog, telephony services
Implementation protocols on network 6 6 0

Monitoring Communication management 4 4 0

GigaBytes Page 106

Final Project Report Version 1.1

Cumulative
Total: Total: 10
Table 92.F: Task summary log sheet

Activity Log Ragetha week

Summary Sheet for: 8

Group Work Individual Work

Stage (total time) (total time)
Implementation 0 6
Monitoring and controlling 4

Project Total
Time
Total Time 0 10 10
Table 93.F: Activity log summary sheet

Week 9
ACTIVITY LOG SHEET
Name Ragetha Week 9
Type Start End
Activity Date Group Individual
(G/I) Time Time
Implement final
I 22/04/2018: 12:00 4:00 0 4
configuration
Communication
I 21/4/2018: 10:00 16:00 0 6
management

GigaBytes Page 107

Final Project Report Version 1.1

Total 0 10
Table 94.F: Activity log sheet

Task
Summary
Sheet Ragetha Week: 9
Estimated Work
Remaining at Start of Hours Spent New
Stage Task Week this Week Estimate
Implement final
Implementation configuration 4 4 0
Communication
Monitoring management 6 6 0

Cumulative Total: Total: 10

Table 95.F: Task summary log sheet

Activity Log Ragetha

Summary Sheet for: week9

Group Work Individual Work

Stage (total time) (total time)
Implementation 0 4
Monitoring 0 6

Project Total
Time
Total Time 0 10 10
Table 96.F: Activity log summary sheet

GigaBytes Page 108

Final Project Report Version 1.1
Week 10
ACTIVITY LOG SHEET
Name Ragetha Week 10
Type Start End
Activity Date Group Individual
(G/I) Time Time
test telephone services, are
I 5/03/2018: 12:00 19:00 0 7
working or not

Total 0 7
Table 97.F: Activity log sheet

Task
Summary
Sheet Ragetha Week: 10
Estimated Work
Remaining at Start of Hours Spent New
Stage Task Week this Week Estimate
test telephone
services, are working
Testing or not 7 7 0

GigaBytes Page 109

Final Project Report Version 1.1
Cumulative Total: Total: 7
Table 98.F: Task summary log sheet

Activity Log Ragetha week

Summary Sheet for: 10

Group Work Individual Work

Stage (total time) (total time)
Testing 0 7

Project Total
Time
Total Time 0 7 7
Table 99.F: Activity log summary sheet

Week 11
ACTIVITY LOG SHEET
Name Ragetha Week 11
Type Start End
Activity Date Group Individual
(G/I) Time Time
Update the wireless
I 11/05/18: 12:00 15:00 0 3
network

Total 0 3
Table 100.F: Activity log sheet

GigaBytes Page 110

Final Project Report Version 1.1

Task
Summary
Sheet Ragetha Week: 11
Estimated Work
Remaining at Start of Hours Spent New
Stage Task Week this Week Estimate
Update the
Monitoring and wireless
controlling network 3 3 0

Cumulative Total: Total: 3

Table 101.F: Task summary log sheet

Activity Log Ragetha week

Summary Sheet for: 11

Group Work Individual Work

Stage (total time) (total time)
Monitoring and controlling 0 3

Project Total
Time
Total Time 0 3 3
Table 102.F: Activity log summary sheet

Week 12
ACTIVITY LOG SHEET
Name Ragetha Week 12

GigaBytes Page 111

Final Project Report Version 1.1
Type Start End
Activity Date Group Individual
(G/I) Time Time
Demonstrate syslog, telephone
I 15/5/2018 16:00 18:00 2
service and IP plan.

Total 2 0
Table 103.F: Activity log sheet

Task
Summary
Sheet Ragetha Week: 12
Estimated Work
Remaining at Start of Hours Spent New
Stage Task Week this Week Estimate
Demonstrate syslog,
telephone service and IP
Closing plan. 2 2 0

Cumulative
Total: Total: 2
Table 104.F: Task summary log sheet

GigaBytes Page 112

Final Project Report Version 1.1

Activity Log Ragetha week

Summary Sheet for: 12

Group Work Individual Work

Stage (total time) (total time)
Closing 2 0

Project Total
Time
Total Time 2 0 2
Table 105.F: Activity log summary sheet

Week 13
ACTIVITY LOG SHEET
Name Ragehta Week
Type Start End
Activity Date Group Individual
(G/I) Time Time
Documentation of
communication report and I 24/5/2018 12:00 19:30 8.5
conclusion.
Document final report G 28/5/2018 10:00 12:00 4

Total 4 8.5
Table 106.F: Activity log sheet

GigaBytes Page 113

Final Project Report Version 1.1

Task
Summary
Sheet Ragetha Week: 13
Estimated Work Hours
Remaining at Start Spent this New
Stage Task of Week Week Estimate
Documentation of
communication report and
Closing conclusion. 8.5 8.5 0
Closing Document final report 4 4

Cumulative
Total: Total: 12.5
Table 107.F: Task summary log sheet

Activity Log Ragetha week

Summary Sheet for: 13

Group Work Individual Work

Stage (total time) (total time)
closing 4 8.5

Project Total
Time
Total Time 4 8.5 12.5
Table 108.F: Activity log summary sheet

Aditya’s log sheets

GigaBytes Page 114

Final Project Report Version 1.1
Week 1

There is no work done on week 1

Week 2
ACTIVITY LOG SHEET
Name Week 2
Activity Type (G/I) Date Start Time End Time Group Individual
Group meeting G 5/3/18 10:00 AM 11:00 AM 1
Make project charter G 6/3/18 10:00 AM 1:00 PM 3
Install required tools G 7/3/18 12:00 AM 1:00 PM 1

Total 5 0
Table 109.F: Activity log sheet

Task
Summary
Sheet Adi Week: 2
Estimated Work
Remaining at Start of Hours Spent New
Stage Task Week this Week Estimate
Group team
Initiation meeting 100% 1
Make project
Initiation charter 100% 3
Install
Initiation required tools 100% 1

Cumulative Total: Total: 5

Table 110.F: Task summary log sheet

GigaBytes Page 115

Final Project Report Version 1.1

Activity Log
Summary Sheet for: Adi

Group Work Individual Work

Stage (total time) (total time)
Initiation 5 0

Project Total
Time
Total Time 5 0 5
Table111.F: Activity log summary sheet

Week 3

ACTIVITY LOG SHEET

Name Aditya Week 3
Activity Type (G/I) Date Start Time End Time Group Individual
Risk management I 3/16/2018 10:00:00 AM 3:00:00 PM 0 5
Code of conduct I 3/17/2018 10:00:00 AM 1:00:00 AM 3
project plan I 3/18/2018 10:00:00 AM 02:00pm 4 0

0
0

Total 4 8
Table 115.F: Activity log sheet

Task
Summary
Sheet Aditya Week: 3

GigaBytes Page 116

Final Project Report Version 1.1
Estimated Work
Remaining at Start of Hours Spent New
Stage Task Week this Week Estimate
Risk
planning management 5 5 0
Code of
planning conduct 3 3 0
planning project plan 4 4 0

Cumulative Total: Total: 12

Table 116.F: Task summary log sheet

Activity Log
Summary Sheet for: week-3

Group Work Individual Work

Stage (total time) (total time)
planning 4 8

Project Total
Time
Total Time 4 8 12
Table 117.F: Activity log summary sheet

Week 5
ACTIVITY LOG SHEET
Name Aditya Week 5
Type
Activity Date Start Time End Time Group Individual
(G/I)
Design on paper I 3/27/2018 3:00:00 PM 7:30:00 PM 0 4.5
Design on packet 11:00:00 12:30:00
I 3/28/2018 0 1.5
tracer AM PM

GigaBytes Page 117

Final Project Report Version 1.1

Total 0 6
Table 118.F: Activity log sheet

Task
Summary
Sheet Aditya Week: 5
Estimated Work
Remaining at Start of Hours Spent New
Stage Task Week this Week Estimate
Design on
Design paper 4.5 4.5 0
Design on
Design packet tracer 1.5 1.5 0

Cumulative Total: Total: 6

Table 119.F: Task summary log sheet

Activity Log
Summary Sheet for: Week-5

Group Work Individual Work

Stage (total time) (total time)

GigaBytes Page 118

Final Project Report Version 1.1
Design 0 6

Project Total
Time
Total Time 0 6 6
Table 120.F: Activity log summary sheet

Week 6
ACTIVITY LOG SHEET
Name Aditya Week 6
Type Start End
Activity Date Group Individual
(G/I) Time Time
Final design G 4/5/2018 11:00 13:00 2 0
Packet tracer design G 4/6/2018 16:00 20:00 4 0
Approval from
G 4/7/2018 16:00 17:00 1 0
supervisor

Total 7 0
Table 121.F: Activity log sheet

Task
Summary
Sheet Aditya Week: 6
Estimated Work
Remaining at Start of Hours Spent New
Stage Task Week this Week Estimate
Design Final design 2 2 0
Packet tracer
Design design 4 4 0

GigaBytes Page 119

Final Project Report Version 1.1
Approval from
Approval supervisor 1 1 0

Cumulative Total: Total: 7

Table 122.F: Task summary log sheet

Activity Log
Summary Sheet for: week-6

Group Work Individual Work

Stage (total time) (total time)
Design/Approval 7 0

Project Total
Time
Total Time 7 0 7
Table 123.F: Activity log summary sheet

Week 7
ACTIVITY LOG SHEET
Name Aditya Week 7
Type Start End
Activity Date Group Individual
(G/I) Time Time
Firewall configuration I 4/12/2018 16:00 22:00 0 6.5
Monitoring team
I 4/13/2018 16:00 20:00 0 4
management and risk

GigaBytes Page 120

Final Project Report Version 1.1

Total 0 10.5
Table 124.F: Activity log sheet

Task
Summary
Sheet Aditya Week: 7
Estimated Work
Remaining at Start of Hours Spent New
Stage Task Week this Week Estimate
Implementation Firewall configuration 5 6.5 0
Monitoring team
Monitoring management and risk 3 4 0

Cumulative
Total: Total: 10.5
Table 125.F: Task summary log sheet

Activity Log
Summary Sheet for: week-7

Group Work Individual Work

Stage (total time) (total time)

implementation 6.5
Monitoring 4

GigaBytes Page 121

Final Project Report Version 1.1

Project Total
Time
Total Time 0 10.5 10.5
Table 126.F: Activity log summary sheet

Week 8
ACTIVITY LOG SHEET
Name Aditya Week 8
Type Start End
Activity Date Group Individual
(G/I) Time Time
Implementing STP, DHCP I 4/19/2018 10:00 18:00 0 8
Implementing DNS, NAT I 4/20/2018 14:00 22:00 0 8
Monitoring Risks, Design,
I 4/21/2018 16:00 20:00 0 4
Team management

Total 0 20
Table 127.F: Activity log sheet

Task
Summary
Sheet Aditya Week: 8
Estimated Work
Remaining at Start of Hours Spent New
Stage Task Week this Week Estimate
Implementing STP,
Implementation DHCP 8 8 0
Implementing DNS,
Implementation NAT 7 8
Monitoring Risks,
Design, Team
Monitoring management 3 4 0

GigaBytes Page 122

Final Project Report Version 1.1

Cumulative
Total: Total: 20
Table 128.F: Task summary log sheet

Activity Log
Summary Sheet for: week-8

Group Work Individual Work

Stage (total time) (total time)
Implementation 0 16
Monitoring 0 4

Project Total
Time
Total Time 0 20 20
Table 129.F: Activity log summary sheet

Week 9
ACTIVITY LOG SHEET
Name Aditya Week 9
Type Start End
Activity Date Group Individual
(G/I) Time Time
Finish the final implementation
I 4/24/2018 16:00 20:00 0 4
for testing
Risk assessment I 4/26/2018 20:00 22:00 0 2
Monitoring Risks, Design,
I 4/27/2018 16:00 20:00 0 4
Team management

GigaBytes Page 123

Final Project Report Version 1.1

Total 0 10
Table 130.F: Activity log sheet

Task
Summary
Sheet Aditya Week: 9
Estimated Work
Remaining at Start of Hours Spent New
Stage Task Week this Week Estimate
Finish the final
implementation for
Implementation testing 4 4 0
Assessment Risk assessment 2 2 0
Monitoring Risks,
Design, Team
Monitoring management 3 4 0

Cumulative
Total: Total: 10
Table 131.F: Task summary log sheet

Activity Log
Summary Sheet for: week-9

Group Work Individual Work

Stage (total time) (total time)
Implementation 0 4
Assessment 0 2
Monitoring 0 4

GigaBytes Page 124

Final Project Report Version 1.1

Project Total
Time
Total Time 0 10 10
Table 132.F: Activity log summary sheet

Week 10
ACTIVITY LOG SHEET
Name Aditya Week 10
Activity Type (G/I) Date Start Time End Time Group Individual
Test STP, DHCP I 5/1/2018 12:00 16:00 0 4
Test DNS, NAT I 5/1/2018 16:00 21:30 0 2.5
Code of conduct I 5/4/2018 10:00 11:30 0 1.5

Total 0 8
Table 133.F: Activity log sheet

Task Summary
Sheet Aditya Week: 10
Estimated Work
Remaining at Start of Hours Spent New
Stage Task Week this Week Estimate
Test STP,
Testing DHCP 4 4 0
Test DNS,
Testing NAT 3 2.5 0
Code of
Evaluating conduct 1 1.5 0

GigaBytes Page 125

Final Project Report Version 1.1

Cumulative Total: Total: 8

Table 134.F: Task summary log sheet

Activity Log
Summary Sheet for: week-10

Group Work Individual Work

Stage (total time) (total time)
Testing 0 8

Project Total
Time
Total Time 0 8 8
Table 135.F: Activity log summary sheet

Week 11
ACTIVITY LOG SHEET
Name Aditya Week 11
Activity Type (G/I) Date Start Time End Time Group Individual
Update the firewall rules I 5/9/2018 16:00 18:30 0 2.5

Total 0 2.5

GigaBytes Page 126

Final Project Report Version 1.1
Table 136.F: Activity log sheet

Task
Summary
Sheet Aditya Week: 11
Estimated Work
Remaining at Start of Hours Spent New
Stage Task Week this Week Estimate
Update the
Updating firewall rules 3 2.5 0

Cumulative Total: Total: 2.5

Table 137.F: Task summary log sheet

Activity Log
Summary Sheet for: 11

Group Work Individual Work

Stage (total time) (total time)
Updating 0 2.5

Project Total
Time
Total Time 0 2.5 2.5
Table 138.F: Activity log summary sheet

Week 12
ACTIVITY LOG SHEET

GigaBytes Page 127

Final Project Report Version 1.1
Name Aditya Week 12
Type Start End
Activity Date Group Individual
(G/I) Time Time
Demonstrate DHCP, DNS,
G 5/15/2018 16:00 18:00 2 0
STP, NAT

Total 2 0
Table 139.F: Activity log sheet

Task
Summary
Sheet Aditya Week: 12
Estimated Work
Remaining at Start of Hours Spent New
Stage Task Week this Week Estimate
Demonstrate DHCP,
Closing DNS, STP, NAT 2 2 0

Cumulative Total: Total: 2

Table 140.F: Task summary log sheet

GigaBytes Page 128

Final Project Report Version 1.1

Activity Log
Summary Sheet for: week-12

Group Work Individual Work

Stage (total time) (total time)
Closing 2 0

Project Total
Time
Total Time 2 0 2
Table 141.F: Activity log summary sheet

Week 13
ACTIVITY LOG SHEET
Name Aditya Week 13
Type Start End
Activity Date Group Individual
(G/I) Time Time
Documentation of Team and
I 5/25/2018 16:00 24:00:00 0 8
methodology report
Final documentation G 5/28/2018 10:00 12:00 4 0

Total 4 8
Table 142.F: Activity log sheet

Task
Summary
Sheet Aditya Week: 13

GigaBytes Page 129

Final Project Report Version 1.1
Estimated Work
Remaining at Start Hours Spent New
Stage Task of Week this Week Estimate
Documentation of Team
Closing and methodology report 10 8 0
Closing Final documentation 4 4 0

Cumulative
Total: Total: 12
Table 143.F: Task summary log sheet

Activity Log
Summary Sheet for: week-13

Group Work Individual Work

Stage (total time) (total time)
Closing 4 8

Project Total
Time
Total Time 4 8 12
Table 144.F: Activity log summary sheet

GigaBytes Page 130