Blade Server Load Balancing via Port Switching

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing load balancing methods for blade servers do not effectively manage workload distribution at the blade level, leading to inefficiencies during Denial of Service (DoS) attacks, as blades are unaware of external uplink loads and continue forwarding workload to overloaded ports.

Innovation Solution

Implementing a blade management module that monitors throughput performance and instructs blades to switch between outgoing ports via an inter-integrated circuit communication bus, allowing for dynamic load balancing by switching to less loaded ports during performance degradation and back to original ports when performance improves.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If load balancing is performed at the server level by shifting workload to other resources, then the server can fend off DoS attacks, but load balancing does not occur at the blade level and blades remain unaware of external uplink loads

Engineering Contradiction:
ImproveDoS attack defense capabilityVSAvoidload balancing granularity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The invention segments the load balancing function from the server level to the blade level. Each blade is equipped with a network interface adapter that independently monitors throughput performance and executes port switching decisions. This segmentation enables fine-grained load balancing at the blade level while maintaining the overall DoS attack defense capability of the server.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The invention implements preliminary action by pre-configuring multiple outgoing ports on each blade and establishing monitoring mechanisms that track throughput performance in real-time. When performance degradation is detected, the blade automatically switches to alternative ports before the attack fully impacts service, enabling proactive defense against DoS attacks.

Inventive Principle:
Principle #10Preliminary action

2Productivity

If blades continuously forward workload to external uplinks, then workload distribution occurs, but blades are unaware of external uplink loads and continue forwarding to overloaded ports

Engineering Contradiction:
Improveworkload distribution efficiencyVSAvoiduplink load awareness
Core Design Contradiction:
ProductivityVSLoss of information

Solution Approach 1:

The invention implements a feedback mechanism where each blade's network interface adapter continuously monitors throughput performance metrics from external uplinks. This feedback information is used to dynamically adjust workload distribution decisions, allowing blades to recognize when uplinks are overloaded and switch to alternative ports, thereby maintaining productive workload distribution while eliminating information loss about uplink status.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

Each blade performs self-service load balancing by autonomously monitoring its own throughput performance and making port switching decisions without requiring external control. The blade's network interface adapter independently evaluates uplink conditions and redirects workload as needed, enabling continuous productive operation while maintaining awareness of external uplink loads through self-monitoring.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS8301752B2Load balancing for network server
Publication Date: 2012.10.30 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US8301752B2 patent drawing
  • US8301752B2 patent drawing
  • US8301752B2 patent drawing

AI summary

Embodiments of the invention address deficiencies of the art in respect to load balancing for servers having multiple blades and provide a novel and non-obvious method, system and computer program product for load balancing at the blade level for servers having multiple blades. In one embodiment of the present invention, a blade server for performing load balancing may comprise a plurality of blades, each blade coupled with a plurality of outgoing ports. The blade server may further include a blade management module configured for monitoring throughput performance of the server and the plurality of blades, wherein each blade is coupled with a plurality of outgoing ports, instructing a blade to switch from a first outgoing port to a second outgoing port when throughput performance decreases and instructing the blade to switch from the second outgoing port back to the first outgoing port when throughput performance increases.