VMware vSphere

Dear Expert,

SSO log in failure.(give error code 503)

Root log in  is fine.

Support give guide t re-deploy a new VCenter server. he said the appliance was crashed.

problem is it is not available on local site to access system. I have to remote the system by Teamviewer. (the internet for that site is very poor due to the system is built on vessel with very small

satellite system)

There are total 6 Vms in the inventory and in running.

I am afraid of the re-deploy will affect the running VMs. and locally access to be needed.

I deployed  VCenter server appliance about two years ago.  And the procedure  is so clear to me.

please give advice the deploy guide. (better for some practical experience)

tks n brgds

Liu Wei

First of all you should know about that Re-Deploying VCSA do not affect to the other VMs, So you can do it without any problem.

But please tell me what's the version of your vCenter? can you open https://vcsa_IP_addr:5480 to manage your appliance or this page also gives you similar error as you mentioned?

for last question did you install it in embedded mode or external? what's the situation of Platform Service Controller services?

Do you have SSH access to your vCenter Server ?

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

Was it helpful? Let us know by completing this short survey here.

version is 6.0.0.10200 see attached photo below.

log in 5480 log in and give GREEN good status.

embedded. I am clear it basic service for  manage virtual storage/virtual switch and VMs. only.

SSH access is ok. Support remote for help by putty.

OK so if you install it in embedded mode, now execute this command in VCSA CLI to check status of SSO:

sso-config.sh -get_identity_sources

Then provide a backup for below file with winSCP connection or CP command or etc:

/opt/vmware/lib64/vmware-identity-sso-config.jar

download following file and replace it with that mentioned file:

https://kb.vmware.com/sfc/servlet.shepherd/version/download/068f4000009EfXrAAK

Restart all of your VCSA Services by running:

service-control --all --stop | --start

Then try to connect to your service and give me your result please.

Thanks. I will do and let you know result.

brgds

Liu Wei

Sir,

backup failure: see attached photo.

I will continue to replace the file?

brgds

Liu

sorry, I mistake. ignore I post ten minutes ago

tks

Liu

Get Status of SSO failure. It sounds SSO going wrong.

brgds

Liu

So try to replace with original file from VMware .... no picture has been attached, i couldn't see anything. Using cp command is very easy do it like this: 

# cp /opt/vmware/lib64/vmware-identity-sso-config.jar​ /opt/vmware/lib64/vmware-identity-sso-config.bak

Good Day, NathanosBlightcaller,

please see the screenshot.

So I think if you replace your file as I said before and nothing has been changed, you need to redeploy VCSA, just remember if you install a new one, first-boot of your new vCenter must be done without any error especially about SSO

Sure!

The current VC is managing two hosts and three data storage.(one is HPE Virtual storage).

please advise if the below is correct:

01. I should drop off hosts and storages from VC first

02. re-deploy and add hosts and storage into new VC.

How can I drop off the hosts/storage,etc from the VC?

Remove the VC from current inventory and delete it, which can be clean up the VC?

brgds

Liu Wei

First you should remove your hosts from virtual datacenter of current vCenter.

Then if your datastore is a added LUN from a SAN infrastructure and your hosts are located in their, you don't need to remove them, just for safety of your procedure:

1. If there is no power-on VM, you can unmount the datastore from list of hosts and then remove hosts and datastore next

2. But if you cannot power-off them no need to do, just leave the hosts and VM working standalone. just remove them from datacenter is enough

Then deploy the new VCSA and after successful installation, step by step add your resources (Hosts and their Storages) to the new VI. just remember if you keep the LUN connected to hosts, they will coming back with adding host to the new vCenter :smileyhappy:

I hope I could give a good advise

lwsamcn01​

Have you tried to reset the password, please check below VMware KBs

https://kb.vmware.com/kb/2034608

https://kb.vmware.com/kb/2146224

I tried as your post to reset SSO password before I submitted the case to Support.  when got the new password, log in still failure as problem as before.

Hey,

Have you ever tried to reboot it and check SSO again? If you access to ssh, please put the output of this command "service-control --status --all" here to see the status of services.  Can you put the complete text of error here? a screenshot would be better!

When you say you have installed it 2 years ago..... most likley the /storage/log or db partition runs out of space.  Can you login into VCSA konsole or ssh and run "df -h" and show us the output?

Regards,

Joerg

That was done.

Based on your last screenshot, your vcsa name is localhost, which will make vCenter not working. YOu need DNS registration for the vCenter. That being said, you will have to redeploy it.

Re-Deploying VCSA do not affect to the other VMs, So you can do it without any problem

Tks!

This same problema (vCSA crashed) occurs on my installation.

I need to redeploy it, but I must verify first of all that all running VMs (Active Directory, CRM, other main servers...) will not be affected.

Before crashing it, vCSA was working with three ESXi, with three datastores: vSAN, FreeNAs and QNAP. Running VMs are in vSAN datastore.

So, my question is: when I will redeploy vCSA, what are the steps to the new vCSA takes the control to the three ESXi? Please verify I am wrong or not:

1. Deattach ESXi from actual vCSA (vCSA is powered OFF but checking ESXi, remains with connectivity to OLD crashed vCSA)

2. Install new vCSA

- Install OVA from vCSA. That is easy, no problema in this part.

- My main questions are in this step: in a new installation, vCSA takes control of ESXi where it is installed and claims disk to datastore.

- Keeping mind that I have running VMS that I can not power OFF (if affects production), how can I do this part of vCSA installation for the new repdeployment?

3. Give all configuration from ESXi (datastores, running VMs and networking) to vCSA. It takes vCSA config from ESXi? I must reconfigure anything?

Thank you for you aclarations. Regards!