VTrak E5000 Articles

How to save a SMART log of HDD/SSD for further analysis?

2025-11-05T07:32:31.5630000

A SMART log (Self-Monitoring, Analysis, and Reporting Technology) is built into PROMISE Vtrak and Vess RAID storage systems that monitors the health and performance of the drive and SSD and then can predict potential failures. It logs various attributes like read error rates, seek error rates, spin-up time, and temperature, providing insights into the drive's condition. By analyzing these logs, technician can identify potential problems before they lead to data loss or drive failure.

Please follow these procedures to collect the SMART log.

1].Login the WebPAM PROe

1.1] Open browser and put the management portal IP

1.2] put administrator account

1.3] default password is password

2].Enable SMART log.

Go to Devices > Component List > Controller > Settings > Controller settings

3].Export SMART log.

Go to Administration > Import/Export > Export > Select "SMART log" from Drop-down menu

VTrak E5000 Series Tutorial Videos : Intro, Cabling, Initial Setup, Mount and Access and Support and Component Replacement

2024-11-20T17:58:25.0070000

Introduction

Cabling

Initial Setup

Mount and Access

Support and Component Replacement

VTrak E5000 Series Power Consumption

2024-11-15T14:49:45.6370000

These numbers are derived from fully populated VTrak E5x00 chassis utilizing SAS drives under full load:

Product	Input Voltage (VAC)	Power (Watts)	Thermal Output (BTU/hour)
E5300fD	120	308	1051
E5320fD	120	357	1218
E5600fD	120	335	1143
E5800fD	120	421	1437
E5300fD	230	296	1011
E5320fD	230	348	1188
E5600fD	230	334	1140
E5800fD	230	417	1423

How to save the Service Report in VTrak E5000 Series

2024-11-05T19:51:41.7000000

In most troubleshooting scenarios, Promise Support will require the Service report to diagnose the problem effectively. This report contains event logs, configuration details, and the status of all hardware components.

Saving from the Home Page :

Log in to the Web Interface of the unit.
Click the “Save Service Report” icon located at the top right corner of the screen to generate the report.

The report will be saved as a compressed zip folder.
Unzip the folder to view the generated report.

Note: Generating the report may take a few minutes depending on the size of the array configuration.

Enabling multipathing (MPIO) on Windows Server 2019

2024-10-31T14:35:37.2000000

Introduction

In some storage configurations, it is possible to have multiple paths from the server to the storage. This is often done for redundant paths or higher bandwidth. Typically multipathing is used in Fibre Channel SANs, in SAS attached storage and in some iSCSI connections.

When there is a multipath configuration, Windows Disk Magagment tool will show the same device multiple times. In the example below the same LUN is seen 4 times by Windows Server.

But there is only (1) LUN. It will be necessary to enable Windows MPIO to see only that one LUN.

Enabling Windows MPIO

To enable Windows MPIO , from the Server Manager select Add Roles and Features.

MPIO is a feature, click Next until you get to the features. Scroll down and enable MPIO.

Click Next and click the Install button.

Once the install is complete, close the Wizard and reboot the server.

Once the server is booted, click the Start menu and type in MPIO

Click MPIO to open the MPIO applet. Select the Discover Multi-Paths tab on top, select the Promise device in Others and click Add.

Another restart will be required. After the reboot the Disk Management tool shows only one disk.

To change the pathing policy open the device manager and select properties for the multipath promise LUN.

Select the MPIO tab at the top and the drop-down menu shows the pathing policies Windows supports.

For best bandwidth Least Queue Depth is suggested.

For iSCSI

iSCSI multipathing is an option in the MPIO applet. Select the Discover Multi-Paths tab and click Add Support for iSCSI devices. Another reboot will be required.

Once Multipathing has been enabled the LUN can be formatted NTFS from the Disk Management console.

Updating Firmware on the VTrak E5000 Subsystem

2024-10-31T13:07:17.6630000

To update the firmware on the VTrak E5000, follow these steps:

1. Download the latest firmware image file from PROMISE support by visiting the website at http://www.promise.com/support/. Save the file to your Host PC or TFTP server.

2. Before proceeding, ensure that no background activities are running on the RAID subsystem.

3. Access the Administration tab and navigate to the Firmware Update section.

4. Choose a download option:
- Local File through HTTP: Click the "Choose File" button, locate the firmware image file on your system, select it, and click "Open."
- TFTP Server: Enter the TFTP Server host name or IP address, port number, and file name.

5. Optionally, you can check the "Non-disruptive Image Update (NDIU)" box. This feature updates the RAID controllers and I/O modules one at a time, allowing I/O operations to continue during the firmware update. Note that updates with this option take longer to complete and are only supported by dual controller models.

6. Click the "Download" button. The subsequent screen will display the Flash Image (firmware image file) Version Number and Build Date.

7. Click "Submit" to initiate the firmware update. The progress of the update will be shown.

Important: Do not power off the subsystem during the update and refrain from navigating to other screens until the firmware update operation is completed.

Once the update is finished, a message will prompt you to reboot the subsystem. Click "OK."

- If you selected the Disruptive Flash Method, the RAID subsystem and JBOD expansion units will automatically restart.
- If you chose the Non-Disruptive Flash Method, the system will automatically flash and restart the RAID controllers one at a time.

Automatic Restart: If the NDIU box was not checked, the RAID subsystem and JBOD expansion units will automatically restart. This action temporarily disrupts I/O operations and may cause your WebPAM PROe connection to drop. To reestablish the connection, follow these steps:

1. Wait for a minimum of two minutes.
2. Click "Logout" in the WebPAM PROe Header and then log in again. If you encounter login issues, wait for 30 seconds and try again.
3. In your browser, click "Logout" in the WebPAM PROe Header and then log in again. If you cannot log in immediately, wait for 30 seconds and try again.

Battery Reconditioning Process on VTrak E5000 Subsystem

2024-10-31T13:05:51.6930000

Battery reconditioning plays a crucial role in maintaining the power supply to the controller cache, ensuring data integrity in the event of a power failure, particularly for unwritten data residing in the cache. The process of reconditioning involves discharging and subsequently recharging the battery to optimize its overall capacity and performance. It is important to note that reconditioning is performed in the background, potentially impacting the input/output (I/O) performance. Once the reconditioning process is completed, the cycle count of the battery increases by one.Battery reconditioning is enabled and scheduled by default. It is set to run on the first Saturday of January, March, May, July, September, and November. However, it is possible to modify the reconditioning status and schedule according to specific requirements

For an immediate battery reconditioning, follow these steps:

1. Navigate to the Device tab.
2. Click on the Component List icon.
3. Select the desired battery, then click on the Recondition button.
4. If a battery reconditioning is already scheduled, a dialog menu will appear, providing an explanation. To proceed with immediate reconditioning, enter "confirm" in the designated field and click on the Confirm button.
- Please note that during the reconditioning process, the battery's remaining capacity and estimated hold time will fluctuate as a result of the discharge and recharge cycles. This behavior is normal.

To modify the scheduled battery reconditioning, follow these steps:

1. Access the Administration tab.
2. Click on the Background Activities icon, displaying the list of Background Activities.
3. Click on the Scheduler button.
4. Hover over Battery Reconditioning and click on the Settings button.
5. Make the necessary adjustments to the settings, such as:
- Start Time
- Uncheck the Enable This Schedule box to disable the activity.
- Recurrence Pattern
- Start From
- End On

Remember to save the changes by clicking on the Save button to apply the new settings.

E5000: Drive Error Reporting

2018-05-18T21:40:23.4830000

E5000 Hard Drive Error Reporting

5/18/2018

This article describes error threshold settings and actions for the E5000 family of controllers with firmware version 11.05.0000.00 or later. The contents of this article also apply to the Ex30 family of controllers.

This table lists the settings and their default values:

	Default Value
Reassigned Block Threshold (BBM Threshold)	1024
Error Block Threshold (Media Patrol Threshold)	128
Medium Error Threshold	64
SMART	disabled

Definitions:

Reassigned Block Threshold, also called Bad Block Manager Threshold (BBM Threshold), reads the grown defect list on SAS drives (known as the “G List”). On SATA drives, the BBM reads the DDF area written to the drive by the VTrak firmware. Please note that the BBM count can only be cleared on SATA drives, and the array information must be deleted first. If the BBM threshold has been reached, PDM will begin.

PDM- Pleaserefer to http://kb.promise.com/thread/what-is-predictive-data-migration-pdm

Error Block Threshold is also called the Media Patrol Threshold. If the threshold has been reached, PDM will begin. The Media Patrol Threshold is attributed to I/O errors occurring during read/write operations:

PdId: 3
OperationalStatus: OK
Alias:
PhysicalCapacity: 931.51GB              ConfigurableCapacity:931.32GB
UsedCapacity: 931.32GB                     BlockSize:512Bytes
ConfigStatus: Array0 SeqNo1             Location:Encl1 Slot3
ModelNo: SEAGATE ST31000640SS       VisibleTo: AllControllers
SerialNo: 9QJ5AM78                     FirmwareVersion:0003
DriveInterface: SAS 12Gb/s                Protocol:SPC-3
WWN: 5000-c500-1003-839f              NumOfPorts:2
Port1Speed: 12Gb/s                       Port2Speed:12Gb/s
Port1SASAddress: 50-00-c5-00-10-03-83-9d
Port2SASAddress: 50-00-c5-00-10-03-83-9e
WriteCacheSupport: Yes                            WriteCache:Enabled
RLACacheSupport: Yes                              RLACache:Enabled
ReadCacheSupport: Yes                      ReadCache:Enabled
CmdQueuingSupport: Yes                  CmdQueuing:Enabled
MediumErrorThreshold: 0
Errors: 0                           NonRWErrors:0
ReadErrors: 0                                            WriteErrors:0
DriveTemperature: 34C/93F                        ReferenceDriveTemperature:68C/154F

Medium Error Threshold is a global physical drive setting. The value is the number of bad blocks tolerated before the controller marks the drive as dead. The value can be set from 0 to 4294967294. The threshold only functions when the array is in an OK or Degraded state. It will not function if the array is critical or if the array is not a redundant RAID type such as Raid 0.

SMART stands for Self-Monitoring, Analysis, and Reporting Technology. If enabled, a polling interval can be assigned. SMART will report errors detected on the disk and PDM will start if the threshold has been reached.

Configuration:

Setting thresholds from the CLI

BBM Threshold– (1~2048)

administrator@cli>bga -a mod -s "BBMThreshold=1024"

MediaPatrol Threshold – (1~2048)

administrator@cli>bga -a mod -s "MediaPatrolThreahold=128"

MediumError Threshold – (0~4294967294)

administrator@cli>phydrv -a mod -s "mediumerrorthreshold=1024"

SMART

administrator@cli>ctrl -a mod -s "smart=disable"

Setting thresholds from WebPAMProE

BBM Threshold

Media Patrol Threshold

Smart

Perfect Rebuild (Vtrak E5000 Series)

2017-12-20T23:56:55.8100000

The PerfectRebuild feature is an innovative approach to rebuilding a RAID array in order to significantly reduce the amount of time needed for completion.

This frees up CPU resources more quickly to be available for I/O and other demands.

PerfectRebuild ignores any portion of the logical drive where no write changes have occurred, focusing only on the parts that have changed.

The conventional approach has been to rebuild the entire logical drive, even sections with no write changes.

This reduction in the total time needed for a rebuild is especially signi cant for very large drives.

It does this by keeping metadata of the logical drive to track writes to it.

In a normal rebuild, the entire logical drive is rebuilt, even if there’s only 1 file in the logical drive. This takes the same amount of time (hours) no matter how full or empty the Logical Drive is.

Perfect Rebuild keeps track of which blocks of the Logical Drive have ben written to and only rebuilds the parts of the Logical Drive that have been written to, reducing the rebuild time.

How does the VTrak E5000 series calculate the remaining lifetime of SSDs?

2017-06-05T17:34:27.1070000

The VTrak E5000 series can monitor SSDs to evaluate their remaining useful life.

When using any SAS Solid State Disks in the VTrak E5000, the VTrak controllers monitor the “Percentage Used Endurance Indicator” parameter of each SAS SSD to keep track of approximately how much time the SSD has been used.

When using SATA Solid State Disks in the VTrak E5000, the VTrak controllers monitor the SMART attributes from each SATA SSD to keep track of approximately how much time the SSD has been used.

The SMART data attributes are different for the various SATA SSD vendors, so be sure to only use SATA SSDs that are on the VTrak E5000 Compatibilty List if you want to have reliable lifetime data.

The default threshold for SSD Percent Lifetime Remaining is 10, and if this value goes below 10 the VTrak E5000 controllers will begin a Predictive Data Migration (PDM) for that drive to a configured spare drive.

The Percent Lifetime Remaining threshhold can be changed by the user.

If the Percent Lifetime Remaining value falls below the threshold, this will result in an entry in the Event Log of “SSD endurance indicator is lower than threshold” that has a Major severity level.

4Gb SFPs are not Supported on the E5000 Series

2017-03-21T19:33:24.9470000

The E5000 Series' FC ports does not support 4Gb SFPs; however, 4Gb speed negotiation is supported.

The E5000 Series requires a qualified 8Gb or 16Gb SFP to be installed on the controller's FC ports.

VTrak E5000 Series Compatibility List

VTrak E5000 Series Release Notes

Contact Promise Technology Support
Need more help? Save time by starting your support request online and a technical support agent will be assigned to your case.

Promise Technology Technical Support >

Promise VTrak RAID Controllers and SAS-connected Expansion Chassis: Xsan (Metadata and Data) Configuration Script - E5800f + (3) J5600s

2016-10-19T06:39:00.4270000

This article contains a script used to configure Promise VTrak RAID Controllers and SAS-connected Expansion Chassis: Xsan (Metadata and Data) configuration script - E5800f + (3) J5600s

To create the configuration script, copy the text below beginning with the line "#Begin Copy" to the line "#End Copy" and paste the text into TextEdit, using these guidelines. Once you've created the script, follow the guidelines in this article to import the configuration script.

#Begin Copy 
# 
# Promise VTrak E5800f + (3) J5600s Configuration Script 
# 
# Script Name: RAID Controllers and 3 SAS-connected Expansion Chassis: Xsan (Metadata and Data) 
# 
# 
# Script Details: builds 10 LUNs from 72 drives (head + 3 expansion units) 
# in the recommended configuration for use with Xsan and StorNext
# 
# Script Assumptions: no arrays or logical drives created 
# (uncomment out array deletion if needed) 
# script works with either SATA or SAS configurations 
# 
# Global controller settings 
# LUN Affinity: enabled [required] 
# ALUA: enabled [required]
# Adaptive Writeback Cache: enabled [optional] 
# Host Cache Flushing: disabled [optional] 
# Forced Read Ahead: enabled [optional] 
# 
ctrl -a mod -s "lunaffinity=enable, alua=enable, adaptivewbcache=enable, hostcacheflushing=disable, forcedreadahead=enable"
# 
# Delete any existing arrays 
# Delete array 0 thru 9 
# 
#array -a del -d 0 
#array -a del -d 1 
#array -a del -d 2 
#array -a del -d 3 
#array -a del -d 4 
#array -a del -d 5 
#array -a del -d 6 
#array -a del -d 7 
#array -a del -d 8 
#array -a del -d 9 
# 
# Build MDC LUN 
# RAID level: 1 
# Physical Drives: 1, 2 
# Alias: MDC 
# Controller Affinity: 1 
# Configuration options: Capacity all (default), 64K stripe size (default), 
# 512 byte sector (default), Read Cache, Write Back
#
array -a add -p 1,2 -s "alias=MDC" -l "alias=MDC, raid=1, readpolicy=readcache, writepolicy=writeback, preferredctrlid=1" 
# 
# Build Audio/Scratch LUN 
# RAID level: 5 
# Physical Drives: 21, 22, 23, 24 
# Alias: Scratch 
# Controller Affinity: 2 
# Configuration options: Capacity all (default), 64K stripe size (default), 
# 512 byte sector (default), Read Ahead, Write Back 
# 
array -a add -p 21,22,23,24 -s "alias=Scratch" -l "alias=Scratch, raid=5, readpolicy=readahead, writepolicy=writeback, preferredctrlid=2" 
# 
# Build Data1 LUN 
# RAID level: 6 
# Physical Drives: 5, 6, 9, 10, 13, 14, 17, 18 
# Alias: Data1 
# Controller Affinity: 1 
# Configuration options: Capacity all (default), 1MB stripe size, 
# 512 byte sector (default), Read Ahead, Write Back 
# 
array -a add -p 5,6,9,10,13,14,17,18 -s "alias=Data1" -l "alias=Data1, raid=6, stripe=1mb, readpolicy=readahead, writepolicy=writeback, preferredctrlid=1" 
# 
# Build Data2 LUN 
# RAID level: 6 
# Physical Drives: 7, 8, 11, 12, 15, 16, 19, 20
# Alias: Data2 
# Controller Affinity: 2 
# Configuration options: Capacity all (default), 1MB stripe size, 
# 512 byte sector (default), Read Ahead, Write Back 
# 
array -a add -p 7,8,11,12,15,16,19,20 -s "alias=Data2" -l "alias=Data2, raid=6, stripe=1mb, readpolicy=readahead, writepolicy=writeback, preferredctrlid=2" 
# 
# Build Data3 LUN 
# RAID level: 6 
# Physical Drives: 25, 26, 29, 30, 33, 34, 37, 38
# Alias: Data3 
# Controller Affinity: 1 
# Configuration options: Capacity all (default), 1MB stripe size, 
# 512 byte sector (default), Read Ahead, Write Back 
# 
array -a add -p 25,26,29,30,33,34,37,38 -s "alias=Data3" -l "alias=Data3, raid=6, stripe=1mb, readpolicy=readahead, writepolicy=writeback, preferredctrlid=1" 
# 
# Build Data4 LUN 
# RAID level: 6 
# Physical Drives: 27, 28, 31, 32, 35, 36, 39, 40
# Alias: Data4
# Controller Affinity: 2 
# Configuration options: Capacity all (default), 1MB stripe size, 
# 512 byte sector (default), Read Ahead, Write Back 
# 
array -a add -p 27,28,31,32,35,36,39,40 -s "alias=Data4" -l "alias=Data4, raid=6, stripe=1mb, readpolicy=readahead, writepolicy=writeback, preferredctrlid=2" 
# 
# Build Data5 LUN 
# RAID level: 6 
# Physical Drives: 41, 42, 45, 46, 49, 50, 53, 54
# Alias: Data5 
# Controller Affinity: 1 
# Configuration options: Capacity all (default), 1MB stripe size, 
# 512 byte sector (default), Read Ahead, Write Back 
# 
array -a add -p 41,42,45,46,49,50,53,54 -s "alias=Data5" -l "alias=Data5, raid=6, stripe=1mb, readpolicy=readahead, writepolicy=writeback, preferredctrlid=1" 
# 
# Build Data6 LUN 
# RAID level: 6 
# Physical Drives: 43, 44, 47, 48, 51, 52, 55, 56
# Alias: Data6
# Controller Affinity: 2 
# Configuration options: Capacity all (default), 1MB stripe size, 
# 512 byte sector (default), Read Ahead, Write Back 
# 
array -a add -p 43,44,47,48,51,52,55,56 -s "alias=Data6" -l "alias=Data6, raid=6, stripe=1mb, readpolicy=readahead, writepolicy=writeback, preferredctrlid=2" 
# 
# Build Data7 LUN 
# RAID level: 6 
# Physical Drives: 57, 58, 61, 62, 65, 66, 69, 70
# Alias: Data7 
# Controller Affinity: 1 
# Configuration options: Capacity all (default), 1MB stripe size, 
# 512 byte sector (default), Read Ahead, Write Back 
# 
array -a add -p 57,58,61,62,65,66,69,70 -s "alias=Data7" -l "alias=Data7, raid=6, stripe=1mb, readpolicy=readahead, writepolicy=writeback, preferredctrlid=1" 
# 
# Build Data8 LUN 
# RAID level: 6 
# Physical Drives: 59, 60, 63, 64, 67, 68, 71, 72
# Alias: Data8
# Controller Affinity: 2 
# Configuration options: Capacity all (default), 1MB stripe size, 
# 512 byte sector (default), Read Ahead, Write Back 
# 
array -a add -p 59,60,63,64,67,68,71,72 -s "alias=Data8" -l "alias=Data8, raid=6, stripe=1mb, readpolicy=readahead, writepolicy=writeback, preferredctrlid=2" 
# 
# Set up global spares 
# Physical Drives: 3, 4 
# Type: Global spares, Revertible 
# 
spare -a add -p 3 -t g -r y 
spare -a add -p 4 -t g -r y 
# 
# Perform Quick Init on all LUNs 
# Note: Ensure any stale filesystem data is destroyed 
# 
init -a start -l 0 -q 100 
init -a start -l 1 -q 100 
init -a start -l 2 -q 100 
init -a start -l 3 -q 100 
init -a start -l 4 -q 100 
init -a start -l 5 -q 100 
init -a start -l 6 -q 100 
init -a start -l 7 -q 100 
init -a start -l 8 -q 100 
init -a start -l 9 -q 100 
# 
# END 
# 
#End Copy

