4.1 Physical Topology

A physical topology describes how network devices and cables are physically arranged.

It answers questions such as: Which cable goes to which device? Where is the switch? How are computers, printers, access points, and routers physically connected?

Example

Computer A ---- Switch ---- Router
Computer B -------|
Printer ----------|

The drawing shows the real physical connections between the devices.

Real-world example

In an office, a computer may connect to a wall jack, the cable inside the wall may continue to a patch panel, and another cable may connect the patch panel to a switch. Those physical connections are part of the physical topology.

4.2 Logical Topology

A logical topology describes how data moves and how devices communicate, even when the physical cable layout looks different.

Physical topology focuses on cables and equipment. Logical topology focuses on communication behavior and data paths.

Example

Physical view:
PC A ---- Switch ---- PC B

Logical view:
PC A sends a frame
        ↓
Switch decides where to forward it
        ↓
PC B receives it

The devices may be physically connected in a star pattern, while the logical flow depends on switching, addressing, VLANs, and routing decisions.

4.3 Bus Topology

In a bus topology, devices share one main communication path or backbone.

Simple diagram

PC A ---- PC B ---- PC C ---- PC D
=================================
          Shared path

Older shared-medium networks are often used to demonstrate the bus idea.

Advantage

A simple bus can use less cabling than designs in which every device has its own dedicated connection.

Disadvantage

The shared path becomes important to everyone. A serious failure in the common path can affect many devices.

4.4 Ring Topology

In a ring topology, devices are connected so that the network forms a circular path.

Example

Device A ------- Device B
   |               |
   |               |
Device D ------- Device C

Data can travel around the ring from one device or connection point to another.

Possible weakness

In a simple ring without protection, one failed connection may interrupt the path. More advanced designs can add redundant paths to improve availability.

4.5 Star Topology

In a star topology, endpoint devices connect to a central networking device, commonly a switch.

Example

              PC A
               |
PC B ------- Switch ------- PC C
               |
             Printer

If one endpoint cable fails, the other endpoint connections can normally continue working.

Important weakness

If the central device fails and there is no redundancy, many connected devices can lose communication.

4.6 Mesh Topology

A mesh topology gives devices or sites multiple possible connections instead of depending on only one path.

Example

Site A -------- Site B
  | \            / |
  |  \          /  |
  |   \        /   |
Site C -------- Site D

If one path fails, another path may still be available.

Why mesh is useful

• More redundancy
• More possible paths
• Better fault tolerance
• Can improve availability

Trade-off

More links can increase cost, configuration work, and troubleshooting complexity.

4.7 Full Mesh

In a full mesh, every participating node has a direct connection to every other participating node.

Four-node example

A connects to B, C, and D
B connects to A, C, and D
C connects to A, B, and D
D connects to A, B, and C

With four nodes, there are six unique direct links.

Advantages

• Excellent path redundancy
• Many alternate routes
• A single link failure may not stop communication

Disadvantage

The number of required links grows quickly as more nodes are added, making a large full mesh expensive and complex.

4.8 Partial Mesh

In a partial mesh, some nodes have multiple direct connections, but not every node connects directly to every other node.

Example

Site A -------- Site B
  | \             |
  |  \            |
Site C -------- Site D

Some redundant paths exist, but the design uses fewer links than a full mesh.

Why use partial mesh?

It can provide redundancy for important locations while controlling cost and complexity.

4.9 Point-to-Point

A point-to-point connection directly joins two endpoints.

Example

Building A ================= Building B

Only two endpoints participate in that link.

Real-world examples

• A direct fiber link between two buildings
• A direct wireless bridge between two locations
• A direct link between two networking devices

4.10 Point-to-Multipoint

A point-to-multipoint design has one central point communicating with several other endpoints.

Example

              Site B
                |
Site C ----- Central ----- Site A
                |
              Site D

The central point serves multiple remote points.

Wireless example

Laptop  )))
Phone   )))  Wireless Access Point
Tablet  )))

One access point can communicate with multiple client devices.

4.11 Hub-and-Spoke

In a hub-and-spoke architecture, one central location acts as the hub and multiple remote locations act as spokes.

Example

                 Branch A
                    |
Branch B ------- Main Site ------- Branch C
                    |
                 Branch D

The main site is the hub. The branches are the spokes.

Advantages

• Simple central design
• Easier centralized management
• Fewer direct links than a full mesh

Disadvantage

If spoke-to-spoke traffic must pass through the hub, the hub can become a bottleneck or important dependency.

4.12 Spine-and-Leaf

