Polytelecom Networking PBL Project Report

Bachelor of ICT Assessment Cover Sheet
Assessment Title:
Poly Telecom Networking PBL Project Report
Programme Title:
Bachelor of ICT
Course code:
ITB6003
Course Title:
Networking and Data Communication 2
Student Names:
Ali Alaali - Habib Khamis - Ahmed Saeed
Student IDs:
201000096 - 201000129 - 201000413
Tutor:
Sunil Seneviratne
Due Date: 13th June, 2013
Date submitted: 13th June, 2013
By submitting this assessment for marking, either electronically or as hard copy, we confirm the
following:
This assignment is our own work.

Any information used has been properly referenced.
We understand that a copy of our work may be used for moderation.
We have kept a copy of this assignment.
Assessor:
Grade/Mark:
Comments:
Date of Marking:

201000096 - 201000129 - 2010000413
Sunil Seneviratne
13th June, 2013
Title
The title of this report is Poly Telecom Networking PBL Project Report. The
authors of this report are: Ali Alaali, Habib Khamis and Ahmed Saeed. Also, the
submitted date of this project is 9th June, 2013.
Abstract
Initially, a private IPv4 addressing scheme has been implemented for the Poly
Telecom Company with proper routing protocol Open Shortest Path First (OSPF).
Secondly, for each site and each department in Poly Telecom Company, Virtual Local
Area Networks (VLANs) have been created. Thirdly, each site has been applied with
wireless access routers. After that, a data link layer encapsulation method has been
implemented on serial links between Network Operations Centre (NOC) and the
Internet Service Provider (ISP) which is Bahrain Internet Exchange (BIX). Then, a Wide
Area Network (WAN) technology, which provides Permanent Virtual Circuits (PVCs)
between the sites, has been used to connect all sites to the Internet, which is the frame
relay. Next, add a Network Address Translation (NAT) to the Network Operations
Centre site. Last of all, to restrict certain network access rights for different users of the
network such as staff, customers and students, access lists (ACLs) has been included to
specific sites.
Acknowledgment
There were two instrumental people who have helped us to accomplish our
objective. They were Mr. Sunil, our networking tutor, and Mr. James, the course
coordinator, and they helped us by explaining some tasks and providing various
instructions and information such as, problems with Variable Length Subnet Masking
(VLSM) and the Access-Lists (ACLs).
Page 2 of 47

201000096 - 201000129 - 2010000413
Sunil Seneviratne
13th June, 2013
Contents
Introduction ........................................................................................................................................................................ 4
Step 1 ................................................................................................................................................................................ 4
Step 1.1: Implement a private IPv4 addressing scheme & future expansion ............................... 4
Step 1.2: Implement an appropriate routing protocol ........................................................................... 4
Step 1.3: Proper login banners ......................................................................................................................... 5
Step 1.4: Encrypted passwords on routers ................................................................................................. 5
Step 2 ................................................................................................................................................................................ 6
Step 2.1: The Local Area Network (LAN) configuration in each site ................................................ 6
Step 3 ................................................................................................................................................................................ 7
Step 3.1: Implement a security measurement ........................................................................................... 7
Step 3.2: Implement a redundancy measurement ................................................................................... 8
Step 4 ................................................................................................................................................................................ 9
Step 4.1: Add a wireless access to the (LANs) in all sites ...................................................................... 9
Step 5 ................................................................................................................................................................................ 9
Step 5.1: Implement a connection between Poly Telecoms NOC and BIX .................................... 9
Step 6 ............................................................................................................................................................................. 10
Step 6.1: Connect all sites together using Permanent Virtual Circuits (PVCs) .......................... 10
Step 7 ............................................................................................................................................................................. 10
Step 7.1: Implement Network Address Translation (NAT) on (NOC) router ............................ 10
Step 8 ............................................................................................................................................................................. 11
Step 8.1: Access list for the IT staff .............................................................................................................. 11
Step 8.2: Access list for student in the training facility ....................................................................... 12
Step 8.3: Access list for the branches ......................................................................................................... 12
Step 8.4: Access list for the Internet ........................................................................................................... 13
Results and Conclusions ............................................................................................................................................. 14
References ........................................................................................................................................................................ 15
Appendices ....................................................................................................................................................................... 16
Page 3 of 47

201000096 - 201000129 - 2010000413
Sunil Seneviratne
13th June, 2013
Introduction
The purpose of this report is to discuss the project that was created relating to
designing and implementing a network for Poly Telecom to provide GSM, 3G and 4G
LTE services to its clients, which have five metropolitan sites: Head Quarter (HQ),
Network Operations Centre (NOC), and three customer branches: Riffa, Saar, Hamad
Town customer branches. Poly Telecom Network requires a plan and prototype
network for the network of Poly Telecom.
Step 1
The first step was to implement a private IP addressing scheme version 4 for Poly
Telecom Network that will also cover the future expansion of the network. Then,
choose and implement a proper routing protocol. Next, an appropriate login banners
for all key networks devices which only include necessary information.
Step 1.1: Implement a private IPv4 addressing scheme & future expansion
The private IP addressing scheme version 4 have three classes A, B and C, and for class
A the private range is 10.0.0.0 - 10.255.255.255. Also, for class B the private range is
172.16.0.0 - 172.31.255.255 and for class C the private range is 192.168.0.0 192.168.255.255. The class B private IP range has been used and implemented in the
topology, and the class C private IP range has been used and implemented for the
Wireless connection in each site using VLSM (CIDR) Subnet Calculator for the current
sites and the future expansion. (See the IP addressing scheme tables in the appendix)
Step 1.2: Implement an appropriate routing protocol

A routing protocol has been chosen and implemented to the network, which is
(OSPF), because it can scale according to the size of the network using Packet
Tracer Software.
This screen (see Figure 1) captured from Hoora Network Operations Centre Router
shows the routing protocol networks included in OSPF in the running configuration. Also,
the OSPF routing protocol has been implemented in all routers in all sites (Seef Head
Quarter, Riffa Customer Branch, Saar Customer Branch and Hamad Town Customer
Branch).
Page 4 of 47

201000096 - 201000129 - 2010000413
Sunil Seneviratne
13th June, 2013
Step 1.3: Proper login banners

Use a proper login banners to all key network devices which includes only the
necessary information such as, a login message indicates that the authorized users
should only use the key devices using Packet Tracer Software.
These screens (see Figure 2) capture from Hoora Network Operations Centre Router
shows the Banner Message of the Day which shows that the unauthorized access is
forbidden to the routers and the Banner Login which shows the name of the router in the
running configuration and once the router started. Also, both Banners have been
implemented in all routers in all sites (Seef Head Quarter, Riffa Customer Branch, Saar
Customer Branch and Hamad Town Customer Branch). However, in all switches in each
site, a Banner Message of the Day has been implemented that shows the unauthorized
access is forbidden in these switches.
Step 1.4: Encrypted passwords on routers

An encrypted password was implemented on all routers when displaying the
running configuration inside each router using Packet Tracer Software.
These screens (see Figure 3) capture from Hoora Network Operations Centre Router
shows the enable secret password encrypted and displayed as unknown characters in
running configuration. Also, this encryption has been implemented in all routers and
switches in each site. Moreover, console and vty lines have been configured with a
password. There are two screen captures which shows the decrypted and the encrypted
password for both lines, as well as, the password for the PPP connection. (See Figure 7).
Page 5 of 47

