![]() | Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition | ||
|
|
![]() |
||||||||||||||||||
Solution Type Problem Resolution Sure Solution 1954627.1 : Exalogic Virtual: EMOC False Warning Messages On Cisco Switch Ports 49 Through 55 With "Te" Or "Fa" In Their Description As FAULTED When These Ports Are Not Connected
In this Document
Created from <SR 3-9901665031> Applies to:Oracle Exalogic Elastic Cloud Software - Version 2.0.4.0.2 to 2.0.6.1.2Exalogic Elastic Cloud X3-2 Quarter Rack - Version X3 to X3 [Release X3] Linux x86-64 SymptomsYou have an Exalogic system running Exalogic Elastic Cloud Software (EECS) in a virtual configuration, where the browser based UI (BUI) for Enterprise Manager OpsCenter (EMOC) is showing unexpected notifications/incidents that indicate some ports on the Cisco switch component, in the range 49 through 55 that include "Te" or "Fa" in their description, are unexpectedly FAULTED. Message: WARNING incident NNN created on port[49]port[49]Te1/49@XX_XX_XX_XX@XX_XX_XX_XXX is FAULTED. (106709)
Message: WARNING incident NNN created on port[49]Te1/49@XX_XX_XX_XXX is FAULTED. (106709) Message: WARNING incident NNN created on port[50]port[50]Te1/50@XX_XX_XX_XX@XX_XX_XX_XXX is FAULTED. (106709) Message: WARNING incident NNN created on port[50]Te1/50@XX_XX_XX_XXX is FAULTED. (106709) Message: WARNING incident NNN created on port[51]port[51]Te1/51@XX_XX_XX_XX@XX_XX_XX_XXX X is FAULTED. (106709) Message: WARNING incident NNN created on port[51]Te1/51@XX_XX_XX_XXX is FAULTED. (106709) Message: WARNING incident NNN created on port[52]port[52]Te1/52@XX_XX_XX_XX@XX_XX_XX_XXX is FAULTED. (106709) Message: WARNING incident NNN created on port[52]Te1/52@XX_XX_XX_XXX is FAULTED. (106709) Message: WARNING incident NNN created on port[55]Fa1@XX_XX_XX_XXX is FAULTED. (106709) Message: WARNING incident NNN created on port[55]port[55]Fa1@XX_XX_XX_XXX@XX_XX_XX_XXX is FAULTED. (106709) CauseWhen used in different size of Exalogic rack, not all ports in the Cisco switch component are wired to other components in the rack and EM OpsCenter (EMOC) therefore ignores the status of the ports it identifies as not expected to be connected to components for the given size of the rack (e.g. eighth, quarter, half etc.) However, due to a change in capabilities for the Cisco switch model shipped in later Exalogic systems, the description of certain ports has changed causing EMOC to fail to correctly identify ports that are not expected to be connected for the given rack type, which leads to incidents/warnings being raised against specific ports. These are false incidents that can be ignored since the flagged ports aren't expected to be connected. (UNPUBLISHED) <BUG:18367008>
non-connected cisco ports are mistakenly reported as faulty
SolutionPlease download and apply the January 2015 Patch Set Update (PSU) for Exalogic virtual systems (EECS 2.0.6.2.0) which contains the fix for this issue: <<PATCH:19370511>>
EXALOGIC VIRTUAL 2.0.6.2.0 (on X2-2/X3-2/X4-2) PATCH SET UPDATE (PSU) FOR JANUARY 2015
<<NOTE:1959624.1>>
Exalogic Patch Set Update (PSU) Release 2.0.6.2.0 (Linux - Virtual) for January 2015
References<NOTE:1933252.1> - Exalogic Kinetic Infrastructure Tools (EKIT): Set of scripts that provide common reusable command line infrastructure actions for Exalogic virtual platforms<BUG:18508750> - DOCUMENT FALSE ALERTS FOR NON-GIGABIT PORTS FROM CISCO SWITCH <BUG:18367008> - NON-CONNECTED CISCO PORTS ARE MISTAKENLY REPORTED AS FAULTY Attachments This solution has no attachment |
||||||||||||||||||
|