I can almost guarantee you are having this problem as I did. http://www.supermicro.com/support/faqs/faq.cfm?faq=11049
You probably have Active State Power Management enabled in your bios. I had the exact same problem with a Supermicro and Intel 82576 onboard NIC.
Disable ASPM and those issues will be gone.
In vApp Workflows under "vApp Power Workflows", there is a Workflow named "Undeploy a vApp" : Stops or suspends a vApp and frees the resources reserved for the vApp. Do you know what resources are freed if I use it instead of "Suspend a vApp": Suspends a vApp. Does not free the resources reserved for the vApp? I'm planning to use vCO for the task of suspending all running vApps.
Thanks!
Here is my understanding ... Straight Suspend does not free the reservations .... Suspend needs to keep the reservations there so you can ensure a resume succeeds. this is just for CPU/MB reservations on the VMs/pools.
Stop will also undeploy, but powers off the VMs ... same as a 'stop' from the UI.
Either of these should be fine for you to perform, since the goal is to power off VMs to take a SAN snap, just that suspend takes that much longer.
Does Hyper natively monitor MSCSclusters?
Thanks,
-MattG
Hi LucD,
I'm using PowerCli 4.1 & 5.1 as well in difference servers. Environment is vSphere 4.x (4.0 and 4.1) servers. Basically i'm looking for LUN information in below format.
Host Name
HBA Name
LUN #
PathSelectionPolicy
Source
Status
Target
Path
Datastore name
and How many paths that LUN has
Thanks in advance
Br,
Kris
what is the sum of all other disks on the VM?
Thank you.
In the past, I used to occasionally go through and reclaim space on thin provisioned disks that had expanded. I was using a technique I've seen listed in lots of different places, involving running sdelete to zero out the empty space, then doing storage vmotion to migrate to a LUN with a different block size. This has worked for at least the last couple of years.
I'm trying it again today, and it's not working. When I do the storage vmotion, no space is reclaimed. I've triple-verified that I'm moving to LUNs with different block sizes. Just for testing purposes I've tried both the -z and -c option in sdelete. (My notes say -c is the way to go, but there's conflicting info out there, and the commands themselves seem to be flipped in sdelete documentation.)
The only thing that's changed is we've upgraded from version 4 to version 5 of vSphere. From what I can see, people claim it still works in v5, but that's all I've got to go on. Anybody else experiencing this.
Hola,
Te paso este link tambien por si te puede ayudar en algo:
Saludos,
What version of Protect are you using and what version of Windows is this installed on?
the ESXi host is not powered down ... the host is put into maintenance mode.
In an ideal world, you would have vCenter/vShield in a different cluster than your vCloud deployed VMs.
For this to happen, you need to ensure DRS is at full auto mode, and that vMotion does actually work.
Aside from that, if you create a provider vDC and prepare ALL hosts, they may all try to enter maintenance mode on their own.
This is a bit of an awkward scenario ... since you can't move VMs onto a host entering maintenance mode.
so even though if failed, if one prepared fine ... see if you can prepare the failed host ... this time it may work.
Hi,
Were you just searching for the plugin version via patch view? Or was this actually looking a software distribution scan results? It is possible the plugin may not be available for software distribution, but I'll have to check further into that.
Can the polling interval to the agents be modified? Can they be modified on a per agent basis?
Can duplicate alerts be suppressed?
DoesHyperichave the ability to monitor or limit the amount of CPU that theHypericagent uses?
Thanks,
-MattG
What build numbers of vShield, vCenter, and ESXi are you working with?
did you configure the vmknic nic to use an actual address? the default is DHCP, but most people need to set static.
It's actually really handy to have DHCP for enough addresses of the vmkernel adapters that get put out.
THanks. Couple of questions.
In an ideal world, you would have vCenter/vShield in a different cluster than your vCloud deployed VMs.
I've heard this before, but note that the documentation for the evaluation set up clearly shows the vShield Manager in the resource cluster, as opposed to the management cluster. Is this a legacy deployment pattern?
For this to happen, you need to ensure DRS is at full auto mode, and that vMotion does actually work.
I'm suprized that I am allowed to create DRS, as I did, on my cluster if vMotion is working . . . shouldn't there be some sort of a warning here?
Aside from that, if you create a provider vDC and prepare ALL hosts, they may all try to enter maintenance mode on their own.
Are you saying that even with vMotion functioning, there could be a problem anyway? I only have two hosts in my cluster, perhaps they are going to have a race condition on who can get into maintenance mode first? This would suggest that you couldn't really deploy any vDC onto clusters that currently have vm's on them, right?
hello
curious as to why everyone in the persona repository has two folders referenced above instead of just one?
thanks in advance
-charlie
"i've heard this before, but note that the documentation for the evaluation set up clearly shows the vShield Manager in the resource cluster, as opposed to the management cluster. Is this a legacy deployment pattern?"
No ... it was a matter of trying to use the fewest number of ESXi hosts.
"I'm surprised that I am allowed to create DRS, as I did, on my cluster if vMotion is working . . . shouldn't there be some sort of a warning here?"
You mean a resource pool? Don't confuse the automation mode (full vs manual) with having DRS enabled/disabled. If you create a cluster of exactly 1 ESXi host, you have to set DRS to manual mode to allow resource pools to exist.
There is no warning if DRS is in Manual Automation mode, since it's doing exactly what it what it thinks is normal ... not moving VMs around.
"Are you saying that even with vMotion functioning, there could be a problem anyway? I only have two hosts in my cluster, perhaps they are going to have a race condition on who can get into maintenance mode first? This would suggest that you couldn't really deploy any vDC onto clusters that currently have vm's on them, right?"
vCloud Director is the one putting all the hosts into maintenance mode at the same time. If you only have 2 hosts, it'll do all hosts. There are some considerations to be had with the "proof of concept" that you are doing since the vShield manager is in the deployment cluster. This issue would be avoided with a non-trial setup.
all that being said ... there are probably still some improvements to be made.
Hello, community!
I have problem with Virtual Machine running at VmWare Workstation.
You can see my networking in attached images.
I'm using vmnet1, which as you can see bridged to eth1 (of host machine). Host machine is GNU/Debian Linux
Also in images you can see
that first interface uses custom virtual network vmnet1 and has mac 00:0c:29:b4:0d:f2. It refers as eth0 inside vm.
and
that second interface also uses custom virtual network vmnet1 and has mac 00:0c:29:b4:0d:fc. It refers as eth1 inside vm.
Also you can see ifconfig for these interfaces.
The problem is: I can ping only second interface (eth1 with ip: 101.1.1.23). While pinging 101.1.1.22 (eth0) I got "request timeout".
As I investigated there is problem with ARP. Both interfaces resolve with same mac address (00:0c:29:b4:0d:fc)
After I flushed ARP table. I did ping to both ips (22 and 23)
I got in ARP table:
101.1.1.22 00:0c:29:b4:0d:fc
101.1.1.23 00:0c:29:b4:0d:fc
Why this happens and how to fix this issue?
Hello all,
I have a messed up installation of vCenter I want to perform a complete re-install of vCenter non-disrutively and I think I can do it but would like to get some other opinions to be sure I am not missing something. I have a 3 host cluster with about 40 VMs that I would like to keep running throughout the entire process. The server is currently running an upgraded instance of vCenter 5.1 U1 but the upgrade did not go very well. The OS is Windows 2003 x64. I have no need to save any of the performance data in the database. I also need to upgrade my 3 ESXi hosts to 5.1 U1.
This is my plan...
