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

freeipmi-devel
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Freeipmi-devel] Re: [Freeipmi-users] Tyan Thunder S2882 with m3289 bmc

From:	Joshua Williams
Subject:	[Freeipmi-devel] Re: [Freeipmi-users] Tyan Thunder S2882 with m3289 bmc module
Date:	Thu, 20 Jan 2005 14:54:24 -0600
User-agent:	Mutt/1.4.1i
I'm not sure how long I will have this hardware but if I have it when
the fix is complete, I'd be more than willing to test it out.

ipmitool will also fail to work unless I do provide a username:

address@hidden software]# ipmitool -I lan -H 10.0.65.3 chassis power status
Failed to set session privilege level to ADMINISTRATOR
Error: Unable to establish LAN session
error in Chassis Status Command

address@hidden software]# ipmitool -I lan -H 10.0.65.3 -U Administrator chassis 
power status
Chassis Power is on

Just in case the former is of help to you, the -v -v -v output is as
follows:

IPMI LAN host 10.0.65.3 port 623
Sending IPMI/RMCP presence ping packet
send_packet (12 bytes)
 06 00 ff 06 be 11 00 00 80 00 00 00
Received IPMI/RMCP response packet: 
  IPMI Supported
  ASF Version 1.0
  RMCP Version 1.0
  RMCP Sequence 255
  IANA Enterprise 6653

>> IPMI Request Session Header
>>   Authtype   : NONE
>>   Sequence   : 0x00000000
>>   Session ID : 0x00000000
>> IPMI Request Message Header
>>   Rs Addr    : 20
>>   NetFn      : 06
>>   Rs LUN     : 0
>>   Rq Addr    : 81
>>   Rq Seq     : 00
>>   Rq Lun     : 0
>>   Command    : 38
send_packet (23 bytes)
 06 00 ff 07 00 00 00 00 00 00 00 00 00 09 20 18
 c8 81 00 38 0e 04 35
ipmi message header (30 bytes)
 06 00 ff 07 00 00 00 00 00 00 00 00 00 10 81 1c
 63 20 00 38 00 02 15 07 00 00 00 00 00 8a
<< IPMI Response Session Header
<<   Authtype   : NONE
<<   Sequence   : 0x00000000
<<   Session ID : 0x00000000
<< IPMI Response Message Header
<<   Rq Addr    : 81
<<   NetFn      : 07
<<   Rq LUN     : 0
<<   Rs Addr    : 20
<<   Rq Seq     : 00
<<   Rs Lun     : 0
<<   Command    : 38
<<   Compl Code : 0x00
IPMI Request Match found
get_auth_capabilities (8 bytes)
 02 15 07 00 00 00 00 00
Channel 02 Authentication Capabilities:
  Privilege Level : ADMINISTRATOR
  Auth Types      : NONE MD5 PASSWORD 
  Per-msg auth    : enabled
  User level auth : enabled
  Non-null users  : enabled
  Null users      : enabled
  Anonymous login : enabled

Proceeding with AuthType NONE
>> IPMI Request Session Header
>>   Authtype   : NONE
>>   Sequence   : 0x00000000
>>   Session ID : 0x00000000
>> IPMI Request Message Header
>>   Rs Addr    : 20
>>   NetFn      : 06
>>   Rs LUN     : 0
>>   Rq Addr    : 81
>>   Rq Seq     : 01
>>   Rq Lun     : 0
>>   Command    : 39
send_packet (38 bytes)
 06 00 ff 07 00 00 00 00 00 00 00 00 00 18 20 18
 c8 81 04 39 00 00 00 00 00 00 00 00 00 00 00 00
 00 00 00 00 00 42
ipmi message header (42 bytes)
 06 00 ff 07 00 00 00 00 00 00 00 00 00 1c 81 1c
 63 20 04 39 00 fe 1d 07 07 a7 61 b1 15 e1 5b 17
 7a 7d 22 9c 16 ed 33 66 7c 8c
<< IPMI Response Session Header
<<   Authtype   : NONE
<<   Sequence   : 0x00000000
<<   Session ID : 0x00000000
<< IPMI Response Message Header
<<   Rq Addr    : 81
<<   NetFn      : 07
<<   Rq LUN     : 0
<<   Rs Addr    : 20
<<   Rq Seq     : 01
<<   Rs Lun     : 0
<<   Command    : 39
<<   Compl Code : 0x00
IPMI Request Match found
get_session_challenge (20 bytes)
 fe 1d 07 07 a7 61 b1 15 e1 5b 17 7a 7d 22 9c 16
 ed 33 66 7c
Opening Session
  Session ID      : 07071dfe
  Challenge       : a761b115e15b177a7d229c16ed33667c
  Privilege Level : ADMINISTRATOR
  Auth Type       : NONE
>> IPMI Request Session Header
>>   Authtype   : NONE
>>   Sequence   : 0x00000000
>>   Session ID : 0x07071dfe
>> IPMI Request Message Header
>>   Rs Addr    : 20
>>   NetFn      : 06
>>   Rs LUN     : 0
>>   Rq Addr    : 81
>>   Rq Seq     : 02
>>   Rq Lun     : 0
>>   Command    : 3a
send_packet (43 bytes)
 06 00 ff 07 00 00 00 00 00 fe 1d 07 07 1d 20 18
 c8 81 08 3a 00 04 a7 61 b1 15 e1 5b 17 7a 7d 22
 9c 16 ed 33 66 7c 69 59 01 6c 1c
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 fe 1d 07 07 01 00 00 00 04 70
<< IPMI Response Session Header
<<   Authtype   : NONE
<<   Sequence   : 0x00000000
<<   Session ID : 0x00000000
<< IPMI Response Message Header
<<   Rq Addr    : 81
<<   NetFn      : 07
<<   Rq LUN     : 0
<<   Rs Addr    : 20
<<   Rq Seq     : 02
<<   Rs Lun     : 0
<<   Command    : 3a
<<   Compl Code : 0x00
IPMI Request Match found
activate_session (10 bytes)
 00 fe 1d 07 07 01 00 00 00 04

