Disassembly of cluster 5.1 ESXi

Similar Questions

• SQL Server 2008 R2 taken Failover Cluster support in ESXi 6?

  Hi guys

  I think that it is based on the many articles of MS and VMWare I was wading in but did anyone have knowledge if a SQL Server 2008 R2 failover cluster is supported on ESXi 6?

  I think we have to run on a Windows Server 2012 R2 operating system unless we are forced to stick with Server 2008 R2 for reasons of inheritance

  Thanks for the tips

  Simon

  Yes, have a look here: VMware KB: Microsoft Clustering on VMware vSphere: guidelines for supported configurations

• Cluster 2008 question ESXi 3.5

  Our installation program.

  Two ESXi host with vCenter.

  Four windows 2008 with the installation of SQL 2008 in a 2-node failover cluster. If two windows 2008 in a cluster and two Windows 2008, in a second cluster using MSCS.

  We aren't vmotion, HA, or any other grouping of VMware or failover but relying on windows MSCS.

  I'm trying to configure the above using ESXi 3.5 update 4 but ran into some concerns read on this. The main problem is the software cluster in a VMware environment stipulates: "Windows 2008 failover cluster will work only in ESX4 (lack of reservation SCSI3 in ESX 3.x)."

  This applies to Windows MSCS or just the VMware HA?

  For cluster Windows 2008 with SQL can I use ESXi 4 in order to have the vmware to handle? I guess I can use the Windows iSCSI initiator to connect to shared drives and it will work?

  I'm on a strict schedule, so I hesitate to switch to ESXi 4 right now so I'm leaning towards just try using Windows iSCSI.

  Thanks for any comments.

  Post edited by: TheTechie

  Currently, you cannot build a failover cluster Windows 2008 on ESX 3.x, using the documentation for VMware (vmdk shared of cluster in a box), or RDM for other cases.

  You must use ESX 4.x.

  Or use the software initiator to point directly to Windows 2008 to shared storage.

  Or use NPIV to directly connect a FC LUN share.

  André

  * If you found this device or any other answer useful please consider awarding points for correct or helpful answers

