Table of contents


This guide describes how to prepare the BVQ Server, the BVQ Clients and the way to integrate the external systems. These has to be done before starting the BVQ installation

The actions to be performed are identified as follows:

  • (warning) Required action
  • (info) Optional action

ToDo list

ActionShort description
Procurement of license key filePlease obtain a valid BVQ license key file.
Check of the hardware and software requirements Please check, if the HW/SW of your systems corresponds to the descriptions under supported environments.
Adjustment of BVQ ServersPlease prepare the BVQ Servers for the installation of BVQ.
Adjustment of SVC/StorwizePlease prepare monitored IBM storage systems appropriately.
Adjustment of the VMware vCenterPlease prepare monitored VMware vCenter systems appropriately.

Gather information for BVQ Scanner configuration

Please prepare a list of all information needed to configure the BVQ Scanners.

Overview BVQ HW / SW components

Overview BVQ HW / SW components

Verification of hardware and software requirements

In the online document BVQ supported environments you find an overview of the hardware requirements and supported operating systems.
(warning) Please check if your systems fullfill these requirements

BVQ Servers

Preparation of the Windows operating system

The following tests and adjustments should be made:

Action                                                              Short description
AdministratorMake sure that the installation of all components is performed by a user who is a member of the local user group 'administrators'.  
RestartsMake sure that the system can be restarted (several times) without any problems during the installation phase.     
Network connections
Disk storageSet up the necessary drives, paths and partitions to the recommended sizes as described in adjust disk storage configuration.
Minimize UACMinimize the Windows User Access Control configuration prior to the installation as recommended under: adjust user account control (UAC)
Customize virus scanner        If necessary, please customize the configuration of an installed virus scanner on the BVQ systems (see customize virus scanner)
Time and time zonePlease ensure that the clocks on all BVQ systems and other integrated systems are synchronized and set to the same time zone (please see check time and time zone) 
Windows userMake sure that the necessary conditions for Windows users are met. 

Additionally required software                    

Install the additionally required software on the BVQ systems
Contribution of BVQ license key files      Please ensure that your BVQ license key file is available in the download directory of your BVQ server. It will be needed for the BVQ installation.

Check and unlock network connections 

BVQ Services require the network connections to communicate with each other, with BVQ Clients and  the external disk- and VMware systems.    

(warning) Please adjust the settings of any existing firewalls accordingly.

(warning) Please check any necessary network connection by using ping.

Overview: Network connections and ports

The following connections should or must be provided for each system:

Links / SystemStandard TCP portBVQ DB ServerBVQ ServerBVQ ClientDescription
RDP to BVQ Client3389(tick)(tick) ←(tick)Microsoft Remote Desktop Protocol for remote screen sessions
SSH to SVC System22 (tick)(question)Secure Shell to access the SVC CLI interface
WebService  to vCenter443 


 Web service with HTTPS on VMware vCenter API
SMI provider to BNA5989
SMI interface to Brocade Network Advisor
MongoDB27017(tick)(tick)(tick)Client to access the MongoDB service
BVQ Server Web UI80
(tick) ←(tick)Client acces to BVQ Server Web UI
BVQ Server Grafana3000
(tick)(tick)Cleint access to BVQ Grafana Dashbord Web UI
InternetN/A(question)(question)(question)Connection to the Internet for remote maintenance or code-download
Overview: Network connections

Legend: (tick) - necessary connection, (question) - optional connection, → - outgoing connection, ← - incoming connection


Notes to Microsoft RDP

The GUI's operation on a BVQ server with the redirection of the screen display to a workstation by using Microsoft Remote Desktop Protocol (RDP) is supported, but is associated with a loss of image quality and speed. Therefore, we recommend to use the BVQ GUI screen directly without any diversion. In Windows 2008 Terminal Services environments certain settings have to be considered before installation starts (enable user installation mode).

Please see: 

(error) The cascading of two or more RDP sessions in a chain one after the other affects the display performance of the BVQ GUI enormously and is therefore not supported!

Adjust disk storage configuration

BVQ Services require a different amount of disk storage capacity at different times for program files, program data  and log files. For the approximately required capacity, please refer to the relevant document under BVQ supported environments.    

To ensure that in case of a problem overflowing directories does not endanger the execution of other services, we recommend to distribute main directories on multiple partitions or drives.       


  • At least for the MongoDB data directory an separate drive or a separate disk partition (typical D:) should be created on a fast SAN storage system.        
  • It is recommended to create the directory D:\bvq_downloads and to gather all necessary files for installation there.


The following main Windows directories are used to a significant degree:

