Hi,

i just setup a 6.7 VCSA via the OVF on the ISO set everyting to DHCP IPV4. and set the Hostname.

I set booth the Root and SSO Passwort to the same password.

after the first boot and multiple reboots i am not able to log in via the local console nor the Website. I always get the Message "Authentifzierung nicht moeglich" translated

Authentication not possible. i also have tried to leave it blank durring install or choose a simple password like testtest the default "vmware" didnt work either.

i allready have installed multiple times because i tought its maybe some failure during the install.

Every hint in the right direction is greatly appreciated ^^

My company has use vsphere 6.5 service

When I am ready to do windows converter

I need a deployment agent to the target computer

But it's always blocked by the firewall

Although you can temporarily turn off the firewall so that the remote deployment agent

However, this method still has risks

Would like to ask how do not close the firewall in the case of deployment agents

Hi all,

I have 3 ESXi hosts with one SAN, managed by a vCenter server. I have a DVSwitch configured with 3 uplinks.

This vCenter server has SSO and is integrated with a Windows Active Directory server which no longer exists. So right now, I am using this vCenter with local admin account to manage the hosts.

I am planning to build a new vCenter server appliance but I have a few questions:

1. Where are these DVSwitch, iSCSI SAN, management pools configurations saved? In the hosts or in the vCenter?
2. When I disjoin the hosts from the current vCenter and join them to the new vCenter server, will I lose all the config?

Thanks

Hello,

I have a customer requirement where they have few VMs deployed and based on the current utilisation of these VM's CPU the requirement is to spin up new ones. For the sake of this condition consider the VMs as any Linux flavour. Can this be done through vCenter?

Thanks,

Subeh

Hi all,

I have a vCenter 5.5 Server (Windows) in my current environment which is acting as a standalone local auth server to manage my hosts. It once belonged to a domain but that domain has been retired. This vCenter server is managing 3 hosts (HA enabled) and 1 SAN (2 software iSCSI controllers each host)  and 1 DVSwitch.

I have a new domain and a new vCenter 6.5 Appliance within that domain. Right now, the new vCenter server is just sitting there doing nothing. Both old and new vCenter servers are in the same network. The new vCenter Appliance is deployed as a VM in one of the hosts managed by the old vCenter Server. I have 5 Resource Pools and a few hundred VMs.

From looking at what I have, what will be the best way to migrate all the hosts, VMs, SAN controllers and DVSwitch config to the new vCenter Appliance and upgrade the hosts to vSphere 6.5?

The objective of this migration and upgrade is to have minimum downtime and reconfig.

This is what I am thinking:

• Export DVSwitch config from old vCenter Server and import it to the new vCenter Appliance
• Move the hosts to the new vCenter Appliance
• Disable HA and DRS
• Move all VMs to two hosts and upgrade the third host to vSphere 6.5
• Move half the VMs to the upgraded host which will free up one of the two hosts.
• Upgrade that empty host.
• Move all VMs onto two upgraded hosts and upgrade the last host.
• Re-enable/reconfigure HA and DRS on the three upgraded hosts.

Any issue/catch you can think of? Is there a correct/better way of doing this?

Hi All,

We are trying to build a new VMWare environment for evaluation, currently we have a ESXi 6.5u1 hypervisor where we are attempting to deploy VCSA 6.7. Stage 1 of the deployment completes successfully, the stage 2 wizard runs and is completed at which point the setup runs however, early on in the setup process we are having trouble.

We get this unrecoverable error message:

Behind the unrecoverable error message, it seems the process stops somewhere around this point.

I have downloaded the logs and attached what I believe to be the relevant components below:

firstbootStatus.json

{    "finalStatus": "failure",    "stepsCompletedList": "visl-support-firstboot,vmafd-firstboot,vmidentity-firstboot,pod_firstboot,soluser_firstboot,vmon-firstboot,rhttpproxy_firstboot,analytics_firstboot",    "stepsStarted": 8,    "failedSteps": "analytics_firstboot",    "totalSteps": 38,    "stepsCompleted": 8,    "runTime": [        {            "visl-support-firstboot": "0:00:03"        },        {            "vmafd-firstboot": "0:00:53"        },        {            "vmidentity-firstboot": "0:00:43"        },        {            "pod_firstboot": "0:00:00"        },        {            "soluser_firstboot": "0:00:07"        },        {            "vmon-firstboot": "0:00:01"        },        {            "rhttpproxy_firstboot": "0:00:02"        },        {            "analytics_firstboot": "0:00:01"        }    ]
}

