Upgrading to vCenter Server 6.0 best practices (2109772) | VMware KB Snapshot VMs Etc before upgrade Mount vCenter ISO to VMs being upgrade - The Wizard is very intuitive. Order Should b...
See more...
Upgrading to vCenter Server 6.0 best practices (2109772) | VMware KB Snapshot VMs Etc before upgrade Mount vCenter ISO to VMs being upgrade - The Wizard is very intuitive. Order Should be SSO/PSC first vCenter Host Remove Snapshots Best of luck
I can completed in the past - Though I did have an external SQL Server to house the Database. See attached link with show the supported OS for vCenter Supported host operating systems for VMwar...
See more...
I can completed in the past - Though I did have an external SQL Server to house the Database. See attached link with show the supported OS for vCenter Supported host operating systems for VMware vCenter Server installation (including vCenter Update Manager and vRealize O…
Hi Aishr thank you for replying - I'm aware it's not supported it a temporary connection in order to use VC to run some PowerCli over the temporarily connected hosts. I Managed to fix the is...
See more...
Hi Aishr thank you for replying - I'm aware it's not supported it a temporary connection in order to use VC to run some PowerCli over the temporarily connected hosts. I Managed to fix the issue afterward. I had to create a new VMK with the natted IPaddress as the interface IP ie 10.12..X. Xand stability improved. "Failed to bind heartbeat socket for host address 10.12.X.X: Cannot assign requested address" error were eliminated
Hey, I'm having an issue at the moment adding ESXI hosts Via their Natted IP address to vCenter VCSA 6.5. Previously I have successfully used this KB successfully Using NAT between the vCe...
See more...
Hey, I'm having an issue at the moment adding ESXI hosts Via their Natted IP address to vCenter VCSA 6.5. Previously I have successfully used this KB successfully Using NAT between the vCenter Server system and ESXi/ESX hosts (1010652) | VMware KB for all previous version of vCenter. The Server IP address in the vpxa.cfg file is correct and port 902 is open and telnet works I have increased the config.vpxd.heartbeat.notRespondingTimeout via this KB https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1005757 Here is a tail of the vxpa agent log 2017-07-10T19:00:41.341Z verbose vpxa[8ED0B70] [Originator@6876 sub=VpxaHalCnxHostagent opID=WFU-376885b1] Received WaitForUpdatesDone callback 2017-07-10T19:00:41.341Z verbose vpxa[8ED0B70] [Originator@6876 sub=VpxaHalCnxHostagent opID=WFU-376885b1] Applying updates from 479 to 480 (at 479) 2017-07-10T19:00:41.341Z verbose vpxa[8ED0B70] [Originator@6876 sub=VpxaHalCnxHostagent opID=WFU-376885b1] Starting next WaitForUpdates() call to hostd 2017-07-10T19:00:41.341Z verbose vpxa[8ED0B70] [Originator@6876 sub=VpxaHalCnxHostagent opID=WFU-376885b1] Completed WaitForUpdatesDone callback 2017-07-10T19:00:41.422Z verbose vpxa[8F54B70] [Originator@6876 sub=VpxaHalCnxHostagent opID=WFU-2f2143e2] Received WaitForUpdatesDone callback 2017-07-10T19:00:41.422Z verbose vpxa[8F54B70] [Originator@6876 sub=VpxaHalCnxHostagent opID=WFU-2f2143e2] Applying updates from 480 to 481 (at 480) 2017-07-10T19:00:41.422Z verbose vpxa[8F54B70] [Originator@6876 sub=VpxaHalCnxHostagent opID=WFU-2f2143e2] Starting next WaitForUpdates() call to hostd 2017-07-10T19:00:41.422Z verbose vpxa[8F54B70] [Originator@6876 sub=VpxaHalCnxHostagent opID=WFU-2f2143e2] Completed WaitForUpdatesDone callback 2017-07-10T19:00:42.268Z warning vpxa[8E8EB70] [Originator@6876 sub=Heartbeat opID=SWI-1c06dac8] Failed to bind heartbeat socket for host address 10.12.X.X: Cannot assign requested address 2017-07-10T19:00:45.946Z verbose vpxa[8F33B70] [Originator@6876 sub=VpxaHalCnxHostagent opID=WFU-30efc29a] Received WaitForUpdatesDone callback 2017-07-10T19:00:45.947Z verbose vpxa[8F33B70] [Originator@6876 sub=VpxaHalCnxHostagent opID=WFU-30efc29a] Applying updates from 481 to 482 (at 481) 2017-07-10T19:00:45.947Z verbose vpxa[8F33B70] [Originator@6876 sub=halservices opID=WFU-30efc29a] [VpxaHalServices] HostChanged Event Fired, properties changed [runtime.healthSystemRuntime] 2017-07-10T19:00:45.947Z verbose vpxa[8F33B70] [Originator@6876 sub=vpxaInvtHost opID=WFU-30efc29a] [HostChanged] Found update for tracked MoRef vim.HostSystem:ha-host 2017-07-10T19:00:45.947Z verbose vpxa[8F33B70] [Originator@6876 sub=VpxaHalCnxHostagent opID=WFU-30efc29a] Starting next WaitForUpdates() call to hostd 2017-07-10T19:00:45.947Z verbose vpxa[8F33B70] [Originator@6876 sub=VpxaHalCnxHostagent opID=WFU-30efc29a] Completed WaitForUpdatesDone callback 2017-07-10T19:00:46.270Z warning vpxa[8E8EB70] [Originator@6876 sub=Heartbeat opID=SWI-1c06dac8] Failed to bind heartbeat socket for host address 10.12.X.X: Cannot assign requested address 10.12.X.X is the host natted ip address.
One thing to note: With the rollout of ESX6.0 Update 2 (build number 362759) VMware has bundled a new VIB for the VMware VSAN in the update. Previously there was no VSAN VIB included the ES...
See more...
One thing to note: With the rollout of ESX6.0 Update 2 (build number 362759) VMware has bundled a new VIB for the VMware VSAN in the update. Previously there was no VSAN VIB included the ESXi Image and if you trying to upgrade your host using esxcli with this command you will run into some difficulty https://cliffcahill.com/2016/11/11/upgrading-hosts-beyond-esxi-6-0-u2/
#Start Setting Paramters for Scripts param( [Parameter(Mandatory=$true)]$vCenter, $VMhost ="*", $clusterName = '*' ) #End Setting Paramters for Scripts #Connect to vCenter ...
See more...
#Start Setting Paramters for Scripts param( [Parameter(Mandatory=$true)]$vCenter, $VMhost ="*", $clusterName = '*' ) #End Setting Paramters for Scripts #Connect to vCenter Write-Verbose "Connecting to vCenter" $server = Connect-VIServer $vCenter -credential $(get-credential) # Start Creating Scratch Partitions ####################################################################################### $currentLoc = Get-Location $cluster = Get-Cluster $clusterName ForEach ($VMhostname in ($cluster | Get-VMHost -name $VMhost)| sort) { #Get only the first part of the FQDN (only if you used the FQDN to add the ESX server to vCenter) $hostname = $VMhostname.name.split(".")[0].ToUpper() Write-Host -ForegroundColor green "Configuring $hostname" $hostnamefolder = $VMhostname.name.split(".")[0] $folder = ".locker_"+$hostnamefolder #Local datastore $datastore = get-datastore -name 'MGMT-DS-01' -Entity $VMhostname Write-Verbose "Datastore is $($datastore.name)" #Make the local datastore accessible as a PSdrive $null = New-PSDrive -Name $hostname -Root \ -PSProvider VimDatastore -Datastore ($datastore) -Scope global Write-Verbose "Created PSDrive at location $hostname" #Access the new PSDrive Set-Location $hostname":" Write-Verbose "Changed Location to datastore" #Create the syslog folder $null = New-Item $folder -ItemType directory -ErrorAction SilentlyContinue Write-Verbose "Created folder named $folder" #Set the advanced parameter to configure the scratch on the boot lun $value = "/vmfs/volumes/$($datastore.name)/"+$folder Get-AdvancedSetting -Entity $VMhostname -Name "ScratchConfig.ConfiguredScratchLocation" | Set-AdvancedSetting -Value $value -confirm:$false Write-Verbose "Set scratch location on $hostname to $value" #Cleanup Set-Location $currentLoc Remove-PSDrive $hostname Clear-Variable hostname -ErrorAction SilentlyContinue Clear-Variable datastorename -ErrorAction SilentlyContinue Clear-Variable value -ErrorAction SilentlyContinue } Write-Host -ForegroundColor Green "End Creating Scratch Partition".ToUpper() # End Creating Scratch Partitions ################################################################################## Attached is a sample for configuring scratch partitions. - You will need to tweek the directory and cluster name to suit. You will need to reboot once they are set for the log folder to appear in the shared storage. Also both location in the second screengrab should be the same. As in Directory Configured and current directory
High Availability does not consult DRS rules for affinity or anti-affinity when a virtual machine is powering on. A DRS can migrate virtual machines to satisfy affinity rules after the virtual ma...
See more...
High Availability does not consult DRS rules for affinity or anti-affinity when a virtual machine is powering on. A DRS can migrate virtual machines to satisfy affinity rules after the virtual machine is powered on.
