Server Management and Security Best Practices

This assignment focuses on essential aspects of server management and security. It emphasizes the importance of remote access tools, hardware failure monitoring, server utilization tracking, and secure account management. The text highlights the need for regular password changes, robust firewalls, and penetration testing to mitigate security risks. Additionally, it stresses the significance of contingency planning to address potential power outages or overheating issues.

NETWORK DESIGN 1
Network Design Assignment
Tatum Spencer

NETWORK DESIGN 2
Contents
Introduction.................................................................................................................................................3
Assumptions in the Design..........................................................................................................................3
Network Requirements...............................................................................................................................3
Network Design...........................................................................................................................................4
TTF WAN Architecture [1]............................................................................................................................4
Technology..............................................................................................................................................4
Cabling.....................................................................................................................................................4
Security....................................................................................................................................................4
Hardware Configuration [4][6]................................................................................................................4
Diagram...................................................................................................................................................5
Directory Structure [7].................................................................................................................................7
Server Design [4][6].....................................................................................................................................8
TTF HQ.........................................................................................................................................................9
Server Farm Access Layer............................................................................................................................9
Access layer.............................................................................................................................................9
NIC Teaming............................................................................................................................................9
Server Monitoring.....................................................................................................................................10
Router [3][5]..............................................................................................................................................10
Router Specification..............................................................................................................................10
Router Protocols....................................................................................................................................10
Security Policies and Plans [5]...............................................................................................................10
User Documentation.................................................................................................................................12
Ongoing Maintenance Support.................................................................................................................13
References.................................................................................................................................................15

NETWORK DESIGN 3
Network Objectives
Introduction
The network for Talon Textile Fasteners (TTF) is designed to satisfy the following requirements:
1) Security – the network should not allow unauthorized access, both physically and
logically.
2) Speed – the network has to have adequate bandwidth. It should meet demand during
peak usage.
3) Reliability – the network should overcome redundancy and make sure that failure of one
system doesn’t bring the entire network down.
4) Scalability – the network must support sustaining scalability without the requirement to
rebuild the system every time a change is implemented.
Assumptions in the Design
1) TTF has a weak and old network design. Thus, it would be wise to build a new network
from scratch.
2) TTF wants all the circuits to be built.
3) Each department of TTF is located within accessible means. There are a few global
offices too.
4) The physical security of the network has to be maintained.
5) TTF does not share its network with other businesses.
Network Requirements
TTF’s major network traffic includes file sharing including accounting details, brochures, reports,
personnel profiles and financial information. The network should take care of various databases
and web pages too. At this moment, TTF needs video teleconferencing and VoIP services.

NETWORK DESIGN 4
Network Design
TTF will have a wide area network connecting several offices to the main headquarters. The
wide-area-network is connected to the company’s backbone network. The backbone network
connects all local-area-networks in the branch offices to the wide-area-network. Every
employee at TTF will be connected to a department local-area-network, which supports
departments to share database information and files.
In the high level, TTF’s WAN follows a star architecture. However, ring architecture would be
easier to manage. Star architecture is faster because information does not travel around a ring
to reach headquarters. TTF does not require a mesh network because it is expensive.
TTF WAN Architecture [1]
Technology
Asynchronous Transfer Mode and Frame Relay are considered for the TTF WAN’s physical and
data layers. Ultimately, 1000Base-FX Gigabit Ethernet is chosen over fiber optic cabling [2].
Both Frame Relay and ATM have latency issues during protocol conversion. The entire network
makes use of the Gigabit Ethernet. This eliminates the need for complex protocols in the TTF
network. Also, the company can make incremental investments during expansion. In case, TTF
plans to open a new branch, they don’t have to worry about anything. Ethernet is shared using
hubs because it is cheaper than fitting the entire building with fiber optic cables.
Cabling
TTF WAN has connections between the branch offices and headquarters. Fiber optic cables can
be laid for this connection. It is recommended for TTF to use leased lines.
Security
Traffic into the network is managed by TTF HQ. There are points to limit the amount of
incoming data. Redundancy can be built in one of the systems to handle problematic situations.
In case the HQ network faces bottle necks, entry points can be redirected to other offices.
Because data has only one entry point, LANs don’t have any firewalls. Security is taken care of
by the anomaly detector and firewall in the TTF HQ machine.
Hardware Configuration [4][6]
The organisation relies on fiber cables. Media converters are used because departs in TTF have
LANs with 100 Mbps Ehternet over the normal Cat 5e cables. The core office can use a Layer 3
switch. This will let the company configure virtual LANS in the future. For instance, sales
managers can use the same circuit when they are within the company showcasing details to
customers. For a Layer 3 switch, Cisco’s 3750 X Catalyst 48P-S is preferred. In the distribution

NETWORK DESIGN 5
layer, there can be four Layer 2 switches (one for LAN, and one for demilitarized zones). The
headquarters has 6 employees broken into three departments (management, sales, technical).
Thus, four switches will be required. Switches act as separate point-to-point connections. This
reduces the chances of collisions.
Diagram
The above diagram shows the TTF WAN configuration. Here are few important points:
1) Each location has its very own router.
2) Each location is connected to the main headquarters
3) Each location has media converters
4) All traffic is routed to a single point

NETWORK DESIGN 6
The backbone network of TTF would look like the following diagram:

NETWORK DESIGN 7
Directory Structure [7]
The logical structure of TTF can be defined as the following:
The forest has two major trees;
1) Tree 1 – this is deployed for security reasons. This has major entities like the certificate
server, the automation server and other enterprise management content.
2) Tree 2- this contains TTF’s computing objects and user accounts that are required for
handling machinery operators, database stuff, marketing teams and e-commerce.
Active directory domains and domain name service domains have similar hierarchical
structures. Naming conventions of DNS are similar to the naming of AD domains. For example,
talon.ac.au, marketing.talcon.ac.au – in simple terms, an organisation’s namespace for the
active directory and DNS domains have similar structures. Active directory clients and domain
controls use resource records to determine the IP addresses. For example, real computer
system: CIO PC desktop can have a DNS name as cio.talcon.ac.au.Sites would be the physical
arrangement of various domains in different branched of TTF.
As noted, Tree-2 domain holds details that interest administrators and users. AD does not use
user or computers to administer boundaries.Instead, organisational units (OU) are used to take
care of the boundaries. Tree-1 breaks into the following organisational units.
1) UoE – all staff accounts are maintained here
2) UoEM – all centrally managed computers and services
3) UoER – all dissolved resources
4) UoES – all customer details are stored here
5) Operations – all operational administration groups
6) ServiceUsers – All accounts and groups for central services

NETWORK DESIGN 8
With respect to sites for the TTF network, there are three major categories. This includes
/clients (ServiceUsers, UoES,UoE), /marketing (UoE) and /operations (UoEM,UoER,operations)
The clients folder can take care of all current clients, previous clients and prospects. Previous
clients would be those who acquired services from TTF but left. Details of these customers
should be moved and handled by a separate department. Client folders can be accessed and
managed by the admin staff, sales staff and service manager. This is an open site; thus, it should
not have customer payment details. Payment details must be stored carefully in
/operations/finance. This is a secure site and secured folder in the system.
Marketing is an important part of TTF network. This is where organizational units that take care
of adwords, co-marketing, contacts, campaigns, social media marketing, road maps and website
management are held. Since TTF is venturing in e-commerce, this is a separate site. There are
organizational employees handling marketing information. These details cannot be accessed by
everyone in the company. However, they can be accessed by admin staff and marketing staff.
Operations site is secured for important operations and file management routines. This site is
handled by managers and owners of the company. It carries groups to take care of finances,
forms, client memos, insurance, products and services, sales, processes and procedures and
employee information. Information in this site is secured from most employees. The operations
folder can be accessed by a known and authorized group of administrative employees,
managers and owners. Most staff members are not allowed to enter into area.
Clients
\!Old
\!Prospects
\ABC Client
\DEF Client
\GHI Client
\JKL Client
\etc.
\Marketing
\Adwords
\Blog Fodder
\Posted
\Campaigns
\Fall Push
\HP - MS - Office
\Spring Microsoft
\Summer
\Co-Marketing
\Contacts - Mailing Lists

NETWORK DESIGN 9
\Graphics
\Handouts and PPTs
\Postcards
\PPTs
\Newsletter
\Press Releases
\Roadmaps
\Social Media Marketing
\Video - YouTube
\Web Site
\Backup
\Design
\Source
\Operations
\Client Memos
\Finances
\QB Backups
\Reports
\Forms
\Insurance
\Processes and Procedures
\Products and Services
\Sales
\Staff Stuff
\Employee On boarding Process
\Job Postings
\Admin Bookkeeper
\Sales Outside
\Tech I
\Tech II
\Personnel
\Strategy
\Mastermind Group

NETWORK DESIGN 10
Server Design [4][6]
The servers used in TTF can be classified into three major categories. Servers provide the
following network-based services:
1) DNS – this is used to resolve hostnames to corresponding IP addresses
2) DHCP – This is used by end devices to get IP addresses along with other parameters like
the IP Address of DNS servers, subnet mask and default gateway from the DHCP server.
This server makes sure the IP Addresses are unique. No two sites can have a similar IP
address. IP address poll management is done by the DHCP server.
3) Directory Services – all details of applications that structure data about the end user and
network resources is managed here.
4) Security and Network Management Server – TTF can rely on Cisco Security Monitoring,
response system and analysis. These servers reduce false positives between end-to-end
view of the network. Promote awareness of unexpected network behavior. MARS offers
recommendations for effective threat removal.
5) Manufacturing application Servers – this helps in handling the database, asset security,
supervisory computers and factory talk servers.
TTF HQ
At TTF HQ, all servers for the TTF networks will be housed. This includes the database,
department file and print servers. There are two domain controllers to handle the employees.
There is a single database server to have details of TTF. IP Addresses are assigned at LAN level
dynamically. HQ will also have a SQL server, application server, IM server and DNS Server.
Options for these servers would be HP Proliant Line or Dell PowerEdge line.
Server Farm Access Layer
Access layer
The access layer represents the physical connectivity to the actual server farm. Applications on
the servers that take care of the manufacturing zone are business-critical ones. Thus, they need
to be dual-homed. The layer has to be connected to the access layer switches. Layer 2 access
model is linked to the aggregation layer using the IEEE 802.1Q trunk. The aggregation switch
takes care of layer 3 processing. The layer model supports VLAN instances throughout the
access layer switches. This allows TTF to rack servers anywhere.
NIC Teaming
TTF needs a mission critical network that can tolerate downtime. To eliminate single server
failures, NIC Teaming is used. NIC Teaming provides software and drivers for failover

NETWORK DESIGN 11
mechanism. In case a single NIC fails, the other one takes over and prevents the disruption of
operations.
Server Specification
TTF has to create three major server functionalities: DNS, print and file servers. These
functionalities have similar resource needs. These servers are not processor centric. This means,
TTF servers don’t need high amounts of memory. Proper virtualization can resolve most of its
requirements. The virtual server design requires a single VMware ESX server with abundant
local SCSI Storage, processing power, network bandwidth and memory. It has to support all
virtual machines that can be shared across departments. If a single ESX server fails, there should
be a redundancy system to keep all the machines running. This is why TTF needs multiple
VMware ESX server installations. Redundancy can be achieved through shared storage – SAN.
ESX Server is used because it supports three different physical server roles. Since the network
design involves three different sites (/client, /marketing, /operations) the servers can be
assigned to each role separately. This helps in breaking up tasks and makes maintenance easy.
And, multiple network cards can be used to provide load balancing and network redundancy.
ESX Servers support AMD-Opteron and DUAL Intel-Xeon processors. Dual-core processors are
easily supported by the ESX server. The organization can choose to install a minimum of 4GB
RAM in the server. With time, the amount of RAM can be increased as the number of machines
supported by the server increases. If the host server has dual-core processors, 8GB would be
recommended.

NETWORK DESIGN 12
For TTF, RAID-1 or disk mirroring is sufficient to take backup of data. However, RAID-5 offers
quicker read access and are highly recommended for organizations. A hot spare drive can be
included to offer immediate failover if a hard drive fails. Additional redundancy can be
introduced through remote access interfaces (Dell DRAC, HP iLO) and redundant fan kits. To take
care of failovers, VMware Consolidated Backup can be used. This is a backup method for
centralized backup of files from the server. This is a standard backup agent with a single instance
in the proxy server. Backup traffic is overcome through the use of Fiber Channel tape devices.
When compared to print and file servers, DNS servers require higher hardware configuration.
The file and print servers are responsible for sending and receiving traffic from client
workstations. TCP connections can be used to handle these sessions. The benefit of using ESX
Servers would be its ability to schedule efficiently. Multiple processors can be hosted. The TTF
server requires only 512 MB RAM. This is because ESX Servers handle memory management
efficiently with transparent page sharing across several virtual machines. This will be a cost
effective method for TTF.
For Networking, virtual switches are used and the ESX Server’s NIC cards are useful. Since TTF
has staff moving across branches, multiple physical NIC adapters can be connected to a single
virtual switch. This takes care of load balancing.
Since a virtual Server is proposed for TTF, everything gets configured into a set of files. Virtual
disks of equal sizes and disk capacity of 8GB are suggested. Implementing shared storage
removes the dependency various machines have on the ESX Server. There are three types of
storage to choose from. This includes NAS, SAN and iSCSI SAN.
Server Test Plan
1. Test 1 – Maximum client capacity
a. To support the growing needs of TTF to handle various load conditions and to
characterize its peak capabilities
b. The maximum steady state DHCP transactions or requests handling capacity
should be gauged. The server performance should not drop with additional
packets or traffic seeping into the server
1. Test 2 – Maximum transaction rate

