Exalogic Virtual : False-Positive Oracle Enterprise Manager (OEM or EM) Alerts claiming that ILOM Storage Nodes are down (irrespective of the Nodes being continuously up) (Doc ID 2039612.1)

Last updated on MARCH 11, 2016

Applies to:

Oracle Exalogic Elastic Cloud Software - Version 2.0.6.2.0 to 2.0.6.2.2
Linux x86-64
Oracle Virtual Server (x86-64)

Symptoms

When Oracle Enterprise Manager (OEM or EM) /Enterprise Manager Cloud Control (EMCC) is used to monitor the Exalogic virtual racks, after upgrading the racks to Exalogic Virtual releases 2.0.6.2.0 (with Patch 20957357) / 2.0.6.2.1 / 2.0.6.2.2 , intermittently false-positive OEM alerts are seen stating that ILOM Storage Node(s) are down even though the Storage nodes are up.

For example, the alert will be as follows:

From: DBA Group <DBAGroup@abc.com>

To: UNIXGroup <UNIXGroup@xxx.com>

Cc: DBA Group <DBAGroup@xxx.com>, Middleware <Middleware@xxx.com>,

Middleware <Middleware@xxx.com>, UNIXGroup <UNIXGroup@xxx.com>

Date: July 14, 2015 at 16:57:15 PM GMT+3

Subject: EM Event: Fatal:/Abc Exalogic/AK00123456/172.xx.xx.xx – The ILOM server /Abc Exalogic/AK00123456/172.xx.xx.xx is down


Host=el01xx.xxx.com

Target type=Oracle Engineered System ILOM Server

Target name=/Abc Exalogic/AK00123456/172.xx.xx.xx

Categories=Availability

Message=The ILOM server /Abc Exalogic/AK00123456/172.xx.xx.xx is down       <====== False-Positive Alert stating Node is DOWN ( but this is not)

Severity=Fatal

Event reported time=Jul 14, 2015 4:57:15 PM EEST

Operating System=Linux

Platform=x86_64

Associated Incident Id=2036845

Associated Incident Status=New

Associated Incident Owner=

Associated Incident Acknowledged By Owner=No

Associated Incident Priority=None

Associated Incident Escalation Level=0

Event Type=Target Availability

Event name=Status

Availability status=Down

Root Cause Analysis Status=Neither Cause Nor Symptom

Causal analysis result=Neither a cause nor a symptom

Rule Name=Exalogic Events,Exalogic Availability

Rule Owner=SYSMAN

Update Details:

The ILOM server /Abc Exalogic/AK00123456/172.xx.xx.xx is down

Incident created by rule (Name = Incident management rule set for all targets, Incident creation rule for a Target Down availability status [System generated rule]).

 

NOTE:

Please note this is a cosmetic annoyance rather than something that's having an impact.

 

Changes

The issue has been observed after upgrading to Exalogic Virtual releases 2.0.6.2.0 (with Patch 20957357) / 2.0.6.2.1 /2.0.6.2.2

Cause

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