Patch catalog - Solaris Catalog
The Solaris Catalog tab determines whether the catalog operates in Online or Offline Mode and defines a number of options.
Defined options include locations (such as location of the source files, the repository, the patchdiag.xref file) as well as filters and whether local copies of the files are created on the target server or downloaded directly during deployment.
- Before applying patches, make sure you are applying the correct patches. BMC Server Automation supports undo for patches, but this rolls back the patches without verification of the type of patches. Some types of patches, such as kernel patches, should not be undone.
- BMC Server Automation can apply patches to global and local zone setups where no lib or var is shared between the global and local zones. BMC Server Automation does not support patching on whole-root and sparse-root zones.
BL does not stop local zones before applying patches to a global zone. Its recommended to stop local zone before zone patching and users should try doing this using a separate deploy command.
- 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 Solaris Catalog tab:
Select one of two options:
- Source from Oracle (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.
If you selected Source from Oracle (Online Mode), enter the user name and password used to access the vendor website.
Enter the following information:
Payload Source Location (NSH Path)
(Offline only) Location where existing metadata and payload files are stored.
Payload Repository Location (NSH Path)
NSH path of the patch repository
Source patchdiag.xref File
(Offline/Oracle Solaris only) (read only) Depot location of the patchdiag.xref file downloaded from the Oracle website
Metadata Corrections File
(Oracle Solaris Only) Depot location of the file used to correct errors found in the patchdiag.xref file that you added to the patch repository
Single User Mode and Reboot Override File
Depot location of the file used to override single user mode and reboot settings for a particular patch
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:
Network URL type for payload deployment
Network URL for Payload Deployment
The value entered here depends on your selection in the Network URL type for payload deployment box.
Select a predefined ACL policy. Permissions defined by the ACL policy are assigned to all depot objects created in the catalog.
Download patches from Oracle
(Online Mode Only) To download the payload at the same time as the patchdiag.xref file, select the Download patches from Oracle check box.
Tip: You can also download the payload by right-clicking the catalog and selecting Download.
Filters limit the amount of information brought into the catalog. A filter defines:
- a specific combination of operating system and architecture
- a list of Patch IDs
- a specific or custom Oracle Solaris cluster
There is no upper limit to the number of filter combinations you can make but there must be at least one. Only clusters and patches that match the combinations you define are added to the catalog.
In Offline Mode, recreate the filters defined in the configuration file used by the download utility.
You can define filters either when the catalog is created or later, when you edit the catalog. Depending on the filter option you selected, provide specific details for the filter such as an operating system-architecture combination, a specific patch identifier, or a cluster name, and then click OK. To begin, click Add Filter and select one of the following options:
Identify a particular operating system and architecture.
Create a list of specific patch identifiers.
Identify a specific Oracle Solaris cluster. If the catalog works in offline mode, you can enter a custom, Oracle Solaris cluster.
- If you create an online Oracle Solaris Catalog with filter type as cluster, the download of patches starts automatically and the Download from Vendor check box is disabled.
- In 2011, Oracle renamed the term 'Solaris Patch Cluster' to 'patchset'.