Intel Xserve Lights Out Management Config Question

When setting up my Intel Xserve I was confused and still am about the way LOM is set up.
Ethernet port 1 uses IP XXX.XXX.XXX.50 for web
Then LOM asked for another IP address on port 1 so I gave it XXX.XXX.XXX.51
How can one port have 2 different IP addresses?
Server monitor connects to XXX.XXX.XXX.51 and all of the other server tools connect to XXX.XXX.XXX.50
Is this correct?
I use port 2 for internal use. Should I use port 2 for LOM?

>Thank you and I did read it before. So what I doing is correct?
What you did is valid, yes. correct? maybe not.
Specifically, I'm concerned by the statement:
>Then LOM asked for another IP address on port 1 so I gave it XXX.XXX.XXX.51
I use port 2 for internal use. Should I use port 2 for LOM?
From your description it sounds like ethernet 1 is used for your public network. This means you've configured LOM in your public network, meaning (firewall aside) anyone can hit your LOM from outside the network, shutdown your machine etc., etc.
I would only ever configure LOM on an private/internal network. There should be no reason to manage LOM from the public network.

Similar Messages

New Intel Xserve Lights Out Management dies

Have a new Xserve with LOM. Problem is that after about 1/2 an hour of monitoring with the Server Monitor application from my desktop MacPro the Xserve stops responding via Server Monitor. The only way to get it to work again is to reboot the server. Not good. Anyone else seeing this behavior? Anyone have a fix or can someone from Apple confirm this is a known problem?
Thanks!

Ok, Having fought with this for the last 2 days, lack of solid documentation, etc, here's my results:
First set dns and reversedns (obviously)
EN0 set to 10.0.1.51
EN1 Disabled
ILO1 set to 10.0.1.52
ILO2 set to 0.0.0.0
This configuration worked, occasionally, but had numerous "Failed to contact server", and remote ipmitool was SLOW.
EN0 set to 10.0.1.51
EN1 Disabled
ILO1 set to 0.0.0.0
ILO2 set to 10.0.1.52
This configuration worked, even less than the first, and remote ipmitool acted slow, but returned nothing.
EN0 set to 10.0.1.51
EN1 set to 10.0.1.52
ILO1 set to 0.0.0.0
ILO2 set to 10.0.1.52
This configuration worked, occasionally, but had numerous "Failed to contact server", and remote ipmitool was SLOW.
EN0 set to 10.0.1.51
EN1 set to 0.0.0.0 (Static IP, and all fields cleared)
ILO1 set to 0.0.0.0
ILO2 set to 10.0.1.52
This configuration works, consistanly and remote ipmitool was very fast.
The command I was using to test ipmitool was:
$ ipmitool -H 10.0.1.52 -U USERNAME -P PASSWORD chassis status
In addition, I found that ANY changes to the IP for EN1 or ILO1/2 caused the ILO module to get lost, and require a reboot. (unplug method)
Thus, this is the method I found to get it working, after setting DNS and RDNS for the 2 IP addresses I was to use:
1) Unplug the power from the XServe for 10 seconds at least (others recommend 30, but I believe that as soon as all lights are off, that's sufficient)
2) In Network Preferences, set up Built-in Ethernet 1 as you'd like for whatever network access you will need.
3) In Network Preferences, enable (if off) Built-in Ethernet 2, and clear all fields. IP address will default to 0.0.0.0, Subnet Mask will default to 255.255.255.0, and all other fields will be blank.
4) In server admin, use "Configure local Machine" to default all values on Port 1 so that IP and gateway are 0.0.0.0 and subnet mask is 255.255.255.0, then switch to Port 2, configure the settings you want the ILO port to use. (do not use the same IP as EN0 obviously).
5) Set the username and password for the ILO user. (I had NO problems whatsoever with usernames less than 8 characters contrary to reports to this extent) You MUST enter a password again, regardless if it's been set in the past, then apply the settings (authenticate if necessary).
6) Shutdown, and disconnect the power once more to shutdown ILO.
7) Boot, make sure the XServe can login to itself at localhost with the ILO login name and password.
8) On another system on the same subnet, run:
$ ipmitool -H IPADDRESS -U USERNAME -P PASSWORD chassis status
(replacing IPADDRESS with the ILO's IP address and USERNAME and PASSWORD with the ones you set in step 5)
9) if you see something like:
System Power : on
Power Overload : false
Power Interlock : inactive
Main Power Fault : false
Power Control Fault : false
Power Restore Policy : always-on
Last Power Event : ac-failed
Chassis Intrusion : inactive
Front-Panel Lockout : inactive
Drive Fault : false
Cooling/Fan Fault : false
you should be fine, and Server Monitor on the remote system should connect fine.
The conclusion is that the key to getting this running is in enabling EN1, yet not giving it any TCP configuration.
Hope this helps someone out there...

Intel Lights Out Management Config

Ok,
there are some pretty intelligent folks here, so I need to find someone who not only knows how to make LOM work, but who also know how to explain it to someone who is not a unix guru or in other words, simple step by step instructions.
I've just installed the new xeon intel xserve. Remote admin works fine. LOM is supposed to be on a different IP. Apple could not have been any more vague on their instruction than they are with setting up LOM.
I have ethernet in port 1, and LOM is setup for channel 1.
Do i need to run ethernet to port 2 and setup LOM for channel 2?
Apple says to use an arbitrary IP for LOM. How arbitrary? Does the subnet need to be the as the internal network IP? Does the Gateway need to be the same, or is it arbitrary as well?
running 10.4.8
Thanks!
pete

Hi,
I have installed a couple of these and have the things up and running with one exception but I'll come to that later. OK, Assuming you have the ip's set up correctly ie main ip's are different to the LOM ones eg 10.0.0.1 and 10.0.0.2 are the main ip's on en0 and en1 respectively and you have 10.0.0.3 and 10.0.0.4 as the LOM ip's (Channel/port 1 and 2) on the respective same interfaces. Let's assume you are using everyting in the same subnet for now ie 255.255.255.0 and have the same gateway eg 10.0.0.254. Set up your LOM username and password in the Server Monitor window. First question - can you see the server via 127.0.0.1 / localhost on the machine itself? Not sure if that is your problem or it is a remote access of the status from another client. Please advise on that. Assuming you can see it locally and the problem is remote connection, once you have entered your LOM setting locally and authorised, shutdown the server, unplug both power cables and push the start button to remove any residual power. Leave it for 30 seconds and plug the power back in. When it boots back up, try and ping (from any other client) the LOM ip. You should get a response. If this is sucessful, try and open Server Monitor and connect to the LOM ip and you should get a sucessful connection. Please make sure you are using the server admin software from the disc supplied with the xserve. If you are unsure, try and install it again on your remote machine, it will only install anything if it is necessary. If you are using ARD, make sure it is version 3.1 and will prompt you by advising that it is updating it the first time you launch it after having installed server admin tools. You can run all basic functions of LOM from ARD or Server Monitor without using any unix tools. With the IPMITool you can get very specific data from the various sensors but most people don't need to get that specific. Let face it, most people just want to be able to reboot the thing is it sticks.
Just to clarify your first question...
The LOM channel / Port is just an ip address for ethernet port 1 and 2. Each physical port has two ip's attached to it very simply, one for main access, the other for LOM. I have configured various xserves with both ports on differrent ranges and subnets and they all work fine for access from anywhere I have tested. I would set them up all on the same subnet and router to start with. Get it running then change if necessary. You don't even need to use en1 if you don't want to. Just config en0 (Etherent port 1 and LOM port/channel 1) with two static ip's in the same subnet pointing at the same router and see how you go.
There is one question that any uber genius's might be able to help me with as Apple can't after 2 weeks...
I don't want to hijack this thread so if it is relevent to you issue, please see
"LOM failure after 1 hour" Thread.
Hope this helps.

Lights-Out Management Firmware Update

I tried to execute the Lights-Out Management Firmware Update, which Apple released, today.
But my Xserve always gives my an error, when I start the update application.
Lights-Out Management Firmware Update: Bad executable (or shared library)
Does anybody have the same problem?
Thanks and Regards,
JO

There's a new firmware update out, version 1.1. I tried simply using Software Update but no luck. It seemed to think it installed both 1.0 and 1.1, but all I saw was 1.0, which (still) did not work.
But I tried something else, and I think this works. I cannot test it until tomorrow when I can actually touch the server (to unplug it).
Open the Terminal application and do the following (omitting the "% " which I include to indicate the prompt).
% sudo rm /Applications/Server/Xserve\ Lights-Out\ Management\ Firmware\ Update.app
% sudo rm /Library/Receipts/LOMUpdate.pkg
% sudo softwareupdate -i LOMUpdate-1.1
The last step is important. It should only download the 1.1 updater. This seemed to work for me. that is, it downloaded the 1.1 updater, which I was able to run (from /Applications/Server/). However it tells me I need to shut down and unplug the the Xserve for one minute, then boot up, then install the update. I cannot do that until I'm back at work tomorrow. We'll see!
--greg
Message was edited by: Greg Welch

Xserve PowerPC G5: Configuring Lights-Out Management (LOM)

