Problem Adding VV to VVSet for VMware Server

[JLester]

When the HP engineers did our initial config, they had us setup host sets for each of our VMware clusters and vv sets for the volumes that would be exported to those host sets. Today, I needed to add a new vv to one of the clusters. I created it and added it to the vvset. It did show up appropriately on the hosts, but two hosts in the clusters had their management agents crash. So, they dropped off vCenter. I had to use iLO to restart the management agents on the host. In the logs, I see that some of the FC connection paths went dead right before they crashed.

Did I do something wrong? It was strange that it only affected two of the hosts. All are identical HP bl460c-G8 blades. I remember reading somewhere that were issues when exporting vv sets to host sets, but I am not sure if that is the issue I had or not.

Thanks,
Jason

[hdtvguy]

You should check all your FC zoning. Also are you exporting the vvset to the host, that is going to come back and potentially haunt you later on. exporting vvsets is a nightmare once you start dealing with numerous volumes and if any of those volumes need to be in more than one vvset you can have conflicts with exporting. None of that vvset stuff should have caused your problems though. Do you have your FC zones set up so one initiator goes to no more that 2 3par ports (and those need to be the same controller pair)? What path policy does you have set for the vmware hosts? What version esix? What inform OS version? And what host type are you using to define your hosts to the 3par? And what HBA and firmware version? All those can have be a factor.