NETWORK DESIGN 13
a. To test the maximum number of transactions the server can sustain without
losing packets or causing errors. Based on the transaction rate, network
configuration information should be defined.
b. State full traffic should be created. Based on specific user-cases, traffic must be
fine-tuned into the system.
c. Number of users, request timeouts, ramp up rate and number of retransmissions
from server should be recorded.
2. Test 3 – Optimal client Response time
a. This test should make sure the server gives acceptable performance with optimal
client response time
b. The rate of arrival of server requests should be controlled to make sure the
server can handle more requests
3. Test 4 – Server resiliency
a. Test characterizes how resilient the servers are during failure conditions or
adverse environments
b. Assess services in TTF that drop due to active failover transition
c. Outage due to human errors and device failures should be recorded
4. Test 5 – Active Directories
a. The best way to test this with the server OS installed in the virtual machine.
b. A domain has to be created inside the virtual domain. These domains should
match the various sites, organizational units and groups involved in TTF.
Router Specification
The network relies on a wired Ethernet connection. It streams numerous files. This is why
Ethernet cables with routers and NAS drives should be used. As the network expands, TTF might
have to invest on more Ethernet devices. The standard Ethernet cable would be Cat5. Since
devices used in this network use Gigabit Ethernet, it would be wise to have Cat5e. This supports
fast Ethernet devices and networks. Cat5e will give TTF the freedom to take advantage of 1
GBps. If TTF does not wise to run Ethernet cables, powerline adapters can be used. These
adapters use electrical outlets to extend network connections. Typical routers have 4 Ethernet
ports. These ports can be used for storage, servers and PCs. A switch can be purchased to
support more ports. This is required when the network expands. 3Com OfficeConnect Gigabit
PoE Switch is apt for the TTF office.

NETWORK DESIGN 14
Server Monitoring
Tests should be performed on the server and the network has to be maintained. Checks should
be performed periodically. This will help in getting regular status updates of the system. The
monitoring system should respond if there are unsuccessful transactions or performance drops.
For example, the server has to be up all the time and ensure the e-commerce system of TTF is
working fine. Data collected from servers can be presented in the form of graphs using Cacti.
This is a tool for collecting packet information and other details about the server. It is an open
source code that can be used without spending much. Nagioscan be used to monitor the
servers and services. This is also an open source code. It is modifiable, scalable and versatile.
There are many plug-ins for monitoring various services in the server. It has reporting and
availability functions too.
Router [3][5]
Router Specification
The routing block takes care of Layer 3 in the TTF network. It connects WAN, the internet, the
main data centre HQ and access blocks in the branch office. TTF can use a regional telephone or
cable server provider with link rates of 10 GbE for the connection. The core backbone router
(HQ) forwards all traffic between the departments, data centre and branch offices. Brocade’s SX
Series of chassis would be an ideal choice for the router. They can be configured with Multi-
Chassis Trunking to ensure high availability and high performance. The data centre has servers
to take care of email, administrative applications, stock control and e-orders. The router blocks
routes that can direct customers and employees to mission-critical channels.
Router Protocols
Routers are responsible for connecting networks together. It is based on information in the
routing table. There are several different types of routing protocols. TTF canuseEnhanced
Interior Gateway Routing Protocol (EIGRP). This is a hybrid protocol that blends Link state and
distance vector routing protocols. It sends partial updates and maintains neighbour
information.
Security Policies and Plans [5]
The CIO is responsible for creating, maintaining, implementing and administrating TTF’s security
policies, procedures, guidelines and standards. Meanwhile, it is the responsibility of the other
employees to ensure security on a daily basis. TTF can hire a security manager to take care of
individual and physical safety of the system. They should check if servers are compromised or if
there are other incidents in the system. System access has to be controlled in many levels. This
can include end-user passwords to make sure only trusted employees are allowed to enter into
the system. At TTF, logon and logoff processes should be handled professionally. If there has
been no activity in a specific system, that workstation could be kept in stand-by mode.
However, these are advanced security policies for TTF. Access to the system should be provided

