No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

Smart Provisioning User Guide 09

Rate and give feedback :
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Deployment Process Description

Deployment Process Description

Setting SP to Enter OS Deploying Process After the SP Starts

Function

Before OS deployment, eSight sets the type of the operating system to be deployed on the systeminfo interface of the server. After the SP is started, the SP reads information from the systeminfo and performs subsequent operations.

Format

Write the following character string to Systeminfo: operator:eSight;osType: ESXi6.5_x64.

Table 3-30 Key value description

Key Value

Key Value Description

Value

operator

Process to configure eSight OS deployment

eSight

osType

Specifies the OS type. Only x64 is supported.

  • ESXi6.0_x64
  • ESXi6.5_x64
  • ESXi6.7_x64
  • CentOS6U9_x64
  • CentOS7U3_x64
  • CentOS7U4_x64
  • CentOS7U5_x64
  • RHEL6U9_x64
  • RHEL7U3_x64
  • RHEL7U4_x64
  • RHEL7U5_x64
  • SLES12SP2_x64
  • SLES12SP3_x64
  • SLES11SP4_x64
  • Ubuntu16.04_x64
  • Ubuntu16.04.1_x64
  • Ubuntu16.04.2_x64
  • Win2012_R2_x64
  • Win2016_x64
Usage Guideline

Write in operator:eSight;osType: After osversion, mount the SmartProvisioning CD-ROM through the KVM, set the boot from the CD-ROM, and restart the x86 system.

After the SP is loaded, check the system Info information. If the keyword operator:eSight is detected, the OS deployment process is started. Otherwise, the SP man-machine interaction interface is displayed.

After entering the OS deployment process, the SP performs the following operations:

  • Copy the driver from the CD-ROM.
  • After the driver is copied, write the response information progress:step1;result:successful;errorCode:0 to the systeminfo.
Example
  1. Write request: operator:eSight;osType:ESXi6.7_x64
  2. After writing, the SP waits for the response. After receiving the request, the SP processes the request and writes the processing result to the System Info.

  3. Read response.

    Table 3-31 lists response contents.

    Table 3-31 Description of response contents

    Field

    Field Description

    Returned Value Description

    progress

    Processing progress

    Step 1: Start and copy the driver.

    result

    Result

    • Successful
    • Failed

    errorCode

    Error code

    • 0: successful
    • 104: Failed to copy the driver.

Setting the Flag for Transmitting OS Configuration Parameter Files

Function

Before installing the operating system, you need to send installation parameter configuration files to the SP and write a specified flag to instruct the SP to receive the files.

Format

Write the following character string to Systeminfo: oscfg:start.

Table 3-32 Key value description

Key Value

Key Value Description

Value

oscfg

Indicates that the OS configuration parameters are to be transferred.

start

Usage Guideline

None

Example
  1. Write request oscfg:start.
  2. After writing, the SP waits for the response. After receiving the request, the SP processes the request and writes the processing result to the System Info.
  3. Read response.
    Table 3-33 lists response contents.
    Table 3-33 Description of response contents

    Field

    Field Description

    Returned Value Description

    oscfg

    Processing progress

    Next: Processing completed. Transfer the next one.

Transferring Configuration File

Function

Send operating system configuration files to the SP through the System Info. The configuration files are encoded using Base64. The encoded configuration file is divided by 200 bytes. Two hundred bytes are transferred each time. When a block with less than 200 bytes is transferred for the last time, :end is added to the end of the character string.

Format

The character string encoded by Base64 is written to System Info. A maximum of 200 bytes can be transferred at a time.

  • The format of a 200-byte character string: oscfg:xxx (enter 200 bytes)
  • The format of a string of less than 200 bytes: oscfg:xxx (enter 0–199 bytes): end
Table 3-34 Key value description

Key Value

Key Value Description

Value

oscfg

Content of the transferred files

  • The format of a 200-byte character string: xxx (enter 200 bytes)
  • The format of a string of less than 200 bytes: oscfg:xxx (enter 0–199 bytes): end
Table 3-35 Configuration file description

Parameter

Description

Value

Mandatory or Not

position

Media for deploying the operating system

NOTICE:

Deploying the OS will cause data loss on the /USB device where the OS is to be installed. Before deploying the OS, remove important data or /USB devices that are not required to prevent data loss.

  • disk selection sequence:
    1. M.2 disk of the Avago SAS3004RAID card
    2. SATA straight-through hard disk in slot 0
    3. Boot disk set for the RAID controller card
    4. NVME pass-through hard disk in slot 0 or Slot 44
    5. If the hard disk cannot be found, the deployment stops.
  • USB disk selection sequence: Sort the queried USB devices by device names and select the first USB device.
  • sanboot disk selection strategy (only for the VMware system): Preferentially select the first sanboot device. If the first device does not exist, search for the next device.
  • Disk: hard disk
  • USB: USB flash drive
  • sanboot: Network hard disk (only supported by the VMware system)

Mandatory

mode

Installation mode

  • 1: standard mode (default value)
  • 2: full mode
  • 3: user-defined mode
  • 1
  • 2
  • 3

Optional

ostype

Indicates operating system types. This parameter is used only when the Windows operating system needs to distinguish the Standard/DataCenter version. The default value is Standard.

The value is defined based on the operating system.

Optional

language

Indicates language options.

The value is defined based on the operating system. For example:

  • en_US
  • zh_CN

Optional

timezone

Indicates time zones.

The value is defined based on the operating system. For example:
  • America/New_York
  • Asia/Shanghai

Optional

keyboard

Indicates the keyboard layout.

The value is defined based on the operating system. For example: US

Optional

cdkey

Indicates cdkey required for the Windows CD-ROM.

Indicates a character string, for example: xxx-xxx-xxx-xxx.

Optional

password

Indicates the default password of the OS administrator. If this parameter is not set, the password is blank. Special characters of XML, for example, <>, are not allowed.

String

Optional

hostname

Indicates the OS host name, which cannot contain special characters of XML, such as <>.

String

Optional

partitions

Indicates a hard disk partition node contains one or more partition nodes. Each partition node refers to the partition information on a hard disk. If this parameter is left blank, the operating system automatically configures partitions.

Partition subnode ID

Optional

partition

Indicates partition information of a hard disk. If there are multiple partitions, use vertical bars (|) to separate them. The partition is in the unit of Mbyte. If the last partition is 1, the remaining space is used.

  • The format in the Windows: Mount point: File format: Capacity, for example, C:NTFS:50000|D:NTFS:100000.
  • The format in the Linux: Mount point: File format: Capacity, for example, swap:swap:10000|/:ext3:1.

Optional

software

Indicates the software deployment tool. Currently, only iBMA is supported.

iBMA

Optional

Usage Guideline

Before files are transferred, they are encoded in Base64 mode, and then split into blocks of 200 bytes. One block is transferred each time, and the next block is transferred after the response is received.

Example
  1. The format of a 200-byte character string is as follows:
  • Write request: oscfg:xxx (enter 200 bytes).
  • After writing, the SP waits for the response. After receiving the request, the SP processes the request and writes the processing result to the System Info.
  • Read response.
    Table 3-36 lists response contents.
    Table 3-36 Description of response contents

    Field

    Field Description

    Returned Value Description

    oscfg

    Processing progress

    Next: Processing completed. Transfer the next one.

2. The format of a character string of less than 200 bytes:

  • Write request: oscfg:xxx (enter 0-199 bytes): end.
  • After writing, the SP waits for the response. After receiving the request, the SP processes the request and writes the processing result to the System Info.
  • Read response.
    Table 3-37 lists response contents.
    Table 3-37 Description of response contents

    Field

    Field Description

    Returned Value Description

    progress

    Processing progress

    Step 2: Transfer configuration parameters in this step.

    result

    Result

    • Successful
    • Failed

    errorCode

    Error code

    • 0: successful
    • 101: Failed to obtain configuration files.

(Optional) Transferring OS User-Defined Response File

Function

If the configuration parameter mode is set to 3 (customized mode), the response file needs to be transferred to the SP through the CD-ROM drive.

Format

Write the following character string to Systeminfo: autoinstFileName:autoinst.xml.

Key value description

Key Value

Key value description

Value

autoinstFileName

Name of response files

Character string. For example, autoinst.xml.

Usage Guideline

After the OS configuration parameter file is transferred, if the installation mode is customized, mount the configuration file by using the KVM, and then send the file name parameter to instruct the SP to copy the corresponding response file from the CD-ROM.

Example
  1. Write request: autoinstFileName:autoinst.xml.
  2. After writing, the SP waits for the response. After receiving the request, the SP processes the request and writes the processing result to the System Info.
  3. Read response.
    Table 3-38 lists response contents.
    Table 3-38 Description of response contents

    Field

    Field Description

    Returned Value Description

    progress

    Processing progress

    Step 2: Transfer configuration parameters in this step.

    result

    Result

    • Successful
    • Failed

    errorCode

    Error code

    • 0: successful
    • 106: Failed to obtain response files.

Notifying the SP to Start Installing

Function

After the OS configuration files are transferred, you can mount the OS installation image and instruct the SP to start installation.

Format

Write the following character string to Systeminfo: osinstall:start.

Table 3-39 Key value description

Key Value

Key value description

Value

osinstall

The OS installation begins.

Start: instruct the SP to start the installation.

Usage Guideline

After the OS configuration files are transferred, you can mount the OS installation image and instruct the SP to start installation.

Example
  1. Write request: osinstall:start.
  2. After writing, the SP waits for the response. After receiving the request, the SP processes the request and writes the processing result to the System Info.
  3. Read response.

    Table 3-40 lists response contents.

    Table 3-40 Description of response contents

    Field

    Field Description

    Returned Value Description

    progress

    Processing progress

    • Step 3: The command for starting the installation is received.
    • Step 4: The OS installation completed.

    result

    Result

    • Successful
    • Failed

    errorCode

    Error code

    • 0: successful
    • 101: waiting
    • 113: Failed to check the CDROM. The possible cause is that the image does not match.

Viewing Installation Progress

Function

After the SP starts the installation, you can view the installation progress over System Info.

Format

Run a specific command to read the character string in system info.

Example

Table 3-41 lists response contents.

Table 3-41 Description of response contents

Field

Field Description

Returned Value Description

result

Installation progress

  • 1: completed 45%
  • 2: completed 60%
  • 3: completed 75%
  • 5: completed 100%
Translation
Download
Updated: 2019-05-11

Document ID: EDOC1100034052

Views: 26789

Downloads: 342

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next