Blog from November, 2023

November 22nd 2023, BVQ version 2023.H2.3 was released. After 3 Family & Friends versions this is now the first publicly available version for BVQ 2023.H2.x.

The release notes & changelogs for the new version can be found here: https://bvq.atlassian.net/wiki/display/BVQ/BVQ+2023.H2.
(warning) Please read the release notes carefully as longer migration times are expected during maintenance mode.

(info) This release also fixes the BVQ issue mentioned in the IMPORTANT information: SVC Code level 8.6.x - SVC GUI/CLI not accessible blog post.
This means that with BVQ version 2023.H2.3 SVC clusters with code level 8.6.x can be scanned again without any problems.

A brief overview of the new features in this release:

  • Improvements for the VMware Platform
  • Enhancements for Brocade (Director Blades & Power Supplies)
  • Optimized DataGrid in the BVQ backend
  • Grafana & MongoDB updates
  • ...

The detailed changelogs for the 2023.H2.x releases can be found here:

Login to https://bvq-software.de to download the new version of BVQ.

November 22nd 2023, BVQ version 2023.H1.6 has been released. This is a minor bugfix release.

Find a list of all the features in version 2023.H1.x here: https://bvq.atlassian.net/wiki/display/BVQ/BVQ+2023.H1 
Changelog of version 2023.H1.5: https://bvq.atlassian.net/wiki/display/BVQ/Changelog+2023.H1.6

(info) This release also fixes the BVQ issue mentioned in the IMPORTANT information: SVC Code level 8.6.x - SVC GUI/CLI not accessible blog post.
This means that with BVQ version 2023.H1.6 SVC clusters with code level 8.6.x can be scanned again without any problems.

Login to https://bvq-software.de to download the new version of BVQ.

A problem with code level 8.6.0.1 was discovered today at one of our customers.

Due to a change in SSH session memory handling, an unstable/unreachable CLI/GUI can occur in SVC clusters with ls commands in combination with loop functions (e.g. while loops).
The problem currently only occurs above a certain size (number of VDisks) in a cluster. In a test in our lab, we were able to reproduce the problem with 600 VDisks.

(info) BVQ has also been using ls commands for a very long time to recognize different object types in SVC clusters, some of which are also executed in a while loop.
(warning) Due to the above-mentioned error in the SVC code level as of 8.6.x, we therefore feel compelled to issue a warning! 
8.6.x SVC Code Level in connection with BVQ versions from 2023.H1.2 should therefore not be used in SVC clusters with more than 200 VDisks.

The problem has already been reported to IBM and is currently under investigation by IBM developers.

Further information can be found in the BVQ wiki on the supported environments → Storage layer