Enterprise networking project
Al Maqsourah Trading — Three-Site Enterprise Network
A proposed multi-site enterprise network based on the business environment of Al Maqsourah Trading: 210 endpoint users across a head office, a branch office and a satellite office.
What was solved and built
Problem
A three-location trading company running on an undocumented network: no written addressing scheme, no VLAN segmentation, and no record of how anything was configured. Faults could not be reasoned about from documentation, because none existed.
Built
A proposed design for a head office, a city branch and an overseas satellite: department-level VLANs, an addressing plan with capacity reserved for infrastructure, WAN connectivity between sites, and a build sheet detailed enough to configure the head office in a lab.
Result
Design and documentation complete and internally consistent — 105 automated assertions check every published figure against the plan. Device configuration and verification in SwitchLab are the next step. Nothing here is claimed as a real deployment.
Key features
- Three-site topology
- VLAN and addressing plan
- DHCP scope design
- WAN link planning
- Troubleshooting case studies
- One documentation format
Business scenario
A trading company operates from three locations. The network was designed headquarters-and-branches: a head office hosting central services and the WAN hub, a second site in the same city acting as a branch, and a satellite office in another country connected over a WAN link.
| Location | Role | Endpoint users | Proposed block |
|---|---|---|---|
| Riyadh Site 1 — Head Office | Headquarters · core and access switching, central services, WAN hub | 100 | 10.10.0.0/16 |
| Riyadh Site 2 — Branch Office | Branch · router and switching, inter-site routing | 60 | 10.20.0.0/16 |
| Egypt — Satellite Office | Satellite · remote LAN, secure WAN connectivity | 50 | 10.30.0.0/16 |
| Total | Three locations | 210 |
Capacity note: the 210 figure counts endpoint users only. It excludes switches, routers, firewalls, wireless access points, network printers, shared peripherals, servers, IP phones, CCTV cameras and other network-connected infrastructure — all of which have their own reserved address capacity in the design. Exact historical device quantities are unknown and are not invented here.
Project objectives
- Design a scalable three-site network architecture.
- Develop an IPv4 addressing and subnetting plan.
- Segment departments using VLANs.
- Configure switching and inter-VLAN routing.
- Establish routing between the three locations.
- Document secure WAN and site-to-site VPN concepts.
- Develop realistic network troubleshooting scenarios.
Technologies
- VLANs
- 802.1Q
- STP
- OSPF
- Static routing
- ACLs
- DHCP
- DNS
- WAN
- VPN concepts
OSPF forms part of this design. The free simulator used for the lab work on this site does not support it, so the routing element is documented as a design exercise rather than a simulated build — see the OSPF and multi-site routing entry.
Site designs
Riyadh Site 1 — Head Office
In progress100 endpoint users · 10.10.0.0/16Core/access switching with departmental VLANs and 802.1Q trunking, inter-VLAN routing, central DHCP/DNS concepts, server and management segmentation, ACL policy, and WAN connectivity to both remote sites.
Riyadh Site 2 — Branch Office
Design only60 endpoint users · 10.20.0.0/16Branch router and switch with departmental VLANs, matched IP addressing/subnetting, DHCP/DNS reachability, WAN connectivity to headquarters, and access restrictions where appropriate.
Egypt — Satellite Office
Design only50 endpoint users · 10.30.0.0/16Remote-office LAN architecture with local switching and VLANs, routing between Egypt and Riyadh, secure site-to-site WAN design concepts, and access limited to approved headquarters resources.
Addressing and VLAN plan
The full subnetting plan: department VLANs, subnets, gateways, reserved infrastructure ranges and DHCP pools for all three sites, with the capacity check and the WAN transit block.
Project deliverables
Each item below is published only once it exists and has been verified.
- Network topology diagrams
- IP addressing and subnetting plan
- VLAN allocation tables
- Configuration examples
- SwitchLab simulation links
- Verification commands and outputs
- Troubleshooting case studies
- Security and design documentation
Interactive lab and evidence
Content pending — SwitchLab shared topology link, configurations, verification output and screenshots
The lab is being built by the owner in SwitchLab. Share links and exported configurations are added here once produced — nothing is faked in the meantime.