Content

Notes

Please note

Starting with version 3.0 the upgrade from DB2 to version 10.5 FP2 is mandatory.
Please download first this DB2 version from the IBM website and then perform the upgrade. For instructions, please see the following document: DB2 upgrade from version 9.7.4 or higher to 10.5.

 
From version 2.9 a new license file is recommended.
Continued use of the old license file is also possible. In this case, new features will appear as 'Missing' in the license dialog and are thus deactivated. Otherwise the function of BVQ is not affected.

Highlights

  • Full support of SVC / Storwize version 7.3 including the new cache statistics
  • Displays now the node port performance statistics of types: FC, IPREP, iSCSI, SAS and PCIe
  • Multi screen support. Tabs can now be distributed in different windows on the desktop
  • New start screen allows selection of multiple BVQ installations on one host
  • Object type 'Disc type' now has an optional name and comment

Highlights details

SVC 7.3 cache metrics

Now the performance view additionally shows the new SVC 7.3 cache statistics. Only this allows a full analysis of the system's performance.
Particularly important advantages of the new 7.3 metrics are:

  • Real IO sizes: all IOs are counted in real transaction sizes and not, as before, limited by 32KiB cache tracks.
  • Upper / lower cache: they are displayed separated in upper cache and lower cache. All remaining 7.2 cache metrics are exclusively related to the upper cache.   
  • VDisk copy metrics: now statistics are available at the level of VDisk copy. Thus, the load which is caused by a VDisk competing with others of the pool (MDisk group) can be determined exactly.
    P
    reviously this was not possible especially in cases when VDisk mirroring, space efficiency, compression or flash copy were used. Please note: the object type VDisk  inherently contains only the upper cache metrics.
    The matching
    lower cache metrics can be found in the correlating VDisk copy of a VDisk.
  • End to end: the active chains in 7.3 can be represented as follows:

    ReadsVDisk SCSI layer→ VDisk upper cache→ VDisk copy lower cache→ MDisk queue outbound→ Node port
    WritesVDisk SCSI layer→ VDisk upper cache partiton→ VDisk copy lower cache partition→ MDisk queue outbound→ Node port

The new 7.3 metrics can be selected in a third tab in the options dialogue of the performance view. Here, for example, the metrics for object type 'Node':

It can be recognized that they are now differentiated in upper and lower cache .

Port statistics for SAS, PCIe, FCoE, iSCSI, IPREP

Now BVQ additionally displays the node ports of not-FC types like SAS, PCIe, FCoE, iSCSI and IP replication in the treemap and in the performance view.  

This completes the analysis options in the port area.

Here is a look on the node ports of a first generation V7000 :

Here the appropriate options-dialogue of the performance view, which allows the access to appropriate metrics:

Some port types like FC & FCoE, SAS and IP replication have specific metrics which are visible at the bottom in the metric selection.

Multi window docking

Tabs can now be converted into window areas. These areas can be extracted from the main window and be placed on the desktop or they can also be ordered  within a window next to or above each other .

Thus,  several performance views can be made visible simultaneously within one presentation. The distribution across multiple screens is also possible.

Here, for example, two treemaps next to each other with transferred selection :

Or multiple performance views of different types with identical time axis within one analysis.

DB connection profile

BVQ DB connection profiles include the access data to BVQ databases. BVQ client tools (currently GUI and reporting) use these whe establishing a connection and enable their management. The profiles are stored in '.bdp' files centrally within the installation directory and can be exchanged throughout the company. All locally installed client tools are using the same .bdp files.

A BVQ GUI or BVQ Reporting GUI can thus be easily switched on all configured BVQ databases.

The following screenshot shows the GUI's selection dialogue:

Encrypted passwords are stored in the .bdp files.

Please note: license-fees have to be paid for each additional BVQ DB.  

Disk type name and comment

The BVQ object type Disk type now has got an optional name and a comment field. With this   subtle differences between two similar disc types can be expressed better (for example: '3.5' vs '2.5', or SAS vs SATA  vs FC or even different transmission speeds).

The name is optional. If not specified, or an existing name is cleared, BVQ derives automatically a new one based on the configured attributes .

If the name is entered  , for example, in BVQ CLI scripts it can later be used for the allocation of disk arrays. As a result, scripts can be created  containing a complete image of a disk subsystem. The previously necessary query of the BVQ ID after creating the disc types is no longer needed. So this script can also be created offline ( for example from tables).

New functions

Issue ID

Module

Description

BVQ-7101

Common

SVC 7.3: new cache architecture statistics integration

BVQ-7183

Common

