Campus networks: plan wired, wireless and secure access together
Start with users, devices and coverage, then align switch ports, wireless access, security policies and operating responsibilities.
Describe the places people actually work
A campus network supports desks, meeting rooms, production areas and shared services. Begin with a floor plan and a device inventory instead of choosing a switch solely by port count. Identify users, phones, cameras, access points and systems that need continuous connectivity. Document which devices need power over Ethernet and which applications are sensitive to interruptions.
Plan access, uplinks and power as one system
Count current endpoints and allow a stated growth reserve. Work out uplink demand from the applications and simultaneous use. For powered devices, check both the per-port requirement and the total power budget of the chosen switch configuration. Cabling length, cable category, optics and existing racks can constrain the design just as much as the product specification.
Read family specifications at the model level
Our catalog includes the Cisco Catalyst 9300 family. Its manufacturer documentation covers multiple variants with different interfaces and stacking options. A family-level feature is not a promise that every selected model supports the same configuration. Confirm the exact switch, power supply, software version, licenses and uplink modules together. Apply the same discipline to access points and their management platform.
Define who can reach each service
Separate employee, guest, operational and device traffic according to the project requirements. Agree identity and access rules, management access and the boundary between internal services and external connections. Wireless placement needs a site survey that considers coverage, density and interference. Available bands, including 6 GHz where relevant, must follow the rules of the deployment region.
Make the handover operable
Before procurement, agree coverage checks, link tests and acceptable recovery behaviour. The final handover should identify installed models, port assignments, approved software and licenses, configuration ownership and monitoring responsibilities. Include a change procedure and a way to restore configuration backups. A network proposal is more useful when the operations team knows how to maintain it after installation.
Manufacturer reference
Cisco Catalyst 9300 Series data sheet
Project guidance
This article is planning guidance, not a tested bill of materials. Product compatibility, pricing and site-specific performance are confirmed for each project. The cover is a conceptual illustration of the topic.