Server Configuration and Deployment
eSight supports template-based server configuration and deployment. Administrators can define common server configurations, including RAID controller card, BIOS, and operating system information, as templates. After that they can create template-based deployment tasks to deploy configurations to servers in batches. The V300R010C00SPC500 version does not support this function. The V300R010C00SPC500 version having a patch version later than V300R010C00SPC500 installed also does not support this function.Versions upgraded from eSight V300R010C00 CP5022(Update tool 1.0) do not support this function.The V300R010C00CP5022 patch does not support this function.
Definition
eSight supports template-based server configuration and deployment. Administrators can define common server configurations, including RAID controller card, BIOS, and OS information, as templates. After that they can create template-based deployment tasks to deploy configurations to servers in batches.
Benefits
The server configuration and deployment function enables simple, automatic batch deployment of RAID, BIOS, OS, and other configuration, improving configuration and deployment efficiency, and reducing server O&M costs.
Application Scenario
Application scenarios on server configuration deployment are as follows:
- Server deployment
In server deployment scenarios, administrators need to upload image files to eSight, install OSs in batches using an OS template, and configure management network port IP addresses for the servers using a network template.
- Server maintenance
In server maintenance scenarios, administrators can create templates (such as BIOS, RAID, and network templates) and batch replication tasks (iBMC and BIOS) to configure servers in batches
Function
Server configuration and deployment implements the following:
- Template management
Administrators can create BIOS, RAID, OS, iBMC, CNA, switch module, network, and power control templates. After configuring configuration templates, administrators can use the template to generate typical configuration files quickly, which can then be used to deploy servers in batches.
- Task management
- By creating a template task, administrators can deliver the configuration in the template to devices according to the deployment policy.
- By creating a batch replication task, administrators can deliver the configuration of the source device to target devices according to the deployment policy.
- Software source management
Administrators can upload, change, or delete OS software packages.
Principle
Server configuration deployment supports two networking modes: fully outband and outband. The working principles of server configuration deployment vary depending on the networking mode.
Template Type |
Networking Mode |
Communication Mode |
Description |
|---|---|---|---|
BIOS, RAID, HBA, and CNA |
Fully outband |
The eSight server communicates with management IP addresses of servers. |
Servers use the management IP address to connect to eSight. |
Operating system, network, power-on and power-off, iBMC, and switch module |
Outband |
The eSight server communicates with management IP addresses of servers. |
Servers use the management IP address to connect to eSight. |
- Fully outband
Fully outband deployment is to deploy configurations on devices in batches using the small operating system automatically mounted by eSight.
In fully outband networking mode, eSight automatically mounts a small operating system to the virtual drive of a device. When the device boots from the operating system, eSight sends iBMC instructions to the device for device configuration.
- The IP address must be valid for the device to connect to eSight.
- The user must have permission on the IPMI protocol for a device to connect to eSight.
- The version of the iBMC must be 2.42 or later.
- Outband
In outband mode, the iBMC sends instructions to deploy devices in batches.
In outband networking mode, eSight sends iBMC instructions to devices for device configuration.
Fully Outband Configuration Deployment Principle
No. |
Description |
|---|---|
1 |
An administrator creates a configuration deployment task for a server on eSight. |
2 |
eSight automatically mounts a small operating system to the virtual drive of the server and delivers a restart command. |
3 |
The server obtains the configuration deployment file from eSight. |
4 |
eSight encapsulates the configuration information into XML files in a certain format and delivers the XML files to the server. |
5 |
The server automatically deploys configurations based on the XML files and sends the deployment result to eSight. |
6 |
The administrator views the configuration deployment result on eSight. |
Outband Configuration Deployment Principle
Figure 3-21 shows the working principle of outband configuration deployment.
No. |
Description |
|---|---|
1 |
An administrator creates a configuration deployment task for a server on eSight. |
2 |
The server obtains the configuration deployment file or command from eSight. |
3 |
eSight encapsulates the configuration information into XML files in a certain format and delivers the XML files to the server, or sends the command to the server. |
4 |
The server automatically deploys configurations based on the XML files or executes the command, and sends the deployment result to eSight. |
5 |
The administrator views the configuration deployment result on eSight. |
Application Restrictions
Restrictions When Southbound and Northbound Services Are Isolated
The network for isolating the southbound and northbound services is not applicable to the eSight multi-subnet scenario.
Southbound and northbound service isolation means that the southbound and northbound IP addresses of eSight are isolated. The northbound IP address is used to log in to the eSight UI, and the southbound IP address is used to communicate with servers.
- Scenario where the southbound and northbound services are not isolated
Multiple NICs on the eSight server can communicate with the servers.
The out-of-band and fully out-of-band networking modes are supported.
- Scenario where the southbound and northbound services are isolated
Only one NIC on the eSight server can communicate with the servers.
- The management plane IP address and the service plane IP address of the server are on the same plane.
The out-of-band and fully out-of-band networking modes are supported.
- The management plane IP address and the service plane IP address of the server are on different planes.
Only the out-of-band and fully out-of-band networking modes are supported.
- The management plane IP address and the service plane IP address of the server are on the same plane.
Application Restrictions
Application restrictions on configuration deployment are as follows:
- This function applies only to Huawei rack, blade, and high-density servers.
- To ensure that the configuration deployment function works properly, a maximum of 16 IP addresses can be set on a server where eSight is installed.
- Before administrators use the operating system configuration deployment function for the first time after eSight installation, they need to download and rename the ServiceCD or Smart Provisioning file, and copy it to a specified directory.
- When a template is deployed, the server will be restarted, causing service interruption.
- The switch module stacking configuration does not support inter-chassis stacking but supports only intra-chassis stacking.
- For the 8100 series devices, if multiple RAID controller cards are installed on the mainboard, eSight does not support RAID controller card configuration.
- The supported operating system specifications vary depending on the server model. Perform the following operations to query and confirm the operating system deployment specifications:
- For details about the supported operating system specifications, visit http://support.huawei.com/onlinetoolsweb/ftca
- eSight supports only operating systems supporting ServiceCD2.0-based installation or supporting Smart Provisioning-based installation in the query result of the compatibility query tool for automatic deployment.
- For the automatic operating system deployment on the V3 server, you need to upload the ServiceCD2.0 first. The download address of the ServiceCD2.0 is as follows: https://support.huawei.com/enterprise/en/servers/fusionserver-tools-pid-21015513
- For the automatic operating system deployment on the V5 server, you need to upload the Smart Provisioning first. The download address of the Smart Provisioning is as follows: https://support.huawei.com/enterprise/en/servers/smart-provisioning-pid-23143793
- For details about the operating system installation parameters, server software and hardware compatibility, and some installation restrictions, see the user guide of the ServiceCD2.0 or Smart Provisioning.
- The deployment task creation does not support the DST function.