201000096 - 201000129 - 2010000413
Sunil Seneviratne
13th June, 2013
Step 2
The second step was to create and implement a Local Area Network (LAN)
configuration table for Poly Telecom Network which will be separate users of
different types. Also, each site will have a broadcast domain name, which will be
same as the site name, to optimize the network and this will be implemented using
Vlan Trunking Protocol (VTP) in all switches in the network. There will be a Server
switch and Client switches in each site. Each type will have a Virtual Local Area
Network (VLAN) ID and name to separate it from another type in the same site.
According to that, every site will have different IDs and names of (VLANs) to all
types from the other sites. Moreover, a Spanning Tree Protocol (STP) will be
implemented to all switches in each site and that will help to prevent switching
loops and layer 2 broadcast storms which will improve the performance of the
network in all sites.
Step 2.1: The Local Area Network (LAN) configuration in each site
A configuration table for the Local Area Network in each site has been created to
separate each site along with its several types, and the used (VLANs) and the (VTP)
information for each site. (See VLAN tables in the appendix).
Page 6 of 47

201000096 - 201000129 - 2010000413
Sunil Seneviratne
13th June, 2013
Step 3
The third step was to implement security and redundancy measures on the (LAN)
of each site. First, the security measurement that was implemented on the (LANs)
was by adding a security sticky MAC port in all switches that are being connected to
the PCs, which means that switches will store the MAC addresses of the PCs to
permit only the exact PC to use a specific port on the switch. Also, implement the
secret and encrypted passwords in all routers and switches. Second, the redundancy
measurement that was implemented on the (LANs) was by adding more switches
and connecting the switches with each other in the distribution and access layers to
prevent any fail that may happened in any link. Also, implement the spanning tree
priority in Seef and Hoora switches to divide the traffic in the switches and to
improve the performance of the network.
Step 3.1: Implement a security measurement
The security measurement has been implemented for all sites in the network and
all key devices routers and switches using Packet Tracer Software.
- The first security measurement was the security port MAC sticky command in all
routers and switches. This security measurement will permit only one PC or Laptop to
connect to the specific port and it will save its MAC address, but when another PC or
Laptop connects to this port, it will shut down the port.
- The second security measurement was the enable secret password command for the
privileged EXEC mode in all routers and switches. This security measurement will deny
any access to the privileged EXEC mode in routers and switches without the configured
password. (See Figure 3, 4)
- The third security measurement was the line console & line vty password command in
all routers and switches. This security measurement will deny any access to any router or
switch from the line console or the line vty without the configured password. (See Figure
3, 4)
- The fourth security measurement was the service password-encryption command in
all routers and switches. This security measurement will encrypt the entire password in
any router or any switch, and it will change it to unknown characters, so only the person
who configured the device will know the password. (See Figure 3, 4)
Page 7 of 47

201000096 - 201000129 - 2010000413
Sunil Seneviratne
13th June, 2013
Step 3.2: Implement a redundancy measurement

The redundancy measurement has been implemented for all sites in the network
in Seef and Hoora switches using Packet Tracer Software.
- The first redundancy measurement was the spanning-tree priority command in the
switches to improve and optimize the network. This redundancy measurement will divide
the packet traffic between the switches in the implemented site, and this will improve the
network performance. (See Figure 5)
- The second redundancy measurement was by adding more switches and connecting
the switches with each other in the distribution and access layers to prevent any fail that
may happen in any link. This redundancy measurement will provide each switch with
more than one option to send the packet in the case that the link went down between
switches. (See Figure 5)
Page 8 of 47

201000096 - 201000129 - 2010000413
Sunil Seneviratne
13th June, 2013
Step 4
The fourth step was to add a wireless access to the (LANs) on all sites in addition
to the fixed access. To accomplish this task, a wireless router has been added to each
(LAN) on all sites.
Step 4.1: Add a wireless access to the (LANs) in all sites
A wireless router has been added to the (LANs) in all sites in addition to the fixed access,
which will allow the users to access the Internet from their laptops over the wireless
router using Packet Tracer Software. A special case for Hoora Network Operations Centre
site, two wireless routers has been added. The first one will be for the student and the
second one will be for the staff in the training facility department. (See Figure 6)
Step 5
The fifth step was to offer an Internet service to all Poly Telecoms customers. Poly
Telecom has got an agreement with Bahrain Internet Exchange (BIX) because it is
connected to Tata Communications which will then provide communication to other
countries Internet services. To implement the connection between Poly Telecoms
NOC and BIX, a public IP addresses assigned to specified link are the 113.10.10.0/30
range. Also, a data link layer encapsulation method on this serial link connection
which will aids authentication, compression and multiple network layer protocols,
and will operate on multi-vendor.
Step 5.1: Implement a connection between Poly Telecoms NOC and BIX
A data link layer encapsulation method on the serial link connection between Poly
Telecoms NOC and BIX has been implemented to provide an Internet service to all sites of
Poly Telecoms Network using Packet Tracer Software. To implement a data link layer
encapsulation method on the serial link connection between Poly Telecoms NOC and BIX,
a Point-to-Point Protocol has been used additionally with encapsulation method. Also, a
public IP addresses used between the both serial links connection, the IP address
113.10.10.1 for the serial in NOC router and the IP address 113.10.10.2 for the serial in
BIX router. (See Figure 7)
Page 9 of 47

201000096 - 201000129 - 2010000413
Sunil Seneviratne
13th June, 2013
Step 6
The sixth step was to connect all sites together using Permanent Virtual Circuits
(PVCs), and this will be implemented through the Internet using the Wide Area
Network (WAN) technology because the sites will not be directly connected.
Step 6.1: Connect all sites together using Permanent Virtual Circuits (PVCs)
A WAN technology has been implemented in the topology using Packet Tracer Software.
All sites will be connected using PVCs which is a networking technology that allows
connecting of the different paths in the network by creating associations within a frame
relay network, and that will handle the management of network traffic. In the frame relay
network, all sites have been connected to each other which create a full mesh topology.
One advantage in a full mesh topology, all routers in the network have virtual circuits to
all other routers, and according to this, it will provide the network with redundancy. See
appendices to check the Permanent Virtual Circuits configuration for each site. (See the
frame relay Tables in the appendix)
Step 7
The seventh step was to implement a Network Address Translation (NAT) at the
(NOC) building router, where Poly Telecom is connected to BIX and the Internet
because it is compulsory to allow the PCs inside the site to connect to the Internet by
translating (converting) the private IP addresses to public IP address.
Step 7.1: Implement Network Address Translation (NAT) on (NOC) router
A Network Address Translation (NAT) has been implemented on (NOC) router where
Poly Telecom is connected to BIX and the Internet to convert the private IP addresses
within the network to public IP addresses using Packet Tracer Software. This is required
to attempt a public communication to allow users to access the Internet. This will
translate only the IP addresses that have a permission to access the Internet, which they
are Seef Head Quarter and Hoora Network Operations Centre. The NAT will use the public
IP address range in the serial link connection between NOC and BIX to give them to the
packets that will reach the Internet. (See Figure 8)
Page 10 of 47

201000096 - 201000129 - 2010000413
Sunil Seneviratne
13th June, 2013
Step 8
The eighth step was to implement access lists to provide rights for different users
because there are several users of the network, for example, staff, customers and
students, and the network demand to restrict certain network access rights for them.
Step 8.1: Access list for the IT staff
An access list has been implemented for the IT staff department and that will permit
only the IT staff members to access all network devices through SSH using Packet Tracer
Software. An Extended ACL has been used to place the closest source link, the Fast
Ethernet Port of each router in bound, to reduce the packet traffic in the network. This
ACL has been implemented in all Customer Branches (Saar, Riffa and Hamad Town)
Routers to give access rights for the IT staff members only to reach the other parts of the
network, but not to reach the Internet or access network devices through SSH.
Customer Branches: Saar, Riffa and Hamad Town (Extended IP Access-List)
deny tcp any any eq 22
permit ip any 172.17.0.0 0.0.255.255
permit ip any 149.153.1.0 0.0.0.15
Head Quarter: Seef (Extended IP Access-List)
permit tcp 172.17.1.224 0.0.0.15 any eq 22
deny ip 172.17.1.128 0.0.0.31 172.17.0.0 0.0.255.255
deny ip host 172.17.1.242 172.17.0.0 0.0.255.255
permit ip host 172.17.1.242 any
permit ip 172.17.1.128 0.0.0.31 any
permit ip any any
Network Operations Centre: Hoora (Extended IP Access-List)
permit ip any any
Page 11 of 47

201000096 - 201000129 - 2010000413
Sunil Seneviratne
13th June, 2013
Step 8.2: Access list for student in the training facility

An access list has been implemented for the students in the training facility to deny them
from accessing HQ, customer branches and all departments at Hoora site except for the
servers, and also allow them to access the Internet using Packet Tracer Software. An
Extended ACL has been used to place the closest source link, the Fast Ethernet Port of
Head Quarter of Student VLAN and Student WRS VLAN in bound, to reduce the packet
traffic in the network. This ACL has been implemented to deny all students from access
the other parts of network from their wireless access point. The IP address of the wireless
access point of the student wireless network has been included to the ACL to deny it from
accessing the other parts of network, but they can access the E-mail and Web servers and
the Internet.
Head Quarter: Seef (Extended IP Access-List)
permit tcp 172.17.1.224 0.0.0.15 any eq 22
deny ip 172.17.1.128 0.0.0.31 172.17.0.0 0.0.255.255
deny ip host 172.17.1.242 172.17.0.0 0.0.255.255
permit ip host 172.17.1.242 any
permit ip 172.17.1.128 0.0.0.31 any
permit ip any any
Step 8.3: Access list for the customer branches

An access list has been implemented for the branches to deny them from having
connection to the Internet, but permit them to access all other parts of the Poly Telecom
network using Packet Tracer Software. An Extended ACL has been used to place the
closest source link, the Fast Ethernet Port of each router in bound, to reduce the packet
traffic in the network. This ACL has been implemented in all Customer Branches (Saar,
Riffa and Hamad Town) Routers to give access rights for them to reach the other parts of
the network, HQ and NOC, but not to reach the Internet. (By default, in the end of the ACL,
the command deny any any is included and that will deny the customer branches from
reaching the Internet).
Customer Branches: Saar, Riffa and Hamad Town (Extended IP Access-List)
permit ip any 172.17.0.0 0.0.255.255
permit ip any 149.153.1.0 0.0.0.15
Page 12 of 47

201000096 - 201000129 - 2010000413
Sunil Seneviratne
13th June, 2013
Step 8.4: Access list for the Internet

An access list has been implemented for the Internet to permits it to access to the
servers in Hoora, which they are E-mail and Web servers, traffic only, but deny it from
accessing to all other parts of the Poly Telecom network using Packet Tracer Software. An
Extended ACL has been used to place the closest source link, the Serial Port of NOC router
in bound that is connected to the BIX router. This ACL has been implemented to give the
permission of www port 80, pop3 port 110 and smtp port 25 protocols to reach the
Web and E-mail servers. (The line in the end of the ACL is to give the permission of other
protocol to pass for the other devices when they request anything, by default the ACL of
the NAT will deny any request from the Internet to pass in).
Network Operations Centre: Hoora (Extended IP Access-List)
permit tcp any 149.153.1.0 0.0.0.15 eq www
permit tcp any 149.153.1.0 0.0.0.15 eq pop3
permit tcp any 149.153.1.0 0.0.0.15 eq smtp
deny ip any 149.153.1.0 0.0.0.15
permit ip any any
Page 13 of 47

201000096 - 201000129 - 2010000413
Sunil Seneviratne
13th June, 2013
Results and Conclusions

In conclusion, Poly Telecom network has been implemented in Packet Tracer. In
addition, the topology seems to have been an accomplishment. The computers in each
site are able to ping each other successfully, as well as through the frame relay.
Moreover, all requirements and steps that have been requested in this PBL project have
been done by the efficient communication. Therefore, it is assumed that the next step to
be undertaken is the implementation of a model network using real hardware to reduce
problems that may arise in the actual implementation of the finalized network.
Page 14 of 47

201000096 - 201000129 - 2010000413
Sunil Seneviratne
13th June, 2013
References
Cisco Systems Inc. (2003). Cisco Networking Academy Program CCNA 3 and 4 Companion Guide,
Third Edition. Cisco press.
Page 15 of 47

201000096 - 201000129 - 2010000413
Sunil Seneviratne
13th June, 2013
Appendices
Head Quarter (HQ) Seef
-
Administration
Address
Network address
172.17.0.0
Broadcast address
172.17.0.31
First address
172.17.0.1
Last address
172.17.0.30
Subnet Mask
255.255.255.224
Usable host
30
CIDR
/27
-
Marketing
Address
Network address
172.17.0.32
Broadcast address
172.17.0.47
First address
172.17.0.33
Last address
172.17.0.46
Subnet Mask
255.255.255.240
Usable host
14
CIDR
/28
-
Accounts
Address
Network address
172.17.0.48
Broadcast address
172.17.0.63
First address
172.17.0.49
Last address
172.17.0.62
Subnet Mask
255.255.255.224
Usable host
14
CIDR
/28
-
Facilities
Address
Network address
172.17.0.64
Broadcast address
172.17.0.79
First address
172.17.0.65
Last address
172.17.0.78
Subnet Mask
255.255.255.224
Usable host
14
CIDR
/28
Page 16 of 47

201000096 - 201000129 - 2010000413
Sunil Seneviratne
13th June, 2013
Native Vlan
Address
Network address
172.17.0.80
Broadcast address
172.17.0.95
First address
172.17.0.81
Last address
172.17.0.94
Subnet Mask
255.255.255.224
Usable host
14
CIDR
/28
-
CEOs Office
Address
Network address
172.17.0.96
Broadcast address
172.17.0.103
First address
172.17.0.97
Last address
172.17.0.102
Subnet Mask
255.255.255.248
Usable host
CIDR
/29
-
Wireless Vlan
Address
Network address
172.17.0.104
Broadcast address
172.17.0.111
First address
172.17.0.105
Last address
172.17.0.110
Subnet Mask
255.255.255.248
Usable host
CIDR
/29
Wireless LAN
Address
Network address
192.168.0.0
Broadcast address
192.168.0.255
First address
192.168.0.100
Last address
192.168.0.149
Subnet Mask
255.255.255.0
Usable host
50
CIDR
/24
Page 17 of 47

201000096 - 201000129 - 2010000413
Sunil Seneviratne
13th June, 2013
VLAN Table
VLAN ID
31
47
63
79
95
Name
Administration
Marketing
Accounts
Facilities
Native
103
CEO
172.17.0.96/29
111
WRS
172.17.0.104/29
VTP Table
Mode
Domain
Name
Password
Client
Seef
seef
seef
Seef SW Distribution 1
Client
Client
Seef
Seef
seef
Server
Seef
seef
Client
Seef
seef
Seef SW Access 1
Client
Seef
seef
Seef SW Access 2
Seef SW Access 3
Client
Seef
seef
Client
Seef
seef
Device Name
Seef SW Core 1
Seef SW Core 2
Network
172.17.0.0/27
172.17.0.32/28
172.17.0.48/28
172.17.0.64/28
172.17.0.80/28
Frame Relay (PVCs)
1st Site
Name dlci
Network
address
1st address
2nd Site
Name - dlci
2nd address
Broadcast
address
Subnet Mask
Usable
host
CIDR
Seef - 201
172.32.0.60
172.32.0.62
Hoora 102
172.32.0.61
172.32.0.63
255.255.255.252
/30
Seef - 203
172.32.0.140
172.32.0.141
Saar - 302
172.32.0.142
172.32.0.143
255.255.255.252
/30
172.32.0.122
172.32.0.123
255.255.255.252
/30
172.32.0.138
172.32.0.139
255.255.255.252
/30
Seef - 204
172.32.0.120
172.32.0.121
Hamad
Town 402
Seef - 205
172.32.0.136
172.32.0.137
Riffa - 502
Page 18 of 47

