VM Identification Mapping in Fibre Channel SANs
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current virtual machine (VM) hypervisors do not provide adequate visibility and management capabilities in storage area networks (SANs), leading to difficulties in resource allocation, chargeback, service level agreement enforcement, and quality of service (QoS) management due to the individual nature of VMs and their NPIV addresses.
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 of VMs on the SAN.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
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 increases
Solution Approach 1:
The patent introduces an intermediary mapping mechanism that translates complex NPIV addresses into simplified VM identifiers. The HBA or SAN switch maintains a mapping table that correlates NPIV addresses with VM IDs, allowing the system to retain precise VM identification while presenting a simplified management interface. This intermediary layer decouples the complexity of NPIV address management from the visibility requirements.
Solution Approach 2:
The patent segments the identification system into multiple layers: physical host level, VM level, and SAN level. Each layer operates with its own identification scheme, allowing VMs to be identified precisely at the VM level using NPIV while enabling simplified group-level management at the host level. This segmentation allows different management granularities to coexist without conflict.
2Ease of operation
If individual VM management is implemented on the SAN, then VM-specific control and chargeback capability is improved, but scalability and management efficiency deteriorates
Solution Approach 1:
The patent implements a universal VM identifier that serves multiple functions simultaneously: it enables individual VM identification for chargeback, provides group-level aggregation for efficient management, and supports both detailed and summary reporting. The same VM ID infrastructure supports multiple management scenarios without requiring separate systems, thereby maintaining ease of operation while improving scalability.
Solution Approach 2:
The patent merges individual VM management capabilities with group-level management efficiency by implementing aggregation functions. The system can combine multiple VM identifiers into group identifiers, allowing administrators to manage collections of VMs efficiently while still maintaining the ability to drill down to individual VM-level control when needed. This merging reduces the management overhead proportional to the number of individual VMs.
3Ease of operation
If VMFS is used for storage management, then ease of administration is improved, but VM identification capability on the SAN deteriorates
Solution Approach 1:
The patent introduces an intermediary layer between VMFS and the SAN that translates VMFS-managed storage operations into SAN-recognizable VM identifiers. The HBA or SAN switch maintains mapping information that correlates VMFS file system operations with underlying VM identities, allowing VMFS to retain its administrative simplicity while restoring VM visibility on the SAN through the intermediary mapping mechanism.
4Productivity
If the environment scales up with more VMs, then resource utilization is improved, but management complexity and scaling difficulty increases
Solution Approach 1:
The patent implements a universal identification scheme that remains consistent regardless of environment scale. The same VM identifier structure and mapping mechanisms work whether there are 10 VMs or 10,000 VMs, allowing the system to scale up resource utilization without proportionally increasing management complexity. The identifier system is designed to be size-independent.
Solution Approach 2:
The patent implements dynamic aggregation and disaggregation capabilities that adapt to the scale of the environment. The system can dynamically adjust the level of aggregation in management operations, combining multiple VMs into groups for high-level management when the environment is large, while allowing easy disaggregation to individual VM level when needed. This dynamic behavior allows the management complexity to remain proportional rather than exponential with scale.
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.