Hello,
I'm having a weird problem with a PowerCLI output report script (attached), there are 3 machines that are not returning any data (the output is on the .txt attached). Probably it's a simple solution, but I don't know how I could reproduce it in my lab and I don't want to mess with the customer production enviroment. Maybe some of you guys have come up with something similar.
I have powershell v.4, PowerCLI 5.1, running on a windows 7 Pro 64-bit
Thanks in advance for your insights.
.
It looks as if the aggregation jobs have stopped running.
Have a look at the scheduled jobs on the DB server where you vCenter DB is stored.
Blog: lucd.info Twitter: @LucD22 Co-author PowerCLI Reference
Are the virtual machines that don't return output with the Get-Stat cmdlet powered on? Because powered off machines show this behavior.
PowerCLI C:\Users\Robert> get-vm pxetest
Name PowerState Num CPUs MemoryGB
---- ---------- -------- --------
pxetest PoweredOff 1 4.000
PowerCLI C:\Users\Robert> get-vm pxetest | get-stat
PowerCLI C:\Users\Robert>
Hi,
I forgot to mention that, yes, the VMs are powered on.
Do these 3 VM show any performance data under the Performance tab in the vSphere client for the period selected ?
And where these VMs powered on at the start of the interval selected ?
Blog: lucd.info Twitter: @LucD22 Co-author PowerCLI Reference
Thanks for your reply LucD. Machines has been powered on for some time, but oddly vCenter stopped collecting data, I restarted vCenter it and it is now showing stats. I should have done that before posting this thread, sorry, but anyway I really appreciate you reply. Time to investigate why it stopped collecting.
It looks as if the aggregation jobs have stopped running.
Have a look at the scheduled jobs on the DB server where you vCenter DB is stored.
Blog: lucd.info Twitter: @LucD22 Co-author PowerCLI Reference
Will do, thanks for the advise LucD