New functions

Support for IBM Spectrum virtualize V9000 Systems


Issue ID





Performance-View VDisk copy: Drilldown to nodes should be possible

BVQ-9901GUITreemap: Coloring: Dc2Sc coloring should use a fallback without any special color




Issue ID



BVQ-9812VM ScannerService startup failure because of a new SSL certificate validation


SVC Scanner

updateBvqChildMDiskGroup query faulty


Issue ID



BVQ-9597GUIList-View: Newly created objects arn't listed in the list-view
BVQ-9830GUIPerformance-View: Forward / backward doesn't restore the timeframe correctly
BVQ-9835GUIEditor: Disk Array: "Copy..." function of editors: OK button broken
BVQ-9839GUITopology-View: VDisk move: VDisk copies can't be moved anymore
BVQ-9840GUIColoring: Disk type: Schema "SL>DC/SC" creates a inconsistent coloring for disk type enterprise
BVQ-9046GUIPerformance-View: CPU: Exception while using the invert function
BVQ-9912GUIDetail Pane: Child Mdisk group: SVC ID should be displayed instead of the BVQ ID
BVQ-9902GUIPerformance-View: OptionsPanel: Drive: SVC ID should be displayed instead of the BVQ ID

Issue ID



BVQ-9827GUIInstaller: GUI Memory heap doesn't pick the value of the previous installation
BVQ-9599GUITreemap: Coloring: Changes of color schema arn't shown in the treemap immediately
BVQ-9841GUIStartup: Exception during Compression_Core_Count calculation with CG8 4Core
BVQ-9904GUITextoverlay: DiskType / Drive: Typdescriptor "Drive" / "DiskType" are shown twice
BVQ-9905GUIDP/TO/TT: DiskArray: DiskType shows array name instead of disk type name
BVQ-9913GUIDetail Pane: Child MDisk group: Extent size unit incorrect
BVQ-9790SVC CLI PersisterException message on startup disclaiming about missing version information



Known Issues

Issue ID




Modifications in a GUI configuration file, regarding the scanner status checks, are necessary when a topology scanner interval > 30min is configured. Please contact the BVQ support in this case.

BVQBVQ Excel Export

The Excel-format generated by BVQ Reporting is compatible with Excel Version 2003 and higher.
The generated format is "XML spreadsheet 2003" (please see Microsoft article).
The default file extension for this format is :'.xml'. If it is saved as '.xls' however, a warning message will appear when opened with Excel.

BVQBVQ Scanner / Scheduler

New features for scanner or scheduler which were unlocked by a new license file will take effect after about 2 hours or after restart of the corresponding services.

IBM PMR 91765,033,724SVC impairment of the VDisk latency by the SVC CLI command 'lsmdiskextent'. Seen at a cluster with 8 nodes (8G4) under
Starting with BVQ 2.4.3 this command is not used anymore. Instead command 'Isvdiskextent' is used. 



Massive accumulation of reaching the SVC limit of 10 simultaneously competitive SSH sessions can trigger a warm restart of the node.
Fixed with

BVQ-6610BVQ VMwareMultiple mappings of a VM virtual disk (and/or of different snapshot versions of a single VM) to a VM virtual machine are not supported yet.      
This happens for example with flash copy managers like TSM4VE. 
BVQ-6623BVQ VMwareScan and representation snapshots and thier capacities are not yet supported by BVQ. The 'Used Capacity' of a VM Virtual disk corresponds currently to the 'Used Capacity' of the original VMDK file.

Currently not supported VMware functions:

  • Partitioned VM SCSI volumes, whose partitions are assigned to multiple VM datastores
  • VM SCSI volumes whose UUIDs are not unique
IBM PMR ?SVC Performance Stats

Starting with version  SLAV, PLAV and DLAV refer to the consolidated backend IO sizes of up to 256k. But not the IO-counter for CTRM and CTP, which means that their quotient may be too low by a factor of 8. Therefore, the VDisk below cache metrics SLAV and PLAV cannot be used directly to assess the backend latencies. Also their transaction size is not the same of the backend (max 32k).    

However, CTD was adapted to the consolidated IO sizes and provides continuously useful values.

Performance Stats
Legacy VDisk cache statistics corrupted
Performance Stats
Node CPU core stats =0
IBM Defect 197194

SVC 7.3 Performance Stats

CPT, OPT, APT much too high
IBM PMR ?SVC 7.4 Performace StatsCPU core COMP (compression) statistics too high (factor ~100).
IBM PMR ?SVC 7.3.0 Performance Stats
  • Legacy stats 'cm' and 'cv' are wrong (interchanged compared to the new stats 'm' and 'v')
  • Legacy stats 'ctr' and 'ctrs' show read misses instead of all reads (new stats 'r' and 'ri' are correct)

DB schema changes




Requirements and restrictions

Requirements of the HW/SW environment

Please see supported environments since BVQ 3.5

Minimum BVQ version required for an update


DB2 Version

DB2 Advanced Workgroup Server Edition V10.5 FP5
Filename: v10.5fp5_ntx64_server_t.exe

Java Runtime minimum version1.8.0.45

More information

Please see Release Notes for BVQ V3.5.4    

Short description of the update steps

Important update notes

  1. BVQ licence: a new license file may be necessary to use certain new features.
  2. GUI favorites:  during some of the GUI updates the predefined favorites are replaced. Possible custom changes will be lost. However, changes in user favorites remain .
  3. Update DB2 JRE: before installing the BVQ update please upgrade the system with the recommended DB2 and JRE versions.
  4. If you have problems: if something is going wrong, please contact your BVQ support partner
  1. Preparations
    • Checking for correct function of the environmentin particular function of the scanner.
    • Manual stop of BVQ Scanner and Alerting-service, Scheduler-services and also of all GUIs and reporting-clients
    • Backup of BVQ installation directory and BVQ DB (e.g. DB offline backup with DB2 CMD, VMware snapshots) 
    • Starting again the BVQ Scanner
  2. Update BVQ Install Package Repository: bvq-package-repository-installer-x64-V3.5.5.exe
    1. DB Schema update
    2. BVQ GUI update
    3. BVQ Reporting Engine update
    4. BVQ Report Module update
    5. BVQ SVC Scanner update 
    6. BVQ VMware Scanner update
    7. BVQ Scheduler update
    8. BVQ Alerting update
  3. Performing functional tests
  4. If necessary inform colleagues about the need to update locally installed BVQ GUI / report clients.  


PDF Version

Page viewed times