Content

Notes

Please note

Starting with version 3.0 the upgrade from DB2 to version 10.5 FP5 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

  • Loading and drawing processes of the performance view were significantly improved
  • Long lasting data load processes can now be interrupted.
  • The performance view for node ports classifies the data and IO rate now according to 'node to local node' and 'node to remote node'.
  • All object types in the topology path can now be set behind the object types 'node' and 'IO group'. 
  • The VDisks which are potentially using a specific node port can now easily by represented by the node´s context menu in the performance view.
  • SVC code version 7.5 beta toleration support

Interruption of a loading process

Long-running loads processes of the performance view, can be aborted via the red button right to the loading bar in the status line.

Classification of some node port metrics in 'node to local node' and 'node to remote node'

The performance view for  node ports classifies now the data-- and command rate  in 'node to local node' and 'node to remote node'. The previous existing column 'node' was replaced accordingly.

The remote data- and command rate is particularly useful in environments which are using remote copy (metro / global mirror)  over long distances in order to  derive directly the load on the transmission lines.

Other object types behind nodes and IO groups

In the topology path all SVC object types can now be set behind the object types 'node' and 'IO group'  .

This can be useful to determine if a 'node' is reaching its performance limits in certain configuration cases.

Load of VDisks behind node ports

The load of a VDisk group runs via certain node ports  into the system. Due to the different multipathing procedures, it is impossible to exactly determine which path is used by a certain VDisk. 

Therefore, the amount of VDisks which are using a particular node port can only be roughly estimated . The localisation is done by  the intersection of:

  1. Connection via access group IO ports: VDisks which are associated with an access IO group containing this node port.
  2. Connection via SAN-zoned host ports to node ports: VDisks whose mapped hosts have a host port in an SAN zone with this node port.

When for example high data rates or a buffer credit wait at a certain date are set for a node port and the causing VDisks have to be found, this can now be easily represented via the object context menu in an additional performance view:   

New functions

Issue ID

Module

Description

BVQ-8870CommonSVC version 7.5 toleration support

BVQ-8270

GUI

Performance view: node port: differentiate metric data rate and command rate node according to 'node to local node' und 'node to remote node'

BVQ-8371

GUI

Topology view: enable  more paths behind 'node' and 'IO group'.

Improvements

Issue ID

Module

Description

BVQ-7085

GUI

Performance view: disable the blocking of the GUI during loading process for PerfView

BVQ-8269

GUI

Performance view: enable interruption of the loading process

BVQ-8612

GUI

Performance view: acceleration of the drawing process for many simultaneous curves by revising the drawing routine

BVQ-8942

GUI

Performance view: acceleration of the drawing processs by using BVQSamplingXYLineRenderer without dots (default)

BVQ-8619

GUI

Performance view: node port: options-dialog: sorting SAS events analogously to FC events

BVQ-8764

GUI

Performance view: button "*": adjust tooltip.

BVQ-8237

GUI

Object node: detail view: show model number additionally in plain text

BVQ-8238

GUI

Topology view: search field: expand results table with  'value' column

BVQ-8370

GUI

Topologiy view: topology navigator: text mode: recognize '/' as final

BVQ-8625

GUI

Topology view: node port: enable a more consistent coloring of the states for IP (iSCSI, iPrep), PCIe and FCoE ports

BVQ-8522

GUI

Object context menu: node port: enable access to relevant VDisk performance view

BVQ-8618

GUI

DB/cluster selection dialog: allow operation even during a waiting period

BVQ-8611

GUI

Tab bar: shorten tab identifiers of the performance view

BVQ-8779

GUI

Tab bar: active tab now always visible by auto-scrolling

BVQ-8708

GUI

Debugging: show VM options in the exception handling dialog

Bug fixes

Critical

Issue ID

Module

Description

BVQ-8589

DB

FC and SAS ports can have the same WWPN in a cluster => persist fails

BVQ-8854

DB

Setup installer: indicates a failure in rare cases as success 

BVQ-8669

SVC Scanner

Topology persist: exception after updating to code version 7.3.0.8  

BVQ-8697

SVC Scanner

Toplology persist: exception

BVQ-8866

SVC Scanner

Ignores various attributes of the VDisk copy from code version 7.3 or later.

BVQ-8871

SVC Scanner

Separator ':' causes problems when scanning Storwize systems starting with code version 7.4

BVQ-8643

Scheduler

Saves PI entries partially without any values 

BVQ-8647

Reporting

CLI doesn`t start

Important

Issue ID

Module

Description

BVQ-8525

DB

Schema migration: installer: update of existing installation no longer available because of missing softlink '/ logs'   

BVQ-8673

DB

Schema migration: installer: update: topology & IOstats path is not read out

BVQ-8621

CLI

Error in argument 'force update'

BVQ-8648

CLI

When creating a disc types an  optional name / comment cannot be placed

BVQ-8696

Common Installer

SVC scanner: topology folder & IOstat folder are not adopted correctly during update

BVQ-8928

Common Installer

Update: for 'leave unchanged'  the respective installer exe should be retained  

BVQ-6329

GUI

Treemap coloring: aggregation of IO density coloration to higher lying objects (grey color)

BVQ-8608

GUI

Treemap coloring: 'Response time compliance': object type storage class: not after peak MDisk group but after peak MDisk

BVQ-8605

GUI

Treemap coloring: node port: SAS: state 'online' doesn´t change to green

BVQ-8672

GUI

Treemap: invert: labeling via SHIFT button is not working properly

BVQ-8831

GUI

Treemap: SeC sorting in the treemap is not always working properly

BVQ-8934

GUI

Treemap: aspect topology: shift-selection doesn't follow the PF (SeC)

BVQ-8604

GUI

Performance view: some keyboard shortcuts don't work properly

BVQ-8716

GUI

Performance view: options: export of aggregated charts delivers an empty csv file

BVQ-8811

GUI

Performance view: memory overflow if date is changed in large periods

BVQ-8945

GUI

Performance view: time-favorite: 'Put timing to all open' doesn't update all open performance views

BVQ-8602

GUI

Node models V7000-100 and V7000-300 are not differentiated correctly

BVQ-8616

GUI

PI loading procedure: particularly wrong results after loading past PI

BVQ-8639

GUI

DB connection profile: file doesn't remain in the previous sub-directory after edit

BVQ-8710

GUI

DB reload is not finished - GUI is locked  (hourglass blocks any entry)

BVQ-8832

GUI

Topo reload doesn't execute the PI reload anymore 

BVQ-8850

GUI

Teilweise wird für Objekte kein Realtime PI Timestamp angezeigt

Issue ID

Module

Description

BVQ-8509

GUI

Docking: moving of the performance view option dialog from a docking main window brings the main window to the front

BVQ-8590

GUI

Docking: now and then NPE when closing a performance view

BVQ-8599

GUI

Docking: IllegalArgumentException when closing a tab in the lower half of the main window

BVQ-8699

GUI

Docking: problems (exception) when a dock is minimized

BVQ-8879

GUI

Docking: NPE DragOperation.getCurrentMouse

BVQ-8613

GUI

Performance view: CPU core: primary column 'Core' doesn't have int-sort but alpha-sort

BVQ-8617

GUI

Performance view: 'Destage count in flight' on unit IO/s instead of 'Count'

BVQ-8658

GUI

Performance view: some lines are omitted, fonts are shown distorted or pixels are magnified 

BVQ-8671

GUI

Performance view: options: when switching tab close button is inoperable

BVQ-8867

GUI

Performance view: new incoming values are displayed only every 5min while 1min intervals are set

BVQ-8528

GUI

Object detail view: cluster partnership: attempts to issue the price ratio, which is unknown 

BVQ-8674

GUI

Closing tab with SHIFT + click causes GUI to freeze & OutOfMemoryError

BVQ-8675

GUI

BVQ license window: high CPU load during visual display

BVQ-8677

GUI

Tab bar: icon is not updated after the first content modification 

BVQ-8715

GUI

Tab bar: IndexOutOfBoundException when last tab is closed 

BVQ-8886

GUI

Table view: open detail views cannot be opened anymore

Known problems

Issue ID

Module

Description

BVQBVQ GUI

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 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.
BVQBVQ VMware

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 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
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).

DB schema changes

Version
Tables
Description
3.3.3.1SCHEMA_LEVELIncreased schema level
3.3.3.2SVC_*_PORT
SVC_PORT_CONNECT
Added port type to primary key due to V7000-300 models using identical WWPN for SAS and FC ports (BVQ-8589)
3.3.3.3PERF_SVC_NODE_PORT

See schema version 3.3.3.2

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 Advanced Workgroup Server Edition V10.5 FP5
Filename: v10.5fp5_ntx64_server_t.exe

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

More information

Please see  release notes for BVQ V3.3.2  

Summary: update steps

Update references

  1. A new license file may be necessary to use certain new features.
  2. The GUI is possibly delivered with new predefined favoritesOnly favorites contained in user favorites are preserved. 

 

  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.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