Compute_layer
Â
Â
IBM PowerVM
IBM PowerVM
A user is required for the operation of the BVQ PowerVM Scanner who should at least have read-only (hmcviewer) access to the HMC.
Please create this user before configuring the BVQ Scanner. We recommend to name the user "bvq"
Please open the user properties dialogue and select "Allow remote access via the web"
Enable performance data collection
BVQ can only collect performance statistics if "Data Collection" is enabled on the managed systems and all LPARs.
Â
Adjust System settings
Enable "Performance Monitoring Data Collection for Managed Servers"
To lower the system load and storage capacity usage on the HMC, we recommend to reduce the number of days to store performance data below the title "Performance Data Storage" to its minimum value of "1". BVQ takes over the role to store a longer history of that data.
Adjust LPAR settings
Switch on "Enable Performance Information Collection" on all LPARs
You can check the state of the "Performance Collection" enablement per LPAR easily. Run the following script on the HMC to show all LPARs without enabled collection:
bvq@hmc3:~> for SYS in $(lssyscfg -r sys -F name); do lssyscfg -r lpar -m $SYS -F name,allow_perf_collection ; done | grep ",0"
rju_viot,0
IOS74DHP,0
HABS74D,0
HAQS74D,0
HAMS74D,0
BVQ Scanner configuration
To configure a PowerVM scanner in BVQ the following information is required:
IP address or hostname of the HMC
User and password of the HMC user for BVQ
Starting with BVQ 2023.H1: Redundant HMCs managing the same systems must be configured in the same PowerVM scanner. Otherwise, the managed systems will appear twice in BVQ. Define the most powerful HMC first, because the order of HMCs determines the order in which they are scanned by BVQ. Additional HMCs managing other systems should be configured in an additional PowerVM scanner.
Up to BVQ 2022.H2: Typically, two redundant HMCs manage the same IBM Power systems. Please ensure that only one scanner is created for one of the HMCs to avoid duplication in BVQ.
Â
Â
Â
VMware vSphere
VMware vSphere
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. The read-only permission for the user must be defined at the vCenter level. Permissions in a lower level (e.g. Datacenter, Cluster, ...) will lead to scan errors.
Please create this user before configuring the BVQ Scanner. We recommend to name the user: bvq
Create or select the right user role
Go to user roles
Â
Â
Clone(1) the read-only role and store it as BVQ-Read-only (2) and add the following privileges (3)
Datastore - browse datastore
VM storage policies - view
Storage views - view
Â
Create the BVQ User for the vCenter
Â
Create the bvq user with the role "BVQ-read-only"
create it as vsphere.local or as AD user - please remember to add it correctly into the scanner dialog laterÂ
Add the user to the vCenter
Add the user to the vCenter, with its Role and do not forget to define it for all children
Â
Add the right vCenter Statistics
Interval duration has to be 5 minutes
Level 2 is sufficient for standard VMware
Level 3 should be used for VSANs
High vCenter CPU usage during BVQ Performance scanDuring 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.
Gather information for BVQ Scanner configuration
BVQ scanners need the following information to be configured for each vCenter system:
vCenter IP address or hostname
vCenter user domain
vCenter ID and password of the bvq user
Preparation for the BVQ Server
For BVQ Servers which are gathering information from NetApps and vCenters, the correct DNS configuration is important.
Make sure that the BVQ Server, NetApp systems and vCenters are in the same domain and have the same DNS server configured.Â
This is required to match the DNS-Name of the NFS Datastores to the corresponding IP Adresses of the NFS file shares on NetApp systems.
Â