Download


Important

This is a "Family & Friends Release" to show new features in an early state. This release is not generally available and not ready for production yet. It is strongly recommended to run it in an BVQ test environment first.

To get the download links and more detailed information, please contact the BVQ Team: bvq@sva.de


  

Recent Version

 

Versions

VersionReleasedInstall Packages
5.612.10.2018All in OneGUI




Highlights


VMware Performance Package

Brief description

The BVQ VMware Performance Package is a new extension to the existing BVQ VMware package. It introduces support for VMware performance metrics and enables you to interactively explore your VMware configuration, check all kind of performance metrics and alert on metrics, create reports and drill through all the layers between SVC, BVQ, and VMware objects in end to end views.

As the new VMware Package will completely support a 'new' platform, customers will be able to use this VMware platform as a standalone solution. So you don't need to license IBM Spectrum Virtualize or Storwize (but a combination of both platforms are possible to get an end to end view of the environment). A combination of the SAN package with the VMware platform is possible, too.

Licensing

Customers using the current VMware package (topology & capacity data) will be able to upgrade to the new VMware platform now including performance data in addition.

The VMware platform is licensed by the number of VMs (virtual machines) running in the environment. Customers will have to license packs of 25 VMs (sum of VMs in the envrionment divided by 25 = number of packs to license) 

Please contact your SVA sales representative for pricing information.

Information gathering

To collect information a BVQ VMware Scanner needs to be configured to connect to a vCenter. If a VMware Scanner already exists to scan topology data, performance data collection can be enabled easily in the scanner configuration.


Important

During the BVQ performance scan of a vCenter server the CPU usage of the vCenter server will increase. Please monitor the vCenter server utilization depending on the workload to avoid performance degradation.
Maybe CPU or memory expansion is needed to be able to scan VMware performance data properly.
BVQ Installation: Preparation#VMwarevCenterSystemsVMwarevCentersystems


See Supported environments and BVQ server requirements for more details and the supported versions of the VMware vCenter versions.


Supported VMware objects

The first version of the BVQ VMware Performance supports most elements of a VMware environment. The following overview depicts the elementary relationships of these objects and their link to connected BVQ objects:

BVQ VMware performance stats object-types V1

Where to find VMware objects?

Similar to the already known VMware Topology package all available objects show up in the BVQ Path browser inside the view property panel or can be opened as a table from the favorite browser. All VMware objects can be combined in an end to end relation to all other objects.

VMware objects in view Path browserVMware object Table views in BVQ Favorites


 BVQ VMware object details
VM vCenter
VM Datacenter

VM Cluster


VM Host
VM SCSI volume
VM Datastore
VM Datastore cluster
VM Virtual disk
VM LUN
VM Virtual machine


VM SCSI volume 2 Host

Performance metrics

The BVQ VMware Performance Package gathers statistics delivered from the VMware performance API. 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 VMware entry in the context menu of this object:


That opens our well known BVQ Chart view, where you can select metrics in the selection panel. The following screenshots shows the full set of available metrics in the expert tab for each object type:

Important

This is a Family and Friends release.

Colors, namings and orderings might change slightly till the final release.


VM Host

 VM Host metric details

These are the available VM Host metrics in more detail:

GroupMetricUnitDescription

CPU

ms per stateWaitms/intervalTotal CPU time spent in wait state
ms per stateSwap waitms/intervalCPU time spent waiting for swap-in
ms per stateCo-stopms/intervalTime the host is ready to run, but is unable to run
due to co-scheduling constraints
ms per stateIdlems/intervalTotal time that the CPU spent in idle state
ms per stateReadyms/intervalTime that the host was ready, but could not get scheduled to run
on the physical CPU during last measurement interval

VM assignedTotalMHzTotal CPU capacity reserved by and available for virtual machines
VM assignedUsage (MHz)MHzCPU usage in megahertz during the interval
VM assignedReservedMHzTotal CPU capacity reserved by virtual machines

% UtilizationUtilization%CPU utilization as a percentage during the interval
(CPU usage & CPU utilization might be different due to
power management technologies or hyper-threading)
% UtilizationUsage%CPU usage as a percentage during the interval
Memory

