AndyDodsworth Tracker

Re: Site access - https://digitallearning.vmware.com/

AndyDodsworth — Wed, 20 Sep 2023 20:41:52 GMT

And it's back... which means I have to study now

Re: Site access - https://digitallearning.vmware.com/

AndyDodsworth — Wed, 20 Sep 2023 20:31:06 GMT

Now showing this so I guess someone is aware..

Site access - https://digitallearning.vmware.com/

AndyDodsworth — Wed, 20 Sep 2023 20:23:07 GMT

When I attempt to connect to https://digitallearning.vmware.com/ via the MyLearn page, I get 'This site can’t be reached digitallearning.vmware.com’s server IP address could not be found.'

I was literally logged in yesterday studying the VCP-VMC course material.

Any ideas?

Re: vSphere Upgrade Pre-Check Failure - Certificate SAN DNS and FQDN Check

AndyDodsworth — Thu, 19 Jan 2023 17:09:10 GMT

Thanks - I ran each step in the KB and all three outputs were set to the FQDN of the VCSA.

I used to have an external PSC but that was consolidated to an embedded maybe a year ago - this is the first major upgrade since that was performed - could that have caused an issue?

The only reference to the old external PSC is on the 'issuer' section of the certs, everything else is set to the FQDN of the VCSA.

vSphere Upgrade Pre-Check Failure - Certificate SAN DNS and FQDN Check

AndyDodsworth — Wed, 18 Jan 2023 17:21:32 GMT

Hello - looking for some advice on an vCenter upgrade I'm attempting from 6.7 U3 to 7.0 U3.

I ran pre-checks using Skyline Health Diagnostics and I have one pre-check failure:

VC_UPC.VCSA.CertSANCheck: Certificate SAN DNS and FQDN Check

vCenter Server 7.0 requires Machine FQDN to be past of SubjectAltName of Certificate

KB Number: 2097936

Resolution:

Certificate Requirements: https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.authentication.doc/GUID-DE49FBF5-E24A-462B-91DC-C4284D93F654.html

Please read KB: https://kb.vmware.com/s/article/2097936 for more details on replacing certificates.

Investigation Details:

Data Collection Time: 2023-01-12T19:50:13

Certificate: vCenter Rhttpproxy TLS Certificate has no DNS Name in SubjectAltName

Certificate Subject Alternative Names

Certificate FQDN SAN-DNS Status

vCenter Rhttpproxy TLS Certificate

(correct FQDN - redacted)

[]

RED

One of more Certificates on vCenter have no or incorrect DNS in SubjectAltName

I have checked the certs on the VCSA and the TRUSTED_ROOTS cert does indeed have a SAN set to the following (which I understand is the default):

X509v3 Subject Alternative Name:

email:email@acme.com, IP Address:127.0.0.1

But given, the error above appears to say the issue is with the vCenter Rhttpproxy TLS Certificate (which I'm not sure is a VCSA or ESXi cert?).

So my question is, which course of action would you recommend to fix this issue?

a) A complete renewal of all certs in the environment?

b) A refresh of the ESXi certs?

c) ?

BTW - we're using VMCA-signed certs in this environment.

TIA.

Re: Can vCenter 6.7 U3 manage an old host running ESXi 5.1 U4?

AndyDodsworth — Tue, 29 Oct 2019 16:19:19 GMT

Thanks for the confirmation Diego.

Can vCenter 6.7 U3 manage an old host running ESXi 5.1 U4?

AndyDodsworth — Wed, 23 Oct 2019 16:01:10 GMT

I need to upgrade our environment from vSphere 6.0 to 6.7 but I have an old host that can't be upgraded due to the apps on running on there (old Cisco apps).

My current vCenter is running 6.0 U3.

The host in question is currently running ESXi 5.1 Patch 9 (3872664) - Note: this is a standalone host, no HA, DRS, etc.

My question is, if I upgrade vCenter to 6.7 then can I still manage this standalone host?

The compatibility matrix is obviously telling me it's not compatible but I'm wondering if anyone has tried this successfully/unsuccessfully?

TIA

Re: Upgrade & Migrate from External PSC to Embedded

AndyDodsworth — Mon, 27 Aug 2018 17:18:47 GMT

[checks latest VMworld Updates...]

It's called the vCenter Server Converge Tool

https://blogs.vmware.com/vsphere/2018/08/under-the-hood-vsphere-6-7-update-1.html

Essentially, you have to go with the in-place upgrade to 6.7 U1, then run the vCenter Server Converge Tool to move your external PSC data to the embedded PSC, lastly decommissioning your external PSC.

Re: Upgrade & Migrate from External PSC to Embedded

AndyDodsworth — Mon, 27 Aug 2018 16:56:54 GMT

Also looking for an update on the migration from an external PSC (6.0 U3) to an embedded (6.7)... TIA

Re: vCenter vsphere-client service fails with Java memory error

AndyDodsworth — Wed, 21 Mar 2018 16:48:11 GMT

I suspected as much.. onwards to 6.5! - thanks

Re: vCenter vsphere-client service fails with Java memory error

AndyDodsworth — Wed, 21 Mar 2018 16:28:06 GMT

I have the exact same issue on 6.0 U3.

Did you find a resolution in the end andreir?

Virtualizing NTP servers

AndyDodsworth — Thu, 18 May 2017 20:17:06 GMT

We're looking into virtualizing our NTP servers and I was wondering if anyone has gone through this process?

There's not much out there in terms of documentation around this (from what I can see - or can't see ).

Looking for pros, cons, caveats, etc - ideally pertaining to a vSphere 6.0 environment (VCSA, external PSC, ESXi hosts).

Cheers

Andy

Re: Can not disable vsanvp firewall rule...

AndyDodsworth — Thu, 16 Jun 2016 22:01:36 GMT

Interested to know if either of you had an update on a fix other than removing IP range?

Re: Patching the PSC 6.0 Appliance using the AMI?

AndyDodsworth — Mon, 04 Apr 2016 21:19:07 GMT

Yes, I read that too.

Just to confirm - I did indeed use the AMI to update my PSC first, then the VCSA, from 6.0 U1 to 6.0 U2.

Access the AMI's via the URLs:

https://[PSC IP]:5480

https://[VCSA IP]:5480

Using 'root' as the username and your corresponding password.

All is good!

Re: Patching the PSC 6.0 Appliance using the AMI?

AndyDodsworth — Mon, 04 Apr 2016 19:41:13 GMT

Thanks for the reply vijayrana968‌.

I had already reviewed that documentation but all installation steps relate to the vCenter Server Appliance and not the PSC specifically - I'm going to assume that the two are interchangeable at this point - although I do appreciate that the PSC has be upgraded first. Thanks again.

Patching the PSC 6.0 Appliance using the AMI?

AndyDodsworth — Mon, 04 Apr 2016 16:28:51 GMT

Hey there,

I can't seem to find a definitive answer in the support section so I'm throwing this out there...

I need to patch our PSC 6.0 appliance (and vCenter appliance accordingly) from 6.0.0 U1 to 6.0.0 U2 and I was wondering if I can perform this installation upgrade using the Appliance Management Interface (AMI)?

I can log in to the PSC using the AMI and I see the upgrade available, but nowhere does it say I can use this to perform the upgrade - only via the Shell from what I've read.

As a side note: When it comes to upgrading the vCenter 6.0 appliance, the documentation states you can use the AMI for this.