There are probably three different questions here and these "pile-on" questions seemingly never end well (for me); I just end up getting confused.
Shot-gun answer follows...
First, this assumes everybody here is running Xserve. If you're not, you don't have a LOM, and if you don't have a LOM, then the IPMI tools aren't going to work for you.
Next, you [must configure your LOM|http://support.apple.com/kb/HT2773].
Next, this assumes you have a unique IP address for your host and a separate and unique address for the LOM. This is part of the configuration, but I've seen duplicate IP addresses used and all sorts of wacky IP network configurations attempted.
Fully configured and without added network interface controllers (NICs), an Xserve can require four and potentially more IP addresses. One IP address for each the host NICs that are in use, and one IP address for each NIC that the LOM is configured to share.
Next, this assumes you have the current firmware loaded on the Xserve. Some of the older firmware versions of the Xserve firmware could sometimes get a little weird, though the weird seems to have been largely purged with the firmware that's been available for the last year or so.
Next, this assumes you are not using link aggregation with your Xserve box, or (if you are) that you have the NIC that is being shared by the LOM outside of the link aggregation set. The LOM is not compatible with a NIC configured for link aggregation.
This also now assumes you have a network connection to the (unique) LOM.
If you're connecting to the LOM by issuing the IPMI command locally and directly on the Xserve system, then (depending on what you're up to) you can get to use the local path or the 127.0.0.1 address. (Without seeing the commands used and errors received, I can only guess.) Where if you're connecting remotely, you use the LOM IP address. The host system IP address is not used here.
Now if the LOM has gone weird, the first troubleshooting stop is usually a shutdown, followed by unplugging the power supply (or both supplies) for around thirty seconds or so; this forces the LOM to perform a full reset.
Here's an example quiery from a handy Xserve box:
$ ipmitool chassis status
System Power : on
Power Overload : false
Power Interlock : inactive
Main Power Fault : false
Power Control Fault : false
Power Restore Policy : previous
Last Power Event : ac-failed
Chassis Intrusion : inactive
Front-Panel Lockout : inactive
Drive Fault : false
Cooling/Fan Fault : false
Front Panel Light : off
$
And Steve I, consider using the email link; you can monitor threads and individual users with the email setting. You'll get notified when somebody responds. Piling onto a thread (and with no added details) just tends to add confusion to the discussions. (No offense is intended.)
