Systems Health Map: Usability improvements and additional functionalityThe Systems Health Map in this release has a lot of improvements for easier usage and quicker insight to potential issues in your environment: - additional presentations of alert rule results: by platform, by severity, by system category or by user category
- possibility to limit the Systems Health Map to selected systems only
- possibility to exclude multiple alert rule results at once and optionally add comments
- copy the contents of the alert rule result table to clipboard for easy import into Excel or other tools
- save timeframe- and autoplay-setting across sessions
Each alert rule result can be analyzed by a only a few clicks. Expert knowledge and the BVQ GUI are not necessarily required to find the root cause of a problem. It's as simple as that: - Select the alert rule of interest from the Systems Health Map
- Select the object which should be investigated further
Now you can find all information about this object: - Summary - Why and when did this object change its status?
- Topology changes - Which attribute has changed in the selected timeframe and possibly led to the object change? Additional attributes can be added to or removed from the table.
- Performance - What was the performance of the selected object at the time of the incident? Additional metrics can be added to the chart or new charts added. Use the "Go to incident"-button to cover the time of the latest state change in your chart.
Alerting: Usability improvements and additional functionalityConfiguration, creation and usage of alert rules in BVQ has also been improved in this release. Predefined alert rules now have a clone function. The rule will now be opened in the advanced editor for further modification:
Alert conditions in an alert rule created with the advanced editor can be cloned as well:
The Categories-tab provides additional functionality: - Click on any user or system category to see which rules are part of it.
- Click on "Rule assignment" to add rules to a category or to remove rules from it.
Generic SAN model Anchor |
---|
| Generic SAN model |
---|
| Generic SAN model |
---|
|
BVQ supports two different Fibre Channel Switch vendors - Brocade and Cisco. And for Brocade SANs, there are two ways of collecting the data - via Brocade Network Advisor (BNA) or REST API directly from the FC switches. This makes three different platforms and object models in total. In this version of BVQ, a generic SAN model has been introduced which combines all three BVQ platforms into one. The following table shows all object types which are available as generic SAN object types and their translations into the specific platforms.
| Generic OT | Brocade | Brocade (Deprecated) | Cisco |
---|
Fabric | SAN Agent | Brocade Agent | Brocade Agent (BNA) | Cisco DCNM |
---|
| SAN Fabric | Brocade Fabric | Brocade Fabric (BNA) | Cisco Fabric |
---|
| SAN Switch | Brocade Switch | Brocade Switch (BNA) | Cisco Logical switch |
---|
| SAN Switch port | Brocade Switch port | Brocade Switch port (BNA) | Cisco LSwitch port |
---|
| SAN Physical switch | Brocade Chassis | Brocade Chassis (BNA) | Cisco Switch |
---|
| SAN ISL | Brocade ISL | Brocade ISL (BNA) | Cisco LISL |
---|
Nodes | SAN Node | Brocade Node | Brocade Node (BNA) | Cisco Node |
---|
| SAN Node port | Brocade Node port | Brocade Node port (BNA) | Cisco Node port |
---|
Zoning | SAN Zone | Brocade Zone | Brocade Zone (BNA) | Cisco Zone |
---|
| SAN Zone member | Brocade Zone member | Brocade Zone member (BNA) | Cisco Zone member |
---|
Further Enhancements
Anchor |
---|
| Further Enhancements |
---|
| Further Enhancements |
---|
|
WebUI tables improvementsSeveral usability improvements are part of this release: - Every table in the WebUI has a search box
- Alert rules are hyperlinks. Clicking on an alert rule name opens the result details for that rule
- Everwhere in the WebUI alert rules display their configuration details. Hover over the question mark to see all information for the selected alert rule
SVC Host cluster supportA host cluster is a group of logical host objects that can be managed together. Volumes mapped to a host cluster are shared by every host in this cluster. This feature, released in SVC version 7.7.1, is now available in BVQ as well. We have introduced a new object type called "SVC Host cluster". |