Enterprise IT Infrastructure Knowledge Centre Server Warehouse (Pty) Ltd
NETCOMTECH Enterprise IT Infrastructure Knowledge Centre

NETCOMTECH

Networking

Switching, VLANs, PoE, Ethernet, routing and network design.

Book 1 | Chapter 1

Chapter opening

Chapter 1 moves from the course overview into networking. The aim is not to memorise product menus or commands. The reader should understand what problem the technology solves, how it fits into the wider networking technical textbook, what normal operation looks like, and how to prove the result in the field.

This is the first chapter in the sequence, so it establishes concepts that later chapters build on.

Networking textbookChapter 1

Learning objectives

  • Explain the main purpose of Networking in plain language.
  • Identify the components that must work together for the service to operate.
  • Use evidence to separate a design problem from a configuration or physical fault.
  • Describe the business impact of a failure and the evidence required for handover.

Why this matters in a real company

This subject matters because networking infrastructure supports normal business operations. Understanding the design makes purchasing, troubleshooting and recovery decisions easier to explain and verify.

Course: Networking Technical Textbook

PLAIN ENGLISH

Technical terms used in this chapter

You do not need to memorise the jargon first. Understand what each term does and why somebody running a company would care about it.

Trunk

VLAN Trunk

A link that carries traffic for multiple VLANs using tags.

In everyday business: One cable between switches can transport several separated networks.

DHCP

Dynamic Host Configuration Protocol

A service that automatically gives devices IP settings such as address, gateway and DNS.

In everyday business: New laptops and phones can join the network without manual IP configuration.

VLAN

Virtual LAN

A logical Layer 2 network that separates devices even when they use the same physical switches.

In everyday business: Staff, cameras and guest WiFi can be kept apart without buying a separate switch for each.

LACP

Link Aggregation Control Protocol

A protocol that combines compatible Ethernet links into one logical bundle.

In everyday business: It can add capacity and keep a connection alive if one member link fails.

OLTS

Optical Loss Test Set

A fibre test method for measuring end-to-end insertion loss.

In everyday business: It proves how much optical power the installed fibre path loses.

ACL

Access Control List

A list of rules that says which network traffic is allowed or blocked.

In everyday business: Like a security guard checking a list at a door.

DNS

Domain Name System

The service that translates names into IP addresses and helps Windows domain clients find services.

In everyday business: People and applications can use names instead of remembering network numbers.

GPO

Group Policy Object

A set of centrally managed Windows settings that can be applied to users or computers.

In everyday business: IT can enforce security and configuration settings across many PCs at once.

See the complete plain-English glossary

BUSINESS TRANSLATION

What this means outside the server room

This topic affects how reliably staff and systems can communicate. Good network design reduces downtime, makes faults easier to find and keeps departments or services separated where required.

VLAN

What it means: A VLAN creates a separate logical network even when devices share the same physical switches.

In normal business language: Think of one office building with separate departments using the same corridors but different access-controlled areas. Staff, cameras, voice and guests can share the same switching hardware without all being in one open network.

Why the decision matters: Use VLANs to separate traffic for security, performance and easier troubleshooting without buying a separate physical switch for every department.

DNS

What it means: DNS translates names into IP addresses and also helps many business services locate each other.

In normal business language: It is the company phonebook for systems. Staff type a name such as fileserver or portal instead of remembering a number.

Why the decision matters: Good DNS design reduces configuration mistakes and is especially important for Windows domains, cloud integrations and internal applications.

DHCP

What it means: DHCP automatically gives devices their network settings.

In normal business language: It is like reception assigning each new visitor a desk number and directions automatically instead of somebody configuring every laptop by hand.

Why the decision matters: Use DHCP for normal endpoints and reserve static addressing for infrastructure where predictable addressing is required.

Firewall

What it means: A firewall controls which network connections are allowed between users, systems and external networks.

In normal business language: It is a security checkpoint between parts of the company network. It should allow legitimate work while blocking unwanted access.

Why the decision matters: Firewall rules should describe real business flows such as 'staff may reach accounting on HTTPS', not unexplained broad permits.

NAT

What it means: NAT changes IP addresses as traffic crosses a network boundary.

In normal business language: It is similar to a company switchboard: many internal extensions can share one public number.

Why the decision matters: NAT helps with address use and publishing services, but it is not a substitute for firewall security.

