IP Library Granted Patent US 11,652,786
Granted Patent B2
US 11,652,786 · App. 17/372,982 · Granted May 16, 2023

Network fabric deployment system

Inventors: Padmanabhan Narayanan (Redmond, WA); Raghava Krishna Jagarlapudi (Ongole, IN); Arun Dharmalingaswamy (Kanyakumari, IN)
Assignee: Dell Products L.P.
H04L61/5014G06F3/0607G06F3/067G06F3/0629G06F3/0665G06F8/63G06F9/4416H04L61/5061
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,652,786
App. No.
17/372,982
Granted
May 16, 2023
Kind
B2
Abstract

A network fabric deployment system includes a fabric deployment management system that is coupled to a DHCP server. The fabric deployment management system generates a cloud-based network fabric that is based on a network fabric topology file and that includes a plurality of cloud-based networking devices that are assigned a physical networking device identifier that identifies a corresponding physical networking device. The fabric deployment management system configures and validates each of the plurality of cloud-based networking devices causing each physical networking device identifier being mapped to an IP address at the DHCP server and then retrieves a deployment image file from each of the plurality of cloud-based networking devices that have been configured and validated, and stores each of the deployment image files in a database in association with the physical networking device identifier such that the corresponding physical networking device boots from that deployment image file.

Claims (68)

1. A network fabric deployment system, comprising:

a Dynamic Host Configuration Protocol (DHCP) server; and

a fabric deployment management system that is coupled to the DHCP server and that is configured to:

generate a virtual network fabric that is based on a network fabric topology and that includes a plurality of virtual networking devices,

wherein each of the plurality of virtual networking devices deployed in the virtual network fabric corresponds to a physical networking device included in a physical network fabric that is connected or will be connected according to the network fabric topology, and

wherein each virtual networking device is assigned a physical networking device identifier that identifies the physical networking device that corresponds to that virtual networking device;

configure and validate each of the plurality of virtual networking devices included in the virtual network fabric until the virtual network fabric is provisioned in a manner that allows the plurality of virtual networking devices to perform networking actions on data traffic, wherein the configuring and validating includes causing each of the plurality of virtual networking devices to obtain an Internet Protocol (IP) address from the DHCP server using the physical networking device identifier assigned to that virtual networking device such that that physical networking device identifier is mapped to the IP address at the DHCP server;

retrieve a deployment image file from each of the plurality of virtual networking devices that have been configured and validated, wherein each deployment image file includes a deployment image of that virtual networking device that has been configured and validated; and

store each of the deployment image files in a fabric deployment image database in association with the physical networking device identifier assigned to the virtual networking device associated with that deployment image file.

2. The system of claim 1 , wherein the DHCP server is configured to:

receive, from a first physical networking device, a DHCP request that includes a first physical networking device identifier;

determine that the first physical networking device identifier is associated with a physical networking device identifier that is associated with a first IP address and a first deployment image file stored in the fabric deployment image database; and

provide the first IP address and the first deployment image file to the first physical networking device.

3. The system of claim 2 , wherein the first physical networking device is configured to:

receive the first deployment image file and the first IP address;

determine that a corresponding virtual networking device has been pre-deployed based on the first deployment image file; and

flash a first deployment image included in the first deployment image file on a storage of the first physical networking device.

4. The system of claim 3 , wherein the first physical networking device is configured to:

resize, when a Network Operating System (NOS) on the first physical networking device boots and using a first cloud partition file that is included with the first deployment image file, partitions based on a recognition that the NOS is booting on a physical networking device rather than a virtual networking device.

5. The system of claim 3 , wherein the first physical networking device is configured to:

update a Master Boot Record (MBR) or a GUID Partition Table (GPT) to directly boot into a NOS on a subsequent boot.

6. The system of claim 1 , wherein the fabric deployment management system is configured to:

verify the physical network fabric that follows the network fabric topology when each of the plurality of physical networking devices boots with a respective deployment image.

7. The system of claim 1 , wherein each of the deployment images includes:

a dump of a plurality of storage partitions included on that virtual networking device, meta data associated with each of the plurality of storage partitions, and a configuration file.

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 fabric deployment management engine that is configured to:

generate a virtual network fabric that is based on a network fabric topology and that includes a plurality of virtual networking devices,

wherein each of the plurality of virtual networking devices deployed in the virtual network fabric corresponds to a physical networking device included in a physical network fabric that is connected or will be connected according to the network fabric topology, and

wherein each virtual networking device is assigned a physical networking device identifier that identifies the physical networking device that corresponds to that virtual networking device;

configure and validate each of the plurality of virtual networking devices included in the virtual network fabric until the virtual network fabric is provisioned in a manner that allows the plurality of virtual networking devices to perform networking actions on data traffic, wherein the configuring and validating includes causing each of the plurality of virtual networking devices to obtain an Internet Protocol (IP) address from a Dynamic Host Configuration Protocol (DHCP) server using the physical networking device identifier assigned to that virtual networking device such that that physical networking device identifier is mapped to the IP address at the DHCP server;

retrieve a deployment image file from each of the plurality of virtual networking devices that were configured and validated, wherein each deployment image file includes a deployment image of that virtual networking device that has been configured and validated; and

store each of the deployment image files in a fabric deployment image database in association with the physical networking device identifier assigned to the virtual networking device associated with that deployment image file.

9. The IHS of claim 8 , wherein the fabric deployment management engine is configured to:

