Typical Campus Networking Solution · Topic 1 of 1
Campus Network Concepts and Project Practices
Learn campus network basics for H12-811: access, aggregation, core and egress layers, technologies per layer, and the stages of a campus network project.
- 5 min
- Campus layers: access, aggregation, core and egress, plus server and management zones.
- Small campuses can use two layers; larger campuses use three.
- Access connects terminals and APs; aggregation hosts gateways; core routes fast; egress does NAT and security.
What it is
A campus network is the network that connects the users, terminals and servers inside one bounded area run by one organization: an office building, a factory, a school or a hospital. It provides wired and wireless access, internal services and a path to the internet or WAN.
A campus network project is the work of building or upgrading one. It runs through fixed stages: planning and design, deployment and implementation, O&M, and optimization.
How it works
Basic concepts: scale and layers
Campus networks range from small sites with a few switches to large campuses with thousands of users. Small campuses often use a two-layer design (access and core), while midsize and large campuses use three layers (access, aggregation and core).
| Layer or zone | Role | Typical technologies |
|---|---|---|
| Access | Connects terminals and APs to the network | VLANs, access ports, PoE, port security, 802.1X or MAC authentication, STP edge ports |
| Aggregation | Collects access switches; usually the gateway for user VLANs | Vlanif gateways, VRRP, DHCP, Eth-Trunk uplinks, ACLs |
| Core | High-speed backbone between aggregation, DC and egress | Fast routing (OSPF), redundant links, stacking or clustering |
| Egress | Connects the campus to the internet or WAN | NAT, firewall security policies, routing to the ISP |
| Data center or server zone | Hosts internal servers | Server access switches, firewall separation |
| Network management zone | Hosts the management platforms | NMS, iMaster NCE, logs, AAA servers |
Wireless fits in the same model. APs connect to access switches with PoE, and the AC usually attaches to the aggregation or core layer.
Reliability in the campus
| Technology | What it gives |
|---|---|
| iStack | Several fixed switches stacked to act as one logical switch |
| CSS (Cluster Switch System) | Two modular switches clustered to act as one logical switch |
| Eth-Trunk | Several physical links bundled into one logical link, with load balancing and backup |
| VRRP | A virtual gateway shared by two devices; the higher priority (default 100) becomes master |
| STP, RSTP, MSTP | Loop prevention on redundant Layer 2 links |
Stacking or clustering plus Eth-Trunk makes the network logically simpler: two physical boxes become one, and redundant links become one bundle with no STP blocking.
A typical aggregation gateway with VRRP:
[AGG1] vlan batch 10 20
[AGG1] interface Vlanif10
[AGG1-Vlanif10] ip address 192.168.10.2 24
[AGG1-Vlanif10] vrrp vrid 10 virtual-ip 192.168.10.1
[AGG1-Vlanif10] vrrp vrid 10 priority 120Users in VLAN 10 use the virtual IP 192.168.10.1 as their gateway. AGG1, with priority 120, is the master; a peer at the default priority 100 is the backup.
Practices in campus network projects
| Stage | Main work |
|---|---|
| Planning and design | Requirement survey, physical topology, VLAN and IP address plan, routing, security, WLAN, reliability and management design |
| Deployment and implementation | Device installation, software commissioning, service cutover, acceptance testing |
| Network O&M | Routine monitoring and inspection, alarm handling, troubleshooting, change management |
| Network optimization | Analyze performance and new needs, then tune, upgrade or expand |
Requirement survey comes first: number of users and terminals, wired and wireless needs, services and bandwidth, security requirements, reliability targets and budget. Every later design choice traces back to it.
A simple VLAN and IP address plan from the design stage:
| Purpose | VLAN | Subnet | Gateway |
|---|---|---|---|
| AP management | 100 | 10.1.100.0/24 | 10.1.100.1 |
| Office users | 10 | 192.168.10.0/24 | 192.168.10.1 |
| Guests | 20 | 192.168.20.0/24 | 192.168.20.1 |
| Device management | 99 | 10.1.99.0/24 | 10.1.99.1 |
Good plans keep the VLAN ID and subnet related, so the network is easy to read and troubleshoot. They also use private address space inside and translate it at the egress with NAT.
A worked example
A company moves into a new four-floor building with 600 users. In the survey it asks for wired and wireless access, guest Wi-Fi separated from staff, and no single point of failure.
The design puts access switches on each floor with PoE for APs, two aggregation switches stacked with iStack and joined by Eth-Trunk to every access switch, and Vlanif gateways on the aggregation. The core runs OSPF to the egress, where a firewall applies NAT and security policies. After installation and commissioning, an acceptance test checks every VLAN, the WLAN and failover before the network is handed to O&M.
How the exam asks about this
- "At which layer of a campus network is the user gateway usually configured?" → The aggregation layer, often with VRRP.
- "Put the campus network project stages in order." → Planning and design, deployment and implementation, network O&M, network optimization.
- "Which technology virtualizes several fixed switches into one logical switch?" → iStack (stacking); CSS does the same for modular switches.
What to remember for the exam
- Campus layers: access, aggregation, core and egress, plus server and management zones.
- Small campuses can use two layers; larger campuses use three.
- Access connects terminals and APs; aggregation hosts gateways; core routes fast; egress does NAT and security.
- Reliability: iStack, CSS, Eth-Trunk, VRRP and STP.
- Project stages: planning and design, deployment and implementation, O&M, optimization.
NAT and the internet-facing security policy belong at the egress, not the access layer. The access layer controls who connects, not how the campus reaches the internet.
Common mistakes
Skipping the requirement survey. Without user counts, services and reliability targets, the design cannot be checked. The survey is the first step of planning.
Mixing up iStack and CSS. iStack stacks fixed (box) switches. CSS clusters modular (chassis) switches.
Thinking acceptance testing is part of O&M. Acceptance testing closes the deployment and implementation stage, before the network is handed over to O&M.
Check yourself
What is the main role of the access layer?
To connect terminals and APs to the network, with VLAN assignment, PoE and access control.
What does VRRP provide at the aggregation layer?
A virtual gateway IP shared by two devices, so users keep their gateway if the master fails.
What happens in the network optimization stage?
Performance and new requirements are analyzed, and the network is tuned, upgraded or expanded, feeding back into planning.
Topic 1 of 1 in Typical Campus Networking Solution
Test yourself on Typical Campus Networking Solution
The full Huawei HCIA-Datacom H12-811 question bank has 600 questions, with timed practice exams and an explanation for every answer.
This study guide is independent and is not affiliated with, endorsed by, or sponsored by Huawei. Vendor names, certification names and exam codes are trademarks of their respective owners and are used for identification only.