Week 4_Project Part 2_DNesbit

ABC COMPANY WAN DESIGN 1

Types of Equipment

Kanita Lukevich, Jared Miner, David Nesbit II, Jessica Petruff

Dr. Ryan Rucker

NT2799: Network Systems Administration Capstone Project

July 12, 2015


As we begin to build our Wide Area Network for the ABC Company, we have to

look at several different pieces of equipment that will take many factors into

consideration. These factors include the companies needs at each of the office

locations and the security needs of the network considering this company needs to send

decently sized files over the network and quickly.

ABC Company is engaged in the development of audio and video special effects

software for the entertainment and advertising industry. “The World Wide Web is a

good example of network multimedia and its manifold capabilities. More than 85 percent

of personal computers sold are multimedia capable. This hardware revolution has

initiated a software revolution that has brought a wide range of audio- and video-based

applications to the desktop. It is not uncommon for computers to run video editing or

image processing applications (such as Adobe Premiere and Photoshop) in addition to

basic "productivity" applications (word processing, spreadsheet, and database

applications). “(CiscoStems, 2012). Multimedia is a combination of media elements

such as text, audio, image, and video in a digital form used by many devices such as

the PC.

For the ABC Company my thoughts for setting up the world wide network would

be as follows. Initially, I would start with the San Francisco, CA site because it is the

headquarters of the company so the Active Domain would be there. It would be the start

of the forest domain for the entire company and have all of the active directory content

from the other regional sites.


With the active domain in San Francisco being the Forest Root Domain, I would

be able to create the other domains as follows: Detroit (ABC_DET), Washington DC

(ABC_WASHdc) and the main server ABC_Company, Tokyo(ABC_Tok), Sao Paulo

(ABC_SP), Liverpool, Eng(ABC_LVRP), Paris Fran(ABC_PAR), Tampa (ABC_TAM),

and Indianapolis(ABC_IND). The questions of what type of security will be enables,

who is going to have access to what are just a couple of questions that need answered.

With all of these domains I would absolutely communicate with the IT department from

all of the tree domains to inform them that all of the rights, passwords, permissions and

the basic organization of the domains would come from the President and/or Vice

president via the San Francisco Forest Domain.

If the funding is available we would could purchase a block of class C IP

addresses and then we could use NAT on all of the Domain routers. That would allow

for network communication among the company and, when need be, internet

communication for those who need to contact customers, staff or communicate via

email or other means. Each tree domain should be connected to the Forest Root

Domain via the ISP.

Each tree domain should be established in the city’s office building with at the

minimum six servers per city domain. The servers will be named for the city they

represent along with the department (Finance/Sales, Creators, IT and Management).

Each department would qualify for their own file/share server with the worldwide

company. The file/share servers would be accessible by any employee in any city in

that department. That will allow each department to be efficient and redundant with


information on the servers. For example an employee in Tampa could easily answer

questions or sever a customer in Tokyo by having access to their server.

I would have the topology of a Star and a Bus configuration for redundancy with

each department having their own secured access to their file server. However, all

departments would be connected to the all-in-one scanner/printer/fax server; which

could be expanded to an additional printer or all-in-one dependent upon company

growth and need.

Management and IT would have access to all servers via Windows Server 2008

and the Organization Units, in all cities for ease of troubleshooting and maintenance

and monitoring of the network. Also we can create the Organization Units through the

domains. Here we can control the group policy, permissions and rights of each

department and their servers. I would make the OU’s Finance/Sales, Creators, Call

Center, IT and Management.

Each office will be set up as their own Client Server Network. This will mean that

there will be a local server at each office in which all the necessary files, printers, and

applications can be shared. Within the headquarters office in San Francisco, we will

have a corporate server that will allow all the offices to be connected in order to further

share any and all necessary files, applications, and anything else that is of great

importance to ABC.

The best topology for our network will be the Star topology. It’s not as reliable as

