HI,
is it possible to identify VMs which hit the IOPS limit?
Kind Regards,
Markus
↧
Detect when a VM hits Disk IOPs Limit
↧
vSphere 6.0U1b can't connect to newly created vVOL ProtocolEndPoint
I downloaded the latest vVNX to test the vVOL, my lab has 3 ESXi6U1b and vCSA 6.0.0.10200. The vVNX is deployed to esxi 6 and one virtual HDD ( carved from 240G SSD drive using Thick provision Eager zero) is used to create a single storage pool, I strictly followed the instructions demonstrated in the following video, I did not create extra Storage Profile beyond these required for setting up vVOL. When vVOL is added to the three hosts, everything seems to be fine, but when I look at the storage size, it is 0 B, but when I looked at the storage devices attached to esx1 host, notice it says "inaccessible". I also chchecked the time, my vCenter, ESXi, vVNX all NTPed to the same server, and their time skew is less than 1 min.
For these small 3 host lab, I did not configure anything thing such as LUN masking or path selection rules. Also the Protocol Endpoint ip address can be seen from the hosts and vcenter, When I ssh to any host and type
" esxcli storage vvol protocolendpoint list " , the result is blank, so it appears that ProtocolEndPoint has some issues, but yesterday, when I had two storage pools, for 30 min, everything worked ( I later destroyed that vVOL due to other mistakes).
Does anyone have clue? I mean the vVOL ver1.0 does seem to have some rough edges.
↧
↧
Re: DataStore 2 VVOL Migration Problem
That makes sense, and not because GB-alignment is needed but because vmdk sizes are supposed to be even 1MB multiples. You cannot create a vmdk in the UI in other than 1MB multiples and VVol sizes are specified in MB. If you have a disk with an odd non-MB multiple size (as a result of a VM conversion, for instance), change the vmdk size to an even MB-multiple before attempting the migration and then the migration should succeed.
Note that it doesn't matter what size the filesystem is in the guest OS - it's the vmdk size (which would appear as the physical device capacity to the guest OS) that matters.
Hope that helps.
↧
Re: verifying q depth of HBA
Thanks for your reply. For some reason I did not receive an email notification when you posted your reply.. but I logged in this morning and saw it.
FYI - I did open a ticket with VMware on this and they said that the command esxcli system module parameters list -m driver from KB1267 would no longer work.
Thanks for the solution, the output for this command is loaded with good info.
↧
Re: verifying q depth of HBA
Also, this command is not found in my 5.0 build, but worked fine in 5.5, do not have a 5.1 build in my environment.
↧
↧
4kn HD support release date?
I spent a long time searching with no information on an ETA for VMware 4kn HDD support. Anybody know the answer. I got 4 brand new 2 TB SAS drives now just being used as paperweights. So the ETA will help me decide if I am to EBay or not to EBay. Thanks in advance everyone.
↧
Re: vSphere 6.0U1b can't connect to newly created vVOL ProtocolEndPoint
Most likely to do with VASA provider and you may find something in there.
↧
Re: vSphere 6.0U1b can't connect to newly created vVOL ProtocolEndPoint
This is EMC vVNX, a virtual storage appliance, I have no idea how to install/uninstall VASA, I thought the VASA 2.0 is embedded into the storage appliance. The link u provided also shows no VASA downloadable from EMC.
↧
Re: vSphere 6.0U1b can't connect to newly created vVOL ProtocolEndPoint
Haven't done VVOL on vVNX but in general you need it to have communication between vCenter and storage.
Check this link:
http://lab.piszki.pl/emc-vvnx-testing-vvol-in-vsphere-6-part-two/
↧
↧
Re: vSphere 6.0U1b can't connect to newly created vVOL ProtocolEndPoint
Thanks, I have already checked this Polish site and other sites, including EMC/VMware video regarding vVNX, really think this might be a bug.
↧
vmware datastore best size
i want to learn that what is the best practives datastore size. for example i have 10 tb storage . 2 x 5 tb datastore or 5 x 2 tb datastore so what is best for my vcenter
↧
Re: vmware datastore best size
There's no rule of thumb for the datastore sizes. It actually depends on your needs (i.e. VM sizes), the number of paths to the storage/LUNs, ...
What I suggest is that - unless VM sizes need to be huge - you consider to create at least as many datastore as you have paths to the storage system.
André
↧
Re: vmware datastore best size
I am also looking for the answer to this question. Although Andre's answer is what I hear most often it doesn't quite help. If you have a LUN with 800GB on it and 2 VMware servers of 300GB each connected to that LUN but you never need to increase the size of them, then you have 200GB that isn't being used. If you have several 800GB LUN in a similar situation it appears that you are wasting a lot of your storage. Or at least, that is how I am looking at it. SO is it better to have several large LUNs, 1TB? I am looking for opinions from the user community. I have only been a user for 2 yrs. and I know that more experienced users could give me a better idea of how to manage my storage.
↧
↧
Re: vSphere 6.0U1b can't connect to newly created vVOL ProtocolEndPoint
Tonight I tried it again, vVOL now shows the right size, which is 150GB, and it has connection to all three hosts, but only esx3 has sustainable connection, esx1, esx2 quickly lose connection after 305 minutes.
I went to /var/log/vvold.log and I found the following, the same thing was not found in the vvold.log on esx3. Looks to me there are some issues with VASA, but I don't know how to resolve this issue, as of right now, HA has been turned off, and there is really no different between esx1, esx2 and esx3.
The esxi6 server (Lenovo H50-55 Desktop, with dual-core AMD A8‑7600 CPU) where I installed vVNX has 16G RAM, and it is partially shared with VRAM, and I managed to create an vVNX VM with 12GB RAM, but the RAM is tight. On the same esxi6 host, I installed another copy of vVNX without VVOL, two iSCSi LUNS were created without any issues. This esxi6 server is NOt managed by the same vCenter managing esx1/2/3, in fact, I am using C# client to manage it.
On esx1 and esx2, when I run command: esxcli storage vvol protocolendpoint list, it is still empty
On esx3, this is what I got:
rfc4122.822ebe79-f151-4374-bbd2-e22fbd93e483
Host Id: e0992541-a79e6176
Array Id: EMC:VIRT1609T88K43
Type: NFS
Accessible: true
Configured: true
Lun Id:
Remote Host: 192.168.1.72
Remote Share: /NAS_PE
Storage Containers: 24790a2e-47b8-4d76-aab7-570bcb008dcf
/var/log/vvold.log content:
2016-03-08T06:09:29.230Z info vvold[FFFAFB70] [Originator@6876 sub=Default] VasaSession::Initialize url is empty
2016-03-08T06:09:29.230Z warning vvold[FFFAFB70] [Originator@6876 sub=Default] VasaSession::DoSetContext: Empty VP URL for VP (VASA)!
2016-03-08T06:09:29.230Z info vvold[FFFAFB70] [Originator@6876 sub=Default] Initialize: Failed to establish connection https://192.168.1.70:8443/vasa/version.xml
2016-03-08T06:09:29.230Z error vvold[FFFAFB70] [Originator@6876 sub=Default] Initialize: Unable to init session to VP VASA state: 0
2016-03-08T06:09:46.117Z info vvold[FFF6EB70] [Originator@6876 sub=Default] VVolUnbindManager::UnbindIdleVVols called
2016-03-08T06:09:46.117Z info vvold[FFF6EB70] [Originator@6876 sub=Default] VVolUnbindManager::UnbindIdleVVols done for 0 VVols
2016-03-08T06:09:59.245Z info vvold[FFD672E0] [Originator@6876 sub=Default] VasaSession::GetEndPoint: with url https://192.168.1.70:8443/vasa/version.xml
2016-03-08T06:09:59.252Z error vvold[FFF6EB70] [Originator@6876 sub=HttpConnectionPool-000000] [ConnectComplete] Connect failed to <cs p:1f07f7a8,
TCP:192.168.1.70:8443>; cnx: (null), error: N7Vmacore3Ssl18SSLVerifyExceptionE(SSL Exception: Verification parameters:
--> PeerThumbprint: 3C:A5:90:95:C0:54:C1:5A:7C:C5:2D:BD:3F:25:C3:63:AE:01:A9:BA
--> ExpectedThumbprint:
--> ExpectedPeerName: 192.168.1.70
--> The remote host certificate has these problems:
-->
--> * self signed certificate in certificate chain)
2016-03-08T06:09:59.252Z warning vvold[FFD672E0] [Originator@6876 sub=Default] VasaSession::GetEndPoint: failed to get endpoint, err=SSL Exception: Verification parameters:
--> PeerThumbprint: 3C:A5:90:95:C0:54:C1:5A:7C:C5:2D:BD:3F:25:C3:63:AE:01:A9:BA
--> ExpectedThumbprint:
--> ExpectedPeerName: 192.168.1.70
--> The remote host certificate has these problems:
-->
--> * self signed certificate in certificate chain, using default
↧
VM Message : There is no more space for virtual disk xxx.vmdk
Hi,
I've the abovementioned issue from last Monday. My both VM not working when the message prompted.
Where should I free the disk space? I've tried "Retry" but nothing happened, I've no choice but to click on "Cancel". Once I clicked on "Cancel", the VM will powered off.
When I power on the VM, the below message prompted
I've to change the memory size to have the VM On.
I've gone through the VM's storage, both VM storage size are sufficient enough.
I've found that the datastore has the exclamation mark. What shall I do to get this solve?
Besides, I suspected that this was due to Backup Exec is running, but I've used the Backup Exec for more than a year so far no issue, only happened recently. Any suggestion on the Backup Exec configuration?
Thank you.
↧
Re: VM Message : There is no more space for virtual disk xxx.vmdk
Based on screenshot, looks like your VM is running from snapshot, what may be the root cause your your space issue... then the first thing you should do is delete the old snapshot, what will free up a lot of storage space. I recommend that your shutdown/power off the virtual machine before start the snapshot removal.
Note that increasing the memory size of your VM will only make your problem bigger, since vSphere will need at least the size of your memory free in datastore to create the .vswp (assuming your are not using memory reservation).
↧
Re: VM Message : There is no more space for virtual disk xxx.vmdk
Hi, yes, I've removed the old snapshot.
I'm reducing the memory size instead of increasing.
I've turn off the backup exec snapshot technology and let's see whether it will help.
Thank you.
↧
↧
Microsoft Cluster over vMSC, RDM usage with 3PAR Peer Persistence
Hello
I'm testing next configuration :
Microsoft SQL CAB Cluster with RDM in physical compatibility mode with 3PAR Peer Persistence and VMware Metro storage cluster. I know that it's not an easy set up, but I could't find any official document either VMware or HP stating that it is not supported setup.
Problem is that RDM is seen with single path from windows guest OS and when you switch over remote copy group to DR storage, cluster disks are lost. I tweaked this registry setting Configuring Microsoft Multipath I/O (MPIO) Timers and after remote copy group swithover disk are remounted automatically but I was not able to achieve not to loose cluster disk.
Is there a way to make this configuration to work ?
↧
(Urgent) Cold migration and storage vMotion timeout at 36% - ESXi 6.0 and vCenter 6.0
(Urgent) Cold migration and storage migration timeout at 36% - ESXi 6.0 and vCenter 6.0
↧
Re: (Urgent) Cold migration and storage vMotion timeout at 36% - ESXi 6.0 and vCenter 6.0
Can you provide more information, such as how much space left for the source and target storage? Did you enable Storage DRS? How is the physical links: any loss of physical uplinks? How about network traffic saturation? Right now it is not clear to me what is going on.
↧