Quantcast
Channel: VMware Communities: Message List - vCenter™ Server
Viewing all 15787 articles
Browse latest View live

Re: Update Manager errors after 6.0 to 6.5.0 upgrade

$
0
0

Hi!

 

Do you mean that you have external Update manager and you can't connect it to vcenter servers?

I'm asking because update manager is embeded into VCSA 6.5 now and I don't fully understand your issue.

 

Hi.  Sorry I did not clarify.  No, we are using the integrated (embedded) Update Manager on the VCSA (appliance).  We've never had a separate Update Manager here, so when we upgraded it upgraded from the previous integrated Update Manager.

 

The issue we are having is all when going to Update Manager through the web client (Flash version), in various areas we get the errors I described earlier.  I also tried uploading an ESXi image today, and the upload succeeded however the image does not show up in the list of images, just just says "this list is empty".  However if I upload again, it says that it exists.  So it seems we are having UI (web page) issues with Update Manager and I am not sure how to fix.

 

Thank you.


Re: Update Manager errors after 6.0 to 6.5.0 upgrade

Re: Update Manager errors after 6.0 to 6.5.0 upgrade

Re: [Help] Platform services controller error 500

$
0
0

I recently had the same issue on VCSA - after joining the PSC to AD domain and rebooting, I received an identical HTTP Status 500 error page.

It looks like it is a cookie issue, so opening a "private" browser (private/inprivate/incognito/etc...) with no cookies will resolve your issue immediately, or close/re-open browser or clear browser cookie(s) should also resolve the issue.

 

Tip: In Chrome, clicking on the "Secure" text in URL bar will show details about connection, clicking on the "x in use" link under Cookies will display the current page's cookies and let you view or remove them. The cookies I had all said "Expires: When the browsing session ends".

Specifically, clearing/removing the JSESSIONID cookie and reloading the page will create a new session.

Brian

Re: VC 6.5 Install failure - identity management service error on first boot

Re: Changing default gateway on vCenter Appliance version 6

$
0
0

1. Open a console session of vCenter Appliance 6 >>> Type "root" >>> Type "Password of root" >>> Run below cmd.

2. # /opt/vmware/share/vami/vami_config_net
3. # Enter No. 2 to change the default gateway >>> enter new gateway >> exit .

 

 

Try this and it will help you .

Re: Unable to login to vSphere Web Client - [500] SSO error: Cannot connect to the VMware Component Manager

Re: Changing default gateway on vCenter Appliance version 6

$
0
0

use below command by taking Vcsa on putty.

 

yast

 

 

it will show you the option to change the ip configuration alternatively you can use vcsa configure portle.

 

https://vcenter-server-fqdn:5480

 

Thanks

Vmwarediary.com


Re: Cannot Start vCenter Server Appliance - "Waiting for vpxd to initialize: ....failed"

$
0
0

This absolutely worked for me. Thank you!

 

In my case, I do not believe I had ran out of space first (df -h was reporting fine).

Re: Deplolying VCenter Server Appliance

$
0
0

Hi,

 

I'm redoing the steps one by one. blocked at step 6! can you help resolve this?

 

1. download hypervisor 6.5 iso

2. download vcsa 6.5 iso

3. download workstation pro

4. install workstation

5. create new VM (for ESXi host). screenshot attached.

6. install vcenter appliance on this ESXi host. Getting "failed to get thumbprint" error. screenshot attachedESXi host.pngvcsa error.png

Re: Deplolying VCenter Server Appliance

$
0
0

Why not just deploy vCSA natively on Workstation? You don't need to do so inside ESXi.

Re: Deplolying VCenter Server Appliance

$
0
0

HI ,

 

vcenter 6.5 installation required proper DNS resolution   .

 

You may create dns records on the host you are trying to deploy VCSA , ESXI hosts , and the Lab hosted machines .

 

If you have DNS server and adding all records over there will be more helpful , because adding local entry sometimes fails .

Re: vSphere client on a Windows 10 machine - mouse problems inside VM consoles

