vCenter & HA issues

Similar Questions

• VCenter deployment issues 6 - domain SSO

  Hello

  I have a problem my head around defining the domain of SINGLE sign-on in my new vSphere deployment package 6.0. I have a domain active directory (server.local) and installing vCenter 6, you are prompted for the SSO domain name (default is vsphere.local). What I want to know, it is important that name and what is the impact of the choice or change default name? The reason for my question is the following:

  1. we have a vSphere/vCenter 5.5 for our domain infrastructure deployment and the application that uses vsphere.local as the domain of SINGLE sign-on.

  2. I am deploying a new environment 6.0 vSphere/vcenter for a new VDI environment.

  3. I will deploy a second 6.0 environment vSphere/vCenter for a second VDI environment.

  4. I will use more connected between two vCenter environment 6 because I want to keep totally separate.

  In factoring, is it safe to use vsphere.local for my first 6.0 deployment even if I use vsphere.local for my production environment 5.5 already? If it is OK, then is it OK to use vsphere.local for both of my 6.0 vSphere deployments, even if all three environments will be authenticating against the domain active directory domain.local? The domain authentication UNIQUE write anything to AD or just authenticates against it so that I can use the same SSO domain in three distinct environments without negative impact?

  Any help with sort my confusion with this would be greatly appreciated.

  Thank you!

  Yes, it is safe to use the same domain name SSO for multiple deployments of vSphere, even if you use the same Active Directory domain as a source of identity. Don't forget that before vCenter 6, you are not able to change the domain name from SSO for anything other than the vsphere.local and this has never been a limit to how many vCenter Server can be deployed and configured to use the same Active Directory domain.

• Licensing vCenter ROBO issues

  Hello

  I just buy a ROBO (25 VM) license key and I wanted to add to my existing vCenter server.

  But whenever I added to vCenter I get this error

  

  Does anyone has worked with before ROBO licenses and could you tell me what is the problem? or contact VMware Support?

  Which vCenter version you're running and which version license did you buy?

  If you're running 5.5 and vSphere bought 6 licenses, you will need to downgrade the license to 5.5.

• VCenter storage issue

  Vcenter needs to see all the storage attached hosts have access to? I tried Googling it but could not find a definitive answer. Thank you!

  Hello

  No, you don't have to present LUNS to storage the vCenter Server (if installed on the physical host). It is recommended to have a redundant between the hosts of ESXi and vCenter network connectivity since that is how the pulse information is shared. In most facilities vCenter is a VM and if that's what you have, then you can srtike this step to present LUNS to the vCenter VM. The storage is configured between ESXi hosts and LUNS and vCenter offers a management interface to create/remove the virtual machines on the underlying storage.

  Arun-

  https://Twitter.com/arunpande

  http://highoncloud.blogspot.in/

  Virtualization VMware on NetApp

• VMware vCenter living is no longer working with Acronis Backup Advanced, Help!

  Hello everyone, I hope this ad in the right area of im, I'm looking for some advice on what could be causing my question about integration using the byproducts, I am struggling to find something on the net that relates exactly to my problem so have resorted to forums to see if anyone has tips or ideas , like im fresh out of them now!

  • VMware Client & Server Version 5.5.0 - (VMware vCentre Server Build 1476327)
  • Acronis advanced backup (Version 11.5 - update 5)

  Since November the synchronization / VMware vCenter integration between the 2 products above seems to have stopped working correctly, which means that any change in the location of the VM machines in the VMware customer environment is not reflected in Acronis more.

  For example, when you move a virtual machine to a folder on a particular data center to another folder in the same Datacenter, this change should be so reflected in the Acronis, what is happening is no longer.

  In addition, when a virtual machine brand new is created in vSphere and is placed in the appropriate Center of data/file structure, this should (and working correctly until November) fill with Acronis 'vcentre' host Group that has the folder structure equivalent to pick up the plans for appropriate backup etc, but this happens is no longer, instead , the only way that you can see the new VM is under "all Virtual Machines.

  In addition, when removal of vSphere VM, also not being properly reflects Acronis more, when go in "All Virtual machines" these deleted machines are still show while intoxicated. But these machines no longer exist in vSphere, this shouldn't show Acronis more. Without doubt, this is connected to vCenter integration issues.

  Here are the steps I took to try to solve this problem

  • Disable/re-enabling integration with the server vCentre.
  • Restarting the Server Service on the management of Acronis Acronis license server
  • Reset all motors of unloading and the virtual machine.
  • Acronis and vCentre servers restarting.
  • A reconstruction complete the Acronis server and all subsequent config, etc. backup plans.

  After the last point (reconstruction of Acronis) integration has worked for a few days, then it stopped working again!

  If anyone has any ideas or possible causes, could you please let me know.

  Here are a few details of what was the root cause of the problem:

  Each VM in vSphere contains a list of parameters such as:

  InstanceUUID

  locationID

  guestFullName

  The problem arises because some of the virtual computers contains a copy of the values of these parameters (name, value). Thus, in order to update the database of AMS, we execute the SQL query with these settings, but when 2 or more of the virtual computers contains the same parameters, the SQL query fails > This is why the changes were not reflected and it was not possible to update the vCenter folder structure.

  The developer removed then duplicate values enable and disable the vCenter integration, by doing this it was able to resolve the problem.

• No network connection between the virtual machines on different hosts ESXi

  I have several 5.0 ESXi hosts in a cluster managed by vCenter Server 5 and I have network problems:

  1. [Host A] running a virtual machine can ping any other computer virtual running on the [host A] great!
  2. A virtual machine running on host [B] can ping any other virtual machine running on [B] home - very well!
  3. [host A] (from the ESXi console) can ping any virtual machine running on [B] home - even better!
  4. [B] home (from the ESXi console) can ping any virtual machine running [host A] - beautiful set!
  5. A virtual machine running [host A] can not ping any virtual computer running on host [B] and vice versa - bad, very bad!

  So basically the problem is that the virtual machines can communicate on hosts. It is a major problem that I need to fix, for obvious reasons.

  Networking on all hosts is configured exactly the same way: a unique and standard vSwitch with a pair of gigabit network cards grouped, vmkernels configured for the vMotion, NFS and network management and a group of ports configured for the VIRTUAL local area network used by the VMs. (vMotion works fine on hosts, storage vMotion works very well too.) All virtual machines are servers Windows (2003 and 2008).

  Reason #3 and #4 above, my assumption is that #5 must be the result of an ESXi/vCenter configuration issue and not a problem with the switches of material upstream. Is this a reasonable assumption?

  Whatever it is, can anyone offer suggestions on how can I fix? It is quite annoying as I'm pretty sure that these hosts are configured in the same manner as those of our production cluster, which does not at all these problems!

  Thanks in advance for any help you guys can provide.

  To be honest, it looks like a problem with your physical network-

  How is the physical network configured - are NIC connects it to the same physical switches? Are the virtual machines on the same subnet? If this is not the case, they are able to ping the gateway sbnet? Can you piing host IP address from the virtual machines?

  I also moved it to a forum more approiate.

• Issue by updating the configuration of the specific data of the provider for a virtual portgroup distributed in vcenter 5.5

  Hi all

  We strive to update provider specific data in config spec for a group of distributed virtual ports, we are able to reconfigure the dvportgroup for the first time and data updates are visible in the list of mob (QuerydvsbyUUID). But the second time, if we try to update specific provider we receive error in vcenter below.

  Could not complete the operation due to simultaneous changes by another operation

  
  

  The environment we use is as follows:

  Customer vpshere 5.5 ESXi and Vcenter 5.5 5.5.

  
  

  We use Vijava to update the specific configuration of the dvportgroup seller (reconfigureDVPortgroup_Task). When we looked this error, we found below thread:

  http://KB.VMware.com/selfservice/microsites/search.do?language=en_US & cmd = displayKC & externalId = 2016329

  But we try to reconfigure the dvportgroup with the root user in VCenter.

  Ask you please let us know if I'm doing something wrong.

  Thank you and best regards,

  Aristides Maximilian

  
  

  Found a similar question in the communities,

  https://communities.VMware.com/message/2342966#2342966

  The issue is a bad configversion.

  Using the last ConfigVersion (the real value of the ConfigVersion from the portgroup extraction) in ReconfigurePortgroup_Task worked well.

• Dell VRTX + vCenter 5.5 + Shared storage is ESXi host import issue in vCenter. Help, please!

  All,

  I have two VRTX to be used for lab purposes that I am currently in configuration.

  Blades feature 4 VRTX with a shared storage infrastructure. Each blade has 5.5 installed on ESXi.

  I configured the shared on the VRTX storage, and all the blades can go very well.

  The question I'm currently facing is when you add the vCenter for managing ESXi hosts.

  Add the first host goes without a hitch. However, add any later host fail, because vCenter finds datastore attached hosts to have the same identifier.

  The error message is (see the attached screenshot): ' Datastore 'Main Shared-storage' is in conflict with a store of data that exists in the data center which has the same URL (ds: / / vmfs/volumes/xxxxx /), but is supported by different physical storage.

  Someone knows how to fix this?

  Thank you.

  Thanks for the reply.

  I think that I have found a workaround.

  First of all, this link does not address my particular issue.

  See, it's a whole new vCenter device installation and configuration. Only one of the four hosts to add host has been added.

  Still, the problem is that each ESXi host is a blade VRTX (M620), which has access to the data store created on the shared storage of VRTX.

  Basically, each host is editing the data store shared even (the only data store created on the shared storage), which works very well except for vCenter complain when you import the hosts.

  In any case, my resolution was as follows:

  -Add the first host with the attached and mounted data store

  -Remove the data store and detach the controller shared by other guests before adding in vCenter

  -Re-attach the controller shared and set up the data store via vCenter once guests have been added

  -Re-configure each host for vSphere HA if necessary

  Thank you.

• I want alarms to stay there in vcenter alarms tab until I manually acknowledge vcenter 5.1, even though the issue has been resolved. Is this possible?

  I want alarms to stay there in vcenter alarms tab until I manually acknowledge vcenter 5.1, even though the issue has been resolved. Is this possible?

  I think that it is possible for costom alarm unless if someone this cleat. but for some the alarm settings by default, it will be deleted once the threshold/connection back to normal. to do this, you need to change the alarm and the need to remove the condition that meet as nornmal (means, for this default it will multiple alarm (one is green to red or another is red to green...) so remove settings from red to green. so he will be there until you ack and reset it)

