Unsolved

This post is more than 5 years old

1 Rookie

 • 

49 Posts

8927

April 12th, 2013 14:00

Incorrect Package

I'm attempting to push out a DRAC update for a M710HD to go from 3.21 to 3.50.  Reviewing the system update logs, it's copying the package "ESM_Firmware_C1GG0_WN32_3.50_A00.EXE" which is the Windows update utility.  This device is running ESXi and I'm pushing the update via the iDRAC method.  Why would it be downloading the incorrect update package?

April 16th, 2013 01:00

Hi,

Thanks for the post.

When you perform System Update task using iDRAC method it will always download a windows
packages. IDRAC update mode is independent of OS.

The package you are seeing is not an invalid package :    (ESM_Firmware_C1GG0_WN32_3.50_A00.EXE)

Thanks,

Nitin

 

1 Rookie

 • 

49 Posts

April 16th, 2013 08:00

Ok, well in that case why did it fail?  Is 3.21 not new enough for the iDRAC update method to work?

327 Posts

April 16th, 2013 10:00

Looks like the firmware update was successful as per this job: JID_001343850494

If you see an update fail in OME, please run the above command and share the results. This will give us more info on the error that happened.

327 Posts

April 16th, 2013 10:00

Failure could be attributed to various reasons. Downloading wrong package usually does not happen.

What is the iDRAC and LC firmware version on M710HD ?

Please run this command from OME system (from OS command prompt) to check job status and share the results:

winrm e cimv2/root/dcim/DCIM_LifecycleJob -u:username -p:password -SkipCNcheck -SkipCAcheck -r:https://iDRAC IPAddress/wsman:443 -auth:basic -encoding:utf-8

Provide actual values for username, password and iDRAC IP Address in the above command syntax.

1 Rookie

 • 

49 Posts

April 16th, 2013 10:00

The DRAC firmware level was 3.21 and the LC Firmware is 1.5.0.672.  After the OME failure I manually updated the DRAC to 3.5 so I'm not sure the command will help, but the output is below.

DCIM_LifecycleJob

   Caption

   CommunicationStatus

   DeleteOnCompletion

   Description

   DetailedStatus

   ElapsedTime

   ElementName

   ErrorCode

   ErrorDescription

   HealthState

   InstallDate

   InstanceID = JID_CLEARALL

   JobRunTimes

   JobStartTime = TIME_NA

   JobState

   JobStatus = Pending

   JobUntilTime = TIME_NA

   LocalOrUtcTime

   Message = NA

   MessageArguments

   MessageID = NA

   Name = CLEARALL

   Notify

   OperatingStatus

   OtherRecoveryAction

   Owner

   PercentComplete = 0

   PrimaryStatus

   Priority

   RecoveryAction

   RunDay

   RunDayOfWeek

   RunMonth

   RunStartInterval

   ScheduledStartTime

   StartTime

   Status

   TimeBeforeRemoval

   TimeOfLastStateChange

   TimeSubmitted

   UntilTime

DCIM_LifecycleJob

   Caption

   CommunicationStatus

   DeleteOnCompletion

   Description

   DetailedStatus

   ElapsedTime

   ElementName

   ErrorCode

   ErrorDescription

   HealthState

   InstallDate

   InstanceID = JID_001343850494

   JobRunTimes

   JobStartTime = 20191010101010

   JobState

   JobStatus = COMPLETED

   JobUntilTime = 2009:8:11

   LocalOrUtcTime

   Message = The command was successful

   MessageArguments

   MessageID = LC001

   Name = LC Config

   Notify

   OperatingStatus

   OtherRecoveryAction

   Owner

   PercentComplete = NA

   PrimaryStatus

   Priority

   RecoveryAction

   RunDay

   RunDayOfWeek

   RunMonth

   RunStartInterval

   ScheduledStartTime

   StartTime

   Status

   TimeBeforeRemoval

   TimeOfLastStateChange

   TimeSubmitted

   UntilTime

1 Rookie

 • 

49 Posts

April 16th, 2013 12:00

Yeah the success was from a manual update I did after the failure.  I'll be sure to run the command in the future after failures.

Thanks

No Events found!

Top