Hi Corey,
I've attached the output of <ipmitool channel info> output. Channel 0 and 6 are
the IPMB according to the output. Please let me know if any additional
information you need.
Thanks,
Roman.
-----Original Message-----
From: Corey Minyard [mailto:[email protected]] On Behalf Of Corey Minyard
Sent: Thursday, February 2, 2017 3:57 PM
To: Korynkevych, RomanX <[email protected]>
Cc: [email protected]
Subject: Re: [Openipmi-developer] Doubled events received from SEL
On 02/01/2017 08:47 AM, Korynkevych, RomanX wrote:
> Thanks Corey,
>
> I've dumped raw SDR data to a file using command <ipmitool sdr dump 123.txt>.
> Could you please advice how to decode it?
Ok, I modified the SDR compiler to decode, but the problem is not there.
However, I think I know what the problem is.
By default OpenIPMI will scan every IPMB channel it finds to see if there are
any management controllers out there that need handling. The trouble is that
this particular BMC is responding to it's own address on channel 6. OpenIPMI
has no way to know that this is not a new BMC because there is no way to
discover what the IPMB address for the BMC is for a specific channel.
OpenIPMI does have some code to handle this (by making assumptions), and I
don't see a bug in it, so I'm wondering if your system has a channel 0 IPMB.
Can you send the output of the following command:
i=0; while [ $i -lt 16 ]; do ipmitool <your connection parms>
channel info $i; i=`expr $i + 1`; done
Channel 0 is supposed to be IPMB, but if channel 0 is not IPMB, then the
scanning will not scan that channel and assume channel 6 is the main IPMB
channel. The SDRs have channel 0 IPMB 20 for the main SDR, so it will be
confused.
I have previously stated that a BMC should respond to it's own address.
I'm wondering if I was wrong here now.
I can modify the simulator a bit to reproduce this situation. But there may
still be a bug elsewhere causing an issue, and this is not the issue.
You can work around this by turning off IPMB scanning. When you call
ipmi_open_domain, pass in options to set IPMI_OPEN_OPTION_ALL off and then
enable all the options 2-7 except for the IPMB scan one.
In the mean time, I'll try to reproduce.
-corey
> Regards,
> Roman.
>
> -----Original Message-----
> From: Corey Minyard [mailto:[email protected]] On Behalf Of Corey
> Minyard
> Sent: Tuesday, January 24, 2017 7:41 PM
> To: Korynkevych, RomanX <[email protected]>;
> [email protected]
> Subject: Re: [Openipmi-developer] Doubled events received from SEL
>
> On 01/24/2017 11:30 AM, Korynkevych, RomanX wrote:
>> Hi Guys,
>>
>> I'm writing application which uses OpenIPMI v2.0.22 library SEL
>> mechanism similar to eventd.c sample application. I register
>> threshold and discrete event handlers for available sensors for
>> domain called mydomain2. When I generate event using ipmitool I'm
>> receive event successfully but it comes twice and all the data is the
>> same (duplicated). After investigation it looks like event is invoked
>> from different MCs. I'm seeing that OpenIPMI lib handler
>> (handle_sel_data()) is called for MC names "mydomain2(0.20)" and
>> "mydomain2(6.20)". In my event handler I'm calling
>> ipmi_sensor_get_mc() and ipmi_mc_get_name() to understand which MC
>> the sensor belongs to and it returns "mydomain2(0.20)". Also I added
>> event handler for SMI interface and when the event arrives there are
>> no doubled events observed.
>>
>> Does anybody has seen this issue? Is this behavior expected? What is
>> the reason I'm receiving events twice?
>>
> It looks like something in your SDRs hash something for IPMB address 20
> channel 6. OpenIPMI adds that as a new MC, but it's the same one as 0.20.
> So it's looking at the same MC as if it was two different MCs, and thus you
> get two events.
>
> I'd have to have the SDRs to be sure. But hopefully you can look at them and
> see. You should have some sensor that's on (6.20).
>
> -corey
>
>> Regards,
>>
>> Roman.
>>
>> --------------------------------------------------------------
>> Intel Research and Development Ireland Limited Registered in Ireland
>> Registered Office: Collinstown Industrial Park, Leixlip, County
>> Kildare Registered Number: 308263
>>
>> This e-mail and any attachments may contain confidential material for
>> the sole use of the intended recipient(s). Any review or distribution
>> by others is strictly prohibited. If you are not the intended
>> recipient, please contact the sender and delete all copies.
>>
>>
>>
>> ---------------------------------------------------------------------
>> -
>> -------- Check out the vibrant tech community on one of the world's
>> most engaging tech sites, SlashDot.org! http://sdm.link/slashdot
>>
>>
>> _______________________________________________
>> Openipmi-developer mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/openipmi-developer
>
>
>
> ----------------------------------------------------------------------
> -------- Check out the vibrant tech community on one of the world's
> most engaging tech sites, SlashDot.org! http://sdm.link/slashdot
>
>
> _______________________________________________
> Openipmi-developer mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/openipmi-developer
Channel 0x0 info:
Channel Medium Type : IPMB (I2C)
Channel Protocol Type : IPMB-1.0
Session Support : session-less
Active Session Count : 0
Protocol Vendor ID : 7154
Channel 0x1 info:
Channel Medium Type : 802.3 LAN
Channel Protocol Type : IPMB-1.0
Session Support : multi-session
Active Session Count : 0
Protocol Vendor ID : 7154
Volatile(active) Settings
Alerting : enabled
Per-message Auth : enabled
User Level Auth : enabled
Access Mode : always available
Non-Volatile Settings
Alerting : enabled
Per-message Auth : enabled
User Level Auth : enabled
Access Mode : always available
Channel 0x2 info:
Channel Medium Type : 802.3 LAN
Channel Protocol Type : IPMB-1.0
Session Support : multi-session
Active Session Count : 0
Protocol Vendor ID : 7154
Volatile(active) Settings
Alerting : enabled
Per-message Auth : enabled
User Level Auth : enabled
Access Mode : always available
Non-Volatile Settings
Alerting : enabled
Per-message Auth : enabled
User Level Auth : enabled
Access Mode : always available
Channel 0x3 info:
Channel Medium Type : 802.3 LAN
Channel Protocol Type : IPMB-1.0
Session Support : multi-session
Active Session Count : 0
Protocol Vendor ID : 7154
Volatile(active) Settings
Alerting : enabled
Per-message Auth : enabled
User Level Auth : enabled
Access Mode : always available
Non-Volatile Settings
Alerting : enabled
Per-message Auth : enabled
User Level Auth : enabled
Access Mode : always available
IPMI command failed: Invalid data field in request
Unable to Get Channel Info
IPMI command failed: Invalid data field in request
Unable to Get Channel Info
Channel 0x6 info:
Channel Medium Type : IPMB (I2C)
Channel Protocol Type : IPMB-1.0
Session Support : session-less
Active Session Count : 0
Protocol Vendor ID : 7154
Channel 0x7 info:
Channel Medium Type : System Interface
Channel Protocol Type : KCS
Session Support : session-less
Active Session Count : 0
Protocol Vendor ID : 7154
IPMI command failed: Invalid data field in request
Unable to Get Channel Info
IPMI command failed: Invalid data field in request
Unable to Get Channel Info
IPMI command failed: Invalid data field in request
Unable to Get Channel Info
IPMI command failed: Invalid data field in request
Unable to Get Channel Info
Given Channel number '12' is either invalid or out of range.
Channel number must be from ranges: <0x0..0xB>, <0xE..0xF>
Given Channel number '13' is either invalid or out of range.
Channel number must be from ranges: <0x0..0xB>, <0xE..0xF>
Channel 0xf info:
Channel Medium Type : System Interface
Channel Protocol Type : KCS
Session Support : session-less
Active Session Count : 0
Protocol Vendor ID : 7154
Channel 0xf info:
Channel Medium Type : System Interface
Channel Protocol Type : KCS
Session Support : session-less
Active Session Count : 0
Protocol Vendor ID : 7154------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Openipmi-developer mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openipmi-developer
