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

OceanStor UltraPath for vSphere 21.3.0 User Guide 03

This document covers the functions, features, installation, configuration, upgrade, uninstallation, maintenance, troubleshooting, and FAQs of OceanStor UltraPath for vSphere (UltraPath forvSphere). UltraPath for vSphere is the multipathing software developed by HuaweiTechnologies Co., Ltd (Huawei for short). The document aims at helping users to be fully familiar with UltraPath for vSphere and its use.
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).
Pre-Installation Check

Pre-Installation Check

This section describes the check before the installation of UltraPath for ESXi.

Procedure

  1. Log in to the ESXi host.
  2. Run /etc/init.d/sfcbd-watchdog status to check whether the CIM Agent has been started.

    ~ # /etc/init.d/sfcbd-watchdog status
    • If sfcbd is not running is displayed, the CIM Agent is not started. In this case, run /etc/init.d/sfcbd-watchdog start to start the CIM Agent. Then view the /var/log/syslog.log file to check whether the CIM Agent has been completely started.

      If the following information is displayed, the CIM Agent has been completely started.

      2013-11-29T23:51:30Z sfcbd-watchdog: starting sfcbd 
      2013-11-29T23:51:30Z sfcbd: Starting sfcbd 
      2013-11-29T23:51:33Z sfcb-sfcb[20560]: --- Log syslog level: 3 
      2013-11-29T23:51:37Z cimslp: --- Using /etc/sfcb/sfcb.cfg
    • If the command output displays sfcbd is running, the CIM Agent has been started.

  3. Run esxcli storage core device list. If the Display Name of each device contains HUAWEI, Huawei storage devices have been mapped to the ESXi hosts.

    • If no Huawei storage devices have been mapped to an ESXi host, install UltraPath for ESXi on the host directly and you do not need to restart the host afterwards.
    • If Huawei storage devices have been mapped to an ESXi host, remove them from the host before installing UltraPath for ESXi. If you do not remove them in advance, restart the host after installing UltraPath for ESXi on it.
    NOTE:

    In SAN boot scenarios, if Huawei storage devices do not need to be removed, install UltraPath for ESXi and restart the host.

    For details about how to safely remove the storage devices, refer to VMware Knowledge Base. After the installation, map the removed storage devices again.

  4. Run esxcli storage core claimrule list to view the claim rule numbers that have been used in the current system.

    ~ # esxcli storage core claimrule list 
    Rule Class Rule  Class    Type       Plugin     Matches                              
    ----------  -----  -------  ---------  ---------  ------------------------------------ 
    MP              0  runtime  transport  NMP        transport=usb                        
    MP              1  runtime  transport  NMP        transport=sata                       
    MP              2  runtime  transport  NMP        transport=ide                        
    MP              3  runtime  transport  NMP        transport=block                      
    MP              4  runtime  transport  NMP        transport=unknown                    
    MP            101  runtime  vendor     MASK_PATH  vendor=DELL model=Universal Xport    
    MP            101  file     vendor     MASK_PATH  vendor=DELL model=Universal Xport    
    MP            200  runtime  vendor     VxDMP      vendor=DGC model=*                   
    MP            200  file     vendor     VxDMP      vendor=DGC model=*                   
    MP            201  runtime  vendor     VxDMP      vendor=EMC model=*                   
    MP            201  file     vendor     VxDMP      vendor=EMC model=*                   
    MP            202  runtime  vendor     VxDMP      vendor=HITACHI model=*               
    MP            202  file     vendor     VxDMP      vendor=HITACHI model=*               
    MP            204  runtime  vendor     VxDMP      vendor=HP model=*                    
    MP            204  file     vendor     VxDMP      vendor=HP model=*                    
    MP            205  runtime  vendor     VxDMP      vendor=COMPAQ model=*                
    MP            205  file     vendor     VxDMP      vendor=COMPAQ model=*                
    MP            206  runtime  vendor     VxDMP      vendor=IBM model=*                   
    MP            206  file     vendor     VxDMP      vendor=IBM model=*                   
    MP            208  runtime  vendor     VxDMP      vendor=NETAPP model=*                
    MP            208  file     vendor     VxDMP      vendor=NETAPP model=*                
    MP            209  runtime  vendor     VxDMP      vendor=XIV model=*                   
    MP            209  file     vendor     VxDMP      vendor=XIV model=*  
    MP            210  runtime  vendor     VxDMP      vendor=HUAWEI model=*                   
    MP            210  file     vendor     VxDMP      vendor=HUAWEI model=*                  
    MP            260  runtime  vendor     PowerPath  vendor=EMC model=SYMMETRIX           
    MP            260  file     vendor     PowerPath  vendor=EMC model=SYMMETRIX           
    MP            270  runtime  vendor     PowerPath  vendor=EMC model=Invista             
    MP            270  file     vendor     PowerPath  vendor=EMC model=Invista             
    MP            300  runtime  vendor     PowerPath  vendor=COMPAQ model=HSV111 (C)COMPAQ 
    MP            300  file     vendor     PowerPath  vendor=COMPAQ model=HSV111 (C)COMPAQ 
    MP            310  runtime  vendor     PowerPath  vendor=EMC model=Celerra             
    MP            310  file     vendor     PowerPath  vendor=EMC model=Celerra             
    MP            400  runtime  vendor     PowerPath  vendor=IBM model=2107900             
    MP            400  file     vendor     PowerPath  vendor=IBM model=2107900             
    MP          65535  runtime  vendor     NMP        vendor=* model=*  
    • If claim rules contain HUAWEI devices, run the following command to delete the claim rule numbers that correspond to the HUAWEI devices before installing UltraPath for ESXi:
      ~ # esxcli storage core claimrule remove --rule 210 
      ~ # esxcli storage core claimrule load              
      ~ # esxcli storage core claimrule run
    • For UltraPath for ESXi, the claim rule number ranges from 400 to 477. Therefore, check whether claim rule numbers that range from 400 to 477 exist in the Rule column. If claim rule numbers that range from 400 to 475 exist in the Rule column, run the following commands to change the claim rule numbers and then install the UltraPath for ESXi. If claim rule number 400 has been used, run the following command to change 400 to another value, for example 320:
    ~ # esxcli storage core claimrule move --claimrule-class=MP --new-rule=320 --rule=400 
    ~ # esxcli storage core claimrule load 
    ~ # esxcli storage core claimrule run  
    ~ # esxcli storage core claimrule list 
    Rule Class Rule  Class    Type       Plugin     Matches                              
    ----------  -----  -------  ---------  ---------  ------------------------------------ 
    MP              0  runtime  transport  NMP        transport=usb                        
    MP              1  runtime  transport  NMP        transport=sata                       
    MP              2  runtime  transport  NMP        transport=ide                        
    MP              3  runtime  transport  NMP        transport=block                      
    MP              4  runtime  transport  NMP        transport=unknown                    
    MP            101  runtime  vendor     MASK_PATH  vendor=DELL model=Universal Xport    
    MP            101  file     vendor     MASK_PATH  vendor=DELL model=Universal Xport    
    MP            200  runtime  vendor     VxDMP      vendor=DGC model=*                   
    MP            200  file     vendor     VxDMP      vendor=DGC model=*                   
    MP            201  runtime  vendor     VxDMP      vendor=EMC model=*                   
    MP            201  file     vendor     VxDMP      vendor=EMC model=*                   
    MP            202  runtime  vendor     VxDMP      vendor=HITACHI model=*               
    MP            202  file     vendor     VxDMP      vendor=HITACHI model=*               
    MP            204  runtime  vendor     VxDMP      vendor=HP model=*                  
    MP            204  file     vendor     VxDMP      vendor=HP model=*                    
    MP            205  runtime  vendor     VxDMP      vendor=COMPAQ model=*                
    MP            205  file     vendor     VxDMP      vendor=COMPAQ model=*                
    MP            206  runtime  vendor     VxDMP      vendor=IBM model=*                   
    MP            206  file     vendor     VxDMP      vendor=IBM model=*                   
    MP            208  runtime  vendor     VxDMP      vendor=NETAPP model=*                
    MP            208  file     vendor     VxDMP      vendor=NETAPP model=*                
    MP            209  runtime  vendor     VxDMP      vendor=XIV model=*                   
    MP            209  file     vendor     VxDMP      vendor=XIV model=*  
    MP            260  runtime  vendor     PowerPath  vendor=EMC model=SYMMETRIX           
    MP            260  file     vendor     PowerPath  vendor=EMC model=SYMMETRIX           
    MP            270  runtime  vendor     PowerPath  vendor=EMC model=Invista             
    MP            270  file     vendor     PowerPath  vendor=EMC model=Invista             
    MP            300  runtime  vendor     PowerPath  vendor=COMPAQ model=HSV111 (C)COMPAQ 
    MP            300  file     vendor     PowerPath  vendor=COMPAQ model=HSV111 (C)COMPAQ 
    MP            310  runtime  vendor     PowerPath  vendor=EMC model=Celerra             
    MP            310  file     vendor     PowerPath  vendor=EMC model=Celerra             
    MP            320  runtime  vendor     PowerPath  vendor=IBM model=2107900             
    MP            320  file     vendor     PowerPath  vendor=IBM model=2107900             
    MP          65535  runtime  vendor     NMP        vendor=* model=*  

  5. Use a digital signature verification tool to verify integrity of the software package.

    NOTE:

    Download the digital signature verification tool from http://support.huawei.com/enterprise/ to verify integrity of the software package. If the verification fails, contact technical support engineers to obtain the correct and secure software package.

  6. Check HBAs of the host. The UltraPath supports Fiber Channel over Ethernet (FCoE) HBAs, Fiber Channel HBAs and iSCSI initiators. A LUN cannot be mapped to a host using HBAs and iSCSI initiators of different firware versions or models or from different vendors.
  7. You have completed the pre-installation check.
Translation
Download
Updated: 2019-06-29

Document ID: EDOC1100052672

Views: 14646

Downloads: 145

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