Content

General note

For the application of BVQ, your environment has to meet certain requirements. Please check whether the components of your environment coincide with the requirements listed here.

  • Your BVQ Serves and clients need to meet some requirements about CPU, Memory, HDD capacity resources, and some software and networking prerequisites as well.
  • The monitored systems' hardware and software needs to be at a supported level.

Overview BVQ HW / SW components

Overview BVQ HW/SW components

BVQ Server requirements

Compute- and memory-resources

The suggested hardware dimensions are suitable for the environment dimensions listed below. For larger environments a customized HW dimension should be requested from your BVQ support partner.   

Small sized environments:

Server

CPU

RAM

HDD C: (free)

HDD D: (free)

LAN

GfX

BVQ consolidated server

3 GHz, 2 cores

6 GB

10 GB

20 GB

100 MBit/s

BVQ GUI client workstation

3 GHz, 1 core

4 GB

5 GB

100 MBit/s

DirectX 9 support

Medium sized environments:

Server

CPU

RAM

HDD C: (free)

HDD D: (free)

LAN

GfX

BVQ consolidated server

3 GHz, 4 cores

12 GB

20 GB

100 GB

100 MBit/s

BVQ GUI client workstation

3 GHz, 2 cores

6 GB

5 GB

 –

100 MBit/s

DirectX 9 support

Large sized environments:

Server

CPU

RAM

HDD C: (free)

HDD D: (free)

LAN

GfX

BVQ DB server

3 GHz,  4 cores

24 GB

10 GB

800 GB

1 GBit/s

BVQ server

3 GHz,  4 cores

16 GB

100 GB

 –

1 GBit/s

BVQ GUI client workstation

3 GHz,  4 cores

8 GB

10 GB

 –

1 GBit/s

DirectX 9 support

Consolidated: DB + server + client

3 GHz, 12 cores

48 GB

120 GB

800 GB

1 GBit/s

DirectX 9 support

Supported operating systems

The following table shows the supported operating systems and versions for BVQ servers and clients.

Operating system (English/German)

BVQ DB server

BVQ server

Consolidated (DB + server + client)

BVQ client workstation (GUIs)

Windows Server 2019(tick)(tick)(tick)(tick)
Windows Server 2016 64-Bit(tick)(tick)(tick)(tick)
Windows Server 2012 R2, 64-Bit(tick)(tick)(tick)(tick)
Windows 10, 64-Bit


(tick)
Windows 8.1, 64-Bit


(tick)

Windows 7, 64-Bit




(tick)

Microsoft Excel 2016
(tick)
(tick)

Virtual machines

The operation of the BVQ server on a VMware  VM is tested and fully supported.
Please consider: The response times of the BVQ application are depending on the total load of the VMware server. Other services and VMs which compete for the resources of the VMware server can cause congestion that leads to bad BVQ response times. Other server visualizations, such as Citrix XEN or Microsoft Hyper V have not been tested, but in other customer environments it has already been determined that such installations ran successfully.

Consolidation of BVQ components on a shared server

The BVQ SW modules (DB, Server, Remote Scanner, GUI) can be distributed across multiple servers or they can be operated on a single server. All combinations of BVQ services are supported. The response time of a such configured BVQ environment remains within the specification, as long as the above HW requirements are complied in sum. The conditions for the shared operating system have to be met for all  BVQ SW modules installed therein.

 

Access to the BVQ GUI via Microsoft RDP

The operation of the GUI on a BVQ server, but with a redirected screen which is displayed on a workstation by using Microsoft Remote Desktop Protocol (RDP), is supported. In this case declines in presentation quality and speed can be expected. The cascading of two or more RDP sessions in a chain (one after another) affects the display performance enormously and is not supported! It is recommended to install the BVQ GUI directly on the workstation to run it locally.         

In Windows 2008 Terminal Services environments certain settings have to be considered before the installation can be started (enable user installation mode).
Please see: http://www.techotopia.com/index.php/Installing_Applications_for_Windows_Server_2008_Terminal_Services

Monitored systems

IBM SVC code family systems: Spectrum Virtualize, Storwize, FlashSystems

