BMC-Based Remote OS Deployment
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In network environments like enterprise datacenters, existing methods for remote OS deployment, such as PXE and UEFI-HTTPS, face challenges including high network traffic, complexity in DHCP server configuration, security vulnerabilities, and compatibility issues, making them unsuitable for scalable and secure OS deployment across multiple IP subnets.
Innovation Solution
The use of a Baseboard Management Controller (BMC) for remote OS deployment, where the BMC is initialized as the first bootable component, establishes a dedicated communication channel for downloading boot files from a remote server, eliminating the need for DHCP servers and NICs, and ensuring secure HTTPS communication.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If PXE or UEFI-HTTPS is used for remote OS deployment, then OS can be deployed remotely without physical access, but network traffic increases significantly and DHCP server configuration becomes complex
Solution Approach 1:
The patent extracts the OS deployment function from the network boot infrastructure (PXE/DHCP) and relocates it to local storage devices. The electronic device boots from local storage instead of requiring network-based PXE/DHCP infrastructure, eliminating the need for complex DHCP server configuration while maintaining remote OS deployment capability through direct local execution of OS images.
Solution Approach 2:
The patent introduces a storage device as an intermediary between the electronic device and the OS image source. The storage device receives OS images remotely, stores them locally, and provides them to the electronic device for execution, thereby mediating between remote deployment requirements and local execution needs without requiring complex network boot infrastructure.
2Adaptability or versatility
If PXE is used for remote OS deployment across multiple IP subnets, then deployment can be performed, but network traffic surges due to multiple broadcast and unicast messages
Solution Approach 1:
The patent performs preliminary action by downloading and storing the complete OS image on local storage devices before execution. This pre-loading approach eliminates the need for continuous network communication during boot and operation, reducing network traffic volume while maintaining the ability to deploy across multiple IP subnets through the storage-mediated approach.
3Ease of operation
If traditional network boot methods are used, then OS deployment can be performed, but security requirements are not met and protocols are blacklisted by firewalls
Solution Approach 1:
The patent replaces the network-based mechanical boot process (PXE/DHCP protocols) with a storage-based boot mechanism. By substituting network protocol-dependent boot with local storage execution, the system achieves OS deployment capability while bypassing security restrictions and firewall blacklists that block traditional network boot protocols.
Data Source
AI summary
Example approaches for remote deployment of an operating system (OS) in an electronic device are described. In an example, a Baseboard Management Controller (BMC) of the electronic device is set as a first bootable component in an order of initialization of hardware components of the electronic device during a boot operation. The BMC is initialized during the boot operation. A remote server information indicative of a network address of a remote server and a path directed to boot files of the OS stored in the remote server is received. The boot files are for deployment of the OS in the electronic device. The boot files from the remote server are downloaded over a dedicated communication channel associated with the BMC, based on the remote server information. The boot files are executed to deploy the OS in the electronic device.