freeipmi-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Freeipmi-devel] Re: [Freeipmi-users] Tyan Thunder S2882 with m3289


From: Anand Babu
Subject: Re: [Freeipmi-devel] Re: [Freeipmi-users] Tyan Thunder S2882 with m3289 bmc module
Date: Thu, 20 Jan 2005 16:07:22 -0800
User-agent: Gnus/5.1007 (Gnus v5.10.7) Emacs/21.3 (gnu/linux)

,----[ Albert Chu <address@hidden> ]
| Whoah!! I see the problem now.
| 
| send_packet (43 bytes)
| 06 00 ff 07 00 00 00 00 00 d3 34 9a 65 1d 20 18
| c8 81 08 3a 00 04 99 43 85 50 c1 1e 9e 0f b6 36
| f4 09 9d 1c 53 47 d4 7d 86 42 a7
| ipmi message header (32 bytes)
| 06 00 ff 07 00 00 00 00 00 00 00 00 00 12 81 1c
| 63 20 08 3a 00 00 d3 34 9a 65 01 00 00 00 04 93
| 
| In every ipmi packet, the session id (in the above "d3 34 9a 65") is
| being sent with the packet, but its not being returned (its all
| zeroes).
| 
| I bet ipmipower is ignoring every packet being returned because the
| session id is incorrect.  It naturally assumes if the session id is
| wrong, the packet has been corrupted.  Ipmitool on the other hand is
| not checking for a correct session id, which is why it accepts every
| packet.
| 
| Bala, AB.  I know you have been working with the Tyan folks.  Can
| you report this issue to them?
| 
| I will think about how best to solve this problem.  On the one hand,
| if the remote BMC is not returning a session id, that is a bug on
| the BMCs part.  However, I do want to try and make ipmipower as
| portable as possible.
`----
I am wondering how it worked with our S288x boards here. Perhaps we
were using a different firmware. Bala is preparing a system with the
exact setup to reproduce this bug. We will work with Tyan to get it
fixed. 

-- 
Anand Babu
Free as in Freedom <www.gnu.org>




reply via email to

[Prev in Thread] Current Thread [Next in Thread]