Exadata ILOMs Fail to Convert in 12c to 13c Target Conversion (Doc ID 2221329.1)

Last updated on JANUARY 13, 2017

Applies to:

Enterprise Manager for Exadata - Version 13.1.1.0.0 to 13.2.1.0.0 [Release 13.1 to 13.2]
Information in this document applies to any platform.

Symptoms

After updating the OMS from 12c to 13c Cloud Control, the Exadata Database Machine conversion from 12c to 13c target is failing on the node ILOMs conversion. 

The pop up window shows the title "Converting Targets - Completed Successfully", however the details Summary shows a list of ILOMs that failed to convert:

Summary
    Number of targets that failed to convert:N

      <ilom1_hostname>(Oracle Engineered System ILOM Server)
      <ilom2_hostname>(Oracle Engineered System ILOM Server)
      <ilom3_hostname>(Oracle Engineered System ILOM Server)
      ...
      <ilomN_hostname>(Oracle Engineered System ILOM Server)

 

Or there is a pop up window with a timeout error similar to: 

<ilom_hostname>:[ConnectTest;Error: A communication error occurred executing command on target. Target: "ilom-ssh://<ilom_hostname>" Metric Collection: "Real-Time Metric Request" Command: [version] Timeout: 1700 seconds.]

Changes

Recently upgraded the OMS to 13c but left the Exadata Database Machine as a 12c target.  Now attempting to convert to 13c target.

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