Frequently asked questions

The questions and answers in this section can help you to better understand BigFix Patch for AIX®.

The Manage Download Plug-ins dashboard is not reflecting any data. What do I do?
Here are some steps you can do to troubleshoot the issue:
  • Gather the latest Patching Support site.
  • Activate the Download Plug-in Versions analysis, available from the Patching Support site.
  • Clear the BigFix console cache.
Why would a patch complete successfully, but ultimately fail?

Under specific circumstances, a patch is successfully applied but the relevance conditions indicate that it is still needed in your deployment. Check to see if there are any special circumstances that are associated with the patch, or contact HCL Software Support.

If a patch fails to install, what should I do?

Ensure that you applied the patch to the correct computers or manually download the patch.

Can I update a single fileset instead of performing full technology level or service pack updates?

Updates are developed and tested as bundles, and updating individual filesets might cause unexpected results. However, if you would still like to update individual filesets, you can do so by downloading the .bff file that you want to deploy and using the fileset option of the AIX Deployment Wizard to generate the necessary Fixlet.

What files can I used in the AIX Deployment Wizard to deploy fileset updates and program temporary fixes (PTFs)?
You can use .bff files to create Fixlets for fileset updates or PTFs. Some AIX fixes might have a different format. For example, the fix packs for SDK, Java Technology Edition uses the .sdk format. To allow the AIX Deployment Wizard to use the fix, rename its extension to .bff file. For example, rename Java6.sdk to Java6.sdk.6.0.0.495.bff.
Why did the update of my AIX system fail?

There are several reasons why an update can fail. The best place to start investigating is with the log files saved in /var/adm/ras.

Some of the more common reasons for failed updates are as follow:

Problem: Insufficient free space in the BES Data Directory (typically /var/opt/BESClient/__Data/)

Solution: Free space or expand the current partition using the chfs -a command

Problem: Warning that filesets are locked or in EFIXLOCKED state

Solution: Filesets can be locked as the result of installed Interim Fixes. Interim Fixes can be viewed either by using the AIX Interim Fixes analysis or by running the command emgr -l. It is recommended that all Interim Fixes be removed prior to deploying updates. Interim Fixes can be removed by using the AIX Interim Fix Management Wizard.

Problem: Error: Installation failed due to BUILDDATE requisite failure

Solution: If the build date of an installed fileset is more recent than the build date of the fileset being installed a warning is displayed and the entire update action might fail. To correct this, upgrade to a more recent technology level or service pack.

Why do NFS actions set the nfs_use_reserved_ports and portchecker values to 1?

Some Linux operating systems use reserved ports that are less than 1024. These settings are temporarily changed to a value of 1 to avoid failures in connecting to remote servers that use these ports.

What are the requirements for an AIX repository?

NFS installations use the Table of Contents (.toc) file in the repository to match packages with their corresponding file names. Use the Generate Fileset Repository TOC File task to generate a current .toc file.

Are there tools available to help build a repository?
Yes. The AIX Download Cacher provides two methods for building a repository:
--no-archive
Use this parameter to download files, without creating an archive .aix file, to the directory specified by the --dir parameter.
--repo <dir>
Use this parameter to save a copy of individual downloaded files to the repository specified by the --repo parameter.
Note: If the --repo parameter is used with the --no-archive parameter, the fix pack files are either:
  • Copied from the repo directory to the output directory, which is specified by --dir parameter.
  • Downloaded from the internet and saved to both the output directory and the repo directory.
Will any files that are missing from the AIX repository be automatically added during an NFS installation?

No. For NFS installation actions, all required files must exist in the specified NFS location.

How do I verify if the download plug-in was registered correctly?

Run a Fixlet with an action task to verify if the download plug-in is registered correctly. Verify that the patch download is successful. Otherwise, you might need to unregister the download plug-in and register it again.

