Skip to main content

Process to Take Out Hosts from NSX Cluster


We recently implemented NSX in one of the VDI environment.  The environment had vShield and trend Micro Deep Security to protect the desktops. Once we migrated from vShield to NSX, we observed that taking out the host from the NSX cluster needs to follow specific steps. If these steps are not followed in the specific order there may be possibility that the host may not be cleaned up thoroughly with NSX vibs. Here is the process that will make sure the hosts are cleaned up properly once removed from NSX cluster.


  • Put the ESXi host in maintenance mode. The NSX agent VMs that are specific and residing on that host for NSX management, will be powered down once host is in maintenance mode.
  • Take out the host from the cluster by dragging it out of the cluster (in the data center or in some other cluster)
  • Wait till the NSX agent/VIB gets uninstalled from the host (you will see that in the task manager of vCenter)

  • Once VIBs are removed by vCenter – Reboot the host


  • Once reboot is complete, remove the host out of maintenance mode – it will delete the 2 VMs that were residing on it (Guest Introspection and trend Micro Deep Security)


  • Once this is complete the host will be all cleared from the NSX vibs. 
Labels:

Comments

Post a Comment

Popular posts from this blog

Guest Introspection(GI) NSX Appliance gets Deleted Automatically after vCenter Disconnect

I was working in an environment where NSX was configured with Trend micro deep security in VDI environment to protect VDI desktops. We had 2 vCenters setup in that way and one of the vCenter is showing some odd symptoms. We are seeing some weird actions with NSX manager in one vCenter. So, I lose the connection to the vCenter from fat client, web client is still fine and doesn’t kick me off. In the process, the Guest Introspection appliance or GI VMs (appliance managed by NSX) from some  random hosts were getting deleted automatically -  from the cluster that was protected with NSX. When I checked the windows logs (as vCenter was on windows server) this is what I saw -  I opened a case with VMware support - They reviewed the NSX logs and came to conclusion that this is not the NSX issue but it's vCenter that is deleting those VMs. vCenter gets disconnected for few seconds, then connects back. It doesn't recognizes those GI VMs and starts de...
2 comments
Read more

Upgrading HPE 3PAR SRA (Storage Replication Adapter) from 6.1 to 6.5

Here  are the high level step to upgrade the HPE 3PAR Storage Replication Adapter (SRA) - If old SRA is visible in add remove programs -  View certificates for old array (that will be removed after migration) from SRM server using following path and TPDsrm utility -        C:\Program Files\VMware\VMware Site Recovery manager\Storage\SRA\3Parinsrv>              TPDsrm.exe viewcert Uninstall old 3PAR SRA from SRM server using uninstall program feature. Reboot the SRM server. Install new 3PAR SRA using the .exe file provided by vendor. Check if you can see the new SRA in Program list. If so, reboot the SRM server.  Validate certificates for new array using following path and command on SRM server -        C:\Program Files\VMware\VMware Site Recovery manager\Storage\SRA\3Parinsrv>               TPDsrm.exe validatecert -s...
Post a Comment
Read more