mesh, as a failure in the hub could potentially bring the network down, but it is much

cheaper than mesh. It also allows for easy expansion to both the WAN network as well

as for adding new computers and equipment to the individual offices. (Lawrence, n.d.).


The first thing that will need to be do is decide on an operating system, and install this

onto all computers in the company. In this case, we could use Microsoft Windows XP,

as it provides networking capabilities incorporated in the OS. Then we can start

networking the computers.

Each office will have a modem to connect to the Internet, and this will be

connected to a router. The router will be cabled to the main PC, but otherwise it will be

connected to all other computers wirelessly. Cat 6 twisted pair cabling will be used for

all cabling necessary, RJ-45 jacks will also be used. The routers will be VPN-enabled

routers, to allow connectivity between offices. For the larger offices, for example the

headquarters in San Francisco, a patch panel will be used. This will be placed in a

server room, and will be connected to the router via Ethernet cable. The patch panel will

make it easier and more organized to connect a large number of computers.

Each location would be comprised of a client/server network and would

interconnect via a router to each location on the network. The main server would be

located at the San Francisco office and the other locations would share its resources.

Other equipment to keep in mind for each location would be a network printer and

telecommunications service. (Rouse, 2008)

Wireless connections will be the norm in most offices. These will be run using the

standard 802.11N, which has a nice range for computers in the office. If the range is not

long enough, such as in the case of multiple buildings at one location, a secure WAPs

can be used to extend the signal. Fiber optic cabling will also be used to connect the

buildings to each other, from server room to server room.


This is the detailed outline of the beginning of the network that is going to be

created in the new buildings. With this new network, building and infrastructure we will

be beginning from the ground up. The standards and codes along with the building

standards and codes will be discussed along with the cabling, network and computer

equipment (Olivero&Woodward, 2012).

The ANSI/TIA standards will be discussed in the following paragraphs

Standards and Codes

1. Cable Standards and Codes from ANSI/TIA

i. ANSI/TIA-568-C.0 Generic Telecommunications Cabling

ii. ANSI/TIA-568-C.1 Commercial Building Telecommunications

Cabling Standard

iii. ANSI/TIA-568-C.2 Balanced Twisted-Pair Telecommunications

2. Cabling and Components Standard

iv. ANSI/TIA-568-C.3 Optical Fiber Cabling Components

v. ANSI/TIA-606-B Administration Standard for Commercial

vi. Telecommunications Infrastructure Cable Standards from ISO

i. ISO/IEC 11801 Generic Cabling for Customer Premises

ii. ISO/IEC 11801 Class EA

3. Building Standards and Codes

i. ANSI/TIA-862-A Building Automation Systems Cabling Standard


ii. ANSI/TIA-942-A Telecommunications Infrastructure Standard for

Data Centers

iii. NFPA 5000, Building Construction and Safety Code

iv. NFPA 70: National Electrical Code

v. NFPA 101: Life Safety Code

vi. NFPA 1: Fire Code, which include:

a. NFPA 54

b. NFPA 58

c. NFPA 30

d. NFPA 13

e. NFPA 25

f. NFPA 72 (Olivero&Woodward, 2012).

The building will have a traditional star network run through the backbone

network from the basement where the telecommunications room will be located. We

can route through the floor plan throughout the offices using horizontal cabling. The

horizontal cabling will connect to the servers from the basement telecommunications via

vertical cabling through the HVAC system through the main equipment room or wired

through the basement ceiling and first floor.

The plan to route cable via conduit pathways from the basement to the horizontal

cabling plan with fiber optic cabling to the wall outlets, switched and hubs and routers.


The routers will be located specifically in the reception area, IT Chief's office, COO, CIO

and CEO's offices. With the main router in the telecommunications room.

The cabling for the infrastructure, since it is a relatively small network, for the

backbone network I would suggest the following cabling guidelines. Starting from the