• Penetrating VM from ESX Cluster stand-alone ESXi Server

  I get an error trying to move a virtual machine of cluster VI in a standalone ESXi Server, someone had a bit of luck this?  I tried the following: Get-VM-name "CO-WS-TEST1" - location (Get-VMHost "CO-WS-TEST1"). Move-VM - Destination (Get-VMHost "CO-VM-TEST2") where CO-VM-TEST2 is a stand-alone ESXi server and CO-WS-TEST1 is in an ESX Cluster with VI.

  I get the following error:

  Get-VMHost: 2009-04-13 13:08:08 Get - VMHost VMHost with the "CO-VM-TEST2" name not found, using the specified filters.

  On line: 1 char: 60

  + Get-VM-name of the CO-WS-TEST1 | Move-VM-Destination (Get-VMHost & lt; & lt; & lt; & lt; "CO-VM-TEST2")

  Move-VM: cannot bind parameter 'Destination '. Could not convert "" to "VMware.VimAutomation.Types.VIContainer".

  On line: 1 char: 48

  + Get-VM-name of the CO-WS-TEST1 | Move-VM-Destination & lt; & lt; & lt; & lt; (Get-VMHost "CO-VM-TEST2")

  Thanks in advance for any help you can give me.

  What is ESXi system managed (for example with a non-free full license) by your vCenter?  If this isn't the case, then you can not make a gesture like this.  You can probably fake it with enough script and help of some external tools to make disk copy.

  [vExpert |] [ http://www.vmware.com/communities/vexpert/], PowerShell MVP, moderator of the VI Toolkit forum

  Author of the book: VMware Infrastructure Management with PowerShell

  Co-host, PowerScripting Podcast (http://powerscripting.net)

  Need help in General, other than VMware PowerShell? Try the PowerShellCommunity.org forums

• Nodes of Cluster ESXi 5.5 with different MTU

  Is a good idea for an ESXi cluster 5.5U2 to have nodes at different units MTU on their vSwitch?  No. VM or VMKernel interfaces are the MTU = 9000 value, only the single vSwitch (vSwitch0) is set to MTU = 9000

  We are currently adding new nodes to an existing cluster 5.5U2 ESXi and set the vSwitch MTU = 9000 to allow frames extended on new nodes, but the existing nodes have MTU = 1500 (default).  The objective is long-term, all nodes vSwitch0 value MTU = 9000, but before this can happen there vMotion all the virtual machines on the existing nodes of ESXi in making the adjustment.

  Yes, it's ok.

  If you use the standard, turn on to do manually on all nodes and if you use distributed switch then you can substitute the single point through the command line or GUI.

• Query - moving from ESX 4.0 (cluster) to ESXi 4.1 (cluster) license

  Hi all

  Am very new to VMware, please bear with me.

  We have in our existing Production cluster, consisting of three (3) 4.0 ESX servers and the intention is to replace them with ESXi 4.1 (U1) (under license).

  The plan should gradually slide each ESX 4.0 Server and install ESXi 4.1 (U1) of an image from HP directly on top.

  No drama it (?), but what about the licenses...

  I have a few questions I have to date not been able to acqurie myself.

  1. With each of the VH in the Production cluster, are we able to move a server in the cluster, upgrade to ESXi 4.1 and go back to the same cluster?
     
     
  2. If NO to question 1, which would be the recommended upgrade path where there is one (1) cluster, three VH (currently ESX 4.0) and we replace with ESXi 4.1 (U1).
     
     We have x 1 vCenter Server Foundation 4 license and three(x3) vShpere4 licenses advanced.
     
     Must these licenses be updated too?

  Am deparate to find answers to these questions.

  Kind regards

  Cameron

  HI - welcome to the community.

  The answer to your question is YES - you can re - allocate your ESX 4.0 license to your hosts updated. the license is generic and can be removed from a host and added to the other using the License Manager.

• ESXi underperformance of the r.620 vs R610

  All,

  I currently run a server R610 (X 5550 procs) and a unit r.620 newly acquired (e5-2650) unit in a vSphere cluster 5. ESXi running the latest version and the latest patches. Dell servers up-to-date with respect to the firmware of all components. The unit uses internal 15 k SAS R610 leads to host the ESXi hypervisor, while the r.620 uses 2 GB SD cards in mirror for the ESXi hypervisor.

  When I migrated some workloads on the new cluster member (r.620), I've seen some of our process execution times increase dramatically. The process performed on a MS SQL 2008 r2 server. When I migrated the VM on the initial cluster member (r610), execution time is back to the normal time.

  I went then to face a series of landmarks a test virtual machine that has been migrated back and forth between each Member of the cluster and seen repeatable results that showed that the r.620 was SLOWER than the R610 in terms of CPU and memory benchmarks (using Passmark v7.0). Cluster using the EVC Nahalem mode. I have also conducted tests by removing the VCA mode and was able to get similar results with the R610 being the fastest performer.

  I checked all the cores and hyperthreading is enabled. A glance at the guide of best practices for ESXi 5.0 gave anything different in my setup...

  Has anyone seen or heard talk about these issues with the r.620 unit, or E5-2650 processors?

  Thank you

  Elvis

  We had the same problem with our new r.620 (2650v2-E5). The performance was well below our old R710 (X 5550).

  We could solve the problems of performance and to maintain a good ratio of energy saving dig by adjusting the profile' system settings ' in the BIOS:

  

  Stone

• ESXi network redundancy

  Hi all

  I would like to ask a few questions about my design of the network.

  I use the small DELL blade solution. (Dell VRTX).

  Currently, we have two servers with essential M620 HA cluster installed with ESXi 5.5 blades more license.

  I have decided to dismiss more my network configuration.

  Each blade has two ports 10 GB switch LOM connected internally (module e/s inside the chassis of the blade) and also connected 2 ports PCI network cards.

  As an attachment, you can find my layout of network design.

  EXPLANATION OF THE LAYOUT

  *********************************

  NIC1, NIC2 = LOM

  NIC3 NIC4 = PCI CARD

  NIC1 + NIC3 = kernel Ports (NIC 1 - standby adapter)

  NIC2 * NIC4 = Standart (NIC2 - Standby adapter) ports

  VSWITCH1 = used for V-MOTION, MANAGEMENT, NETWORK (same as our network LAN, VLAN7)

  VSWITCH2 = branches with 3 MPLS network VLAN

  CONNECTION of RED = traffic vlan 7 geocoded

  CONNECTION BLUE = trunk (VLAN1, 2, 3)

  CONNECTION GREEN = trunk (VLAN 1,2,3,7)

  BB is two stucked switch node.

  I would like to ask if my drawing is correct.

  Thanks in advance

  Hi Roman,

  First of all, I would be divided management and vMotion traffic VLANS separated. I've seen some process of vMotion goes wild, I like to keep this seperated ;-)

  Thus, you could use NIC1 to management, with NIC3 mode sleep for this and use NIC3 for vMotion with NIC1 pending.

  Secondly, I recommend you to use NIC2 and NIC4 in active/active mode, if you use the second card for the VM network traffic load balancing and not to waste it in fashion watches.

  See you soon

  Tim

• Retiring legacy 4.1 ESX cluster

  
  Hi all

  We currently have two clusters managed by a single server vCenter.  It is the most recent cluster 5.1 ESXi and the other is the legacy ESX 4.1 cluster.  We have already migrated all of our virtual servers to the new cluster 5.1 ESXi.  The ESX 4.1 cluster legacy has no more any virtual server in it.  Existing ESX 4.1 cluster hosts will not be reused.  Data exported to the existing cluster warehouses also won't be necessary and in storage arrays are deleted.

  I would like to know what are the appropriate steps to remove the ESX 4.1 cluster legacy?

  Thank you

  Soraya

  Here is a guide on best practices to remove LUN with the vSphere data store: best practices: how to properly remove a unit number logic of a host ESX - VMware vSphere Blog - VMware Blogs

  In any case, if the unit number logic/data store used by the hosts to version 4.x are not accessible from the hosts to 5.x, you can simply delete the host to vCenter and the data store will be deleted too without impact to the hosts to 5.x.

• Should the RAM for an ESXi host replaced the same ones remaining?

  Hello

  We are running a cluster of servers ESXi 5.1 - 2 of them are Xeon E7440 2.4 GHz (64 GB of RAM) and 1 of them is Xeon X 5460 3.16 GHz (32 GB of RAM).

  Currently, the use of the memory of all three ESXi hosts are about 60%.

  We will replace the Xeon X 5460 server with a new physical server.  We would like to ask for your opinion how much RAM you must order (my manager of door on the cost of the new server).

  Thank you

  Hi again Tony,

  1. No, it is not high at all. You should begin to worry about this, after reaching approximately 85-90%.
  2. My short experience with clusters of memory-unbalanced, adding that more memory would be a lot like the DRS manages memory locations & 'kindness host' in the right direction, but I'm not really sure how that would turn out in the long term. If you decide to present more memory to your server, it would be possible to upgrade the other two guests sooner than later
  3. Yes, ask the seller would be the right thing to do. Please note that you will need to put in place an enhanced vMotion to conform to your next "older" CPU then, because you'll have something other than X 5460. I guess you'll have to "intensify" a generation or two, depending on what you have found.

• VM doesn't qutoboot upward after the restart of the ESXi host

  Hi all

  I environment, there is only a single Cluster. The Cluster has an ESXi host. all virtual machines including vCenter VM are resides on the ESXi host. When I reboot the host can all VM does not start?

  For comparison, there is a different environment, there are two Clusters (Cluster 1 and Cluster 2) in vCenter, Cluster 1 has two hosts ESXi Cluster 2 has only a single ESXi host. vCenter runs on the ESXi host residing in Cluster1.

  When I reboot the host residing in Cluster2, all virtual machines may start automatically.

  is that any expert can explain the difference? Why single environment can auto boot VMs when both of these environment has a host to the Cluster and cluster activate HA service?

  environments are executed at the ESX5.5.

  You will need to check the box allow VMS to start and stop automatically with the host system and then change the setting on the edit tab, and mention what needs to be done for each machine.

• go esxi hosts and virtual machines in one vCenter to another

  I built a new vCenter (Windows vCenter), I intend to move on ESXi hosts the old vCenter (Virtual appliance vCenter) to the new vCenter. I don't know if it's feasible, please notify my step is correct or not: 1) build a new vcenter 2) create a cluster with two esxi hosts first 3) Mount data (NetApp Filer Storage) to the new vCenter warehouses 4) add an empty host for the new vCenter VMs) 5 download then upload to the host in new vcenter

  Hi friend

  Its doable without any problem.

  Please follow the procedure below.

  1 build a new vCenter (your first step is correct)

  2 creating a cluster (because it is new vCenter there will not be any available host.) That is why cluster creation wizard will not get to add in the new cluster host). While initially empty cluster would be created.

  3. once the cluster is created, immediately do a right-click on the cluster and add your hosts one by one. Not necessary to cancel the registration and the VM. Virtual machines will automatically be added who were there on the data store available with all guests.

  Don't forget,

  1. we do not mount any store data in vCenter, we assemble the data store on the host.

  2. If you mount the new data store (which did not exist before), you can mount once the new hosts are added to the new cluster. (Your SAN admin help)

  3. If you want to move your virtual machines from data store before the newly added/mounted data store, please SVMotion these virtual machines (by right-clicking on the VM > migrate > data store > select the data store that is new)... Please follow the same procedure for all virtual machines.

  4. you don't need to add empty hosts to the new cluster, add just as soon as all guests without you register VMs. Later, you can migrate to other store of data according to the requirement. NO need to download or download the VM.

  5. Please make sure that your ESXi hosts will be compatible with the new vCenter. Old version of ESXi always compatible with the new version of vCenter. Just check if you have all valid licenses.

  Please let me know if you need any clarification

