| 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 Technical Instruction Sure Solution 1002758.1 : Sun StorEdge[TM] 351x: JBOD's at Different SES Firmware Revisions is not reported
PreviouslyPublishedAs 203773 Description There is a strict requirement that the SES(SCSI Enclosure Services) firmware revisions within a StorEdge[TM] 3510 or 3511 RAID array be at the same level to avoid interprocessor communication issues. It is strongly recommended that SES firmware be at the latest released revision across JBOD expansion trays, but there is no technical requirement. Steps to Follow Within the raid array, there is an internal protocol between controllers for interprocessor communication. The SES device receives commands from the raid controller and communicates across the i2c busses with the alternate SES device. The nature of this internal protocol requires that data structures and commands be synchronized and this may not occur if SES firmware revisions differ. This internal protocol only occurs within the raid array. Between JBOD's, the SES devices communicate across the fibre channel adhering to a standard FC protocol. Consider a 3510 RAID array with 4 JBOD's attached. The SES firmware on at least 3 of the expansion units is different. * SES Ch Id Chassis Vendor/Product ID Rev PLD WWNN WWPN ------------------------------------------------------------------------------- '''2 12''' 0843BE SUN StorEdge 3510F A '''1046''' 1000 204000C0FF0843BE 214000C0FF0843BE Topology: loop(a) 2 28 07D43F SUN StorEdge 3510F D '''1040''' 1000 205000C0FF07D43F 215000C0FF07D43F Topology: loop(a) 2 44 08773A SUN StorEdge 3510F D '''1046''' 1000 205000C0FF08773A 215000C0FF08773A Topology: loop(a) 2 60 087770 SUN StorEdge 3510F D '''1046''' 1000 205000C0FF087770 215000C0FF087770 Topology: loop(a) 2 76 098E18 SUN StorEdge 3510F D '''1080''' 1000 205000C0FF098E18 215000C0FF098E18 Topology: loop(a) '''3 12''' 0843BE SUN StorEdge 3510F A '''1046''' 1000 204000C0FF0843BE 224000C0FF0843BE Topology: loop(b) 3 28 07D43F SUN StorEdge 3510F D '''1040''' 1000 205000C0FF07D43F 225000C0FF07D43F Topology: loop(b) 3 44 08773A SUN StorEdge 3510F D '''1046''' 1000 205000C0FF08773A 225000C0FF08773A Topology: loop(b) 3 60 087770 SUN StorEdge 3510F D '''1046''' 1000 205000C0FF087770 225000C0FF087770 Topology: loop(b) 3 76 098E18 SUN StorEdge 3510F D '''1080''' 1000 205000C0FF098E18 225000C0FF098E18 Topology: loop(b) There will only be an SES mismatch alarm if the channel 2 and channel 3 entries for the SES device, device 12 are different indicating a mismatch within the same chassis. The Raid Unit is identifiable by the "3510F A" rather than "3510F D" Product ID. The raid unit needs to be at chassis ID 0 to yield ID 12 SES devices. No other id configuration is supported and a non zero value would cause problems on loop initialization if attached to JBODs. In this example, they are both at revision 1046, so there is no mismatch. The first JBOD, with a chassis ID of 1 (SES device 28) is at SES firmware revision 1040. The second JBOD, with a chassis ID of 2 (SES device 44), and third JBOD, with a chassis ID of 3 (SES device 60) are both at SES firmware revision 1046. The fourth JBOD, with a chassis ID of 4 (SES device 76) is at SES firmware revision 1080. In this example, the RAID array and and all 4 JBOD's should be at the latest SES firmware revision 1080, but there is no strict requirement across JBOD's. There is no inter-expansion unit checking by the controller to ensure that JBOD's are at the same revision. Although it is strongly recommended that all SES firmware be upgraded to the latest released version, it is not imperative or fatal for JBOD's to be different firmware revisions. Product Sun StorageTek 3511 SATA Array JBOD Sun StorageTek 3510 FC Array JBOD Sun StorageTek 3511 SATA Array Sun StorageTek 3510 FC Array Sun StorageTek 3510 2U FC Array Internal Comments To ensure you have the latest SES firmware revision, please check the internal PTS website or the latest patch release:
See: CR 6400757 for further details.
The Knowledge work queue for this article is KNO-STO-VOLUME_DISK SES, SE3510, SE3511, 3510, 3511, firmware, mismatch, JBOD, expansion unit, expansion tray, audited Previously Published As 88191 Change History Date: 2007-11-13 User Name: 7058 Action: Approved Comment: changed sunsolve2 reference to sunsolve.central in internal only section. Version: 7 Date: 2007-11-13 User Name: 7058 Action: Update Started Comment: fixing link problem. Version: 0 Date: 2007-06-29 User Name: 7058 Action: Add Comment Comment: Notes for Normalizaton: This document is referenced by: 89047 Subset Root path: 88191-->89047-->89034-->89031-->89050 Project: Minnow Normalization Version: 0 Date: 2007-06-29 User Name: 7058 Action: Approved Comment: Fixed 2 STM link link errors. Either too many ]'s or not enough. Links in internal only section now activated. Attachments This solution has no attachment |
||||||||||||
|
||||||||||||