Filter
Top Products
5. Collecting Failure Information
147
(3) Transferring failure backup information files to the remote operation terminal
Figure 5-4: Transferring the Failure Backup Information File to the Remote Operation Terminal
> cd /usr/var/core/
> ls <-------------------------1
nimd.core nodeInit.core
> ftp 192.168.0.1 <--------------2
Connected to 192.168.0.1.
220 FTP server (Version 6.00LS) ready.
Name (192.168.0.1:staff1): staff1
331 Password required for staff1.
Password:
230 User staff1 logged in.
Remote system type is UNIX.
Using binary mode to transfer files.
ftp> prompt <--------------3
Interactive mode off.
ftp> bin <--------------4
200 Type set to I.
ftp>cd <target directory> <--------------5
250 CMD command successful.
ftp> mput *.core <--------------6
local: nimd.core remote: nimd.core
200 EPRT command successful.
150 Opening BINARY mode data connection for 'nimd.core'.
100% |**********************************************************************|
272 KB 1.12 MB/s 00:00 ETA
226 Transfer complete.
278528 bytes sent in 00:00 (884.85 KB/s)
local: nodeInit.core remote: nodeInit.core
200 EPRT command successful.
150 Opening BINARY mode data connection for 'nodeInit.core'.
100% |**********************************************************************|
1476 KB 1.40 MB/s 00:00 ETA
226 Transfer complete.
1511424 bytes sent in 00:01 (1.33 MB/s)
ftp> bye
221 Goodbye.
>
1. Check if the failure backup information file exists. If no file exists, exit without any action.
2. Specify the target terminal address.
3. Change the interaction mode.
4. Enter binary mode.*
5. Specify a transfer target directory.
6. Transfer the failure backup information file.
*
Be sure to transfer the failure backup information file in binary mode. The accurate information will not be obtained
if the failure backup information file is transferred in ASCII mode.