Forum Discussion

ttodd's avatar
ttodd
Puritan
10 months ago
Solved

bmorris Drive letters are displayed in the Pure Plugin

bmorris Drive letters are displayed in the Pure Plugin for the vSphere Web Client. Check out this quick tour video. Make sure you have updated VMTools installed and running. Also, the vDrive tab in RVTools shows disk ID and drive letter mapping as well.
  • bmorris's avatar
    bmorris
    10 months ago
    The plugin is partially helpful in identifying the drive letters. I say partially because it seems with Microsoft clustered VMs, the plugin is only showing the vVols added to the first node. The vVols were then added to the other nodes as existing disks. And in this case, the clustered volume is active on one of the other nodes so the plugin is unable to get the drive letter. For vVols active on the primary node, I do indeed see the drive letters. A temporary workaround would be to fail over the role with the volume to the primary node, get the drive letter and vVol names, then fail the role back. I will email you for a copy of the powercli script to see if that has better results.
  • ttodd's avatar
    ttodd
    Puritan
    10 months ago
    bmorris and chris - I adapted and updated a powercli script that creates a CSV of disk info for a particular VM. email me at mailto:ttodd@purestorage.com|ttodd@purestorage.com if you'd like a copy of it.
  • chris's avatar
    chris
    Novice I
    10 months ago
    Ha. Neat. I didn't realize you could get it that way. I think we're still doing something cockamamie with serial numbers? Would have to check.
  • bmorris's avatar
    bmorris
    Novice I
    10 months ago
    The plugin is partially helpful in identifying the drive letters. I say partially because it seems with Microsoft clustered VMs, the plugin is only showing the vVols added to the first node. The vVols were then added to the other nodes as existing disks. And in this case, the clustered volume is active on one of the other nodes so the plugin is unable to get the drive letter. For vVols active on the primary node, I do indeed see the drive letters. A temporary workaround would be to fail over the role with the volume to the primary node, get the drive letter and vVol names, then fail the role back. I will email you for a copy of the powercli script to see if that has better results.