+- Sinisterly (https://sinister.ly)
+-- Forum: Computers (https://sinister.ly/Forum-Computers)
+--- Forum: Networking (https://sinister.ly/Forum-Networking)
+--- Thread: Networking 101 (/Thread-Networking-101)
Pages:
1
2
Networking 101 - fiddlesticks - 11-23-2016
Hi, I'm fiddlesticks as i mentioned in my introduction I'm a full time network engineer. I've been taught and taught Alot and i thought i should share some of the main 'buzzwords' you'll come across in the networking industry and what they mean, this is no way Original content however it isn't just cut and pasted either.
(NOTE: These are just some off the top of my head as I've been doing / using most of these concepts today myself)
Let's begin -
Switch - A network switch also known as a switching hub is a device used to connect many devices together on a computer network.
(OSI) Open System Interconnection -A model used to standardize internal functions of a communication system by placing units in documented layers (UDP & TCP are layer 4 for example)
LAN - Local Area Network
WAN - Wider Area Network
Ethernet - A Large network of LAN technology
Intranet - A Private network used by companies to share information to employees
Extranet - A Public network used to share information
Fiber Channel - A Protocol that connects servers to create storage area networks
SAN - Storage Area Networks
DAS - Direct Attached Storage
NFS - Network File System Interface
CIFs - Common Internet File Systems
IOPs - Input/Output operations (per seconds)
DC - Domain Controller
CIFS - Common internet file system
NAS - Network area storage
FTTP - Fibre to premises (by cables)
-Common Networking Terms-
DNS (Domain Name System) - Used to map a name to IP addresses
VLANS (Virtual LAN) - Used to create segmented LAN instances within a switch
MAC Address (Media Access Control) - A unique way to define a host within an ethernet network (end-point)
OSPF (Open Shortest first path) - A 3 layer based routing protocol
Switching - Layer 2 in the OSI model used to forward based on MAC addresses
Routing - Layer 3 forwarding based on IP addresses
MultiCast - A packet that's sent to a group or subset
DHCP (Dynamic Host Configuration Protocol) - Used to assign an dynamic IP address to a device
Trunking Link Aggregation- (also known as LAG) used to match multiple devices to the same speed to form a higher speed link.
That should cover my first post, feel free to request more as I've not even scratched the surface of networking. If you like i can continue covering more basic concepts and gradually cover more advanced stuff. I plan to go over Cisco & Brocade switching. and a guide on changing configs as well as stacking switches and how to prioritize a stack.
Let me know if that's something you guys want. Thanks for reading.
RE: Networking 101 - Skullmeat - 11-23-2016
I'm actually going for CCNA, so this is somewhat useful. Alot of these I already knew tho.
RE: Networking 101 - fiddlesticks - 11-23-2016
(11-23-2016, 11:03 PM)Skullmeat Wrote: I'm actually going for CCNA, so this is somewhat useful. Alot of these I already knew tho.
I've already got my CCNA, like i said if requested i'll make more advanced content along with switching & routing for cisco devices.
RE: Networking 101 - Skullmeat - 11-23-2016
(11-23-2016, 11:06 PM)fiddlesticks Wrote:(11-23-2016, 11:03 PM)Skullmeat Wrote: I'm actually going for CCNA, so this is somewhat useful. Alot of these I already knew tho.
I've already got my CCNA, like i said if requested i'll make more advanced content along with switching & routing for cisco devices.
Nothing like that right now, although I've been asked to design a SOHO Network for a client. I was thinking a UTM with pf Sense, a managed switch, and a server. Other than that, basic clients.
RE: Networking 101 - fiddlesticks - 11-23-2016
(11-23-2016, 11:11 PM)Skullmeat Wrote:(11-23-2016, 11:06 PM)fiddlesticks Wrote:(11-23-2016, 11:03 PM)Skullmeat Wrote: I'm actually going for CCNA, so this is somewhat useful. Alot of these I already knew tho.
I've already got my CCNA, like i said if requested i'll make more advanced content along with switching & routing for cisco devices.
Nothing like that right now, although I've been asked to design a SOHO Network for a client. I was thinking a UTM with pf Sense, a managed switch, and a server. Other than that, basic clients.
Why would you include a switch in a basic network for one client? Also if you're using a server are you going to be using a firewall? for the switch i recommend a BroCade c12 ICX 6430.
RE: Networking 101 - Skullmeat - 11-23-2016
(11-23-2016, 11:30 PM)fiddlesticks Wrote:(11-23-2016, 11:11 PM)Skullmeat Wrote:(11-23-2016, 11:06 PM)fiddlesticks Wrote: I've already got my CCNA, like i said if requested i'll make more advanced content along with switching & routing for cisco devices.
Nothing like that right now, although I've been asked to design a SOHO Network for a client. I was thinking a UTM with pf Sense, a managed switch, and a server. Other than that, basic clients.
Why would you include a switch in a basic network for one client? Also if you're using a server are you going to be using a firewall? for the switch i recommend a BroCade c12 ICX 6430.
10 or so machines. All need CAT5. The client has complained about outages, so a managed switch would give me some better tools.
RE: Networking 101 - fiddlesticks - 11-23-2016
(11-23-2016, 11:46 PM)Skullmeat Wrote:(11-23-2016, 11:30 PM)fiddlesticks Wrote:(11-23-2016, 11:11 PM)Skullmeat Wrote: Nothing like that right now, although I've been asked to design a SOHO Network for a client. I was thinking a UTM with pf Sense, a managed switch, and a server. Other than that, basic clients.
Why would you include a switch in a basic network for one client? Also if you're using a server are you going to be using a firewall? for the switch i recommend a BroCade c12 ICX 6430.
10 or so machines. All need CAT5. The client has complained about outages, so a managed switch would give me some better tools.
Yeah, C12 and you're going to want something like 300mt CAT5 or you might want to use 2 switches and start a stack? depends on how much you're willing to drop on it.
RE: Networking 101 - Nil - 11-23-2016
"Routing - Layer 3 forwarding based on IP addresses"
The only nitpicking I'd do here is to define routing without using the term forwarding. While it's only a vague definition and the terms are often used interchangeably anyway, they still both have distinct functions and it may come off as confusing to some.
RE: Networking 101 - fiddlesticks - 11-23-2016
(11-23-2016, 11:56 PM)God Wrote: "Routing - Layer 3 forwarding based on IP addresses"
The only nitpicking I'd do here is to define routing without using the term forwarding. While it's only a vague definition and the terms are often used interchangeably anyway, they still both have distinct functions and it may come off as confusing to some.
Sorry, i meant routing is layer 3 (on the OSI model) and it can be used to forward IP addresses
You're right however, sorry I've not written anything in-depth yet wanted to start basic stuff first learn some formatting tips etc before i start to make more advanced threads. Really do appreciate the feedback though!
RE: Networking 101 - zorrophreak - 11-24-2016
Also working on my CCNA so this is pretty helpful aswell. I might want to add that where you talk about Routing you may want to go a little into or at least mention the Border Gateway Protocol (BGP) as at this point it is critical for routing at the backbone and network layer.