Peter's Solaris Zone

StorEdge 3320 basic configuration

The Sun StorEdge 3320 array is a SCSI array. Most of what I say here applies equally well to the 3310 array, which preceded it. The main difference is that the 3320 uses Ultra320 SCSI and the 3310 was Ultra160.

Like the 3510 (fiber channel) array, the 3320 has dual controllers for redundancy. Unlike the 3510, the 3320 doesn't have multiple SCSI paths to a host. You can attach 2 hosts, but you can't make the host connection redundant.

If you're just connecting 1 host, then the simplest is to join the scsi ports labelled "0" and "single bus conf", and connect the host to scsi port "1".

Connecting to the serial port

You can talk to the array over the SCSI connection (see next section), via a serial port, or over a network. You're likely to need a serial port at some stage, so you may as well set it up.

To make this easier, I have the following entry in /etc/remote, with the correct settings for the StorEdge 3000 series:


Then all I need to do is tip se3310 and I'm in. Then type ctrl-L to refresh the screen, maybe scan through some messages, and select the desired terminal emulation (normally VT100) to get to the main interface.

Software Installation

While you can attach a terminal to the serial port of the array, you can also use in-band management tools - sccli. You need to download this first, of course, and then install on the host.

(I haven't found a really good link. If you go to Sun's download site and go to the A-Z tab, then look under S for "Sun StorEdge [tm] 3000 Family Storage Products--Related Software" or some such. This is what you'll need for any of the 3000 series arrays, scsi or fibre.)

After installing the software, running sccli should connect you to the array.

Creating LUNs

The first thing you'll need to do is create some LUNs. Before actually doing that, you'll probably need to delete the factory supplied LUNs, which exist solely for sccli to see the array.

The first thing to do is to remove the Host lun mappings. Then delete the initial LUNs. Then create new ones as required. And then map the LUNs.

If you're connected to the serial port, go to the "view and edit Host luns" menu. You get the two controllers showing. Hit return to see the luns mapped to each controller. (The factory configuration has one lun per controller just to bootstrap things, but you'll never want to use those.) Hit return on a selected lun and it will ask for delete confirmation. (If you move to an empty slot you get into the add a lun menu.)

Once you've got rid of the lun mappings, go to the first menu "view and edit Logical drives". Hitting return on a selected logical drive brings up the actions menu, for which you can delete it.

To create a logical drive, go to the first menu "view and edit Logical drives". Hit return on an empty logical drive, say you want to create a logical drive, and choose your raid level and drives.

Then go back to the "view and edit Host luns" menu. Select the channel you've connected the host to, and select an empty lun. Hitting return, it will ask you whether you want a logical drive or volume, and then give you a list - just select the one you want and hit return.

LUN configuration

How should you set up your LUNs? Well, that's really up to you! After all, I guess you know what you're going to use this for.

However, I invariably create a single large raid-5 lun with a hot spare. So the host sees a single 10-disk sized object, and you can then split it up with partitions.

The reason I do it this way is to keep things simple. Simplicity always wins. It also defers the need for you to make decisions about how to split the space up until later. I also tend to create a single large filesystem (or maybe 2 if I need to keep the filesystem size under a terabyte to get a ufs filesystem with sane parameters).

Peter's Home | Zone Home