provide, to the DHCP server, a first deployment image file of the deployment image files in the fabric deployment image database in response to a DHCP request provided to the DHCP server that includes a first physical networking device identifier that is associated with the physical networking device identifier associated with the first deployment image file, wherein the DHCP server provides the IP address and the first deployment image file to a physical networking device that made the DHCP request.

10. The IHS of claim 9 , wherein the deployment image file causes the physical networking device to:

determine that a corresponding virtual networking device has been pre-deployed based on the deployment image file; and

flash a first deployment image included in the first deployment image file on a storage of the first physical networking device to provide a provisioned physical networking device.

11. The IHS of claim 8 , wherein the fabric deployment management engine is configured to:

verify the physical network fabric that follows the network fabric topology when each of the plurality of physical networking devices boots with a respective deployment image.

12. The IHS of claim 8 , wherein each of the deployment images includes:

a dump of a plurality of storage partitions included on that virtual networking device, meta data associated with each of the plurality of storage partitions, and a configuration file.

13. The IHS of claim 8 , wherein the fabric deployment management engine is configured to:

derive a customized cloud partition file that is based on a cloud partition file for a type of physical networking device and that is based on a network fabric provisioning plan for the virtual networking device.

14. A method for deploying a network fabric, comprising:

generating, by a fabric deployment management system, a virtual network fabric that is based on a network fabric topology and that includes a plurality of virtual networking devices,

wherein each of the plurality of virtual networking devices deployed in the virtual network fabric corresponds to a physical networking device included in a physical network fabric that is connected or will be connected according to the network fabric topology, and

wherein each virtual networking device is assigned a physical networking device identifier that identifies the corresponding physical networking device for that virtual networking device;

managing, by the fabric deployment management system, configuration and validation of each of the plurality of virtual networking devices included in the virtual network fabric until the virtual network fabric is provisioned in a manner that allows the plurality of virtual networking devices to perform networking actions on data traffic, wherein the configuring and validating includes causing each of the plurality of virtual networking devices to obtain an Internet Protocol (IP) address from a Dynamic Host Configuration Protocol (DHCP) server using the physical networking device identifier assigned to that virtual networking device such that that physical networking device identifier is mapped to the IP address at the DHCP server;

retrieving, by the fabric deployment management system, a deployment image file from each of the plurality of virtual networking devices that were configured and validated, wherein each deployment image file includes a deployment image of that virtual networking device that has been configured and validated; and

storing, by the fabric deployment management system, each of the deployment image files in a fabric deployment image database in association with the physical networking device identifier assigned to the virtual networking device associated with that deployment image file.

15. The method of claim 14 , further comprising:

receiving, by the DHCP server, a DHCP request that includes a first physical networking device identifier;

determining, by the DHCP server, that the first physical networking device identifier is associated with a physical networking device identifier that is associated with a first IP address and a first deployment image file stored in the fabric deployment image database; and

providing, by the DHCP server, the first IP address and the first deployment image file to a first physical networking device that made the DHCP request.

16. The method of claim 15 , further comprising:

receiving, by the first physical networking device, the first deployment image file and the first IP address;

determining, by the first physical networking device, that a corresponding virtual networking device has been pre-deployed based on the first deployment image file; and

flashing, by the first physical networking device, a first deployment image included in the first deployment image file on a storage of the first physical networking device.

17. The method of claim 16 , further comprising:

resizing, when a Network Operating System (NOS) on the first physical networking device boots and using a first customized cloud partition file that is included with the first deployment image file, partitions based on a recognition that the NOS is booting on a physical networking device rather than a virtual networking device.

18. The method of claim 16 , further comprising:

updating, by the first physical networking device, a Master Boot Record (MBR) or a GUID Partition Table (GPT) to directly boot into a NOS on a subsequent boot.

19. The method of claim 14 , further comprising:

verifying, by the first physical networking device, the physical network fabric that follows the network fabric topology when each of the plurality of physical networking devices boots with a respective deployment image.

20. The method of claim 14 , wherein each of the deployment images includes:

a dump of a plurality of storage partitions included on that virtual networking device, meta data associated with each of the plurality of storage partitions, and a configuration file.

Assignments (8)
RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (058014/0560) Recorded Jun 10, 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 062022/0473 →
RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (057931/0392) Recorded Jun 10, 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 062022/0382 →
RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (057758/0286) Recorded Jun 10, 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 061654/0064 →
SECURITY INTEREST Recorded Oct 6, 2021
From: DELL PRODUCTS L.P.; EMC IP HOLDING COMPANY LLC
To: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT
Reel/Frame 058014/0560 →
SECURITY INTEREST Recorded Oct 6, 2021
From: DELL PRODUCTS L.P.; EMC IP HOLDING COMPANY LLC
To: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT
Reel/Frame 057758/0286 →
SECURITY INTEREST Recorded Oct 6, 2021
From: DELL PRODUCTS L.P.; EMC IP HOLDING COMPANY LLC
To: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT
Reel/Frame 057931/0392 →
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 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 12, 2021
From: NARAYANAN, PADMANABHAN; JAGARLAPUDI, RAGHAVA KRISHNA; DHARMALINGASWAMY, ARUN
To: DELL PRODUCTS L.P.
Reel/Frame 056828/0791 →
Priority Claims (1)
IN 202111027076 · Jun 17, 2021 · national
Continuity (1)
Related Publication 20220407836A1 · Dec 22, 2022