NETWORK DESIGN 15
by the CIO who belongs to Tree-1 in the Active Directory. It is critical for the organisation to
have established access paths. This means, changes like reconfiguration of routers, adding
remote lines, new software and change in network addresses should be done with predefined
access paths. This way unexpected changes can be prevented.
The CIO should have proper data and program backup methods. There should be multi-user
servers and communication channels to make periodic backups. These servers should be
handled by trusted partners. In the longer run, the network should support remote printing too.
This means, only authorised persons will be allowed to access the printers. CIO must have audit
information about all activities that were carried out in the system from a centralised location.
If there are risks in information security, these should be identified. Risks in relevant areas of
TTF’s operations should be assessed, including the following:
1) Employee management
2) Employee training
3) Detecting, preventing and tackling attacks
4) Designing and implementing effective safeguards
User Documentation
At TTF’s HQ several network functionalities can be carried out. This includes network printing
using Windows services and TCP/IP protocols. The printer server is responsible for producing
printouts. Likewise, there is a separate computer in the network to let employees scan
important documents. These scans can be mailed to their emails respectively. With respect to
management, these servers are handled by the Administrator. Their details are carefully keyed
into the system.
Several types of connections are established in this system. The most important one would be
the TCP/IP link. Network shared printing is achieved using TCP/IP protocol. You can use
DHCP/BOOTP/RARP protocols to configure the IP address automatically. This protocol works on
all operating systems like Linux and Windows. The servers support Domain Name Service client
function. This service can be used to access the printer and scanner server. The DNS name is
sufficient to access these devices. Port 9100 is the common port for printing protocols. This port
should not be used with any other servers. To send and receive mail, the SMTP client protocol is
used. The Internet Printing Protocol is applicable for users who want to print documents from
remote locations. This means, branch offices can use IIP to print documents in HQ. TELNET is a
command line configuration that can be used to print and scan documents also.
To manage devices like network ready machines, routers and computers, the Simple Network
Management Protocol SNMP is used. If you want to change configuration settings, HTTP
protocols can be used.

NETWORK DESIGN 16
TTF network has special utilities to help in managing all machines that are connected to the
network. Machines in the TCP/IP environment can be managed using this professional utility
program. This utility program is protected by a username and password.
If you are a network engineer, maintaining this system, the following lines will be useful in
setting up your network.
Installing Printer
Before you connect the printer to your system, a software has to be installed and configured.
Appropriate TCP/IP network settings should be configured in the machine. Most devices come
with CD-ROM that can be used for installing the right packages.
To use the printer in the TCP/IP environment, the IP address and subnet mask has to be
configured. The IP address assigns the system to a print server, which could be in the same
logical network as the main, host PCs. If you don’t want it to be attached to the host computer,
you should configure the subnet mask and gateway addresses appropriately. The IP address is a
collection of numbers to identify devices attached to the particular network. This network relies
on the DHCP server, so the printer server would receive its IP address automatically. The DHCP
server provides the IP address.
To configure network settings, the LAN control panel is useful. This control panel has nine major
sections. This includes the node name, IP address, WINS, Boot method, DNS server, APIPA,
Config and WINS server. The network control panel has static modes where IP addresses can be
assigned and locked. To keep the network stable across several platforms, the auto mode can be

NETWORK DESIGN 17
used. The auto mode sets IP addresses automatically. It works well for the DHCP server. During
an adverse scenario, when the BOOTP is not available, the RARP server becomes useful.
The network engineer has to set up internet too. This has five major sections: POP3 server,
Mailbox, Mail address, Mailbox Name and SMTP server. Here, the SMTP server is extremely
important as it helps in sending and receiving messages over the network. Setup mail RX has
five major selections. This includes Notification, Poll Frequency, Auto Polling, Del Error Mail and
Header.
1) Auto Polling – checks POP3 for messages
2) Poll Frequency – the interval for checking if new messages are on
the POP3 server
3) Header – contents of the mail header
4) Del Error Mail – deletes erroneous mails automatically
5) Notification – sends confirmation of mail
Setup MISC
1. The Ethernet link in this network works in half duplex or 100BaseTX duplex mode
2. Time Zone takes care of time differences between Greenwich Mean Time and your
country.
3. If required, print server can be restored to default factory settings. Details of IP
addresses and passwords will be reset.
Ongoing Maintenance Support
The TTF network requires periodic maintenance. It has to be reconfigured based on recent
organisational requirements. If there are attacks or unexpected downtimes, the issue has to be
handled and prevented with the right kind of system changes. This could include server
upgrades, software changes, and modifications of router protocols and installation of new
stations.
Verifying that the backups are properly working and can be used at any time it is also needed. If
there is a need for deleting critical data, then we might need to perform some recovery tests,
so that if anything goes wrong, it can easily be restored. Also, the backups should be placed at
some locations that can easily be accessed when needed and cannot be exposed due to
security reasons.
The server should not be used to store all the data started storing from the very first day it was
implemented. All the old data including logs, emails, data and other files should be permanently
moved from the server to some data houses.