$
0
0

In my case, I can't seem to find that option to Disable High DPI scaling under Windows 10 Creator's update (1709).

I tried individual options under Override high DPI scaling behavior but all still did not show the mouse cursor

EVC issue

$
0
0

Greetings,

 

I'm trying to create new cluster with EVC Nephalem mode (issue happens in any mode). I have vCSA 6.5.0.14100 Build Number 7801515. My host is VMware ESXi, 6.5.0, 7388607. I'm creating new cluster object, enabling EVC mode and trying to move my host in there. The error is like following

 

The host's CPU hardware should support the cluster's current Enhanced vMotion Compatibility mode, but some of the necessary CPU features are missing from the host.  Check the host's BIOS configuration to ensure that no necessary features are disabled (such as XD, VT, AES, or PCLMULQDQ for Intel, or NX for AMD). For more information, see KB articles 1003212 and 1034926.

 

vpxd.log shows the following

 

2018-02-26T14:52:38.553Z info vpxd[7F522172E700] [Originator@6876 sub=Default opID=HostMigrationActionCommand-apply-85510-ngc:70011794-99] [VpxLRO] -- ERROR task-6320 -- domain-c1205 -- vim.ClusterComputeResource.moveInto: vim.fault.EVCAdmissionFailedCPUFeaturesForMode:

--> Result:

--> (vim.fault.EVCAdmissionFailedCPUFeaturesForMode) {

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

-->    faultMessage = <unset>,

-->    productName = <unset>,

-->    productVersion = <unset>,

-->    faults = (vmodl.MethodFault) [

-->       (vim.fault.FeatureRequirementsNotMet) {

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

-->          faultMessage = <unset>,

-->          featureRequirement = (vim.vm.FeatureRequirement) [

-->             (vim.vm.FeatureRequirement) {

-->                key = "cpuid.IBPB",

-->                featureName = "cpuid.IBPB",

-->                value = "Bool:Min:1"

-->             },

-->             (vim.vm.FeatureRequirement) {

-->                key = "cpuid.IBRS",

-->                featureName = "cpuid.IBRS",

-->                value = "Bool:Min:1"

-->             },

-->             (vim.vm.FeatureRequirement) {

-->                key = "cpuid.STIBP",

-->                featureName = "cpuid.STIBP",

-->                value = "Bool:Min:1"

-->             }

-->          ],

-->          vm = <unset>,

-->          host = 'vim.HostSystem:ha-host'

-->          msg = "The target host does not support the virtual machine's current hardware requirements."

-->       }

-->    ],

-->    currentEVCModeKey = ""

-->    msg = "The host's CPU hardware should support the cluster's current Enhanced vMotion Compatibility mode, but some of the necessary CPU features are missing from the host.  Check the host's BIOS configuration to ensure that no necessary features are disabled (such as XD, VT, AES, or PCLMULQDQ for Intel, or NX for AMD). For more information, see KB articles 1003212 and 1034926."

--> }

--> Args:

-->

--> Arg host:

--> (ManagedObjectReference) [

-->    'vim.HostSystem:e3a5d87e-e2c2-4c61-991b-b703c695bf34:host-790'

--> ]

 

Using PowerCLI I can confirm that cpuid.IBRS, cpuid.IBPB and cpuid.STIBP are not exposed. I've tried to check for updates, but there are none. Is there any way to "hot add" host to EVC cluster? (If I'm adding hosts before enabling EVC it can be enabled afterwards.)

Re: vSphere client on a Windows 10 machine - mouse problems inside VM consoles

$
0
0

I've redownloaded the vsphere client from my vcenter via browser and installed it (uninstalling my existing one) and it's working now.


Re: vMotion not showing available hosts

$
0
0

I have the same problem. Vcenter 6.5 (in Windows platform) and ESXi Host 6. In my case, the workaround of chage CD to shared iso its not working. Any news about that?.

ESX 5.5 migration to 6.0 - SSL issue

$
0
0

Hi folks,

 

