Page tree
Skip to end of metadata
Go to start of metadata

The Red Hat 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 information about the Red Hat Catalog tab: 

Catalog Mode

Select one of two options:

  • Source from Red Hat Network (Online Mode): Use this mode if the BMC Server Automation Application Server is installed on a server with Internet access.
  • 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.

Red Hat Network Credentials

If you selected Source from Red Hat Network (Online Mode) enter the user name and password supplied by the vendor and required to access the Red Hat Network website.

Repository Options

Enter the following information:

Field

Description

Payload Source Location (NSH path)

(Offline Only) location of existing metadata and payload files
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 of the patch repository
This location must be on a Linux platform (Red Hat, SUSE or Oracle Enterprise Linux). BMC recommends that this location have ample free space. Repositories typically contain many files, usually totaling gigabytes of data.
Note: (Online Mode) You can copy pre-existing Errata and RPMs manually into this directory. BMC Server Automation does not download duplicate files from the Red Hat Network site.

Notes

  • The Payload Source Location and the Repository Location can point to the same directory.
  • 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: mount the device specified in the URl and deploy patch payloads directly to the agent. The Deploy Job does not copy patch payloads to a staging area on the agent, so the job does not create any local copies of the patches on target servers.

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

Browse to and select a predefined ACL Policy. Permissions defined by the ACL Policy are assigned to all Depot objects created in the catalog.

Filters

Filters limit the amount of information brought into the catalog.There is no upper limit to the number of filter combinations you can make but there must be at least one. Only RPMs and Errata that match the combinations you define (and their dependent RPMs and Errata) are added to the catalog. Note that you cannot create multiple filters for the same combination of operating system and architecture.

Available types of filters are:

  • Errata Type
  • Errata Advisory

  • Update Level

 Click here to view limitations on filters that can be created for RHEL 7

  • When patching on RHEL7, you cannot create update-level or channel-level filters. You must use errata-level filters instead.
  • if your repository server runs on RHEL 5 or earlier, you can only download packages to your repository and not the errata metadata. Note that although the errata metadata is not downloaded, you can still create errata ID and errata-type filters in the online or offline 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:

Online Mode (Red Hat Network is selected automatically)

Field

Description

Channel

Select the channel from the list provided. The operating system (OS) and architecture are supplied automatically in read-only boxes. If you want to download child channels, select Offline Mode, and use the Patch Downloader utility for Red Hat Enterprise Linux, as described in Downloading child channels using the Patch Downloader utility.

By Errata Type

For Errata Type, choose:

  • Bug Fix Advisory
  • Product Enhancement Advisory
  • Security Advisory

    For Errata Severity, choose:
  • Critical
  • Important
  • Moderate
  • Low

By Errata Advisory

Create an Include List by entering the names of individual Errata Advisories.

By Update Level

Select the Update Level from the list provided.


Offline Mode (Disk Repository is selected automatically)

In Offline Mode, you must create the filters definitions in the configuration file that is used by the patch downloader utility. 

Field

Description

Enable Update Level

Select an Update Level that you previously downloaded.

Update Level

Select an Update Level identifier; only one can be included for each filter.