For more information about options configured by this script, see Promise VTrak: Configuring for Optimal Performance (E5000 Series)

Promise VTrak RAID Controllers and SAS-connected Expansion Chassis: Xsan (Metadata and Data) Configuration Script - E5800f + J5600s

2016-10-19T06:31:06.7900000

This article contains a script used to configure Promise VTrak RAID Controllers and SAS-connected Expansion Chassis: Xsan (Metadata and Data) configuration script - E5800f + J5600s

To create the configuration script, copy the text below beginning with the line "#Begin Copy" to the line "#End Copy" and paste the text into TextEdit, using these guidelines. Once you've created the script, follow the guidelines in this article to import the configuration script.

#Begin Copy 
# 
# Promise VTrak E5800f + J5600s Configuration Script 
# 
# Script Name: RAID Controllers and 1 SAS-connected Expansion Chassis: Xsan (Metadata and Data) 
# 
# 
# Script Details: builds 6 LUNs from 40 drives (head + 1 expansion units) 
# in the recommended configuration for use with Xsan and StorNext
# 
# Script Assumptions: no arrays or logical drives created 
# (uncomment out array deletion if needed) 
# script works with either SATA or SAS configurations 
# 
# Global controller settings 
# LUN Affinity: enabled [required] 
# ALUA: enabled [required]
# Adaptive Writeback Cache: enabled [optional] 
# Host Cache Flushing: disabled [optional] 
# Forced Read Ahead: enabled [optional] 
# 
ctrl -a mod -s "lunaffinity=enable, alua=enable, adaptivewbcache=enable, hostcacheflushing=disable, forcedreadahead=enable"
# 
# Delete any existing arrays 
# Delete array 0 thru 5 
# 
#array -a del -d 0 
#array -a del -d 1 
#array -a del -d 2 
#array -a del -d 3 
#array -a del -d 4 
#array -a del -d 5 
#
# 
# Build MDC LUN 
# RAID level: 1 
# Physical Drives: 1, 2 
# Alias: MDC 
# Controller Affinity: 1 
# Configuration options: Capacity all (default), 64K stripe size (default), 
# 512 byte sector (default), Read Cache, Write Back
#
array -a add -p 1,2 -s "alias=MDC" -l "alias=MDC, raid=1, readpolicy=readcache, writepolicy=writeback, preferredctrlid=1" 
# 
# Build Audio/Scratch LUN 
# RAID level: 5 
# Physical Drives: 21, 22, 23, 24 
# Alias: Scratch 
# Controller Affinity: 2 
# Configuration options: Capacity all (default), 64K stripe size (default), 
# 512 byte sector (default), Read Ahead, Write Back 
# 
array -a add -p 21,22,23,24 -s "alias=Scratch" -l "alias=Scratch, raid=5, readpolicy=readahead, writepolicy=writeback, preferredctrlid=2" 
# 
# Build Data1 LUN 
# RAID level: 6 
# Physical Drives: 5, 6, 9, 10, 13, 14, 17, 18 
# Alias: Data1 
# Controller Affinity: 1 
# Configuration options: Capacity all (default), 1MB stripe size, 
# 512 byte sector (default), Read Ahead, Write Back 
# 
array -a add -p 5,6,9,10,13,14,17,18 -s "alias=Data1" -l "alias=Data1, raid=6, stripe=1mb, readpolicy=readahead, writepolicy=writeback, preferredctrlid=1" 
# 
# Build Data2 LUN 
# RAID level: 6 
# Physical Drives: 7, 8, 11, 12, 15, 16, 19, 20
# Alias: Data2 
# Controller Affinity: 2 
# Configuration options: Capacity all (default), 1MB stripe size, 
# 512 byte sector (default), Read Ahead, Write Back 
# 
array -a add -p 7,8,11,12,15,16,19,20 -s "alias=Data2" -l "alias=Data2, raid=6, stripe=1mb, readpolicy=readahead, writepolicy=writeback, preferredctrlid=2" 
# 
# Build Data3 LUN 
# RAID level: 6 
# Physical Drives: 25, 26, 29, 30, 33, 34, 37, 38
# Alias: Data3 
# Controller Affinity: 1 
# Configuration options: Capacity all (default), 1MB stripe size, 
# 512 byte sector (default), Read Ahead, Write Back 
# 
array -a add -p 25,26,29,30,33,34,37,38 -s "alias=Data3" -l "alias=Data3, raid=6, stripe=1mb, readpolicy=readahead, writepolicy=writeback, preferredctrlid=1" 
# 
# Build Data4 LUN 
# RAID level: 6 
# Physical Drives: 27, 28, 31, 32, 35, 36, 39, 40
# Alias: Data4
# Controller Affinity: 2 
# Configuration options: Capacity all (default), 1MB stripe size, 
# 512 byte sector (default), Read Ahead, Write Back 
# 
array -a add -p 27,28,31,32,35,36,39,40 -s "alias=Data4" -l "alias=Data4, raid=6, stripe=1mb, readpolicy=readahead, writepolicy=writeback, preferredctrlid=2" 
#
# Set up global spares 
# Physical Drives: 3, 4 
# Type: Global spares, Revertible 
# 
spare -a add -p 3 -t g -r y 
spare -a add -p 4 -t g -r y 
# 
# Perform Quick Init on all LUNs 
# Note: Ensure any stale filesystem data is destroyed 
# 
init -a start -l 0 -q 100 
init -a start -l 1 -q 100 
init -a start -l 2 -q 100 
init -a start -l 3 -q 100 
init -a start -l 4 -q 100 
init -a start -l 5 -q 100 
# 
# END 
# 
#End Copy

For more information about options configured by this script, see Promise VTrak: Configuring for Optimal Performance (E5000 Series)

Promise VTrak: RAID Head - Xsan (Metadata and Data) Configuration Script - E5800f

2016-10-19T06:23:47.3300000

This article contains a script used to configure Promise VTrak E5800f RAID Controllers for Xsan (Metadata and Data).

To create the configuration script, copy the text below beginning with the line "#Begin Copy" to the line "#End Copy" and paste the text into TextEdit, using these guidelines. Once you've created the script, follow the guidelines in this article to import the configuration script.

#Begin Copy 
# 
# Promise VTrak E5800f Configuration Script 
# 
# Script Name: RAID Controllers Only: Xsan (Metadata and Data) 
# 
# 
# Script Details: builds 4 LUNs from 24 drives (head units) 
# in the recommended configuration for use with Xsan and StorNext
# 
# Script Assumptions: no arrays or logical drives created 
# (uncomment out array deletion if needed) 
# script works with either SATA or SAS configurations 
# 
# Global controller settings 
# LUN Affinity: enabled [required] 
# ALUA: enabled [required]
# Adaptive Writeback Cache: enabled [optional] 
# Host Cache Flushing: disabled [optional] 
# Forced Read Ahead: enabled [optional] 
# 
ctrl -a mod -s "lunaffinity=enable, alua=enable, adaptivewbcache=enable, hostcacheflushing=disable, forcedreadahead=enable"
# 
# Delete any existing arrays 
# Delete array 0 thru 3 
# 
#array -a del -d 0 
#array -a del -d 1 
#array -a del -d 2 
#array -a del -d 3 
# 
# Build MDC LUN 
# RAID level: 1 
# Physical Drives: 1, 2 
# Alias: MDC 
# Controller Affinity: 1 
# Configuration options: Capacity all (default), 64K stripe size (default), 
# 512 byte sector (default), Read Cache, Write Back
#
array -a add -p 1,2 -s "alias=MDC" -l "alias=MDC, raid=1, readpolicy=readcache, writepolicy=writeback, preferredctrlid=1" 
# 
# Build Audio/Scratch LUN 
# RAID level: 5 
# Physical Drives: 21, 22, 23, 24 
# Alias: Scratch 
# Controller Affinity: 2 
# Configuration options: Capacity all (default), 64K stripe size (default), 
# 512 byte sector (default), Read Ahead, Write Back 
# 
array -a add -p 21,22,23,24 -s "alias=Scratch" -l "alias=Scratch, raid=5, readpolicy=readahead, writepolicy=writeback, preferredctrlid=2" 
# 
# Build Data1 LUN 
# RAID level: 6 
# Physical Drives: 5, 6, 9, 10, 13, 14, 17, 18 
# Alias: Data1 
# Controller Affinity: 1 
# Configuration options: Capacity all (default), 1MB stripe size, 
# 512 byte sector (default), Read Ahead, Write Back 
# 
array -a add -p 5,6,9,10,13,14,17,18 -s "alias=Data1" -l "alias=Data1, raid=6, stripe=1mb, readpolicy=readahead, writepolicy=writeback, preferredctrlid=1" 
# 
# Build Data2 LUN 
# RAID level: 6 
# Physical Drives: 7, 8, 11, 12, 15, 16, 19, 20
# Alias: Data2 
# Controller Affinity: 2 
# Configuration options: Capacity all (default), 1MB stripe size, 
# 512 byte sector (default), Read Ahead, Write Back 
# 
array -a add -p 7,8,11,12,15,16,19,20 -s "alias=Data2" -l "alias=Data2, raid=6, stripe=1mb, readpolicy=readahead, writepolicy=writeback, preferredctrlid=2" 
# 
# Set up global spares 
# Physical Drives: 3, 4 
# Type: Global spares, Revertible 
# 
spare -a add -p 3 -t g -r y 
spare -a add -p 4 -t g -r y 
# 
# Perform Quick Init on all LUNs 
# Note: Ensure any stale filesystem data is destroyed 
# 
init -a start -l 0 -q 100 
init -a start -l 1 -q 100 
init -a start -l 2 -q 100 
init -a start -l 3 -q 100 
# 
# END 
# 
#End Copy

