- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- ProLiant Servers (ML,DL,SL)
- >
- Re: Detecting if the "F1" prompt will halt a reboo...
ProLiant Servers (ML,DL,SL)
1752272
Members
5784
Online
108786
Solutions
Forums
Categories
Company
Local Language
юдл
back
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
юдл
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- 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
тАО01-26-2005 10:37 PM
тАО01-26-2005 10:37 PM
Detecting if the "F1" prompt will halt a reboot
It's really bad news to have servers hang at an F1 prompt when doing a massive patch deployment.
I'd like to create a simple command-line utility that would return an error level if the F1 prompt is set to hang the server. Then, I could easily create deployment scripts that could safely skip those servers (of course, logging the failures to a text file for later follow-up) and not cause high-severity tickets and panic! I didn't see anything reported by WMI to check the flag. Can I programmatically access the Compaq monitoring agents via some kind of API?
I had to ditch the simplistic idea of scanning the event logs for failures. Our servers archive their logs every night and start clean each day. We're not allowed to use Insight Manager, so that's also not an option.
I can't be the only one who's needed something like this!
Thanks,
Derek
I'd like to create a simple command-line utility that would return an error level if the F1 prompt is set to hang the server. Then, I could easily create deployment scripts that could safely skip those servers (of course, logging the failures to a text file for later follow-up) and not cause high-severity tickets and panic! I didn't see anything reported by WMI to check the flag. Can I programmatically access the Compaq monitoring agents via some kind of API?
I had to ditch the simplistic idea of scanning the event logs for failures. Our servers archive their logs every night and start clean each day. We're not allowed to use Insight Manager, so that's also not an option.
I can't be the only one who's needed something like this!
Thanks,
Derek
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-27-2005 12:41 AM
тАО01-27-2005 12:41 AM
Re: Detecting if the "F1" prompt will halt a reboot
I believe you can turn a setting on in the bios to not stop on an error, but it requires a rev upgrade to latest firmware. We have had to do this with several older servers(1850,6400, etc) and I believe the 5000 was also one of them. Hope it helps.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-27-2005 03:10 AM
тАО01-27-2005 03:10 AM
Re: Detecting if the "F1" prompt will halt a reboot
Why are you "not allowed" to use Insight Manager?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-27-2005 07:31 PM
тАО01-27-2005 07:31 PM
Re: Detecting if the "F1" prompt will halt a reboot
Well, the F1 hangup is good for things that could possibly cause data loss if booting continues, so disabling it probably wouldn't be a good thing in the long run. However, it seems a bit overkill for something simple such as a bad power supply or bad drive.
As for not being able to use Insight Manager, I think our management is really pushing Tivoli for monitoring and wants us to use it as the ONLY monitoring tool since it automatically generates service tickets to the correct support groups on the mainframe ticketing system. This way, they actively monitor all operating systems (Win/Unix/Linux) with a single tool, no matter what brand of hardware it's running on.
When people attempt to remotely reboot servers in a multi-site environment, it's just counterproductive to have to travel to each site (or open trouble tickets for physically unreachable sites) just because one or two servers get stuck during reboot. That's why I was looking for something that could not ignore, but temporarily skip a server in a batch reboot procedure. It would let the immediate work be completed without needless business impact.
As for not being able to use Insight Manager, I think our management is really pushing Tivoli for monitoring and wants us to use it as the ONLY monitoring tool since it automatically generates service tickets to the correct support groups on the mainframe ticketing system. This way, they actively monitor all operating systems (Win/Unix/Linux) with a single tool, no matter what brand of hardware it's running on.
When people attempt to remotely reboot servers in a multi-site environment, it's just counterproductive to have to travel to each site (or open trouble tickets for physically unreachable sites) just because one or two servers get stuck during reboot. That's why I was looking for something that could not ignore, but temporarily skip a server in a batch reboot procedure. It would let the immediate work be completed without needless business impact.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP