[op5-users] check_esx3 - why no info

[Juborg, Per (WSP Sweden, Stockholm-Globen)]

Sounds good.

From OP5 I only check specific volumes since we're not interested in the local file systems which shows up when running check_esx3 -l VMF. I did not get any indications on failed paths or anything.

/Per

-----Original Message-----
From: kgushtin [mailto:kgushtin at n-ix.com.ua] 
Sent: den 25 augusti 2010 19:28
To: Juborg, Per (WSP Sweden, Stockholm-Globen)
Subject: Re: [op5-users] check_esx3 - why no info

Hi.
> I was working on few other bugs. And now back to your request. After 
> thinking for a while, I come up with this idea :
> If this broken hba is represented as VMFS volume then you can try to 
> issue this checks:
> /opt/plugins/check_esx3.pl -H {ESXi host name, which has a problem} -u 
> {user name} -p {password} -l vmfs -s {broken volume name} or 
> /opt/plugins/check_esx3.pl -H {ESXi host name, which has a problem} -f 
> {path to file with credentials} -l vmfs -s {broken volume name} In 
> normal case it should display "CHECK_ESX3.PL OK - storages : ...", but 
> in your case it can display other stuff. If so can you post it to me ?
I rewrite vmfs check and now it will told you if some of the volumes aren't accessible, instead of silently showing cached values. Also you can run checks without -s argument.

PS: need to fix other bugs which I discovered, so will look to "check the number of Targets/devices/paths for an adapter" tomorrow.

Regards,
Kostyantyn