vSphere 6 - requires NSX?

Similar Questions

• Host profile in vSphere 6 - requirements of Maintenance Mode

  I was instructed to check the profiles of the vSphere host 6.  The main reason why we don't use them in our environment v5.5 is because when you apply the profile of the host a host to perform a restoration, regardless of change in a significant way, there must be a maintenance of the host mode.  This poses an administrative challenge in my environment.

  So, I have been instructed to read that vSphere 6 had updated Host Profiles to demand maintenance mode only if required by the properties defined by the profile of specified host.  I think OK, now trivial changes like adding that a group of ports for a vSwitch will not require the host to be maintenance mode trying to "clean up" the host with a profile of the host that makes this type of low level change.  Unfortunately, I still get the error "host must be in before maintenance mode a host profile can be applied to him" whenever I try to apply a profile of the host to a host that is in non-compliance, no matter how tiny change.

  Everyone knows this?  I have something misconfigured?

  vSphere 6: updates to Host Profiles - VMware vSphere Blog - VMware Blogs

  OK I thought about it.  This new feature to Host Profiles fact exist, but it only exists in the Web Client vSphere.  The vSphere client c# don't has not been updated to behave this way, it always requires a host to be in the mode of maintenance for all corrections.

  Time to start using the web client more.  = S

• Confirming that vsphere 6 requires flash and does not support a customer to RHEL6/firefox?

  Hello

  My reading leads me to conclude that vsphere 6

  1. always requires flash

  2. can't access customer to RHEL6, either native one or through firefox

  Is this right?

  Thank you

  Hi mips,

  Yes, 'officially' the vSphere Web Client 6.0 does not support the RHEL6 and requires flash to operate. However the following may be of interest (even if it is for 5.5): KB VMware: cannot open the vSphere 5.5 Web Client in a browser on a Linux-based desktop

• What are the material and the vSphere license requirements?

  I searched the net and I can't get a clear answer...

  Should I x 64 hardware to run vSphere?

  My ESX3 low-income countries work on vSphere?

  Thank you

  II

  Yes, you need 64-bit hardware to run ESX 4.0-

  You cannot use the licrnses directly, but if you have Service and active support on your ESX3 licenses your will can update the license ESX 4 licenses.

  If you find this or any other answer useful please consider awarding points marking the answer correct or useful

• vDS now comes with the NSX for vSphere

  Hello

  I found a few kb articles saying that we can use vDS on any edition of vSphere with the NSX.

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

  • If you are using VMware vSphere 5.5 update 3 or vSphere 6.0.x, NSX VMware vSphere 6.x does not require a license of vSphere Enterprise Plus and can run on any edition of vSphere.

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

  • Note: vDS is now delivered with NSX to vSphere (NSXv) and VMware Virtual SAN (VSAN) in vSphere 6.0.

  
  

  I've implemented the vSphere environment with the standard license and NSX for vSphere with the license of the company.

  But I can't use vDS. If I can create new vDS on vCenter, I can't add hosts with standard license to a vDS.
  

  
  

  I used below products.

  
  

  • ESXi 6.0.0
  • vCSA 6.0.0.
  • NSX for vSphere 6.2.1

  
  

  Have someone at - he tried vSphere standard with NSX license ?

  If I could, might have some tips?

  Any kinds of comments would be greatly appreciated.

  Thank you

  Danne

  Thank you. In this case, I think you're right. I have not tried specifically because I rarely see Standard.

  Please open an SR for support can examine why this is happening. Sorry I can't be more help.

