HMC UPDATE - HMC UPGRADE
(Remote HMC update/upgrade using network images.)
During the update or upgrade some of these commands may be useful:
- monhmc -r disk <--it is like "df -k" and refreshes every 4 seconds, good to check always
- ls -l /mnt/upgrade <--during saveupgdata.. (doRestore file makes possible after reboot start upgrade automatically)
- ls -l /hmcdump <--during "getupgfiles..."can be checked all files and correct sizes were completely downloaded
- tail -f /tmp/HmcInstall.log <--during update (updhmc) installation log entries are logged here
- ls -l /dump/efix <--during update, image from ftp server first will be copied to this directory before installing it
-------------------------------
HMC UPDATE:
(e.g. 7.9 update to SP2)
1. Read IBM Documentation (readme)
e.g. readme of 7.9 updates can be found here:
http://delivery04.dhe.ibm.com/sar/CMA/HMA/05byc/0/MH01519.readme.html
http://delivery04.dhe.ibm.com/sar/CMA/HMA/0574a/0/MH01451.readme.html
2. Download iso image
e.g. 7.9: http://www-912.ibm.com/s_dir/slkbase.NSF/82a337f562831d2986256839005c83c7/33c6e3ffd6fd09c886257cb30041575d?OpenDocument
- checksum on iso files, compare values with the value on above readme links
csum -h SHA1 HMC_Update_V7R790_SP2.iso
csum -h SHA1 MH01519.iso
3. Note HMC info, backup and reboot
- save some config: lshmc -v; lshmc -V; lshmc -n; lshmc -r
- do a backup (it can take longer): in GUI or in CLI: bkconsdata -r ftp -h <ftp host> -u <user> -d <directory>
- reboot hmc: hmcshutdown -t now -r
4. Update
- GUI: Updates --> Update HMC
- CLI: updhmc -t s -h <myservername> -f </home/updates/corrrective_service.iso> -u <HMC_username> -i
(-t s: type to update from is server (s), -i: prompt for password)
5. Backup HMC
-------------------------------
HMC UPGRADE:
1. Read full documentation
- read many important info about firmwares, HMC models, fixes and dual HMC instructions
7.3 -> 7.7: http://www-912.ibm.com/s_dir/SLKBase.nsf/0/47b71827e031a0ec86257b16004d90a3?OpenDocument
7.7 -> 7.9: http://www-912.ibm.com/s_dir/slkbase.NSF/DocNumber/703169924
2. Download network images
- download from link: http://www14.software.ibm.com/webapp/set2/sas/f/netinstall/home.html
(all files are needed, usually these are: bzImage, initrd.gz, disk1.img, disk2.img, disk3.img, hmcnetworkfiles.sum
- do a checksum: sum <file>, and compare results with hmcnetworkfiles.sum
1. sum bzImage initrd.gz disk1.img disk2.img disk3.img
2. cat hmcnetworkfiles.sum
3. Note HMC info, backup and reboot
- save some config: lshmc -v; lshmc -V; lshmc -n; lshmc -r
- do a backup (it can take longer): in GUI or in CLI: bkconsdata -r ftp -h <ftp host> -u <user> -d <directory>
- save profile data of each managed system:
GUI: System Management --> Server --> Configuration --> Manage Partition Data --> Backup
CLI: 1. BK_DATE="`date '+%Y%m%d'`"; export BK_DATE
2. for MSYS in `lssyscfg -r sys -F name`; do bkprofdata -m ${MSYS} -f ${MSYS}_${BK_DATE}.prof --force; done
- close open service events: chsvcevent -o closeall
- clear old archived diagnostic logs: chhmcfs -o f -d 0
- reboot hmc to see it will come back: hmcshutdown -t now -r
4. Save Upgrade Data
- Save configuration data: saveupgdata -r disk
This operation will mount /mnt/upgrade and save configuration data then unmount /mnt/upgrade. This should take ony a few moments.
(This data will be used during next boot, so do not initiate reboot after this has been done, or you have to do this step again.)
5. Get Upgrade Files
- copy network images from ftp server to HMC: getupgfiles -h <ftp host> -u <user> -d <directory>
Files will be copied temporarily in the directory /hmcdump and during the copy there is no indication of progress.
To monitor progress, open another session and type: "ls -l /hmcdump" to check file size (do this repeatedly to see progress)
After the files have been downloaded, the restricted shell returns to the command prompt.
The /hmcdump dir will be empty because, after the download the files are placed in a special location (alternate boot location).
6. Set HMC to boot from alternate disk
- check if alternate boot is enabled before setting the alternate boot: lshmc -r
- set alternate boot: chhmc -c altdiskboot -s enable --mode upgrade
- check again tio make sure alternate boot is enabled: lshmc -r
(it should show something like: ssh=enable,[...],netboot=disable,altdiskboot=enable,[...])
7. Reboot HMC
- reboot HMC: hmcshutdown -t now -r
The HMC will boot from the alternate disk partition then start processing the upgrade files.
Most installs complete between one to two hours.
8. Create a backup
-------------------------------
FTP connection between HMC and FTP server
FTP connection will be needed between HMC and FTP server. FTP server is where the install images are stored (it can be a NIM server.)
If you want to use remote FTP installs on HMC, an FTP user will be needed on the remote (AIX) server.
There is a default script on AIX which creates an ftp or anonymous user for this FTP connection: /usr/samples/tcpip/anon.ftp
IBM officially says this scripts should be used to create FTP user, otherwise connection will work but files may won’t be reachable by HMC, but actually I created in the past FTP users with other method and it worked well.
FTP check from HMC:
- in GUI try to do an update operation, and choose FTP, or do an HMC backup (just it could take long)
- try sendfile command on HMC, which transfer files with ftp to another server
sendfile -f id_dsa.pub -h 10.10.10.1 -d /nim/hmcftp -u hmcftp
-------------------------------
The below post was my original description about HMC upgrades, and I keep it for reference, but the method described above is more detailed and up to date.
HMC UGRADE (v6.1.3 -> v7.3.5)
(this can be done as hmc user)
1. check prerequisites:
- hmc device supports new hmc version
- system firmware on supported levels (http://www-933.ibm.com/support/fixcentral/firmware/supportedCombinations)
- Back up critical console data (to an FTP server is OK)
2. some fixes have to be installed prior to the upgrade:
MH01082, MH01110, MH01128 and after that MH01127 (this will enable upgrade to v7 in 1 step)
- download zip files and store them on an FTP server
- on HMC: Licensed Internal Code upd. -> HMC Code Update -> Inst. Corr. Serv. -> Download from remote ... (give absolute path to file)
- hmcshutdown -t now -r <--reboot HMC (it took for me 10-15 minutes)
- lshmc -V <--verify update successfully installed
3. upgrade to v7.3.5:
- download necessary install images to an FTP server
- chsvcevent -o closeall <--closes all serviceable events on the HMC to clean up before upgrade (for me did not work)
- chhmcfs -o f -d 0 <--clearing out old logfiles to clean up before upgrade (for me did not work)
- hmcshutdown -t now -r <--make sure there are no problems with reboot (if we did this in step 2 we can omit here)
- saveupgdata -r disk <--it mounts /mnt/upgrade, save config. data then unmounts it (it took less than a minute)
(this is only configuration data, which will be used during reboot after the upgrade)
- getupgfiles -h <ftp server> -u <user> --passwd <paswd> -d <dir on ftp server> <--mounts /hmcdump, copy install files there, umount
- chhmc -c altdiskboot -s enable --mode upgrade <--it sets HMC to boot from the install images and allow the upgrade to proceed
- hmcshutdown -t now -r <--it took 30-40 minutes for me
- lshmc -V <--it will show new version
4. some fixes are available to 7.3.5 which can be installed:
- download iso images to FTP server
(first HMC_Update_V7R350_SP3.iso has to be installed after that MH01259.iso)
- install:
from command line:
updhmc -t s -h <ftp server> -u <user> -p <passwd> -f /software/server/hmc/fixes/MH01195.iso -r
from GUI:
Updates -> Update HMC -> next, next ...
- hmcshutdown -t now -r <--reboot HMC for the changes to be available (after each fix install)
5. create backup
--------------------------------------------
(Remote HMC update/upgrade using network images.)
During the update or upgrade some of these commands may be useful:
- monhmc -r disk <--it is like "df -k" and refreshes every 4 seconds, good to check always
- ls -l /mnt/upgrade <--during saveupgdata.. (doRestore file makes possible after reboot start upgrade automatically)
- ls -l /hmcdump <--during "getupgfiles..."can be checked all files and correct sizes were completely downloaded
- tail -f /tmp/HmcInstall.log <--during update (updhmc) installation log entries are logged here
- ls -l /dump/efix <--during update, image from ftp server first will be copied to this directory before installing it
-------------------------------
HMC UPDATE:
(e.g. 7.9 update to SP2)
1. Read IBM Documentation (readme)
e.g. readme of 7.9 updates can be found here:
http://delivery04.dhe.ibm.com/sar/CMA/HMA/05byc/0/MH01519.readme.html
http://delivery04.dhe.ibm.com/sar/CMA/HMA/0574a/0/MH01451.readme.html
2. Download iso image
e.g. 7.9: http://www-912.ibm.com/s_dir/slkbase.NSF/82a337f562831d2986256839005c83c7/33c6e3ffd6fd09c886257cb30041575d?OpenDocument
- checksum on iso files, compare values with the value on above readme links
csum -h SHA1 HMC_Update_V7R790_SP2.iso
csum -h SHA1 MH01519.iso
3. Note HMC info, backup and reboot
- save some config: lshmc -v; lshmc -V; lshmc -n; lshmc -r
- do a backup (it can take longer): in GUI or in CLI: bkconsdata -r ftp -h <ftp host> -u <user> -d <directory>
- reboot hmc: hmcshutdown -t now -r
4. Update
- GUI: Updates --> Update HMC
- CLI: updhmc -t s -h <myservername> -f </home/updates/corrrective_service.iso> -u <HMC_username> -i
(-t s: type to update from is server (s), -i: prompt for password)
5. Backup HMC
-------------------------------
HMC UPGRADE:
1. Read full documentation
- read many important info about firmwares, HMC models, fixes and dual HMC instructions
7.3 -> 7.7: http://www-912.ibm.com/s_dir/SLKBase.nsf/0/47b71827e031a0ec86257b16004d90a3?OpenDocument
7.7 -> 7.9: http://www-912.ibm.com/s_dir/slkbase.NSF/DocNumber/703169924
2. Download network images
- download from link: http://www14.software.ibm.com/webapp/set2/sas/f/netinstall/home.html
(all files are needed, usually these are: bzImage, initrd.gz, disk1.img, disk2.img, disk3.img, hmcnetworkfiles.sum
- do a checksum: sum <file>, and compare results with hmcnetworkfiles.sum
1. sum bzImage initrd.gz disk1.img disk2.img disk3.img
2. cat hmcnetworkfiles.sum
3. Note HMC info, backup and reboot
- save some config: lshmc -v; lshmc -V; lshmc -n; lshmc -r
- do a backup (it can take longer): in GUI or in CLI: bkconsdata -r ftp -h <ftp host> -u <user> -d <directory>
- save profile data of each managed system:
GUI: System Management --> Server --> Configuration --> Manage Partition Data --> Backup
CLI: 1. BK_DATE="`date '+%Y%m%d'`"; export BK_DATE
2. for MSYS in `lssyscfg -r sys -F name`; do bkprofdata -m ${MSYS} -f ${MSYS}_${BK_DATE}.prof --force; done
- close open service events: chsvcevent -o closeall
- clear old archived diagnostic logs: chhmcfs -o f -d 0
- reboot hmc to see it will come back: hmcshutdown -t now -r
4. Save Upgrade Data
- Save configuration data: saveupgdata -r disk
This operation will mount /mnt/upgrade and save configuration data then unmount /mnt/upgrade. This should take ony a few moments.
(This data will be used during next boot, so do not initiate reboot after this has been done, or you have to do this step again.)
5. Get Upgrade Files
- copy network images from ftp server to HMC: getupgfiles -h <ftp host> -u <user> -d <directory>
Files will be copied temporarily in the directory /hmcdump and during the copy there is no indication of progress.
To monitor progress, open another session and type: "ls -l /hmcdump" to check file size (do this repeatedly to see progress)
After the files have been downloaded, the restricted shell returns to the command prompt.
The /hmcdump dir will be empty because, after the download the files are placed in a special location (alternate boot location).
6. Set HMC to boot from alternate disk
- check if alternate boot is enabled before setting the alternate boot: lshmc -r
- set alternate boot: chhmc -c altdiskboot -s enable --mode upgrade
- check again tio make sure alternate boot is enabled: lshmc -r
(it should show something like: ssh=enable,[...],netboot=disable,altdiskboot=enable,[...])
7. Reboot HMC
- reboot HMC: hmcshutdown -t now -r
The HMC will boot from the alternate disk partition then start processing the upgrade files.
Most installs complete between one to two hours.
8. Create a backup
-------------------------------
FTP connection between HMC and FTP server
FTP connection will be needed between HMC and FTP server. FTP server is where the install images are stored (it can be a NIM server.)
If you want to use remote FTP installs on HMC, an FTP user will be needed on the remote (AIX) server.
There is a default script on AIX which creates an ftp or anonymous user for this FTP connection: /usr/samples/tcpip/anon.ftp
IBM officially says this scripts should be used to create FTP user, otherwise connection will work but files may won’t be reachable by HMC, but actually I created in the past FTP users with other method and it worked well.
FTP check from HMC:
- in GUI try to do an update operation, and choose FTP, or do an HMC backup (just it could take long)
- try sendfile command on HMC, which transfer files with ftp to another server
sendfile -f id_dsa.pub -h 10.10.10.1 -d /nim/hmcftp -u hmcftp
-------------------------------
The below post was my original description about HMC upgrades, and I keep it for reference, but the method described above is more detailed and up to date.
HMC UGRADE (v6.1.3 -> v7.3.5)
(this can be done as hmc user)
1. check prerequisites:
- hmc device supports new hmc version
- system firmware on supported levels (http://www-933.ibm.com/support/fixcentral/firmware/supportedCombinations)
- Back up critical console data (to an FTP server is OK)
2. some fixes have to be installed prior to the upgrade:
MH01082, MH01110, MH01128 and after that MH01127 (this will enable upgrade to v7 in 1 step)
- download zip files and store them on an FTP server
- on HMC: Licensed Internal Code upd. -> HMC Code Update -> Inst. Corr. Serv. -> Download from remote ... (give absolute path to file)
- hmcshutdown -t now -r <--reboot HMC (it took for me 10-15 minutes)
- lshmc -V <--verify update successfully installed
3. upgrade to v7.3.5:
- download necessary install images to an FTP server
- chsvcevent -o closeall <--closes all serviceable events on the HMC to clean up before upgrade (for me did not work)
- chhmcfs -o f -d 0 <--clearing out old logfiles to clean up before upgrade (for me did not work)
- hmcshutdown -t now -r <--make sure there are no problems with reboot (if we did this in step 2 we can omit here)
- saveupgdata -r disk <--it mounts /mnt/upgrade, save config. data then unmounts it (it took less than a minute)
(this is only configuration data, which will be used during reboot after the upgrade)
- getupgfiles -h <ftp server> -u <user> --passwd <paswd> -d <dir on ftp server> <--mounts /hmcdump, copy install files there, umount
- chhmc -c altdiskboot -s enable --mode upgrade <--it sets HMC to boot from the install images and allow the upgrade to proceed
- hmcshutdown -t now -r <--it took 30-40 minutes for me
- lshmc -V <--it will show new version
4. some fixes are available to 7.3.5 which can be installed:
- download iso images to FTP server
(first HMC_Update_V7R350_SP3.iso has to be installed after that MH01259.iso)
- install:
from command line:
updhmc -t s -h <ftp server> -u <user> -p <passwd> -f /software/server/hmc/fixes/MH01195.iso -r
from GUI:
Updates -> Update HMC -> next, next ...
- hmcshutdown -t now -r <--reboot HMC for the changes to be available (after each fix install)
5. create backup
--------------------------------------------