Cisco Catalyst 9000 Campus Network Design
Catalyst 9000 includes fixed and modular switching families for branch, access, distribution and core roles. Correct selection depends on the complete campus topology and availability goal.
Build the physical and logical design together
Confirm scale, topology, power, uplinks, management, licensing, security, testing and lifecycle before selecting hardware.
Platform and architecture fit
Choose collapsed-core, three-tier, routed-access or another validated model from building count, users, services and outage tolerance. Assign each switch an access, distribution, core or edge role. Size forwarding, routing, MAC, policy, multicast and uplink scale for that role.
Existing Catalyst generations require lifecycle review. A working switch may lack current software, support, power or speed for new access points and endpoints. Record migration dependencies and feature parity rather than copying configuration blindly.
- Campus layer and topology
- Platform scale and feature requirements
- Existing hardware lifecycle
- Availability and convergence goals
Ports, power and physical infrastructure
Model copper speed, UPOE/PoE loads, uplinks, optics, StackWise or StackWise Virtual, redundant power and cooling. PoE budgets must include simultaneous device demand and UPS runtime. Verify transceiver support for the exact hardware and IOS XE release.
Coordinate racks, grounding, patching, fiber polarity and cable certification. Stack members, power supplies and uplinks need labels matching the logical configuration. Reserve physical room for replacement and service.
- Port speed and PoE load
- Stacking and redundant power
- Uplinks and supported optics
- Rack, fiber and patching records
| Family | Common role | Confirm |
|---|---|---|
| 9200 | Branch and access | Ports, PoE, uplinks and scale |
| 9300 | Access and distribution | Stacking, UPOE and routing |
| 9400 | Modular access/distribution | Supervisors, line cards and power |
| 9500/9600 | Core/distribution | Density, redundancy and routing scale |
Management, security and lifecycle
Decide whether switches use CLI, Catalyst Center, Meraki cloud monitoring or another supported operations model. Confirm Smart Licensing, account ownership, telemetry and administrator roles. Protect console, SNMP, APIs and configuration archives.
Use Cisco recommended releases and staged upgrades. Review ISSU or other high-availability claims for the exact platform and topology. Back up configurations and verify stack, routing and services after change.
- IOS XE and management model
- Smart Licensing and ownership
- Named roles and secure management
- Staged update and rollback
Commissioning and closeout
Test VLANs, routing, authentication, PoE, uplinks, redundancy, monitoring and application traffic. Simulate a member, link or power failure where the design requires resilience. Record convergence and any manual recovery.
Deliver diagrams, rack and port schedules, serials, licenses, optics, configs and test evidence. Document local recovery access without exposing credentials in public files.
Before final acceptance, reconcile the installed bill of materials with the approved design and current manufacturer records. Confirm model, hardware revision, serial, support status, software, license or subscription, rack location, power source, switch port and uplink for every managed component. Review alarms and logs after a representative traffic period, not only at the instant the link becomes active. Operations should receive a protected configuration backup, recovery access procedure, escalation path, maintenance assumptions and a list of known exceptions. Where cloud management is used, verify that the client organization—not an individual installer account—owns the tenant, subscriptions and recovery contacts. These controls make later support, expansion and replacement practical across multiple sites.
- VLAN and routing tests
- Power, link and stack failures
- Monitoring and application validation
- Protected configuration closeout
How we plan and deliver the work
The final design depends on site conditions, existing systems, client policies and the selected manufacturer or platform.
Discover
Inventory sites, users, applications, circuits and existing assets.
Engineer
Select topology, hardware, power, optics, licenses and policy.
Stage and deploy
Preconfigure, back up and install through change control.
Validate
Test performance, resilience, monitoring and recovery and deliver records.
Information to gather before design
Good decisions are easier when the project team starts with complete operational and technical information. The following items help reduce assumptions, change orders and avoidable return visits.
- Site and application requirements
- Topology, ports, PoE and uplinks
- Management, licenses and administrator roles
- Security, software and recovery
- Testing and documentation standards
Frequently asked questions
These are common planning questions. A site-specific answer should be confirmed during discovery and design.
Is Catalyst 9300 always the correct access switch?
No. Select the platform from port, PoE, uplink, scale, resilience and feature requirements.
Can Catalyst switches be monitored in Meraki Dashboard?
Selected models and modes support cloud monitoring or management; verify current eligibility and feature behavior.
Does stacking eliminate every outage?
No. Power, software, uplinks, topology and failure modes still require design and testing.
Where should IOS XE come from?
Use Cisco official software and support channels with entitlement and compatibility review.
Manufacturer software, firmware and technical files remain on the manufacturer’s official website. We do not mirror firmware files locally.
Plan a testable network-infrastructure project
Share available drawings, site counts, pathways, distances, applications and turnover requirements. We will help identify the surveys, materials, testing and documentation the project needs.