Main directoryStandard pathTypical standard pathStandard driveUsage
Program files%PROGRAMFILES%\SVA\BVQC:\Program Files\SVA\BVQC:Storage of program files
Program data%PROGRAMDATA%\SVA\BVQC:\ProgramData\SVA\BVQC:Storage of service logs and queue data
Program files%PROGRAMFILES%\SVA\BVQ\bvq-mongodbC:\Program Files\SVA\BVQ\bvq-mongodbC:Storage of MongoDB program files
Program data%PROGRAMDATA%\SVA\BVQ\bvq-mongodbC:\ProgramData\SVA\BVQ\bvq-mongodbC:Storage of MongoDB database
Overview: BVQ main directories

A significant use can also be expected for the following main directories on each system:     

Directory / systemBVQ DB ServerBVQ ServerBVQ Client
Program files(tick)(tick)(tick)
Program data (tick)(tick)
MongoDB Database(tick)


Overview: main directories per system

Adjust User Account Control (UAC)

UAC - User Account Control Windows 2008 R2, 2012, Vista, 7, 8:

Microsoft introduced Windows Vista User Account Control (UAC) in Windows platforms to avoid that all actions are performed with administrator privileges.  

(warning) For the installation of BVQ components it is recommended to set the UAC temporarily to 'Never notify' (reboot required).     
When finished, it can be reseted to the previously set level. 


 How-To - Changes in the dialog 'UAC Manager'
  • Start UAC dialogue:
    • Either: start → execute/search field → enter: uac
    • Or: start → system control → path field → enter: system control\user accounts\user accounts → click 'Change settings of User Account Control'
  • Set control to lowest level 'Never notify'
  • After installation is finished reset control to original or desired value.

Customize virus scanner

(warning)  During the installation of BVQ disable any virus scanner or other programs which vary from the basis Windows installation and might interfere with the installation.

The virus scanner on the BVQ server should be set so that the following directories are NOT searched:

Database Directory

Note: Problems has been observed in context with the virus scanner 'Sophos', which could be relevant for others too.

Check time and time zone

The time and time zone of the BVQ systems have to be set properly.

(warning) Please check whether a NTP server is configured in Windows: it is strongly recommended to use a NTP server to synchronize all clocks of all systems (SVC nodes, Windows) .

(warning) Please check whether the time zone is set correctly: the time zone of all systems (SVC, Windows) have to be set to the same value.

Check Windows users

Locally managed users

The following users and groups are created during the BVQ installation on the BVQ server. This chapter does not contain any adjustments to be carried out here and just provides an overview.   

(info) Often the username 'BVQ' is shared for the BVQ Service and DB user. In this case, the name of the BVQ Server may not be 'BVQ' as both the server and the user name are managed in the same Windows namespace .

TypeNameMember ofDescription
User accountbvqLocal administratorsBVQ user account (Access and create the database, updates bvq database, BVQ Windows services)
User account (optional)bvqservice BVQ Windows services run under this user account

Users managed by active directory

If a domain registration is used, the database and the BVQ User must be created in advance on the AD server.
The following table provides an overview of the required users and their user groups in active directory.



Member of


User account


Domain user, local administrators

BVQ user (Access and create the database, updates bvq database, BVQ Windows services)


Additional required software

The following overview shows which software is required on the BVQ systems:

Software / SystemBVQ DB ServerBVQ ServerBVQ Client
Java Runtime Environment (tick)(tick)
Microsoft Excel 2016
PuTTY (question)(question)
PDF Reader (question)(question)
Remote Screenshare(question)(question)(question)
Overview: additionally required software per system

Legend: (tick) - required software, (question) - optional software

BVQ installation packages

Download files

Please download the following software from the Internet on the BVQ ServerBVQ installer

Java Runtime Environment (JRE)

An Oracle Java Runtime Environment version 1.8.x 64 bit with most current patches has to be installed as the main system JRE on the BVQ server, database server and the clients.

JRE 32/64 bit versions overwrite each other

Internet browsers usually run as 32-Bit versions. If they are used to install a JRE, they auto-download a 32-Bit version and overwrite a 64-Bit system java. Please ensure to reinstall a 64-Bit JRE afterwards.


The installed version of Java and the existence of the java.exe in the system path can be checked by using the following command:

Check your java settings
C:\>java -version
java version "1.8.0_xx"
Java(TM) SE Runtime Environment (build 1.8.0_xx)
Java HotSpot(TM) 64-Bit Server VM (build xx, mixed mode)

Microsoft Excel

Microsoft Excel 2016 or later has to be installed on the BVQ Server to be able to create advanced BVQ Reports with that. BVQ Excel based reports are connected to the BVQ Server's REST endpoint via MS PowerQuery, which is embedded in Excel since version 2016. You can automate the creation of such Reports by using MS Powershell and Windows Scheduler. Please ask your BVQ Support Partner for more information.

PuTTY (optional)

 Click here to expand...

PuTTY is an optionally required free Secure Shell (SSH) terminal console. It is used to perform commands in the SVC CLI  .

