After VCSA

Similar Questions

• [SOLVED] After you deploy vCSA root 6 has no right.

  Hello Forum,

  I'm experimenting with vSphere 6 for possible deployment in our environment. We already have a 5.5 vSphere (that I put in place, too!) and we have quite some experience with VMware environments, having two VCP here (including me).

  Already, we configure the server vSPhere vCenter 4.1, including devices in 5.0 and 5.1.

  Here's what we did:

  A host has been installed with 6 ESXi hypervisor, vSphere 6.0 device has been deployed by using the new method. The deployment was successful, the Web Client starts and I can connect using the root account.

  However root can not do anything, including:

  • Adding hosts or data centers
  • join an ActiveDirectory (or see the appropriate menu entry, by the way)
  • Adding users or roles assinging

  What has gone wrong or who should I go from here? If I can't add users, join a domain or assign other rights users, the device is a little pointless...

  Any help is appreciated.

  Kind regards

  
  Thomas Zimmermann

  You can try with [email protected] user to perform

  • Adding hosts or data centers
  • join an ActiveDirectory (or see the appropriate menu entry, by the way)
  • Adding users or role assignment

  Concerning

• VCSA starts only after the loss of power?

  Got a weird problem.

  I'm under vcenter Unit 5.5 update1 on a cluster 2 host in my lab.  I started with 5.5 and upgraded to 5.5 u1.  It was working fine but yesterday my lab lost power and I don't have a chance to make the soft stop.  Now I can start on that vcenter.

  I get "waiting for vpxd to intitialize: successful" message

  I put the finger because of the database which I think was caused by the blackout, and I am trying to see if its possible to recover instead of do reset DB or redeploy the device.

  When I test the database, I get the following:

  Error: Incompatible DB schema version

  /var/og/VMware/VPX/vpxd_cfg.log shows the following:

  2014-04-16 20:25:53 22314: BEGINNING of blocking... / usr/sbin/vpxd_servicecfg db test

  2014-04-16 20:25:53 22317: [22314] BEGIN execution of: / usr/sbin/vpxd_servicecfg 'db' 'test' "embedded" "" "" CENSORED

  2014-04-16 20:25:53 22317: test DB.  Type (embedded) () () of the user () of the Port Instance Server

  Enable autostart of vpostgres instance...

  insserv: network of services is not respected in the levels of operation 4 to use the postgresql service

  insserv: syslog Service is missed in the levels of operation 4 to use the postgresql service

  Waiting for the database shipped to start: [OK]

  2014-04-16 20:25:53 22317: link test DB.  Type (PostgreSQL) Server (127.0.0.1) Port (5432) Instance (VCDB) user (vc)

  2014-04-16 20:25:54 22317: ERROR: DB version is not compatible with vpxd: 551 (VirtualCenter Database 5.5), should:

  2014-04-16 20:25:54 22317: VC_DB_SCHEMA_VERSION = 5.5 VirtualCenter Database

  2014-04-16 20:25:54 22317: VC_DB_SCHEMA_VERSION_ID = 551

  2014-04-16 20:25:54 22317: VC_CFG_RESULT = 412

  2014-04-16 20:25:54 22317: completed

  Any ideas on how to fix this without losing my vcenter config?

  Thank you

  
  Alex

  Yes, you're right!

  In any case, the cause of your problem is the same:

  Cause

  The problem occurs when the database schema version is not compatible with the version of vCenter Server device.

  I guess you need to reinstall the device vcenter.

  Another option may be to back up and restore the database to the new vcenter appliance:

  VMware KB: Backup and restore of the database vPostgres of vCenter Server Appliance

  Best regards

  Pablo

