CONFIGURE NETWORK DEVICES

 Define Network configuration.

Network configuration is the process of setting up the policies, controls and data
flows that allow devices and systems to communicate across a computing network.

 Network architecture

TCP/IP protocol suite

Here’s a breakdown of the TCP/IP protocol suite (also called the Internet protocol
suite) — what it is, how it works, and its main layers and protocols.

What is the TCP/IP protocol suite

 The TCP/IP suite is a collection of networking protocols that enable data

communication over diverse networks (including the Internet).
  The “TCP/IP” name comes from two of its core protocols: Transmission
Control Protocol (TCP) and Internet Protocol (IP).
 It was originally developed in the 1970s (by DARPA and others) to allow
heterogeneous networks to interconnect.
 The suite defines how data should be packetized, addressed, transmitted,
routed, and received.

Architecture / Layering

Unlike the more theoretical OSI model (with 7 layers), TCP/IP uses a simpler
model (commonly 4 layers) to describe how communication works.

Here are the layers (from top to bottom) and what they do:

Application Layer

 This is the topmost layer, where user‐applications operate (web browser,

email client, file transfer, etc.).
 Protocols: e.g., HTTP (web), FTP (file transfer), SMTP (email), DNS
(domain name resolution).
 Role: Provide services directly to user applications; send data down to lower
layers for transport.

Transport Layer

 Responsible for end‐to‐end communication between hosts (i.e., from a

process on one machine to a process on another).
 Key protocols: TCP (reliable, ordered delivery) and UDP (User Datagram
Protocol — connectionless, faster, less guarantee)
 Tasks: segmentation of data, sequencing, error checking, flow control
(especially in TCP).

Internet (or Network) Layer

 Manages addressing and routing: how packets traverse networks and get
from source to destination.
  Key protocol: IP (Internet Protocol) — handles the packet structure, source
& destination addressing, routing.
 Also includes other supporting protocols (for example control messages).

Network Access (or Link) Layer

 The lowest layer: deals with the physical or link‐specific aspects of sending
bits over hardware, local network segments, etc.
 Tasks: converting packets into frames, addressing on a link (e.g., MAC
addresses), dealing with physical media (cable, wireless).

How it works (simplified flow)

Here’s a simple end-to-end overview of how data moves across the TCP/IP stack:

1. A user’s application (say web browser) generates data.

2. At the Application layer: the data is prepared using the relevant protocol
(e.g., HTTP).
3. At the Transport layer: data is broken into segments (TCP) or datagrams
(UDP), with appropriate headers (sequence numbers, ports).
4. At the Internet layer: each segment/datagram is encapsulated into an IP
packet; source and destination IP addresses are added; maybe fragmentation
if needed; routing decisions are made.
5. At the Network Access layer: the IP packet is encapsulated into a frame (for
the specific link, e.g., Ethernet); physical transmission occurs.
6. On the receiving side: each layer strips its header and passes the remaining
data up to the next layer, eventually reaching the application.

This encapsulation / de‐encapsulation ensures heterogeneous networks can

interoperate.
Why it matters / advantages & considerations
Advantages

 Platform and hardware independent: works across many types of systems

and networks.
 Scalable: suitable for small networks to global Internet.
 The protocol suite is open / non‐proprietary, helping wide adoption.

Considerations / Limitations

 Although robust, the suite was originally not designed with many modern
security concerns in mind (so layered security additions are required).
 Because it's widely used and standardized, changes/updates in some parts
can be slow or constrained.

Some key protocols to know

Here are a few of the important protocols in the TCP/IP suite:

 IP (Internet Protocol): Handles addressing, routing of packets.

 TCP (Transmission Control Protocol): Reliable, ordered, connection‐
oriented transport.
 UDP (User Datagram Protocol): Connectionless, lower overhead transport.
 ICMP (Internet Control Message Protocol): Used for control messages
(errors, diagnostics). (Mentioned in passing in some sources)
 Others at the application layer: HTTP, FTP, SMTP, DNS, etc.

Ethernet network architecture

What is Ethernet

 Ethernet is a family of wired computer networking technologies mainly used

in Local Area Networks (LANs).
 It was originally developed in the 1970s and standardized in the IEEE 802.3
standard.
 Ethernet supports a range of data rates, media types, and topologies.

