Scribd
Upload
386 views

HyperFlex Edge Customer Cleanup Guide-V1

This document provides instructions for cleaning up an existing HyperFlex Edge deployment before reinstalling. The procedures will remove VMs and reset the system configuration but will not completely remove all HyperFlex components from the nodes. It involves cleaning up vCenter, reinstalling ESXi on each node, and cleaning up Intersight by removing service profiles and devices. The goal is to reset the nodes for easy reinstallation of HyperFlex while backing up any existing VMs and data.

Uploaded by

opedro9850
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
386 views

HyperFlex Edge Customer Cleanup Guide-V1

This document provides instructions for cleaning up an existing HyperFlex Edge deployment before reinstalling. The procedures will remove VMs and reset the system configuration but will not completely remove all HyperFlex components from the nodes. It involves cleaning up vCenter, reinstalling ESXi on each node, and cleaning up Intersight by removing service profiles and devices. The goal is to reset the nodes for easy reinstallation of HyperFlex while backing up any existing VMs and data.

Uploaded by

opedro9850
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 34

HyperFlex Edge

Customer Cleanup Guide

7/24/2019
Before You Begin…
• This field guide is meant to be used by customers for cleaning up an existing HyperFlex Edge
deployment for the purposes of reinstalling
• The procedures to follow are DESTRUCTIVE. Make sure all VMs and data are backed up before
proceeding.
• This procedure is meant for cleaning up a node for the purposes of redeploying HyperFlex. It will not
completely remove all HX components from the nodes, just reset the system so it may be easily
reinstalled. Contact TAC for the full cleanup procedure.
• Consult the latest version of this document: https://community.cisco.com/t5/unified-computing-system/hyperflex-
edge-customer-cleanup-guide/ta-p/3896668
Revision History
Version Date Author
1.1 7/24/2019 Gina Nienaber
Mandatory ESXi License Check
If you supplied traditional VMware license keys, you may proceed with
this cleanup procedure

If your HyperFlex nodes shipped with ESXi licensed from factory (Enterprise Plus
or Standard editions), do not continue with this re-image procedure. Contact TAC
to assist with an alternate cleanup procedure.
You can determine your licensing by looking in ESXi for the license key. If the key
is obfuscated, you must not proceed with a re-image.
Example OEM key: 0J497-XXXXX-XXXXX-XXXXX-0HL0M
Exception: If the key is an OEM Foundation License, you may proceed.
Prerequisites
• In preparation for cleanup procedure, download the VMware ESXi custom image
specific to HyperFlex – install-only.iso
• Reminder: Edge does not have Fabric Interconnects and SED drives are not
supported.

Note:
After cleanup is finished, there will be a few differences when re-running the install vs.
running with a fresh node shipped from factory.
• In this case, the controller VMs have been removed and must be redeployed vs. being
already deployed from factory.
• This will add some small amount of time to the deployment vs. the out-of-box experience on
factory fresh nodes.
• Minus this small difference, the process is still automated. The controller VM is
automatically redeployed.
Reimage Cleanup Procedure
For HyperFlex Edge
Reimage Cleanup Workflow
ü Cleanup VMware vCenter
ü Cleanup vCenter GUI
ü Reinstall ESXi
ü Cleanup Intersight
ü Part 1: Service Profiles
ü Part 2: Devices
Example Scenario
• RTP Data Center has two (2) HyperFlex 2-Node clusters deployed.
• HX-Edge-2
• HX-Edge-3

• In this scenario we will reimage the HX-Edge-2a host in the HX-Edge-2 Cluster.

• Note: This procedure can be used for 3 and 4 node HX-Edge clusters as well.

• Note: If you are not using Cisco Intersight to manage your 3 or 4 node system, disregard the Intersight steps in this
guide.
Before you begin..
• Login here http://www.cisco.com/c/en/us/support/hyperconverged-systems/hyperflex-hx-data-
platform-software/tsd-products-support-series-home.html and download the ESXi version you
wish to deploy.
• Reference the most recent version of the release notes to confirm compatibility.
• In this scenario we downloaded: Cisco HX Custom Image for ESXi 6.5 U2 EP13 Install.
Cleanup vCenter Workflow Overview
Cleanup vCenter GUI
Step 1: Login to VMware vSphere GUI.

Login to VMware vSphere GU for the cluster you


would like to cleanup. In this case, HX-Edge-2.
Cleanup vCenter GUI
Step 2: Delete the HyperFlex Cluster.

Delete the HyperFlex cluster you would like to cleanup.


In this case, HX-Edge-2. HX ESXi hosts must be removed
HX-Edge-2 cluster is now deleted from the RTP
from the vCenter inventory (in case they happen to be
datacenter in vCenter.
elsewhere under another DC object).

WARNING! Do not delete the top level datacenter (RTP)!


especially if you have multiple clusters installed under
the datacenter and your intention is to only cleanup one
(1) cluster.

‘Right click’ on the ‘HX-Edge-2’ cluster, and select


‘delete’. This will remove the cluster from vCenter

vCenter is now cleaned-up!


Reinstall ESXi Workflow Overview
Reinstall ESXi
Step 1: Login to the CIMC of host 1 of N.

You must RE-INSTALL ESXi on each server in the cluster.


