A13x's Posts

Are these devices listed under the compatibility matrix: VMware Compatibility Guide - System Search Did you check the passthrough configuration on the esxi host, did you test removing it, ... See more...
Are these devices listed under the compatibility matrix: VMware Compatibility Guide - System Search Did you check the passthrough configuration on the esxi host, did you test removing it, adding it again and then reconfigure the guest os?
If you just want to use it as a storage platform to present storage to devices you are better of installing a NAS / Storage solution. As you mentioned FreeNAS is just one of a fair few solutions ... See more...
If you just want to use it as a storage platform to present storage to devices you are better of installing a NAS / Storage solution. As you mentioned FreeNAS is just one of a fair few solutions out there that is free and able to present iscsi. I guess some people out there might install ESXi onto the server and then have a VM running a storage solution. Personally i would just install a NAS solution rather than adding ESXi into the mix.
ATS and VAAI Hold hands. You cannot just disable ATS and expect everything to work fine. by disabling ATS you pretty much turned off VAAI and if you created any data store volumes with VAAI/ ATS ... See more...
ATS and VAAI Hold hands. You cannot just disable ATS and expect everything to work fine. by disabling ATS you pretty much turned off VAAI and if you created any data store volumes with VAAI/ ATS enabled and then later on disable this feature well you are running in a configuration which is prone to issues.Any host that has access to that datastore i would, maintenance mode, enable the setting. give the hosts a reboot and then once they are all backup start powering on vms. If you have multiple hosts that have access to the datastore and you decided to disable ATS on ONE of the hosts i am surprised your platform remained stable.
Are you using the Post Gen 9 Disk or pre g9 also have you setup your controller correctly
Has anyone had any success on having vRO work with a limited number of switches that have SNMP enabled with the correct creds. I thought i would enable SNMP with the creds on for certain switches... See more...
Has anyone had any success on having vRO work with a limited number of switches that have SNMP enabled with the correct creds. I thought i would enable SNMP with the creds on for certain switches to see what vRO does. Firstly it seems to go off and find random switches that it has not access too and then ignores the switches it does have access too. I thought about adding the switches manually with ips etc but vRO never polls them. The connector i can see is green and is polling something but i dont know what, there are two random physical switches which appeared in the inventory which vRO does not have access too, there are no spine or leaf switches at all.
i recently went from v6 server to v6.5 appliance. i would recommend why you are sitll on server to perform any maintenance tasks before the migration to the appliance. my db shrank from 60gb to l... See more...
i recently went from v6 server to v6.5 appliance. i would recommend why you are sitll on server to perform any maintenance tasks before the migration to the appliance. my db shrank from 60gb to less than 10gb and helped massively before migrating.
in log insight go to Administration (top right) then vsphere. Did you enter in the vcenter credentials here? Also under hosts is your vcenter listed under the hosts?
use the program RVtools to locate where these files are. they might appear under health tab for zombie vmdks I am not too sure if its possible to reload the vmx when the vm name is unknown. ... See more...
use the program RVtools to locate where these files are. they might appear under health tab for zombie vmdks I am not too sure if its possible to reload the vmx when the vm name is unknown. Reload inaccessible or invalid VM's with this PowerCLI one-liner | Techazine (Get -View -ViewType VirtualMachine) |?{$_.Runtime.ConnectionState -eq "invalid" -or $_.Runtime.ConnectionState -eq "inaccessible" } |%{$_.reload()} The other option is to remove from inventory (AFTER You know the datastore they are listed) and then re-add.
The vCenter upgrade in general is either hit or miss. If you are already on the appliance its fairly straight forward. If you are still on vCenter Server and moving to the 6.5 appliance with well... See more...
The vCenter upgrade in general is either hit or miss. If you are already on the appliance its fairly straight forward. If you are still on vCenter Server and moving to the 6.5 appliance with well over 10 million database entries it might be a tad difficult and painful. You need to get the compatibility matrix and see if NSX needs to be upgraded and if you are a version that might catch you out with the amount of bugs. Guest introspection had a very bad period late last year as well as the duplicate vtep issue whenever vcenter was rebooted. When i did might i took the opportunity to clean out the database of stuff i no longer required. I made a backup and then a snapshot of the vCenter and NSX Manager. Then it was a case of following the upgrade order and before the vcenter upgrade see what i could clean up. I reduced our vCenter database down from 60GB to less than 10GB which made the upgrade so much easier. The 6.5 roll back is fairly easy, shut down the faulty appliance and power back on your old stuff. If you are running vRops or other logging it might be worth shutting these down and only powering them back up when vcenter is up for good. We ended up with a few duplicate enteries when we had to roll back. We set DRS to manual and made sure the nsx components and vmware appliances did not move to keep routes going while the upgrade was taking place.
The early days of version 6 and the buggy firmware on the raid controller crippled most of us. Now with esxi 6.5 and more up to date firmware they are a lot more stable.
command line is what i prefer but i believe this can also be done via update manager.
why not just create them a VM they can remote into to access vCenter?
this is a bug. if you join hosts to the domain this message will vanish
i dont think the vmware interface actually lets you choose a evc mode higher than what your cpus support.
You need vSphere Standard NOT Essentials Plus.
are these on a distributed virtual switch?
VMware ESXi when installed allows you to use all features for a limited time period to test. No need for a Key unless you wish to run ESXi free edition which you get by logging into vmware portal
You get to keep the FQDN, if you want to keep the same name in the inventory just rename the vcenter before you start deployment, for the new vcenter 6.5 appliance call it the original vcenter na... See more...
You get to keep the FQDN, if you want to keep the same name in the inventory just rename the vcenter before you start deployment, for the new vcenter 6.5 appliance call it the original vcenter name and everything will switch over.
Host licensing is possible and you can have an unlimited amount of red hat vms running on that host. This is how we do it and use DRS rules/ groups to pin redhat vms to certain hosts in a cluster... See more...
Host licensing is possible and you can have an unlimited amount of red hat vms running on that host. This is how we do it and use DRS rules/ groups to pin redhat vms to certain hosts in a cluster. We use powershell to auto move red hat vms to the drs groups based on the guest os detected You will need the red hat licensing appliance and the host uuids in order to perform updates / patches to red hat vms.
Yes you need to point these to a datastore. Here is the VMware KB to help you https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2032823