...
Note | ||
---|---|---|
| ||
Starting with version 3.0 the upgrade from DB2 to version 10.5 FP2 FP5 is mandatory. 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
...
SVC 7.4 toleration support
New functions
Issue ID | Module | Description |
---|---|---|
BVQ-8450 | Common | SVC 7.4 toleration support |
Improvements
Issue ID | Module | Description | ||
---|---|---|---|---|
BVQ-8411 | GUI | Cluster selection dialog: show SVC code level and modify default sorting8326 | GUI | Performance view: consolidate various axes |
BVQ-8350 | GUI | Docking: design of a clearer appointment in the Windows task bar | ||
BVQ-8445 | GUI | Context menu: performance view: arranging general order depending on SVC layer | ||
BVQ-8511 | GUI | DB connection profile: improve handling by File Chooser | ||
BVQ-8520 | GUI | Performance view: cache partition: point tooltip: update of IO group specification |
Bug fixes
Critical
Issue ID | Module | Description |
---|---|---|
BVQ-8603 | SVC Scanner | V7000-300 SAS ports lead to scan errors - quick fix: SAS ports and performance will not be scanned. Final fix in 3.3.3 |
BVQ-8493 | SVC Scanner | Topology: exception with firmware version 7.1.0.2 |
BVQ-84598588 | DB schema Schema migration | |
Issue ID | Module | Description |
BVQ-8392 | GUI | Treemap search: several selected objects from different levels lead to an exception |
BVQ-8413 | GUI | JDBC connection timeouts during slow connections |
BVQ-8415 | GUI | Migscript Failure at Mig-skript 3.3.0.20 for table PERF_SVC_NODE_PORT sometimes fails This means that no node port stats are recognized anymore and the directory BVQ-scanner/iostat/instanceX/error is filled up. |
BVQ-8460 | DB schema migration | Some run-time errors during the execution of mig scripts in DB2CMD are ignored. |
Important
Performance view: node CPU core metric tooltip doesn't show core ID19 | ||
BVQ-8481 | Schema migration | Prereq check not sufficient for owner |
---|
Important
Issue ID | Module | Description |
---|---|---|
BVQ-8607 | GUI | Context menu: VDisk group: exception during calling if no VDisks are included |
BVQ-8566 | GUI | DB/Cluster selection dialogue: DB connection error in user names with special characters |
BVQ-8393 | GUI | DB/Cluster selection dialogue: error message when adding new DB connections |
BVQ-8409 | GUI | Performance view: node port: NPE when calling the node port performance views of a V3700 |
BVQ-8416 | GUI | Performance view: node to node: Y-axis of data rate does not respect lower scaling limit |
BVQ-8431 | GUI | Performance view: untitled favorites cause an exception / some performance favorites don`t have generated name / overwrite doesn`t work |
BVQ-8441 | GUI | Performance view: options: object list: default sorting not always related to primary column |
BVQ-8442 | GUI | Performance view: options: object list: remove of multiple objects in a sorted table is faulty |
BVQ-8458 | GUI | Performance view: drawing metric-sequence not correct in node port BBCZ and MDisk |
BVQ-8443 | GUI | Favorites: performance view: favorites of some object types are grayed out unexpectedly |
Recommended
Issue ID | Module | Description |
---|---|---|
BVQ-84108402 | GUI | Performance view: show VDisk & VDiskCopy cannot be opened with IO group |
BVQ-8418 | GUI | Performance view: Node2Node: inconsistent tab name und perf-view options window title |
...
Docking: when all tabs are closed in the main window, no tabs from the existing undock main windows can be pulled out into the main window anymore | ||
BVQ-8403 | GUI | Docking: X-button: when a tab is taken with D&D out from the main window , a undock main window without X button is produced |
---|---|---|
BVQ-8404 | GUI | Docking: X-button: when a new tab is created via '+' button in the undock main windows. It reappears after changing the input focus |
BVQ-8440 | GUI | Performance view: options: object list: remove of a visible object causes the visibility of the uppermost |
BVQ-8490 | GUI | Favorites: rename favorite has no effect on the name in add favorite. |
Known Problems
Issue ID | Module | Description |
---|---|---|
IBM PMR 91765,033,724 | SVC 6.2.0.3 | Severe 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. |
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 |
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 Statsperformance stats | CPT, OPT, APT much too high |
BVQ-8602 | GUI | Nodes of models V7000-100, V7000-300, V3700 are not properly differentiated because of the same node type 300 - fix expected in BVQ V3.4 |
BVQ-8589 | SVC Scanner | In V7000-300 systems FC and SAS ports have the same WWPN. Primary key is not properly implemented. Therefore SAS ports were completely removed from BVQ 3.3.2. Fix expected in BVQ V3.3.3 |
DB schema changes
Version | Tables | Description |
---|---|---|
3.3.0.2019 | PERF_SVC_NODE_PORT | Improved order of the RENAME TABLE in the script for BVQ-8459Migsript adapted also for V5000 ports |
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 Advanced Workgroup Server Edition V10.5 FP4FP5 |
Java Runtime minimum version | 1.7.0.71 (Java 1.8 not supported) |
More information | Please see release notes für BVQ V3.3.1 |
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.
...
- 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
- Update BVQ Install Package Repository:
bvq-package-repository-installer-x64-V3.3.2.exe
- 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.
...
Hinweise
Note | ||
---|---|---|
| ||
Ab Version 3.0 ist der Upgrade von DB2 auf Version 10.5 FP4 zwingend erforderlich. Ab Version 2.9 wird eine neue Lizenzdatei empfohlen. |
Highlights
SVC 7.4 Toleration Support
Neue Funktionen
Issue ID | Modul | Beschreibung |
---|---|---|
BVQ-8450 | Common | SVC 7.4 Toleration Support |
Verbesserungen
Issue ID | Modul | Beschreibung |
---|---|---|
BVQ-8326 | GUI | Performance-Ansicht: Diverse Achsen konsolidieren |
BVQ-8350 | GUI | Docking: Benennung in der Windows Taskleiste klarer gestalten |
BVQ-8445 | GUI | Kontextmenü: Performance-Ansicht: Generelle Reihenfolge nach SVC Layers orientieren |
BVQ-8511 | GUI | DB Connection Profile: Handling durch File Chooser verbessern |
BVQ-8520 | GUI | Performance-Ansicht: Cache Partition: Punkt-Tooltip: Angabe der IO group ergänzen |
Fehlerkorrekturen
Kritische
Issue ID | Modul | Beschreibung |
---|---|---|
BVQ-8603 | SVC Scanner | V7000-300 SAS Ports führen zu Scan-Fehlern - QuickFix: SAS Ports und Performance wird nicht weiter gescannt. Final Fix in 3.3.3 |
BVQ-8493 | SVC Scanner | Topology: Exception mit Firmware Version 7.1.0.2 |
BVQ-8588 | Schema Migration | Fehlschlag bei Mig-Skript 3.3.0.19 |
BVQ-8481 | Schema Migration | Prereq Check für Owner nicht ausreichend |
Wichtige
Issue ID | Modul | Beschreibung |
---|---|---|
BVQ-8607 | GUI | Kontextmenü: VDisk group: Exception beim Aufruf wenn keine VDisks enthalten sind |
BVQ-8566 | GUI | DB/Cluster Auswahldialog: DB Verbindungs-Fehler bei Benutzernamen mit Sonderzeichen |
BVQ-8393 | GUI | DB/Cluster Auswahldialog: Beim Hinzufügen neuer DB Connections kommt es zu einer Fehlermeldung |
BVQ-8409 | GUI | Performance-Ansicht: Node Port: NPE beim Aufruf der Node Port Performance Views einer V3700 |
BVQ-8416 | GUI | Performance-Ansicht: Node to Node: Y-Achse von Data rate beachtet Untergrenze der Skalierung nicht |
BVQ-8431 | GUI | Performance-Ansicht: Favoriten ohne Name führen zur Exception / Manche PerformanceFavoriten haben keinen generierten Namen / Overwrite funktioniert nicht |
BVQ-8441 | GUI | Performance-Ansicht: Options: Objektliste: Default-Sortierung nicht immer nach Primäspalte |
BVQ-8442 | GUI | Performance-Ansicht: Options: Objektliste: Remove von mehreren Objekten in sortierter Tabelle fehlerhaft |
BVQ-8458 | GUI | Performance-Ansicht: Metrik-Reihenfolge beim Zeichnen nicht korrekt bei Node Port BBCZ und auch MDisk |
BVQ-8443 | GUI | Favoriten: Performance-Ansicht: Favoriten für einige Objekttypen werden unerwartet ausgegraut |
Empfohlene
Issue ID | Modul | Beschreibung |
---|---|---|
BVQ-8402 | GUI | Docking: Sobald im Main Window keinen Tab mehr offen ist, lässt sich kein Tab aus bestehenden Undock-Main-Windows heraus in das Main Window ziehen |
BVQ-8403 | GUI | Docking: X-Button: Zieht man einen Tab per D&D aus dem Main Window heraus, so entsteht ein Undock-Main-Window ohne X-Button |
BVQ-8404 | GUI | Docking: X-Button: Sobald im Undock-Main-Windows ein neuer Tab per +-Button erzeugt wird. Nach dem Wechseln des Input-Focus erscheint dieser wieder |
BVQ-8440 | GUI | Performance-Ansicht: Options: Objektliste: Remove eines visible Objektes führt zur Visibility des Obersten |
BVQ-8490 | GUI | Favoriten: Rename Favorite wirkt sich nicht auf den Namen in Add Favorite aus. |
Bekannte Probleme
...
Issue ID
...
Modul
...
Beschreibung
...
Massiv gehäuftes Erreichen des SVC Limits von 10 gleichzeitig konkurrierenden SSH Sessions, kann einen Warmstart der Knoten auslösen.
Fixed seit 6.4.1.3
...
- .
...
CTD hingegen wurde auf die konsolidierten IO sizes angepasst und liefert weiterhin brauchbare Werte.
...
SVC 7.3 Performance Stats
...
DB Schema Änderungen
Version | Tabellen | Beschreibung |
---|---|---|
3.3.0.19 | PERF_SVC_NODE_PORT | Migsript auch für V5000 Ports angepasst |
Voraussetzungen und Einschränkungen
...
Voraussetzungen der HW/SW Umgebung
...
Siehe Unterstützte Umgebungen ab BVQ 3.0
...
Für eine Aktualisierung erforderliche BVQ Mindest-Version
...
V2.7
...
DB2 Version
...
DB2 Express V10.5 FP5
...
Weitere Hinweise
...
...
- Bei Konfiguration eines Topologie Scanner Intervalls >30min ist eine Anpassung in einer GUI Konfigurationsdatei, bezüglich der Scanner Status Checks, notwendig. Bitte in diesem Fall beim BVQ Support zurückfragen.
- Das vom BVQ Reporting erzeugte Excel-Format ist kompatibel mit Excel ab Version 2003.
Es handelt sich um das Format "XML Kalkulationstabelle 2003" (siehe Microsoft Artikel ).
Die Standard Dateiendung für dieses Format ist: ".xml". Wird es trotzdem mit ".xls" abgespeichert, kommt es zu einer Warnmeldung beim Öffnen mit Excel. - Lizenzänderungen werden erst nach ca. 2h oder nach Neustart im Scanner und Scheduler wirksam.
- Derzeit nicht unterstützte VMware Funktionen:
- Partitionierte VM SCSI Volumes, deren Partitionen mehreren VM Datastores zugeordnet sind
- VM SCSI Volumes deren UUIDs nicht eindeutig sind.
Kurzbeschreibung: Aktualisierungsschritte
Warning | ||
---|---|---|
| ||
Wir empfehlen die unten angegebene Reihenfolge der Aktualisierungsschritte einzuhalten. |
...
- Prüfung auf korrekte Funktion der Umgebung, insbesondere des Scanners.
- BVQ Scanner-, Alerting-Service, Scheduler-Services und alle GUIs, Reporting-Clients manuell stoppen
- BVQ Installation-Verzeichnis und BVQ DB sichern (z.B. DB Offline Backup mit DB2 CMD)
- BVQ Scanner wieder Starten
...
...
...
Viewtracker |
---|