daphnissov's Accepted Solutions

Only thing to recommend at this time is to bring that old host fully up-to-date with regard to patches. The build number you have suggests U1 while the latest release for the 5.1 version was U3 patch 9 (build 3872664). So update the host to that build and see if the PSOD still happens.

That's a "back in time" upgrade which is not supported. You'll have to wait for the next version of vCSA 7 for that path to open up to you. ___________________________________________________________________________ Did you find this helpful? Let us know by completing this survey (takes 1 minute!)

The 6.7 appliance. You have to fix the cert issue before you attempt the migration again. ____________________________________________________________________________ "Did you find this helpful? Let us know by completing this survey (takes 1 minute!)"

When you perform the upgrade/migration, it would have to initially live on a 5.5 host if that's all you have, but once the 6.5 upgrade is complete you should be upgrading your ESXi hosts. Did you find this helpful? Let us know by completing this survey (takes 1 minute!)

There's no specific capability to do exactly as you ask. Disabling HA on specific VMs only works if those VMs are on a host which fails; it does nothing for surviving VMs that you wish to deprioritize. The only good solution here would be to script something which watches for an HA event and shuts those VMs down. Quickest thing that comes to mind would be integrating Log Insight and vRealize Orchestrator together and have vRLI watch for the HA event and trigger a workflow in vRO which calls out to vCenter to initiate a shutdown request. If not clear, this would be a manual scripting/cobbling things together approach.

We want to add one more ESXi host with one CPU to the system. Do I need a licenses for the ESXi host? Will the one availalbe CPU licenses on the server allow me to add this new host, and if not, what do I need to buy? According to your existing, 12-socket entitlement to vSphere Standard in which only 11 are claimed, you have capacity to add another single-socket host.

My question is :  I need static route for each network on Guest OS with multiple NICs? the moral of the story , I have 4 VMs like below. I am using L3 switch. Do I have to define static route for each network on VM A with multiple NICs? So like you said , I want the NICs that are on different VLANs to talk to one another. You should not need static routes if the communication occurs over L2 for each of those NICs. If VM A with vNIC A is configured for VLAN 20 which is 10.0.0.10/24 and VM B with vNIC B is on the same segment at 10.0.0.11/24, then they should be able to talk by virtue of each vNIC existing on that segment. You can verify the routing table with the route print command. Aside from this, your question is not related to any VMware technology, so any further "issues" and you should direct them elsewhere for general network troubleshooting.

Not much to say other than you have a firewall/routing issue upstream in your environment. This isn't something ESXi is blocking for you as there are no policies applied to virtual machine port groups. I'd look at your routing tables on your L3 device and see if you have a bad route somewhere.

Replacing license keys does not incur downtime. That said, if you no longer have an active support agreement you are taking a big gamble, especially if, as you say, this is a private cloud environment.

1.  Is Kubernetes part of ESXI or Is its come with bundle? I‘m not see an option to enable and have that configured. Is it come with VCF? It's built into ESXi and vCenter. You can only acquire the add-on license as part of VCF. 2. Is the vsphere VM objects in the Vsphere 7 are containers henceforth This question doesn't make sense in English. If you're asking about the so-called "native pods" or "vSphere pods" those are Kubernetes pods, not containers. 3. Can  assign the same VM configurations like VDS switch on the VM like on Vsphere VM objects on the Containers to Again, this doesn't make sense in English so I don't know what you're asking. As stated in the answer to #2, Kubernetes runs pods, not containers. The native/vSphere pods you see when workloads run on the supervisor cluster are not containers. 4. How many containers can I host on a normal ESX with See previous answers. Kubernetes runs pods, not containers. For Pod maximums, see the config max tool. Some specifics relating to native pods are as follows Also, "ESX" and "ESXi" are two totally different hypervisors. Do not say "ESX" any more, especially when referring to vSphere 7 with Kubernetes. 5. Is this available with single node as well, What the cluster specifications? No, cluster minimum supported size for the supervisor is three hosts. 6. Is there any vmware docs with Kubernetes to help to build Kubernetes cluster and container. Did you do any basic searches yourself? If so, you probably would have seen at least the official documentation.