Sun StorEdge 3000 Family RAID Firmware 4.2x User's Guide

This chapter lists default configurations and provides guidelines you need to be aware of when configuring your array.

This chapter covers the following topics:

• Default Configurations
• Default Logical Drive Configuration
• Default Channel Configurations

• Maximum Drive Configurations per Array
• Maximum Number of Disks and Maximum Usable Capacity per Logical Drive
• Controller Operation Guidelines
• Dual-Controller Guidelines
• Single-Controller Guidelines

• Cache Optimization Mode and Stripe Size Guidelines
• Cache Write Policy Guidelines
• Fibre Connection Protocol Guidelines
• A Sample SAN Point-to-Point Configuration
• A Sample DAS Loop Configuration
• Array Configuration Summary

---

Default Configurations

This section provides default configuration information for drives and channel settings.

Default Logical Drive Configuration

Sun StorEdge 3000 family arrays are preconfigured with a single RAID 0 logical drive mapped to LUN 0, and no spare drives. This is not a usable configuration. You must delete this logical drive and create new logical drives, as shown in First-Time Configuration for SCSI Arrays and First-Time Configuration for FC or SATA Arrays.

Default Channel Configurations

Sun StorEdge 3000 family arrays are preconfigured with the channel settings shown in the following tables. The most common reason to change a host channel to a drive channel is to attach expansion units to a RAID array.

Sun StorEdge 3310 SCSI array default channel settings are shown in TABLE 3-1.

Sun StorEdge 3510 FC array default channel settings are shown in TABLE 3-2.

Sun StorEdge 3511 SATA array default channel settings are shown in TABLE 3-3.

---

Maximum Drive Configurations per Array

TABLE 3-4 lists the maximum number of physical and logical drives, partitions per logical drive and logical volume, and maximum number of logical unit number (LUN) assignments for each array.

---

Maximum Number of Disks and Maximum Usable Capacity per Logical Drive

The following tables show the maximum number of disks per logical drive, and the maximum usable capacity of a logical drive, depending on RAID level and optimization mode.

The maximum capacity per logical drive supported by the RAID firmware is:

• 16 Tbyte with random optimization
• 64 Tbyte with sequential optimization

Actual logical drive maximum capacities are usually determined by practical considerations or the amount of disk space available.

Caution - In FC and SATA configurations with large drive capacities, the size of the logical drive might exceed the device capacity limitation of your operating system. Be sure to check the device capacity limitation of your operating system before creating the logical drive. If the logical drive size exceeds the capacity limitation, you must partition the logical drive.

TABLE 3-5 shows the usable capacity of the drives available in Sun StorEdge 3000 family arrays.

TABLE 3-6 shows the maximum usable storage capacity for Sun StorEdge 3310 SCSI arrays, Sun StorEdge 3320 SCSI arrays, Sun StorEdge 3510 FC arrays, and Sun StorEdge 3511 SATA arrays, using the maximum number of expansion units, fully populated with the largest currently available drives.

TABLE 3-7 shows the maximum number of disks that can be used in a single logical drive, based upon the drive size, and the optimization method chosen.

TABLE 3-8 shows the maximum usable capacity of a single logical drive in a Sun StorEdge 3510 FC array, depending on drive size.

TABLE 3-9 shows the maximum usable capacity of a single logical drive in a Sun StorEdge 3310 SCSI array, depending on drive size.

TABLE 3-10 shows the maximum usable capacity of a single logical drive in a Sun StorEdge 3511 SATA array, depending on drive size.

---

Controller Operation Guidelines

This section provides guidelines for dual-controller and single-controller operation.

Dual-Controller Guidelines

Keep the following operation details in mind when configuring a dual-controller array.

• The controller firmware assumes that two controllers are available, or might be made available during operation at any time. In a one-rack-unit (1U) single-controller configuration, a two-rack-unit (2U) single-controller configuration, or a 2U dual-configuration, once the primary controller (which might be the only controller) is powered on, it begins to scan for a second controller. Until a second controller is discovered, which does not happen in a 1U single-controller configuration or a 2U single-controller configuration, the Peripheral Device Status for the redundant controller shows a status of Scanning. This is correct behavior and enables the firmware to discover a second controller whenever it is added without the necessity of rebooting the primary controller.
• After booting, the controllers autonegotiate and designate one controller as primary and the other controller as secondary.
• The two controllers behave as one primary controller. Once redundancy takes effect, configuration can be applied only to the primary controller. The secondary controller then synchronizes with the configuration of the primary controller, making the configurations of the two controllers exactly the same.