VM memory reservation

ReservedGiBTotal amount of memory reservation used by powered-on
virtual machines and vSphere services on the host
VM memory reservationUnreservedGiBAmount of memory that is unreserved
VM memory reservationTotalGiBTotal amount of memory reservation used by and available
for powered-on virtual machines and vSphere services on the host
VM memory reservation% Reserved%
VM memory reservation% Unreserved%

Consumedby VMsGiBAmount of physical memory consumed by VMs on this host
ConsumedTotalGiBAmount of host physical memory consumed by a
virtual machine, host, or cluster

By typeGrantedGiBAmount of host physical memory or physical memory that is
mapped for a virtual machine or a host
By typeSharedGiBAmount of guest physical memory that is shared with other
virtual machines, relative to a single virtual machine or to all
powered-on virtual machines on a host
By typeActiveGiBAmount of guest physical memory that is being actively read or
written by guest. Activeness is estimated by ESXi
By typeActive writeGiBEstimate for the amount of memory actively being written to
by the virtual machine
By type% Active write%

SwapSwap inMiBAmount swapped-in to memory from disk
SwapSwap outMiBAmount of memory swapped-out to disk
SwapSwap usedMiBAmount of memory that is used by swap
Swap% Swap in%
Swap% Swap out%

% WaitComp/Swap%Percentage of time the virtual machine is waiting to access swapped or
compressed memory

TresholdLow free

GiB

Threshold of free host physical memory below which ESX/ESXi
will begin reclaiming memory from virtual machines
through ballooning and swapping
Fairness
CountCPUCount/intervalFairness of distributed CPU resource allocation on the host
CountMemoryCount/intervalFairness of distributed memory resource allocation on the host
Storage
Worst latencyDatastoremsHighest latency value across all datastores used by the host
Worst latencyDiskmsHighest latency value across all disks used by the host
Worst latencyStorage adaptermsHighest latency value across all storage adapters used by the host
Worst latencyStorage pathmsHighest latency value across all storage paths used by the host

Disk data rateRMiB/sAverage number of kilobytes read from the disk each second
during the collection interval
Disk data rateWMiB/sAverage number of kilobytes written to disk each second
during the collection interval
Disk data rateR+W (Usage)MiB/sAggregated disk I/O rate. For hosts, this metric includes the rates
for all virtual machines running on the host during the collection interval
Disk data rate% R%
VM Virtual machine

 VM Virtual machine metric details

These are the available VM Virtual machine metrics in more detail:

GroupMetricUnitDescription

CPU

ms per stateWaitms/intervalTotal CPU time spent in wait state
ms per stateSwap waitms/intervalCPU time spent waiting for swap-in
ms per stateCo-stopms/intervalTime the virtual machine is ready to run,
but is unable to run due to co-scheduling constraints
ms per stateIdlems/intervalTotal time that the CPU spent in an idle state
ms per stateReadyms/intervalTime that the virtual machine was ready, but could
not get scheduled to run on the physical CPU during
last measurement interval

UsageUsage (%)%CPU usage as a percentage during the interval
UsageUsage (MHz)MHzCPU usage in megahertz during the interval
Memory
UtilizationUsage%Memory usage as percentage of total configured or
available memory
UtilizationConsumedGiBAmount of host physical memory consumed by a
virtual machine, host, or cluster

By typeGrantedGiBAmount of host physical memory or physical memory
that is mapped for a virtual machine or a host
By typeSharedGiBAmount of guest physical memory that is shared with other
virtual machines, relative to a single virtual machine or
to all powered-on virtual machines on a host
By typeActiveGiBAmount of memory that is actively used, as estimated by
VMkernel based on recently touched memory pages
By typeActive writeGiBEstimate for the amount of memory actively being written to
by the virtual machine
By type% Active write%

SwapSwap inMiBAmount swapped-in to memory from disk
SwapSwap outMiBAmount of memory swapped-out to disk
SwapSwap usedMiBCurrent amount of guest physical memory swapped out to
the virtual machine swap file by the VMkernel
Swap% Swap in%
Swap% Swap out%