I've started today the migration of our 5.5 into 6.0. During pre-checks, an SSL issue came out

"Error: vCenter CA certificate not verified. Stopping...."

ScreenShot136.jpg

 

I've googled and find out that SSL have to be renewed.

I've followed that guide : https://anthonyspiteri.net/upgrading-windows-vcenter-5-5-to-6-0-in-place-issues-and-fixes/

which then lead to :  VMware Knowledge Base  and  https://anthonyspiteri.net/dealing-with-a-revoked-vcenter-ssl-certificate/

New SSL were created, vxpd -p has been used in order to generate a new password and services were restarted.

I've used the VmWare Certificate automation tool and here starts the mess.

Right after using 5, 2 options, I'm entering all the requested credentials, and it fails with the error :

 

[27/02/2018 - 14:55:44.94]: Validating the configuration and state of vCenter Server

 

---------- C:\PROGRAMDATA\VMWARE\VMWARE VIRTUALCENTER\VPXD.CFG

[27/02/2018 - 14:55:45.01]: Validating the input parameters...

        STATE              : 4  RUNNING

HTTPError: Unable to open or read page.

HTTP Error 401: basic auth failed

[27/02/2018 - 14:56:10.56]: "Cannot log in to vCenter."

[27/02/2018 - 14:56:10.56]: The vCenter certificate update failed.

 

Current status:

- I cannot logon on vSphere.

- VmWare VirtualCenter Server service starts

- VmWare VirtualCenter Management WebServices service keeps on crashing after a few seconds.

- I'm notable to login with all accounts I've got on https://localhost/mob/?moid=vpxd-securitymanager&method=reloadSslCertificate&vmodl=1

 

What would you recommend to do in order to quickly fix this? Reinstall vSphere 5.5 first?

Please share your thoughts.

 

Regards,

poy

Re: ESX 5.5 migration to 6.0 - SSL issue

$
0
0

Hi PoY00ch

 

Your SSL certificate on vCenter 5.5 is CA signed SSL certificate or deault-self signed certificate??

 

We had similar issue (one of our vcenter had self-signed certificate) and below was the steps we followed to fix:

To resolve this issue, toggle the certificate settings on the source vCenter Server Appliance to regenerate new certificates with the appropriate hostname and IP address.

 

To toggle the certificate settings:

  1. Log in to the source vCenter Server Appliance Web interface at https://Source_vCenter_Server_Appliance_FQDN:5480/.
  2. Click the Admin tab.
  3. Regenerate certificates:
    • vCenter Server 5.5: Select Yes under Certificate regeneration enabled.
  4. Click Submit.
  5. Reboot the vCenter Server Appliance.
  6. After the vCenter Server Appliance reboots, ensure that the Certificate regeneration enabledoption is set todisabled and disable if it is enabled.

After completing, attempt to upgrade the vCenter Server Appliance 5.x to vSphere 6.0.

 

This is from KB :VMware Knowledge Base

 

Other error w.r.t extensions can be fixed after upgrade by removing the old extensions from vcenter MOB and re-register again with vcenter.

How to delete or unregister vSphere Replication extension or plugin from vCenter Server MOB – HyperVMwareCloud

Migrate vCenter Appliance (SUSE) from one host to another host

$
0
0

- I have VMware system with below information:

+ 01 vCenter Appliance ( running SUSE) on host A

+ Information vCenter:

- OS: SUSE

- Storage: local data store host A

- Configed standard switch and distributed switch for vCenter system.

- I want to migrate vCenter host A to host B. Can you show me how?

Thank you very much

Re: ESX 5.5 migration to 6.0 - SSL issue

$
0
0

Hi rajen450m

 

thanks for your message and for your suggestion.

 

it's actually for a self signed certificate.

 

Sadly, I can't reach the website on port 5480. I've tried even on the server itself, with localhost, doesn't answer.

 

However, the address https://Source_vCenter_Server_Appliance_FQDN/mob works but I can't login with any of my credentials.

 

Any ideas/suggestions?

Regards,

Poy

Viewing all 15787 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>