Moving VMware Host between Clusters

I've got 16 ESXi Server.

New 9 ESXi Servers (5 for Server Cluster and 4 for Workstation Cluster) running as production currently.
Old 7 ESXi Servers (5 for Server Cluster and 2 for Workstation Cluster) and Workstation Cluster is running as production currently. Server Cluster is for backup purpose.

One day I've to remove for 5 ESXi Servers of Server Cluster to make free space of Server Rack for new server increment setup.
But the problem is those old 7 ESXi Servers are located on two rack and some more is two servers from two clusters are located on separate RACK.
So, I've got to move those server to be in same rack and same cluster.

Below are my experience of moving VMs and Host between clusters for reference for who might encounter like me.

Moving host got two method.
1) moving vms from that host and moving the intended host from cluster to cluster by drag and drop with maintenance mode.
2) moving vms from that host and disconnect it from current cluster and re-connect to other cluster without going through maintenance mode. But this method more complicated and more steps to carry on than method 1.
So, I've used method 1 for easy going of my day to do this. But I'll write about method 2 also if got convenient time.

OK. Let's start!
First of all, moving running VMs to other host before entering to maintenace mode for the host that planning to move to other cluster.
Take a closer look at on Screen-shots for details.

Once all running VMs on that host moved, enter it to maintenance mode.

After the host into Maintenance Mode, select it and drag and drop to other cluster that you plan to move then.

Exit host from Maintenance Mode when moving to other cluster has successfully done.

That's it.

Now one host from Server Cluster to Workstation Cluster has been move successfully ( in my case moved from Rack 1 to Rack 2 also).

Next will be moving host from Workstation Cluster to Server Cluster.

OK. Hope you get what you expected from this post.

May you all be happy.
(Be knowledgeable, pass it on then)

Comments

Fortigate guide for Begineer - 6

I would like to explaine how to troubleshoot the Fortigate Unit configured by Transparent Mode in step by step this time. Let's assume, you have one Fortigate Unit that configured as Transparent Mode. But devices from Internal/Private Network unable to access Internet/Public Network through your Fortigate Unit. OK. Let's troubleshoot with following steps, 1) Check the physical network connections between the network and the FortiGate unit, and between the FortiGate unit and the Internet. 2) Check the router and ISP-supplied equipment to make sure it is operating correctly. 3) Verify that you can connect to the internal interface by connecting to the management IP address of the FortiGate unit from the Internal network. From the internal network, attempt to ping the management IP address. If you cannot connect to the internal interface, verify the IP configuration of the PC and make sure the cables are connected and all switches and other devices on the network are powered on a...

Why do we need network virtualization?

We need to think about Server Virtualization first if we want to talk about Network Virtualization. In the era of cloud computing, servers are virtualized and used in Data Centers. We are facing a lot of problem when we virtualized our Servers, 1) Routing and Switching Problem Routing become the issue when we create Virtual Switch and VLANs according to production requirement. Network Team might need some time to change on their end to meet with Server Virtualization Team changes on their end. ၂) Firewall Services Physical Firewall are difficult to manage due to the large number of rules needed to satisfy business requirements. New applications, new projects, and new networks all come with potential security requirements, which impact centralized firewall management. ၃) Load Balancing Let's say your company deploys a new physical load balancer for each tenant, resulting in increased capital expenditures. Once a tenant reaches their maximum capacity, it ca...

Link Aggregating with Synology NAS and Cisco Switch

I’d like to share how to setup Link Aggregating between Synology NAS and Cisco Switch. I’ve got one Synology NAS with 4 Network Ports and I’m going to use 2 of them. Both Network Port to be as one Logical Link, Fault Tolerance and Load Balancing. To do that, I need to configure Link Aggregating on Synology NAS and EtherChannel with LACP on Cisco Switch. Below is brief steps to do to meet with my requirements. - Get connected Synology NAS and Cisco Switch as shown in picture. - Bonding two Network Ports of Synology NAS and assign IP Address - Configure EtherChannel with LACP in Cisco Switch and add two physical ports as Member. OK. Let’s begin from Synology NAS. - Login to the Synology and go to Control Panel>Network>Create>Create Bond - Select IEEE 802.3ad to get Fault Tolerance and Load Balancing Featureyou’re your switch not support 802.3ad you can only select Fault Tolerance only feature). After that click “Next”. - Choose the network port f...

ICT for Myanmar in English

Search This Blog