Posts

Showing posts from December, 2017

Validation error on field ‘name’ String value has invalid format

Image
After the upgrade there were many bits and peace which we need to look for after that and there are chances, that some of the might break during after the upgrade.
Same here I faced. I have VCD environment with 8.2 where I have upgraded my vCenter to 6.0 . 
After the upgrade, I was able to connect the VCD without any issue.
Now when I tried to create the vApp, create VM in VCD or making any changes into the Org VDC we were getting below error.



[2f8s242a-2d74-4f00-ad90-45b4d78098ee] validation error on field ‘name’ String value has invalid format
Solution:

After investigation, I found the cause of this issue. In the properties of Org VCD & Provider VDC, in name section there was extra space/ white space was added which is not required. Here while trying to update.



That’s the reason, it’s prompting for the validation error in the field of ‘name’ string where its not able to read the proper name of the source.

Happy Sharing ... :)

VM Creation Date & Time from Powercli

Most of the times we have several requirement when we talk about IT environment like designing , deployment , compliance check or for Security auditing the environment.
Somewhere during security auditing we require to provide several information to security team to get successful audit.
One of them is the compliance of Virtual machine auditing of creation date and time.
Here into this post we will explore how to get the creation date and time of virtual machine hosted into the vCenter or ESXi.
To get the details we will use VMware Powercli to extract the details.
By default there is no function added into Powercli to get such details, so here we will add a function of vm creation date.
Below is the function which needed to be copy and paste into the Powercli.
=======================================================================
function Get-VMCreationTime { $vms = get-vm $vmevts = @() $vmevt = new-object PSObject foreach ($vm in $vms) { #Progress bar: $foundString = "       Found: "+$v…

LUN VMFS partition table corrupted

Last week I got an issue where customer was having issue where one of the shared LUN got disappeared from all the ESXi host.
Well, while troubleshooting I found some error found in vmkernal.log
2017-11-30T06:47:09.272Z cpu78:12160496)WARNING: Partition: 1224: Partition 1 is active, failure to update partition table for naa. 600666666666666666666 2017-11-30T06:47:09.422Z cpu78:12160496)WARNING: Partition: 1224: Partition 1 is active, failure to update partition table for naa. 600666666666666666666
Try to verify if the LUN is attached to ESXi by using below command and found its connected. esxcli storage core path list OR esxcfg-mpath -l
Later, Verified if the LUN status is showing online, degraded or offline by using command esxcli storage core device list -d NAA_ID
At present, I was able to see the LUN status online. However the LUN is still not visible in device section.
From the vmkernal.log error which was mentioned above “WARNING: Partition: 1051: Partition 1 is active, failure to update …