Session Activated
  Auth Type       : NONE
  Max Priv Level  : ADMINISTRATOR
  Session ID      : 07071dfe
  Inbound Seq     : 00000001

>> IPMI Request Session Header
>>   Authtype   : NONE
>>   Sequence   : 0x00000001
>>   Session ID : 0x07071dfe
>> IPMI Request Message Header
>>   Rs Addr    : 20
>>   NetFn      : 06
>>   Rs LUN     : 0
>>   Rq Addr    : 81
>>   Rq Seq     : 03
>>   Rq Lun     : 0
>>   Command    : 3b
send_packet (22 bytes)
 06 00 ff 07 00 01 00 00 00 fe 1d 07 07 08 20 18
 c8 81 0c 3b 04 34
ipmi message header (23 bytes)
 06 00 ff 07 00 00 00 00 00 00 00 00 00 09 81 1c
 63 20 0c 3b 81 04 14
<< IPMI Response Session Header
<<   Authtype   : NONE
<<   Sequence   : 0x00000000
<<   Session ID : 0x00000000
<< IPMI Response Message Header
<<   Rq Addr    : 81
<<   NetFn      : 07
<<   Rq LUN     : 0
<<   Rs Addr    : 20
<<   Rq Seq     : 03
<<   Rs Lun     : 0
<<   Command    : 3b
<<   Compl Code : 0x81
IPMI Request Match found
set_session_privlvl (1 bytes)
 04
Failed to set session privilege level to ADMINISTRATOR

Error: Unable to establish LAN session
error in Chassis Status Command

- Josh

On Thu, Jan 20, 2005 at 11:26:50AM -0800, Albert Chu wrote:
> Hi Josh,
> 
> Thanks.  It seems ipmitool does something strangely subtle.  Even with
> an authentication type of "none", they actually send the username to the
> remote machine.  
> 
> I looked through the IPMI specification a bit, and although this doesn't
> make any logical sense to me, it does seem the IPMI specification will
> allow this behavior.  When I get some time, I'll try to fix ipmipower
> up.  Would you mind checking out the newer version I release?
> 
> Al
> 
> --
> Albert Chu
> address@hidden
> Lawrence Livermore National Laboratory
> 
> ----- Original Message -----
> From: Joshua Williams <address@hidden>
> Date: Thursday, January 20, 2005 11:03 am
> Subject: Re: [Freeipmi-users] Tyan Thunder S2882 with m3289 bmc module
> 

