This file is then uploaded into the patch application in preparation for running an assessment. To specify your system configuration, select the link "upload new system information" on the Run a patch assessment page. Select the system to assess and the assessment profile to use, then click "Display candidate patches".
Shortly, a patch assessment results page is displayed. The result is a list of patch related issues, presented depending on the assessment profile. Patches or patch bundles that address an identified issue are listed as recommended. Some issues may not have a recommendation. To generate a more detailed, text-only assessment report, ideal for archiving or emailing, use the "Show detailed assessment report" link near the top of the results page.
This report captures system characteristics, the assessment profile, which patches or bundles each chosen analyzer recommends, and a summary with detailed information about the recommended patches.
Review all recommended items. Take special care to review any recommended patches that have a warning or special installation instructions.
From the assessment results page, deselect any recommended item that is not appropriate for your system. Press the "Add to My Patch List" button to add all selected items to your selected patch list. Press the "Download Selected" button to take delivery of the patches.
From the download patches page, you may select from a variety of formats including tar, zip, gzip. The assessment profile allows you to customize the behavior of the patch assessment tool. Adjust the profile to indicate which types of issue to identify, which patch sets to validate against, and how risk averse your patch strategy is. Identifies patches that contain critical fixes but are not installed. Choose among these options, depending on your patch strategy:.
Quality pack patch bundles QPKs contain stable defect-fix patches for the proactive maintenance of HPE servers and workstations. Patch sets identify the appropriate patches for hardware, operating system, and software applications. They are updated weekly by HPE, so contain the current, best known configurations.
Patch sets are maintained for restrictive and conservative patch strategies, and can be used to determine if you are properly configured to run the applications installed on your system. If you specify the "innovative" patch strategy, the appropriate "conservative" patch set is used. Use the application patch set selector to select from the available application patch sets.
Be sure to browse within all categories to identify all appropriate sets. For each set, the patch assessment tool verifies that all patches or their successors in the patch set, appropriate for your patching strategy, are installed.
The output of a patch assessment contains a list of patch issues identified for the system being analyzed. Which issues are displayed is controlled by the configuration profile as described above. When possible, for each patch issue shown, a recommendation is made specifying the appropriate patch or patch bundle which resolves the issue. The recommended item will usually be a newer patch that contains an appropriate defect fix.
Which patch is recommended is determined by the patching strategy specified in the assessment profile. Frequently, a single recommendation resolves several related issues. This is especially likely if installing the latest quality pack is recommended. In such a case, all issues resolved by the recommended patch or patch bundle are listed immediately below it.
The assessment profile controls which analyzers are used during the patch assessment. For each issue displayed, the name of the analyzer which identified the issue is included. A more detailed patch assessment report, in text format only, can be generated via a link on the assessment results page. This report provides details about the system, the assessment profile, and each analyzer's recommendations, and is ideal for archiving or emailing. You have specified "latest quality pack patch bundle" in the assessment profile and quality pack patch bundle P1 is not installed on your system.
The recommendation will be P1. Quality pack patch bundle P1, which is not yet installed on your system but is recommended for installation, contains patch P2 with a warning, either critical or non-critical. The recommendation will be a successor of patch P2 which does not have a warning. If the patch strategy specified in the assessment profile is "innovative", the recommendation will be the "most recent" patch on the chain. Otherwise, it will be the "recommended" patch on the chain.
If no recommendation is made, be sure to review the details of the patch in question to determine if the warning will affect your system once the quality pack patch bundle is installed. Take appropriate action. Patch P1 has been identified as a security patch appropriate for your system; it is not currently installed. In this case, a patch recommendation will always be made. If all patches which resolve this issue have warnings, the best patch with warnings is recommended.
In this situation, be sure to review the warnings against the recommended patch and decide if installing the patch is appropriate. Patch P1 is currently installed on your system and that patch has a warning, either critical or non-critical. The recommendation will be a successor of patch P1 which does not have a warning. If no recommendation is made, be sure to review the details of the patch in question to determine if the warning will affect your system. You have specified "critical fixes" in the assessment profile.
Patch P1 was identified to contain a critical fix. However, this patch is not installed on your system. You have specified "updates for the patches already installed" in the assessment profile.
Installed patch P1 has been replaced and the best replacement, according to your patch strategy is P2. The recommendation will be P2. You have specified "all applicable patches" in the assessment profile and patch P1 is not installed on your system. You have specified in the assessment profile that patch P1 should be installed on this system. However, P1 is not installed.
However, P1 is not applicable to this system. This results because P1 patches filesets which are not installed on this system. There will be no recommendation. You have specified in the assessment profile that patch P1 or one of P1's successors should be installed on this system.
However, neither P1 nor any of its successors is installed. However, the patch assessment tool does not recognize this patch. However, P1 is not installed and is not applicable to this system.
This results because P1 patches filesets which are not currently installed on this system. You have specified patch set S1 in your assessment profile. Patch P1 is included in this set. However, neither P1 nor any of its successors is installed on your system.
The recommended patch will be P1. Additionally, you have specified patch strategy S2. It was not possible to locate an appropriate patch set for your system, which is running operating system OS1. It was not possible to locate an appropriate patch set for your system, which is a model M1 running operating system OS1. This results because this system does not have particular software installed which is required by the patch set.
The system configuration file indicates that patch P1 is installed on your system. If this patch is a special early release patch obtained from HP, be sure to discard any recommended patches which may interfere with this patch. Your system has patch P1 installed, and patch P1 lists patch P2 as a dependency. However, P2 is not installed. This may result for several reasons:. If all patches which resolve this issue have warnings, the best patch with warnings will be recommended.
If this issue arises because patch P2 is not applicable to your system, the software distributor tool 'swinstall' may not allow you to install the recommendation.
Frequently, a recommended patch requires another patch as a dependency. If the dependent patch is not already installed and it does not resolve other patch issues, it will be listed in the additional dependencies table. Occasionally, the only patch that satisfies a dependency will have a warning. In this case, review the warning prior to adding the patch to the download list. If you decide not to take delivery of the dependent patch, you will have to deselect the recommended patch as well.
When two issues are emitted during a patch assessment that involve related patches one is a successor of the other , it is possible that their recommendations may conflict. In this case, the most recent of the recommendations will be used to resolve both issues. Frequently the patch assessment tool will identify issues with your system for which no recommendation is made. The recommendations made by the system depend on your specified patching strategy. Frequently, there is no patch with sufficient rating for your specified strategy that resolves the issue.
In this situation, you should review the issue and make an appropriate decision. Effective November 28th, , HP-UX patches may include additional text called Advisory Notices that will be used to call attention to defects with certain characteristics that customers may want to search the HPE Support Center database for. There are two forms of advisories:. HP-UX 11i version 2 B. During installation, it will automatically determine which software to load. Note: To avoid kernel build failures, please read the information in the following two boxes prior to updating to HP-UX 11i v2 September Customers with an older release of HP-UX 11i v2 who have an HPE support contract should have received a letter with instructions on how to request the HP-UX 11i v2 September media as part of their support service.
See the "Important Note" on the previous page for more details. If you have a version of HP-UX 11i v2 released earlier than September , you will need to first update your system prior to doing a patch assessment. If version B. If you attempt to download one of these required patches individually from the HPE Support Center, you will be given the following warning:. See the "Obtaining the HP-UX 11i v2 September media" section for details on obtaining media if needed, and also read the important notes in the two text boxes contained in this document prior to updating to HP-UX 11i v2 September The patch redirected you to this web page.
There should be no further need to load this particular patch once HP-UX 11i v2 September or later is loaded. Patch sets are groups of patches that should be installed to support common HPE products and sub-systems. Not all patch sets are available for all versions of HP-UX. If there is no version of a specific patch set for your version of HP-UX, it is most likely because no patch set is needed to support the product or subsystem on that HP-UX version.
While patch sets are added and modified on a regular basis, the tables in the sections below show the current patch sets available. The major difference in JFS 3.
AdvanceJFS 3. HPE OpenView Service Assurance allows you to collect, consolidate, correlate, associate, filter and report on all the elements in your infrastructure, generating real-time alert, event and alarm information so you can proactively manage - from end-to-end - all the critical elements of your service environment.
Last updated September Enterprise Information Library. Education and training. Sign up for email updates. Get support. All Files. These bundles are released regularly and provide the most reliable and thoroughly tested set of patches. All forum topics Previous Topic Next Topic. Valued Contributor. I have a codeword. I was just worried about the differences in versions. V1 June and V2 June ? Honored Contributor. Kwahae, According to this document it should work just fine, since we are using the same bundle for HP-UX Work hard when the need comes out.
Acclaimed Contributor. While it may have the same compiler bits, it is packaged differently. No, you can't do that. The importance is v1 vs v2, not the dates. Thanks Denis, I thought so. Esteemed Contributor.
Codewords are not specific to a machine. Codewords are specific to a license agreement.
0コメント