You need to insert the Web server dark site ip/dns adres in settings.

Hello @Dominik.Siedlak 

For ESXi to need to do it from Prism, and keep in mind that DRS must be enabled, otherwise you need to upgrade ESXi manually. For more details: https://portal.nutanix.com/page/documents/details?targetId=vSphere-Admin6-AOS:vsp-node-upgrade-manual-vsphere-c.html

For AOS and FS you can upload them to the LCM dark site web server, you need to check the compatibility.

Hi,
Yes, this part is done. As you can see LCM dark site offline bundle & HPE firmware is detected correctly.  My question is: is it possible to update AOS/ESXi via Dark Site inventory? If yes, what is the correct location (Dark Site server) for uploading files like:
* 7.0.0-u3f-20036589-hp-dx.json (METADATA) and ESXi update (VMware-ESXi-7.0.3-20036589-HPE-703.0.0.10.10.0.12-Oct2022.zip)
* Prism metadata (generated-nutanix_installer_package-release-fraser-6.5.1.6-stable-7c84485a320ec3a2552e8894822c9b6933ad8c91-x86_64-metadata.json) and install package (nutanix_installer_package-release-fraser-6.5.1.6-stable-7c84485a320ec3a2552e8894822c9b6933ad8c91-x86_64.tar.gz)

Question is: is LCM with Dark Site server repository (no access to the internet) can be used for upgrading AOS & hypervisor or just only LCM itself and firmware bundle?
Dominik

Hi Moustafa, great info. So, if you can guide me please: what is the correct location for the following files:
Prism metadata (generated-nutanix_installer_package-release-fraser-6.5.1.6-stable-7c84485a320ec3a2552e8894822c9b6933ad8c91-x86_64-metadata.json) and install package (nutanix_installer_package-release-fraser-6.5.1.6-stable-7c84485a320ec3a2552e8894822c9b6933ad8c91-x86_64.tar.gz) ?

Here is my http server structure:

Dominik

Hello @Dominik.Siedlak 

Upload to “release” directory. For LCM dark site setup please check below:

https://portal.nutanix.com/page/documents/details?targetId=Life-Cycle-Manager-Dark-Site-Guide-v2_3:Setting%20Up%20a%20Local%20Web%20Server

Thanks Moustafa, but no luck…

I’ve done inventory, but still no joy:

Is any special file name for .json and AOS upgrade package that can be ‘detected’ with LCM via DarkSite?
Dominik

Hello @Dominik.Siedlak 

Share with us Prism LCM configuration, and hardware model and generation, ESXi version , AOS Verison.

Thanks Moustafa,

Prism Central: pc.2021.9.4
NCC Version:   4.3.0
LCM:               updated from 2.4.4.2 to 2.5.0.2 via LCM Dark Site bundle

AOS: 5.20.2 LTS with NCC 4.2.0.1 and LCM 2.5.0.2 (LCM updated via Dark Site server)

Hypervisor: 7.0.2-17867351
Hardware: Proliant DX360 Gen10 4LFF

Plan is to:
1/ upgrade Prism Central to pc.2022.6.0.1  (NCC, upgrade and againg NCC),
2/ upgrade PE (NCC, upgrade PE and again NCC),
3/ upgrade foundation (is it required?)
4/ perform LCM inventory and upgrade AOS (if is possible via LCM Dark Site)
5/ update HPE firmware via LCM Dark site. After uploading HPE bundle to repository it is available for LCM:

6/ upgrade ESXi to 7.0.3 (customized bundle): if is possible via LCM or if not, via Lifecycle Manager:
https://customerconnect.vmware.com/en/downloads/details?downloadGroup=OEM-ESXI70U3-HPE&productId=974
 

Dominik

Hello @Dominik.Siedlak 

You can upgrade to Prism 2022.6.0.1 with AOS 6.5.1.6 with the below ESXi versions:

Yes, please upgrade Foundation, for Recommended upgrade order please follow the below guide:

https://portal.nutanix.com/page/documents/details?targetId=Acropolis-Upgrade-Guide-v6_5:upg-lcm-upgrade-some-c.html

Dear Moustafa,

Thanks, but it is still not answering how to upload ESXi and AOS bundle to the Dark Site server.

https://portal.nutanix.com/page/downloads?product=hypervisordetails

Dominik

Hello @Dominik.Siedlak 

For ESXi use Prism Hypervisor upgrade not LCM.

1. Before performing any upgrade procedure, make sure you are running the latest version of the Nutanix Cluster Check (NCC) health checks and upgrade NCC if necessary.
2. Run NCC as described in Run NCC Checks.
3. Log on to the Nutanix support portal and navigate to the Hypervisors Support page from the Downloads menu, then download the Nutanix-qualified ESXi metadata .JSON files to your local machine or media.
   1. The default view is All. From the drop-down menu, select Nutanix - VMware ESXi, which shows all available JSON versions.
   2. From the release drop-down menu, select the available ESXi version. For example, 7.0.0 u2a.
   3. Click Download to download the Nutanix-qualified ESXi metadata .JSON file.
4. Log on to the Prism Element web console for any node in the cluster.
5. Click the gear icon in the main menu, select Upgrade Software in the Settings page, and then click the Hypervisor tab.
6. Click the upload the Hypervisor binary link.

7. Click Choose File for the metadata JSON (obtained from Nutanix) and binary files (obtained from VMware), respectively, browse to the file locations, select the file, and click Upload Now.

8. When the file upload is completed, click Upgrade > Upgrade Now, then click Yes to confirm.

   lOptional] To run the pre-upgrade installation checks only on the Controller VM where you are logged on without upgrading, click Upgrade > Pre-upgrade. These checks also run as part of the upgrade procedure.

9. Type your vCenter IP address and credentials, then click Upgrade.Ensure that you are using your Active Directory or LDAP credentials in the form of domain\username or username@domain.

   Note: AOS can detect if you have uploaded software that is already installed or upgraded. In this case, the Upgrade option is not displayed, because the software is already installed.

   The Upgrade Software dialog box shows the progress of your selection, including status of pre-installation checks and uploads, through the Progress Monitor.

Currently the following components have bundles that support direct upload.

For all other components, use a local web server.

• Components that have bundles that support either direct upload or a web server use the filename format lcm_component_version.tar.gz.

  The exception is the LCM framework bundle itself, which uses the filename lcm_dark_site_bundle_version.tar.gz.

• Components that have bundles that support only a web server do not have a consistent filename format. Currently the following components are available for a web server but not for direct upload.

Update AOS at a site without Internet access.

Thanks Moustafa for your help. I will try and report here in any case of success or failure ;-)
Dominik