Reference Guide

cd
quit
• Example 2: racadm> get <press tab>
get
getconfig
getled
getniccfg
getraclog
getractime
getsel
getsensorinfo
getssninfo
getsvctag
getsysinfo
gettracelog
getversion
• Example 3:
racadm> getl<press tab>
racadm> getled <press enter> or <racadm getled>
LEDState: Not-Blinking
• Example 4:
racadm>> get bios.uefiBootSettings
BIOS.UefiBootSettings
BIOS.UefiBootSettings.UefiBootSeq
BIOS.UefiBootSettings.UefiPxeIpVersion
NOTE: In the RACADM autocomplete mode, some of the RACADM commands specific to certain server platforms may
not be available. In such scenarios, execute the RACADM command in the normal execution mode.
Lifecycle Controller Log
Lifecycle Controller logs provide the history of changes related to components installed on a managed system. You can also add
work notes to each log entry.
The following events and activities are logged:
• System events
• Storage devices
• Network devices
• Configuration
• Audit
• Updates
You can view and filter logs based on the category and severity level. You can also export and add a work note to a log event.
If you initiate configuration jobs using RACADM CLI or iDRAC web interface, the Lifecycle log captures the information about the
user, interface used, and the IP address of the system from which you initiate the job.
Supported RACADM Subcommands
The following table provides the list of RACADM subcommands and their corresponding interface support. For more information
about the RACADM subcommands including syntax and valid entries, see RACADM Subcommand Details.
Table 2. Supported RACADM Subcommands
Subcommand iDRAC on Blade Servers
Telnet/SSH/Serial Local RACADM Remote RACADM
autoupdatescheduler Yes Yes Yes
arp Yes Yes Yes
13