components critical vCenter

Similar Questions

• The State of health critical vCenter 5.5 follow-up

  Hello

  I have a new alarm 'Critical Health Status Monitoring' and in the description, it says see vCenter Service Health in the request of the Administration, but when I go to the Administration (logged as administrator) there is no section of Health Service of vCenter . I do not see a vCenter Service Health section even being logged in as the admin. root

  Found a few suggestions to check services, but they're all on the vcenter server.

  
  

  Form what I found, seems to be on a compatible web browser and have installed the plugin for integration of customer, although it includes the same way on Google Chrome and IE 11.

  I have no way to see what is about this error, any thoughts?

  Thank you!

  Hello

  you have two options to check for this.

  1. connect to your vSphere Client and goto vCenter Service status.

  2 log in to your vSphere Web Client, open your vCenter and goto followed and Service status

  We could see if a Service is not working as it should.

  Frank

• Migrate from vCenter 6.0 from 2008 to 2012

  Hello

  We have vCenter 6.0 running server 2008, 2012 with the database on SQL server.

  I want to know how can I migrate vCenter 6.0 from 2008 to 2012. Step by step guide will be very appreciated.

  Thank you

  Mihir

  Hello

  Not quite same as 5.1

  The important thing here is that if your CSP is separated deployed and your CV is a virtual machine then you can shut it down, take a backup of SQL DB and a snapshot of the virtual machine and then build a VC again on a new virtual machine with the same information.

  Just install the components of vCenter and link it to your existing DB. If this does not work, then off the VM, restore your SQL DB and turn your old vCenter.

• Standard managed via vCenter essential Kit

  Hello

  We got 3 ESXi 4.1 cluster host, but the version doesn't matter, because we want to upgrade in the nearly future. The thing is that we also want to expand our infrastructure, lets say with 2 new hosts. This cluster has a kit with a single instance of critical vCenter more essential. If buy us a license for vCenter standard server and a standard for this 2 new host license will be able to manage in a Standard vCenter? (essentially more host kit 3 + host vSphere standard 2 - by vCenter)

  I dive with care through all licenses pappers from documentation and white, so I know that essential kits does not exceed 3 host limit, but if I buy the standard for vCenter license will be I be able to manage the two cluster throug or I have to re license old Kit essential cluster?

  I hope his celar enough

  Wojtek

  It does not work. Kits only Essentials, you can manage with vCenter Server Standard are the "Retail and Branch Office Kits". In your case, you will need to purchase CPU licenses for all guests. What may be interesting to watch from a cost standpoint, is an upgrade of the Kit Essentials Plus a kit of acceleration (including vCenter Server Standard and 6 licenses processors) and then buy the CPU licenses also required.

  André

• vCenter 5.5 Installation stops after SSO

  Hello

  Just downloaded a copy of eval for vCenter 5.5 and when I try to do a simple installation nothing happens after AUTHENTICATION is complete. I tried this on 2012 and 2008 R2. I have to manually install the rest of the components (inventory, vCenter, web). In vCenter 5.1 everything I had to do is hit the facility, the Simple installation menu button and everything worked very well. Is this a known issue? already?

  Adrian

  Works now, there was something has messed with my profiles on the server.

• Cannot use Chrome to connect to the web client vcenter after update.

  vCenter Web Client Version 5.1.0 build 1115182

  Customer integration Plugin VMRC version 5.1.0 build 1060398

  Customer support version 5.1.0 build 832030

  Flash Player WIN 11,8,800,94

  Browser Google Chrome Version 29.0.1547.66 m

  After all components of vCenter update I am more able to use Chrome to access vCenter Web Client.  When the connection page opens, I get the following error:

  Connection error: could not connect to vSphere Web Client. Contact your administrator to resolve this problem.

  If I try to connect, I get this error:

  Provided credentials are not valid.

  Everything works fine if I use IE 10.  Someone at - it see this before and knows how to solve?

  Thank you

  Mux

  It is fixed.  I had 'Block third-party cookies' checked.  After unchecking it connected perfectly.

  Mux

• How is the web client vCenter/SSO

  In vSphere 5.1, when I type https://myhost.mycompany.com:9443 / vsphere client / in my browser, I immediately get a login screen. When I enter my credentials, all work great. I guess that in this example, the backend of the web client is listening on port 9443.

  -Customer web backend expects SSO to always be running on the same host as himself. I mean, it is possible to have a scenario where the backend of the web client is running on a different host than vCenter or SSO.

  -If at the time of installation, we have configured the SSO to listen to one port other than the default, do I have to configure the client web backend as well, or is it also get reconfigured.

  Thank you.

  Yes, you can install SSO separately from other components of vCenter: see http://pubs.vmware.com/vsphere-51/topic/com.vmware.vsphere.install.doc/GUID-595E62F1-4D32-4A09-81F4-BE59B9217A51.html

  When you separate facilities you must install first SSO. When you subsequently install the WebClient service you must point to the SSO service by providing the URL of the SSO service. SSO listening on the 7444 default https port. If you have configured it differently (I don't know if this is possible) then you just need to change the port number in the URL of SSO.

  The WebClient service is listening on port 9443 default. See http://pubs.vmware.com/vsphere-51/topic/com.vmware.vsphere.install.doc/GUID-74AA3EF1-BDF3-4752-89DB-A522CDE30A66_copy.html

  -Andreas

• Question of ESXi and Vcenter licenses

  Hello

  I bought vcenter just now as well as some vsphere licenses, however were still about 15 older ESXi servers that I want to upgrade and manage vcenter.

  However, I am a bit confused about the cost of the upgrades for my ESXi free installs to connect to vcenter.  I watched the Essentials Kit where you can buy 3 licenses but it's to connect to vCenter Essentials.

  What is the difference?  I'm guessing that you can not essential home standard licenses to vCenter ESXi...

  I am not otherwise interested in HA or vmotion, I just need a way to access my vCenter ESXi.

  Thank you

  Essential ESXi connects to critical vcenter. for your case, you will need to vsphere Standard to be able to be managed by the vCenter.

• Sanitation Manager Update: only the scan, patch no host?

  Hi, we have a whole new ESXi 4.1 installation host with brand new install V-Center server 4.1, I installed all the components of Vcenter virtual server on a Windows 2003 X 64 computer (which is not part of this new license key we just buy for a branch of the Department), Update Manager of plug-in is here, I can see and test its configuratuions , I can see his Large patches (218) (88 reviews and 130 not critics) lists the ins Patch repository. So far, everything seems to work, Scan takes less than 30 seconds.

  Now the real problem for me: I was not able to apply these patches using 'Cleanup' - I tried like a task executed immediately or later, it ends always in less than 1 Minute (I knew it should take much more time because I used the host-setting utility to update on the free ESXi 3.5, it took about 10 Minutes to patch a host) , of the event, I see this: it seems only scan patches, do not have true patch for the host.

  I read the entire Update Manager Guide, do not understand why it doesn't NOT patch the host (the base line is here, each reference has a number of fixes, I tried many times and checked the ESXI host, up to now, nothing happens), suggestions and advise are greatly appreciated.

  (almost all our configuration server Vcenter by default is because we have only 2 ESXI hosts)

  Analysis 10.1.1.40 for patches successfully.
  Info
  21/04/2011-14:38:51
  Clean up the entity
  10.1.1.40
  Administrator

  Analysis 10.1.1.40 for patches successfully.
  Info
  21/04/2011-14:38:48
  Clean up the entity
  10.1.1.40
  Administrator

  Task: Clean up entity
  Info
  21/04/2011-14:38:43
  Clean up the entity
  10.1.1.40
  Administrator

  With construction 348481 host already has the new installed patches. Perhaps VUM indicates these fixes as critical, but they do not apply to the host.

  André

• I'm looking for help to share best practices to upgrade the Site Recovery Manager (SRM), if someone can summarize the preparatory tasks?

  I'm looking for help to share best practices to upgrade the Site Recovery Manager (SRM), if someone can summarize the preparatory tasks?

  Hello

  Please check the content below, you may find useful.

  Please refer to the URL: Documentation VMware Site Recovery Manager for more detailed instructions.

  Important

  Check that there is no cleanup operation pending on recovery plans and there is no problem of configuration for the virtual machines that protects the Site Recovery Manager.

  1 all the recovery plans are in ready state.

  2 the protection status of all protection groups is OK.

  3 the status of the protection of all the individual virtual machines in the protection groups is OK.

  4 the recovery of all groups of protection status is ready.

  5. If you have configured the advanced settings in the existing installation, note settings you configured before the upgrade.

  6 the vCenter local and remote server instances must be running when you upgrade the Site Recovery Manager.

  7 upgrade all components Server vCenter Site Recovery Manager on a site until you upgrade vCenter Server and Site Recovery Manager on the other site.

  8 download the setup of Site Recovery Manager file in a folder on the machines to be upgraded the Site Recovery Manager.

  9 make sure no other facilities-\no updates windows restarts done shoud

  Procedure:

  1. connect to the machine on the protected site on which you have installed the Site Recovery Manager.

  2. backup the database of Site Recovery Manager by using the tools that offers the database software.

  3. (optional) If you upgrade of Site Recovery Manager 5.0.x, create a 64-bit DSN.

  4 upgrade the instance of vCenter Site Recovery Manager server that connects to vCenter Server 5.5.

  If you upgrade a vCenter Server and Site Recovery Manager 4.1.x, you upgrade the instances of vCenter Server and Site Recovery Manager server in the correct sequence until you can upgrade to Site Recovery Manager 5.5.

  a upgrade vCenter Server 4.1.x to 5.0.x server.

  b Update Site Recovery Manager of 4.1.x to 5.0.x.

  c upgrade server vCenter Server 5.0.x to 5.5.

  Please let me know if it helped you or not.

  Thank you.

• 5.5 upgrade Question

  We have in place upgrade from 4.1 to 5.1, with all components of vCenter installed on Windows 2008 server except Update Manager and SQL server on separate virtual machines. 2 years ago we currently have about 40 clusters/200 esxi hosts/1200 virtual machines. We need to upgrade to 5.5 U2 envirorment. We must also build the hybrid cloud from this infrastructure. I would like to know what is the best way to improve the environment like this one where we use vSS not vDS, simple installation was used for 5.1 upgrade. do we need to set the SSO, web client, Inv. srvs and vcenter servers on separate etc.do we use linked modes, heartbeat etc. If we vDS is better than vSS, we need to upgrade with existing configurations that leter migrate vSS to vDS?

  On the vCenter component distributed installation, take a look at the following picture of this document: http://www.vmware.com/files/pdf/vcenter/VMware-vCenter-Server-5.5-Technical-Whitepaper.pdf

  

  And vSS to vDS migration, if you have multiple physical NICs in your host, you can migrate without any down time, take a look at the following articles:

  Migration of vSS for a VDS exchanges

  VMware KB: Migration of virtual machines between vSwitch or exchanges of vDS or dvPortgroups

• Best practices for backup and restore

  Hello!

  I couldn't find any recommended official VMware to backup/restore the components of vCenter: vCenter, SSO, Update Manager, heartbeat...

  Anyone provide any doc where it should be mentioned?

  Thank you.

  Discover this for SSO. VMware KB: backup and restore of the configuration of VMware vCenter Single Sign-On 5.5

  Thank you

  DJ

• 5.2 horizon problem pool view

  Hi all

  I'm new to this forum... I have a problem with my farm of the view. I installed view 5.2. I created all the components (composer, vCenter, field, ecc). Everything is green... When I create a pool, I see not all VMs in the list Parent VMs.

  I created a VM XP SP3 in my farm, with DHCP, in my field, and with the Agent of the installed display. But nothing: view does not show me the virtual machines.

  Any suggestion?

  Thank you!!!

  Matrix

  Hi all!!!

  I have some news! I restarted the Service of inventory (?) on vCenter and after the connection to the server. Now everything is OK!

  Thank you all!

  Matrix

• VMware 5.5 u1 - iScsi adapter hangs the system

  Hi all

  Last week I was not successful in improving the environment VMware 5.5 to 5.5U1. First installation well happened, set up the first ESXi host and created a profile of the host. So far so good, no major issues. Where to install the rest of the other 5 blade servers and applying the host profile all seem to work well while things went sideways when the environment has been stopped and restarted.

  Te of installation as follows:

  Servers Dell 1955 blades Center (x 6)

  Switches Cisco 3030 connected to the blades of the

  vCenter server as a virtual machine on the ESXi cluster

  Manager upgrade from vCenter as a virtual machine

  Distributed Virtual Switch configured

  During the shutdown procedure I move all components of vCenter to a single host before feeding the server vCenter (Windows 2008). Then I stop the ESXi host using the management client as vCenter is no longer available.

  Turn on the cycle must start this first ESXi host, connect to it and then powering the vCenter components. Once that of all DRS and power management is set to automatic, then the virtual machine simulation is started.

  With 5.5 all worked well and no problems at all. When I installed 5.5 U1 I could no longer connect to the ESXi server and it gave a 503 error when it connects to it. Through the journal showed that the components on the file system was not found after what I decided to do a cleaning of the files install.

  After the reinstallation of the entire batch, I connected to an ESXi host and helped the network and added the iScsi card. At this point, the system stops responding and the session between the client and the ESXi host is disconnected.

  Running several tests, I have concluded that something must be wrong with the components of virtual disk system, iScsi or vSan. 5 of 6 guests will be deployed to vmware 5.5 as vmware 5.5U1 is not stable...

  Can use some to help solve this problem I will leave 1 server in the current state, is to identify the root cause because I'm stuck at the moment. Later, I'll post a few newspapers of sections of the file with the errors that I have identified. (Pass it restart does not solve the problem)

  Kind regards

  Martin Meuwese

  Hi Martin,

  Could you please check the hardware compatibility list. I couldn't see Center blade server Dell 1955 support in 5.5U1 HCL.

• question 1(b) 5.0.0 to 5.0 update

  I have to update the VirtualCenter with a new disk for 1 b before you install this update? or do I just patch my hosts and remain in the current vcenter?

  Update 1b is only available for components and vCenter Server. For ESXi version last updated 1 (more a few fixes).

  André