freeipmi-users
[Top][All Lists]
Advanced

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

Re: [Freeipmi-users] ipmiconsole BMC Implementation with x38ml


From: Al Chu
Subject: Re: [Freeipmi-users] ipmiconsole BMC Implementation with x38ml
Date: Tue, 23 Sep 2008 10:22:39 -0700

Hey Kimitoshi,

It does seem we got a little bit farther.

(1) - the remote motherboard is reporting bad values, and (3) indicates
that the "solpayloadsize" workaround does indeed get around that
problem.

(2) and (4) - indicate the intel20 workaround is something that should
not be used on this motherboard.

(5) - indicates we definitely need the authcap workaround for this
motherboard.

So lets concentrate on (3), since it got the furthest.

A) Could you also throw in the "solport" workaround.  The motherboard is
asking ipmiconsole to try connecting to another port.  On atleast one
other motherboard, we found out that the new port was a lie.  So the
"solport" workaround will tell ipmiconsole to ignore that new port and
connect to the default one.

B) No motherboard I've ever seen has used the "connect to another port"
option in IPMI.  So this path in the ipmiconsole code has never been
tested, and there may be bugs.  In fact, I think I may have found a bug.
Could you also give this tar.gz a try?

http://ftp.zresearch.com/pub/freeipmi/qa-
release/freeipmi-0.6.9.beta0.tar.gz

If both the old and new tar.gz fail, could you send me the --debug of
both?

Thanks,
Al

On Tue, 2008-09-23 at 15:12 +0900, ktaka wrote:
> Hi Al,
> 
> Thanks for the suggestion.
> Unfortunately, no luck so far.
> 
> > Could you try the "solpayloadsize" workaround as well?  For some reason
> > that motherboard is reporting bad payload sizes.  If this works, can you
> > please send me more detailed specs on that motherboard?  I'll add it
> > into the list of motherboards in the manpages/docs.
> >
> > If it stills fails to work with that workaround and the "authcap"
> > workaround, you may want to try the "intel20" workaround as well and see
> > if that helps.
> 
> x60:~# ipmipower -W authcap -u ktaka -h 192.168.20.116 -s
> 192.168.20.116: on
> 
> x60:~# ipmiconsole -V
> ipmiconsole 0.6.7
> 
> (1) ipmiconsole -W authcap -u rt -p rt  -h 192.168.20.116
> ipmiconsole_submit_block: BMC Implementation
> 
> (2) ipmiconsole -W authcap,intel20 -u rt -p rt  -h 192.168.20.116
> [error received]: password invalid
> 
> (3) ipmiconsole -W authcap,solpayloadsize -u rt -p rt  -h 192.168.20.116
> 
> (Never returns to the shell before hitting ^c.)
> 
> (4) ipmiconsole -W authcap,solpayloadsize,intel20  -u rt -p rt  -h
> 192.168.20.116
> [error received]: password invalid
> 
> 
> (5)
> ipmiconsole -u rt -p rt  -h 192.168.20.116
> [error received]: username invalid
> 
> ipmiconsole -W solpayloadsize -u rt -p rt  -h 192.168.20.116
> [error received]: username invalid
> 
> ipmiconsole -W intel20 -u rt -p rt  -h 192.168.20.116
> [error received]: username invalid
> 
> ipmiconsole -W intel20,solpayloadsize -u rt -p rt  -h 192.168.20.116
> [error received]: username invalid
> 
> 
> The followings are the error messages seen in the debug output.
> 
> (1) With authcap workaroud only, I see the following message in the
> debug output.
> 
> (ipmiconsole_checks.c, ipmiconsole_check_outbound_sequence_number, 254):
> hostname=192.168.20.116; protocol_state=0x5: session sequence number
> check failed; p = 9; session_sequence_number = 0;
> highest_received_sequence_number = 0
> 
> (ipmiconsole_processing.c, _check_payload_sizes_legitimate, 2080):
> hostname=192.168.20.116; protocol_state=0x8: payload sizes invalid:
> max_inbound_payload_size=1024 max_outbound_payload_size=1024
> 
> (2) With authcap,intel20, I see the following message.
> 
> (ipmiconsole_checks.c,
> ipmiconsole_check_rakp_2_key_exchange_authentication_code, 805):
> hostname=192.168.20.116; protocol_state=0x3: rakp 2 key exchanged
> authentication code check failed; p = 5
> 
> (3) With authcap,solpayloadsize, I see the following message repeatedly,
>    and the loop seems infinite.
> 
> (ipmiconsole_checks.c, ipmiconsole_check_outbound_sequence_number, 254):
> hostname=192.168.20.116; protocol_state=0x5: session sequence number
> check failed; p = 9; session_sequence_number = 0;
> highest_received_sequence_number = 0
> (ipmiconsole_processing.c,
> _process_protocol_state_activate_payload_sent, 2958):
> hostname=192.168.20.116; protocol_state=0x8: trying new port: 6F02
> 
> (4) With authcap,solpayloadsize,intel20, I see the following message in
> the debug output.
> 
> (ipmiconsole_checks.c,
> ipmiconsole_check_rakp_2_key_exchange_authentication_code, 805):
> hostname=192.168.20.116; protocol_state=0x3: rakp 2 key exchanged
> authentication code check failed; p = 5
> 
> (5) With any conbination of solpayloadsize,intel20, without authcap,
> results in "[error received]: username invalid".
> No significant error message in the debug output.
> 
> Do you think new workaroud is needed ?
> 
-- 
Albert Chu
address@hidden
925-422-5311
Computer Scientist
High Performance Systems Division
Lawrence Livermore National Laboratory





reply via email to

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