- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-11-2018 05:23 AM - edited 03-01-2019 01:37 PM
I want to make sure I have this right before I begin.
Our hosts are HXAF240C-M5SX's running HX 2.6.1d-26761 and ESXi 6.0.0
Our FIs are 6332's running firmware 3.2(3a) and the hosts are running 3.2(3a)
I have this downloaded to do the upgrade.
CISCO HX Custom Image for ESXi 6.5 U1 Patch 2 Offline Bundle
Is the "Upgrading ESXi" section of this documentation valid for my scenario?
Solved! Go to Solution.
- Labels:
-
Other Unified Computing System
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-11-2018 05:39 AM
That is the general procedure to upgrade an ESXi host. Since you mentioned these are HX nodes, I would follow the procedure documented specifically for those servers.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-11-2018 05:35 AM
Yes this procedure would work for your cluster.
I would also look towards getting off 3.2.3a as it is deferred code.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-11-2018 05:37 AM
Thanks Wes,
I also came across this procedure. Will this also work?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-11-2018 05:39 AM
That is the general procedure to upgrade an ESXi host. Since you mentioned these are HX nodes, I would follow the procedure documented specifically for those servers.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-11-2018 06:41 AM
Ensure that the cluster becomes healthy between each ESXi upgrade.
stcli cluster storage-summary --detail
I get stcli: not found
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-11-2018 06:47 AM
The stcli commands should be run from a Storage Controller Virtual machine running on an ESXi host. They should not be run from an ESXi host cli.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-11-2018 07:56 AM
Thanks that worked.
Maybe related or unrelated but now I am not able to access the Cisco HyperFlex Connect.
NetworkError when attempting to fetch resource. (TypeError: NetworkError when attempting to fetch resource.)
This happened once before, it seemed to fix itself after a day or so?
Related to that the Springpath VM on the host I updated is using 72GB of memory.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-11-2018 09:31 AM
I don't know if I fixed my own problem or not but I rebooted the Springpath VM that had the HX Connect IP under it. That seemed to allow me back in the HX Connect.
