If somewhere in the whole patern there are no jumbo frames, everything will go back to the standard MTU (1500). If you have a reason why you would need jumbo frames on the OS then you'll have to ...
See more...
If somewhere in the whole patern there are no jumbo frames, everything will go back to the standard MTU (1500). If you have a reason why you would need jumbo frames on the OS then you'll have to configure it. This is usually if a customer wants it or for a specific app. If you are using iSCSI storage it is usually suggested to use Jumbo frames as well.
Can you try to do a host vmotion and see if it gets resolved? If not, can you shut down the VM's and start them again? I have seen this issue before and a shutdown and start resolved it.
Can you try to do a host vmotion and see if it gets resolved? If not, can you shut down the VM's and start them again? I have seen this issue before and a shutdown and start resolved it.
Not yet. vSphere 5.1 is the latest release but it has had patches released (a and b). VMware will announce information when they decide it is time for it so there is at the moment nothing know...
See more...
Not yet. vSphere 5.1 is the latest release but it has had patches released (a and b). VMware will announce information when they decide it is time for it so there is at the moment nothing known to the outside world about version 6 or whatever they will call it.
This is normal as this is a small version of ps. Why exactly would you need the list? You could get the command list using awk if needed: ps | awk {'print $4'}
There are some scripts out there who can do this but I think this one can help you: http://ict-freak.nl/2009/06/09/powercli-set-vm-startup-policy/ Keep in mind that this won't work if you are...
See more...
There are some scripts out there who can do this but I think this one can help you: http://ict-freak.nl/2009/06/09/powercli-set-vm-startup-policy/ Keep in mind that this won't work if you are using an HA cluster as already mentioned.
You will need to generate a public and private key on Windows using puttygen. You will then have to copy the public key towards your ESXi host (.ssh/authorized_keys). You will then have to con...
See more...
You will need to generate a public and private key on Windows using puttygen. You will then have to copy the public key towards your ESXi host (.ssh/authorized_keys). You will then have to configure putty on how to use the private key and you will be able to login via SSH without password. I suggest you use https://hkn.eecs.berkeley.edu/~dhsu/ssh_public_key_howto.html as a guide.
Try something like this: Connect-VIServer localhost | Out-Null $vm = Get-VM | Select Name, Notes Write-Output $vm Disconnect-VIServer localhost -Confirm:$false This will show you t...
See more...
Try something like this: Connect-VIServer localhost | Out-Null $vm = Get-VM | Select Name, Notes Write-Output $vm Disconnect-VIServer localhost -Confirm:$false This will show you the VM name and the standard notes.
Try the following, this will give you all the VM's which have been restarted and the time when it happened. Connect-VIServer -Server yourserver $start = (Get-Date).AddDays(-5) Get-VIEvent...
See more...
Try the following, this will give you all the VM's which have been restarted and the time when it happened. Connect-VIServer -Server yourserver $start = (Get-Date).AddDays(-5) Get-VIEvent -MaxSamples 1000000 -Start $start -Type warning | Where {$_.FullFormattedMessage -Match "vSphere HA restarted"} | Select ObjectName, CreatedTime, FullFormattedMessage Disconnect-VIServer -Confirm:$false
You should be able to do something like this (instead of Get-Host | Get-VM | enable-memhotadd $vms = Get-VM foreach ($vm in $vms) { Enable-MemHotAdd ($vm) } This will enable it...
See more...
You should be able to do something like this (instead of Get-Host | Get-VM | enable-memhotadd $vms = Get-VM foreach ($vm in $vms) { Enable-MemHotAdd ($vm) } This will enable it for all the VM's in your vCenter, keep in mind this might take a while if you have a lot of VM's.
The following can be found in the vCenter 5 release notes, maybe this is your solution: With software FCoE enabled, attempts to display Storage Maps fail with an error message This problem...
See more...
The following can be found in the vCenter 5 release notes, maybe this is your solution: With software FCoE enabled, attempts to display Storage Maps fail with an error message This problem affects only those ESXi hosts that have been added to vCenter Server without any previous software FCoE configuration. After you enable software FCoE adapters on these hosts, attempts to display Storage Maps in the vSphere Client fail. The following error message appears: An internal error has occurred: Failed to serialize response . Workaround: Configure software FCoE on the ESXi host first, and then add the host to vCenter Server.
You can build a raid set per server and then combine these by using the appliance. I would suggest testing different raid sets to maximize your performance. This also depends on the type of disks...
See more...
You can build a raid set per server and then combine these by using the appliance. I would suggest testing different raid sets to maximize your performance. This also depends on the type of disks (SAS, SATA, SSD).
Can you please inform us about the used hardware: - Which type of local storage are you using? - Did the install run fine or did you run into an error? - Via which medium did u perform the ins...
See more...
Can you please inform us about the used hardware: - Which type of local storage are you using? - Did the install run fine or did you run into an error? - Via which medium did u perform the install?
You can remove the datastore from the cluster by dragging it into your datacenter via the vSphere client. You can disable SIOC via a host in the configuration tab -> storage. You can disabl...
See more...
You can remove the datastore from the cluster by dragging it into your datacenter via the vSphere client. You can disable SIOC via a host in the configuration tab -> storage. You can disable HA heartbeat by disabling HA on your Hosts cluster. Usually when you get this warning it means the datastore is still in use by something. First try the first 2 options and then try removing it before disabling HA on your cluster. This should resolve the issue on removing it.
It will disable all the alarm actions for that specific datastore, so not the while vCenter. Make sure you are in the correct view "Home -> Inventory -> Datastores and Datastore clusters" I...
See more...
It will disable all the alarm actions for that specific datastore, so not the while vCenter. Make sure you are in the correct view "Home -> Inventory -> Datastores and Datastore clusters" If you are in Host and clusters you can disable the alarms on that specifc SQL VM.