Menu
▾
▴
ipmitool-devel
|
From: Olivier A. <oli...@te...> - 2006-09-04 20:50:50
|
Hi,
I'm new to ipmi, and i'm in trouble using it with lan interface.
here what i've do:
drennec:~# /usr/share/ipmitool/ipmi.init.basic
Setting up OpenIPMI driver...
FATAL: Module ipmi_kcs_drv not found.
drennec:~# /usr/share/ipmitool/bmclanconf -c 1
Setting channel authentication capabilities
Enabling channel 1
drennec:~# lsmod | grep ipmi
ipmi_devintf 8072 0
ipmi_si 32720 0
ipmi_msghandler 30272 2 ipmi_devintf,ipmi_si
drennec:~# dmesg
ipmi message handler version 39.0
IPMI System Interface driver.
ipmi_si: Trying SMBIOS-specified KCS state machine at I/O address 0xca8,
slave address 0x20, irq 0
ipmi: Found new BMC (man_id: 0x000878, prod_id: 0x0000, dev_id: 0x20)
IPMI KCS interface initialized
ipmi device interface
drennec:~# dpkg -l | grep ipmi
ii ipmitool 1.8.7-2 utility for
IPMI control with kernel driver
ii libopenipmi0 2.0.2-2 Intelligent
Platform Management Interface -
ii openipmi 2.0.2-2 Intelligent
Platform Management Interface (f
drennec:~# uname -a
Linux drennec 2.6.17-2-486 #1 Fri Aug 11 20:00:44 UTC 2006 i686 GNU/Linux
drennec:~# ipmitool channel info 1
Channel 0x1 info:
Channel Medium Type : 802.3 LAN
Channel Protocol Type : IPMB-1.0
Session Support : multi-session
Active Session Count : 0
Protocol Vendor ID : 7154
Volatile(active) Settings
Alerting : enabled
Per-message Auth : enabled
User Level Auth : enabled
Access Mode : always available
Non-Volatile Settings
Alerting : enabled
Per-message Auth : enabled
User Level Auth : enabled
Access Mode : always available
drennec:~# ipmitool -A NONE -I lan -H x.x.x.x session info active
Error: Unable to establish LAN session
ipmi_lan_send_cmd failed to open intf
Get Session Info command failed
Do I missed something ?
--
Olivier
|
|
From: Daniel T. <dt...@we...> - 2006-09-04 23:30:17
|
Olivier Archer wrote: > Hi, > I'm new to ipmi, and i'm in trouble using it with lan interface. > here what i've do: [cut] > drennec:~# ipmitool channel info 1 > Channel 0x1 info: > Channel Medium Type : 802.3 LAN > Channel Protocol Type : IPMB-1.0 > Session Support : multi-session > Active Session Count : 0 > Protocol Vendor ID : 7154 > Volatile(active) Settings > Alerting : enabled > Per-message Auth : enabled > User Level Auth : enabled > Access Mode : always available > Non-Volatile Settings > Alerting : enabled > Per-message Auth : enabled > User Level Auth : enabled > Access Mode : always available > > drennec:~# ipmitool -A NONE -I lan -H x.x.x.x session info active > Error: Unable to establish LAN session > ipmi_lan_send_cmd failed to open intf > Get Session Info command failed > > Do I missed something ? Hi, I have similar problem with a AOC-SIMSO device on a Supermicro motherboard.. But, did you set the IP address? You can check the IP, MAC & gateway with # ipmitool lan print Then see help for "ipmitool set". -- Daniel Toma |
|
From: Daniel T. <dt...@we...> - 2006-09-04 23:33:59
|
> Then see help for "ipmitool set". I mean .. "ipmitool lan set" |
|
From: Olivier A. <oli...@te...> - 2006-09-05 15:01:02
|
Daniel Toma wrote:
> Olivier Archer wrote:
>
>> Hi,
>> I'm new to ipmi, and i'm in trouble using it with lan interface.
>> here what i've do:
>>
> [cut]
>
>> drennec:~# ipmitool channel info 1
>> Channel 0x1 info:
>> Channel Medium Type : 802.3 LAN
>> Channel Protocol Type : IPMB-1.0
>> Session Support : multi-session
>> Active Session Count : 0
>> Protocol Vendor ID : 7154
>> Volatile(active) Settings
>> Alerting : enabled
>> Per-message Auth : enabled
>> User Level Auth : enabled
>> Access Mode : always available
>> Non-Volatile Settings
>> Alerting : enabled
>> Per-message Auth : enabled
>> User Level Auth : enabled
>> Access Mode : always available
>>
>> drennec:~# ipmitool -A NONE -I lan -H x.x.x.x session info active
>> Error: Unable to establish LAN session
>> ipmi_lan_send_cmd failed to open intf
>> Get Session Info command failed
>>
>> Do I missed something ?
>>
>
> Hi,
>
> I have similar problem with a AOC-SIMSO device on a Supermicro motherboard..
> But, did you set the IP address? You can check the IP, MAC & gateway with
>
> # ipmitool lan print
>
> Then see help for "ipmitool set".
>
>
Ok,
I didn't fix manualy the ip addr, since bmclanconf -c 1 gave me one
by dhcp. what is this ip @ ? Is it the same as the network main iface
(eth0)? And i've said bmclanconf to configure channel 1, but how to deal
choosing channel number ?
so i've always got "Unable to establish LAN session" error.
drennec:~# ipmitool lan print 1
Set in Progress : Set In Progress
Auth Type Support : NONE MD2 MD5 PASSWORD
Auth Type Enable : Callback : MD2 MD5
: User : MD2 MD5
: Operator : MD2 MD5
: Admin : MD2 MD5
: OEM : MD2 MD5
IP Address Source : Static Address
IP Address : x.y.z.40
Subnet Mask : 255.255.255.240
MAC Address : 00:30:48:56:5c:4c
SNMP Community String : public
IP Header : TTL=0x40 Flags=0x40 Precedence=0x00 TOS=0x10
Default Gateway IP : x.y.z.33
Default Gateway MAC : 00:a0:f9:09:96:28
Backup Gateway IP : 0.0.0.0
Backup Gateway MAC : 00:00:00:00:00:00
802.1q VLAN ID : Disabled
802.1q VLAN Priority : 0
Cipher Suite Priv Max : Not Available
|
|
From: Daniel T. <dt...@we...> - 2006-09-05 15:14:57
|
Olivier Archer wrote: > I didn't fix manualy the ip addr, since bmclanconf -c 1 gave me one > by dhcp. what is this ip @ ? Is it the same as the network main iface > (eth0)? And i've said bmclanconf to configure channel 1, but how to deal > choosing channel number ? > so i've always got "Unable to establish LAN session" error. I'm not sure, but in documentation for my device is written: "Please use an IP that is different from your system IP." ftp://ftp.supermicro.com/CDR-SIMIPMI_1.01_for_SIM_IPMI/Rev1.02_Beta/Manuals/Note-SIMSO.pdf -- Daniel Toma |
|
From: Olivier A. <oli...@te...> - 2006-09-05 16:28:39
|
Daniel Toma wrote: > Olivier Archer wrote: > >> I didn't fix manualy the ip addr, since bmclanconf -c 1 gave me one >> by dhcp. what is this ip @ ? Is it the same as the network main iface >> (eth0)? And i've said bmclanconf to configure channel 1, but how to deal >> choosing channel number ? >> so i've always got "Unable to establish LAN session" error. >> > > I'm not sure, but in documentation for my device is written: > "Please use an IP that is different from your system IP." > > ftp://ftp.supermicro.com/CDR-SIMIPMI_1.01_for_SIM_IPMI/Rev1.02_Beta/Manuals/Note-SIMSO.pdf > > [reply-to set to list] Ok, I've set another IP address, tryed one local and one public. Both are non pingable. Are they supposed to be ? do i have to add extra route ? The only documention I read is README and manpages . Tha not a lot. Is there other documentation/FAQ ? -- Olivier |
|
From: Steffen G. <ste...@ae...> - 2006-09-15 10:37:13
|
On Tue, Sep 05, 2006 at 06:28:31PM +0200, Olivier Archer wrote: > Daniel Toma wrote: > > Olivier Archer wrote: > > > >> I didn't fix manualy the ip addr, since bmclanconf -c 1 gave me one > >> by dhcp. what is this ip @ ? Is it the same as the network main iface > >> (eth0)? And i've said bmclanconf to configure channel 1, but how to deal > >> choosing channel number ? > >> so i've always got "Unable to establish LAN session" error. > >> > > > > I'm not sure, but in documentation for my device is written: > > "Please use an IP that is different from your system IP." > > > > ftp://ftp.supermicro.com/CDR-SIMIPMI_1.01_for_SIM_IPMI/Rev1.02_Beta/Manuals/Note-SIMSO.pdf > > > > > [reply-to set to list] > > Ok, I've set another IP address, tryed one local and one public. Both > are non pingable. Are they supposed to be ? do i have to add extra route ? > The only documention I read is README and manpages . Tha not a lot. Is > there other documentation/FAQ ? Strange ... I got both a SIMSO+ and a SIMSO to test, and while I was able to ping (and connect to) the SIMSO+, I couldn't get in touch with the SIMSO (no plus). I used (DOS based) ipnmac to set and verify the IP and MAC addresses. No way. I'll return the non-plus one... There's a small chance that it doesn't have a proper firmware, but the LED is active so I guess the Linux on the ARM is running. No way to check though. Steffen |
|
From: Daniel T. <dt...@we...> - 2006-09-15 10:57:27
|
Steffen Grunewald wrote: >> Ok, I've set another IP address, tryed one local and one public. Both >> are non pingable. Are they supposed to be ? do i have to add extra route ? >> The only documention I read is README and manpages . Tha not a lot. Is >> there other documentation/FAQ ? > > Strange ... I got both a SIMSO+ and a SIMSO to test, and while I was able to > ping (and connect to) the SIMSO+, I couldn't get in touch with the SIMSO > (no plus). I used (DOS based) ipnmac to set and verify the IP and MAC addresses. > No way. I'll return the non-plus one... There's a small chance that it doesn't > have a proper firmware, but the LED is active so I guess the Linux on the ARM > is running. No way to check though. > > Steffen None of the bios/firmware upgrades helps me so I sent the SIMSO back to Supermicro and I'm waiting for a SIMSO+ in place of it. Looks for me that they delivered an unfinished product.. -- Daniel Toma |
|
From: Duncan L. <dl...@gm...> - 2006-09-15 15:50:30
|
On 9/15/06, Steffen Grunewald <ste...@ae...> wrote: > > On Tue, Sep 05, 2006 at 06:28:31PM +0200, Olivier Archer wrote: > > Daniel Toma wrote: > > > Olivier Archer wrote: > > > > > >> I didn't fix manualy the ip addr, since bmclanconf -c 1 gave me > one > > >> by dhcp. what is this ip @ ? Is it the same as the network main iface > > >> (eth0)? And i've said bmclanconf to configure channel 1, but how to > deal > > >> choosing channel number ? > > >> so i've always got "Unable to establish LAN session" error. > > >> > > > > > > I'm not sure, but in documentation for my device is written: > > > "Please use an IP that is different from your system IP." > > > > > > > ftp://ftp.supermicro.com/CDR-SIMIPMI_1.01_for_SIM_IPMI/Rev1.02_Beta/Manuals/Note-SIMSO.pdf > > > > > > > > [reply-to set to list] > > > > Ok, I've set another IP address, tryed one local and one public. Both > > are non pingable. Are they supposed to be ? do i have to add extra route > ? > > The only documention I read is README and manpages . Tha not a lot. Is > > there other documentation/FAQ ? > > Strange ... I got both a SIMSO+ and a SIMSO to test, and while I was able > to > ping (and connect to) the SIMSO+, I couldn't get in touch with the SIMSO > (no plus). I used (DOS based) ipnmac to set and verify the IP and MAC > addresses. > No way. I'll return the non-plus one... There's a small chance that it > doesn't > have a proper firmware, but the LED is active so I guess the Linux on the > ARM > is running. No way to check though. It is sad when Linux is stuck in an embedded system with no way to break out or look in. At least penguins at the zoo can be observed. Free Tux! -duncan |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X