Patching AIX
Concert supports AIX iFix detection as part of the IBM Power assessment. This capability ensures accurate vulnerability reporting by identifying when an AIX interim fix (iFix) is already installed on the host.
AIX iFix detection during IBM Power assessments
- If an AIX iFix required to remediate a CVE is already installed, the CVE is excluded from the assessment results.
- If the iFix is missing, the CVE continues to appear as an open exposure and a remediation action is generated for the affected AIX host.
About AIX iFix patching
- Some iFixes require earlier iFixes (base iFix) to be installed first.
- A later iFix cannot be applied without selecting its required prerequisites.
- Dependency sequencing
- Validation of prerequisite iFix selections
- Parallel installation of independent fixes
- Real-time status tracking during remediation
| Status | Meaning |
|---|---|
| Completed | All selected iFixes installed successfully. |
| Partially processed | At least one iFix installed successfully and one or more dependent iFixes failed. Dependent iFixes are skipped and marked as Ignored. |
| Failed | All iFixes failed or the action was aborted. |
Review AIX iFix patches
When missing AIX iFixes are detected, Concert generates a patch remediation action for the affected AIX VM.
- Go to .
- Select the System or Stand-alone VM for which you want to see the action.
- Click Actions.
- Click Review and approve.
- Open the iFixes tab.
Figure 1. iFixes
This panel lists:- Available AIX iFixes
- Associated file sets
- Whether a reboot is required
- Clear the selection for any iFixes you do not want to apply.
By default, all iFixes are selected for both AIX and VIOS.
- Click Save.
- Click Approve.
- Provide a schedule and confirm by clicking Approve in the approval window.
After approval, Concert installs the selected iFixes sequentially. Each iFix addresses specific CVEs and behaves similarly to applying a targeted package fix rather than performing a full version update.
Apply AIX iFix patches
- Downloads the required iFix packages from configured sources
- Validates package checksums
- Applies the iFixes in dependency order
- Updates the system and records remediation status
If any iFix requires a system reboot, this is indicated in the action details. Review the reboot requirement before approval to plan maintenance windows appropriately.
Partial success handling
- All dependent iFixes are skipped.
- Skipped iFixes are marked as Ignored.
- Successfully applied iFixes remain installed.
- The overall action status is set to Partially processed.
This behavior prevents dependency-chain errors and ensures the system remains in a valid state.