Campus Network Infrastructure
Build the campus brief before choosing equipment
A campus network connects people and devices across a site. For a school or university project, record the different needs of classrooms, lecture halls, offices, laboratories and outdoor areas instead of assuming that one access point layout or switch configuration suits them all.
Prepare building plans, an endpoint inventory and an application list. Identify concurrent users and operational constraints for each area, including teaching schedules and permitted maintenance windows. The questions below are a procurement and acceptance checklist, not a promise of a particular speed, coverage level or financial saving.
Separate the design workstreams
| Workstream | Information to agree before a quotation |
|---|---|
| Wired access | Endpoint locations, available cable routes, required ports, uplinks and the power requirements of attached devices. |
| Wireless access | Client types, expected simultaneous usage, application needs, mounting constraints and the areas to be measured during a survey. |
| Building connections | Existing fiber records, equipment-room locations, permitted works and ownership of inter-building links. |
| Access policy | Which staff, student, guest and operational devices may reach each service, and who approves exceptions. |
| Operations | Configuration ownership, monitoring, backup, escalation and the agreed software maintenance process. |
Use a design reference without copying a universal bill of materials
Cisco's Campus LAN and Wireless LAN Solution Design Guide discusses access, distribution and core design, PoE considerations, wireless access, authentication and resilience. Its campus definition covers both small sites and multi-building environments. The referenced edition is dated May 2020; treat it as an architectural reference, not evidence that a listed platform is currently orderable or suitable for this project.
The guide describes 802.1X authentication using a client supplicant, a network authenticator and an authentication server. Confirm the proposed client and identity-service support before including that workflow in the acceptance criteria. Redundant links or components also require a defined design and test procedure; their presence alone is not an uptime guarantee.
Validate capacity and power against the selected models
Ask for a model-specific schedule showing access points, switches, power supplies, optics, mounts and licenses. Check supported software and regional ordering requirements in current manufacturer documentation. Do not equate an advertised radio rate with application throughput for every user.
For an existing catalog example, the RUCKUS R850 ordering and power notes identify model-specific considerations to check. This is a reference for a proposed hardware review, not a recommendation that the device meets every campus requirement or interoperates with every management platform.
Agree a pilot and handover record
- Select representative areas and agree the client devices, applications and measurement method before the pilot.
- Test normal access and permitted isolation between user groups against the approved policy.
- Measure the agreed wireless and application criteria under a documented load, recording device and software versions.
- Where redundancy is in scope, test an approved failure and recovery scenario during a controlled window.
- Handover the final port map, configuration backups, license record, test results and support responsibilities.
Record exceptions and owners rather than declaring the entire campus accepted from a single successful connection. Any deployment services, support hours or response commitments must appear in the agreed scope.
Provide the inputs for an enquiry
Share building plans, existing equipment, user and device estimates, application requirements, identity platform, maintenance restrictions and expansion needs. Request separate equipment, subscription, installation and support line items. For equipment-room dependencies, use the data center and facility-readiness checklist alongside the network brief.