MattiasN81's Posts

If you created the datastore during the esxi installation the scratch location will be pointing to to your datastore by default, you need to remove logging by remove the value from "ScratchConfig... See more...
If you created the datastore during the esxi installation the scratch location will be pointing to to your datastore by default, you need to remove logging by remove the value from "ScratchConfig.ConfiguredScratchLocation" and "ScratchConfig.CurrentScratchLocation" under Host -> Manage -> System -> Advanced settings. Reboot the host and try to remove the datastore again.
I was searching for this myself, found a precompiled binary that works on 6.7.
Do you have Intel VT-d enabled in BIOS ?
Do you see "vmx| CPUID differences from hostCPUID" in the VMs vmware.log file?
‌I did provide a oneliner you can use in task scheduler, see my first post in this thread
Hi. ESXi dosnt support SNMP GET, only Traps by looking at your check string i assume you are running a Nagios/Naemon based monitoring. There are tons of VMware ESXi plugins at Nagios Excha... See more...
Hi. ESXi dosnt support SNMP GET, only Traps by looking at your check string i assume you are running a Nagios/Naemon based monitoring. There are tons of VMware ESXi plugins at Nagios Exchange that pulls hardware status directly from the ESXi native agents. OMSA VIBs are not neccesary unless you are using OpenManage Essentials and not having iDRAC Enterprise on your servers. ‌
‌The vSwitch configs are stored on the hosts so you dont need to worry about the VMs. I usally do this when i migrate to another vCenter. 0. The hosts should NOT be in maintenace mode and t... See more...
‌The vSwitch configs are stored on the hosts so you dont need to worry about the VMs. I usally do this when i migrate to another vCenter. 0. The hosts should NOT be in maintenace mode and the VMs should be running as normal during this operation. this is due to two things, 1. The VM needs to be added to the new vCenter, VMs will be added to the vCenter inventory automaticlly when they are still added to a host inventory. 2. You dont want any downtime on the VMs, so keep them running. This will not affect the VMs. 1. Configure the new vCenter as desired 2. Disconnect the hosts from the old vCenter 3. When the hosts are disconnected, remove them from the old vCenter this will remove the vCenter configs on the hosts and cleanup any certificates tied to the old vCenter. 4. Add the hosts to the new vCenter. 5. Done It will look a little bit scary on the old vCenter when you remove the hosts, when VMs starts dissapearing, this is normal as they are only removed from the vCenter inventory but not the host inventory, they will keep running on the host as nothing happened at all :smileygrin: I have done this many times under full workload hours without any impact on the VMs Note.. If you use DVSwitches then you need to export the old switches and import them to the new vCenter so that the VMs are assigned to the new DVS before you add the hosts.
‌The script you provided isnt written in PowerShell, its a shell script written for esxi. To use this script you need to tun it directly on the esxi
I dont think the pNIC is the culprit here, most of the communications goes only through vmkernel anyway, I suspect its storage related. I have seen a similar problem before with a Dell PowerEdge... See more...
I dont think the pNIC is the culprit here, most of the communications goes only through vmkernel anyway, I suspect its storage related. I have seen a similar problem before with a Dell PowerEdge R710 with an PERC 6i controller (LSI chip), and the problem was a raid parity calculation bug. Can you provide the make, model and firmware version for the LSI card ? Also make, model and firmware on the SSDs that is hosting the datastore(s) would be nice, so can see if i can dig anything up. Also start a copy between the machines that are affected and then post the vmkernel.log, then run "dmsg > /var/log/dmsg.log" and post dmsg.log too. These steps would help alot :smileygrin:
You can find it here. https://my.vmware.com/en/group/vmware/info?slug=datacenter_cloud_infrastructure/vmware_vsphere/6_5 You can choose from whatever edition you like, the vcenter and esxi ... See more...
You can find it here. https://my.vmware.com/en/group/vmware/info?slug=datacenter_cloud_infrastructure/vmware_vsphere/6_5 You can choose from whatever edition you like, the vcenter and esxi images are the same for all of them. vCenter comes with a trial 60day license preinstalled
True, i spelled it out wrong, dont want to confuse people I meant that even with the hypervisor license you can have 2 sockets, no license only allows one socket
vSphere with Opsmanager is just a suite, you dont need the whole suite In this case you just need do download the vcenter appliance and deploy it on your esxi, then login to the vcenter, add the... See more...
vSphere with Opsmanager is just a suite, you dont need the whole suite In this case you just need do download the vcenter appliance and deploy it on your esxi, then login to the vcenter, add the host to it.. and done
True, i deleted my last post stating that vCenter isnt needed for a single host, i got a mental meltdown :smileygrin: The migrate feature is a vCenter feature so you need a vCenter to use Storag... See more...
True, i deleted my last post stating that vCenter isnt needed for a single host, i got a mental meltdown :smileygrin: The migrate feature is a vCenter feature so you need a vCenter to use Storage vMotion. You can use a trial license for vCenter aswell.
Can you check and see if ESXi sees the other CPUs by running "esxcli hardware cpu list" from SSH or shell ?
Someone can correct me if im wrong :smileygrin: All ESXi liceses is minimum 2 sockets, i never seen a license that allow only one socket, even the free license allows 2 sockets. I have seen t... See more...
Someone can correct me if im wrong :smileygrin: All ESXi liceses is minimum 2 sockets, i never seen a license that allow only one socket, even the free license allows 2 sockets. I have seen this before though, when you have a cluster and assingn licenses via vCenter server and have one CPU hosts in the mix, ive also seen this when using esxi licenses bundled with horizon (host desktop licenses)
Take a look at this KB "503 service unavailable" error when connecting to vSphere Web Client (2121043) | VMware KB
Hi The easiest way to migrate VMs from one datastore to another is Storage vMotion, i think standard licensing covers it. If you dont have a license that covers it then you can use a trial li... See more...
Hi The easiest way to migrate VMs from one datastore to another is Storage vMotion, i think standard licensing covers it. If you dont have a license that covers it then you can use a trial license (trial license is a 60day timebombed enterprise+ license) then revert to the old license when you are finished. Storage vMotion moves VMs on the fly without downtime on the VMs
Damn, never thought of doing the same with AHCI, reverting to the old achi driver worked like a charm, no more crappy errors on the drives thanks for the enlighement :smileygrin:
It sounds like your ESXi is not configured for LACP, this is a typical problem when the loadbalancing/failover policies don't match the switch(es) in order to use LACP you need the enterprise+ l... See more...
It sounds like your ESXi is not configured for LACP, this is a typical problem when the loadbalancing/failover policies don't match the switch(es) in order to use LACP you need the enterprise+ license, vCenter server and use distributed switches. otherwise you can use IP hash loadbalancing policy on your portgroups and etherchannel on the switch, however etherchannel is a Cisco solution and i don't know if HP have an equivalent of that.
the host CD/DVD drive isn't supported as a passthrough device, you need a USB/eSATA device for that.