On some machines it's the same IP, and on some it's different, and it 
has to be configured separately from the OS.  The channel list is 
strange, but you may not have a LAN interface on that system.  A LAN 
interface is not required.

There are only 16 possible channels, and 0xe and 0xf are special, so if 
you list more than that, ipmitool seems to truncate the number to 16 
bits so you get the same thing over and over.  From what is displayed, 
you do not have a LAN interface.

-corey

Dieter Plaetinck wrote:
> On Wed, 01 Jul 2009 10:19:44 -0500
> Corey Minyard <miny...@acm.org> wrote:
>
>   
>> Can you do any IPMI operation over the lan, like a get device id?  It 
>> appears it's not even able to set up the IPMI v2 session.
>>
>> On many systems, you cannot connect from the system itself, you have
>> to connect from another machine.
>>
>> -corey
>>     
>
> Yes I'm connecting from another machine.
> And indeed, it seems like it cannot connect at all. (even though i can
> just ssh to the ip)
>
> IPMI_PASSWORD=foo ipmitool -I lanplus -H $ip -U $user
> -E chassis status
> Error: Unable to establish IPMI v2 / RMCP+ session
> Error sending Chassis Status command
>
> Dieter
>
>   
>> Dieter Plaetinck wrote:
>>     
>>> Hi list,
>>> I've got 2 new hp dl320 machines.
>>> The problem is I'm having a hard time setting up sol on them.
>>> According to the tech specs these boxen support ilo 2 / ipmi v2 so
>>> it should be possible.
>>> In the firmware, we configured ip's for the ilo cards and
>>> setup an account.
>>> I can ssh $u...@$ip just fine (though with this method you cannot
>>> get a login console for the host system), however:
>>> IPMI_PASSWORD=$pass ipmitool -I lanplus -H $ip -U $user -E sol
>>> activate gives:
>>> Error: Unable to establish IPMI v2 / RMCP+ session
>>> Error: No response activating SOL payload
>>> I'm not sure, but it looks like the problem (or a related one) is
>>> that there are no "lan channels" (see below)
>>>
>>> I tried:
>>> ipmitool mc reset cold
>>> ipmitool mc reset warm
>>>
>>> but this did not seem to do anything
>>>
>>> This command shows that apparently all channels are not lan
>>> channels. # for i in `seq 0 1000`; do ipmitool lan print $i 2>&1 |
>>> grep -i 'invalid' | grep -i 'not a lan channel'; done 
>>> #
>>>
>>>
>>> Here are the channels that are not "reserved":
>>>
>>> een:~# for i in `seq 0 1000`; do res="`ipmitool channel info $i |
>>> grep 'Type' | grep -v reserved`"; [ -n "$res" ] && echo -e "Chan
>>> $i\n$res"; done
>>>
>>> Chan 7 Channel Medium Type   : Unknown (0x60)
>>>   Channel Protocol Type : KCS
>>> Chan 14
>>>   Channel Medium Type   : System Interface
>>>   Channel Protocol Type : KCS
>>> Chan 15
>>>   Channel Medium Type   : System Interface
>>>   Channel Protocol Type : KCS
>>> Chan 263
>>>   Channel Medium Type   : Unknown (0x60)
>>>   Channel Protocol Type : KCS
>>> Chan 270
>>>   Channel Medium Type   : System Interface
>>>   Channel Protocol Type : KCS
>>> Chan 271
>>>   Channel Medium Type   : System Interface
>>>   Channel Protocol Type : KCS
>>> Chan 519
>>>   Channel Medium Type   : Unknown (0x60)
>>>   Channel Protocol Type : KCS
>>> Chan 526
>>>   Channel Medium Type   : System Interface
>>>   Channel Protocol Type : KCS
>>> Chan 527
>>>   Channel Medium Type   : System Interface
>>>   Channel Protocol Type : KCS
>>> Chan 775
>>>   Channel Medium Type   : Unknown (0x60)
>>>   Channel Protocol Type : KCS
>>> Chan 782
>>>   Channel Medium Type   : System Interface
>>>   Channel Protocol Type : KCS
>>> Chan 783
>>>   Channel Medium Type   : System Interface
>>>   Channel Protocol Type : KCS
>>>
>>>
>>> The upper limit of 1000 is something I made up.  I'm suprised it can
>>> even go that far.  According to most tutorials channel 1 should be
>>> the lan (SOL) channel on most systems.
>>>
>>> een:~# lsmod | grep ipmi
>>> ipmi_devintf           13200  0 
>>> ipmi_si                43756  0 
>>> ipmi_msghandler        38520  2 ipmi_devintf,ipmi_si
>>>
>>>
>>>
>>> Thanks,
>>> Dieter
>>>
>>> ------------------------------------------------------------------------------
>>> _______________________________________________
>>> Ipmitool-devel mailing list
>>> Ipmitool-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/ipmitool-devel
>>>
>>>   
>>>       
>
>   


------------------------------------------------------------------------------
_______________________________________________
Ipmitool-devel mailing list
Ipmitool-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ipmitool-devel

Reply via email to