Reference Guide

ping6

Description

Verifies if the destination IPv6 address is reachable from iDRAC or with the current

routing-table contents. A destination IPv6 address is required. Based on the current

routing-table contents, an ICMP echo packet is sent to the destination IPv6 address.

Verifies if the destination IPv6 address is reachable from CMC or with the current

routing-table contents. A destination IPv6 address is required. Based on the current

routing-table contents, an ICMP echo packet is sent to the destination IPv6 address.

To run this subcommand, you must have the Administrator privilege.

To run this subcommand, you must have Debug privilege.

Synopsis

racadm ping6 <ipv6address>

Input <ipv6address> — the IPv6 address of the remote endpoint to ping.

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

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

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