New SAN package
The BVQ SAN Package is a complete new extension package for BVQ. It introduces support for Brocade SAN switches and directors. It enables you to interactively explore your SAN configuration and check it for issues, chart SAN Switch port performance and error metrics, create reports about port utilization and drill through all the layers between SVC, BVQ, and VMware objects in end to end views.
Similar to all other available BVQ add on packages, its licensing is based on the capacity of a licensed primary system platform (Spectrum virtualize (SVC), Storwize, ...). Please review the BVQ License Information Page or ask your sales contact for more information.
To collect information a BVQ SAN Scanner needs to be configured to connect to a Brocade SMI/S Provider, which can be enabled as part of a Brocade Network Advisor (BNA). There is an issue with the Brocade SMI provider and the tracking of changes, so we strongly recommend to use the free (headless) Brocade SMI provider separately or at least to switch off "Track changes" in the BNA. See Supported environments and BVQ server requirements for more details and the supported versions of the Brocade SMI provider.
Supported SAN objects
This first version of the BVQ SAN Package supports basic elements of a SAN environment. The following overview depicts the elementary relationships of these objects and their link to connected BVQ objects:
Where to find SAN objects?
Similar to all other objects, they show up in the BVQ Path browser inside the view property panel or can be opened as a Table from the Favorite browser. All SAN objects can be combined in an end to end relation to all other objects.
|SAN objects in view Path browser||SAN object Table views in BVQ Favorites|
|SAN Agent||The SMI Provider gathering information for the monitored SAN Devices|
|SAN||The SAN to which the monitored SAN Fabrics belong to. Only routed SANs will contain more than one SAN Fabric in a SAN.|
|Part of a SAN, that contains one or more interlinked (logical) SAN Switches.|
|SAN Switch||Represents a logical SAN Switch configured inside a physical SAN Switch or Director as part of a SAN Fabric.|
|SAN Chassis||Represents the physical SAN Switch or Director. A BVQ Room connected to a BVQ Site can be configured for it.|
|SAN Switch port||Fiber channel Port of a SAN Switch. This can be physically cabled to a SAN Node port or to a SAN Switch port of another Switch.|
|SAN Trunk||Multiple SAN Switch ISLs can be bundled to a SAN Trunk to improve the performance an availability of a Switch to Switch connection.|
|SAN ISL||Interconnection between two SAN Switch ports to bind another SAN Switch into the same SAN Fabric. Multiple ISLs can be grouped to a SAN Trunk|
|SAN Node port||Fiber channel port inside a SAN attached device (host, storage system, ...) connected to a SAN Switch port. BVQ directly connects them to gathered Ports of BVQ monitored storage systems.|
Primary identifier: World Wide Port Name (WWPN)
One or more ports physically places inside the same device show up in a SAN Node.
|SAN Platform||A configured FDMI driver of a SAN Node device can deliver more helpful information about the system driving the SAN Node ports (e.g. Hostname, Device driver Version).|
BVQ displays the full set of all reported attributes for each supported SAN object. Be aware that only a subset of configuration parameters is reported by the Brocade SMI provider. In addition, BVQ calculates counters for each grouping object, so that their number of grouped objects are known. For example a SAN Fabric knows how many SAN Switches it contains, how many SAN Switch ports they have and how many of them are connected or free for use. Please explore the BVQ SAN Table view favorites to get an impression of the most important attributes.
Performance and error metrics
The BVQ SAN Package gathers all SAN Switch port statistics delivered from the Brocade SMI provider. Similar to all other statistics, you can simply drill into a chart with the statistics related to an object with a simple click on the SAN entry in the context menu of this object:
That opens our well known BVQ Chart view, where you can select statistic metrics in the selection panel. The following screenshot shows the full set of available metrics in the expert tab:
These are the available SAN Switch port statistics in more detail:
|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|
|Frame rate||Rx||Frames/s||Received frame rate|
|Frame rate||Tx||Frames/s||Sent frame rate|
|Frame rate||Rx+Tx||Frames/s||Overall frame rate|
|Frame rate||Rx%||%||% received of total transferred frames|
|Frame size||Rx||Byte||Framesize received|
|Frame size||Tx||Byte||Framesize sent|
|Frame size||Rx&Tx||Byte||Weighted 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|
Buffer credit wait
|%||%||Buffer to buffer credit zero wait %|
|Frame discards||RxTO||Frames/s||Frame timeout rate in receive buffer|
|TxTO||Frames/s||Frame timeout rate in transmit buffer|
|Other||Frames/s||All other frame discards not due to a timeout (unreachable, zone misses, unrouteable ...)|
|Offline sequences||Rx||Count/s||Offline sequences receive rate|
|Offline sequences||Tx||Count/s||Offline sequence send rate|
|Offline sequences||Rx+Tx||Count/s||Overall offline sequence rate|
|Link resets||Rx||Count/s||Link reset receive rate|
|Link resets||Tx||Count/s||Link reset send rate|
|Link resets||Rx+Tx||Count/s||Overall link reset rate|
|Encoding Errors||In||Count/s||Rate of encoding errors inside frame|
|Encoding Errors||Out||Count/s||Rate of encoding errors outside frame|
|Encoding Errors||In+Out||Count/s||Overall Encoding error rate|
|CRC||GEOF||Count/s||Rate of CRC errors with good End Of Frame (EOF) delimiter|
|CRC||Overall||Count/s||Rate of all CRC errors|
|Invalid ordered sets||Rx||Count/s||Invalid ordered set rate|
|Errors||Protocol||Count/s||Protocol error rate|
|Errors||Address||Count/s||Address error rate|
|Errors||Delimiter||Count/s||Delimiter error rate|
|Errors||Too long||Count/s||Rate of too long frames|
|Link errors||LF||Count/s||Link failure rate|
|Link errors||LSY||Count/s||Loss of sync rate|
|Link errors||LSI||Count/s||Loss of signal rate|
You can find a collection of use cases on the BVQ SAN Package (Brocade) page.
|SAN Routing||Toleration support only. Full Feature support can be added to a later release|
|SAN Zoning||Will be added in the next major release|
|SAN Access gateway||Will be added in the next major release|
|SAN Director blade||Limited support. Currently the blade slot number is unknown. This will be added in one of the next releases.|
|SAN NPIV||Limited support. Full feature support will be added in the next major release|
|Separate SMI Provider||Recommended. A problem in the SMI provider of current BNA versions prohibits its use in combination with BNA change tracking.|
New alerting engine
With version 5.5 BVQ got a whole new alerting engine which replaces the old module functionality completely.
New key features:
- Web UI to visualize alerting results
- Flexible object selection to avoid manual mappings
- Alert conditions based on topology attributes and all available performance indicators
- Alert rule creation possible from the Web UI and the Classic GUI
- New notification concept with new additional options
Alerting Web UI
The new Alerting Web UI is available via the BVQ-Server and splitted into two main areas Overview and Manage alert rules
- Overview: Get an overview of the current and historical alert levels for all alert rules, one specific alert rule or even one specific object
- Manage alert rules: Create, edit, delete or organize your alert rules
Manage alert rules
Alert rules can be created and edited form the Web UI and Classic GUI and require some configuration in different sections.
|Name||A user defined name for the alert rule. It should express the usecase for this rule.|
The object type is the base object, all alert conditions are applied on.
From the viewpoint of the Classic GUI it can be seen as the last object in the path.
|Default alert level||If no alert condition matches in this rule, the default alert level is applied as current state (typical value: OK).|
|Fallback alert level||If conditions can't be calculated the fallback level is applied as current state. This might happen, if there are missing performance values (typical value: Unknown).|
|Enabled||Only enabled alert rules will be calculated.|
To define a subset of objects, the alert rule should be applied to it is possible to add multiple selection definitions. Each definition will be applied to a specific object type.
The selection actually is a topology filter in the Treemap and utilizes the powerful functionality of the enhanced filtering options.
It's possible to add multiple alert conditions with different alert levels and filters to one alert rule.
Alert conditions are always evaluated top → down end exit with the first match.
One alert rule can contain multiple report configs. Per default there is a Default alerting file you can choose as report type (Notification). You can create your own Notifications and choose them as report type. All level changes are published to this Notification config and handled accordingly.
Using the From and To level, it is possible to define dedicated alerts. A notification will only be send if the level changes.
Define the execution schedule for this alert rule using Cron syntax.
|Comment||Allows to add documentation about this alert rule|
With this version we introduce a new concept to notify the user. Use the BVQ Web UI to configure all its options, like Notification configurations, Email servers, log filenames and others. You give each Notification configuration a specific name, by which it can be reused in any Alert rule.
Although the notifications are only used within the alerting right now there are many plans for the near future to use this concept for different usecases.
The Email server can be used in multiple notification configurations. For that you need to give it an unique name.
A Notification configuration defines how the notification should be delivered. The settings vary in detail based on the selected type.
At this time we support the following notification types:
|Email server, sender, recipient||You can add multiple receiver addresses using a ; as seperator|
|File||Filename||The filename should already include the output extension (xxx.log)|
|Slack||Slack webhook URL||https://api.slack.com/incoming-webhooks|
SVC 8.2 & IBM FlashSystem 9100 support
On July 10th, 2018, IBM has announced the next generation FlashSystem product built with Spectrum Virtualize capabilities. The FS9100 is running SW version 8.2.0. BVQ is ready to scan and support both, the new hardware and the new software. This support was added in BVQ v5.5.2
SVC 7.6 & 7.8.1 feature support
SVC 7.6 - Distributed RAID (DRAID) support
A new type of RAID has been introduced in SVC v7.6 - Distributed RAID (DRAID).
While traditional RAID arrays have one or more dedicated spare drives which are idle unless an active member in the array fails, DRAID arrays have so called rebuild areas which means there is no dedicated spare drive and all drives in the array can do I/O.
DRAIDs have two major advantages over traditional RAID arrays: greater throughput and a massively reduced rebuild time in case of a drive failure.
There are a bunch of new attributes related to DRAID which can now be displayed in the Detail Pane for Object Type "Drive Array".
SVC 7.6 - Hyperswap & Remote Copy integration
When creating a volume on an SVC cluster configured in Hyperswap topology, four VDisks are created:
- one "master" VDisk
- one "auxiliary" VDisk which is in an active-active remote copy relationship with the "master" VDisk
- two change volumes which are flash copy targets for "master" and "auxiliary" VDisk
All new SVC attributes related to the new feature are now included in BVQ.
To make it easier to find out which VDisks belong to a volume, BVQ displays the master's volume name (instead of its own VDisk name) followed by a suffix indicating the use of the VDisk. The names of related FC mappings are displayed in a similar way:
|VDisk display name||FC map display name|
|M||Master VDisk||M>MC||Master to Master change|
|A||Auxiliary VDisk||A>AC||Auxiliary to Auxiliary change|
|MC||Change volume for master VDisk||MC>M||Master change to Master|
|AC||Change volume for auxiliary VDisk||AC>A||Auxiliary change to Auxiliary|
Some examples for RC relationships, FC mappings and related VDisks:
The same name-suffix-logic also applies to VDisks and FC mappings of GMCV relationships (Global Mirror with Change Volumes):
SVC 7.8.1 - Port Congestion Performance Statistics
Some additional SVC FC node port congestion statistics became available in SVC v7.8.1 which are helpful to explore problems between SVC and SAN. Prior to SVC v7.8.1 (which means 8GB FC HBAs), metric Buffer credit zero wait % (BBCZ) has always been helpful but this metric is no longer reported by 16GB (and newer) FC HBAs. To cover this gap, IBM developed this new congestion statistic set which is available for FC port types. Please refer to the IBM documentation for more details about them. Especially Transfer congestion > Normal > Blocked int % is the most comparable to Buffer credit zero wait % and has the same meaning: % of measured interval blocked due to congestion.
The new congestion statistics can be found in the metric chooser's Basic- and Expert-Tab of object type "SVC Node Port":
|Basic Port congestion statistics||Expert Port congestion statistics|
New menu to add table columns
Adding columns to a table is now much easier than in earlier releases because a new menu allows you to select multiple attributes at once. All attributes available for the selected object type including their description and CLI notation are listed in this new menu. Just right-click on the table header column and select "Table columns". The new menu opens and you can simply add one ore more new attributes by single-clicking on the check-box or double-clicking anywhere on the selected row.
|Open the Table columns configuration panel from the table menu||Table columns configuration panel in the view's properties|
Enhanced Chart Context Menu
The chart context menu which open on a right click on the chart background has been made more user friendly. More actions can now be performed via a single menu:
- use Timing to select a different time interval
- choose Metrics to change, add or remove metrics
- go to Objects to select the objects that should be charted
- adjust Drawing options if required
- select General to change the path to display different object types in a different hierarchy
Path Base Charting (PBC) in Object Context Menu
Path Based Charting was introduced in v5.3 (see v5.3 Introduction of PBC), continued in v5.4 (see v5.4 Enhanced PBC) and completely replaced the old chart view consistently in this release. Now a PBC view also opens, when called from the Object Context Menu. A so invoked PBC view opens with the chart in the top section and a table section showing all contained objects below it. A path is preselected for that view, that only contains
/BVQ/<chosen object type>. As usual, only the "Aggregated" object visible, but in a PBC view, the leading path element "BVQ" has taken over this role. The chosen object type path element is also filtered to only contain the objects that had been selected before the context menu was opened. To change the visibility of your objects, use the new Chart > Objects dialog in the view's properties or the Chart visibility menu options in the object context menu.
|Call a PBC from Object Context Menu||Change object visibility in View Properties||Change visibility in Object Context Menu|
Object specific actions in Table view
In previous releases, a all cells of a row in a Table view only behave as the primary object. For example, a double-click anywhere in the row opened the Detail pane for the given object of that row. In this release, all cells showing references to other objects allow specific action on these. For example, a double-click on such a cell will open the Detail pane for this object. Its Object Context Menu also offers specific actions (change chart visibility, call PBC, select it in another view, ...). A cell that supports that feature shows the object's name underlined.
Improved BVQ Server Web UI
The BVQ-Server Web UI has been migrated to a new CSS Framework (VueJS). In this process we improved many details and reorganized some pages.
- The old scanner overview showed a state based on the last task of a scanner or persist, which could lead to confusing results if tasks are executed in different schedules. For each task we now made a visual representation.
- Scan and persist duration with their histograms have been moved to a separate screen. Click the status button to get to the new overview.
- The log button disappeared. To view the logs you can just click the green/red button for each state of a scanner.
Reduced Sidebar Navigation Entries
- Some top level navigation links in the sidebar are now grouped an a more appropriate Administration or Support group
- Host, Database, Cache and Heap Information are now grouped in a new "System Information" page
Requirements and restrictions
Requirements of the HW/SW environment
Minimum BVQ version required for an update
V5.1.0 (without Data Migration)
|Recommended Java Runtime version|
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-, Alerting- and Scheduler-services and also all GUIs and reporting-clients
- 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 Alerting 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-3722||Common||Integration of SAN system components|
|BVQ-10139||GUI||Path integrated Perf-View|
|BVQ-12598||Server||BVQ Notification Config|
|BVQ-10172||Common: SVC 7.6||Distributed RAID (DRAID) support|
|BVQ-10173||Common: SVC 7.6||Hyperswap & RC enhancement integration|
|BVQ-12077||Common: SVC 7.8.1||Add new port congestion perfstats|
|BVQ-12975||GUI||GUI: Add possibility to open a DP from a table cell referencing another DataObject|
|BVQ-13036||Perf: DAO||Create combined DAOs via annotation processor|
Reports should not have default names
|BVQ-11592||Alerting||Enable sending test Email|
|BVQ-12629||Alerting 2.0||Add Fields to AlertRule and AlertReportConfig|
|BVQ-12989||GUI: Chart Context Menu||Apply more options to "save as"|
|BVQ-11100||GUI: Chart view||Restructure chart context menu|
|BVQ-12182||GUI: Chart view||Time legend: Add duration|
|BVQ-12960||GUI: Favorites||Extend favorite menu|
|BVQ-12104||GUI: Favorites||Enhance save dialog with some file & folder operations|
|BVQ-12832||GUI: Favorites||Improve Favo Manager Window handling|
|BVQ-13032||GUI: Perf||Create/Update basic metrics panel|
|BVQ-4073||GUI||Reload DB button should open cluster selection dialog|
|BVQ-13074||GUI||Remove "At least 1 scanner has an error!"-toaster|
|BVQ-13080||GUI:Table View||Add table column selection to Property panel|
|BVQ-12556||GUI||View-Properties: Add Forwards / Backwards buttons to title bar|
|BVQ-12633||Grafana||Preserve configuration and dashboards during update|
|BVQ-9624||Scanner||Scan SVC Cluster partnership via "lspartnership"|
|BVQ-12703||Server||Lower priority of Report generation vs Scan|
|BVQ-12710||GUI||Update/Modify/Change/Improve Attribute Descriptions|
|Critical||BVQ-13137||GUI:Topology View||MDisk groups missing after path change|
Filter mode: Topology counter filter are Text instead of Int
|Major||BVQ-13138||GUI:Table View||NULL objects shows no name in column "object"|
|Major||BVQ-12916||GUI||DataReductionPools: Topology Persist:NumberFormatException|
|Major||BVQ-10978||GUI:Docking||Faulty restore after maximizing within a floating frame|
Attribute IO density leads to StackOverFlowException
|Minor||BVQ-12420||DataGrid||CRUD of objects blocked by PI load|
|Minor||BVQ-11393||GUI||Floating Frames do not center title in freespace between menu and buttons|
|Minor||BVQ-12168||GUI||Floating the last Single View of a window leads to non-dockable floating window|
|Minor||BVQ-12961||GUI||JFreeChart 1.5.0 migration|
|Minor||BVQ-11702||GUI:Multi View||Favorite ignores minimized Single Views|
|Minor||BVQ-12272||GUI||Optimistic Locking not for all editable Object Types|
|Minor||BVQ-12982||GUI:Filter||No parser available for strings starting with numbers|
|BVQ-13073||Common: Data Reduction Pools||Add new Unmap/Data Reduction perfstats|
|BVQ-12927||Web UI||New Web UI with improved usability|
|BVQ-13058||GUI||Display port type for controller and host|
|BVQ-13216||GUI||Enable "Chart visibilty", "Isolate" and "Select subelements" in link-object context menu|
|BVQ-13065||GUI||Favorite menu usability impovement|
Main menu: Favorites: Alert rules: Add functions
|BVQ-13259||Common||Remove metrics for SVC code level 7.2|
|BVQ-13198||Common||Rename SAN Performance Metrics|
|BVQ-13057||Common||SVC 8.1.2: Support efficiency type of vdisks in DR pools|
|BVQ-13212||Common||SVC: Rename Change VDisks according to Master/Auxiliary VDisks|
|Critical||BVQ-13282||GUI: Table||Flipping Column widths with enabled auto compact|
|Critical||BVQ-13273||GUI: PBC||Charts don't show different objects with same name|
|Critical||BVQ-13298||GUI: PBC||Selection in chart not always hits the right object in table|
Division by zero-Exception when opening "General Performance Overview"
|Major||BVQ-13263||GUI||Handle view saving dosen't work correct|
Change flag not triggerd by most changes in tables
|Major||BVQ-13254||GUI: Favorite||Analytic Multi-Views don't show up in object context menu|
|Major||BVQ-13257||Alerting||MDisk group selection filter cannot be added to an alert rule|
|Major||BVQ-13244||Alerting: Editor||Be able to commit "Add selection" dialog with only the Aggregate flag set|
SAN scan fails because of different folder structure
|Major||BVQ-13292||Persister||SAN: Persist error parsing date "CEST" with german syslang|
Historical Reports unable to render if cluster id changed
|Major||BVQ-13287||BVQ-Server||Shutdown during SRS Capacity Report rendering|
|Minor||BVQ-13270||GUI||Delete discovered systems doesn't support SAN|
|Minor||BVQ-13153||GUI||NPE when closing the last MV-frame in a floating window|
|Minor||BVQ-13182||GUI||Select managed systems dialogue doesn't show vCenter systems properly|
|Minor||BVQ-13227||GUI: Table||Auto compact flips back after closing property sheet|
|Minor||BVQ-13276||GUI: Table||Column attribute chooser: Column "Object" can be removed|
|Minor||BVQ-13068||GUI: Chart||Spikes in LineCharts if 2 data points are very close|
|Minor||BVQ-13340||GUI: Chart||Contest menu: Save as PNG missing|
|Minor||BVQ-13250||GUI: Detail pane||32 GB Port speed not shown correctly|
|Minor||BVQ-13309||Grafana||"Node detail" dashboard has a fixed timing|
|BVQ-13375 & BVQ-13386||Common: SVC||Add support for new FlashSystem FS9100 and SW level 8.2|
|BVQ-13136||GUI: PBC Properties||Add tab "Chart objects" with visibility controls|
|BVQ-13150||GUI: Detail pane||All tab should have preference before Alert tab|
|BVQ-13412||GUI: PBC Perf view||"Chart visibility": Add "This layer" entry|
|BVQ-13387||GUI: Property panel: Charting||Restructure Tabs|
|Blocker||BVQ-13400||GUI: Properties: Chart|
Metrics Dialog empty if PBC is calld by OCM
Unable to migrate DB from 5.5.1 to a later version
|Critical||BVQ-13280||GUI: SAN||Path /BVQ/SAN Agent/SVC Node displays incorrect information|
|Critical||BVQ-13395||SAN: Scanner||Persister runs on error parsing Date/Time of some attributes|
Config files not deleted if moved to another instance
|Major||BVQ-13238||GUI||CPU Core Chart displays values > 100%|
|Major||BVQ-13410||GUI: Chart visibility||"Manage" doesn't always open proper tab in Properties Panel|
|Major||BVQ-13394||GUI: Perf-View: SAN Switch Port||BCW% shows values > 100%|
|Major||BVQ-13310||GUI: Table view||Columns can't be switched back to unsorted|
|Major||BVQ-13361||SAN||Topology and performance file cleanup incorrect|
|Major||BVQ-12858||SVC Persister||Persisting of topology data fails with "Update operation not valid! enclosure_id must not be null!"|
All User-Favorite not working after update
|Minor||BVQ-13378||GUI||Exception: "Found 5 DockableNode but 6 DockingState"|
|Minor||BVQ-13315||GUI||Broken alignment in detail for new PI metrics|
|Minor||BVQ-12876||MongoDB Installer||Error creating user on mongodb|
|Minor||BVQ-13384||Server||MongoDB Schema migration fails|
|Minor||BVQ-12901||Repo Installer||GUI not starting after update|
Pre installation checklist
- BVQ installation manual
- BVQ installation - questions and answers
- BVQ users manual
- Customize BVQ for IO heat map analysis (only needed for BVQ for SVC)
- Teamviewer - how to use it for remote control and meetings