locked
New to SCOM, how do I ignore alerts (I think this may need an override) RRS feed

  • Question

  • Hello All,

    I'm new to Ops Manager and I'm trying to get a feel for it.

    To start off with I'm trying to cleanup the current alerts that I have.

    For starters, I have the HP Proliant Managment Pack,

    I have about 10 servers that have dual power supplies installed and only one connected.

    (this is the way we want it)

    I don't have blanks for the power supply slot should I remove the extra power supply.

    (We also have other HP servers that have redundant power (that should) that I do not want to ignore)

    Is there away to 'acknowledge and ignore' a specific alert  for specific hosts?

    Below are the alerts that I am refering to:

     

    WARNING - HP ProLiant SNMP Power Supplies Collection Health Monitor - Power Supplies (Power Supplies (ProLiant SNMP)

    Date and Time: 8/15/2011 5:55:43 PM
    Property Name Property Value
    Processors_SNMP.HealthState HealthSuccess
    Cooling_SNMP.HealthState HealthSuccess
    Memory_SNMP.HealthState HealthSuccess
    ServerNetworks_SNMP.HealthState HealthSuccess
    PowerSupplies_SNMP.HealthState HealthWarning
    PowerSupplies_SNMP.FailedComponent Power Supply 1
    RealtimeMonitors_SNMP.HealthState HealthSuccess
    ManagementProcessors_SNMP.HealthState HealthSuccess
    ServerStorage_SNMP.HealthState HealthSuccess
    TemperatureSensors_SNMP.HealthState HealthSuccess
    Logs_SNMP.HealthState HealthSuccess
    ServerOthers_SNMP.HealthState HealthError
    ServerOthers_SNMP.FailedComponent Other System Health (UID, POST)

    Critical - HP Proliant SNMP Server Others Collection Health Monitor - Server Others (Others (ProLiant SNMP))

    Date and Time: 12/24/2011 6:37:10 PM
    Property Name Property Value
    Processors_SNMP.HealthState HealthSuccess
    Cooling_SNMP.HealthState HealthSuccess
    Memory_SNMP.HealthState HealthSuccess
    ServerNetworks_SNMP.HealthState HealthSuccess
    PowerSupplies_SNMP.HealthState HealthWarning
    PowerSupplies_SNMP.FailedComponent Power Supply 1
    RealtimeMonitors_SNMP.HealthState HealthSuccess
    ManagementProcessors_SNMP.HealthState HealthSuccess
    ServerStorage_SNMP.HealthState HealthSuccess
    TemperatureSensors_SNMP.HealthState HealthSuccess
    Logs_SNMP.HealthState HealthSuccess
    ServerOthers_SNMP.HealthState HealthError
    ServerOthers_SNMP.FailedComponent Other System Health (UID, POST)

    Thanks!


    -Ryan Biddle-


    • Edited by rbiddle Wednesday, December 28, 2011 4:50 PM
    Wednesday, December 28, 2011 4:39 PM

Answers

  • Hi Ryan,

    I do not know this management pack very well, but i don't see a reason for monitoring a single PSU. If it fails your server will be off without SCOM seeing it was the PSU that failed. It just loses contact with the agent and fails to get any information until the server is fixed.

    My recommendation is to hook up the second PSU for redundany, override the rule if possible (select the error, click healt explorer in the right pane an create an override for the specific object) or remove the PSU.

     

    Hope this helps,

     


    Wednesday, December 28, 2011 8:29 PM

All replies

  • Hi Ryan,

    I do not know this management pack very well, but i don't see a reason for monitoring a single PSU. If it fails your server will be off without SCOM seeing it was the PSU that failed. It just loses contact with the agent and fails to get any information until the server is fixed.

    My recommendation is to hook up the second PSU for redundany, override the rule if possible (select the error, click healt explorer in the right pane an create an override for the specific object) or remove the PSU.

     

    Hope this helps,

     


    Wednesday, December 28, 2011 8:29 PM
  • Thank you for the response.

    Leading me to the overrides from the health explorer/monitor properties/overrides helped alot.

    I chose create override 'for specific object of class "HP Proliant SNMP Power Supplies Collection"'

    This allowed me to disable this monitor for the systems that were causing the false alarm.

    thanks again!

     

     


    -Ryan Biddle-
    Wednesday, December 28, 2011 9:29 PM