Usually PuTTY is installed  on the BVQ Server and, if necessary, also on the client workstations. 

In a BVQ environment the following added values are offered with the installation and configuration of PuTTY:        

  1. PuTTY allows independent assessment of the SVC connections on the BVQ server and, if necessary, also the test or adaptation of SVC parameters.
  2. The pogram PuTTYgen  allows the user to create a SSH private/public key pairs, which may be needed for the configuration of the BVQ Scanner.
  3. A user may use pre-configured PuTTY sessions from the BVQ GUI, to adjust the configuration of SVC resources (see also Cluster CLI scripts).

For a working call out of the  BVQ GUI the following configuration steps have to be executed: 

(warning) Please attach the PuTTY directory  to the system search path %PATH% an (typically: ;C:\PROGRA~2\PuTTY ).

Can be configured in computer → properties advanced system settings Advanced → environment variables → user variables→ path

(warning) Please create a PuTTY session for each SVC / Storwize cluster  with the same name as the cluster (from lssystem name,  please note upper / lower case).

The following parameters have to be defined in PuTTY to connect to an SVC Cluster:

    • Category: session
      • Host name (or IP address) = IP address or DNS entry for the relevant SVC cluster 
      • Port = 22
      • Connection type = SSH
      • Saved sessions = name ot the relevant SVC Cluster
    • Category: connection -> aata
      • Auto-login username = bvq
    • Category: connection -> SSH -> auth
      • Private key file for authentication = select a SSH private key file.
    • Back to category: session
      • Click button 'save' in order to store settings permanently

During the first connection the error message that the SSH fingerprint has not been saved in the registry can occur. This has to be confirmed once with 'Yes'.

Remote Screenshare (optional)

 Click here to expand...

If you grant the BVQ support team a controlled access to a screen session on your BVQ systems, support for you and the BVQ team is greatly simplified. Answers for questions or errors can be found much faster and unnecessary back and forth sending of e-mails is avoided.

We recommend the installation ofl the software 'TeamViewer' on one or more BVQ systems which have access to the Internet. As a result, you can enable the BVQ support to work together with you on the local screen. TeamViewer can be downloaded from the Internet with the following link:

Some companies prohibit communication with the TeamViewer server (in Germany) by a firewall. In this case please contact your network administrator.


IBM Spectrum virtualize (SVC), Storwize & Flash systems

The following checks and adjustments should be made to the SVC / Storwize systems:

ActionShort Description
Configuration of SVC userPlease create a user account (typically 'bvq') within the group 'Administrators'.
Check SSH access for free sessionsPlease check whether 3 SSH sessions are free on each involved system in order to ensure communication with the BVQ SVC scanners.
Check time and time zonePlease check whether an NTP server and the same time zone are set on each involved system as well as on the  BVQ systems.
Check performance statistics intervalPlease check the settings of the performance statistics  on each involved system (default: 5 minutes).

Configuration of SVC user

For the communication of the BVQ SVC Scanner with the SVC CLI a user account on each SVC is mandatory, which should be at least member of the group 'Administrator'.

(warning) Please create such a user. We recommend that to give that user the following name: bvq

The user authentication can be only done via password SSH key pair  authentication is no longer supported by BVQ)

  • Creation of an SVC user with password for BVQ with SVC CLI:

    svctask mkuser -name bvq -usergrp Administrator -password P@ssw0rd

  • Creation of the BVQ user with SVC Web GUI:
    1. Please Browse with a web browser to the following URL: https://<cluster ip address>/gui#users-users
    2. Log in with a user in the group SecurityAdmin (superuser)
    3. Click on 'Create User" and fill in the following dialogue as following
    4. If you have chosen an authentication via SSH key pair, you can upload the public key in this dialogue.

*Unfortunately, the performance monitoring of an SVC / Storwize cluster without the permission level 'Administrator' is not possible so far as for copying the performance statistics files from the other nodes into the config node the CLI command svctask cpdumps is mandatory. This is the only administrator-level command, which uses the BVQ SVC scanner. For all other commands (svcinfo lsxxx) the permission level 'monitor' would be sufficient. 

Check SSH access for free sessions

The number of simultaneously opened SSH sessions is limited in the SVC/Storwize to 10 sessions for SVC Code < v7.5 (32 sessions >v7.5) . If the sessions are used by other applications, it should be ensured that for a short time up to 3 SSH sessions are simultaneously required for the communication with the BVQ SVC Scanner.

Check time and time zone

The time and the time zone of the SVC/Storwize systems have to be set correctly.

(warning) Please check if an NTP server is configured: we strongly recommend to use an NTP server to synchronize the time of all systems (SVC Nodes, Windows). 

CLI command for setting an NTP server:
svctask chcluster -ntpip <IP address of NTP Server> ### Example: svctask chcluster -ntpip

