Touchless Server Provisioning with Static IP Support
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing automated provisioning solutions for server-class information handling systems are complex and may not be compatible with all server configurations, particularly those requiring static IP addresses, as they often rely on dynamic host configuration protocol (DHCP) services.
Innovation Solution
A touchless provisioning method that configures information handling systems to support multiple network services, including DHCP and multicast DNS (mDNS), allowing for the retrieval of a configuration profile locator to enable provisioning agents to configure the system according to a server configuration profile, even in scenarios with static IP addresses.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Extent of automation
If automated provisioning solutions rely on DHCP service, then provisioning automation is achieved, but compatibility with static IP address systems is lost
Solution Approach 1:
The system implements multiple network service support (DHCP, mDNS, and other alternatives) within the same provisioning framework, allowing the management controller to select appropriate services based on the system's IP configuration type. This multi-functional approach enables the provisioning solution to work with both dynamic and static IP address systems.
Solution Approach 2:
The provisioning system dynamically selects which network service to use based on the detected IP configuration. The management controller attempts DHCP first, and if unsuccessful or inappropriate, transitions to alternative services like mDNS. This dynamic adaptation resolves the contradiction by making the automation approach flexible rather than fixed.
2Adaptability or versatility
If multiple network services are supported, then compatibility with different IP configurations is improved, but system complexity increases
Solution Approach 1:
The management controller is pre-configured with knowledge of multiple network services and their purposes before provisioning begins. The system has predetermined fallback mechanisms and service selection logic already in place, eliminating the need for complex runtime decision-making and reducing operational complexity.
Solution Approach 2:
The provisioning system automatically detects which network service is appropriate and executes the provisioning process without requiring manual configuration or user intervention. The system self-determines whether to use DHCP, mDNS, or other services based on its configuration, eliminating the need for users to manage the complexity of multiple network services.
3Productivity
If DHCP service is used for provisioning, then automated configuration retrieval is achieved, but systems requiring static IP addresses cannot be provisioned
Solution Approach 1:
The system implements a dynamic service selection process where the management controller attempts DHCP first for rapid provisioning, but automatically transitions to alternative services like mDNS if DHCP is unavailable or inappropriate for static IP configurations. This dynamic approach maintains high productivity for DHCP-compatible systems while enabling support for static IP systems.
Solution Approach 2:
The management controller acts as an intermediary that mediates between the provisioning needs and available network services. It intelligently selects the appropriate service based on the system's IP configuration type, enabling fast DHCP-based provisioning when applicable while seamlessly transitioning to alternative mechanisms for static IP systems.
Data Source
AI summary
A disclosed touchless provisioning method configures a baseboard management controller (BMC) of a bare metal server to include or support two or more network services for retrieving a configuration profile locator (CPL) identifying a network-accessible configuration file containing a server configuration profile (SCP). At least one of the network services may be invoked to retrieve the CPL and pass the CPL to a provisioning agent process configured to access the configuration file and configure the system in accordance with the SCP. The server may require a static IP address and the two or more network services may include at least one network service, such as a multicast domain name service (mDNS), suitable for use in conjunction with a static IP address system and at least one network service, such as a DHCP service, suitable for use in conjunction with servers that do not require a static IP address.