For more information about options configured by this script, see Promise VTrak: Configuring for Optimal Performance (E5000 Series)

Promise VTrak RAID Controllers and SAS-connected Expansion Chassis: Xsan (Metadata and Data) Configuration Script - E5600f + (3) J5600s

2016-10-19T04:01:19.7470000

This article contains a script used to configure Promise VTrak RAID Controllers and SAS-connected Expansion Chassis: Xsan (Metadata and Data) configuration script - E5600f + (3) J5600s

To create the configuration script, copy the text below beginning with the line "#Begin Copy" to the line "#End Copy" and paste the text into TextEdit, using these guidelines. Once you've created the script, follow the guidelines in this article to import the configuration script.

#Begin Copy 
# 
# Promise VTrak E5600f + (3) J5600s Configuration Script 
# 
# Script Name: RAID Controllers and 3 SAS-connected Expansion Chassis: Xsan (Metadata and Data) 
# 
# 
# Script Details: builds 12 LUNs from 64 drives (head + 3 expansion units) 
# in the recommended configuration for use with Xsan and StorNext
# 
# Script Assumptions: no arrays or logical drives created 
# (uncomment out array deletion if needed) 
# script works with either SATA or SAS configurations 
# 
# Global controller settings 
# LUN Affinity: enabled [required] 
# ALUA: enabled [required]
# Adaptive Writeback Cache: enabled [optional] 
# Host Cache Flushing: disabled [optional] 
# Forced Read Ahead: enabled [optional] 
# 
ctrl -a mod -s "lunaffinity=enable, alua=enable, adaptivewbcache=enable, hostcacheflushing=disable, forcedreadahead=enable"
# 
# Delete any existing arrays 
# Delete array 0 thru 11 
# 
#array -a del -d 0 
#array -a del -d 1 
#array -a del -d 2 
#array -a del -d 3 
#array -a del -d 4 
#array -a del -d 5 
#array -a del -d 6 
#array -a del -d 7 
#array -a del -d 8 
#array -a del -d 9 
#array -a del -d 10 
#array -a del -d 11 
#
# Build MDC LUN 
# RAID level: 1 
# Physical Drives: 1, 2 
# Alias: MDC 
# Controller Affinity: 1 
# Configuration options: Capacity all (default), 64K stripe size (default), 
# 512 byte sector (default), Read Cache, Write Back
#
array -a add -p 1,2 -s "alias=MDC" -l "alias=MDC, raid=1, readpolicy=readcache, writepolicy=writeback, preferredctrlid=1" 
# 
# Build Data1 LUN 
# RAID level: 5 
# Physical Drives: 5, 6, 9, 10, 13, 14
# Alias: Data1 
# Controller Affinity: 2
# Configuration options: Capacity all (default), 1MB stripe size, 
# 512 byte sector (default), Read Ahead, Write Back 
# 
array -a add -p 5,6,9,10,13,14 -s "alias=Data1" -l "alias=Data1, raid=5, stripe=1mb, readpolicy=readahead, writepolicy=writeback, preferredctrlid=2" 
# 
# Build Data2 LUN 
# RAID level: 5 
# Physical Drives: 7, 8, 11, 12, 15, 16
# Alias: Data2 
# Controller Affinity: 1 
# Configuration options: Capacity all (default), 1MB stripe size, 
# 512 byte sector (default), Read Ahead, Write Back 
# 
array -a add -p 7,8,11,12,15,16 -s "alias=Data2" -l "alias=Data2, raid=5, stripe=1mb, readpolicy=readahead, writepolicy=writeback, preferredctrlid=1" 
# 
# Build Data3 LUN 
# RAID level: 5 
# Physical Drives: 17, 18, 21, 22, 25, 26
# Alias: Data3 
# Controller Affinity: 2 
# Configuration options: Capacity all (default), 1MB stripe size, 
# 512 byte sector (default), Read Ahead, Write Back 
# 
array -a add -p 17,18,21,22,25,26 -s "alias=Data3" -l "alias=Data3, raid=5, stripe=1mb, readpolicy=readahead, writepolicy=writeback, preferredctrlid=2" 
# 
# Build Data4 LUN 
# RAID level: 5 
# Physical Drives: 19, 20, 23, 24, 27, 28
# Alias: Data4
# Controller Affinity: 1 
# Configuration options: Capacity all (default), 1MB stripe size, 
# 512 byte sector (default), Read Ahead, Write Back 
# 
array -a add -p 19,20,23,24,27,28 -s "alias=Data4" -l "alias=Data4, raid=5, stripe=1mb, readpolicy=readahead, writepolicy=writeback, preferredctrlid=1" 
# 
# Build Data5 LUN 
# RAID level: 6 
# Physical Drives: 33, 34, 37, 38, 41, 42
# Alias: Data5 
# Controller Affinity: 2 
# Configuration options: Capacity all (default), 1MB stripe size, 
# 512 byte sector (default), Read Ahead, Write Back 
# 
array -a add -p 33,34,37,38,41,42 -s "alias=Data5" -l "alias=Data5, raid=5, stripe=1mb, readpolicy=readahead, writepolicy=writeback, preferredctrlid=2" 
# 
# Build Data6 LUN 
# RAID level: 6 
# Physical Drives: 35, 36, 39, 40, 43, 44
# Alias: Data6
# Controller Affinity: 1 
# Configuration options: Capacity all (default), 1MB stripe size, 
# 512 byte sector (default), Read Ahead, Write Back 
# 
array -a add -p 35,36,39,40,43,44 -s "alias=Data6" -l "alias=Data6, raid=5, stripe=1mb, readpolicy=readahead, writepolicy=writeback, preferredctrlid=1" 
# 
# Build Data7 LUN 
# RAID level: 6 
# Physical Drives: 49, 50, 53, 54, 57, 58
# Alias: Data7 
# Controller Affinity: 2 
# Configuration options: Capacity all (default), 1MB stripe size, 
# 512 byte sector (default), Read Ahead, Write Back 
# 
array -a add -p 49,50,53,54,57,58 -s "alias=Data7" -l "alias=Data7, raid=5, stripe=1mb, readpolicy=readahead, writepolicy=writeback, preferredctrlid=2" 
# 
# Build Data8 LUN 
# RAID level: 6 
# Physical Drives: 51, 52, 55, 56, 59, 60
# Alias: Data8
# Controller Affinity: 1 
# Configuration options: Capacity all (default), 1MB stripe size, 
# 512 byte sector (default), Read Ahead, Write Back 
# 
array -a add -p 51,52,55,56,59,60 -s "alias=Data8" -l "alias=Data8, raid=5, stripe=1mb, readpolicy=readahead, writepolicy=writeback, preferredctrlid=1" 
# 
# Build Audio/Scratch1 LUN 
# RAID level: 5 
# Physical Drives: 29, 30, 31 
# Alias: Scratch1 
# Controller Affinity: 2 
# Configuration options: Capacity all (default), 64K stripe size (default), 
# 512 byte sector (default), Read Ahead, Write Back 
# 
array -a add -p 29,30,31 -s "alias=Scratch1" -l "alias=Scratch1, raid=5, readpolicy=readahead, writepolicy=writeback, preferredctrlid=2" 
# 
# Build Audio/Scratch2 LUN 
# RAID level: 5 
# Physical Drives: 45, 46, 47
# Alias: Scratch2 
# Controller Affinity: 1 
# Configuration options: Capacity all (default), 64K stripe size (default), 
# 512 byte sector (default), Read Ahead, Write Back 
# 
array -a add -p 45,46,47 -s "alias=Scratch2" -l "alias=Scratch2, raid=5, readpolicy=readahead, writepolicy=writeback, preferredctrlid=1" 
# 
# Build Audio/Scratch3 LUN 
# RAID level: 5 
# Physical Drives: 61, 62, 63 
# Alias: Scratch3 
# Controller Affinity: 2 
# Configuration options: Capacity all (default), 64K stripe size (default), 
# 512 byte sector (default), Read Ahead, Write Back 
# 
array -a add -p 61,62,63 -s "alias=Scratch3" -l "alias=Scratch3, raid=5, readpolicy=readahead, writepolicy=writeback, preferredctrlid=2" 
# 
# Set up global spares 
# Physical Drives: 3, 4, 32, 48, 64 
# Type: Global spares, Revertible 
# 
spare -a add -p 3 -t g -r y 
spare -a add -p 4 -t g -r y 
spare -a add -p 32 -t g -r y 
spare -a add -p 48 -t g -r y 
spare -a add -p 64 -t g -r y 
# 
# Perform Quick Init on all LUNs 
# Note: Ensure any stale filesystem data is destroyed 
# 
init -a start -l 0 -q 100 
init -a start -l 1 -q 100 
init -a start -l 2 -q 100 
init -a start -l 3 -q 100 
init -a start -l 4 -q 100 
init -a start -l 5 -q 100 
init -a start -l 6 -q 100 
init -a start -l 7 -q 100 
init -a start -l 8 -q 100 
init -a start -l 9 -q 100
init -a start -l 10 -q 100 
init -a start -l 11 -q 100
# 
# END 
# 
#End Copy

