This document is work in progress and not valid until further notice.
BVQ licensing overview
BVQ is licensed as a combination of BVQ editions and capacities entitlements:
|Editions & Packages|
Compute layer (VMs or LPARs)
Network layer (Ports)
Storage layer (TiB)
For very large installations, other licensing methods can be used that are mutually beneficial.
BVQ editions & packages
BVQ functionality is tailored to the typical needs of different infrastructure sizes and customer demands:
More information about the features of the different BVQ editions can be found here: BVQ Editions
|BVQ Enterprise edition||Full BVQ functionality: Monitoring, reporting, alerting & analysis|
Includes BVQ Connect package
|BVQ Entry edition||Major BVQ functionality: Monitoring, reporting, alerting|
BVQ capacity entitlements
The size of a BVQ managed environment is measured with capacity entitlements. Each BVQ edition has a specific price for one of the three following entitlement types related to an IT-infrastrucure layer grouping the platforms and their systems supported by BVQ. Entitlements are marketed in packages, that contain a specific count of entitlements.
|Layer||Entitlement||Package size||Supported platforms|
|Compute||Virtual machine count (VMs or LPARS)||25 VMs||Compute layer|
|Network||Port count (licensed Ports only)||100 Ports||Network layer|
Managed Storage capacity TiB count
Withdrawn: Installed enclosure count
|1 TiB||Storage layer|
Compute layer Virtual machine entitlements
BVQ license is validated against the total count of all Virtual machines or Logical partitions (VMs) configured of all systems monitored by BVQ. The count is independent from the online state or function of the VMs. IBM PowerVM VIOS are excluded from the count.
In case a BVQ OS Agent is used on a System that is already monitored via PowerVM HMC or VMware vSphere BVQ Scanners, no additional entitlement VM count is needed.
Support for the BVQ VMware package is discontinued since . There is a migration path from the old package to the new platform based licensing. Please ask your SVA contact for details.
Network layer Port entitlements
BVQ license is validated against the total count of all ports of all switches and directors monitored by BVQ, which are activated by a license of the device vendor. The count is independent from the online state or function of the ports.
Support for the BVQ SAN package is discontinued since . There is a migration path from the old package to the new platform based licensing. Please ask your SVA contact for details.
Storage layer Capacity entitlements
For the most storage systems the BVQ license is validated against the total count of managed storage pool capacity TiB of all systems monitored by BVQ. The count is independent from the online state or usage of the capacity.
Managed storage pool capacity is based on the amount of total capacity that is provided by the storage system pools that can be assigned to volumes, filesystems or metadata. This capacity is typical less than the gross raw disk capacity and less than the capacity after volume data reduction (compression, de-duplication, thin provisioning, ...).
BVQ licensing tries not to take care where data reduction takes place
- In case of volume data reduction: This does not affect the total managed capacity of the pools, so it does not affect the BVQ license.
- In case of pool data reduction: BVQ license is validated against the smaller physical allocatable capacity not the logical capacity.
- In case of drive level data reduction: BVQ license is validated against the smaller physical allocatable capacity not the logical capacity. This is currently only applicable for some systems. All other systems need to be licensed for the pool capacity as explained above.
BVQ respects drive level data reduction for the following systems:
- IBM Storwize family systems
- IBM FlashSystems
- In case of Thin Provisioned MDisks provisioned from BE Systems to the Storage virtualization layer (eg IBM Spectrum virtualize (SVC)), the sum of the physical capacity and the sum of the logical capacity is calculated and only the smallest of both results is counted.
The support of Thin Provisioned MDisks in the virtualization layer. is required for that. IBM supports that feature for a growing number of backend storage subsystems from IBM and other vendors.
BVQ licensing tries to keep storage virtualization layer transparent
In the storage virtualization layer, the managed storage pool capacity of storage pools provisioned by backend storage subsystems monitored and completely licensed by BVQ is not validated against the BVQ license. Otherwise, managed storage pool capacity of storage pools provisioned by backend storage subsystems not monitored by BVQ is completely validated against the BVQ license.
You can take the following advantages by including supported backend storage subsystems in your BVQ monitoring:
- This may decrease the amount of licensed BVQ capacity, in case data reduction takes place inside the backed subsystems .
- This provides deeper end-to-end monitoring expertise, without additional charge if the backend subsystem capacity is completely provisioned to the virtualization layer.
Example calculation (based on TiB)
|Backend subsystem||Virtualization layer||BVQ|
|BVQ monitored?||Drive physical|
|Pool physical capacity||Pool logical capacity||Volume logical capacity||pool logical|
|100||100||100||100||100||100||100||No data reduction at all|
Volume level data reduction in BE subsystem is respected by BVQ
Pool level data reduction in BE subsystem is respected by BVQ
|100||200||100||200||200||200||100||Drive level data reduction in BE subsystem is respected by BVQ|
|N/A (50)||N/A (100)||50||100||100||100||100||Drive level data reduction in BE subsystem not listed to be respected by BVQ|
|N/A||N/A||N/A||N/A||N/A (100)||100||100||No information from BE subsystem: Virtualization layer pool logical capacity counts.|
|100||100||100||100||100||50||100||Not all capacity of a BE subsystem managed by BVQ is provisioned to the virtualization layer: Total managed BE System capacity counts.|
|N/A||N/A||N/A||N/A||N/A (200)||100||100||Not all capacity of the BE subsystem is provisioned to the virtualization layer: Virtualization layer capacity counts.|
|N/A||N/A||100||N/A||200||200||100||Inline inquiry information from BE subsystem via Thin Provisioned MDisks:|
Pool level data reduction in BE subsystem is respected by BVQ
|N/A||N/A||200||N/A||100||50||100||Inline inquiry information from BE subsystem via Thin Provisioned MDisks, but|
not all physical capacity of the BE Pool is provisioned to the virtualization layer:
Pool level data reduction in BE subsystem is ignored by BVQ.
Storage layer Enclosure entitlements
This way of licensing is withdrawn from market since . Customers with an active BVQ license may still extend their systems with that type of license.
For eligible storage systems, the BVQ license is validated against the total count of all enclosures containing disk drives (controller an expansion enclosures). The count is independent from the online state of the enclosure.
The following storage systems are eligible for BVQ enclosure based licensing: IBM Storwize V5000, V7000, V7000F
- All Storwize systems' capacity below SVC is not eligible for enclosure based licensing.
- Standalone Storwize systems not attached to SVC, must be completely licensed by enclosure or be completely licensed by capacity entitlements. Partial entitlement intermix is not supported.