![]() | Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition | ||
|
|
![]() |
||||||||||||
Solution Type Problem Resolution Sure Solution 2112346.1 : 12cEM reports error on Exadata X2-8 or X3-8 ILOM targets: "Status Metric evaluation error start - oracle.sysman.emSDK.agent.fetchlet.exception.FetchletException: - Could be because of an invalid username/password"
Applies to:Enterprise Manager for Exadata - Version 12.1.0.4.0 to 12.1.0.6.0 [Release 12.1]Exadata Database Machine X2-8 - Version All Versions and later Exadata X3-8 Hardware - Version All Versions and later Information in this document applies to any platform. SymptomsThe compute nodes on an Exadata X2-8 or X3-8 Rack are running EM 12c with the 12.1.0.6 version Exadata Plugin. The following errors are continuously reported for all compute node ILOM targets: IM summary: ILOM: Ilom : Status Metric evaluation error start -oracle.sysman.emSDK.agent.fetchlet.exception.FetchletException: - Could be because of an invalid username/password - at /opt/OracleHomes/agent_home/plugins/oracle.sysman.xa.agent.plugin_1...[19]... The ILOM /var/log/messages file may also contain the following messages: Jan 27 02:33:07 xxx-ilom syslogd 1.5.0: restart. Jan 27 02:34:07 xxx-ilom kernel: nf_conntrack: table full, dropping packet.
ChangesThe ILOM versions on the X2-8 or X3-8 rack have been upgraded from 3.0.16.20.e to 3.0.16.20.g CauseUnpublished Bug 21523493 - X4800-M2 ILOM resource problem This issue has only been reported on X2-8 or X3-8 Exadata Rack Models. SolutionThe fix for Bug 21523493 will be included in the next Exadata Plugin monthly Bundle Patch.
Workaround: Create a monitoring template and disable all the metrics on the ILOM target temporarily to stop the alerts. This template can then be applied to as many ILOM targets as needed. This involves no patching/code change and can be easily reversed when the ILOM patch is available.
1. From the Enterprise menu, select Monitoring and then Monitoring Templates. 2. Click Create. Enterprise Manager gives you the option of selecting either a specific target or a target type. Select Target > Click on the Search Icon > select any ILOM Target > click continue. 3. Enter the template information on the General Tab. 4. Click on the Metric Thresholds tab. To add metrics, click Add Metrics to Template. The Add Metrics to Template page displays as shown in the following graphic: 5. Click on Search Icon > select a ILOM Target. Under "Select the metrics whose settings you would like to be part of this monitoring template" choose Select All > Click Continue. 6. Remove "Warning Threshold" and "Critcal Threshold" for all the Metrics as empty Thresholds will disable alerts for that metric. Remove "Response" Metric > Click on OK. Now the Monitoring template is created: 7. To apply a template: From the Enterprise menu, select Monitoring > Monitoring Templates. Select the desired template from the table > Click Apply. Use Option "Template will completely replace all metric settings in the target" When the template is applied, all metrics and policies defined in the template will be applied to the target. Pre-existing target monitoring settings not defined in the template will be disabled: Metric thresholds will be set to NULL or blank. Policies will be disabled. This effectively eliminates alerts from these metrics and policies by clearing current severities and violations. Click on Add and select all the desired ILOM Targets > Click OK. For the Selected ILOM targets, all the Metric alerts generated due to this bug are now disabled by using Monitoring Templates as work around.
References<BUG:21523493> - X4800-M2 ILOM RESOURCE PROBLEMAttachments This solution has no attachment |
||||||||||||
|