Copying diagnostic data to a remote host, USB device, PC or UNIX workstation

You can use the CLI to copy the following types of switch data to a text file in a destination device:

Command output

Sends the output of a switch CLI command as a file on the destination device.

Event log

Copies the switch's Event Log into a file on the destination device.

Crash data

Software-specific data useful for determining the reason for a system crash.

Crash log

Processor-specific operating data useful for determining the reason for a system crash.

Flight data recorder (FDR) logs

Information that is “interesting” at the time of the crash, as well as when the switch is not performing correctly but has not crashed.

The destination device and copy method options are as follows (CLI keyword is in bold):

  • Remote Host via TFTP.

  • Physically connected USB flash drive via the switch's USB port.

  • Serially connected PC or UNIX workstation via Xmodem.

Copying command output to a destination device (CLI)

Syntax:

copy command-output <"cli-command"> tftp <ip-address> <filepath-filename>

copy command-output <"cli-command"> usb <filename>

copy command-output <"cli-command"> xmodem

These commands direct the displayed output of a CLI command to a remote host, or to a serially connected PC or UNIX workstation.

These commands direct the displayed output of a CLI command to a remote host, attached USB device, or to a serially connected PC or UNIX workstation.

Example:

To use Xmodem to copy the output of show config to a serially connected PC:

Sending command output to a file on an attached PC

Sending command output to a file on an attached PC

[NOTE: ]

NOTE: The command you specify must be enclosed in double quotation marks.


Copying Event Log output to a destination device (CLI)

Syntax:

copy event-log tftp <ip-address> <filepath_filename>

copy event-log usb <filename>

copy event-log xmodem <filename>

These commands copy the Event Log content to a remote host, or to a serially connected PC or UNIX workstation.

These commands copy the Event Log content to a remote host, attached USB device, or to a serially connected PC or UNIX workstation.

Example:

To copy the event log to a PC connected to the switch:

Sending event log content to a file on an attached PC

Sending event log content to a file on an attached PC

Copying crash data content to a destination device (CLI)

This command uses TFTP, USB, or Xmodem to copy the Crash Data content to a destination device. You can copy individual slot information or the management module’s switch information. If you do not specify either, the command defaults to the management function’s data.

Syntax:

copy crash-data [ <slot-id | master> ]tftp <ip-address> <filename>

copy crash-data [ <slot-id | mm> ]usb <filename>

copy crash-data [ <slot-id | mm> ]xmodem

These commands copy the crash data content to a remote host, attached USB device, or to a serially connected PC or UNIX workstation.

slot-id a - h—Retrieves the crash log or crash data from the processor on the module in the specified slot
mm Retrieves crash log or crash data from the switch's chassis processor. When "mm" is specified, crash files from both management modules are copied.
oobm For switches that have a separate OOBM port, specifies that the transfer is through the OOBM interface. (Default is transfer through the data interface.)

You can copy individual slot information or the management module (mm) switch information. If you do not specify either, the command defaults to the mm data.

To copy the switch's crash data to a file in a PC:

Copying switch crash data content to a PC

Switch(config)# copy crash-data xmodem pc
Press 'Enter' and start XMODEM on your host... 1



Transfer complete

1

At this point press [Enter] and start the Xmodem command sequence in your terminal emulator.