analytics_firstboot.py_6504_stderr.log

INFO:root:Register service with LS.
2018-05-10T14:59:56.955Z  Failed to register Analytics Service with Component Manager: SoapException:
faultcode: ns0:FailedAuthentication
faultstring: Invalid credentials
faultxml: <?xml version='1.0' encoding='UTF-8'?><S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/"><S:Body><S:Fault xmlns:ns4="http://www.w3.org/2003/05/soap-envelope"><faultcode xmlns:ns0="http://docs.oasis-open.org/ws-sx/ws-trust/200512">ns0:FailedAuthentication</faultcode><faultstring>Invalid credentials</faultstring></S:Fault></S:Body></S:Envelope>
2018-05-10T14:59:56.969Z  Traceback (most recent call last):  File "/usr/lib/vmware-analytics/firstboot/analytics_firstboot.py", line 161, in register_with_cm    cloudvm_sso_cm_register(keystore, cisreg_spec, key_alias, dyn_vars, isPatch=is_patch)  File "/usr/lib/vmware-cm/bin/cloudvmcisreg.py", line 700, in cloudvm_sso_cm_register    serviceId = do_lsauthz_operation(cisreg_opts_dict)  File "/usr/lib/vmware/site-packages/cis/cisreglib.py", line 1044, in do_lsauthz_operation    ls_obj.register_service(svc_id, svc_create_spec)  File "/usr/lib/vmware/site-packages/cis/cisreglib.py", line 340, in add_securityctx_to_requests    with self._sso_client.securityctx_modifier(self._stub):  File "/usr/lib/python3.5/contextlib.py", line 59, in __enter__    return next(self.gen)  File "/usr/lib/vmware/site-packages/cis/cisreglib.py", line 240, in securityctx_modifier    self._update_saml_token()  File "/usr/lib/vmware/site-packages/cis/cisreglib.py", line 223, in _update_saml_token    self._uname, self._passwd, token_duration=120)  File "/usr/lib/vmware/site-packages/pyVim/sso.py", line 317, in get_bearer_saml_assertion    ssl_context)  File "/usr/lib/vmware/site-packages/pyVim/sso.py", line 256, in perform_request    raise SoapException(fault, *parsed_fault)
pyVim.sso.SoapException: SoapException:
faultcode: ns0:FailedAuthentication
faultstring: Invalid credentials
faultxml: <?xml version='1.0' encoding='UTF-8'?><S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/"><S:Body><S:Fault xmlns:ns4="http://www.w3.org/2003/05/soap-envelope"><faultcode xmlns:ns0="http://docs.oasis-open.org/ws-sx/ws-trust/200512">ns0:FailedAuthentication</faultcode><faultstring>Invalid credentials</faultstring></S:Fault></S:Body></S:Envelope>


2018-05-10T14:59:56.970Z  Exception: Traceback (most recent call last):  File "/usr/lib/vmware-analytics/firstboot/analytics_firstboot.py", line 161, in register_with_cm    cloudvm_sso_cm_register(keystore, cisreg_spec, key_alias, dyn_vars, isPatch=is_patch)  File "/usr/lib/vmware-cm/bin/cloudvmcisreg.py", line 700, in cloudvm_sso_cm_register    serviceId = do_lsauthz_operation(cisreg_opts_dict)  File "/usr/lib/vmware/site-packages/cis/cisreglib.py", line 1044, in do_lsauthz_operation    ls_obj.register_service(svc_id, svc_create_spec)  File "/usr/lib/vmware/site-packages/cis/cisreglib.py", line 340, in add_securityctx_to_requests    with self._sso_client.securityctx_modifier(self._stub):  File "/usr/lib/python3.5/contextlib.py", line 59, in __enter__    return next(self.gen)  File "/usr/lib/vmware/site-packages/cis/cisreglib.py", line 240, in securityctx_modifier    self._update_saml_token()  File "/usr/lib/vmware/site-packages/cis/cisreglib.py", line 223, in _update_saml_token    self._uname, self._passwd, token_duration=120)  File "/usr/lib/vmware/site-packages/pyVim/sso.py", line 317, in get_bearer_saml_assertion    ssl_context)  File "/usr/lib/vmware/site-packages/pyVim/sso.py", line 256, in perform_request    raise SoapException(fault, *parsed_fault)
pyVim.sso.SoapException: SoapException:
faultcode: ns0:FailedAuthentication
faultstring: Invalid credentials
faultxml: <?xml version='1.0' encoding='UTF-8'?><S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/"><S:Body><S:Fault xmlns:ns4="http://www.w3.org/2003/05/soap-envelope"><faultcode xmlns:ns0="http://docs.oasis-open.org/ws-sx/ws-trust/200512">ns0:FailedAuthentication</faultcode><faultstring>Invalid credentials</faultstring></S:Fault></S:Body></S:Envelope>


