Do I need that sp part? the IP address is the SP so I just label it as such. But if the command needs it Ill add it!
With the script I need to do calculations based on the last successful check of the tick values. I store these tick values in a file in /tmp. On the next successful check I overwrite this file with the latest tick values. I needed to name the file something and I didn't want data from different SP checks getting mixed up. This is why I chose to enforce the --sp option so my file would be named uniquely. For example I monitor both SP's on my Nagios host so I end up with the following files in /tmp : check_emc_clariion_cbtbusy_192.168.100.201_A_tmp and check_emc_clariion_cbtbusy_192.168.100.202_B_tmp.
Fantastic! Cue the applause! Definitely jives with Navisphere stats!
Great stuff, it's good to get the result we were after. With the formula you provided we were able to work together to make it happen
I had noticed during my manual sampling that EMC was capable of throwing some "bad data". During one sample the Busy count threw a negative number.
Hmmm interesting. I should probably update the script so that it detects any negative numbers and discards this information and waits for the next check. I'll have a play with this and get back to you.