Caution - Major upgrades of controller firmware, or replacing a controller with one that has a significantly different version of firmware, might involve differences in non-volatile RAM (NVRAM) that require following special upgrade procedures. For more information, refer to the Sun StorEdge 3000 Family FRU Installation Guide and to the release notes for your array.

The two controllers continuously monitor each other. When either controller detects that the other controller is not responding, the working controller immediately takes over and disables the failed controller.

• In an active-to-active configuration (standard configuration), you can assign any logical drive to either of the controllers, and then map the logical configurations to host channel IDs and LUNs. I/O requests from a host computer are directed to the primary or the secondary controller accordingly. The total drive capacity can be grouped into several logical drives and assigned to both controllers so that they share the workload. This active-to-active configuration engages all array resources to actively maximize performance.

An active-to-standby configuration is also available but is not usually selected. In this configuration, assigning all the logical drives to one controller means that the other controller remains idle, becoming active only if the primary controller fails.

Single-Controller Guidelines

Keep the following operation details in mind when configuring a single-controller array.

• The controller must be the primary controller or the controller cannot operate. The primary controller controls all logical drive and firmware operations. Keep the controller as the primary controller at all times and assign all logical drives to the primary controller.

A secondary controller is used only in dual-controller configurations for redistributed I/O and for failover.

• In a single-controller configuration, disable the Write-Back Cache feature to avoid the possibility of data corruption in the event of a controller failure. This has a negative effect on performance. To avoid either issue, use dual controllers.

Using two single controllers in a clustering environment with host-based mirroring provides some of the advantages of using a dual controller. However you still need to disable the Write-Back Cache in case one of the single controllers fails, to avoid the risk of data corruption. For this reason, a dual controller configuration is preferable.

• For a single-controller configuration, the Peripheral Device Status shows a status of Scanning, which indicates that the firmware is scanning for primary and secondary controller status and redundancy is enabled even though it is not used. There is no performance impact.
• If you are using a single controller, save your NVRAM after any configuration changes so that you can restore it in the event of a controller failure and replacement. See Saving Your Configuration (NVRAM) to Disk and Restoring Your Configuration (NVRAM) From Disk for more information.

Caution - Major upgrades of controller firmware, or replacing a controller with one that has a significantly different version of firmware, might involve differences in non-volatile RAM (NVRAM) that require following special upgrade procedures. For more information, refer to the Sun StorEdge 3000 Family FRU Installation Guide and to the release notes for your array.

• Also keep a written record of your configuration, including the firmware version number, using tables similar to those found in Appendix C. Major firmware upgrades or downgrades can require manually recreating your configuration from these records, since no synchronization from a second controller is possible. Refer to the Sun StorEdge 3000 Family FRU Installation Guide for information about replacing controllers.

---

Cache Optimization Mode and Stripe Size Guidelines

Before creating or modifying logical drives, determine the appropriate optimization mode for the RAID array. The controller supports two optimization modes, sequential I/O and random I/O. Sequential I/O is the default mode.

When you specify sequential or random cache optimization, the controller determines a default stripe size for newly-created logical drives. But you can specify whatever stripe size you choose for each logical drive when you create it, enabling you to maximize performance by matching stripe size with your application requirements. Since different applications may use different logical drives, this functionality provides you with greatly increased flexibility.

• For sequential optimization, available stripe size choices include 16 Kbyte, 32 Kbyte, 64 Kbyte, 128 Kbyte, and 256 Kbyte.
• The default stripe size for sequential optimization is 128 Kbyte for all logical drives except RAID 3, which is 16 Kbyte.
• For sequential optimization, the cache block size is 128 Kbyte.
• For random optimization, available stripe size choices include 4 Kbyte, 8 Kbyte, 16 Kbyte, 32 Kbyte, 64 Kbyte, 128 Kbyte, and 256 Kbyte.
• The default stripe size for random optimization is 32 Kbyte for all logical drives except RAID 3, which is 4 Kbyte.
• For random optimization, the cache block size is 32 Kbyte.

See Cache Optimization Mode (SCSI) for information about how to set the cache optimization mode on a Sun StorEdge 3310 SCSI array or Sun StorEdge 3320 SCSI array. See Cache Optimization Mode (FC and SATA) for information about how to set the cache optimization mode for a Sun StorEdge 3510 FC array or Sun StorEdge 3511 SATA array.

The RAID array's cache optimization mode determines the cache block size used by the controller for all logical drives. An appropriate cache block size improves performance when a particular application uses either large or small stripe sizes:

• Video playback, multimedia post-production audio and video editing, and similar applications read and write large files in sequential order.
• Transaction-based and database update applications read and write small files in random order.

Once logical drives are created, you cannot use the RAID firmware's Optimization for Random I/O or Optimization for Sequential I/O menu option to change the optimization mode without deleting all logical drives. You can, however, use the Sun StorEdge CLI set cache-parameters command to change the optimization mode while logical drives exist. Refer to the Sun StorEdge 3000 Family CLI 2.0 User's Guide for more information.

Since the cache block size works in conjunction with stripe size, the optimization mode you choose determines default logical drive stripe sizes that are consistent with the cache block size setting. But you can now fine-tune performance by specifying each logical drive's stripe size so that it matches your application needs, using a firmware menu option that is available at the time you create the logical drive. See Cache Optimization Mode and Stripe Size Guidelines for more information.

See (Optional) Configure the logical drive stripe size. for information about how to set the stripe size for a logical drive you are creating on a Sun StorEdge 3310 SCSI array or Sun StorEdge 3320 SCSI array. See (Optional) Configure the logical drive stripe size. for information about how to set the stripe size for a logical drive you are creating on a Sun StorEdge 3510 FC array or Sun StorEdge 3511 SATA array.

---

Cache Write Policy Guidelines

The cache write policy determines when cached data is written to the disk drives. The ability to hold data in cache while it is being written to disk can increase storage device speed during sequential reads. Write policy options include write-through and write-back.

When write-through cache is specified, the controller writes the data to the disk drive before signaling the host operating system that the process is complete. Write-through cache has slower write operation and throughput performance than write-back cache, but it is safer, with minimum risk of data loss on power failure. Because a battery module is installed, power is supplied to the data cached in memory and the data can be written to disk after power is restored.

When write-back cache is specified, the controller receives the data to write to disk, stores it in the memory buffer, and immediately sends the host operating system a signal that the write operation is complete, before the data is actually written to the disk drive. Write-back caching improves the performance of write operations and the throughput of the controller card.

Write-back cache is enabled by default. When you disable write-back cache, write-through cache is automatically enabled. The setting you specify becomes the default global cache setting for all logical drives. With RAID firmware version 4.11 and later, the cache setting can now be individually tailored for each logical drive. When you configure a logical drive, you can set its individual cache write policy to default, write-back, or write-through.

If you specify default for an individual logical drive, the global write policy is assigned to it. Then, if the global cache write policy that applies to the entire RAID array is changed, any logical drive that has been assigned the default setting write policy is also changed.

If you specify write-back or write-through for an individual logical drive, the cache write policy for that drive remains the same regardless of any changes to the global cache write policy.

If you have specified a global write-back policy, you can also configure the RAID array to automatically change from a write-back cache policy to a write-through cache policy when one or more of the following trigger events occur:

• Controller failure
• Battery-backup unit failure or battery not fully charged
• Power supply failure
• Fan failure

Once the condition that led to the trigger event is rectified, the cache policy automatically returns to its previous setting. For more information on configuring the write policy to automatically switch from write-back cache to write-through cache, see Event Trigger Operations.

---

Fibre Connection Protocol Guidelines

Sun StorEdge 3510 FC arrays and Sun StorEdge 3511 SATA arrays support the following connection protocols:

• Point-to-Point

This protocol can be used only with a switched fabric network configuration, also called a storage area network (SAN). The point-to-point protocol supports full duplex communication, but only allows one ID per channel.

• Fibre Channel-Arbitrated Loop (FC-AL), also known as loop mode

The loop mode can be used with direct-attached storage (DAS) or SAN configurations. Loop mode supports only half-duplex communication, but allows up to eight IDs per channel.

The following guidelines apply when implementing point-to-point configurations and connecting to fabric switches.

• The default mode is Loop only. If you prefer to use a point-to-point configuration, change the Fibre Channel Connection mode to Point-to-point only. See Fibre Connection Protocol for information about how to change this setting.

• Check the host IDs on all the channels to ensure that there is only one ID per channel (on the primary controller or on the secondary controller) for point-to-point mode. When viewing the host IDs, there should be one primary controller ID (PID) or one secondary controller ID (SID); the alternate port ID should display N/A. Proper point-to-point mode allows only one ID per channel.
• If you change the mode to Point-to-point only and attempt to add a second ID, the controller does not allow you to add an ID to the same channel. For example, if you have ID 40 on CH 0 PID, and N/A on CH 0 SID, the controller does not allow you to add another PID to CH 0.

