IP Library Granted Patent US 10,855,538
Granted Patent B2
US 10,855,538 · App. 16/260,560 · Granted Dec 1, 2020

Single management connection automatic device stack configuration system

Inventor: Sudharsan Dhamal Gopalarathnam (Tamil Nadu, IN)
Assignee: Dell Products L.P.
H04L41/0886H04L41/0853H04L41/0873H04L41/0893H04L41/0806H04L41/0813
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 10,855,538
App. No.
16/260,560
Granted
Dec 1, 2020
Kind
B2
Abstract

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.

Claims (75)

1. An automatic device stack configuration system, comprising:

a management device;

a plurality of member stack devices; and

a master stack device that is coupled to the management device and the plurality of member stack devices, wherein the master stack device includes:

a first processing system; and

a first memory system that is coupled to the first processing system and that includes instructions that, when executed by the first processing system, cause the first processing system to provide a first stack engine that is configured to:

receive, from the management device, stack configuration information that includes a plurality of member stack device addresses;

identify, in a master stack device port/address database, a first subset of the plurality of member stack device addresses that were received via respective ports on the master stack device;

configure each of the respective ports on the master stack device that received the first subset of the plurality of member stack device addresses as stack ports;

transmit, to each of the plurality of member stack devices that are associated with the first subset of the plurality of member stack device addresses, a second subset of the plurality of member stack device addresses that were not received via ports on the master stack device;

receive, from at least some of the plurality of member stack devices, identifications of ports that are included on the plurality of member stack devices, that received the second subset of the plurality of member stack device addresses, and that have been configured as stack ports and, in response, cause a reboot of the master stack device and each of the plurality of member stack devices; and

provide, following the reboot of master stack device and each of the plurality of member stack devices, a stack that includes the master stack device and each of the plurality of member stack devices.

2. The system of claim 1 , wherein each of the plurality of member stack devices that are associated with the first subset of the plurality of member stack device addresses includes:

a second processing system; and

a second memory system that is coupled to the second processing system and that includes instructions that, when executed by the second processing system, cause the second processing system to provide a second stack engine that is configured to:

determine whether at least one of the second subset of the plurality of member stack device addresses were received via respective ports on that member stack device;

configure, in response to determining that the at least one of the second subset of the plurality of member stack device addresses were received via the respective ports on that member stack device, each of the respective ports on that member stack device that received the at least one second subset of the plurality of member stack device addresses as stack ports; and

transmit, to the master stack device, an identification of each of the respective ports on that member stack device that were configured as stack ports.

3. The system of claim 1 , wherein the first stack engine of the master stack device is configured to:

designate each of the plurality of member stack devices that transmitted the first subset of the plurality of member stack device addresses to the master stack device as discovered stack devices.

4. The system of claim 3 , wherein the first stack engine of the master stack device is configured to:

designate each of the plurality of member stack devices that transmitted the second subset of the plurality of member stack device addresses to others of the plurality of member stack devices as discovered stack devices.

5. The system of claim 4 , wherein the first stack engine of the master stack device is configured to:

determine that each of the plurality of member stack devices has been designated as a discovered stack device and, in response, cause at least one of the plurality of member stack devices, which has not configured a port on that member stack device as a stack port, to configure that port as a stack port.

6. The system of claim 4 , wherein the first stack engine of the master stack device is configured to:

determine that each of the plurality of member stack devices has been designated as a discovered stack device; and

cause, subsequent to a time period following the determination that each of the plurality of member stack devices has been designated as a discovered stack device, the reboot of the master stack device and each of the member stack devices.

7. The system of claim 1 , wherein the causing the reboot of master stack device and each of the plurality of member stack devices includes the master stack device:

sending a reboot instruction to each of the plurality of member stack devices that causes each of those member stack devices to perform a reboot operation; and

performing a reboot operation.

8. An Information Handling System (IHS), comprising:

a processing system; and

a memory system that is coupled to the processing system and that includes instructions that, when executed by the processing system, cause the processing system to provide a stack engine that is configured to:

receive, from a management device, stack configuration information that includes a plurality of member stack device addresses;

identify, in a master stack device port/address database, a first subset of the plurality of member stack device addresses that were received via respective ports that are coupled to the processing system;

configure each of the respective ports that are coupled to the processing system and that received the first subset of the plurality of member stack device addresses as stack ports;

transmit, to each of a plurality of member stack devices that are associated with the first subset of the plurality of member stack device addresses, a second subset of the plurality of member stack device addresses that were not received via ports that are coupled to the processing system;

receive, from at least some of the plurality of member stack devices, identifications of ports that are included on the plurality of member stack devices, that received the second subset of the plurality of member stack device addresses, and that have been configured as stack ports and, in response, cause a reboot of the each of the plurality of member stack devices; and

provide, following the reboot of each of the member stack devices, a stack that includes each of the plurality of member stack devices.

9. The IHS of claim 8 , wherein the stack engine is configured to:

designate each of the plurality of member stack devices that transmitted the first subset of the plurality of member stack device addresses to the respective ports that are coupled to the processing system as discovered stack devices.

10. The IHS of claim 9 , wherein the stack engine is configured to:

designate each of the plurality of member stack devices that transmitted the second subset of the plurality of member stack device addresses to others of the plurality of member stack devices as discovered stack devices.

11. The IHS of claim 10 , wherein the stack engine is configured to:

determine that each of the plurality of member stack devices has been designated as a discovered stack device and, in response, cause at least one of the plurality of member stack devices, which has not configured a port on that member stack device as a stack port, to configure that port as a stack port.