demarcation point we are going to run fiber optic cable to the patch panel in the

basement to the maintenance room, then to the telecommunications room to the patch

panel. From the patch panel we can break down cables to voice and data sections.

From there to the server rooms we can continue with more fiber optic cable into the wall

outlets and computers with patch cables, also fiber optic.


The telecommunication room will run data cabling to the server rooms for the

WAN/LAN connections. Each server room will have the capability to have ten plus

servers per room. The servers will be on the racks to keep them organized. Before we

connect all the cables to the servers we will splice the end of the fiber optics with the

appropriate terminal ends to be introduced into the servers. We will then make these

runs from the server room to five switches.


The components used to design a structured cabling system should be based on

accepted specifications and should allow the following applications: analog voice/digital

voice, 10Base-T, 100Base-TX, 16Mbps Token Ring, RS-232, etc. to use the cabling

system. The components should also adhere to performance specifications so that the

IT Chief installer or IT staff will know exactly what types of applications will be

supported. All of these runs will be marked for identification and then grouped together

with Velcro ties.

From here we will start with our vertical Cat5e cabling, because the distance is

greater than 328feet, via the HVAC ducts to the first, second, third and fourth floors and

connect to the switches on each floor. Every floor will be cabled the same since the floor


plans are the same. This is where our horizontal cabling takes over. We will run the

Cat5e cable to the wall jack outlets where the RJ45 outlets will be placed into the walls.

We will have three wall outlets with two RJ45 outlets. To keep attenuation down to a

minimum we will make the patch runs from the wall outlets to the workstations fiber

optic cabling.

We will be able to split the fiber optic cables into the proper areas for VoIP and

data connections, respectively for phone and internet connections.

Equipment Quantity Cost


Fortinet FG-100D-US

FortiGate-100D Network

Security

5 $1,759.99/unit

HP ProLiant DL180 G9

2U Rack Server - Intel

Xeon E5-2609 v3 1.90

GHz

20 $1,959.99/unit

Avatar A-Workstation Mid-

Tower ATX Server

System Intel Core i7-4770

3.4GHz 4C/8T 16GB

120G SDD (boot-up drive)

2TB SATAIII 7200RPM

HDD Operating System

Windows 10 professional

5 $999.99/unit

HP Envy Desktop

Computer With 6th Gen

AMD A10 Quad-Core

Accelerated Processor,

700-406/216/056

75 $645.99/unit

HP Smart Buy LV1911 40 $84.99/unit


Black 18.5" 5ms

Widescreen LED-Backlit

LCD Monitor 200 cd/m2

600:1 (static) / 3000000:1

(dynamic)

BELKIN C-PP5-48-F-BK

48-Port Rack-Mount

Patch Panel - CAT5e 700

Series

5 $147.99/unit


REFERENCES

CiscoStems. (2012, 16 October). Internetwork Design Guide -- Designing Internetworks for multimedia. Retrieved from Cisco: http://docwiki.cisco.com/wiki/Internetwork_Design_Guide__Designing_Internetworks_for_Multimedia

Lawrence, M. (n.d). What is a WAN Topology?. Houston Chronicle. Retrieved from: http://smallbusiness.chron.com/wan-topology-68492.html

Networks, B. (2015, July 12). Improving Performance, Availability, and Security of Distributed networks. Retrieved from Barracuda: https://www.barracuda.com/products/ngfirewall

Oliviero, A., & Woodward, B. (2012). Bonus appendix: telecommunications to accompany cabling. (Fourth ed.). Hoboken, NJ: John Wiley & Son, Inc. Retrieved from http://www.wiley.com/go/permissions.

Rouse, M. (2008). client/server(client/server model, client/server architecture). TechTarget Retrieved from: http://searchnetworking.techtarget.com/definition/client-server

Week 4_Project Part 2_DNesbit

Documents

Transcript of Week 4_Project Part 2_DNesbit