CLI Guide

Example
Pinging 2011:de11:bdc:194::31 from 2011:de11:bdc:194::101 with 32 bytes of
data:
Reply from 2011:de11:bdc:194::31: time<1ms
Reply from 2011:de11:bdc:194::31: time<1ms
Reply from 2011:de11:bdc:194::31: time<1ms
Reply from 2011:de11:bdc:194::31: time<1ms
Ping statistics for 2011:de11:bdc:194::31:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
RACADM Proxy
Table 71. Details of RACADM Proxy
Description
On the PowerEdge FX2/FX2s systems, you can manage the
compute sleds and CMC using
the iDRAC’s RACADM Proxy feature
that redirects commands from iDRAC to CMC. You
can return the CMC response to local or remote RACADM.to
access the CMC configuration and reporting
features without placing the CMC on the management network.
The CMC configuration commands are supported through local
proxy when local configuration is enabled on iDRAC.
NOTE: Local racadm and local racadm proxy runs with
root user privilege.
Synopsis
Local RACADM proxy usage
racadm <CMC racadm subcommand> --proxy
Remote RACADM proxy usage
racadm <CMC racadm subcommand> -u
<username> -p <password> -r <idrac-ip
connected to cmc> --proxy
NOTE:
• The attribute racadm getconfig -g
cfgractuning -o
cfgRacTuneChassisMgmtAtServer must be set as
non-zero in CMC.
• The attribute racadm get
system.ChassisControl.ChassisManagementMo
nitoring attribute must be enabled in iDRAC.
• --proxy must be entered at the end of the
command.
• Table 72. The root privilege is the default privilege for
Local RACADM proxy.
Required CMC Privilege
for an operation
Required iDrac Privilege
for proxy operation
CMC Login User Login
Chassis Configuration
Administrator
Configure
96 RACADM Subcommand Details