...
Issue ID | Module | Description |
|---|---|---|
BVQ-8509 | GUI | Docking: moving of the performance view option dialog from a docking main window brings the main window to the front |
BVQ-8590 | GUI | Docking: now and then NPE when closing a performance view |
BVQ-8599 | GUI | Docking: IllegalArgumentException bei Schließen eines Tabs in der unteren Hälfte des Hauptfensters |
BVQ-8699 | GUI | Docking: Probleme problems (Exception) beim Minimize eines Docksexception) when a dock is minimized |
BVQ-8879 | GUI | Docking: NPE DragOperation.getCurrentMouse |
BVQ-8613 | GUI | Performance -Ansichtview: CPU Core: Primärspalte "Core" hat keinen Int-Sort sondern Alpha-Sort |
BVQ-8617 | GUI | Performance view: Destage Count in Flight auf Einheit IO/s statt count |
BVQ-8658 | GUI | Performance view: Teilweise werden Linien weggelassen, Fonts verzerrt dargestellt oder Pixel vergrößert |
BVQ-8671 | GUI | Performance view: Options: Close Button bei Tabwechsel funktionslos |
BVQ-8867 | GUI | Performance view: Anzeige neu hereinkommender Werte nur alle 5min trotz 1min Intervalle |
BVQ-8528 | GUI | Object detail view: Cluster Partnership: Versucht eine Priceratio auszugeben, die sie so aber nicht kennt. |
BVQ-8674 | GUITab | schließen mit Closing tab with SHIFT + Klick führt zu GUI Freeze click causes GUI freeze & OutOfMemoryError |
BVQ-8675 | GUI | BVQ license window: high CPU load during visual display |
BVQ-8677 | GUI | Tab bar: icon is not updated after the first content modification |
BVQ-8715 | GUI | Tab bar: IndexOutOfBoundException when last tab is closed |
BVQ-8886 | GUI | Table view: open detail views cannot be opened anymore |
...
Issue ID | Module | Description |
|---|---|---|
| BVQ | BVQ GUI | 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 rückfragenModifications 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 ExportDas | 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 als ".xls" abgespeichert, kommt es zu einer Warnmeldung beim Öffnen mit The Excel-format generated by BVQ Reporting is compatible with Excel Version 2003 and higher. |
| BVQ | BVQ Scanner / Scheduler | Neue Eigenschaften bezüglich Scanner oder Scheduler, die durch einspielen einer neuen Lizenzdatei freigeschaltet wurden, werden erst nach ca. 2h oder nach Neustart der entsprechenden Services wirksam.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 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 | 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 disk corresponds currently to the 'Used Capacity' of the original VMDK file. |
| BVQ | BVQ VMware | Derzeit nicht unterstützte VMware FunktionenCurrently not supported VMware functions:
|
| 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 |
| IBM PMR ? | SVC 7.4 Performace Stats | CPU core COMP (compression) statistics too high (factor ~100). |
...