Campus switching: Catalyst and Cisco Smart Switches
In the Catalyst 9000 portfolio, the 9200/9200CX families serve access scenarios; 9300/9300X, stackable enterprise access; 9400, modular access; 9500/9500X, fixed core and aggregation; and 9600, modular core and aggregation. This structure helps select the device's role before comparing variants. Interfaces, power supplies, modules, stacking and features must be checked by model and version. The portfolio also includes Cisco C9350 for access, C9550 for fixed aggregation and core, and C9610 for modular core. These are Cisco C9000 Smart Switches families, with their own hardware, software and subscription rules. Similar naming does not justify treating any existing Catalyst as equivalent, nor does it imply mandatory replacement. The assessment must preserve useful investments and check the evolution path for each installation.
Enterprise Wi-Fi: access points and controllers
The project may involve Wi-Fi 6/6E and Cisco Wireless Wi-Fi 7 generations, according to device profiles, density, environment and refresh cycle. AP families and Catalyst 9800/CW9800 controllers provide deployment alternatives; cloud management through Meraki Dashboard also depends on platform eligibility. The vendor matrix determines the supported combination. Coverage is only part of the problem. We plan channels, power, capacity per area, client movement and integration with the wired network. Features such as MLO and wider channels depend on the AP, client, software and permitted installation conditions. An advertised radio speed does not represent an application's guaranteed usable throughput.
Branches and WAN: Catalyst SD-WAN
Catalyst 8000 Edge platforms are part of the Catalyst SD-WAN ecosystem, with physical and virtual alternatives for connecting branches, data centers and cloud environments. Selection must consider encrypted traffic, enabled services, interfaces, available connectivity and licensing. In WAN engineering, redundancy must be tested with actual link failures and quality degradation. Important decisions include which applications can access the internet locally, how internal networks will be accessed and where to apply inspection and security policies. SD-WAN and firewall responsibilities must be explicitly designed.
Data center: Nexus, NX-OS, ACI and Nexus Dashboard
The Nexus 9000 portfolio brings together families for data center networks. Depending on hardware and version, the project can adopt NX-OS, a VXLAN EVPN fabric or Cisco ACI. Selection considers leaf or spine roles, interfaces, scale, telemetry and support for the desired operating mode. The Nexus 9000 name alone does not guarantee all these features. ACI uses its own policy model and APIC controllers; an NX-OS/VXLAN EVPN deployment has different organization and tools. The architecture should be chosen according to existing integrations, teams and operations. Migration between models requires design, compatibility and an appropriate window. Nexus Dashboard centralizes data center operational functions. In the current unified generation, capabilities previously presented as Fabric Controller, Insights and Orchestrator have become part of a unified product. DCN entitlements and support matrices still determine available functions. Materials from earlier versions must be read in their context.
Identity and access: Cisco ISE
Cisco Identity Services Engine contributes to the network access control strategy, with features that vary by version, license and integration. Authentication, device classification and identity-based policies help organize who can access which services. Deployment must consider certificates, directories, devices without a supplicant, guests and recovery procedures.