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

FusionServer Tools 2.0 uMate User Guide 37

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).
CLI

CLI

Inspecting Servers

Scenarios

Use the uMate CLI to inspect servers.

NOTE:
  • You are advised to perform a PMI on one server. If the PMI is successful, perform batch PMIs. It is recommended that the number of servers for batch operation be less than 200.
  • For details about how to handle the problems occurring during the operation process, see Troubleshooting.
  • The OSs installed on VMs (for example, VMware VMs) do not support PMI using uMate.
Prerequisites

Conditions

  • The PC is properly communicating with the BMC or HMM of each target server. The IPMI, SNMP, SSH, and VMM communication ports are enabled. Ensure that the server BMC or HMM IP address is pinged from the local PC.

    If you want to connect your local PC directly to the MM910 using a network cable but the MGMT port on the active MM910 is already connected with a network cable, do not remove the network cable from the MGMT port on the active MM910. Otherwise, an active/standby switchover of the MM910s will be triggered, which may cause network interruption. You can connect the network cable from the local PC to the STACK port of the active MM910 in the chassis. If the STACK port on the active MM910 is also used, connect the network cable to an idle STACK port on an active MM910 in a chassis cascaded with the E9000 chassis.

  • Check whether the server is compatible. For details, see Compatibility List.
  • Check whether the environment meets the uMate running requirements. For details, see Environmental Requirements.

Data

The following data needs to be prepared before the operation is performed:

  • IP address of the server BMC or HMM management network port. The IP address indicates only the IPv4 address.
  • User name and password of the server BMC or HMM
Procedure
  1. Run the following command to go to the uMate directory.

    cd

    [root@localhost /]# cd home/uMate-Linux-Vxxx/ 
    [root@localhost uMate-Linux-Vxxx]# ls 
    bin  config  help  hwServers.xls  hwServers.xml  image  jre  lib  serviceConf.xml  template  tools  uMate_CLI.sh  uMate.sh

  2. Run the following command to modify the hwServers.xml configuration file and run the :wq command to save the settings and exit. For details, see Table 4-12.

    The configuration file contains user data. Delete it after use.

    vi hwServers.xml

    NOTE:
    • If there are multiple servers, add multiple Servers nodes.
    • The .xml configuration file cannot contain the following special characters. If the following special characters need to be used in the configuration file, you must convert them as follows:
      • Convert & to &.
      • Convert < to &lt;.
      • Convert > to &gt;.
      • Convert " to &quot;.
      • Convert ' to &apos;.

      For example, convert huawei&123 to huawei&amp;123.

  3. Run the following command to inspect servers:

    ./uMate_CLI.sh inspect hwServers.xml

    [root@localhost uMate-Linux-Vxxx]# ./uMate_CLI.sh inspect hwServers.xml 
    IPAddress        ProductName         SerialNumber             Result 
    10.10.10.10      RH2288 V3           2102311NQP10G9000002     Minor 
    Summary: 
    1) total inspect 1 servers,OK 0,Major 0,Minor 1,Unknown 0 
    2) detail log in work/Inspect/20171012165415/

    Table 4-63 describes the parameters.

    NOTE:

    You can use the output.xml file in the uMate-Linux-Vxxx/work/Inspect/Date+Time+Number directory (for example, uMate-Linux-V138/work/Inspect/20171012165415) to view the inspection results.

    Table 4-63 Item description

    Item

    Description

    IPAddress

    Specifies the server IP address. The IP address indicates only the IPv4 address.

    ProductName

    Specifies the server name.

    NOTE:

    This item specifies the HMM name if a blade server is used.

    SerialNumber

    Specifies the server serial number.

    Result

    Specifies the server inspection result.

    • OK
    • Warning
    • Minor
    • Major
    • Critical
    • Unknown

Collecting Server Logs

Scenarios

Use the uMate CLI to collect server logs.

NOTE:
  • You are advised to collect logs on one server. If the log collection task is successful, perform batch log collection. It is recommended that the number of servers for batch operation be less than 200.
  • For details about how to handle the problems occurring during the operation process, see Troubleshooting.
  • The user who performs log collection must be the first administrator in the BMC or HMM local user list.
  • Does not support collection of switch module logs on the CLI.
  • For the log items that can be collected, see Log Collection Items.
Prerequisites

Conditions

  • The PC is properly communicating with the BMC or HMM of each target server. The IPMI, SNMP, and SSH communication ports are enabled. Ensure that the server BMC or HMM IP address is pinged from the local PC.

    If you want to connect your local PC directly to the MM910 using a network cable but the MGMT port on the active MM910 is already connected with a network cable, do not remove the network cable from the MGMT port on the active MM910. Otherwise, an active/standby switchover of the MM910s will be triggered, which may cause network interruption. You can connect the network cable from the local PC to the STACK port of the active MM910 in the chassis. If the STACK port on the active MM910 is also used, connect the network cable to an idle STACK port on an active MM910 in a chassis cascaded with the E9000 chassis.

  • Check whether the server is compatible. For details, see Compatibility List.
  • Check whether the environment meets the uMate running requirements. For details, see Environmental Requirements.

Data

The following data needs to be prepared before the operation is performed:

  • IP address of the server BMC or HMM management network port. The IP address indicates only the IPv4 address.
  • User name and password of the server BMC or HMM
Procedure
  1. Run the following command to go to the uMate directory.

    cd

    [root@localhost /]# cd home/uMate-Linux-Vxxx/ 
    [root@localhost uMate-Linux-Vxxx]# ls 
    bin  config  help  hwServers.xls  hwServers.xml  image  jre  lib  serviceConf.xml  template  tools  uMate_CLI.sh  uMate.sh

  2. Run the following command to modify the hwServers.xml configuration file and run the :wq command to save the settings and exit. For details, see Collecting Server Logs.

    The configuration file contains user data. Delete it after use.

    vi hwServers.xml

    NOTE:
    • If there are multiple servers, add multiple Servers nodes.
    • The .xml configuration file cannot contain the following special characters. If the following special characters need to be used in the configuration file, you must convert them as follows:
      • Convert & to &amp;.
      • Convert < to &lt;.
      • Convert > to &gt;.
      • Convert " to &quot;.
      • Convert ' to &apos;.

      For example, convert huawei&123 to huawei&amp;123.

  3. Run the following command to collect server logs:

    ./uMate_CLI.sh logcollect hwServers.xml

    [root@localhost uMate-Linux-Vxxx]# ./uMate_CLI.sh logcollect hwServers.xml 
    IPAddress        ProductName         SerialNumber             Result 
    10.10.10.10      RH2288 V3           2102311NQP10G9000002     PASS 
    Summary: 
    1) total log collect 1 servers,PASS 1,FAIL 0 
    2) detail log in work/LogCollect/20171012165610/

    Table 4-64 describes the parameters.

    Table 4-64 Item description

    Item

    Description

    IPAddress

    Specifies the server IP address. The IP address indicates only the IPv4 address.

    ProductName

    Specifies the server name.

    NOTE:

    This item specifies the HMM name if a blade server is used.

    SerialNumbe

    Specifies the server serial number.

    Result

    Specifies the server log collection result.

    • PASS: indicates that the log collection is successful.
    • Failed: indicates that the log collection fails.

  4. Run the following command to go to the uMate-Linux-Vxxx/work/LogCollect/Date+Time+Number directory (such as uMate-Linux-V138/work/LogCollect/20171012165610):

    cd

    [root@localhost uMate-Linux-Vxxx]# cd work/LogCollect/20171012165610/ 
    [root@localhost 20171012165610]# ls 
    172.100.15.22  output.xml

    You can use the output.xml file to view the log collection results and view the collected logs based on IP addresses.

Upgrading Server Firmware

Scenarios

Use the uMate CLI to upgrade the server BMC, BIOS, and mainboard CPLD.

NOTE:
  • You are advised to upgrade the firmware on one server. If the upgrade is successful, perform batch firmware upgrades. It is recommended that the number of servers for batch operation be less than 200.
  • For details about how to handle the problems occurring during the operation process, see Troubleshooting.
  • Before the upgrade, check whether power capping is enabled. If power capping fails during the firmware upgrade, services may be interrupted.
  • Perform firmware upgrade and power control operations only when services are offline. Otherwise, services may be interrupted.
  • Do not power on, power off, or reset the server, reset the BMC, or remove or install boards during a firmware upgrade.
Prerequisites

Conditions

  • The PC is properly communicating with the BMC of each target server. The IPMI, SNMP, SSH, and VMM communication ports are enabled. Ensure that the server BMC IP address is pinged from the local PC.
  • Check whether the server is compatible. For details, see Compatibility List.
  • Check whether the environment meets the uMate running requirements. For details, see Environmental Requirements.

Data

The following data needs to be prepared before the operation is performed:

  • IP address of the server BMC or HMM management network port. The IP address indicates only the IPv4 address.
  • User name and password of the server BMC or HMM

Software

Server BMC, BIOS, and mainboard CPLD software packages (in .zip format)

Procedure
  1. Upload upgrade packages to the server directory. For details, see Uploading the Software Package.
  2. Run the following command to go to the uMate directory.

    cd

    [root@localhost /]# cd home/uMate-Linux-Vxxx/ 
    [root@localhost uMate-Linux-Vxxx]# ls 
    bin  config  help  hwServers.xls  hwServers.xml  image  jre  lib  serviceConf.xml  template  tools  uMate_CLI.sh  uMate.sh

  3. Run the following command to modify the hwServers.xml configuration file and run the :wq command to save the settings and exit. For details, see Upgrading Server Firmware by Using the BMC.

    The configuration file contains user data. Delete it after use.

    vi hwServers.xml

    NOTE:
    • If there are multiple servers, add multiple Servers nodes.
    • The .xml configuration file cannot contain the following special characters. If the following special characters need to be used in the configuration file, you must convert them as follows:
      • Convert & to &amp;.
      • Convert < to &lt;.
      • Convert > to &gt;.
      • Convert " to &quot;.
      • Convert ' to &apos;.

      For example, convert huawei&123 to huawei&amp;123.

  4. Run the following command to view the upgrade help information.

    ./uMate_CLI.sh FWUpgrade

    [root@localhost uMate-Linux-Vxxx]# ./uMate_CLI.sh FWUpgrade 
    No parameter provided! 
    Usage: FWUpgrade -f upgradefile.zip -s hwServers.xml -n
      upgradefile.zip:the upgrade file. 
      hwServers.xml:the target server information for upgrade.
      -n:After the firmware is upgraded, the tool does not perform any power control operation.
    NOTE:
    • upgradefile.zip indicates the upgrade package path. The path can be a relative path of uMate_CLI.exe or a full path. If spaces exist in the path, you need to place the path into double quotation marks.
    • -n is an optional parameter. If the -n parameter is used, the tool does not automatically perform power control operations after the firmware upgrade is complete. You need to manually perform power control operations to make the firmware upgrade take effect. If the -n parameter is not used, the tool automatically performs power control operations after the firmware upgrade is complete.

  5. Run the following command to upgrade server firmware:

    ./uMate_CLI.sh FWUpgrade -f "RH2288 V3-BIOS-V350.zip" -s hwServers.xml

    [root@localhost uMate-Linux-Vxxx]# ./uMate_CLI.sh FWUpgrade -f "RH2288 V3-BIOS-V350.zip" -s hwServers.xml 
    Tool Version : FusionServer Tools-uMate V138 
    Get all target devices successfully. 
    Parse upgrade file successfully. 
    Upgrade module:BIOS,upgrade version:3.50,active mode:ResetServer. 
    Check upgrade environmental successfully. 
    Upgrade task start... 
    172.100.15.22 Product Name:RH2288 V3;iBMC Version:2.56;BIOS Version:3.25 
    172.100.15.22 upgrade progress:3. 
    172.100.15.22 upgrade progress:4. 
    172.100.15.22 upgrade progress:5. 
    172.100.15.22 upgrade progress:7. 
    172.100.15.22 upgrade progress:9. 
    172.100.15.22 upgrade progress:11. 
    172.100.15.22 upgrade progress:13. 
    172.100.15.22 upgrade progress:16. 
    172.100.15.22 upgrade progress:56. 
    172.100.15.22 upgrade progress:63. 
    172.100.15.22 upgrade progress:69. 
    172.100.15.22 upgrade progress:71. 
    172.100.15.22 upgrade progress:73. 
    172.100.15.22 upgrade progress:76. 
    172.100.15.22 upgrade progress:81. 
    172.100.15.22 upgrade progress:84. 
    172.100.15.22 upgrade progress:86. 
    172.100.15.22 upgrade progress:89. 
    172.100.15.22 upgrade progress:91. 
    172.100.15.22 upgrade progress:93. 
    172.100.15.22 upgrade progress:98. 
    172.100.15.22 upgrade successfully 
     
     
    Summary: 
    1) total upgrade 1 servers,PASS 1,FAIL 0 
    2) detail log in work/FWUpgrade/20170712171459/
    NOTE:
    • The mode used for the upgrade to take effect is determined by the value of ActiveMode in the version.xml file in the upgrade package.
    • You can use the output.xml file in the uMate-Linux-Vxxx/work/FWUpgrade/Date+Time+Number directory (for example, uMate-Linux-V138/work/FWUpgrade/20170712171459) to view the upgrade results.

Configuring the BIOS

Scenarios

Use the uMate CLI to configure the BIOS.

NOTE:
  • The batch operation does not support different models of servers. You are advised to configure the BMC on one server. If the BMC configuration is successful, perform batch BMC configurations. It is recommended that the number of servers for batch operation be less than 200.
  • For details about how to handle the problems occurring during the operation process, see Troubleshooting.
  • During the configuration, do not reset or power off and on the servers.
  • Manually reset the system or reset the system using uMate for the BIOS configuration to take effect.
  • If the BIOS information of a slot is configured through Stateless Computing configuration on the MM910 WebUI, the BIOS of the node in the slot cannot be configured using uMate.
Prerequisites

Conditions

  • The PC is properly communicating with the BMC of each target server. The IPMI, SNMP, and SSH communication ports are enabled. Ensure that the server BMC IP address is pinged from the local PC.
  • Check whether the server is compatible. For details, see Compatibility List.
  • Check whether the environment meets the uMate running requirements. For details, see Environmental Requirements.

Data

The following data needs to be prepared before the operation is performed:

  • IP address of the server BMC or HMM management network port. The IP address indicates only the IPv4 address.
  • User name and password of the server BMC or HMM
Procedure
  1. Run the following command to go to the uMate directory.

    cd

    [root@localhost /]# cd home/uMate-Linux-Vxxx/ 
    [root@localhost uMate-Linux-Vxxx]# ls 
    bin  config  help  hwServers.xls  hwServers.xml  image  jre  lib  serviceConf.xml  template  tools  uMate_CLI.sh  uMate.sh

  2. Run the following command to view the BIOS configuration help information:

    ./uMate_CLI.sh BIOSConfig

    [root@localhost uMate-Linux-Vxxx]# ./uMate_CLI.sh BIOSConfig 
    No command provided! 
    Usage: BIOSConfig [options...] <command> 
    options 
        -H hostname      Remote iBMC IP address 
        -U username      Remote username 
        -P password      Remote password 
        -I IPMI port     Remote IPMI port [default=623] 
        -d               Re-download BIOS config file 
    commands 
        -r nodename      BIOS node name 
        -s               Start BIOS config 
        -w nodename value 
            nodename     BIOS node name 
            value        BIOS node value to set 
        -e               End BIOS config, configuration effect after reset system 
        -g templatefile 
            templatefile Generation BIOS configuration template 
        -f templatefile 
            templatefile Write BIOS config settings by this file 
        -b input.xml changed.ini 
            input.xml    Devices information for config 
            changed.ini  BIOS config file 
     
    

    Table 4-65 describes the parameters.

    Table 4-65 Parameter description

    Parameter

    Description

    Remarks

    -H hostname

    Specifies the BMC IP address.

    -U username

    Specifies the name of an BMC user who has administrator rights.

    -P password

    Specifies the iBMC user password.

    -I IPMI port

    Specifies the IPMI port number.

    The default value is 623.

    -d

    Specifies whether to download the configuration file again.

    Set this parameter when you need to obtain the BIOS configuration or export the configuration file to a template. This parameter must be used with -r or -g.

    -r nodename

    Obtains the values of BIOS configuration items.

    You can run -d to download the latest configuration file.

    -s

    Starts BIOS configuration.

    The configuration data entered by -w will be cleared.

    -w nodename value

    Sets configuration items.

    Run the -s command before setting configuration items.

    -e

    Stops BIOS configuration and delivers the configuration to servers.

    -g templatefile

    Exports the server configuration file into a template file.

    The template can be used for batch configuration or be provided on the GUI. You can run -d to download the latest configuration file.

    -f templatefile

    Uses the configuration file to configure the BIOS of a single server.

    V5 servers are not supported.

    -b input.xml changed.ini

    Configures BIOSs in batches by using a configuration file.

  3. Obtain the BIOS configuration.

    1. Export the value information of all BIOS configuration items of the server to a local file, for example, template.ini.
      NOTE:
      • If the file name contains special characters such as spaces, you need to place the template file in double quotation marks.
      • The exported file is saved in the uMate-Linux-Vxxx directory by default.
      [root@localhost uMate-Linux-Vxxx]# ./uMate_CLI.sh BIOSConfig -H 10.10.10.10 -U **** -P ********* -d -g template.ini
      Generate BIOS configuration start ...
      Generate BIOS config successfully.
      • Figure 4-356 shows the template.ini file exported from a V2 or V3 server. The first column indicates the description of BIOS configuration items, the third column indicates the available values of BIOS configuration items, and the fourth column indicates the current values of BIOS configuration items.
        Figure 4-356 template.ini

        Go to the uMate-Linux-Vxxx\work\BIOSConfig\tmp\BMC IP\ directory and open the display0.ini file using a tool, as shown in Figure 4-357. The first column indicates the description of BIOS configuration items, the second column indicates the names of BIOS configuration items (for example, the italic characters in Figure 4-357 indicate the names in the BIOS interface), and the third column indicates the available values of BIOS configuration items.

        Figure 4-357 display0.ini
      • Figure 4-358 shows the template.ini file exported from a V5 server. The first column indicates the description of BIOS configuration items, and the second column indicates the current values of BIOS configuration items.
        Figure 4-358 template.ini

        Go to the uMate-Linux-Vxxx\work\BIOSConfig\tmp\BMC IP\ directory and open the registry.json file using a tool (for example, the Notepad++ tool on which the JSON Viewer plug-in is installed). Select all content of the file and load the JSON Viewer plug-in. The registry.json file shown in Figure 4-359 is displayed. The values of DisplayName indicate the names of BIOS configuration items (the names in the BIOS interface), the values of AttributeName indicate the description of BIOS configuration items, and the values of ValueName in the Value area indicate the available values of BIOS configuration items.

        Figure 4-359 registry.json
        NOTE:

        To configure one BIOS configuration item of a server, go to 4. To configure multiple BIOS configuration items of a server, go to 5 to 7.

  4. Configure one BIOS configuration item of a server.

    1. Use the -r parameter to obtain the BIOS configuration item value.
       ./uMate_CLI.sh BIOSConfig -H 10.10.10.10 -U **** -P  ********* -r BootTypeOrder[0] 
    2. Use the -s parameter to start the BIOS configuration.
       ./uMate_CLI.sh BIOSConfig -H 192.168.2.98 -U **** -P ********* -s   
    3. Use the -d and -w parameters to set the BIOS configuration item value.
      ./uMate_CLI.sh BIOSConfig -H 192.168.2.98 -U **** -P ********* -d -w BootTypeOrder[0] 2
    4. Use the -e parameter to end the BIOS configuration, and deliver the configuration result to the server.
      ./uMate_CLI.sh BIOSConfig -H 192.168.2.98 -U **** -P ********* -e 
    NOTE:
    • You can also restart the OS to view the BIOS configuration item.
    • BootTypeOrder[0] indicates the BIOS configuration item description AttributeName. In BootTypeOrder[0] 2, 2 indicates the BIOS configuration item value ValueName.
    • For details about the BIOS configuration item description AttributeName and value ValueName, see the display0.ini file in 3 for V3 servers and the registry.json file in 3 for V5 servers.
    • After step 4 is performed, if you need to make the configuration take effect immediately, go to 8 and 9.

  5. Edit the template.ini file.

    • For a V2 or V3 server, you can refer to the display0.ini file to edit the current values (only digits are supported) of BIOS configuration items in the template.ini file.
    • For a V5 server, you can refer to the registry.json file to edit the current values (the values must be the same as those of ValueName in the registry.json file) of BIOS configuration items in the template.ini file.
    NOTE:

    For details about the BIOS configuration items and their values, see the parameter reference document of each BIOS platform.

  6. Run the following command to modify the hwServers.xml configuration file and run the :wq command to save the settings and exit. For details, see Table 4-42.

    The configuration file contains user data. Delete it after use.

    vi hwServers.xml

    NOTE:
    • If there are multiple servers, add multiple Servers nodes.
    • The .xml configuration file cannot contain the following special characters. If the following special characters need to be used in the configuration file, you must convert them as follows:
      • Convert & to &amp;.
      • Convert < to &lt;.
      • Convert > to &gt;.
      • Convert " to &quot;.
      • Convert ' to &apos;.

      For example, convert huawei&123 to huawei&amp;123.

  7. Run the following command to configure BIOSs in batches.

    ./uMate_CLI.sh BIOSConfig -b hwServers.xml template.ini

    [root@localhost uMate-Linux-Vxxx]# ./uMate_CLI.sh BIOSConfig -b hwServers.xml template.ini 
    Begin discover devices ... 
    IPAddress        ProductName         SerialNumber             Result 
    10.10.10.10      RH2288 V3           2102311NQP10G9000002     PASS 
    Summary: 
    1) total discover 1 servers,PASS 1,FAIL 0 
    2) detail log in work/BIOSConfig/20171012135204/ 
    End discover devices. 
     
    Begin BIOS Configuration 
    IPAddress        ProductName         SerialNumber             Result 
    10.10.10.10      RH2288 V3           2102311NQP10G9000002     PASS 
    Summary: 
    1) total config 1 servers,PASS 1,FAIL 0 
    2) detail log in work/BIOSConfig/20171012135204/20171012135230/

  8. Run the following command to restart the server system.

    reboot

  9. (Optional) Run the following command to add the -d parameter and download the latest BIOS configuration file.

    D:\uMate\FusionServer Tools-uMate-Win-Vxxx>./uMate_CLI.sh BIOSConfig -H 1******* -U **** -P ********* -d -r BootTypeOrder[0] 
    Current value: 2:Hard Disk Drive 
    Range: 2:Hard Disk Drive/3:CD or DVD-ROM Drive/128:PXE/238:Other

NOTE:

If a system boot option is configured, the system starts from the boot option when the server is started next time.

Mounting Virtual Media

Scenarios

Use the uMate CLI to mount virtual media.

NOTE:

For details about how to handle the problems occurring during the operation process, see Troubleshooting.

During the configuration, do not reset or power off and on the servers.

Prerequisites

Conditions

  • The PC is properly communicating with the BMC or HMM of each target server. The IPMI, SNMP, SSH, and VMM communication ports are enabled. Ensure that the server BMC or HMM IP address is pinged from the local PC.

    If you want to connect your local PC directly to the MM910 using a network cable but the MGMT port on the active MM910 is already connected with a network cable, do not remove the network cable from the MGMT port on the active MM910. Otherwise, an active/standby switchover of the MM910s will be triggered, which may cause network interruption. You can connect the network cable from the local PC to the STACK port of the active MM910 in the chassis. If the STACK port on the active MM910 is also used, connect the network cable to an idle STACK port on an active MM910 in a chassis cascaded with the E9000 chassis.

  • Check whether the server is compatible. For details, see Compatibility List.
  • Check whether the environment meets the uMate running requirements. For details, see Environmental Requirements.

Data

The following data needs to be prepared before the operation is performed:

  • IP address of the server BMC or HMM management network port. The IP address indicates only the IPv4 address.
  • User name and password of the server BMC or HMM
Procedure
  1. Run the following command to go to the uMate directory.

    cd

    [root@localhost /]# cd home/uMate-Linux-Vxxx/ 
    [root@localhost uMate-Linux-Vxxx]# ls 
    bin  config  help  hwServers.xls  hwServers.xml  image  jre  lib  serviceConf.xml  template  tools  uMate_CLI.sh  uMate.sh

  2. Run the following command to view the help information:

    ./uMate_CLI.sh vmmcfg -h

    [root@localhost uMate-Linux-Vxxx]# ./uMate_CLI.sh vmmcfg -h 
    Usage: vmmcfg [options...] [ports...] <command> 
    options 
        -h, --help         Display this help message 
        -H host-name       Remote iBMC/HMM IP address 
        -U user-name       Remote user name 
        -P password        Remote password 
    mount specific 
        -t  file|dir       Media type to mount [default=file] 
                           file: Local or shared media file, such as .iso or .img 
                           dir : Local or shared directory 
        -s slot-number     E9000 device must input which slot to mount, range: 1-32 
        -l  media-path     File, dir or dev path to mount 
        -lU user-name      Shared file user name 
        -lP password       Shared file password 
    ports 
        -ipmiport port     Remote IPMI port [default=623] 
        -snmpport port     Remote SNMP Agent port [default=161] 
        -sshport  port     Remote SSH/SFTP port [default=22] 
        -vmmport  port     Remote VMM port [default=8208] 
    commands 
        --mount            Mount local file, dir or dev to remote device 
        --unmount          Unmount local file, dir or dev from remote device 
        --status           Query remote device mount status 
        --list             List all devices and its status 
        --startServer      Start device management service 
        --stopServer       Stop device management service, all devices would be unmounted 
     
    For example: 
        Local media mount: 
            vmmcfg -H 192.168.2.98 -U **** -P ********* -l "imagedir/media.iso" --mount 
        Shared media mount: 
            vmmcfg -H 192.168.2.98 -U **** -P ********* -l "//192.168.2.100/imagedir/media.iso" -lU **** -lP ********* --mount 
        Unmount: 
            vmmcfg -H 192.168.2.98 -U **** -P ********* --unmount 
        Status: 
          vmmcfg -H 192.168.2.98 -U **** -P ********* --status 
        List manage devices: 
            vmmcfg --list 
        Start device management service: 
            vmmcfg --startServer 
        Stop device management service: 
            vmmcfg --stopServer

    Table 4-66 describes the parameters.

    Table 4-66 Parameter description

    Remarks

    Description

    Remarks

    -h, --help

    Displays help information.

    -H host-name

    Indicates the IP address of the BMC or HMM management network port of the remote device.

    -U user-name

    Indicates the administrator name.

    -P password

    Indicates the administrator password.

    -t file|dir

    Indicates the mount file or directory.

    • Mount an .iso file to the CD-ROM drive.
    • Mount an .img file to the floppy drive.
    • Mount a directory to the CD-ROM drive.

    -s slot-number

    Indicates the slot number of the MM910.

    NOTE:

    If you mount virtual media to a blade server by using an HMM, you must enter a slot number. This parameter is not required in other scenarios.

    Value range: 1 to 32

    -l media-path

    Indicates the path of the image file or directory to be mounted.

    The read and right permissions are required for accessing .img files.

    -lU user-name

    Indicates the administrator name of the remote server.

    -lP password

    Indicates the administrator password of the remote server.

    -ipmiport port

    Indicates the IPMI port number of the remote server.

    The default value is 623.

    -snmpport port

    Indicates the SNMP port number of the remote server.

    The default value is 161.

    -sshport port

    Indicates the SNMP port number of the remote server.

    The default value is 22.

    -vmmport port

    Indicates the VMM port number of the remote server.

    The default value is 8208.

    --mount

    Mounts virtual media.

    --unmount

    Unmounts virtual media.

    --status

    Displays the virtual media status.

    --list

    Queries and displays the mounting status of the servers and virtual media managed by uMate.

    --startServer

    Starts the server management service.

    --stopServer

    Stops the server management service.

    NOTE:

    After the device management service is stopped, all the virtual media will be demounted.

  3. Mount virtual media.

    • Mount a local .iso file.
      [root@localhost uMate-Linux-Vxxx]# ./uMate_CLI.sh vmmcfg -H 10.10.10.10 -U **** -P ********* -l "/home/uMate/media_dir/tools.iso" --mount 
      Mount media successfully.
    • Mount a local directory.
      [root@localhost uMate-Linux-Vxxx]# ./uMate_CLI.sh vmmcfg -H 10.10.10.10 -U **** -P ********* -l "/home/uMate-Linux-Vxxx/work/" --mount 
      Mount media successfully.
    • Mount a local IMG.
      [root@localhost uMate-Linux-Vxxx]# ./uMate_CLI.sh vmmcfg -H 10.10.10.10 -U **** -P ********* -l "/home/uMate/media_dir/tools.img" --mount 
      Mount media successfully.
    NOTE:

    The mounted IMG file must be smaller than the standard capacity 1.44 MB of the floppy disk drive.

Translation
Download
Updated: 2019-07-10

Document ID: EDOC1000068881

Views: 92708

Downloads: 5415

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