...
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: Objektliste: Remove von mehreren Objekten in sortierter Tabelle fehlerhaftobject list: remove of multiple objects in a sorted table is faulty |
BVQ-8458 | GUI | Performance view: Metrik-Reihenfolge beim Zeichnen nicht korrekt bei Node Port BBCZ und auch drawing metric-sequence not correct in node port BBCZ and MDisk |
BVQ-8443 | GUI | Favorites: performance view: Favoriten für einige Objekttypen werden unerwartet ausgegraut 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: 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. |
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 Stats | CPT, OPT, APT much too high |
...