Sun Storage 3310 Array
 

GCS>Sun Microsystems>Storage - Disk>Modular Disk - 3xxx Arrays
 

3310 with a single RAID-Head
---------------------------
For better comprehension, here follows a simple configuration :
- target 0 is set to the primary controller for all channels : PID=0
- only one LD (Logical Drive) is created onto this Primary-ctrl
- LD partitions are mapped to CH1 and CH3 ports.
Then, partitions become LUNs.
All LUNs mapped to Host-channels (CH1 & CH3) and connected to nodes will be
seen with a cXt0dX target - target 0 is inherited from the PID setting.
SCSI channels that connect a LVD HBA to a 3310 Host-channel (CHA) are
isolated from other hosts' scsi-channels by the 3310 - there is no shared
SCSI bus between 2 hosts.
Since each host will have only one HBA connected to each 3310 array,
Sun[TM] Cluster requirements dictate that we must have host-based software
mirroring between two arrays to avoid a Single Point Of Failure (SPOF).
Here we have these SCSI channels :
3310-A CH1(t0) <- to -> PCI1(t7) of n2 node
3310-A CH3(t0) <- to -> PCI1(t7) of n1 node
3310-B CH1(t0) <- to -> PCI4(t7) of n2 node
3310-B CH3(t0) <- to -> PCI4(t7) of n1 node
Host SCSI channels are separated by the I/O module and termination board of
a 3310 RAID-Head.
Since these SCSI channels are electrically isolated from each other, one can
unplug a cable from a CHA or a HBA (on a channel) with no
effects to the other one. Maintenance is then quite easy.
During installation, there is no need to change the scsi-initiator-id on the
HBA side (they keep on running with target 7, the default value).
- Drawing :
t0                                       +---------+
+----------------------------------------|- PCI1   |
+-----------|----------------+                     t7|         |
| [CH0]   [CH3]   [SB]       |                       |         | Node n2
|                     3310-A |                       |         |
| [CH1]   [CH2]---[DB]       |                       |         |
+---|------------------------+            +----------|- PCI4   |
+--------------------------------+   /         t7+---------+
t0                                \ /
/
t0                        / \
+------------------------+   \           +---------+
+-----------|----------------+            +----------|- PCI1   |
| [CH0]   [CH3]   [SB]       |                     t7|         |
|                     3310-B |                       |         |
| [CH1]   [CH2]---[DB]       |                       |         | Node n1
+---|------------------------+                       |         |
+------------------------------------------------|- PCI4   |
t0                                             t7+---------+
- From node side :
Luns belonging to 3310-A will be seen as cxt0d[0-n]
(i.e. : c2t0d[0-2]) on each node)
Luns belonging to 3310-B will be seen as cyt0d[0-n]
(i.e. : c3t0d[0-2]) on each node)
3310 with JBOD (Just a Bunch Of Disks) extension
------------------------------------------------
With a JBOD extension to a Raid-Head, the single bus configuration is the
only one supported.
See SunAlert < Document: 1000500.1 > : Dual-Bus Sun StorEdge 3310 JBOD Configurations
may Lose SCSI Termination in a Multi-Initiator Environment
We use the same config as before : same LDs, Luns and mapping.
- Drawing
t0-t1                                      +---------+
+----------------------------------------|- PCI1   |
+-----------|----------------+                     t7|         |
| [CH0]   [CH3]   [SB]       |                       |         |
|   |               |        |                       |         | Node n2
|   +---------------+ 3310-A |                       |         |
|                            |                       |         |
| [CH1]   [CH2]   [DB]       |                       |         |
+---|-------|----------------+                  +----|- PCI4   |
+-------|-----------------------+          /   t7+---------+
t0-t1   t7+t6----------------+     \        /
+----------------------------+ |      \      /
|  [B out]     +---[A out]   | |       \    /
|             /       JBOD-A | |        \  /
|   [B in]---+      [A in]   | |         \/
+----------------------|-----+ |         /\
+-------+        /  \
/    \
/      \
t0-t1                      /        \
+-----------------------+          \     +---------+
+-----------|----------------+                  +----|- PCI1   |
| [CH0]   [CH3]   [SB]       |                     t7|         |
|   |               |        |                       |         |
|   +---------------+ 3310-B |                       |         | Node n1
|                            |                       |         |
| [CH1]   [CH2]   [DB]       |                       |         |
+---|-------|----------------+                       |         |
+-------|----------------------------------------|- PCI4   |
t0-t1   t7+t6----------------+                   t7+---------+
+----------------------------+ |
|  [B out]     +---[A out]   | |
|             /       JBOD-B | |
|   [B in]---+      [A in]   | |
+----------------------|-----+ |
+-------+
LD0 is created first, on RAID-head, assigned to the Primary controller.
These Luns on LD0 will be created and presented via t0 (PID=0) to both nodes.
PID is set to 7 on CH2  (6 in internal) to access to the JBOD.
New LDs in the JBOD should be created on the secondary controller if there
is one. If not , assign the LDs in the JBOD to the primary controller too.
The Secondary Controller ID (SID) should be set to 1 (SID=1 <> PID=0).
All Luns mapped to Channels (CH1 & CH3) via the Secondary ctrl will be seen
with a t1 target (inherited from SID definition) on the node side.
If there is no secondary, all LUNs will be presented via cXt0dX as well.
If you run out of assignable LUNs (maximum 32 per target) it is possible to
assign a 2nd target to a controller. Make sure to map it to both CH1 and
CH3 as well.
You can then assign the next 32 LUNs to the 2nd target.

This solution has no attachment