201000096 - 201000129 - 2010000413
Sunil Seneviratne
13th June, 2013
Addressing Table
Interface
IP address
Subnet mask
Fa0/0.31
Fa0/0.95
Fa0/0.111
Fa0/1.47
172.17.0.30
172.17.0.94
172.17.0.110
172.17.0.46
255.255.255.224
255.255.255.240
255.255.255.248
255.255.255.240
Default
Gateway
N/A
N/A
N/A
N/A
Fa0/1.63
172.17.0.62
255.255.255.240
N/A
Fa0/1.79
172.17.0.78
255.255.255.240
N/A
Fa0/1.103
172.17.0.102
255.255.255.248
N/A
S0/0/0.201
172.32.0.62
255.255.255.252
N/A
S0/0/0.203
172.32.0.141
255.255.255.252
N/A
S0/0/0.204
172.32.0.121
255.255.255.252
N/A
S0/0/0.205
172.32.0.137
255.255.255.252
N/A
Seef SW Core 1
Seef SW Core 2
Vlan 95
Vlan 95
172.17.0.81
172.17.0.82
255.255.255.240
255.255.255.240
172.17.0.94
172.17.0.94
Vlan 95
Vlan 95
Vlan 95
172.17.0.83
172.17.0.84
172.17.0.85
255.255.255.240
255.255.255.240
255.255.255.240
172.17.0.94
172.17.0.94
172.17.0.94
Seef SW Access 1
Seef SW Access 2
Seef SW Access 3
Vlan 95
Vlan 95
Vlan 95
172.17.0.86
172.17.0.87
172.17.0.88
255.255.255.240
255.255.255.240
255.255.255.240
172.17.0.94
172.17.0.94
172.17.0.94
WAN
172.17.0.105
255.255.255.248
172.17.0.110
LAN/Wireless
NIC
NIC
NIC
NIC
192.168.0.1
172.17.0.97
172.17.0.33
172.17.0.49
172.17.0.65
255.255.255.0
255.255.255.248
255.255.255.240
255.255.255.240
255.255.255.240
N/A
172.17.0.102
172.17.0.46
172.17.0.62
172.17.0.78
PC5 (Administration 1)
NIC
172.17.0.1
255.255.255.224
172.17.0.30
PC6 (Administration 1)
NIC
172.17.0.2
255.255.255.224
172.17.0.30
Device
Seef (Router)
Seef WRS Access point

PC1 (CEOs office)
PC2 (Marketing)
PC3 (Accounts)
PC4 (Facilities)
Page 19 of 47

201000096 - 201000129 - 2010000413
Sunil Seneviratne
13th June, 2013
Network Operations Centre (NOC) - Hoora

-
NOC
Address
Network address
172.17.1.0
Broadcast address
172.17.1.127
First address
172.17.1.1
Last address
172.17.1.126
Subnet Mask
255.255.255.128
Usable host
126
CIDR
/25
-
Training Facility (Students)

Address
Network address
172.17.1.128
Broadcast address
172.17.1.159
First address
172.17.1.129
Last address
172.17.1.158
Subnet Mask
255.255.255.224
Usable host
30
CIDR
/27
-
Customer Service
Address
Network address
172.17.1.160
Broadcast address
172.17.1.191
First address
172.17.1.161
Last address
172.17.1.190
Subnet Mask
255.255.255.224
Usable host
30
CIDR
/27
-
Native Vlan
Address
Network address
172.17.1.192
Broadcast address
172.17.1.223
First address
172.17.1.193
Last address
172.17.1.222
Subnet Mask
255.255.255.224
Usable host
30
CIDR
/27
Page 20 of 47

201000096 - 201000129 - 2010000413
Sunil Seneviratne
13th June, 2013
IT Department
Address
Network address
172.17.1.224
Broadcast address
172.17.1.239
First address
172.17.1.225
Last address
172.17.1.238
Subnet Mask
255.255.255.240
Usable host
14
CIDR
/28
Wireless Vlan
Address
Network address
172.17.1.240
Broadcast address
172.17.1.255
First address
172.17.1.241
Last address
172.17.1.254
Subnet Mask
255.255.255.240
Usable host
14
CIDR
/28
-
Website Developers
Address
Network address
172.17.2.0
Broadcast address
172.17.2.7
First address
172.17.2.1
Last address
172.17.2.6
Subnet Mask
255.255.255.248
Usable host
CIDR
/29
-
Training Facility (Staff)

Address
Network address
172.17.2.8
Broadcast address
172.17.2.15
First address
172.17.2.9
Last address
172.17.2.14
Subnet Mask
255.255.255.248
Usable host
CIDR
/29
Page 21 of 47

201000096 - 201000129 - 2010000413
Sunil Seneviratne
13th June, 2013
Wireless LAN (Staff)

Address
Network address
192.168.3.0
Broadcast address
192.168.3.255
First address
192.168.3.100
Last address
192.168.3.149
Subnet Mask
255.255.255.0
Usable host
50
CIDR
/24
-
Wireless LAN (Student)

Address
Network address
192.168.7.0
Broadcast address
192.168.7.255
First address
192.168.7.100
Last address
192.168.7.149
Subnet Mask
255.255.255.0
Usable host
50
CIDR
/24
-
VLAN Table
VLAN ID
7
15
127
159
191
Name
WebsiteDevelopers
TrainingStaff
NOC
TrainingStudents
CustomerService
Network
172.17.2.0/29
172.17.2.8/29
172.17.1.0/25
172.17.1.128/27
172.17.1.160/27
223
Native
172.17.1.192/27
239
ITDepartment
172.17.1.224/28
255
WRS
172.17.1.240/28
Frame Relay (PVCs)
Network
address
1st address
2nd Site
Name - dlci
2nd
address
Broadcast
address
Subnet Mask
Usable
host
CIDR
172.32.0.60
172.32.0.61
Seef - 201
172.32.0.62
172.32.0.63
255.255.255.252
/30
172.32.0.56
172.32.0.57
Saar - 301
172.32.0.58
172.32.0.59
255.255.255.252
/30
Hoora 104
172.32.0.36
172.32.0.37
Hamad
Town - 401
172.32.0.38
172.32.0.39
255.255.255.252
/30
Hoora 105
172.32.0.52
172.32.0.53
Riffa - 501
172.32.0.54
172.32.0.55
255.255.255.252
/30
1st Site
Name - dlci
Hoora 102
Hoora 103
Page 22 of 47