. Architecture / Layers & Key Features

Layers involved

 In the OSI (Open Systems Interconnection) sense, Ethernet spans Physical

Layer (Layer 1) and Data Link Layer (Layer 2).
 Within the Data Link layer, there is the MAC (Media Access Control)
sublayer defined by IEEE 802.3.

Key mechanisms

 Frame format: Ethernet frames carry payloads plus headers/trailers

(addresses, type/length, CRC). For example, typical frames are between 64
and 1518 bytes (without optional VLAN tags).
 Addressing: Each network interface has a unique MAC (Media Access
Control) address (48 bits) for frame delivery on the link.
 Medium access method: In traditional shared‐medium Ethernet (e.g., coax
or hub‐based), the access method is CSMA/CD (Carrier Sense Multiple
Access with Collision Detection).
 Topology and media: Ethernet has evolved through various physical media
(coaxial cable, twisted pair, and fiber) and topologies (bus, star, tree).
Architecture of a Typical Ethernet LAN

 End-devices (PCs, printers, servers) connect via twisted-pair cables to a

switch (access switch).
 Switches connect upward (via uplinks) to aggregation or core switches.
 Switches forward Ethernet frames based on MAC addresses (learning and
forwarding).
 Broadcasts (e.g., ARP) propagate within the broadcast domain unless
segmented via VLANs or routers.
 VLANs (Virtual LANs) are often used to partition the network logically
while still using Ethernet switching fabric.

How it Works: Key Flows

1. A host wants to send data to another on the same Ethernet segment.

2. The host builds an Ethernet frame: destination MAC, source MAC,
type/length field, payload, CRC.
3. On a shared medium, the host listens (carrier sense) and if idle transmits. If
another device transmits at the same time a collision occurs, and both detect
it (CD), they back-off and retry.
4. On a switched network, the switch learns MAC addresses on each port, and
forwards frames only to the port where the destination resides (instead of
flooding all ports).
5. If the destination is on another IP subnet, the frame first goes to the default
gateway (router) which strips the frame and forwards at IP level.
6. For higher speeds and modern links, full-duplex links and switching
eliminate collisions—CSMA/CD is no longer needed in those scenarios.

Key Strengths, Design Considerations & Limitations

Strengths

 Ethernet is simple, well-understood, and cost-effective.

 Scalable in terms of speed and media (from 10 Mbps up to multi-Gigabit
and beyond).
  Ubiquitous: massive ecosystem of devices and vendors.

Design Considerations

 Physical media and cable length limitations (e.g., twisted pair has distance
limits).
 Broadcast domains: large flat Ethernet segments can suffer from broadcast
storms and excessive ARP traffic — hence VLANs or routing segmentation
are used.
 Collision vs. contention: in older shared mediums collisions were a problem;
switching largely eliminated that but design must ensure switches are
properly configured.
 Performance: oversubscription, slow uplinks, improper segmentation can
degrade performance.
 Security: Ethernet is a local broadcast medium, so precautions (VLANs, port
security, etc.) are required.
 Compatibility/backwards-compatibility: newer standards build on older ones
(e.g., twisted-pair replacing coax) but legacy considerations may apply.

Limitations

 A pure Ethernet LAN is typically limited to a broadcast domain and cannot

by itself span subnets without routers.
 Shared mediums (legacy) had collisions and scaling issues; modern switched
Ethernet alleviates these but requires proper infrastructure.
 Physical media constraints: e.g., cable types, distances, signal attenuation.
 Without segmentation (VLANs, routing) large networks can become
inefficient and difficult to manage.

 Network protocol

A network protocol is a set of formal rules and conventions that govern how
devices communicate over a network. They define how data is packaged,
addressed, transmitted, routed, received, and interpreted.
How protocols are categorized

Protocols can be grouped by which layer of a network model they operate in (e.g.,
the OSI model or the Internet protocol suite).
Below are typical layers and what protocols you’ll find in them:

Layer Role Example protocols

Delivers data between hosts, Transmission Control Protocol

