Remote Access Controller Failover via Telemetry Analysis

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In enterprise environments, systems with multiple applications and devices face challenges with remote access controllers (RACs) losing connections to networks frequently, leading to operational inefficiencies and potential failures.

Innovation Solution

A method is implemented to recommend changes to the RAC configuration by analyzing telemetry data to detect connection loss frequencies exceeding a threshold. The method involves determining the current RAC configuration and recommending modifications to how the RAC uses its network interfaces, which are then implemented.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the RAC uses a single network interface for remote management, then the device complexity is reduced, but the reliability of network connection deteriorates due to frequent connection losses

Engineering Contradiction:
Improvenetwork connection reliabilityVSAvoidnetwork interface configuration complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The network interface functionality is segmented into multiple independent network interfaces (first and second NIs) within the RAC. Each interface can operate independently, and when one interface experiences connection loss, the system can switch to the other interface, thereby improving network connection reliability without significantly increasing overall device complexity

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system dynamically changes the operational parameters of the network interfaces by detecting connection loss frequency through telemetry analysis. When connection loss exceeds a threshold, the system modifies the configuration to enable failover capabilities, changing the state from single-interface operation to multi-interface redundant operation

Inventive Principle:
Principle #35Parameter changes

2Reliability

If telemetry monitoring and automated recommendation systems are implemented, then the reliability of remote management is improved, but the device complexity increases

Engineering Contradiction:
Improveremote management reliabilityVSAvoidsystem configuration complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system implements self-service through automated telemetry collection, analysis, and recommendation generation. The RAC automatically monitors its own network connection status, analyzes telemetry data to detect connection loss patterns, and generates configuration recommendations without requiring external intervention, thereby improving remote management reliability while keeping the operational complexity manageable

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system establishes a feedback loop where telemetry data from network interface operations is continuously collected and analyzed. This feedback mechanism detects connection loss frequency and triggers automated recommendation generation, creating a closed-loop system that continuously improves remote management reliability through data-driven configuration optimizations

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS12212459B2Method to recommend failover and reliable connection for remote management of devices
Publication Date: 2025.01.28 DELL PROD LP
  • US12212459B2 patent drawing
  • US12212459B2 patent drawing
  • US12212459B2 patent drawing

AI summary

Embodiments described herein relate to a method for recommending changes to a system that includes a remote access controller (RAC) which has at least two network interfaces (NI). An orchestrator reconfigures the remote access controller and/or it network interfaces when telemetry is retrieved from the system and the telemetry indicates that the remote access controller loses its connections with a connected network at a greater frequency than a threshold. The orchestrator determines recommend changes, notifies a user, and when able reconfigures the remote access controller to at least use the at least two network interfaces in a failover configuration.