(warning) Please check whether the time zone is set correctlythe time zoneof all systems (SVC, Windows) should be set to the same value. 

CLI command for setting the time zone (here Europe/Berlin):
svctask settimezone -timezone 360 ### Timezone 360: Europe/Berlin !!!

(warning) At the end please check  whether  the expected time is actually displayed.

CLI command for showing the cluster time:
svqueryclock ### Check the cluster's current date and time

Check performance statistics interval

The SVC performance statistics are generated regularly (in intervals) by the SVC and picked up by the BVQ SVC Scanner. BVQ supports all intervals possible in the SVC (1min to 60min). We recommend to set the time interval to 5 minutes. If a closer monitoring should be necessary, the interval can also be reduced to 1 minute.

(warning) Check the interval time set in the SVC / Storwize. Example:

svcinfo lssystem | while read key value; do [[ "$key" =~ ^(statistics_status|statistics_frequency)$ ]] && echo "$key $value"; done
statistics_status on
statistics_frequency 5

(warning) Set the statistics interval time:

svctask startstats -interval 5 ### Set SVC Perf Statistics Interval (possible values 1-60)

(warning) Clear old performance statistic files on all nodes. It is not certain that they were created at the same point in time or they may contain no longer existing nodes.

svcinfo lsnode -nohdr | while read id rest ; do svctask cleardumps -prefix /dumps/iostats $id ; done

Configure a Unified Storwize V7000

The V7000u system consists of 2 levels:

  1. The upper level provides a file service gateway (file nodes)
  2. The lower level consists of a V7000 (storage nodes)

The administration of a V7000u is usually done by using the IP addresses of the file service gateways. CLI commands are tunneled through that layer to the underlying V7000. Unfortunately, the performance statistics of the V7000 cannot be downloaded from this upper level . Hence cluster IP addresses have to be assigned to the underlying V7000.

(warning) Check whether a cluster IP address is set there on the V7000u:

cluster_id       cluster_name location port_id IP_address   subnet_mask   gateway       IP_address_6 prefix_6 gateway_6
00000200A080006A swv1blk      local    1
00000200A080006A swv1blk      local    2

(warning) If necessary, set a cluster IP address on the V7000u:

chsystemip -clusterip -gw -mask -port 1

Similar to a usual V7000 the BVQ SVC Scanner has be configured  to access this IP address.

VMware vCenter systems

VMware vCenter user

For the operation of BVQ VMware Scanner, a user is required for the operation of the BVQ VMware Scanner, who should at least have read-only access to the VMware vCenter system.

(warning) Please create this user before installing the VMware BVQ Scanner. We recommend to name the user as follows: 'bvq'

VMware vCenter statistic settings

With BVQ version 5.6 it will be possible to scan performance data for VMware objects (virtual machines, ESX hosts, etc.) within BVQ. No setting changes are required for a default setup.

(warning) Data rate metrics for VM Datastores are not delivered on default statistic level 1. To gather the data rate you should increase the 5min statistic level to at least "Level 2".

 How to change the statistic interval
  1. Log in to the vCenter web client (https://DNS_or_IP_of_vCenter_server) with an administrative user
  2. Navigate to the vCenter settings

    Select: vCenter → Configure tab → Settings - General  → Statistics
  3. To collect VMware Datastore data rate metrics the 5 minutes interval duration must be set to statistics level 2 - You can check the current settings in the table (screenshot shows correct configuration)
  4. To modify click "Edit" top right
  5. Within the next dialogue you can set the statistics level to 2 within the drop down menu

    Tip: Check the required database size required by configuring the physical hosts & virtual machines. Depending on the selected configuration, this will show you an estimate of the db size (filesystem space required on the vCenter server).
    (warning) Maybe you have to modify the vCenter filesystem size to collect/save the additional performance data.
  6. Click OK to save the settings
  7. Check the changes within the overview table (see 2.) →  5 minutes interval duration must be set to statistics level 2

vCenter CPU usage during BVQ performance scan

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.

Brocade SAN Scanner

Important Requirement: a separate system/server is needed to run the Brocade SMI Scanner

Brocade SAN Switch user

For the operation of BVQ Brocade SAN Scanner, a user is required on the SAN core switch.
The user
should at least have "Operator role" and AOR (Areas of Responsibility) =All Fabrics, All Hosts.


(warning) Please create this user before installing the BVQ Brocade SAN Scanner. We recommend to name the user as follows: 'bvq'

Gather information for BVQ Scanner configuration

BVQ scanners need the following information to be configured for each System.

In addition to the BVQ licensed IBM Spectrum virtualize systems (SVC), BVQ Scanners should also be configured for each BVQ supported backend system behind them. Such Systems are already covered by your BVQ license and can be added without additional cost, but be aware to have them included in your BVQ license key file.

For each IBM storage system:

For a VMware vCenter system:

  • No labels