Hey all -

I have an external PSC deployed at each site using the same SSO domain.  Site 1 was deployed first - created a new SSO domain.  Deployed VCSA there, all is well.  Site 2 was deployed second with external PSC, joined existing SSO domain specifying the IP of the first PSC.  Deployed 2nd VCSA, all is well.

I can log in as SSO admin or AD and see Site 1 and Site 2 from site 2 VCSA.  However, at Site 1, I can see the two PSCs and two VCSA in "Nodes" under System Deployment, but I cannot see the vCenters, just the single Site 1 VCSA.

Any pointers?

Hi all - just getting around to toying with external PSC and VCSA.  All is well, but I can't use the enhanced auth plugin by going to https://[vcsa-fqdn/vsphere-client/?csp but if I go to "Platform Services Controller web interface" https://[psc-fqdn]/websso/SAML2/SSO/... the check box presents itself.  Granted, that only logs me into the PSC and I can't do much from there.  However, if I revisit https://[vcsa-fqdn/vsphere-client/?csp I get logged right in.  Kind of irritating.  Any thoughts?

I created  a Microsoft  KMS server to activate new VM's and was told that the Vsphere host has to be configured to connect to the KMS server to activate, is there documentation or does anyone know how to do this? I've searched google and have not seen anything. Thanks.

Mitch

Is anyone else experiencing a failure when installing VC 6.5?  I have this occuring when installing using the CLI installer, and when deploying the OVA using the ESXi web client.

The version of VC is 6.5.0 build 4240420, the recent release candidate.

The exception report looks like:

Encountered an internal error. Traceback (most recent call last): File "/usr/lib/vmidentity/firstboot/vmidentity-firstboot.py", line 2017, in main vmidentityFB.boot() File "/usr/lib/vmidentity/firstboot/vmidentity-firstboot.py", line 349, in boot self.configureSTS(self.__stsRetryCount, self.__stsRetryInterval) File "/usr/lib/vmidentity/firstboot/vmidentity-firstboot.py", line 1478, in configureSTS self.startSTSService() File "/usr/lib/vmidentity/firstboot/vmidentity-firstboot.py", line 1140, in startSTSService returnCode = self.startService(self.__sts_service_name, self.__stsRetryCount * self.__stsRetryInterval) File "/usr/lib/vmidentity/firstboot/vmidentity-firstboot.py", line 88, in startService return service_start(svc_name, wait_time) File "/usr/lib/vmware/site-packages/cis/utils.py", line 784, in service_start raise ServiceStartException(svc_name) ServiceStartException: { "resolution": null, "detail": [ { "args": [ "vmware-stsd" ], "id": "install.ciscommon.service.failstart", "localized": "An error occurred while starting service 'vmware-stsd'", "translatable": "An error occurred while starting service '%(0)s'" } ], "componentKey": null, "problemId": null }

My group and I am curious to hear whether or not anyone else is experience this and if there are any workarounds.

Thanks!

Our vCenter currently running on vCenter 5.5 and we would like to go with 6.5 (Windows installtion) rather 6.0. What is the process?

What all things I need to take backup before I proceed for upgrade. Will DB backup enough to go for vCenter upgrade. Its production environment. Please suggest.

Additional Component associated.

1. Update Manager

2. SRM

3. Orchestrator

4. DB Switch.

5. SSO

6. Replication

6. Some more Plugin installed.

Thanks,

Bijendra

Hi

LAN

I’m Setting up a new test environment with 3 ESXi Server which controlled by vCSA.

1^st ESXi VMware ESXi 6.0.0 build-3620759

2^nd ESXi VMware ESXi 6.0.0 build-5050593

3^rd ESXi VMware ESXi 6.0.0 build-5050593

vCSA Version 6.0.0.30000

The issue is, I’m unable to access the vCenter via vSphere web client inside the network and outside the network.

When I access the vCenter vSphere web client in LAN using the below browser

Opera Version: 44.0.2510.1218 (PGO)

Internet Explorer: Version 11.0.14393.0

FlashPlayer : Version WIN 11,5,500,104

I’m getting the login page but post key in my credential it was white page.  Please find screenshots file name "IE" & "Opera"for reference.

But when I try to access the vSphere Web client using the below browser from the same server where I have accessed earlier, I don’t find any issue. I able to see the hosts and VMs inventory etc., Works fine.