12. The IHS of claim 10 , wherein the stack engine is configured to:

determine that each of the plurality of member stack devices has been designated as a discovered stack device; and

cause, subsequent to a time period following the determination that each of the plurality of member stack devices has been designated as a discovered stack device, the reboot of the each of the member stack devices.

13. The IHS of claim 8 , wherein the stack engine is configured to:

send a reboot instruction to each of the plurality of member stack devices that causes each of those member stack devices to perform a reboot operation; and

perform a reboot operation.

14. A method for automatically configuring a device stack, comprising:

receiving, by a master stack device from a management device, stack configuration information that includes a plurality of member stack device addresses;

identifying, by the master stack device in a master stack device port/address database, a first subset of the plurality of member stack device addresses that were received via respective ports on the master stack device;

configuring, by the master stack device, each of the respective ports on the master stack device that received the first subset of the plurality of member stack device addresses as stack ports;

transmitting, by the master stack device to each of a plurality of member stack devices that are associated with the first subset of the plurality of member stack device addresses, a second subset of the plurality of member stack device addresses that were not received via ports on the master stack device;

receiving, by the master stack device from at least some of the plurality of member stack devices, identifications of ports that are included on the plurality of member stack devices, that received the second subset of the plurality of member stack device addresses, and that have been configured as stack ports and, in response, causing a reboot of the master stack device and each of the plurality of member stack devices; and

providing, by the master stack device following the reboot of master stack device and each of the plurality of member stack devices, a stack that includes the master stack device and each of the plurality of member stack devices.

15. The method of claim 14 , further comprising:

determining, by each of the plurality of member stack devices that are associated with the first subset of the plurality of member stack device addresses, whether at least one of the second subset of the plurality of member stack device addresses were received via respective ports on that member stack device;

configuring, by each of the plurality of member stack devices that are associated with the first subset of the plurality of member stack device addresses in response to determining that the at least one of the second subset of the plurality of member stack device addresses were received via the respective ports on that member stack device, each of the respective ports on that member stack device that received the at least one second subset of the plurality of member stack device addresses as stack ports; and

transmitting, by each of the plurality of member stack devices that are associated with the first subset of the plurality of member stack device addresses to the master stack device, an identification of each of the respective ports on that member stack device that were configured as stack ports.

16. The method of claim 14 , further comprising:

designating, by the master stack device, each of the plurality of member stack devices that transmitted the first subset of the plurality of member stack device addresses to the master stack device as discovered stack devices.

17. The method of claim 16 , further comprising:

designating, by the master stack device, each of the plurality of member stack devices that transmitted the second subset of the plurality of member stack device addresses to others of the plurality of member stack devices as discovered stack devices.

18. The method of claim 17 , further comprising:

determining, by the master stack device, that each of the plurality of member stack devices has been designated as a discovered stack device and, in response,

causing at least one of the plurality of member stack devices, which has not configured a port on that member stack device as a stack port, to configure that port as a stack port.

19. The method of claim 17 , further comprising:

determining, by the master stack device, that each of the plurality of member stack devices has been designated as a discovered stack device; and

causing, by the master stack device subsequent to a time period following the determination that each of the plurality of member stack devices has been designated as a discovered stack device, the reboot of the master stack device and each of the member stack devices.

20. The method of claim 14 , wherein the causing the reboot of master stack device and each of the plurality of member stack devices includes:

sending, by the master stack device, a reboot instruction to each of the plurality of member stack devices that causes each of those member stack devices to perform a reboot operation; and

performing, by the master stack device, a reboot operation.

Assignments (5)
RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (053546/0001) Recorded Jun 23, 2022
From: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT
To: DELL MARKETING L.P. (ON BEHALF OF ITSELF AND AS SUCCESSOR-IN-INTEREST TO CREDANT TECHNOLOGIES, INC.); DELL INTERNATIONAL L.L.C.; DELL PRODUCTS L.P.; DELL USA L.P.; EMC CORPORATION; DELL MARKETING CORPORATION (SUCCESSOR-IN-INTEREST TO FORCE10 NETWORKS, INC. AND WYSE TECHNOLOGY L.L.C.); EMC IP HOLDING COMPANY LLC
Reel/Frame 071642/0001 →
SECURITY AGREEMENT Recorded Oct 1, 2021
From: DELL PRODUCTS, L.P.; EMC IP HOLDING COMPANY LLC
To: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH
Reel/Frame 057682/0830 →
SECURITY AGREEMENT Recorded Apr 22, 2020
From: CREDANT TECHNOLOGIES INC.; DELL INTERNATIONAL L.L.C.; DELL MARKETING L.P.; DELL PRODUCTS L.P.; DELL USA L.P.; EMC CORPORATION; FORCE10 NETWORKS, INC.; WYSE TECHNOLOGY L.L.C.; EMC IP HOLDING COMPANY LLC
To: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A.
Reel/Frame 053546/0001 →
SECURITY AGREEMENT Recorded Mar 21, 2019
From: CREDANT TECHNOLOGIES, INC.; DELL INTERNATIONAL L.L.C.; DELL MARKETING L.P.; DELL PRODUCTS L.P.; DELL USA L.P.; EMC CORPORATION; FORCE10 NETWORKS, INC.; WYSE TECHNOLOGY L.L.C.; EMC IP HOLDING COMPANY LLC
To: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A.
Reel/Frame 049452/0223 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 29, 2019
From: GOPALARATHNAM, SUDHARSAN DHAMAL
To: DELL PRODUCTS L.P.
Reel/Frame 048165/0988 →