Sun Microsystems, Inc.  Sun System Handbook - ISO 3.4 June 2011 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-72-1008359.1
Update Date:2009-03-10
Keywords:

Solution Type  Problem Resolution Sure

Solution  1008359.1 :   Sun StorageTek[TM] 3xxx Arrays - Unable to change controller assignment on LogicalDisk  


Related Items
  • Sun Storage 3510 FC Array
  •  
  • Sun Storage 3310 Array
  •  
  • Sun Storage 3511 SATA Array
  •  
  • Sun Storage 3320 SCSI Array
  •  
Related Categories
  • GCS>Sun Microsystems>Storage - Disk>Modular Disk - 3xxx Arrays
  •  

PreviouslyPublishedAs
211430


Symptoms
When trying to change the controller assignment of an LD on a SE3510 array
from primary controller to secondary controller via the firmware menu
interface, the error message

"Secondary Controller SCSI Id Is Not Assigned"

is printed.

Resolution
The "SCSI ID" in the message refers to the SCSI id of the drive channels.
Because each of the disks has two ports, each of the drive channels used
to communicate with that disk must have IDs assigned to them.
When a array is sipped from the factory, both (primary and secondary) SCSI
Ids are set for the two default drive channels, 2 and 3.  For example,
here we can see that the primary ID (PID) for drive channels 2 and 3 is
14, and the secondary ID (SID) for those same drive channels is 15.
Ch  Type    Media   Speed   Width  PID / SID
--------------------------------------------
0  Host    FC(P)   2G      Serial  41 / N/A
1  Host    FC(P)   N/A     Serial  N/A / 42
2  DRV+RCC FC(L)   2G      Serial  14 / 15
3  DRV+RCC FC(L)   2G      Serial  14 / 15
4  Host    FC(P)   2G      Serial  43 / N/A
5  Host    FC(P)   N/A     Serial  N/A / 44
6  Host    LAN     N/A     Serial  N/A / N/A
Sometimes, when multiple JBODs (just a bunch of disks) are attached to the RAID array, host
channels are "converted" to drive channels.  When a host channel is
converted to a drive channel, it is necessary to also set PIDs and SIDs
for those two channels.
If only a PID is assigned to these new drive channels, as seen here:
Ch  Type    Media   Speed   Width  PID / SID
--------------------------------------------
0  Host    FC(P)   2G      Serial  41 / N/A
1  Host    FC(P)   N/A     Serial  N/A / 42
2  DRV+RCC FC(L)   2G      Serial  14 / 15
3  DRV+RCC FC(L)   2G      Serial  14 / 15
4  Drive   FC(L)   2G      Serial  119 / N/A
5  Drive   FC(L)   2G      Serial  119 / N/A
6  Host    LAN     N/A     Serial  N/A / N/A
then the disks physically attached to channels 4 and 5 can ONLY be used in
LDs assigned to the primary controller.  If an attempt is made to change
the LD controller assignent of an LD with disks using channels 4 and 5,
the error
"Secondary Controller SCSI Id Is Not Assigned"
would be issued.
This is easily fixed.  In the firmware interface:
select menu entry: view and edit channelS
select drive channel 4
select menu entry: Secondary controller scsi id
this will print an acceptable range of IDs for you to choose from.
before resetting the array, go back, do that SAME thing (and use the
same ID for drive channel 5, and THEN reset the array (obviously
stop all i/o first).
After correctly assigning a secondary SCSI id, the output from 'show
channels' would look something like this:
Ch  Type    Media   Speed   Width  PID / SID
--------------------------------------------
0  Host    FC(P)   2G      Serial  41 / N/A
1  Host    FC(P)   N/A     Serial  N/A / 42
2  DRV+RCC FC(L)   2G      Serial  14 / 15
3  DRV+RCC FC(L)   2G      Serial  14 / 15
4  Drive   FC(L)   2G      Serial  119 / 120
5  Drive   FC(L)   2G      Serial  119 / 120
6  Host    LAN     N/A     Serial  N/A / N/A


Product
Sun StorageTek 3511 SATA Array JBOD
Sun StorageTek 3511 SATA Array
Sun StorageTek 3510 FC Array JBOD
Sun StorageTek 3510 FC Array
Sun StorageTek 3320 SCSI Array
Sun StorageTek 3310/3510/3511/3120 Reset Switch FRU
Sun StorageTek 3310/3510/3511 Firmware 4.11 Upgrade
Sun StorageTek 3310 SCSI Array
Sun StorageTek 3510 2U FC Array

Internal Comments
escalation raised on this issue - no documentation or other sunsolve document had this documented.

Previously Published As
88203

Change History
Date: 2007-01-10
User Name: 95826
Action: Approved
Comment: - verified metadata
- review date ok : 2008-01-10
- checked for TM - 1 added + full product name in title
- checked audience : contract
Publishing
Version: 3
Date: 2007-01-10

Attachments
This solution has no attachment
  Copyright © 2011 Sun Microsystems, Inc.  All rights reserved.
 Feedback