For more information about options configured by this script, see Promise VTrak: Configuring for Optimal Performance (E5000 Series)

Promise VTrak RAID Controllers and SAS-connected Expansion Chassis: Xsan (Metadata and Data) Configuration Script - E5600f + J5600s

2016-10-19T02:33:01.8430000

This article contains a script used to configure Promise VTrak RAID Controllers and SAS-connected Expansion Chassis: Xsan (Metadata and Data) configuration script - E5600f + J5600s

To create the configuration script, copy the text below beginning with the line "#Begin Copy" to the line "#End Copy" and paste the text into TextEdit, using these guidelines. Once you've created the script, follow the guidelines in this article to import the configuration script.

#Begin Copy 
# 
# Promise VTrak E5600f + J5600s Configuration Script 
# 
# Script Name: RAID Controllers and 1 SAS-connected Expansion Chassis: Xsan (Metadata and Data) 
# 
# 
# Script Details: builds 6 LUNs from 32 drives (head + 1 expansion units) 
# in the recommended configuration for use with Xsan and StorNext
# 
# Script Assumptions: no arrays or logical drives created 
# (uncomment out array deletion if needed) 
# script works with either SATA or SAS configurations 
# 
# Global controller settings 
# LUN Affinity: enabled [required] 
# ALUA: enabled [required]
# Adaptive Writeback Cache: enabled [optional] 
# Host Cache Flushing: disabled [optional] 
# Forced Read Ahead: enabled [optional] 
# 
ctrl -a mod -s "lunaffinity=enable, alua=enable, adaptivewbcache=enable, hostcacheflushing=disable, forcedreadahead=enable"
# 
# Delete any existing arrays 
# Delete array 0 thru 5
# 
#array -a del -d 0 
#array -a del -d 1 
#array -a del -d 2 
#array -a del -d 3 
#array -a del -d 4 
#array -a del -d 5 
# 
# Build MDC LUN 
# RAID level: 1 
# Physical Drives: 1, 2 
# Alias: MDC 
# Controller Affinity: 1 
# Configuration options: Capacity all (default), 64K stripe size (default), 
# 512 byte sector (default), Read Cache, Write Back
#
array -a add -p 1,2 -s "alias=MDC" -l "alias=MDC, raid=1, readpolicy=readcache, writepolicy=writeback, preferredctrlid=1" 
# 
# Build Data1 LUN 
# RAID level: 5 
# Physical Drives: 5, 6, 9, 10, 13, 14
# Alias: Data1 
# Controller Affinity: 2
# Configuration options: Capacity all (default), 1MB stripe size, 
# 512 byte sector (default), Read Ahead, Write Back 
# 
array -a add -p 5,6,9,10,13,14 -s "alias=Data1" -l "alias=Data1, raid=5, stripe=1mb, readpolicy=readahead, writepolicy=writeback, preferredctrlid=2" 
# 
# Build Data2 LUN 
# RAID level: 5 
# Physical Drives: 7, 8, 11, 12, 15, 16
# Alias: Data2 
# Controller Affinity: 1 
# Configuration options: Capacity all (default), 1MB stripe size, 
# 512 byte sector (default), Read Ahead, Write Back 
# 
array -a add -p 7,8,11,12,15,16 -s "alias=Data2" -l "alias=Data2, raid=5, stripe=1mb, readpolicy=readahead, writepolicy=writeback, preferredctrlid=1" 
# 
# Build Data3 LUN 
# RAID level: 5 
# Physical Drives: 17, 18, 21, 22, 25, 26
# Alias: Data3 
# Controller Affinity: 2 
# Configuration options: Capacity all (default), 1MB stripe size, 
# 512 byte sector (default), Read Ahead, Write Back 
# 
array -a add -p 17,18,21,22,25,26 -s "alias=Data3" -l "alias=Data3, raid=5, stripe=1mb, readpolicy=readahead, writepolicy=writeback, preferredctrlid=2" 
# 
# Build Data4 LUN 
# RAID level: 5 
# Physical Drives: 19, 20, 23, 24, 27, 28
# Alias: Data4
# Controller Affinity: 1 
# Configuration options: Capacity all (default), 1MB stripe size, 
# 512 byte sector (default), Read Ahead, Write Back 
# 
array -a add -p 19,20,23,24,27,28 -s "alias=Data4" -l "alias=Data4, raid=5, stripe=1mb, readpolicy=readahead, writepolicy=writeback, preferredctrlid=1" 
# 
# Build Audio/Scratch1 LUN 
# RAID level: 5 
# Physical Drives: 29, 30, 31 
# Alias: Scratch1 
# Controller Affinity: 2 
# Configuration options: Capacity all (default), 64K stripe size (default), 
# 512 byte sector (default), Read Ahead, Write Back 
# 
array -a add -p 29,30,31 -s "alias=Scratch1" -l "alias=Scratch1, raid=5, readpolicy=readahead, writepolicy=writeback, preferredctrlid=2" 
# 
# Set up global spares 
# Physical Drives: 3, 4, 32
# Type: Global spares, Revertible 
# 
spare -a add -p 3 -t g -r y 
spare -a add -p 4 -t g -r y 
spare -a add -p 32 -t g -r y 
# 
# Perform Quick Init on all LUNs 
# Note: Ensure any stale filesystem data is destroyed 
# 
init -a start -l 0 -q 100 
init -a start -l 1 -q 100 
init -a start -l 2 -q 100 
init -a start -l 3 -q 100 
init -a start -l 4 -q 100 
init -a start -l 5 -q 100 
# END 
# 
#End Copy

For more information about options configured by this script, see Promise VTrak: Configuring for Optimal Performance (E5000 Series)

Promise VTrak: RAID Head - Xsan (Metadata and Data) Configuration Script - E5600f

2016-10-19T01:51:56.0700000

This article contains a script used to configure Promise VTrak E5600f RAID Controllers for Xsan (Metadata and Data).

To create the configuration script, copy the text below beginning with the line "#Begin Copy" to the line "#End Copy" and paste the text into TextEdit, using these guidelines. Once you've created the script, follow the guidelines in this article to import the configuration script.

#Begin Copy 
# 
# Promise VTrak E5600f Configuration Script 
# 
# Script Name: RAID Controllers: Xsan (Metadata and Data) 
# 
# 
# Script Details: builds 3 LUNs from 16 drives (head units) 
# in the recommended configuration for use with Xsan and StorNext
# 
# Script Assumptions: no arrays or logical drives created 
# (uncomment out array deletion if needed) 
# script works with either SATA or SAS configurations 
# 
# Global controller settings 
# LUN Affinity: enabled [required] 
# ALUA: enabled [required]
# Adaptive Writeback Cache: enabled [optional] 
# Host Cache Flushing: disabled [optional] 
# Forced Read Ahead: enabled [optional] 
# 
ctrl -a mod -s "lunaffinity=enable, alua=enable, adaptivewbcache=enable, hostcacheflushing=disable, forcedreadahead=enable" 
# 
# Delete any existing arrays 
# Delete array 0 thru 2
# 
#array -a del -d 0 
#array -a del -d 1 
#array -a del -d 2 

# 
# Build MDC LUN 
# RAID level: 1 
# Physical Drives: 1, 2 
# Alias: MDC 
# Controller Affinity: 1 
# Configuration options: Capacity all (default), 64K stripe size (default), 
# 512 byte sector (default), Read Cache, Write Back
#
array -a add -p 1,2 -s "alias=MDC" -l "alias=MDC, raid=1, readpolicy=readcache, writepolicy=writeback, preferredctrlid=1" 
# 
# Build Data1 LUN 
# RAID level: 5 
# Physical Drives: 5, 6, 9, 10, 13, 14
# Alias: Data1 
# Controller Affinity: 2
# Configuration options: Capacity all (default), 1MB stripe size, 
# 512 byte sector (default), Read Ahead, Write Back 
# 
array -a add -p 5,6,9,10,13,14 -s "alias=Data1" -l "alias=Data1, raid=5, stripe=1mb, readpolicy=readahead, writepolicy=writeback, preferredctrlid=2" 
# 
# Build Data2 LUN 
# RAID level: 5 
# Physical Drives: 7, 8, 11, 12, 15, 16
# Alias: Data2 
# Controller Affinity: 1 
# Configuration options: Capacity all (default), 1MB stripe size, 
# 512 byte sector (default), Read Ahead, Write Back 
# 
array -a add -p 7,8,11,12,15,16 -s "alias=Data2" -l "alias=Data2, raid=5, stripe=1mb, readpolicy=readahead, writepolicy=writeback, preferredctrlid=1" 
#
# Set up global spares 
# Physical Drives: 3, 4
# Type: Global spares, Revertible 
# 
spare -a add -p 3 -t g -r y 
spare -a add -p 4 -t g -r y 
# 
# Perform Quick Init on all LUNs 
# Note: Ensure any stale filesystem data is destroyed 
# 
init -a start -l 0 -q 100 
init -a start -l 1 -q 100 
init -a start -l 2 -q 100 
# END 
# 
#End Copy

