File Transfers

Copying Diagnostic Data to a Remote Host, USB Device, PC or UNIX Workstation

Syntax: copy crash-data [<slot-id master>] tftp <ip-address> <filename> [oobm] copy crash-data [<slot-id mm>] usb <filename>

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

where: slot=-ida - h, and retrieves the crash log or crash data from the processor on the module in the specified slot.

mmRetrieves 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 out-of-band management port, specifies that the transfer will be through the out-of-band management interface. (Default is transfer through the data interface.)

These commands copy the crash data content to a remote host, attached USB device, or to a serially connected PC or UNIX workstation. 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.

For example, to copy the switch’s crash data to a file in a PC:

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

Figure A-15. Example of Copying Switch Crash Data Content to a PC

Copying Crash Data with Redundant Management. When you are using redundant management, the copy crash-datacommand operates somewhat differently.

Syntax: copy crash-data [<slot-id> mm] tftp <ip-address> <filename> [oobm}

Copies both the active and standby management modules’ crash data to a user-specified file. If no parameter is specified, files from all modules (management and interface) are concatenated.

A-42