NETWORK DESIGN 18
Updating the Operating System (OS) is also a major need for the server to operate well in
different conditions. Updates scheduling should be used, so that the updates are automatically
encountered after every certain interval of time. We should be aware of all the latest releases
and the attack/threats, so that we can have a backup plan for that kind of threat if it happened
and we can respond back as quickly as possible.
The Control Panel where the hosting is should also be updated. Updating doesn’t mean that
only the control panel should be updated, but it involves updating the software associated with
it. For example we must manually be updating the PHP versions for any of the known
threats/bugs/fixes. Updating the Control panel does not automatically update the other
software, so we have to do it manually.
Check for application updates. The Web applications and web sites are most popularly known
for the attacks that are encountered in the current years so we have to make sure that the web
applications are well secured, especially the programs made in popular sites like wordpress.
We should make sure, if there are so dispersed servers, so we should have access to them any
time needed. If we encounter some difficulties accessing the server remotely, we should fix it
soon enough. The three major and essential tools for server management are remote console,
remote reboot and rescue control.
There should be proper monitoring for hardware failures. We should properly monitor the logs
for any hardware failure, overheating, disk access errors, page faults, and most of all the
network failure with the server. These issues can be very hazardous. There are mostly no errors
regarding the hardware, but it’s better to keep a monitor for these problems.
The server utilisation should be properly monitored because there can be issues related to
RAM, CPUs, storages, and the network utilisation. If the monitors display the maximum use of
these hardware devices, we might want to plan for upgrading and adding extra storages to
increase the utilisation as well as we can include a new server.
The accounts should be properly reviewed and monitored, because their can be changes in staff
where the accounts also can either change, or create new accounts for the new staff. In this
account, if the previous staff is no longer an employee of the organisation, their data is
consuming extra storage on the server. Storing old user accounts and old sites is a risky
situation for the organisation, because old account holders are very well known with workings
and they can easily exploit the servers.
Changing the passwords periodically is the best security solution that is needed and decreases
the chances of threats by almost 40%. Changing the passwords is very important, because the
passwords are shared with many staff members including the maintenance support teams.
There should be a regular check based on the security of the servers that is especially related
with leakages, the information stored, the sharing of passwords. There should be properly

NETWORK DESIGN 19
installed firewalls that prevent the attacks by a great percentage. These firewalls should
regularly be upgraded and checked for new updates from the providers. Regular Security Audit
checks should be arranged. Companies hire ethical hackers, especially to find out the leakages
in the systems of the organisation, which helps the organisation to make some plans to resolve
the leakages.
There should be regular checks that can uncover the most unexpected type of situations
including the failures of electric supply, failures of server due to overheating etc

NETWORK DESIGN 20
References
1. Freeman, R.L. (2004), Telecommunication System Engineering, 4th ed. New York, New
York: John Wiley & Sons, Inc..
2. Riley, S. and Breyer, R. (1999) Switched, Fast, and Gigabit Ethernet, 3rd ed. Indianapolis,
Indiana: New Riders Publishing.
3. Haugdahl, J. S. (2000), Network Analysis and Troubleshooting. Reading, Massachusetts:
Addison-Wesley Publishing Company, Inc.
4. McCabe, J. D. (2007) Network Analysis, Architecture and Design, 3rd ed. San Francisco,
California: Morgan Kaufmann Publishers, Inc.
5. Kaufman, C., Perlman, R. and Speciner, M. (2002), Network Security: Private
Communication in a Public World, 2nd ed. Upper Saddle River, New Jersey: Prentice Hall.
6. Oppenheimer, P. (2010), Top-Down Network Design, 3rd ed. Indianapolis, Indiana: Cisco
Press.
7. Microsoft (2017), AD DS Design Guide, Available at<https://technet.microsoft.com/en-
us/library/cc754678(v=ws.10).aspx>[Accessed 18 February 2017].