- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- ProLiant Servers (ML,DL,SL)
- >
- Re: Logging of ASR Service
ProLiant Servers (ML,DL,SL)
1755964
Members
3308
Online
108839
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
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
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
11-06-2009 02:45 AM
11-06-2009 02:45 AM
Logging of ASR Service
Hello,
I have a problem on ML350 G5 server that, sometime ... in random day, was restarted by ASR service during the night ... in the event viewer of windows, when ASR restart server, there are nothing of abnormal ( I find only critical error of ASR ) ... In HP Prolinat Integrated Management Log Viewer I find only the ASR Critical Event and nothing else ... When ASR restart, server running backup procedures with Symantec Backup Exec 11 ( I have written also in Symantec forum ) ... there is a method to have detailed information about why ASR restart server ?
Sorry for my english
I have a problem on ML350 G5 server that, sometime ... in random day, was restarted by ASR service during the night ... in the event viewer of windows, when ASR restart server, there are nothing of abnormal ( I find only critical error of ASR ) ... In HP Prolinat Integrated Management Log Viewer I find only the ASR Critical Event and nothing else ... When ASR restart, server running backup procedures with Symantec Backup Exec 11 ( I have written also in Symantec forum ) ... there is a method to have detailed information about why ASR restart server ?
Sorry for my english
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-06-2009 07:10 AM
11-06-2009 07:10 AM
Re: Logging of ASR Service
Oscar,
Auto self recovery is triggered by the Hardware Watch dog timer, basically is a clock counting and if it reaches its limit (default 10 min) it forces the server to re-start .
In ideal conditions this clock never reaches 1 second because the server is contansly sending reset signals to it (severals per second.
If the operating system is not hanging, it may be possible that you have hardware malfuntion or firmware corruption that is making the clock go up to 10 min, my first recommendation will be to download FW-CD 8.60 and force a flash of firmware for the entire server, additionally update ILO managment driver and chipset driver.
JQ
Auto self recovery is triggered by the Hardware Watch dog timer, basically is a clock counting and if it reaches its limit (default 10 min) it forces the server to re-start .
In ideal conditions this clock never reaches 1 second because the server is contansly sending reset signals to it (severals per second.
If the operating system is not hanging, it may be possible that you have hardware malfuntion or firmware corruption that is making the clock go up to 10 min, my first recommendation will be to download FW-CD 8.60 and force a flash of firmware for the entire server, additionally update ILO managment driver and chipset driver.
JQ
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