Highlights

• 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

Example:

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.

Refactored Contextmenu

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.

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

New functions

Improvements

Bugs

Critical

Important

Recommended

Known issues

DB Schema migrations

Requirements and restrictions

Short description of the update steps

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, VMware snapshots) 
   • Starting again the BVQ Scanner
2. Update BVQ Install Package Repository: bvq-package-repository-installer-x64-V3.5.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 

   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