Transport layer handles reliability, ordering, (TCP)
etc. User Datagram Protocol (UDP)
Hypertext Transfer Protocol
Interfaces with user (HTTP) & HTTPS
Application applications and defines
layer application-specific File Transfer Protocol (FTP),
communication. Simple Mail Transfer Protocol
(SMTP)
Internet Control Message
Handles addressing, routing Protocol (ICMP, routing
Network layer
packets between networks. protocols like Routing
Information Protocol (RIP)
Link / Data- Concerned with the
Point‐to‐Point Protocol (PPP) for
Link / Physical transmission of bits and
link layer direct connections
layers frames over a medium.

Important network protocols & what they do

 TCP (Transmission Control Protocol): Ensures reliable, ordered, error‐

checked delivery of a stream of data between applications. It is connection-
oriented (i.e., a “session” is established) and part of the Internet protocol
suite.
 UDP (User Datagram Protocol): A lighter-weight transport protocol that
sends datagrams without guaranteeing delivery, ordering, or duplicate
 protection. Good for applications where speed is more important than
absolute reliability (e.g., streaming).
 HTTP (Hypertext Transfer Protocol) / HTTPS: Used for retrieving web
pages from web servers by web browsers. HTTPS adds encryption (using
SSL/TLS) for secure communication.
 FTP (File Transfer Protocol): Designed for transferring files between a
client and server over a network. Typically uses ports 20 / 21.
 DNS (Domain Name System): Translates human-readable domain names
(like [Link]) into machine IP addresses.
 DHCP (Dynamic Host Configuration Protocol): Automatically assigns IP
addresses and other network configuration settings to devices on a network.
 SMTP (Simple Mail Transfer Protocol): Used for sending email messages
between servers.
 PPP (Point-to-Point Protocol): A link layer protocol used to create a direct
connection between two network nodes. It supports authentication,
encryption, and encapsulation of multiple network layer protocols.

TCP/IP Model – Layers & What They Do

Layer Name Primary Role

Interfaces with user applications and supports
4 Application Layer
protocols like HTTP, FTP, DNS, and SMTP.
Provides host-to-host communication, reliability,
3 Transport Layer order. Key protocols: TCP (reliable) and UDP
(unreliable).
Internet (or Network) Responsible for addressing and routing packets
2
Layer across networks. Main protocol: IP.
Network Access (Link Handles the physical and data-link aspects of
1
or Physical) Layer sending bits over a media (e.g., Ethernet, Wi-Fi).
🧮 How It Works – Data in Motion

Here’s a simplified flow of data from sender to receiver:

1. Application Layer: A user action (e.g., browsing a website) triggers a

request using an application-level protocol (e.g., HTTP).
2. Transport Layer: The data is divided into segments, and mechanisms like
reliability (if using TCP) or faster delivery (if using UDP) are applied.
3. Internet Layer: Each segment becomes a packet or datagram with source
and destination IP addresses, and routing decisions are made to forward
across networks.
4. Network Access Layer: The packet is framed according to the local link
technology (Ethernet, Wi-Fi etc.) and sent over the physical medium.
5. At the destination, the reverse happens: link layer receives, passes up to
internet layer (checks IP address), then to transport layer (re-assembles,
checks for errors), and finally to application layer (renders the content).

Key Protocols in the Suite

 IP (Internet Protocol): Handles addressing and routing of packets between

networks. Doesn’t guarantee delivery.
 TCP (Transmission Control Protocol): Reliable, connection-oriented
transport. Ensures ordered delivery, handles retransmissions, flow control.
 UDP (User Datagram Protocol): Transport protocol with lower overhead,
no guarantee of delivery — used when speed is more critical than perfect
reliability.
 Other protocols: There are many others in this suite (e.g., ICMP, ARP)
dealing with error, network control, address resolution.

Why TCP/IP is Important

 Universality & interoperability: It works across different hardware,

operating systems and network types.
 Scalability: It supports everything from small LANs to the global Internet.
 Routing & flexibility: Its design allows internetworking — connecting
different networks seamlessly.
 Limitations & Considerations

 The suite was not originally designed with strong security built-in — many
security features are added on top.
 IP addressing (especially IPv4) has limitations (address exhaustion) though
mitigated by IPv6.
 Overhead: Some layers (especially TCP) add complexity (headers,
handshakes) — may reduce performance in certain scenarios.

 Network operating system (NOS).

A network operating system is specialized software that enables multiple

computers and devices on a network to communicate, share resources (files,
printers, applications), and be managed centrally.
A set of software utilities that, working in conjunction with an operating system,
provides the local-area network (LAN) user interface and controls network
operation.

Functions of a NOS
Printing

 Providing access to remote printers.

 Managing which users are using which printers at what time.
 Managing how print jobs are queued.
 Recognizing which printers are offline.

Files and storages

 Enabling and managing access to files on remote systems.

 Determining which user can access what files.
 Specifying a storage location for each user.
 Preventing users from storing files outside the allowed storage locations.
 Monitoring and controlling file access.
 Applications and resources

 Granting access to remote applications and resources, such as the Internet.

 Making resources seem like local resources to the user.
 Allowing users to work on a single application from multiple computers.
 Storing the data of the application in a single location.

Routing and monitoring

 Providing routing services, including support for major networking protocols, so

that the operating system knows what data to send where
 Monitoring the system and security, to provide proper security against viruses,
hackers, and data corruption.

Administration and security

 Providing network administration utilities (such as SNMP, or Simple Network

Management Protocol).
 Enabling an administrator to perform tasks involving managing network resources
and users.
 Blocking unauthorized accesses

NOS services
DHCP services: - These allow the administrator to configure the server to assign
IP addresses to clients on the network.

DNS services: - These services allow the administrator to map hostnames with
related IP address

E-mail services: - These services allow the administrator to configure the server to
send and receive e-mail using the Simple Mail Transfer Protocol (SMTP).

Web services: - These services allow the administrator to host websites and
related applications on the server.

File and print services: - These services allow the administrator to share files and
printers among clients.
Directory services: - These services allow the administrator to build a centralized
database of objects, such as user accounts that may be used by clients to log on to
the network. On Windows Server, the directory service is known as Active
Directory.

Group policies: - These services allow an administrator to deploy settings down to

the client operating systems from a central point. Some of the types of settings that
can be applied to clients through group policies are user rights, folder redirection,
file permissions, and installation of software.

NOS features
The common features of a NOS are the following.

Multitasking
One NOS can handle many thousands of tasks simultaneously. A NOS also runs
each service separately. This means, if one service fails, it does not affect other
services. Other services will be running without any lag.

Stability
A NOS can run for years without crashing. Most services running on the NOS can
be restarted without a system-level restart. It means a NOS does not restart for
every change or update.

Multiusers
A NOS allows several users to log into the system simultaneously. A NOS initiates
a separate login session for each user. A NOS allows a user to log into the same
system at the same time as another user.

High performance and hotplug support

A NOS supports the largest capacity of hardware devices. A NOS also supports the
hotplug feature. The hotplug feature allows the administrator to replace or upgrade
most of the hardware without shutting down the system.

Key Features & Functions

Some of the main functions of a NOS include:

  Resource sharing: enabling users to share printers, files, applications across
the network.
 User & group management: creating user accounts, managing permissions,
controlling access rights.
 Network security: access control, authentication, possibly encryption or
other protections across the network.
 Application & service provisioning: providing services like file servers,
print servers, database access, possibly remote access.
 Monitoring, administration and troubleshooting: tools for managing the
network, monitoring performance, diagnosing issues.
 Scalability and resource management: accommodating growth in number
of users/devices, managing network resources efficiently.

Types / Architectures

There are commonly two broad architectures you’ll see in NOS environments:

 Peer-to-Peer (P2P) NOS: Each device (workstation) may share resources

with others; there is no dedicated server. Suited for small networks.
 Client-Server NOS: A more centralized model: servers provide shared
services, clients connect to them. Better suited for larger networks,
enterprises.

Advantages & Disadvantages

Advantages

 Centralized control (in client-server models): easier to manage users,

resources, security.
 Resource sharing reduces duplication (e.g., one printer, many users).
 Often better scalability and manageability for enterprise networks.

Disadvantages

 In client-server model: more expensive (servers, dedicated infrastructure).

 The network or server becomes a point of failure if not properly configured.
  Maintenance, updates, security management become more complex in larger
networks.

Examples of Network Operating Systems

Here are some real-world examples of NOSes:

 Microsoft Windows Server (proprietary) — widely used in enterprise

networks as the NOS/server OS.
 Unix or Linux based systems (e.g., server distributions) can act as NOSes by
providing file/print/network services.
 NOSes for network devices (routers, switches) — e.g., SONiC (open-source
network OS for switches)

 Connect and configure network devices (practical)