Hypervisor VM Identification in Fibre Channel SANs
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current virtual machine (VM) hypervisors do not provide effective visibility and management of VMs in storage area networks (SANs), leading to difficulties in resource allocation, chargeback, and quality of service (QoS) management, especially when using VMFS or CSV-based systems.
Innovation Solution
The hypervisor provides VM identification, priority, and LUN/LBA range information to the host bus adapter (HBA) or network interface, which creates a table for VM identification and priority mapping, using a unique identifier in Fibre Channel headers to facilitate fabric-wide handling and improved management.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of information
If NPIV features are used to identify VMs on SAN, then VM visibility is improved, but management complexity increases
Solution Approach 1:
The patent introduces an intermediary mechanism (VM identification module in HBA) that translates VM identities into Fibre Channel headers without requiring NPIV. This mediator enables SAN visibility while simplifying management by handling VM identification transparently at the HBA level rather than requiring complex NPIV configuration.
2Ease of operation
If VMFS is used for easier VM administration, then ease of operation is improved, but VM identification capability on SAN is lost
Solution Approach 1:
The patent segments the VM identification function from the storage management system (VMFS) and places it in the HBA's firmware. This segmentation allows VMFS to continue providing easy administration while the HBA independently handles VM identification and insertion into Fibre Channel headers, preserving both ease of operation and identification capability.
3Productivity
If individual VM management is implemented, then chargeback and QoS are improved, but zoning complexity increases
Solution Approach 1:
The patent implements self-service by enabling the HBA to automatically insert VM identities into Fibre Channel headers without manual configuration. This automation provides the VM-level visibility needed for chargeback and QoS while eliminating complex manual zoning, as the system self-configures based on VM identity information.
4Loss of information
If NPIV is used for VM identification, then VM visibility is improved, but scalability decreases
Solution Approach 1:
The patent creates a universal solution that works with both NPIV and VMFS configurations by implementing VM identification at the HBA level. This multi-functional approach allows the same mechanism to provide VM visibility across different hypervisor configurations and scales efficiently by handling identification in firmware rather than requiring complex software-based NPIV management.
Data Source
AI summary
A hypervisor preferably provides VM (virtual machine) identification, priority and LUN/LBA range information to the HBA (host bus adapter) when a VM is created. Alternatively, the HBA can determine that a LUN/LBA range is new and request VM identity, priority and LUN/LBA range from the hypervisor. The HBA creates a table containing the VM identification, priority and LUN/LBA range. The HBA then detects operations directed to the LUN/LBA range and does a lookup to determine VM identification and priority. VM identification and priority are then mapped into a field in a frame using a unique identifier. The unique identifier can be placed using reserved bits on the existing Fiber Channel (FC) header or can use bits in an additional header, such as a modified IFR header or an optional device header. The VM identification aware HBAs register with the NS.