Checking The Health Of The Active Switch; Failing Over To The Upgraded Switch; Success Path; Failure Path - Acopia Adaptive Resource Switch Cli Maintenance Manual

Checking the Health of the Active Switch

Failing Over to the Upgraded Switch

Success Path

Failure Path

prtlndA1kB# boot system oldRelease.rel
CLI Maintenance Guide
Repeat the health checks at the active switch, where the previous release is still
running. Use the
show redundancy
formed, and use show health to verify that there are no active alarms. Both peers and
the quorum disk should all have a status of "Up," and there should be no active
alarms.
If the status is not "Up" for any of the nodes, or if any active alarms appear, contact
Acopia Support before proceeding.
The next step is to fail over and put the new software into active service. Reload the
other switch, the switch currently running services on the old software. Use the
priv-exec command. This forces failover to the switch running the new
reload
software.
From here, there are two paths to follow: the success path (you want to deploy the
new software) or the failure path (you want to continue running the old software).
Upgrade the peer switch (now in the Backup role) to the new release. Use the same
steps that you used above.
When the switch returns from its reboot, both switches are now running the new
software.
To return the originally-active peer ("prtlndA1k" in our examples) to its active status,
use on the currently-active peer ("prtlndA1kB"). This causes a failover.
reload
To return to the old release, you can downgrade the now-Active switch to the old
software. Use
boot system
Downgrading deletes all configuration parameters, both the running-config and the
global-config; a CLI prompt asks for confirmation before doing this. For example:
command to confirm that the redundant pair is
to select the old release, then use
Upgrading Software
Upgrading a Redundant Pair
to install it.
reload
4-15