> Date: Thu, 20 Jan 2005 13:03:17 -0600
> From: Joshua Williams <address@hidden>
> Subject: Re: [Freeipmi-users] Tyan Thunder S2882 with m3289 bmc module
> To: Albert Chu <address@hidden>
> Cc: address@hidden
> 
> Certainly, here it is:
> 
> IPMI LAN host 10.0.65.3 port 623
> Sending IPMI/RMCP presence ping packet
> send_packet (12 bytes)
>  06 00 ff 06 be 11 00 00 80 00 00 00
> Received IPMI/RMCP response packet: 
>   IPMI Supported
>   ASF Version 1.0
>   RMCP Version 1.0
>   RMCP Sequence 255
>   IANA Enterprise 6653
> 
> >> IPMI Request Session Header
> >>   Authtype   : NONE
> >>   Sequence   : 0x00000000
> >>   Session ID : 0x00000000
> >> IPMI Request Message Header
> >>   Rs Addr    : 20
> >>   NetFn      : 06
> >>   Rs LUN     : 0
> >>   Rq Addr    : 81
> >>   Rq Seq     : 00
> >>   Rq Lun     : 0
> >>   Command    : 38
> send_packet (23 bytes)
>  06 00 ff 07 00 00 00 00 00 00 00 00 00 09 20 18
>  c8 81 00 38 0e 04 35
> ipmi message header (30 bytes)
>  06 00 ff 07 00 00 00 00 00 00 00 00 00 10 81 1c
>  63 20 00 38 00 02 15 07 00 00 00 00 00 8a
> << IPMI Response Session Header
> <<   Authtype   : NONE
> <<   Sequence   : 0x00000000
> <<   Session ID : 0x00000000
> << IPMI Response Message Header
> <<   Rq Addr    : 81
> <<   NetFn      : 07
> <<   Rq LUN     : 0
> <<   Rs Addr    : 20
> <<   Rq Seq     : 00
> <<   Rs Lun     : 0
> <<   Command    : 38
> <<   Compl Code : 0x00
> IPMI Request Match found
> get_auth_capabilities (8 bytes)
>  02 15 07 00 00 00 00 00
> Channel 02 Authentication Capabilities:
>   Privilege Level : ADMINISTRATOR
>   Auth Types      : NONE MD5 PASSWORD 
>   Per-msg auth    : enabled
>   User level auth : enabled
>   Non-null users  : enabled
>   Null users      : enabled
>   Anonymous login : enabled
> 
> Proceeding with AuthType NONE
> >> IPMI Request Session Header
> >>   Authtype   : NONE
> >>   Sequence   : 0x00000000
> >>   Session ID : 0x00000000
> >> IPMI Request Message Header
> >>   Rs Addr    : 20
> >>   NetFn      : 06
> >>   Rs LUN     : 0
> >>   Rq Addr    : 81
> >>   Rq Seq     : 01
> >>   Rq Lun     : 0
> >>   Command    : 39
> send_packet (38 bytes)
>  06 00 ff 07 00 00 00 00 00 00 00 00 00 18 20 18
>  c8 81 04 39 00 41 64 6d 69 6e 69 73 74 72 61 74
>  6f 72 00 00 00 e1
> ipmi message header (42 bytes)
>  06 00 ff 07 00 00 00 00 00 00 00 00 00 1c 81 1c
>  63 20 04 39 00 d3 34 9a 65 99 43 85 50 c1 1e 9e
>  0f b6 36 f4 09 9d 1c 53 47 24
> << IPMI Response Session Header
> <<   Authtype   : NONE
> <<   Sequence   : 0x00000000
> <<   Session ID : 0x00000000
> << IPMI Response Message Header
> <<   Rq Addr    : 81
> <<   NetFn      : 07
> <<   Rq LUN     : 0
> <<   Rs Addr    : 20
> <<   Rq Seq     : 01
> <<   Rs Lun     : 0
> <<   Command    : 39
> <<   Compl Code : 0x00
> IPMI Request Match found
> get_session_challenge (20 bytes)
>  d3 34 9a 65 99 43 85 50 c1 1e 9e 0f b6 36 f4 09
>  9d 1c 53 47
> Opening Session
>   Session ID      : 659a34d3
>   Challenge       : 99438550c11e9e0fb636f4099d1c5347
>   Privilege Level : ADMINISTRATOR
>   Auth Type       : NONE
> >> IPMI Request Session Header
> >>   Authtype   : NONE
> >>   Sequence   : 0x00000000
> >>   Session ID : 0x659a34d3
> >> IPMI Request Message Header
> >>   Rs Addr    : 20
> >>   NetFn      : 06
> >>   Rs LUN     : 0
> >>   Rq Addr    : 81
> >>   Rq Seq     : 02
> >>   Rq Lun     : 0
> >>   Command    : 3a
> 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
> << IPMI Response Session Header
> <<   Authtype   : NONE
> <<   Sequence   : 0x00000000
> <<   Session ID : 0x00000000
> << IPMI Response Message Header
> <<   Rq Addr    : 81
> <<   NetFn      : 07
> <<   Rq LUN     : 0
> <<   Rs Addr    : 20
> <<   Rq Seq     : 02
> <<   Rs Lun     : 0
> <<   Command    : 3a
> <<   Compl Code : 0x00
> IPMI Request Match found
> activate_session (10 bytes)
>  00 d3 34 9a 65 01 00 00 00 04
> 
> Session Activated
>   Auth Type       : NONE
>   Max Priv Level  : ADMINISTRATOR
>   Session ID      : 659a34d3
>   Inbound Seq     : 00000001
> 
> >> IPMI Request Session Header
> >>   Authtype   : NONE
> >>   Sequence   : 0x00000001
> >>   Session ID : 0x659a34d3
> >> IPMI Request Message Header
> >>   Rs Addr    : 20
> >>   NetFn      : 06
> >>   Rs LUN     : 0
> >>   Rq Addr    : 81
> >>   Rq Seq     : 03
> >>   Rq Lun     : 0
> >>   Command    : 3b
> send_packet (22 bytes)
>  06 00 ff 07 00 01 00 00 00 d3 34 9a 65 08 20 18
>  c8 81 0c 3b 04 34
> ipmi message header (23 bytes)
>  06 00 ff 07 00 00 00 00 00 00 00 00 00 09 81 1c
>  63 20 0c 3b 00 04 95
> << IPMI Response Session Header
> <<   Authtype   : NONE
> <<   Sequence   : 0x00000000
> <<   Session ID : 0x00000000
> << IPMI Response Message Header
> <<   Rq Addr    : 81
> <<   NetFn      : 07
> <<   Rq LUN     : 0
> <<   Rs Addr    : 20
> <<   Rq Seq     : 03
> <<   Rs Lun     : 0
> <<   Command    : 3b
> <<   Compl Code : 0x00
> IPMI Request Match found
> set_session_privlvl (1 bytes)
>  04
> Set Session Privilege Level to ADMINISTRATOR
> 
> >> IPMI Request Session Header
> >>   Authtype   : NONE
> >>   Sequence   : 0x00000002
> >>   Session ID : 0x659a34d3
> >> IPMI Request Message Header
> >>   Rs Addr    : 20
> >>   NetFn      : 00
> >>   Rs LUN     : 0
> >>   Rq Addr    : 81
> >>   Rq Seq     : 04
> >>   Rq Lun     : 0
> >>   Command    : 01
> send_packet (21 bytes)
>  06 00 ff 07 00 02 00 00 00 d3 34 9a 65 07 20 00
>  e0 81 10 01 6e
> ipmi message header (25 bytes)
>  06 00 ff 07 00 00 00 00 00 00 00 00 00 0b 81 04
>  7b 20 10 01 00 01 00 02 cc
> << IPMI Response Session Header
> <<   Authtype   : NONE
> <<   Sequence   : 0x00000000
> <<   Session ID : 0x00000000
> << IPMI Response Message Header
> <<   Rq Addr    : 81
> <<   NetFn      : 01
> <<   Rq LUN     : 0
> <<   Rs Addr    : 20
> <<   Rq Seq     : 04
> <<   Rs Lun     : 0
> <<   Command    : 01
> <<   Compl Code : 0x00
> IPMI Request Match found
> Chassis Power is on
> >> IPMI Request Session Header
> >>   Authtype   : NONE
> >>   Sequence   : 0x00000003
> >>   Session ID : 0x659a34d3
> >> IPMI Request Message Header
> >>   Rs Addr    : 20
> >>   NetFn      : 06
> >>   Rs LUN     : 0
> >>   Rq Addr    : 81
> >>   Rq Seq     : 05
> >>   Rq Lun     : 0
> >>   Command    : 3c
> send_packet (25 bytes)
>  06 00 ff 07 00 03 00 00 00 d3 34 9a 65 0b 20 18
>  c8 81 14 3c d3 34 9a 65 29
> ipmi message header (22 bytes)
>  06 00 ff 07 00 00 00 00 00 00 00 00 00 08 81 1c
>  63 20 14 3c 00 90
> << IPMI Response Session Header
> <<   Authtype   : NONE
> <<   Sequence   : 0x00000000
> <<   Session ID : 0x00000000
> << IPMI Response Message Header
> <<   Rq Addr    : 81
> <<   NetFn      : 07
> <<   Rq LUN     : 0
> <<   Rs Addr    : 20
> <<   Rq Seq     : 05
> <<   Rs Lun     : 0
> <<   Command    : 3c
> <<   Compl Code : 0x00
> IPMI Request Match found
> 
> Closed Session 659a34d3
> 
> - Josh
> 
> On Thu, Jan 20, 2005 at 10:55:10AM -0800, Albert Chu wrote:
> > Hey Josh,
> > 
> > Do you think you could you run ipmitool with "-v -v -v" at the command
> > line and send me the output?  Something is a little odd.  I'd like to
> > try and figure out what they're doing differently.  
> > 
> > Thanks,
> > Al
> > 
> > --
> > Albert Chu
> > address@hidden
> > Lawrence Livermore National Laboratory
> > 
> > ----- Original Message -----
> > From: Joshua Williams <address@hidden>
> > Date: Thursday, January 20, 2005 10:50 am
> > Subject: Re: [Freeipmi-users] Tyan Thunder S2882 with m3289 bmc module
> > 
> > > I get the same problem:
> > > 
> > > address@hidden software]# ipmipower --authtype none -s -h 10.0.65.3
> > > 10.0.65.3: timed out
> > > 
> > > - Josh
> > > 
> > > On Thu, Jan 20, 2005 at 10:44:17AM -0800, Albert Chu wrote:
> > > > Hi Josh,
> > > > 
> > > > A little investigation shows that when you pass a username with no
> > > > password to ipmitool, the default is to authenticate with the
> > > > authentication type "none".  Whereas, in ipmipower 0.1.3, I 
> > > default to 
> > > > a cleartext password, even if the password is NULL (i.e. i send 
> > > 16 null
> > > > bytes as the password).
> > > > 
> > > > How about trying the "--authtype none" option on ipmipower 0.1.3 
> > > without> a username/password at the prompt?
> > > > 
> > > > Al
> > > > 
> > > > --
> > > > Albert Chu
> > > > address@hidden
> > > > Lawrence Livermore National Laboratory
> > > > 
> > > > ----- Original Message -----
> > > > From: Joshua Williams <address@hidden>
> > > > Date: Thursday, January 20, 2005 10:22 am
> > > > Subject: Re: [Freeipmi-users] Tyan Thunder S2882 with m3289 bmc 
> > > module> 
> > > > > Al,
> > > > > 
> > > > > There is no username option in ipmipower 0.1.2:
> > > > > 
> > > > > address@hidden bin]# ./ipmipower --help
> > > > > Usage: ipmipower [OPTION...] [FILE...]
> > > > > power ON or OFF a remote IPMI compliant machine.
> > > > > 
> > > > >  -f, --off                  Power OFF the remote IPMI box
> > > > >  -h, --hostname=IPMI host   Hostname of remote IPMI box
> > > > >  -n, --on                   Power ON the remote IPMI box
> > > > >  -p, --password=Password    Password for remote IPMI box
> > > > >  -v, --verbose              Print verbose information
> > > > >  -?, --help                 Give this help list
> > > > >      --usage                Give a short usage message
> > > > >  -V, --version              Print program version
> > > > > 
> > > > > With ipmipower 0.1.3, if I write the following to the BMC via
> > > > > bmc-config --commit:
> > > > > 
> > > > > ...
> > > > > Section User3
> > > > >        Username                                     Administrator
> > > > >        Password                                     asdf
> > > > > ...
> > > > > Commit Section <User2> Key <Username> Value <Operator> FAILED
> > > > > Commit Section <User3> Key <Username> Value <Administrator> FAILED
> > > > > Commit Section <User4> Key <Username> Value <Callback> FAILED
> > > > > ...
> > > > > 
> > > > > The subsequent 'ipmipower -o' reveals that the password wasn't 
> > > set:> > 
> > > > > ...
> > > > > ection User3
> > > > >        Username                                     Administrator
> > > > >        Password                                     
> > > > > ...
> > > > > 
> > > > > So, apparently I can't set a password.  Using the '-u 
> > > Administrator'> > option and no -p option with 'ipmipower -s' 
> > > results in the same error
> > > > > condition... it times out.
> > > > > 
> > > > > Maybe I just got a flakey Tyan IPMI board?
> > > > > 
> > > > > - Josh
> > > > > 
> > > > > On Thu, Jan 20, 2005 at 09:01:16AM -0800, Albert Chu wrote:
> > > > > > Hi Joshua,
> > > > > > 
> > > > > > Do you think you could try using a username and password with 
> > > > > ipmipower?>   I'm thinking anonymous authentication does not 
> > > work 
> > > > > by default on your
> > > > > > BMC.
> > > > > > 
> > > > > > Thanks,
> > > > > > Al
> > > > > > 
> > > > > > --
> > > > > > Albert Chu
> > > > > > address@hidden
> > > > > > Lawrence Livermore National Laboratory
> > > > > > 
> > > > > > ----- Original Message -----
> > > > > > From: Joshua Williams <address@hidden>
> > > > > > Date: Thursday, January 20, 2005 8:47 am
> > > > > > Subject: Re: [Freeipmi-users] Tyan Thunder S2882 with m3289 
> > > bmc 
> > > > > module> 
> > > > > > > This morning before doing anything else, I downloaded ipmitool
> > > > > > > (ipmitool.sourceforge.net) and it appears to work:
> > > > > > > 
> > > > > > > address@hidden software]# ipmitool -I lan -H 10.0.65.3 -U 
> > > > > > > Administrator chassis power status
> > > > > > > Chassis Power is on
> > > > > > > address@hidden software]# ipmitool -I lan -H 10.0.65.3 -U 
> > > > > > > Administrator chassis power off
> > > > > > > Chassis Power Control: Down/Off
> > > > > > > 
> > > > > > > I downloaded and installed the libcdcipmi and ipmipower you 
> > > > > mention> > below, compiled them, and reran ipmipower but it 
> > > just 
> > > > > hangs:> > 
> > > > > > > address@hidden bin]# ./ipmipower -h 10.0.65.3 -f 
> > > > > > > Password: 
> > > > > > > 
> > > > > > > I'll use ipmitool from here on.  If there's anything else 
> > > you 
> > > > > want me
> > > > > > > to try for you on this hardware, let me know.  Thanks for 
> > > all 
> > > > > your 
> > > > > > > help!
> > > > > > > - Josh
> > > > > > > 
> > > > > > > On Wed, Jan 19, 2005 at 02:48:10PM -0800, Bala.A wrote:
> > > > > > > > Hi,
> > > > > > > > 
> > > > > > > > Here is very old and unmaintained version of ipmipower.  
> > > This 
> > > > > is for
> > > > > > > > testing purpose.
> > > > > > > > 
> > > > > > > > 1. Uninstall freeipmi completely
> > > > > > > > 
> > > > > > > > 2. Install libcdcipmi.  You can get it from
> > > > > > > > 
> > > > > > >
> > > > > > 
> > > > >
> > > > 
> > >
> > ftp://ftp.californiadigital.com/pub/freeipmi/download/misc/libcdcipmi-0.1.1.tar.gz
> > > > > > > > 
> > > > > > > > 3. Install ipmipower. You can get it from
> > > > > > > > 
> > > > > > >
> > > > > > 
> > > > >
> > > > 
> > >
> > ftp://ftp.californiadigital.com/pub/freeipmi/download/misc/ipmipower-0.1.2.tar.gz
> > > > > > > > 
> > > > > > > > Please try this and let me know.
> > > > > > > > 
> > > > > > > > Thanks,
> > > > > > > > 
> > > > > > > > Best Regards
> > > > > > > > Bala
> > > > > > > > 
> > > > > > > > 
> > > > > > > > 
> > > > > > > > > Tried both.  The on-board Intel Pro100 card was the 
> > > only 
> > > > > card 
> > > > > > > up and I
> > > > > > > > > used a cross-over cable to connect my laptop directly 
> > > to 
> > > > > the 
> > > > > > > machine.> > ipmiping and rmcpping worked fine over the 
> > > cross-
> > > > > over 
> > > > > > > but the ipmipower
> > > > > > > > > command exhibited the same behavior.
> > > > > > > > >
> > > > > > > > > - Josh
> > > > > > > > >
> > > > > > > > > On Wed, Jan 19, 2005 at 01:12:07PM -0800, Bala.A wrote:
> > > > > > > > >> Hi,
> > > > > > > > >>
> > > > > > > > >> Can you try ipmipower with the following conditions?
> > > > > > > > >>
> > > > > > > > >> 1. Bring up ONLY on-board Intel Pro100 card (IPMI).
> > > > > > > > >> 2. Try ipmipower with cross-over cable connected to 
> > > > > another 
> > > > > > > machine.> >>
> > > > > > > > >> Thanks,
> > > > > > > > >>
> > > > > > > > >> Best Regards
> > > > > > > > >> Bala
> > > > > > > > >>
> > > > > > > > >>
> > > > > > > > >> > On Wed, Jan 19, 2005 at 01:54:06PM -0600, Joshua 
> > > > > Williams 
> > > > > > > wrote:> >> >> On Wed, Jan 19, 2005 at 10:40:55AM -0800, 
> > > Bala.A 
> > > > > wrote:> > > >> >> > Hi
> > > > > > > > >> >> >
> > > > > > > > >> >> > > Sorry for the confusion on my end... This is an 
> > > > > S2882 
> > > > > > > and there
> > > > > > > > >> were
> > > > > > > > >> >> > > actually four ethernet cards in the system.  
> > > Three 
> > > > > > > onboard and
> > > > > > > > >> one
> > > > > > > > >> >> > > PCI (another Intel - eth3).  I was trying to 
> > > give 
> > > > > the 
> > > > > > > BMC the
> > > > > > > > >> >> addresses
> > > > > > > > >> >> > > of the PCI card (eth3).  Once I figured things 
> > > out 
> > > > > I 
> > > > > > > gave it the
> > > > > > > > >> >> > > addresses of the onboard Intel card (eth2) and 
> > > > > started 
> > > > > > > using eth2
> > > > > > > > >> as
> > > > > > > > >> >> > > the primary network interface, ipmiping and 
> > > > > rmcpping 
> > > > > > > started to
> > > > > > > > >> >> work.
> > > > > > > > >> >> > > I can't get 'ipmipower --stat' to work though.  
> > > I 
> > > > > get 
> > > > > > > the simple
> > > > > > > > >> >> message:
> > > > > > > > >> >> > >
> > > > > > > > >> >> > >       # ipmipower --stat --hostname tomato
> > > > > > > > >> >> > >       tomato: timed out
> > > > > > > > >> >> >
> > > > > > > > >> >> > 1. Your on-board Intel Pro100 card should be up 
> > > and 
> > > > > > > running with
> > > > > > > > >> same
> > > > > > > > >> >> IP
> > > > > > > > >> >> > address of BMC in GNU/Linux. This is known 
> > > problem in 
> > > > > SMDC> > > >> firmware.
> > > > > > > > >> >>
> > > > > > > > >> >> This is true:
> > > > > > > > >> >>
> > > > > > > > >> >> address@hidden root]# ifconfig eth2
> > > > > > > > >> >> eth2      Link encap:Ethernet  HWaddr 
> > > 00:E0:81:2B:0A:AC> > > > > >> >>           inet addr:10.0.65.3  
> > > Bcast:10.0.65.255  
> > > > > > > Mask:255.255.255.0> >> >> ...
> > > > > > > > >> >>
> > > > > > > > >> >> address@hidden root]# bmc-config --checkout
> > > > > > > > >> >> ...
> > > > > > > > >> >> Section LAN_Conf
> > > > > > > > >> >>         ## Possible values:
> > > > > > > > >> >> Unspecified/Static/Use_DHCP/Use_BIOS/Use_Others
> > > > > > > > >> >>         Ip_Address_Source                           
> > > 
> > > > > Static> > > >> >>         ## Give valid IP Address
> > > > > > > > >> >>         Ip_Address                                  
> > > 
> > > > > 10.0.65.3> > > >> >>         ## Give valid MAC Address
> > > > > > > > >> >>         Mac_Address
> > > > > > > > >> 00:E0:81:2B:0A:AC
> > > > > > > > >> >>         ## Give valid Subnet mask
> > > > > > > > >> >>         Subnet_Mask                                 
> > > 
> > > > > > > 255.255.255.0> >> >>         ## Give valid IP Address
> > > > > > > > >> >>         Default_Gateway_Ip_Address                  
> > > 
> > > > > 10.0.65.1> > > >> >>         ## Give valid MAC Address
> > > > > > > > >> >>         Default_Gateway_Mac_Address
> > > > > > > > >> 00:00:00:00:00:00
> > > > > > > > >> >>         ## Give valid IP Address
> > > > > > > > >> >>         Backup_Gateway_Ip_Address                   
> > > 
> > > > > 10.0.65.1> > > >> >>         ## Give valid MAC Address
> > > > > > > > >> >>         Backup_Gateway_Mac_Address
> > > > > > > > >> 00:00:00:00:00:00
> > > > > > > > >> >> EndSection
> > > > > > > > >> >> ...
> > > > > > > > >> >>
> > > > > > > > >> >> > 2. Install GNU FreeIPMI in another machine (This 
> > > > > machine 
> > > > > > > should be
> > > > > > > > >> in
> > > > > > > > >> >> same
> > > > > > > > >> >> > network of IPMI machine by on-board Intel Pro100 
> > > card).> > > > > >> >>
> > > > > > > > >> >> Installed on:
> > > > > > > > >> >>
> > > > > > > > >> >> address@hidden root]# rpm -q freeipmi
> > > > > > > > >> >> freeipmi-0.1.3-0.20041102
> > > > > > > > >> >
> > > > > > > > >> > Sorry, this should have read:
> > > > > > > > >> >
> > > > > > > > >> > address@hidden root]# rpm -q freeipmi
> > > > > > > > >> > freeipmi-0.1.3-0.20041102
> > > > > > > > >> >
> > > > > > > > >> > - Josh
> > > > > > > > >> >
> > > > > > > > >> >> address@hidden root]# ifconfig
> > > > > > > > >> >> eth0      Link encap:Ethernet  HWaddr 
> > > 00:0F:1F:2A:FC:B4> > > > > >> >>           inet addr:10.0.3.81  
> > > Bcast:10.0.3.255  
> > > > > > > Mask:255.255.255.0> >> >> ...
> > > > > > > > >> >>
> > > > > > > > >> >> This is on a 10.0.3.x subnet while the IPMI card is 
> > > on 
> > > > > a 
> > > > > > > 10.0.65.x> >> >> subnet.  Should not matter though because 
> > > as 
> > > > > > > you'll see below,
> > > > > > > > >> ipmiping
> > > > > > > > >> >> works between the two.
> > > > > > > > >> >>
> > > > > > > > >> >> > 3. Test ICMP ping to IPMI machine.  This should 
> > > be 
> > > > > working.> > > >> >>
> > > > > > > > >> >> This works:
> > > > > > > > >> >>
> > > > > > > > >> >> address@hidden root]# ping 10.0.65.3
> > > > > > > > >> >> PING 10.0.65.3 (10.0.65.3) 56(84) bytes of data.
> > > > > > > > >> >> 64 bytes from 10.0.65.3: icmp_seq=0 ttl=62 
> > > time=0.447 ms
> > > > > > > > >> >> 64 bytes from 10.0.65.3: icmp_seq=1 ttl=62 
> > > time=0.386 ms
> > > > > > > > >> >> 64 bytes from 10.0.65.3: icmp_seq=2 ttl=62 
> > > time=0.373 ms
> > > > > > > > >> >> 64 bytes from 10.0.65.3: icmp_seq=3 ttl=62 
> > > time=0.382 ms
> > > > > > > > >> >> 64 bytes from 10.0.65.3: icmp_seq=4 ttl=62 
> > > time=0.365 ms
> > > > > > > > >> >>
> > > > > > > > >> >> --- 10.0.65.3 ping statistics ---
> > > > > > > > >> >> 5 packets transmitted, 5 received, 0% packet loss, 
> > > time 
> > > > > 3999ms> > > >> >> rtt min/avg/max/mdev = 
> > > 0.365/0.390/0.447/0.036 
> > > > > ms, pipe 2
> > > > > > > > >> >>
> > > > > > > > >> >> > 4. If ICMP ping is successful, test whether 
> > > > > ipmipower, 
> > > > > > > ipmiping and
> > > > > > > > >> >> > rcmpping are working or not.
> > > > > > > > >> >>
> > > > > > > > >> >> ipmiping works:
> > > > > > > > >> >>
> > > > > > > > >> >> address@hidden root]# ipmiping 10.0.65.3
> > > > > > > > >> >> ipmiping 10.0.65.3 (10.0.65.3)
> > > > > > > > >> >> response received from 10.0.65.3: rq_seq=0
> > > > > > > > >> >> response received from 10.0.65.3: rq_seq=1
> > > > > > > > >> >> response received from 10.0.65.3: rq_seq=2
> > > > > > > > >> >> response received from 10.0.65.3: rq_seq=3
> > > > > > > > >> >> response received from 10.0.65.3: rq_seq=4
> > > > > > > > >> >> response received from 10.0.65.3: rq_seq=5
> > > > > > > > >> >> --- ipmiping 10.0.65.3 statistics ---
> > > > > > > > >> >> 6 requests transmitted, 6 responses received in 
> > > time, 
> > > > > 0.0% 
> > > > > > > packet> >> loss
> > > > > > > > >> >>
> > > > > > > > >> >> As does rmcpping:
> > > > > > > > >> >>
> > > > > > > > >> >> address@hidden root]# rmcpping 10.0.65.3
> > > > > > > > >> >> rmcpping 10.0.65.3 (10.0.65.3)
> > > > > > > > >> >> pong received from 10.0.65.3: msg_tag=0
> > > > > > > > >> >> pong received from 10.0.65.3: msg_tag=1
> > > > > > > > >> >> pong received from 10.0.65.3: msg_tag=2
> > > > > > > > >> >> pong received from 10.0.65.3: msg_tag=3
> > > > > > > > >> >> pong received from 10.0.65.3: msg_tag=4
> > > > > > > > >> >> pong received from 10.0.65.3: msg_tag=5
> > > > > > > > >> >> --- rmcpping 10.0.65.3 statistics ---
> > > > > > > > >> >> 6 pings transmitted, 6 pongs received in time, 0.0% 
> > > > > packet 
> > > > > > > loss> >> >>
> > > > > > > > >> >> What fails is ipmipower:
> > > > > > > > >> >>
> > > > > > > > >> >> address@hidden root]# ipmipower --stat --hostnames 
> > > > > 10.0.65.3> > > >> >> 10.0.65.3: timed out
> > > > > > > > >> >>
> > > > > > > > >> >> This should not be an IPMI IP port issue (section 
> > > 13.1 
> > > > > of 
> > > > > > > freeipmi> >> >> documentation) because:
> > > > > > > > >> >>
> > > > > > > > >> >> address@hidden root]# tail -n 4 /etc/services
> > > > > > > > >> >> # BMC IPMI/RMCP services
> > > > > > > > >> >> rmcp    623/udp         # Aux Bus Shunt (Primary 
> > > RMCP 
> > > > > Port)> > > >> >> rmcps   664/udp         # Secure Aux Bus 
> > > > > (Secondary RMCP Port)
> > > > > > > > >> >>
> > > > > > > > >> >> I also have done the following:
> > > > > > > > >> >>
> > > > > > > > >> >> address@hidden root]# touch -f 
> > > /var/lib/freeipmi/ipckey.new> > > > > >> >> address@hidden root]# ls -
> > > -inode /var/lib/freeipmi/ipckey*
> > > > > > > > >> >> 3533355 /var/lib/freeipmi/ipckey  3533399
> > > > > > > > >> /var/lib/freeipmi/ipckey.new
> > > > > > > > >> >> address@hidden root]# mv -f /var/lib/freeipmi/ipckey.new
> > > > > > > > >> >> /var/lib/freeipmi/ipckey
> > > > > > > > >> >> address@hidden root]# ls --inode 
> > > /var/lib/freeipmi/ipckey> > > > > >> >> 3533399 
> > > /var/lib/freeipmi/ipckey> > > > > >> >>
> > > > > > > > >> >> Any suggestions?
> > > > > > > > >> >>
> > > > > > > > >> >> - Josh
> > > > > > > > >> >>
> > > > > > > > >> >> > Please try these steps and let me know.
> > > > > > > > >> >> >
> > > > > > > > >> >> >
> > > > > > > > >> >> >
> > > > > > > > >> >> > > The S2882 BIOS and the SMDC firware are the 
> > > latest 
> > > > > up 
> > > > > > > to date
> > > > > > > > >> >> versions.
> > > > > > > > >> >> > > The only sign of something amiss is the 
> > > following 
> > > > > bmc-
> > > > > > > config> >> output:
> > > > > > > > >> >> > >
> > > > > > > > >> >> > > ...
> > > > > > > > >> >> > > Section Serial_Channel
> > > > > > > > >> >> > > Error in checkout of key <Volatile_Access_Mode>
> > > > > > > > >> >> > > Error in checkout of key 
> > > > > <Volatile_Enable_User_Level_Auth>> > > >> >> > > Error in 
> > > checkout 
> > > > > of key 
> > > > > > > <Volatile_Enable_Per_Message_Auth>> >> >> > > Error in 
> > > checkout 
> > > > > of 
> > > > > > > key <Volatile_Enable_Pef_Alerting>
> > > > > > > > >> >> > > Error in checkout of key 
> > > > > > > <Volatile_Channel_Privilege_Limit>> >> >> > > Error in 
> > > checkout 
> > > > > of 
> > > > > > > key <Non_Volatile_Access_Mode>
> > > > > > > > >> >> > > Error in checkout of key 
> > > > > > > <Non_Volatile_Enable_User_Level_Auth>> >> >> > > Error in 
> > > > > checkout 
> > > > > > > of key <Non_Volatile_Enable_Per_Message_Auth>
> > > > > > > > >> >> > > Error in checkout of key 
> > > > > > > <Non_Volatile_Enable_Pef_Alerting>> >> >> > > Error in 
> > > checkout 
> > > > > of 
> > > > > > > key <Non_Volatile_Channel_Privilege_Limit>
> > > > > > > > >> >> > > EndSection
> > > > > > > > >> >> > > Section Serial_Conf
> > > > > > > > >> >> > > Error in checkout of key <Enable_Basic_Mode>
> > > > > > > > >> >> > > Error in checkout of key <Enable_PPP_Mode>
> > > > > > > > >> >> > > Error in checkout of key <Enable_Terminal_Mode>
> > > > > > > > >> >> > > Error in checkout of key <Connect_Mode>
> > > > > > > > >> >> > > Error in checkout of key <Page_Blackout_Interval>
> > > > > > > > >> >> > > Error in checkout of key <Call_Retry_Time>
> > > > > > > > >> >> > > Error in checkout of key <Enable_DTR_Hangup>
> > > > > > > > >> >> > > Error in checkout of key <Flow_Control>
> > > > > > > > >> >> > > Error in checkout of key <Bit_Rate>
> > > > > > > > >> >> > > EndSection
> > > > > > > > >> >> > > ...
> > > > > > > > >> >> >
> > > > > > > > >> >> > Tyan does not support Serial Channel in BMC.  You 
> > > can 
> > > > > > > safely ignore
> > > > > > > > >> >> this
> > > > > > > > >> >> > as warnings and they are not related with 
> > > > > > > ipmipower,ipmiping or
> > > > > > > > >> >> rmcpping.
> > > > > > > > >> >> >
> > > > > > > > >> >> >
> > > > > > > > >> >> >
> > > > > > > > >> >> > Thanks,
> > > > > > > > >> >> >
> > > > > > > > >> >> > Best Regards
> > > > > > > > >> >> > Bala
> > > > > > > > >> >> >
> > > > > > > > >> >> > --
> > > > > > > > >> >> > Free as in Freedom
> > > > > > > > >> >> > http://www.gnu.org/
> > > > > > > > >> >
> > > > > > > > >> >
> > > > > > > > >>
> > > > > > > > >>
> > > > > > > > >> --
> > > > > > > > >> Free as in Freedom
> > > > > > > > >> http://www.gnu.org/
> > > > > > > > >
> > > > > > > > 
> > > > > > > > 
> > > > > > > > -- 
> > > > > > > > Free as in Freedom
> > > > > > > > http://www.gnu.org/
> > > > > > > 
> > > > > > > 
> > > > > > > _______________________________________________
> > > > > > > Freeipmi-users mailing list
> > > > > > > address@hidden
> > > > > > > http://lists.gnu.org/mailman/listinfo/freeipmi-users
> > > > > > > 
> > > > > > 
> > > > > 
> > > > 
> > > 
> >
[Prev in Thread]
Current Thread
[Next in Thread]
[Freeipmi-devel] Re: [Freeipmi-users] Tyan Thunder S2882 with m3289 bmc module, Albert Chu, 2005/01/20
- [Freeipmi-devel] Re: [Freeipmi-users] Tyan Thunder S2882 with m3289 bmc module, Joshua Williams <=
- [Freeipmi-devel] Re: [Freeipmi-users] Tyan Thunder S2882 with m3289 bmc module, Albert Chu, 2005/01/20
  - Re: [Freeipmi-devel] Re: [Freeipmi-users] Tyan Thunder S2882 with m3289 bmc module, Anand Babu, 2005/01/20
Prev by Date: [Freeipmi-devel] releasing a freeipmi-0.1.4
Next by Date: Re: [Freeipmi-devel] releasing a freeipmi-0.1.4
Previous by thread: [Freeipmi-devel] Re: [Freeipmi-users] Tyan Thunder S2882 with m3289 bmc module
Next by thread: [Freeipmi-devel] Re: [Freeipmi-users] Tyan Thunder S2882 with m3289 bmc module
Index(es):
- Date
- Thread