How do I register a download plug-in? Do I use the register download plug-in task or the Manage Download Plug-in dashboard?
To register a download plug-in, you must use the Manage Download Plug-in dashboard in the Patching Support site. Existing register download plug-in tasks are being deprecated. To learn more about plug-in registration, see Registering the AIX download plug-in.
Note: You must also use the Manage Download Plug-in dashboard to unregister, configure, and upgrade download plug-ins. The existing unregister and edit download plug-in tasks are being deprecated. .
I was expecting the password to be obfuscated, but it is still in clear text. Why is that?

Check if your download plug-in version is earlier than 2.0. If so, you are still using an old version of the download plug-in that stores credentials in clear text. To encrypt credentials, upgrade your download plug-in to version 2.0 or later from the Manage Download plug-ins dashboard in the Patching Support site.

Where can I find the AIX Patching log files?
Here is a list of the log files and their locations:
  • AIX Download Cacher: Default log directory of the BigFix client on the target system.
  • AIX Download Plug-in: AIXProtocol/logs directory of the default DownloadPlugin directory on the BigFix server (For example: C:\Program Files (x86)\BigFix Enterprise\BES Server\DownloadPlugins\AIXProtocol\logs).
  • Installation Logs: /var/adm/ras/ on the target system. Logs are unique for each operating system level.
I want to use the AIX Download Cacher to download packages for a fix pack, what must I specify in the command line?
You must enter the following command: AIXDownloadCacher.exe --dir <path to output directory> --fixid <Fix Pack ID> [optional parameters]
The <Fix Pack ID> can either be the AIX Fix Pack ID or the Interim Fix APAR ID of the package that is to be downloaded. For example, 6100-08-07-1524 or IZ93611.
Note: Ensure that the AIX Fix Pack ID contains the operating system level, technology level, service pack level, and build number. If at least one information is missing, the utility returns an invalid patch identifier error.
When should I create a repository for a single fix pack?

Create a repository for a single fix pack when you are using the technology level and service pack updates using the NFS actions. Issues might occur when the installer automatically attempts to install the latest version of any fileset that it finds in the source directory. For example, if you want to update a system to a specific technology level and service pack level, you must store it in its own isolated location to ensure that is not overridden by later versions.

What are the requirements for using an existing repository of filesets that is accessible on NFS mount?

All fix pack files must be in the NFS directory with a current .toc file. Each fix pack must be stored in its own dedicated share space.

How are the fix packs installed when I deploy technology level or service pack updates?

Fix packs are installed in an applied state that can later be rejected, if needed. Applied filesets must be committed after they are verified. They can be committed by using the Commit Applied Filesets task. Technology level updates cannot be rejected; attempting to do so might produce unexpected results.

Why did the OS level of my new NIM master change after I installed the NIM filesets?
The OS level is determined by comparing a list of installed filesets with a list of known APARs. When you install new filesets, the target system might become applicable to APARs that were not previously applicable. The OS level is changed to reflect these newly-applicable APARs.
What's the difference between installing the NIM master filesets from the Install NIM Filesets and NIM Master Configuration tabs?
There is no difference. The installation of the NIM master filesets is added to the NIM Master Configuration tab to simplify and consolidate the process of setting up a NIM master.
What happens if I previously installed the master filesets then chooses to install the master filesets during the manual NIM Master configuration?
The second installation attempt detects that filesets are already installed and exits without doing anything. However, if the second installation has a later version of the filesets, then an update is performed.
Can I configure a NIM master outside the dashboard and then configure the client from the dashboard?
Yes, this is possible. If you have preexisting NIM environments, you generate NIM content to manage existing clients or add new clients.
What is an IBM ID? Do I need one?
An IBM ID is a free, single ID and password that you can use across the ibm.com domain. Updates to operating systems and other software products are entitled only to customers under an applicable warranty or support agreement. To this end, an IBM ID is required for the AIX download plug-in to successfully download updates.
What is an IBM Customer Number (ICN)?
ICNs are unique numbers that are assigned to customer agreements with IBM, including software maintenance agreements.
Why do I need to link my IBM ID to an IBM Customer Number (ICN)?
For a list of benefits of linking your ICNs and your IBM ID, see the announcement at http://www-01.ibm.com/support/icn/.
Where can I find the log for the preview deployment feature of the AIX Advanced Deployment Wizard?
You can find the log file with this format preview_<os_level>-<technology_level>-<service_pack>-<build_date> in the directory /var/opt/BESClient/__BESData/__MLPkgInstall/PreviewLog. A new log file is generated for each fix pack ID, hence the existing log file gets overwritten.
Where can I find the log for the fileset inventory?
The log file for the fileset inventory action is in the directory /var/opt/BESClient/__BESData/__AIXInventory.
What are the commands used in breaking mirrors?
These are the commands used for breaking mirrors: 
unmirrorvg rootvg $mirrorDisk
reducevg rootvg $mirrorDisk
chpv -c $mirrorDisk
chdev -l $mirrorDisk -a pv=clear
bootlist -m normal $bootDisk
What commands are executed by the Re-mirror disk back to rootvg task?
These are the commands used for re-mirrong disks: 
chpv
chdev
extendvg
mirrorvg
bosboot
bootlist
Where can I find the log files for troubleshooting mirror management?
Check the following logs when troubleshooting issues with managing mirrors:
For breaking mirrors:
/var/adm/ras/altDiskNewDeploy.log
For re-mirroring disks:
/var/adm/ras/reMirror.log
Are there any logs that shows the results of the reboot command for operating systems in an alternate disk environment?
Yes, you can use the following logs:
  • /var/adm/ras/KZCopyAltDiskBESDATA.log
  • /var/adm/ras/SZCopyAltDiskBESDATA.log
