IP Library Granted Patent US 11,012,287
Granted Patent B1
US 11,012,287 · App. 16/731,946 · Granted May 18, 2021

System management domain and network management domain synchronization system

Inventors: Sudhir Vittal Shetty (Cedar Park, TX); Charles Chul Hyon Park (San Jose, CA); Zoheb Khan (Austin, TX); Balaji Rajagopalan (Sunnyvale, CA); Pawan Kumar Singal (Milpitas, CA); Joseph LaSalle White (San Jose, CA)
Assignee: Dell Products L.P.
H04L41/042H04L12/185H04L61/1511H04L61/2069H04L12/4641
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 11,012,287
App. No.
16/731,946
Granted
May 18, 2021
Kind
B1
Abstract

A system/network management domain synchronization system includes a first computing system that belongs to a first MCM group and that includes a first computing system I/O module that belongs to a first network management domain, and a second computing system that is coupled to the first computing system. The second computing system includes a second computing system management module that joins the first MCM group and, in response, broadcasts a first announcement that includes a first MCM group identifier for the first MCM group. The second computing system also includes a second computing system I/O module that receives the first announcement, determines that the second computing system management module is included in the second computing system with the second computing system I/O module and, n response, joins the first network management domain.

Claims (86)

1. A system management domain and network management domain synchronization system, comprising:

a first computing system that belongs to a first Multi-Chassis Management (MCM) group and that includes a first computing system Input/Output (I/O) module that belongs to a first network management domain; and

a second computing system that is coupled to the first computing system, wherein the second computing system includes:

a second computing system management module that includes at least one processor that is configured to:

join a second MCM group; and

broadcast, in response to joining the second MCM group, a second announcement that includes a second MCM group identifier for the second MCM group; and

a second computing system Input/Output (I/O) module that includes at least one processor that is configured to:

receive the second announcement that was broadcast by the at least one processor included in the second computing system management module and that includes the second MCM group identifier for the second MCM group;

determine, in response to receiving the second announcement, that the second computing system management module is included in the second computing system with the second computing system I/O module; and

join, in response to receiving the second MCM group identifier for the second MCM group in the second announcement broadcast by the second computing system management module and determining that the second computing system management module is included in the second computing system with the second computing system I/O module, a second network management domain,

wherein the at least one processor included in the second computing system management module is configured, subsequent to joining the second MCM group, to:

join the first MCM group that includes the first computing system; and

broadcast, in response to joining the first MCM group, a first announcement that includes a first MCM group identifier for the first MCM group, and

wherein the at least one processor included in the second computing system Input/Output (I/O) module is configured, subsequent to joining the second network management domain, to:

receive the first announcement that was broadcast by the at least one processor included in the second computing system management module and that includes the first MCM group identifier for the first MCM group;

determine, in response to receiving the first announcement, that the second computing system management module is included in the second computing system with the second computing system I/O module; and

leave, in response to receiving the first MCM group identifier for the first MCM group in the first announcement broadcast by the second computing system management module and determining that the second computing system management module is included in the second computing system with the second computing system I/O module, the second network management domain and join the first network management domain.

2. The system of claim 1 , wherein each of the first announcement and the second announcement include a multicast Domain Name System (mDNS) announcement.

3. The system of claim 1 , further comprising:

a third computing system that is coupled to the first computing system and the second computing system, wherein the third computing system includes:

a third computing system management module that includes at least one processor that is configured to:

join the first MCM group that includes the first computing system and the second computing system; and

broadcast, in response to joining the first MCM group, a third announcement that includes the first MCM group identifier for the first MCM group; and

a third computing system I/O module that includes at least one processor that is configured to:

receive the third announcement that was broadcast by the third computing system management module and that includes the first MCM group identifier for the first MCM group;

determine, in response to receiving the third announcement, that the third computing system management module is included in the third computing system with the third computing system I/O module; and

join, in response to receiving the first MCM group identifier for the first MCM group in the third announcement broadcast by the third computing system management module, and determining that the third computing system management module is included in the third computing system with the third computing system I/O module, the first network management domain.

4. The system of claim 1 , wherein the at least one processor included in the second computing system I/O module is configured to:

perform a hashing operation on the second MCM group identifier for the second MCM group received in the second announcement to generate a second network management domain identifier for the second network management domain; and

use the second network management domain identifier to join the second network management domain.

5. The system of claim 4 , wherein the using the second network management domain identifier to join the second network management domain includes:

determining that the second network management domain identifier is associated with the second MCM group identifier in a database.

6. The system of claim 1 , wherein the at least one processor included in the second computing system I/O module is configured to:

perform a hashing operation on the first MCM group identifier for the first MCM group received in the first announcement to generate a first network management domain identifier for the first network management domain; and

use the first network management domain identifier to join the first network management domain.

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

a processing system including at least one processor; and

a memory system that is coupled to the processing system and that includes instructions that, when executed by the at least one processor included in the processing system, cause the at least one processor included in the processing system to provide an Input/Output (I/O) engine that is configured to:

receive a first announcement that was broadcast by a first management module and that includes a first MCM group identifier for a first Multi-Chassis Management (MCM) group;

determine, in response to receiving the first announcement, that the first management module is included in a first chassis with the I/O engine; and

join, in response to receiving the first MCM group identifier for the first MCM group in the first announcement broadcast by the first management module and determining that the first management module is included in the first chassis with the I/O engine, a first network management domain, and

wherein the I/O engine is configured, subsequent to joining the first network management domain, to:

receive a second announcement that was broadcast by the first management module and that includes a second MCM group identifier for a second MCM group;

determine, in response to receiving the second announcement, that the first management module is included in the first chassis with the I/O engine; and

leave, in response to receiving the second MCM group identifier for the second MCM group in the second announcement broadcast by the first management module and determining that the first management module is included in the first chassis with the I/O engine, the first network management domain and join a second network management domain that is provided by at least one I/O module in a second chassis that is included in the second MCM group.

8. The IHS of claim 7 , wherein each of the first announcement and the second announcement include a multicast Domain Name System (mDNS) announcement.

9. The IHS of claim 7 , wherein the I/O engine is configured to:

perform a hashing operation on the first MCM group identifier for the first MCM group received in the first announcement to generate a first network management domain identifier for the first network management domain; and

use the first network management domain identifier to join the first network management domain.

10. The IHS of claim 9 , wherein the using the first network management domain identifier to join the first network management domain includes:

determining that the first network management domain identifier is associated with the first MCM group identifier in a database.

11. The IHS of claim 7 , wherein the I/O engine is configured to:

perform a hashing operation on the second MCM group identifier for the second MCM group received in the second announcement to generate a second network management domain identifier for the second network management domain; and

use the second network management domain identifier to join the second network management domain.

12. The IHS of claim 11 , wherein the joining the first network management domain includes:

performing a hashing operation on the first MCM group identifier for the first MCM group received in the first announcement to generate a first network management domain identifier for the first network management domain;

determining that the first network management domain identifier is not associated with the first MCM group identifier in a database; and

performing network management domain identifier reservation operations for the first network management domain identifier to join the first network management domain.

13. The IHS of claim 7 , wherein the I/O engine is configured to:

receive a third announcement that was broadcast by the first management module and that includes a third MCM group identifier for a third MCM group;

determine, in response to receiving the third announcement, that the first management module is included in the first chassis with the I/O engine;

leave, in response to receiving the third MCM group identifier for the third MCM group in the third announcement broadcast by the first management module and determining that the first management module is included in the first chassis with the I/O engine, the second network management domain and provide a third network management domain for the third MCM group.

14. A method for synchronizing a system management domain and a network management domain, comprising:

receiving, by at least one processor included in a first Input/Output (I/O) module in a first computing system, a first announcement that was broadcast by a first management module and that includes a first MCM group identifier for a first MCM group;

determining, by the at least one processor included in the first I/O module in the first computing system in response to receiving the first announcement, that the first management module is included in the first computing system with the first I/O module;

joining, by the at least one processor included in the first I/O module in the first computing system in response to receiving the first MCM group identifier for the first MCM group in the first announcement broadcast by the first management module and determining that the first management module is included in the first computing system with the first I/O module, a first network management domain;

receiving, by the at least one processor included in the first I/O module in the first computing system subsequent to joining the first network management domain, a second announcement that was broadcast by the first management module and that includes a second MCM group identifier for a second MCM group;

determining, by the at least one processor included in the first I/O module in the first computing system in response to receiving the second announcement, that the first management module is included in the first computing system with the first I/O module; and