Environment dimensions

The number of managed objects is crucial for the dimension of the BVQ server resources. The following categories of environmental variables can frequently be observed and can be managed in a single BVQ instance:

Objekt

Small

Medium

LargeMax *

VDisks

250

1.000

10.000

20.000

MDisks

60

250

2.500

5.000

Cluster

2

5

10

30

Hosts

25

100

1.000

2.000

* Note: larger configurations are possible, but have to be tested and adjusted specially. Please request support in such cases. 

Supported IBM Spectrum virtualize (SVC) code family systems


System type

BVQ support

min. BVQ versionLicensing
based on

Comment

SAN Volume Controller (SVC, except SA2/SV2)

yes

any

TiB

IBM Storwize V7000U

yes

anyEnclosure

 

IBM Storwize V3500
IBM Storwize V3700

yes

anyEnclosure


IBM Storwize V5000 Gen1
IBM Storwize V5000 Gen2

yes

anyEnclosure


V5010, V5020, V5030

IBM Storwize V7000 Gen1
IBM Storwize V7000 Gen2

yesanyEnclosure

IBM FlashSystem V840
IBM FlashSystem V9000

yes

anyEnclosure
IBM FlashSystem FS840
IBM FlashSystem FS900
yesanyEnclosureno performance stats gathered
IBM FlashSystem FS91xxyes5.5Enclosure / TiB
IBM Storwize V5000 Gen3yes5.7.2EnclosureV5010E, V5030E, V5100
SVC model SA2/SV2yes6.1.3TiB
IBM FlashSystem FS92xxyes6.1.3Enclosure / TiB

Storwize systems below SVC

Configurations with Storwize systems below SVC clusters are generally supported. All systems (SVC and Storwize) can be collected in one common BVQ DB.
An additional license purchase for the  capacity of Storwize systems mapped to a BVQ licensed SVC is not required. But such systems have to be added to the license key file to be discoverable by BVQ. Please ask your BVQ support team to extend your key file accordingly. Storwize systems themselves used for virtualization without any overlying SVC, will be configured as SVC clusters by BVQ and separate licenses have to be purchased for them.

Storwize V7000 Unified

Storwize V7000 unified code will be installed as a package consisting of fileservice- and V7000 code. Supported are all V7000u code versions that include V7000 code versions from the table below.

Supported IBM Spectrum Virtualize (SVC, Storwize, FlashSystem V9x & FS9x) & IBM FlashSystem 840/900 code versions

The following IBM Spectrum Virtualize code versions are supported. Compare also: SVC Microcode overview.

The following FS840/FS900 code versions are supported. Compare also: Flash system Microcode overview.

Spectrum Virtualize (SVC) / Storwize

Code version

BVQ support

BVQ version

Comment / Limits

<7.5.0.0

not supported

N/A

Out of IBM support (BVQ support on special request)

7.5.0.0 → 7.5.0.14supported3.4 → currentToleration support - Support of new V7.5 Feature: Local Hyperswap integrated in 4.1
7.6.0.0 → 7.6.1.8supported4.0 → currentToleration support - Support of new V7.6 Feature: DRAID integrated in 4.1
7.7.0.0 → 7.7.0.5supported4.1.1 → currentToleration support - Support of new V7.7 Features: NPIV Hosts, IO throttling planned for H2 2020
7.7.1.1 → 7.7.1.9supported5.0.1 → currentToleration support - Support of new V7.7.1 Feature: Host groups planned for later release
7.8.0.0 → 7.8.0.2supported5.0.2 → currentToleration support - Support of new V7.8 Features: Cloud tiering planned for later release
7.8.1.0 → 7.8.1.11supported5.2.7 → currentToleration support - Support of new V7.8.1 Feature: Port congestion stats integrated in 5.5
8.1.0.0 → 8.1.0.2supported5.4 → currentToleration support - Support of new V8.1.0 Feature: Hot spare node planned for H2 2020
8.1.1.0 → 8.1.1.2supported5.4 → currentToleration support - Support of new V8.1.1 Feature: Thin-Provisioned MDisks planned for H2 2019
8.1.2.0 → 8.1.2.1supported5.5 → currentToleration support - Support of new V8.1.2 Feature: Data Reduction Pool integrated in 5.6.3
8.1.3.0 → 8.1.3.6supported5.5 → currentToleration support - Support of new V8.1.3 Feature: Deduplication integrated in 5.6.3
8.2.0.0 → 8.2.0.4supported5.5.3 → currentSupport for FS9100 & V7000, no new relevant Features in V8.2.0.0
8.2.1.0 → 8.2.1.10supported

