Network design
Simple Network Design
A good simple network starts with clear requirements. You then plan how it works and where everything goes, and you finish with testing and documentation.
The goal is not to build the most complex network possible. The goal is a network that meets its requirements reliably, securely, and with room to grow.
1. Understand the requirements
Write down what the network must do before you choose or place any equipment.
Start with the goals:
- Wi-Fi should cover areas X, Y, and Z.
- Staff devices and guest devices use separate networks.
- Cameras must communicate with the recording server.
- IP phones must reach the VoIP service.
- Guests get internet access but no access to internal systems.
Then turn those goals into technical rules for each VLAN. A VLAN is a separate virtual network that runs on the same equipment.
- Staff: Login with a password or central authentication. Access to approved internal services.
- Guests: Open network with a web login page. Internet only, with guest devices isolated from each other when required.
- Cameras: Access to the recording system. No unnecessary internet access.
- Management: Used only to manage network devices.
Also define what the network must handle:
- Size: Internet speed, number of users, devices per user, and the most devices connected at once.
- Use: The applications people will use and the areas that need Wi-Fi.
- Reliability: Required availability, acceptable downtime, and expected growth.
The number of people connected at the same time usually matters more than the total number of users. A crowded space needs more capacity and may need more access points, even when one access point could technically cover the whole area.
Example: A small hotel wants Wi-Fi in the reception, restaurant, and 30 guest rooms. The network must support up to 80 simultaneous guest devices, 15 staff devices, 20 cameras, and 10 IP phones. Guests get only the internet. Staff also need the property-management system and printers.
2. Record the scope and limits
Write down the limits that affect the design:
- Project: Budget, deadline, areas included and excluded, and allowed downtime during installation.
- Building: Building restrictions, cable routes, electrical outlets, and environmental conditions.
- Equipment: Equipment you must reuse, available internet connections, and equipment availability.
Inspect what already exists before you plan replacements or additions. Record the router or firewall, switches, access points, network cabinets, cabling, fiber links, internet entry points, VLANs, and IP ranges. Note anything outdated, damaged, or unsupported.
A design that looks ideal may not be practical once you consider the budget, cabling, power, or building structure.
Example: The project has a budget of €5,000 and must reuse two existing PoE switches, which power devices through the network cable. New cables cannot go through the main lobby during operating hours. The installation must therefore use existing cable routes and finish between 01:00 and 06:00.
3. Estimate users, devices, and traffic
Estimate how the network will be used.
Count the people and devices:
- Staff, guests, and devices per person.
- Cameras, phones, printers, servers, and controllers.
- The most Wi-Fi devices connected at once, and when that peak happens.
Then list the traffic you expect. This could include web browsing, video streaming, video calls, cloud applications, file transfers, camera streams, VoIP calls, backups, and software updates.
Think about future demand as well as current demand. A good design leaves room for growth without rebuilding the whole network.
Example: A restaurant expects 100 customers at peak hours. If each customer may use two devices, plan for up to 200 guest devices, not 100. Add staff tablets, payment terminals, cameras, and phones separately.
4. Design the logical network
The logical design explains how devices communicate, no matter where they are installed.
Define:
- Addressing: The VLANs, plus the IP subnet, DHCP range, and default gateway for each one. DHCP is the service that gives devices their IP addresses. Also define DNS services and static IP reservations.
- Wi-Fi: Which SSID, or Wi-Fi network name, belongs to which VLAN.
- Access: Routing between VLANs, firewall rules, internet access rules, and management access rules.
For every VLAN, answer five questions:
- Which devices belong to it?
- Which internal services can it access?
- Can it access the internet?
- Can other VLANs connect to it?
- Can devices inside it communicate with each other?
Use the principle of least privilege. Allow only the communication that is required.
- Guest devices should normally reach the internet, but not staff devices, cameras, printers, servers, or network-management interfaces.
- Cameras should normally reach the recording server, but not unrelated internal systems.
- Network-management interfaces should open only from approved administrator devices or a management network.
Here is an example logical plan:
| VLAN | Subnet | Access |
|---|---|---|
| 10: Staff | 192.168.10.0/24 | Internet, printers, and internal applications allowed |
| 20: Guests | 192.168.20.0/23 | Internet allowed, internal networks blocked |
| 30: Cameras | 192.168.30.0/24 | Recording server allowed, general internet blocked |
| 99: Management | 192.168.99.0/24 | Accessible only from administrator devices |
5. Design the physical plan
Open the building map digitally or print it. Sketch where each device goes, and label it with its type and, when possible, a unique identifier.
Include every device: access points, cameras, PCs, printers, IP phones, routers, firewalls, switches, network cabinets, patch panels, servers, and UPS units. A UPS is a battery backup.
The plan should also show:
- Connections: How devices connect, cable routes, uplinks, and fiber links.
- Locations: Switches, network cabinets, and internet entry points.
- Site details: Power sources, outdoor areas, and connections between floors or buildings.
Do not plan only where devices will sit. Also plan how power and data will reach each device.
Example: Place one network cabinet in the ground-floor technical room and connect it to a second-floor cabinet using fiber. Connect access points, cameras, and phones to the nearest PoE switch instead of running every cable to the main cabinet.
6. Plan Wi-Fi coverage and capacity
Wi-Fi coverage is not a fixed circle around an access point. Usable coverage depends on three things:
- Equipment: Access-point model, antenna type and orientation, transmit power, frequency band, channel width, and what client devices support.
- Building: Walls, construction materials, furniture, equipment, metal structures, and interference.
- Demand: The number of simultaneous clients and the speed and connection quality they need.
Higher-frequency bands generally reach less far and pass through walls less well than 2.4 GHz. However, they can provide more bandwidth and channels.
Access points should usually be close to the people they serve. You may need extra access points inside when:
- The space is very wide or has many separate rooms.
- Walls are thick or contain concrete or metal reinforcement.
- Elevators, machinery, storage systems, or metal surfaces block or reflect the signal.
- One access point would have to reach through several walls.
- You expect a high number of clients.
Common materials reduce signal power by roughly these amounts:
| Material | Signal loss | Power reduction |
|---|---|---|
| Drywall | About 3 dB | About 50% |
| Brick wall | About 10 dB | About 90% |
| Concrete wall | About 12 dB | About 94% |
These values are planning estimates. Actual loss depends on thickness, moisture, reinforcement, conductivity, construction method, frequency band, and signal angle.
The percentages describe radio power. They do not mean usable Wi-Fi range drops by exactly the same percentage.
Metal and reinforced structures can cause even worse signal loss or reflection, so be cautious with them. Base your design on expected real conditions, not the best-case range the manufacturer advertises.
Also plan these settings and targets:
- Radio settings: Frequency bands, channels, channel width, and transmit power.
- Networks: SSIDs and their VLAN assignments.
- Movement: Cell overlap and roaming, which is when a device moves between access points.
- Targets: Minimum signal strength, minimum throughput, and maximum clients per access point.
Orientation matters too. An access point designed for the ceiling may not give the intended coverage when mounted on a wall.
Start with a cautious predictive design. After installation, carry out an on-site wireless survey and test with real client devices.
Example: A corridor has ten rooms on each side, separated by reinforced concrete walls. One access point at the start of the corridor may show a signal at the far end but still perform poorly inside the rooms. A safer design may use several ceiling-mounted access points along the corridor and check the result inside each room.
7. Plan cabling and power
For every wired device, check:
- Cable: Type, route length, quality, and whether it is for indoor or outdoor use.
- Capacity: Patch-panel capacity, free switch ports, and uplink capacity.
- Site needs: Fiber between floors or buildings, grounding, and surge protection.
Power over Ethernet (PoE) sends power through the network cable. For PoE devices, check:
- Whether the switch supports the required PoE standard.
- How much power each device needs.
- The total PoE budget of the switch.
- How much PoE capacity remains after all devices are connected.
A switch may have enough ports but still lack the PoE capacity to power every access point, camera, or phone.
Plan electrical protection for important equipment. Consider UPS protection and runtime, surge protection, generator support, safe shutdown procedures, and cooling and ventilation inside network cabinets.
Example: A 24-port PoE switch has a total power budget of 195 watts. Twelve cameras need 10 watts each, and six access points need 15 watts each. The total demand is 210 watts, so the switch does not have enough PoE capacity, even though it has enough ports.
8. Plan security
Security should be part of the original design, not something added after installation.
Define:
- Access: Staff and guest authentication, guest-device isolation, administrator access, and the management VLAN.
- Traffic: Firewall rules and access between VLANs.
- Upkeep: Credential, firmware-update, and configuration-backup policies, plus logging and monitoring.
- Physical security: Who can reach cabinets and devices.
A shared Wi-Fi password may be enough for a small, controlled environment. Larger environments may benefit from WPA2-Enterprise or WPA3-Enterprise, which authenticate each user individually.
Protect network-management interfaces from guest and ordinary staff networks. Change default credentials and disable unused management services.
Example: Guests join an open SSID and log in through a captive portal, which is a web login page. Firewall rules allow the internet but block all private IP ranges. Switches, access points, and the firewall can be managed only from the management VLAN, using approved administrator devices.
9. Plan for failures
Work out what happens when each important part fails. Review the internet connection, router or firewall, core and access switches, wireless controller, fiber uplinks, power supply, UPS, and DHCP and DNS services.
Depending on how important the network is, consider:
- Backup connections: A backup internet connection, redundant uplinks, and link aggregation.
- Backup equipment: A redundant firewall or core switch, and controller high availability.
- Fast recovery: Spare access points or switches, configuration backups, and replacement procedures.
Not every simple network needs full redundancy. However, every design should identify its single points of failure and what happens if each one fails.
Example: A small office may use one firewall because temporary internet downtime is acceptable. Its configuration should still be backed up, and a replacement device should be available. The network can then be restored without rebuilding the configuration by hand.
10. Review the plan
Go back to the original requirements and check every part of the plan against them.
- Wi-Fi: Does it cover every required area, based on realistic building materials? Is there enough capacity at peak times? Are access points near the users?
- Network: Does every device have a suitable connection? Does every VLAN have a clear purpose and a large enough IP range? Are firewall rules clearly defined?
- Security: Are guest devices isolated? Are management interfaces protected?
- Hardware: Are there enough switch ports? Is the PoE budget sufficient? Are cable routes practical? Could any link become a bottleneck?
- Failures: Are important components protected by a UPS? Are there unacceptable single points of failure?
- Future: Can the network expand without a major redesign? Can another technician understand and maintain it?
Be cautious when information is uncertain. Do not design around perfect signal, maximum advertised performance, or ideal client behavior.
Example: The plan includes one access point for a conference room that holds 100 people. The signal may cover the room, but the access point may not have enough capacity for 100 active devices. Revise the plan based on expected client density, not only coverage.
11. Define testing and acceptance criteria
Define measurable acceptance criteria before you install the network. For example:
- Every required area has usable Wi-Fi coverage.
- Clients connect to the correct SSID and get an IP address from the correct subnet.
- Staff devices can access approved services.
- Guest devices cannot access internal networks.
- Cameras can reach the recording server, and IP phones can reach the VoIP service.
- Internet speed meets the agreed target.
- Roaming works where users move between access points.
- The network stays stable during expected peak usage.
- Backup links work when the primary link fails, and UPS systems provide the required runtime.
After installation, test:
- Connections: Wired connectivity, wireless coverage and throughput, roaming, and PoE.
- Services: DHCP, DNS, and internet access.
- Separation: Inter-VLAN routing, firewall restrictions, and guest isolation.
- Operations: Failover, monitoring, and logging.
Test under realistic conditions where possible. An empty building may give different Wi-Fi results from the same building full of people, furniture, equipment, and active devices.
Example: Connect a test device to the guest Wi-Fi. Confirm that it gets an address from the guest subnet and can access the internet. Then confirm that it cannot reach the staff printer or the firewall-management page. It also must not reach another guest device when client isolation is enabled.
12. Document the final network
After installation, update the plan so it shows the network that was actually built.
Document:
- Layout: Physical topology, logical topology, and rack positions.
- Devices: Names, models, serial numbers, management IP addresses, and firmware versions.
- Addressing: VLANs, subnets, DHCP ranges, default gateways, and SSID assignments.
- Connections: Switch-port assignments, patch-panel ports, and cable labels.
- Configuration: Firewall rules and configuration-backup locations.
- Operations: Internet-provider information, maintenance procedures, troubleshooting notes, and change history.
Keep sensitive credentials in an approved password manager. Do not put plaintext passwords in general network diagrams or documentation.
Good documentation lets another technician understand, maintain, troubleshoot, and expand the network without having to rediscover how it works.
Example: Document that access point AP-02 is in the first-floor corridor and uses management IP 192.168.99.12. It connects to switch SW-F1 port 8 and patch-panel port F1-08, receives power through PoE, and broadcasts the Staff and Guest SSIDs.
Sources and further reading
The scenarios, device counts, budgets, addresses, and power calculations in this article are illustrative planning examples. Material loss, coverage, capacity, electrical protection, and security controls must be verified for the actual building, equipment, regulations, and client requirements.
- Cisco Wireless RF Reference Guide — RF behavior, frequency bands, access-point placement, attenuation estimates, and wireless survey guidance.
- NIST SP 800-153: Guidelines for Securing Wireless Local Area Networks — WLAN security throughout design, deployment, maintenance, and monitoring.
- CISA: A Guide to Securing Networks for Wi-Fi — layered controls for reducing wireless-network threats.
- RFC 1918: Address Allocation for Private Internets — the private IPv4 address ranges used in the logical-design examples.