vSphere 5.0 and 5.5 ESXi cluster

Similar Questions

• Migration of virtual machines to vCD and again in a standard ESXi cluster itself?

  We currently have a relatively small cluster of ESXi (5.0.0 1489271) which uses a dedicated installation vCenter (5.0.0 1300600) and an instance of vCD (vCD 5.1.2.1068441).  Our goal is to move the virtual machines running in this configuration to our standard ESXi clusters (5.5.0 1892794) supported by installation of different vCenter (5.5.0 1891313).

  The instance of vCD seems to add additional parameters to the level of the virtual machine that prevents the VM of to be easily transferred out of the instance of vCD.  What we are looking for is a way to easily migrate these servers on and completely remove the vCD of the equation.  The only details around that we found cause downtime for exports out of vCD can be extended to reason the total amount of drive to the VM and VM level, which we really do not think it is an option to open a window of time to stop long enough to work through this process.

  Did someone went down this road before?  We have approximately 120 virtual machines in the cluster vCD using about 52 TB of disk.

  Maybe we're wrong understand something fundamental about the nature of migration of VMs on the vCD instance, but we have not been able to find many details on what options exist to make this move.  We have spoken several times with VMware support in this regard.  They mentioned a potential tool in the work within engineering migrate vCD to vCAC (which isn't really fall under our goal unless vCAC would then provide a clear path to return the virtual machines to a standard ESXi cluster).

  Any suggestions or ideas are appreciated.

  I am a colleague of GTC and wanted to just sent to our discussion of this topic with the help of VMware.  Basically, we should be able to Setup VMs in vCenter, outside of vCloud Director, pointing them to the same files VMDK and MAC then power off VM vCD and power on VM vCenter.

  : The NASA-EAST region

  Moment of validation: 2014-09-05 11:32 EDT

  Severity of the request for assistance: 4 - low

  Description of the request for assistance: we are looking for ways simple and less disruptive migrate VMS off vCloud Director and vCenter management.

  We have the advantage of a single principle in vCloud, managed by a vCenter and the network configuration is simple with no VXLAN.

  What are the problems with the realization of the following?

  vCD 5.1 is managed by vCenter 5.0, the final result will move VMs in vCenter even

  -Create a new virtual machine in vCenter that points to the same vmdk files as virtual machine in vCD you want to migrate, allocate same configurations of processor, memory, and network (we do not use the vCD with advanced networking)

  -Turning off the virtual computer in vCD

  -Once the vCD WHAT VM is off, power on VM in vCenter

  We must ensure that the VM vCD never gets turned on again and then when we are completely finished with all migrations of VMS in vCenter we abandon vCD.

  Of course there are details to help users migrate to how they use the vCD to vSphere vCenter client web interface or web interface.

  Entry date: 04/09/2014

  Since the opening of the case, I had interviews with several members of VMware support staff and these additional points were added.

  -Configure vCenter VM with the same vNIC driver MAC and like vCD VM vNIC

  -Rename VMDK files to make for easier management, or if not renamed then detach from the propelled out of vCD VM

• Prices (not storage vmotion) vmotion, DRS (Distributed Resource Scheduler) features available in ESXi cluster?

  Prices (not storage vmotion) vmotion, DRS (Distributed Resource Scheduler) features available in ESXi cluster?

  I thought that ESXi is a correct free download?

  Yes and no. ESXi Hypervisor binaries are the same for all editions (free and paid). It depends only on the license key that you have what features are available and if you can add an instance of vCenter server host.

  If you just want to test vSphere, you can sign up for a free 60-day trial (no required license key) during this period, all the features of the 'Business Plus' edition are available.

  André

• A few questions about VMware tools and U2 of ESXi 4.0 and 4.1

  In my workplace, there is a cluster of vSphere 4 six nodes containing 5 servers ESXi 4.0 U2 (4.0.0, 261974) and a server ESXi 4.1 (4.1.0, 260247).  Aparently, it was built that way in the environment concept then deployed into production and now I head for VMware deployment.  This environment is up in producgtion now for over 8 months with this configuration, but starting to be more widely used.  Ideally, I know, we should have all the nodes on the same patch level, but here's the question.

  Models used to get the operating system to the virtual machines in this environment were built on the apparently new 4.1 server using this version of VMware tools (Version 8.3.2 build-257859).  All so most of the running virtual machines, use this version of VMware tools.  Using this new version of VMware tools on a virtual machine running on a server ESXi 4.0 U2 ESXi would cause issues?  ESXi 4.0 U2 servers push version 4.0.0 build 261974 of the VMware tools, identical to the ESXi version.  The status of the VMware tools when the new 4.1 version is running on a host of U2 4.0 still shows as OK and we have operated this way for more than 8 months.

  Another problem is that we have still a few other virtual machines with the 4.0 build U2 VMware tools so when these virtual machines will eventually be VMotioned to an ESXi 4.1 host, VMware tools show as outdated.

  Until we can get of planned downtime to upgrade the servers, it should be like that for several weeks if possible.  We have HL7 interfaces on many of these virtual machines that are not too good with VMotion and being in an organization of health care, sometimes difficult to get downtime.  It is perhaps more possible to downgrade the only host to 4.0 U2 until we can plan time to upgrade all hosts.  I would keep the node in the cluster, even if for the moment, assuming that to release 4.1 with other guests at 4.0 U2 should not cause problems, since we can use the resources of that node in this cluster.

  Until then, ensuring that all the virtual machines in the cluster use the ESXi version 4.1 of the VMware tools (Version 8.3.2 build-257859) would be acceptable?  I just wanted to check that this version should be fully backwards compatible with the previous version of ESXi 4.0 U2, and as I mentioned before, its run like that and have noticed yet all the problems and the status of the VMware Tools also records OK when this new version works on ESXi 4.0 U2 host computer.  I just wanted some feedback from those of the community.

  Thank you

  Exactly, do you VMotion, virtual host 4.1 machine and if necessary would upgrade the VMware tools. To install VMware tools, it is necessary to restart the virtual machine.

  And another option that I say is the first upgraded version of all hosts ESXi4.0 U2 to 4.1, after that, you do an upgrade in the tools of all virtual machines vmware.

  Perfect.

  You´re are welcome!

• Update Server VC and 5.5 ESXi hosts to update 3 b (Build 3248547)

  I'm in vCenter Server 5.5 and 5.5 ESXi hosts.  Both are updated 3A, patched to version 201510001, which is the build 3116895.  I plan the upgrade of update 3 b (Build 3248547) and I'm a little confused on the question of SSLv3.

  I wonder if this point below ESXi55 U3b & VC 55U3b Known Issues applies to my config:

  ESXi does not automatically added to the inventory of the vCenter servers
  If you install an earlier version of vCenter Server and vSphere Update Manager for ESXi 5.5 updated 3B, then after the task of sanitation, ESXi does not automatically added to the VC inventory. Remediation process never gets done and ESXi State of connection in the VC inventory is presented as disconnected. Solution: When you restart ESXi after reorganization process is started, enable SSLv3 on ESXi (which is disabled by default). This will ensure that ESXi is added to the VC inventory automatically in minutes and sanitation as completed.

  If I'm reading things correctly, upgrade to vCenter Server to 3 b first and then upgrade the ESXi hosts, will avoid lost communication problems.  Can anyone confirm?

  It should be good if you update vCenter first.

  The problem is that pre - U3b vCenter 5.5 forces an SSLv3 connection when connecting to an ESXi host on port 443 (not the reverse). It does this, even if the host ESXi and vCenter SSL/TLS libraries actually support TLS 1.0 + since at least vSphere 4.0.

  So when you update one host to 5.5 U3b, the oldest vCenter again will try to force a connection SSLv3 that will fail, since SSLv3 has been disabled to the host. If you're updating vCenter, first of all, it will initiate a good TLS 1.0 + connection to more similar and updated hosts.

  Here is an explanation of the (pre - U3b) vCenter SSLv3 handshake behavior:

  Re: vCenter and host communication SSL v3

• This VM could not become vSphere protected HA and HA cannot attempt to restart after a power failure

  ESXI 4.0 3 running virtual machines.

  600 GB HDD / 8 Gigas of RAM / Xenon QuadCore.

  ESXI 5.5 (I had two).

  Using Raid 01 (1 TB)

  RAM of 64 Gbite

  Hearts CoreI5 Xenon proceso.

  VCenter server deployment with Vmware Storage appliance.

  Problem:

  I've had enough material resources, in fact, I had twice the disk space and memory to four times more in the reception of news

  When migrating virtual machines in ESXI 4 server and get Vcentener turn it on the message "this VM could not become vSphere protected HA and HA cannot attempt to restart after a power failure.  "

  I do not understand because the servers have resources, I can't find what is wrong.

  Should I use another method of migration?

  Once that you have migrated, can solve this problem without re-migration of computers?

  I found this post, but it's no imformation. This VM could not become vSphere protected HA and HA cannot attempt to restart after failure of.

  Thank you

  See:

  Re: This VM could not become vSphere protected HA and HA cannot attempt to restart after a power failure.

• Differences between the ISCSI connections to the storage in vSphere 4.1 and 5.0.

  I'm in trouble of setting up the connections of storage in a new VSphere 5.0 test environment. In our environment VSphere 4.1, it was possible to create a virtual switch add two Broadcom NetXtreme II 5709 NIC. Set assets. IP Hash value as load balancing. (LACP Etherchannel on physical switches) This configuration uses a grain port and a single IP address. Then add our NetApp NFS storage and ISCSI Equillogic storage. In VSphere 5.0, I can't create this same configuration. I have to create separate with separate IP addresses vmkernal ports? The idea was to have redundant connections to the storage and flow of these two NETWORK cards. Possibly adding additional if necessary to the futuer NETWORK cards. Any help with this would be greatly appreciated.

  How can I work around this:

  "VMkernel network adapter must have an active link exactly and no waiting rising to be eligible for the iSCSI HBA connection."

  I can certainly say that the way which allows you to configure the iSCSI Multipathing is incorrect.

  The main idea is to let Native Multipathing Plugin to decide what network path to choose, not the vSwitch.

  At the level of the network layer, you must have 1 VMK by a physical NIC.

  This technique applies as well for vSphere 4.1 and 5.0, but with the 5.0 it is configured easier and more quickly.

  Here's a very brief consequence of steps

  1. get 2 VMK interfaces and assign an IP by each VMK.

  2. set each VMK to use only one physical NETWORK adapter

  3 GB with storage iSCSI software adapter, turn it on and bind your VMKs 2.

  4 connect to your iSCSI storage space

  5 rescan devices, create the VMFS datastore

  6. set the desired load balancing VMFS method or just set up a prior default create new VMFS

  and it is strongly recommended to read this guide - http://pubs.vmware.com/vsphere-50/topic/com.vmware.ICbase/PDF/vsphere-esxi-vcenter-server-50-storage-guide.pdf

• Stand-alone Microsoft en ESXi cluster?

  Señores,

  Consulta, tengo than present a proyecto donde want tener los servicios Exchange, in total 6 VMs son y me preguntan lo siguiente:

  Option 1: ESX, x-axis storage, 2 HA, vMotion etc...

  Option 2.2 ESXi, con Microsoft cluster. (6 cada ESXi virtual machines)

  SE supone than the option 2 the advantage that're avatar.3D.DVDSCR.XviD el shared storage is las licenses VMWare, pero nunca he created Microsoft en ESXi cluster, eso possible? good works? y los tienen experience, which would be los contras of the option 2?

  MUCHAS gracias por su ayuda.

  Saludos,

  JLF

  Hola JLF,

  Option 1:

  • Advantages: Dispones las caracteristicas HA y vMotion. Con una license essential MORE than permite 3 hosts + vCenter todo lo that need dispondras. SOLO have Québec usar 6 licenses for Microsoft Windows Server.

  • And/or: TIENE TIEMPO DE PARADA, that al is not a las-ser cluster UN VMs need that arrancar in another host desde cero.

  Option 2:

  • Advantages: TIEMPO DE PARADA ERO, are al ser a cluster estan causa x-axis cual are known estado is the TR algun host espera to hacer los recursos cargo has.

  • And/or: Para maquinas 6 en cada necesitaras host a total of 12 licenses Microsoft Windows Server ENTERPRISE data CENTER o, además las VMs in ESPERA have consumiendo recursos a espera of Quebec sean've o no una caida. Respond to the environment, having as optar por usar RDM tambien Mayor has the publicar los almacenamientos hora.

  Respecto what indexes del has storage of into account that en both soluciones ser shared, are only a comparte el storage cluster ha y VMware para poder hacer HA y tambien comparte storage vMotion, of hecho VMFS is considered a cluster ficheros sistema.

  If is pueden enabling una parada menor a 5 minutos optaria por the opcion approximately 1, is what is mas economica y knew operation will be bastante bueno. Por lo contrario, if no can divertir parada del servicio have Québec ir has the option 2 y mas perras in todo lo necessary price.

  Here you have several documents that may be of interest.

  http://communities.VMware.com/docs/doc-13275

  http://communities.VMware.com/docs/doc-13273

  http://KB.VMware.com/kb/1004617

  A greeting.

  -