201000096 - 201000129 - 2010000413
Sunil Seneviratne
13th June, 2013
Addressing Table
Interface
IP address
Subnet mask
Fa0/0.7
Fa0/0.127
Fa0/0.191
Fa0/0.239
172.17.2.6
172.17.1.126
172.17.1.190
172.17.1.238
255.255.255.248
255.255.255.128
255.255.255.224
255.255.255.240
Default
Gateway
N/A
N/A
N/A
N/A
Fa0/1.15
172.17.2.14
255.255.255.248
N/A
Fa0/1.159
172.17.1.158
255.255.255.224
N/A
Fa0/1.223
172.17.1.222
255.255.255.224
N/A
Fa0/1.255
172.17.1.254
255.255.255.240
N/A
S0/0/0.102
172.32.0.61
255.255.255.252
N/A
S0/0/0.103
172.32.0.57
255.255.255.252
N/A
S0/0/0.104
172.32.0.37
255.255.255.252
N/A
S0/0/0.105
172.32.0.53
255.255.255.252
N/A
Hoora SW Core 1
Hoora SW Core 2
Vlan 223
Vlan 223
172.17.1.193
172.17.1.194
255.255.255.224
255.255.255.224
172.17.1.222
172.17.1.222
Hoora SW Distribution 1
Vlan 223
Vlan 223
Vlan 223
172.17.1.195
172.17.1.196
172.17.1.197
255.255.255.224
255.255.255.224
255.255.255.224
172.17.1.222
172.17.1.222
172.17.1.222
Hoora SW Access 1
Hoora SW Access 2
Hoora SW Access 3
Vlan 223
Vlan 223
Vlan 223
172.17.1.198
172.17.1.199
172.17.1.200
255.255.255.224
255.255.255.224
255.255.255.224
172.17.1.222
172.17.1.222
172.17.1.222
Hoora SW Access 4
Vlan 223
172.17.1.201
255.255.255.224
172.17.1.222
Hoora SW Access 5
Vlan 223
172.17.1.202
255.255.255.224
172.17.1.222
Hoora SW Access 6
Vlan 223
172.17.1.203
255.255.255.224
172.17.1.222
Hoora SW Access 7
Vlan 223
172.17.1.204
255.255.255.224
172.17.1.222
Hoora SW Access 8
Vlan 223
172.17.1.205
255.255.255.224
172.17.1.222
Device
Hoora (Router)
WAN
172.17.1.241
255.255.255.240
172.17.1.254
LAN/Wireless
WAN
192.168.3.1
172.17.1.241
255.255.255.0
255.255.255.240
N/A
172.17.1.254
PC1 (NOC 1)
PC2 (NOC 2)
PC3 (NOC 3)
PC4 (NOC 4)
LAN/Wireless
NIC
NIC
NIC
NIC
192.168.7.1
172.17.1.1
172.17.1.2
172.17.1.3
172.17.1.4
255.255.255.0
255.255.255.128
255.255.255.128
255.255.255.128
255.255.255.128
N/A
172.17.1.126
172.17.1.126
172.17.1.126
172.17.1.126
PC5 (NOC 5)
NIC
172.17.1.5
255.255.255.128
172.17.1.126
PC6 (Customer service)
NIC
172.17.1.161
255.255.255.224
172.17.1.190
PC7 (Website developers)
NIC
172.17.2.1
255.255.255.248
172.17.2.6
Wireless NIC
DHCP
255.255.255.0
192.168.3.1
PC9 (IT department)
NIC
172.17.1.225
255.255.255.240
172.17.1.238
PC10 (Staff Training facility)
NIC
172.17.2.9
255.255.255.248
172.17.2.14
Laptop1 (Student Training facility)
NIC
172.17.1.129
255.255.255.224
172.17.1.158
Laptop2 (Student Training facility)
Wireless NIC
DHCP
255.255.255.0
192.168.7.1
Hoora WRS Access point (Staff)

Hoora WRS Access point (Student)
PC8 (WRS - Staff Connection)
Page 23 of 47

201000096 - 201000129 - 2010000413
Sunil Seneviratne
13th June, 2013
VTP Table
Mode
Domain
Name
Password
Hoora SW Core 1
Client
Seef
seef
Hoora SW Core 2
Client
Client
Seef
seef
Seef
seef
Server
Seef
seef
Client
Seef
seef
Hoora SW Access 1
Client
Seef
seef
Hoora SW Access 2
Hoora SW Access 3
Client
Seef
seef
Client
Seef
seef
Hoora SW Access 4
Client
Seef
seef
Hoora SW Access 5
Hoora SW Access 6
Client
Seef
seef
Client
Seef
seef
Hoora SW Access 7
Client
Seef
seef
Hoora SW Access 8
Client
Seef
seef
Device Name
Page 24 of 47

201000096 - 201000129 - 2010000413
Sunil Seneviratne
13th June, 2013
Customer Branch - Riffa

-
Customer Service
Address
Network address
172.17.3.0
Broadcast address
172.17.3.15
First address
172.17.3.1
Last address
172.17.3.14
Subnet Mask
255.255.255.240
Usable host
14
CIDR
/28
-
Manager
Address
Network address
172.17.3.16
Broadcast address
172.17.3.23
First address
172.17.3.17
Last address
172.17.3.22
Subnet Mask
255.255.255.248
Usable host
CIDR
/29
-
Native Vlan
Address
Network address
172.17.3.24
Broadcast address
172.17.3.31
First address
172.17.3.25
Last address
172.17.3.30
Subnet Mask
255.255.255.248
Usable host
CIDR
/29
-
Wireless Vlan
Address
Network address
172.17.3.32
Broadcast address
172.17.3.35
First address
172.17.3.33
Last address
172.17.3.34
Subnet Mask
255.255.255.252
Usable host
CIDR
/30
Page 25 of 47

201000096 - 201000129 - 2010000413
Sunil Seneviratne
13th June, 2013
Wireless LAN
Address
Network address
192.168.9.0
Broadcast address
192.168.9.255
First address
192.168.9.100
Last address
192.168.9.149
Subnet Mask
255.255.255.0
Usable host
50
CIDR
/24
-
Addressing Table
Device
Riffa (Router)
Riffa SW Core
Riffa SW Distribution 1
Riffa SW Distribution 2
Riffa SW Access 1
Riffa SW Access 2
Riffa WRS Access point
PC1 (Manager)
PC2 (Staff)
Interface
Fa0/0.15
Fa0/0.23
Fa0/0.31
Fa0/0.35
S0/0/0.501
IP address
172.17.3.14
172.17.3.22
172.17.3.30
172.17.3.34
172.32.0.54
Subnet mask
255.255.255.240
255.255.255.248
255.255.255.248
255.255.255.252
255.255.255.252
Default Gateway
N/A
N/A
N/A
N/A
N/A
S0/0/0.502
172.32.0.138
255.255.255.252
N/A
S0/0/0.503
172.32.0.114
255.255.255.252
N/A
S0/0/0.504
172.32.0.22
255.255.255.252
N/A
Vlan 31
Vlan 31
Vlan 31
Vlan 31
Vlan 31
WAN
LAN/Wireless
NIC
NIC
172.17.3.25
172.17.3.26
172.17.3.27
172.17.3.28
172.17.3.29
172.17.3.33
192.168.9.1
172.17.3.17
172.17.3.1
255.255.255.248
255.255.255.248
255.255.255.248
255.255.255.248
255.255.255.248
255.255.255.252
255.255.255.0
255.255.255.248
255.255.255.240
172.17.3.30
172.17.3.30
172.17.3.30
172.17.3.30
172.17.3.30
172.17.3.34
N/A
172.17.3.22
172.17.3.14
VLAN Table
VLAN ID
15
23
31
35
Name
CustomerService
Manager
Native
WRS
Page 26 of 47
Network
172.17.3.0/28
172.17.3.16/29
172.17.3.24/29
172.17.3.32/30

201000096 - 201000129 - 2010000413
Sunil Seneviratne
13th June, 2013
VTP Table
Mode
Domain
Name
Password
Riffa SW Core
Riffa SW
Distribution 1
Riffa SW
Distribution 2
Riffa SW Access 1
Server
Riffa
riffa
Client
Riffa
riffa
Client
Riffa
riffa
Client
Riffa
riffa
Riffa SW Access 2
Client
Riffa
riffa
Device Name
Frame Relay (PVCs)
1st Site
Name - dlci
Network
address
1st address
2nd Site Name dlci
2nd address
Broadcast
address
Subnet Mask
Usable
host
CIDR
Riffa - 501
Riffa - 502
172.32.0.52
172.32.0.54
Hoora - 105
172.32.0.53
172.32.0.55
255.255.255.252
/30
172.32.0.136
172.32.0.138
Seef - 205
172.32.0.137
172.32.0.139
255.255.255.252
/30
Riffa - 503
172.32.0.112
172.32.0.114
Saar - 305
172.32.0.113
172.32.0.115
255.255.255.252
/30
Riffa - 504
172.32.0.20
172.32.0.22
Hamad Town 405
172.32.0.21
172.32.0.23
255.255.255.252
/30
Page 27 of 47

201000096 - 201000129 - 2010000413
Sunil Seneviratne
13th June, 2013
Customer Branch - Saar

