- Performance view: Auto refresh
- Undo / Redo option for topology and performance view
- Metric-Selection changed to use 7.3 statistics as default and refactoring of contextmenu to open the performance view
- Split of capacity aspects into "SVC Capacity" and "VM Capacity"
- SVC 7.4 child mdisk group & disk encryption support
- Performance view: options-dialog: objektlist: additional useful columns added
- "SCSI ID count" enables alerts for incorrect cluster mappings
- Performance view: Relocate of node cpu stats from node cache into node cpu
- Reduce of memory consumption of performance view
Performance view: Auto refresh
The auto refresh option provides another step to a realtime monitoring. The "Now-Button" has been renamed to Skip to last and skips the view to the last possible datapoint of the visible graph.
The new Play Button starts a refresh each 60 seconds. So the manual refresh isn't necessary anymore and the graph can be updated without any user interaction and display the most recent data continuously.
- Auto refresh settings are captured with the timing favorite so new charts are opend in "auto refresh mode"
- Combined with the docking functionality complex views with multiple auto refresh charts can be generated and display different time ranges and metrics
- Enabling the automatic topology reload doesn't close the performance view anymore
Undo / Redo option for topology and performance view
This enhancement allows a navigation between different states of a toplogy and performance view. Each change is tracked by a change history and it's possible navigate forth and back between this different states.
Metric-Selection changed to use 7.3 statistics as default and refactoring of contextmenu to open the performance view
Till version 3.4.x the BVQ metrics had been aligned to the SVC statistics up to code level 7.2.x. As the cache architecture changed in SVC code 7.3 and this code level get's more popular we changed the BVQ default selection to the SVC 7.3 statistic model. All previous statistics are still available. Because of this changes we refactored the treemap contextmenu to call the different performance views. The new two level structure provides a better separation between different metrics.
Split of capacity aspects into "SVC Capacity" and "VM Capacity"
In previous BVQ versions all SVC and VM capacity aspects were grouped together. This leads to some confusion and we splitted the aspects into separate groups called SVC Capacity and VM Capacity to make thier purpose more obvious.
SVC 7.4 child mdisk group & disk encryption support
In SVC Version 7.4 IBM offered the possibility to devide mdisk groups (storage pool) into smaller units - child mdisk groups (child pools). BVQ version 3.5 added the functionality to support this feature.
MDg = MDisk Group | CMDg = Child MDisk Group
Performance view: Options-Dialog: Objectlist: Additional useful columns added
The list of available object in the performance view options dialog had been extended. The new options are hidden by default but can be made visible using the contextmenu. So it is now possible to display more useful details for each object and make a more specific selection with special reauirements.
|Perfomance view||New objects|
|VDisk||Cache type, Cache partition, Cache IO group, Preferred Node, Copy count, IO governing|
|VDisk copy||Cache type, MDisk group, Cache IO group, Preferred Node, IO governing, Efficiency type|
|MDisk||MDisk tier, MDisk group, Controller, Disk array, Disk type, Site, Room|
|Node||IO group, Type, Cache, Site, Room, Compression active|
|Node Port||Type, IO group, UID, Port speed, Room, Site|
|Node CPU Core||Node type, IO group, Room, Site|
|Node to Node|
IO group, Room, Site
Example: Options-dialog VDisk
New value "SCSI ID count"
The SCSI ID count value shows how many different SCSI IDs are assigned to a VDisk via hostmapping. A value of one shows that a VDisk just uses one SCSI ID in there hostmappings and therefor is distinct. Higher values are indicating multiple SCSI IDs which might lead to problematic behavior especially in VMware Cluster environments.
Based on the SCSI ID count value you can trigger different alerts to find non optimal configurations.
Reduce of memory consumption of performance view
Objecttyp "Disk type": Typ "Hybrid" added
SVC 7.4: "Child MDisk groups" support
SVC 7.4: "MDisk encryption" support
Objecttyp "VDisk" : Aggregation "SCSI ID count" added to enable alerts for non optimal cluster configuration
Performance view: Auto refresh added
Performance view: Added change Color option for point context menu
Performance view: Options dialog: Metric selection changed to use 7.3 statistics as default
Performance view: Relocate of node cpu stats from node cache into node cpu
Aspects: Split of capacity aspects into "SVC Capacity" and "VM Capacity"
Objecttyp VM: "VM virtual capacity" splitted into "From VM_VDisks" and "From DataStore"
Listview: Placeholder in filter for Text-Columns
Performance Scan & Persist: SVC 7.5: Use the partition MDisk group ID in Nn Stat Files
Dialog "Configure report" improved
Report Installer: DB Parameter stored
|BVQ-7197||GUI||Don't close performance view with automatic topology reload|
Performance view: Options-Dialog: Objectlist: Add additional useful columns
Performance view: Options-Dialog: Split VDisk and VDisk copy into Upper Cache und Lower Cache
Performance view: Objekt-Contextmenu: Restructure with sub menu
Performance view: Cache: Accelerate the loading process: Minimize DB access
Performance view: Cache: Compress and minimize memory utilization (JBoss Infinispan)
Performance view: Add duration "5d"
|BVQ-9602||GUI||Performance view: Initial scaling for Mdg Upper/Lower Cache Charts|
|BVQ-9628||GUI||Performance view: Improve timeline of x-axis|
|BVQ-9586||GUI||Performance view: Skip to EoD and Auto Play should use the LastScanDate of the cluster the chart is showing|
Objekt Detail-View: Adjust Cache Partition context to 7.3
Objekttyp Disk Array: Extend the info in Detail-View, Tooltip and Text Overlay
Editiors: Comment-Fields should support word wrap
Editoren: Distinguish editable and locked files in Multi Edit Mode
Listview: Filter to support filtering with combobox "Yes", "No" and "Undef"
Status Bar: PI Load: Improve tooltip formating
Scanner Status overview starts pretty slow and blocks GUI
Objecttyps Cluster, IO group, Node: Detail-View: Adjust appeareance of "Max lower cache"
|BVQ-9325||GUI||Tabs: Clone function|
|BVQ-9662||SVC Scanner||Minimize ERROR Log output|
DB Schema Migration
DB should check for correct migscript sequenz
|BVQ-9561||DB Setup||New BVQ DBs should be created with INITIALSIZE 1 G|
Java Min lversion up to 8
iSCSI Ports with same IQN can't be stored
Topology persist Error BVQMobilityZoneToMDiskGroupMapping
|BVQ-9644||SVC Scanner||Performance Scan stops with SCP error on 1. attempt|
SVC_HOST_PORT recognized as Duplikat if multiple hosts are connected to one SVC Cluster
Primary Index,reorg und runstats not consistent
|BVQ-9614||GUI||Treemap: Coloring of MDisks by tier in performance view not shown|
Port connect: Name for port_connect: "from" Part missing if opponent isn't loaded
Treemap: ATS: RC Relationship not shown in aspect Cap Util.
|BVQ-9590||GUI||Performance view: CPU: Top-Aggregation duplicated|
|BVQ-9583||GUI||Drag & Drop between MDisks groups|
|BVQ-9648||GUI||Exception during tooltip creation after undo|
|BVQ-9660||GUI||Performance view: Node-Port: Remote Node: IPRep Data Rate incorrect|
|BVQ-8888||SVC Scanner||CLI Persister: Performance files aren't persisted if no Topology file is stored|
PI Timeset Selector not updated after PI Reload
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.
|BVQ||BVQ Excel Export|
The Excel-format generated by BVQ Reporting is compatible with Excel Version 2003 and higher.
|BVQ||BVQ 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,724||SVC 126.96.36.199||Severe impairment of the VDisk latency by the SVC CLI command 'lsmdiskextent'. Seen at a cluster with 8 nodes (8G4) under 188.8.131.52. |
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.
|BVQ-6610||BVQ VMware||Multiple 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-6623||BVQ VMware||Scan 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:
|IBM PMR ?||SVC Performance Stats|
Starting with version 184.108.40.206 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|
|Legacy VDisk cache statistics corrupted|
|IBM PMR ?||SVC 7.3|
|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 Stats||CPU core COMP (compression) statistics too high (factor ~100).|
|IBM PMR ?||SVC 7.3.0 Performance Stats|
DB Schema migrations
|220.127.116.11||N/A||Raise Schema Level for Migration|
|18.104.22.168||SVC_MDISK||New column "ENCRYPT"|
|22.214.171.124||MOBILITY_ZONE_TO_MDISK_GROUP||Adjustment of Foriegn Keys for Child MDisk groups|
|126.96.36.199||SVC_CHILD_MDISK_GROUP||Data-Migration from SVC_MDISK_GROUP into SVC_CHILD_MDISK_GROUP|
|188.8.131.52||Diverse||Update of Stored Procedures for runstats and reorgs|
|184.108.40.206||DIverse||Renaming of Primary index corrected|
|220.127.116.11||PERF_SVC_NODE_*_CACHE_PARTITION||Added of Partiton ID|
|18.104.22.168||N/A||Raise Schema Level for Migration|
|22.214.171.124||SVC_CHILD_MDISK_GROUP||Column EASY_TIER resized|
Requirements and restrictions
Requirements of the HW/SW environment
Minimum BVQ version required for an update
DB2 advanced workgroup server edition version
|Java Runtime minimum version||126.96.36.199|
Short description of the update steps
Important update notes
- BVQ licence: a new license file may be necessary to use certain new features.
- 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 .
- Update DB2 JRE: before installing the BVQ update please upgrade the system with the recommended DB2 and JRE versions.
- If you have problems: if something is going wrong, please contact your BVQ support partner.
- 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, VMware snapshots)
- Starting again the BVQ Scanner
- Update BVQ Install Package Repository:
- DB Schema update
- BVQ GUI update
- BVQ Reporting Engine update
- BVQ Report Module update
- BVQ SVC Scanner update
- BVQ VMware Scanner update
- BVQ Scheduler update
- BVQ Alerting update
- Performing functional tests
- If necessary inform colleagues about the need to update locally installed BVQ GUI / report clients.