FAQ
and Opinions
This section is contains the most commonly asked questions and a
few recommendations concerning the update_all. Most answers will be kept short
and to the point (as much as possible).
1. Is it okay to install my Technology Level in the “APPLIED” state ? What if I want to reject the TL update if there is a problem ?
With the introduction of Technology Levels and the “all or nothing” packaging format, these updates are bringing in on the upwards of 400+ fileset updates for each TL. Attempting to perform a “reject” process on so much code simply does not work well, and is not supported. Recommended back-out methods are discussed earlier in this document.
1a. Does the same hold true for Service Packs ?
The Service Pack updates are certainly much smaller groups of updates....typically numbering around 40-50 per update. While you certainly will have a better chance of successfully rejecting 40 filesets instead of 400, it would still be best to have one of the back-out methods mentioned earlier.
2. Why does my update_all have problems when I use an NFS mounted cdrom ?
When running an update_all over NFS, you create your own mount point for the cdrom drive. This does not allow it to recognize the fact that there are multiple volumes available that contain the correct requisite filesets. Multiple update_all operations may be needed on each volume when NFS mounting a cdrom drive. A better option may be to ‘bffcreate’ the contents of all CDs down to a directory, then NFS mount that directory.
3. The update_all failed. What now ?
Do not reboot. You can review the log to find out what failed and why. If you are comfortable and familiar with these situations you can correct the failures and re-update the filesets. If not, please call the helpdesk and open a PMR for assistance. Have the log available to email in if necessary.
4. I need to run my update today but I may not be able to reboot until next week. Is that a problem ?
Plans should be made to reboot as soon as the update is complete and checks have been made to ensure there were no failures. System files will have been replaced, but the corresponding kernel and library updates will not be loaded until boot time. You will likely encounter problems if you delay rebooting.
5. Is it recommended to reboot before issuing a TL upgrade ?
If this is possible, absolutely. There are systems out there that have not been rebooted in a year or more. Who is to say that something has not happened in that time that simply would not show up until a reboot. Rebooting the system first assures a good boot image, a stable system, and would isolate any problem that normally would not be caught until the post-update reboot as either a preexisting issue, or an issue directly related to the TL update itself.
6. Some say to use base AIX install media when updating the TL, others say the TL fix downloads or CDs should be used. Which is right ?
The recommendation is to use the TL fix downloads from FixCentral, or the TL CDs that can be ordered either online or from AIX SupportLine. You can also use the base AIX installation media, however without getting into a long answer, the recommendation is using the TL fix packages.
7. How long will the update_all take ?
This is a question that does not quite have a definite answer. The length of time required for the update_all depends on how many filesets are being updated as well as the available system resources such as processors and memory.
Giving a ballpark figure however, going up one TL should only take about 30-60 minutes plus reboot time. Some admins prefer to be more on the conservative side and block a 2-3 hour downtime. Consideration should also be made to the amount of time it would take to restore, depending on the backup method selected.
8. Is it okay to run the update_all while people are online ?
Updating could affect running processes. As such, applications should be down and users offline as a general rule.
9. Where can I download new service packs or technology levels ?
TL and SP updates can be acquired from the FixCentral website located here :http://www-933.ibm.com/support/fixcentral/
10. Will product X at level Y.Z work with my new technology level ?
Some products may only be certified up to a certain operating system level while other products may require an update. The best thing to do would be to contact product X's support center. If it is an IBM product feel free to contact our support center and open a PMR requesting to speak to the product X team. Any 3rd party products should be cleared by their support before upgrading.
11. The 'oslevel -s' and/or 'oslevel -r' commands do not report what I expect after the udpate. How can I determine what is missing ?
If your 'oslevel' commands do not report correctly after your update_all you can add the "-l" flag to determine which filesets still need to be updated in order to complete your upgrade.
The syntax :
# oslevel -rl
# oslevel -sl
Example :
# oslevel -rl 6100-01
-or-
# oslevel -sl 6100-00-01-0748
The filesets listed will show an "Actual Level" heading (your current level) and a "Maintenance Level" heading (the level you need to be at to satisfy the TL/SP).
11a. Some filesets occasionally require multiple update_all operations.
There are cases where a second update_all operations need to be executed to pick up the full TL update. This is not defective behavior. Please also take note that this tip is not intended to resolve a "FAILED" status of your update_all. If you notice that your TL update was successful, but some filesets did not get updated and are on your media or in your download location, you may need to run the update_all a second time to pick them up.
12. What are other best practices with regards to keeping the AIX operating system updated?
IBM maintains a best practices site for service and support for Power Systems.
Visit http://www.ibm.com/support/customercare/sas/f/best for more information.
1. Is it okay to install my Technology Level in the “APPLIED” state ? What if I want to reject the TL update if there is a problem ?
With the introduction of Technology Levels and the “all or nothing” packaging format, these updates are bringing in on the upwards of 400+ fileset updates for each TL. Attempting to perform a “reject” process on so much code simply does not work well, and is not supported. Recommended back-out methods are discussed earlier in this document.
1a. Does the same hold true for Service Packs ?
The Service Pack updates are certainly much smaller groups of updates....typically numbering around 40-50 per update. While you certainly will have a better chance of successfully rejecting 40 filesets instead of 400, it would still be best to have one of the back-out methods mentioned earlier.
2. Why does my update_all have problems when I use an NFS mounted cdrom ?
When running an update_all over NFS, you create your own mount point for the cdrom drive. This does not allow it to recognize the fact that there are multiple volumes available that contain the correct requisite filesets. Multiple update_all operations may be needed on each volume when NFS mounting a cdrom drive. A better option may be to ‘bffcreate’ the contents of all CDs down to a directory, then NFS mount that directory.
3. The update_all failed. What now ?
Do not reboot. You can review the log to find out what failed and why. If you are comfortable and familiar with these situations you can correct the failures and re-update the filesets. If not, please call the helpdesk and open a PMR for assistance. Have the log available to email in if necessary.
4. I need to run my update today but I may not be able to reboot until next week. Is that a problem ?
Plans should be made to reboot as soon as the update is complete and checks have been made to ensure there were no failures. System files will have been replaced, but the corresponding kernel and library updates will not be loaded until boot time. You will likely encounter problems if you delay rebooting.
5. Is it recommended to reboot before issuing a TL upgrade ?
If this is possible, absolutely. There are systems out there that have not been rebooted in a year or more. Who is to say that something has not happened in that time that simply would not show up until a reboot. Rebooting the system first assures a good boot image, a stable system, and would isolate any problem that normally would not be caught until the post-update reboot as either a preexisting issue, or an issue directly related to the TL update itself.
6. Some say to use base AIX install media when updating the TL, others say the TL fix downloads or CDs should be used. Which is right ?
The recommendation is to use the TL fix downloads from FixCentral, or the TL CDs that can be ordered either online or from AIX SupportLine. You can also use the base AIX installation media, however without getting into a long answer, the recommendation is using the TL fix packages.
7. How long will the update_all take ?
This is a question that does not quite have a definite answer. The length of time required for the update_all depends on how many filesets are being updated as well as the available system resources such as processors and memory.
Giving a ballpark figure however, going up one TL should only take about 30-60 minutes plus reboot time. Some admins prefer to be more on the conservative side and block a 2-3 hour downtime. Consideration should also be made to the amount of time it would take to restore, depending on the backup method selected.
8. Is it okay to run the update_all while people are online ?
Updating could affect running processes. As such, applications should be down and users offline as a general rule.
9. Where can I download new service packs or technology levels ?
TL and SP updates can be acquired from the FixCentral website located here :http://www-933.ibm.com/support/fixcentral/
10. Will product X at level Y.Z work with my new technology level ?
Some products may only be certified up to a certain operating system level while other products may require an update. The best thing to do would be to contact product X's support center. If it is an IBM product feel free to contact our support center and open a PMR requesting to speak to the product X team. Any 3rd party products should be cleared by their support before upgrading.
11. The 'oslevel -s' and/or 'oslevel -r' commands do not report what I expect after the udpate. How can I determine what is missing ?
If your 'oslevel' commands do not report correctly after your update_all you can add the "-l" flag to determine which filesets still need to be updated in order to complete your upgrade.
The syntax :
# oslevel -rl
# oslevel -sl
Example :
# oslevel -rl 6100-01
-or-
# oslevel -sl 6100-00-01-0748
The filesets listed will show an "Actual Level" heading (your current level) and a "Maintenance Level" heading (the level you need to be at to satisfy the TL/SP).
11a. Some filesets occasionally require multiple update_all operations.
There are cases where a second update_all operations need to be executed to pick up the full TL update. This is not defective behavior. Please also take note that this tip is not intended to resolve a "FAILED" status of your update_all. If you notice that your TL update was successful, but some filesets did not get updated and are on your media or in your download location, you may need to run the update_all a second time to pick them up.
12. What are other best practices with regards to keeping the AIX operating system updated?
IBM maintains a best practices site for service and support for Power Systems.
Visit http://www.ibm.com/support/customercare/sas/f/best for more information.
No comments:
Post a Comment