Skip to main content
Sign Out

Welcome to Dell

My Account
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Enjoy members-only rewards and discounts
  • Create and access a list of your products
  • Manage your Dell EMC sites, products, and product-level contacts using Company Administration.
Sign In Create an Account Dell Financial Services Premier Sign In Partner Program Sign In
Contact Us

Your Dell.com Carts

Integrated Dell Remote Access Controller 9 RACADM CLI Guide

PDF

Remote RACADM

NOTE:
  • By default, TLS version 1.0 is enabled on Windows 2012 R2 which is not supported on the Remote RACADM. Install the latest Windows update available, to updgrade TLS to version 1.1 or higher. Also, set the TLS version in the iDRAC.Webserver.TLSProtocol as appropriate. For more information about Windows update see, support.microsoft.com/en-us/help/3140245/update-to-enable-tls-1-1-and-tls-1-2-as-default-secure-protocols-in-wi
  • If Force Change of Password (FCP) feature is enabled, it is recommended to change the default password using SSH or iDRAC GUI. Changing the default password using Remote RACADM may not be successful. 
racadm -r <racIPAddr> -u <username> -p <password> <subcommand>
Example 
racadm -r 192.168.0.2 -u root -p xxxx getsysinfo 
Security Alert: Certificate is invalid - Certificate is not signed by Trusted Third Party Continuing execution.
NOTE:The following command does not display a security error: 
racadm -r 192.168.0.2 -u noble -p xxx getsysinfo --nocertwarn
The remote RACADM commands must link to the libssl library on the HOST, which corresponds to the version of OpenSSL package installed on the HOST. Perform the following steps to verify and link the library.

  • Check the openssl version installed in the HOST: 

    [root@localhost ~]# openssl
OpenSSL> version
OpenSSL 1.0.1e-fips 11 Feb 2013
OpenSSL>

  • Locate the openSSL libraries are in the HOST machine (/usr/lib64/ in case of RHEL), and to check the various versions of the libraries: 

    [root@localhost ~]# ls -l /usr/lib64/libssl*
-rwxr-xr-x. 1 root root 249368 Oct 15  2013 /usr/lib64/libssl3.so
lrwxrwxrwx. 1 root root     16 Oct 29  2014 /usr/lib64/libssl.so.10 -> libssl.so.1.0.1e
-rwxr-xr-x. 1 root root 439912 Sep 27  2013 /usr/lib64/libssl.so.1.0.1e

  • Link the library libssl.so using ln -s command to the appropriate OpenSSL version in the HOST: 

    [root@localhost ~]# ln -s /usr/lib64/libssl.so.1.0.1e /usr/lib64/libssl.so

  • Verify if the libssl.so soft linked to libssl.so.1.0.1e: 

    [root@localhost ~]# ls -l /usr/lib64/libssl*
-rwxr-xr-x. 1 root root 249368 Oct 15  2013 /usr/lib64/libssl3.so
lrwxrwxrwx. 1 root root     27 Aug 28 13:31 /usr/lib64/libssl.so -> /usr/lib64/libssl.so.1.0.1e
lrwxrwxrwx. 1 root root     16 Oct 29  2014 /usr/lib64/libssl.so.10 -> libssl.so.1.0.1e
-rwxr-xr-x. 1 root root 439912 Sep 27  2013 /usr/lib64/libssl.so.1.0.1e

Rate this content

Accurate
Useful
Easy to understand
Was this article helpful?
0/3000 characters
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please select whether the article was helpful or not.
  Comments cannot contain these special characters: <>()\