4069 Views 13 Replies Latest reply: Sep 24, 2009 2:23 PM by Pope7
AFAIK you always need to use localhost/127.0.0.1 when using Server Monitor to connect to the machine it's running on.
You should test your 10.0.0.21 LOM address from a different machine on the network.
Even though LOM is supposed - even designed - to work remotely, it shouldn't prevent you from using the network address from the machine itself. I know that doesn't make a whole lot of sense, but it does seem to work that way.
Things have been busy - sorry about the delay in response. Over the weekend I played with the LOM (powering off for 30 seconds whenever I made a change).
From the local machine 127.0.0.1 works fine. (I'm not going to worry about 10.0.0.21 working on the local machine, since all I'm actually concerned in is getting LOM to work from other machines. (But I appreciate all the notes on where I'd have to start looking to get that working)
Now when I try to connect from a remote machine to LOM on 10.0.0.21 there is no response. The log gives "Failed to contact server". Seems like it has all taken a step backwards.
Also, ipmitool user list is now giving "Command failed with error 0xfffef9cc" and ipmitool lan print gives "Channel 14 is not a LAN channel."
I'll tinker with the settings this evening if someone has a good suggestion. Is LOM typically this difficult to establish?
Now when I try to connect from a remote machine to LOM on 10.0.0.21 there is no response
Where are you testing from? more specifically, what's the IP address of the machine that you're testing from?
This could just be an issue with routing - your machine needs to be able to route to 10.0.0.21, and the LOM needs to be able to route back to your machine.
Of course, if your machine is in the same subnet then routing shouldn't be an issue, in which case you could be looking at a port authentication or VLAN issue.
I'm sitting at 10.0.0.54, so there shouldn't be a problem there.
Shouldn't be a problem? Um, it's IP. Almost by definition, there are problems when IP is involved. Thanks for the chuckle, though.
Any managed switches or vLANs or routers in the network here?
The comment indicates the box was powered off for thirty seconds. Is that exactly what was done? Or was the box unplugged for thirty seconds? (Yes, I know, this question can be construed as pedantic, apologies for that, and yes, this requirement is discussed in [HT2773|http://support.apple.com/kb/HT2773], but this distinction is important here. But what was written can lead to exactly what is being seen here.)
Thanks for all the help with this.
(In the following, unplugged = ethernet, ac power, etc)
- I powered down and unplugged last, and the problems persisted
- I powered down, unplugged, booted up, issued ipmitool reset, and still no luck
- I powered down, unplugged, booted up, and used the Server Monitor LOM reset option and no luck there either.
Since LOM is amazingly convenient but not a strict necessity at the moment, I'm going to put it on my "when I have free time" list for the moment. But if you have more recommendations let me know.
Edit: And to answer a question from earlier - nothing fancy here. No vlans or odd router setups.
Message was edited by: Pope7
To ensure I still understand what you're trying here, you're working to connect via the IP address into the box that's with LOM, correct? Not via localhost, but via the published IP address, directly from that same Xserve box host?
If that's the case, that typically does not work. (If this is the case, then you're dealing with how IP and Ethernet work here; a host that's transmitting a packet is not listening to receive that packet, and the Mac OS X driver stack isn't AFAIK set up to "reflect" this traffic at a higher level. Yes, technically, a Ethernet station can listen for jamming. But that's typically the limit for listening while transmitting.)
If you're trying to connect from another host, that's supposed to work. This presuming that one or both of the NICs is connected and operating, and that the LOM is configured to be connected to one (or both) of the connected NICs, using unique addresses for each connected NIC.
All of which is pretty much what's in that previously-cited [HT2773 support article|http://support.apple.com/kb/HT2773]. Which then implies there's a hardware problem or a LOM configuration or a network problem with this Xserve box, presuming you're using a remote client trying to connect to the Xserve box.
I am trying to access LOM on the Xserve from my Laptop. I'm not sure why I'd ever want to connect from the Xserve to its own LOM, especially when I could just connect via local 127.0.0.1.
Both machines are behind the same point of the network. The server is 10.0.0.20 with a lom address of 10.0.0.21. And my laptop is 10.0.0.54.
Here are the problems I've had with HT2773...
1.) Server Assistant is for when setting up the machine.
2.) Server Monitor - I've repeatedly tried to setup LOM using this, but to no avail. When I try to connect from my laptop it always says ""Failed to connect to server" in either of the following scenarios...
Scenario 1: When given the right IP address but wrong username and password
Scenario 2: When given the wrong IP address and right username and password
So trouble shooting if it is a connection or a user problem is difficult.
3.) I tried using ipmitool, but now it is giving the two errors I listed previously...
"ipmitool lan print" gives the error: "Channel 14 is not LAN"
"ipmitool user list" gives the error: "Command failed with error 0xFFFEF9CC
These errors only appeared after I used ipmitool to create a new user and to assign the LOM ip address.
Message was edited by: Pope7
"ipmitool channel info 1" and "ipmitool channel info 2" give appropriate responses. I'm not sure why in the world it is looking at Channel 14 - or how it got set that way.
"ipmitool channel info 14" gives...
Channel Medium Type: System Interface
Channel Protocol Type: KCS
Session Support: session-less
Active Session Count: 0
Protocol Vendor ID: 7154
I've had no luck in getting it to switch to a different channel either.