Spine-and-leaf is a two-layer network design commonly used where many systems need high-speed communication with predictable paths.

The leaf switches connect endpoints such as servers. The spine switches provide the high-speed interconnection between leaf switches.

Simplified example

        Spine 1       Spine 2
        /  |  \       /  |  \
      Leaf1 Leaf2   Leaf3 Leaf4
        |     |       |     |
      Server Server  Server Server

In a typical design, leaf switches connect upward to the spine layer so traffic can move between leaf-connected systems using a consistent path structure.

Benefits

• Scalable design
• Multiple paths
• High aggregate bandwidth
• Useful for heavy internal system-to-system traffic

4.13 Three-Tier Architecture

A three-tier network architecture separates a campus-style network into three functional layers:

• Access
• Distribution
• Core

Simple diagram

              Core
             /    \
      Distribution Distribution
         /   \       /   \
      Access Access Access Access
        |      |      |      |
      Users  Users  Users  Users

Separating functions into layers can make larger networks easier to organize, scale, and troubleshoot.

4.14 Access Layer

The access layer is where endpoint devices normally connect to the network.

Typical endpoint examples

• Desktop computers
• Laptops through wired or wireless infrastructure
• Printers
• Phones
• Wireless access points
• Cameras and other networked devices

Example

PC ----\
Phone --- Access Switch
Printer -/

The access switch provides the first network connection for the endpoint devices.

4.15 Distribution Layer

The distribution layer sits between the access layer and the core in a traditional three-tier design.

It aggregates access-layer connections and can be a place where routing, filtering, policy, and network boundaries are applied.

Example

Access Switch 1 ----\
                    Distribution ---- Core
Access Switch 2 ----/

Instead of every access switch connecting directly throughout the entire network, distribution devices can organize and aggregate their traffic.

4.16 Core Layer

The core layer is the high-speed backbone of a traditional three-tier architecture.

Its main purpose is to move large amounts of traffic efficiently between major parts of the network.

Example

Distribution A ===== Core ===== Distribution B
      |                              |
   Building A                     Building B

The core connects major distribution areas and is designed for fast, reliable transport.

Design idea

A core should avoid unnecessary bottlenecks because many parts of the network may depend on it.

4.17 Collapsed Core

A collapsed core combines the core and distribution functions into one layer.

Three-tier

Core
 |
Distribution
 |
Access

Collapsed-core design

Core / Distribution
        |
      Access

This can be practical for smaller or medium-sized environments that do not need separate core and distribution layers.

Possible benefits

• Less equipment
• Lower cost
• Simpler design

The architecture still needs appropriate redundancy when the combined layer is important to many users.

4.18 On-Premises Architecture

An on-premises architecture places computing and networking resources at facilities controlled by the organization, such as its office, campus, or private data center.

Example

Office Users
     |
Local Switches
     |
Local Servers
     |
Local Storage

The organization may own or directly manage the physical servers, switches, storage systems, cabling, power, and security controls.

Possible advantages

• Direct control of physical infrastructure
• Local access to systems
• Ability to design infrastructure around specific requirements

Possible challenges

• Hardware purchase and replacement costs
• Power and cooling
• Physical security
• Maintenance and capacity planning

4.19 Cloud Architecture

A cloud architecture uses computing, storage, networking, or application resources delivered from remote provider-operated infrastructure and accessed through network connections.

This is a general architecture concept and does not refer to any one provider.

Example

Office Users
     |
   Internet
     |
Remote Cloud Resources
     |
Applications / Storage / Compute

Possible benefits

• Resources can often be added without purchasing local hardware
• Services can be available from many locations
• Capacity can be adjusted as requirements change

Important beginner point

Using cloud resources does not remove networking. Users still need reliable connectivity, addressing, routing, security controls, identity controls, and monitoring.

4.20 Hybrid Architecture

A hybrid architecture combines on-premises resources with remote cloud resources.

Example

Local Office / Data Center
          |
     Secure Network Link
          |
     Cloud Resources

An organization might keep some applications and data locally while placing other workloads or services in cloud infrastructure.

Example situation

A company may keep a local file or application system for internal operations while using remote cloud services for public applications, backups, analytics, or additional capacity.

Why hybrid designs are used

• Gradual migration
• Different workloads have different requirements
• Need for local resources plus remote scalability
• Business continuity and backup strategies

Important challenge

The local and remote environments must be connected and secured correctly. Network design, identity, routing, monitoring, and data protection become especially important.

Chapter 4 Beginner Summary