- Support for Cisco MDS Switches
- Horizontal Marker
- VMware: Additional attributes
- New license model
- WebUI: BVQ support package
- WebUI: Reporting Improvements
- Further Enhancements
- Export GUI: Ease expansion of objects in tree mode tables
- WebUI: BVQ GUI downloadable from server
- WebUI: Add possibility to disable performance scan for SAN and SVC scanners
- WebUI: Individual data expiration definitions
- WebUI: Ease identification of Scanner problems
- WebUI: Exclusion/Re-inclusion of alert rule ojects
- WebUI: Show license status on Home dashboard
Support for Cisco MDS Switches
The BVQ Cisco Module is a complete new extension package for BVQ. It introduces support for Cisco MDS switches. It enables you to interactively explore your Cisco SAN configuration and check it for issues, chart switch port performance and error metrics, create reports about port utilization and drill through all the layers between Storage, BVQ, and Compute objects in end to end views.
Please review BVQ License Information Page or ask your sales contact for more information.
Topology and performance data for BVQ is gathered through the Cisco Data Center Network Manager (DCNM). Information from all MDS switches managed by DCNM are collected using SMI-S.
See BVQ server requirements & Supported environments for more information
In BVQ release 6.1 the following Cisco object types are supported:
|Physical||DCNM||Data Center Network Manager. This is the so called MasterGroupingObject and is parent for all other object types|
|Switch||The physical switch, i.e. the real hardware (incl. Device type, model, S/N, etc.)|
The physical switch port, i.e. the real hardware port on the physical switch (e.g. fc1/1).
In BVQ, switch ports have a color coding:
|ISL||Inter-switch link. A FC connection between two physical Cisco MDS switches|
Port channels are a bundling of ISLs (FC or Ethernet) or, to be more precise, the aggregation of multiple physical interfaces into one logical interface to provide higher aggregated bandwidth, load balancing, and link redundancy.
|Logical||Fabric||The sum of switches that are connected via FC and are able to communicate with each other build up a fabric.|
Virtual SAN. Single or multiple ports on a switch in a fabric can build a VSAN.
|All ports on a physical switch that are configured in the same VSAN make up a logical switch.|
|Logical Switch port|
Each switch port that is configured in a VSAN is a logical port. While a phyiscal switch port is unique on a particular switch, a logical switch port is not.
As a result, physical switch port fc1/3 is unique on switch A and switch B but logical switch port fc1/3 shows up twice on switch A and switch B: once for each VSAN (X and Y)
Logical switch ports have the same color coding as physical switch ports.
|Logical ISL||An ISL can be used by multiple VSANs (trunking). Hence, a Logical ISL (LISL) is an ISL in a VSAN.|
World Wide Node Name (WWNN) of a connected device
In BVQ, nodes have a color coding:
World Wide Port Name (WWPN) of a connected device.
Node ports have the same color coding as nodes.
Set of zones.
|Zone||Definition of devices that are allowed to communicate with each other.|
|Zone member||Member of a zone. A zone member can be in the form of WWPN, Port, Device Alias oder FC Alias|
Cisco FC Alias.
The following overview shows the elementary relationships of physical and logical objects:
(blue colored objects are physical, light blue colored objects are logical)
Where to find Cisco objects?
Similar to all other objects, they show up in the BVQ Path browser inside the property panel or can be opened as a Table view from the Favorite browser. All Cisco objects can be combined in an end to end relation to many other objects.
|Cisco objects in view Path browser||Cisco object Table views in BVQ Favorites|
BVQ displays all interesting attributes provided by the DCNM through SMI-S. Be aware that this set of parameters is much smaller than what is provided by the Cisco CLI.
In addition, BVQ calculates counters for each object. For example a Cisco fabric knows how many switches it contains, how many switch ports those have and how many of them are connected or free for use. Please explore the BVQ Cisco table view favorites to get an impression of the most important attributes.
Performance and error metrics
The BVQ Cisco module gathers all switch port statistics delivered from the DCNM. To view performance statistics for one or multiple objects, simply select the object(s), right-click and select the performance object type you are interested in.
In the chart view, open the properties panel to select the metrics you are interested in:
|Frame rate||Rx||Frames/s||Received frame rate|
|Frame rate||Tx||Frames/s||Sent frame rate|
|Frame rate||Rx+Tx||MiB/s||Overall frame rate|
|Frame rate||Rx%||%||% received of total transferred frames|
|Data rate||Rx||MiB/s||Received data rate|
|Data rate||Tx||MiB/s||Sent data rate|
|Data rate||Rx+Tx||MiB/s||Overall data rate|
|Data rate||Rx%||%||% received of total transferred data|
|Data rate util % avg||Rx||%||Port bandwidth utilized by overall receive data rate|
|Data rate util % avg||Tx||%||Port bandwidth utilized by overall transmit data rate|
|Data rate util % avg||Rx &Tx||%||Maximum port bandwidth utilization of overall transmit and receive data rate|
|Data rate util % peak||Rx||%||Single object peak port bandwidth utilized by overall receive data rate|
|Data rate util % peak||Tx||%||Single object peak port bandwidth utilized by overall transmit data rate|
|Data rate util % peak||Rx & Tx||%||Single object peak port bandwidth utilization of overall transmit and receive data rate|
|Frame size||Rx||Bytes/Frame||Framesize received|
|Frame size||Tx||Bytes/Frame||Framesize transmitted|
|Frame size||Rx&Tx||Bytes/Frame||Average overall framesize|
|Frame size min||Rx||Bytes/Frame||Minimum framesize received|
|Frame size min||Tx||Bytes/Frame||Minimum framesize transmitted|
|Frame size min||Rx&Tx||Bytes/Frame||Minimum average overall framesize|
|Frame rate by class||Rx C2||Frames/s||Received class 2 frame rate|
|Frame rate by class||Rx C3||Frames/s||Received class 3 frame rate|
|Logical layer (peak)|
|Frame discards||RxTO||Frames/s||Single object peak frame timeout rate in received buffer|
|TxTO||Frames/s||Single object peak frame timeout rate in transmitted buffer|
|Other||Frames/s||Single object peak all other frame discards not due to a timeout (unreachable, zone misses, unrouteable ...)|
|Offline sequences||Rx||Count/s||Single object peak offline sequences receive rate|
|Offline sequences||Tx||Count/s||Single object peak offline sequence transmit rate|
|Offline sequences||Rx+Tx||Count/s||Single object peak overall offline sequence rate|
|Link resets||Rx||Count/s||Single object peak link reset receive rate|
|Link resets||Tx||Count/s||Single object peak link reset transmit rate|
|Link resets||Rx+Tx||Count/s||Single object peak overall link reset rate|
|Physical layer (peak)|
|Encoding errors||In||Count/s||Single object peak rate of encoding errors inside frame|
|Encoding errors||Out||Count/s||Single object peak rate of encoding errors outside frame|
|Encoding errors||In+Out||Count/s||Single object peak overall Encoding error rate|
|CRC errors||Overall||Count/s||Single object peak rate of all CRC errors|
|Link errors||LF||Count/s||Single object peak link failure rate|
|Link errors||LSY||Count/s||Single object peak loss of sync rate|
|Link errors||LSI||Count/s||Single object peak loss of signal rate|
|Errors||Protocol||Count/s||Single object peak protocol error rate|
|Errors||Address||Count/s||Single object peak address error rate|
|Errors||Delimiter||Count/s||Single object peak delimiter error rate|
|Errors||Too long||Count/s||Single object peak rate of too long frames|
Charts in BVQ rely on user interpretation in most situations. To support the user to save and visualize general or custom thresholds "Horizontal Marker" has been introduced in the BVQ GUI.
- Stored with the favorite
- Dynamic visibility
- Available for performance and all chartable attributes
To create a marker open a chart and go to the new "Marker Tab". Use the Buttons to add, edit or delete markers.
|Use a meaningful label to identify the marker. The Unit will allways be appended.|
|Color||Choose a color for line and fill|
Select the metric the marker will be bound to.
|Unit||Select a unit the the Threshold is formatted. This is especially useful for capacity values.|
|Threshold||Value the marker should be drawn at|
|Visible||Is the marker visible?|
Does the marker draw a background fill?
The Fill is always draw above the marker line up to the next marker.
To control the visibility of a marker there are 4 conditions which have to keept in mind.
- The drawing options are extended with a global "Marker" checkbox. If unchecked no marker will be displayed for this favorite and ignore all other conditions
- A marker will only be shown if the appropriate metric is visible
- A marker will only be shown if the "Visible" checkbox is checked
- A marker might be invisible if it is scaled out. Due to the Auto-Adjust Feature it might happen that a 90% Marker is invisible if the max chart value is 40%.
VMware: Additional attributes
With version 6.1 we added many additional attributes to the VMware objects Cluster, Host, Virtual Machine and SCSI Volume. Therefor we updated the related table views and made the attributes available for Alerting and charting in the GUI, Reports and Grafana.
|DRS enabled||Cluster vSphere DRS mode enabled||Cluster vSphere DRS enabled flag for Cluster|
|DRS defaultVmBehavior||Cluster vSphere DRS default VM behavior||Cluster vSphere DRS default VM behavior|
|HA Mode||VM HA mode||High Availability (DAS) mode|
|DAS Host monitoring||Cluster HA Host monitoring||High Availability (DAS) Host monitoring|
|DAS VM monitoring||Cluster HA VM monitoring||High Availability (DAS) VM monitoring|
|DAS CPU failover resources in %||CPU failover resources reservation in percent||High Availability (DAS) CPU failover resources reservation in percent|
|DAS Memory failover resources in %||Memory failover resources reservation in percent||High Availability (DAS) Memory failover resources reservation in percent|
|vm drs fault||VM with a fault in DRS||VM that cound't be moved by DRS because of a fault|
|drs fault||DRS fault code||The fault code of DRS|
|VM Host Mem||VM Host Memory||Memory present in VM Host|
|Vendor name||Vendor name||Hardware vendor name|
|Model name||Model name||Hardware model name|
|Serial number||Serial number||Hardware serial number|
|API Version||Version of the API||...|
|OS name||Name of the operating system||...|
|Boot time||Boot time||...|
|In maint. mode?||In maintenance mode?||Is system in maintenance mode?|
|In qaran. mode?||In quarantine mode?||Is system in quarantine mode?|
|Conn state||Connection state||Connection state of the system|
|Power state||Host power state||Power state of the Host system|
|DAS state||DAS Host State||DAS state of the Host|
|Bios||Bios version||Version of the bios|
|Bios rel.||Bios release date||Release date of the bios|
|NTP Server||NTP Server||NTP Server|
|Time zone||Time zone||Time zone|
|Lock mode||Lockdown mode||Lockdown mode|
|TSM-SSH||Tech Support Mode-SSH||Tech Support Mode-SSH|
|TSM||Tech Support Mode||Tech Support Mode|
|vmsyslogd||VM Syslog Server||VM Syslog Server|
|DNS address||DNS address||Address of the DNS server|
|DHCP||DHCP||Is DHPC active?|
|Domain Name||Domain Name||The Domain Name|
|searchDomain||searchDomain||The search Domain|
|Memory||VM Memory (RAM)||Amount of memory (RAM) configured for the virtual machine|
|OS version||VM OS version||Operating system version of the virtual machine|
|HW version||VM Hardware version||Hardware/Compatibility version of the virtual machine|
|Hostname||VM Hostname||Hostname of the virtual machine|
|Boot time||Time of last boot||Timestamp when the virtual machine was last booted|
|Uptime||VM Uptime||Uptime for the virtual machine|
|Tools version||VMware Tools version||Current version of the VMware tools installed on the virtual machine|
|Tools status||VMware Tools status||Current status of the VMware tools installed on the virtual machine|
|Tools mounted||VMware Tools mounted||Current mount status of the VMware tools installer on the virtual machine|
|EVC enabled||CPU EVC mode enabled||CPU enabled flag for the virtual machine|
|Min EVC mode||Minimum CPU EVC mode||Minimum CPU EVC (Enhanced vMotion Compatibility) mode key needed for the virtual machine|
|HA mode||VM HA mode||High Availability (DAS) mode for the virtual machine|
|FT info||VM FT info||Fault Tolerance info for the virtual machine|
|FT state||VM FT state||Fault Tolerance state for the virtual machine|
|Notes||VM Notes||Notes for the virtual machine|
|Custom attributes||VM Custom attributes||Custom attributes for the virtual machine (comma separated)|
The operational states of the LUN.
|Lun type||Lun type|
The type of SCSI device
Disk format version
VMFS version this SCSI volume is formatted
SSD tier enabled / disabled for the SCSI volume
Transport protocol of the SCSI volume
Raw device mapping
Raw device mapping is enabled / disabled
|vSAN cache disk||vSAN cache disk|
vSAN cache disk enabled / disabled
The hardware acceleration functionality enables the ESXi host to integrate with compliant storage systems
String representing the path selection policy for a device.
New license model
New License needed
To update to BVQ 6.1 a new BVQ License is needed. Please contact the BVQ-Team firstname.lastname@example.org
With version 6.1 we introduced a new license model. To simplify the usage new licenses wouldn't need specific system id's any more. This will reduce the cases to create a new license because of id changes in your environment.
More detailed license information are available here: https://bvqwiki.sva.de/x/loLrAw
The license changes are reflected in the BVQ WebUI as well and will provide a better overview.
New licenses are based on entitlements. Capacity for storage, Virtual machine counts for compute platforms and port counts for network layers.
The overview table provide a summary over all systems. The info button will display a more detailed table for each system.
|Feature||Shows if special features are licensed.|
|License||Information about the license type.|
|Timeframe||Runtime: The date until BVQ will be usabel. |
Support: The date until the customer has purchased support. Without a valid support BVQ updates aren't allowed.
WebUI: BVQ support package
BVQ stores various log files in different locations. All those log files can now be easily collected in one single package. Once provided to the BVQ support team, they can now isolate and fix a potential problem more quickly.
To collect a support package, go to Support > Support package. Select from two types of support packages:
- Scanner logs of each scanner instance
- All scanner configurations
- BVQ-Server logs
- File count report. How many files are in each folder of bvq-server\data
Logs, Topology and Performance Package
- Latest 5 topology files of each scanner instance (error, invalid, done, etc.)
- Latest 5 performance files of each scanner instance (error, invalid, done, etc.)
- Latest 5 event files of each scanner instance (error, invalid, done, etc.)
- Scanner logs of each scanner instance
- All scanner configurations
- BVQ-Server logs
- File count report. How many files are in each folder of bvq-server\data
WebUI: Reporting Improvements
In former BVQ releases, topology tables or performance charts could only be used in report templates if the views were previously created in the Expert GUI and stored as favorites in the All-users folder. This was a complex and complicated procedure.
With BVQ 6.1, topology tables and performance charts are now available as report template snippets which makes their usage much easier.
The new snippets can be found here:
How to create topology table snippets
In the "Select & Filters"-tab, select and save an object type. Optionally, add one or more object types to the selection path to group the selected object type.
Object types can be reordered by using Drag & Drop. If required, add filters to one or all of the object types. Then choose between flat and tree table mode.
In the "Columns"-tab, select one or more attributes for the object type. Apart from the default attributes, all manually added attributes can be removed again by selecting the "x"-button next to the attribute.
The column order of the attributes can optionally be changed in the "Sorting"-tab using Drag & Drop. For tables in flat mode, columns can be sorted ascending/descending by clicking on the up/down arrow next to the attribute.
Use the "Preview"-Button in the upper right corner of the snippet to get a quick overview of the table that has just been configured.
How to create performance chart snippets
First, select a "Chart object type" in the corresponding tab. Only object types which provide performance metrics can be selected here.
In the "Selection & Filters"-tab, one or more object types can be added to the selection path to group the selected chart object type. If required, filters can be added to any object type. The visibility of an object type can be enabled or disabled.
In the "Metrics"-tab, choose one or more metrics for the selected object type. Keep in mind, that a chart gets confusing quickly if too many objects and/or metrics are selected!
The usage of the "Options"-tab is optional. Here chart related options like line design, latency filters or chart legends can be configured.
Use the "Preview"-Button in the upper right corner of the snippet to get a quick overview of the chart covering the last hour.
Export GUI: Ease expansion of objects in tree mode tables
Expanding objects in a tree mode table can require a lot of clicks if the amount of objects is high. To make navigation through different object levels easier, each object type in the path can now be expanded/collapsed separately. Just right-click on the table header and select the required object type to expand up or collapse down to this level.
WebUI: BVQ GUI downloadable from server
To avoid DB schema level mismatches, it is recommended to use a GUI version that matches the BVQ Server version. In the past, the only resource to download the GUI was this Wiki here. While this option still exists, it is now also possible to download the GUI directly from the login screen of the BVQ Server.
WebUI: Add possibility to disable performance scan for SAN and SVC scanners
By default, performance data collection for SVC, Brocade and Cisco scanners is enabled. Just like VMware scanners, an option has been added to those other scanner types to make collection of performance data configurable.
WebUI: Individual data expiration definitions
By default, performance indicators and alert rule results are being deleted from MongoDB after a certain timeframe. Those default values are the following:
- raw performance data: 31 days
- 5-minute-interval performance data: 91 days
- 1-hour-interval performance data: 365 days
- 1-day-interval performance data: 730 days
- alert rule results: 28 days
Depending on the number and type of scanned systems in BVQ, the size of the database can increase quite quickly. In addition, data from different systems might be of more or less importance so the above default values are not suitable for all systems.
As a result, the expiration dates in BVQ are now configurable on a per system basis.
There are two ways of adjusting the expiration dates in the WebUI:
- Go to Scanner and edit the required scanner configuration. At the bottom of the dialogue, enter the new expiration dates for the selected system:
- Go to Administration > Data Expiration. Each system scanned by BVQ is listed here. Use the Edit-Button to open the scanner-configuration dialogue and adjust the expiration dates for this particular system. To adjust the default values so that expiration dates change for all scanned systems, click on Edit default expiration dates on the upper right corner of the page.
WebUI: Ease identification of Scanner problems
If a BVQ configuration contains a lot of scanner instances, it was often difficult to find out if all scanners were working properly or if there were any issues. To make identification of erroneous scanners easier, they are duplicated on top of the scanner overview page under "Critical configurations".
WebUI: Exclusion/Re-inclusion of alert rule ojects
Alert rules help to monitor the health of the monitored systems. As long as all objects have a good status, everything's fine. Objects in warning or error state are often cause for worry and indicate a more or less critical issue. But there can be circumstances where an object is known to be in error state, e.g. a hardware part is known to be broken but won't be repaired within the next days. In this case, it is annoying that the Systems Health Map shows a bad result although the reason is understood and a solution underway. Those objects are then typically excluded from the view. Inclusion of the object was a manual process which means that the excluded object never shows up again in this particular alert rule if you forgot to include it manually.
To avoid this from happening, more options to automatically reinclude an object after inclusion have been added to the exclusion-dialogue:
- Go to Alerting > Results, select the alert rule of interest and click on the eye-icon next to the required object:
- the exclude/include-dialogue offers different methods to auto-include the object:
- select "Manually" to re-include the object individually (default option)
- select "At next Alert rule run after" and enter date and time. In this case, the object is auto-included once this alert rule is executed the first time after this date. Be aware that - dependent on the execution frequency of the rule - the inclusion of the object is much later than the defined date and time!
- select "At next transition to default Alert level" to auto-include the object the next time it changes to default level. Default level typically is the OK-state unless the user has defined a different default level.
- select "At next transition to Alert level" and enter the alert level to auto-include the object the next time it changes to this level.
WebUI: Show license status on Home dashboard
For easier determination of a license issue, the license status is now visible on the BVQ WebUI Home dashboard. Once logged it, the status is shown in the upper right corner of the dashboard. A click into the box takes you directly to Administration > License where you can see all details of the license and identify potential license issues quickly.
Requirements and restrictions
Requirements of the HW/SW environment
Minimum BVQ version required for an update
Update from a previous MongoDB Installation step by step
- Check for the correct function of the whole environment, in particular the function of the scanner.
- Manual stop of BVQ Scanner- and Server-services and also close all GUIs
- Backup the BVQ installation directory and BVQ DB (e.g. DB backup with
mongodumpor VMware snapshots)
- Restart the BVQ Scanner
- Update BVQ Install Package Repository:
- MongoDB update
- BVQ GUI update
- BVQ Server update
- Test the function of the BVQ environment.
- If necessary inform colleagues about the need to update locally installed BVQ GUI clients.
|BVQ-15521||Server: SHM||Modify & add predefined VMware vSAN Disk group alerts|
|BVQ-15425||Server: Support package||Remove delay when clicking "Create support package"/ "Run report" & long waiting on 100%|
|BVQ-15368||Common||Disable JMX RMI for BVQ java processes|
|Major||BVQ-15394||GUI||Estimated IO density heat coloring is not shown|
|Major||BVQ-15510||Server: Reporting||SRS Performance Report: Percent values factor 100 too high|
|Minor||BVQ-15522||GUI||ClassCastException for numeric / date flat table filter value when opening favo or changing columns|
|Minor||BVQ-15534||License||Unlicensed ports are counted for license|
|BVQ-14630||WebUI: Reporting||New improved Brocade SAN Reports|
|BVQ-15326||WebUI: Reporting||New improved Brocade SAN Performance Report|
|BVQ-13374||WebUI: Alerting||Visualize enabled/disabled alert rules with coloring in Manage alert rules menu|
|BVQ-14471||WebUI: Alerting||Missing and incorrect filters in predefined alert rule "SVC Thin provisioned VDisk copy contingency capacity too low"|
|BVQ-13992||WebUI: Scanner||Show license-status for hftcs in scanner-overview|
|BVQ-15380||WebUI: Scanner: Cisco / Brocade||Support "Ignore SSL check" for CIMClient based scans|
|BVQ-14501||WebUI: SHM||Add SHM System Alerts for VM CPU wait % metrics|
|BVQ-13085||Maintenance mode||Show log output of mongod.log during schema migration|
|BVQ-14014||GUI: Filtering||Add "subelementcount > 0" as predefined filter option|
|BVQ-14628||GUI: DetailPane: "All"-Tab||Add TreeTableControl to search Attributes-TreeTable|
|BVQ-14534||VMware: Metrics||Add peak metrics for latency|
|Major||BVQ-15394||Broadened Performance||Duplicate Key Exceptions because of svc_vdisk_uid = null|
|Major||BVQ-14676||GUI||Hangs on startup due to views.xml file with newer version|
|Major||BVQ-15409||WebUI: Reporting||Execution of aggregated chart report with filter runs into exception|
|Major||BVQ-15348||WebUI: Reporting||Horizontal marker don't show up in report snippets|
|Major||BVQ-15391||WebUI: Alerting||Unexpected behaviour when overwriting threshold defaults in predefined alert rules|
|Major||BVQ-15305||WebUI: Alerting||Predefined AR input fields don't accept floating numbers on English language systems|
|Minor||BVQ-15450||GUI: Table view||10GBit FC Ports (FCoE) not rendered properly|
|Minor||BVQ-15481||GUI: Table view||Exception on modifying tables when columns are hidden|
|Minor||BVQ-15388||GUI: Event view||Results for BVQ object types (e.g. Application) are not visible|
|Minor||BVQ-14784||GUI: Horizontal marker||Label background is sometimes not visible or set|
|Minor||BVQ-15419||WebUI: Alerting||Pre-filter in predefined alert rules don't work|
|Minor||BVQ-15378||WebUI: Reporting||Bugs in (SRS Capacity) Report|
|Minor||BVQ-15396||WebUI: Scanner config||Error message when trying to delete scanner and system from DB|
|Minor||BVQ-15455||License||GUI does not recognize license if runtime.validUntil is exact the same date as current date|
|Minor||BVQ-15454||License||Persist pre-execution check does not regard grace period|
|Minor||BVQ-14565||Maintenance Mode||Disable navigation between steps|
|Minor||BVQ-15458||Cisco||Restore on topo persist error uses SVC Cluster/SAN Agent instead of CISCO_DCNM|
|Minor||BVQ-15463||Brocade||Restore on topo persist error uses SVC Cluster instead of SAN_AGENT in PreExecution case|
|Minor||BVQ-15451||VMWare: Latencies||Normalization and Aggregation for VmScsiLunToVmHost and VmVirtualDiskToVmVmPerformance broken|
|Minor||BVQ-15457||VMWare||No pre execution checks during event persist|
|Minor||BVQ-15427||VMWare||Out Of memory exception during packaging of VMWare performance files|
|Minor||BVQ-15466||VMWare||Restore on topo persist error uses SVC Cluster instead of VM VIServer in PreExecution case|
|BVQ-14474||Performance Metrics||Add Peak values for VMware VM CPU % wait metrics|
|BVQ-14694||WebUI||Improve logging for FilesystemAccessCheck|
|BVQ-15311||WebUI: Predefined alert rules||Add additional SAN & SVC rules|
|BVQ-15313||WebUI: SystemsHealthMap||Improve descriptions|
|Major||BVQ-14668||GUI: Attributes||Node port attribute "attachment" does not show a value|
|Major||BVQ-15314||GUI: Chart||Different values in readout and chart if interval is set to 15 minutes|
|Major||BVQ-15302||GUI: Chart||Different values in readout and chart if moving average is enabled|
Different values in readout and chart for native interval
|Minor||BVQ-15266||GUI: Favorites||Alert & Event favorites open with change flag|
|Minor||BVQ-14970||WebUI: Alerting||CISCO Rules improvements|
|Minor||BVQ-15365||WebUI: Alerting||Links in predefined alert rules not working|
|Minor||BVQ-15273||WebUI: Alerting||Wrong conditions and description in predefined alert rule "VDisk compression efficiency low"|
|Minor||BVQ-15312||WebUI: Alerting||Fix units and description in predefined alert rules "Cisco Switch F-Port Utilization" & "Switch F-Port Utilization"|
|Minor||BVQ-15350||WebUI: Scanner||Event and Hftcs Persist events are counted as Scan events in scanner statistics|
|Minor||BVQ-15372||SVC: Persist||Unable to persist topology file|
|BVQ-14831||GUI||Enable SSL/TLS for mongoDB connection|
|BVQ-14608||GUI||Horizontal marker improvements|
|BVQ-15209||Licensing: Enclosure||Allow TiB licensing alternative to Enclosure based|
|Critical||BVQ-15283||WebUI: Alerting||Exception after trying to save alert rule in custom alert rule editor|
|Major||BVQ-15248||GUI: Event view||Filter not applied correctly|
|Major||BVQ-15236||WebUI: Scanner||VMware scanner fails with "The session is not authenticated"|
|Minor||BVQ-15187||VMware: Event scan||DuplicateKeyException when trying to persist VMware events|
|Minor||BVQ-15006||GUI: EventView||BVQ alerts for Drive (SVC) shows Tech type instead of SVC ID as Object|
|Minor||BVQ-15272||GUI: Eventview: Performance||Object Type tree incomplete|
|Minor||BVQ-15260||GUI: Favorites||Remove old Event favorite in System/Storage/SVC/Table views|
|Minor||BVQ-15186||GUI||NullPointerException in "General SVC performance overview"|
|Minor||BVQ-15264||GUI||TreeTable expand breaks undo / redo|
|Minor||BVQ-15246||WebUI: Reporting||Chart favorite without visible objects should render aggragte|
|Minor||BVQ-15224||WebUI: REST||JSON Parse error when rendered in FF|
Improve error message for invalid Notification configurations
|BVQ-14639||WebUI: Scanner Overview|
Link log download button to support package page
Allow storewizes to be licensed by enclosure
Change MEM_SWAPIN/MEM_SWAPOUT and corresponding PIs to swap in / out rate
Toleration support for vCenter Code level 188.8.131.52
|Critical||BVQ-15112||Topo Persist||SVC VDisk copy sync called to often and mdisk persist too slow in huge environments|
|Major||BVQ-15185||WebUI: Alerting||Exceeded memory limit for $group|
Cluster Deletion Tool should remove performance and event data
Wong condition in Alert rule "VM Disk group write low buffer free %"
|Minor||BVQ-15145||License||License not read with UTF-8 character set|
Misleading log messages about skipped objects persistence
|Minor||BVQ-15070||CLI Persister||SAN CLI Persist fails|
|BVQ-14432||VMware & Brocade||Receive Event log information via SNMP traps|
|BVQ-14934||GUI: Favorites||Split Event favorites|
|BVQ-14938||GUI: Event Favorites||Set default interval to 1d|
|BVQ-14903||WebUI: Scanner||Monitor status for local scanner process|
|BVQ-14797||WebUI: Alerting||Create default alert rules for CISCO|
|BVQ-14612||WebUI: Reporting: Templates: Topo table snippet: Sorting-Tab||Make attribute names unique|
|BVQ-14691||Common: SVC||Support for new IBM Spectrum Virtualize and FlashSystem models|
|Major||BVQ-15073||Brocade Persist||NPEs during Brocade perf persist|
|Minor||BVQ-14820||GUI||Adding a group of attributes to a table leads to different order of columns than in store|
|Minor||BVQ-14664||GUI||Exeception when trying to to save table with sanport_porttype-Filter|
|Minor||BVQ-14896||GUI||NPE when resizing TreeTable Column via double click|
|Minor||BVQ-14783||GUI||New Windows open in different sizes than the main window|
|Minor||BVQ-14953||GUI: Table view||Filter "Empty" cannot be saved|
|Minor||BVQ-14923||GUI: Table view||Filter become invalid after switching table mode|
|Minor||BVQ-14854||GUI: Topo view||Column filter does not work for "visible" column|
|Minor||BVQ-14874||GUI: Topo view||Isolate and Detail doesn't display object type names|
|Minor||BVQ-14868||GUI: EventView||View loads information for non-relevant object types (visible in progressbar)|
|Minor||BVQ-14889||Performance Indicator||BroadenedPerformanceDao.createBroadenPerformanceCalculator = false has no effect|
|Minor||BVQ-14941||WebUI: Alerting||Imported alert rules are not calculated|
|Minor||BVQ-14940||WebUI: Alerting: Custom Alert Rules||Alertrules with empty Filter in Selection cannot be activated|
|Minor||BVQ-14858||WebUI: Alerting: Predefined Alert Rules||Link in description not found|
|Minor||BVQ-14602||Grafana||Certain topo capacity metric are missing (e.g. SVC Cluster)|
|Minor||BVQ-14891||WebUI: Reporting||IllegalArgumentException when looping over chart type|
|Minor||BVQ-14749||WebUI: Reporting: Report List||Reports based on "invalid" templates aren't marked as invalid|
|Minor||BVQ-14928||WebUI: Scanner||Reuse of scanner name after deletion and server restart fails|
|Minor||BVQ-14592||WebUI: Support Package||Add version.txt and mongodb logs|
|BVQ-14816||Grafana: VMware||New 'VMware - Cluster overview' Dashboard|
|BVQ-14781||SVC||Add support for new drive tech_type "tier_scm"|
|BVQ-14620||Cisco||Be able to link a physical Switch to a Room/Site|
|Major||BVQ-14832||Server: Licensing||Cisco ports are not counted|
|Major||BVQ-14826||Server: Persist: Cisco||ObjectNotValidException|
|Major||BVQ-14726||WebUI: Reporting: Performance Chart||Filter Help for Perf Chart OT missiung|
|Minor||BVQ-14818||GU||Context Menu on tab header causes exception|
|Minor||BVQ-14842||GUI||Exception when trying to change metric color|
|Minor||BVQ-14841||GUI: EventView||Unable to check an unchecked checkbox|
|Minor||BVQ-14679||GUI: Properties: Table tab||PI metric selections missing|
|Minor||BVQ-14836||WebUI: Reporting||Configured charts and tables don't react to loop snippets|
|Minor||BVQ-14808||WebUI: Alerting||System Rule lowNumberOfCompressedVDisksUsedIOGroup uses wrong attribute|
|Minor||BVQ-14802||Grafana: Cisco||Full_qualified_name is "name"|
|BVQ-14465||GUI||New system favos for Cisco|
|BVQ-14603||GUI||Loading views is too slow|
|BVQ-14535||GUI: Dot notation: Attributes||Ease chooser usage|
|BVQ-14692||GUI: Dot notation: Attributes||Change sort & filter mode attribute handling|
|BVQ-14636||GUI: Dot notation||Technical Name should be shown consistent in table header tooltips|
|BVQ-14658||GUI: Favourites: VMware||Enrich existing VMware favourites with additional attributes|
|BVQ-14558||GUI: Table view||Show Object type and Attribute name in table header in two rows for tables in flat mode|
|BVQ-14686||GUI: Favorites||Add horizontal markers to existing Favorites|
|BVQ-14433||Scanner||Scan Brocade events via SNMP|
|BVQ-14606||VMware||Add attribute names for VM SCSI volume (vm_scsilun)|
|BVQ-14780||SAN||Some switch port attribute descriptions need to be improved|
|BVQ-14365||Alerting: Cisco||Create default alert rules for CISCO|
|BVQ-14588||Alerting: VMware||Add predefined alert rules for VMware|
|BVQ-14791||WebUI||Replace "Download logs" button with link to support package|
|BVQ-14769||WebUI||Improve some predefined alerting rules descriptiony|
|BVQ-14739||WebUI: Reporting||Several minor fixes and improvements|
Unable to save perf chart snippets for certain object types
|BVQ-14685||WebUI: Notifications||Add help information to email notification|
|BVQ-14683||Grafana||Add new Cisco Fabric overview & reworked dashboards|
|Critical||BVQ-14725||WebUI: Reporting: Snippet Loop||Cannot select an Atribute for Snippet Loop Headers|
|Major||BVQ-14674||WebUI||Unable to delete systems from DB|
|Major||BVQ-14675||GUI: Table view||Propeties panel opens with wrong tab|
|Major||BVQ-14701||SVC||PortType iSER leads to IllegalArgumentException during perf persist|
|Major||BVQ-14741||Grafana: Plugin||Dropdown entries are invisible|
|Minor||BVQ-14557||GUI||Metric-View Layout ignores empty spaces|
|Minor||BVQ-14569||GUI||View in multiview looses selection|
|Minor||BVQ-14706||Reporting||Loop Snippet does incorrect apply to TopoTableSnippet|
|Minor||BVQ-14757||Cisco/Brocade Switch port||sanport_speed = sanport_maxspeed although no device connected|
|Minor||BVQ-14660||Topology persist||controller_merge_id is null for disk array|