PoE

What it means: Power over Ethernet sends both data and electrical power over the same Ethernet cable.

In normal business language: A camera or access point can use one cable instead of separate network and power wiring.

Why the decision matters: PoE can simplify installation and UPS protection, but the switch power budget and cable quality still need to be designed.

Chapter contents

  1. 1.1 1GbE vs 2.5GbE vs 10GbE
  2. 1.2 Go deeper: installation and configuration
  3. 1.3 Hands-on training
  4. 1.4 Advanced operations

Back to Knowledge Centre

1.1 1GbE vs 2.5GbE vs 10GbE

Understand the practical differences between 1GbE, 2.5GbE and 10GbE network connections and how to choose an appropriate speed.

1GbE vs 2.5GbE vs 10GbE

Practical comparison of 1 Gigabit, 2.5 Gigabit and 10 Gigabit Ethernet for workstations, access points, servers, storage and switch uplinks.

DAS vs NAS vs SAN

Compare Direct Attached Storage, Network Attached Storage and Storage Area Networks at a practical infrastructure level.

Fibre vs Copper Networking

Understand the practical differences between fibre optic and copper Ethernet cabling for network infrastructure.

How to Choose Ethernet Cable

Practical guide to choosing Ethernet network cable by category, speed, environment, installation and future requirements.

How to Choose a NAS

A practical guide to choosing NAS storage based on capacity, drive bays, performance, networking, resilience and future growth.

How to Choose a Network Switch

Detailed guide to choosing a business network switch based on port count, management, VLANs, PoE, uplinks, speed, redundancy and future growth.

How to Choose a UniFi Access Point

Practical guide to selecting a Ubiquiti UniFi access point based on WiFi generation, bands, Ethernet uplink, PoE, location and client requirements.

Managed vs Unmanaged Switches

Understand the practical difference between managed and unmanaged network switches and when each approach can make sense.

Network Cable Management

Practical guide to network cable management, patch leads, cable managers, labelling and rack organisation.

Routers vs Switches

Understand the different roles of routers and network switches in a business network.

SFP and SFP+ Explained

Understand SFP and SFP+ network transceivers, their role in switches and the importance of compatibility.

Ubiquiti LTU Explained

Understand Ubiquiti LTU radios and customer premises equipment in wireless network deployments.

What Is NAS?

Understand what Network Attached Storage is, how it works and where it fits into business infrastructure.

What Is a SAN?

Understand what a Storage Area Network is and how SAN storage differs from NAS and local server storage.

1.2 Go deeper: installation and configuration

Use the procedure-driven playbooks when you need the practical installation, configuration, verification and troubleshooting steps.

1.3 Hands-on training

1.4 Advanced operations

WORKED BUSINESS SCENARIO

Scenario: turn the technology into an operational service

A company depends on this technology every day. The technical configuration may be correct, but the real requirement is predictable operation, evidence when something fails and documentation another technician can understand.

What the chapter teaches us: Treat the subject as a service with a purpose, dependencies, normal behaviour, failure modes and a recovery method.

Think it through

  1. What business process depends on this component?
  2. What would normal operation look like?
  3. What evidence would prove the cause of a failure?
PRACTICAL WORK

Hands-on lab

Create a small isolated lab that reproduces the chapter's core architecture. Record the starting configuration, make one controlled change and prove the result with measurable evidence.

Troubleshooting exercise

Take one realistic failure, list the evidence you would collect before changing anything, then write the shortest fault-isolation path.

Chapter field checklist

  • I can explain the subject without relying only on acronyms.
  • I can draw or describe the main traffic, storage, power or service path.
  • I know what normal operation should look like.
  • I know which logs, counters or test results prove the result.
  • I can explain the business impact if this component fails.
  • I would document the final configuration and evidence at handover.

Chapter summary

Networking should now be understood as a business service with a technical implementation, not simply a collection of commands or product names. The important habit is to know the purpose, understand the dependencies, measure the result and document what was proven.

END OF CHAPTER

Review questions

  1. Explain the subject in plain language to a business owner.
  2. List the main dependencies that must be healthy before this service can work.
  3. Describe one realistic failure and the first three pieces of evidence you would collect.
  4. Explain what should be documented at handover.

A good answer should explain the reason, not only repeat a product name or command.