How to Run a Cisco Expressway Cluster Upgrade Safely

Expressway upgrades are a change-window gamble: four node web UIs, a manual order to get right, and no safety net if a peer does not come back.

The manual reality

You log into each Expressway-C and Expressway-E node, take backups by hand, put nodes in maintenance, drain calls, upload and install in the right order, reboot, and verify, all while watching the clock.

The staged way

Atlas auto-detects your C and E pairs, takes a pre-upgrade backup during preflight, then runs the whole sequence in the order you set: maintenance, drain calls, upload, install, reboot, verify. It halts the entire run on any failure, and a halted run resumes where it stopped.

Lifecycle management for Expressway-C and Expressway-E clusters.