I compared the KB download to one VMware sent me this week to resolve some stale certificate trust mismatches and they are the same. I'm pretty sure that is the latest version (as there is a template...
See more...
I compared the KB download to one VMware sent me this week to resolve some stale certificate trust mismatches and they are the same. I'm pretty sure that is the latest version (as there is a template for v8.0), so might be worth logging the issue to VMware for support. I also compared it to an old one I downloaded in the past and neither contains the specific template you're after -- vCenter Server 6.5 Update 3s | 08 FEB 2022 | ISO Build 19261680.
Hi All, I've got a newly built vSphere 7 infrastructure. Two vCenter servers (v7.0 U2) in enhanced linked mode as part of the same SSO domain vSphere replication appliances (v8.4) in both sites ...
See more...
Hi All, I've got a newly built vSphere 7 infrastructure. Two vCenter servers (v7.0 U2) in enhanced linked mode as part of the same SSO domain vSphere replication appliances (v8.4) in both sites SRM appliances (v8.4) in both sites This has been deployed using the default VMCA self-signed certificates, but I now have a requirement to use external SSL certificates signed by an internal Microsoft CA. Is there a simplified walkthrough available to show the sequence of tasks or has someone done this recently that can provide some guidance? I'm busy going through the documentation to work it out, but I thought I'd ask the community to help understand and validate my assessment of what needs to be done. My concerns are to ensure that all the components continue to function (PROD environment) as I go through the certificate replacement, and that I have a documented process at the end for when the certificates expire. Once I have a plan together, I will test this in a non-production environment before doing the same in production. Reference for Hybrid mode > vSphere Security Certificates (vmware.com) Cheers, Jon
Download it from the release notes download link ... but it's end of general support. VMware vSphere Replication 8.2.1.2 Release Notes VMware vSphere Replication 8.2.1.2 | 27 MAY 2021 | Build 17...
See more...
Download it from the release notes download link ... but it's end of general support. VMware vSphere Replication 8.2.1.2 Release Notes VMware vSphere Replication 8.2.1.2 | 27 MAY 2021 | Build 17913946 | Download
Have you got your BIOS optimised for high-performance (disabling C states, eg. C1E on Dell servers) and configured your hosts for high-performance rather than balanced mode?
Hi Marcelo, I've seen this multiple times and it could be a number of issues that you need to work through by process of elimination. The first things to check are firmware and drivers, ensuring yo...
See more...
Hi Marcelo, I've seen this multiple times and it could be a number of issues that you need to work through by process of elimination. The first things to check are firmware and drivers, ensuring you have the correct levels for the specific hardware and ESXi build version. If these are onboard ports, collect logs and send them to your hardware vendor for analysis. Next check the switch ports for CRC errors, caused by faulty SFP, bad port or even a damaged cable (sometimes not visible). Replace the ethernet cable to rule it out. Review the release notes for the ESXi build number to identify any known issues. Simpler to check with Skyline if you have it implemented. You'll probably find that the port stays up for a while if you manually bring it up but then goes down again. This behaviour will continue to occur until you're identified and resolved the root cause. Cheers, Jon
It sounds like something configured in the VMX file is no longer available, can you upload the VMX file? You could try deleting the existing .vmsd file (re-created on power on) and then powering the...
See more...
It sounds like something configured in the VMX file is no longer available, can you upload the VMX file? You could try deleting the existing .vmsd file (re-created on power on) and then powering the VM on to see if you still get this error.
Can you confirm there are no snapshots and check what files the disks are pointing to? If you attach the VMX file and a directory listing from the VM folder we can check. I've seen similar issues ca...
See more...
Can you confirm there are no snapshots and check what files the disks are pointing to? If you attach the VMX file and a directory listing from the VM folder we can check. I've seen similar issues caused by failed consolidation tasks where the VMX is pointing to a delta file even though no snapshots exist. The fix was to remove the VM from inventory, edit the VMX file to point back to the base disks and not the delta/ redo disks, re-register the VM using the updated VMX file and then power it on. But it sounds like you can't remove it from inventory? It may also be a file lock which you'll need to trace, but in some instances, I've seen restarting the management agents on the host resolve where the VM is being managed from allowing admin tasks such as removal from inventory.
I'm assuming these are hosts without shared storage (ie. local to local migration requirement)? If you can get the guest downtime and the servers are in close proximity, you could directly connect t...
See more...
I'm assuming these are hosts without shared storage (ie. local to local migration requirement)? If you can get the guest downtime and the servers are in close proximity, you could directly connect the hosts together using an ethernet cable and spare NIC port. Configure a vmotion vmkernel port (backed by the NICS that are directly connected) using a basic address (eg. 192.168.0.1 and 192.168.0.2) on both hosts and do a cold (ie. powered off VM's) migration between hosts. See limitations Requirements and Limitations for vMotion Without Shared Storage (vmware.com)
What guest OS are you running and what VM compatibility/ hardware version are you using? I think you need version 11 or above. I wouldn't expect masking to be used to expose a feature, but rather to...
See more...
What guest OS are you running and what VM compatibility/ hardware version are you using? I think you need version 11 or above. I wouldn't expect masking to be used to expose a feature, but rather to hide or standardise features (eg. for EVC compatibility). Do you specifically need this masking or can you remove it to start with all features exposed to the guest OS?
I remember that pain, it was either needing one and not being able to find one or picking an erroneously placed one when all you wanted was a working ethernet cable - the pain was real!
I'd have a look through the logs for clues, including running through the document troubleshooting steps in this KB article. Troubleshooting vmware-hostd service if it fails or stops responding on a...
See more...
I'd have a look through the logs for clues, including running through the document troubleshooting steps in this KB article. Troubleshooting vmware-hostd service if it fails or stops responding on an ESX/ESXi host (1002849) If you have a support contract in place, upload a bundle to VMware for root cause analysis.
Yes, pretty sure that's what I've done in the past with gigabit NICs. In this scenario, I've generically referred to the direct connection between the two hosts as a crossover connection but technica...
See more...
Yes, pretty sure that's what I've done in the past with gigabit NICs. In this scenario, I've generically referred to the direct connection between the two hosts as a crossover connection but technically this would just be a regular ethernet connection and not a crossover cable ... which I remember having to manually crimp in the 90's
You've got an extra curly bracket that should be removed. At the moment your script is looping though each VM, but not doing anything as there are no actions within the "foreach VM loop". Change ...
See more...
You've got an extra curly bracket that should be removed. At the moment your script is looping though each VM, but not doing anything as there are no actions within the "foreach VM loop". Change this section .... foreach ($vm in $vms){ } To this ... foreach ($vm in $vms){ # } ... or just delete the line that I've commented out with a #. And you'll need to add an additional closing curly brackets at the end to close the "for each VC loop". Cheers, Jon
It's likely your hostd service is not running, see below where I replicate the issue by stopping the service. Probably worth restarting all your management agents using "services.sh restart". [x...
See more...
It's likely your hostd service is not running, see below where I replicate the issue by stopping the service. Probably worth restarting all your management agents using "services.sh restart". [xx\xxx@xxx:~] /etc/init.d/hostd stop watchdog-hostd: Terminating watchdog process with PID 67849 hostd stopped. [xx\xxx@xxx:~] /etc/init.d/hostd status hostd is not running. [xx\xxx@xxx:~] esxcli software vib list Connection failed [xx\xxx@xxx:~] /etc/init.d/hostd start hostd started. [xx\xxx@xxx:~] /etc/init.d/hostd status hostd is running. [xx\xxx@xxx:~] esxcli software vib list Name Version Vendor Acceptance Level Install Date ----------------------------- ------------------------------------ --------------------- ---------------- ------------ .... removed list to make the post short Cheers, Jon
Hi Chris, If I've understood correctly what you're after, then yes this would be possible but you would still need the crossover cable between the two ESXi hosts to maintain the requirement for keep...
See more...
Hi Chris, If I've understood correctly what you're after, then yes this would be possible but you would still need the crossover cable between the two ESXi hosts to maintain the requirement for keeping some traffic off the production network. The obvious issue with this is that it doesn't scale if you need to add any additional hosts (but this could be resolved by adding a separate switch). The ESXi hosts would need one virtual switch backed by your production network interfaces (assume two interfaces for redundancy), and a second virtual switch backed by the crossover interface. So each host would need at least 3 NIC ports. The VM's would have two interfaces connected to the port groups of each virtual switch, one for production traffic and the other for direct crossover traffic. When the VM's are on the same host, the traffic should traverse the backplane of the host and then on separate hosts it should traverse the crossover cable. See attached pic of what it looks like in my head. Hopefully that makes sense! Cheers, Jon
I've not seen this before myself, but perhaps this KB article helps? "Datastore conflicts with an existing datastore in the datacenter that has the same URL" error in vCenter Server (79623) (vmware....
See more...
I've not seen this before myself, but perhaps this KB article helps? "Datastore conflicts with an existing datastore in the datacenter that has the same URL" error in vCenter Server (79623) (vmware.com)
It sounds like you're experiencing the out of memory condition in the vAPI Endpoint Service; vSphere Web client unresponsive in vCenter Server 6.0 (2146538) | VMware KB If this is the case, t...
See more...
It sounds like you're experiencing the out of memory condition in the vAPI Endpoint Service; vSphere Web client unresponsive in vCenter Server 6.0 (2146538) | VMware KB If this is the case, then all you need to do is restart this service on ALL your vCenter Servers - there is no impact, and it should work immediately afterwards. The fix is scheduled to be released with U3 in Q1 2017. Cheers, Jon