
Hardware Management Console Best Practices
- 36 -
7 Maintaining Licensed Internal Code
Make sure you keep track of new releases, updates and emergency fixes to HMC
code. You can do this in one of two ways:
• Sign up for the technical support subscription service to receive
emails when updates become available on the web
• Monitor the web manually on a regular basis:
http://www14.software.ibm.com/webapp/set2/sas/f/hmc/home.html
Read the web site carefully. Select the appropriate platform, POWER4 or p5,
whichever is appropriate. There are many additional resources on the site, such as
links to additional technical information, hints and tips, and the latest Command
Line Specification, where you’ll find new commands that may have been added.
You can order Recovery CDs or download packages that contain the files needed
to burn your own Recovery CD. The files used to create CDs have an .iso file
extension. The CDs created from these packages are bootable. You can download
updates to HMC code as well as emergency fixes, and you can order CDs
containing the updates and fixes. The CDs containing updates and fixes are NOT
bootable.
7.1 Critical Console Data Backups
It’s important to maintain a current Critical Console Date (CCD) backup to use in
recovering the HMC after the loss of a disk drive. Whenever you go to a new
version level of HMC code, or use a Recovery CD to update the HMC, you
should create a new CCD backup immediately following the installation. If you
update HMC code between releases using the Corrective Service files
downloadable from the web, and then create new CCD backups after the update,
you can use those CCD backups and the last-used Recovery CD to rebuild the
HMC to the level in use when the disk drive was lost.
Another example where a CCD would be useful is when replacing an FSP or BPC
on a POWER5 server. A fresh CCD backup should be made before starting the
replacement in order to preserve the DHCP lease file on the HMC that lists the
starting FSP and BPC IP addresses. If for some reason things don’t work after
replacing the FSP or BPC, this backup can be used to restore the original
information so the customer can go back to the original FSP and BPC. If the
replacement is successful, a new IP address will be assigned to the new
component and the lease file will be updated. At this point, a new CCD backup
should be created capturing that freshly updated DHCP lease file.
Komentáře k této Příručce