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

Remove ESXi host from vCenter greyed out

$
0
0

Environment:

 

VMware ESXi, 6.7.0, 15160138

vCenter: 6.7.0.41000 build number: 14836122

 

We cannot remove one crashed VMware host from our datacenter. We do not have any clusters configured. We do have a vDS. Other hosts are working fine and in production. Remove from inventory is greyed out in vCenter.

 

The following action I already tried:

 

Disconnect the host (succesfully)

Remove host from vDS (succesfully)

Remove from inventory is greyed out

Used PowerCLI but came with this error:

 

Remove-VMHost : 21-4-2020 08:23:16      Remove-VMHost           The method is disabled by 'com.vmware.vcIntegrity'

At line:1 char:1

+ Remove-VMHost ESXVN0XX.FQDN

 

Any ideas?


Re: Invalid credentials for newly added user

$
0
0

Hello! Url is do not work. I have this problem.

Invalid credentials for newly added user

$
0
0

I'm running a vCenter Server 6.5. There's no problem logging into vCenter SSO with the default administrator-user. However, I've tried adding a new user but I'm simply not allowed to login with it, I've added it to all the administrator-groups in vCenter too for the sake of testing. It's in the same local domain as the administrator "@vsphere.local" (which I'm using to login as well) and for simplicity I've even given them the same password. It's joined to AD or such, local users. But all I get is "Invalid credentials" when I try to use it when I try to loggining with newly added users..

 

I see this community Invalid credentials for newly added user  but url http://www.virtuallypeculiar.com/2016/11/vsphere-65-login-to-web-client-fails.html does not open.

Re: vCenter 6.5 to 6.7 upgrade

$
0
0

i asked about 6.5U3g no u3f.

due to the matrix that is not back in time scenario.

Re: vCenter 6.5 to 6.7 upgrade

$
0
0

already compared.

the matrix and the "back in time" KB conflicts.

Re: vCenter 6.5 to 6.7 upgrade

$
0
0

Did you see the exceptions in the KB article?

Due to recent out-of-band patching for PhotonOS, there are versions of vCenter Server with a release date that appear to make them supported upgrade paths, but would still create a regression of code.

These are detailed below:

  • vCenter Server Appliance 6.5 U3f > vCenter Server Appliance 6.7 U3f
  • ...

This means that v6.5 U3f (or later) cannot be upgraded to v6.7 U3f (or earlier).

 

André

Re: Remove ESXi host from vCenter greyed out

$
0
0

What was the solution?

 

The "com.vmware.vcIntegrity" referrers to VMware Update Manager.

 

Regards,

Joerg

vSphere 6 standard - sso

$
0
0

The admin walked out the door and I have no access other than RDP into the server and use my windows login.

Any advice on how to promote to have the sso role. My backup server cant login remotely to run back ups.

 

I used to be able to run the client from my desktop and login using my admin account. But now I can only run the client from the actual server.

Any advice or documentation to help me get this function back?

 

Thanks!

DC


Re: vSphere 6 standard - sso

$
0
0

Welcome to the Community,

 

to find out what can be done, please provide some details:

  • what's the vCenter Server version, and build number?
  • is it the Windows based version, or the vCenter Server Appliance (a Linux based VM)?
  • are you still using the Windows client, or the web client?
  • is it the "administrator@vsphere.local" that you need to reset?

 

You say that the backup doesn't work either. Is the backup configured to use the administrator@vsphere.local account? In this case you may consider to change that to a separate account once the access/login issue is fixed..


André

Re: vSphere 6 standard - sso

$
0
0

Hi Andre!

I have VMware Vsphere client 6.0.0 build 3016447

running on Windows Server 2012 R2

 

The web client or the windows client will not connect unless you have checked the box "use windows session creds"

If I uncheck that box and type in the exact credentials it will not log in.

"Cannot complete login due to an incorrect user name or password"

 

I believe my Barracuda Backup source is having the same issue.

When I test its creds from the appliance it cant connect to the VMserver.

 

I am not sure if I need the vsphere local admin reset or not.

I'm just wondering what happened to my ability to login from the outside to the Vsphere client.

I checked the services and I didnt see any vmware.sso type running. So now Im not sure it has sso.

Re: vSphere 6 standard - sso

$
0
0

If there are no active tasks (migrations, or other things) running on vCenter Server, is it possible to reboot the server, to see whether this resolves the issue?


André

Standalone VCSA?

$
0
0

Hi all,

 

I haven't worked with VMware for the last 4 years or so and - as it does - the landscape has changed somewhat.

I'm currently working on upgrading vCenter 6.0 to v6.7, and we've opted to move to a appliance-based VCSA, and retire the Windows Server host that the vCenter environment is currently sitting on.

 

Initially, I was under the impression that VCSA could be deployed as a standalone VM/box, and we could move the hosts to it. So far, all the documentation seems to point towards "ingesting" the VCSA into an existing environment, then moving all your assets across.

 

Is there any way of having a standalone VCSA box from scratch?

 

I hope I'm making some sense, and thanks upfront

Re: Standalone VCSA?

$
0
0

The vcsa is deployed from an app on your computer, if you want it an be a brand new one, but if you want to "upgrade" a windows one it firsts creates a new appliance then transfers the settings over. I think this is what you mean by ", then moving all your assets across. " You can start from scratch and deploy the vcsa to a new host if you want, there is no prereq to deploy it in a pre existing environment.

Re: Standalone VCSA?

$
0
0

Thanks for the prompt response.

I'm still in the development phase at this point, and I've been wanting to get a working lab up and running first. All the KB articles I've dug into all seem to suggest installing the VCSA in an existing environment. I was under the impression that, since it's built on Linux, I could deploy the VCSA first.

 

Could you perhaps point me in the direction of setting it up as a brand new one, please? Ideally, in my test lab, I'm hoping to have a VCSA VM that isn't built on a Windows Server host, if possible?

Re: Standalone VCSA?


Re: Standalone VCSA?

$
0
0

Yep, so, this is pretty much in line with what I've come across so far.

It's either my expectation of the product or my understanding of it, but this is still effectively using Windows as a starting point - and running a Windows installer to get the VCSA up.

 

I really thought VCSA could be installed, almost like it's own OS, on a VM (or host) somehow - is this not possible?

Re: Standalone VCSA?

$
0
0

you don't install it you deploy a preconfigured appliance and configure it.

Re: VCenter 7.0 deployment from CLI stuck at waiting for deployment status

$
0
0

I triggered the vCenter installer from another VM on another server. Like this:

Command:

./vcsa-deploy install /root/vcenter/config/embedded_vCSA_on_ESXi.json --accept-eula --no-esx-ssl-verify --no-ssl-certificate-verification --log-dir=/root/vcenter/log

 

Result: Failed with below logs on screen.

 

OVF Tool: Opening VI target: vi://root@10.251.105.18:443/

OVF Tool: Deploying to VI: vi://root@10.251.105.18:443/

OVF Tool: Disk progress: 99%

OVF Tool: Transfer Completed

OVF Tool: Powering on VM: Embedded-vCenter-Server-Appliance

OVF Tool: Task progress: 0%

OVF Tool: Task Completed

OVF Tool: Waiting for IP address...

OVF Tool: Received IP address: 10.251.105.113

OVF Tool: Completed successfully

====================== [SUCCEEDED] Successfully executed Task 'Deploying vCenter Server Appliance' in TaskFlow 'embedded_vCSA_on_ESXi' at 06:59:33 ======================

================================= [START] Start executing Task: Monitor the entire VCSA deployment using appliance REST API at 06:59:33 =================================

Checking if the target VCSA is powered on and ready for operations...

Successfully verified that the target VCSA 'Embedded-vCenter-Server-Appliance' has been powered on and is now ready for operations

Checking if the target VCSA appliance API is available for query

The certificate of server '10.251.105.113' will not be verified because you have provided either the '--no-ssl-certificate-verification' or '--no-esx-ssl-verify' command

parameter, which disables verification for all certificates. Remove this parameter from the command line if you want server certificates to be verified.

 

Error:     Problem Id: None     Component key: setnet     Detail:         Failed to set the time via NTP. Details: Failed to sync to NTP servers.. Code:

com.vmware.applmgmt.err_ntp_sync_failed         Could not set up time synchronization.     Resolution: Verify that provided ntp servers are valid.

============================================================ [FAILED] Task: MonitorDeploymentTask: Monitoring Deployment execution failed at 09:36:53

============================================================

=========================================================================================================================================================================

Error message: The appliance REST API was not yet available from the target VCSA 'Embedded-vCenter-Server-Appliance'because 'HTTPSConnectionPool(host='10.251.105.113',

port=5480): Max retries exceeded with url: /rest/vcenter/deployment (Caused by NewConnectionError('<urllib3.connection.VerifiedHTTPSConnection object at 0x7fbd0e841ac8>:

Failed to establish a new connection: [Errno 110] Connection timed out',)). If the error message contains references about messages being expired, a login problem, or

its context indicates a timing issue, a possible reason could be system clock skew. Refer to error messages in 'taskflow.log' for more details. '. The VCSA might still

be starting up.

=============================================================================== 09:36:53 ===============================================================================

Result and Log File Information...

WorkFlow log directory: /root/vcenter/log/workflow_1587452127185

 

Questions:

1. how to check, what is wrong with NTP. Because, on the ESXi host, on the GUI, The NTP status is shown as 'sync' and running

 

Current date and time

Wednesday, April 22, 2020, 00:34:27 UTC

 

 

NTP service status

Running

 

 

NTP servers

  1. 1. 10.251.101.234

 

 

 

2.

The appliance REST API was not yet available from the target VCSA 'Embedded-vCenter-Server-Appliance'because 'HTTPSConnectionPool(host='10.251.105.113',

port=5480): Max retries exceeded with url: /rest/vcenter/deployment (Caused by NewConnectionError('<urllib3.connection.VerifiedHTTPSConnection object at 0x7fbd0e841ac8>:

Failed to establish a new connection: [Errno 110] Connection timed out',)). If the error message contains references about messages being expired, a login problem, or

its context indicates a timing issue, a possible reason could be system clock skew. Refer to error messages in 'taskflow.log' for more details. '. The VCSA might still

be starting up.

   . i have checked time is same on both the client (from where this installer is invoked) and ESXI host.

     . ESXi host is sync with NTP server

     . The client VM(10.251.108.132) is unable to reach the

 

The log file from workflow logs directory shows that:

vcsa-cli-installer.log

2020-04-21 07:10:03,049 - vCSACliInstallLogger - DEBUG - Retrieved all ip addresses from appliance Embedded-vCenter-Server-Appliance: ['10.251.105.113']

2020-04-21 07:10:03,067 - vCSACliInstallLogger - DEBUG - Querying REST endpoint '/rest/vcenter/deployment' on appliance '10.251.105.113' for deployment status

2020-04-21 07:10:03,067 - vCSACliInstallLogger - DEBUG - Proceed with certificate thumbprint check...

2020-04-21 07:10:03,068 - vCSACliInstallLogger - DEBUG - Requesting deployment status from target vCSA REST API endpoint 'https://10.251.105.113:5480/rest/vcenter/deployment'

 

I am unable to figure out the reason why this rest api is unreachable from my client VM

API changes in VCSA 7.0

$
0
0

We use an automated pipeline to create VM templates and then register then in Vcenter using govc. Our exact code is:

 

register-template(){

   echo"Registering the template"

   GOVC_DATACENTER="${dst_dc}"GOVC_DATASTORE="${dst_ds}" govc vm.register -dump=true-template-host="${host}""${template}/${template}.vmtx"

}

 

However, I've updated our VCSA appliance from 6.7 to 7.0 and now this command causes the vcenter-service to fail and causes the API endpoints and Vsphere UI to become unresponsive and display the message no object exists . In searching these forums I'm not seeing anyone else having this issue. We're a small shop and don't have SDK support. Does anyone know if there was an API change that might be causing this? Or any other suggest work around? I had to roll our VCSA appliance back to the previous version (6.7) and now the gitlab pipeline that includes this code completes without error.

Re: API changes in VCSA 7.0

$
0
0

govc hasn't been updated for 7.0 so I'd suspect there are some API differences with respect to this pipeline. Nothing to really suggest other than stay on 6.7 until there's coverage.

Viewing all 15787 articles
Browse latest View live


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