The goal of this KB was to go through several vVol failure scenarios and cover possible results from impacts to either the vVol Data Path or Management Path. A key takeaway would be that impact to the Management Path does not indicate a failure of the Data Path; ie the VMs didn't go down and there isn't an outage in the environment. That being said, while the VMs are up and running when the Management Path is down, any vVol related operations will fail. For example powered off vVol VMs can not be powered on, vVol VMs can not be edited, vMotion'd, or otherwise changed. Powering off a vVol VM when the Management Path is down will result in being unable to power back on that VM as well. The lesson to be learned is not to panic when the Storage Provider is offline or the vVol Datastore is reporting as inaccessible.