• What are the free ESXi / 5.1 vsphere Hypervisor hardware required / restrictions?

  Situation: I'm going to update a few web servers where I am currently under the free version of ESXi/vSphere 4.0.  When 5.0 was released, I decided to not look at new versions of VMware because of the restriction of vRAM and either run an earlier version or something.  I came across a post that says 5.1 license was different and stopped by the page 5.1 and read this http://www.vmware.com/products/datacenter-virtualization/vsphere-hypervisor/requirements.html who actually reads differently.

  Questions: am I correct in my understanding of the restrictions for 5.1 are:

  1. 32 GB max RAM PHYSICS?  (It's a big change from 32GB vRAM).

  2. no limit on the number of CPUs or cores?  (This is a big change of physical processor 1 up to 6 cores max.)

  Thank you!
  

  PS: If the only real limitation is now 32 GB RAM virtual, VMware made a good shot.  I'm not the skin to VMware, so I think that physical 32 GB is perfect.  There is still only so much you can do in the 32 GB, but there is not the complexities of licensing.  The restriction of vRAM was impassable.  Server purchase is unnecessarily complicated by restrictions of socket and core.  This means that I could buy a standard speed core 8 or 10 cheaper XEON or use an older multiprocessor machine instead of an expensive high-frequency 6 core with hyperthreading.

  1. 32 GB max RAM PHYSICS?  (It's a big change from 32GB vRAM).

  Yes that's right FREE esxi supports maximum 32 GB physical RAM can only

  2. no limit on the number of CPUs or cores?  (This is a big change of physical processor 1 up to 6 cores max.)

  No Yes No limit on physical CPU or cores

• vSphere replication seeding

  Hi guys,.

  Basically the standard way to do a seed must turn off the virtual machine on the source site, make a copy of it and then she picks up on the site of DR to put it on a data store and the replication source site VM instance point to posterity.

  My question is rather than this cant you just use a POS/Veeam backup restore on the target site, itll be a bit outdated and replication of vSphere point to that?

  I take its probably not possible, I'm sure he would have been on the internet somewhere, if not I'm curious as to why not?

  See you soon,.

  Bilal

  vSphere replication requires that source and target UUID drives match. When restoring machines virtual/VMDK POS, Veeam, etc., restored disks get new UUID. You can manually change the UUID of each restored disc, but it's a little heavy. See this FAQ for more information: vSphere replication frequently asked Questions (FAQ) - the current version of this doc has moved to: https://storagehub.vmware.com/#! / vsphere-replication/vsphere-replication-faq

• with vSphere replication to replicate vCenter Server in a VM

  Hi guys,.

  I am trying to find some info on this. I currently have vCenter 5.5 running on a Windows 2008 R2 VM server. I was wondering can I use replication to replicate it in some shared storage for backup purposes, and if I had to lose it could I recover and this and be good to go? He runs a database integrated. or is it as AD/SQL/Exchange and in general you shouldn't use replication or something of the sort for them.

  Also, if I have reproduced on the recovering site, I could pick it up and re protect him using MRS. and migrate to the main site once I had everything back up and restart? Is there a difference if I ran the vCenter device instead of the version of Windows inside a virtual machine?

  My apologies if this has been answered before that somewhere, it just went through my mind randomly and Googling gives me really a lot of results, so if its been answered somewhere, please point me in that direction.

  Hello

  vSphere replication requires vCenter to function, you cannot use VR to protect it that you wouldn't have a way to recover, unless it has been replicated on a different vCenter (whereby it might be recovered, but only inside the other vCenter) or if it has been managed by a different vCenter.

  If you are in the second option, where you have a vCenter management appliance RV, and you have an another vCenter, so yes, you can use RS in this model to protect and auto restore your internal vCenter.

  No difference in the functionality between vCA and windows version of vCenter.

  As for your statement: "or is it as AD/SQL/Exchange and in general you shouldn't use replication or something of the sort for them."

  -vSphere replication supports VSS suspension

  -I'm Okay I wouldn't recommend AD replication (SQL and Exchange or if you can use the built in replication at the application level)

  -If you can not however, most modern applications work very well in a consistent state of crash (VR normal replication) and the rest works with VSS

  Hope that answers your questions

• Windows licensing for vSphere Essentials all Linux virtual machines running

  We offer vSphere Essentials and Essentials Plus of application virtualization on a company that currently has 4 servers that run multiple applications under CentOS. The two products are very good values, providing important functionality at a reasonable cost. Yet, society of the end-user has some resistance to the required cost of Windows Server licenses. There is no Windows servers on this network. Even a minimal vSphere Essentials requires usually 3 Windows Server licenses (for the domain controller, vCenter server, and database server) and a SQL server license. Even when using standard licenses, the total cost of these is higher than the cost of the essential elements of vSphere. Other people deploying vSphere Essentials on Linux-oriented networks are finding ways to use a lower number of Windows Server licenses?

  vCenter Linux would be an alternative in such cases, but this project seems to be stalled.

  Thank you.

  Welcome to the community,

  If you're only going to do the virtualization of servers (not VMware View) the vCenter Server does not need to be a member of the domain, or you need a separate SQL Server for a small environment. The edition of SQL SERVER 2005 Express (included in the vCenter Server installation) is sufficient.

  While a single license of Windows (more CALs) would do.

  André

• Impossible to add Nova deploy clusters at the premiere of VIO

  Hi all

  I try an initial deployment of Violence in my lab, and I can't select a cluster to use for Nova.

  Are there settings required components that must be enabled for the VIO cluster compatible?

  vSphere 5.5, NSX, already put in place (although not tested).

  Let me know what I can provide additional information. I have attached a screenshot.

  Thank you!

  Tim

  This problem may be caused by a problem in our beta build 2 - calculation of the nova cluster must be in the area of transport (NSX), so disabled UI groups are not in the area of transport and also to disable the cluster were selected as Cluster Edge.

  We have now removed this restriction.

• Configure HA

  Hi all

  I'm fairly new to VMware and have recently setup a new environment.

  However, we receive these two warnings.

  We have that 1 data store and we do not currently have another network to create a secondary management network.

  "This host currently has no management network redundancy.

  "The number of vSphere HA heartbeat for this host data warehouses is 1, which is less than required: 2".

  

  We have no intention in the near future to get another data store. (I'm not perfect!)

  But we will always have HA between 2 hosts?

  

  

  This is the recommendation to have the redundant network and store data to better serve you. in any case you can escape these message following these parameters.

  "The number of vSphere HA heartbeat for this host data warehouses is 1, which is less than required: 2".

  This problem occurs if there is no redundancy in a shared storage to allow pulsations of data store. From 5.0 vSphere, vSphere HA requires a minimum of two warehouses of common data shared between all hosts in a cluster for heartbeat detection function correct datastore.

  To resolve this problem, disable the HA error message.
  Warning: The resolution removes the error that makes account configuration having insufficient data warehouses heart.

  To turn off the HA error message:

  1. Connect to the vCenter server.
  2. Right-click on the cluster, and then click change settings.
  3. Click on vSphere HA > Advanced Options.
  4. Under Option, add an entry for das.ignoreInsufficientHbDatastore.
  5. Under value, type true.
  6. Click Cluster components.
  7. Deselect enable vSphere HA option, and then click OK.
  8. Wait for all hosts in the cluster, Unconfigure HA, then right-click on the cluster and click Edit settings.
  9. Click Cluster components.
  10. Click Activate vSphere HA.
  11. Click OK.

  "This host currently has no management network redundancy.

  VMware KB: Message of network redundancy when configuring VMware High Availability in vCenter Server

• 6.1.2 no edge.bridging service permissions

  When you try to create a bridge of L2 on a ldr, I get the following error:

  «The user is not allowed access edge.bridging l2bridge03 and the function of object, please check object scope and feature access privileges for the user.»

  My username has the role of business administrator and I can do everything on the ldr but only for layer 2 briding me seems to have no permission?

  Where can I activate the permissions of layer 2 so I can create a bridge.

  Kind regards

  John

  It is a problem experienced with 6.1.2, which will be fixed in the next update - at the same time create the instance of bridge using the API of the NSX a workaround is possible (see pg 139 of the vSphere API Guide NSX).

• ESXi HA and SQL Failover Clustering - resolved

  Dears

  My current environment is

  3 5.5 Esxi with active HA hosts

  Requirement;

  I prepared 2 R2 2012 Windows of the virtual machine and I need to build a node two SQL cluster on them. (with WFCS) and I was reading the article for taking in charge option and discovered I need activation were of affinity

  VMware KB: Microsoft Clustering on VMware vSphere: guidelines for supported configurations

  I got confused and lost on how to enable these options on HA only clusters.

  grateful if someone could share their experience in this regard,

  DRS requires vSphere Enterprise license. This is the reason why it does not show these options in your environment. vSPhere HA requires vSphere Standard edition. As you have the standard version, you are able to configure HA.

  There is NO as such impact.

  1. you use MSCS as a cluster of virtual machines & if anything happens to the clustering configured application, MSCS are switched to another VM in the MSCS cluster.  (I'm assuming you use IPC config. Cluster in a box)

  2 vSphere HA allows you to give an extra level of HA at the host/VM level. As you use your virtual machines to the MSCS cluster on top of guests. vSPhere HA is additional HA.

  3. in the case, host fails, vSphere HA are toggled MSCS grouped all VMs to other available inside the HA cluster host vSphere. That is to say it will restart all virtual machines on the other host. Please note that the restart of a virtual computer will have minimal downtime. In this case, as all virtual machines are on the same host, same MSCS cluster will have same downtime as vSphere THAT HA will have. But if you use CAB (Cluster in the box) as MSCS configuration, you can minimize interruptions of service MSCS VMs.

  4. in the case, VM itself fails (no host), vSphere HA will restart the VM has failed on the same host. In this case MSCS are switched all your app on the other virtual machines in the MSCS cluster.

  You have only vSPhere HA without Drs It should be good. Just as DRS gives you more flexibility.

  Please note that in any HA solution, in case of failure, you will come across with minimal downtime (time may differ across different solution HA).

• Migration of servers to new host and SAN

  Hello

  Current configuration:

  2 x ESXi servers, local storage, share nothing.  License of VMWare Essentials

  New configuration:

  3 x SAN Eqllogic, ESXi servers. Essential Plus VMWare license

  I would like to make the transition to the new configuration with minimal downtime, we have invited a few large (> 1 TB) on one of the servers and I don't want them to be disconnected for more than a few minutes, then a migration cold is out of the question.

  I had a thought that I could put the license key more on the old servers and 1 new servers, set the new SAN on the old servers, use VMWare replication to replicate virtual machines among the old servers to the new server/storage, and then perform a recovery.

  I would then remove this old Vsphere server, add a new server and transfer the license, then perform the same task on the old server to 2nd.

  Once it is finished I remove the old server 2, add the new 3rd server, and move the license.

  Can someone tell me if this is possible, or suggest alternatives?

  Thank you

  Dean.

  Hi Dean,

  Replication (replication vSphere) VMware will be requires downtime when you are recovering from the old host to new host.

  How much time can you afford for downtime?

  The recovery process will turn off the source/protected VM on the current host (VM function how long it would normally take to perform a shutdown comments) and destination/recovery VM will be powered on to a new host (again, depends on VM normally, how long it would take for the operating system and services until then a normal diet on the process).

  vSphere replication requires vSphere Web Client and other requirements, as described here: 5.5 - replication requirements vSphere vSphere Documentation Centre

  You have a vCenter Server?
  What version of ESXi (and vCenter) do you use?

  If you don't have a vCenter Server yet, I suggest you install a vCenter server and add all the current 2 ESXi hosts + 1 new ESXi host.

  From there, you'll have an ESXi 3 host, then you can migrate current ESXi host for new.

  If you are using vSphere 5.1 + you can vMotion, even if the host do not have access to the same storage see this: library of vSphere 5.5 - Migration with vMotion in environments without storage shared

  Its quite simple, if you are using vSphere 5.1 +.

  -Make sure you have vcenter Server 5.1 + with vSphere Web Client

  -Add current hosts + 1 new hosts

  -Make sure the vMotion without requirement for shared storage are filled with VSphere 5.5 Documentation Center - requirements and restrictions for vMotion without Shared Storage

  -Perform vMotion without process Shared Storage of current host to the new host + local storage to SAN EqualLogic - you can start with small VM and VM less critical first if you are not sure.

  -Once all virtual machines have been migrated to the new host + EqualLogic SAN, you can do a maintenance on the current host mode, and then delete the vCenter Server (vSphere licenses will be retrieved)

  -Add the 2 remaining new hosts.

  If you are using vSphere 5.1 prior, you must present the SAN EqualLogic again 1 new host and current 2 hosts.

  Once current hosts can see the EqualLogic SAN, make a Storage vMotion (live migration records) local storage to the EqualLogic.

  For first migration vSphere 5.1, there are 2 ways that I can think of:

  1. with vMotion - without interruption

  There are certain requirements of configuration for vMotion work: Documentation Centre of vSphere 5.5 - Migration with vMotion

  Make sure your classes and new hosts are run in the same processor / EVC mode or matrix, you can check it out here: http://www.vmware.com/resources/compatibility/search.php?deviceCategory=cpu

  If they are on different EVC Mode, you can turn on the CEV on new hosts.

  The steps are:

  S ' ensure that virtual machines are in EqualLogic (you can use Storage vMotion)

  -Perform a vMotion from the current host to new host.

  -Once all virtual machines have been migrated, you can safely do a maintenance on the current host mode and remove the vCenter Server

  -Add the remaining 2 new hosts the vCenter.

  2. without vMotion - requires the interruptions of service commissioning

  It's cold migration but without migration of storage, must be less compared to downtime directly cold immigration to localdisk of shared storage.

  The steps are:

  S ' ensure that virtual machines are in EqualLogic (you can use Storage vMotion)

  -Turn off the virtual machines in the current hosts and migrate (cold) of the host-to-host former New (you can also drag the virtual computer and drop it to the new host).

  -Once all virtual machines have been migrated, you can safely do a maintenance on the current host mode and remove the vCenter Server

  -Add the remaining 2 new hosts the vCenter.

• Disks that spans Source

  If I forward a disc on the VM source, these changes are replicated to the side correct recovery?  I don't have to reconfigure protection or anything?

  In fact, I thought ABR only.

  If you use replication of vSphere, this requires some work:

  http://pubs.VMware.com/SRM-51/index.jsp?topic=%2Fcom.VMware.SRM.admin.doc%2FGUID-5139CC95-65BA-4B0A-B126-780D0FB3215F.html

  Michael.