and later [Release: N/A and later ]
Sun Storage 2510 Array - Version: Not Applicable and later [Release: N/A and later]
Sun Storage 2530 Array - Version: Not Applicable and later [Release: N/A and later]
Sun Storage 2540-M2 Array - Version: Not Applicable and later [Release: N/A and later]
Sun Storage 2540 Array - Version: Not Applicable and later [Release: N/A and later]
Information in this document applies to any platform.
Symptoms
There are no specific symptoms. The "Wide port transitioned from failed to degraded" messages may be seen in the event log when troubleshooting the StorageTek 2500 or Sun Storage 2500-M2 Arrays. The purpose of this document is to show they are expected when resetting a controller.
Cause
There are different possible causes for these events:
- User initiated controller reset.
- FW initiated a controller reset.
If you get these events although there was no controller reset, please refer to <Document 1002514.1> Collecting Sun StorageTek[TM] Common Array Manager Array Support Data to collect an array supportdata and engage the Oracle support.
Solution
When a controller is manually reset, you will see the following events in majorEvents.txt:
- Controller return status/function call for requested operation
- Wide port transitioned from optimal to degraded
- Wide port transitioned from degraded to failed
- Controller reset by its alternate
- Start-of-day routine begun
- Start-of-day routine completed
- Wide port transitioned from degraded to optimal
The examples below were taken from firmware version 07.35.55.11.
Scenario
- Controller A was manually reset via CAM.
- CAM array support data collected to review events in majorEventLog.txt.
Refer <Document 1002514.1> Collecting Sun StorageTek[TM] Common Array Manager Array Support Data for the procedure to collect an array supportdata.
Note: The examples below were parsed for brevity. It is not the intent of this document to show a complete list of events when a controller is manually reset.
- Then, controller B reports "wide port transitioned from optimal to degraded" since controller A is going down:
Date/Time: Mon Jul 18 13:06:12 EDT 2011
Sequence number: 6035
Event type: 1706
Event category: Error
Priority: Critical
Description: Wide port transitioned from optimal to degraded
Event specific codes: 0/0/0
Component type: IOM
Component location: Tray.85 (IOM)
Logged by: Controller in slot B
- Then, controller B reports that controller A was reset:
Date/Time: Mon Jul 18 13:06:13 EDT 2011
Sequence number: 6039
Event type: 400F
Event category: Notification
Priority: Informational
Description: Controller reset by its alternate
Event specific codes: 0/0/0
Component type: Controller
Component location: Controller in slot B
Logged by: Controller in slot B
- Finally, controller A reports its coming back up per the Start-of-day event:
Date/Time: Mon Jul 18 13:07:04 EDT 2011
Sequence number: 6044
Event type: 2606
Event category: Notification
Priority: Informational
Description: Start-of-day routine begun
Event specific codes: 0/0/0
Component type: Controller
Component location: Controller in slot A
Logged by: Controller in slot A
- Controller A reports a successful boot:
Date/Time: Mon Jul 18 13:08:10 EDT 2011
Sequence number: 6059
Event type: 2605
Event category: Notification
Priority: Informational
Description: Start-of-day routine completed
Event specific codes: 0/0/0
Component type: Controller
Component location: Controller in slot A
Logged by: Controller in slot A
- Ports on the A Controller transition back to optimal:
Date/Time: Mon Jul 18 13:06:28 EDT 2011
Sequence number: 6062
Event type: 1709
Event category: Notification
Priority: Informational
Description: Wide port transitioned from degraded to optimal
Event specific codes: 0/0/0
Component type: IOM
Component location: Tray.85 (IOM)
Logged by: Controller in slot B
The following is an internal only information. Run the support data through SRAS first, then check majorEventLog_sras.txt for faster parsing.
The example below was seen against the firmware (FW) 07.35.55.11.
Scenario
- Controller A was manually reset via CAM.
- CAM array support data collected, and then run thru SRAS.
All events below were parsed from majorEventLog_sras.txt
- Then, controller B reports "wide port transitioned" events since controller A is going down:
B:Mon Jun 06 13:13:33 EDT 2011 : 5679 : 0/0/0 : 1706 : Error : IOM : Tray.85 (IOM) : Wide port transitioned from optimal to degraded
B:Mon Jun 06 13:13:33 EDT 2011 : 5680 : 0/0/0 : 1707 : Error : IOM : Tray.85 (IOM) : Wide port transitioned from degraded to failed
B:Mon Jun 06 13:13:33 EDT 2011 : 5681 : 0/0/0 : 1706 : Error : IOM : Tray.85 (IOM) : Wide port transitioned from optimal to degraded
B:Mon Jun 06 13:13:33 EDT 2011 : 5682 : 0/0/0 : 1707 : Error : IOM : Tray.85 (IOM) : Wide port transitioned from degraded to failed
- Then, controller B reports that controller A was reset:
B:Mon Jun 06 13:13:35 EDT 2011 : 5683 : 0/0/0 : 400F : Notification : Controller : Controller in slot B : Controller reset by its alternate
---> Reboot Reason: REBOOTALT_DBM_HEALTH_CHECK_EVENT
- Then more "wide port transitioned" events:
B:Mon Jun 06 13:13:36 EDT 2011 : 5684 : 0/0/0 : 1706 : Error : IOM : Tray.85 (IOM) : Wide port transitioned from optimal to degraded
B:Mon Jun 06 13:13:37 EDT 2011 : 5685 : 0/0/0 : 1707 : Error : IOM : Tray.85 (IOM) : Wide port transitioned from degraded to failed
B:Mon Jun 06 13:13:40 EDT 2011 : 5686 : 1ff00/2/0 : 1012 : Error : Drive : None : Destination driver event : Device fail timeout Device fail timeout on Channel: 00
- Finally, controller A reports its coming back up:
A:Mon Jun 06 13:14:17 EDT 2011 : 5687 : 0/0/0 : 2606 : Notification : Controller : Controller in slot A : Start-of-day routine begun
- Controller A reports a successful boot:
A:Mon Jun 06 13:15:10 EDT 2011 : 5702 : 0/0/0 : 2605 : Notification : Controller : Controller in slot A : Start-of-day routine completed
- Ports transition back to optimal, resulting in the controller being back online:
B:Mon Jun 06 13:13:50 EDT 2011 : 5704 : 0/0/0 : 1708 : Notification : IOM : Tray.85 (IOM) : Wide port transitioned from failed to degraded
B:Mon Jun 06 13:13:50 EDT 2011 : 5705 : 0/0/0 : 1709 : Notification : IOM : Tray.85 (IOM) : Wide port transitioned from degraded to optimal
B:Mon Jun 06 13:14:07 EDT 2011 : 5706 : 0/0/0 : 1708 : Notification : IOM : Tray.85 (IOM) : Wide port transitioned from failed to degraded
B:Mon Jun 06 13:14:07 EDT 2011 : 5707 : 0/0/0 : 1709 : Notification : IOM : Tray.85 (IOM) : Wide port transitioned from degraded to optimal
B:Mon Jun 06 13:14:07 EDT 2011 : 5708 : 0/0/0 : 1708 : Notification : IOM : Tray.85 (IOM) : Wide port transitioned from failed to degraded
B:Mon Jun 06 13:14:07 EDT 2011 : 5709 : 0/0/0 : 1709 : Notification : IOM : Tray.85 (IOM) : Wide port transitioned from degraded to optimal
Attachments
This solution has no attachment
