Configuring Basic Service Data in Batches
You can use SmartKit to configure the BMCs, BIOSs, and RAIDs, and install the OSs in batches.
Four scenarios are proposed based on whether the RAID controller card can be configured using SmartKit and whether the OS can be installed using SmartKit. For details about how to configure RAID and install the OS in each scenario, see Table 1-4. For details about how to view the RAID controller card model, see Obtaining RAID Controller Card Information. This section uses scenario 1 as an example to describe how to perform RAID configuration and OS deployment in batches using the server deployment function.
For details about the RAID controller cards supported by SmartKit, see "Using SmartKit > Server Deployment > Compatibility List" in the FusionServer Tools x.x SmartKit User Guide (for Engineers). For details about the OSs supported by SmartKit, see "Using SmartKit > Performing the OS Deployment > Compatibility List" in the FusionServer Tools x.x SmartKit User Guide (for Engineers).
Scenario |
Whether the RAID Controller Card Can Be Configured Using SmartKit |
Whether the OS Can Be Installed Using SmartKit |
How to Configure RAID |
How to Install the OS |
---|---|---|---|---|
1 |
Yes |
Yes |
See Server Deployment. |
|
2 |
Yes |
No |
See "Using SmartKit > Hardware Configuration > Configuring the RAID" in the FusionServer Tools x.x SmartKit User Guide (for Engineers). |
See the corresponding OS installation guide obtained from A500 Pro-3000. |
3 |
No |
Yes |
See "Initial Configuration" in the Atlas 500 Pro AI Edge Server User Guide (Model 3000). |
See the corresponding OS installation guide obtained from A500 Pro-3000. |
4 |
No |
No |
For the Atlas 500 Pro AI edge server (model 3000), query whether SmartKit is supported based on the model of the RAID controller card and the OS to be installed. For details, see the corresponding scenario.
- You are advised to configure one server first and then configure the servers in batches. It is recommended that the number of servers to be operated in batches be less than or equal to 200.
During the process, do not perform operations such as power-on, power-off, and restart on servers.
Back up data before RAID configuration because the data on drives will be lost after RAID configuration.
The RAID controller card must support out-of-band management to implement RAID configuration.
- The RAID controller card models selected for batch configuration must be the same.
- During batch configuration, the device models, and iBMC, BIOS, and Smart Provisioning versions must be the same. This section uses the same device model, iBMC, BIOS, and Smart Provisioning version of all servers as an example. Otherwise, perform multiple server deployment tasks.
Prerequisites
- You have obtained the IP addresses of the BMC management network ports on servers.
- You have obtained the user names and passwords for logging in to the BMCs of servers.
- Ensure that a PC is properly communicating with the BMCs of target servers, the IPMI, SNMP, and SSH communication ports are enabled, and the server BMC IP addresses can be pinged from the local PC.
- You have planned the IP addresses and subnet masks of the service network ports on servers.
Importing BMC Devices in Batches
- On the Home page, click Devices.
- In the navigation pane on the left, choose Server.
- On the iBMC tab page, click
to download the device list template file ServerDeviceList_Template to the local host.
- Fill in the template by referring to Table 1-5. Figure 1-5 shows an example.
Table 1-5 Configuration items
Parameter
Setting
Start IP Address
IP address of the BMC management network port
If there is only one device, set this parameter to the value of Start IP. For example, the start IP address is 192.168.2.2 and the end IP address is 192.168.2.2.
- If multiple servers with consecutive IP addresses and the same user names and passwords are used, enter the start IP address and end IP address of each address segment.
- If multiple servers with inconsecutive IP addresses or different user names or passwords are used, configure the parameter in the same way as you do for a single device.
End IP Address
User Name
User name of the iBMC administrator. The default value is Administrator.
Password
Password of the iBMC administrator. For details, see the Atlas Hardware Product User List.
SNMP Port
Use the actual port number of the device. If the port number is not changed, use the default value.
IPMI Port
SSH/SFTP Port
VMM Port
HTTPS Port
Other Configuration Items
Leave them empty.
- After the editing is complete, click
, select the edited template file, and click OK to import the template.
Server Deployment
Before performing this operation, ensure that Importing BMC Devices in Batches has been completed.
- On the Home page, choose Server > Site Deployment Delivery > Server Deployment.
The Server Deployment wizard window is displayed.
- Click Device Selection and select devices for device variation in the device list.
- Click OK to return to the wizard window.
- Click Server Deployment.
The Server Deployment page is displayed.
- Click Download the import template to download the server deployment template file ServerDeploy_template_xx to the local PC.Open the Excel file. If the Protected View dialog box is displayed, click the message and click Enable Editing.
You can obtain help information in the following ways:
- Hover the cursor over a configuration item cell. The value description and configuration method are displayed.
- The BMC_details, BIOS_details(x86), BIOS_details(TaiShan), RAID_details, and OS_details sheets provide detailed description and examples of BMC, BIOS, RAID configuration, and OS deployment.
- Click the BMC tab and delete the example.
- Click the BIOS(TaiShan) tab and delete the example.
- Click the RAID tab and set parameters in the Logical Drive area.
Figure 1-6 shows a configuration example.
- Table 1-6 lists the parameters for configuring logical drives.
Enter a row of data for each logical drive.
To add a logical drive, copy a line of data, and modify the corresponding parameters.
Table 1-6 Logical drive parametersParameter
Setting
Operation
- If the value is 0, the existing logical drives are not cleared.
- If the value is 1 or 2, the existing logical drives are cleared.
RAID Level
Set this parameter based on the site requirements.
Values: 0, 1, 5, 6, 10, 50, 60.
Number of Drives per Span
Number of logical drive spans.
- If the RAID level is 0, 1, 5, or 6, you do not need to set this parameter.
- If the RAID level is 10, set this parameter to 2.
- If the RAID level is 50 or 60, set this parameter to 3.
Disk ID
Member drive list.
Enter the actual slot number of the drive. For example, the physical drive ID configuration example in Figure 1-6 indicates that the drives in slots 0, 1, 2, and 3 form RAID 0.
Value range: 0–63
Strip Size(KB)
Set this parameter to the planned data strip size on each logical drive.
This parameter is mandatory when Operation is set to 0 or 1.
Values: 64, 128, 256, 512, 1024.
Read Policy
Default read policy of the logical drive.
This parameter is mandatory when Operation is set to 0 or 1.
Values: ReadAhead, NoReadAhead
Write Policy
Default write policy of the logical drive.
This parameter is mandatory when Operation is set to 0 or 1.
Values: WriteThrough, WriteBackWithBBU, WriteBack.
I/O Policy
Default cache policy of the logical drive.
This parameter is mandatory when Operation is set to 0 or 1.
Values: CachedIO, DirectIO.
Disk Cache Policy
Cache policy of a member drive.
This parameter is mandatory when Operation is set to 0 or 1.
Values: Unchanged, Enabled, Disabled.
Access Policy
Access policy of the logical drive.
This parameter is mandatory when Operation is set to 0 or 1.
Values: ReadWrite, ReadOnly, Blocked.
Initialization State
Initialization mode of a logical drive.
This parameter is mandatory when Operation is set to 0 or 1.
Values: UnInit, QuickInit, FullInit.
Other Configuration Items
Leave them empty.
- Table 1-6 lists the parameters for configuring logical drives.
- Click the OS tab and set parameters.Figure 1-7 shows an example.
- Set common OS parameters by referring to Table 1-7.
Table 1-7 Common OS parameters
Parameter
Setting
System Type
OS type.
For example, CentOS7U6 indicates CentOS7.6.
System Version
OS version.
Example:
CentOS_aarch Linux 7. Update 6 aarch64 indicates CentOS 7.6 of the ARM architecture.
Language
Simplified Chinese
Keyboard
U.S. English
Time Zone
Asia/Shanghai
BIOS Boot Mode
UEFI
Image File Path
Path of the OS image file on the local PC, for example, D:\ISO\xxxxxxxxxx.iso.
- Set OS parameters by referring to Table 1-8.
Fill in one row for each server.
To add a server, copy a line of data, and modify the corresponding parameters.
Table 1-8 OS parametersParameter
Setting
DeviceIP
Configured IP address of the BMC management network port on the server where the OS is to be installed.
RootPwd
Initial password of the root user of the OS.
HostName
If you need to specify a name, enter a name consisting of 0 to 9, a to z, A to Z, and -. The name can contain a maximum of 15 characters.
Partition Information
Partition_Name
Partition name. The root directory / and swap partition must be configured. If multiple partitions are configured, separate the partition names with vertical bars (|), for example, /|swap|/home.
Partition_FileSystem
File system format. When configuring the multi-partition file system format, separate multiple partition names with slashes (/), for example, ext3/swap/ext3.
Partition_Size
Partition size, in GB. If multiple partitions are configured, separate the partition sizes with slashes (/), for example, 100/30/200.
Device_Name
Enter the actual network port names of the server. Use slashes (/) to separate multiple network ports, for example, eth0/eth1/eth2/eth3.
IPv4 Information
IPv4_AddressOrigin
Mode for obtaining the service IP address. The value can be DHCP or Static.
When IPv4_AddressOrigin is set to Static, IPv4_Address, IPv4_SubnetMask, and IPv4_Gateway are mandatory.
IPv4_Address
Planned BMC service IP address.
IPv4_SubnetMask
Planned subnet mask.
IPv4_Gateway
Gateway address.
Other Configuration Items
Leave them empty.
The number of IPv4_AddressOrigin must be the same as the number of Device_Name.
- Set common OS parameters by referring to Table 1-7.
- After the template file is configured, click Set Parameters on the Server Deployment page. In the Configuration Mode area, select Import Template, as shown in Figure 1-8. Then click Next.
- On the Obtain Device Information page, select a device and click Obtain the information, as shown in Figure 1-9. After the configuration information is obtained, click Next.
- Click Select Template, select the edited template file, and click OK to import the template.
- Click Finish and then click OK.
- Click Deploy, identify and confirm the precautions, and click OK.
The system starts the deployment.
You can set the number of servers that can be operated in batches at the same time in the Number of concurrent tasks (1 to 50) text box. The value ranges from 1 to 50. The default value is 20.
- Exit the wizard after the configuration is complete.
Changing a Password
You are advised to change the initial iBMC user password, U-Boot password, and BIOS password of the server. The U-Boot password and BIOS password cannot be configured in batches.
- For details about how to change the iBMC user password, see "Using SmartKit > Hardware Configuration > Configuring the iBMC" in the FusionServer Tools x.x SmartKit User Guide (for Engineers).
- For details about how to change the U-Boot and BIOS passwords, see "Initial Configuration" > "Changing the iBMC Initial Password" and "Initial Configuration" > "Configuring the BIOS" respectively in the Atlas 500 Pro AI Edge Server User Guide (Model 3000).