Hi,
I am getting the abive error when trying to add a vCentre into Skyline.
I have follow all the other stes posted including FQDN and using .vsphere.local as opposed to my AD domain but still get errors.
Any Idea's?
Hi @s_simon,
We were unable to reach you on the email id which you had shared and received bounce email.
| ||||||||
|
Let us know if there is an alternate way to reach you out. You may provide us, your details in below link.
---------------------------------------------------------------------------------------------------------
Was it helpful? Let us know by completing this short survey here.
Hi S_Simon,
Welcome to Skyline Communities.
From the error it looks that skyline is not able to communicate to vCenter or PSC server.
Could you please check if we able to ping PSC and vCenter from Skyline appliance and port is reachable.
curl -v telnet//PSC-FQDN 7444
curl -v telnet//vCenter-IP 443
Go to vCenter advanced confirgraton and search SSO to find PSC information.
This may also require some additional troubleshooting. I would request to share your details here, so we can get back to you.
Additional Troubleshooting Steps:-
Hello,
Sorry for the delay. I will check over the information and get back to you.
Hey Ajay,
I have tried all that and it still fail's.
I can ping from the SKyline Server using the root details and did an nslookup on the IP of the vCentre everything comes back okay unfortunatly.
Are we able to have a webex?
Many Thanks,
Hi S_Simon,
Please provide your contact details here, so we can get back to you.
Thank you. just replied
Hi @s_simon,
We were unable to reach you on the email id which you had shared and received bounce email.
| ||||||||
|
Let us know if there is an alternate way to reach you out. You may provide us, your details in below link.
---------------------------------------------------------------------------------------------------------
Was it helpful? Let us know by completing this short survey here.
Hi Simon,
This is to inform you that we are about to archive this thread as its been inactive for quite long.
We request to share the resolution if your issue is resolved.