Last updated on OCTOBER 14, 2016
Applies to:Enterprise Manager Ops Center - Version 11g to 12c (12.1) [Release 11.0 to 12.0]
Information in this document applies to any platform.
Customer has T4 servers with older firmware (8.1.4f or 8.2.0a). They attempt to use OpsCenter 12cU1 to flash the firmware on these servers.
The servers have a dedicated ILOM account "admin" with 'test' permissions (same as the default 'root' LOM ID)
Ops Center is configured via SSH to connect to "admin". The servers are reporting in OpsCenter and can see the hardware information.
They do use the default prompt for SC (sc>) (rules out a certain bug I ran into in the past)
Tried logging into the ILOM to issue a "reset /SP" then waited about 5 minutes and tried the fw update
Customer has the firmware downloaded - configured from Oracle and residing in local library of firmware.
They select "update firmware", select the 8_2_0_f version for the T4-1 server, and apply it to one of the servers, and schedule the job to run now.
The host OS is then shut down (as expected), and the server is powered off.
The next message they see is a fault in the job.
Looking at the task, it says the download has succeeded, but then there is an 'exception' and a timeout after 1800 seconds.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms