Release notes and notices
This set of Release Notes describes version 11.1 of BMC Discovery.
Version history
The following table displays the version history of BMC Discovery:
| BMC Discovery version | Release date | Remarks |
|---|---|---|
| 11.1 | 11 November 2016 | For complete information about this release, see the features listed in the following section of this page. |
| 11.1 patch 1 | 18 November 2016 | This release resolves important defects. |
| 11.1 patch 2 | 2 December 2016 | This release resolves important defects. |
| 11.1 patch 3 | 17 February 2017 | This release resolves important defects. See also the warning below. |
| 11.1 patch 5 | 7 June 2017 | This release resolves important defects. |
| 11.1 patch 6 | 11 October 2017 | This release resolves important defects. |
| 11.1 patch 7 | 22 June 2018 | This release resolves important defects. |
| 11.1 patch 8 | 03 May 2019 | This release resolves important defects and security vulnerabilities. It also introduces a feature for restricting the paths on which you can run commands. |
BMC Discovery version 11.1 patch 3 resolves some important defects. As a result of those enhancements, an appliance running 11.1 patch 3 cannot join a cluster running 11.1 patch 2 or earlier.
In normal circumstances, all cluster members have the same version. You can upgrade a cluster running any version from 10.1 onwards to 11.1 patch 3.
There is one obscure circumstance in which you may require a new appliance running 11.1 patch 2. If you have a fault tolerant cluster running 11.1 patch 2 (or an earlier patch) and a member has failed, then your cluster is in a degraded state. In that state, you must replace the failed member before you can upgrade the cluster. You cannot replace the failed member with a new appliance running 11.1 patch 3, so you must use an appliance running 11.1 patch 2. Once the cluster has recovered from the failure, it is possible to upgrade the whole cluster to 11.1 patch 3 as usual.
If you are in this situation, and you do not have an image of 11.1 patch 2 with which to replace the failed cluster member, please contact Customer Support. They will provide a suitable download.
You can upgrade to version 11.1.x from version 10.1 and later.
Release Notes
These Release Notes detail the following information:
- 11.1 Enhancements
- Known and corrected issues
- Important information for users of BMC Atrium CMDB
- Technical bulletins
- Product announcements
- Limitations and restrictions of this version
Additional permissions required on XML and CSV APIs
The permission required to access the CSV and XML API has changed. You need to grant the new API access permission (api-access group), or updating group permissions to include the api/access permission for users who require access to the CSV and XML web APIs. Existing integrations will fail if you do not add the permission.
Updated SSH server
The SSH server installed on BMC Discovery appliances 10.2 and later has been modified. This modification removes some weak ciphers and HMAC algorithms (and non-FIPS approved) from the list of allowed connections. Therefore, some older versions of ssh clients might be unable to connect. The following client versions (or later) have been tested and are known to work:
- PuTTY (0.64)
- WinSCP (5.7.2)
- mRemoteNG (1.72 using ssh2)
- MobaXterm (6.5)
- KiTTY (0.63.2.2)
- Bitvise SSH Client (6.22)
BMC Atrium Discovery OS and application software have been tested and found to be free from susceptibility to date/time issues which may occur as the result of the additional day in a leap year.
Comments