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

Similar Messages

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 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

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...

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 - 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

How do those who don't watch boards find out about firmware updates?

Since 'Software Update' doesn't alert users to firmware updates, I wonder how those that don't monitor these boards and other 'Mac news' sites find out about firmware updates?
Yes, Boot Camp made headline news in many major newspapers and those who wanted to install it found they needed to update the firmware first.
But, had I not read about it elsewhere earlier, I would not have known about the second MBP firmware update (which, apparently, solves some of the 'whine' issues - I've had no whining but I like to keep my firmware, in particular, up to date!).
Just as a note to Apple - you've a database of all who have registered their MPB's (at least those with AppleCare if not those who simply run set-up with new Mac purchases). If firmware updates aren't included in the 'Software Updates' procedure, shooting off an email to those with machines that might be in need of firmware updates may save a world of grief to overworked phone support techs.

Yes, I'm familiar with the support page but my point is that not all (in act, likely very few) are familiar enough with that page to go to "Top Downloads" to find firmware updates.
On page 25 of the MacBook Pro Users Guide, Apple DOES suggest, in the next to the last paragraph, suggest "For support information, user discussion boards, and the latest Apple software downloads, go to www.apple.com/support."
But if a new user is having problems he or she is more likely than not to pick up the phone first - and although there's the 90-day phone support and 3 year phone support for those who purchase AppleCare (which new users may not - particularly if buying from, say, CompUSA or other stores who push 'extended warranties' even with the purchase of products whose manufacturers already provide LIFETIME warranties) Apple has thoughtfully provided automated Software Updates (which Windows switchers understand all too well!) but no automated way to be lead to firmware updates. It's my feeling that if firmware notification were included in SU notifications, or via email, it might reduce the number of phone calls and result in happier computers.
While I enjoy reading all the Mac news on a daily basis, a lot of users don't and there may be an even greater number who don't know the wheat from the chaff (or even know where to find the wheat!).
Some firmware updates are critical, some of minor importance, and some (more and more of late, it seems) just a bit cryptic (for instance, 1.01 says "This firmware update is for (MacBook Pro)/iMac (early 2006) computers with Intel processors only. It now runs on localized systems that use languages that read right to left." and then lists the languages supported - which do not include Hebrew or Arabic, two "languages that read right to left".
The only reason that I brought this up is that there are a number of sites that reported that the firmware update alleviates some of the 'whine' that some MBP users are reporting (and now I am reading of 'hum' issues - forget GarageBand! An hundred MBP's could replace a symphony!). Now is that true or not? Apple doesn't say - some users report yes, some no. And as there are no whine or hum issues on the iMac, I doubt 1.01 would 'solve' any of those problems with that machine (and interesting, too, that the "iMac (early 2006) Firmware Update 1.0.1" isn't in the "Top Downloads" section as is "MacBook Pro (early 2006) Firmware Update 1.0.1": what's up with that? Are there really more MBPs out there than Intel iMacs? Or are MBP owners running Windows in Arabic more than Intel iMac owners? Or just hopeful that the update does, indeed, help with the whine problem.
I keep getting off topic (sort of)...
...my point is that it would be simple to notify, and simpler for (in my opinion), Apple to notify customers of firmware updates.

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

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 - 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.

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

How to get out of firmware update...I dont have an ac adapter.

I got a new Ipod 4th gen 20gb off of Ebay. Its new and only came with usb cable & headphones. From what I can tell I can only add music by itunes. I installed itunes and it said there was an update available. I told it to update, but it says I need to connect an ac adapter to continue. I dont have one! The ipod has a picture of a outlet on the screen and I can not do anything! How do I cancel out of this update and just use the ipod? Can't I just use the usb connection like I did to charge it to begin with?

Connect the iPod to a 6-pin FireWire port on a computer, or its power adaptor, or a car adaptor, or a unit such as the iPod Hi-Fi, or try using this method to charge the iPod. If there's a retail Apple Store nearby, they will likely charge it enough for free if it's brought in as well.
(42724)

Firmware Password Lock, Managing Firmware Updates

I want to increase my data security beyond account password protection. (Ran FileVault previously but encountered a disaster - user account information became corrupted somehow. Password would be accepted but login denied with an error message but no code. Ouch.)
Firmware Password Lock looks to me like a good bump up in security (I know it's not in the same league as FileVault from experience). I'm thinking I'll have to settle for this less secure option.
Please help me to understand possible pitfalls beyond the obvious "retain the password".
Will Firmware updates continue to come in normally with Software Update? Please help. Tony

nublu wrote:
Thank you for helping with my security question. I have googled a bit. I have found examples of physical damage to computers (new mother board needed) because of failure to get firmware update before upgrading OS. In that case it was upgrade to OS10 from OS9. This doesn't directly apply to my case, never the less, it does cause me to pause.
Is it correct that if firmware password lock is enabled, firmware updates will load and install without unlocking firmware.
I'm not sure about this. a firmware update will always come with instructions and if the firmware password needs to be turned off to install it, this will be explicitly mentioned. as turning the firmware password off is very easy and firmware upgrades are very rare, this should not be a consideration IMO.
(sorry for asking again - just trying to be sure. Could not find a specific answer to this in apple support info.)
I did find this recommendation to check for and load firmware updates outside of Software Update.
http://support.apple.com/kb/HT1237
Please tell me if this is recommended.
there is absolutely nothing wrong with downloading an update manually.

Power Light Blinks after firmware update to 1.00.17

I have model # WRT54GX4.
It has worked great, i just wanted to update the firmware.
I updated the firmware from 1.00.15 to 1.00.17 and now the power light just blinks.
Based on what i read it sounds like the firmware needs re-loaded because it could be corrupt on the router now. It could have been the way that i upgraded. i was in wireless mode when i did the upgrade thru the web utility, mayby i should have been plugged in. The other thing is that i use 192.168.1.X range (not 192.168.0.X range), i am not sure if the firmware upgrade changes the ip back to 192.168.1.1, which affected the upgrade.
In either case my power light is blinking. i also tryed to hold the reset button for 10 seconds, i also tried 30. After that i plugged directly into the router from the pc using a regular patch cable. I change the ip on my machine to 192.168.1.8 and the subnet to 255.255.255.0 to match the router. i am assuming that the router is reset to 192.168.1.1 now that i pressed the reset button. After doing all this i get a network connection, but i cannot ping 192.168.1.1.
Here is my other question. To fix the issue i would think that i would have to run the firmware upgrade utility from outside the router, now that the router is not accessible. But the download page does not have a firmware utility like the other models. The instructions want you to use the web utility on the router.
Please help.

HI,
u can upgrade the router from the "outside" using the tftp utility available at ftp.linksys.com/pub/network/tftp.exe .
however you first have to be able to ping the router....reduce the NIC speed to 10Mbps...assign a static IP to your PC ...reset the router and then try to ping....once the ping is confirmed....you can upgrade the firmware.
and yes the default router IP should now be 192.168.1.1

Lights-Out Management Firmware Update

Similar Messages

Maybe you are looking for