Re: [Freeipmi-users] Using IPMI on Compulab MintBox

[Amos Shapir]

Hi Al and ipmi users,

Now we got a new ethernet card which is sure to have an I210 (device ID is
1533); however, I get exactly the same behavior.
If the device's addresses are not advertised, how can we discover the
addresses?  Are the ipmi tools still usable?

Thanks

On Wed, Sep 18, 2019 at 10:52 AM Amos Shapir <address@hidden>
wrote:

> Thanks Al & ipmi users,
>
> After going through all 530 pages of Intel's documentation, I found that one
> of the main differences between I210 and I211 is that the latter does NOT
> have NC-SI and MCTP capabilities; that's a good reason for not responding...
>
> We are now trying workarounds, possibly replacing the NIC to one which
> does include an I210 chip.
>
> On Mon, Sep 16, 2019 at 7:16 PM Al Chu <address@hidden> wrote:
>
>> Hi Amos,
>>
>> It definitely looks like your board does not publish any information
>> about addresses to communicate on your board.  This isn't the end of
>> the world, but if the system defaults aren't working (I assume
>> "ipmi_si", would try defaults, but I can't speak to that.  You'll have
>> to ask the "openipmi" project about that), it's possible your board
>> uses non-default device addresses that aren't advertised.
>>
>> In this case, you just need to get the information from the vendor on
>> the right addresses to use and set things up with those addresses
>> specifically.
>>
>> Al
>>
>> On Mon, 2019-09-16 at 11:49 +0300, Amos Shapir wrote:
>> > Hi IPMI users,
>> >
>> > I'm trying to use the IPMI tools on Compulab's MintBox, running
>> > Ubuntu
>> > 16.04and their Fitlet2 board.  This board includes an Intel I211
>> > network
>> > controller, which is supposed to have NC-SI capabilities, but the
>> > IPMI
>> > tools cannot communicate with it.
>> >
>> > All tools seem to be running OK, but:
>> > - The *ipmi_si *kernel module doesn;t load, claiming "Unable to find
>> > any
>> > System Interface(s)"
>> > - Trying *ipmi-locate, *it states FAILED on all probed interfaces,
>> > and
>> > produces "wrong mapping type" error messages in the kernel's log
>> > (which may
>> > be caused by the missing kernel module)
>> > - *ipmiping* fails to get a response from any IP address (not
>> > surprising)
>> >
>> > In short, it seems the device just doesn't advertise itself.  Does
>> > anyone
>> > on the list have experience with using I210/I211 under Linux, and how
>> > it
>> > should be configured?
>> > (The ultimate goal here is to use it to control another device via
>> > PHY)
>> >
>> > Thanks much,
>>
>>
>
> --
>
> *Amos Shapir*
> *  Senior Developer*
> *  +972-54-4642719 <%2B972-58-7801771> I address@hidden
> <address@hidden>*
>
> *  www.halo-digital.com <http://www.halo-digital.com/>*
>
>


-- 

*Amos Shapir*
*  Senior Developer*
*  +972-54-4642719 <%2B972-58-7801771> I address@hidden
<address@hidden>*

*  www.halo-digital.com <http://www.halo-digital.com/>*