• Nested ESXi 5.5 lab for the SRM demo with iSCSI

  Hi all

  I was wondering if it is possible to install ESXi in ESXi 5.5 5.5 make recovery of the Server Tier - 1 Microsoft with Site Recovery manager?

  So level 1 server applications are: Exchange Server, SQL Server, SharePoint Server and AD DC servers with 5 x test Win 7 desktop.

  The external data store to the VMFS will take place by iSCSI NAS connected to the physical server.

  Any suggestion and input would be greatly appreciated.

  Thank you

  One thing you'll want to do is to make sure that use you VSphere switches distributed on your cluster nested to ESXi hosts so that you can use the network i/o control (NIOC). For me, I put iSCSI to high priority traffic and everything to normal priority.

  With the help of the NIOC will allow your cluster nested in order to operate more fluidly than without it.

  My SRM 5.x laboratory is fully nested - probably not supported in a production environment where supported VMware should however.

  Here's a blog post of Ather Beg on its results by using the nested NIOC and ESXi hosts - it is the reduction of the spikes that Ather blog article shows that made work nested ESXi hosts networks so much better:

  http://atherbeg.com/2014/02/04/why-enabling-NIOC-network-IO-control-in-a-home-lab-is-a-good-idea/

  Datto

• ESXi 5.1 status host HA is showing that the election

  Hello

  I have a node 4 ESXi 5.1 HA and DRS Cluster. Recently, I replaced all these hosts SSL certificates and prior to this activity, I had turned off the AP. Now, after replacing the hosts SSL certificates - when I am allowing the PA on the cluster, 1 single ESXi host is projection status of HA - ' Running (Master) and rest all three hosts are 'Election' HA status.»

  Tried to re - install the HA agent on the host, but issue still persists. Also tried the re - configure the AP on hosts ESXi, deactivation and activation of AP on the cluster, but no luck.

  Can someone help me for that to be resolved.

  Thank you

  KC

  Hi all

  Thanks for all your response.

  Problem is solved without the help of the HostReconnect.pl script. I followed the steps below and now all ESXi hosts demonstrate normal HA status.

  (1) put the host in Maintenance Mode. Unplug and remove from the vCenter server.

  (2) restart the management through DCUI Agent.

  (3) uninstalled the HA agent using the command line.

  (4) add the host to the Cluster.

  5) out of Maintenance Mode.

  By following these steps - correctly configured the AP on all four ESXi hosts. Now a single host is show as master and rest three hosts are displayed as slaves HA status.

  Kind regards

  KC