The controller displays a warning if the user is in point-to-point mode and tries to add an ID to the same channel but on the other controller. The warning is displayed because you have the ability to disable the internal connection between the channels on the primary and secondary controller using the set inter-controller link CLI command and, by doing this, you can have one ID on the primary and another ID on the secondary as a legal operation.

However, if you ignore this warning and add an ID to the other controller, the RAID controller does not allow a login as an FC-AL port because this would be illegal in a point-to-point configuration.

• You can add up to eight IDs per channel (four IDs on each controller), which forces the fabric switch port type to become FC-AL (Loop). To ensure F-port behavior (full fabric/full duplex) when attaching to a switch, only one ID can be present on each channel and the array port must be set to point-to-point mode.
• With four host channels and four host IDs, you should load-balance the host ID setup so that half the IDs are on the primary controller and half the IDs are on the secondary controller. When setting up LUNs, map each LUN to either two PIDs or two SIDs. For example, to provide redundancy, map half of the LUNs across Channel 0 (PID 40) and Channel 4 (PID 42), and then map the other half of your LUNs across Channel 1 (SID 41) and Channel 5 (SID 43). The hosts are in turn dual-pathed to the same two switched fabrics.
• Point-to-point mode enables a maximum of 128 LUNs per array. In a redundant configuration, 32 LUNs are dual-mapped across two channels on the primary controller, and another 32 LUNs are dual-mapped across the secondary controller, for a total of 64 distinct LUNs.

To use more than 64 LUNs, you must change to Loop only mode, add host IDs to one or more channels, and add 32 LUNs for each host ID.

---

A Sample SAN Point-to-Point Configuration

A point-to-point configuration has the following characteristics:

• In SAN configurations, the switches communicate with the host ports on a Sun StorEdge 3510 FC array or Sun StorEdge 3511 SATA array using a fabric point-to-point (F_port) mode.
• When you use fabric point-to-point (F_port) connections between a Sun StorEdge 3510 FC array or Sun StorEdge 3511 SATA array and fabric switches, the maximum number of LUNs is limited to 128 LUNs for a nonredundant configuration and 64 LUNs for a redundant configuration.
• Fibre Channel standards allow only one ID per port when operating point-to-point protocols, resulting in a maximum of four IDs with a maximum of 32 LUNs for each ID, and a combined maximum of 128 LUNs.
• The working maximum number of LUNs is actually 64 LUNs in a configuration where you configure each LUN on two different channels for redundancy and to avoid a single point of failure.

In a dual-controller array, one controller automatically takes over all operation of a second failed controller in all circumstances. However, when an I/O controller module needs to be replaced and a cable to an I/O port is removed, that I/O path is broken unless multipathing software has established a separate path from the host to the operational controller. Supporting hot-swap servicing of a failed controller requires the use of multipathing software, such as Sun StorEdge Traffic Manager software, on the connected servers.

Remember these important considerations:

• A single logical drive can be mapped to only one controller, either the primary controller or the secondary controller.
• In a point-to-point configuration, only one host ID per channel is allowed. The host ID can be assigned to the primary controller and be a PID, or it can be assigned to the secondary controller and be a SID.
• If you have two switches and set up multipathing (to keep all logical drive connections operational for any switch failure or the removal of any I/O controller module), ensure that each logical drive is mapped to two ports, one on each I/O controller module, and on two channels. The cables from the two ports mapped to each logical drive must be cabled to two separate switches. See FIGURE 3-1 and FIGURE 3-2 for examples of this configuration.

The following figures show the channel numbers (0, 1, 4, and 5) of each host port and the host ID for each channel. N/A means that the port does not have a second ID assignment. The primary controller is the top I/O controller module, and the secondary controller is the bottom I/O controller module.

The dashed lines between two ports indicate a port bypass circuit that functions as a mini-hub and has the following advantages:

• The port bypass circuit on each channel connects the upper and lower ports on the same channel and provides access to both controllers at the same time.
• Since there are host connections to two channels, if one host connection is removed, the other host connection remains operational.
• Therefore, if you have a redundant multipathing configuration in which you have two host connections to each logical drive and one connection fails, the remaining path maintains a connection to the logical drive.

In FIGURE 3-1 and FIGURE 3-2, with multipathing software to reroute the data paths, each logical drive remains fully operational when the following conditions occur:

• One switch fails or is disconnected, and the logical drive is routed to the second switch. For example, if switch 0 fails, switch 1 automatically accesses logical drive 0 through the cabling to the lower port on PID 42.
• One I/O controller module fails, and all the host IDs for that controller are reassigned (moved) to the second 1/O controller module. For example, if the upper I/O controller module is removed, host IDs 40 and 44 are automatically moved to the lower module and are managed by the second controller.
• An I/O controller module fails or one cable is removed from an I/O controller module, and all I/O traffic to the disconnected channel is rerouted through the second port/host LUN assigned to the logical drive. For example, if you remove the cable to channel 4, the data path for logical drive 1 switches to the port on channel 5.

  FIGURE 3-1 A Point-to-Point Configuration with a Dual-Controller Sun StorEdge 3510 FC Array and Two Switches

  FIGURE 3-2 A Point-to-Point Configuration With a Dual-Controller Sun StorEdge 3511 SATA Array and Two Switches

TABLE 3-11 summarizes the primary and secondary host IDs assigned to logical drives 0 and 1, based on FIGURE 3-1 and FIGURE 3-2.

Perform the following steps, which are described in more detail later in this guide, to set up a typical point-to-point SAN configuration based on FIGURE 5-1 and FIGURE 5-2.

1. Check the position of installed small form-factor pluggable transceivers (SFPs). Move them as necessary to support the connections needed.

You need to add SFP connectors to support more than four connections between servers and a Sun StorEdge 3510 FC array or Sun StorEdge 3511 SATA array. For example, add two SFP connectors to support six connections and add four SFP connectors to support eight connections.

2. Connect expansion units, if needed.

3. Create at least two logical drives (logical drive 0 and logical drive 1) and configure spare drives.

Leave half of the logical drives assigned to the primary controller (default assignment). Assign the other half of the logical drives to the secondary controller to load-balance the I/O.

4. Create up to 32 partitions (LUNs) in each logical drive.

5. Change the Fibre Connection Option to "Point to point only" ("view and edit Configuration parameters Host-side SCSI Parameters Fibre Connections Option").

6. For ease of use in configuring LUNs, change the host IDs on the four channels to the following assignments:

Channel 0: PID 40 (assigned to the primary controller)

Channel 1: PID 41 (assigned to the primary controller)

Channel 4: SID 50 (assigned to the secondary controller)

Channel 5: SID 51 (assigned to the secondary controller)

7. Map logical drive 0 to channels 0 and 1 of the primary controller.

Map LUN numbers 0 through 31 to the single ID on each host channel.

8. Map logical drive 1 to channels 4 and 5 of the secondary controller.

Map LUN numbers 0 through 31 to the single ID on each host channel. Since each set of LUNs is assigned to two channels for redundancy, the total working maximum number of LUNs is 64 LUNs.

9. Connect the first switch to ports 0 and 4 of the upper controller.

10. Connect the second switch to ports 1 and 5 of the lower controller.

11. Connect each server to each switch.

12. Install and enable multipathing software on each connected server.

The multipathing software prevents path failure but does not alter the controller redundancy through which one controller automatically takes over all functions of a second failed controller.

---

A Sample DAS Loop Configuration

The typical direct attached storage (DAS) configuration shown in FIGURE 3-3 and FIGURE 3-4 includes four servers, a dual-controller array, and two expansion units. Expansion units are optional.

Servers, as shown in FIGURE 3-3 and FIGURE 3-4, are connected to the channels shown in TABLE 3-12.

Establishing complete redundancy and maintaining high availability requires the use of multipathing software such as Sun StorEdge Traffic Manager software. To configure for multipathing:

1. Establish two connections between each server and the array.

2. Install and enable multipathing software on the server.

3. Map the logical drive each server is using to the controller channels that the server is connected to.

DAS configurations are typically implemented using a fabric loop (FL_port) mode. A loop configuration example is described under A Sample DAS Loop Configuration.

Fabric loop (FL_port) connections between a Sun StorEdge 3510 FC array or Sun StorEdge 3511 SATA array and multiple servers allow up to 1024 LUNs to be presented to servers. For guidelines on how to create 1024 LUNs, see Planning for 1024 LUNs on an FC or SATA Array (Optional, Loop Mode Only).

  FIGURE 3-3 A DAS Configuration With Four Servers, a Dual-Controller Sun StorEdge 3510 FC Array, and Two Expansion Units

  FIGURE 3-4 A DAS Configuration With Four Servers, a Dual-Controller Sun StorEdge 3511 SATA Array, and Two Expansion Units

