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 220.127.116.11.0 to 18.104.22.168.2
Oracle Virtual Server (x86-64)
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 22.214.171.124.0 (with Patch 20957357) / 126.96.36.199.1 / 188.8.131.52.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:
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
Target type=Oracle Engineered System ILOM Server
Target name=/Abc Exalogic/AK00123456/172.xx.xx.xx
Message=The ILOM server /Abc Exalogic/AK00123456/172.xx.xx.xx is down <====== False-Positive Alert stating Node is DOWN ( but this is not)
Event reported time=Jul 14, 2015 4:57:15 PM EEST
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
Root Cause Analysis Status=Neither Cause Nor Symptom
Causal analysis result=Neither a cause nor a symptom
Rule Name=Exalogic Events,Exalogic Availability
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]).
Please note this is a cosmetic annoyance rather than something that's having an impact.
The issue has been observed after upgrading to Exalogic Virtual releases 184.108.40.206.0 (with Patch 20957357) / 220.127.116.11.1 /18.104.22.168.2
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!