Blade Server Network Address Auto-Configuration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In information handling system networks, replacing a blade server or FC HBA introduces a new WWN, requiring manual administrative changes on FC switches and storage arrays, leading to potential errors, expertise dependency, and delayed resource availability due to differences in network addresses.

Innovation Solution

A system dynamically allocates network addresses by applying a common network address seed to local information at each information handling system, using a management controller and network address generator to generate WWNs for networking components, eliminating the need for manual adjustments and ensuring seamless communication.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a replacement blade information handling system is introduced to the network, then hardware failure recovery is enabled, but manual administrative changes are required on FC switches and storage arrays

Engineering Contradiction:
Improvehardware failure recoveryVSAvoidmanual administrative changes
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The replacement blade server automatically performs network address configuration by retrieving the WWN from the failed server's FRU and applying it to its own HBA through the management controller, eliminating the need for manual administrative changes to switch zoning and array-LUN masking

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The management controller pre-configures the network address (WWN) for the replacement blade server by copying it from the failed server's FRU before the server is fully powered on, ensuring immediate network compatibility upon activation

Inventive Principle:
Principle #10Preliminary action

2Reliability

If manual changes to switch zoning and array-to-LUN masking are performed, then the blade information handling system can retain access to SAN storage devices, but administrative expertise and time are required

Engineering Contradiction:
ImproveSAN storage accessVSAvoidadministrative time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system automatically maintains SAN storage access by having the management controller copy the WWN from the failed server's FRU to the replacement server's HBA, which automatically updates switch zoning and array-LUN masking configurations without requiring administrative intervention

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The WWN is pre-configured in the replacement server's management controller before power-on, ensuring that SAN storage access is immediately established without waiting for manual configuration changes

Inventive Principle:
Principle #10Preliminary action

3Adaptability or versatility

If a new WWN is introduced to the network, then the replacement blade server can operate independently, but network communication is disrupted until reconfiguration

Engineering Contradiction:
Improveindependent operationVSAvoidnetwork communication restoration
Core Design Contradiction:
Adaptability or versatilityVSSpeed

Solution Approach 1:

The management controller pre-configures the WWN in the replacement blade server before it is powered on or connected to the network, ensuring that network communication is immediately restored upon activation without disruption or reconfiguration delays

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS7953827B2System and method for dynamic allocation of information handling system network addresses
Publication Date: 2011.05.31 DELL PROD LP
  • US7953827B2 patent drawing
  • US7953827B2 patent drawing
  • US7953827B2 patent drawing

AI summary

Network addresses are dynamically allocated to blade information handling systems supported by a blade chassis having plural blade slots. A network address seed stored in memory associated with the blade chassis is retrieved by a management controller of a blade information handling system and applied by a network address generator to local network address information to generate a network address. The generated network address is applied by the management controller to a network component of the blade information handling system to establish communications over a network. For example, a WWN generated from a blade chassis seed address provides a blade information handling system host bus adapter access to a storage area network for boot from SAN support for the blade information handling system.