
A-35
File Transfers
Copying Diagnostic Data to a Remote Host, USB Device, PC or UNIX Workstation
Copying Crash Data with Redundant Management.
When you are using
redundant management, the
copy crash-data
command operates somewhat
differently.
Copying Crash Log Data Content to a Destination Device
For example, to copy the Crash Log for slot C to a file in a PC connected to
the switch:
Syntax:
copy crash-data [<
slot-id
> | mm] tftp <
ip-address
> <
filename
>
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.
slot-id:
retrieves the crash data from the module in the
specified slot.
mm:
retrieves the crash data from both management modules
and concatenates them.
Syntax:
copy crash-log [<
slot-id
| master>] tftp <
ip-address>
<filepath and filename
>
copy crash-log [<
slot-id
| master>] usb
<filename
>
copy crash-log [<
slot-id
| master>] xmodem
where:
slot-id
=
a
-
h
,
and retrieves the crash log from
the processor on the module in the specified slot.
master
Retrieves the crash log from the switch’s
chassis processor. When master is specified,
crash files from both management modules are
copied.
These commands copy the Crash Log 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
master switch information. If you do not specify either, the
command defaults to the master data.
3500-5400-6200-8200-MCG-Jan08-K_13_01.book Page 35 Monday, January 28, 2008 10:04 AM