% WaitComp/Swap%Percentage of time the virtual machine is waiting to access swapped
or compressed memory

Balloon targetBalloon target

MiB

Target value set by VMkernal for the virtual machine's
memory balloon size

Storage
Worst latencyDatastoremsHighest latency value across all datastores used by the host
Worst latencyDiskmsHighest latency value across all disks used by the host

SCSI Disk data rateRMiB/s

Average number of kilobytes read from the disk
each second during the collection interval

SCSI Disk data rateWMiB/s

Average number of kilobytes written to disk
each second during the collection interval

SCSI Disk data rateR+W (Usage)MiB/s
SCSI Disk data rate% R%
VM LUN

 VM LUN metric details

These are the available VM LUN metrics in more detail:

GroupMetricUnitDescription
Traffic

IO rate

RIO/s

Average number of read commands issued per second
to the virtual disk during the collection interval

IO rate

WIO/s

Average number of write commands issued per second
to the virtual disk during the collection interval

IO rate

R+WIO/s

IO rate

R%%

Data rateRMiB/sRate of reading data from the virtual disk
Data rateWMiB/sRate of writing data to the virtual disk
Data rateR+WMiB/s
Data rateR%%

LatencyRms/IOThe average time a read from the virtual disk takes
LatencyWms/IOThe average time a write to the virtual disk takes
LatencyR&Wms/IO

Transfer sizeRKiB/IO
Transfer sizeWKiB/IO
Transfer sizeR&WKiB/IO

Outstanding requestsRcountAverage number of outstanding read requests to the virtual disk
during the collection interval
Outstanding requestsWcountAverage number of outstanding write requests to the virtual disk
during the collection interval
Outstanding requestsR+Wcount
Outstanding requestsR%%
VM vCenter

 VM vCenter metric details

These are the available VM vCenter metrics in more detail:

GroupMetricUnitDescription

System

Usage% CPU%CPU used by vCenter Server in user mode
UsageMemoryMiBVirtual memory used by vCenter Server
VM Cluster

 VM Cluster metric details

These are the available VM Cluster metrics in more detail:

GroupMetricUnitDescription

System

CPUTotalMHzTotal amount of CPU resources of all hosts in the cluster
CPUAvailableMHzTotal available CPU resources of all hosts within a cluster
CPU% Available%

MemoryTotalGiBTotal amount of host physical memory of all hosts in the cluster
that is available for virtual machine memory (physical memory for use by
the guest OS) and virtual machine overhead memory
MemoryAvailableGiBTotal amount of machine memory of all hosts in the cluster that is available
for use for virtual machine memory and overhead memory
Memory% Available%
VM SCSI volume 2 Host

 VM SCSI volume 2 Host metric details

These are the available VM SCSI volume 2 Host metrics in more detail:

GroupMetricUnitDescription
Traffic

IO rate

RIO/sAverage number of disk reads per second during the collection interval

IO rate

WIO/sAverage number of disk writes per second during the collection interval

IO rate

R+WIO/s

IO rate

R%IO/s

Date rateRMiB/sAverage number of kilobytes read from the disk each second during the collection interval
Date rateWMiB/sAverage number of kilobytes written to disk each second during the collection interval
Date rateR+WMiB/s
Date rateR%MiB/s

Transfer sizeRKiB/s
Transfer sizeWKiB/s
Transfer sizeR&WKiB/s

SCSIRes. conflictscountNumber of SCSI reservation conflicts for the LUN during the collection interval
VM Datastore

 VM Datastore metric details

These are the available VM Datastore metrics in more detail:

GroupMetricUnitDescription
Traffic

IO rate

RIO/sAverage number of read commands issued per second
to the datastore during the collection interval

IO rate

WIO/sAverage number of write commands issued per second
to the datastore during the collection interval

IO rate

R+WIO/s

IO rate

R%IO/s

Date rateRMiB/sRate of reading data from the datastore
Date rateWMiB/sRate of writing data to the datastore
Date rateR+WMiB/s
Date rateR%MiB/s