-
Customer Service
Address
Network address
172.17.4.0
Broadcast address
172.17.4.15
First address
172.17.4.1
Last address
172.17.4.14
Subnet Mask
255.255.255.240
Usable host
14
CIDR
/28
-
Manager
Address
Network address
172.17.4.16
Broadcast address
172.17.4.23
First address
172.17.4.17
Last address
172.17.4.22
Subnet Mask
255.255.255.248
Usable host
CIDR
/29
-
Native Vlan
Address
Network address
172.17.4.24
Broadcast address
172.17.4.31
First address
172.17.4.25
Last address
172.17.4.30
Subnet Mask
255.255.255.248
Usable host
CIDR
/29
-
Wireless Vlan
Address
Network address
172.17.4.32
Broadcast address
172.17.4.35
First address
172.17.4.33
Last address
172.17.4.34
Subnet Mask
255.255.255.252
Usable host
CIDR
/30
Page 28 of 47

201000096 - 201000129 - 2010000413
Sunil Seneviratne
13th June, 2013
Wireless LAN
Address
Network address
192.168.10.0
Broadcast address
192.168.10.255
First address
192.168.10.100
Last address
192.168.10.149
Subnet Mask
255.255.255.0
Usable host
50
CIDR
/24
Addressing Table
Device
Saar (Router)
Saar SW Core
Saar SW Distribution 1
Saar SW Distribution 2
Saar SW Access 1
Saar SW Access 2
Saar WRS Access point
PC1 (Manager)
PC2 (Staff)
Interface
Fa0/0.15
Fa0/0.23
Fa0/0.31
Fa0/0.35
S0/0/0.301
IP address
172.17.4.14
172.17.4.22
172.17.4.30
172.17.4.34
172.32.0.58
Subnet mask
255.255.255.240
255.255.255.248
255.255.255.248
255.255.255.252
255.255.255.252
Default Gateway
N/A
N/A
N/A
N/A
N/A
S0/0/0.302
172.32.0.142
255.255.255.252
N/A
S0/0/0.304
172.32.0.97
255.255.255.252
N/A
S0/0/0.305
172.32.0.113
255.255.255.252
N/A
Vlan 31
Vlan 31
Vlan 31
Vlan 31
Vlan 31
WAN
LAN/Wireless
NIC
NIC
172.17.4.25
172.17.4.26
172.17.4.27
172.17.4.28
172.17.4.29
172.17.4.33
192.168.10.1
172.17.4.17
172.17.4.1
255.255.255.248
255.255.255.248
255.255.255.248
255.255.255.248
255.255.255.248
255.255.255.252
255.255.255.0
255.255.255.248
255.255.255.240
172.17.4.30
172.17.4.30
172.17.4.30
172.17.4.30
172.17.4.30
172.17.4.34
N/A
172.17.4.22
172.17.4.14
VLAN Table
VLAN ID
15
23
31
35
Name
CustomerService
Manager
Native
WRS
Page 29 of 47
Network
172.17.4.0/28
172.17.4.16/29
172.17.4.24/29
172.17.4.32/30

201000096 - 201000129 - 2010000413
Sunil Seneviratne
13th June, 2013
VTP Table
Mode
Domain
Name
Password
Saar SW Core
Saar SW
Distribution 1
Saar SW
Distribution 2
Saar SW Access 1
Server
Saar
saar
Client
Saar
saar
Client
Saar
saar
Client
Saar
saar
Saar SW Access 2
Client
Saar
saar
Device Name
Frame Relay (PVCs)
1st Site
Name - dlci
Network
address
1st address
2nd Site Name dlci
2nd address
Broadcast
address
Subnet Mask
Usable
host
CIDR
Saar - 301
Saar - 302
172.32.0.56
172.32.0.58
Hoora - 103
172.32.0.57
172.32.0.59
255.255.255.252
/30
172.32.0.140
172.32.0.142
Seef - 203
172.32.0.141
172.32.0.143
255.255.255.252
/30
Saar - 304
172.32.0.96
172.32.0.97
Hamad Town 403
172.32.0.98
172.32.0.99
255.255.255.252
/30
Saar - 305
172.32.0.112
172.32.0.113
Riffa - 503
172.32.0.114
172.32.0.115
255.255.255.252
/30
Page 30 of 47

201000096 - 201000129 - 2010000413
Sunil Seneviratne
13th June, 2013
Customer Branch - Hamad Town

-
Customer Service
Address
Network address
172.17.5.0
Broadcast address
172.17.5.15
First address
172.17.5.1
Last address
172.17.5.14
Subnet Mask
255.255.255.240
Usable host
14
CIDR
/28
-
Manager
Address
Network address
172.17.5.16
Broadcast address
172.17.5.23
First address
172.17.5.17
Last address
172.17.5.22
Subnet Mask
255.255.255.248
Usable host
CIDR
/29
-
Native Vlan
Address
Network address
172.17.5.24
Broadcast address
172.17.5.31
First address
172.17.5.25
Last address
172.17.5.30
Subnet Mask
255.255.255.248
Usable host
CIDR
/29
-
Wireless Vlan
Address
Network address
172.17.5.32
Broadcast address
172.17.5.35
First address
172.17.5.33
Last address
172.17.5.34
Subnet Mask
255.255.255.252
Usable host
CIDR
/30
Page 31 of 47

201000096 - 201000129 - 2010000413
Sunil Seneviratne
13th June, 2013
Wireless LAN
Address
Network address
192.168.11.0
Broadcast address
192.168.11.255
First address
192.168.11.100
Last address
192.168.11.149
Subnet Mask
255.255.255.0
Usable host
50
CIDR
/24
Addressing Table
Device
Hamad Town (Router)
Hamad Town SW Core

Hamad Town SW Distribution 1
Hamad Town SW Distribution 2
Hamad Town SW Access 1
Hamad Town WRS Access point
PC1 (Manager)
PC2 (Staff)
Interface
IP address
Subnet mask
Fa0/0.15
Fa0/0.23
Fa0/0.31
Fa0/0.35
S0/0/0.401
172.17.5.14
172.17.5.22
172.17.5.30
172.17.5.34
172.32.0.38
255.255.255.240
255.255.255.248
255.255.255.248
255.255.255.252
255.255.255.252
Default
Gateway
N/A
N/A
N/A
N/A
N/A
S0/0/0.402
172.32.0.122
255.255.255.252
N/A
S0/0/0.403
172.32.0.98
255.255.255.252
N/A
S0/0/0.405
172.32.0.21
255.255.255.252
N/A
Vlan 31
Vlan 31
Vlan 31
Vlan 31
Vlan 31
WAN
LAN/Wireless
NIC
NIC
172.17.5.25
172.17.5.26
172.17.5.27
172.17.5.28
172.17.5.29
172.17.5.33
192.168.11.1
172.17.5.17
172.17.5.1
255.255.255.248
255.255.255.248
255.255.255.248
255.255.255.248
255.255.255.248
255.255.255.252
255.255.255.0
255.255.255.248
255.255.255.240
172.17.5.30
172.17.5.30
172.17.5.30
172.17.5.30
172.17.5.30
172.17.5.34
N/A
172.17.5.22
172.17.5.14
VLAN Table
VLAN ID
15
23
31
35
Name
CustomerService
Manager
Native
WRS
Page 32 of 47
Network
172.17.5.0/28
172.17.5.16/29
172.17.5.24/29
172.17.5.32/30

201000096 - 201000129 - 2010000413
Sunil Seneviratne
13th June, 2013
VTP Table
Device Name
Mode
Domain
Name
Password
Hamad Town SW Core

Hamad Town SW
Distribution 1
Hamad Town SW
Distribution 2
Server
HamadTown
hamadtown
Client
HamadTown
hamadtown
Client
HamadTown
hamadtown
Client
HamadTown
hamadtown
Client
HamadTown
hamadtown
Frame Relay (PVCs)
1st address
2nd Site
Name dlci
2nd address
Broadcast
address
Subnet Mask
Usable
host
CIDR
172.32.0.36
172.32.0.38
Hoora 104
172.32.0.37
172.32.0.39
255.255.255.252
/30
Hamad
Town - 402
172.32.0.120
172.32.0.122
Seef 204
172.32.0.121
172.32.0.123
255.255.255.252
/30
Hamad
Town - 403
172.32.0.96
172.32.0.98
Saar 304
172.32.0.97
172.32.0.99
255.255.255.252
/30
Hamad
Town - 405
172.32.0.20
172.32.0.21
Riffa 504
172.32.0.22
172.32.0.23
255.255.255.252
/30
1st Site
Name - dlci
Network
address
Hamad
Town - 401
Page 33 of 47

