I NEED YOUR HELP I have to create a diagram representation of internet network for some company but...

>no, it's for a cookery class
What in the fuc-
>no i'm blackanese
Ah, my work here is done

Listen guys, I'm sorry but If I was clever I wouldn't be asking it on Jow Forums in such insolent way

>>That the service be available between the hours 8 am and 6 pm
>>That the service provides 99.9% availability during these times
>>That the network is secure and has an internet connection
>That the network provides a reliable service
>>The network should provide high performance for the end users
>>The new network should have sufficient capacity to support the business for 5 years.
none of this means anything to me

Just meme words
You wouldn't be able to do anything with it in visio anyway.

you'd only be able to say that is what happens, because you can't possibly imply any of that using a diagram

Looks to me like it's a problem solved with text explanations and has nothing to do with actual technology, the teacher is probably a brainlet as well.

this
refer to for an answer and then explain that's what it does

He's a pajeet, so go figure.
Assignment sheets are always so vague.

Would you guys say every set of 100 computers need a switch and separate firewall?

Are you seriously this fucking retarded? oriiblammies

>it's for college
>comes to Jow Forums for knowledge they are paying an actual institution to provide them with

Attached: IMG_20180223_182421.jpg (418x420, 24K)

Why are you asking here you colossal retard, there's a board for this sort of shit and a thread specifically for questions like these

which one is it? a

OP you're literally a fucking a retard.

This is the epitome of basic networking 101. You've obviously not learned a thing in your course and honestly: You need to drop out you fucking retard
This question proves it and shows that you haven't even seen what a fucking corporate level switch even LOOKS like. Fucking hell OP. You make me sick and I only hope that some poor manager doesn't have to put up with your incompetence in the workplace

Did you somehow miss the entire fucking board dedicated to technology on your way to make this thread?

this user has the right idea I'll sketch something up because i'm bored

fast-files.com/getfile.aspx?file=161169
visio file

Attached: Drawing1.jpg (1270x793, 81K)

I forgot to connect the other switches to the backbone

The back bone could be 10gigabit desu

Also following Cisco code I think i'm missing a layer

to get your marks you need something like so: omnisecu.com/cisco-certified-network-associate-ccna/three-tier-hierarchical-network-model.php

I believe

Attached: Drawing1.jpg (1270x793, 83K)

You can add two incoming internet lines, in that case double the fiber conversion, mention they're two different companies providing the lines

also the high availability switches can be in a group four like so

Attached: Drawing1.jpg (1270x918, 91K)

This looks like something someone would come up with who has never actually built networks in real life.

enlighten me please, as I would love to have more practical knowledge. I only manage companies no bigger than a couple hundred employees.

Pointless router, media converters are a common point of failure, just terminate the fiber direct, most firewalls support SFPs at this point. 4 friggin core "HA" switches, whatever the fuck that means but you have a single firewall. Most of this is a waste of time though as you have non-redundant power feeds. A single, flat subnet not broken up, including wireless like this is crazy, you have to use a floor plan and do a proper survey for proper density and placement. It goes on and on.

Let me help you with the basics, Ethernet is level 2 of the of OSI model. Data link level. Switches, routers, are level 3. Modems are outdated and should be retired by now.

user I'm assuming this isn't a 40% credit project for user, hell I don't even know if he can subnet

>Pointless router, media converters are a common point of failure, just terminate the fiber direct, most firewalls support SFPs at this point
oversight from me, I do run into a lot of the smaller companies that I manage with media conversion still. I didn't scale my network knowledge for this project.

>non-redundant power feeds
I guess? should I mark them all as dual PSU

>A single, flat subnet not broken up
There are two circumstances I'd care to break up the subnet
1. if I want my wireless to be isolated
2. If I want servers to be isolated

usability wise my /21 network would allow all the devices on the network to have an address and communicate properly, particularly with service and fp servers they need to be on the same subnet for client machines anyways.

so overall you would recommend adding fiber direct to the router, having redundancy on the router and firewall. And splitting the subnet, redundant PSUs as well?

No, I mean having all those fucking switches is pointless in most enterprises cause the building has non-redundant power. Even when they say they have dual feed, it isn't diverse, so you lose power anyway. Failure rate of hardware is fairly lower, redundant firewalls is nice cause you can do upgrades without taking things down but that is about it. I spent most of my network engineer career in telecom, so I was mostly doing real redundancy but when I did enterprise you just worry about things that actually fail and try to mitigate best you can, most important shit like servers you keep off site at this point cause then you can get real uptimes.

>usability wise my /21 network would allow all the devices on the network to have an address and communicate properly, particularly with service and fp servers they need to be on the same subnet for client machines anyways.

They can do this anyway, you generally put your gateways on your core switches and they will communicate by the very nature of them being directly connected. Generally if you need actual firewall segmentation, you would backhaul to the firewall or go nuts with microsegmentation depending on the security stance. A flat network is a broadcast nightmare, especially on chatty windows devices. I would get rid of the router, as it is 100% pointless in this design.

AHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHH

That cat infuriates THE FUCK OUT OF ME AHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHH

CONTENT IS BEING PRODUCED ORIGINALLY READING IS WRITING IS READING IS

right, the power problems can be mitigated with batteries, and power failing I feel would have to fall out of the scope of the SLA by some measure.

At least if I was holding a 99.9% entire network SLA I wouldn't keep responsibility after a specific up time in battery, example, after 120 minutes of power outtage it's outside my SLA to hold the 99.9%

>most important shit like servers you keep off site at this point cause then you can get real uptimes.
it would add a lot of cost and you have to consider the bandwidth traffic in and out of the network. Really shouldn't pose too much of an issue to host in house with the right planning.

Batteries usually give you ~20min uptime, they are just for clearing until a generator kicks in. Most places won't pay for one, so that is moot. The carrier providing the circuit will not have their equipment on battery backup, so you lose LAN on power outage anyway. Most enterprises don't have a real SLA codified as once you start showing them what it actually costs, budget suddenly matters and you just slap together the best you can for the money they have.

>it would add a lot of cost and you have to consider the bandwidth traffic in and out of the network. Really shouldn't pose too much of an issue to host in house with the right planning.

Bandwidth is cheap, no one bothers hosting shit on site anymore other than the basics like DHCP, DNS, fileshares and even then, that is going too, you either rent colo space or just do cloud cause it is near impossible to have real uptimes in most buildings an enterprise will get unless you are fortune 500. If it isn't that important for them to do that, they host on site and don't waste the money trying to get crazy uptime as the budget expenditure doesn't justify the return.