• Spaces
  • Collections
  • Help
    • ×
     
     
    •  
    Server Automation Documentation

    Page tree

    The AIX Catalog tab defines a number of options including locations (such as the location of the source files and the repository), as well as filters and whether local copies of the files are created on the target server or downloaded directly during deployment.

    Note

    After a catalog option update, ensure you update the patch catalog for the catalog option update to take effect.

    The following sections provide more information about the AIX Catalog tab:

    Catalog Mode

    Select one of two options:

    • Source from IBM Network (Online Mode): Use this mode if the BMC Server Automation Application Server is installed on a server with Internet access. Credentials are not required.
    • Source from Disk Repository (Offline Mode): Use this mode in a secured environment where download occurs on a server, with Internet access, outside of the environment.

    Download option

    Select one of the two download options:

    • Fixget: Use this mode if you want to download the AIX patches from Fixget servers.

    • SUMA: Use this mode if you want to download the AIX patches from Fix Central servers using IBM Service Update Management Assistance (SUMA).

      Note

      Before you use the SUMA download option, ensure that:

      • The repository server is running AIX 6 TL 6 or a later version and that it is configured with ECC.
      • You are not using a proxy server to access internet connection. Proxy servers are not supported when creating a patch catalog with the SUMA download option.

    Repository Options

    Enter the following information:

    Field

    Description

    Payload Source Location (NSH path)

    Location where existing metadata and payload files are stored
    Metadata files stored in this location are copied to the catalog automatically. Payload files are not copied to the catalog.

    Repository Location (NSH path)

    NSH path to the location where the patch repository is located
    BMC recommends that this location have ample free space. Repositories typically contain many files, usually totaling gigabytes of data.
    (Offline Only)
    Either this location must be hosted on an AIX platform, or the downloader must be run on an AIX platform. If both are not on AIX platforms, you cannot create an AIX patch catalog.
    (Online Only)
    This location must be hosted on an AIX platform.
    Note: As you do not need to specify the URL of the patch files, the Payload Source Location (NSH path) option is dimmed.

    Note

    When specifying a host within an NSH path, you can use either the host name of the IP address (IPv4 or IPv6).

    Base Repository Location

    Enter the following information:

    Field

    Description

    Base Repository Location

    NSH path to the location where base-level payload files are stored. Base-level payload files are not copied to the repository location.

    Base Repository Network URL

    URL of the location where base-level metadata and payload files are stored. Specifying a value for this field is optional if you have selected the Copy to agent at staging option for the Network URL Type For Payload Deployment field.

    Notes:

    • If the patches that you require do not contain dependencies, you need not specify values for the Base Repository Location and Base Repository Network URL fields.
    • For more information about how to upgrade or install AIX patches using the Base Repository Location and the Base Repository Network URL options, see Creating a patch catalog for AIX in online mode.

    Note

    When specifying a host within an NSH path, you can use either the host name of the IP address (IPv4 or IPv6).

    Depot Object Options

    Enter the following information:

    Field

    Description

    Network URL Type For Payload Deployment

    • (Default) Copy to agent at staging: The BMC Server Automation Application Server copies patch payloads to a staging directory on the target server during the Deploy Job staging phase.
    • Agent mounts source for direct use at deployment (no local copy): A Deploy Job instructs the agent on a target server to either mount the device specified in the URL or deploy patch payloads directly to the agent.

    Network URL For Payload Deployment

    The value entered here depends on your selection in the Network URL Type for Payload Deployment box.

    • If you chose Copy to agent at staging, do not enter a value here. The value is autopopulated based on the repository location.
    • If you chose Agent mounts source for direct use at deployment (no local copy), enter the NFS-accessible path to the location of the payload.
      If you specify the host in this path as an IPv6 address, enclose the IPv6 address in square brackets.

    RBAC Policy

    A predefined ACL Policy
    Permissions defined by the ACL Policy are assigned to all Depot objects created in the catalog.

    OS Base Version

    Version of the operating system (OS) for which you want to source Technology Levels, Service Packs, and so on. The SUMA download option is only supported on AIX 6.1 and AIX 7.1.

    Filters

    Filters limit the amount of information brought into the catalog. For an offline catalog, re-create the filters defined in the configuration file used by the download utility. Available filter types are as follows:

    • By Update Level
    • By Fix Type
    • By Fix ID

    Only patches that match the combinations you define are added to the catalog. You can define filters either when the catalog is created or later, when you edit the catalog. To begin, click Add Filter and select from the following:

    Field

    Description

    By Update Level

    Select either Technology Level or Service Pack (which includes Concluding Service packs). The corresponding list is enabled. You can include more than one Technology Level or Service Pack in the patch catalog.
    Note:The list of available Technology Levels and Service Packs depends on a file downloaded from the vendor and stored on your server. To see the identifier list in the patch catalog, you must identify the location of the file in the AIX Updates List File box. For more information, see the AIX Updates List File field in Global configuration parameters list.

    By Fix Type

    Select one of the following three fix types for a particular update level — All Latest Fixes, All Security Fixes, or All Critical Fixes. Only one Fix Type filter can be included in the patch catalog.

    Note: The SUMA download option is only supported for the All Latest Fixes update level.

    OS Level

    Fixes of a particular type are downloaded for the Operating System Level defined here.

    By Fix ID

    Create an individual filter for a specific APAR or PTF. Multiple filters of this type are permitted in the patch catalog.

    • Type: Select either APAR or PTF. Multiple filters of this type are permitted in the patch catalog.
    • APAR Id/PTF Id: Enter the identifier for the APAR/PTF.
      If the patch catalog contains this type of filter, you can create an Include/Exclude list as part of the analysis options for a Patching Job based on this patch catalog.

    Note: The SUMA download option is only supported for PTF type of filters.

    © Copyright 2005-2024 BMC Software, Inc. Use of this site signifies your acceptance of BMC’s Terms of Use . BMC, the BMC logo, and other BMC marks are assets of BMC Software, Inc. These trademarks are registered and may be registered in the U.S. and in other countries.