Week 11 · Lesson 1

Introduction to Servers

Almost every service you have studied so far — DNS, DHCP, web, email, files — is provided by a server. But what is a server, and why does it look different from the laptop on your desk? This lesson defines the server, contrasts it with a desktop, and explains the hardware choices that let a machine run unattended, twenty-four hours a day, for years.

CCNA 200-301 Servers & Virtualisation Verified 2026-10-11
Part 1

What is a server?

You met the word “server” in Week 1 as a role: the host that provides a service while a client requests it. That role is still true, but when people talk about “a server” in a data centre they mean a specific kind of machine built to play that role permanently. A server is both hardware and software working together.

Definition — server. A server is a computer (hardware running an operating system and one or more server applications) that provides services, data, or resources to clients over a network. It listens for requests and answers them.

The hardware is the physical box: CPUs, memory, disks, and network adapters. The software is the operating system plus the service that clients actually use — a web server, a file server, a database engine. Neither half is useful alone: a database program on a powered-off box serves nobody, and a powerful box with no service installed is just expensive metal. In the client–server model the server centralises a resource so that many clients can share it, and one administrator can manage it. That centralisation is the whole point: patch one machine, and every client benefits.

Anatomy of a server · select a layer

Role, not a brand. “Server” is still a role. Any computer can serve files. What makes a machine a server in practice is that it is dedicated to that job: it is always on, it is not used as a personal desktop, and its hardware is chosen for reliability rather than for a single user.
Part 2

Server versus desktop

On the surface both are computers. The differences are about purpose, and each difference follows from the fact that a server is shared by many users and must not stop.

AttributeDesktop / workstationServer
Power statePowered off overnight; reboots for updatesAlways on, 24×7, minimal downtime
User interfaceLocal monitor, keyboard, desktop OSHeadless — no screen; managed remotely
CPUOne CPU, few cores, built for bursty tasksMultiple cores/sockets, built for many concurrent requests
MemoryModest RAMLarge RAM with ECC error correction
StorageOne or two disksRAID arrays, often hot-swap drive bays
PowerSingle power supplyRedundant (dual) power supplies
NetworkOne NICMultiple NICs, often teamed for bandwidth and failover
PlacementDesk or lapData centre, rack, or server room
Server or desktop? · pick an attribute

Always-on and headless are the two ideas to memorise. Always-on means the machine must survive hardware faults without a human present, which is why redundancy features exist. Headless means there is no local screen or keyboard — administrators connect over the network, typically by remote desktop or a secure shell, so the network connection itself is part of the management path.

Part 3

Form factors: tower, rack, blade

A form factor is the physical shape and mounting style of the chassis. The three you must know are the tower, the rack-mount, and the blade.

Form factorDescriptionTypical use
TowerA standalone upright “pedestal” case, like a large desktop PC. No rack required.Small business, branch office, first server
Rack-mount (1U / 2U)A flat chassis that bolts into a standard 19-inch rack. Height is measured in rack units (U): 1U = 1.75 in = 44.45 mm. A 2U server is twice that height.Data centres; high density, easy stacking
BladeA thin server module that slides into a blade enclosure (chassis) which shares power, cooling, and networking across all blades.Very high-density data-centre deployments
Rack space · pick a form factor, then size the rack

The rack unit is worth remembering exactly, because exams and data-centre plans quote it: 1U is 1.75 inches, or 44.45 millimetres, tall. A typical full rack is 42U, so you can also think of rack space as a budget you spend one U at a time.

Part 4

Server hardware worth knowing

Server hardware is chosen for reliability and for handling concurrent work. Walk through the list, because each item answers a specific failure or load problem.

Multiple CPU coresone socket = many cores = many threads
ECC RAMdetects and corrects single-bit errors
RAIDmany drives = one logical volume
Redundant PSUstwo supplies, two circuits, hot-swap
Hot-swap drivesreplace a disk without downtime
Dual / teamed NICsbandwidth plus failover
Exam tip. Every one of these features answers the same question: what happens if this part fails at 3 a.m.? If a scenario mentions unattended operation, no local technician, or a service that must stay up, redundancy is the answer being tested.
Part 5

RAID: redundancy from many drives

