HP LTO5 Tape Drive
 
HP LTO3 Tape Drive
 
HP LTO4 Tape Drive
 

PLA-Support>Sun Systems>TAPE>Tape Hardware>SN-TP: OEM Drive and Library
 

Applies to:

Goal

HP Dione Log Extraction Procedure:
The Dione firmware maintains an internal record of the operations which it performs, which may be of use if incorrect behavior is suspected.
Note that because the log will continue to fill up all the time, it is important to retrieve it as soon as possible after the suspected point of failure.

Solution

Steps to Follow
Retrieval is a two-part process.
Firstly you must instruct Dione to dump its internal log into a format suitable for retrieval; then secondly you retrieve the log and store it in a file on the local system.

Pre 1.200 logs all have to be analyzed by HP, a case should be opened to:   GL-TSC-STO-COLLAB-OPEN_SYS_TAPE

From Dione-2 firmware 1.200 and onwards two logs are dumped, one has to be analyzed by HP the second, networklog.txt, is in human readable text format.

The steps to follow (assuming the default IP address of 10.0.0.1) are:

1.Log in to Dione using telnet, with username admin and password admin:
2.C:\> telnet 10.0.0.1 Dione Telnet Interface login: admin Password: admin
3.Instruct Dione to dump the log to an internal file: > query log
4.Tracelogs dumped should be output
5. Close the telnet session, and open an ftp session.
6.The login credentials are the same. > C:\> ftp 10.0.0.1
7. Ensure the transfer will be done in binary mode, and retrieve the tracelog file.
8. bin
9. get bank0.bin
10. Transfer complete should be output. Then quit.

Send the tracelog file bank0.bin to T3 for analysis.

From Dione-2 firmware release 1.200 onwards, a second log is also dumped in text format at step 2; this log records KMA connection activity.

To retrieve this log as well at step (4) above, after the bank0.bin transfer has completed, issue the command: get networklog.txt before closing the ftp connection.

Examination of the networklog file can be analyzed by the field and may help debug connectivity issues between Dione and the KMA.

Internal Comments
Example of networklog.txt file:
Example of a network issue, where both KMA's were not able to communicate to the drive, hence the SSL connect fails.

Dione Network event log
-----------------------
Firmware version : 1.200
Log extracted 0000:09:43.509 after power-on

hhhh:mm:ss.mmm  Event
--------------  --------------------------------------------------
0000:00:28.294 : Connect to port 3335
0000:00:28.295 :         on host 172.18.18.30
0000:00:44.528 : SSL Connect failed!  Error = 0x1 (1)
0000:00:44.537 : KMS Trace 0x208 (520)
0000:00:44.537 : KMS Trace 0x208 (520)
0000:00:44.538 : KMS Trace 0x208 (520)
0000:00:44.538 : KMS Trace 0x334 (820)
0000:00:44.543 : KMS Trace 0x207 (519)
0000:00:44.553 : Connect to port 3335
0000:00:44.554 :         on host 172.18.18.30
0000:00:58.791 : SSL Connect failed!  Error = 0x1 (1)
0000:00:58.800 : KMS Trace 0x208 (520)
0000:00:58.800 : KMS Trace 0x208 (520)
0000:00:58.800 : KMS Trace 0x208 (520)
0000:00:58.801 : KMS Trace 0x334 (820)
0000:00:58.802 : KMS Trace 0x207 (519)
0000:00:58.812 : Connect to port 3335
0000:00:58.813 :         on host 172.18.18.31
0000:01:12.911 : SSL Connect failed!  Error = 0x1 (1)
0000:01:12.920 : KMS Trace 0x208 (520)
0000:01:12.920 : KMS Trace 0x208 (520)
0000:01:12.920 : KMS Trace 0x208 (520)
0000:01:12.920 : KMS Trace 0x334 (820)
0000:01:13.351 : KMS Trace 0x207 (519)
0000:08:41.738 : Connect to port 3335
0000:08:41.739 :         on host 172.18.18.30
0000:08:55.833 : SSL Connect failed!  Error = 0x1 (1)
0000:08:55.843 : KMS Trace 0x208 (520)
0000:08:55.843 : KMS Trace 0x208 (520)
0000:08:55.843 : KMS Trace 0x208 (520)
0000:08:55.843 : KMS Trace 0x334 (820)
0000:08:55.848 : KMS Trace 0x207 (519)
0000:08:55.858 : Connect to port 3335
0000:08:55.859 :         on host 172.18.18.30
0000:09:09.950 : SSL Connect failed!  Error = 0x1 (1)
0000:09:09.959 : KMS Trace 0x208 (520)
0000:09:09.960 : KMS Trace 0x208 (520)
0000:09:09.960 : KMS Trace 0x208 (520)
0000:09:09.960 : KMS Trace 0x334 (820)
0000:09:09.962 : KMS Trace 0x207 (519)
0000:09:09.972 : Connect to port 3335
0000:09:09.972 :         on host 172.18.18.31
0000:09:24.141 : SSL Connect failed!  Error = 0x1 (1)
0000:09:24.151 : KMS Trace 0x208 (520)
0000:09:24.151 : KMS Trace 0x208 (520)
0000:09:24.151 : KMS Trace 0x208 (520)
0000:09:24.152 : KMS Trace 0x334 (820)
0000:09:24.583 : KMS Trace 0x207 (519)
0000:09:24.595 : Connect to port 3334
0000:09:24.596 :         on host 172.18.18.31
0000:09:41.289 : SSL Connect failed!  Error = 0x1 (1)
0000:09:41.297 : KMS Trace 0x208 (520)
0000:09:41.298 : KMS Trace 0x208 (520)
0000:09:41.298 : KMS Trace 0x208 (520)
0000:09:41.299 : KMS Trace 0x208 (520)
0000:09:41.299 : KMS Trace 0x208 (520)
0000:09:41.299 : KMS Trace 0x310 (784)
0000:09:41.312 : Connect to port 3334
0000:09:41.313 :         on host 172.18.18.30

This solution has no attachment