- Community Home
- >
- Networking
- >
- IMC
- >
- Default Alarm Timeouts/Recovery
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-26-2018 01:14 AM
тАО04-26-2018 01:14 AM
Default Alarm Timeouts/Recovery
Due to various reasons we have a rather long-lived alarm relating to a secondary power supply that appears to have auto-recovered (via $SYSTEM) without the power supply actually being replaced. In addition I do not see an info level alarm indicating a recovery event. To my eyes it looks like there is some kind of default threshold within iMC that has recovered this after a period of 30 days.
If my assumtpion is correct my question is, is there a setting somewhere in iMC whereby we can either extend this value for all managed devices or a specific device. Normally these sort of conditions do not hang around this long but there are occasional excpetions so we need to be able to manage this.
Regards and thanks
Mike
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-30-2018 01:41 PM
тАО04-30-2018 01:41 PM
Re: Default Alarm Timeouts/Recovery
How was the original alarm triggered? Via syslog, SNMP trap, or via SNMP polling?
I'm wondering if the original event was from a trap or log, and the data export policies have exported the old records, and the alarm was recovered at that point. Just a guess.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-02-2018 01:46 AM
тАО05-02-2018 01:46 AM
Re: Default Alarm Timeouts/Recovery
Lindsay,
Thank you for taking the time to reply. The original event resulted in a trap. You may need to point me in the direction of the data export policies and whether there are options there to tweak things either wholesale or more granularly.
Regards
Mike
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-02-2018 06:12 PM
тАО05-02-2018 06:12 PM
Re: Default Alarm Timeouts/Recovery
Look up "Data Export" in the Admin guide. This has some details about what options exist. It may also tell you how it handles unrecovered alarms.