For more information about options configured by this script, see Promise VTrak: Configuring for Optimal Performance (E5000 Series)

Promise VTrak: RAID Controllers and SAS-connected Expansion Chassis: Xsan (Metadata and Data) Configuration Script - E5320f + (2) J5600s

2016-10-18T23:49:55.6970000

This article contains a script used to configure Promise VTrak RAID Controllers and SAS-connected Expansion Chassis: Xsan (Metadata and Data) configuration script - E5320f + (2) J5600s

To create the configuration script, copy the text below beginning with the line "#Begin Copy" to the line "#End Copy" and paste the text into TextEdit, using these guidelines. Once you've created the script, follow the guidelines in this article to import the configuration script.

#Begin Copy 
# 
# Promise E5320f + (2) J5600s Configuration Script 
# 
# Script Name: RAID Controllers Only: Xsan (Metadata and Data) 
# 
# 
# Script Details: builds 7 LUNs from 56 drives (head units) 
# in the recommended configuration for use with Xsan and StorNext
# 
# Script Assumptions: no arrays or logical drives created 
# (uncomment out array deletion if needed) 
# script works with either SATA or SAS configurations 
# 
# Global controller settings 
# LUN Affinity: enabled [required] 
# ALUA: enable [required]
# Adaptive Writeback Cache: enabled [optional] 
# Host Cache Flushing: disabled [optional] 
# Forced Read Ahead: enabled [optional] 
# 
ctrl -a mod -s "lunaffinity=enable, alua=enable, adaptivewbcache=enable, hostcacheflushing=disable, forcedreadahead=enable"
# 
# Delete any existing arrays 
# Delete array 0 thru 3 
# 
#array -a del -d 0 
#array -a del -d 1 
#array -a del -d 2 
#array -a del -d 3 
# 
# Build MDC LUN 
# RAID level: 1 
# Physical Drives: 1, 2 
# Alias: MDC 
# Controller Affinity: 1 
# Configuration options: Capacity all (default), 64K stripe size (default), 
# 512 byte sector (default), Read Cache, Write Back
#
array -a add -p 1,2 -s "alias=MDC" -l "alias=MDC, raid=1, readpolicy=readcache, writepolicy=writeback, preferredctrlid=1" 
# 
# Build Data1 LUN 
# RAID level: 5 
# Physical Drives: 5,6,7,8,9,10,11,12,13,14 
# Alias: Data1 
# Controller Affinity: 1 
# Configuration options: Capacity all (default), 64K stripe size (default),
# 512 byte sector (default), Read Ahead, Write Back 
# 
array -a add -p 5,6,7,8,9,10,11,12,13,14 -s "alias=Data1" -l "alias=Data1, raid=5, readpolicy=readahead, writepolicy=writeback, preferredctrlid=1" 
# 
# Build Data2 LUN 
# RAID level: 5 
# Physical Drives: 15,16,17,18,19,20,21,22,23,24
# Alias: Data2 
# Controller Affinity: 2 
# Configuration options: Capacity all (default), 64K stripe size (default),
# 512 byte sector (default), Read Ahead, Write Back 
# 
array -a add -p 15,16,17,18,19,20,21,22,23,24 -s "alias=Data2" -l "alias=Data2, raid=5, readpolicy=readahead, writepolicy=writeback, preferredctrlid=2" 
# 
# Build Data3 LUN 
# RAID level: 6 
# Physical Drives: 25,29,30,33,34,37,38
# Alias: Data3 
# Controller Affinity: 2 
# Configuration options: Capacity all (default), 64K stripe size (default),
# 512 byte sector (default), Read Ahead, Write Back 
# 
array -a add -p 25,29,30,33,34,37,38 -s "alias=Data3" -l "alias=Data3, raid=6, readpolicy=readahead, writepolicy=writeback, preferredctrlid=2" 
# 
# Build Data4 LUN 
# RAID level: 6 
# Physical Drives: 28,31,32,35,36,39,40
# Alias: Data4 
# Controller Affinity: 2 
# Configuration options: Capacity all (default), 64K stripe size (default),
# 512 byte sector (default), Read Ahead, Write Back 
# 
array -a add -p 28,31,32,35,36,39,40 -s "alias=Data4" -l "alias=Data4, raid=6, readpolicy=readahead, writepolicy=writeback, preferredctrlid=2" 
# 
# Build Data5 LUN 
# RAID level: 6 
# Physical Drives: 41,45,46,49,50,53,54
# Alias: Data5 
# Controller Affinity: 2 
# Configuration options: Capacity all (default), 64K stripe size (default),
# 512 byte sector (default), Read Ahead, Write Back 
# 
array -a add -p 41,45,46,49,50,53,54 -s "alias=Data5" -l "alias=Data5, raid=6, readpolicy=readahead, writepolicy=writeback, preferredctrlid=2" 
# 
# Build Data6 LUN 
# RAID level: 6 
# Physical Drives: 44,47,48,51,52,55,56
# Alias: Data6 
# Controller Affinity: 2 
# Configuration options: Capacity all (default), 64K stripe size (default),
# 512 byte sector (default), Read Ahead, Write Back 
# 
array -a add -p 44,47,48,51,52,55,56 -s "alias=Data6" -l "alias=Data6, raid=6, readpolicy=readahead, writepolicy=writeback, preferredctrlid=2" 
# 
# Set up dedicated spares 
# Physical Drives: 3, 4 
# Type: dedicated spares, Revertible to meta, data1, data2
# 
spare -a add -p 3 -d 0,1,2 -t d -r y 
spare -a add -p 4 -d 0,1,2 -t d -r y 
# 
# Set up dedicated spares 
# Physical Drives: 26, 27
# Type: dedicated spares, Revertible to data3, data4
# 
spare -a add -p 26 -d 3,4 -t d -r y 
spare -a add -p 27 -d 3,4 -t d -r y 
# 
# Set up dedicated spares 
# Physical Drives: 50, 51
# Type: dedicated spares, Revertible to data5, data6
# 
spare -a add -p 42 -d 5,6 -t d -r y 
spare -a add -p 43 -d 5,6 -t d -r y 
# 
# Perform Quick Init on all LUNs 
# Note: Ensure any stale filesystem data is destroyed 
# 
init -a start -l 0 -q 100 
init -a start -l 1 -q 100 
init -a start -l 2 -q 100 
init -a start -l 3 -q 100 
init -a start -l 4 -q 100 
init -a start -l 5 -q 100 
init -a start -l 6 -q 100 
# 
# END 
# 
#End Copy

For more information about options configured by this script, see Promise VTrak: Configuring for Optimal Performance (E5000 Series)

Promise VTrak: RAID Controllers and SAS-connected Expansion Chassis: Xsan (Metadata and Data) Configuration Script - E5320f + J5600s

2016-10-18T23:26:26.3670000

This article contains a script used to configure Promise VTrak RAID Controllers and SAS-connected Expansion Chassis: Xsan (Metadata and Data) configuration script - E5320f + J5600s

To create the configuration script, copy the text below beginning with the line "#Begin Copy" to the line "#End Copy" and paste the text into TextEdit, using these guidelines. Once you've created the script, follow the guidelines in this article to import the configuration script.

#Begin Copy 
# 
# Promise E5320 + J5600s configuration script 
# 
# Script Name: RAID Controllers Only: Xsan (Metadata and Data) 
# 
# 
# Script Details: builds 5 LUNs from 40 drives (head units) 
# in the recommended configuration for use with Xsan and StorNext 
# 
# Script Assumptions: no arrays or logical drives created 
# (uncomment out array deletion if needed) 
# script works with either SATA or SAS configurations 
# 
# Global controller settings 
# LUN Affinity: enabled [required] 
# ALUA: enabled [required]
# Adaptive Writeback Cache: enabled [optional] 
# Host Cache Flushing: disabled [optional] 
# Forced Read Ahead: enabled [optional] 
# 
ctrl -a mod -s "lunaffinity=enable, alua=enable, adaptivewbcache=enable, hostcacheflushing=disable, forcedreadahead=enable"
# 
# Delete any existing arrays 
# Delete array 0 thru 3 
# 
#array -a del -d 0 
#array -a del -d 1 
#array -a del -d 2 
#array -a del -d 3 
# 
# Build MDC LUN 
# RAID level: 1 
# Physical Drives: 1, 2 
# Alias: MDC 
# Controller Affinity: 1 
# Configuration options: Capacity all (default), 64K stripe size (default), 
# 512 byte sector (default), Read Cache, Write Back
#
array -a add -p 1,2 -s "alias=MDC" -l "alias=MDC, raid=1, readpolicy=readcache, writepolicy=writeback, preferredctrlid=1" 
# 
# Build Data1 LUN 
# RAID level: 5 
# Physical Drives: 5,6,7,8,9,10,11,12,13,14 
# Alias: Data1 
# Controller Affinity: 1 
# Configuration options: Capacity all (default), 64K stripe size (default),
# 512 byte sector (default), Read Ahead, Write Back 
# 
array -a add -p 5,6,7,8,9,10,11,12,13,14 -s "alias=Data1" -l "alias=Data1, raid=5, readpolicy=readahead, writepolicy=writeback, preferredctrlid=1" 
# 
# Build Data2 LUN 
# RAID level: 5 
# Physical Drives: 15,16,17,18,19,20,21,22,23,24
# Alias: Data2 
# Controller Affinity: 2 
# Configuration options: Capacity all (default), 64K stripe size (default),
# 512 byte sector (default), Read Ahead, Write Back 
# 
array -a add -p 15,16,17,18,19,20,21,22,23,24 -s "alias=Data2" -l "alias=Data2, raid=5, readpolicy=readahead, writepolicy=writeback, preferredctrlid=2" 
# 
# Build Data3 LUN 
# RAID level: 6 
# Physical Drives: 25,29,30,33,34,37,38
# Alias: Data3 
# Controller Affinity: 2 
# Configuration options: Capacity all (default), 64K stripe size (default),
# 512 byte sector (default), Read Ahead, Write Back 
# 
array -a add -p 25,29,30,33,34,37,38 -s "alias=Data3" -l "alias=Data3, raid=6, readpolicy=readahead, writepolicy=writeback, preferredctrlid=2" 
# 
# Build Data4 LUN 
# RAID level: 6 
# Physical Drives: 28,31,32,35,36,39,40
# Alias: Data4 
# Controller Affinity: 2 
# Configuration options: Capacity all (default), 64K stripe size (default),
# 512 byte sector (default), Read Ahead, Write Back 
# 
array -a add -p 28,31,32,35,36,39,40 -s "alias=Data4" -l "alias=Data4, raid=6, readpolicy=readahead, writepolicy=writeback, preferredctrlid=2" 
# 
# Set up dedicated spares 
# Physical Drives: 3, 4 
# Type: dedicated spares, Revertible to meta, data1, data2
# 
spare -a add -p 3 -d 0,1,2 -t d -r y 
spare -a add -p 4 -d 0,1,2 -t d -r y 
# 
# Set up dedicated spares 
# Physical Drives: 26, 27
# Type: dedicated spares, Revertible to data3, data4
# 
spare -a add -p 26 -d 3,4 -t d -r y 
spare -a add -p 27 -d 3,4 -t d -r y 
# 
# Perform Quick Init on all LUNs 
# Note: Ensure any stale filesystem data is destroyed 
# 
init -a start -l 0 -q 100 
init -a start -l 1 -q 100 
init -a start -l 2 -q 100 
init -a start -l 3 -q 100 
init -a start -l 4 -q 100 
# 
# END 
# 
#End Copy

