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 complexities in zoning, quality of service (QoS) management, and chargeback mechanisms, especially when using VMFS or CSV file 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 the SAN, then VM visibility is improved, but management complexity increases
Solution Approach 1:
The patent introduces an intermediary mechanism (VM identification field in FCP commands and HBA mapping table) that translates between VM-specific identifiers and SAN addressing. This intermediary layer provides VM visibility without requiring complex NPIV configuration, as the HBA acts as a mediator between the VM layer and SAN layer.
Solution Approach 2:
The patent segments the VM identification function from the physical HBA configuration by allowing multiple VMs to share a single HBA port while maintaining individual VM identifiers in the FCP command stream. This segmentation enables VM-level visibility without requiring separate physical paths or complex zoning for each VM.
2Ease of operation
If VMFS is used for easier VM administration, then ease of operation is improved, but VM identification capability on the SAN deteriorates
Solution Approach 1:
The patent applies preliminary action by embedding the VM identification field in the FCP command structure before commands are sent to the SAN. The HBA is pre-configured with a mapping table that translates VM identifiers to SAN addresses, enabling VM identification to work seamlessly with VMFS without requiring changes to the file system operation.
3Loss of information
If individual VM management is implemented, then chargeback capability is improved, but QoS management complexity increases
Solution Approach 1:
The patent makes the VM identification field multi-functional by using the same field for both chargeback accounting and QoS prioritization. The unique VM identifier embedded in FCP commands serves dual purposes: tracking resource usage for chargeback and enabling quality of service differentiation, thereby improving both capabilities without proportionally increasing complexity.
Data Source
AI summary
A hypervisor preferably provides VM identification, priority and LUN/LBA range information to the HBA 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 either be placed using reserved bits on the existing Fibre Channel (FC) header or can use bits in an additional header, such as a modified IFR header.