Can Lights-Out Management be configured using Server Monitor on an Xserve PowerPC G5? Thank you.
I was wondering because the "Configure Local Machine" feature is disabled.

Hi,
I'm afraid the G5 Xserve doesn't have Lights Out. It's a feature only found on the Intel Xserves.
All the best
Beatle

Asking for Lights out Management?

Running 10 iMacs & 10 Min Macs.
We can lock, restart, power off, control, all of that.
But as soon as we try to power on from shutdown, it comes up with ARD not active, and Lights out management not supported.
Obviously LOM has been discountinued with Xserve, but has it been integrated somewhere else?
I dont understand how it can be asking for LOM when it doesn't exist anymore.
Is there a solution to this? How can we power the mac's on using remote desktop?
And yes, before you ask, they are intel based.
Ross.

Hi
". . . but has it been integrated somewhere else?"
As of yet, no. It's not clear if Apple ever will? It has only ever been available on Intel XServes only.
"I dont understand how it can be asking for LOM when it doesn't exist anymore?"
It's not specifically asking for it as clearly LOM does exist but not on your hardware. ARD supports this feature if you're supporting hardware that does which can only be Intel XServe models.
"Is there a solution to this? How can we power the mac's on using remote desktop?"
Yes - you walk round to them and power them on. You can't use ARD to do this. You can however use ARD to send a terminal command that will set a power management schedule that goes some way in doing this for you. Mind you if you're having to go round to them all to switch them on you may as well apply the schedule settings locally. In an ideal world and assuming you have a mac server you can either define the settings you want in the build image you use to push out to rest or apply the settings using MCX.
Depending which method you use the Macs will have to be switched on at some point.
Questions specific to ARD are better asked in the dedicated ARD Forum here:
https://discussions.apple.com/community/servers_enterprise_software/apple_remote _desktop
HTH?
Tony

Lights-Out Management is not showing full status

Hi,
Since I upgraded my Intel XServe to Leopard, I don't get the full Lights-Out Management (LOM) status any more.
In Server Monitor it is only showing the status for:
- Power
- Temperature
- Blowers
- Security
Not the
- Info
- Memory
- Drives
- Network
Any idea what's wrong?
Thanks,
JO

http://discussions.apple.com/thread.jspa?threadID=1256863&tstart=0

How Do I Disable Lights Out Management (LOM)?

I was happily running 10.5 Server yesterday on my Intel XServe. The outside world was able to see my web server just fine.
I updated to 10.6 Server late last night and now my http service is not visible to the outside world (or local LAN for that matter).
Suspecting it has something to do with Lights Out Management (LOM).
How do I get LOM to turn loose of the local IP address of the ethernet interface?

What makes you think the LOM has anything to do with this?
There are about two million other things I'd check before I'd worry about the LOM. In fact I can't even think how the LOM could have have effect.
For a start have you verified the services are running? What do the logs say? Can you hit the web service from the machine itself? What about other services that should be running on the machine?
Have you checked the network configuration to make sure the server's IP address hasn't changed, that the default route is set correctly?
Then there are external factors to consider - maybe coincidences that occurred around the same time as your upgrade and may be masking the problem. Have you checked that your port forwarding is set correctly in your router? Are you sure your ISP hasn't started blocking port 80 traffic?

Lights Out Management...

