AlterPath Manager 2500 Upgrade instructions from previous versions to V_1.4.1 (Apr/21/2006): 1. Login to the 2500 console as root. 2. cd /tmp 3. Download the all_2500_v141.tgz and all_2500_v141.tgz.md5sum from ftp://ftp.cyclades.com/pub/cyclades/alterpath/apm/2500/released/V_1.4.1 to /tmp. Note: If you want to make sure the md5sum file is really from Cyclades web site, you can call Cyclades Technical Support and double-check the md5sum value. 4. Do a backup of all filesystems before installing this image, i.e., run the "backup" command. Save the backup file in another system. Note: If you have V_1.4.0-RC1 or earlier, "backup" command can fail with the error "mysqldump: Got error: 2020: Got packet bigger than 'max_allowed_packet' when retrieving data from server". In this case, download "backup" from ftp://ftp.cyclades.com/pub/cyclades/alterpath/apm/2500/released/V_1.4.0 to /tmp, then copy the file from /tmp to /sbin: cp /sbin/backup /sbin/backup.original cp /tmp/backup /sbin 5. If Heartbeat is enabled, you will have to disable Heartbeat and upgrade each APM independently. a. First, please make sure the Primary and the Secondary APM's are synchronized. You can run "cat /proc/drbd" to check the progress of synchronization. All drbd devices will show "ld:Consistent" when the synchronization is complete. b. Stop Heartbeat in the Secondary APM by running "sethearbeat". Answer "n" to the "Do you want to enable Heartbeat, Redundancy, Data Synchronization and Failover?" question. c. Reboot the Secondary APM. d. Repeat steps b and c on the Primary APM. The following steps should be done in each APM. 6. Run these commands to install the new version: mke2fs /dev/hda4 fsck /dev/hda4 /sbin/installimg all all_2500_v141.tgz Attention: In case of any errors in step 6, repeat the commands in step 6. If you still have errors, call Cyclades Technical Support. 7. If step 6 was OK, run: reboot 8. After the upgrade, running sysinfo in the shell prompt or clicking the "about" link on the web should display Config Version : V_1.4.1 OS Version : V_1.4.1 (Apr/21/2006) APM Version : V_1.4.1 (04/21/2006) APM Database : V_1.4.1 (2006-04-21) 9. Check if there is no line with "FAILED" in /var/log/conf-V_1.4.1.log (run "grep FAILED /var/log/conf-V_1.4.1.log"). If there is any line with "FAILED", you will need to run "defconf" and reboot the APM to restore the System configuration to the factory default. 10. These steps should be done only for Heartbeat: Note: Both APM's should be running the same version. a. If no error happened during the upgrade, re-enable Heartbeat from the GUI. b. Reboot the primary APM and reboot the secondary APM to activate the Heartbeat configuration. c. The APM will be ready to use after the synchronization is complete.