- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- Server Management - Remote Server Management
- >
- Re: iLO temporarily unavailable
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-18-2005 05:23 AM
тАО03-18-2005 05:23 AM
iLO temporarily unavailable
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-24-2005 08:21 AM
тАО03-24-2005 08:21 AM
Re: iLO temporarily unavailable
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-25-2005 03:50 AM
тАО03-25-2005 03:50 AM
Re: iLO temporarily unavailable
http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=714052
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-29-2005 05:49 AM
тАО07-29-2005 05:49 AM
Re: iLO temporarily unavailable
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-29-2005 10:37 AM
тАО07-29-2005 10:37 AM
Re: iLO temporarily unavailable
Was the firmware update to 1.80 successful?
(the login problem being something differnet).
Can you see the iLO LEDs inside the system? There are a bank of 8 green LEDs. Sometimes they are not shown if the host is turned on, so turn the system off, and look for LEDs. There should be a couple blinking LEDs next to each other at one end of the bank.
These LEDs basically indicate that the iLO firmware is running and is healthy. If they are not regularly blinking as described, they might indicate an error.
A "Night Rider" pattern indicates that the firmware flash failed. I suggest trying it again using the Smart Start firmware update CD.
A pattern switching regularly between two different values like
on off off on on off off on
off off off off off off on off
is a bad sign. Try unplugging the host for a couple minutes and restarting (this reboots iLO). If the pattern returns, You will need to reset iLO to defaults.
The way to do that at this point is to unplug the host and then remove the coin battery from the system board for at least a couple minutes. This is a delicate procedure. Note the orientation of the battery before you remove it. This will cause you to lose all iLO settings and host ROM settings, too.
Put the battery back in, then plug in the system and see if iLO is alive.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-23-2010 06:49 AM
тАО08-23-2010 06:49 AM
Re: iLO temporarily unavailable
I had almost the same problem today: "Integrated Lights Out is temporarily available (1)", and it's been resolved after 3 reboots.