...
Issue ID | Module | Description |
|---|---|---|
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 ziehenwhen 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: Zieht man einen Tab per D&D aus dem Main Window heraus, so entsteht ein Undock-Main-Window ohne X-Buttonbutton: 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: Sobald im Undock-Main-Windows ein neuer Tab per +-Button erzeugt wird. Nach dem Wechseln des Input-Focus erscheint dieser wiederbutton: when a new tab is created via '+' button in the undock main windows. It reappears after changing the input focus |
BVQ-8440 | GUI | Performance -Ansichtview: Optionsoptions: Objektliste: Remove eines visible Objektes führt zur Visibility des Oberstenobject list: remove of a visible object causes the visibility of the uppermost |
BVQ-8490 | GUIFavoriten | : Rename Favorite wirkt sich nicht auf den Namen in Add Favorite ausFavorites: 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 | Bei InV7000-300 Systemen haben systems FC - und SAS-Ports die gleiche and SAS ports have the same WWPN. Primary Key verletzt. Daher wurden SAS Ports komplett aus key is not properly implemented. Therefore SAS ports were completely removed from BVQ 3.3.2 entfernt. Fix erwartet expected in BVQ V3.3.3 |
DB schema changes
Version | Tables | Description |
|---|---|---|
| 3.3.0.19 | PERF_SVC_NODE_PORT | Migsript adapted also for V5000 ports |
...