Asset ID:	1-71-1009054.1
Update Date:	2010-09-14
Keywords:

---

Solution Type  Technical Instruction Sure

Solution  1009054.1 :   'Assertion Reset' or 'Exception Reset' reported in Sun StorEdge[TM] T3, T3+, 6120 syslog file  


PreviouslyPublishedAs
212483

Description

In the syslog file on a Sun StorEdge [TM] T3 or T3+ (or on the host the
file is syslog'ed out to) there are entries similiar to the following:

 Jan 20 16:51:00 sh05[1]: W: u1ctr Assertion Reset (3000) was initiated at
20031217 162813 ../../common/lpc/lpc_hbt.c line 533, Assert(0) => 0 BOOT

OR

 Jun 17 12:20:06 sh04[1]: W: u1ctr Exception Reset (2003) was initiated at
20030617 083352 Data Access exception

Steps to Follow

These entries are produced when the array controller is reset. The message
is stored on the NVRAM of the controller. It is copied to the syslog file
when the 'logger -dmprstlog' command is run.

In the first example above, the log is dated Jan 20, even though the
controller was actually reset on 17th December 2003 (200312170) at 16:28
and 13 seconds (162813).

In 6020 / 6120 arrays, these entries may not contain the date when the crash was logged. The example below is taken collecting an extractor:

 Feb 18 19:24:49 array03 sh18[1]: N: .loop stat
Feb 18 19:24:50 array03 sh18[1]: N: logger -dmprstlog
Feb 18 19:24:50 array03 sh18[1]: N: u1ctr Reset (3000) lpc_hbt.c line 367, Assert(0) => 0
Feb 18 19:24:50 array03 sh18[1]: N: CPU trap exception (3072) frame...

 !!! 

There is no indication about when the crash was generated.

The message will survive a power cycle. The only time it is overwritten is
when there is another valid reset log.

If you have already diagnosed the controller issue, or if the message is
outdated and you do not want the message reported anymore, you can
manually clear the contents of the reset log by running 'logger -clrrstlog'
on the array. This can be run during normal service. Alternatively, the
message can be ignored.

Product
Sun StorageTek T3 Array
Sun StorageTek T3+ Array
Sun StorageTek 6120/6320 Controller Firmware 3.2

T3, Assertion Reset, Exception Reset, logger -dmpstlog
Previously Published As
73432

Change History
Date: 2006-03-15
User Name: 7058
Action: Approved
Comment: Enabled STM to offset preformatted text.
No further changes needed.
OK to republish.
Version: 3
Date: 2006-03-14
User Name: 7058
Action: Accept
Comment:
Version: 0
Date: 2006-03-14
User Name: 85390
Action: Approved
Comment: Good document. I just edited "logger -dumpstlog" with change "logger -dmprstlog" which is correct syntax.
Version: 0
Date: 2006-03-14
User Name: 85390
Action: Add Comment
Comment: edited document changed "logger -dumpstlog" to "logger -dmprstlog" which represents the actual command to enter.

I approve.
Version: 0
Date: 2006-03-02
User Name: 85390
Action: Accept
Comment:
Version: 0
Date: 2006-03-02
User Name: C135270
Action: Approved
Comment: - Updated scope to 6020 arrays.
- Add some comments about crash dump generation.
Version: 0
Date: 2006-03-02
User Name: C135270
Action: Update Started
Comment: - Update scope to 6x20 systems.
- Add some clarification comments.
Version: 0
Date: 2004-03-11
User Name: C149439
Action: Approved
Comment: Made very minor edits.

Gail Waldron
Version: 0
Date: 2004-03-10
User Name: C149439
Action: Accepted
Comment:
Version: 0
Date: 2004-03-10
User Name: 75028
Action: Approved
Comment: Reviewed document, recommend it is published
Version: 0
Date: 2004-03-10
User Name: 75028
Action: Accepted
Comment:
Version: 0
Date: 2004-03-10
User Name: 120710
Action: Approved
Comment: Please review document
Version: 0
Date: 2004-01-21
User Name: 120710
Action: Created
Comment:
Version: 0
Product_uuid
2a6d7d50-0a18-11d6-8e0b-f0bd33b24928|Sun StorageTek T3 Array
2a714b10-0a18-11d6-86e2-d56b387d4fbf|Sun StorageTek T3+ Array
3ad132b5-248c-11d9-8d5c-080020a9ed93|Sun StorageTek 6120/6320 Controller Firmware 3.2

Attachments

This solution has no attachment