5.6.2 → current

Toleration support - Support of new V8.2.1 Features: NVMe + others planned for H2 2020
8.3.0.0 → 8.3.0.3supported5.7.1 → currentToleration support
8.3.1.0 → 8.3.1.1supported6.1.0 → current
All otheron requestN/A

Versions which are not mentioned above are considered as 'not supported'.
Please contact us
in this case!  
We reserve the time to test new versions internally first.


IBM FlashSystem FS840 / FS900

Code version

BVQ support

BVQ version

Comment / Limits

1.3.0.2 → 1.3.0.9supported4.0 → 5.4.0

 Tejas performance stats currently not gathered

1.4.0.7 → 1.4.0.10supported4.0 → 5.4.0
1.4.3.0supported4.0 → 5.4.0
1.4.4.0 → 1.4.6.1supported4.0 → 5.4.0
1.4.7.0supported5.4.1 → current
1.4.8.0supported5.4.1 → current
1.5.1.0 → 1.5.1.2supported5.4.1 → current
1.5.2.0 → 1.5.2.6supported5.4.1 → current
1.6.1.0 → 1.6.1.1supported5.4.1 → current
All otheron requestN/A

Versions which are not mentioned above are considered as 'not supported'.
Please contact us
in this case!  
We reserve the right to test unknown versions internally first.

VMware systems

Environment dimensions

The following categories of environmental dimensions can be managed in a single BVQ instance:

Object

SmallMedium

Large

Max *
vCenter1124
VMs502502.5005.000
VM virtual disks1005005.00010.000
VM SCSI LUNs1002502.5005.000
VM datastores1002502.5005.000

* Note: larger configurations are possible, but have to be tested and adjusted separately.

Supported software versions

The following VMware vCenter software versions are supported:


VMware version

BVQ support

BVQ version

Comment

<5.0

not supported



5.0

supported

2.8 → current


5.1supported2.8 → current
5.5supported3.4 → current
6.0supported3.5.4 → current
6.5supported5.0 → current
6.7supported6.0 → current
7.0supported6.1.4 → current

SAN systems

Environment dimensions

The following categories of environmental dimensions can be managed in a single BVQ instance. This is true for both SAN platforms, Brocade and Cisco:

Object

SmallMedium

Large

Max *
SAN SMI Provider1124
SAN Switches41664256
SAN Switch ports12851220488192
SAN Node ports12851220488192
Zones502008003000

* Note: larger configurations are possible, but have to be tested and adjusted separately.

Supported SAN systems and software versions

Brocade

All SAN systems and software versions supported by the Brocade Network Advisor version listed in the following table are supported.

Please refer to Network Advisor Release Notes available on https://my.brocade.com for a list of supported Switch Hardware & Software.

Recommendations:

  • Please use standalone headless Brocade SMI Agent
  • If using a standard BNA installation, please deactivate change tracking for all fabrics

     Deactivate change tracking

Tested Releases:

BNA version

BVQ support

BVQ version

≤ 14.4.1

unsupported


14.4.2

supported

5.5.2 or higher
14.4.3supported5.5.2 or higher


Known Limitations:

SAN Routingv5.5.2 has toleration support only.
SAN Director bladeLimited support. Currently the blade slot number is unknown.


Cisco

Performance and topology data for Cisco MDS switches is collected through the Cisco Data Center Network Manager (DCNM) using SMI-S.

Tested Releases:

DCNM version

BVQ support

BVQ version

11.1(1)

supported

6.1 or higher
11.2(1)supported6.1 or higher