VMware vSphere Virtual Volumes (VVol) with Hitachi - Tips from the trenches

Document created by Paul Morrissey Employee on Apr 27, 2015Last modified by Jill Ross on Jul 1, 2015
Version 2Show Document
  • View in full screen mode

Capturing some tips from early customers who are deploying VMware vSphere Virtual Volumes (VVol) with Hitachi Storage/Infrastructure.

Encourage the community add others via comments and we'll update the documentation as we progress with this feedback loop

For general questions, review the FAQ Blog Series Hitachi and VMware Virtual Volumes - Part 1




SymptomPotential Cause
Symptom: Unable to register the Storage ProviderCause: Sys Admin had been leaving the Storage Provider in “maintenance mode” after adding the Storage Containers which was apparently causing a problem for registering the Storage Provider in vCenter.  When he exited “maintenance mode” the registration within vCenter completed fine.
Symptom: We had an issue where the SP would not communicate to the Admin EVS when attempting to add the HNAS cluster as new managed hardwareCause: firewall issue with port 8443
Symptom: Storage Container showing 0 bytes

Cause: NFS export permissions must include *(rw, insecure,no_root_squash)