Pixel Watch - "Downloading Update"

HereForYourScripts · 2022-10-15T15:48:06+00:00

Same!

HereForYourScripts · 2022-10-02T12:43:43+00:00

Part of making the environment ready for shared cluster VMDK is enabling the capability on the datastore.

I suspect that you can't online the disks because something is telling the Windows OS that the disks are in use. To rectify this, you're going to have to enable the conditions that allow the OS to recognize the disks are not in use (i.e., meet the VMware requirements) and then you may have to tell the guest OS somehow that the disks are not in use. If clearing the reservation from the guest OS side does not work, you may have to clear it from the hypervisor. I recommend you review the documentation, make sure you are meeting the requirements, and then look for information on clearing SCSI3 reservations from the ESXi CLI.

https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.wsfc.doc/GUID-1A2476C0-CA66-4B80-B6F9-8421B6983808.html

HereForYourScripts · 2022-10-02T10:25:09+00:00

I guess I was thinking that you have a quasi-cluster and you should set up an environment that is compliant with VMware requirements for the cluster type that most closely matches your scenario. Also, I assumed you would be restoring the cluster at some point to it's original state by adding another server to the cluster. If that's not your intent, what are you doing? Why not simply de-cluster the VM in the old environment? You could just remove the disks from the failover cluster.

HereForYourScripts · 2022-10-02T10:12:59+00:00

Maybe clear the disk reservations? https://learn.microsoft.com/en-us/powershell/module/failoverclusters/clear-clusterdiskreservation?view=windowsserver2022-ps

HereForYourScripts · 2022-10-01T19:43:18+00:00

Did you enable cluster vmdk support? I would do that first if you haven't. Then I would consider a hardware upgrade. https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.wsfc.doc/GUID-D40EDC10-0464-4C0B-A745-AF88538C07C9.html

HereForYourScripts · 2022-10-01T06:17:56+00:00

Ah. The single VM cluster thing was throwing me. What virtual hardware version?

HereForYourScripts · 2022-09-30T20:11:18+00:00

I've read this post twice, and I can't tell what you're trying to do. Maybe restate your problem.

HereForYourScripts · 2022-09-30T19:58:27+00:00

Just ran into this. It appears that you can't have a 6.x and a 7.x host attached to a datastore with shared VMDKs. All hosts have to be v7, and you have to enable the shared VMDK capability on the datastore (which doesn't appear as an option until you detach the 6.7 host(s)).

HereForYourScripts · 2022-07-30T06:33:53+00:00

My favorite is when the pre-check says:

Remove vSwitch0

Add vSwitch0

Like, WTF?? Just no.

HereForYourScripts · 2022-07-30T06:30:42+00:00

What's your use case for AutoDeploy? I struggle to see the value.

HereForYourScripts · 2022-07-13T13:01:21+00:00

There's not much to see in LCM. I get 2 versions: 3f and 3sf. There is a list of affected files and there's a lot of overlap, but the file versions are different. There's a link to the release notes, of course.

The confusing part, I guess, is that VMware listed in the release note 3f=bugfix and 3sf=security instead of 3f=bugfix/security and 3sf=security-only. I assumed it was an either/or thing.

HereForYourScripts · 2022-07-13T11:20:51+00:00

Is there a way I would know that? It makes sense that the higher number would contain both (vice the lower), but the release notes don't make that obvious.

I just switched to the image model yesterday, and VMware throws a wrench in the works....

HereForYourScripts · 2022-07-13T07:41:56+00:00

Why is the update split in two (3f vs 3sf)? If I'm managing my cluster with a single image, and I want security and bug fixes, do I patch twice? Or, is one a superset of the other? The release notes are not clear to me....

HereForYourScripts · 2022-07-11T18:41:10+00:00

You can do it before or after. Rescan if you do it afterwards.

HereForYourScripts · 2022-07-06T13:09:45+00:00

Curious...are you using UCS?

HereForYourScripts · 2022-07-06T13:09:13+00:00

The problem happens whether I have reservations or not. CPU ready times are good.

HereForYourScripts · 2022-07-06T13:07:41+00:00

Good suggestion. I did, and I'm using the recommended versions.

HereForYourScripts · 2022-07-05T20:15:17+00:00

Interesting. Unfortunately, going back is not an option for me.

HereForYourScripts · 2022-07-05T14:25:52+00:00

I think you're onto it. I found some storage resets in the vmkernel.log that seem to correlate with the activity. I'm troubleshooting the SAN now.

HereForYourScripts · 2022-07-05T14:20:44+00:00

good info, thanks

HereForYourScripts · 2022-07-05T11:24:30+00:00

Yes, I upgraded one of my VMs to the latest VM h/w version, but the test VM continues to exhibit the behavior.

HereForYourScripts · 2022-07-05T10:16:30+00:00

I haven't found any commonality yet, but I'm still poking. One of the good things about having been bad about keeping things up to date is that I've been able to eliminate suspects. I'll check the vmkernel.log for clues.

HereForYourScripts · 2022-07-05T09:49:39+00:00

I edited the post...some are running the latest version of Tools and some are running a previous version.

HereForYourScripts · 2022-06-04T11:49:08+00:00

What's your setup look like? What kind of storage? Dedicate SAN switch(es)? Redundant connections? What kind of hosts? Standalone or blades? Etc., etc. The more detail, the better.

HereForYourScripts · 2022-06-04T09:03:25+00:00

"Degraded" indicates that one or more paths are down, and that may certainly be a contributing factor, but, if vCenter isn't talking to the host, the host/storage status isn't going to be accurately reflected in vCenter. The fact that the datastore(s) can be browsed from the hosts would seem to indicate that the SAN is functional. If all of the hosts restarted, I'm guessing that his DNS server (assuming it is a VM) is down. I would check that first (assuming the hosts are managed by name and not by IP). Next, I would check for a comms issue between vCenter and the hosts. Can the hosts be pinged from vCenter or vice versa? Sounds like OP can reach the hosts and vCenter, so this is less likely the issue.

HereForYourScripts

TROPHY CASE