Dell EqualLogic Multipathing Extension Module v1.4 missing setup.pl

Hello,

Is this package still being built ? 

Because one month later the download still ain't available :

Yeah i'm still waiting for this 1.4 build. I was able to get 1.4 installed in my test environment but come to found out they didn't digitally sign the drivers which is why i believe they ended up taking it down after I called them about it. 

Can Version 1.3 still be downloaded?  Can you provide a link?

In the zip file to deploy to the esxi 6 host, there is 3 different versions inside. 

1.4.0-426823

1.4.0-426823.0

1.4.0-426823.0.0 

Is 1.4.0-426823.0.0 the correct one to install? 

Sorry for the confusion. When you import the zip dell-eql-mem-esx6-1.4.0.426823.zip file into update manager, it imports all 3 versions of that file as extensions available for install. So i'm not sure which one of the three I listed do i need to install through update manager to the host. I'm guessing the last one with 0.0 on the end of it but i wanted to double check before deploying to the host. 

I had the 1.3 MEM installed and I'm now trying to install 1.4. I also see 3 separate extensions being imported instead of 1 like in previous versions. On top of that, the import finally fails with this error:

"Invalid vendor code del in patch metadata, another vendor code with different capitalization already exists in database. Check the Update Manager log files for more details."

Any ideas what could be causing this?

I can confirm the confusion and also the error msg. Together with a borked OMSA 8.4 i was unable to apply any ESXi patches after importet the dell MEM/OMSA packages into VUM and installed on ESXi.

After deinstallation of the 3 MEM vibs (right order is needed!) i was not able to get VUM working again and i wipe the database and importet MEM 1.3. which works like a charm.

Regards,
Joerg

ESXi 6. VSphere on Server 2012R2.

Exact same problem here. 1.3 in repository, "invalid vendor code delin patch metadata" when I try to add 1.4. No option to remove extension. Nothing in "C:\ProgramData\VMware\VMware Update Manager\Logs\2016_12_21.request.log" except for "POST /vum-fileupload/login HTTP/1.1 200" and "POST /vum-fileupload/upload HTTP/1.1 200"

I also have ServerAdministrator 8.3 and 8.4 extensions in the repository.

EDIT.

Imported successfully on second VSphere site, but 3 different patches added.

EDIT.

Was unable to even scan hosts with these in the repository. Had to edit database to remove (unsupported but worked).

I just opened a case in TechDirect and am in conversation with them. I wanted to share with the community some things I've found though. First, the index.xml file in 1.4 is incorrectly constructed, with the vendor code showing up as "del" instead of "DELL" as in versions 1.3 and 1.2 and possible all versions before that. If this is the first MEM you install via Update Manager, it wont cause any problems. But if like me you've been adding to the same Host Extension baseline then, yeah, this is going to be a problem. Also, the reason why in this version there are 3 extensions showing up instead of 1, like *xseitdept* brought up, is because there are 3 different bulletin files inside the metadata zip instead of like in previous versions where there is one bulletin file referencing the 3 VIBs. This isn't necessarily bad, but definitely inconsistent and confusing. I'm including screenshots of both cases and comparing them to the previous version.

MEM 1.3 index.xml

MEM 1.4 index.xml (with incorrect vendor code "del")

MEM 1.3 metadata bulletin file (referencing all 3 files)

MEM 1.4 metadata bulletin file (referencing just one file each)

MEM 1.4 metadata bulletin file

Fixed: http://en.community.dell.com/support-forums/storage/f/3775/t/20000602

I did. E-Support SR # 941050656. Not too helpful though. Been waiting for over a day and getting very slow responses. Been having better luck playing around with the files. As a matter of fact I fixed the 2 problems with the MEM but I asked them if they thought it was the correct course of action but I haven't received a response yet.