Multi-Host HBA Consolidating Blade Server SAN Interfaces

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Modern server environments face limitations in data throughput due to the small capacity and link speeds of traditional host bus adapters (HBAs) in blade servers, despite advancements in storage area networks and server technology, leading to underutilization of network capabilities.

Innovation Solution

A multi-host HBA is connected to multiple host devices, providing an interface for multiple SAN hosts to a SAN fabric using PCI Express to Fibre Channel ports, eliminating the need for an on-board HBA on each host blade by directly interfacing with the bridge and processing commands and responses within the HBA.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Speed

If a dedicated HBA is installed on each host blade, then each host can independently access the SAN fabric, but the data throughput is limited by the small capacity and link speeds of traditional HBAs

Engineering Contradiction:
Improvedata throughputVSAvoidHBA configuration
Core Design Contradiction:
SpeedVSDevice complexity

Solution Approach 1:

Multiple host blades share a single HBA device in the blade chassis, consolidating what would traditionally be separate HBA components into one shared resource. This merging allows the system to achieve higher data throughput by utilizing the HBA's full capacity while reducing the number of individual HBA components needed.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The shared HBA serves multiple host blades simultaneously, performing the function of multiple dedicated HBAs through a single device. The HBA can handle I/O operations for multiple hosts through virtualization and command queuing, making it a universal interface that replaces multiple specialized components.

Inventive Principle:
Principle #6Universality (Multi-functionality)

2Productivity

If traditional HBAs with small capacity are used in each host blade, then device complexity is reduced, but the network capabilities remain underutilized

Engineering Contradiction:
Improvenetwork capability utilizationVSAvoidHBA capacity
Core Design Contradiction:
ProductivityVSQuantity of substance

Solution Approach 1:

By combining the HBA resources of multiple host blades into a single shared device, the system unlocks the full capacity and link speed potential of the HBA. This consolidation allows the network capabilities to be fully utilized rather than being constrained by multiple smaller, less capable individual HBAs.

Inventive Principle:
Principle #5Merging (Combining)

3Reliability

If each host blade has its own HBA, then independence and reliability are improved, but physical space and costs increase

Engineering Contradiction:
Improvehost independenceVSAvoidphysical space
Core Design Contradiction:
ReliabilityVSArea of stationary object

Solution Approach 1:

Multiple host blades share a single HBA physical component located in the blade chassis, dramatically reducing the physical space required compared to having a dedicated HBA slot in each host blade. This consolidation eliminates redundant hardware while maintaining functional independence through virtualization.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The shared HBA provides universal access to the SAN fabric for multiple host blades, delivering the same functionality that would require separate dedicated HBAs. Each host maintains its own HBA software driver and logical interface, preserving independence while sharing the physical hardware resource.

Inventive Principle:
Principle #6Universality (Multi-functionality)

4Ease of operation

If dedicated HBAs are installed in each host blade, then host-specific configuration is simplified, but overall system costs and complexity increase

Engineering Contradiction:
Improvehost-specific configurationVSAvoidoverall system configuration
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

Each host blade maintains its own HBA software driver and logical configuration interface, preserving ease of host-specific operation. Meanwhile, the physical HBA components are consolidated into a single shared device in the chassis, reducing overall system complexity and the number of physical components that need to be managed.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentUS7669000B2Host bus adapter with multiple hosts
Publication Date: 2010.02.23 AVAGO TECHNOLOGIES INTERNATIONAL SALES PTE LTD
  • US7669000B2 patent drawing
  • US7669000B2 patent drawing
  • US7669000B2 patent drawing

AI summary

A multi-host host bus adapter (HBA) can be connected to multiple host devices to allow the multiple host devices to communicate on a SAN fabric. More specifically, the multi-host HBA provides an interface for multiple SAN hosts without necessitating an HBA on each host, eliminating the need for an on-board HBA on each SAN host. The multi-host HBA interfaces to memory in each SAN host to which it is connected using PCI-Express (or a similar protocol), and communicates with other devices on the SAN fabric using Fibre Channel ports. The multi-host HBA communicates by receiving a command from a connected host, forwarding the command to a processor in the multi-host HBA, and sending the command to a device on a SAN. When the multi-host HBA receives a response from the device on the SAN, the multi-host HBA associates the response with the process and sends the response to the host.