Home > Workload Solutions > Oracle > Guides > User Guide—Dell Plug-in for Oracle Enterprise Manager > Troubleshooting
You may encounter configuration or behavior issues when working with the Dell Plug-in for Oracle EM. This section provides information required to troubleshoot common issues.
The Dell Plug-in for Oracle EM log files can be found on the local system of the OMA. Depending on the installation location of the OMA, the logs will be located in the following location:
[OMA_HOME] /plugins/dell.em.ome.agent.plugin_13.5.2.12.0/scripts/logs
There will be two types of log files in this directory, a plug-in target trace log and a target discovery log.
Log File | Description |
Discovery Log | Use this log to diagnose problems that may have occurred during the discovery process. |
Trace Log | This log is the main event-tracing log for the plug-in, specific to each target. The log file is named according to its host target. |
The Dell Plug-in for Oracle EM trace log file may also be viewed through the Oracle Enterprise Manager Cloud Control web console.
The following steps describe the steps to view the plug-in logs.
When users navigate through the tree view at left side of Dell OpenManage Enterprise target MPCUI page, it may show devices with no data. To enable data collection for the device sub-targets of the OpenManage target, each device sub-target must be promoted within the Oracle EM Cloud Control. Use the following steps to resolve this issue:
Note: The time between the target being promoted and data for the target returning depends on the configured collection interval in OMA.
There are several reasons a Dell target may have a down status. This is most often caused by a configuration error while adding the target. Ensure that you have verified all credentials that are used to connect to the Dell OpenManage Enterprise or Dell PowerFlex gateway when configuring the respective targets. If any of these credentials are incorrect or is changed /is updated on OpenManage Enterprise or PowerFlex gateway and not changed in Oracle EM target configuration, the target will go into a down status until rectified.
The Dell Plug-in for Oracle EM is designed to monitor an OpenManage environment where each device has a unique device name. Issues may arise if devices in the environment have duplicate names. Common issues include no status for devices, plug-in reports that devices are not promoted, or a display error in All Metrics describing that the Result has repeating key value.
Contact your administrator to modify if there are multiple devices with matching device names. After the device names have been modified, remove the device targets that have been modified and run the auto discovery process for the plug-in. The auto discovery process will find the newly named devices that are available for promotion.
Similarly, for PowerFlex target, it is expected each SDC has unique name matching to host target name in Oracle EM.
The Dell Plug-in 2.0 has a new validation health script added to validate the plug-in deployment status and its connectivity to PowerFlex targets.
This is a health validation tool to generate reports that can be shared with Dell support in case you face any issues with Dell PowerFlex targets of Dell Plug-in. This includes a health script to validate the deployment status of the plug-in v13.5.2.12.0 and the connectivity to the PowerFlex target.
The script, Dell_PowerFlex_Oracle EMTarget_HealthCheck.sh is available as part of plug-in and will be deployed to the agent’s plugin folder at
Agent_base/agent_13.5.0.0.0/plugins/ dell.em.xome.agent.plugin_13.5.2.x.x/scripts
E.g.: /home/oracle/agent/agent_13.5.0.0.0/plugins/dell.em.xome.agent.plugin_13.5.2.x.x/scripts/ Dell_PowerFlex_OracleEMTarget_HealthCheck.sh
This script will complete the following checks:
The output of the script will be a report that the customer can share with Dell support to understand the status of the Oracle EM plug-in.
Note: Supported OMA version:13.5.0.0.0
The script can be performed on either of the following:
chmod 755 Dell_PowerFlex_OracleEMTarget_HealthCheck.sh
>> . oraenv
>> . oraenv
Use the following steps when OMS and OMA which has the Dell plug-in is on single host.
Steps to run the script
Run the script using the following command:
./ Dell_PowerFlex_OracleEMTarget_HealthCheck.sh
When running the script on an OMA where plug-in is deployed, and the agent is not on the OMS host, follow below steps.
Note: If the Dell Plug-in for Oracle EM v 13.5.2.12.0 is not deployed then the script will be terminated and the report is generate
Note: If the discovery component is not available, a warning is displayed.This component is part of Dell Plug-in but does not directly affect the PowerFlex targets.
Note: If the user gives Y without even completing the steps, the following part of the script may encounter this error. Rest of the script will perform correctly.
oracle is not in the sudoers file. This incident will be reported.
Note: If the user gives Y without even completing the steps, the following part of the script may encounter this error. Rest of the script will run correctly.
oracle is not in the sudoers file. This incident will be reported.
Note: Incase the Dell Plug-in for Oracle EM v 13.5.2.12.0 is not deployed then the script will be terminated and the report is generated.