Hi Paul, I understand this RAID 6 only has/had the vmfs datastore. This is not a local drive which is also used for ESXi Install having multiple partitions. If a local drive is used for ES...
See more...
Hi Paul, I understand this RAID 6 only has/had the vmfs datastore. This is not a local drive which is also used for ESXi Install having multiple partitions. If a local drive is used for ESXi Install, the installation usually creates a vmfs partition on the remaining space of the LUN. Also provide the latest vmkernel log after running the below command vmkfstools -V (to refresh the vmkfs mounts) voma -m vmfs -d /vmfs/devices/disks/mpx.vmhba1:C0:T1:L0:1 -s /tmp/analysis.txt Check the linked KB for help VMware KB: Using vSphere On-disk Metadata Analyzer (VOMA) to check VMFS metadata consistency Regards, Mudasser
Hi Joe, Please provide the output of below commands and also share the latest vmkernel log file. vmkping <targetIP> nc -z <targetIP> 3260 vmkiscsi-tool -E -l <software iSCSI adapt...
See more...
Hi Joe, Please provide the output of below commands and also share the latest vmkernel log file. vmkping <targetIP> nc -z <targetIP> 3260 vmkiscsi-tool -E -l <software iSCSI adapter> Regards, Mudasser
Hi, I have DVS 5.5 in my production environment with 2 Active nics on Each host. This is a HP blade enclosure and connects to Nexus 5K upstream switches. As per the Network admin, the ports ...
See more...
Hi, I have DVS 5.5 in my production environment with 2 Active nics on Each host. This is a HP blade enclosure and connects to Nexus 5K upstream switches. As per the Network admin, the ports are configured for vPC(virtual port channel) I need to know the differences between creating a LAG and just using the nics in active/active configuration
If you want to get the LUN from the storage end moved, you will have to unmap it from the hosts in current datacenter and present it to ESX hosts in new datacenter. Otherwise storage vMotion t...
See more...
If you want to get the LUN from the storage end moved, you will have to unmap it from the hosts in current datacenter and present it to ESX hosts in new datacenter. Otherwise storage vMotion the VMs to a newly mapped LUN and delete the old one once all the machines are moved
Hi, What is the tool and how do you intend to use it. as there will multiple partitions on the local RAID drive along with vmfs, I am not expecting this to be cake walk. If you can, please...
See more...
Hi, What is the tool and how do you intend to use it. as there will multiple partitions on the local RAID drive along with vmfs, I am not expecting this to be cake walk. If you can, please share some details
Hello Brian, Make sure the hostd services on source and destination hosts are fine, run the below command and make sure you are getting an output. If both ESXi hosts are connected to the sa...
See more...
Hello Brian, Make sure the hostd services on source and destination hosts are fine, run the below command and make sure you are getting an output. If both ESXi hosts are connected to the same upstream switch, try creating a separate 192.168.x.x class C network to get a different broadcast domain. this will take out any issues with physical network. test a vmkping across the hosts on newly created vmkernel ports for vMotion. and try vMotion. you have to disable vMotion on all other ports and have it enabled only on same subnet ports on source and destination. I have seen this happen in cases where Admins enabled vMotion on dissimilar ports on source and destination.
Hi Paul, As MkGuy said, share the partition layout of the identified naa.ID. The fact that it recognizes there is a vmfs label, it is possible that the partition table is an issue.
Hi Ngas, Login with administrator@vsphere.local and verify your identity sources. Make sure you have a valid domain mentioned as the Identity source and remove the local OS users if any. C...
See more...
Hi Ngas, Login with administrator@vsphere.local and verify your identity sources. Make sure you have a valid domain mentioned as the Identity source and remove the local OS users if any. Check the below KB. http://kb.vmware.com/kb/2043070
