Network topology for buildings

Network topology is the shape of a network: which switches connect to which, and what path traffic takes from a device to the core and out to the internet. In most buildings the right answer is a star, with each telecom room linked back to a central core, built in two tiers for small and mid-size buildings and three tiers for large sites and campuses.

Why topology matters

Topology decides three things that owners and facility managers notice: what fails when a single cable or switch fails, how much traffic can move between floors before it becomes a bottleneck, and how hard it is to add a floor, a tenant or a new system later. Two networks with identical switches can behave very differently because one was planned and the other grew one closet at a time.

Topology also shapes the cabling. The physical layout of rooms and risers in the building, which follows structured cabling practice under ANSI/TIA-568, sets the limits the logical design has to work within. That is why topology and cabling should be planned together rather than one after the other.

The basic shapes

Three physical shapes show up in buildings. Most real networks are a star, sometimes with ring or chain sections added for specific systems.

• Star. Every switch has its own link back to a central point. A fault on one link affects only that switch and the devices behind it. This is the standard layout for building networks and the one structured cabling standards are written around.
• Ring. Switches are linked in a loop, so each one has two paths. If one link is cut, traffic goes the other way. Rings are common in industrial plants, parking structures and long linear sites such as tunnels, where running every link back to the centre would take far more cable.
• Daisy chain. Switches are linked one after another in a line. It is cheap to install and easy to extend, but a single fault cuts off everything beyond it. Chains often appear by accident when someone plugs a new switch into the nearest port instead of running a link back to the telecom room.

How the star maps onto a building

In a building, the star follows the telecom rooms. Carrier services arrive at the main distribution frame (MDF), usually on the ground floor or in a basement, where the core switches and firewall sit. Each floor or zone has an intermediate distribution frame (IDF) holding the access switches for that area. Fibre backbone runs up a riser from the MDF to each IDF, and copper horizontal cable runs from each IDF to outlets, access points, cameras and controllers.

The important detail is that each IDF has its own fibre back to the MDF. Floor 3 should not be fed through the switch on floor 2. If floor 2's switch is replaced or loses power, floor 3 should not notice.

Two tiers or three

Network designers describe the logical layers of a star as tiers.

Two-tier, or collapsed core

The core and distribution functions sit in one pair of switches in the MDF, and access switches in each IDF connect straight to them. This suits most single buildings, including offices, schools, clinics and mid-rise residential buildings. There are fewer devices to buy, power, cool and manage, and fewer places for something to go wrong.

Three-tier

A separate distribution layer sits between the core and the access switches, usually one distribution pair per building or per large zone. This fits campuses, hospitals, large industrial sites and buildings with many IDFs, where it keeps the core from becoming a tangle of links and lets each building or zone be managed and upgraded on its own schedule.

The choice is not permanent. A building that starts with a collapsed core can grow into three tiers by adding a distribution pair when a second building or a large wing comes online, provided the original design left fibre strands, rack space and core ports for it. Planning that growth path is cheaper than redesigning later.

Choosing a topology: a worked example

Take a typical case: a six-storey office building with one MDF in the basement and an IDF on each floor, planning to add cameras, card readers and building automation to the network. The owner also has a single-storey warehouse across the parking lot.

1. Count the rooms and devices. Seven telecom rooms and a few hundred devices point to a two-tier design. A separate distribution layer would add cost without solving a problem.
2. Check the riser. Each IDF gets its own fibre home run to the MDF. Where the riser allows, a second fibre pair takes a different route so one damaged sleeve does not cut off a floor.
3. Size the uplinks. Add up what each floor sends to the core at busy times, including camera streams, which run all day, and pick uplink speeds with room to grow.
4. Treat the warehouse as its own zone. It connects back to the core over fibre between buildings, or a point-to-point wireless link where trenching is impractical, with its own access switches.
5. Record it. A logical diagram and a riser diagram, kept current, are what let the next contractor understand the network in an hour rather than a week.

Common mistakes

• Accidental chains. A switch under a desk feeding another switch in a meeting room is a daisy chain nobody designed. Each one adds a failure point and a place where loops can form.
• Undersized uplinks. Fast access ports with a slow uplink mean the floor slows down as soon as several people or cameras are busy.
• Telecom rooms as afterthoughts. An IDF in a janitor's closet with no cooling or dedicated power undermines whatever topology is drawn on paper.
• No room to grow. Filling every fibre strand and every rack unit on day one makes the first renovation expensive.
• Undocumented changes. Most topology problems in older buildings are changes that were made in a hurry and never recorded.

How ehZee can help

Our network design service starts by asking what the network has to support, surveys the telecom rooms and cabling you have, and produces a topology, riser and rack layout you can build from. We coordinate with the structured cabling design so the logical and physical layouts match. For related topics, see building network redundancy and network switch basics.

Common questions