Ah, now I understand the issue. It would appear that there maybe a bug in the setup.pl script - I'll inform Engineering. The output of the esxcli command indicates that the MEM is installed. You can verify this be creating a volume and viewing the default path policy that was assigned.
If you continue to run into issues, please open a Support ticket, and request that I be CC'd on the case.
The --query command is used to check the MEM status of the host, in your case it is reporting that it is not installed.
To install MEM you would use the --install parameter, and to configure the vSwitch for iSCSI (if you've not already done so) use the --configure parameter.
This is still a problem. Here's the story of my workaround...
When using setup.pl from vMA 6.0 (specifically 6.0.0.1-3755529), you have to add the host's SHA-1 thumbprint into a credential store before running setup.pl, or setup.pl will appear to install the module, but not actually do it. This is in addition to doing a vifp addserver before running setup.pl.
The additional steps (which I wish were in Dell’s documentation) are:
Do something like:
esxcli --server=HOSTNAME systemhostnameget
That’ll give you an error that will show you the host’s SHA-1 thumbprint.
Okay, reading more thoroughly, your problem was a little different, but I'd still bet that trusting the SHA-1 thumbprint of the host is the workaround for you too.
d_glynn
7 Posts
1543
0
Posted August 3rd, 2015 12:00
Ah, now I understand the issue. It would appear that there maybe a bug in the setup.pl script - I'll inform Engineering. The output of the esxcli command indicates that the MEM is installed. You can verify this be creating a volume and viewing the default path policy that was assigned.
If you continue to run into issues, please open a Support ticket, and request that I be CC'd on the case.
Thanks