Mike,
Thank you for the reply. Yes we do use Opteron (AMD) based board.
However, this is the second time we are using AMD board and it had no
problem with previous one (different IPMI card from Supermicro). I saw
your earlier thread that you are using AOC-SIMSO(+) and AOC-SIMLC(+). I
have them with H8DMU+ and H8DA3-2 motherboards. So you have to have one
designed with just IPMI and other one with regular network? I don't
think we can afford it. No extra ports :-(
________________________________
From: Mike Lovell [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 08, 2008 7:39 PM
To: Choi, Paul
Cc: ipmitool-devel@lists.sourceforge.net
Subject: Re: [Ipmitool-devel] IPMI Card Hanging
What utility are you using to set the IP address of the IPMI card? I
have found that the IPMI cards usually need a reboot after changing IP
information but that can be done by 'ipmitool bmc reset cold' or
'ipmicfg-linux.x86 -r' if you have a newer version of the Supermicro
configuration utility. Power cycling the box does essentially the same
thing. I would recommend trying one of those command, or something
similar, before power cycling the card/box. I think I have killed a few
cards by power cycling at just the wrong moment.
Also, what motherboard/cpu are you using? I had a bunch of Xeon based
boards that had no problem keeping up with the network. (my network has
a ton of broadcasts). But then I switched to an Opteron based board with
the same model IPMI card. The same IPMI in the new boards was freaking
out with all the broadcasts. I am assuming its TCP stack wasn't
processing the broadcasts quick enough. I eventually had to move the
IPMI to a different VLAN from the production network.
I don't know of a way to view the event message queue. I have seen the
error a few times when I tried to change LAN or SOL settings. I'm not
sure what caused it but my setting changes would still take effect. Even
changes made after the first error. So I don't really know what it
means.
>From my experience, it is often best to have the IPMI card be on a
different network/VLAN from the rest of the production traffic. If you
are using a board with shared LAN, this can be done by only using the
shared port for the IPMI and using the non-shared port for the operating
system. You can even disable the shared interface in the BIOS or by the
jumpers and the IPMI will still work. (or at least should)
Hopefully that provides some help.
Mike
Choi, Paul wrote:
Hi,
I am using one of the supermicro's IPMI card and I am having some
problem.
I am thinking this is problem with my network (too many arp message).
When I set the card with IP address, it won't work until I power recycle
or until actually power cord off the server and put it back on. I am
thinking network is flooded with arp message and IPMI card's interface
isn't fast enough (supermicro said 400Kbs). If I ping regular IP address
in a NIC, it take about 0.1 ms. IPMI card's IP address takes about 150
ms. Also, I am getting kernel message said "IPMI event message queue
full. Incoming message discarded". Is there way to discard all messages
but IPMI command on IPMI? Also, is there way to see what's in event
queue?
Thx
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Ipmitool-devel mailing list
Ipmitool-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ipmitool-devel
