HBA VM Identification Mapping for SAN Visibility
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 due to the individual nature of VMs and their NPIV addresses, 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 or optional device headers to simplify fabric-wide handling and enable improved management and chargeback mechanisms.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of information
If NPIV features are used to identify VMs on the SAN, then VM visibility and identification capability is improved, but device complexity and management difficulty increase due to individual VM operation requirements
Solution Approach 1:
The HBA acts as an intermediary between the VMFS file system and the SAN, translating virtual machine identifiers into NPIV addresses. The HBA receives VM identification information from VMFS, maps it to physical NPIV addresses for SAN communication, and maintains this mapping in a table, thereby enabling VM visibility without requiring individual VM configuration on the SAN side
Solution Approach 2:
The patent replaces the manual mechanical process of individually configuring each VM for NPIV with an automated software-based mapping mechanism. The HBA driver automatically translates VMFS virtual identifiers to physical NPIV addresses, eliminating the need for manual SAN zoning configuration for each VM and simplifying management
2Loss of information
If NPIV is used for VM identification, then VM visibility is improved, but ease of operation deteriorates due to individual VM management requirements
Solution Approach 1:
The HBA serves as a mediator that automatically handles the translation between virtual and physical identifiers. Administrators interact with VMs through the simplified VMFS interface, and the HBA automatically manages the complex NPIV address mapping and SAN communication, eliminating the need for administrators to manually configure each VM for NPIV
Solution Approach 2:
The system performs self-service by automatically maintaining the mapping between VM identifiers and NPIV addresses. The HBA driver automatically translates identifiers when VMs access SAN storage, eliminating the need for manual intervention in VM configuration and SAN zoning for each individual VM
3Ease of operation
If VMFS file system is used, then ease of administration is improved, but VM identification capability on SAN deteriorates
Solution Approach 1:
The HBA acts as an intermediary layer between VMFS and the SAN, translating the virtual identifiers used by VMFS into physical NPIV addresses that the SAN can recognize. This allows administrators to continue using the simple VMFS interface while the HBA handles the complex translation to enable VM identification on the SAN
Solution Approach 2:
The patent replaces the need for complex manual VM configuration with an automated software-based translation mechanism in the HBA driver. The driver automatically translates VMFS virtual identifiers to physical addresses, enabling VM identification without requiring changes to the simple VMFS administration interface
4Measurement precision
If individual NPIV addresses are assigned to each VM, then VM identification precision is improved, but device complexity increases for QoS and chargeback management
Solution Approach 1:
The HBA maintains a mapping table as an intermediary that stores the relationship between VM identifiers and NPIV addresses. This table enables precise VM identification through the mapping mechanism while simplifying QoS management, as the HBA can translate any VM identifier to its corresponding NPIV address and associated QoS parameters without requiring complex manual configuration
Data Source
AI summary
A hypervisor preferably provides VM (virtual machine) identification, priority and LUN/LBA range information to the HBA (hoist 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.