1. Home
  2. How to tell what BCM version are you running?

How to tell what BCM version are you running?

There are several ways to identify the BCM version your cluster is running. The following are the two most common methods:

Using the Package Manager:

For RPM-based OS (i.e. RHEL, Rocky Linux, SLES):

# rpm -qi cmdaemon

For DEB-based OS (i.e. Ubuntu):

# dpkg-query -l cmdaemon

Using cmsh:

# cmsh -c "main; versioninfo"

These methods will show which release BCM version X is running. For example, the following output indicates that BCM is currently running version 10.0-156713:

root@bright10:~# cmsh -c "main; versioninfo"
Version Information
------------------------ ----------------------------------------------------
Cluster Manager 10.0
CMDaemon 3.0
CMDaemon Build Index 156713
CMDaemon Build Hash 14e56b67c0
Database Version 36293

However, the provided output displays the release number of the package but does not include the minor release number. To identify the specific minor release your cluster is running, you can use the tool ‘cm-package-release-info.’

For example, to determine the minor release version of cmdaemon that the cluster is running, execute the following command on the headnode:

root@bright10:~# cm-package-release-info -f cmdaemon
Name Version Release(s)
-------- --------- ------------
cmdaemon 156713 10.23.11

We can see from the output that the cluster is running cmdaemon release 10.23.11.

This tool works with any cm-related package. For example, you can check what version of cluster-tools you are running as follows:

root@bright10:~# cm-package-release-info -f cluster-tools
Name Version Release(s)
------------- --------- ------------
cluster-tools 119767 10.23.11

The output here shows that the cluster-tools package installed is also of version 10.23.11.

Why is it inaccurate to say that “the cluster is running 10.xx.yy”?

To answer this question, it is important to know that BCM is composed of multiple different packages rather than a single entity. The primary package, ‘cmdaemon,’ serves as the core that depends on other several packages.

Let’s assume that you initially downloaded and installed 10.23.10, so it’s easy to say that the cluster is running 10.23.10.

However, there may be scenarios where, for specific reasons, you would like to update a particular package on the cluster, such as the ‘cluster-tools’ package using “yum update cluster-tools”, or “apt install cluster-tools”…etc.

After updating the cluster-tools package, the cluster will look like this:

root@bright10:~# cm-package-release-info -f cmdaemon,cluster-tools
Name Version Release(s)
------------- --------- ------------
cluster-tools 119838 10.23.11
cmdaemon 156713 10.23.10

While the ‘cluster-tools’ is now running version 10.23.11, it’s noteworthy that ‘cmdaemon’ still remains at version 10.23.10.

Assuming once again that you wish to update the ‘cm-setup’ package to its latest release to leverage a feature in one of its tools, with the intention of not affecting the main ‘cmdaemon’ package:

yum update cm-setup
apt install cm-setup

Checking the packages versions, the cluster will appear as follows::

root@bright10:~# cm-package-release-info -f cmdaemon,cluster-tools,cm-setup
Name           Version    Release(s)
-------------  ---------  ------------
cluster-tools  119838     10.23.11
cm-setup       119838     10.23.12
cmdaemon       156713     10.23.10

From the output above, we can observe that every package is running a different minor release version, but all of them belong to version 10.23.

While it is generally recommended to have all packages aligned with the same version, BCM’s nature, composed of multiple packages, allows for variations in minor releases across the packages. Consequently, the cluster can function seamlessly with different minor releases across its components. It’s important to note that due to the diverse package structure in BCM, specifying a single release version for the entire cluster might not accurately represent its composition.

Updated on March 27, 2024