I was troubleshooting storage related problems at a customer site for some time. We run into massive ESXi storage connection problems after installing a new array. Interestingly enough problems occurred on already existing storage a few hours after new array was installed. Because searching for root cause took some time, I thought it is worth to share.
Normally when using a self-signed certificate you get a warning. It is also normal to accept the certificate to continue your task. These days I wanted to register a 3PAR system as storage provider in vCenter. Because of a certification error, this could not be accomplished. In this post I describe how to solve – at least my – problem.
Recently I had to investigate an interesting behavior of ESXi hosts during Storage vMotion between two arrays of the same vendor – in this case HDS (G600 –> G700/F700). In this post I list observed symptoms and a very simple way to boost performance in this situation.
In this blog post you can see how to configure IO limit for VM at VMDK level and how ESXi hosts executes these limits. Furthermore you will see differences between SIOC (Storage IO Control) v1 and v2 and how IO size matters.