Integration of SVC asset informationen into SVC nodes from lsnodehw (RAM, #CPU, #Cores)

BVQ-7811

Common

Object type: disk type: several improvements

BVQ-7870

Common

SVC 7.3: full support

BVQ-7952

Common

Node ports: integrate FC, IPREP, iSCSI, SAS, PCIe + show performance

BVQ-8059

Common

Node ports: FC: using expanded possibilities of Isportfc

BVQ-7903

DB

Tables for new perf stats from SVC 7.3 code

BVQ-7683

VMware scanner

Allow removing of a VM  vCenter from the  BVQ DB by using modified TopoFile

BVQ-3682

GUI

Multi window GUI (Jyloo Docking Framework)

BVQ-8134

GUI

Enable selection of DB at start

BVQ-8193

Reporting

Enable selection of DB at start

Improvements

Issue ID

Module

Description

BVQ-8121

Common

Deeper detailing of SVC Isnodehw asset information for SVC nodes

BVQ-7510

Common

Object type 'Disk type': add name and comment

BVQ-8197

Common

Integration of IP V6 support for all SVC IP adresses

BVQ-8306

SVC Scanner

Perf-persist: set up for  large counters (>Max(Signed Int64))

BVQ-8144

Scheduler

PI: align realtime PI according to SVC Perf Stat interval

BVQ-5930

DB

Rename performance columns coherently according to <XML_ATTRIBUTE_NAME>

BVQ-7729

DB schema migration

Integrate prereq check for user=owner

BVQ-8149

DB setup

Better detection and notification of db2cmd warnings 

BVQ-7733

GUI

Object type 'Extent': DP & TT: add information %Capacity of MDisk / VDisk

BVQ-8084

GUI

Performance view: options dialog: improve filter for column 'visible'

BVQ-8138

GUI

Performance view: reduce storage consumption of the perf-raw data

BVQ-8154

GUI

Performance view: upgrade  JFreeChart to current version

BVQ-8226

GUI

Favorites: disabled if not able to start

BVQ-8233

GUI

Security request when GUI is closed per window X-button 

BVQ-8255

GUI

Alerting: editors: better labeled assignment dialogs for n2m

BVQ-8285

Reporting

Upgrade Eclipse BIRT  to version 4.4.1

Bug fixes

Critical

Issue ID

Module

Descripton

BVQ-8116

DB Setup

SQL scripts are not executed

BVQ-8305

SVC Scanner

Performance persist: exception: the XML construct 'ctps' cannot be converted to a long

Important

Issue ID

Module

Description

BVQ-8205

GUI

Performance view: VDisk: unexplainable grey gap areas

BVQ-8223

GUI

Status bar: PI load date: allows selection of a date in the future and does not always show the loaded time 

Issue ID

Module

Description

BVQ-8023

GUI

Table view: cannot be closed with the ESC-key

BVQ-8292

GUI

Default L&F is not always 'White Vision'

BVQ-8297

GUI

License check in the GUI doesn't work with wrong public key

Known problems

Issue ID

Module

Description

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

IBM PMR
unknown

SVC 6.4.0.3

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

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 
IBM PMR ?SVC Performance Stats

Starting with version 6.1.0.1  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.

IBM PMR ?SVC 7.3
Performance Stats
Legacy VDisk cache statistics corrupted
IBM PMR ?SVC 7.3
Performance Stats
Node CPU Core stats =0

DB schema changes

Version
Tables
Description
3.3.0.1N/ARaise schema level

Requirements and restrictions

Requirements of the HW/SW environment

Please see supported environments since BVQ 3.0

Minimum BVQ version required for an update

V2.7

DB2 Version

DB2 Express V10.5 FP4

Java Runtime minimum version1.7.0.71 (Java 1.8 not supported)

More information

Please see release notes for BVQ V3.2.2   

Notes

  • When configuring a topology scanner interval >30 min an adaptation in a GUI configuration file is necessary, concerning the scanner status checks. In this case please contact BVQ support.  
  • The Excel format generated by the BVQ Reporting is compatible with the Excel version of 2003 and higher.  
    This is the format 'XML spreadsheet 2003' (please see this Microsoft article for more information).
    The standard file extension for this format is '.xml'. If it is despite  saved with '.xls', a warning message appears when it is openend with Excel.
  • License changes only take effect after about 2 hours or after restarting the scanner and scheduler.
  • 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.

Summary: update steps

Update references

  1. (warning)* For an upgrade of BVQ Scanner from version 2.7 to 2.8 or higher should be noted that now a VMware Scanner can exist besides the SVC Scanner. Therefore, it is installed in a new default directory bvq-svc-scanner (previously  bvq-scanner). To use the existing scanner configuration again, the update should be proceeded as follows before performing update step 3:
    1. Stop BVQ Scanner services manually
    2. Rename directory bvq-scanner in bvq-svc-scanner
    3. Continue with update step 3.
  2. Before possibly new functions can be used, a new license file is required. 
    After the import of the new license the GUI has to be restarted.
  3. The GUI is delivered with new predefined favorites. Only favorites from User favorites are retained.   

We recommend to follow the sequence of update steps shown below.

 

  1. Preparations
    • Checking for correct function of the environment, in 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) 
    • Starting again the BVQ Scanner
  2. Update BVQ Install Package Repository: bvq-package-repository-installer-x64-V3.3.exe
    1. DB Schema update
    2. BVQ GUI update
    3. BVQ Reporting Engine update
    4. BVQ Report Module update
    5. BVQ SVC Scanner update (warning)*
    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