Backing Up The Running-Config (Backup Switch Only); Upgrading The Backup Switch - Acopia Adaptive Resource Switch Cli Maintenance Manual

prtlndA1kB# show health
System Health Information
Date
---------------------------------------------------------------------------------------
Wed Feb 28 04:45:02 2007 (0)
prtlndA1kB# ...

Backing Up the Running-Config (Backup Switch Only)

prtlndA1kB(cfg-redundancy)# end
prtlndA1kB# copy running-config ftp://juser:jpasswd@ftp.wwmed.com/runConfA1k
% INFO: The copy command completed successfully.
prtlndA1kB# ...

Upgrading the Backup Switch

prtlndA1kB# copy ftp://jusr:jpasswd@ftp.acopia.com/new.rel releases new.rel
CLI Maintenance Guide
If the status is not "Up" for any of the nodes, contact Acopia Support before
proceeding.
Otherwise, use the
show health
ID Event
- No active alarms.
If any active alarms appear, contact Acopia Support before proceeding.
To prepare for a failed upgrade, save the running-config of the Backup switch. These
configuration parameters will be invaluable if you decide to revert to the old release
after the upgrade. (The global config does not need to be backed up; it will be
preserved on the redundant switch.)
You can use
copy running-config
site. For example, the following command copies the running config to an FTP server
at ftp.wwmed.com:
The next step is to upgrade the Backup switch as described above. For example, the
following command sequence downloads a new software release, new.rel, arms the
switch with the new release, and reloads the system:
command to check for any alarm conditions:
Description
to copy the config to the local chassis or to an FTP
Upgrading Software
Upgrading a Redundant Pair
4-13