There are two things which i would like to suggest:.
First, i would recomment that you use the system update feature in OpenManage Essentials 1.1 to update the firmware of DRAC. You can update the firmware of iDRAC either by choosing OMSA method, when you are creating the system update task or you can also use the iDRAC method of system update.
Second,this error message is thrown when the racadm command is not able to connet to the RAC. Please make sure that you are using iDRAC IP in the argument. Also, you need to make sure that remote racadm is enabled on the iDRAC for this command to work on the iDRAC
iDRAC5 firmware version 1.20 and I am trying to upgrade it to 1.60.
This device is not getting discovered and is showing as unknown even though all settings in the DRAC are correct to allow so I thought maybe it was due to the FW being so old.
I don't have the ability to install OMSA on this and most of our servers due to the servers being in used in a way that updates that OMSA would install to run would conflict with the functionality of the services running on the production servers.
Welcome to this thread. Actually, if iDRAC is in a correct state, there are no reasons for update to fail. So, one thing is to check is the output of the following command once you start the system update task. As soon as you start the system update task, please execute this command from you command prompt every 2-3 secs. Do run the command as administrator.
Replace the username, password and iDRAC IP with the correct details. It will show if the package is downloaded to the lifecycle controller or not.
If this does not work, please restart the server, press F10, enter system services, save and then EXIT. This will make the lifecycle go to a state from where system update should work properly.
Also, you can enable CSIOR using the following racadm command:
C:\rac>racadm –r –u –p set
However, inventory will be collected only at boot up. But again, this command is only for iDRAC7. For iDRAC6, this needs to be done from the system services option by pressing F10.
cameronredux
2 Intern
•
615 Posts
0
January 16th, 2013 09:00
Excellent!
I will try this today.
lakshmi - Dell
21 Posts
0
January 16th, 2013 09:00
Hi Cameron,
Firmware update using generic command line at OME works fine
For Update :
Command : C:\Program Files (x86)\Dell\SysMgt\rac5\racadm.exe
Argument : -r $RAC_IP -u $USERNAME -p $PASSWORD fwupdate -g -u -a -d
To get the Status :
Argument : -r $RAC_IP -u $USERNAME -p $PASSWORD fwupdate –s
One can write a batch file/Power Shell script to continuously retrieve the status.
Update process will take 5-7 min.
Lakshmi.
cameronredux
2 Intern
•
615 Posts
0
January 16th, 2013 16:00
When I try it I get this error:
Results: Exit code:1.
Output from command (stderr): ERROR: Unable to connect to RAC at specified IP address.
What port does this function use?
DELL-Pupul M
2 Intern
•
1K Posts
0
January 17th, 2013 04:00
Hi Cameron,
There are two things which i would like to suggest:.
First, i would recomment that you use the system update feature in OpenManage Essentials 1.1 to update the firmware of DRAC. You can update the firmware of iDRAC either by choosing OMSA method, when you are creating the system update task or you can also use the iDRAC method of system update.
Second,this error message is thrown when the racadm command is not able to connet to the RAC. Please make sure that you are using iDRAC IP in the argument. Also, you need to make sure that remote racadm is enabled on the iDRAC for this command to work on the iDRAC
.
cameronredux
2 Intern
•
615 Posts
0
January 17th, 2013 08:00
Thank you for your assistance!
In the System Update section of OME 1.1.1 I see no way to update any DRAC firmware.
The only things that I can update there are firmware for NICs, PERC controllers etc.
My catalog is the latest.
I also see not way to make a system update task.
The only task creation area I can see in OME is in remote tasks.
I am definitely using the DRAC IP.
I only connect to DRACs from OME.
Remote Racadm is enabled on the target DRAC.
Any other ideas on what I can do to troubleshoot the connectivity issue?
DELL-Rob C
3 Apprentice
•
2.8K Posts
0
January 17th, 2013 09:00
cameron,
What is the current f/w version on your iDrac 7?
Also, can you confirm you have discovered and inventoried them via WS-Man?
Do you have OMSA installed on these servers?
Thanks,
Rob
btw, patch whitepapers are on www.delltechcenter.com/ome, but you may already be reviewing those.
cameronredux
2 Intern
•
615 Posts
0
January 17th, 2013 09:00
It's not a iDRAC7. It's old :)
iDRAC5 firmware version 1.20 and I am trying to upgrade it to 1.60.
This device is not getting discovered and is showing as unknown even though all settings in the DRAC are correct to allow so I thought maybe it was due to the FW being so old.
I don't have the ability to install OMSA on this and most of our servers due to the servers being in used in a way that updates that OMSA would install to run would conflict with the functionality of the services running on the production servers.
DELL-Raj S
327 Posts
0
January 17th, 2013 11:00
Is it a 9G server ? What is the server model ?
Please note that deploying updates via iDRAC is only supported on 11G and 12G servers.
For 9G server, if OMSA cannot be installed on the server, you will probably need to follow the steps outlined by Lakshmi above.
To troubleshoot this error:
Output from command (stderr): ERROR: Unable to connect to RAC at specified IP address.
Run this command from OS command prompt on OME server:
~Program Files (x86)\Dell\SysMgt\rac5\racadm.exe -r -u -p getsysinfo
If the above command returns the same error, try an RMCP ping on the RAC IP Address and check if it can be eached from OME server.
Remote racadm utility uses https protocol to send commands to DRAC 5 and requires port 443 enabled. Here is the link to DRAC 5 ports (page 16):
www.dell.com/.../DellRemoteAccessController5Security.Pdf
Thanks,
Raj Shresta
cameronredux
2 Intern
•
615 Posts
0
January 17th, 2013 13:00
Yes it's a 1950 :(
Only a few left in our fleet.
That command run from powershell returns the data about the server and rac info so that part is working.
I am going to try the non OME method now :)
dilipnet
2 Intern
•
153 Posts
0
August 2nd, 2013 04:00
Hi,
What are the possible scenario's to failed update via iDRAC
/Dilipnet
DELL-Pupul M
2 Intern
•
1K Posts
0
August 2nd, 2013 05:00
Hi Dilip,
Welcome to this thread. Actually, if iDRAC is in a correct state, there are no reasons for update to fail. So, one thing is to check is the output of the following command once you start the system update task. As soon as you start the system update task, please execute this command from you command prompt every 2-3 secs. Do run the command as administrator.
winrm get cimv2/root/dcim/DCIM_LifecycleJob?InstanceID= -r:https:// /wsman:443 -u: -p: -SkipCNCheck -SkipCACHeck -a:basic -encoding:utf-8
Replace the username, password and iDRAC IP with the correct details. It will show if the package is downloaded to the lifecycle controller or not.
If this does not work, please restart the server, press F10, enter system services, save and then EXIT. This will make the lifecycle go to a state from where system update should work properly.
Also, you can enable CSIOR using the following racadm command:
C:\rac>racadm –r –u –p set
However, inventory will be collected only at boot up. But again, this command is only for iDRAC7. For iDRAC6, this needs to be done from the system services option by pressing F10.
Hope this helps.
dilipnet
2 Intern
•
153 Posts
0
August 2nd, 2013 06:00
Hi Pupul,
it's okay np.
Please find the output
DCIM_LifecycleJob
InstanceID = JID_CLEARALL
JobStartTime = TIME_NA
JobStatus = Pending
JobUntilTime = TIME_NA
Message
MessageID
Name = CLEARALL
PercentComplete = 0
DCIM_LifecycleJob
InstanceID = JID_001375455882
JobStartTime = TIME_NA
JobStatus = Downloading
JobUntilTime = TIME_NA
Message = Downloading package.
MessageID = RED003
Name = update:DCIM:INSTALLED:NONPCI:20137:1.70
PercentComplete = NA
DCIM_LifecycleJob
InstanceID = RID_001375455890
JobStartTime = TIME_NA
JobStatus = Pending Reboot
JobUntilTime = TIME_NA
Message = NA
MessageID = NA
Name = Reboot1
PercentComplete = NA
Regards
Dilip
DELL-Pupul M
2 Intern
•
1K Posts
0
August 2nd, 2013 06:00
Hi Dilip, Please execute this command. Extremely sorry for the inconvenience:
winrm e cimv2/root/dcim/DCIM_LifecycleJob -u: -p: -r:https:// /wsman:443 -SkipCNCheck -SkipCACheck -SkipRevocationCheck -auth:basic -encoding:utf-8
The other command is to get the status of the specific job.
dilipnet
2 Intern
•
153 Posts
0
August 2nd, 2013 06:00
F.Y.I
DCIM_LifecycleJob
InstanceID = JID_CLEARALL
JobStartTime = TIME_NA
JobStatus = Pending
JobUntilTime = TIME_NA
Message
MessageID
Name = CLEARALL
PercentComplete = 0
DCIM_LifecycleJob
InstanceID = JID_001375455882
JobStartTime = TIME_NA
JobStatus = Failed
JobUntilTime = TIME_NA
Message = Package verification failed.
MessageID = RED007
Name = update:DCIM:INSTALLED:NONPCI:20137:1.70
PercentComplete = NA
Regards
Dilip
dilipnet
2 Intern
•
153 Posts
0
August 2nd, 2013 06:00
Hi Pupul,
What is the JOB_ID to be specified ?
once I executed the above command without JOB_ID it returns the below output
"The system cannot find the file specified."
Press F10, enter system services and saved before execute the command.
Regards
Dilip