Asset ID:	1-71-1003516.1
Update Date:	2010-10-05
Keywords:

---

Solution Type  Technical Instruction Sure

Solution  1003516.1 :   Meaning of LT_OP and LT_TASK Messages in Sun StorEdge[TM] T3+/SE6x20 syslog  


PreviouslyPublishedAs
204943

Description
Starting with v3.1.0 firmware, T3+ and SE6x20 arrays can log Notice level
messages of the following format to syslog:

Jul 07 09:32:30 LT08[1]: N: u1ctr LT_TASK 8 received LT_OP Vol Init
....
Jul 07 09:39:45 LT08[1]: N: u1ctr LT_TASK 8 LT_OP Vol Init succeeded

Steps to Follow

These messages were logged at an information level only, prior to v3.1.0
firmware, so would not have been seen on arrays using the default syslog level.
The reason for the change in log level of these messages was to provide
accountability for "vol verify" commands performed via the array's web
interface. As well as telnet interfaces, the T3 and SE6x20 arrays also have
web (or "token" or "http") interfaces which can be used to manage the
array. All commands run via the telnet interface are accountable via the
"cmdlog" file, but commands issued via the web interface are not logged
into the "cmdlog" file.
Instead, the web interface puts its commands into a message queue to be
run by another process. These syslog messages track the start and end of
each "Long Transaction" command from this queue. There are four possible
formats to the LT_TASK message - a "received" message to indicate the
beginning of a command, and then three different messages to indicate the
result of a command: "aborted", "Failed" or "succeeded".
The list of possible "Long Transaction" commands logged this way are:
"Noop", "Disable", "Auto Disable", "Recon", "Sync", "Format", "Vol Init",
"Vol Unmount", "Vol Verify", "Disk Plug", "Disk Unplug", "Set Sys Block
Size", "Set Sys Data", "Set Sys Vendor", "PGR", "Vol Add Standby", "Vol
Remove Standby", "Marked Disable Recon"
Some of these are internal operations that do not have command-line
equivalents. As a result of this change, because the web interface is not
the exclusive user of "Long Transactions", messages have been exposed
representing internal operations of the array, which can be ignored, e.g.
the array issuing "sync" commands after a user-initiated "reset":
Jul 07 16:42:15 sh36[1]: N: reset
Jul 07 16:42:17 CFGT[1]: N: Resetting system
Jul 07 16:42:18 LT10[1]: N: u1ctr LT_TASK 10 received LT_OP Sync
Jul 07 16:42:18 ISR1[1]: N: u1ctr ISP2200[2] interface going offline
Jul 07 16:42:18 ISR1[1]: N: u1ctr ISP2200[2] qlcf_init_pdb: PDB Initialize
Jul 07 16:42:18 ISR1[1]: N: u1ctr ISP2200[2] QLCF_I_ABORT_ALL_TM_CMDS:
Target-mode Flush Started (lun = 0x0)
Jul 07 16:42:18 FCC0[1]: N: Target Reset Received
Jul 07 16:42:18 ISR1[1]: N: u1ctr ISP2200[2] QLCF_NOTIFY_ACK: Target-mode
Flush Complete (lun = 0x0)
Jul 07 16:42:18 FCC0[1]: N: u1ctr <> on port 0, abort 0
Jul 07 16:42:18 LT10[1]: N: u1ctr LT_TASK 10 LT_OP Sync succeeded
Jul 07 16:42:19 LT10[1]: N: u1ctr LT_TASK 10 received LT_OP Sync
Jul 07 16:42:20 LT10[1]: N: u1ctr LT_TASK 10 LT_OP Sync succeeded
Examples of applications which use the web interface to manage the array
are StorADE and the SE6000 Configuration Service software, e.g. the "sscs"
command.

Product
Sun StorageTek T3+/6X20 Controller Firmware 3.1
Sun StorageTek T3 Array
Sun StorageTek 6320 System
Sun StorageTek 6120 Array

Internal Comments
This document is based on information from the following bug:

Bug Id: 4907545
Synopsis: vol verify run from web interface (storade) does not show in cmdlog
or syslog

T3, 6120, 6320, syslog, LT_TASK, LT_OP
Previously Published As
77362

Change History
Date: 2006-01-23
User Name: 71396
Action: Update Canceled
Comment: *** Restored Published Content *** from ssh audit update
Version: 0
Date: 2006-01-23
User Name: 71396
Action: Update Started
Comment: updating per ssh audit
Version: 0
Date: 2005-09-23
User Name: 71396
Action: Update Canceled
Comment: *** Restored Published Content *** Deleting update copy
Version: 0
Date: 2005-09-23
User Name: 71396
Action: Update Started
Comment: .
Version: 0
Date: 2005-06-27
User Name: 95826
Action: Update Canceled
Comment: *** Restored Published Content *** canceling update as updater is no longer within Sun
Version: 0
Date: 2005-06-27
User Name: 95826
Action: Reassign
Comment: reassigning document as updater is no longer within Sun
Version: 0
Date: 2005-06-16
User Name: 132461
Action: Update Started
Comment: Title
Version: 0
Date: 2004-07-12
User Name: C139400
Action: Approved
Comment: added tmark, corrected title, format, spacing, spelling, usage, applied KE procedures
Version: 0
Date: 2004-07-12
User Name: C139400
Action: Accepted
Comment:
Version: 0
Date: 2004-07-08
User Name: 71066
Action: Approved
Comment: TR done. The KE might have to check the trademarks.

Thanks
Nicolas
Version: 0
Date: 2004-07-08
User Name: 71066
Action: Accepted
Comment:
Version: 0
Date: 2004-07-08
User Name: 75028
Action: Approved
Comment: F.A.O. Nicolas Wipfli to review

BTW "Noop" standards for "no operation", i.e. do nothing! I doubt it is actually ever used for anything, but it is in the source code, so I am including it the Infodoc for the sake of completeness.

Purpose of the doc is just to try and re-assure people that these syslog messages don't represent a problem - you know how customers can get about strange messages in the T3 syslog...
Version: 0
Date: 2004-07-07
User Name: 71066
Action: Rejected
Comment: Submitter requested to push this doc back into the draft stage.

Nicolas
Version: 0
Date: 2004-07-07
User Name: 71066
Action: Accepted
Comment:
Version: 0
Date: 2004-07-07
User Name: 75028
Action: Approved
Comment: Please review
Version: 0
Date: 2004-07-07
User Name: 75028
Action: Created
Comment:
Version: 0
Product_uuid
62772b5a-05c6-11d8-84cb-080020a9ed93|Sun StorageTek T3+/6X20 Controller Firmware 3.1
2a6d7d50-0a18-11d6-8e0b-f0bd33b24928|Sun StorageTek T3 Array
4de60cc2-a08e-4610-b8bf-6a1881cb59c6|Sun StorageTek 6320 System
2cd2e7d2-2980-11d7-9c3f-c506fe37b7ef|Sun StorageTek 6120 Array

Attachments

This solution has no attachment