Skip to main content
O português é fornecido por meio de tradução automática para sua conveniência. O inglês precede o português em caso de inconsistências.

Verificação multipath para hosts ESXi

Colaboradores

Como parte do processo de importação de LUN estrangeiro (FLI), você deve verificar se o multipath está configurado e funcionando corretamente em seus hosts.

Conclua as etapas a seguir para hosts ESXi.

Passos
  1. Determine o ESXi e a máquina virtual usando o VMware vSphere Client.

    Armazenamentos de dados de storage do vSphere
  2. Determine os LUNs SAN a serem migrados usando o vSphere Client.

    Dispositivos de armazenamento vSphere
  3. Determine os volumes VMFS e RDM (vfat) a serem migrados: esxcli storage filesystem list

    Mount Point                                        Volume Name        UUID                                 Mounted  Type           Size         Free
    -------------------------------------------------  -----------------  -----------------------------------  -------  ------  -----------  -----------
    /vmfs/volumes/538400f6-3486df59-52e5-00262d04d700  BootLun_datastore  538400f6-3486df59-52e5-00262d04d700     true  VMFS-5  13421772800  12486443008
    /vmfs/volumes/53843dea-5449e4f7-88e0-00262d04d700  VM_datastore       53843dea-5449e4f7-88e0-00262d04d700     true  VMFS-5  42681237504   6208618496
    /vmfs/volumes/538400f6-781de9f7-c321-00262d04d700                     538400f6-781de9f7-c321-00262d04d700     true  vfat     4293591040   4269670400
    /vmfs/volumes/c49aad7f-afbab687-b54e-065116d72e55                     c49aad7f-afbab687-b54e-065116d72e55     true  vfat      261853184     77844480
    /vmfs/volumes/270b9371-8fbedc2b-1f3b-47293e2ce0da                     270b9371-8fbedc2b-1f3b-47293e2ce0da     true  vfat      261853184    261844992
    /vmfs/volumes/538400ef-647023fa-edef-00262d04d700                     538400ef-647023fa-edef-00262d04d700     true  vfat      299712512     99147776
    ~ #
    Observação

    No caso de VMFS com extends (VMFS expandido), todos os LUNs que fazem parte do span devem ser migrados. Para mostrar todas as extensões na GUI, vá para Configuração e armazenamento de dados e clique em datastore para selecionar o link Propriedades.

    Observação

    Após a migração, ao adicioná-los de volta ao armazenamento, você verá várias entradas de LUN com o mesmo rótulo VMFS. Neste cenário, deve pedir ao cliente que selecione apenas a entrada marcada como Head.

  4. Determine o LUN e o tamanho a serem migrados: esxcfg-scsidevs -c

    Device UID                            Device Type      Console Device                                            Size      Multipath PluginDisplay Name
    mpx.vmhba36:C0:T0:L0                  CD-ROM           /vmfs/devices/cdrom/mpx.vmhba36:C0:T0:L0                  0MB       NMP     Local Optiarc CD-ROM (mpx.vmhba36:C0:T0:L0)
    naa.60060e801046b96004f2bf4600000014  Direct-Access    /vmfs/devices/disks/naa.60060e801046b96004f2bf4600000014  20480MB   NMP     HITACHI Fibre Channel Disk (naa.60060e801046b96004f2bf4600000014)
    naa.60060e801046b96004f2bf4600000015  Direct-Access    /vmfs/devices/disks/naa.60060e801046b96004f2bf4600000015  40960MB   NMP     HITACHI Fibre Channel Disk (naa.60060e801046b96004f2bf4600000015)
    ~~~~~~ Output truncated ~~~~~~~
    ~ #
  5. Identificar LUNs de mapeamento de dispositivos brutos (RDM) a serem migrados.

  6. Encontrar dispositivos RDM: find /vmfs/volumes -name **-rdm**

    /vmfs/volumes/53843dea-5449e4f7-88e0-00262d04d700/Windows2003/Windows2003_1-rdmp.vmdk
    /vmfs/volumes/53843dea-5449e4f7-88e0-00262d04d700/Windows2003/Windows2003_2-rdm.vmdk
    /vmfs/volumes/53843dea-5449e4f7-88e0-00262d04d700/Linux/Linux_1-rdm.vmdk
    /vmfs/volumes/53843dea-5449e4f7-88e0-00262d04d700/Solaris10/Solaris10_1-rdmp.vmdk
  7. Remova -rdmp e -rdm da saída anterior e execute o comando vmkfstools para encontrar mapeamento vml e tipo RDM.

    # vmkfstools -q /vmfs/volumes/53843dea-5449e4f7-88e0-00262d04d700/Windows2003/Windows2003_1.vmdk
    vmkfstools -q /vmfs/volumes/53843dea-5449e4f7-88e0-00262d04d700/Windows2003/Windows2003_1.vmdk
    Disk /vmfs/volumes/53843dea-5449e4f7-88e0-00262d04d700/Windows2003/Windows2003_1.vmdk is a Passthrough Raw Device Mapping
    Maps to: vml.020002000060060e801046b96004f2bf4600000016444636303046
    ~ # vmkfstools -q /vmfs/volumes/53843dea-5449e4f7-88e0-00262d04d700/Windows2003/Windows2003_2.vmdk
    Disk /vmfs/volumes/53843dea-5449e4f7-88e0-00262d04d700/Windows2003/Windows2003_2.vmdk is a Non-passthrough Raw Device Mapping
    Maps to: vml.020003000060060e801046b96004f2bf4600000017444636303046
    ~ # vmkfstools -q /vmfs/volumes/53843dea-5449e4f7-88e0-00262d04d700/Linux/Linux_1.vmdk
    Disk /vmfs/volumes/53843dea-5449e4f7-88e0-00262d04d700/Linux/Linux_1.vmdk is a Non-passthrough Raw Device Mapping
    Maps to: vml.020005000060060e801046b96004f2bf4600000019444636303046
    ~ # vmkfstools -q /vmfs/volumes/53843dea-5449e4f7-88e0-00262d04d700/Solaris10/Solaris10_1.vmdk
    Disk /vmfs/volumes/53843dea-5449e4f7-88e0-00262d04d700/Solaris10/Solaris10_1.vmdk is a Passthrough Raw Device Mapping
    Maps to: vml.020004000060060e801046b96004f2bf4600000018444636303046
    ~ #
    Observação

    A passagem é RDM com o físico (RDMP), e o nonpassthrough é RDM com o virtual (RDMV). As VMs com RDMs virtuais e cópias Snapshot da VM serão interrompidas após a migração devido ao VM Snapshot delta vmdk apontando para um RDM que tenha um ID naa obsoleto. Portanto, antes da migração, peça ao cliente para remover todas as cópias Snapshot de tais VMs. Clique com o botão direito do rato em VM e clique no botão Snapshot -→ Snapshot Manager Delete All (Eliminar tudo). Consulte o NetApp KB 3013935 para obter detalhes sobre o bloqueio acelerado por hardware para VMware no armazenamento NetApp.

  8. Identificar o mapeamento de dispositivos LUN naa para RDM.

    ~ # esxcfg-scsidevs -u | grep vml.020002000060060e801046b96004f2bf4600000016444636303046
    naa.60060e801046b96004f2bf4600000016                            vml.020002000060060e801046b96004f2bf4600000016444636303046
    ~ # esxcfg-scsidevs -u | grep vml.020003000060060e801046b96004f2bf4600000017444636303046
    naa.60060e801046b96004f2bf4600000017                            vml.020003000060060e801046b96004f2bf4600000017444636303046
    ~ # esxcfg-scsidevs -u | grep vml.020005000060060e801046b96004f2bf4600000019444636303046
    naa.60060e801046b96004f2bf4600000019                            vml.020005000060060e801046b96004f2bf4600000019444636303046
    ~ # esxcfg-scsidevs -u | grep vml.020004000060060e801046b96004f2bf4600000018444636303046
    naa.60060e801046b96004f2bf4600000018                            vml.020004000060060e801046b96004f2bf4600000018444636303046
    ~ #
  9. Determine a configuração da máquina virtual: esxcli storage filesystem list | grep VMFS

    /vmfs/volumes/538400f6-3486df59-52e5-00262d04d700  BootLun_datastore  538400f6-3486df59-52e5-00262d04d700     true  VMFS-5  13421772800  12486443008
    /vmfs/volumes/53843dea-5449e4f7-88e0-00262d04d700  VM_datastore       53843dea-5449e4f7-88e0-00262d04d700     true  VMFS-5  42681237504   6208618496
    ~ #
  10. Registre o UUID do datastore.

  11. Faça uma cópia /etc/vmware/hostd/vmInventory.xml e anote o conteúdo do arquivo e do caminho de configuração vmx.

    ~ # cp /etc/vmware/hostd/vmInventory.xml /etc/vmware/hostd/vmInventory.xml.bef_mig
    ~ # cat /etc/vmware/hostd/vmInventory.xml
    <ConfigRoot>
      <ConfigEntry id="0001">
        <objID>2</objID>
        <vmxCfgPath>/vmfs/volumes/53843dea-5449e4f7-88e0-00262d04d700/Windows2003/Windows2003.vmx</vmxCfgPath>
      </ConfigEntry>
      <ConfigEntry id="0004">
        <objID>5</objID>
        <vmxCfgPath>/vmfs/volumes/53843dea-5449e4f7-88e0-00262d04d700/Linux/Linux.vmx</vmxCfgPath>
      </ConfigEntry>
      <ConfigEntry id="0005">
        <objID>6</objID>
        <vmxCfgPath>/vmfs/volumes/53843dea-5449e4f7-88e0-00262d04d700/Solaris10/Solaris10.vmx</vmxCfgPath>
      </ConfigEntry>
    </ConfigRoot>
  12. Identifique os discos rígidos da máquina virtual.

    Esta informação é necessária após a migração para adicionar os dispositivos RDM removidos em ordem.

    ~ # grep fileName /vmfs/volumes/53843dea-5449e4f7-88e0-00262d04d700/Windows2003/Windows2003.vmx
    scsi0:0.fileName = "Windows2003.vmdk"
    scsi0:1.fileName = "Windows2003_1.vmdk"
    scsi0:2.fileName = "Windows2003_2.vmdk"
    ~ # grep fileName /vmfs/volumes/53843dea-5449e4f7-88e0-00262d04d700/Linux/Linux.vmx
    scsi0:0.fileName = "Linux.vmdk"
    scsi0:1.fileName = "Linux_1.vmdk"
    ~ # grep fileName /vmfs/volumes/53843dea-5449e4f7-88e0-00262d04d700/Solaris10/Solaris10.vmx
    scsi0:0.fileName = "Solaris10.vmdk"
    scsi0:1.fileName = "Solaris10_1.vmdk"
    ~ #
  13. Determine o dispositivo RDM, o mapeamento da máquina virtual e o modo de compatibilidade.

  14. Usando as informações anteriores, observe o mapeamento RDM para o dispositivo, máquina virtual, modo de compatibilidade e ordem.

    Você precisará dessas informações mais tarde, ao adicionar dispositivos RDM à VM.

    Virtual Machine -> Hardware -> NAA -> Compatibility mode
    Windows2003 VM -> scsi0:1.fileName = "Windows2003_1.vmdk" -> naa.60060e801046b96004f2bf4600000016
    -> RDM Physical
    Windows2003 VM -> scsi0:2.fileName = "Windows2003_2.vmdk" -> naa.60060e801046b96004f2bf4600000017
    -> RDM Virtual
    Linux VM -> scsi0:1.fileName = “Linux_1.vmdk” -> naa.60060e801046b96004f2bf4600000019 -> RDM Virtual
    Solaris10 VM -> scsi0:1.fileName = “Solaris10_1.vmdk” -> naa.60060e801046b96004f2bf4600000018 -> RDM Physical
  15. Determine a configuração multipath.

  16. Obtenha configurações de multipath para seu armazenamento no vSphere Client:

    1. Selecione um host ESX ou ESXi no vSphere Client e clique na guia Configuration (Configuração).

    2. Clique em armazenamento.

    3. Selecione um datastore ou LUN mapeado.

    4. Clique em Propriedades.

    5. Na caixa de diálogo Propriedades, selecione a extensão desejada, se necessário.

    6. Clique em dispositivo de extensão > Gerenciar caminhos e obtenha os caminhos na caixa de diálogo Gerenciar caminho.

      Caminhos dos dispositivos de armazenamento vSphere
  17. Obtenha informações de multipathing LUN a partir da linha de comando do host ESXi:

    1. Faça login no console do host ESXi.

    2. Execute a lista de dispositivos nmp de armazenamento esxcli para obter informações de multipath.

      # esxcli storage nmp device list
      naa.60060e801046b96004f2bf4600000014
         Device Display Name: HITACHI Fibre Channel Disk (naa.60060e801046b96004f2bf4600000014)
         Storage Array Type: VMW_SATP_DEFAULT_AA
         Storage Array Type Device Config: SATP VMW_SATP_DEFAULT_AA does not support device configuration.
         Path Selection Policy: VMW_PSP_RR
         Path Selection Policy Device Config: {policy=rr,iops=1000,bytes=10485760,useANO=0; lastPathIndex=3: NumIOsPending=0,numBytesPending=0}
         Path Selection Policy Device Custom Config:
         Working Paths: vmhba2:C0:T1:L0, vmhba2:C0:T0:L0, vmhba1:C0:T1:L0, vmhba1:C0:T0:L0
         Is Local SAS Device: false
         Is Boot USB Device: false
      
      naa.60060e801046b96004f2bf4600000015
         Device Display Name: HITACHI Fibre Channel Disk (naa.60060e801046b96004f2bf4600000015)
         Storage Array Type: VMW_SATP_DEFAULT_AA
         Storage Array Type Device Config: SATP VMW_SATP_DEFAULT_AA does not support device configuration.
         Path Selection Policy: VMW_PSP_RR
         Path Selection Policy Device Config: {policy=rr,iops=1000,bytes=10485760,useANO=0; lastPathIndex=0: NumIOsPending=0,numBytesPending=0}
         Path Selection Policy Device Custom Config:
         Working Paths: vmhba2:C0:T1:L1, vmhba2:C0:T0:L1, vmhba1:C0:T1:L1, vmhba1:C0:T0:L1
         Is Local SAS Device: false
         Is Boot USB Device: false
      
      naa.60060e801046b96004f2bf4600000016
         Device Display Name: HITACHI Fibre Channel Disk (naa.60060e801046b96004f2bf4600000016)
         Storage Array Type: VMW_SATP_DEFAULT_AA
         Storage Array Type Device Config: SATP VMW_SATP_DEFAULT_AA does not support device configuration.
         Path Selection Policy: VMW_PSP_RR
         Path Selection Policy Device Config: {policy=rr,iops=1000,bytes=10485760,useANO=0; lastPathIndex=1: NumIOsPending=0,numBytesPending=0}
         Path Selection Policy Device Custom Config:
         Working Paths: vmhba2:C0:T1:L2, vmhba2:C0:T0:L2, vmhba1:C0:T1:L2, vmhba1:C0:T0:L2
         Is Local SAS Device: false
         Is Boot USB Device: false
      
      naa.60060e801046b96004f2bf4600000017
         Device Display Name: HITACHI Fibre Channel Disk (naa.60060e801046b96004f2bf4600000017)
         Storage Array Type: VMW_SATP_DEFAULT_AA
         Storage Array Type Device Config: SATP VMW_SATP_DEFAULT_AA does not support device configuration.
         Path Selection Policy: VMW_PSP_RR
         Path Selection Policy Device Config: {policy=rr,iops=1000,bytes=10485760,useANO=0; lastPathIndex=1: NumIOsPending=0,numBytesPending=0}
         Path Selection Policy Device Custom Config:
         Working Paths: vmhba2:C0:T1:L3, vmhba2:C0:T0:L3, vmhba1:C0:T1:L3, vmhba1:C0:T0:L3
         Is Local SAS Device: false
         Is Boot USB Device: false
      
      naa.60060e801046b96004f2bf4600000018
         Device Display Name: HITACHI Fibre Channel Disk (naa.60060e801046b96004f2bf4600000018)
         Storage Array Type: VMW_SATP_DEFAULT_AA
         Storage Array Type Device Config: SATP VMW_SATP_DEFAULT_AA does not support device configuration.
         Path Selection Policy: VMW_PSP_RR
         Path Selection Policy Device Config: {policy=rr,iops=1000,bytes=10485760,useANO=0; lastPathIndex=1: NumIOsPending=0,numBytesPending=0}
         Path Selection Policy Device Custom Config:
         Working Paths: vmhba2:C0:T1:L4, vmhba2:C0:T0:L4, vmhba1:C0:T1:L4, vmhba1:C0:T0:L4
         Is Local SAS Device: false
         Is Boot USB Device: false
      
      naa.60060e801046b96004f2bf4600000019
         Device Display Name: HITACHI Fibre Channel Disk (naa.60060e801046b96004f2bf4600000019)
         Storage Array Type: VMW_SATP_DEFAULT_AA
         Storage Array Type Device Config: SATP VMW_SATP_DEFAULT_AA does not support device configuration.
         Path Selection Policy: VMW_PSP_RR
         Path Selection Policy Device Config: {policy=rr,iops=1000,bytes=10485760,useANO=0; lastPathIndex=1: NumIOsPending=0,numBytesPending=0}
         Path Selection Policy Device Custom Config:
         Working Paths: vmhba2:C0:T1:L5, vmhba2:C0:T0:L5, vmhba1:C0:T1:L5, vmhba1:C0:T0:L5
         Is Local SAS Device: false
         Is Boot USB Device: false