Cisco Catalyst 9000 Stack and Switch Cutover
Catalyst 9000 families span fixed, modular, access and core roles with different StackWise, uplink, power and IOS XE requirements. TechRunz converts the approved design into a field procedure that reconciles hardware, licenses, software, stack order, interfaces and downstream services before production cables move.
Make each dispatch repeatable and recoverable
Define prerequisites, remote ownership, method of procedure, acceptance evidence and rollback before technicians arrive onsite.
Hardware, software and configuration readiness
Reconcile every serial, model, module, stack cable, power supply, optic and license against the design. Confirm rack depth, airflow, circuit and UPS capacity. Verify the approved IOS XE release and install or bundle mode before dispatch.
Stage hostname, management, AAA, VLANs, trunks, spanning tree, port-channels, routing, DHCP relay, QoS, telemetry and access ports through the client process. Compare the intended configuration with the source and identify obsolete or site-specific commands rather than copying blindly.
The remote team should supply the site identifier, approved design, equipment list, configuration status, contacts, access window and success criteria. The field technician verifies serials, labels, damage, accessories and prerequisites before changing production service.
- Chassis/modules/optics
- Stack and power components
- IOS XE and boot mode
- Configuration and license baseline
Rack, stack and port migration
Label stack members, priority, stack ports, uplinks and power before assembly. Verify stack-ring or virtual architecture status using the model-specific procedure. Photograph and label the old switch interfaces before moving any cable.
Migrate uplinks and downstream ports in documented groups with remote hold points. Keep known-good optics, patch leads and old hardware available. Record interfaces that do not come up and avoid moving unidentified cables solely to make the port count match.
Use a written method of procedure with hold points for configuration-sensitive actions. Photograph and label the before state, preserve known-good cabling or configuration, and keep a practical rollback path. Record deviations as they occur instead of reconstructing them after the visit.
- Member and uplink labels
- Old-to-new port map
- Controlled migration groups
- Old hardware preserved
| Gate | Required state | Evidence |
|---|---|---|
| Ready | Hardware, software and configuration match | Staging sheet |
| Physical | Rack, stack, power and uplinks healthy | Status/photos |
| Service | Ports, VLANs, routing and endpoints pass | Test record |
| Recoverable | Backup, old switch and ownership retained | Closeout/approval |
Layer 2, Layer 3, PoE and resilience tests
Validate stack/member state, software, license, management, NTP, AAA, VLANs, spanning tree, port-channels, routing and monitoring. Check every uplink for speed, errors and optic levels where available and every access group for negotiated speed, PoE and intended VLAN.
Test voice, wireless, security, printers, building systems and representative users. Exercise an approved member, uplink or power failure when resilience is part of the design. Compare logs and convergence with the acceptance threshold.
Validation must cover physical status, management visibility, addressing, uplinks, power, policies and representative user traffic. When redundancy is expected, test the approved failure and restoration scenarios. Escalations should include timestamps, identifiers and reproducible evidence.
- Stack/routing/L2 health
- Port, PoE and optics
- Representative endpoints
- Approved failure scenarios
Inventory, backup and operational handoff
Deliver serial and member inventory, rack and stack map, port migration sheet, software and boot state, configuration backup, test output, exceptions and photographs. Flag shutdown, err-disabled, high-error or temporary interfaces.
Transfer configuration, software, licensing, monitoring, backup and support ownership. Remove sensitive configuration from general reports and store it in the client-controlled repository. Do not disconnect or dispose of the previous switch until authorized.
Closeout combines annotated photographs, serials, port and cable records, software versions, test output, exceptions and ownership. Credentials and private configurations belong in the client-controlled repository, while public pages should point only to official manufacturer support resources.
- Serial/member reconciliation
- Port sheet and backups
- Exception and log review
- Named operations ownership
How we plan and deliver the work
The final design depends on site conditions, existing systems, client policies and the selected manufacturer or platform.
Prepare
Confirm access, equipment, remote readiness and rollback.
Execute
Install through the approved method and document deviations.
Test
Validate management, service, resilience and user workflows.
Close
Deliver evidence, inventory, exceptions and support ownership.
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 access and remote contacts
- Staging, inventory and prerequisites
- Method, maintenance window and rollback
- Acceptance tests and escalation
- Evidence and operational ownership
Frequently asked questions
These are common planning questions. A site-specific answer should be confirmed during discovery and design.
Can a configuration be copied unchanged from an older Catalyst?
Not safely. Review hardware, interface names, software, licenses and deprecated or site-specific commands.
Why document stack member order?
Member numbering and priority affect interface mapping, replacement and troubleshooting.
Is a green port light sufficient acceptance?
No. Verify VLAN, PoE, policy, errors and the endpoint workflow.
When can the old switch be removed?
After service acceptance, backups, dependencies and the authorized rollback window are complete.
Manufacturer software, firmware and technical files remain on the manufacturer’s official website. We do not mirror firmware files locally.
Build a repeatable field-deployment plan
Provide the site list, target schedule, equipment responsibility, change-window constraints and acceptance criteria. We will help turn them into a practical rollout and closeout workflow.