Here’s a step by step guide that helps you to run through the upgrade steps of PSC 6.5 to 6.7 appliance. STEP1 : Prepare your PSC for the upgrade. Delete all existing snapshots from the PSC VM. Validate that the services are up and running. Ensure that forward and reverse lookup are working for the… Continue reading PSC Appliance 6.5 TO 6.7 STEP BY STEP Upgrade.
VCSA 6.5 TO 6.7 STEP BY STEP UPGRADE
This article explains a Step by Step run through of an appliance upgrade from vCenter 6.5 to vCenter 6.7.
upgrading VCSA to 6.7 – Stage1 fails with Error “Failed to send HTTP data”
Symptoms: VCSA UI installer stage -1 (deploying PSC/VCSA) fails during the OVF deployment. UI installer reports "A problem occured during installation" Installer log reports "Failed to send HTTP data" Error: Installer Log: 2018-11-27T15:29:13.531Z - info: output:ERROR + <Errors> + <Error> + <Type>ovftool.http.send</Type> + <LocalizedMsg> + Failed to send http data + </LocalizedMsg> + </Error> +… Continue reading upgrading VCSA to 6.7 – Stage1 fails with Error “Failed to send HTTP data”
vMotion fails with error ” Unable to prepare migration. Network address is not valid for translation”
Symptoms: Migrating virtual machine fails with error in VPXD log as below, Error: faultMessage = (vmodl.LocalizableMessage) [(vmodl.LocalizableMessage) { key = "msg.migrate.prepare.failed", arg = <unset>, message = "Unable to prepare migration." }, (vmodl.LocalizableMessage) { key = "msg.migrate.addr.convert", arg = (vmodl.KeyAnyValue) [ (vmodl.KeyAnyValue) { key = "1", value = "esxi02.myad.local" } ], message = "Network address 'esxi02.myad.local'… Continue reading vMotion fails with error ” Unable to prepare migration. Network address is not valid for translation”
"NSX Manager appliance boot screen reports unexpected inconsistency- Run FSCK manually /dev/sda*"
You might have already referred to the VMware KB article -https://kb.vmware.com/s/article/2081464. The VMware KB article 2081464 explains to have the FSCK done from the inbuilt GRUB loader in the vSphere appliance. However, NSX manager appliance does not let you to edit the GRUB string , so you cannot force appliance with /bin/bash. Symptoms: vCenter Web… Continue reading "NSX Manager appliance boot screen reports unexpected inconsistency- Run FSCK manually /dev/sda*"
Performing storage vmotion throws "The Operation is not allowed in the current state of the datastore"
Symptoms: Performing storage vMotion of any VM onto datastore shows validation failure with error "Operation not allowed in the current state of the datastore" Creating new VMs ends up with same error. Cause: Integrating VASA plugin for the storage array to vSphere management inculcates some of the alarms for easier storage / vSphere management. This… Continue reading Performing storage vmotion throws "The Operation is not allowed in the current state of the datastore"
ESXi 6.0 storage configuration Shows 0 devices and all active paths
Symptoms: ESXi 6.0 can read/write to the data store actively and no impact to the performance. ESXi host configuration -- > storage shows all data stores as Normal and active. But devices will be 0 and paths will be fine. Running command "esxcli storage core device list" or any other esxcli command returns the message… Continue reading ESXi 6.0 storage configuration Shows 0 devices and all active paths
vCenter 6.0 upgrade: Error occured while creating scheduled task for IIAD
While upgrading vCenter server from 5.5 to 6.0 U3 , you may face error as below, Stderr: ERROR:The network address is invalid. Error occurred while creating scheduled task for IIAD. Symptoms: While upgrading vCenter server from 5.5 to 6.0 Update 3, you may face error as below, An error occurred while invoking external command :… Continue reading vCenter 6.0 upgrade: Error occured while creating scheduled task for IIAD
VMware vMotion fails with Error " Timed out waiting for Migration data"
This article assumes that you have checked the VMware KB articles below for troubleshooting vMotion network. vMotion of a VM fails with the error: "Timed out waiting for migration data" (2143834) Symptoms: VMware vMotion fails between ESXi hosts. vMotion VMK ping is successful between ESXi hosts. Virtual machine is large in Size ( VMs with… Continue reading VMware vMotion fails with Error " Timed out waiting for Migration data"
ESXi 6.0 U2 running on UCS B200 M4 goes unresponsive while all storage paths are dead.
Symptoms: ESXi 6.0 U2 with VIC 1340 is not responding in the vCenter. KVM console of the ESXi host becomes unresponsive. Cannot take vSphere client , but host is pingable. Cannot putty into the ESXi host through SSH. All storage paths are dead and all devices shows inactive. Other hosts in the cluster remains fine. In… Continue reading ESXi 6.0 U2 running on UCS B200 M4 goes unresponsive while all storage paths are dead.
virtuSolve 