NCM reboot / none reboot and Update path

    I wanted to put the information needed for NCM for VMware install / update in one place:

     

     

    Do I need a dedicated NCM version for each ESXi release

    NCM release is is dedicated to each ESXi release, you will find a package for each release (5/6/6.5).

    NCM is compatible with previous Nimble OS, when upgrading a Nimble OS, you should also upgrade your NCM software on the host.

     

    When do you need to reboot ESXi host

     

    * Fresh install of NCM on ESXi 6.0.

    * Fresh install of NCM on ESXi 6.5.

    * Update or uninstall NCM

     

    When do you NOT need to reboot ESXi host

     

    * Fresh install of NCM on ESXi 5.x does not require a reboot.

     

    Using update manager

    When using the VUM only signed VIBs can be used.

     

     

    Note: as of 8th of March, NCM 3.4.0 is signed by VMware and it's possible to install it with VUM.

     

     

    NCM version 3.4.0 is not signed by VMware for ESXi 5.0/6.0/6.5. Until the NCM bundles are signed by VMware, installation can be done through esxcli command only, and not through the VMware Update Manager.

     

    Note:

    When installing the VIB, the  --no-sig-check option must be used.

    Online bundle installation example for ESXi 6.0:

    esxcli software vib install -d https://update.nimblestorage.com/esx6/3.4.0 --no-sig-check

    Online bundle installation example for ESXi 6.5:

    esxcli software vib install -d https://update.nimblestorage.com/esx6.5/3.4.0 --no-sig-check

    Online bundle installation example for ESXi 5.0:

    esxcli software vib install -d https://update.nimblestorage.com/esx5/3.4.0 --no-sig-check

     

    TLS considerations

    Recently Nimble changed the transport layer security (TLS) of the update server (update.nimblestorage.com) to accept TLS v1.2 (see Infosight EXT-0032).

    This change impact the ESXi NCM online install, as some ESXi releases do not support TLS v1.2, the full list of compatibility of the ESXi server can be reviewed here:

     

    https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2145796

     

    Be sure to check the compatibility of the ESXi server with TLS version.

     

    The current settings are as followed:

     

    For VMware ESXi 5.1, 5.0 and earlier end of life products, use the offline bundle.

    For VMware ESXi 5.5+ NOT on a build supporting TLS v1.2, use the offline bundle.

    For VMware 6.x and ESXi 5.5 on a build supporting TLS v1.2, use the online or offline bundle.

     

    Also, note that the URL path changed from "http" to "https".

     

     

     

    Upgrade path

     

    3.4.0:

     

    From

    To

    3.3.0

    3.4.0

    3.2.0

    3.4.0

    3.1.0

    3.4.0

    2.3.x

    3.4.0

    2.2.x

    3.4.0

    2.1.x

    3.4.0

    2.0.x

    3.4.0

     

    3.3.0:

     

    From

    To

    3.2.0

    3.3.0

    3.1.0

    3.3.0

    2.3.x

    3.3.0

    2.2.x

    3.3.0

    2.1.x

    3.3.0

    2.0.x

    3.3.0

     

     

    3.2.0:

     

     

     

    3.1.0

    3.2.0

    2.3.x

    3.2.0

    2.2.x

    3.2.0

    2.1.x

    3.2.0

    2.0.x

    3.2.0

     

     

    3.1.0:

     

     

     

    2.3.x

    3.1.0

    2.2.x

    3.1.0

    2.1.x

    3.1.0

    2.0.x

    3.1.0

     

     

    2.3.1:

     

     

     

    2.2.1

    2.3.1

    2.1.0

    2.3.1

    2.0.7

    2.3.1

    2.0.6

    2.3.1

    2.0.4

    2.3.1