The software on a BMC Discovery appliance, whether a downloaded virtual appliance, or a kickstarted hardware appliance, consists of the operating system (OS) and the BMC Discovery application software. You can upgrade the OS using an OS upgrade (OSU) package. When the BMC Discovery application software is upgraded, that upgrade includes the latest OS upgrade at the time of its release.
The OSU documentation contains the following topics:
The replacement of earlier OS versions with CentOS 7 ensures continued support for the appliance OS during its lifetime, and provides support for newer hardware where you choose to install on hardware. It also provides SMB 2 support, and the ability to run Apache 2.4.
CentOS is an enterprise-class Linux platform that is derived from and aims to be functionally compatible with its upstream source, RHEL. This compatibility enables BMC to perform the same CentOS testing against the Red Hat 6 and 7 STIGs.
When applying OS upgrades to BMC Discovery 11.3, ensure that you download and apply the correct CentOS operating system upgrade.
The upgrade to BMC Discovery 11.2 replaces Red Hat Enterprise Linux 6 with CentOS 6. CentOS is an enterprise-class Linux platform which is derived from, and aims to be functionally compatible with its upstream source, Red Hat Enterprise Linux (RHEL).
As CentOS is derived from, and aims to be functionally compatible with its upstream source, Red Hat Enterprise Linux, BMC performs the same testing against the Red Hat 6 STIGs.
When applying OS upgrades to BMC Discovery 11.2, ensure that you download and apply the Latest CentOS 6 operating system upgrade.
Red Hat release bug fixes and security updates to Red Hat Enterprise Linux (RHEL) frequently, and CentOS subsequently incorporates these updates. Each month BMC creates OS upgrades containing the subset of RHEL and CentOS packages applicable to BMC Discovery.
It is anticipated that most customers will not consider it necessary to upgrade the OS on their appliance every time BMC releases an OS upgrade package, however each customer needs to determine their own patching and upgrade policy. In order to assist with this assessment, BMC will highlight any patches to serious defects or security vulnerabilities that affect BMC Discovery when announcing its availability to customers with a support contract.
OS upgrades are cumulative, that is, when you install the latest upgrade package, all packages are upgraded to the current version. You do not need to apply any previous upgrade before applying the latest.
The preferred method of upgrading the operating system, in standalone or clustered systems, is to use the upgrade UI. If you do choose to use the script described in upgrading the operating system, only the local machine is updated (not the cluster) and it is not rebooted automatically.
Based on the RHEL versions that support BMC Discovery, the following OS upgrades are available:
To learn about the content of the latest RHEL 6 and 5 OS upgrades, packages which have been updated since the previous OS upgrade, and the latest OS upgrade file names, see the following documentation:
If you want to learn about the content of the previous OS upgrades, from the Previous operating system upgrades page, select the link for the corresponding period.
From the September 2017 OS upgrade, equivalent CentOS packages are included in the RHEL OS upgrade. This ensures that when BMC Discovery systems which have had OS upgrades applied are upgraded to a release running on CentOS, parked packages are available to ensure that the upgrade does not revert the OSU level current at the time of the product release.
Updating Java in BMC Discovery has only been possible when the product itself is upgraded. From in version 10.2, the OS upgrade process manages Java packages, providing a simple means of maintaining a patched, up to date version. As part of this capability, Java packages are included in OSUs from January 2015 onwards.
Before BMC Discovery 10.2, updated Java packages are installed, but they are not active, they are “parked”. The term parked means that the package is installed, but none of the environment variables ($JAVA_HOME), symbolic links, and so forth are updated, so the new version installed is not used.
You can see Java packages in the package list for each OSU from January 2015 onwards, and in the OS Upgrade logs you will see lines in the output similar to the following: