Filter
Top Products
5. Collecting Failure Information
144
5.2 Transferring Files for Maintenance Information
This section describes how to transfer log information or dump information automatically stored when failure occurred
while operating to the console or remote operation terminal. Three commands are available, that is, ftp, zmodem
[IP8800/S3600] [IP8800/S2400], and show tech-support. Maintenance information includes the following
items.
Table 5-2: Maintenance Information
No. Item Storage Location and File Name File Transfer
Format for ftp
Command
1 Dump information file
created when system
restarts
/dump0/rmdump
Delete the file after transfer.
binary
2 Dump information file
created when BSU
failure occurs
[IP8800/S6700]
/usr/var/hardware/bsu**.*** in the active or standby system where the failure
occurs (In Ver.10.5 or earlier, /dump0/bsu**.***)
**: BSU number of the faulty BSU
***: Serial number assigned from when dump was collected. Up to two files,
oldest and latest files, are stored.
Delete the file after transfer.
binary
3 BSU dump information
file created when the
dump bsu command
is executed
[IP8800/S6700]
/dump0/bsu**.cmd in the active or standby system where the command is
executed
**: BSU number of the specified BSU
Delete the file after transfer.
binary
4 Dump information file
created when PSP
failure occurs
[IP8800/S6300]
• /usr/var/hardware/psp**.*** in the active or standby system where the failure
occurs (In Ver.10.5 or earlier, /dump0/psp**.***)
(The information is stored in above location in the active system even if the
failure occurred in the standby PSP. Confirm whether dump information was
collected in the active or standby system according to the file name.)
**: If PSP where the failure occurred is MSU1, 01 is indicated. If PSP where
the failure occurred is MSU2, 02 is indicated.
***: Serial number assigned from when dump was collected. Up to two files,
the oldest and latest files are stored.
• /dump0/rmdump in the system where the failure occurs
(The information is collected simultaneously. If the failure occurred in the
standby PSP, it is collected in the standby system.)
Delete the file after transfer.
binary
5 PSP dump information
file created when the
dump psp command
is executed
[IP8800/S6300]
/usr/var/hardware/psp**.*** in the active or standby system where the command
is executed (In Ver.10.5 or earlier, /dump0/psp**.cmd)
**: If specified PSP is MSU1, 01 is indicated. If specified PSP is MSU2, 02 is
indicated. Confirm whether dump information was collected in the active or
standby system according to the file name.
***: Serial number assigned from when dump was collected. Up to two files, the
oldest and latest files are stored.
Delete the file after transfer.
binary
6 Dump information file
created when NIF
failure occurs
[IP8800/S6700]
[IP8800/S6600]
[IP8800/S6300]
/usr/var/hardware/nif**.*** in the active system (In Ver.10.5 or earlier, /dump0/
nif**.***)
**: NIF number of the faulty NIF
***: Serial number assigned from when dump was collected. Up to two files, the
oldest and latest files, are stored.
Delete the file after transfer.
binary