OpsCenter needs to be improved so that a CRITICAL alert is not sent out when a server is reset manually. (Doc ID 1677545.1)

Last updated on JULY 29, 2016

Applies to:

Solaris Operating System - Version 10 1/13 U11 and later
Information in this document applies to any platform.

Goal

If critical alerts being generated is the standard thing to happen when an admin clicks on the reset button in the ILOM and there is a better process to reset a server during OS builds, troubleshooting, etc, which would prevent these critical alerts from being generated, please let me know what that better process is.

Ops Center is reporting several critical alerts, like the ones below :

Incidents reported by Ops Center:
Current Incident:
Severity: CRITICAL
ID: 11865938
State: UNASSIGNED
Description: critical alert on faulty component SMI Handler. A generic system component error due to Initiated by warm reset.
Creation Date: Wed May 07 09:43:25 CDT 2014

The resets were manually invoked by clicking the reset button from the ILOM web GUI, as I was trying to get the OS built on this server. Being that there is not hardware failure or issue, I would like to see why OpsCenter generated such a high level event when nothing was wrong.

I would think that OpsCenter needs to be fixed/improved so that a CRITICAL alert is not sent out when a server is reset.
 

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms