If the only VMDK is the one you are using, then you should be good to go. Also, make sure your free space looks right.
↧
Re: File Server Datastore Provisioning assistance
↧
Re: File Server Datastore Provisioning assistance
Here is what it looks like. Do you see any potential issues?
↧
↧
Re: Extend existing datastores vs Creating new datastores
Doing an in-place VMFS3 to VMFS5 upgrade is indeed not recommended, because the resulting datastores do not utilize all VMFS5 enhancements. Datastores need to be recreated.
Recommendation to not *extend* datastores most likely comes from the VMFS3 days. Where to increase a datastore you had to add an extent, which was a bit clunky.
It's changed with VMFS5, as it's now a single extent file system. That said, I personally see no concerns around extending VMFS5 datastores.
↧
Re: File Server Datastore Provisioning assistance
That's ok.
As a side note: The reason why the .vmdk files are named VIPFS_1.vmdk and VIPFS_2.vmdk rather then VIPFS.vmdk and VIPFS_1.vmdk is that you didn't close the VM's settings after removing the VM's virtual disk, and adding the new ones. However, this is just a cosmetic issue, and doesn't cause any technical issues.
André
↧
Re: Extend existing datastores vs Creating new datastores
Gotcha, I was not aware that it did not take advantage of all of the enhancements when upgrading. I was aware of the supposed issues with extents within VMFS3. Thanks for your input!
↧
↧
Re: Detect when a VM hits Disk IOPs Limit
No suggestions?
At the Moment outstanding IOs (OIO) are possible for me. But I'm not sure how reliable this is and what a high watermark is…
↧
Re: Detect when a VM hits Disk IOPs Limit
You may be able to create a custom alert using PowerCLI if you can identify the EventTypeID that you're wanting to monitor.
VMware Front Experience: Creating vCenter alarms with PowerCLI
↧
Re: vSphere 6.0U1b can't connect to newly created vVOL ProtocolEndPoint
I have the exact same issue:
VVOLd.log:
error vvold[FFA762E0] [Originator@6876 sub=HttpConnectionPool-000000] [ConnectComplete] Connect failed to <cs p:1f0a33e0, TCP:sgstorage:31443>; cnx: (null), error: N7Vmacore3Ssl18SSLVerifyExceptionE(SSL Exception: Verification parameters:
--> PeerThumbprint: F1:C9:68:55:11:D5:8F:0F:38:D0:D7:8B:D0:29:7B:B2:2B:5D:08:BD
--> ExpectedThumbprint:
--> ExpectedPeerName: sgstorage
--> The remote host certificate has these problems:
-->
--> * self signed certificate in certificate chain)
↧
Re: vSphere 6.0U1b can't connect to newly created vVOL ProtocolEndPoint
I have found a resolution:
Simple remove the esxi host from the inventory and readd it.
After that, the provider on the esxi host are ONLINE and the endpoints are created and working
↧
↧
Storage Issue ( and vCenter Gone )
Hi Experts,
I have 2 hosts and connected to the shared iscsi storage. There were some issues in storage connection and as the result those esxi can't connect to the storage, the problem is vCenter VM is sitting inside the iscsi storage so vCenter access has been lost . I have rebooted the esxi hosts and add the required storage adapter and device can be detected as shown below :
But in datastores tab, show nothing. I have tried to list using "esxcfg-volume -l", also show nothing so i can't do force mount since no label/UUID listed.
I executed this command "esxcli storage core device list"
Mount this device using "Add Storage" wizard is possible but it will destroy all the data (option "keep existing signature" didn't appear), the datastore contains several VMs including the vCenter.
How can i mount this storage device without re-formating it?
Thanks alot
BR,
Davy
↧
Re: Storage Issue ( and vCenter Gone )
I've seen such issues with newly added datastores (which actually doesn't seem to be the case here) which have the same/duplicate label as existing datstores. It might at least be worth a try to temporarily rename your existing datastore(s), and then run a rescan, just to rule out such an issue. You may also want to take a look at the vmkernel log to see whether there are errors reported during the rescan operation.
If this doesn't help, run esxcli storage filesystem list to see whether this shows the missing datastore?
André
↧
Re: Storage Issue ( and vCenter Gone )
Hi Andre,
"esxcli storage filesystem list" also shows nothing related with this shared storage device. In both host, only local datastore left and the name is different with the shared datastore..
Thanks alot
↧
Re: iSCSI storage presented to hosts managed by different vCenter Server - any issues?
Was able to decommission the previous vcenter server. The hosts with esxi 5.0 was disconnected and removed from the cluster of the old vcenter server and moved to the new cluster in the new vcenter server without any issue.
Interesting to note is the EVC was disabled in both the clusters in the new vcenter server BUT I was able to move most of my VMs on the fly to the new cluster (new hosts) from the cluster that contained the old hosts. No shutdown was needed. There were a few VMs that reported hardware incompatibility.
The hosts in the old cluster has intel xeon CPU x5670 @2.93 GHz and the hosts in the new cluster has intel xeon E5-2680 v3 @2.50 GHz. So, I am assuming the VMs that were migrated were using just the baseline CPU instruction set that is common to both the clusters?
↧
↧
Re: iSCSI storage presented to hosts managed by different vCenter Server - any issues?
X5670 is Westmere and E5-2680 is Sandy Bridge. Not sure how you managed to vMotion between the two. But glad to hear it worked out well for you.
↧
3PAR VAAI Integration with failsafe copy groups
Hi all,
Does anyone have any experience using 3PAR storage in a stretched peer persistent config?
Failing that does anyone know of any tech docs that describes how the 3PAR VAAI integration works under the hood??
I'm investigating a fairly significant issue with VAAI operations when a Virtual Volume in a copy group is in failsafe state.
Any help or direction appreciated!
Cheers
↧
Re: Detect when a VM hits Disk IOPs Limit
The problem is, I cannot identify any event or log entry when this happens...
↧
Re: iSCSI storage presented to hosts managed by different vCenter Server - any issues?
Managed to vmotion 48 virtual machines without shutting them down. A couple of windows 2003 VMs shouted about hardware incompatibilities. EVC is disabled in both the clusters. Not sure why validation succeeded.
↧
↧
Re: Storage Issue ( and vCenter Gone )
I have seen this problem a few times recently:
- to fix it try to boot one host into an ESXi-boot-stick that never has seen storage before (either use a ESXi LiveCD or a newly installed stick)
- if that does not help extraction of the data should be possible with some workarounds - call me if necessary.
Ulli
↧
vCenter 6 VVOLs + 3par TDVV = dying vms, can't find OS?
I have a vCenter 6 environment running VVOLs on a 3par 7450 with thin dedupe (TDVV) on. I have been having some space reclaim issues and performance probs for the last few weeks, but overall everything appears fine.
I am now having vm's randomly die. They appear to lose access to the disk and cannot find OS upon reboot. Some vm's appear alive still in memory, but eventually die off. The VM's also appear corrupt and unrecoverable or usable.
I have tried migrating to another array (after the fact) and no luck, but I was able to convert one VMDK file from TDVV to TPVV and it saw the boot device but then windows said it was corrupt.
It appears all VM's on the VVOLs that are TPVV are fine, after reboots, can write to disk, etc.. It is JUST the TDVV VMs.
vCenter 6, storage container, PEs, VASA, etc all appear happy and fine. Any ideas?
↧
VNX5400 change management IPs
Hello there. I have asked this question on community.emc.com first, but my thread stucks for a whole day with a warning that moderator needs to check my discussion prior the thread will be published. So I decide to ask here, im sure there are people here who can help me.
I got VNX 5400 with flare 05.33.008.5.119. There are few hosts (ESXi) registered on this storage and these hosts are attached to few LUNs by FC.
Now I want to change SPA/SPB management IPs (new IPs would be at the same network as the old IPs). Is it possible to face some problems after this procedure?
↧