201000096 - 201000129 - 2010000413
Sunil Seneviratne
13th June, 2013
Customer Branch - Juffair

- Customer Service
Address
Network address
172.17.6.0
Broadcast address
172.17.6.15
First address
172.17.6.1
Last address
172.17.6.14
Subnet Mask
255.255.255.240
Usable host
14
CIDR
/28
-
Manager
Address
Network address
172.17.6.16
Broadcast address
172.17.6.23
First address
172.17.6.17
Last address
172.17.6.22
Subnet Mask
255.255.255.248
Usable host
CIDR
/29
-
Native Vlan
Address
Network address
172.17.6.24
Broadcast address
172.17.6.31
First address
172.17.6.25
Last address
172.17.6.30
Subnet Mask
255.255.255.248
Usable host
CIDR
/29
-
Wireless Vlan
Address
Network address
172.17.6.32
Broadcast address
172.17.6.35
First address
172.17.6.33
Last address
172.17.6.34
Subnet Mask
255.255.255.252
Usable host
CIDR
/30
Page 34 of 47

201000096 - 201000129 - 2010000413
Sunil Seneviratne
13th June, 2013
Wireless LAN
Address
Network address
192.168.12.0
Broadcast address
192.168.12.255
First address
192.168.12.100
Last address
192.168.12.149
Subnet Mask
255.255.255.0
Usable host
50
CIDR
/24
-
Addressing Table
Device
Juffair (Router)
Juffair SW Core
Juffair SW Distribution 1
Juffair SW Distribution 2
Juffair SW Access 1
Juffair SW Access 2
Juffair WRS Access point
PC1 (Manager)
PC2 (Staff)
-
Interface
IP address
Subnet mask
Fa0/0.15
Fa0/0.23
Fa0/0.31
Fa0/0.35
Vlan 31
Vlan 31
Vlan 31
Vlan 31
Vlan 31
WAN
LAN/Wireless
NIC
NIC
172.17.6.14
172.17.6.22
172.17.6.30
172.17.6.34
172.17.6.25
172.17.6.26
172.17.6.27
172.17.6.28
172.17.6.29
172.17.6.33
192.168.12.1
172.17.6.17
172.17.6.1
255.255.255.240
255.255.255.248
255.255.255.248
255.255.255.252
255.255.255.248
255.255.255.248
255.255.255.248
255.255.255.248
255.255.255.248
255.255.255.252
255.255.255.0
255.255.255.248
255.255.255.240
VLAN Table
VLAN ID
15
23
31
35
Name
CustomerService
Manager
Native
WRS
Page 35 of 47
Network
172.17.6.0/28
172.17.6.16/29
172.17.6.24/29
172.17.6.32/30
Default
Gateway
N/A
N/A
N/A
N/A
172.17.6.30
172.17.6.30
172.17.6.30
172.17.6.30
172.17.6.30
172.17.6.34
N/A
172.17.6.22
172.17.6.14

201000096 - 201000129 - 2010000413
Sunil Seneviratne
13th June, 2013
Customer Branch - Budaiya

- Customer Service
Address
Network address
172.17.7.0
Broadcast address
172.17.7.15
First address
172.17.7.1
Last address
172.17.7.14
Subnet Mask
255.255.255.240
Usable host
14
CIDR
/28
-
Manager
Address
Network address
172.17.7.16
Broadcast address
172.17.7.23
First address
172.17.7.17
Last address
172.17.7.22
Subnet Mask
255.255.255.248
Usable host
CIDR
/29
-
Native Vlan
Address
Network address
172.17.7.24
Broadcast address
172.17.7.31
First address
172.17.7.25
Last address
172.17.7.30
Subnet Mask
255.255.255.248
Usable host
CIDR
/29
-
Wireless Vlan
Address
Network address
172.17.7.32
Broadcast address
172.17.7.35
First address
172.17.7.33
Last address
172.17.7.34
Subnet Mask
255.255.255.252
Usable host
CIDR
/30
Page 36 of 47

201000096 - 201000129 - 2010000413
Sunil Seneviratne
13th June, 2013
Wireless LAN
Address
Network address
192.168.13.0
Broadcast address
192.168.13.255
First address
192.168.13.100
Last address
192.168.13.149
Subnet Mask
255.255.255.0
Usable host
50
CIDR
/24
-
Addressing Table
Device
Budaiya (Router)
Budaiya SW Core
Budaiya SW Distribution 1
Budaiya SW Distribution 2
Budaiya SW Access 1
Budaiya SW Access 2
Budaiya WRS Access point
PC1 (Manager)
PC2 (Staff)
-
Interface
IP address
Subnet mask
Fa0/0.15
Fa0/0.23
Fa0/0.31
Fa0/0.35
Vlan 31
Vlan 31
Vlan 31
Vlan 31
Vlan 31
WAN
LAN/Wireless
NIC
NIC
172.17.7.14
172.17.7.22
172.17.7.30
172.17.7.34
172.17.7.25
172.17.7.26
172.17.7.27
172.17.7.28
172.17.7.29
172.17.7.33
192.168.13.1
172.17.7.17
172.17.7.1
255.255.255.240
255.255.255.248
255.255.255.248
255.255.255.252
255.255.255.248
255.255.255.248
255.255.255.248
255.255.255.248
255.255.255.248
255.255.255.252
255.255.255.0
255.255.255.248
255.255.255.240
VLAN Table
VLAN ID
15
23
31
35
Name
CustomerService
Manager
Native
WRS
Page 37 of 47
Network
172.17.7.0/28
172.17.7.16/29
172.17.7.24/29
172.17.7.32/30
Default
Gateway
N/A
N/A
N/A
N/A
172.17.7.30
172.17.7.30
172.17.7.30
172.17.7.30
172.17.7.30
172.17.7.34
N/A
172.17.7.22
172.17.7.14

201000096 - 201000129 - 2010000413
Sunil Seneviratne
13th June, 2013
Customer Branch - Hamala

- Customer Service
Address
Network address
172.17.8.0
Broadcast address
172.17.8.15
First address
172.17.8.1
Last address
172.17.8.14
Subnet Mask
255.255.255.240
Usable host
14
CIDR
/28
-
Manager
Address
Network address
172.17.8.16
Broadcast address
172.17.8.23
First address
172.17.8.17
Last address
172.17.8.22
Subnet Mask
255.255.255.248
Usable host
CIDR
/29
-
Native Vlan
Address
Network address
172.17.8.24
Broadcast address
172.17.8.31
First address
172.17.8.25
Last address
172.17.8.30
Subnet Mask
255.255.255.248
Usable host
CIDR
/29
-
Wireless Vlan
Address
Network address
172.17.8.32
Broadcast address
172.17.8.35
First address
172.17.8.33
Last address
172.17.8.34
Subnet Mask
255.255.255.252
Usable host
CIDR
/30
Page 38 of 47

