236
21.3 How to obtain SP failure information
This section explains how to obtain failure information for the SP.
To obtain log data:
1.
Log in to the SP on which the failure occurred.
1-1. Go from CSU administrator mode to SP administrator mode.
1-2. If CSU administrator mode cannot be switched to SP administrator mode:
1-2-1. Execute the
dump nif
command from the CSU.
Obtain the data dumped by the above command as error information.
1-2-2. Restart the SP from the CSU. (See 21.4.)
1-2-3. After the recovery, perform step 2 and after to collect the failure data.
2.
Collect the
tech-support
file.
SP01# show tech-support
3.
Check if the remote server can be connected to.
SP01# ping
remote-server-address
3-1. If the remote server can be connected to:
Transfer the failure information to the remote server.
SPs support the following protocols for file transfers:
-
tftp (Trivial File Transfer Protocol) See 21.3.1
-
ftp (File Transfer Protocol) See 21.3.2
Select the transfer method appropriate for the remote server.
3-2. If the remote server cannot be connected to (see 21.3.3):
Save the file in a local non-volatile data area, make it possible to connect to
the remote server by restarting the server or rolling back the logical module,
and then obtain failure information from the remote server by using FTP.
21.3.1 Transferring failure information by using TFTP
This section explains how to transfer failure information to the remote server by using TFTP
(Trivial File Transfer Protocol).
To transfer failure information to the remote server by using TFTP:
1.
Start the TFTP server on the remote server.
2.
Execute the following command to transfer failure information to the remote device:
SP01# export dump-file tftp://192.168.1.1/dump-data
Dump-file creating start.
WARNING: exporting dump file...
exporting to file tftp://192.168.1.1/dump-data
Sent 10942577 bytes in 5.9 seconds
Note:
dump-data
indicates the failure information to be transferred to the remote
server.
Summary of Contents for GX1000-SMC013X
Page 94: ...94 5 Configuration Guide 5 1 Base Software Configuration Guide ...
Page 105: ...105 7 Access Lists 7 1 Access lists ...
Page 153: ...153 8 Policy Based Switching 8 1 Policy based switching ...
Page 165: ...165 9 Policy Based Routing 9 1 Policy based routing ...
Page 177: ...177 Figure 10 1 Overview of mode transitions ...
Page 213: ...213 17 MIB Reference 17 1 Private MIBs 17 2 Supported MIB Traps ...
Page 229: ...229 H W BOOT 11 44 MISC 1 0 SPCT 0 34 10 The updating of the SP files is finished ...
Page 451: ...451 28 Additional Information ...