Perform the following steps, which are described in more detail later in this manual, to set up a DAS loop configuration based on FIGURE 3-3 and FIGURE 3-4.

1. Check the location of installed SFPs. Move them as necessary to support the connections needed.

You need to add SFP connectors to support more than four connections between servers and a Sun StorEdge 3510 FC array or Sun StorEdge 3511 SATA array. For example, add two SFP connectors to support six connections and add four SFP connectors to support eight connections.

2. Connect expansion units, if needed.

3. Create at least one logical drive per server, and configure spare drives as needed.

4. Create one or more logical drive partitions for each server.

5. Confirm that the Fibre Connection Option is set to Loop only.

6. Set up to eight IDs on each channel, if needed (see TABLE 3-13).

7. Map logical drive 0 to channels 0 and 5 of the primary controller.

8. Map logical drive 1 to channels 1 and 4 of the secondary controller.

9. Map logical drive 2 to channels 0 and 5 of the primary controller.

10. Map logical drive 3 to channels 1 and 4 of the secondary controller.

11. Connect the first server to port FC 0 of the upper controller and port FC5 of the lower controller.

12. Connect the second server to port FC 4 of the upper controller and port FC1 of the lower controller.

13. Connect the third server to port FC 5 of the upper controller and port FC0 of the lower controller.

14. Connect the fourth server to port FC 1 of the upper controller and port FC4 of the lower controller.

15. Install and enable multipathing software on each connected server.

---

Array Configuration Summary

This section lists the typical sequence of steps for completing a first-time configuration of the array. For detailed steps and more information, see the referenced sections.

Typical steps for completing a first-time configuration of the array are as follows:

1. Set up the serial port connection.

2. Set an IP address for the controller.

See Setting an IP Address.

3. Determine whether sequential or random optimization is more appropriate for your applications and configure your array accordingly.

See Cache Optimization Mode and Stripe Size Guidelines for more information. Also see Cache Optimization Mode (SCSI) for information about how to configure a SCSI array's optimization mode, or Cache Optimization Mode (FC and SATA) for information about how to configure an FC or SATA array's optimization mode.

4. Check physical drive availability.

See To Check Physical Drive Availability for a SCSI array. See Physical Drive Status for FC or SATA arrays.

5. (Optional) Configure host channels as drive channels.

See Channel Settings for a SCSI array. See Channel Settings for FC or SATA arrays.

6. For a Fibre Channel or SATA array, confirm or change the Fibre Connection Option (point-to-point or loop).

See Fibre Connection Protocol Guidelines and Fibre Connection Protocol for the procedure to configure the Fibre Connection protocol.

7. Revise or add host IDs on host channels.

See To Add or Delete a Unique Host ID for SCSI arrays. See To Add or Delete a Unique Host ID for FC or SATA arrays.

The IDs assigned to controllers take effect only after the controller is reset.

8. Delete default logical drives and create new logical drives as required.

See Deleting Logical Drives and Creating Logical Drives for SCSI arrays. See Deleting Logical Drives and Creating Logical Drives for FC or SATA arrays.

9. (Optional) In dual-controller configurations only, assign logical drives to the secondary controller to load-balance the two controllers.

See Controller Assignment for a SCSI array. See Controller Assignment for FC or SATA arrays.

10. (Optional) Partition the logical drives.

See Partitions for SCSI arrays. See Partitions for Fibre Channel and SATA arrays.

11. Map each logical drive partition to an ID on a host channel.

For more information, see Mapping a Partition to a Host LUN for SCSI arrays.

For information about different operating system procedures, refer to the Sun StorEdge 3000 Family Installation, Operation and Service Manual for your array.

12. (Optional) Create and apply host LUN filters to FC or SATA logical drives.

See Mapping a Partition to a Host LUN for Fibre Channel and SATA arrays.

13. Reset the controller.

The configuration is complete.

14. Save the configuration to a disk.

See Saving Configuration (NVRAM) to a Disk.

15. Ensure that the cabling from the RAID array to the hosts is complete.

Refer to the Sun StorEdge 3000 Family Installation, Operation and Service Manual for your array.

^{1 (TableFootnote) Sun StorEdge 3511 SATA expansion units can be connected to a Sun StorEdge 3510 FC array, either alone or in combination with Sun StorEdge 3510 FC expansion units}

Sun StorEdge 3000 Family RAID Firmware 4.2x User's Guide

817-3711-18

Copyright © 2009, Dot Hill Systems Corporation. All rights reserved.