[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Freeipmi-users] Mixed assertion/deassertion problems on Sun X4150
From: |
Al Chu |
Subject: |
Re: [Freeipmi-users] Mixed assertion/deassertion problems on Sun X4150 |
Date: |
Fri, 15 May 2009 09:40:54 -0700 |
Hi Rob,
Argh! I was afraid some vendor would do something like this eventually.
Having the same "style" sensors report states/events in non-consistent
manners. I will have to think of a way to deal with this in the future.
As for your question ...
> I've been trying to figure if I can get ipmimonitoring to simply not
> report some sensors (e.g the PS*/*_FAULT) ones above - but can't
> figure how to do this. Is it possible?
There is a --groups and --sensors option for ipmimonitoring where you
can specifically list which sensors/groups you want to see. You can
configure the default list of groups into the freeipmi.conf file to make
it default to a certain output if that makes things easier for you [1].
Unfortunately, these are "show me this stuff" options, not "exclude this
stuff" options. So you'll have to list all the groups/sensors you want.
Longer term (it's now on my TODO), it might be good if I create a
"--exclude-groups" and "--exclude-sensors" options, that can eliminate
sensors to list.
Hope that answers your question. And thanks for e-mailing about this.
Now I see a new good option I should put into ipmi-sensors and
ipmimonitoring.
Al
[1] There's a typo in the freeipmi.conf file that'll be fixed soon. You
separate groups by spaces, not commas.
On Fri, 2009-05-15 at 08:03 -0700, ocoro02 wrote:
> Hi Folks - I'm using FreeIPMI 0.7.8 on Solaris 10 on some Sun X4150 servers -
> these have had their Eloms updated to be Iloms running (from memory)
> 2.0.2.10 of the Ilom firmware.
>
> With ipmimonitoring for the Power_Supply group I see:
>
> # ipmimonitoring | grep "Power Supply"
> 29 | PS0/VINOK | Power Supply | Warning | N/A | 'State Asserted'
> 30 | PS0/PWROK | Power Supply | Warning | N/A | 'State Asserted'
> 31 | PS0/CUR_FAULT | Power Supply | Nominal | N/A | 'State Deasserted'
> 32 | PS0/VOLT_FAULT | Power Supply | Nominal | N/A | 'State Deasserted'
> 33 | PS0/FAN_FAULT | Power Supply | Nominal | N/A | 'State Deasserted'
> 34 | PS0/TEMP_FAULT | Power Supply | Nominal | N/A | 'State Deasserted'
> 43 | PS1/VINOK | Power Supply | Warning | N/A | 'State Asserted'
> 44 | PS1/PWROK | Power Supply | Warning | N/A | 'State Asserted'
> 45 | PS1/CUR_FAULT | Power Supply | Nominal | N/A | 'State Deasserted'
> 46 | PS1/VOLT_FAULT | Power Supply | Nominal | N/A | 'State Deasserted'
> 47 | PS1/FAN_FAULT | Power Supply | Nominal | N/A | 'State Deasserted'
> 48 | PS1/TEMP_FAULT | Power Supply | Nominal | N/A | 'State Deasserted'
>
> You see the problem? The '*OK' sensors are asserted, but in Warning state.
> Unfortunately I can't flip assertion in ipmi_monitoring_sensors.conf - i.e
> like this:
>
> IPMI_Power_Supply_State_Deasserted Critical
> IPMI_Power_Supply_State_Asserted Nominal
>
> because the '*_FAULT' sensors will then be in Critical.
>
> I've been trying to figure if I can get ipmimonitoring to simply not report
> some sensors (e.g the PS*/*_FAULT) ones above - but can't figure how to do
> this. Is it possible?
--
Albert Chu
address@hidden
Computer Scientist
High Performance Systems Division
Lawrence Livermore National Laboratory