Mellanox on vSphere - Error Extracting File

Brand new card, new in server. It likely has firmware back rev issue… but server is vSphere 6.7 so working through process to get it up and working for iSER

When I follow documentation to deploy driver (which it basically is working as the driver goes live) I am trying to install per the installation guide but getting this error:

############

[root@x395001:/tmp] esxcli software acceptance set --level=PartnerSupported

Host acceptance level changed to ‘PartnerSupported’.

[root@x395001:/tmp] esxcli software sources profile list -d /tmp/MLNX-NATIVE-ESX-ConnectX-4-5_4.17.13.8-10EM-670.0.0-8873266.zip

[MetadataDownloadError]

Could not download from depot at zip:/tmp/MLNX-NATIVE-ESX-ConnectX-4-5_4.17.13.8-10EM-670.0.0-8873266.zip?index.xml, skipping ((‘zip:/tmp/MLNX-NATIVE-ESX-ConnectX-4-5_4.17.13.8-10EM-670.0.0-8873266.zip?index.xml’, ‘’, ‘Error extracting index.xml from /tmp/MLNX-NATIVE-ESX-ConnectX-4-5_4.17.13.8-10EM-670.0.0-8873266.zip: “There is no item named ‘index.xml’ in the archive”’))

url = zip:/tmp/MLNX-NATIVE-ESX-ConnectX-4-5_4.17.13.8-10EM-670.0.0-8873266.zip?index.xml

Please refer to the log file for more details.

[root@x395001:/tmp] lspci | grep Mellanox

0000:18:00.0 Network controller: Mellanox Technologies MT27800 Family [ConnectX-5] [vmnic8]

0000:18:00.1 Network controller: Mellanox Technologies MT27800 Family [ConnectX-5] [vmnic9]

[root@x395001:/tmp] esxcli software vib list | grep nmlx

nmlx4-core 3.16.11.6-1OEM.650.0.0.4598673 MEL VMwareCertified 2018-07-31

nmlx4-en 3.16.11.6-1OEM.650.0.0.4598673 MEL VMwareCertified 2018-07-31

nmlx4-rdma 3.16.11.6-1OEM.650.0.0.4598673 MEL VMwareCertified 2018-07-31

nmlx5-core 4.16.12.12-1OEM.650.0.0.4598673 MEL VMwareCertified 2018-07-31

nmlx5-rdma 4.16.12.12-1OEM.650.0.0.4598673 MEL VMwareCertified 2018-07-31

[root@x395001:/tmp]

[root@x395001:/tmp] esxcli software sources profile list -d /tmp/MLNX-NATIVE-ESX-ConnectX-4-5_4.17.13.8-10EM-670.0.0-8873266.zip

[MetadataDownloadError]

Could not download from depot at zip:/tmp/MLNX-NATIVE-ESX-ConnectX-4-5_4.17.13.8-10EM-670.0.0-8873266.zip?index.xml, skipping ((‘zip:/tmp/MLNX-NATIVE-ESX-ConnectX-4-5_4.17.13.8-10EM-670.0.0-8873266.zip?index.xml’, ‘’, ‘Error extracting index.xml from /tmp/MLNX-NATIVE-ESX-ConnectX-4-5_4.17.13.8-10EM-670.0.0-8873266.zip: “There is no item named ‘index.xml’ in the archive”’))

url = zip:/tmp/MLNX-NATIVE-ESX-ConnectX-4-5_4.17.13.8-10EM-670.0.0-8873266.zip?index.xml

Please refer to the log file for more details.

[root@x395001:/tmp]

########

I downloaded it twice to validate it was not download issue. I tried two separate servers and same issue.

I think I see issue here… it is a zip within a zip.

[root@x385004:/tmp] unzip MLNX-NATIVE-ESX-ConnectX-4-5_4.17.13.8-10EM-670.0.0-8873266.zip

Archive: MLNX-NATIVE-ESX-ConnectX-4-5_4.17.13.8-10EM-670.0.0-8873266.zip

inflating: MLNX-NATIVE-ESX-ConnectX-4-5_4.17.13.8-10EM-670.0.0-offline_bundle-8873266.zip

inflating: doc/README.txt

inflating: doc/open_source_licenses_nmlx5-core_4.17.13.8-1OEM.670.0.0.8169922.txt

inflating: doc/release_note_nmlx5-core_4.17.13.8-1OEM.670.0.0.8169922.pdf

inflating: doc/open_source_licenses_nmlx5-rdma_4.17.13.8-1OEM.670.0.0.8169922.txt

inflating: doc/release_note_nmlx5-rdma_4.17.13.8-1OEM.670.0.0.8169922.pdf

inflating: source/driver_source_nmlx5-core_4.17.13.8-1OEM.670.0.0.8169922.tgz

inflating: source/driver_source_nmlx5-rdma_4.17.13.8-1OEM.670.0.0.8169922.tgz

[root@x385004:/tmp] esxcli software vib install -d /tmp/MLNX-NATIVE-ESX-ConnectX-4-5_4.17.13.8-10EM-670.0.0-offline_bundle-8873266.zip

Installation Result

Message: The update completed successfully, but the system needs to be rebooted for the changes to be effective.

Reboot Required: true

VIBs Installed: MEL_bootbank_nmlx5-core_4.17.13.8-1OEM.670.0.0.8169922, MEL_bootbank_nmlx5-rdma_4.17.13.8-1OEM.670.0.0.8169922

VIBs Removed: MEL_bootbank_nmlx5-core_4.16.12.12-1OEM.650.0.0.4598673, MEL_bootbank_nmlx5-rdma_4.16.12.12-1OEM.650.0.0.4598673

VIBs Skipped:

[root@x385004:/tmp]

Be nice if it was noted as such anywhere in readme. Or name the zip such that it needs unzip before scp to vsphere host.