RAID (Redundant Array of Independent Disks) treats several physical drives as one logical drive. Each level makes a different trade-off between performance, usable capacity, and fault tolerance. Learn the four levels below cold — the numbers and the minimum drive counts are exam favourites.

LevelTechniqueMin. drivesFault toleranceUsable capacity
RAID 0Striping — data is split across all drives for speed2None (one drive fails, all data is lost)100% (N drives)
RAID 1Mirroring — every drive holds an identical copy2Tolerates 1 drive failure50% (N/2)
RAID 5Striping with distributed parity — parity spread across all drives3Tolerates 1 drive failure(N−1) of N drives
RAID 10Mirrored stripes (RAID 1 + 0) — pairs are mirrored, then striped4Tolerates 1 drive per mirror pair50%
RAID builder · choose a level and a drive count

Exam tip. Anchor each level to one word: RAID 0 = speed (zero redundancy); RAID 1 = mirror; RAID 5 = parity (minimum three drives); RAID 10 = mirror + stripe (minimum four drives). If a question says “fault tolerant with the least wasted capacity”, the answer is RAID 5.
Warning — RAID is not a backup. RAID protects against a disk failing. It does not protect against accidental deletion, ransomware, a failed controller, or a fire. A backup is a separate copy stored elsewhere; RAID and backups solve different problems.
Part 6

Common server roles

A single powerful server can run several roles at once, or each role can get its own machine. Match each role to the service it provides.

RoleWhat it providesExample service
File serverCentral storage for shared documents and foldersSMB/CIFS, NFS
Print serverQueues and shares printers to many clientsWindows Print Spooler
Web serverDelivers web pages and web applicationsHTTP/HTTPS (Apache, Nginx, IIS)
Mail serverSends, receives, and stores emailSMTP, IMAP, POP3
DNS serverResolves names such as example.com to IP addressesBIND, Microsoft DNS
DHCP serverHands out IP addresses and network settings automaticallyISC DHCP, Microsoft DHCP
Database serverStores and queries structured data for applicationsMySQL, PostgreSQL, SQL Server
Application serverRuns the business application logic clients connect toJava/.NET application tier
Virtualisation hostRuns many virtual machines on one physical boxVMware ESXi, Hyper-V, KVM

Notice that the virtualisation host role is different in kind: instead of serving clients directly, it serves other servers. Lesson 2 covers hypervisors and how one physical server can host many virtual ones.

The rack and the clients

The first figure shows a typical rack elevation. Each rectangle is a server or switch occupying a number of U of vertical space; a top-of-rack switch aggregates their network links.

19-inch rack (elevation) 1U Top-of-rack switch 2U Web server 2U Database server 1U DNS / DHCP server 1U File server 2U Virtualisation host 1U = 1.75 in = 44.45 mm tall; a 2U server is twice that height. Redundant (dual) power supplies and hot-swap drive bays. ECC RAM, many CPU cores, teamed NICs for failover.
A rack-mount deployment. Servers are measured in rack units (U) and stacked in a 19-inch rack so they share power distribution and cooling. The top-of-rack switch connects every server to the network.

The second figure steps back from the hardware: a server is only useful because clients reach it across the network to use its services.

Server (runs services) File Web DNS DHCP Switch Desktop PC Laptop Phone Printer wired / Wi-Fi
One server, many clients. Every client requests a service (a file, a web page, a name lookup, an IP address) and the server answers. The server must stay available because all these clients depend on it at once.
Part 7 · Your turn

Review

Check what you have learned with these review questions.

Review · 6 questions

Sources

Sources & references

  1. Cisco. CCNA (200-301) Exam Topics — network components and services. cisco.com.
  2. Cisco Networking Academy. Networking Basics (server and client roles, converged networks). netacad.com.
  3. Microsoft. Windows Server documentation: Storage Spaces and RAID levels. learn.microsoft.com.
  4. Braden, R. RFC 1122: Requirements for Internet Hosts — Communication Layers (host roles and terminology). rfc-editor.org/rfc/rfc1122.
  5. IANA. Service Name and Transport Protocol Port Number Registry. iana.org.

Target exams: CCNA 200-301 v1.1 · CyberOps Associate 200-201. Last content verification: 2026-10-11.