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.
Before the truck rolls, the dispatch packet should name the closet, the change ticket, the console and out-of-band path, and who can authorize a stop. On arrival the technician checks serials against the license and boot-mode expectation, and reports a mismatched module or missing stack cable before powering anything.
- 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.
Stack member order and priority decide which unit becomes master after the next reload, so set them deliberately and write down what you chose. Confirm the stack cables are seated in a ring rather than a chain before powering up, because a half-connected ring survives commissioning and fails during the first member replacement.
- 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.
Evidence for a Catalyst cutover reads better as saved command output than as a checkmark: member and ring state, interface counters, PoE draw against the supply, and neighbor tables captured at a known time. When a phone or access point stays down, the escalation carries that output plus the interface name, not a description.
- 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.
A year later someone tracing a strange VLAN will want the old-to-new interface sheet, the boot image and license state recorded at cutover, and the serial that a support contract is written against. Keep the running configuration and any credentials in the client repository, and point published instructions at Cisco documentation.
- 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.
Reconcile hardware
Match delivered chassis, uplink modules, power supplies and licenses against the approved design before any rack work begins.
Stage software
Load the agreed IOS XE image, set stack member order and priorities, and apply the reviewed configuration offline.
Migrate ports
Move uplinks and access ports group by group against the port map, labeling each cable as it lands.
Verify services
Check Layer 2 and Layer 3 reachability, PoE draw, stack resilience and downstream device recovery before releasing the site.
Information to gather before design
A Catalyst cutover depends on details that live outside the switch itself, so the port map, license position and downstream device list decide how the night runs.
- Current running configuration and version
- Port map with VLAN assignments
- Stack member order and roles
- PoE device list per closet
- Uplink fiber and transceiver types
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.
Planning a Catalyst 9000 switch replacement?
If the design is approved but the field procedure is not written yet, send the site list, current switch models, uplink types and the maintenance window you have to work inside.