Hello..
I admit to being a fan of the 'sysstat -x' output, especially for the columns of CP Time, CP Type and Overall Disk Utilization. No fuss, no mess, just the facts. And with very low impact to the filer to produce that data!
And I can do that command when logged into a 7-Mode or Cluster just fine.
I have a Powershell script that invokes the sysstat command against the 7Mode filers and then formats the output very nicely into centered columns and mails me the result. The script doesn't need to do lots and lots of calls to get counters, do math, average things out. The script uses the invoke-nassh command and then massages the resulting info into a nice table format that closely matches what we see when done on the command line.
When I try the same sequence against the clusters, the invoke-ncssh command detects the sysstat command and says:
"sysstat" is not supported: use the (privilege: advanced) "statistics { start | stop | show } -preset sysstat" command.
Why can't the CDOT API and filer code just allow this command to execute natively and save everyone, including the filer, a lot of overhead when we know a Powershell script isn't going to be able to do things on 1 second intervals over time so the numbers aren't going to come out right to start with?
I read through the following thread and it dealt with CP counters and not the CP types that can come to be.
http://community.netapp.com/t5/Software-Development-Kit-SDK-and-API-Discussions/CP-info/td-p/192
What are the suggested means to get this high level data, quickly, easily and at an accurate periodic?
Or maybe this needs to be an enhancement request to allow sysstat with the invoke-ncssh command?
My thanks for your time and thoughts.
pdc