CLI Guide

Table 112. Details of traceroute (continued)
Synopsis
racadm traceroute <IPv4 address>
Input IPv4 — Specifies IPv4 address.
Output
traceroute to 192.168.0.1 (192.168.0.1), 30 hops max, 40 byte packets
1 192.168.0.1 (192.168.0.1) 0.801 ms 0.246 ms 0.253 ms
traceroute6
Table 113. Details of traceroute6
Description Traces the network path of routers as the packets traverse from the system to a destination IPv6 address.
To run this subcommand, you must have the Execute Diagnostic Commands permission.
Synopsis
racadm traceroute6 <IPv6address>
Input <IPv6address> – Specifies IPv6 address.
Output
traceroute to fd01::1 (fd01::1) from fd01::3,
30 hops max, 16 byte packets
1 fd01::1 (fd01::1) 14.324 ms 0.26 ms 0.244 ms
update
Table 114. Details of update subcommand
Description
Allows you to update the firmware of devices on the server. The supported firmware image file types are:
● .exe — Windows-based Dell Update Package (DUP)
● .d9
● .pm
● .sc
The supported catalog files are:
● .xml
● xml.gzip
NOTE:
● Updating the platforms from the repository is not supported for IPv6.
● The firmware update through FTP has a limitation of file name up to 64 characters.
● Depending on the network traffic, the HTTP packet transfer may fail if you perform update
operation from a remote RACADM through a local share. In such cases, retry the operation. If the
issue persists, use remote RACADM with the CIFS or NFS share.
● The supported share types for single file or DUP updates are CIFS, NFS, HTTP, and HTTPS. For
Repository updates, the supported share types are CIFS, NFS, FTP, TFTP, and HTTP.
● When a port number is appended to an IP address for firmware update, the job fails with an internal
error.
RACADM Subcommand Details 157