• Upgrading ESX 3.5.0 build 110268 ESXi 5.1 or newer

  I need to upgrade our current VMware ESX 3.5 cluster for the ESXi 5.1. To summarize the migration, we will use all of the new materials for vsphere 5.1 5.1 ESXi and new iSCSI SAN.

  Existing/current cluster environment (about 44 vms) is as follows:-vcenter (version 2.5) (1) and (3) dell servers to ESX 3.5 for a total of 4 servers, storage Fibre Channel EMC CX 300.  We went ahead and bought 4 new Dell servers and storage iSCSI, SAN Compellent Dell to replace the current environment.  The only difference is that the NEW strorage for cluster 5.1 will not fibre channel, but will rather iSCSI.

  I read a few post regarding similar improvements which I have summarized, but I'm a little unsure of how to proceed in particular relative to the storage side, (cluster running FC and iSCSI for new cluster).

  1. install Vcenter 5 on of the new material/vcenter Server

  (A) disconnect all ESX 3.5 knots of vcenter 2.5 and plug the new Vsphere 5 and set up the cluster

  (B) connect all new ESXi 5.1 nodes to the new vsphere 5 for the new Vsphere 5 cluster will contain all of the new and the old 3.5/ESXi 5.1 ESX servers

  -This is where I am confused.  My plan is to have the new cluster 5.1 vsphere manage guests to vmotion ESX 3.5 and ESXi 5.1, the old 3.5 ESX virtual machine in the new 5.1 ESXi.  Can I add new nodes 5.1 ESXi or ESX 3.5 to the new cluster 5.1 first, or that matter which node I add first?  Also, the new 5.1 ESXi hosts should have access to FC storage that the old ESX 3.5 has access to?  In other words, the new and old ESX/ESXi hosts would need to have visibility to the FC SAN for vmotion, right?  I do not know if I can add the ESX 3.5 and ESXi 5.1 to the new cluster if not all guests have access to the old CF storage?

  2. through ESXi 5 knots ESX 3.5 virtual machines using vmotion

  3. plan downtime for virtual machines and upgrade virtual hardware (use of snapshot before you upgrade upgrade goes bad snack)

  4 use storage vmotion to move vm data warehouses to the new iSCSI SAN

  Introduce the new iSCSI LUNS to the new cluster and make a storage vmotion to move storage vm of FC SAN to the iSCSI SAN.

  Thank you in advance, all the tips

  Who should do -