In this case we will login to HX-Edge-2a and HX-Edge-2b. This
example will show the re-install process on HX-Edge-2a.
Reinstall ESXi
Step 2: Launch KVM.
Reinstall ESXi
Step 3: Activate Virtual Devices and mount the ‘custom HyperFlex ESXi install only ISO’.

1. Click on ‘Virtual Media’ and select ’Activate Virtual Devices’.


2. Click on ‘Virtual ‘Media’ and select ‘Map CD/DVD’.
This allows you to attach a virtual CD ROM to the servers
and mount the HyperFlex ESXi install only ISO.
Reinstall ESXi
Step 3: Activate Virtual Devices and mount the custom ‘HyperFlex ESXi install only ISO’.

3. Browse to the ESXi ISO image you downloaded 4. Power Cycle the host.
(HX Custom ESXi image), open, and map drive.
Reinstall ESXi 6. Select to boot device ‘Cisco KVM-Mapped vDVD1.24’.

Step 4: Select to boot to the Cisco vKVM mapped drive.


5. During boot up, Select <F6> to open the ‘BOOT MENU’.

7. Select HyperFlex Converged Node – HX PIDs-Only. Enter ERASE


(all CAPs) and hit enter.
Reinstall ESXi
Step 5: Installation automatically completes.
9. Ignore Warnings! These are expected and can be safely ignored.
Let ESXi reboot automatically.

8. The rest of the install is hands off. The server will reboot multiple times.
Reinstall ESXi
Step 5: Installation automatically completes.

You will see the message on the previous


page about the system finishing install. ESXi
will automatically restart.

The first time ESXi boots, it will run a


customization script. This will cause ESXi to
reboot a second time.

Once ESXi boots again, you will be at the


DCUI as shown to the right, ready for graceful
shutdown and new HX deployment.
ESXi is now reinstalled!
Reinstall ESXi
Step 6: Repeat the process on host 2 of N.

10. In this case, re-install ESXi on the second server, HX-Edge-2b.

ET E on
OMP L
tal l C
SXi r e-ins G E- 2a!
ü E HX-ED
Cleanup Intersight Workflow Overview
Part 1: Cleanup Intersight Service Profile
Step 1: Login to Intersight
Part 1: Cleanup Intersight Service Profile
Step 2: Under Service Profiles, unassign the HX cluster profile and delete if not needed going forward.
1. Locate the cluster you want to
2. Click on ‘…’ and then on ‘unassign’ to remove the nodes
remove under Service Profiles. In
from the HX Cluster.
this case we will be removing HX-
Edge-2.

5. If you are not going to re-use the


profile on re-install, delete the service
3. Click on ‘unassign’. 4. Status is now ‘not assigned’. profile.
Note: If you are going to re-deploy this cluster, don’t delete this
service profile. You can use all the information contained within it
when you re-install your cluster. If you are not going to re-use
the service profile, the next step would be to delete this profile as
shown in step 6.
Part 2: Cleanup Intersight Devices
Under Devices, remove the HyperFlex cluster
6. Under ‘devices’ remove the ‘HyperFlex cluster’ 7. After removing the HyperFlex Cluster from Devices it
as a device from Intersight by ‘deleting’ the will no longer appear under HyperFlex Clusters, as shown
HyperFlex Cluster. below.
Warning: Don’t delete the individual servers, only
the hyperflex cluster.

8. If you want to completely remove the servers from


Intersight, the last step in the process would be to
‘unclaim’ the servers under ‘devices’. Select the
devices and delete. Do Not delete if you plan to re-
install the nodes.
Redeploying HyperFlex Overview
When Redeploying HyperFlex via Intersight
Step 1: Check the box for The hypervisor on this node uses the default password.

This checkbox must be checked to ensure a new password is set.

This box is found on the cluster configuration page under the security policy. The password will
be set to a secure user-defined password as part of installation.
When Redeploying HyperFlex via Intersight
Step 2: Check the box to clean up disk partitions.

Make sure this box is checked to clean up disk partitions!


It is found on the cluster configuration page.
When Re-Deploying HyperFlex via
On-Premise Installer OVA
Step 1: When redeploying, check the box for The hypervisor on this node uses the default password.

The default password must be used when redeploying HyperFlex.


This box is found on the credentials tab (Hypervisor Credentials).

Note: When the cluster is reimaged the password is set to the default.
When Re-Deploying HyperFlex via
On-Premise Installer OVA
Step 2: When redeploying, check to clean up disk partitions.

Make sure this box is checked to clean up disk partitions!


It is found on the final page (cluster configuration) before starting deployment.
Troubleshooting
Disk /dev/… is Formatted as a storfs Disk

• Click edit configuration


Continue
• Check the box to “Clean Up Disk
Partitions”
• Click Continue Click “Retry
Deploy” at the top of the page
• See this step
Host x.x.x.x is Disconnected

You must remove the stale ESXi host


from vCenter inventory, even if using
a new management IP. The unique ID
of the server is remembered by VC
and must be removed.
Clear out the old host entry from the
vCenter inventory and retry
deployment.
HyperFlex Resources
• https://www.cisco.com/c/en/us/support/hyperconverged-systems/hyperflex-
hx-data-platform-software/tsd-products-support-series-home.html
Thank You

You might also like