Hi Community,
I was wondering whether anyone out there has either experienced issue or at lest can point me in the correct direction?
I'm running the following PowerCLI script against 6.5 VC on a cluster consisting of 12 ESXi 6.0 U2 hosts which I'm in the process of upgrading to 6.5 U2.
i'm experiencing slow start up of hypervisor, at the "vmw_satp_alua loaded successfully" stage, which apparently is down to RDM searches (used for MS Clustering) slowing down the boot process.
My PowerCIi script:
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Import-Module VMware.VimAutomation.Core
Connect-VIServer "VC" -User domain\DomainAdminAC
$RDMList = Get-VM -Location "Cluster" | Get-HardDisk -DiskType "RawPhysical", "RawVirtual" | Select Parent,Name,DiskType,ScsiCanonicalName
$RDMList = $RDMList.scsicanonicalname
Connect-VIServer "ESXIHost" -User root
$esxcli = Get-EsxCli
Foreach ($address in $RDMList)
{
$esxcli.storage.core.device.setconfig($false, $address, $true)
}
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
The above has also been done directly on ESXi host, having obtained list of RDM LUNS:
Example:
Import-Module VMware.VimAutomation.Core
Connect-VIServer "ESXiHost" -Credential (Get-Credential)
$esxcli = Get-EsxCli
$esxcli.storage.core.device.setconfig($false, "(RDM Identifier Number) ", $true)
$esxcli.storage.core.device.setconfig($false, "(RDM Identifier Number) ", $true)
$esxcli.storage.core.device.setconfig($false, "(RDM Identifier Number) ", $true)
$esxcli.storage.core.device.setconfig($false, "(RDM Identifier Number) ", $true)
$esxcli.storage.core.device.setconfig($false, "(RDM Identifier Number) ", $true)
$esxcli.storage.core.device.setconfig($false, "(RDM Identifier Number) ", $true)
$esxcli.storage.core.device.setconfig($false, "(RDM Identifier Number) ", $true)
$esxcli.storage.core.device.setconfig($false, "(RDM Identifier Number) ", $true)
$esxcli.storage.core.device.setconfig($false, "(RDM Identifier Number) ", $true)
$esxcli.storage.core.device.setconfig($false, "(RDM Identifier Number) ", $true)
$esxcli.storage.core.device.setconfig($false, "(RDM Identifier Number) ", $true)
$esxcli.storage.core.device.setconfig($false, "(RDM Identifier Number) ", $true)
Disconnect-VIServer * -Confirm:$false | Out-Null
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
I've SSH'd onto given hosts and run the following against known RDM Luns
Example:
esxcli storage core device list -d (RDM Identifier Number)
The "Is Perennially Reserved: True" statement is as it should be. So scratching my head as to what else to do?
I've observed, having upgraded previous hosts from 6 - 6.5 in same cluster, which took forever too start up, the "Is Perennially Reserved: false" statement has reverted back. I'm wondering whether this is a non persistent issue between reboots?
Any help or advice in the above will be kindly appreciated.