Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[QUESTION]: Firmware updates on iDRAC 8 #632

Closed
spear-dev opened this issue Mar 12, 2024 · 4 comments
Closed

[QUESTION]: Firmware updates on iDRAC 8 #632

spear-dev opened this issue Mar 12, 2024 · 4 comments
Labels
type/question Further information is requested

Comments

@spear-dev
Copy link

spear-dev commented Mar 12, 2024

How can the team help?

Hi,
We need to support Dell R630s, R640s, and R650s. I am using the redfish_firmware module for the R640s and R650s (iDRAC 9). Is there a alternative module that I can use for the R630 (iDRAC 8) ? The other modules seem want a Catalog file, but we just have the .exe file shared VIA an HTTP server.

Details: ?

@spear-dev spear-dev added the type/question Further information is requested label Mar 12, 2024
@anupamaloke
Copy link
Contributor

@spear-dev, recommendation would be to use the catalog based firmware update as that is the optimum way to update component firmware on iDRAC without worrying about scheduling the updates in required order with minimum server reboots. You can create a firmware repository using Dell Repository Manager. It can be installed on your linux or windows machine and can be used to create a catalog file and repository that you can host on your HTTP web server. Best part is that you don't have to create multiple repository for all your servers (R630, R640 and R650).

If you still want to go via the .exe route, then I guess the only way would be to use the 'racadm' commands with ansible ssh or directly call the WS-Man APIs using ansible.builtin.uri modules (see iDRAC8 Linux WS-Man Guide )

@spear-dev
Copy link
Author

@anupamaloke thank you for the recommendation. We will try those options out.

@anupamaloke
Copy link
Contributor

@spear-dev, please let us know whether we can close this now.

@anupamaloke
Copy link
Contributor

@spear-dev, I am closing this issue now. Please feel free to reopen a new issue(s) if you have any questions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants