I recently started using SMVI on my NFS-based VMware Infrastructure set up (details of my system configuration are included below). Unfortunetly since starting to use SMVI I've been experiencing issue with VMs powering off unexpectedly. Though I should note it doesn't happen at the same time as the snapshot. The only relevant log entry I can see is in VMware Infrastructure Client (there's nothing in the NetApp syslog to indicate an issue):
Configuration file for vm-name cannot be found
This is followed shortly afterwards by
Virtual Machine vm-name is connected
Reviewing TR-3428*, section 14.3 it discusses a problem related to deleting VMware snapshots and a patch (ESX350-200808401-BG) for the problem. However, it then goes on to note:
"When this patch is in use, there is a condition where virtual machines running 3rd party virtual machine management agents may get powered off unexpectedly. In order to avoid this behavior, please consult the support organization of the management agent regarding virtual disk pooling interval tuning."
I haven't followed the steps in 14.3 to fully enable the patch, but am I right in thinking that even having ESX350-200808401-BG installed could lead to this problem?
Am I also right in thinking that HP CIM constitutes a 3rd party virtual machine management agent in this context? Or is this referring to SMVI itself?
Any clarification or experience on this would be much appreciated.
Summary of set up:
- Active-active 3140 w/ ONTAP 126.96.36.199
- SMVI 1.2
- ESXi 3.5 u4 (176894)
- NFS datastores
- vCenter 2.5 u5
- HP BL490 G6 blades
*NetApp and VMware Virtual Infrastructure 3 StorageBest Practices 4.5.2 (July 2009)