leaving, by the at least one processor included in the first I/O module in the first computing system in response to receiving the second MCM group identifier for the second MCM group in the second announcement broadcast by the first management module and determining that the first management module is included in the first computing system with the first I/O module, the first network management domain and joining a second network management domain that is provided by at least one second I/O module in a second computing system that is included in the second MCM group.

15. The method of claim 14 , wherein each of the first announcement and the second announcement include a multicast Domain Name System (mDNS) announcement.

16. The method of claim 14 , further comprising:

performing, by the at least one processor included in the first I/O module in the first computing system, a hashing operation on the first MCM group identifier for the first MCM group received in the first announcement to generate a first network management domain identifier for the first network management domain; and

using, by the at least one processor included in the first I/O module in the first computing system, the first network management domain identifier to join the first network management domain.

17. The method of claim 16 , wherein the using the first network management domain identifier to join the first network management domain includes:

determining, by the at least one processor included in the first I/O module in the first computing system, that the first network management domain identifier is associated with the first MCM group identifier in a database.

18. The method of claim 14 , further comprising:

performing, by the at least one processor included in the first I/O module in the first computing system, a hashing operation on the second MCM group identifier for the second MCM group received in the second announcement to generate a second network management domain identifier for the second network management domain; and

using, by the at least one processor included in the first I/O module in the first computing system, the second network management domain identifier to join the second network management domain.

19. The method of claim 18 , wherein the joining the first network management domain includes:

performing, by the at least one processor included in the first I/O module in the first computing system, a hashing operation on the first MCM group identifier for first MCM group received in the first announcement to generate a first network management domain identifier for the first network management domain;

determining, by the at least one processor included in the first I/O module in the first computing system, that the first network management domain identifier is not associated with the first MCM group identifier in a database; and

performing, by the at least one processor included in the first I/O module in the first computing system, network management domain identifier reservation operations for the first network management domain identifier to join the first network management domain.

20. The method of claim 14 , further comprising:

receiving, by the at least one processor included in the first I/O module in the first computing system, a third announcement that was broadcast by the first management module and that includes a third MCM group identifier for a third MCM group;

determining, by the at least one processor included in the first I/O module in the first computing system in response to receiving the third announcement, that the first management module is included in the first computing system with the first I/O module;

leaving, by the at least one processor included in the first I/O module in the first computing system in response to receiving the third MCM group identifier for the third MCM group in the third announcement broadcast by the first management module and determining that the first management module is included the first computing system with the first I/O module, the second network management domain and providing a third network management domain for the third MCM group.

Assignments (9)
RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (053311/0169) Recorded Jun 23, 2022
From: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT
To: DELL PRODUCTS L.P.; EMC CORPORATION; EMC IP HOLDING COMPANY LLC
Reel/Frame 060438/0742 →
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 →
RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (052216/0758) Recorded Jun 23, 2022
From: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT
To: DELL PRODUCTS L.P.; EMC IP HOLDING COMPANY LLC
Reel/Frame 060438/0680 →
RELEASE OF SECURITY INTEREST AF REEL 052243 FRAME 0773 Recorded Nov 2, 2021
From: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH
To: DELL PRODUCTS L.P.; EMC IP HOLDING COMPANY LLC
Reel/Frame 058001/0152 →
SECURITY INTEREST Recorded Jun 5, 2020
From: DELL PRODUCTS L.P.; EMC CORPORATION; EMC IP HOLDING COMPANY LLC
To: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS COLLATERAL AGENT
Reel/Frame 053311/0169 →
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 26, 2020
From: DELL PRODUCTS L.P.; EMC IP HOLDING COMPANY LLC
To: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH
Reel/Frame 052243/0773 →
PATENT SECURITY AGREEMENT (NOTES) Recorded Mar 24, 2020
From: DELL PRODUCTS L.P.; EMC IP HOLDING COMPANY LLC
To: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS COLLATERAL AGENT
Reel/Frame 052216/0758 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 3, 2020
From: SHETTY, SUDHIR VITTAL; PARK, CHARLES C.; KHAN, ZOHEB; RAJAGOPALAN, BALAJI; SINGAL, PAWAN KUMAR; WHITE, JOSEPH LASALLE
To: DELL PRODUCTS L.P.
Reel/Frame 051408/0301 →