• Manager certificates 're-record of lstool' failed: 1 / VCSA Certificate Manager Option 1: certificate to replace Machine SSL with certificate custom

  As a result of this post...

  Configuration of VMware vSphere 6.0 CA VMware as a subordinate certification authority

  .. .we have now installed a brand-new VCSA. This is a clean install.

  "In accordance with the recommendation of support, I am now trying to do ' Option 1: certificate to replace Machine SSL with certificate custom" using a Microsoft CA

  This is the error message:

  2016 07-13 T 15: 24:25.268Z of INFORMATION serial number of the certificate manager before replacement: < redacted >

  2016 07-13 T 15: 24:25.268Z of INFORMATION: < redacted Certificate Manager after replacement serial number >

  2016 07-13 T 15: 24:25.268Z INFO-Certificate Manager footprint before replacement:< redacted >

  2016 07-13 T 15: 24:25.268Z INFO-Certificate Manager footprint after replacement:< redacted >

  2016 07-13 T 15: 24:25.268Z certificate MACHINE_SSL_CERT certificate INFORMATION-Manager replaced successfully. Serial number and the fingerprint has changed.

  2016 07-13 T 15: 24:44.90Z ERROR-certificate error when replacing Manager machine SSL Cert, please visit /var/log/vmware/vmcad/certificate-manager.log for more information.

  2016 07-13 T 15: 24:44.91Z "lstool record" has no certificate ERROR Manager: 1

  A pension case is ongoing. But if someone has any ideas?

  <>rant

  It is incredibly frustrating that something (replacement of a SSL certificate) that should be so simple is so hard.

  It's extremely annoying to know that the Certificate Manager is able to completely screw up a VCSA.

  How VMware is justified in the marketing of this new approach ver.6 as a 'simplification' of the management of SSL certificates?

  < / end of rant >

  Thank you

  Robert

  This has been fixed by an Incident of Support VMware

  I don't know how to fix them, but it took over 2 days (except "waiting for a response" time)

• ESXi crash happening with vCSA?

  Hello

  I have 4 ESXi 6 hosts in a HA cluster.

  What will happen if the ESXi host falls down and vCSA was running on this host?

  The vCSA always automatically starts on a different host? (I think: this must be a vCSA action, but when it is low nothing will happen.)

  Is there a way to avoid this? I know I can build 2 vCS of Windows in a cluster, but I really don't want that.

  Kind regards

  S

  vSphere HA is not to have a dependency on the server vCenter after successful configuration.

  so if your ESXi Host which hosts vCenter VM fails, HA will still be able to detect this failure and launch the failover, so in a few minutes, you will find your device being powered in a healthy host in your cluster HA of vCenter.

• DNS issue on vcsa at 5.5 to 6 level

  We are in the process of upgrading our vCenter (vcsa) of 5.5 to 6.0 U2. During the upgrade, I get a warning that the "Host name xxxx is not be resolved by DNS, but corresponds to VC and SSO. certificates. If you don't configure a mapping of host name can be resolved to valid DNS, you may not be not able to connect to vCSA 6.0 thereafter. Please or device file/etc/hosts to access DNS servers properly update DNS servers device with the correct host name mapping. "To check if the DNS a record all local host name, please run" dig xxxx + short "locally on the device, or"nslookup xxxx"on a windows machine. However, I checked through nslookup on the device that resolves the host name. I also checked that DNS is correct on the device and our DNS entries are correct. Given that the host name is resolved, I guess I could get the vcsa after the upgrade very well. Any thoughts are appreciated. Thank you!

  Thanks Camero. We have checked and guaranteed that all resolve correctly. The error still persists, but we feel confident that we can move forward. The vcsa updated very well and we could access/determination afterwards.

• Can not connect to vcenter after reboot

  Hello VMware,

  I can not connect to vcenter after reboot with the error «Failed to connect to the Vmware research service»

  

  I tried to follow below doc but no help.

  http://www.myvmwareblog.com/2012/11/28/lookupservicesdk-SSL-certificate-verification-failed/

  I tried to play with the Vcenter screen underneath, but no luck.

  
  

  To resolve this problem, replace the VCSA IP with hostname VCSA in the search service configuration file, ls_url.txt file.

  To replace the VCSA IP address with the host VCSA name in the ls_url.txt file:

  1. Connect to the VCSA via ssh under the root user
  2. Go to the directory/etc/vmware-sso using the command:

     CD/etc/vmware-sso

  3. Make a backup copy of the file ls_url.txt using the command:

     CP ls_url.txt ls_url.txt.bak

  4. Open the file ls_url.txt using a text editor
  5. Replace the VCSA IP address with the host name of the VCSA. For example:

     https:// Lookupservice/XXXXXXXXXX/sdk

     Where XXXXXX is the host name of the VCSA.

     Note: It is usually the host name of the domain the VCSA FULL name. Make sure it matches the common name (CN) in the certificate name.

  6. Restart the VCSA services by running the command:

     restart the /etc/init.d/VMware-vpxd
     restart the /etc/init.d/VMware-SSO
     restart the /etc/init.d/VMware-InventoryService

     Or

     Restart the VCSA.

  Alternatively, you can use this workaround to regenerate the certificates for the vCenter Server Appliance.To to regenerate the certificates for the vCenter Server Appliance:

  1. Temporarily change the IP address of the vCenter Server Appliance to a different IP address, not used
  2. Restart the vCenter Server Appliance
  3. Change the IP address of the vCenter Server Appliance to the originating IP address
  4. Restart the vCenter Server Appliance
  5. Connect to vCenter Server Appliance, https://vcenterserveripmanagement Web page: 5480
  6. Click the Administration tab, and then select Yes to certificate enabled regeneration
  7. Click send to save the changes
  8. Restart the vCenter Server Appliance

• vCenter 5.5 Update 2 b adapter stop collecting data after vRops 6.2 upgrade

  Hello

  I just upgraded my vRealize operations to 6.2, and I work with two servers vCenter - vCenter 5.5 Update 2 b Build 2183111 (Windows OS) and vCenter Server 6 (Linux VCSA Appliance).

  After the successful upgrade - stop vCenter 5.5 collect information (adapter stuck on 'Start-up'), the vCenter 6 is very well and continue to collect information.

  What I've done so far:

  1. Restart both vROps and vCenter 5.5.
  2. Click on the Stop button next to the vCenter adapter 5.5 and click on start.
  3. Restart vCenter 5.5, click on stop, then wait for all services of vCenter to get running and click Start.

  Anyone who is familiar with this issue and know how to solve? I'll be happy to learn some tips/advice/solutions/solutions to my problem.

  Thank you! :-)

  Hello

  You can try to remove the adapter and re - create.

  Remove and re-add the adapter Instance

  Remove and re-add (X / +)

  Home > Administration > Solutions > choose adapter > Configure (click on the gear icon) >

  Save the vCenter display name, Description, IP address of the server, credentials and expand the advanced parameters and note the configuration of collectors/groups (it may be by default group of collector)

  Delete:

  Select the Instance of the adapter

  Click on the "X" icon to delete the instance.

  Do not check the box "delete releated objects '.

  Click the Yes button

  Click on the "X" icon to delete the instance.

  Add:

  Click the '+' to add the instance.

  Enter the display name, Description, vCenter Server IP address, credentials and expand the advanced settings and select the same collectors/groups configuration previously used (it may be by default group of collector)

  Click on the button "test connection".

  Review and accept the certificate

  (You can select and copy the certificate information and save it for a record)

  Click the 'Save Settings' button

  If you are prompted, select this option to Force recording

  Click on the close"" button.

• without uplinks in dvSwitch created by UCS vCSA 6.0, 6.0u1b, 6.0u2 Manager

  I try to configure passthru vnic UCS in vCenter Server Appliance 6.0u1b. I had:

  1. updated my UCS field for the 2.2 version (6f).
  2. installed VMware-VCSA-all - 6.0.0 - 3343019.iso;
  3. installed ESXi 5.1 with the latest updates and cisco-vem-v151 - 5.1 - 1.1.1.1.zip;
  4. moved this 5.1 to vCenter ESXi host;
  5. exported vCenter extension of UCS Manager;
  6. any succesfully extension to vCenter;
  7. created vCenter, Datacenter, folder and DVS in the UCS Manager;

  After a few moments UCS created this DVS in vCenter. When I try to move 5.1 ESXi host at this DVS, there is no uplinks:

  

  VCenter then unable to bind ESXi vmnic for anything whatsoever. In addition, I tried to add an ESXi host to DVS without uplinks and obviously it worked. For example, it is a screenshot of vCenter Server Appliance 5.5 in the same window of uplinks. Servers is B200-M4 with VIC 1340 adapters to the chassis with modules e/s 2208XP. Is it possible to install vnic passthru vCSA 6.0u1b and ESXi 5.1/5.5 Server blades Cisco UCS?

  This is a bug of the vmware vsphere web 6.0 client, 6.0u1b, 6.0u2 and maybe later versions. It can not find or just cannot display the uplinks in ucs-associated distributed switch. so I could not add the host to the switch via vmware vsphere client web. uplinks in switch is very good, so this bug have several workaround solutions. host can be added to the distributed switch ucs related through:

  1. application of VMware vsphere client. It will automatically assign first free uplink in the switch and i/o directpath will work;
  2. profiles of the host. in this case I can attribute any any vmnic uplink as I want. This can be done in vsphere client of web as application of vmware vsphere client.
  3. client VMware console or sdk. I did not tried this case, but I guess it will work fine.

  success. distributed switch:

  

  virtual machine:

  