• How to create ESXi cluster or team two ESXi servers to avoid VMHA of HA?

  Hello world

  The scene is, I have two machines Dell 2950 and want to install ESXi U4 or ESXi 4 on both machines.  The requirement is that I have to install Windows 2 K 8 Server as guest and installing MS SQL Server inside on HOST1 (for example). This will be a production server.  Now I want the APP or database on this to be highly available.  I can mirror whatever say who's here to HOST1 on another machine HOST2 and keep it to fail the course in time REAL.  OR can I team or bonds or group these two hosts using local storage (data warehouses) and without the use of third-party storage (I can't afford VMHA, because it involves SAN and SAN or NAS in turn need fail on).

  In simple terms, the creation of ESXi cluster or team two ESXi servers to avoid VMHA of HA?

  TIA for all your contributions.

  -Nadine

  VnonCP

  Try Openfiler or FreeNas?

  Both will allow you to use the local storage on your ESX as an NFS share.

  Problem is that if your ESX host plant... you have a data store that is dead.

• VCS 'OLD' device and device New VCS cluster "(CE500)" ""

  Hello.

  An easy question, can you do a VCS cluster between the 'old' and the 'new' device? is there a limitation?

  In the prerequisites, I saw some VM 8 hearts, but do not understand a lot.

  Thancks! An optimal day

  Hello Alex.

  As long as the VCS platform is the same (physical or virtual) and running the same versions of software and complete you the prerequisites.  See Maintenance and creation of VCS Cluster Deployment Guide for more information.

  The part on the cores is related to your virtual deployments, so if you use virtual VCS, he wants to make sure that you use the same size of deployment noticed on pg 4 of the installation Guide for the VCS VM.  You don't have to worry about this with the hardware appliance.

• How to run Qemu and KVM on ESXi?

  Team,

  Can someone please guide me: how to run Qemu and KVM on ESXi?

  Thank you

  John

  Follow please: http://www.virtuallyghetto.com/2014/09/how-to-run-qemu-kvm-on-esxi.html

  Thank you

  Venance

• The path 'Administrator@VSPHERE.LOCAL.log' and 'noUser.log' in VCENTER 6.0

  Hi all

  I have deployed the plugin in vcenter 6.0 and it is deployed successfully.

  I found the diary of the Virgin in C:\ProgramData\VMware\vCenterServer\logs\vsphere-client\logs.

  But I could not find "[email protected]" and "noUser.log" where my plugin will record all the problems.

  Kindly help me.

  As far as I KNOW vsphere_client_virgo.log contains everything.  Check out server/configuration/serviceability.xml where you can reactivate user logs.

• Please mention even small and large difference in features vSphere 5.1 and 5.5 of vSphere.

  Friends,

  Please mention even small and large difference in features vSphere 5.1 and 5.5 of vSphere.

  His advantage and advantage tell.

  Concerning

  Sirot

  I would recommend you read http://www.vmware.com/files/pdf/vsphere/VMware-vSphere-Platform-Whats-New.pdf to find out what is new, and that these features are important to you.

  André

• Fedora 17 office is different under VMware vSphere 4.1 and Workstation 8.0.3

  Fedora 17 office is different under VMware vSphere 4.1 and Workstation 8.0.3

  http://Forum.ICST.org.tw/phpBB/viewtopic.php?f=16 & t = 26288 & sid = 523862dca09b4cf69f52bf9dfdd76086

  Hello

  I'm sorry but I don't understand the position, but if I'm right you wonder why the office are different.

  It is simply because the desktop 8.0.3 Fedora 17 can start the new interface of Gnome 3, on vSphere 4.1, it can be started and Fedora will then be restored in "compatibility mode".

  HTH

  Giuseppe

• vSphere 4i? and 4?

  Hey guys,.

  I noticed, vsphere 4 versions and 4i, I guess they're on the lines of 3.5 and 3.5i the latter having does not access the consoles and the smallest footprint.

  I thought vmware away from 4 and was moving in foot print smaller version the 'i' (Please correct my jargon here)

  Is it wise for me to load the host 3.5i with 4 4.5i (upgrade)?

  Please advice

  RJ

  We will all live a virtual life...

  Here are some links worth visiting

  http://KB.VMware.com/kb/1006543

  http://KB.VMware.com/kb/1010579