What are the alternate disk related logs that I can use for troubleshooting?
The following log files can be found in the client folder in the directory /var/adm/ras/.
altDiskNewDeploy.log
Lists the results of deploying updates to new or existing alternate disk.
altDiskCreateClone.log
Lists the results of a new alternate disk creation.
What are the multibos related logs that I can use for troubleshooting?
When problems occur, you can determine what went wrong by viewing messages in the appropriate log files that provide information about how to correct errors.

The following log files can be found in the client folder in the directory /var/adm/ras/.

MultibosExpress.log
Lists the results of the Multibos Express task, which creates a new standby BOS and deploys patches, that is created from the AIX Advanced Deployment Wizard.
MultibosCreateClone.log
Lists the results of the standby BOS creation action that is created from the AIX Advanced Deployment Wizard.
MultibosFixPackDeploy.log
Lists the results of the standby BOS update action that is created from the AIX Advanced Deployment Wizard.
MultibosExpress_emgr.log
Lists the interim fixes that are to be removed on the standby BOS before the updates are installed using the express task.
MultibosFixPackDeploy_emgr.log
Lists the interim fixes that are to be removed on the standby BOS before the updates are installed using the BOS update action.
MultibosDeleteClone.log
Lists the results of the standby BOS removal action that is created from the AIX Advanced Deployment Wizard.
SZCopyMultibosBESDATA.log
Lists the logging information about the AIX startup script for the multibos reboot.
KZCopyMultibosBESDATA.log
Lists the logging information about the AIX shutdown script for the multibos reboot.
I want to upgrade my endpoints using multibos, what is the suggested way to do this in BigFix Patch?
  1. Use the Determine OS level Fixlet (ID #6) to check the current technology level or service pack level of the endpoint.
  2. Use the AIX Advanced Deployment Wizard to generate individual Fixlets for creating a standby BOS and for deploying patches to a standby BOS instance. This method provides you the flexibility to deploy the actions separately. You can also run a preview for each of the individual task to check if everything runs smoothly. To find more information about these options in the wizard, see Standby BOS creation and Patch deployment.

    Alternatively, you can use the express task in the AIX Advanced Deployment Wizard to complete both operations from a single action. For more information, see Creating a new BOS and deploying patches.

  3. Reboot to the standby BOS.
    Note: Before rebooting, you must run the Deploy AIX StartUp/Shutdown script for multibos reboot task (ID #92).

    You can use the Restart Computer task (ID #62) to complete this action.

    Alternatively, you can use the AIX Advanced Deployment Wizard to create a task for this step. For more information, see Updating the rootvg boot logical volume.

  4. Check the OS level again to confirm the upgrade.
Can I preview the creation of the standby BOS instance?
Yes, the AIX Advanced Deployment Wizard provides an option to preview the operation first.
  1. From the AIX Advanced Deployment Wizard, click the Multibos Tasks tab.
  2. Click Multibos Individual Task Operations to expand the individual task selection options pane, and select Create a New BOS.
  3. Set the Run a preview option to yes.
Can I run a preview of the patch deployment on a standby BOS?
Yes, a preview option is available from the AIX Advanced Deployment Wizard. For more information, see Deploying technology levels and service packs to a standby BOS.
I want to upgrade the technology level on my endpoint using multibos, however I do not have a standby BOS yet. How do I create the standby BOS?
There are two methods to create a standby BOS from the AIX Advanced Deployment Wizard. You can either use any of the following methods:
  • Create a standby BOS without deploying any patches, which provides you options to preview the creation operation. For more information, see Creating a new BOS.
  • Create a standby BOS and then deploy patches to that BOS instance. For more information, see Creating a new BOS and deploying patches.
Can I automatically reboot to the standby BOS after creation?
Yes, this is possible. When creating a BOS from the Multibos Individual Task Operations of the AIX Advanced Deployment Wizard, you can set to reboot to the newly created standby BOS.
I need to back out of the update because the update procedure failed. What do I do?
To bring back the older AIX version before the update, set and verify the boot list back to the previous boot logical volume and boot to the original BOS instance.
  1. From the AIX Advanced Deployment Wizard, click the Multibos Tasks tab.
  2. Click Multibos Individual Task Operations and select Update Boot Logical Volume.
  3. Set the boot list and verify that the boot logical volume is set to the previous BOS instance.
I created a Multibos Express Task to include a reboot of the standby BOS and deployed it to the endpoints, however the task reported back as "failed" after rebooting. What do I do?
To troubleshoot, complete the following steps:
  1. Ensure that every step of the task is completed successfully.
  2. Ensure that the MultibosExpress.log file, which can be found in the endpoint's directory /var/adm/ras/, does not contain any error.
    Note: Before running any multibos operation, ensure that relevant interim fixes are installed on the endpoints. Otherwise, the multibos task might fail.
  3. Check the SZCopyMultibosBESDATA.log file for any errors.
    An APAR is reported on failures to mount the standby BOS. If you see a mounting failure in the log, similar to the following error, install the interim fix for the APAR.
    mount: 0506-324 Cannot mount /dev/hd4 on /bos_inst: 
The requested resource is busy.
multibos: 0645-007 ATTENTION: mount_dev() returned an unexpected result.
multibos: 0565-026 Error mounting file systems.
The TL and SP installation takes too long to complete. Is there a way to improve the performance?
BigFix sets 2% as the default CPU usage limit. If serious performance lag is identified, consider increasing the CPU usage limit by using the task BES Client Setting: CPU Usage on the BES Support site.
What is the possible cause for a patch download process to not complete for BigFix Red Hat servers?
The download queue size for the BigFix Red Hat server might be larger than 1024 KB, which prevents the download process from completing. The Linux setting 'Max file open limit'; is not accepted by the BigFix server, which limits the download queue to 1024 KB. You must update the BigFix server to version 9.2.7.54 or 9.5.0.51.
Why are there duplicate endpoints appearing in the console after deploying a multibos or alternate disk task?
The duplicate endpoints might appear in the console because the shutdown scripts are not running. Double-check if the following Fixlets were deployed:
  • Fixlet 84: Deploy AIX Startup/Shutdown script for alt disk reboot
  • Fixlet 92: Deploy AIX Startup/Shutdown script for multibos reboot
What is the turnaround time for BigFix patch content for AIX?
BigFix Patch for AIX content are made available five working days after an IBM advisory of an update or fix.
Is firmware upgrade for Power machines supported by BigFix?
BigFix supports firmware updates only on endpoints that are not managed by IBM Hardware Management Console (HMC). If a system is managed by HMC, you must apply the firmware through the management console.
You can use the AIX Deployment Wizard to deploy packages for firmware updates, on endpoints that are not managed by HMC.