Automatic Stack Configuration via Single Management Connection

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The conventional configuration of a stack of switch devices requires network administrators to manually configure management connections and stack configurations for each device, which is time-consuming and inefficient, especially since member switch devices do not use these connections during operation.

Innovation Solution

An Information Handling System (IHS) with a processing system and memory that includes instructions to provide a stack engine to receive stack configuration information, identify and configure member stack device addresses, transmit configuration to member devices, and reboot them to form a unified stack using a single management connection, eliminating the need for temporary management connections to member devices.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If manual configuration of management connections and stack configurations is performed for each switch device, then configuration accuracy and reliability are improved, but configuration time and administrative effort increase significantly

Engineering Contradiction:
Improveconfiguration reliabilityVSAvoidconfiguration time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system enables self-service configuration where the master switch device automatically configures member switch devices without requiring manual intervention. The master switch device pushes stack configuration to member devices, and member devices automatically identify their stack ports based on received configuration data, eliminating the need for administrators to manually configure each device while maintaining configuration accuracy

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The master switch device performs preliminary actions by pre-configuring stack configuration data and pushing it to member switch devices before the stack operation begins. This preliminary configuration includes providing stack configuration that enables member devices to automatically identify their stack ports, thereby reducing on-site configuration time while ensuring proper configuration is established in advance

Inventive Principle:
Principle #10Preliminary action

2Ease of operation

If temporary management connections are provided to each member switch device for configuration, then configuration capability is improved, but system complexity and resource requirements increase

Engineering Contradiction:
Improveconfiguration capabilityVSAvoidsystem complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The invention extracts the configuration capability from individual member switch devices and consolidates it in the master switch device. The master switch device alone maintains the management connection and performs all configuration actions, while member devices receive configuration data passively. This eliminates the need for temporary management connections to member devices and reduces system complexity

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The master switch device serves multiple functions: it acts as the sole management interface for the entire stack, configures all member devices, and provides the configuration data that enables automatic port identification. This multi-functionality consolidates what would otherwise require multiple separate management connections and administrative actions across multiple devices

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

Data Source

PatentUS10855538B2Single management connection automatic device stack configuration system
Publication Date: 2020.12.01 DELL PROD LP
  • US10855538B2 patent drawing
  • US10855538B2 patent drawing
  • US10855538B2 patent drawing

AI summary

An automatic device stack configuration system includes a master stack unit coupled to a management device and member stack devices. The master stack device receives member stack device addresses from the management device, identifies a first subset of member stack device addresses received via its respective ports, and configures each of those respective ports as stack ports. The master stack device then transmits a second subset of member stack device addresses that were not received via its ports to the member stack devices associated with the first subset of member stack device addresses. When the master stack device receives identifications that ports on the member stack devices that received the second subset of the member stack device addresses have been configured as stack ports, it reboots the master stack device and member stack devices. Following the reboot, a stack including the master stack device and member stack devices is provided.