Rubeck's Accepted Solutions

Hi... I have no idea on what the issue might be, but maybe the Linux package, "open-vm-tools", is something worth looking in to? VMware support for Open VM Tools (2073803) | VMware KB ... See more...
Hi... I have no idea on what the issue might be, but maybe the Linux package, "open-vm-tools", is something worth looking in to? VMware support for Open VM Tools (2073803) | VMware KB /Rubeck
Try executing the "dcui" command within a SSH session.... Accessing Direct Console User Interface (DCUI) from an SSH session (2039638) | VMware KB /Rubeck
Hi.. Were VM snapshots taken while having an .iso mounted to them? If so, this would explain it.. /Rubeck
You need a vCenter server to work with templates.... vCenter can then be managed by using PowerCLI. /Rubeck
According to the HP/VMware recipe here: http://vibsdepot.hp.com/hpq/recipes/HP-VMware-Recipe.pdf There's a note regarding the NC551i: /Rubeck
If I run a 5.1 ESX cluster BUT I manage it using a vCenter 5.5, am I out of support or not? According to the VMware Product Interoperability Matrixes your config is fully supported: ... See more...
If I run a 5.1 ESX cluster BUT I manage it using a vCenter 5.5, am I out of support or not? According to the VMware Product Interoperability Matrixes your config is fully supported: /Rubeck
Hi.. Both are actually automatically generated... 00:00c:29 is generated by the ESXi host itself when not joined to a vCenter instance. 00:50:56 is generated by vCenter if the ESXi host is jo... See more...
Hi.. Both are actually automatically generated... 00:00c:29 is generated by the ESXi host itself when not joined to a vCenter instance. 00:50:56 is generated by vCenter if the ESXi host is joined to such. But can I reuse the automatically generated MAC address which starts with 00:0c:29 (and of course make sure ESXi won't use the same MAC address for another VM)? Yes.. /Rubeck
The VM lives on a NFS datastore with no HW accel.? If so, that would explain it. /Rubeck
Example: Download the .vib package here: http://vibsdepot.hp.com/hpq/feb2013/esxi-5x-vibs/hpacucli/hpacucli-9.40-12.0.vib and place it on a datastore seen by the host... Install it using ... See more...
Example: Download the .vib package here: http://vibsdepot.hp.com/hpq/feb2013/esxi-5x-vibs/hpacucli/hpacucli-9.40-12.0.vib and place it on a datastore seen by the host... Install it using CLI: esxcli software vib install -d /vmfs/volumes/<datastore name>/hpacucli-9.40-12.0.vib Now run it: ~ # cd /opt/hp/hpacucli/bin /opt/hp/hpacucli/bin # ./hpacucli HP Array Configuration Utility CLI 9.40.12.0 Detecting Controllers...Done. Type "help" for a list of supported commands. Type "exit" to close the console. => ctrl all diag file=/tmp/my_ADUreport.zip ris=on xml=on zip=on    Generating diagnostic report...done => exit /opt/hp/hpacucli/bin # my_ADUreport.zip in /tmp can now be downloaded from the host.. Hope it helps.. /Rubeck
Will it restrict our ability to add hot cpu ?? No it will not... See VMware KB: Disabling the HotAdd/HotPlug capability in ESXi 5.x and ESXi/ESX 4.x virtual machines /Rubeck
When I use these commands : vmkfstools -i vmfs/volumes/mydatastore/myvirtualmachinefoldername/my.vmdk vmfs/volumes/mydatastore/newmachinefoldername/new.vmdk -d thin Unless your working dire... See more...
When I use these commands : vmkfstools -i vmfs/volumes/mydatastore/myvirtualmachinefoldername/my.vmdk vmfs/volumes/mydatastore/newmachinefoldername/new.vmdk -d thin Unless your working directory from where you execute this command is /, you would need a "/" in front of the paths....  so try: "vmkfstools -i /vmfs/volumes/mydatastore/myvirtualmachinefoldername/my.vmdk /vmfs/volumes/mydatastore/newmachinefoldername/new.vmdk -d thin" /Rubeck
Shut the VM down, remove the entry manually from its .vmx file and reload it,,, (or unregister and register) /Rubeck
SCSI controller changed from LSI Logic SAS into Paravirtual Not really an option..... This isn't supported by VMware in a MSCS setup.. /Rubeck
Hi Matt. ...on ESXi 4.1 with a vSphere 4 Enterprise licence.. For vSphere 4 you need an Enterprise Plus license if want to create 8 vCPU VMs, In vSphere 5 any license will do...  ... See more...
Hi Matt. ...on ESXi 4.1 with a vSphere 4 Enterprise licence.. For vSphere 4 you need an Enterprise Plus license if want to create 8 vCPU VMs, In vSphere 5 any license will do...  /Rubeck
Could you do a "show interface brief" and "show interface" on the HP switch and paste it here? I would remove the trunks as I can't see why this is needed in your setup.. Verify that Route ... See more...
Could you do a "show interface brief" and "show interface" on the HP switch and paste it here? I would remove the trunks as I can't see why this is needed in your setup.. Verify that Route based on the originating virtual port ID is selected on vSwitch1 and on the two configured portgroups (PLC and Proces). Remove the trunks on the HP switch and tag/untag required VLANs onto the individual ports which were used previously as a part of these trunks..  Quick config needed for the HP.. conf t no trunk 23,47 Trk10 Trunk no trunk 24,48 Trk10 Trunk vlan 1 untagged 23,24,47,48 vlan 40 tagged 23,24,47,48 vlan 41 tagged 23,24,47,48 WARNING: You might have some network hickups when doing this.. What switch model do you use.. ? /Rubeck
Hi.. Have you tried to append forced at the end to see if this does the trick? "Esxcli - s <server ip address> hpacucli cmd –q “controller slot=3 logicaldrive 1 modify size=max forced". ... See more...
Hi.. Have you tried to append forced at the end to see if this does the trick? "Esxcli - s <server ip address> hpacucli cmd –q “controller slot=3 logicaldrive 1 modify size=max forced". /Rubeck
Maybe the Promise VessRAID iSCSI SAN only has a single storage controller/storage processor (SP) with multiple ports? When looking at their website it looks like the Vess series are single contr... See more...
Maybe the Promise VessRAID iSCSI SAN only has a single storage controller/storage processor (SP) with multiple ports? When looking at their website it looks like the Vess series are single controller only.... So obviously it won't be able to fail over to another storage processor if the primary fails..  /Rubeck
Maybe this KB has some relevant info   ;: http://kb.vmware.com/kb/1015268 /Rubeck
According to this VMware vSphere 5.1 the vCenter co-stop counter was introduced in v5.0..... The counter is available in 4.1 but in esxtop only.. not in vCenter..   /Rubeck
Try Disconnect-VIServer -confirm:$false .... /Rubeck