For more information about options configured by this script, see Promise VTrak: Configuring for Optimal Performance (E5000 Series)

Promise VTrak: RAID Controllers and SAS-connected Expansion Chassis: Xsan (Metadata and Data) Configuration Script - E5320f + J5320s

2016-10-18T22:01:48.8100000

This article contains a script used to configure Promise VTrak RAID Controllers and SAS-connected Expansion Chassis: Xsan (Metadata and Data) configuration script - E5320f + J5320s

To create the configuration script, copy the text below beginning with the line "#Begin Copy" to the line "#End Copy" and paste the text into TextEdit, using these guidelines. Once you've created the script, follow the guidelines in this article to import the configuration script.

#Begin Copy 
# 
# Promise Promise E5320f + J5320s Configuration Script 
# 
# Script Name: RAID Controllers Only: Xsan (Metadata and Data) 
# 
# 
# Script Details: builds 5 LUNs from 48 drives (head units) 
# in the recommended configuration for use with Xsan and StorNext 
# 
# Script Assumptions: no arrays or logical drives created 
# (uncomment out array deletion if needed) 
# script works with either SATA or SAS configurations 
# 
# Global controller settings 
# LUN Affinity: enabled [required] 
# ALUA: enabled [required]
# Adaptive Writeback Cache: enabled [optional] 
# Host Cache Flushing: disabled [optional] 
# Forced Read Ahead: enabled [optional] 
# 
ctrl -a mod -s "lunaffinity=enable, alua=enable, adaptivewbcache=enable, hostcacheflushing=disable, forcedreadahead=enable"
# 
# Delete any existing arrays 
# Delete array 0 thru 3 
# 
#array -a del -d 0 
#array -a del -d 1 
#array -a del -d 2 
#array -a del -d 3 
# 
# Build MDC LUN 
# RAID level: 1 
# Physical Drives: 1, 2 
# Alias: MDC 
# Controller Affinity: 1 
# Configuration options: Capacity all (default), 64K stripe size (default), 
# 512 byte sector (default), Read Cache, Write Back
#
array -a add -p 1,2 -s "alias=MDC" -l "alias=MDC, raid=1, readpolicy=readcache, writepolicy=writeback, preferredctrlid=1" 
# 
# Build Data1 LUN 
# RAID level: 5 
# Physical Drives: 5,6,7,8,9,10,11,12,13,14 
# Alias: Data1 
# Controller Affinity: 1 
# Configuration options: Capacity all (default), 64K stripe size (default),
# 512 byte sector (default), Read Ahead, Write Back 
# 
array -a add -p 5,6,7,8,9,10,11,12,13,14 -s "alias=Data1" -l "alias=Data1, raid=5, readpolicy=readahead, writepolicy=writeback, preferredctrlid=1" 
# 
# Build Data2 LUN 
# RAID level: 5 
# Physical Drives: 15,16,17,18,19,20,21,22,23,24
# Alias: Data2 
# Controller Affinity: 2 
# Configuration options: Capacity all (default), 64K stripe size (default),
# 512 byte sector (default), Read Ahead, Write Back 
# 
array -a add -p 15,16,17,18,19,20,21,22,23,24 -s "alias=Data2" -l "alias=Data2, raid=5, readpolicy=readahead, writepolicy=writeback, preferredctrlid=2" 
# 
# Build Data3 LUN 
# RAID level: 5 
# Physical Drives: 29,30,31,32,33,34,35,36,37,38
# Alias: Data3 
# Controller Affinity: 2 
# Configuration options: Capacity all (default), 64K stripe size (default),
# 512 byte sector (default), Read Ahead, Write Back 
# 
array -a add -p 29,30,31,32,33,34,35,36,37,38 -s "alias=Data3" -l "alias=Data3, raid=5, readpolicy=readahead, writepolicy=writeback, preferredctrlid=2" 
# 
# Build Data4 LUN 
# RAID level: 5 
# Physical Drives: 39,40,41,42,43,44,45,46,47,48
# Alias: Data4 
# Controller Affinity: 2 
# Configuration options: Capacity all (default), 64K stripe size (default),
# 512 byte sector (default), Read Ahead, Write Back 
# 
array -a add -p 39,40,41,42,43,44,45,46,47,48 -s "alias=Data4" -l "alias=Data4, raid=5, readpolicy=readahead, writepolicy=writeback, preferredctrlid=2" 
# 
# Set up dedicated spares 
# Physical Drives: 3, 4 
# Type: dedicated spares, Revertible to meta, data1, data2
# 
spare -a add -p 3 -d 0,1,2 -t d -r y 
spare -a add -p 4 -d 0,1,2 -t d -r y 
# 
# Set up dedicated spares 
# Physical Drives: 25, 26, 27, 28 
# Type: dedicated spares, Revertible to data3, data4
# 
spare -a add -p 25 -d 3,4 -t d -r y 
spare -a add -p 26 -d 3,4 -t d -r y 
spare -a add -p 27 -d 3,4 -t d -r y 
spare -a add -p 28 -d 3,4 -t d -r y 
# 
# Perform Quick Init on all LUNs 
# Note: Ensure any stale filesystem data is destroyed 
# 
init -a start -l 0 -q 100 
init -a start -l 1 -q 100 
init -a start -l 2 -q 100 
init -a start -l 3 -q 100 
init -a start -l 4 -q 100 
# 
# END 
# 
#End Copy

For more information about options configured by this script, see Promise VTrak: Configuring for Optimal Performance (E5000 Series)

Promise VTrak: RAID Head - Xsan (Metadata and Data) Configuration Script - E5320f

2016-10-18T21:50:34.4700000

This article contains a script used to configure Promise VTrak E5320f RAID Controllers for Xsan (Metadata and Data).

To create the configuration script, copy the text below beginning with the line "#Begin Copy" to the line "#End Copy" and paste the text into TextEdit, using these guidelines. Once you've created the script, follow the guidelines in this article to import the configuration script.

#Begin Copy 
# 
# Promise VTrak E5320f Configuration Script 
# 
# Script Name: RAID Controllers Only: Xsan (Metadata and Data) 
# 
# 
# Script Details: builds 3 LUNs from 24 drives (head units) 
# in the recommended configuration for use with Xsan and StorNext
# 
# Script Assumptions: no arrays or logical drives created 
# (uncomment out array deletion if needed) 
# script works with either SATA or SAS configurations 
# 
# Global controller settings 
# LUN Affinity: enabled [required] 
# ALUA: enabled [required]
# Adaptive Writeback Cache: enabled [optional] 
# Host Cache Flushing: disabled [optional] 
# Forced Read Ahead: enabled [optional] 
# 
ctrl -a mod -s "lunaffinity=enable, alua=enable, adaptivewbcache=enable, hostcacheflushing=disable, forcedreadahead=enable"
# 
# Delete any existing arrays 
# Delete array 0 thru 3 
# 
#array -a del -d 0 
#array -a del -d 1 
#array -a del -d 2 
#array -a del -d 3 
# 
# Build MDC LUN 
# RAID level: 1 
# Physical Drives: 1, 2 
# Alias: MDC 
# Controller Affinity: 1 
# Configuration options: Capacity all (default), 64K stripe size (default), 
# 512 byte sector (default), Read Cache, Write Back
#
array -a add -p 1,2 -s "alias=MDC" -l "alias=MDC, raid=1, readpolicy=readcache, writepolicy=writeback, preferredctrlid=1" 
# 
# Build Data1 LUN 
# RAID level: 5 
# Physical Drives: 5,6,7,8,9,10,11,12,13,14 
# Alias: Data1 
# Controller Affinity: 1 
# Configuration options: Capacity all (default), 64K stripe size (default),
# 512 byte sector (default), Read Ahead, Write Back 
# 
array -a add -p 5,6,7,8,9,10,11,12,13,14 -s "alias=Data1" -l "alias=Data1, raid=5, readpolicy=readahead, writepolicy=writeback, preferredctrlid=1" 
# 
# Build Data2 LUN 
# RAID level: 5 
# Physical Drives: 15,16,17,18,19,20,21,22,23,24
# Alias: Data2 
# Controller Affinity: 2 
# Configuration options: Capacity all (default), 64K stripe size (default),
# 512 byte sector (default), Read Ahead, Write Back 
# 
array -a add -p 15,16,17,18,19,20,21,22,23,24 -s "alias=Data2" -l "alias=Data2, raid=5, readpolicy=readahead, writepolicy=writeback, preferredctrlid=2" 
# 
# Set up dedicated spares 
# Physical Drives: 3, 4 
# Type: dedicated spares, Revertible to meta, data1, data2
# 
spare -a add -p 3 -d 0,1,2 -t d -r y 
spare -a add -p 4 -d 0,1,2 -t d -r y 
# 
# Perform Quick Init on all LUNs 
# Note: Ensure any stale filesystem data is destroyed 
# 
init -a start -l 0 -q 100 
init -a start -l 1 -q 100 
init -a start -l 2 -q 100 
# 
# END 
# 
#End Copy