Hi all,
I'm having troubles getting LOM to work on my new Intel XServe. During the Setup Assistant, without knowing anything about this feature, I happily skipped setting it up, thinking that it would be easy to enable it later (if deemed useful). The server is installed as a gateway (eth0 is WAN and eth1 is LAN), it is running local DNS, NAT, DHCP, Firewall and I can access the Server Admin and Workgroup Manager remotely using the domain name that points to the server.
Now when I go to the Server Monitor locally on the server and try to connect via. 127.0.0.1, it seems to connect briefly (i.e. the status lights at the bottom of the app change to green for a second), then the server listing itself disappears from the Server Monitor (i.e. the interface appears that I've never added a server). Now, if I try to add the server again (using the same local credentials), it says that that server has already been configured. The only way to remove this vanishing entry is to relaunch Server Monitor and delete the offending entry in the few seconds before it connects and vanishes again.
I've tried using the "Setup Local Server" menu option in the Server Monitor, but it's not clear to me what these values should be and everything that I've tried so far doesn't work. Should the port 1 have the same settings as my WAN port and port 2 the same as my LAN port?
Any help would be appreciated as guessing and testing isn't getting me too far and I'm concerned that by skipping the configuration of LOM in the Setup Assistant, I've made this impossible to turn on now.
Thanks for any suggestions,
Mike P

Thanks for this.
I've read that Apple doc already (to no avail), but thanks for the link anyways, others might find it useful.
Just so I understand your suggestion, when configuring Lights Out Management for LAN access, I should use Server Monitor -> Setup Local Server and change port 2 (I assume that port 2 would correspond to eth1 which is my LAN port distributing addresses in the 192.168.1.* range) by picking a valid IP within that range (e.g. 192.168.1.100), and filling in my subnet mask and router information (255.255.0.0 / 192.168.1.1 respectively)? This would then allow access to the server through Server Monitor while connected locally to the LAN via. 192.168.1.100?
Does this imply that for WAN access to Lights Out Management I would need my ISP to provide me with 2 static IP addresses (one for Lights Out and the other for web / internet services)?
Thanks again,
Mike P

Lights Out Management - Crashing / Resetting

It appears that Light-Out-Management is crashing, and I would like to know if there is a way to restart the LOM controller manually.
I have a Quad-Core Intel Xeon Xserve (XServe2,1).
- 2GB of memory (from factory)
- 80GB boot drive, 1TB drive modules in bays 2 and 3.
- 1 power supply
- no expansion cards
- connected to storage arrays via Firewire 800
- both ethernet ports are in use, 1 connected to the internal network via gigabit ethernet, the other to the fallback ISP
I have have configured Lights Out Management via Server Monitor. It typically works well, delivers information, sends notifications when needed. The lights-out management controller seems to crash or stop functioning regularly. I can only tell this has happened when I stop receiving notifications and the machine no longer appears in the Server Monitor list. The network connection to the machine is up and all other services seem to function normally. If I remote into the machine and do "Configure Local Machine" in Server Monitor, I get the marble of doom for about a minute, and when the Configure Local Machine interface does appear, all of the settings are zeroed out. (i.e. 0.0.0.0 for IP, subnet and router. username and password are blank.) Trying to re-enter the settings delivers an unhelpful error.
Restarting the machine does not help, when it reboots the LOM settings are still zeroed out. However if I shut down the machine and have the power disconnected for a short time (until the back panel lights go out) and then power up the machine, everything goes back to normal.
This is the only Intel Xserve in the rack, and the only one running 10.5. All the others are G5s running 10.4 or Ubuntu. Server Monitor runs well on the other OS X machines.

This problem has existed since the Intel Xserve was released. I haven't found a solution yet. The LOM usually comes back when I remove power from both power supplies for 15 seconds or so, but I'm not inclined to shut down my servers as frequently as the LOM quits.
It would be valuable for us if it worked, since its ipmi compliant.

Lights-Out Management Settings - Confusion

Just installed my new Intel Xserve. There doesn't seem to be any documentation for Lights-Out Management settings. At first I decided to just copy the external and internal network settings for LOM. The assistant didn't accept that. Then I used another real IP numer for the external and different one out of my internal net for the second interface (server internal IP 192.168.2.1 LOM 192.168.2.2). To no avail. Whenever I try to connect to these addresses using server monitor I get no answer from the server.
Could someone please explain a typical setting for LOM?
Thank you very much in advance!

Tim,
I could not get your suggestion to work. So I called Apple. Together Apple and I could not get it working either.
So I am back to square one. The biggest problem here folks is the terminology. In the Server Assistant (that runs automatically after the server operating system has been installed) talks about "channels," not ports. I am making the assumption that they are talking about Primary Port and Secondary Port or Port 1 or Port 2. Geez, talk about inconsistency!
Tim: When you say your "secondary port," I am not sure whether you are referring to Port 2 on the physical server. I don't have an Ethernet cable running to, nor I do intend to, as this should work on Port 1, no?
I plugged an Ethernet cable into Port 2 of the server and still no dice. I can ping the IP address I put in Server Monitor for LOM on either primary port or "secondary" port from another computer. I just cannot use its IP address on a remote computer to get it working!
The Apple guy said on the phone that you need to use the LOM IP address, and alluded to the terminal to change it, but also inferred that this can also be done in Server Monitor as Tim spoke about earlier by adding the srever as local host (127.0.0.1).
Very frustrating... Other than this fault, I am sure that the server works fine, but I would like to have this ironed out before I proceed.
By the way, the settings for LOM are stored on the logic board and will be automatically filled in if you erase and install the Server Monitor hardware.
Some one please write if you get this more concretely nailed down, and of course, I will keep everyone apprised if I make any headway get this working.

Lights Out Management - not accessable outside subnet

Have a new out of the box XServe and have configured the Lights Out Management Card for one interface port. Works great locally and on the same subnet, however, outside the subnet can not connect to it. Server is in a layer 3 environment, does the Lights Out protocol use broadcast packets (as those could be what is being blocked).
Lights Out Port has IP, Subnet mask, and Gateway configured properly (double checked, and triple).
Thanks

i 'believe' LOM does not work outside the local subnet. annoyingly.
not even sure why.
[quote]Using Server Monitor
The Xserve comes with the Server Monitor application. You can find Server Monitor in
/Applications/Server/ and on the Admin Tools disc that comes with the Xserve. You can
use Server Monitor to:
Â Check the current status of the Xserve and its components, including
Â Drive module status
Â Power supply status and system internal voltages
Â Network interface status and activity level
Â Temperatures of critical internal components
Â Cooling fan status
Â Review basic Xserve information such as
Â Uptime
Â Mac OS X Server version running on the Xserve
Â Amount and type of memory installed in each slot
Â Model and capacity of each drive module
Â Shut down, start up, or restart the Xserve
Â Generate an Apple System Profiler report for the Xserve
Â Send email alerts in response to changes in the status of the Xserve
You can run Server Monitor on the Xserve or on any computer that can connect to the
same network. [/quote]
notice the last line....
if anyone figures anything out i'd be grateful. i thought i'd use the second enet int'fce and configure it for LOM, giving it a second WAN IP, but i abandoned that idea for some reason.. can't remember why that wasn't working....
also, this may help: http://www.afp548.com/article.php?story=20070211101829496
Message was edited by: dtich
Message was edited by: dtich

Lights-Out-Management - Same or different IP ?

Hello,
I manage 5 remote xservers (intel - recent model) which are located in a data center. ARD and remote desktop is fine, but lights-out-management is not working
reliably.
Which is the correct way to set it up?
I have tried two ways:
A) Configuring LOM to use the same IP as the server itself
B) Dedicating a different IP to the LOM interface.
It wasn't working well on (A), so we gave each server a second IP, just for the
LOM. However in ARD there is no way to add this second IP as part of the machine details in the Edit details window. Just the user/pass details for LOM. If I configure for (B), in Scanner I can see the servers listed by their LOM IP, but they are not responsive to PowerOn, Shutdown etc requests issued from ARD.
How do others have LOM configured?
and does it work well for you for remote management?
Thanks
Paul

