| Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback |
| Sun System Handbook - ISO 3.4 June 2011 Internal/Partner Edition | ||
|
|
||
 |
||||||||||||
Solution Type Problem Resolution Sure Solution 1012692.1 : Sun StorEdge [TM] 351x Array: How to Resolve Devices Missing from The Se3kxtr "show_frus" and "show_ses-devices" Output
PreviouslyPublishedAs 217449 This article explains how to resolve devices missing from se3kxtr show_frus and show_ses-devices files due to Duplicate Box Id's.
Applies to:Sun Storage 3310 ArraySun Storage 3510 FC Array Sun Storage 3511 SATA Array All Platforms Symptoms{SYMPTOM}Symptoms In the se3kxtr's show_frus.out output, the fru instances for the primary and secondary "FC_RAID_IOM " and "BATTERY_BOARD" are missing. Only the 3510 JBOD chassis's FRUs are reported in the "show frus" output. Additional Symptoms: 1. The output for the command "show battery-status" reports that "sccli: retrieving battery status: error: not an existing target." 2. The "show_loopmaps [ch2/ch3]" report the 3510FC RAID Chassis's SES Devices with a SEL_ID of 125. 3. The se3kxtr output for show_ses-devices.out file reports only the 3510 JBOD's SES devices for CH (2/3)loops (a/b) respectively. Changes{CHANGE}Cause{CAUSE}The symptoms described in the problem statement, were a result of two separate problems seen on a 3510 FC Array. Similar symptoms and resolution could occur on a 3511 SATA array. 1) Duplicate Chassis/Box IDs. This was certainly confusing considering the loop map outputs from both ch2/ch3 reported the RAID device FRUs with a ENCL_ID of "0" and the JBOD device FRUs with a ENCL_ID of "1." It is uncertain whether this is a reporting bug or consequence of SCCLI's inability to properly communicate with the RAID Chassis. It was visibly proven that the Box ID's were indeed both set to "1" so one can conclude for this instance that sccli only assumes the ID's were unique when it could not communicate to the RAID Chassis and assigned unique ENCL_ID's in the channel loop maps. *Please also note that there are other documented symptoms associated with having duplicate Chassis/Box IDs that are not mentioned in this document. 2) SES Mismatch discovered between the Primary/Secondary RAID I/O MODULES. Solution
Corrective Actions: 2) Power-cycled the 3510FC in the following order: First powered OFF the RAID head, then the JBOD. Then powered ON the JBOD followed by the RAID head. 3) Then the RAID Chassis came up with and audible alarm and an amber maintenance LED was blinking, uncovering an SES firmware mismatch which apparently existed in the RAID I/O MODULE SES devices. Possibly introduced on a prior RAID I/O MODULE replacement or maintenance activity. 4) The RAID Chassis SES on the primary controller that previously had a SEL_ID 125 instead of 12 had to be manually upgraded using sccli from SES-FW 1046 to 1080 to match that of the secondary's SES and another shutdown, reset was initiated. After the reset the SEL_ID for primary controller's SES then was identified correctly as SEL_ID 12.
5) A new se3k-extractor was collected and all was reported correctly. Additional Information: Problem/Symptom Analysis Reference: Array Configuration: se3kextractor symptom output: (Note: comments inline ending with !!) sccli: selected device /dev/rdsk/c10t600C0FF0000000000856810FD409B300d0s2 [SUN Name: FC_CHASSIS_BKPLN Name: FC_JBOD_IOM Manufacturing Date: Mon Nov 28 20:56:50 2005 Name: AC_POWER_SUPPLY Name: AC_POWER_SUPPLY Name: FC_JBOD_IOM show_battery-status.out --------------------------------------------------------------- show_loop-map_channel_2.out 28 devices found in loop map Channel Loop Map retrieved from CH 2 ID 28AL_PA SEL_ID SEL_ID TYPE ENCL_ID SLOT show_loop-map_channel_3.out 28 devices found in loop map === Channel Loop Map retrieved from CH 3 ID 28 === AL_PA SEL_ID SEL_ID TYPE ENCL_ID SLOT show_ses-devices.out --->Notice only displays JBOD SES Devices !! Internal Comments This document contains normalized content and is managed by the the Domain Lead(s) of the respective domains. To notify content owners of a knowledge gap contained in this document, and/or prior to updating this document, please contact the domain engineers that are managing this document via the “Document Feedback” alias(es) listed below: [email protected] The Knowledge Work Queue for this article is KNO-STO-VOLUME_DISK. SEL_ID, 125, SES, show_frus.out, show_ses.out, FRU, missing, box id, show_battery-status.out, audited, retrieving, chassis id, se3kxtr, se3k, extractor, 3510, 3511 Previously Published As 86947 Change History Date: 2009-12-23 User Name: [email protected] Action: Currency & Update Date: 2007-06-29 User Name: 7058 Action: Approved Attachments This solution has no attachment |
||||||||||||
|
||||||||||||