For more information about options configured by this script, see Promise VTrak: Configuring for Optimal Performance (E5000 Series)

Promise VTrak: RAID Head - Xsan (Metadata and Data) Configuration Script - E5300f

2016-10-18T21:08:55.0800000

This article contains a script used to configure Promise VTrak E5300f RAID Controllers for Xsan (Metadata and Data).

To create the configuration script, copy the text below beginning with the line "#Begin Copy" to the line "#End Copy" and paste the text into TextEdit, using these guidelines. Once you've created the script, follow the guidelines in this article to import the configuration script.

#Begin Copy 
# 
# Promise VTrak E5300f Configuration Script 
# 
# Script Name: RAID Controllers Only: Xsan (Metadata and Data) 
# 
# 
# Script Details: builds 3 LUNs from 12 drives (head units) 
# in the recommended configuration for use with Xsan and StorNext 
# 
# Script Assumptions: no arrays or logical drives created 
# (uncomment out array deletion if needed) 
# script works with either SATA or SAS configurations 
# 
# Global controller settings 
# LUN Affinity: enabled [required] 
# ALUA: enabled [required]
# Adaptive Writeback Cache: enabled [optional] 
# Host Cache Flushing: disabled [optional] 
# Forced Read Ahead: enabled [optional] 
# 
ctrl -a mod -s "lunaffinity=enable, alua=enable, adaptivewbcache=enable, hostcacheflushing=disable, forcedreadahead=enable" 
# 
# Delete any existing arrays 
# Delete array 0 thru 3 
# 
#array -a del -d 0 
#array -a del -d 1 
#array -a del -d 2 
#array -a del -d 3 
# 
# Build MDC LUN 
# RAID level: 1 
# Physical Drives: 1, 2 
# Alias: MDC 
# Controller Affinity: 1 
# Configuration options: Capacity all (default), 64K stripe size (default), 
# 512 byte sector (default), Read Cache, Write Back
#
array -a add -p 1,2 -s "alias=MDC" -l "alias=MDC, raid=1, readpolicy=readcache, writepolicy=writeback, preferredctrlid=1" 
# 
# Build Data1 LUN 
# RAID level: 5 
# Physical Drives: 5,6,9,10
# Alias: Data1 
# Controller Affinity: 2 
# Configuration options: Capacity all (default), 64K stripe size (default), 
# 512 byte sector (default), Read Ahead, Write Back 
# 
array -a add -p 5,6,9,10 -s "alias=Data1" -l "alias=Data1, raid=5, readpolicy=readahead, writepolicy=writeback, preferredctrlid=2" 
# 
# Build Data2 LUN 
# RAID level: 5 
# Physical Drives: 7,8,11,12
# Alias: Data2 
# Controller Affinity: 1 
# Configuration options: Capacity all (default), 64K stripe size, 
# 512 byte sector (default), Read Ahead, Write Back 
# 
array -a add -p 7,8,11,12 -s "alias=Data2" -l "alias=Data2, raid=5, readpolicy=readahead, writepolicy=writeback, preferredctrlid=1" 
# 
# Set up dedicated spares 
# Physical Drives: 3, 4 
# Type: dedicated spares, Revertible to meta, data1, data2
# 
spare -a add -p 3 -d 0,1,2 -t d -r y 
spare -a add -p 4 -d 0,1,2 -t d -r y 
# 
# Perform Quick Init on all LUNs 
# Note: Ensure any stale filesystem data is destroyed 
# 
init -a start -l 0 -q 100 
init -a start -l 1 -q 100 
init -a start -l 2 -q 100 
# 
# END 
# 
#End Copy

For more information about options configured by this script, see Promise VTrak: Configuring for Optimal Performance (E5000 Series)

Promise VTrak: Configuring for Optimal Performance (E5000 Series)

2016-10-18T20:47:16.7430000

Promise VTrak: Configuring for Optimal Performance (E5000 Series)

Configure Promise VTrak RAIDs for best performance using the guidelines in this article.

These scripts are inteded to be used for  Xsan and Quantum StorNext Deployments

- For the Promise VTrak E5000 series, the scripted options below are currently not built into the Promise Admin interface. At this juncture, it is necessary to create and import the configuration scripts. In the next service release of the firmware, these scripts will be embedded in the GUI.

- For the Promise VTrak E5000 & J5000 Series, create and import the desired script, as described below.

- Some of the configuration scripts configure Global or Dedicated Revertible Spare Drives. In the event that a drive is replaced, data will be migrated from the Spare Drive to the replacement drive. Performance may be impacted for the duration of the migration procedure.

Note: All these scripts have ALUA (Asymmetric Logical Unit Access) enabled by default. If all your host's operating systems are ALUA compliant; you may leave ALUA enabled.

In the case that you need to disable ALUA due to your operating system's non-compliancy, following the instructions below.

Locate alua=enable :

ctrl -a mod -s "lunaffinity=enable, alua=enable, adaptivewbcache=enable, hostcacheflushing=disable, forcedreadahead=enable"Modify the alua variable in the script before importing:

ctrl -a mod -s "lunaffinity=enable, alua=disable, adaptivewbcache=enable, hostcacheflushing=disable, forcedreadahead=enable"

Configure via Script

Create the script file

Determine which script you should use from the following list, then click the linked article to get the text of the script. Follow the instructions in the linked article to save the script, then return to this article.

RAID Controller: Xsan (Metadata and Data) - E5300f

Configures a RAID Controller that will be used as an Xsan or StorNext volume. Configures arrays to be used as a metadata LUN, two data LUNs, and two spares. Each Xsan or StorNext volume must contain one metadata LUN.

RAID Controller: Xsan (Metadata and Data) - E5600f

Configures a RAID Controller that will be used as an Xsan or StorNext Volume. Configures arrays to be used as a metadata LUN, two data LUNs, and two spares. Each Xsan or StorNext volume must contain one metadata LUN.

RAID Controller and SAS-connected Expansion Chassis: Xsan (Metadata and Data) - E5600f + J5600s

Configures a RAID Controller and SAS-connected Expansion Chassis that will be used as an Xsan or StorNext volume. Configures arrays to be used as a metadata LUN, four data LUNs, one scratch LUN, and three spares. Each Xsan or StorNext volume must contain one metadata LUN.

RAID Controller and SAS-connected Expansion Chassis: Xsan (Metadata and Data) - E5600f + (3) J5600s

Configures a RAID Controller and (3) SAS-connected Expansion Chassis that will be used as an Xsan or StorNext volume. Configures arrays to be used as a metadata LUN, eight data LUNs, three scratch LUNs, and five spares. Each Xsan or StorNext volume must contain one metadata LUN.

RAID Controller: Xsan (Metadata and Data) - E5800f

Configures a RAID Controller that will be used as an Xsan or StorNext volume. Configures arrays to be used as a metadata LUN, two data LUNs, one scratch LUN, and two spares. Each Xsan or StorNext volume must contain one metadata LUN.

RAID Controller and SAS-connected Expansion Chassis: Xsan (Metadata and Data) - E5800f + J5600s

Configures a RAID Controller and a SAS-connected Expansion Chassis that will be used as an Xsan or StorNext volume. Configures arrays to be used as a metadata LUN, four data LUNs, one scratch LUN, and two spares. Each Xsan or StorNext volume must contain one metadata LUN.

RAID Controller and SAS-connected Expansion Chassis: Xsan (Metadata and Data) - E5800f + (3) J5600s

Configures a RAID Controller and (3) SAS-connected Expansion Chassis that will be used as an Xsan or StorNext volume. Configures arrays to be used as a metadata LUN, eight data LUNs, one scratch LUN, and two spares. Each Xsan or StorNext volume must contain one metadata LUN.

RAID Controller: Xsan (Metadata and Data) - E5320f

RAID Controllers and SAS-connected Expansion Chassis: Xsan (Metadata and Data) - E5320f + J5320s

Configures a RAID Controller and a SAS-connected Expansion Chassis that will be used as an Xsan or StorNext volume. Configures arrays to be used as a metadata LUN, four data LUNs, and six spares. Each Xsan or StorNext volume must contain one metadata LUN.

RAID Controllers and SAS-connected Expansion Chassis: Xsan (Metadata and Data) - E5320f + J5600s

Configures a RAID Controller and a SAS-connected Expansion Chassis that will be used as an Xsan or StorNext volume. Configures arrays to be used as a metadata LUN, four data LUNs, and four spares. Each Xsan or StorNext volume must contain one metadata LUN.

RAID Controllers and SAS-connected Expansion Chassis: Xsan (Metadata and Data) - E5320f + (2) J5600s

Configures a RAID Controller and (2) SAS-connected Expansion Chassis that will be used as an Xsan or StorNext volume. Configures arrays to be used as a metadata LUN, six data LUNs, and six spares. Each Xsan or StorNext volume must contain one metadata LUN.