Fabric Address Resolution in Enterprise Server Switching

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current server architectures face challenges in dynamically provisioning and managing compute, storage, and network resources efficiently, leading to suboptimal datacenter availability, efficiency, and utilization.

Innovation Solution

The Enterprise Fabric (EF) architecture introduces a hybrid server/multi-layer switch system with Virtual Network Interface Controllers (VNICs) and Virtual Input/Output Controllers (VIOCs) for dynamic provisioning and management of virtual servers, enabling scalable, high-bandwidth, low-latency I/O operations and flexible resource pooling.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If traditional server architectures are used for resource provisioning, then device simplicity is maintained, but resource allocation efficiency and datacenter utilization deteriorate

Engineering Contradiction:
Improveresource allocation efficiencyVSAvoidarchitecture complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The system segments physical server resources into virtual components through VNICs and VIOCs. Each virtual network interface controller represents a separable unit that can be independently provisioned, allocated, and managed. This segmentation enables flexible resource distribution across multiple virtual servers while maintaining underlying physical infrastructure integrity.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The fabric switch architecture provides universal connectivity that serves multiple functions simultaneously. The same fabric infrastructure supports storage, data, and management traffic across diverse server types and configurations. This multi-functionality allows a single complex system to replace multiple specialized components, improving resource utilization without proportionally increasing complexity.

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

2Adaptability or versatility

If static resource provisioning is used, then device complexity is reduced, but adaptability to changing workloads and multi-site failover capabilities deteriorate

Engineering Contradiction:
Improvedynamic resource reconfiguration capabilityVSAvoidprovisioning management complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system implements dynamic resource provisioning where VNICs and VIOCs can be created, moved, and configured in real-time based on workload demands. Resource allocation is not fixed but can be adjusted dynamically through software control, enabling rapid response to changing requirements and automatic failover between sites without manual reconfiguration.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The fabric switch acts as an intermediary layer between physical resources and virtual servers. This intermediary abstracts the complexity of direct resource management, providing standardized interfaces for resource allocation while handling the complex coordination required for dynamic provisioning, multi-site synchronization, and failover operations centrally.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Speed

If conventional I/O architectures are used, then device complexity is minimized, but I/O bandwidth and latency performance deteriorate

Engineering Contradiction:
ImproveI/O bandwidth and latencyVSAvoidI/O architecture complexity
Core Design Contradiction:
SpeedVSDevice complexity

Solution Approach 1:

The system replaces traditional mechanical bus-based I/O architectures with a fabric-based switching infrastructure. This substitution enables parallel data paths and non-blocking data flow, dramatically improving bandwidth and reducing latency compared to sequential bus architectures, though it introduces switching fabric complexity.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

Solution Approach 2:

The fabric architecture adds dimensional complexity by creating a mesh-like multi-path network structure instead of simple linear or star topologies. This dimensional expansion provides multiple concurrent data paths between any two points, enabling high-bandwidth parallel communication and low-latency routing through optimal path selection.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

Data Source

PatentUS7561571B1Fabric address and sub-address resolution in fabric-backplane enterprise servers
Publication Date: 2009.07.14 ORACLE INT CORP
  • US7561571B1 patent drawing
  • US7561571B1 patent drawing
  • US7561571B1 patent drawing

AI summary

A hybrid server and multi-layer switch system architecture, referred to hereinafter as the Enterprise Fabric (EF) architecture, forms the basis for a number of Enterprise Server (ES) chassis embodiments. Each ES embodiment generally includes one or more Processor Memory Modules (PMMs, each generally having one or more symmetric multiprocessor complexes), one or more Network Modules, and a System Control Module (SCM). The SCM includes a cellified switching-fabric core (SF) and a System Intelligence Module (SIM). Each PMM has one or more resident Virtual IO Controller (VIOC) adapters. Each VIOC is a specialized I/O controller that includes embedded layer-2 forwarding and filtering functions and tightly couples the PMM to the SF. Thus the layer-2 switch functionality within the ES chassis is distributed over all of the SCM, NM, and PMM modules. Through the use of VIOC/VNIC device drivers, host operating system software (Host O/S) running on the PMMs is presented with a plurality of Virtual Network Interface Cards (VNICs). In some embodiments, each VNIC behaves as a high-performance Ethernet interface at the full disposal of the Host O/S. In other embodiments, at least some of the VNICs behave as high-performance Fiber Channel Host Bus Adapters.