Sounds like a pretty awful oversight from Dell.   What about racadm get -f /tmp/somefile.out It takes like 3 minutes to execute.  And it doesn't write to standard out.  Yuck.  But that seems to retrieve all the parameters too me, even if it does force me to work with a separate file. Im working on a script to bring our racadm configs into conformance with one another and I would rather only update what needs updating than push ever setting given how unbearably slow every interaction with racadm already is. So it's a big help to retrieve all config first so I can inspect it before sending set commands. Too bad I can't batch those set commands too.
Racadm is slow and I want to use it in a script to check and fix the list if idrac users. I can run racadm get racadm -r server -u root -p pass get iDRAC.Users.1 racadm get racadm -r server -u root -p pass get iDRAC.Users.2 racadm get racadm -r server -u root -p pass get iDRAC.Users.3 racadm get racadm -r server -u root -p pass get iDRAC.Users.4 racadm get racadm -r server -u root -p pass get iDRAC.Users.5 racadm get racadm -r server -u root -p pass get iDRAC.Users.6 racadm get racadm -r server -u root -p pass get iDRAC.Users.7 etc... and wait for each one to complete. But can I just run racadm get racadm -r server -u root -p pass get iDRAC.Users.* to get all of the user data in one command?  Why not?  Or what is the right syntax?
Racadm GET wildcard