During handling of the above exception, another exception occurred:


Traceback (most recent call last):
  File "/usr/lib/vmware-analytics/firstboot/analytics_firstboot.py", line 260, in main    fb.register_with_cm(analytics_int_http, is_patch)  File "/usr/lib/vmware-analytics/firstboot/analytics_firstboot.py", line 172, in register_with_cm    problem_id='install.analytics.cmregistration.failed')
cis.baseCISException.BaseInstallException: {    "resolution": {        "localized": "Please search for these symptoms in the VMware Knowledge Base for any known issues and possible resolutions. If none can be found, collect a support bundle and open a support request.",        "id": "install.analytics.cmregistration.failed.res",        "translatable": "Please search for these symptoms in the VMware Knowledge Base for any known issues and possible resolutions. If none can be found, collect a support bundle and open a support request."    },    "componentKey": "analytics",    "problemId": "install.analytics.cmregistration.failed",    "detail": [        {            "localized": "Analytics Service registration with Component Manager failed.",            "id": "install.analytics.cmregistration.failed",            "translatable": "Analytics Service registration with Component Manager failed."        }    ]
}


2018-05-10T14:59:56.970Z  VMware Analytics Service firstboot failed

Any help or suggestions are greatly appreciated!

Cheers,

Hello,

I have followed some tutorial to install vCenter, we are doing a test lab btw.

But it won't proceed with stage 2 of the installation.

I searched up online and found that I need a DNS entry. So I entered sth like follows into etc/hosts:

vcenter.local  10.10.10.200

and I entered these info in the step 1 installation.

but it still won't proceed to stage 2

I read the error log, and it says, unable to connect to http://10.10.10.200:5480 (I am typing on another machine, this may not be the error msg excacly.)

I am unsure what is happening. Any help would be appreciated.

Thanks!

Hello,

We have some remote hosts, quite far geographically which we connected to our on-premises vcenter. What I see now is that approx every 60 seconds these hosts are shown as "not connected" for a second or two. I've tried the following fix: VMware Knowledge Base (added the heartbeat not responding timeout setting to 120) and what happened is that now the servers go to "not connected" state every two minutes.

Does anyone have an idea on what can be tweaked in order to avoid such behavior?

Hi all,

i i tried upgrade the controller to 6.7.0 it's gave me successful but  when open PSC gave me ( PSC:5480/configure/#/installer?locale=en ) link in Pic , i after that i tried upgrade the appliance and already upgraded to 6.7.0 and working fine but still the controller stuck i tried all solution but nothing working

Thank you

Hello friends!

I am currently working on some tasks that are requiring me to gather several data points from ESXi statistics. I am currently looking to gather the data on a .csv file to then move over to my collection sheet. I would sure appreciate some feedback on commands and scripting to gather these statistics:

CMDs

Reads

Writes

DAVG/cmd/rd/wr

KAVG/cmd/rd/wr

IOPS Highest, Lowest, Average IOPs

I would like to have this populated into a .csv in columns. I found a script that gathers some of the data but it is not exactly what we are looking at collecting.

Any help would be appreciated!

Version 6.0 and 6.5 vCenters sending SNMP traps to 3rd party tool for Host Connection And Power State Alarm. 

vmwVpxdObjValue shows either

alarm.HostConnectionStateAlarm - State = Not responding AND State = Unknown

or

alarm.Host connection and power state - State = Not responding AND State = Unknown

vpxd_Host.connection.and.power.state)|HostConnectionStateAlarm

Cannot determine why events from same vCenter version / build differ in what is sent for this alarm.    Anyone see this before?  Thanks

I just upgraded one of my vCenters to Version 6.5.0.13000 Build 8024368. Now that vCenter can no longer get entries from a content library that is publish from my vCenter at another site, which is Version 6.0.0 Build 6855238. Attempts to sync the library fail with a "General System Error: Internal Error" and attempts to clone individual items fail with something like "Error retrieving files for library item 56b01a77-9817-4eda-abef-e075cb0894ae. Reason: disk-vdcs-1.vmdk: target 'ds:///vmfs/volumes/...//contentlib-45e6a3cd-b7e7-4e43-9e5c-.../56b01a77.../disk-vdcs-1_....vmdk?serverId=...' error: Unable to parse disk image while uploading to: ds:///vmfs/volumes/.../contentlib-.../disk-vdcs-....vmdk?serverId=c4f3fb52-9373-4039-932e-..."

Are content libraries supposed to be compatible between vCenter 6.0 and 6.5?

Looking for a little help here… So we are addressing the Spectre/Meltdown issue by updating the server BIOS & firmware on our HPE ProLiant DL380 G8 population. So we place the targeted ESXi 6.0, 6921384, server into maintenance mode and all of the guest VMs migrate off to the other Host. Once the VMs are gone we mount the Firmware ISO through the vCenter console session and boot the server to it. Once the server spins up the ISO the install menu shows up and I just let the ISO install all of the firmware automatically. Once it finishes installing the server reboots and comes back up. I check to make sure everything looks good if so, I take the server out of maintenance mode. Once out I select the other ESXi Host in the pair and place it in Maintenance Mode. In the vCenter console Tasks it will show all of the guest VMs that are going to vMotion off and shows the progress. So the first 4 VMs show progress right up to about 74% and begin erroring out with “Failed to receive migration”. The error stack states, “The source detected that the destination failed to resume. Failed to receive migration.”

My first thought was to check resources, no problem. Next I went to restart the vCenter services, didn’t clear it up. I tried to vMotion one VM at a time, still got the error. At this point I’m stuck. The funny thing is I used the same update process on larger clusters and never had an issue. It’s only happening on smaller, 2 – 3 Host clusters.

All tips, tricks and advice accepted and appreciated.  Thanks

I am facing with vcenter virtualcenter server service can't start . Error code is 1068.

The vcenter version is 6.0 u2 and hosts are 6.0u3.

Hi,

I have a cluster with HP G9 servers, I have added a new G10 server that has a different microarchitecture.

I was able to vmotion VM's between the old hosts and the new G10 host in both directions without issue.

Should i still enable EVC Mode in this cluster?

If I was to enable EVC mode, does that mean downtime on any of my hosts/VM's?

Thanks in advance,

Stephen

Hello Everybody,

after installing Update manger in the Vcenter, I have all objects menu wich are grayed out.

Have you any idea please.

Best regards.

Hey,

we just upgraded from 6.5 to 6.7 Appliance and are now having trouble with logging into the flash client. HTML5 works fine, but after logging in into the flash client, nothing happens...

Thanks for help in advance.

Cheers,

Daniel

Hello.

I've seen this problem posted by other members and could use some help.

The eam.properties file in /etc/vmware-eam/ has this content:

eam.web.root=/usr/lib/vmware-eam/web

eam.web.root=/usr/lib/vmware-eam/web

That looks a far cry from anything normal or what?

Please help.

Best Regards

Peter Rasch Lageri

Does anyone know how to set the response headers on the VMWare VCenter Server Appliance?

Looking to mitigate the vulnerabilities by being able to set the following on the appliance

"Strict-Transport-Security"

"X-Frame-Options" => "SAMEORIGIN",

"X-Content-Type-Options" => "nosniff"

Im trying to deploy a new machine SSL with VCenter 6.5 from a public CA. Ive spent 3 days with multiple failures. This being the latest. Ive followed every vmware instructional video and guides for 5.5 and 6.0 but we cannot deploy a Public CA SSL cert so far. it gets to 10% and kicks an error message. Ive tried every variation of certs. We get issued a CA-Bundle, and p7b and a crt file. We cannot figure out what vcenter certificate manager is wanting from these certs. Ha any one else faced this issue?

2017-01-13T15:10:04.706Z ERROR certificate-manager

2017-01-13T15:10:04.707Z ERROR certificate-manager Error while replacing Machine SSL Cert, please see C:\ProgramData\VMware\vCenterServer\logs\vmca\certificate-manager.log for more information.

2017-01-13T15:10:04.707Z ERROR certificate-manager {

    "resolution": null,

    "detail": [

        {

            "args": [

                ""

            ],

            "id": "install.ciscommon.command.errinvoke",

            "localized": "An error occurred while invoking external command : ''",

            "translatable": "An error occurred while invoking external command : '%(0)s'"

        },

        "Error in creating a new entry for __MACHINE_CERT in VECS Store MACHINE_SSL_CERT."

    ],

    "componentKey": null,

    "problemId": null