Automated Virtual Interface Failover in Mass Storage Clusters

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Manual programming of failover configuration rules for virtual interfaces (VIFs) in mass data storage systems is labor-intensive, prone to errors, and requires significant effort to accommodate changes in system size, limiting the effectiveness of redundancy and data accessibility.

Innovation Solution

An automated method for establishing and reconfiguring VIFs among servers in a cluster, using status messages to transfer IP addresses from inoperative to operative ports, ensuring redundancy and equal distribution without manual intervention.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If manual programming of failover configuration rules is used, then system reliability is improved through redundancy, but device complexity and ease of operation deteriorate due to labor-intensive configuration and error-prone manual programming

Engineering Contradiction:
Improvesystem reliabilityVSAvoidconfiguration complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system performs self-configuration of failover rules automatically without requiring manual programming. The automated method monitors port status, detects failures, and dynamically generates failover configuration rules, allowing the system to service itself and eliminating the need for manual intervention in configuration management.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system pre-establishes failover capability by automatically monitoring port status and maintaining a pool of standby virtual interfaces. When a failure occurs, the failover configuration is already prepared and can be activated immediately, ensuring system reliability without the complexity of manual pre-programming.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If manual programming of failover configuration rules is used, then system reliability is improved through redundancy, but productivity deteriorates due to labor-intensive configuration and time-consuming maintenance

Engineering Contradiction:
Improvesystem reliabilityVSAvoidconfiguration productivity
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The automated method enables the system to automatically generate, update, and maintain failover configuration rules without human intervention. This self-service capability dramatically improves productivity by eliminating the labor-intensive manual programming and configuration maintenance while preserving system reliability through automated redundancy management.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system continuously monitors port status and uses this feedback to automatically adjust failover configuration rules. When port failures are detected, the system receives feedback about the failure state and automatically updates the configuration, eliminating the need for manual reconfiguration and improving productivity while maintaining reliability.

Inventive Principle:
Principle #23Feedback

3Reliability

If manual programming of failover configuration rules is used, then system reliability is improved through redundancy, but ease of operation deteriorates due to difficulty in accommodating system changes

Engineering Contradiction:
Improvesystem reliabilityVSAvoidconfiguration ease
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The failover configuration rules are made dynamic rather than static. The automated method continuously adapts the configuration based on real-time port status and system changes, allowing the system to easily accommodate additions or removals of network interfaces without requiring manual reprogramming while maintaining reliability through automated redundancy management.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system automatically detects system changes such as added or removed network interfaces and self-adjusts the failover configuration rules accordingly. This self-service capability makes operation easier by eliminating the need for manual configuration updates when the system changes, while preserving reliability through automated failover rule generation.

Inventive Principle:
Principle #25Self-service

4Productivity

If automated method is used, then productivity and ease of operation are improved, but device complexity increases due to automation mechanisms

Engineering Contradiction:
Improveconfiguration productivityVSAvoidautomation complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The automated method uses universal monitoring and configuration mechanisms that can handle multiple types of network interfaces and failure scenarios with a single system. This multi-functionality improves productivity by providing comprehensive automation while managing complexity through a unified approach rather than separate mechanisms for each scenario.

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

Solution Approach 2:

The automation complexity is managed through feedback-driven adaptive configuration. The system monitors port status and automatically adjusts failover rules based on real-time feedback, which simplifies the automation process by making it responsive and adaptive rather than requiring complex pre-programming for all possible scenarios, thereby improving productivity without excessive complexity.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS7818408B1Automated virtual interface failover in a mass storage cluster
Publication Date: 2010.10.19 NETAPP INC
  • US7818408B1 patent drawing
  • US7818408B1 patent drawing
  • US7818408B1 patent drawing

AI summary

Virtual interfaces on a cluster of servers in a mass data storage system are automatically reconfigured by transferring an internet protocol (IP) address hosting responsibility from one operative port to another operative port within the cluster, in response to a change in operative status of any port within the cluster.