Embed Size (px)
Citation preview
Upgrade Procedures
bull Recommended Upgrade Method on page 1bull Upgrading Your HyperFlex Cluster Using the HX Connect UI on page 1bull Post vCenter Upgrade Tasks on page 4bull Online Upgrade Process Workflow on page 5bull Offline Upgrade Process Workflow on page 8
Recommended Upgrade MethodFor both combined upgrade and split upgrade Cisco recommends upgrading the HyperFlex components inthe following order for optimizing the upgrade time
Make sure to upgrade the vCenter to the desired version based on the ESXi version and recommendation fromVMware before upgrading ESXi
Note
1 Upgrade Cisco UCS Infrastructure
2 Upgrade Cisco HX Data Platform
3 Upgrade Cisco customized VMware ESXi
4 Upgrade Cisco UCS firmware
Upgrading Your HyperFlex Cluster Using the HX Connect UI
Hypercheck Health Check UtilitymdashCisco recommends running this proactive health check utility on yourHyperFlex cluster prior to upgrade These checks provide early visibility into any areas that may need attentionand will help ensure a seamless upgrade experience For more information see the Hyperflex Health ampPre-Upgrade Check Tool TechNote for full instructions on how to install and run Hypercheck
Note
Upgrade Procedures1
Use the HX Connect UI when upgrading from a current HX Data Platform version of 25(1a) or later releasesImportant
Procedure
Step 1 If UCSM (A-bundle) or UCS Server Firmware (C-bundle) upgrade is required download Cisco UCSInfrastructure A blade bundle B and rack bundle C See Downloading Software for more details
Step 2 Ensure that the hx-storage-data and vMotion upstream switches are configured for full network failovercapability before proceeding forward Otherwise the HyperFlex Cluster becomes offline and all datastoresunmount from the ESXi hosts See Test Upstream Network Connectivity for more details
Step 3 Upgrade Cisco UCS Infrastructure bundle as required See Upgrading Cisco UCS Infrastructure Using CiscoUCS Manager for more details
It is important that you manually upgrade the UCS infrastructure first before initiating the upgradesequence of the HyperFlex components as outlined in Recommended Upgrade Method on page1 The upgrade feature of the HX Platform software will not upgrade the UCS infrastructurebundle This upgrade is a manual process
Note
Step 4 Bootstrap to upgrade Cisco HX Data Platform
If you are running HyperFlex release 35(1a) or later you can upgrade the Cisco HX Data Platformby performing the auto-bootstrap process from the HXConnect UI (Auto Bootstrap Upgrade Processfrom HX Connect UI) However if you are running a HyperFlex release that is earlier than release35(1a) you must run the manual bootstrap process to upgrade the Cisco HXData Platform (ManualBootstrap Upgrade Process)
Note
Step 5 Log in to HX Connecta) Enter the HX Storage Cluster management IP address in a browser Navigate to
httpsltstorage-cluster-management-ipgtb) Enter the administrative username and passwordc) Click Login
Step 6 In the Navigation pane select UpgradeStep 7 Choose the type of upgrade from the Select Upgrade Type page
After manual bootstrap validation will fail if you perform UCS only ESXi only or UCS and ESXicombined upgrade For successful upgrade Cisco recommends the following upgrade types
bull HX Data Platform only upgrade followed by UCS Firmware andor Hypervisor Softwareupgrade
bull HX Data Platform and UCS Firmware
bull HX Data Platform and Hypervisor Software
bull HX Data Platform UCS Firmware and Hypervisor Software
Caution
Step 8 Depending on the type of upgrade you want to perform complete the following fields on theEnter Credentialstab
Upgrade Procedures2
Upgrade ProceduresUpgrading Your HyperFlex Cluster Using the HX Connect UI
UCS Server Firmware
Essential InformationField
Enter the Cisco UCS Manager FQDN or IP address Example10193211120
UCS Manager Hostname field
Enter the Cisco UCS Manager ltadmingt usernameUser Name field
Enter the Cisco UCS Manager ltadmingt passwordAdmin Password field
Click Discover to view the current UCS firmware package version inthe Current Version field
Discover button
HX Data Platform
Essential InformationUI Element
Upload the latest Cisco HyperFlex Data Platform Upgrade Bundle forupgrading existing clusters with previous releasetgz package file fromDownload Software - HyperFlex HX Data Platform
Sample file name format storfs-packages-352a-31601tgz
Drag the HX file here or click tobrowse
Displays the current HyperFlex Data Platform versionCurrent version
Lists the HyperFlex cluster details like the HyperFlex version andCluster upgrade state
Current cluster details
Displays the HyperFlex Data Platform version of the uploaded bundleBundle version
The MD5 Checksum number is stored in a separate text file at the tmpdirectory where the upgrade package was downloaded
This is an optional step that helps you verify the integrity of the uploadedupgrade package bundle
(Optional) Checksum field
ESXi
The ESXi upgrade option is supported in the HyperFlex Connect UI for HyperFlex release 35(1a)or later
Note
Essential InformationUI Element
Upload the latest Cisco HyperFlex Custom Image Offline Bundle forupgrading existing ESXi hosts from Download Software - HyperFlexHX Data Platform
ExampleHX-ESXi-65U2-10884925-Cisco-Custom-6524-upgrade-bundlezip
Drag the ESXi file here or clickto browse field
Displays the current ESXi versionCurrent version field
Lists the HyperFlex cluster details like the Hypervisor version andCluster upgrade state
Current hypervisor details field
Upgrade Procedures3
Upgrade ProceduresUpgrading Your HyperFlex Cluster Using the HX Connect UI
Essential InformationUI Element
Displays the ESXi version of the uploaded bundleBundle details field
vCenter Credentials
Essential InformationUI Element
Enter the vCenter ltadmingt usernameUser Name field
Enter the vCenter ltadmingt passwordAdmin Password field
Step 9 Click Upgrade to begin the cluster upgrade processStep 10 The Validation Screen on the Upgrade Progress page displays the progress of the checks performed Fix
validation errors if any Confirm that the upgrade is complete
When upgrade is in progress you may see an error message Websocket connection failed Automatic refreshdisabled You can either refresh the page or log out and log back in to clear the error message You can safelyignore this error message
During cluster upgrade if the orchestration node reboots or power cycles due to power issue the clusterupgrade will be stuck Once the node is up restart the cluster upgrade process after cleaning the cluster systemusing the following commandstcli cluster upgrade --components hxdp ndashclean
If the clean-up command fails restart the stMgr service on all control VMs (ctrlVM) by running the followingcommandrestart stMgr
Then clean the cluster system by rerunning the following commandstcli cluster upgrade --components hxdp ndashclean
Here is a sample coderootucs-stctlvm-385-1~ stcli cluster upgrade --clean --components hxdpForcefully cleaned up upgrade progressrootucs-stctlvm-385-1~ stcli cluster upgrade --statusNo active upgrade found Upgrade progress available after triggering an upgrade
Post vCenter Upgrade TasksIf the extension is not working and HyperFLex and vCenter are upgraded to compatible version perform thefollowing steps
If you have more than one HyperFlex cluster then you must first update all HX clusters to compatible HXversions for the corresponding vCenter versions prior to attempting to reregister Do not unregistercomspringpathsysmgmt unless all clusters are removed from the vCenter
Note
Upgrade Procedures4
Upgrade ProceduresPost vCenter Upgrade Tasks
Before you begin
Verify the extension is working If so then there is no need to perform any post upgrade tasks
Procedure
Step 1 Try to reregister the extenstion If the extension still does not work then continue with the next stepsStep 2 Unregister the extension
Examplecomspringpathsysmgmtdomain-ltidgt
comspringpathsysmgmt
Use the mob browser httpsltvCenter IP or FQDNgtmob (content gt extensionManager path and InvokeUnregisterExtension method)
We recommend to remove the cluster before unregistering extensionsNote
Step 3 Re-register the Springpath plug-in using
Examplestcli cluster reregister
You can use stcli cluster reregister ndash-h for help and then continue with thereregistration
Note
Online Upgrade Process Workflow
If you are running HyperFlex release 35(1a) or later you can upgrade the Cisco HX Data Platform byperforming the auto-bootstrap process from the HX Connect UI (Auto Bootstrap Upgrade Process from HXConnect UI) However if you are running a HyperFlex release that is earlier than release 35(1a) you mustrun the manual bootstrap process to upgrade the Cisco HXData Platform (Manual Bootstrap Upgrade Process)
Attention
When using the online upgrade process workflow consider the following
bull First upgrade Cisco UCS infrastructure to the latest version and then use the automated upgrade workflowfor a combined upgrade of Cisco UCS firmware and Cisco HX Data Platform Online upgrade uses hostfirmware packages to upgrade all server endpoints
bull During online upgrade as one node is being upgraded (placed into maintenance mode) the number oftolerated node failures is reduced based on the Data Replication Factor and the Access Policy settings
See Entering Cisco HyperFlex Maintenance Mode for the procedures on how to access Cisco HyperFlexMaintenance Mode
bull If upgrading both HXDP and UCS firmware combined upgrade can be selected through HX Connectdepending on the length of the maintenance window
Upgrade Procedures5
Upgrade ProceduresOnline Upgrade Process Workflow
bull Do not use Firefox browser It is not supported due to an outdated version of flash that is bundled withthe browser
Cisco UCSManager infrastructure upgrade is only supported using AutoInstall and the direct server firmwareupgrade should be performed only through the upgrade orchestration framework provided by the HX DataPlatform Plug-in
Note
During the online upgrade process do not acknowledge server reboot pending activities from UCS ManagerDoing so will interrupt the upgrade process and can cause storage outage HyperFlex will automatically rebooteach node
Note
The following table summarizes the online upgrade workflow
ReferenceDescriptionStep
Downloading SoftwareIf UCSM (A-bundle) or UCS Server Firmware(C-bundle) upgrade is required download Cisco UCSInfrastructure A blade bundle B and rack bundle C
1
Test Upstream NetworkConnectivity
Ensure that the hx-storage-data and vMotion upstreamswitches are configured for full network failovercapability before proceeding forward Otherwise theHyperFlex Cluster becomes offline and all datastoresunmount from the ESXi hosts
2
Upgrading Cisco UCSInfrastructure Using Cisco UCSManager
Upgrade Cisco UCS Infrastructure bundle as required
It is important that you manually upgradethe UCS infrastructure first before initiatingthe upgrade sequence of the HyperFlexcomponents as outlined in RecommendedUpgrade Method on page 1 The upgradefeature of the HX Platform software willnot upgrade the UCS infrastructure bundleThis upgrade is a manual process
Note
3
Upgrade Procedures6
Upgrade ProceduresOnline Upgrade Process Workflow
ReferenceDescriptionStep
HX Release 35(1a) and later
bull Auto bootstrap is supportedbeginning with HX release35(1a) Auto BootstrapUpgrade Process from HXConnect UI
HX Release earlier than 35(1a)
bull Manual cluster bootstrap isrequired HX releases earlierthan 35(1a) ManualBootstrap Upgrade Process
Bootstrap to upgrade Cisco HX Data Platform4
Run the command stcli
snapshot-schedule --disableDisable snapshot schedule on the bootstrapped storagecontroller VM
It is enough to run this script on one of thecontroller nodes
Note
5
Log in to HX Connect with administrator credentials6
Upgrading Your HyperFlex ClusterUsing the HX Connect UI on page1
Start combined upgrade of
bull HX Data Platform and UCS Firmware
bull HX Data Platform and Hypervisor Software
7
Upgrading Cisco HyperFlex DataPlatform Using HX Connect
Upgrading Cisco UCS ServerFirmware Using the HX ConnectUI
Upgrading ESXi Using the HXConnect UI
To perform a split upgrade you mustupgrade HX Data Platform first After HXData Platform is upgraded to 35(1x) youcan perform a split upgrade of UCSM onlyandor ESXi only
When only UCS firmware is beingupgraded you may see the upgrade processpause at the validation screen after the fabricinterconnect discovery It may be a networkconnectivity failure issue however in mostcases it just requires waiting for the processto finish
Attention
Post Upgrade TasksConfirm that the upgrade task is complete8
Starting with 40(2a) releaseDynamic self-signed certificate aregenerated rather than staticcertificates
Dynamic certificate creation9
Run the command stcli
snapshot-schedule -ndashenableOn the same controller VM enable snapshot schedule10
Upgrade Procedures7
Upgrade ProceduresOnline Upgrade Process Workflow
Offline Upgrade Process WorkflowThe following table summarizes the offline upgrade workflow
ReferenceDescriptionStep
Downloading SoftwareIf UCSM (A-bundle) or UCSServer Firmware (C-bundle)upgrade is required downloadCisco UCS Infrastructure A bladebundle B and rack bundle C
1
Test Upstream NetworkConnectivity
Ensure that the hx-storage-data andvMotion upstream switches areconfigured for full network failovercapability before proceedingforward Otherwise the HyperFlexCluster becomes offline and alldatastores unmount from the ESXihosts
2
Upgrading Cisco UCSInfrastructure Using Cisco UCSManager
Upgrade Cisco UCS Infrastructurebundle as required
It is important that youmanually upgrade theUCS infrastructure firstbefore initiating theupgrade sequence of theHyperFlex componentsas outlined inRecommendedUpgradeMethod on page 1The upgrade feature ofthe HX Platformsoftware will notupgrade the UCSinfrastructure bundleThis upgrade is amanual process
Note
3
Upgrade Procedures8
Upgrade ProceduresOffline Upgrade Process Workflow
ReferenceDescriptionStep
Graceful Shutdown of a HXClusterLaunch the vSphere Web Clientand power down all user VMsresiding on HX servers and all userVMs running on HX datastoresThis includes VMs running oncompute-only nodes After theVMshave been shut down verify thehealth state of the cluster andperform a graceful shutdown
HyperFlex controllerVMs (stCtlVMs) mustremain powered on
Important
4
Modifying Host Firmware PackageUsing Cisco UCS Manager
Manually stage the correctfirmware version before starting theupgrade process
5
In vCenter right-click on each HXController VM (stCtlVM) andselect Power gt Shut Down GuestOS
Shutdown theHyperFlexControllerVMs (stCtlVMs)
6
In vCenter right-click on eachESXi host select MaintenanceMode gt Enter MaintenanceMode
Once the Controller VMs areshutdown place the ESXi hostsinto Maintenance Mode
7
Acknowledge the pending rebooton the servers that comprise yourHX cluster nodes including bothconverged nodes and compute-onlynodes connected to the clusterWait until all nodes are upgradedConfirm that correct firmwarepackages have been installed beforeproceeding
8
In vCenter right-click on eachESXi host select MaintenanceMode gtExit Maintenance Mode
Once the ESXi hosts have bootedtake them out of MaintenanceMode Now the controller VMshould come back online
9
Upgrade Procedures9
Upgrade ProceduresOffline Upgrade Process Workflow
ReferenceDescriptionStep
Manual Bootstrap Upgrade ProcessBootstrap to upgrade the Cisco HXData Platform Plug-in
Important bull Be sure to copy thebootstrap file to thecontroller VMtmp directory
bull Ensure that youconfirm the versionof the plug-in inthe vCenterAdministration gtClient Plug-Inspage
10
Run the command stcli
snapshot-schedule --disableDisable snapshot schedule on thebootstrapped storage controllerVM
It is enough to run thisscript on one of thecontroller nodes
Note
11
Upgrading Your HyperFlex ClusterUsing the HX Connect UI on page1
Offline Upgrade Using CLI onpage 11
From the same controller VMbegin the upgrade
12
Post Upgrade TasksConfirm that upgrade is complete13
Start Cluster and Power On VMs on page 12
After the upgrade is complete startthe cluster and power on VMs
14
Run the command stcli
snapshot-schedule -ndashenableOn the same controller VM enablesnapshot schedule
15
Offline Upgrade Guidelines
bull --ucsm-host and --ucsm-user parameters are required when you are upgrading from 17x to 18x Theseparameters must not be used when moving up from 18(1a)18(1b) to 20(1a) as we are not changingthe Cisco UCS server firmware version
Cisco recommends using HX Connect UI to upgrade HyperFlex clusters over CLI for ease of use andbetter reporting You can safely ignore Cluster Invalid State alerts in HX Connect
Important
Upgrade Procedures10
Upgrade ProceduresOffline Upgrade Guidelines
Before you proceed with either combined or split upgrade consider the following guidelines
bull The package name must match the file that you uploaded to the controller VM
bull Enter passwords when prompted
bull Nodes are upgraded with the new version of the Cisco HX Data Platform software and rebooted one ata time
bull Offline cluster upgrades with nested vCenter is not supported
Offline Upgrade Using CLI
If you need to perform a split upgrade you must upgrade HX Data Platform first After HX Data Platform isupgraded to Release 35(1x) you can perform a split upgrade of UCSM only andor ESXi only
Important
Combined Upgrade of Cisco HX Data Platform ESXi and Cisco UCS Firmware
M5 Servers
stcli cluster upgrade --components ucs-fw hxdp hypervisor --locationtmpltstorfs package nameESXi package namegt --ucsm-host ltIPFQDN of UCSMgt--ucsm-user ltUCSM Usergt --ucsm5-fw-version ltUCSM Firmware Versiongt
Example for M5 Servers
~ stcli cluster upgrade --components ucs-fw hxdp hypervisor --locationtmpstorfs-packages-351a-19712tgz--ucsm-host eng-fi16engstorvisorcom --ucsm-user admin --ucs5fw-version 31(2g)
M4 Servers
stcli cluster upgrade --components ucs-fw hxdp hypervisor --locationtmpltstorfs package name ESXi package namegt --ucsm-host ltIPFQDN of UCSMgt--ucsm-user ltUCSM Usergt --ucsfw-version ltUCSM Firmware Versiongt
Example for M4 Servers
~ stcli cluster upgrade --components ucs-fw hxdp hypervisor --locationtmpstorfs-packages-351a-19712tgz--ucsm-host eng-fi16engstorvisorcom --ucsm-user admin --ucsfw-version 31(2g)
Combined Upgrade of Cisco HX Data Platform and ESXi
M5 Servers
stcli cluster upgrade --components hxdphypervisor --location tmphxupgrade_bundletgz--hypervisor-bundle tmpesxiupgrade_bundlezip
Example for M5 Servers
~ stcli cluster upgrade --components hxdphypervisor --location tmphxupgrade_bundletgz--hypervisor-bundle tmpesxiupgrade_bundlezip
M4 Servers
stcli cluster upgrade --components hxdphypervisor --location tmphxupgrade_bundletgz--hypervisor-bundle tmpesxiupgrade_bundlezip
Example for M4 Servers
Upgrade Procedures11
Upgrade ProceduresOffline Upgrade Using CLI
~ stcli cluster upgrade --components hxdphypervisor --location tmphxupgrade_bundletgz--hypervisor-bundle tmpesxiupgrade_bundlezip
Combined Upgrade of Cisco HX Data Platform and Cisco UCS Firmware
M5 Servers
stcli cluster upgrade --components hxdpucs-fw --locationtmpltstorfs package namegt --vcenter-user ltvcusergt --ucsm-host ltIPFQDN of UCSMgt--ucsm-user ltUCSM Usergt --ucsm5-fw-version ltUCSM Firmware Versiongt
M4 Servers
stcli cluster upgrade --components hxdpucs-fw --locationtmpltstorfs package namegt --vcenter-user ltvcusergt --ucsm-host ltIPFQDN of UCSMgt--ucsm-user ltUCSM Usergt --ucsfw-version ltUCSM Firmware Versiongt
Example for M4 Servers
~ stcli cluster upgrade --components hxdpucs-fw --locationtmpstorfs-packages-181c-19712tgz --vcenter-user administratorvspherelocal--ucsm-host eng-fi16engstorvisorcom --ucsm-user admin --ucsfw-version 31(2b)
Start Cluster and Power On VMsAfter the upgrade is complete and the cluster has been upgraded log out and log back in to vCenter to seeupgrade changes
Procedure
Step 1 After the upgrade is complete start your clusterStep 2 Login to any controller VM through SSH
stcli cluster start
ExampleHyperFlex StorageController 18(1c)Last login Wed Sept 21 235423 2016 from pguo-devengstorvisorcomrootucs-stclivm - 384 -1~ stcli cluster upgrade-statusCluster upgrade succeeded Cluster version 18(1c)rootucs-stctlvm-384~ stcli cluster startwaiting for Cluster to start on nodes [ucs-383 ucs-384 ucs-385 ucs-386]
This will start the cluster and mount the HX datastores Wait for cluster to come online You will see thepromptStarted cluster on nodes [ucs-383 ucs-384 ucs-385 ucs-386]Cluster is onlinerootucs-stctlvm-384-1~
Step 3 Wait for cluster to become healthy before starting the VMs Run command
~ stcli clustr info| grep health
Example
rootSpringpathControllerZRVF040451~ stcli cluster info | grep healthhealthState healthy
Upgrade Procedures12
Upgrade ProceduresStart Cluster and Power On VMs
state healthystorage cluster is healthy
Step 4 After the cluster is healthy launch vSphere Web Client or Thick Client navigate to Hosts and Cluster gtDatacenter gt Cluster gt Right click select Powergt Power On to start the VMs
Upgrade Procedures13
Upgrade ProceduresStart Cluster and Power On VMs
Upgrade Procedures14
Upgrade ProceduresStart Cluster and Power On VMs
Use the HX Connect UI when upgrading from a current HX Data Platform version of 25(1a) or later releasesImportant
Procedure
Step 1 If UCSM (A-bundle) or UCS Server Firmware (C-bundle) upgrade is required download Cisco UCSInfrastructure A blade bundle B and rack bundle C See Downloading Software for more details
Step 2 Ensure that the hx-storage-data and vMotion upstream switches are configured for full network failovercapability before proceeding forward Otherwise the HyperFlex Cluster becomes offline and all datastoresunmount from the ESXi hosts See Test Upstream Network Connectivity for more details
Step 3 Upgrade Cisco UCS Infrastructure bundle as required See Upgrading Cisco UCS Infrastructure Using CiscoUCS Manager for more details
It is important that you manually upgrade the UCS infrastructure first before initiating the upgradesequence of the HyperFlex components as outlined in Recommended Upgrade Method on page1 The upgrade feature of the HX Platform software will not upgrade the UCS infrastructurebundle This upgrade is a manual process
Note
Step 4 Bootstrap to upgrade Cisco HX Data Platform
If you are running HyperFlex release 35(1a) or later you can upgrade the Cisco HX Data Platformby performing the auto-bootstrap process from the HXConnect UI (Auto Bootstrap Upgrade Processfrom HX Connect UI) However if you are running a HyperFlex release that is earlier than release35(1a) you must run the manual bootstrap process to upgrade the Cisco HXData Platform (ManualBootstrap Upgrade Process)
Note
Step 5 Log in to HX Connecta) Enter the HX Storage Cluster management IP address in a browser Navigate to
httpsltstorage-cluster-management-ipgtb) Enter the administrative username and passwordc) Click Login
Step 6 In the Navigation pane select UpgradeStep 7 Choose the type of upgrade from the Select Upgrade Type page
After manual bootstrap validation will fail if you perform UCS only ESXi only or UCS and ESXicombined upgrade For successful upgrade Cisco recommends the following upgrade types
bull HX Data Platform only upgrade followed by UCS Firmware andor Hypervisor Softwareupgrade
bull HX Data Platform and UCS Firmware
bull HX Data Platform and Hypervisor Software
bull HX Data Platform UCS Firmware and Hypervisor Software
Caution
Step 8 Depending on the type of upgrade you want to perform complete the following fields on theEnter Credentialstab
Upgrade Procedures2
Upgrade ProceduresUpgrading Your HyperFlex Cluster Using the HX Connect UI
UCS Server Firmware
Essential InformationField
Enter the Cisco UCS Manager FQDN or IP address Example10193211120
UCS Manager Hostname field
Enter the Cisco UCS Manager ltadmingt usernameUser Name field
Enter the Cisco UCS Manager ltadmingt passwordAdmin Password field
Click Discover to view the current UCS firmware package version inthe Current Version field
Discover button
HX Data Platform
Essential InformationUI Element
Upload the latest Cisco HyperFlex Data Platform Upgrade Bundle forupgrading existing clusters with previous releasetgz package file fromDownload Software - HyperFlex HX Data Platform
Sample file name format storfs-packages-352a-31601tgz
Drag the HX file here or click tobrowse
Displays the current HyperFlex Data Platform versionCurrent version
Lists the HyperFlex cluster details like the HyperFlex version andCluster upgrade state
Current cluster details
Displays the HyperFlex Data Platform version of the uploaded bundleBundle version
The MD5 Checksum number is stored in a separate text file at the tmpdirectory where the upgrade package was downloaded
This is an optional step that helps you verify the integrity of the uploadedupgrade package bundle
(Optional) Checksum field
ESXi
The ESXi upgrade option is supported in the HyperFlex Connect UI for HyperFlex release 35(1a)or later
Note
Essential InformationUI Element
Upload the latest Cisco HyperFlex Custom Image Offline Bundle forupgrading existing ESXi hosts from Download Software - HyperFlexHX Data Platform
ExampleHX-ESXi-65U2-10884925-Cisco-Custom-6524-upgrade-bundlezip
Drag the ESXi file here or clickto browse field
Displays the current ESXi versionCurrent version field
Lists the HyperFlex cluster details like the Hypervisor version andCluster upgrade state
Current hypervisor details field
Upgrade Procedures3
Upgrade ProceduresUpgrading Your HyperFlex Cluster Using the HX Connect UI
Essential InformationUI Element
Displays the ESXi version of the uploaded bundleBundle details field
vCenter Credentials
Essential InformationUI Element
Enter the vCenter ltadmingt usernameUser Name field
Enter the vCenter ltadmingt passwordAdmin Password field
Step 9 Click Upgrade to begin the cluster upgrade processStep 10 The Validation Screen on the Upgrade Progress page displays the progress of the checks performed Fix
validation errors if any Confirm that the upgrade is complete
When upgrade is in progress you may see an error message Websocket connection failed Automatic refreshdisabled You can either refresh the page or log out and log back in to clear the error message You can safelyignore this error message
During cluster upgrade if the orchestration node reboots or power cycles due to power issue the clusterupgrade will be stuck Once the node is up restart the cluster upgrade process after cleaning the cluster systemusing the following commandstcli cluster upgrade --components hxdp ndashclean
If the clean-up command fails restart the stMgr service on all control VMs (ctrlVM) by running the followingcommandrestart stMgr
Then clean the cluster system by rerunning the following commandstcli cluster upgrade --components hxdp ndashclean
Here is a sample coderootucs-stctlvm-385-1~ stcli cluster upgrade --clean --components hxdpForcefully cleaned up upgrade progressrootucs-stctlvm-385-1~ stcli cluster upgrade --statusNo active upgrade found Upgrade progress available after triggering an upgrade
Post vCenter Upgrade TasksIf the extension is not working and HyperFLex and vCenter are upgraded to compatible version perform thefollowing steps
If you have more than one HyperFlex cluster then you must first update all HX clusters to compatible HXversions for the corresponding vCenter versions prior to attempting to reregister Do not unregistercomspringpathsysmgmt unless all clusters are removed from the vCenter
Note
Upgrade Procedures4
Upgrade ProceduresPost vCenter Upgrade Tasks
Before you begin
Verify the extension is working If so then there is no need to perform any post upgrade tasks
Procedure
Step 1 Try to reregister the extenstion If the extension still does not work then continue with the next stepsStep 2 Unregister the extension
Examplecomspringpathsysmgmtdomain-ltidgt
comspringpathsysmgmt
Use the mob browser httpsltvCenter IP or FQDNgtmob (content gt extensionManager path and InvokeUnregisterExtension method)
We recommend to remove the cluster before unregistering extensionsNote
Step 3 Re-register the Springpath plug-in using
Examplestcli cluster reregister
You can use stcli cluster reregister ndash-h for help and then continue with thereregistration
Note
Online Upgrade Process Workflow
If you are running HyperFlex release 35(1a) or later you can upgrade the Cisco HX Data Platform byperforming the auto-bootstrap process from the HX Connect UI (Auto Bootstrap Upgrade Process from HXConnect UI) However if you are running a HyperFlex release that is earlier than release 35(1a) you mustrun the manual bootstrap process to upgrade the Cisco HXData Platform (Manual Bootstrap Upgrade Process)
Attention
When using the online upgrade process workflow consider the following
bull First upgrade Cisco UCS infrastructure to the latest version and then use the automated upgrade workflowfor a combined upgrade of Cisco UCS firmware and Cisco HX Data Platform Online upgrade uses hostfirmware packages to upgrade all server endpoints
bull During online upgrade as one node is being upgraded (placed into maintenance mode) the number oftolerated node failures is reduced based on the Data Replication Factor and the Access Policy settings
See Entering Cisco HyperFlex Maintenance Mode for the procedures on how to access Cisco HyperFlexMaintenance Mode
bull If upgrading both HXDP and UCS firmware combined upgrade can be selected through HX Connectdepending on the length of the maintenance window
Upgrade Procedures5
Upgrade ProceduresOnline Upgrade Process Workflow
bull Do not use Firefox browser It is not supported due to an outdated version of flash that is bundled withthe browser
Cisco UCSManager infrastructure upgrade is only supported using AutoInstall and the direct server firmwareupgrade should be performed only through the upgrade orchestration framework provided by the HX DataPlatform Plug-in
Note
During the online upgrade process do not acknowledge server reboot pending activities from UCS ManagerDoing so will interrupt the upgrade process and can cause storage outage HyperFlex will automatically rebooteach node
Note
The following table summarizes the online upgrade workflow
ReferenceDescriptionStep
Downloading SoftwareIf UCSM (A-bundle) or UCS Server Firmware(C-bundle) upgrade is required download Cisco UCSInfrastructure A blade bundle B and rack bundle C
1
Test Upstream NetworkConnectivity
Ensure that the hx-storage-data and vMotion upstreamswitches are configured for full network failovercapability before proceeding forward Otherwise theHyperFlex Cluster becomes offline and all datastoresunmount from the ESXi hosts
2
Upgrading Cisco UCSInfrastructure Using Cisco UCSManager
Upgrade Cisco UCS Infrastructure bundle as required
It is important that you manually upgradethe UCS infrastructure first before initiatingthe upgrade sequence of the HyperFlexcomponents as outlined in RecommendedUpgrade Method on page 1 The upgradefeature of the HX Platform software willnot upgrade the UCS infrastructure bundleThis upgrade is a manual process
Note
3
Upgrade Procedures6
Upgrade ProceduresOnline Upgrade Process Workflow
ReferenceDescriptionStep
HX Release 35(1a) and later
bull Auto bootstrap is supportedbeginning with HX release35(1a) Auto BootstrapUpgrade Process from HXConnect UI
HX Release earlier than 35(1a)
bull Manual cluster bootstrap isrequired HX releases earlierthan 35(1a) ManualBootstrap Upgrade Process
Bootstrap to upgrade Cisco HX Data Platform4
Run the command stcli
snapshot-schedule --disableDisable snapshot schedule on the bootstrapped storagecontroller VM
It is enough to run this script on one of thecontroller nodes
Note
5
Log in to HX Connect with administrator credentials6
Upgrading Your HyperFlex ClusterUsing the HX Connect UI on page1
Start combined upgrade of
bull HX Data Platform and UCS Firmware
bull HX Data Platform and Hypervisor Software
7
Upgrading Cisco HyperFlex DataPlatform Using HX Connect
Upgrading Cisco UCS ServerFirmware Using the HX ConnectUI
Upgrading ESXi Using the HXConnect UI
To perform a split upgrade you mustupgrade HX Data Platform first After HXData Platform is upgraded to 35(1x) youcan perform a split upgrade of UCSM onlyandor ESXi only
When only UCS firmware is beingupgraded you may see the upgrade processpause at the validation screen after the fabricinterconnect discovery It may be a networkconnectivity failure issue however in mostcases it just requires waiting for the processto finish
Attention
Post Upgrade TasksConfirm that the upgrade task is complete8
Starting with 40(2a) releaseDynamic self-signed certificate aregenerated rather than staticcertificates
Dynamic certificate creation9
Run the command stcli
snapshot-schedule -ndashenableOn the same controller VM enable snapshot schedule10
Upgrade Procedures7
Upgrade ProceduresOnline Upgrade Process Workflow
Offline Upgrade Process WorkflowThe following table summarizes the offline upgrade workflow
ReferenceDescriptionStep
Downloading SoftwareIf UCSM (A-bundle) or UCSServer Firmware (C-bundle)upgrade is required downloadCisco UCS Infrastructure A bladebundle B and rack bundle C
1
Test Upstream NetworkConnectivity
Ensure that the hx-storage-data andvMotion upstream switches areconfigured for full network failovercapability before proceedingforward Otherwise the HyperFlexCluster becomes offline and alldatastores unmount from the ESXihosts
2
Upgrading Cisco UCSInfrastructure Using Cisco UCSManager
Upgrade Cisco UCS Infrastructurebundle as required
It is important that youmanually upgrade theUCS infrastructure firstbefore initiating theupgrade sequence of theHyperFlex componentsas outlined inRecommendedUpgradeMethod on page 1The upgrade feature ofthe HX Platformsoftware will notupgrade the UCSinfrastructure bundleThis upgrade is amanual process
Note
3
Upgrade Procedures8
Upgrade ProceduresOffline Upgrade Process Workflow
ReferenceDescriptionStep
Graceful Shutdown of a HXClusterLaunch the vSphere Web Clientand power down all user VMsresiding on HX servers and all userVMs running on HX datastoresThis includes VMs running oncompute-only nodes After theVMshave been shut down verify thehealth state of the cluster andperform a graceful shutdown
HyperFlex controllerVMs (stCtlVMs) mustremain powered on
Important
4
Modifying Host Firmware PackageUsing Cisco UCS Manager
Manually stage the correctfirmware version before starting theupgrade process
5
In vCenter right-click on each HXController VM (stCtlVM) andselect Power gt Shut Down GuestOS
Shutdown theHyperFlexControllerVMs (stCtlVMs)
6
In vCenter right-click on eachESXi host select MaintenanceMode gt Enter MaintenanceMode
Once the Controller VMs areshutdown place the ESXi hostsinto Maintenance Mode
7
Acknowledge the pending rebooton the servers that comprise yourHX cluster nodes including bothconverged nodes and compute-onlynodes connected to the clusterWait until all nodes are upgradedConfirm that correct firmwarepackages have been installed beforeproceeding
8
In vCenter right-click on eachESXi host select MaintenanceMode gtExit Maintenance Mode
Once the ESXi hosts have bootedtake them out of MaintenanceMode Now the controller VMshould come back online
9
Upgrade Procedures9
Upgrade ProceduresOffline Upgrade Process Workflow
ReferenceDescriptionStep
Manual Bootstrap Upgrade ProcessBootstrap to upgrade the Cisco HXData Platform Plug-in
Important bull Be sure to copy thebootstrap file to thecontroller VMtmp directory
bull Ensure that youconfirm the versionof the plug-in inthe vCenterAdministration gtClient Plug-Inspage
10
Run the command stcli
snapshot-schedule --disableDisable snapshot schedule on thebootstrapped storage controllerVM
It is enough to run thisscript on one of thecontroller nodes
Note
11
Upgrading Your HyperFlex ClusterUsing the HX Connect UI on page1
Offline Upgrade Using CLI onpage 11
From the same controller VMbegin the upgrade
12
Post Upgrade TasksConfirm that upgrade is complete13
Start Cluster and Power On VMs on page 12
After the upgrade is complete startthe cluster and power on VMs
14
Run the command stcli
snapshot-schedule -ndashenableOn the same controller VM enablesnapshot schedule
15
Offline Upgrade Guidelines
bull --ucsm-host and --ucsm-user parameters are required when you are upgrading from 17x to 18x Theseparameters must not be used when moving up from 18(1a)18(1b) to 20(1a) as we are not changingthe Cisco UCS server firmware version
Cisco recommends using HX Connect UI to upgrade HyperFlex clusters over CLI for ease of use andbetter reporting You can safely ignore Cluster Invalid State alerts in HX Connect
Important
Upgrade Procedures10
Upgrade ProceduresOffline Upgrade Guidelines
Before you proceed with either combined or split upgrade consider the following guidelines
bull The package name must match the file that you uploaded to the controller VM
bull Enter passwords when prompted
bull Nodes are upgraded with the new version of the Cisco HX Data Platform software and rebooted one ata time
bull Offline cluster upgrades with nested vCenter is not supported
Offline Upgrade Using CLI
If you need to perform a split upgrade you must upgrade HX Data Platform first After HX Data Platform isupgraded to Release 35(1x) you can perform a split upgrade of UCSM only andor ESXi only
Important
Combined Upgrade of Cisco HX Data Platform ESXi and Cisco UCS Firmware
M5 Servers
stcli cluster upgrade --components ucs-fw hxdp hypervisor --locationtmpltstorfs package nameESXi package namegt --ucsm-host ltIPFQDN of UCSMgt--ucsm-user ltUCSM Usergt --ucsm5-fw-version ltUCSM Firmware Versiongt
Example for M5 Servers
~ stcli cluster upgrade --components ucs-fw hxdp hypervisor --locationtmpstorfs-packages-351a-19712tgz--ucsm-host eng-fi16engstorvisorcom --ucsm-user admin --ucs5fw-version 31(2g)
M4 Servers
stcli cluster upgrade --components ucs-fw hxdp hypervisor --locationtmpltstorfs package name ESXi package namegt --ucsm-host ltIPFQDN of UCSMgt--ucsm-user ltUCSM Usergt --ucsfw-version ltUCSM Firmware Versiongt
Example for M4 Servers
~ stcli cluster upgrade --components ucs-fw hxdp hypervisor --locationtmpstorfs-packages-351a-19712tgz--ucsm-host eng-fi16engstorvisorcom --ucsm-user admin --ucsfw-version 31(2g)
Combined Upgrade of Cisco HX Data Platform and ESXi
M5 Servers
stcli cluster upgrade --components hxdphypervisor --location tmphxupgrade_bundletgz--hypervisor-bundle tmpesxiupgrade_bundlezip
Example for M5 Servers
~ stcli cluster upgrade --components hxdphypervisor --location tmphxupgrade_bundletgz--hypervisor-bundle tmpesxiupgrade_bundlezip
M4 Servers
stcli cluster upgrade --components hxdphypervisor --location tmphxupgrade_bundletgz--hypervisor-bundle tmpesxiupgrade_bundlezip
Example for M4 Servers
Upgrade Procedures11
Upgrade ProceduresOffline Upgrade Using CLI
~ stcli cluster upgrade --components hxdphypervisor --location tmphxupgrade_bundletgz--hypervisor-bundle tmpesxiupgrade_bundlezip
Combined Upgrade of Cisco HX Data Platform and Cisco UCS Firmware
M5 Servers
stcli cluster upgrade --components hxdpucs-fw --locationtmpltstorfs package namegt --vcenter-user ltvcusergt --ucsm-host ltIPFQDN of UCSMgt--ucsm-user ltUCSM Usergt --ucsm5-fw-version ltUCSM Firmware Versiongt
M4 Servers
stcli cluster upgrade --components hxdpucs-fw --locationtmpltstorfs package namegt --vcenter-user ltvcusergt --ucsm-host ltIPFQDN of UCSMgt--ucsm-user ltUCSM Usergt --ucsfw-version ltUCSM Firmware Versiongt
Example for M4 Servers
~ stcli cluster upgrade --components hxdpucs-fw --locationtmpstorfs-packages-181c-19712tgz --vcenter-user administratorvspherelocal--ucsm-host eng-fi16engstorvisorcom --ucsm-user admin --ucsfw-version 31(2b)
Start Cluster and Power On VMsAfter the upgrade is complete and the cluster has been upgraded log out and log back in to vCenter to seeupgrade changes
Procedure
Step 1 After the upgrade is complete start your clusterStep 2 Login to any controller VM through SSH
stcli cluster start
ExampleHyperFlex StorageController 18(1c)Last login Wed Sept 21 235423 2016 from pguo-devengstorvisorcomrootucs-stclivm - 384 -1~ stcli cluster upgrade-statusCluster upgrade succeeded Cluster version 18(1c)rootucs-stctlvm-384~ stcli cluster startwaiting for Cluster to start on nodes [ucs-383 ucs-384 ucs-385 ucs-386]
This will start the cluster and mount the HX datastores Wait for cluster to come online You will see thepromptStarted cluster on nodes [ucs-383 ucs-384 ucs-385 ucs-386]Cluster is onlinerootucs-stctlvm-384-1~
Step 3 Wait for cluster to become healthy before starting the VMs Run command
~ stcli clustr info| grep health
Example
rootSpringpathControllerZRVF040451~ stcli cluster info | grep healthhealthState healthy
Upgrade Procedures12
Upgrade ProceduresStart Cluster and Power On VMs
state healthystorage cluster is healthy
Step 4 After the cluster is healthy launch vSphere Web Client or Thick Client navigate to Hosts and Cluster gtDatacenter gt Cluster gt Right click select Powergt Power On to start the VMs
Upgrade Procedures13
Upgrade ProceduresStart Cluster and Power On VMs
Upgrade Procedures14
Upgrade ProceduresStart Cluster and Power On VMs
UCS Server Firmware
Essential InformationField
Enter the Cisco UCS Manager FQDN or IP address Example10193211120
UCS Manager Hostname field
Enter the Cisco UCS Manager ltadmingt usernameUser Name field
Enter the Cisco UCS Manager ltadmingt passwordAdmin Password field
Click Discover to view the current UCS firmware package version inthe Current Version field
Discover button
HX Data Platform
Essential InformationUI Element
Upload the latest Cisco HyperFlex Data Platform Upgrade Bundle forupgrading existing clusters with previous releasetgz package file fromDownload Software - HyperFlex HX Data Platform
Sample file name format storfs-packages-352a-31601tgz
Drag the HX file here or click tobrowse
Displays the current HyperFlex Data Platform versionCurrent version
Lists the HyperFlex cluster details like the HyperFlex version andCluster upgrade state
Current cluster details
Displays the HyperFlex Data Platform version of the uploaded bundleBundle version
The MD5 Checksum number is stored in a separate text file at the tmpdirectory where the upgrade package was downloaded
This is an optional step that helps you verify the integrity of the uploadedupgrade package bundle
(Optional) Checksum field
ESXi
The ESXi upgrade option is supported in the HyperFlex Connect UI for HyperFlex release 35(1a)or later
Note
Essential InformationUI Element
Upload the latest Cisco HyperFlex Custom Image Offline Bundle forupgrading existing ESXi hosts from Download Software - HyperFlexHX Data Platform
ExampleHX-ESXi-65U2-10884925-Cisco-Custom-6524-upgrade-bundlezip
Drag the ESXi file here or clickto browse field
Displays the current ESXi versionCurrent version field
Lists the HyperFlex cluster details like the Hypervisor version andCluster upgrade state
Current hypervisor details field
Upgrade Procedures3
Upgrade ProceduresUpgrading Your HyperFlex Cluster Using the HX Connect UI
Essential InformationUI Element
Displays the ESXi version of the uploaded bundleBundle details field
vCenter Credentials
Essential InformationUI Element
Enter the vCenter ltadmingt usernameUser Name field
Enter the vCenter ltadmingt passwordAdmin Password field
Step 9 Click Upgrade to begin the cluster upgrade processStep 10 The Validation Screen on the Upgrade Progress page displays the progress of the checks performed Fix
validation errors if any Confirm that the upgrade is complete
When upgrade is in progress you may see an error message Websocket connection failed Automatic refreshdisabled You can either refresh the page or log out and log back in to clear the error message You can safelyignore this error message
During cluster upgrade if the orchestration node reboots or power cycles due to power issue the clusterupgrade will be stuck Once the node is up restart the cluster upgrade process after cleaning the cluster systemusing the following commandstcli cluster upgrade --components hxdp ndashclean
If the clean-up command fails restart the stMgr service on all control VMs (ctrlVM) by running the followingcommandrestart stMgr
Then clean the cluster system by rerunning the following commandstcli cluster upgrade --components hxdp ndashclean
Here is a sample coderootucs-stctlvm-385-1~ stcli cluster upgrade --clean --components hxdpForcefully cleaned up upgrade progressrootucs-stctlvm-385-1~ stcli cluster upgrade --statusNo active upgrade found Upgrade progress available after triggering an upgrade
Post vCenter Upgrade TasksIf the extension is not working and HyperFLex and vCenter are upgraded to compatible version perform thefollowing steps
If you have more than one HyperFlex cluster then you must first update all HX clusters to compatible HXversions for the corresponding vCenter versions prior to attempting to reregister Do not unregistercomspringpathsysmgmt unless all clusters are removed from the vCenter
Note
Upgrade Procedures4
Upgrade ProceduresPost vCenter Upgrade Tasks
Before you begin
Verify the extension is working If so then there is no need to perform any post upgrade tasks
Procedure
Step 1 Try to reregister the extenstion If the extension still does not work then continue with the next stepsStep 2 Unregister the extension
Examplecomspringpathsysmgmtdomain-ltidgt
comspringpathsysmgmt
Use the mob browser httpsltvCenter IP or FQDNgtmob (content gt extensionManager path and InvokeUnregisterExtension method)
We recommend to remove the cluster before unregistering extensionsNote
Step 3 Re-register the Springpath plug-in using
Examplestcli cluster reregister
You can use stcli cluster reregister ndash-h for help and then continue with thereregistration
Note
Online Upgrade Process Workflow
If you are running HyperFlex release 35(1a) or later you can upgrade the Cisco HX Data Platform byperforming the auto-bootstrap process from the HX Connect UI (Auto Bootstrap Upgrade Process from HXConnect UI) However if you are running a HyperFlex release that is earlier than release 35(1a) you mustrun the manual bootstrap process to upgrade the Cisco HXData Platform (Manual Bootstrap Upgrade Process)
Attention
When using the online upgrade process workflow consider the following
bull First upgrade Cisco UCS infrastructure to the latest version and then use the automated upgrade workflowfor a combined upgrade of Cisco UCS firmware and Cisco HX Data Platform Online upgrade uses hostfirmware packages to upgrade all server endpoints
bull During online upgrade as one node is being upgraded (placed into maintenance mode) the number oftolerated node failures is reduced based on the Data Replication Factor and the Access Policy settings
See Entering Cisco HyperFlex Maintenance Mode for the procedures on how to access Cisco HyperFlexMaintenance Mode
bull If upgrading both HXDP and UCS firmware combined upgrade can be selected through HX Connectdepending on the length of the maintenance window
Upgrade Procedures5
Upgrade ProceduresOnline Upgrade Process Workflow
bull Do not use Firefox browser It is not supported due to an outdated version of flash that is bundled withthe browser
Cisco UCSManager infrastructure upgrade is only supported using AutoInstall and the direct server firmwareupgrade should be performed only through the upgrade orchestration framework provided by the HX DataPlatform Plug-in
Note
During the online upgrade process do not acknowledge server reboot pending activities from UCS ManagerDoing so will interrupt the upgrade process and can cause storage outage HyperFlex will automatically rebooteach node
Note
The following table summarizes the online upgrade workflow
ReferenceDescriptionStep
Downloading SoftwareIf UCSM (A-bundle) or UCS Server Firmware(C-bundle) upgrade is required download Cisco UCSInfrastructure A blade bundle B and rack bundle C
1
Test Upstream NetworkConnectivity
Ensure that the hx-storage-data and vMotion upstreamswitches are configured for full network failovercapability before proceeding forward Otherwise theHyperFlex Cluster becomes offline and all datastoresunmount from the ESXi hosts
2
Upgrading Cisco UCSInfrastructure Using Cisco UCSManager
Upgrade Cisco UCS Infrastructure bundle as required
It is important that you manually upgradethe UCS infrastructure first before initiatingthe upgrade sequence of the HyperFlexcomponents as outlined in RecommendedUpgrade Method on page 1 The upgradefeature of the HX Platform software willnot upgrade the UCS infrastructure bundleThis upgrade is a manual process
Note
3
Upgrade Procedures6
Upgrade ProceduresOnline Upgrade Process Workflow
ReferenceDescriptionStep
HX Release 35(1a) and later
bull Auto bootstrap is supportedbeginning with HX release35(1a) Auto BootstrapUpgrade Process from HXConnect UI
HX Release earlier than 35(1a)
bull Manual cluster bootstrap isrequired HX releases earlierthan 35(1a) ManualBootstrap Upgrade Process
Bootstrap to upgrade Cisco HX Data Platform4
Run the command stcli
snapshot-schedule --disableDisable snapshot schedule on the bootstrapped storagecontroller VM
It is enough to run this script on one of thecontroller nodes
Note
5
Log in to HX Connect with administrator credentials6
Upgrading Your HyperFlex ClusterUsing the HX Connect UI on page1
Start combined upgrade of
bull HX Data Platform and UCS Firmware
bull HX Data Platform and Hypervisor Software
7
Upgrading Cisco HyperFlex DataPlatform Using HX Connect
Upgrading Cisco UCS ServerFirmware Using the HX ConnectUI
Upgrading ESXi Using the HXConnect UI
To perform a split upgrade you mustupgrade HX Data Platform first After HXData Platform is upgraded to 35(1x) youcan perform a split upgrade of UCSM onlyandor ESXi only
When only UCS firmware is beingupgraded you may see the upgrade processpause at the validation screen after the fabricinterconnect discovery It may be a networkconnectivity failure issue however in mostcases it just requires waiting for the processto finish
Attention
Post Upgrade TasksConfirm that the upgrade task is complete8
Starting with 40(2a) releaseDynamic self-signed certificate aregenerated rather than staticcertificates
Dynamic certificate creation9
Run the command stcli
snapshot-schedule -ndashenableOn the same controller VM enable snapshot schedule10
Upgrade Procedures7
Upgrade ProceduresOnline Upgrade Process Workflow
Offline Upgrade Process WorkflowThe following table summarizes the offline upgrade workflow
ReferenceDescriptionStep
Downloading SoftwareIf UCSM (A-bundle) or UCSServer Firmware (C-bundle)upgrade is required downloadCisco UCS Infrastructure A bladebundle B and rack bundle C
1
Test Upstream NetworkConnectivity
Ensure that the hx-storage-data andvMotion upstream switches areconfigured for full network failovercapability before proceedingforward Otherwise the HyperFlexCluster becomes offline and alldatastores unmount from the ESXihosts
2
Upgrading Cisco UCSInfrastructure Using Cisco UCSManager
Upgrade Cisco UCS Infrastructurebundle as required
It is important that youmanually upgrade theUCS infrastructure firstbefore initiating theupgrade sequence of theHyperFlex componentsas outlined inRecommendedUpgradeMethod on page 1The upgrade feature ofthe HX Platformsoftware will notupgrade the UCSinfrastructure bundleThis upgrade is amanual process
Note
3
Upgrade Procedures8
Upgrade ProceduresOffline Upgrade Process Workflow
ReferenceDescriptionStep
Graceful Shutdown of a HXClusterLaunch the vSphere Web Clientand power down all user VMsresiding on HX servers and all userVMs running on HX datastoresThis includes VMs running oncompute-only nodes After theVMshave been shut down verify thehealth state of the cluster andperform a graceful shutdown
HyperFlex controllerVMs (stCtlVMs) mustremain powered on
Important
4
Modifying Host Firmware PackageUsing Cisco UCS Manager
Manually stage the correctfirmware version before starting theupgrade process
5
In vCenter right-click on each HXController VM (stCtlVM) andselect Power gt Shut Down GuestOS
Shutdown theHyperFlexControllerVMs (stCtlVMs)
6
In vCenter right-click on eachESXi host select MaintenanceMode gt Enter MaintenanceMode
Once the Controller VMs areshutdown place the ESXi hostsinto Maintenance Mode
7
Acknowledge the pending rebooton the servers that comprise yourHX cluster nodes including bothconverged nodes and compute-onlynodes connected to the clusterWait until all nodes are upgradedConfirm that correct firmwarepackages have been installed beforeproceeding
8
In vCenter right-click on eachESXi host select MaintenanceMode gtExit Maintenance Mode
Once the ESXi hosts have bootedtake them out of MaintenanceMode Now the controller VMshould come back online
9
Upgrade Procedures9
Upgrade ProceduresOffline Upgrade Process Workflow
ReferenceDescriptionStep
Manual Bootstrap Upgrade ProcessBootstrap to upgrade the Cisco HXData Platform Plug-in
Important bull Be sure to copy thebootstrap file to thecontroller VMtmp directory
bull Ensure that youconfirm the versionof the plug-in inthe vCenterAdministration gtClient Plug-Inspage
10
Run the command stcli
snapshot-schedule --disableDisable snapshot schedule on thebootstrapped storage controllerVM
It is enough to run thisscript on one of thecontroller nodes
Note
11
Upgrading Your HyperFlex ClusterUsing the HX Connect UI on page1
Offline Upgrade Using CLI onpage 11
From the same controller VMbegin the upgrade
12
Post Upgrade TasksConfirm that upgrade is complete13
Start Cluster and Power On VMs on page 12
After the upgrade is complete startthe cluster and power on VMs
14
Run the command stcli
snapshot-schedule -ndashenableOn the same controller VM enablesnapshot schedule
15
Offline Upgrade Guidelines
bull --ucsm-host and --ucsm-user parameters are required when you are upgrading from 17x to 18x Theseparameters must not be used when moving up from 18(1a)18(1b) to 20(1a) as we are not changingthe Cisco UCS server firmware version
Cisco recommends using HX Connect UI to upgrade HyperFlex clusters over CLI for ease of use andbetter reporting You can safely ignore Cluster Invalid State alerts in HX Connect
Important
Upgrade Procedures10
Upgrade ProceduresOffline Upgrade Guidelines
Before you proceed with either combined or split upgrade consider the following guidelines
bull The package name must match the file that you uploaded to the controller VM
bull Enter passwords when prompted
bull Nodes are upgraded with the new version of the Cisco HX Data Platform software and rebooted one ata time
bull Offline cluster upgrades with nested vCenter is not supported
Offline Upgrade Using CLI
If you need to perform a split upgrade you must upgrade HX Data Platform first After HX Data Platform isupgraded to Release 35(1x) you can perform a split upgrade of UCSM only andor ESXi only
Important
Combined Upgrade of Cisco HX Data Platform ESXi and Cisco UCS Firmware
M5 Servers
stcli cluster upgrade --components ucs-fw hxdp hypervisor --locationtmpltstorfs package nameESXi package namegt --ucsm-host ltIPFQDN of UCSMgt--ucsm-user ltUCSM Usergt --ucsm5-fw-version ltUCSM Firmware Versiongt
Example for M5 Servers
~ stcli cluster upgrade --components ucs-fw hxdp hypervisor --locationtmpstorfs-packages-351a-19712tgz--ucsm-host eng-fi16engstorvisorcom --ucsm-user admin --ucs5fw-version 31(2g)
M4 Servers
stcli cluster upgrade --components ucs-fw hxdp hypervisor --locationtmpltstorfs package name ESXi package namegt --ucsm-host ltIPFQDN of UCSMgt--ucsm-user ltUCSM Usergt --ucsfw-version ltUCSM Firmware Versiongt
Example for M4 Servers
~ stcli cluster upgrade --components ucs-fw hxdp hypervisor --locationtmpstorfs-packages-351a-19712tgz--ucsm-host eng-fi16engstorvisorcom --ucsm-user admin --ucsfw-version 31(2g)
Combined Upgrade of Cisco HX Data Platform and ESXi
M5 Servers
stcli cluster upgrade --components hxdphypervisor --location tmphxupgrade_bundletgz--hypervisor-bundle tmpesxiupgrade_bundlezip
Example for M5 Servers
~ stcli cluster upgrade --components hxdphypervisor --location tmphxupgrade_bundletgz--hypervisor-bundle tmpesxiupgrade_bundlezip
M4 Servers
stcli cluster upgrade --components hxdphypervisor --location tmphxupgrade_bundletgz--hypervisor-bundle tmpesxiupgrade_bundlezip
Example for M4 Servers
Upgrade Procedures11
Upgrade ProceduresOffline Upgrade Using CLI
~ stcli cluster upgrade --components hxdphypervisor --location tmphxupgrade_bundletgz--hypervisor-bundle tmpesxiupgrade_bundlezip
Combined Upgrade of Cisco HX Data Platform and Cisco UCS Firmware
M5 Servers
stcli cluster upgrade --components hxdpucs-fw --locationtmpltstorfs package namegt --vcenter-user ltvcusergt --ucsm-host ltIPFQDN of UCSMgt--ucsm-user ltUCSM Usergt --ucsm5-fw-version ltUCSM Firmware Versiongt
M4 Servers
stcli cluster upgrade --components hxdpucs-fw --locationtmpltstorfs package namegt --vcenter-user ltvcusergt --ucsm-host ltIPFQDN of UCSMgt--ucsm-user ltUCSM Usergt --ucsfw-version ltUCSM Firmware Versiongt
Example for M4 Servers
~ stcli cluster upgrade --components hxdpucs-fw --locationtmpstorfs-packages-181c-19712tgz --vcenter-user administratorvspherelocal--ucsm-host eng-fi16engstorvisorcom --ucsm-user admin --ucsfw-version 31(2b)
Start Cluster and Power On VMsAfter the upgrade is complete and the cluster has been upgraded log out and log back in to vCenter to seeupgrade changes
Procedure
Step 1 After the upgrade is complete start your clusterStep 2 Login to any controller VM through SSH
stcli cluster start
ExampleHyperFlex StorageController 18(1c)Last login Wed Sept 21 235423 2016 from pguo-devengstorvisorcomrootucs-stclivm - 384 -1~ stcli cluster upgrade-statusCluster upgrade succeeded Cluster version 18(1c)rootucs-stctlvm-384~ stcli cluster startwaiting for Cluster to start on nodes [ucs-383 ucs-384 ucs-385 ucs-386]
This will start the cluster and mount the HX datastores Wait for cluster to come online You will see thepromptStarted cluster on nodes [ucs-383 ucs-384 ucs-385 ucs-386]Cluster is onlinerootucs-stctlvm-384-1~
Step 3 Wait for cluster to become healthy before starting the VMs Run command
~ stcli clustr info| grep health
Example
rootSpringpathControllerZRVF040451~ stcli cluster info | grep healthhealthState healthy
Upgrade Procedures12
Upgrade ProceduresStart Cluster and Power On VMs
state healthystorage cluster is healthy
Step 4 After the cluster is healthy launch vSphere Web Client or Thick Client navigate to Hosts and Cluster gtDatacenter gt Cluster gt Right click select Powergt Power On to start the VMs
Upgrade Procedures13
Upgrade ProceduresStart Cluster and Power On VMs
Upgrade Procedures14
Upgrade ProceduresStart Cluster and Power On VMs
Essential InformationUI Element
Displays the ESXi version of the uploaded bundleBundle details field
vCenter Credentials
Essential InformationUI Element
Enter the vCenter ltadmingt usernameUser Name field
Enter the vCenter ltadmingt passwordAdmin Password field
Step 9 Click Upgrade to begin the cluster upgrade processStep 10 The Validation Screen on the Upgrade Progress page displays the progress of the checks performed Fix
validation errors if any Confirm that the upgrade is complete
When upgrade is in progress you may see an error message Websocket connection failed Automatic refreshdisabled You can either refresh the page or log out and log back in to clear the error message You can safelyignore this error message
During cluster upgrade if the orchestration node reboots or power cycles due to power issue the clusterupgrade will be stuck Once the node is up restart the cluster upgrade process after cleaning the cluster systemusing the following commandstcli cluster upgrade --components hxdp ndashclean
If the clean-up command fails restart the stMgr service on all control VMs (ctrlVM) by running the followingcommandrestart stMgr
Then clean the cluster system by rerunning the following commandstcli cluster upgrade --components hxdp ndashclean
Here is a sample coderootucs-stctlvm-385-1~ stcli cluster upgrade --clean --components hxdpForcefully cleaned up upgrade progressrootucs-stctlvm-385-1~ stcli cluster upgrade --statusNo active upgrade found Upgrade progress available after triggering an upgrade
Post vCenter Upgrade TasksIf the extension is not working and HyperFLex and vCenter are upgraded to compatible version perform thefollowing steps
If you have more than one HyperFlex cluster then you must first update all HX clusters to compatible HXversions for the corresponding vCenter versions prior to attempting to reregister Do not unregistercomspringpathsysmgmt unless all clusters are removed from the vCenter
Note
Upgrade Procedures4
Upgrade ProceduresPost vCenter Upgrade Tasks
Before you begin
Verify the extension is working If so then there is no need to perform any post upgrade tasks
Procedure
Step 1 Try to reregister the extenstion If the extension still does not work then continue with the next stepsStep 2 Unregister the extension
Examplecomspringpathsysmgmtdomain-ltidgt
comspringpathsysmgmt
Use the mob browser httpsltvCenter IP or FQDNgtmob (content gt extensionManager path and InvokeUnregisterExtension method)
We recommend to remove the cluster before unregistering extensionsNote
Step 3 Re-register the Springpath plug-in using
Examplestcli cluster reregister
You can use stcli cluster reregister ndash-h for help and then continue with thereregistration
Note
Online Upgrade Process Workflow
If you are running HyperFlex release 35(1a) or later you can upgrade the Cisco HX Data Platform byperforming the auto-bootstrap process from the HX Connect UI (Auto Bootstrap Upgrade Process from HXConnect UI) However if you are running a HyperFlex release that is earlier than release 35(1a) you mustrun the manual bootstrap process to upgrade the Cisco HXData Platform (Manual Bootstrap Upgrade Process)
Attention
When using the online upgrade process workflow consider the following
bull First upgrade Cisco UCS infrastructure to the latest version and then use the automated upgrade workflowfor a combined upgrade of Cisco UCS firmware and Cisco HX Data Platform Online upgrade uses hostfirmware packages to upgrade all server endpoints
bull During online upgrade as one node is being upgraded (placed into maintenance mode) the number oftolerated node failures is reduced based on the Data Replication Factor and the Access Policy settings
See Entering Cisco HyperFlex Maintenance Mode for the procedures on how to access Cisco HyperFlexMaintenance Mode
bull If upgrading both HXDP and UCS firmware combined upgrade can be selected through HX Connectdepending on the length of the maintenance window
Upgrade Procedures5
Upgrade ProceduresOnline Upgrade Process Workflow
bull Do not use Firefox browser It is not supported due to an outdated version of flash that is bundled withthe browser
Cisco UCSManager infrastructure upgrade is only supported using AutoInstall and the direct server firmwareupgrade should be performed only through the upgrade orchestration framework provided by the HX DataPlatform Plug-in
Note
During the online upgrade process do not acknowledge server reboot pending activities from UCS ManagerDoing so will interrupt the upgrade process and can cause storage outage HyperFlex will automatically rebooteach node
Note
The following table summarizes the online upgrade workflow
ReferenceDescriptionStep
Downloading SoftwareIf UCSM (A-bundle) or UCS Server Firmware(C-bundle) upgrade is required download Cisco UCSInfrastructure A blade bundle B and rack bundle C
1
Test Upstream NetworkConnectivity
Ensure that the hx-storage-data and vMotion upstreamswitches are configured for full network failovercapability before proceeding forward Otherwise theHyperFlex Cluster becomes offline and all datastoresunmount from the ESXi hosts
2
Upgrading Cisco UCSInfrastructure Using Cisco UCSManager
Upgrade Cisco UCS Infrastructure bundle as required
It is important that you manually upgradethe UCS infrastructure first before initiatingthe upgrade sequence of the HyperFlexcomponents as outlined in RecommendedUpgrade Method on page 1 The upgradefeature of the HX Platform software willnot upgrade the UCS infrastructure bundleThis upgrade is a manual process
Note
3
Upgrade Procedures6
Upgrade ProceduresOnline Upgrade Process Workflow
ReferenceDescriptionStep
HX Release 35(1a) and later
bull Auto bootstrap is supportedbeginning with HX release35(1a) Auto BootstrapUpgrade Process from HXConnect UI
HX Release earlier than 35(1a)
bull Manual cluster bootstrap isrequired HX releases earlierthan 35(1a) ManualBootstrap Upgrade Process
Bootstrap to upgrade Cisco HX Data Platform4
Run the command stcli
snapshot-schedule --disableDisable snapshot schedule on the bootstrapped storagecontroller VM
It is enough to run this script on one of thecontroller nodes
Note
5
Log in to HX Connect with administrator credentials6
Upgrading Your HyperFlex ClusterUsing the HX Connect UI on page1
Start combined upgrade of
bull HX Data Platform and UCS Firmware
bull HX Data Platform and Hypervisor Software
7
Upgrading Cisco HyperFlex DataPlatform Using HX Connect
Upgrading Cisco UCS ServerFirmware Using the HX ConnectUI
Upgrading ESXi Using the HXConnect UI
To perform a split upgrade you mustupgrade HX Data Platform first After HXData Platform is upgraded to 35(1x) youcan perform a split upgrade of UCSM onlyandor ESXi only
When only UCS firmware is beingupgraded you may see the upgrade processpause at the validation screen after the fabricinterconnect discovery It may be a networkconnectivity failure issue however in mostcases it just requires waiting for the processto finish
Attention
Post Upgrade TasksConfirm that the upgrade task is complete8
Starting with 40(2a) releaseDynamic self-signed certificate aregenerated rather than staticcertificates
Dynamic certificate creation9
Run the command stcli
snapshot-schedule -ndashenableOn the same controller VM enable snapshot schedule10
Upgrade Procedures7
Upgrade ProceduresOnline Upgrade Process Workflow
Offline Upgrade Process WorkflowThe following table summarizes the offline upgrade workflow
ReferenceDescriptionStep
Downloading SoftwareIf UCSM (A-bundle) or UCSServer Firmware (C-bundle)upgrade is required downloadCisco UCS Infrastructure A bladebundle B and rack bundle C
1
Test Upstream NetworkConnectivity
Ensure that the hx-storage-data andvMotion upstream switches areconfigured for full network failovercapability before proceedingforward Otherwise the HyperFlexCluster becomes offline and alldatastores unmount from the ESXihosts
2
Upgrading Cisco UCSInfrastructure Using Cisco UCSManager
Upgrade Cisco UCS Infrastructurebundle as required
It is important that youmanually upgrade theUCS infrastructure firstbefore initiating theupgrade sequence of theHyperFlex componentsas outlined inRecommendedUpgradeMethod on page 1The upgrade feature ofthe HX Platformsoftware will notupgrade the UCSinfrastructure bundleThis upgrade is amanual process
Note
3
Upgrade Procedures8
Upgrade ProceduresOffline Upgrade Process Workflow
ReferenceDescriptionStep
Graceful Shutdown of a HXClusterLaunch the vSphere Web Clientand power down all user VMsresiding on HX servers and all userVMs running on HX datastoresThis includes VMs running oncompute-only nodes After theVMshave been shut down verify thehealth state of the cluster andperform a graceful shutdown
HyperFlex controllerVMs (stCtlVMs) mustremain powered on
Important
4
Modifying Host Firmware PackageUsing Cisco UCS Manager
Manually stage the correctfirmware version before starting theupgrade process
5
In vCenter right-click on each HXController VM (stCtlVM) andselect Power gt Shut Down GuestOS
Shutdown theHyperFlexControllerVMs (stCtlVMs)
6
In vCenter right-click on eachESXi host select MaintenanceMode gt Enter MaintenanceMode
Once the Controller VMs areshutdown place the ESXi hostsinto Maintenance Mode
7
Acknowledge the pending rebooton the servers that comprise yourHX cluster nodes including bothconverged nodes and compute-onlynodes connected to the clusterWait until all nodes are upgradedConfirm that correct firmwarepackages have been installed beforeproceeding
8
In vCenter right-click on eachESXi host select MaintenanceMode gtExit Maintenance Mode
Once the ESXi hosts have bootedtake them out of MaintenanceMode Now the controller VMshould come back online
9
Upgrade Procedures9
Upgrade ProceduresOffline Upgrade Process Workflow
ReferenceDescriptionStep
Manual Bootstrap Upgrade ProcessBootstrap to upgrade the Cisco HXData Platform Plug-in
Important bull Be sure to copy thebootstrap file to thecontroller VMtmp directory
bull Ensure that youconfirm the versionof the plug-in inthe vCenterAdministration gtClient Plug-Inspage
10
Run the command stcli
snapshot-schedule --disableDisable snapshot schedule on thebootstrapped storage controllerVM
It is enough to run thisscript on one of thecontroller nodes
Note
11
Upgrading Your HyperFlex ClusterUsing the HX Connect UI on page1
Offline Upgrade Using CLI onpage 11
From the same controller VMbegin the upgrade
12
Post Upgrade TasksConfirm that upgrade is complete13
Start Cluster and Power On VMs on page 12
After the upgrade is complete startthe cluster and power on VMs
14
Run the command stcli
snapshot-schedule -ndashenableOn the same controller VM enablesnapshot schedule
15
Offline Upgrade Guidelines
bull --ucsm-host and --ucsm-user parameters are required when you are upgrading from 17x to 18x Theseparameters must not be used when moving up from 18(1a)18(1b) to 20(1a) as we are not changingthe Cisco UCS server firmware version
Cisco recommends using HX Connect UI to upgrade HyperFlex clusters over CLI for ease of use andbetter reporting You can safely ignore Cluster Invalid State alerts in HX Connect
Important
Upgrade Procedures10
Upgrade ProceduresOffline Upgrade Guidelines
Before you proceed with either combined or split upgrade consider the following guidelines
bull The package name must match the file that you uploaded to the controller VM
bull Enter passwords when prompted
bull Nodes are upgraded with the new version of the Cisco HX Data Platform software and rebooted one ata time
bull Offline cluster upgrades with nested vCenter is not supported
Offline Upgrade Using CLI
If you need to perform a split upgrade you must upgrade HX Data Platform first After HX Data Platform isupgraded to Release 35(1x) you can perform a split upgrade of UCSM only andor ESXi only
Important
Combined Upgrade of Cisco HX Data Platform ESXi and Cisco UCS Firmware
M5 Servers
stcli cluster upgrade --components ucs-fw hxdp hypervisor --locationtmpltstorfs package nameESXi package namegt --ucsm-host ltIPFQDN of UCSMgt--ucsm-user ltUCSM Usergt --ucsm5-fw-version ltUCSM Firmware Versiongt
Example for M5 Servers
~ stcli cluster upgrade --components ucs-fw hxdp hypervisor --locationtmpstorfs-packages-351a-19712tgz--ucsm-host eng-fi16engstorvisorcom --ucsm-user admin --ucs5fw-version 31(2g)
M4 Servers
stcli cluster upgrade --components ucs-fw hxdp hypervisor --locationtmpltstorfs package name ESXi package namegt --ucsm-host ltIPFQDN of UCSMgt--ucsm-user ltUCSM Usergt --ucsfw-version ltUCSM Firmware Versiongt
Example for M4 Servers
~ stcli cluster upgrade --components ucs-fw hxdp hypervisor --locationtmpstorfs-packages-351a-19712tgz--ucsm-host eng-fi16engstorvisorcom --ucsm-user admin --ucsfw-version 31(2g)
Combined Upgrade of Cisco HX Data Platform and ESXi
M5 Servers
stcli cluster upgrade --components hxdphypervisor --location tmphxupgrade_bundletgz--hypervisor-bundle tmpesxiupgrade_bundlezip
Example for M5 Servers
~ stcli cluster upgrade --components hxdphypervisor --location tmphxupgrade_bundletgz--hypervisor-bundle tmpesxiupgrade_bundlezip
M4 Servers
stcli cluster upgrade --components hxdphypervisor --location tmphxupgrade_bundletgz--hypervisor-bundle tmpesxiupgrade_bundlezip
Example for M4 Servers
Upgrade Procedures11
Upgrade ProceduresOffline Upgrade Using CLI
~ stcli cluster upgrade --components hxdphypervisor --location tmphxupgrade_bundletgz--hypervisor-bundle tmpesxiupgrade_bundlezip
Combined Upgrade of Cisco HX Data Platform and Cisco UCS Firmware
M5 Servers
stcli cluster upgrade --components hxdpucs-fw --locationtmpltstorfs package namegt --vcenter-user ltvcusergt --ucsm-host ltIPFQDN of UCSMgt--ucsm-user ltUCSM Usergt --ucsm5-fw-version ltUCSM Firmware Versiongt
M4 Servers
stcli cluster upgrade --components hxdpucs-fw --locationtmpltstorfs package namegt --vcenter-user ltvcusergt --ucsm-host ltIPFQDN of UCSMgt--ucsm-user ltUCSM Usergt --ucsfw-version ltUCSM Firmware Versiongt
Example for M4 Servers
~ stcli cluster upgrade --components hxdpucs-fw --locationtmpstorfs-packages-181c-19712tgz --vcenter-user administratorvspherelocal--ucsm-host eng-fi16engstorvisorcom --ucsm-user admin --ucsfw-version 31(2b)
Start Cluster and Power On VMsAfter the upgrade is complete and the cluster has been upgraded log out and log back in to vCenter to seeupgrade changes
Procedure
Step 1 After the upgrade is complete start your clusterStep 2 Login to any controller VM through SSH
stcli cluster start
ExampleHyperFlex StorageController 18(1c)Last login Wed Sept 21 235423 2016 from pguo-devengstorvisorcomrootucs-stclivm - 384 -1~ stcli cluster upgrade-statusCluster upgrade succeeded Cluster version 18(1c)rootucs-stctlvm-384~ stcli cluster startwaiting for Cluster to start on nodes [ucs-383 ucs-384 ucs-385 ucs-386]
This will start the cluster and mount the HX datastores Wait for cluster to come online You will see thepromptStarted cluster on nodes [ucs-383 ucs-384 ucs-385 ucs-386]Cluster is onlinerootucs-stctlvm-384-1~
Step 3 Wait for cluster to become healthy before starting the VMs Run command
~ stcli clustr info| grep health
Example
rootSpringpathControllerZRVF040451~ stcli cluster info | grep healthhealthState healthy
Upgrade Procedures12
Upgrade ProceduresStart Cluster and Power On VMs
state healthystorage cluster is healthy
Step 4 After the cluster is healthy launch vSphere Web Client or Thick Client navigate to Hosts and Cluster gtDatacenter gt Cluster gt Right click select Powergt Power On to start the VMs
Upgrade Procedures13
Upgrade ProceduresStart Cluster and Power On VMs
Upgrade Procedures14
Upgrade ProceduresStart Cluster and Power On VMs
Before you begin
Verify the extension is working If so then there is no need to perform any post upgrade tasks
Procedure
Step 1 Try to reregister the extenstion If the extension still does not work then continue with the next stepsStep 2 Unregister the extension
Examplecomspringpathsysmgmtdomain-ltidgt
comspringpathsysmgmt
Use the mob browser httpsltvCenter IP or FQDNgtmob (content gt extensionManager path and InvokeUnregisterExtension method)
We recommend to remove the cluster before unregistering extensionsNote
Step 3 Re-register the Springpath plug-in using
Examplestcli cluster reregister
You can use stcli cluster reregister ndash-h for help and then continue with thereregistration
Note
Online Upgrade Process Workflow
If you are running HyperFlex release 35(1a) or later you can upgrade the Cisco HX Data Platform byperforming the auto-bootstrap process from the HX Connect UI (Auto Bootstrap Upgrade Process from HXConnect UI) However if you are running a HyperFlex release that is earlier than release 35(1a) you mustrun the manual bootstrap process to upgrade the Cisco HXData Platform (Manual Bootstrap Upgrade Process)
Attention
When using the online upgrade process workflow consider the following
bull First upgrade Cisco UCS infrastructure to the latest version and then use the automated upgrade workflowfor a combined upgrade of Cisco UCS firmware and Cisco HX Data Platform Online upgrade uses hostfirmware packages to upgrade all server endpoints
bull During online upgrade as one node is being upgraded (placed into maintenance mode) the number oftolerated node failures is reduced based on the Data Replication Factor and the Access Policy settings
See Entering Cisco HyperFlex Maintenance Mode for the procedures on how to access Cisco HyperFlexMaintenance Mode
bull If upgrading both HXDP and UCS firmware combined upgrade can be selected through HX Connectdepending on the length of the maintenance window
Upgrade Procedures5
Upgrade ProceduresOnline Upgrade Process Workflow
bull Do not use Firefox browser It is not supported due to an outdated version of flash that is bundled withthe browser
Cisco UCSManager infrastructure upgrade is only supported using AutoInstall and the direct server firmwareupgrade should be performed only through the upgrade orchestration framework provided by the HX DataPlatform Plug-in
Note
During the online upgrade process do not acknowledge server reboot pending activities from UCS ManagerDoing so will interrupt the upgrade process and can cause storage outage HyperFlex will automatically rebooteach node
Note
The following table summarizes the online upgrade workflow
ReferenceDescriptionStep
Downloading SoftwareIf UCSM (A-bundle) or UCS Server Firmware(C-bundle) upgrade is required download Cisco UCSInfrastructure A blade bundle B and rack bundle C
1
Test Upstream NetworkConnectivity
Ensure that the hx-storage-data and vMotion upstreamswitches are configured for full network failovercapability before proceeding forward Otherwise theHyperFlex Cluster becomes offline and all datastoresunmount from the ESXi hosts
2
Upgrading Cisco UCSInfrastructure Using Cisco UCSManager
Upgrade Cisco UCS Infrastructure bundle as required
It is important that you manually upgradethe UCS infrastructure first before initiatingthe upgrade sequence of the HyperFlexcomponents as outlined in RecommendedUpgrade Method on page 1 The upgradefeature of the HX Platform software willnot upgrade the UCS infrastructure bundleThis upgrade is a manual process
Note
3
Upgrade Procedures6
Upgrade ProceduresOnline Upgrade Process Workflow
ReferenceDescriptionStep
HX Release 35(1a) and later
bull Auto bootstrap is supportedbeginning with HX release35(1a) Auto BootstrapUpgrade Process from HXConnect UI
HX Release earlier than 35(1a)
bull Manual cluster bootstrap isrequired HX releases earlierthan 35(1a) ManualBootstrap Upgrade Process
Bootstrap to upgrade Cisco HX Data Platform4
Run the command stcli
snapshot-schedule --disableDisable snapshot schedule on the bootstrapped storagecontroller VM
It is enough to run this script on one of thecontroller nodes
Note
5
Log in to HX Connect with administrator credentials6
Upgrading Your HyperFlex ClusterUsing the HX Connect UI on page1
Start combined upgrade of
bull HX Data Platform and UCS Firmware
bull HX Data Platform and Hypervisor Software
7
Upgrading Cisco HyperFlex DataPlatform Using HX Connect
Upgrading Cisco UCS ServerFirmware Using the HX ConnectUI
Upgrading ESXi Using the HXConnect UI
To perform a split upgrade you mustupgrade HX Data Platform first After HXData Platform is upgraded to 35(1x) youcan perform a split upgrade of UCSM onlyandor ESXi only
When only UCS firmware is beingupgraded you may see the upgrade processpause at the validation screen after the fabricinterconnect discovery It may be a networkconnectivity failure issue however in mostcases it just requires waiting for the processto finish
Attention
Post Upgrade TasksConfirm that the upgrade task is complete8
Starting with 40(2a) releaseDynamic self-signed certificate aregenerated rather than staticcertificates
Dynamic certificate creation9
Run the command stcli
snapshot-schedule -ndashenableOn the same controller VM enable snapshot schedule10
Upgrade Procedures7
Upgrade ProceduresOnline Upgrade Process Workflow
Offline Upgrade Process WorkflowThe following table summarizes the offline upgrade workflow
ReferenceDescriptionStep
Downloading SoftwareIf UCSM (A-bundle) or UCSServer Firmware (C-bundle)upgrade is required downloadCisco UCS Infrastructure A bladebundle B and rack bundle C
1
Test Upstream NetworkConnectivity
Ensure that the hx-storage-data andvMotion upstream switches areconfigured for full network failovercapability before proceedingforward Otherwise the HyperFlexCluster becomes offline and alldatastores unmount from the ESXihosts
2
Upgrading Cisco UCSInfrastructure Using Cisco UCSManager
Upgrade Cisco UCS Infrastructurebundle as required
It is important that youmanually upgrade theUCS infrastructure firstbefore initiating theupgrade sequence of theHyperFlex componentsas outlined inRecommendedUpgradeMethod on page 1The upgrade feature ofthe HX Platformsoftware will notupgrade the UCSinfrastructure bundleThis upgrade is amanual process
Note
3
Upgrade Procedures8
Upgrade ProceduresOffline Upgrade Process Workflow
ReferenceDescriptionStep
Graceful Shutdown of a HXClusterLaunch the vSphere Web Clientand power down all user VMsresiding on HX servers and all userVMs running on HX datastoresThis includes VMs running oncompute-only nodes After theVMshave been shut down verify thehealth state of the cluster andperform a graceful shutdown
HyperFlex controllerVMs (stCtlVMs) mustremain powered on
Important
4
Modifying Host Firmware PackageUsing Cisco UCS Manager
Manually stage the correctfirmware version before starting theupgrade process
5
In vCenter right-click on each HXController VM (stCtlVM) andselect Power gt Shut Down GuestOS
Shutdown theHyperFlexControllerVMs (stCtlVMs)
6
In vCenter right-click on eachESXi host select MaintenanceMode gt Enter MaintenanceMode
Once the Controller VMs areshutdown place the ESXi hostsinto Maintenance Mode
7
Acknowledge the pending rebooton the servers that comprise yourHX cluster nodes including bothconverged nodes and compute-onlynodes connected to the clusterWait until all nodes are upgradedConfirm that correct firmwarepackages have been installed beforeproceeding
8
In vCenter right-click on eachESXi host select MaintenanceMode gtExit Maintenance Mode
Once the ESXi hosts have bootedtake them out of MaintenanceMode Now the controller VMshould come back online
9
Upgrade Procedures9
Upgrade ProceduresOffline Upgrade Process Workflow
ReferenceDescriptionStep
Manual Bootstrap Upgrade ProcessBootstrap to upgrade the Cisco HXData Platform Plug-in
Important bull Be sure to copy thebootstrap file to thecontroller VMtmp directory
bull Ensure that youconfirm the versionof the plug-in inthe vCenterAdministration gtClient Plug-Inspage
10
Run the command stcli
snapshot-schedule --disableDisable snapshot schedule on thebootstrapped storage controllerVM
It is enough to run thisscript on one of thecontroller nodes
Note
11
Upgrading Your HyperFlex ClusterUsing the HX Connect UI on page1
Offline Upgrade Using CLI onpage 11
From the same controller VMbegin the upgrade
12
Post Upgrade TasksConfirm that upgrade is complete13
Start Cluster and Power On VMs on page 12
After the upgrade is complete startthe cluster and power on VMs
14
Run the command stcli
snapshot-schedule -ndashenableOn the same controller VM enablesnapshot schedule
15
Offline Upgrade Guidelines
bull --ucsm-host and --ucsm-user parameters are required when you are upgrading from 17x to 18x Theseparameters must not be used when moving up from 18(1a)18(1b) to 20(1a) as we are not changingthe Cisco UCS server firmware version
Cisco recommends using HX Connect UI to upgrade HyperFlex clusters over CLI for ease of use andbetter reporting You can safely ignore Cluster Invalid State alerts in HX Connect
Important
Upgrade Procedures10
Upgrade ProceduresOffline Upgrade Guidelines
Before you proceed with either combined or split upgrade consider the following guidelines
bull The package name must match the file that you uploaded to the controller VM
bull Enter passwords when prompted
bull Nodes are upgraded with the new version of the Cisco HX Data Platform software and rebooted one ata time
bull Offline cluster upgrades with nested vCenter is not supported
Offline Upgrade Using CLI
If you need to perform a split upgrade you must upgrade HX Data Platform first After HX Data Platform isupgraded to Release 35(1x) you can perform a split upgrade of UCSM only andor ESXi only
Important
Combined Upgrade of Cisco HX Data Platform ESXi and Cisco UCS Firmware
M5 Servers
stcli cluster upgrade --components ucs-fw hxdp hypervisor --locationtmpltstorfs package nameESXi package namegt --ucsm-host ltIPFQDN of UCSMgt--ucsm-user ltUCSM Usergt --ucsm5-fw-version ltUCSM Firmware Versiongt
Example for M5 Servers
~ stcli cluster upgrade --components ucs-fw hxdp hypervisor --locationtmpstorfs-packages-351a-19712tgz--ucsm-host eng-fi16engstorvisorcom --ucsm-user admin --ucs5fw-version 31(2g)
M4 Servers
stcli cluster upgrade --components ucs-fw hxdp hypervisor --locationtmpltstorfs package name ESXi package namegt --ucsm-host ltIPFQDN of UCSMgt--ucsm-user ltUCSM Usergt --ucsfw-version ltUCSM Firmware Versiongt
Example for M4 Servers
~ stcli cluster upgrade --components ucs-fw hxdp hypervisor --locationtmpstorfs-packages-351a-19712tgz--ucsm-host eng-fi16engstorvisorcom --ucsm-user admin --ucsfw-version 31(2g)
Combined Upgrade of Cisco HX Data Platform and ESXi
M5 Servers
stcli cluster upgrade --components hxdphypervisor --location tmphxupgrade_bundletgz--hypervisor-bundle tmpesxiupgrade_bundlezip
Example for M5 Servers
~ stcli cluster upgrade --components hxdphypervisor --location tmphxupgrade_bundletgz--hypervisor-bundle tmpesxiupgrade_bundlezip
M4 Servers
stcli cluster upgrade --components hxdphypervisor --location tmphxupgrade_bundletgz--hypervisor-bundle tmpesxiupgrade_bundlezip
Example for M4 Servers
Upgrade Procedures11
Upgrade ProceduresOffline Upgrade Using CLI
~ stcli cluster upgrade --components hxdphypervisor --location tmphxupgrade_bundletgz--hypervisor-bundle tmpesxiupgrade_bundlezip
Combined Upgrade of Cisco HX Data Platform and Cisco UCS Firmware
M5 Servers
stcli cluster upgrade --components hxdpucs-fw --locationtmpltstorfs package namegt --vcenter-user ltvcusergt --ucsm-host ltIPFQDN of UCSMgt--ucsm-user ltUCSM Usergt --ucsm5-fw-version ltUCSM Firmware Versiongt
M4 Servers
stcli cluster upgrade --components hxdpucs-fw --locationtmpltstorfs package namegt --vcenter-user ltvcusergt --ucsm-host ltIPFQDN of UCSMgt--ucsm-user ltUCSM Usergt --ucsfw-version ltUCSM Firmware Versiongt
Example for M4 Servers
~ stcli cluster upgrade --components hxdpucs-fw --locationtmpstorfs-packages-181c-19712tgz --vcenter-user administratorvspherelocal--ucsm-host eng-fi16engstorvisorcom --ucsm-user admin --ucsfw-version 31(2b)
Start Cluster and Power On VMsAfter the upgrade is complete and the cluster has been upgraded log out and log back in to vCenter to seeupgrade changes
Procedure
Step 1 After the upgrade is complete start your clusterStep 2 Login to any controller VM through SSH
stcli cluster start
ExampleHyperFlex StorageController 18(1c)Last login Wed Sept 21 235423 2016 from pguo-devengstorvisorcomrootucs-stclivm - 384 -1~ stcli cluster upgrade-statusCluster upgrade succeeded Cluster version 18(1c)rootucs-stctlvm-384~ stcli cluster startwaiting for Cluster to start on nodes [ucs-383 ucs-384 ucs-385 ucs-386]
This will start the cluster and mount the HX datastores Wait for cluster to come online You will see thepromptStarted cluster on nodes [ucs-383 ucs-384 ucs-385 ucs-386]Cluster is onlinerootucs-stctlvm-384-1~
Step 3 Wait for cluster to become healthy before starting the VMs Run command
~ stcli clustr info| grep health
Example
rootSpringpathControllerZRVF040451~ stcli cluster info | grep healthhealthState healthy
Upgrade Procedures12
Upgrade ProceduresStart Cluster and Power On VMs
state healthystorage cluster is healthy
Step 4 After the cluster is healthy launch vSphere Web Client or Thick Client navigate to Hosts and Cluster gtDatacenter gt Cluster gt Right click select Powergt Power On to start the VMs
Upgrade Procedures13
Upgrade ProceduresStart Cluster and Power On VMs
Upgrade Procedures14
Upgrade ProceduresStart Cluster and Power On VMs
bull Do not use Firefox browser It is not supported due to an outdated version of flash that is bundled withthe browser
Cisco UCSManager infrastructure upgrade is only supported using AutoInstall and the direct server firmwareupgrade should be performed only through the upgrade orchestration framework provided by the HX DataPlatform Plug-in
Note
During the online upgrade process do not acknowledge server reboot pending activities from UCS ManagerDoing so will interrupt the upgrade process and can cause storage outage HyperFlex will automatically rebooteach node
Note
The following table summarizes the online upgrade workflow
ReferenceDescriptionStep
Downloading SoftwareIf UCSM (A-bundle) or UCS Server Firmware(C-bundle) upgrade is required download Cisco UCSInfrastructure A blade bundle B and rack bundle C
1
Test Upstream NetworkConnectivity
Ensure that the hx-storage-data and vMotion upstreamswitches are configured for full network failovercapability before proceeding forward Otherwise theHyperFlex Cluster becomes offline and all datastoresunmount from the ESXi hosts
2
Upgrading Cisco UCSInfrastructure Using Cisco UCSManager
Upgrade Cisco UCS Infrastructure bundle as required
It is important that you manually upgradethe UCS infrastructure first before initiatingthe upgrade sequence of the HyperFlexcomponents as outlined in RecommendedUpgrade Method on page 1 The upgradefeature of the HX Platform software willnot upgrade the UCS infrastructure bundleThis upgrade is a manual process
Note
3
Upgrade Procedures6
Upgrade ProceduresOnline Upgrade Process Workflow
ReferenceDescriptionStep
HX Release 35(1a) and later
bull Auto bootstrap is supportedbeginning with HX release35(1a) Auto BootstrapUpgrade Process from HXConnect UI
HX Release earlier than 35(1a)
bull Manual cluster bootstrap isrequired HX releases earlierthan 35(1a) ManualBootstrap Upgrade Process
Bootstrap to upgrade Cisco HX Data Platform4
Run the command stcli
snapshot-schedule --disableDisable snapshot schedule on the bootstrapped storagecontroller VM
It is enough to run this script on one of thecontroller nodes
Note
5
Log in to HX Connect with administrator credentials6
Upgrading Your HyperFlex ClusterUsing the HX Connect UI on page1
Start combined upgrade of
bull HX Data Platform and UCS Firmware
bull HX Data Platform and Hypervisor Software
7
Upgrading Cisco HyperFlex DataPlatform Using HX Connect
Upgrading Cisco UCS ServerFirmware Using the HX ConnectUI
Upgrading ESXi Using the HXConnect UI
To perform a split upgrade you mustupgrade HX Data Platform first After HXData Platform is upgraded to 35(1x) youcan perform a split upgrade of UCSM onlyandor ESXi only
When only UCS firmware is beingupgraded you may see the upgrade processpause at the validation screen after the fabricinterconnect discovery It may be a networkconnectivity failure issue however in mostcases it just requires waiting for the processto finish
Attention
Post Upgrade TasksConfirm that the upgrade task is complete8
Starting with 40(2a) releaseDynamic self-signed certificate aregenerated rather than staticcertificates
Dynamic certificate creation9
Run the command stcli
snapshot-schedule -ndashenableOn the same controller VM enable snapshot schedule10
Upgrade Procedures7
Upgrade ProceduresOnline Upgrade Process Workflow
Offline Upgrade Process WorkflowThe following table summarizes the offline upgrade workflow
ReferenceDescriptionStep
Downloading SoftwareIf UCSM (A-bundle) or UCSServer Firmware (C-bundle)upgrade is required downloadCisco UCS Infrastructure A bladebundle B and rack bundle C
1
Test Upstream NetworkConnectivity
Ensure that the hx-storage-data andvMotion upstream switches areconfigured for full network failovercapability before proceedingforward Otherwise the HyperFlexCluster becomes offline and alldatastores unmount from the ESXihosts
2
Upgrading Cisco UCSInfrastructure Using Cisco UCSManager
Upgrade Cisco UCS Infrastructurebundle as required
It is important that youmanually upgrade theUCS infrastructure firstbefore initiating theupgrade sequence of theHyperFlex componentsas outlined inRecommendedUpgradeMethod on page 1The upgrade feature ofthe HX Platformsoftware will notupgrade the UCSinfrastructure bundleThis upgrade is amanual process
Note
3
Upgrade Procedures8
Upgrade ProceduresOffline Upgrade Process Workflow
ReferenceDescriptionStep
Graceful Shutdown of a HXClusterLaunch the vSphere Web Clientand power down all user VMsresiding on HX servers and all userVMs running on HX datastoresThis includes VMs running oncompute-only nodes After theVMshave been shut down verify thehealth state of the cluster andperform a graceful shutdown
HyperFlex controllerVMs (stCtlVMs) mustremain powered on
Important
4
Modifying Host Firmware PackageUsing Cisco UCS Manager
Manually stage the correctfirmware version before starting theupgrade process
5
In vCenter right-click on each HXController VM (stCtlVM) andselect Power gt Shut Down GuestOS
Shutdown theHyperFlexControllerVMs (stCtlVMs)
6
In vCenter right-click on eachESXi host select MaintenanceMode gt Enter MaintenanceMode
Once the Controller VMs areshutdown place the ESXi hostsinto Maintenance Mode
7
Acknowledge the pending rebooton the servers that comprise yourHX cluster nodes including bothconverged nodes and compute-onlynodes connected to the clusterWait until all nodes are upgradedConfirm that correct firmwarepackages have been installed beforeproceeding
8
In vCenter right-click on eachESXi host select MaintenanceMode gtExit Maintenance Mode
Once the ESXi hosts have bootedtake them out of MaintenanceMode Now the controller VMshould come back online
9
Upgrade Procedures9
Upgrade ProceduresOffline Upgrade Process Workflow
ReferenceDescriptionStep
Manual Bootstrap Upgrade ProcessBootstrap to upgrade the Cisco HXData Platform Plug-in
Important bull Be sure to copy thebootstrap file to thecontroller VMtmp directory
bull Ensure that youconfirm the versionof the plug-in inthe vCenterAdministration gtClient Plug-Inspage
10
Run the command stcli
snapshot-schedule --disableDisable snapshot schedule on thebootstrapped storage controllerVM
It is enough to run thisscript on one of thecontroller nodes
Note
11
Upgrading Your HyperFlex ClusterUsing the HX Connect UI on page1
Offline Upgrade Using CLI onpage 11
From the same controller VMbegin the upgrade
12
Post Upgrade TasksConfirm that upgrade is complete13
Start Cluster and Power On VMs on page 12
After the upgrade is complete startthe cluster and power on VMs
14
Run the command stcli
snapshot-schedule -ndashenableOn the same controller VM enablesnapshot schedule
15
Offline Upgrade Guidelines
bull --ucsm-host and --ucsm-user parameters are required when you are upgrading from 17x to 18x Theseparameters must not be used when moving up from 18(1a)18(1b) to 20(1a) as we are not changingthe Cisco UCS server firmware version
Cisco recommends using HX Connect UI to upgrade HyperFlex clusters over CLI for ease of use andbetter reporting You can safely ignore Cluster Invalid State alerts in HX Connect
Important
Upgrade Procedures10
Upgrade ProceduresOffline Upgrade Guidelines
Before you proceed with either combined or split upgrade consider the following guidelines
bull The package name must match the file that you uploaded to the controller VM
bull Enter passwords when prompted
bull Nodes are upgraded with the new version of the Cisco HX Data Platform software and rebooted one ata time
bull Offline cluster upgrades with nested vCenter is not supported
Offline Upgrade Using CLI
If you need to perform a split upgrade you must upgrade HX Data Platform first After HX Data Platform isupgraded to Release 35(1x) you can perform a split upgrade of UCSM only andor ESXi only
Important
Combined Upgrade of Cisco HX Data Platform ESXi and Cisco UCS Firmware
M5 Servers
stcli cluster upgrade --components ucs-fw hxdp hypervisor --locationtmpltstorfs package nameESXi package namegt --ucsm-host ltIPFQDN of UCSMgt--ucsm-user ltUCSM Usergt --ucsm5-fw-version ltUCSM Firmware Versiongt
Example for M5 Servers
~ stcli cluster upgrade --components ucs-fw hxdp hypervisor --locationtmpstorfs-packages-351a-19712tgz--ucsm-host eng-fi16engstorvisorcom --ucsm-user admin --ucs5fw-version 31(2g)
M4 Servers
stcli cluster upgrade --components ucs-fw hxdp hypervisor --locationtmpltstorfs package name ESXi package namegt --ucsm-host ltIPFQDN of UCSMgt--ucsm-user ltUCSM Usergt --ucsfw-version ltUCSM Firmware Versiongt
Example for M4 Servers
~ stcli cluster upgrade --components ucs-fw hxdp hypervisor --locationtmpstorfs-packages-351a-19712tgz--ucsm-host eng-fi16engstorvisorcom --ucsm-user admin --ucsfw-version 31(2g)
Combined Upgrade of Cisco HX Data Platform and ESXi
M5 Servers
stcli cluster upgrade --components hxdphypervisor --location tmphxupgrade_bundletgz--hypervisor-bundle tmpesxiupgrade_bundlezip
Example for M5 Servers
~ stcli cluster upgrade --components hxdphypervisor --location tmphxupgrade_bundletgz--hypervisor-bundle tmpesxiupgrade_bundlezip
M4 Servers
stcli cluster upgrade --components hxdphypervisor --location tmphxupgrade_bundletgz--hypervisor-bundle tmpesxiupgrade_bundlezip
Example for M4 Servers
Upgrade Procedures11
Upgrade ProceduresOffline Upgrade Using CLI
~ stcli cluster upgrade --components hxdphypervisor --location tmphxupgrade_bundletgz--hypervisor-bundle tmpesxiupgrade_bundlezip
Combined Upgrade of Cisco HX Data Platform and Cisco UCS Firmware
M5 Servers
stcli cluster upgrade --components hxdpucs-fw --locationtmpltstorfs package namegt --vcenter-user ltvcusergt --ucsm-host ltIPFQDN of UCSMgt--ucsm-user ltUCSM Usergt --ucsm5-fw-version ltUCSM Firmware Versiongt
M4 Servers
stcli cluster upgrade --components hxdpucs-fw --locationtmpltstorfs package namegt --vcenter-user ltvcusergt --ucsm-host ltIPFQDN of UCSMgt--ucsm-user ltUCSM Usergt --ucsfw-version ltUCSM Firmware Versiongt
Example for M4 Servers
~ stcli cluster upgrade --components hxdpucs-fw --locationtmpstorfs-packages-181c-19712tgz --vcenter-user administratorvspherelocal--ucsm-host eng-fi16engstorvisorcom --ucsm-user admin --ucsfw-version 31(2b)
Start Cluster and Power On VMsAfter the upgrade is complete and the cluster has been upgraded log out and log back in to vCenter to seeupgrade changes
Procedure
Step 1 After the upgrade is complete start your clusterStep 2 Login to any controller VM through SSH
stcli cluster start
ExampleHyperFlex StorageController 18(1c)Last login Wed Sept 21 235423 2016 from pguo-devengstorvisorcomrootucs-stclivm - 384 -1~ stcli cluster upgrade-statusCluster upgrade succeeded Cluster version 18(1c)rootucs-stctlvm-384~ stcli cluster startwaiting for Cluster to start on nodes [ucs-383 ucs-384 ucs-385 ucs-386]
This will start the cluster and mount the HX datastores Wait for cluster to come online You will see thepromptStarted cluster on nodes [ucs-383 ucs-384 ucs-385 ucs-386]Cluster is onlinerootucs-stctlvm-384-1~
Step 3 Wait for cluster to become healthy before starting the VMs Run command
~ stcli clustr info| grep health
Example
rootSpringpathControllerZRVF040451~ stcli cluster info | grep healthhealthState healthy
Upgrade Procedures12
Upgrade ProceduresStart Cluster and Power On VMs
state healthystorage cluster is healthy
Step 4 After the cluster is healthy launch vSphere Web Client or Thick Client navigate to Hosts and Cluster gtDatacenter gt Cluster gt Right click select Powergt Power On to start the VMs
Upgrade Procedures13
Upgrade ProceduresStart Cluster and Power On VMs
Upgrade Procedures14
Upgrade ProceduresStart Cluster and Power On VMs
ReferenceDescriptionStep
HX Release 35(1a) and later
bull Auto bootstrap is supportedbeginning with HX release35(1a) Auto BootstrapUpgrade Process from HXConnect UI
HX Release earlier than 35(1a)
bull Manual cluster bootstrap isrequired HX releases earlierthan 35(1a) ManualBootstrap Upgrade Process
Bootstrap to upgrade Cisco HX Data Platform4
Run the command stcli
snapshot-schedule --disableDisable snapshot schedule on the bootstrapped storagecontroller VM
It is enough to run this script on one of thecontroller nodes
Note
5
Log in to HX Connect with administrator credentials6
Upgrading Your HyperFlex ClusterUsing the HX Connect UI on page1
Start combined upgrade of
bull HX Data Platform and UCS Firmware
bull HX Data Platform and Hypervisor Software
7
Upgrading Cisco HyperFlex DataPlatform Using HX Connect
Upgrading Cisco UCS ServerFirmware Using the HX ConnectUI
Upgrading ESXi Using the HXConnect UI
To perform a split upgrade you mustupgrade HX Data Platform first After HXData Platform is upgraded to 35(1x) youcan perform a split upgrade of UCSM onlyandor ESXi only
When only UCS firmware is beingupgraded you may see the upgrade processpause at the validation screen after the fabricinterconnect discovery It may be a networkconnectivity failure issue however in mostcases it just requires waiting for the processto finish
Attention
Post Upgrade TasksConfirm that the upgrade task is complete8
Starting with 40(2a) releaseDynamic self-signed certificate aregenerated rather than staticcertificates
Dynamic certificate creation9
Run the command stcli
snapshot-schedule -ndashenableOn the same controller VM enable snapshot schedule10
Upgrade Procedures7
Upgrade ProceduresOnline Upgrade Process Workflow
Offline Upgrade Process WorkflowThe following table summarizes the offline upgrade workflow
ReferenceDescriptionStep
Downloading SoftwareIf UCSM (A-bundle) or UCSServer Firmware (C-bundle)upgrade is required downloadCisco UCS Infrastructure A bladebundle B and rack bundle C
1
Test Upstream NetworkConnectivity
Ensure that the hx-storage-data andvMotion upstream switches areconfigured for full network failovercapability before proceedingforward Otherwise the HyperFlexCluster becomes offline and alldatastores unmount from the ESXihosts
2
Upgrading Cisco UCSInfrastructure Using Cisco UCSManager
Upgrade Cisco UCS Infrastructurebundle as required
It is important that youmanually upgrade theUCS infrastructure firstbefore initiating theupgrade sequence of theHyperFlex componentsas outlined inRecommendedUpgradeMethod on page 1The upgrade feature ofthe HX Platformsoftware will notupgrade the UCSinfrastructure bundleThis upgrade is amanual process
Note
3
Upgrade Procedures8
Upgrade ProceduresOffline Upgrade Process Workflow
ReferenceDescriptionStep
Graceful Shutdown of a HXClusterLaunch the vSphere Web Clientand power down all user VMsresiding on HX servers and all userVMs running on HX datastoresThis includes VMs running oncompute-only nodes After theVMshave been shut down verify thehealth state of the cluster andperform a graceful shutdown
HyperFlex controllerVMs (stCtlVMs) mustremain powered on
Important
4
Modifying Host Firmware PackageUsing Cisco UCS Manager
Manually stage the correctfirmware version before starting theupgrade process
5
In vCenter right-click on each HXController VM (stCtlVM) andselect Power gt Shut Down GuestOS
Shutdown theHyperFlexControllerVMs (stCtlVMs)
6
In vCenter right-click on eachESXi host select MaintenanceMode gt Enter MaintenanceMode
Once the Controller VMs areshutdown place the ESXi hostsinto Maintenance Mode
7
Acknowledge the pending rebooton the servers that comprise yourHX cluster nodes including bothconverged nodes and compute-onlynodes connected to the clusterWait until all nodes are upgradedConfirm that correct firmwarepackages have been installed beforeproceeding
8
In vCenter right-click on eachESXi host select MaintenanceMode gtExit Maintenance Mode
Once the ESXi hosts have bootedtake them out of MaintenanceMode Now the controller VMshould come back online
9
Upgrade Procedures9
Upgrade ProceduresOffline Upgrade Process Workflow
ReferenceDescriptionStep
Manual Bootstrap Upgrade ProcessBootstrap to upgrade the Cisco HXData Platform Plug-in
Important bull Be sure to copy thebootstrap file to thecontroller VMtmp directory
bull Ensure that youconfirm the versionof the plug-in inthe vCenterAdministration gtClient Plug-Inspage
10
Run the command stcli
snapshot-schedule --disableDisable snapshot schedule on thebootstrapped storage controllerVM
It is enough to run thisscript on one of thecontroller nodes
Note
11
Upgrading Your HyperFlex ClusterUsing the HX Connect UI on page1
Offline Upgrade Using CLI onpage 11
From the same controller VMbegin the upgrade
12
Post Upgrade TasksConfirm that upgrade is complete13
Start Cluster and Power On VMs on page 12
After the upgrade is complete startthe cluster and power on VMs
14
Run the command stcli
snapshot-schedule -ndashenableOn the same controller VM enablesnapshot schedule
15
Offline Upgrade Guidelines
bull --ucsm-host and --ucsm-user parameters are required when you are upgrading from 17x to 18x Theseparameters must not be used when moving up from 18(1a)18(1b) to 20(1a) as we are not changingthe Cisco UCS server firmware version
Cisco recommends using HX Connect UI to upgrade HyperFlex clusters over CLI for ease of use andbetter reporting You can safely ignore Cluster Invalid State alerts in HX Connect
Important
Upgrade Procedures10
Upgrade ProceduresOffline Upgrade Guidelines
Before you proceed with either combined or split upgrade consider the following guidelines
bull The package name must match the file that you uploaded to the controller VM
bull Enter passwords when prompted
bull Nodes are upgraded with the new version of the Cisco HX Data Platform software and rebooted one ata time
bull Offline cluster upgrades with nested vCenter is not supported
Offline Upgrade Using CLI
If you need to perform a split upgrade you must upgrade HX Data Platform first After HX Data Platform isupgraded to Release 35(1x) you can perform a split upgrade of UCSM only andor ESXi only
Important
Combined Upgrade of Cisco HX Data Platform ESXi and Cisco UCS Firmware
M5 Servers
stcli cluster upgrade --components ucs-fw hxdp hypervisor --locationtmpltstorfs package nameESXi package namegt --ucsm-host ltIPFQDN of UCSMgt--ucsm-user ltUCSM Usergt --ucsm5-fw-version ltUCSM Firmware Versiongt
Example for M5 Servers
~ stcli cluster upgrade --components ucs-fw hxdp hypervisor --locationtmpstorfs-packages-351a-19712tgz--ucsm-host eng-fi16engstorvisorcom --ucsm-user admin --ucs5fw-version 31(2g)
M4 Servers
stcli cluster upgrade --components ucs-fw hxdp hypervisor --locationtmpltstorfs package name ESXi package namegt --ucsm-host ltIPFQDN of UCSMgt--ucsm-user ltUCSM Usergt --ucsfw-version ltUCSM Firmware Versiongt
Example for M4 Servers
~ stcli cluster upgrade --components ucs-fw hxdp hypervisor --locationtmpstorfs-packages-351a-19712tgz--ucsm-host eng-fi16engstorvisorcom --ucsm-user admin --ucsfw-version 31(2g)
Combined Upgrade of Cisco HX Data Platform and ESXi
M5 Servers
stcli cluster upgrade --components hxdphypervisor --location tmphxupgrade_bundletgz--hypervisor-bundle tmpesxiupgrade_bundlezip
Example for M5 Servers
~ stcli cluster upgrade --components hxdphypervisor --location tmphxupgrade_bundletgz--hypervisor-bundle tmpesxiupgrade_bundlezip
M4 Servers
stcli cluster upgrade --components hxdphypervisor --location tmphxupgrade_bundletgz--hypervisor-bundle tmpesxiupgrade_bundlezip
Example for M4 Servers
Upgrade Procedures11
Upgrade ProceduresOffline Upgrade Using CLI
~ stcli cluster upgrade --components hxdphypervisor --location tmphxupgrade_bundletgz--hypervisor-bundle tmpesxiupgrade_bundlezip
Combined Upgrade of Cisco HX Data Platform and Cisco UCS Firmware
M5 Servers
stcli cluster upgrade --components hxdpucs-fw --locationtmpltstorfs package namegt --vcenter-user ltvcusergt --ucsm-host ltIPFQDN of UCSMgt--ucsm-user ltUCSM Usergt --ucsm5-fw-version ltUCSM Firmware Versiongt
M4 Servers
stcli cluster upgrade --components hxdpucs-fw --locationtmpltstorfs package namegt --vcenter-user ltvcusergt --ucsm-host ltIPFQDN of UCSMgt--ucsm-user ltUCSM Usergt --ucsfw-version ltUCSM Firmware Versiongt
Example for M4 Servers
~ stcli cluster upgrade --components hxdpucs-fw --locationtmpstorfs-packages-181c-19712tgz --vcenter-user administratorvspherelocal--ucsm-host eng-fi16engstorvisorcom --ucsm-user admin --ucsfw-version 31(2b)
Start Cluster and Power On VMsAfter the upgrade is complete and the cluster has been upgraded log out and log back in to vCenter to seeupgrade changes
Procedure
Step 1 After the upgrade is complete start your clusterStep 2 Login to any controller VM through SSH
stcli cluster start
ExampleHyperFlex StorageController 18(1c)Last login Wed Sept 21 235423 2016 from pguo-devengstorvisorcomrootucs-stclivm - 384 -1~ stcli cluster upgrade-statusCluster upgrade succeeded Cluster version 18(1c)rootucs-stctlvm-384~ stcli cluster startwaiting for Cluster to start on nodes [ucs-383 ucs-384 ucs-385 ucs-386]
This will start the cluster and mount the HX datastores Wait for cluster to come online You will see thepromptStarted cluster on nodes [ucs-383 ucs-384 ucs-385 ucs-386]Cluster is onlinerootucs-stctlvm-384-1~
Step 3 Wait for cluster to become healthy before starting the VMs Run command
~ stcli clustr info| grep health
Example
rootSpringpathControllerZRVF040451~ stcli cluster info | grep healthhealthState healthy
Upgrade Procedures12
Upgrade ProceduresStart Cluster and Power On VMs
state healthystorage cluster is healthy
Step 4 After the cluster is healthy launch vSphere Web Client or Thick Client navigate to Hosts and Cluster gtDatacenter gt Cluster gt Right click select Powergt Power On to start the VMs
Upgrade Procedures13
Upgrade ProceduresStart Cluster and Power On VMs
Upgrade Procedures14
Upgrade ProceduresStart Cluster and Power On VMs
Offline Upgrade Process WorkflowThe following table summarizes the offline upgrade workflow
ReferenceDescriptionStep
Downloading SoftwareIf UCSM (A-bundle) or UCSServer Firmware (C-bundle)upgrade is required downloadCisco UCS Infrastructure A bladebundle B and rack bundle C
1
Test Upstream NetworkConnectivity
Ensure that the hx-storage-data andvMotion upstream switches areconfigured for full network failovercapability before proceedingforward Otherwise the HyperFlexCluster becomes offline and alldatastores unmount from the ESXihosts
2
Upgrading Cisco UCSInfrastructure Using Cisco UCSManager
Upgrade Cisco UCS Infrastructurebundle as required
It is important that youmanually upgrade theUCS infrastructure firstbefore initiating theupgrade sequence of theHyperFlex componentsas outlined inRecommendedUpgradeMethod on page 1The upgrade feature ofthe HX Platformsoftware will notupgrade the UCSinfrastructure bundleThis upgrade is amanual process
Note
3
Upgrade Procedures8
Upgrade ProceduresOffline Upgrade Process Workflow
ReferenceDescriptionStep
Graceful Shutdown of a HXClusterLaunch the vSphere Web Clientand power down all user VMsresiding on HX servers and all userVMs running on HX datastoresThis includes VMs running oncompute-only nodes After theVMshave been shut down verify thehealth state of the cluster andperform a graceful shutdown
HyperFlex controllerVMs (stCtlVMs) mustremain powered on
Important
4
Modifying Host Firmware PackageUsing Cisco UCS Manager
Manually stage the correctfirmware version before starting theupgrade process
5
In vCenter right-click on each HXController VM (stCtlVM) andselect Power gt Shut Down GuestOS
Shutdown theHyperFlexControllerVMs (stCtlVMs)
6
In vCenter right-click on eachESXi host select MaintenanceMode gt Enter MaintenanceMode
Once the Controller VMs areshutdown place the ESXi hostsinto Maintenance Mode
7
Acknowledge the pending rebooton the servers that comprise yourHX cluster nodes including bothconverged nodes and compute-onlynodes connected to the clusterWait until all nodes are upgradedConfirm that correct firmwarepackages have been installed beforeproceeding
8
In vCenter right-click on eachESXi host select MaintenanceMode gtExit Maintenance Mode
Once the ESXi hosts have bootedtake them out of MaintenanceMode Now the controller VMshould come back online
9
Upgrade Procedures9
Upgrade ProceduresOffline Upgrade Process Workflow
ReferenceDescriptionStep
Manual Bootstrap Upgrade ProcessBootstrap to upgrade the Cisco HXData Platform Plug-in
Important bull Be sure to copy thebootstrap file to thecontroller VMtmp directory
bull Ensure that youconfirm the versionof the plug-in inthe vCenterAdministration gtClient Plug-Inspage
10
Run the command stcli
snapshot-schedule --disableDisable snapshot schedule on thebootstrapped storage controllerVM
It is enough to run thisscript on one of thecontroller nodes
Note
11
Upgrading Your HyperFlex ClusterUsing the HX Connect UI on page1
Offline Upgrade Using CLI onpage 11
From the same controller VMbegin the upgrade
12
Post Upgrade TasksConfirm that upgrade is complete13
Start Cluster and Power On VMs on page 12
After the upgrade is complete startthe cluster and power on VMs
14
Run the command stcli
snapshot-schedule -ndashenableOn the same controller VM enablesnapshot schedule
15
Offline Upgrade Guidelines
bull --ucsm-host and --ucsm-user parameters are required when you are upgrading from 17x to 18x Theseparameters must not be used when moving up from 18(1a)18(1b) to 20(1a) as we are not changingthe Cisco UCS server firmware version
Cisco recommends using HX Connect UI to upgrade HyperFlex clusters over CLI for ease of use andbetter reporting You can safely ignore Cluster Invalid State alerts in HX Connect
Important
Upgrade Procedures10
Upgrade ProceduresOffline Upgrade Guidelines
Before you proceed with either combined or split upgrade consider the following guidelines
bull The package name must match the file that you uploaded to the controller VM
bull Enter passwords when prompted
bull Nodes are upgraded with the new version of the Cisco HX Data Platform software and rebooted one ata time
bull Offline cluster upgrades with nested vCenter is not supported
Offline Upgrade Using CLI
If you need to perform a split upgrade you must upgrade HX Data Platform first After HX Data Platform isupgraded to Release 35(1x) you can perform a split upgrade of UCSM only andor ESXi only
Important
Combined Upgrade of Cisco HX Data Platform ESXi and Cisco UCS Firmware
M5 Servers
stcli cluster upgrade --components ucs-fw hxdp hypervisor --locationtmpltstorfs package nameESXi package namegt --ucsm-host ltIPFQDN of UCSMgt--ucsm-user ltUCSM Usergt --ucsm5-fw-version ltUCSM Firmware Versiongt
Example for M5 Servers
~ stcli cluster upgrade --components ucs-fw hxdp hypervisor --locationtmpstorfs-packages-351a-19712tgz--ucsm-host eng-fi16engstorvisorcom --ucsm-user admin --ucs5fw-version 31(2g)
M4 Servers
stcli cluster upgrade --components ucs-fw hxdp hypervisor --locationtmpltstorfs package name ESXi package namegt --ucsm-host ltIPFQDN of UCSMgt--ucsm-user ltUCSM Usergt --ucsfw-version ltUCSM Firmware Versiongt
Example for M4 Servers
~ stcli cluster upgrade --components ucs-fw hxdp hypervisor --locationtmpstorfs-packages-351a-19712tgz--ucsm-host eng-fi16engstorvisorcom --ucsm-user admin --ucsfw-version 31(2g)
Combined Upgrade of Cisco HX Data Platform and ESXi
M5 Servers
stcli cluster upgrade --components hxdphypervisor --location tmphxupgrade_bundletgz--hypervisor-bundle tmpesxiupgrade_bundlezip
Example for M5 Servers
~ stcli cluster upgrade --components hxdphypervisor --location tmphxupgrade_bundletgz--hypervisor-bundle tmpesxiupgrade_bundlezip
M4 Servers
stcli cluster upgrade --components hxdphypervisor --location tmphxupgrade_bundletgz--hypervisor-bundle tmpesxiupgrade_bundlezip
Example for M4 Servers
Upgrade Procedures11
Upgrade ProceduresOffline Upgrade Using CLI
~ stcli cluster upgrade --components hxdphypervisor --location tmphxupgrade_bundletgz--hypervisor-bundle tmpesxiupgrade_bundlezip
Combined Upgrade of Cisco HX Data Platform and Cisco UCS Firmware
M5 Servers
stcli cluster upgrade --components hxdpucs-fw --locationtmpltstorfs package namegt --vcenter-user ltvcusergt --ucsm-host ltIPFQDN of UCSMgt--ucsm-user ltUCSM Usergt --ucsm5-fw-version ltUCSM Firmware Versiongt
M4 Servers
stcli cluster upgrade --components hxdpucs-fw --locationtmpltstorfs package namegt --vcenter-user ltvcusergt --ucsm-host ltIPFQDN of UCSMgt--ucsm-user ltUCSM Usergt --ucsfw-version ltUCSM Firmware Versiongt
Example for M4 Servers
~ stcli cluster upgrade --components hxdpucs-fw --locationtmpstorfs-packages-181c-19712tgz --vcenter-user administratorvspherelocal--ucsm-host eng-fi16engstorvisorcom --ucsm-user admin --ucsfw-version 31(2b)
Start Cluster and Power On VMsAfter the upgrade is complete and the cluster has been upgraded log out and log back in to vCenter to seeupgrade changes
Procedure
Step 1 After the upgrade is complete start your clusterStep 2 Login to any controller VM through SSH
stcli cluster start
ExampleHyperFlex StorageController 18(1c)Last login Wed Sept 21 235423 2016 from pguo-devengstorvisorcomrootucs-stclivm - 384 -1~ stcli cluster upgrade-statusCluster upgrade succeeded Cluster version 18(1c)rootucs-stctlvm-384~ stcli cluster startwaiting for Cluster to start on nodes [ucs-383 ucs-384 ucs-385 ucs-386]
This will start the cluster and mount the HX datastores Wait for cluster to come online You will see thepromptStarted cluster on nodes [ucs-383 ucs-384 ucs-385 ucs-386]Cluster is onlinerootucs-stctlvm-384-1~
Step 3 Wait for cluster to become healthy before starting the VMs Run command
~ stcli clustr info| grep health
Example
rootSpringpathControllerZRVF040451~ stcli cluster info | grep healthhealthState healthy
Upgrade Procedures12
Upgrade ProceduresStart Cluster and Power On VMs
state healthystorage cluster is healthy
Step 4 After the cluster is healthy launch vSphere Web Client or Thick Client navigate to Hosts and Cluster gtDatacenter gt Cluster gt Right click select Powergt Power On to start the VMs
Upgrade Procedures13
Upgrade ProceduresStart Cluster and Power On VMs
Upgrade Procedures14
Upgrade ProceduresStart Cluster and Power On VMs
ReferenceDescriptionStep
Graceful Shutdown of a HXClusterLaunch the vSphere Web Clientand power down all user VMsresiding on HX servers and all userVMs running on HX datastoresThis includes VMs running oncompute-only nodes After theVMshave been shut down verify thehealth state of the cluster andperform a graceful shutdown
HyperFlex controllerVMs (stCtlVMs) mustremain powered on
Important
4
Modifying Host Firmware PackageUsing Cisco UCS Manager
Manually stage the correctfirmware version before starting theupgrade process
5
In vCenter right-click on each HXController VM (stCtlVM) andselect Power gt Shut Down GuestOS
Shutdown theHyperFlexControllerVMs (stCtlVMs)
6
In vCenter right-click on eachESXi host select MaintenanceMode gt Enter MaintenanceMode
Once the Controller VMs areshutdown place the ESXi hostsinto Maintenance Mode
7
Acknowledge the pending rebooton the servers that comprise yourHX cluster nodes including bothconverged nodes and compute-onlynodes connected to the clusterWait until all nodes are upgradedConfirm that correct firmwarepackages have been installed beforeproceeding
8
In vCenter right-click on eachESXi host select MaintenanceMode gtExit Maintenance Mode
Once the ESXi hosts have bootedtake them out of MaintenanceMode Now the controller VMshould come back online
9
Upgrade Procedures9
Upgrade ProceduresOffline Upgrade Process Workflow
ReferenceDescriptionStep
Manual Bootstrap Upgrade ProcessBootstrap to upgrade the Cisco HXData Platform Plug-in
Important bull Be sure to copy thebootstrap file to thecontroller VMtmp directory
bull Ensure that youconfirm the versionof the plug-in inthe vCenterAdministration gtClient Plug-Inspage
10
Run the command stcli
snapshot-schedule --disableDisable snapshot schedule on thebootstrapped storage controllerVM
It is enough to run thisscript on one of thecontroller nodes
Note
11
Upgrading Your HyperFlex ClusterUsing the HX Connect UI on page1
Offline Upgrade Using CLI onpage 11
From the same controller VMbegin the upgrade
12
Post Upgrade TasksConfirm that upgrade is complete13
Start Cluster and Power On VMs on page 12
After the upgrade is complete startthe cluster and power on VMs
14
Run the command stcli
snapshot-schedule -ndashenableOn the same controller VM enablesnapshot schedule
15
Offline Upgrade Guidelines
bull --ucsm-host and --ucsm-user parameters are required when you are upgrading from 17x to 18x Theseparameters must not be used when moving up from 18(1a)18(1b) to 20(1a) as we are not changingthe Cisco UCS server firmware version
Cisco recommends using HX Connect UI to upgrade HyperFlex clusters over CLI for ease of use andbetter reporting You can safely ignore Cluster Invalid State alerts in HX Connect
Important
Upgrade Procedures10
Upgrade ProceduresOffline Upgrade Guidelines
Before you proceed with either combined or split upgrade consider the following guidelines
bull The package name must match the file that you uploaded to the controller VM
bull Enter passwords when prompted
bull Nodes are upgraded with the new version of the Cisco HX Data Platform software and rebooted one ata time
bull Offline cluster upgrades with nested vCenter is not supported
Offline Upgrade Using CLI
If you need to perform a split upgrade you must upgrade HX Data Platform first After HX Data Platform isupgraded to Release 35(1x) you can perform a split upgrade of UCSM only andor ESXi only
Important
Combined Upgrade of Cisco HX Data Platform ESXi and Cisco UCS Firmware
M5 Servers
stcli cluster upgrade --components ucs-fw hxdp hypervisor --locationtmpltstorfs package nameESXi package namegt --ucsm-host ltIPFQDN of UCSMgt--ucsm-user ltUCSM Usergt --ucsm5-fw-version ltUCSM Firmware Versiongt
Example for M5 Servers
~ stcli cluster upgrade --components ucs-fw hxdp hypervisor --locationtmpstorfs-packages-351a-19712tgz--ucsm-host eng-fi16engstorvisorcom --ucsm-user admin --ucs5fw-version 31(2g)
M4 Servers
stcli cluster upgrade --components ucs-fw hxdp hypervisor --locationtmpltstorfs package name ESXi package namegt --ucsm-host ltIPFQDN of UCSMgt--ucsm-user ltUCSM Usergt --ucsfw-version ltUCSM Firmware Versiongt
Example for M4 Servers
~ stcli cluster upgrade --components ucs-fw hxdp hypervisor --locationtmpstorfs-packages-351a-19712tgz--ucsm-host eng-fi16engstorvisorcom --ucsm-user admin --ucsfw-version 31(2g)
Combined Upgrade of Cisco HX Data Platform and ESXi
M5 Servers
stcli cluster upgrade --components hxdphypervisor --location tmphxupgrade_bundletgz--hypervisor-bundle tmpesxiupgrade_bundlezip
Example for M5 Servers
~ stcli cluster upgrade --components hxdphypervisor --location tmphxupgrade_bundletgz--hypervisor-bundle tmpesxiupgrade_bundlezip
M4 Servers
stcli cluster upgrade --components hxdphypervisor --location tmphxupgrade_bundletgz--hypervisor-bundle tmpesxiupgrade_bundlezip
Example for M4 Servers
Upgrade Procedures11
Upgrade ProceduresOffline Upgrade Using CLI
~ stcli cluster upgrade --components hxdphypervisor --location tmphxupgrade_bundletgz--hypervisor-bundle tmpesxiupgrade_bundlezip
Combined Upgrade of Cisco HX Data Platform and Cisco UCS Firmware
M5 Servers
stcli cluster upgrade --components hxdpucs-fw --locationtmpltstorfs package namegt --vcenter-user ltvcusergt --ucsm-host ltIPFQDN of UCSMgt--ucsm-user ltUCSM Usergt --ucsm5-fw-version ltUCSM Firmware Versiongt
M4 Servers
stcli cluster upgrade --components hxdpucs-fw --locationtmpltstorfs package namegt --vcenter-user ltvcusergt --ucsm-host ltIPFQDN of UCSMgt--ucsm-user ltUCSM Usergt --ucsfw-version ltUCSM Firmware Versiongt
Example for M4 Servers
~ stcli cluster upgrade --components hxdpucs-fw --locationtmpstorfs-packages-181c-19712tgz --vcenter-user administratorvspherelocal--ucsm-host eng-fi16engstorvisorcom --ucsm-user admin --ucsfw-version 31(2b)
Start Cluster and Power On VMsAfter the upgrade is complete and the cluster has been upgraded log out and log back in to vCenter to seeupgrade changes
Procedure
Step 1 After the upgrade is complete start your clusterStep 2 Login to any controller VM through SSH
stcli cluster start
ExampleHyperFlex StorageController 18(1c)Last login Wed Sept 21 235423 2016 from pguo-devengstorvisorcomrootucs-stclivm - 384 -1~ stcli cluster upgrade-statusCluster upgrade succeeded Cluster version 18(1c)rootucs-stctlvm-384~ stcli cluster startwaiting for Cluster to start on nodes [ucs-383 ucs-384 ucs-385 ucs-386]
This will start the cluster and mount the HX datastores Wait for cluster to come online You will see thepromptStarted cluster on nodes [ucs-383 ucs-384 ucs-385 ucs-386]Cluster is onlinerootucs-stctlvm-384-1~
Step 3 Wait for cluster to become healthy before starting the VMs Run command
~ stcli clustr info| grep health
Example
rootSpringpathControllerZRVF040451~ stcli cluster info | grep healthhealthState healthy
Upgrade Procedures12
Upgrade ProceduresStart Cluster and Power On VMs
state healthystorage cluster is healthy
Step 4 After the cluster is healthy launch vSphere Web Client or Thick Client navigate to Hosts and Cluster gtDatacenter gt Cluster gt Right click select Powergt Power On to start the VMs
Upgrade Procedures13
Upgrade ProceduresStart Cluster and Power On VMs
Upgrade Procedures14
Upgrade ProceduresStart Cluster and Power On VMs
ReferenceDescriptionStep
Manual Bootstrap Upgrade ProcessBootstrap to upgrade the Cisco HXData Platform Plug-in
Important bull Be sure to copy thebootstrap file to thecontroller VMtmp directory
bull Ensure that youconfirm the versionof the plug-in inthe vCenterAdministration gtClient Plug-Inspage
10
Run the command stcli
snapshot-schedule --disableDisable snapshot schedule on thebootstrapped storage controllerVM
It is enough to run thisscript on one of thecontroller nodes
Note
11
Upgrading Your HyperFlex ClusterUsing the HX Connect UI on page1
Offline Upgrade Using CLI onpage 11
From the same controller VMbegin the upgrade
12
Post Upgrade TasksConfirm that upgrade is complete13
Start Cluster and Power On VMs on page 12
After the upgrade is complete startthe cluster and power on VMs
14
Run the command stcli
snapshot-schedule -ndashenableOn the same controller VM enablesnapshot schedule
15
Offline Upgrade Guidelines
bull --ucsm-host and --ucsm-user parameters are required when you are upgrading from 17x to 18x Theseparameters must not be used when moving up from 18(1a)18(1b) to 20(1a) as we are not changingthe Cisco UCS server firmware version
Cisco recommends using HX Connect UI to upgrade HyperFlex clusters over CLI for ease of use andbetter reporting You can safely ignore Cluster Invalid State alerts in HX Connect
Important
Upgrade Procedures10
Upgrade ProceduresOffline Upgrade Guidelines
Before you proceed with either combined or split upgrade consider the following guidelines
bull The package name must match the file that you uploaded to the controller VM
bull Enter passwords when prompted
bull Nodes are upgraded with the new version of the Cisco HX Data Platform software and rebooted one ata time
bull Offline cluster upgrades with nested vCenter is not supported
Offline Upgrade Using CLI
If you need to perform a split upgrade you must upgrade HX Data Platform first After HX Data Platform isupgraded to Release 35(1x) you can perform a split upgrade of UCSM only andor ESXi only
Important
Combined Upgrade of Cisco HX Data Platform ESXi and Cisco UCS Firmware
M5 Servers
stcli cluster upgrade --components ucs-fw hxdp hypervisor --locationtmpltstorfs package nameESXi package namegt --ucsm-host ltIPFQDN of UCSMgt--ucsm-user ltUCSM Usergt --ucsm5-fw-version ltUCSM Firmware Versiongt
Example for M5 Servers
~ stcli cluster upgrade --components ucs-fw hxdp hypervisor --locationtmpstorfs-packages-351a-19712tgz--ucsm-host eng-fi16engstorvisorcom --ucsm-user admin --ucs5fw-version 31(2g)
M4 Servers
stcli cluster upgrade --components ucs-fw hxdp hypervisor --locationtmpltstorfs package name ESXi package namegt --ucsm-host ltIPFQDN of UCSMgt--ucsm-user ltUCSM Usergt --ucsfw-version ltUCSM Firmware Versiongt
Example for M4 Servers
~ stcli cluster upgrade --components ucs-fw hxdp hypervisor --locationtmpstorfs-packages-351a-19712tgz--ucsm-host eng-fi16engstorvisorcom --ucsm-user admin --ucsfw-version 31(2g)
Combined Upgrade of Cisco HX Data Platform and ESXi
M5 Servers
stcli cluster upgrade --components hxdphypervisor --location tmphxupgrade_bundletgz--hypervisor-bundle tmpesxiupgrade_bundlezip
Example for M5 Servers
~ stcli cluster upgrade --components hxdphypervisor --location tmphxupgrade_bundletgz--hypervisor-bundle tmpesxiupgrade_bundlezip
M4 Servers
stcli cluster upgrade --components hxdphypervisor --location tmphxupgrade_bundletgz--hypervisor-bundle tmpesxiupgrade_bundlezip
Example for M4 Servers
Upgrade Procedures11
Upgrade ProceduresOffline Upgrade Using CLI
~ stcli cluster upgrade --components hxdphypervisor --location tmphxupgrade_bundletgz--hypervisor-bundle tmpesxiupgrade_bundlezip
Combined Upgrade of Cisco HX Data Platform and Cisco UCS Firmware
M5 Servers
stcli cluster upgrade --components hxdpucs-fw --locationtmpltstorfs package namegt --vcenter-user ltvcusergt --ucsm-host ltIPFQDN of UCSMgt--ucsm-user ltUCSM Usergt --ucsm5-fw-version ltUCSM Firmware Versiongt
M4 Servers
stcli cluster upgrade --components hxdpucs-fw --locationtmpltstorfs package namegt --vcenter-user ltvcusergt --ucsm-host ltIPFQDN of UCSMgt--ucsm-user ltUCSM Usergt --ucsfw-version ltUCSM Firmware Versiongt
Example for M4 Servers
~ stcli cluster upgrade --components hxdpucs-fw --locationtmpstorfs-packages-181c-19712tgz --vcenter-user administratorvspherelocal--ucsm-host eng-fi16engstorvisorcom --ucsm-user admin --ucsfw-version 31(2b)
Start Cluster and Power On VMsAfter the upgrade is complete and the cluster has been upgraded log out and log back in to vCenter to seeupgrade changes
Procedure
Step 1 After the upgrade is complete start your clusterStep 2 Login to any controller VM through SSH
stcli cluster start
ExampleHyperFlex StorageController 18(1c)Last login Wed Sept 21 235423 2016 from pguo-devengstorvisorcomrootucs-stclivm - 384 -1~ stcli cluster upgrade-statusCluster upgrade succeeded Cluster version 18(1c)rootucs-stctlvm-384~ stcli cluster startwaiting for Cluster to start on nodes [ucs-383 ucs-384 ucs-385 ucs-386]
This will start the cluster and mount the HX datastores Wait for cluster to come online You will see thepromptStarted cluster on nodes [ucs-383 ucs-384 ucs-385 ucs-386]Cluster is onlinerootucs-stctlvm-384-1~
Step 3 Wait for cluster to become healthy before starting the VMs Run command
~ stcli clustr info| grep health
Example
rootSpringpathControllerZRVF040451~ stcli cluster info | grep healthhealthState healthy
Upgrade Procedures12
Upgrade ProceduresStart Cluster and Power On VMs
state healthystorage cluster is healthy
Step 4 After the cluster is healthy launch vSphere Web Client or Thick Client navigate to Hosts and Cluster gtDatacenter gt Cluster gt Right click select Powergt Power On to start the VMs
Upgrade Procedures13
Upgrade ProceduresStart Cluster and Power On VMs
Upgrade Procedures14
Upgrade ProceduresStart Cluster and Power On VMs
Before you proceed with either combined or split upgrade consider the following guidelines
bull The package name must match the file that you uploaded to the controller VM
bull Enter passwords when prompted
bull Nodes are upgraded with the new version of the Cisco HX Data Platform software and rebooted one ata time
bull Offline cluster upgrades with nested vCenter is not supported
Offline Upgrade Using CLI
If you need to perform a split upgrade you must upgrade HX Data Platform first After HX Data Platform isupgraded to Release 35(1x) you can perform a split upgrade of UCSM only andor ESXi only
Important
Combined Upgrade of Cisco HX Data Platform ESXi and Cisco UCS Firmware
M5 Servers
stcli cluster upgrade --components ucs-fw hxdp hypervisor --locationtmpltstorfs package nameESXi package namegt --ucsm-host ltIPFQDN of UCSMgt--ucsm-user ltUCSM Usergt --ucsm5-fw-version ltUCSM Firmware Versiongt
Example for M5 Servers
~ stcli cluster upgrade --components ucs-fw hxdp hypervisor --locationtmpstorfs-packages-351a-19712tgz--ucsm-host eng-fi16engstorvisorcom --ucsm-user admin --ucs5fw-version 31(2g)
M4 Servers
stcli cluster upgrade --components ucs-fw hxdp hypervisor --locationtmpltstorfs package name ESXi package namegt --ucsm-host ltIPFQDN of UCSMgt--ucsm-user ltUCSM Usergt --ucsfw-version ltUCSM Firmware Versiongt
Example for M4 Servers
~ stcli cluster upgrade --components ucs-fw hxdp hypervisor --locationtmpstorfs-packages-351a-19712tgz--ucsm-host eng-fi16engstorvisorcom --ucsm-user admin --ucsfw-version 31(2g)
Combined Upgrade of Cisco HX Data Platform and ESXi
M5 Servers
stcli cluster upgrade --components hxdphypervisor --location tmphxupgrade_bundletgz--hypervisor-bundle tmpesxiupgrade_bundlezip
Example for M5 Servers
~ stcli cluster upgrade --components hxdphypervisor --location tmphxupgrade_bundletgz--hypervisor-bundle tmpesxiupgrade_bundlezip
M4 Servers
stcli cluster upgrade --components hxdphypervisor --location tmphxupgrade_bundletgz--hypervisor-bundle tmpesxiupgrade_bundlezip
Example for M4 Servers
Upgrade Procedures11
Upgrade ProceduresOffline Upgrade Using CLI
~ stcli cluster upgrade --components hxdphypervisor --location tmphxupgrade_bundletgz--hypervisor-bundle tmpesxiupgrade_bundlezip
Combined Upgrade of Cisco HX Data Platform and Cisco UCS Firmware
M5 Servers
stcli cluster upgrade --components hxdpucs-fw --locationtmpltstorfs package namegt --vcenter-user ltvcusergt --ucsm-host ltIPFQDN of UCSMgt--ucsm-user ltUCSM Usergt --ucsm5-fw-version ltUCSM Firmware Versiongt
M4 Servers
stcli cluster upgrade --components hxdpucs-fw --locationtmpltstorfs package namegt --vcenter-user ltvcusergt --ucsm-host ltIPFQDN of UCSMgt--ucsm-user ltUCSM Usergt --ucsfw-version ltUCSM Firmware Versiongt
Example for M4 Servers
~ stcli cluster upgrade --components hxdpucs-fw --locationtmpstorfs-packages-181c-19712tgz --vcenter-user administratorvspherelocal--ucsm-host eng-fi16engstorvisorcom --ucsm-user admin --ucsfw-version 31(2b)
Start Cluster and Power On VMsAfter the upgrade is complete and the cluster has been upgraded log out and log back in to vCenter to seeupgrade changes
Procedure
Step 1 After the upgrade is complete start your clusterStep 2 Login to any controller VM through SSH
stcli cluster start
ExampleHyperFlex StorageController 18(1c)Last login Wed Sept 21 235423 2016 from pguo-devengstorvisorcomrootucs-stclivm - 384 -1~ stcli cluster upgrade-statusCluster upgrade succeeded Cluster version 18(1c)rootucs-stctlvm-384~ stcli cluster startwaiting for Cluster to start on nodes [ucs-383 ucs-384 ucs-385 ucs-386]
This will start the cluster and mount the HX datastores Wait for cluster to come online You will see thepromptStarted cluster on nodes [ucs-383 ucs-384 ucs-385 ucs-386]Cluster is onlinerootucs-stctlvm-384-1~
Step 3 Wait for cluster to become healthy before starting the VMs Run command
~ stcli clustr info| grep health
Example
rootSpringpathControllerZRVF040451~ stcli cluster info | grep healthhealthState healthy
Upgrade Procedures12
Upgrade ProceduresStart Cluster and Power On VMs
state healthystorage cluster is healthy
Step 4 After the cluster is healthy launch vSphere Web Client or Thick Client navigate to Hosts and Cluster gtDatacenter gt Cluster gt Right click select Powergt Power On to start the VMs
Upgrade Procedures13
Upgrade ProceduresStart Cluster and Power On VMs
Upgrade Procedures14
Upgrade ProceduresStart Cluster and Power On VMs
~ stcli cluster upgrade --components hxdphypervisor --location tmphxupgrade_bundletgz--hypervisor-bundle tmpesxiupgrade_bundlezip
Combined Upgrade of Cisco HX Data Platform and Cisco UCS Firmware
M5 Servers
stcli cluster upgrade --components hxdpucs-fw --locationtmpltstorfs package namegt --vcenter-user ltvcusergt --ucsm-host ltIPFQDN of UCSMgt--ucsm-user ltUCSM Usergt --ucsm5-fw-version ltUCSM Firmware Versiongt
M4 Servers
stcli cluster upgrade --components hxdpucs-fw --locationtmpltstorfs package namegt --vcenter-user ltvcusergt --ucsm-host ltIPFQDN of UCSMgt--ucsm-user ltUCSM Usergt --ucsfw-version ltUCSM Firmware Versiongt
Example for M4 Servers
~ stcli cluster upgrade --components hxdpucs-fw --locationtmpstorfs-packages-181c-19712tgz --vcenter-user administratorvspherelocal--ucsm-host eng-fi16engstorvisorcom --ucsm-user admin --ucsfw-version 31(2b)
Start Cluster and Power On VMsAfter the upgrade is complete and the cluster has been upgraded log out and log back in to vCenter to seeupgrade changes
Procedure
Step 1 After the upgrade is complete start your clusterStep 2 Login to any controller VM through SSH
stcli cluster start
ExampleHyperFlex StorageController 18(1c)Last login Wed Sept 21 235423 2016 from pguo-devengstorvisorcomrootucs-stclivm - 384 -1~ stcli cluster upgrade-statusCluster upgrade succeeded Cluster version 18(1c)rootucs-stctlvm-384~ stcli cluster startwaiting for Cluster to start on nodes [ucs-383 ucs-384 ucs-385 ucs-386]
This will start the cluster and mount the HX datastores Wait for cluster to come online You will see thepromptStarted cluster on nodes [ucs-383 ucs-384 ucs-385 ucs-386]Cluster is onlinerootucs-stctlvm-384-1~
Step 3 Wait for cluster to become healthy before starting the VMs Run command
~ stcli clustr info| grep health
Example
rootSpringpathControllerZRVF040451~ stcli cluster info | grep healthhealthState healthy
Upgrade Procedures12
Upgrade ProceduresStart Cluster and Power On VMs
state healthystorage cluster is healthy
Step 4 After the cluster is healthy launch vSphere Web Client or Thick Client navigate to Hosts and Cluster gtDatacenter gt Cluster gt Right click select Powergt Power On to start the VMs
Upgrade Procedures13
Upgrade ProceduresStart Cluster and Power On VMs
Upgrade Procedures14
Upgrade ProceduresStart Cluster and Power On VMs
state healthystorage cluster is healthy
Step 4 After the cluster is healthy launch vSphere Web Client or Thick Client navigate to Hosts and Cluster gtDatacenter gt Cluster gt Right click select Powergt Power On to start the VMs
Upgrade Procedures13
Upgrade ProceduresStart Cluster and Power On VMs
Upgrade Procedures14
Upgrade ProceduresStart Cluster and Power On VMs
Upgrade Procedures14
Upgrade ProceduresStart Cluster and Power On VMs
![Zggh]hPH>new.groteck.ru/images/catalog/40429/9deec18637ee6ecbb5a6ae0a1… · UCS 6200 Series Fabric Interconnect UCS Manager UCS C240 M3/M4 Series Rack Server UCS Integrated Infrastructure](https://img.pdfslide.us/doc/110x75/5fcc7e22130a463bbb0b3c57/zgghhphnew-ucs-6200-series-fabric-interconnect-ucs-manager-ucs-c240-m3m4.jpg)