• vCenter 5.1 having issues with snapshot size alerts

  Hello world
  I have a problem regarding the sending of alerts by e-mail when vm snapshot size exceeds a certain size. (in fact, any size with problems)

  She doesn't send traps, ignoring what I did come in like it size and spamming my Inbox.

  Go to alerts vcenter - new alarm - monitor: VMS - monitor specific conditions or State...

  Trigger: Condition: above

  Size of Snapshot in VM (GB): WARNING: level 1

  Snapshot in VM (GB) size: alert level: 2

  Send email to: myself

  When I click on ok. I have tons of emails from vcenter which all my virtual machines exceeded the size limit of 1 GB instant! (but he doesn't based on storage views)

  Then I put the level to 10 GB makes no sense. It keeps me spamming all my virtual machines with snapshot size exceeded.

  This setting worked well with vcenter 5.0 because I upgraded to vcenter 5.1, this problem appeared. Note that I have 2 vcenters, two of them having the same problem.

  Please see the attached photos.

  VCenter version: 5.1 build: 880146 running on windows server.

  Would you kindly try to put the same trap and let me know if this is a bug or not?

  Thank you all happy new year

  It is a known issue with vCenter Server 5.1 (VM Snapshot size (GB) alarm incorrectly triggers on VMS with no snapshots (2037464)), which - according to http://www.vmware.com/support/vsphere5/doc/vsphere-vcenter-server-510b-release-notes.html - does not seem to have been resolved with the last 5. 1 b version.

  André

• Issues of recovery site: domain/Vcenter controller

  Guys,

  I'm new to SRM.  I have a few questions about the installation of the infrastructure of the Dr site.

  1. my vcenter protected site is broken out in distinct roles, VC/SQL.  On the site of recovery for the sake of simplicity, that I would just have a single VC with SQL Server express.  Guys do you see any issues with that?

  2. what should always live on the site of recovery from the point of view of the infrastructure?  Do I need a domain controller or can I just add my server to vcenter Site Recovery at existing on the protected site domain controller?

  Thanks in advance,

  Ian

  Hello

  You should have AD / DNS server to the recovery of the site as well. If your vCenter / SRM are joined to the domain, it will be difficult for them to communicate / authenticate.

  Michael.

• vSphere vCenter - vCenter 4.0 Update 1 resolution VM issues slow because the disk i/o latency?

  vSphere vCenter - vCenter 4.0 Update 1 resolution VM issues slow because the disk i/o latency?

  My client is slow VM problems that appear to be disk I/O latency on Hitachi storage 1000. I heard in VMware meetings vCenter 4.0 Update 1 solves these problems... without any explanation as to why.

  Rumor is that "after working all the angles of the slowness of the virtual machine including vmtools hardware version, latency of storage, etc. called VMware support and advised to get vCenter to U1 to solve the 'known problem' VM performance issues." "U1 fact and problem solved.

  It is VMware User meeting and I have no other details.

  Customer did not of U1 and having problems of slowness VM believes may be due to the assets/Hitachi 1000 s and favorite paths questions (known to cause problems). Preferred fixed pathing but questions continue.

  My limited participation in the issue of troubleshooting in the date limit information available now. It is just an issue if 'known problem' exists and is known to be resolved via U1 vCenter or ESX 4.0 U1?

  Not vCenter 4.0 Update 1 solve disk i/o latency issues considered the slow pace of the vm? Why?

  All points will be awarded.

  that strike!  You can use round robin or MRU for active/passive.

• vCenter Update to 5.5U2 to 5.5U3D - SSL issues?

  Hi, currently I am planning my vCenters of 5.5U2 to 5.5U3d update.

  Are there pitfalls I should be aware of that. I understand that SSL is U3b removed\disabled leave.

  Update of the VC directly to 5.5U3d could cause problems with VC connect to current ESXi (U2 2718055) due to SSL TLS change hosts?

  
  Also there are the implications on the 5.8 SRM?

  Thanks in advance!

  Update of the VC directly to 5.5U3d could cause problems with VC connect to current ESXi (U2 2718055) due to SSL TLS change hosts?

  No, and if you plan to upgrade your hosts you will really need to have your first improved vCenter.

  Also there are the implications on the 5.8 SRM?

  You should upgrade your SRM version 5.8.1 see: VMware product interoperability Matrices

• vCenter to migration issues of device 5.5 to 6.0

  Hi all

  My production environment consists of 2 devices U2e vCenter 5.5 (VCSA), one per physical location.  Due to limitations in the VCSA, there is no bound mode, and each unit has its own internal SSO configuration.  5.5, VMware was pushing its customers to use the VCSA and the embedded database.  Given that we were well within the camera and knew it was the future of vCenter, we migrated to it and put the ugly Windows vCenter with SQL behind us-based.

  VMware is said now that they want to vCenter and the PSC on separate VMs/devices.  Oh but wait, if you're on a 5.5 VCSA and want to upgrade, you can pass only to a 6.0 with a built-in PSC.  Once VMware still change my mind.

  In view of all this, what are my options?  Ideally, I would like to keep the vCenters separated on the device, but use a single instance of the CSP in a config HA, use linked modes, etc..  It will not be the end of the world if I have to keep the same way they are now things (completely not separated, no bound mode), but it seems that there should be an easier way.

  I've seen some articles on the creation of a new SSO and pointing to her devices, but those who carried out based on Windows Installer.  I found this article:

  http://KB.VMware.com/selfservice/microsites/search.do?language=en_US & cmd = displayKC & externalId = 2113917

  But he said that I would do is not supported.  Any ideas?

  In response to me here.  I just received a response from our SE stating that vSphere than u1 6 should support the upgrade in place and selecting an external PSC.  He expects it to be released in Q3.

• Connecting to vCenter issue certificate in 2.0GA

  I just upgraded my 2.0Beta instance to 2.0GA and watched dashboard inventory and noticed that the connected the vCenters number is 0.

  
  

  I thought that I need to update the password, so I did and when I tried the password I got:
  

  
  

  Transport HTTP error: javax.net.ssl.SSLHandshakeException: java.security.cert.CertificateException: certificate is not consistent with the constraints of the algorithm

  
  

  I was working on a separate problem with a nobody trying to connect a tool the vcenter and they had a certificate error, thus, I think that it may have to do with this KB

  http://KB.VMware.com/selfservice/microsites/search.do?language=en_US & cmd = displayKC & externalId = 2074942

  
  

  He is a former vCenter which has been improved over time. It's like 5.5GA

  
  

  I was able to add another vCenter is 5.5u1 which has a cert of 2048 bits.
  

  Check the certificate of your old vCenter, this needs to be at least 1024 bits, or you can change the perspicacity of newspaper to support 512 bits to work around the problem.

  Check this thread for more information: vCenter won't connect after upgrade to 2.0