Transfer sizeRKiB/s
Transfer sizeWKiB/s
Transfer sizeR&WKiB/s


Performance Indicators (PI)

The VMware Performance Package also take full advantage of the new BVQ Feature: "Performance Indicators for all performance metrics" which enables the use of all performance metrics as PI.

This finally allows a PI based treemap sizing as well as the usage of PI in a table for VMware objects.


Thereby it is much easier to find "High Performer" and Bottlenecks.





SAN Zoning

The BVQ SAN Package which was introduced in version 5.5. has now been enhanced to support zoning. Once a valid SAN license is installed, advantage can be taken of this new feature.


The following Object Types have been added to the existing SAN Model:

  • SAN Alias
  • SAN Zone
  • SAN Zone member


A SAN Alias is a substitute name for a SAN Switch port (Port ID) or SAN Node port (WWPN). An Alias can contain one or more Port IDs and/or WWPNs.

A SAN Zone defines which devices are allowed to communicate with each other in an active zone set. It consists of multiple SAN Aliases, SAN Switch ports and/or SAN Node ports.

A SAN Zone member is one of those devices which is part of a zone.


FOS 7.4 and later supports a new zone type called Peer Zoning. It is based on WWPN zoning (Aliases are supported in FOS 8.1 and above) and defines a principal and its members within the zone. All members can communicate with the principal but cannot communicate with any other member in the same zone. This zone type is supported by BVQ as well.

Example: Path /BVQ/SAN Agent/SAN Fabric/SAN Zone/SAN Zone member/SAN Alias



Performance Indicators for all performance metrics

The concept of a "Performance indicator" (PI) is well-known in BVQ history to express a performance metric over a longer period of time inside a single value. These indicators have been available for some pre-selected performance metrics in the past.
With version 5.6 all available performance metrics are available as PI - no matter if originated from SVC, SAN or VMware.


 What is a Performance Indicator?

Performance metrics are collected in a specific interval and visualized as performance charts to observe the change in a specific time frame.

Performance indicators are an aggregation of this raw performance data for predefined time frames. BVQ distinguishes four different time frames for each PI.

NameShortcutTime frame
RealtimeRT<=5m
Short termST4h
Mid termMT1d
Long termLT1w

Each PI with it's corresponding time frame can be aggregated like a performance metric to provide performance indicators to grouping objects.


Performance indicators are very useful in different areas in BVQ:

  1. Performance based sizing in the topology treemap
  2. Performance values inside a table
  3. Performance based alerting


As the number of available performance indicators has been increased dramatically we changed the selection options.

Display PI inside a table

The way to select the PI you want to display within a table changed fundamentally.

Inside the properties panel the "Table tab" has been extended to hold a dedicated tab for each object type that is capable for it's performance data (1) and reachable by the last object in the topology path.

For each object you are able to select each PI from each timeframe (2). The PI selection pane is the same like the metric pane for performance charts and divided into the same groups (3).


Auto interval

Beside the fixed intervals it is also possible to select performance indicators from the "Auto interval" tab.

The "Auto interval" is bound to the PI timing setting for the treemap and will pick the time frame based on this setting.

Favorites with old PIs will loose functionality

User Favorites addressing legacy PIs in Filters or Table columns will loose functionalty, which depends on these PIs. The PIs inside such favorites are not migrated automatically. Please upgrade them manually.



Java 10 Migration

BVQ is no longer dependant on the Java version that is installed on the server and/or client it is running on.

With the release of BVQ 5.6, Java JRE is now bundled with BVQ which means it is part of the Repository and GUI installer packages. There is no need to install or up-/downgrade Java prior to installing BVQ because the correct Java version - Java 10 in version 5.6 - is delivered together with the product.

With the migration to Java 10 BVQ is able to use system resources much more efficient.





 

Requirements and restrictions 

Requirements of the HW/SW environment

Please see Supported Environments

Minimum BVQ version required for an update

V5.4

Known Issues

See https://customercenter.sva.de/home/x/NwwgAw
(support agreement needed to get access credentials)

 

Update from a previous MongoDB Installation step by step 

