I was unable to retrieve data.  When I run the script:

C:\junk\test 2 vscsistats> .\get_vscsistats.ps1 -esxip 192.168.110.5 -username root -password xxxx

It pauses for a few moments and returns:

"not running anymore so quit"

Preflight check was successful.

See attachment

The "not running anymore so quit" dialog refers to the script trying to receive results but the vscsistats is outputting nothing for the specified world/diskhandlid's.  Any chance you're running 4.0 (prolly not)? One thing to mention with this script is that it doesn't manage which VMs and disks are being monitored.  It assumes that you have ran the commands from the document to kick the monitoring process off.  The script then logins into the ESX console and receives the metrics via SSH for one session and then repetitive commands every x seconds.   If you log in through SSH and run the command that receives the output of a running vscsistats session, do you see anything?  If not then this is why the script will report that the not running anymore.

Thanks for the feedback, let me know.

Yes I had kicked off vscsiStats on the ESX/ESXi host first.  That was my first thought based on the output from the script so I ran the vscsiStats -p all command to make sure data was being collected on the 3 virtual disks for the VM being monitored.

ESX/ESXi 4.1 Update 1

We can talk more tomorrow.

Hi 

I get this error while running the script, is that a problem ?

Receive-Job : Destination array was not long enough. Check destIndex and length
, and the array's lower bounds.
At C:\Users\Administrator\Desktop\pshell_get_vscsistats_022011\get_vscsistats.p
s1:126 char:55
+     if ($joboutput = (get-job -name job1 | receive-job <<<<  -keep | where {$
_.field -match '\*\* JOB DONE \*\*' }) | select -last 1) {
    + CategoryInfo          : NotSpecified: (:) [Receive-Job], ArgumentExcepti
   on
    + FullyQualifiedErrorId : System.ArgumentException,Microsoft.PowerShell.Co
   mmands.ReceiveJobCommand

I just posted an updated copy of the vscsistats script that allows for ESX/i 4.0 and fixes some XP/2003 job compatibility issues.  Also make sure to use "set-executionpolicy  bypass" if you are getting security warnings when executing the script.  Security warnings can cause the script to hang in the background as it kicks off the collection jobs.

Hi, I just downloaded the zip file with the differnet powershell scripts.  I did not see a get_vscsistats.ps1 in the folder.

When extracted, it came with the following powershell scripts:
collect_vscsistats.ps1

exec_vscsistats.ps1

show_vscsistats.ps1

ssh_function.ps1

As I was reading through the Instruction PDF, it only mentions Get_vscsistats.ps1

If I'm totally missing this, I'm sorry, I'm very new to VMWare, and never have done anything from PowerShell before yesterday.

Any help would be appreciated.  Thanks

Edit:

In the manual, should i just be replaceing the get_vscsistats.ps1 with collect_vscsistats.ps1?

I actually tried this command: collect_vscsistats.ps1 -esxip 10.X.X.X -username root - password password

It returned: need an -outcsv

The document was just updated to match the most recent version.  The -outcsv is a requirement, and the script was renamed to collect_vscsistats.ps1 more closely reference what it really does and to be standarized across other similar ones.

Thanks

Thanks, I'm retrying now.

I'm using the same command but added -outcsv c:\temp  at the end.

After about 5 Minutes it came back with an error. (attached)

I'm also assuming I'll have to run this command on all of my esx servers once I figure out what is going on, correct?

Ok... I see I need to install vscsistats on my ESX hosts.. looks like something to do when I'm doing maintance on them sometime.

Thanks for your help.

Hi Clinton

Im having some problems with the script... The script is running fine, but at some point I start getting an 'error' that there is no io from vm...

I cant figure out if its a timeout or what... The shortest vscsistats i ran lasted only 6 minutes before the message came... The longest ran close to an hour...

Any idea ?

This refers to a situation where there is either no active IO occuring, or all vscsistats sessions have ended on the esx host.  Vscsistats has been a bit unpredictable for me at times in terms of length of runs.  Jason Boche mentioned a 30 minute default timeout for the session, but I've seen it last longer and shorter as well.  If anyone has any insight into why a vscsistats session would end without a forced stop I would be interested to hear.

For now you can kick off the command on the ESX host to start back up the session and vscsistats will continue recording the output.  A management script for automagically kicking off and ensuring it is running might be needed to overcome the challenge.