Sun System Handbook - ISO 3.4 June 2011 Internal/Partner Edition | |||
|
|
Solution Type Problem Resolution Sure Solution 1006810.1 : Sun[TM] Cluster 3.x & Sun StorEdge[TM] 3120 SCSI Array Initiator Configuration Tip
PreviouslyPublishedAs 209465 Symptoms After setting the SCSI initiator ID on the shared path(s) for ONE node in a clustered environment (set to '6' in most cases) the following types of messages were unexpectedly seen with a 3120 JBOD: /pci@1e,600000/scsi@3,1 (mpt1): We could not find sufficient documentation specifically addressing this array's setup, so we thought this document would help others since changing the device ID on the array itself was necessary. Resolution In this example, we had 2 nodes/hosts each with a dual-port SCSI card going to a Sun StorEdge 3120 JBOD. It is a split (dual) bus JBOD with multi-host/multi-intiator. Attached is a drawing of how the CORRECTED configuration ended up looking. Changing the 'scsi-initiator-id' to 6 (using NVRAMRC) on one host for the shared paths did not completely resolve the issue. The Sun StorEdge 3120 had its device ID (SAF-TE) set to 6, so to resolve the conflict, we switched it to a 5 (as the diagram demonstrates). A 'probe-scsi-all' worked on both systems without error, and the systems booted without error. Additional Information For additional references and guidance, see: Technical Instruction <Document: 1005129.1> - Sun Cluster[TM] 3.x software: scsi-initiator-id setup in clusters with Sun StorEdge[TM] 3xx0 SCSI arrays Technical Instruction <Document: 1007430.1> : - Setting the scsi-initiator-id on PCI Systems with Sun[TM] Cluster Software Product Sun Cluster 3.0 Sun Cluster 3.1 Sun StorageTek 3120 SCSI Array Internal Comments Thanks to SSE (Mark Rollins) for discovering this fix on Case: 64922609! Initial Authors: J. D. Halverson (jh1@sun.com) & Mark Rollins sun cluster, 3120, scsi-initiator-id, dual-host array Previously Published As 85106 Change History Date: 2006-05-05 User Name: 111868 Action: Approved Comment: checked keywords checked TM - corrected checked expiry date checked audience replaced attached drawing in BMP format with one in JPG format, for two reasons: size and format publishing Version: 4 Date: 2006-05-05 User Name: 111868 Action: Delete Attachment Comment: I'm replacing the BMP type file with the file in JPG format. Cause: 1. JPG is generally supported format and readable by most of the browsers, BMP isn't. 2. JPG picture in compressed form has got 45KB instead of 1167KB in BMP. Attachments This solution has no attachment |
||||||||||||
|