Important update notes

  1. BVQ license: A new license file may be required to use new modules/features.
  2. GUI favorites:  During a GUI update the predefined System favorites might get replaced. Possible user changes will be lost. However, changes in User favorites and All User favorites are kept.
  3. If you have problems: Please contact your BVQ support partner


  1. Preparations
    • Check for the correct function of the whole environmentin particular the function of the scanner.
    • Manual stop of BVQ Scanner- and Server-services and also all GUIs
    • Backup the BVQ installation directory and BVQ DB (e.g. DB backup with mongodump or VMware snapshots) 
    • Restart the BVQ Scanner
  2. Update BVQ Install Package Repository: bvq-package-repository-installer-x64-V5.6(.x).exe
    1. MongoDB update
    2. BVQ GUI update
    3. BVQ Server update
  3. Test the function of the BVQ environment.
  4. If necessary inform colleagues about the need to update locally installed BVQ GUI clients.  

 

Changelogs

 Version 5.6

Version 5.6

New features

Issue ID

Module

Description

BVQ-12929VMwareCollection and display of VMware performance statistics
BVQ-10564Performance IndicatorsAll PIs should be selectable in charts in all chart metrics should be PIs
BVQ-13119SANIntegrate SAN zoning in topology
BVQ-13217CommonBuild BVQ on Java 10


Improvements

Issue ID

Module

Description

BVQ-13260

GUI: Detail Pane

Improve handling of column width

BVQ-13423GUIImprove attribute descriptions for svc_name and volume_name
BVQ-13451GUI: Chart ViewSet inital Tab of property panel to "chart > metrics"
BVQ-13454GUI: PBCKeep non Isolate filters during PBC initalization & window refresh
BVQ-13461REST InterfaceRemove Enum Numbers
BVQ-13476GUIAdd SAN System Favorites

BVQ-13489

GUI: SANBVQ Qualified Attribute and Coloring missing
BVQ-13495GUI: Perf view: Properties: Metrics: SANAdjust some metric tooltip texts


Bug fixes

 

Issue ID

Module

Description

CriticalBVQ-13421Scanner

Scanner fails to persist FS9100 node performance data

CriticalBVQ-13474GUI: Multi ViewException after Window Refresh
CriticalBVQ-13422Attributes: SAN Port

"Is Connected" does not respect ISLs

CriticalBVQ-13459SAN

Path Trunk / ISL shows different Content than ISL / Trunk

Critical

BVQ-13494

GUI: Favorites

Exeption after open of favorite moved into new directory

MajorBVQ-13351GUI

Minimized SW leads to multple docking state exceptions if other view is changed

MajorBVQ-13392GUI

Trying to open a MV in a floating window leads to exceptions

MajorBVQ-13396Repository Installer

Not enough disk space: Log directory

MajorBVQ-13411GUI: Table View

Filter becomes invalid when adding/removing table columns

MajorBVQ-13444GUI Drive type table

IndexOutOfBoundsException: valid viewIndex: 0 <= index < 12 but was: -1

MajorBVQ-13446GUI: Editor: Disk typeEntered Name is not applied
MajorBVQ-13447GUIFilter comparison with "subelementcount" fails
MajorBVQ-13456GUILC Partition Performance chart displays incorrect data
MajorBVQ-13458GUI: TreetableClose of Table section leaves Property panel Table tabs open
MajorBVQ-13492GUI: Favorites: Edit info

Show in context menu no longer shows up

MajorBVQ-13493GUI: Perf view: Properties: MetricsFavo menu switching no longer works
MajorBVQ-13496GUIRight-click on SAN object in flat mode table leads to NPE
MinorBVQ-13069GUI: Properties: ChartProperties

Big Metric Panels are not displayed completely

MinorBVQ-13326GUI: LUN: Detail pane"LUN #" shows HEX instead of DEC value
Minor

BVQ-13356

GUI: FilterDataAttributeRenderer parsing values with wrong unit
MinorBVQ-13443GUIReload Topo Data doesn't display SAN Agents


Page viewed 137 times by 8 users since Oct 02, 2018

  • No labels