201000096 - 201000129 - 2010000413
Sunil Seneviratne
13th June, 2013
Wireless LAN
Address
Network address
192.168.14.0
Broadcast address
192.168.14.255
First address
192.168.14.100
Last address
192.168.14.149
Subnet Mask
255.255.255.0
Usable host
50
CIDR
/24
-
Addressing Table
Device
Hamala (Router)
Hamala SW Core
Hamala SW Distribution 1
Hamala SW Distribution 2
Hamala SW Access 1
Hamala SW Access 2
Hamala WRS Access point
PC1 (Manager)
PC2 (Staff)
-
Interface
IP address
Subnet mask
Fa0/0.15
Fa0/0.23
Fa0/0.31
Fa0/0.35
Vlan 31
Vlan 31
Vlan 31
Vlan 31
Vlan 31
WAN
LAN/Wireless
NIC
NIC
172.17.8.14
172.17.8.22
172.17.8.30
172.17.8.34
172.17.8.25
172.17.8.26
172.17.8.27
172.17.8.28
172.17.8.29
172.17.8.33
192.168.14.1
172.17.8.17
172.17.8.1
255.255.255.240
255.255.255.248
255.255.255.248
255.255.255.252
255.255.255.248
255.255.255.248
255.255.255.248
255.255.255.248
255.255.255.248
255.255.255.252
255.255.255.0
255.255.255.248
255.255.255.240
VLAN Table
VLAN ID
15
23
31
35
Name
CustomerService
Manager
Native
WRS
Page 39 of 47
Network
172.17.8.0/28
172.17.8.16/29
172.17.8.24/29
172.17.8.32/30
Default
Gateway
N/A
N/A
N/A
N/A
172.17.8.30
172.17.8.30
172.17.8.30
172.17.8.30
172.17.8.30
172.17.8.34
N/A
172.17.8.22
172.17.8.14

201000096 - 201000129 - 2010000413
Sunil Seneviratne
13th June, 2013
Customer Branch - Hidd

- Customer Service
Address
Network address
172.17.9.0
Broadcast address
172.17.9.15
First address
172.17.9.1
Last address
172.17.9.14
Subnet Mask
255.255.255.240
Usable host
14
CIDR
/28
-
Manager
Address
Network address
172.17.9.16
Broadcast address
172.17.9.23
First address
172.17.9.17
Last address
172.17.9.22
Subnet Mask
255.255.255.248
Usable host
CIDR
/29
-
Native Vlan
Address
Network address
172.17.9.24
Broadcast address
172.17.9.31
First address
172.17.9.25
Last address
172.17.9.30
Subnet Mask
255.255.255.248
Usable host
CIDR
/29
-
Wireless Vlan
Address
Network address
172.17.9.32
Broadcast address
172.17.9.35
First address
172.17.9.33
Last address
172.17.9.34
Subnet Mask
255.255.255.252
Usable host
CIDR
/30
Page 40 of 47

201000096 - 201000129 - 2010000413
Sunil Seneviratne
13th June, 2013
Wireless LAN
Address
Network address
192.168.15.0
Broadcast address
192.168.15.255
First address
192.168.15.100
Last address
192.168.15.149
Subnet Mask
255.255.255.0
Usable host
50
CIDR
/24
-
Addressing Table
Device
Hidd (Router)
Hidd SW Core
Hidd SW Distribution 1
Hidd SW Distribution 2
Hidd SW Access 1
Hidd SW Access 2
Hidd WRS Access point
PC1 (Manager)
PC2 (Staff)
-
Interface
IP address
Subnet mask
Fa0/0.15
Fa0/0.23
Fa0/0.31
Fa0/0.35
Vlan 31
Vlan 31
Vlan 31
Vlan 31
Vlan 31
WAN
LAN/Wireless
NIC
NIC
172.17.9.14
172.17.9.22
172.17.9.30
172.17.9.34
172.17.9.25
172.17.9.26
172.17.9.27
172.17.9.28
172.17.9.29
172.17.9.33
192.168.15.1
172.17.9.17
172.17.9.1
255.255.255.240
255.255.255.248
255.255.255.248
255.255.255.252
255.255.255.248
255.255.255.248
255.255.255.248
255.255.255.248
255.255.255.248
255.255.255.252
255.255.255.0
255.255.255.248
255.255.255.240
Default
Gateway
N/A
N/A
N/A
N/A
172.17.9.30
172.17.9.30
172.17.9.30
172.17.9.30
172.17.9.30
172.17.9.34
N/A
172.17.9.22
172.17.9.14
VLAN Table
VLAN ID
15
23
31
35
Name
CustomerService
Manager
Native
WRS
Network
172.17.9.0/28
172.17.9.16/29
172.17.9.24/29
172.17.9.32/30
Tables: IP Version 4 Private Addressing Scheme/LAN Configuration/Frame Relay
Page 41 of 47

201000096 - 201000129 - 2010000413
Sunil Seneviratne
13th June, 2013
Figure 1: Appropriate Routing Protocol
Figure 2: Proper Login Banners
Page 42 of 47

201000096 - 201000129 - 2010000413
Sunil Seneviratne
13th June, 2013
Figure 3: Encrypted Passwords on Routers/Security Measurements
Page 43 of 47

201000096 - 201000129 - 2010000413
Sunil Seneviratne
13th June, 2013
Figure 4: Security Measurements
Page 44 of 47

201000096 - 201000129 - 2010000413
Sunil Seneviratne
13th June, 2013
Figure 5: Redundancy Measurements
Page 45 of 47

201000096 - 201000129 - 2010000413
Sunil Seneviratne
13th June, 2013
Figure 6: Wireless Access Point
Figure 7: PPP between NOC and BIX
Page 46 of 47

201000096 - 201000129 - 2010000413
Sunil Seneviratne
13th June, 2013
Figure 8: IP NAT on NOC Router
Page 47 of 47

Polytelecom Networking PBL Project Report

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Polytelecom Networking PBL Project Report

Caricato da

Copyright:

Formati disponibili

Bachelor of ICT Assessment Cover Sheet

Poly Telecom Networking PBL Project Report

Networking and Data Communication 2

Ali Alaali - Habib Khamis - Ahmed Saeed

201000096 - 201000129 - 201000413

Due Date: 13th June, 2013

Date submitted: 13th June, 2013

This assignment is our own work.

Poly Telecom Networking PBL Project Report

Poly Telecom Networking PBL Project Report

Poly Telecom Networking PBL Project Report

Step 1.2: Implement an appropriate routing protocol

Poly Telecom Networking PBL Project Report

Step 1.3: Proper login banners

Step 1.4: Encrypted passwords on routers

Poly Telecom Networking PBL Project Report

Poly Telecom Networking PBL Project Report

Poly Telecom Networking PBL Project Report

Step 3.2: Implement a redundancy measurement

Poly Telecom Networking PBL Project Report

Poly Telecom Networking PBL Project Report

Poly Telecom Networking PBL Project Report

Poly Telecom Networking PBL Project Report

Step 8.2: Access list for student in the training facility

Step 8.3: Access list for the customer branches

Poly Telecom Networking PBL Project Report

Step 8.4: Access list for the Internet

Poly Telecom Networking PBL Project Report

Results and Conclusions

Poly Telecom Networking PBL Project Report

Poly Telecom Networking PBL Project Report

Poly Telecom Networking PBL Project Report

Poly Telecom Networking PBL Project Report

Frame Relay (PVCs)

Poly Telecom Networking PBL Project Report

Seef WRS Access point

Poly Telecom Networking PBL Project Report

Network Operations Centre (NOC) - Hoora

Training Facility (Students)

Poly Telecom Networking PBL Project Report

Training Facility (Staff)

Poly Telecom Networking PBL Project Report

Wireless LAN (Staff)

Wireless LAN (Student)

Frame Relay (PVCs)

Poly Telecom Networking PBL Project Report

PC6 (Customer service)

PC7 (Website developers)

PC9 (IT department)

PC10 (Staff Training facility)

Laptop1 (Student Training facility)

Laptop2 (Student Training facility)

Hoora WRS Access point (Staff)

PC8 (WRS - Staff Connection)

Poly Telecom Networking PBL Project Report

Poly Telecom Networking PBL Project Report

Customer Branch - Riffa

Poly Telecom Networking PBL Project Report

Poly Telecom Networking PBL Project Report

Frame Relay (PVCs)

2nd Site Name dlci

Hamad Town 405

Poly Telecom Networking PBL Project Report