• mgmt vCenter/vCSA and non routable network

  How are they managing get you all vCSA connected non-routable management network without burdening the network mgmt vCSA? I have the VLAN for all networks (mgmt, vmotion, storage) and network of the vm on VLAN 0. When install vCSA you use a routable IP address, but after that, I have to add the network mgmt to the vCSA in order so that it connects to the host, but it does not seem like the right way. vCSA with extra vnic is not supported.

  How do you manage this?

  Well, you need to sort out why one needs a management not routed network. In case it is a safety requirement, you would probably violate it by multiple your vcenter.

  In order to manage your vCenter inventory you would be obliged to get in this isolated NET or create a safe / trust / hardened machine multi-homed "jumpbox" that could be used for management activities.

• 6 VCSA with vRO

  Hello

  Can you confirm vRO is not included (embedded) VCSA 6? I sow the deployment vRO as an external device and also with a vCenter on Windows platforms but it VCSA as version 5 x?

  Thank you so much in advance!

  Right, vRO is not incorporated in VCSA. It is recommended to use the vRO (separate download!) and deploy independently of vCenter.

  After you have deployed the vRO appliance, you can configure the Plugin vCenter to connect to vCenter (any version, 5.x or 6, windows or device) via the workflow configuration.

  Kind regards

  Joerg

• VCSA 6.0u1 (updated 6.0 VCSA) vSphere Web Client error

  

  After that I upgraded my VCSA 6.0 to 6.0u1, I can't connect to the Web Client vSphere.

  How upgrade from 5.x and 6.x VCSA to VCSA 6.0 Update 1? virtuallyGhetto

  Clock animation Flash Adobe turn for a few moments, then it gives the error in the attached screenshot. «There is an internal error occurred - Index '0' specified is out of range.» It happens in IE10 and Chrome.

  It is a standalone PSC and I can connect to the device management https:// < vcsa >: 5480 and apparently in good health. Can I deploy a new VCSA from scratch, but it would be nice if I could fix it.

  Any suggestion would be appreciated!

  And if the clearing the cache of the web browser does not solve your problem, try to delete the database of serenity:

  To delete the files in the VMware vSphere Client Web serenity database:

  1. Stop the vSphere WebClient service. For more information, see stopping, starting, or you restart the services of VMware vCenter Server (1003895) and the stop, start, or restart services from VMware vCenter Server 6.0 (2109881).
  2. To delete the files in the database of serenity, type these commands:

     For Windows vCenter Server 5.x:

     Use File Explorer to delete the content of C:\programdata\vmware\vSphere Web Client\SerenityDB\serenity
     For Windows vCenter Server 6.0.x:

     Use File Explorer to delete the content of C:\programdata\vmware\vCenterServer\data\vSphere Web Client\SerenityDB\serenity

     For the VMware vCenter Server Appliance 5.x:

     Type this command when logged in as root with a shell of the console or SSH session:

     rm - rf/etc/vmware-vsphere-client/SerenityDB/serenity / *.

     For the VMware vCenter Server Appliance 6.0.x:

     Type this command when logged in as root with a shell of the console or SSH session:

     rm - rf/storage/vsphere-client/SerenityDB/serenity / *.

  3. Restart the vSphere WebClient service. For more information, see stopping, starting, or you restart the services of VMware vCenter Server (1003895) and the stop, start, or restart services from VMware vCenter Server 6.0 (2109881).

  Source: VMware KB: The VMware vSphere Client Web reports an internal error 1009

• Automation of the vCSA 6.0 PostgreSQL database backup?

  I am looking for some suggestions in the automation of the backup of the embedded database and get these backups unloaded on our Windows, file servers.

  I prefer not to get on any part to the vCSA himself, more that I read what is usually a pain in the ass.
  
  

  I had worked to try to get the SSH keys to work with with a script of winscp, but I had no chance to get SSH keys to work with vCSA 6.0 using PuTTY.

  I'm looking for suggestions or advice.

  Oh well I think I'm half way there now after going through this.
  SUSE Linux Enterprise Server 11 - SSH Server - auth keys: World Server

  I had tried one number of other SSH keys generating guides and nothing seems to work properly until that.
  WE AT WINSCP SCRIPTING!

• Unable to join u1 VCSA 6 back to the domain. Error messages are not found anywhere online.

  I was wondering if someone can help troubleshoot me SSO with a VCSA to 6u1 running. PLEEASE!  This has been updated about a week ago of 6.0 and had no problems until he decided to collapse Monday. At this time, that we had problems with our domain controllers, I don't know if it was related.

  Monday Veeam backup by using a domain account to access VCenter has stopped working. Authentication failure. Try to connect to VCenter WebClient with SSO that weI made for years also failed. Signature as root for web client has as well.

  Signature to the C++ client worked for connections without any problem, but really limited what we can do. So I spare the domain and attempted to join without success.

  I can sign into the web client with [email protected], you try to join the domain as we did before the results in "Idm client exception: error trying to join AD, code error [31], user..." " - no reference to error 31 anywhere. Yes the username in the form of [email protected]. The computer account has been recreated on the field. Connectivity to the domain controller is fine, because if I put the password wrongly, it tells me that authentication has failed. All services on the VCSA are started with the exception of the function Auto-déployer.

  I tried via SSH connected as long as root (it tells me that [email protected] has no shell access) domaine.net/opt/likewise/bin/domainjoin-cli join [email protected] translated by ERROR_GEN_FAILURE [code 0x0000001f], yet once a mistake that relevant results.

  I am unable to create beams journal via the web client or via the C++ client, I suspect because space on the VCSA which I was not able to solve. Execution of the VSAN performance monitoring seem to chew place until I turned it off, but haven't found all the resources online as to where to find them or how to remove.

  I have a snapshot that was done before I got updated to 6u1 8 days ago, but I'm afraid that everything I have done since then will crumble. This VCenter manages a VSAN production, and I can't get him off.

  Please can someone untangle me this mess? With the lack of informative error messages I don't know where to start!

  Thank you

  B

  Woohoo! I finally thought to it.

  To start with I've implemented a new VCenter server as a trial, nothing configured, just deploy the iso 6u1. I found that it was not automatically joined to the domain and has attempted to do. SAME ERROR! So the problem is not with VSphere. In recent weeks, we introduced two new DCs R2 2012 and retired from one of our 2008 R2 domain controllers. I closed the DCs 2012 and tried again with only the old DC on the network. It worked! I was able to join the VCSA test to the field, and after a reboot because the button leave available domain.

  So I she disjoint and then attempted to join the domain when running wireshark on 2008R2 domain controller's NETWORK card. Then, I grew up a DC 2012R2, waited 10 minutes or so close the 2008R2. Yet once, I ran wireshark but this time on the 2012R2 server's NETWORK card. I compare the results of a successful or not join and I saw that the 2012R2 DC has been a lack of outgoing SMB packets to the VCSA. The Server service is running on the domain controller in 2012, but the Microsoft recommendation has been to change startup srv.sys from automatic to manual on 2012 R2 server. I thought it was odd at the time, but we have changed when we put in place the new domain controllers to meet the BPA. I compared it to the registry setting on the 2008R2 domain controller. which has been set to automatic startup.

  So to allow VCSA to join the domain when you get the error 31, cancel it

  http://social.technet.Microsoft.com/wiki/contents/articles/21104.SRV-sys-should-be-set-to-start-on-demand.aspx

  on your server 2012R2 DCs if it has been applied it causes domain join failure.

  Command prompt: sc config srv = auto start

  or

  Register: HKLM:\System\CurrentControlSet\Services\srv\ from 3 to 2

  I hope this saves someone else the time it took me to understand! I guess I can cancel my request for support now...

• ESXi host running 6 VCSA disconnected from the vCenter

  Hi guys,.

  I have a weird problem with my vCenter build 6. Single cluster of ESXi hosts. Running VCSA 6.0 and 6.0 ESXI. Making a storage of the vCenter vMotion initially got stuck at 77% and the ESXi host running the disconnected from vCenter vCenter. But I can connect directly to the ESXi host with vsphere client and see the vCenter VM works perfectly well. If I try to manually connect host ESXi and vCenter, I get the error "Failed to contact the host specified") both are in the same subnet and VLAN. I can migrate to other virtual machines without problem. I even restarted the host and yet I am not able to connect to vCenter. The host connects to vCenter if I reboot vCenter, but after a few minutes, disconnects again (even if no task does run on this topic.) I have no HA or DRS enabled at this point that I build this new environment and only presented a single LUN as a store of test data to the cluster.

  Any ideas?

  OK, I think I fixed that or have at least a work around. So the underlying question was hiding ID mode/CPU EVC. I'm under the cluster to a level of EVC to reduce until I have migrate workloads from old environment and I think that this created a problem for the unit vCenter. To resolve this problem, I turned off the unit, directly connected to the ESXi host that had the camera running, edited the virtual machine and reset the masking of CPUID. Also, I've hidden the flag NX/XD of the guest. It's temporary (I hope) as once I increase the EVC to the Haswell, I will expose the NX/XD comments and test. For the moment, it is of the workaround I did. It may be of some use to someone.