L&TT Analysis Test

[Trevor4LOOP]

I receive the following when running an analysis test on Red Hat ES 3 using HP's L&TT software:

Main > Drive Information > Test > Viewer >
-------------------------------------------------------------------------------------------------------------------------------
- Test 'Device Analysis' started on device 'HP DLT VS80' at address '10.8.0[1-/dev/sg0]'
- Passed
- Operations Log
- Executing Rules Based Analysis (rules file is /opt/ltt/scripts/DLT1Drv.rul)
- Test passed with warnings
- Analysis Results
- Device Analysis for DLT1 Drives
- Product ID is 'DLT VS80' with 'V064' firmware
- Drive power on hours: 9631
- Tape pulling hours: 174
- Drive reports 2 error events within the last 120 operating hours.
- Script is unable to verify if this device is using latest firmware - revision data was not loaded from web.
- There were 22 rules checked.

I just wanted to ask:
1. How can i view what the warnings in the "test passed with warnings" are? How can i find out what these are?

2. There were 2 error events. How can i find out what these two error events are?

The above report view was done in detail mode of "Everything".

Any help in deciphering the above would be appreciated.

Trevor

[David Paris AKA Mixmast]

You can see that warnings in the logs that LTT generate, LTT have a tab that shows you the devices and what warnings have been create in a particular device.

Regards

[Trevor4LOOP]

Hi

Thank you for the response.

However, I'm using the linux version of the tool. Is the tab you are referring to in the linux version of ltt?

I've checked the event log and it has :
10:4:4:40:3:3:42:1:1:Name:Device Analysis:1252:0
10:1:8:44:0:8:0x24004001:1151453264:1151453264:0:1:8:0:0
10:2:8:40:1:7:50:65:0:0
10:3:8:40:2:7:41:1:1:s_system:4.0.2.0:enu
10:4:8:40:3:7:44:1:3:Testname:50:500:0:0
10:5:8:40:4:7:44:2:3:41:1:1:s_system:4.0.2.0:enu
10:6:8:40:5:7:44:3:3:41:1:1:s_system:4.0.2.0:enu
10:7:8:40:6:7:42:1:1:ProductID:HP DLT VS80:1252:0
10:8:8:40:7:7:42:1:1:Path:10.8.0[1-/dev/sg0]:1252:0
10:1:4:45:44:8:0x28004010:1151453264:1151453264:0:1:8:0:0
10:2:4:40:1:3:50:199:0:0
10:3:4:40:2:3:41:1:1:s_system:4.0.2.0:enu
10:4:4:40:3:3:42:1:1:Filename:/opt/ltt/scripts/DLT1Drv.rul:1252:0
10:1:4:46:44:8:0x28040010:1151453264:1151453264:0:4:8:0:0
10:2:4:40:1:3:120:50:0:0
10:3:4:40:2:3:41:1:1:s_system:4.0.2.0:enu
10:4:4:40:3:3:42:1:1:PlainText:Script version\: V28.07.2003:1252:0
10:1:4:47:44:8:0x28040001:1151453264:1151453264:0:0:8:0:0
10:2:4:40:1:3:120:50:0:0
10:3:4:40:2:3:41:1:1:s_system:4.0.2.0:enu
10:4:4:40:3:3:42:1:1:PlainText:Device Analysis for DLT1 Drives:1252:0
10:1:4:48:0:8:0x28040020:1151453264:1151453264:0:0:8:1044480:0
10:2:4:40:1:3:120:50:0:0
10:3:4:40:2:3:41:1:1:s_system:4.0.2.0:enu
10:4:4:40:3:3:42:1:1:PlainText:Rules_DLT001.xml:1252:0
10:1:4:49:47:8:0x28040001:1151453264:1151453264:0:1:8:0:0
10:2:4:40:1:3:120:50:0:0
10:3:4:40:2:3:41:1:1:s_system:4.0.2.0:enu
10:4:4:40:3:3:42:1:1:PlainText:Product ID is 'DLT VS80' with 'V064' firmware:1252:0
10:1:4:50:47:8:0x28040001:1151453264:1151453264:0:1:8:0:0
10:2:4:40:1:3:120:50:0:0
10:3:4:40:2:3:41:1:1:s_system:4.0.2.0:enu
10:4:4:40:3:3:42:1:1:PlainText:Drive power on hours\: 9630:1252:0
10:1:4:51:47:8:0x28040001:1151453264:1151453264:0:1:8:0:0
10:2:4:40:1:3:120:50:0:0
10:3:4:40:2:3:41:1:1:s_system:4.0.2.0:enu
10:4:4:40:3:3:42:1:1:PlainText:Tape pulling hours\: 174:1252:0
10:1:4:52:842084149:8:0x28040001:1151453264:1151453264:0:3:8:0:0
10:2:4:40:1:3:120:50:0:0
10:3:4:40:2:3:41:1:1:s_system:4.0.2.0:enu
10:4:4:40:3:3:42:1:1:PlainText:Drive reports 2 error events within the last 120 operating hours.:1252:0
10:1:4:53:44:8:0x48040001:1151453264:1151453264:0:1:8:0:0
10:2:4:40:1:3:120:50:0:0
10:3:4:40:2:3:41:1:1:s_system:4.0.2.0:enu
10:4:4:40:3:3:42:1:1:PlainText:Script is unable to verify if this device is using latest firmware - revision data was not loaded from web.:1252:0
10:1:4:54:44:8:0x28040001:1151453264:1151453264:0:0:8:0:0
10:2:4:40:1:3:120:50:0:0
10:3:4:40:2:3:41:1:1:s_system:4.0.2.0:enu
10:4:4:40:3:3:42:1:1:PlainText:There were 22 rules checked.:1252:0
10:1:4:55:0:8:0x28040020:1151453264:1151453264:0:0:8:1040384:0
10:2:4:40:1:3:120:50:0:0
10:3:4:40:2:3:41:1:1:s_system:4.0.2.0:enu
10:4:4:40:3:3:42:1:1:PlainText:Errors=0 Warnings=1:1252:0
10:1:4:56:44:8:0x28004020:1151453264:1151453264:0:0:8:0:0
10:2:4:40:1:3:120:50:0:0
10:3:4:40:2:3:41:1:1:s_system:4.0.2.0:enu
10:4:4:40:3:3:42:1:1:PlainText:Device Analysis completed, some problems were encountered. See below for further details.:1252:0
10:1:4:57:44:8:0x28004020:1151453264:1151453264:0:0:8:0:0
10:2:4:40:1:3:120:50:0:0
10:3:4:40:2:3:41:1:1:s_system:4.0.2.0:enu
10:4:4:40:3:3:42:1:1:PlainText::1252:0
10:1:4:58:0:8:0x28040020:1151453264:1151453264:0:0:8:1040384:0
10:2:4:40:1:3:120:50:0:0
10:3:4:40:2:3:41:1:1:s_system:4.0.2.0:enu
10:4:4:40:3:3:42:1:1:PlainText:END:1252:0

What does the above mean? How do you decipher it?

It seems odd that that the log file for a diagnostic tool is output in such a way as to be useless to the user.

Can any one help?

Thank you

Trevor

[Torsten.]

From the online help:

"The information it (the event log) contains is intended for use by L&TT programmers as a tool for debugging software issues within the program itself. "


You should create and review a support ticket, not the event log.