- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- ProLiant Servers (ML,DL,SL)
- >
- Re: ProLiant DL380 G3 weekly ASR reboot
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
тАО04-21-2004 12:24 AM
тАО04-21-2004 12:24 AM
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-21-2004 12:58 AM
тАО04-21-2004 12:58 AM
Re: ProLiant DL380 G3 weekly ASR reboot
ASR Disabeling won't going to help you. But what is the exact error reported under iml in same case any bug check error or any other notification. any error information under event veiwer.
Regards,
Prashant S.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-21-2004 01:06 AM
тАО04-21-2004 01:06 AM
Re: ProLiant DL380 G3 weekly ASR reboot
"Index Description Time Of Event Update Time Count
1 ASR Detected by System ROM 4/21/2004 6:10AM 4/21/2004 7:57AM 1"
There are no further errors. The Windows Event Viewer does not report any errors. I utilize Compaq Insight Manager. It reports the following Minor error: "Event description:The server is operational again. The server has previously been shutdown by the Compaq Automatic Server Recovery (ASR) feature and has just become operational again."
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-21-2004 01:20 AM
тАО04-21-2004 01:20 AM
Re: ProLiant DL380 G3 weekly ASR reboot
Run Server Diagnostics if feasible to determine if this is a hardware or software issue and Increment ASR timeout in the RBSU if still does not help you then go for disabling.
Regards,
Prashant S.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-21-2004 01:35 AM
тАО04-21-2004 01:35 AM
Re: ProLiant DL380 G3 weekly ASR reboot
I ran Server Diagnostics and no errors were reported. I have Google'd this topic and understand that I am not the only individual encountering this situation. Perhaps there is a flaw in the ASR implementation. Would a BIOS upgrade potentially correct this problem ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-21-2004 07:39 AM
тАО04-21-2004 07:39 AM
Re: ProLiant DL380 G3 weekly ASR reboot
So far, we're exploring bad ServerWorks chipset revisions with HP--you might want to confirm that your motherboards don't have a flawed ServerWorks GC-LE chipset.
See this link for the story:
http://www.linuxworld.com/story/35213.htm
Beware the ServerWorks GC-LE Chipset
Summary
There's a bug in some of the ServerWorks Grand Champion LE chipsets that's bad enough to hang the servers they're used in. The company says that - after IBM found the problem - ServerWorks ran up a software utility that will let OEMs screen out defective boards.
Both the dl360-g3 and dl380-g3 contain this chipset. So far, I'm unaware of a consumer tool to screen for defective chipsets.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-21-2004 08:07 AM
тАО04-21-2004 08:07 AM
Re: ProLiant DL380 G3 weekly ASR reboot
Here are all the things we've tried to solve this problem (to no avail):
- Kernel upgrades (up to 2.4.9-e.39 using RedHat's Enterprise series)
- upgrading/turning off all HP server/health agents
- hardware swapping:
1. memory
2. cpu
3. motherboard
4. ppms (power modules for each CPU)
- multiple diags pre/post lockup
- BIOS upgrades: system ROM & 5i RAID controller ROM
- OS reinstallation/rebuilding
- ethernet controller driver switch (HP's bcm5700 -> RedHat's tg3)
Also: we sent a machine to HP's lab in Texas about a month ago, but they haven't found anything yet.
Please post if you get any new information or clues.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-21-2004 01:21 PM
тАО04-21-2004 01:21 PM
Re: ProLiant DL380 G3 weekly ASR reboot
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-21-2004 02:09 PM
тАО04-21-2004 02:09 PM
Re: ProLiant DL380 G3 weekly ASR reboot
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-21-2004 07:16 PM
тАО04-21-2004 07:16 PM
Solutionthe default schedule of the survey service is Wednesday 6 am and this on a weekly basis (or after every reboot) so it looks like something that happens during the survey service data collection process causes your server to lock up. You say no jobs are scheduled , you probably mean your custom jobs then since the above looks a bit to much of a coincidence to me.
Check if you're using the latest versions of the management agents and surveyor.exe or disable it till you found a fix.
Attached is a doc on how to change the default schedule of the survey service.
HTH
Kris