Unsolved
1 Rookie
•
3 Posts
0
128
December 9th, 2024 16:21
Built-in Appliance Share HTTPS
Help me understand, why can't i update remote machines. Both OME and remote iDRAC can reach each other by IP, TCP443 port. Remote iDRAC is up to date. Thanks for ideas!
OME 4.2.0 (Build 89)
Messages:
Running
Verifying if the device Service Tag is valid.
The device Service Tag is valid.
Starting communication with the device.
Performing the requested operation
Delete Job Queue has been attempted
Checking LC Service State
Checking Remote Services availability
Remote LC Services are ready.
Reset-iDRAC and/or Clear Job Completed
System Lockdown status is Unknown, continuing.
Checking Remote LC Services availability
Remote LC Services are ready now
performIDRACUpdate(): Attempting to initiate/stage iDRAC payload instance: DCIM:INSTALLED#iDRAC.Embedded.1-1#IDRACinfo
Initiated Status check for Job ID : JID_337859696093
Job state for JID_337859696093 is NEW
Job state for JID_337859696093 is DOWNLOADING
Job state for JID_337859696093 is FAILED
Unable to update the Chassis firmware, communication with Chassis Management Controller/Management Module took more time than expected.
Task Failed. Completed With Errors.
No Events found!
Origin3k
4 Operator
4 Operator
•
2.2K Posts
0
December 9th, 2024 18:49
Well,
OME place a JOB within the iDRAC. The iDRAC than call back the OME to fetch the needed files by CIFS(this is the default) or by HTTPS.
The address of your OME instance is placed within the JOB infos and you can choose between DNS (ome.acme.local aka. YourCompany) or just IP. If you select DNS you need to be sure that the iDRAC can resolve the given FQHN of your OME.
We configure that HTTPS is used (easier for our Firewall management) and plain IP because we manage Servers outside of our "network" where we cant control the DNS.
Within an update Job you can choose a clear Existing Jobs and Reboot iDRAC first. Try that first because you can validate if the iDRAC execute these commands. Later just use "Clean Jobs".
If you get an "time out" than the iDRAC cant reach the OME instance.
Iam confused about the "...Chassis firmware...." because you talk about iDRAC and not a CMC.
Regards,
Joerg
DELL-Young E
Moderator
Moderator
•
4.8K Posts
0
December 10th, 2024 03:11
Hello the issue is with iDRAC fetching the files from OME. You can check iDRAC logs for download error.
https://dell.to/3VxO9f4
Respectfully,
grabavozas
1 Rookie
1 Rookie
•
3 Posts
0
December 10th, 2024 10:27
UPDATE:
everyting works with HTTPS and server FQDN (have domain name on external IP). Earlier tried CIFS and forwarding ports - did not work. Maybe remote server gets inner network OME IP (192.x.x.x)?
Origin3k
4 Operator
4 Operator
•
2.2K Posts
0
December 11th, 2024 23:02
Youre welcome
DELL-Young E
Moderator
Moderator
•
4.8K Posts
0
December 12th, 2024 06:24
Hello you have to to make sure that all the ports are open specifically from iDRAC to OME. Your system is OME, as long as you have any server in warranty you can open the case and your region support can do a packet capture to see if iDRAC packets are reaching OME appliance.
Respectfully,