The LOM needs to have it's own IP. It has to be unique, and ARD expects that it is. "B" is the correct configuration.
You should add the Server to ARD using the IP address assigned to the server, not the LOM. I believe ARD "asks" the Server what it's LOM IP address is once the LOM username and password is supplied.

X2100M2 Embedded LIghts Out Manager best practice

Hi guys,
I'm in worry about the best practice of configuring network interface on a X2100M2 Solaris 5.10 for the Embedded LIghts Out Manager. Hope you can help. I haven't find any documents of it which explain the best practice.
Here is the situation :
I've have 4 network interfaces but I only need two of them. So I decide to use the bge0 and the bge1 interfaces.
bge0 is the server interface with an IP with .157
bge1 is the ELOM interface with an IP with .156
In the past, it was the reverse : bge0 was the ELOM with .156 and bge1 was the network server int. with .157
Could you please guys let me know what is the best practice? Does the int.0 must be the server one? Is it possible to have network problem with this kind of configuration?
Thanks
Cheers,

hi guys,
No one have a clue? I've got some dukeDolars to offer...
Tks

LOM (Lights Out Management) v/ VPN Connection

The only time I can access LOM via the Server Monitor tool is when plugged directly into the LAN where my Intel servers live.
If I attempt to use Server Monitor while connected via VPN to my office, it doesn't work. Server Monitor indicates that there is "No response..." since last time I connected in my office.
Any thoughts?
Remote Access 3.0 indicates LOM Status:Not Configured - however, again, on the LAN it works just fine.
Thanks,
Phillip

Just want to add that I have had this problem for Months and I only just found the extremely simple tip that worked where everything else had failed.
Follow all of the steps provided elsewhere.. Configure in Server Monitor via "Configure Local Machine:, two different IPs from the main address and save.
(i.e http://docs.info.apple.com/article.html?artnum=304896)
What actually made this work is to then Shutdown the server after saving. Unplug it (or both power supplies) for about 30 seconds
Plug in and power on.
I can assure you this works if all the config steps are followed.
Literally 6 months I have been trying to get this to work and tried just about everything, but It turns out is just the enet contoller that needs to be reset by powering off and on.
I am just shocked that this simple tip is not mentioned in any of the Apple kbase articels or documentation that I could find

Intel Xserve Lights Out Management Config Question

Similar Messages

Maybe you are looking for