Nimble Connection Manager Download Sources for VMware Update Manager

[cbrasga24]

The following download sources are available for VMware Update Manager, to receive the latest Nimble Connection Manager patches.

ESX Version	Download Source
ESXi 5.x	https://update.nimblestorage.com/esx5/ncm/index.xml
ESXi 6.0	https://update.nimblestorage.com/esx6/ncm/index.xml
ESXi 6.5	https://update.nimblestorage.com/esx6.5/ncm/index.xml

Add the URL(s) as a Download Source in VMware Update Manager's settings and it will check for and download the latest Nimble Connection Manager.

[rn216]

Is there a url to download nimble NCM for esxi 6.7 via update manager?

[ShankarG]

@rn216 You can use 6.5 NCM version for 6.7 too

[Seenivasan-XP]

Hi rn216,

If you using NCM 5.1.0 For ESXi 6.7, use NCM Software for ESXi 6.5.

Let me know if you have any questions on this.

[MRaybone]

Hi,

Could you please explain how this is possible, as when you add the 6.5 update source, the 6.7 update manager won't install NCM as it sees it as being Not Applicable as it is listed as being for esx 6.5, not 6.7.

[Sonic01]

download the NMC from the HPE Infosight portal, upload the nmc zip to a datastore your ESXi 6.7 host can reach, enable ssh, connect to the host and run as follows:

esxcli software vib install -d "/vmfs/volumes/yourdatastorename/nimble-ncm-for-esx6.5-5.1.0-650006.zip"

reboot :)

[jmzetterman84]

While that method does work, HPE really needs to update the NCM plugin so that vSphere recognizes it for 6.7. The point of update manager is to keep packages like this up-to-date. Right now, if HPE puts out an update to NCM and you're not aware of it, you won't get updated until you become aware of it. Not to mention, it's a pain in the butt to have to manually install this one plugin when everything else can be managed via Update Manager. These are the little things that Nimble Storage would never have missed prior to HPE purchasing them.

[mamatadesaiNim]

Looking into this, I'll update this thread soon.  Thanks for reporting.

[mamatadesaiNim]

Good news!  We will have this out shortly, along with the next NimOS release.  Once it is published to the repo, you will see the update in VUM!

[msnyder_vdc]

Any timeframe other than shortly when this is going to actually happen? We are waiting as we have to deploy to a number of severs that we don't want to have to do manually.

[ONE2019]

Hello,

When will this be done?

At time om writing it is still not in the VUM repository.

[mamatadesaiNim]

Very very soon!!  Please stay tuned :-)

[Mark_Wolfe]

Yes, please get this out soon.

ESXi 6.7 will be one year old next week.

[mamatadesaiNim]

Does it work for you today?

[Mark_Wolfe]

No. I see that a new version of NCM was posted on 4/8/19, but it's still explicitly coded for ESXi 6.5.

[mamatadesaiNim]

Mark_Wolfe, we would like to know exactly what error you are seeing and at which step.

I have an ESX 6.7 host with GA build 8169922 and it had an older version of NCM, 5.1.0-650006.  Here are steps I followed:

1. Make sure update manager has the source https://update.nimblestorage.com/esx6.5/ncm/index.xml

2.  Go to update manager home, click on "download now".  Filter by Vendor Nimble Storage.  See the last line on this image, shows ESXi version 6.7.

3. Edit/create an extension baseline for NCM, and select the last line as source.  Attach this baseline to your ESX 6.7 host, check compliance - it will show non-compliant.

After remediation, my ESXi host has NCM version 6.0.0-650005.

Thanks!

PS: If you find this post useful, please consider giving me Kudos!

[SWithrington]

Hi mamatadesaiNim,

Thanks very much for following this up, I too have been waiting for this update to assist with a deployment. 

I've just followed your instructions but I see a slightly updated patch (v5.1.0-650006) but this one only have 6.5 support - could it be that a new version have been released but the compatibility has reverted? If so can I install the old one for now?

(sorry if the above screenshot doesn't appear, I can't get it to preview)

Edit - Sorry I missed the v6.0.0 prefix on your screenshot, so I've still got the old one showing up. I've hit Download Now button but it's not found the new version however? 

Thanks vm,

Stephen

[mamatadesaiNim]

Hi Stephen,

If you've added the URL https://update.nimblestorage.com/esx6.5/ncm/index.xml to Update Manager, click on "Download Now" and filter by Vendor Nimble, you should see what is shown in step 2 above in my post.

We would like to know what you are seeing.  Unfortunately your post does not contain a screenshot, did you attach is using the "photos" icon?

--m

[SWithrington]

Hi mamatadesaiNim,

Thanks for your reply. I have found out what I missed; I was filtering on the download results by the baseline I set up to look for the NCM extension but I needed to edit that baseline to include the new version.

All OK now, thank you!
Stephen

[mamatadesaiNim]

Awesome, we're thrilled to hear that!

[SWithrington]

Thanks very much for sorting this, Kudos to you!

Stephen

[pdv-Support]

Still works beautifully with ESXi 6.7 in late 2020. Thank you!

[mamatadesaiNim]

Very very happy to hear positive feedback!

--m

[EliteX2Owner]

Can this thread sticky be updated to include the link to the NCM 7 repo for vSphere 7.x?

https://update.nimblestorage.com/esx7.0/ncm/

and if the following post is still valid, it should probably be referenced so people do the proper uninstall process:

https://infosight.hpe.com/InfoSight/media/cms/active/public/pubs_VMware_Integration_Guide_NOS_51x.whz/owv1587703953194.html

[EliteX2Owner]

It's really insane HPE can't fix this garbage even seven months after the botched and stupid rename from Nimble Connection Manager to HPE Storage Connection Manager just for the sake of getting the new name in there.

2021-10-17T16:07:20Z esxupdate: 2103673: vmware.esximage.Vib: ERROR: Failed to verify VIB signature #2: ('HPE_bootbank_HPE-Storage-psp_7.0.2-700014', 'Could not find a trusted signer: certificate signature failure')

Million dollar disk arrays and the f'ing drivers can't even be installed without command line and signature ignore.