Firefox : Version 54.0.1 (64-bit)

Chrome : version 51.0.2704.103 m (64-bit)

FlashPlayer : Version WIN 11,5,500,104

---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

WAN

Now When I try to access the vSphere web client form external network (WAN) with the below browser

Chrome: Version 59.0.3071.115 (Official Build) (64-bit)

Opera: Version 46.0.2597.46 (PGO)

Internet Explorer: Version 11.1480.14393.0

FireFox : Version 54.0.1 (64-bit)

vSphere Web Client : Version 6.0.0 Build 5112533

FlashPlayer : Version WIN 11,5,500,104

Its redirecting me to https://<vCenter> /websso/SAML2/SSOSSL RelyingPartyEntityId=aHR0cHM6Ly8xMzAuMTc1LjEwOS4xMTM6OTQ0My92c3BoZXJlLWNsaWVudC9zYW1sL3dlYnNzby9tZXRhZGF0YQ==

I Treid with port no 9443 in the url as https://<vCenter>:9443/vsphere-client it also redirect me to

https://<vCenter> /websso/SAML2/SSOSSL?RelyingPartyEntityId=aHR0cHM6Ly8xMzAuMTc1LjEwOS4xMTM6OTQ0My92c3BoZXJlLWNsaWVudC9zYW1sL3dlYnNzby9tZXRhZGF0YQ==

Also please find below screenshots file names "Opera" & "Chrome"  for different errors in different browser.

---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

I have gone thru many articles and VMware Discussion forums and non of them resolve my issue.

My Query

1) I could like to know the reason how come I'm able to access vSphere web Client in LAN using "FireFox" & "Chorme"  but not able to access using "IE" or "Opera"?

2) Also I could like to know the reason how come the same vCenter when I access via WAN redirect to "websso/SAML2/SSOSSL RelyingPartyEntityId"

Much appreciated if some one help me to get this resolved.

Thanks

MSG

Hi experts,

I tried to install vCenter 6.0, and got the following error:

• Installation of component VCSServiceManager failed with error code '1603'. Check the logs for more details.

Checked the release notes, ipv4 stack is all fine.

I tried a couple of times, couldn't overcome this. Also tried to upgrade from 5.5 to 6.0, failed with the same error.

How can I overcome this?

Thanks a lot for your help!

Forget to mention: I am installing this on Windows Server 2008 R2 Standard

After reading http://kb.vmware.com/kb/2003322 and doing some experimentation I'm trying to figure out if it is possible to use Host Profiles to configure syslog to use a local VMFS datastore. I have come up with these approaches, none of which do what I want:

1) Create a local VMFS datastore, e.g. "Datastore1", on each host and set "Syslog.global.logDir" to "[Datastore1] /Syslog". The problem with this approach is that I end up with name collision on the Storage view in vCenter.

2) Create a local VMFS datastore, e.g. "<ESXi hostname>--Datastore1", on each host which avoids the name collision problem, but then I can't (apparently) use "Host Profiles".

3) Set "Syslog.global.logDir"  to some shared storage and set "Syslog.global.logDirUnique" to True, but then this isn't using a local VMFS datastore.

My concern is that my shared storage is all IP based (both iSCSI and NFS). I was hoping to use a local datastore to add some resiliency to syslog.

Thanks.

Dear all,

during a trouble-shooting session, I accidentally removed the com.vmware.cis.inventory from MOB browser.

Naturally, now my vsphere seems to have no inventory. Neither the HTML5 nor the Flash Gui show anything.

Is there a way to fix this issue? I have restarted the vcenter vm already but to no avail.

I'm running VMware vCenter Server Appliance patch level 6.5.0.5600

Needless to say I'm desparate  ...

Thanks for your help, Peter

If a root password has expired (even though we can still SSH into vCenter with it), and you then change it to never expire, is the current password still considered needing to be changed? We're not sure if it's a chicken before the egg thing. We're hoping to just make the account never expire, and leave the password as is.

Unless someone knows the password memory of the account. IE does it not care if you used a password 1 password back, or needs to be unique going back 10 passwords. If so, I'll change it once, change it back to what I want, and set it to never expire.

Thanks.

Hi all,

Is it required to have the VIP of the NLB already configured and operating BEFORE the final command to configure PSC HA is run (UpdateLsEndpoint)?

i.e. Before you run the last command for the PSC HA, the actual NLB VIP is already configured and functioning?

I ask this as I need to deploy a vCenter/PSC before I deploy NSX and I wanted to use the NLB function of NSX to allow me to protect the PSCs with HA/NLB.

So, in the interest of saving a few minutes, I was thinking that I might be able to install 2 extra PSCs in the environment in parallel and configure them as much as possible for PSC HA.

Then deploy the NSX and NLB and configure the VIP for the PSC NLB.

Then finally just repoint the vCenter to the PSC NLB.

However trying all that in my test lab, I am seeing that the last command is failing and I saw the words "No route to host (Host unreachable)" in the output.

So I suspect that the command is somehow trying to reach the PSCs through the NLB IP and, as I don´t yet have that configured, is failing.

Does that sound right?

If it is correct it isn´t a big deal as I will just leave that last command until the NSX and NLB is 100% ready.

I just wanted to check if that was indeed the case to confirm my suspicions.

By the way I deployed the PSCs using the ISO for vCenter appliance 6.5 GA

Thanks in advance

Mark

Salutations,

I am about to install VSphere 6.5e and am wondering if FT will cover the PSC or not. Help?

Hello guys,

We are looking for some kind of logs for all the REST API calls that we made thought our VCenter 6. Like POST https://{server}/rest/vcenter/vm

We've looked at this URL to find some info about log location : https://virtualizationexpress.com/2014/01/01/log-locations-vmware-products/comment-page-1/#vcenter6

We first through about vapi / endpoint.log but we can't see that we are looking for.

Is there a way to find that kind of info ?

Many thanks,

Arnaud

Chokes on the vcsservicemanager with a dialog box merely saying i"nternal error"? Tail of vminst.log is below:

2017-07-27 13:00:36.065-04:00| vcsInstUtil-4944578| I: LaunchPkgMgr: Hiding the cancel button

2017-07-27 13:00:36.065-04:00| vcsInstUtil-4944578| I: Entering function: PitCA_HideCancelButton

2017-07-27 13:00:36.065-04:00| vcsInstUtil-4944578| I: PitCA_HideCancelButton: Successful in hiding the Cancel button.

2017-07-27 13:00:36.065-04:00| vcsInstUtil-4944578| I: Leaving function: PitCA_HideCancelButton

2017-07-27 13:00:36.065-04:00| vcsInstUtil-4944578| I: LaunchPkgMgr: Telling child to install "D:\vCenter-Server\Packages\vcsservicemanager.msi" with "ALLUSERS=1 ARPSYSTEMCOMPONENT=1 INSTALLPATH="C:\Program Files\VMware\vCenter Server\" APPDATAPATH="C:\ProgramData\VMware\vCenterServer\" PARENTUILEVEL=5 DEBUG_SKIP_ROLLBACK=0 FIRSTBOOT=1 UPDATEBOOT=1 UPGRADEBOOT=1 VM_UPGRADE="" " details 1

2017-07-27 13:00:36.081-04:00| vcsInstUtil-4944578| I: wWinMain: Exe is told to run "D:\vCenter-Server\Packages\vcsservicemanager.msi" with "ALLUSERS=1 ARPSYSTEMCOMPONENT=1 INSTALLPATH="C:\Program Files\VMware\vCenter Server\" APPDATAPATH="C:\ProgramData\VMware\vCenterServer\" PARENTUILEVEL=5 DEBUG_SKIP_ROLLBACK=0 FIRSTBOOT=1 UPDATEBOOT=1 UPGRADEBOOT=1 VM_UPGRADE="" " details 1

2017-07-27 13:00:39.267-04:00| vcsInstUtil-4944578| I: Entering function: VM_RunFirstBoot

2017-07-27 13:00:39.267-04:00| vcsInstUtil-4944578| I: RunFirstLastUpdateboot: Action Started

2017-07-27 13:00:39.267-04:00| vcsInstUtil-4944578| I: RunFirstLastUpdateboot: Established explicit progress

2017-07-27 13:00:39.267-04:00| vcsInstUtil-4944578| I: RunFirstLastUpdateboot: DEBUG: silentMode 0

2017-07-27 13:00:39.267-04:00| vcsInstUtil-4944578| I: RunFirstLastUpdateboot: Told to run "C:\Windows\system32\cmd.exe /S /C ""C:\Program Files\VMware\vCenter Server\bin\run-firstboot-scripts.bat" >> C:\Users\gchamby\AppData\Local\Temp\vminst-con.log 2>&1""

2017-07-27 13:00:39.267-04:00| vcsInstUtil-4944578| I: RunFirstLastUpdateboot: got current env variable: "C:\ProgramData\VMware\vCenterServer\logs"

2017-07-27 13:00:39.267-04:00| vcsInstUtil-4944578| I: RunFirstLastUpdateboot: Got log env var: "C:\ProgramData\VMware\vCenterServer\logs"

2017-07-27 13:00:39.267-04:00| vcsInstUtil-4944578| I: RunFirstLastUpdateboot: Status file directory is "C:\ProgramData\VMware\vCenterServer\logs\firstboot\"

2017-07-27 13:00:39.267-04:00| vcsInstUtil-4944578| I: RunFirstLastUpdateboot: Status file path is "C:\ProgramData\VMware\vCenterServer\logs\firstboot\fbInstall.json"

2017-07-27 13:00:39.267-04:00| vcsInstUtil-4944578| I: RunFirstLastUpdateboot: Monitoring common status file

2017-07-27 13:00:39.267-04:00| vcsInstUtil-4944578| I: Entering function: LaunchProcAndMonitorCommonStatusFile

2017-07-27 13:00:39.267-04:00| vcsInstUtil-4944578| I: Entering function: LaunchProcAndMonitorStatus

2017-07-27 13:00:39.267-04:00| vcsInstUtil-4944578| I: LaunchProcAndMonitorStatus: Launching "C:\Windows\system32\cmd.exe /S /C ""C:\Program Files\VMware\vCenter Server\bin\run-firstboot-scripts.bat" >> C:\Users\gchamby\AppData\Local\Temp\vminst-con.log 2>&1"" in "C:\Windows\system32\"

2017-07-27 13:00:39.267-04:00| vcsInstUtil-4944578| I: LaunchProcAndMonitorStatus: Launched process with pid 2672 tid 4412

2017-07-27 13:00:39.267-04:00| vcsInstUtil-4944578| I: Entering function: MonitorStatusFile

2017-07-27 13:00:39.267-04:00| vcsInstUtil-4944578| I: MonitorStatusFile: Status file directory is "C:\ProgramData\VMware\vCenterServer\logs\firstboot\"

2017-07-27 13:00:39.267-04:00| vcsInstUtil-4944578| I: MonitorStatusFile: Monitoring directory "C:\ProgramData\VMware\vCenterServer\logs\firstboot\" for file "fbInstall.json"

2017-07-27 13:00:39.267-04:00| vcsInstUtil-4944578| I: MonitorStatusFile: Started execution of process

2017-07-27 13:00:52.744-04:00| vcsInstUtil-4944578| I: Entering function: ParseStatusFile

2017-07-27 13:00:52.744-04:00| vcsInstUtil-4944578| I: ParseStatusFile: STATUS: 0%: ""

2017-07-27 13:00:52.744-04:00| vcsInstUtil-4944578| I: ParseStatusFile: Calling callback with 0 -> 0 ""

2017-07-27 13:00:52.744-04:00| vcsInstUtil-4944578| I: Entering function: UpdatePkgMgrProgressFromStatusFile

2017-07-27 13:00:52.744-04:00| vcsInstUtil-4944578| I: ProcessMsiMsg: ACTIONDATA reporting ""

2017-07-27 13:00:52.744-04:00| vcsInstUtil-4944578| I: Leaving function: UpdatePkgMgrProgressFromStatusFile

2017-07-27 13:00:52.744-04:00| vcsInstUtil-4944578| I: Leaving function: ParseStatusFile

2017-07-27 13:00:56.218-04:00| vcsInstUtil-4944578| I: Entering function: ParseStatusFile

2017-07-27 13:00:56.233-04:00| vcsInstUtil-4944578| I: ParseStatusFile: curr error msg: "The installation of vCenter Server failed due to an internal error."

2017-07-27 13:00:56.233-04:00| vcsInstUtil-4944578| E: ParseStatusFile: Displaying error message for "VMware vCenter Server": "The installation of vCenter Server failed due to an internal error.

This is an unrecoverable error, please retry install. If you run into this error again, please collect a support bundle and open a support request."

Running multiple ESXi 5.5u3 Build 3248547hosts & vCenter Server Version 5.5.0 Build 3000241.   After installing patch ESXi550-20151001 I am unable to connect to hosts that have been disconnected.   When attempting to connect I get the following error:

"

Reconnect host

vmhost3.oemstorage.loc

Datastore 'XXXX' conflicts with an existing datastore in the datacenter that has the same URL (

ds:///vmfs/volumes/XXXXXXX/), but is backed by different physical

storage.

root

vcenter

If I back out the patch the problem goes away and I can successfully re-connnect the host.  (I've actually fully patches the system, and isolated it down to the individual update mentioned in this thread).   Has anyone seen this, and know of a solution?   VMware support has been contacted, but said it was a storage issue.  We've had the same problem with multiple vendors, so I don't believe this to be the case.

Hi.

I setup ESXI 6.5 on a server with 2 NICS. The first NIC is what was assigned as the management network and is connected directly to LAN (same network). I require to attach the second NIC to a different network. My VMs can access and be reached on the first NIC but not on the second NIC. Below are the issues faced when trying to use the 2nd NIC

• It can ping machines in the network of the second NIC but those same machines cannot ping it.
• It can ping its own VMKernel NIC IP but the host machine cannot ping the IP of the VMs

Hi,

from time to time the VCSA 6.5e statsmonitor service stops unexpectedly. This breaks the ability to backup VCSA data via PowerCLI script. Another consequence is that there are no CPU/Memory/Database Statistics collected in VCSA management backend.

vRealize LogInsight Log excerpt is attached for the considered timeframe and filtered by "statsmonitor". I cannot tell from this log why it tried to add this service, tried to start it and then failed.

So the stop occurred on June, 13th for the last time. It remained stopped since then. Before June, 13th, I realized it and fixed it on June, 8th.

I see this problem occurring one one of our VCSA 6.5 instances but not on the other ones.

Does anyone else see this behavior or any idea what's wrong?

I have been trying to get a host (ESXi 6.0.0 Update 3 build-5050593) to join a dvSwitch (6.0) using a Host Profile and it keeps failing. This fails for other hosts too. The error in vpxd.log is:

2017-07-31T17:22:31.697-04:00 info vpxd[08692] [Originator@6876 sub=Default opID=cf4e050b-b76b-4d35-b606-22a540f3cd34-2106-ngc-f] [VpxLRO] -- ERROR task-2910 -- HostProfileManager -- vim.profile.host.ProfileManager.applyHostConfiguration: vmodl.fault.InvalidArgument:

--> Result:

--> (vmodl.fault.InvalidArgument) {

-->    faultCause = (vmodl.MethodFault) null,

-->    invalidProperty = "dvsName",

-->    msg = ""

--> }

After a number or rounds of testing I have stripped down a full Host Profile to just "Host Profile > Networking configuration > vSphere Distributed Switch > [DvSwitch Instance] >Uplink port configuration > 2 x [Uplink port configuration]". vmk0 is on a Standard Switch. Other iterations included more of the "Host Profile > Networking configuration" branch, and all cases failed with the same error. I tried resetting the configuration of the host, rejoining to vCenter but this also did not work.

At one point I thought ESXi600-201504401-BG might be the fix, but this is more than two years old and I'm not doing any stateless/AutoDeploy thing at this time.

So, is it possible to join a host to a dvSwitch using a Host Profile?

Hello,

We have recently downloaded and installed vCenter and vSphere Replication for an evaluation period on one of our two ESXI host.

I believe that I was successfully able to download and install VRA; however, I do not see an icon for vSphere Replication in vCenter.  Does anyone have any suggestions as to what the issue could be?

Thanks in advance,

                            Reese

When running VI Client 4 or 4 U1, on Vista SP1 x64, I get the following error message.

The type initializer for threw an exception for 'VirtualInfrastructure.Utils.ClientsXml' threw an exception.

and the VI Client exists.

Any ideas, I've found similiar with users running on Windows 7, I've followed those treads, but it still gives me the error message, VI Client used to work, but has stopped.

e.