VTrak E-Class SBB PM v1.0

VTRAK
E-Class
Version 1.0
PRODUCT MANUAL
E830f, E630f, E330f
VTrak E-Class Product Manual
Copyright
2010 PROMISE Technology, Inc. All Rights Reserved. PROMISE, the PROMISE logo, VTrak, SmartStor, SuperTrak, FastTrak, VessRAID, Vess, PerfectPATH, PerfectRAID, SATA150, ULTRA133, VTrak S3000, BackTrak, HyperCache, HyperCache-R, HyperCache-W, DeltaScan and GreenRAID are registered or pending trademarks of PROMISE Technology, Inc. in the U.S. and other countries. All other trademarks are the property of their respective owners. Information regarding products, services and offerings may be superseded by subsequent documents and are subject to change without notice. For the latest information and specifications regarding PROMISE Technology, Inc. and any of its offerings or services, please contact your local PROMISE office or the corporate headquarters. Visit www.promise.com for more information on PROMISE products.
Important data protection information

You should back up all data before installing any drive controller or storage peripheral. PROMISE Technology is not responsible for any loss of data resulting from the use, disuse or misuse of this or any other PROMISE Technology product.
Notice
Although PROMISE Technology has attempted to ensure the accuracy of the content of this document; it is possible that this document may contain technical inaccuracies, typographical, or other errors. PROMISE Technology assumes no liability for any error in this publication, and for damages, whether direct, indirect, incidental, consequential or otherwise, that may result from such error, including, but not limited to loss of data or profits. PROMISE Technology provides this publication as is without warranty of any kind, either express or implied, including, but not limited to implied warranties of merchantability or fitness for a particular purpose. The published information in the manual is subject to change without notice. PROMISE Technology reserves the right to make changes in the product design, layout, and driver revisions without notification to its users. This version of this document supersedes all previous versions.
Recommendations
In this Product Manual, the appearance of products made by other companies, including but not limited to software, servers, and disk drives, is for the purpose of illustration and explanation only. PROMISE Technology does not recommend, endorse, prefer, or support any product made by another manufacturer.
ii
Contents
Chapter 1: Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1 About This Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1 VTrak Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2 Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2 GreenRAID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2 Service and Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2 Architectural Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6 Controller Module Features . . . . . . . . . . . . . . . . . . . . . . . . . . . .6 Drive Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6 External I/O Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6 Data Cache . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6 Operational Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6 RAID Level Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6 RAID Stripe Size Support . . . . . . . . . . . . . . . . . . . . . . . . . . .6 Hot Spare Drives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6 Maximum LUNs Supported . . . . . . . . . . . . . . . . . . . . . . . . .7 Advanced Storage Features . . . . . . . . . . . . . . . . . . . . . . . . .7 Background Activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7 PerfectRAID Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7 GreenRAID Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8 System Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8 Management Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . .8 Supported Browsers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8 General Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9 Power Supplies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9 Voltage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9 Current (Maximum) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9 Power Conversion Efficiency . . . . . . . . . . . . . . . . . . . . . . . .9 Operating Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9 Temperature Range . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9 Humidity Range . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9 Noise, Shock, and Vibration . . . . . . . . . . . . . . . . . . . . . . . . . . . .9 Acoustic Noise Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9 Shock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10 Vibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10 Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10 Weight . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10
iii
Chapter 1: Introduction, cont. Safety and Environmental . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11 Safety Standards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11 Environmental Standards . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11 Warranty and Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12 Warranty . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12 Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12 Chapter 2: Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13 Unpacking the VTrak . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13 Mounting VTrak in a Rack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14 Mounting VTrak E830f/s and E630f/s in a Rack . . . . . . . . . . . .15 Mounting VTrak E330f/s in a Rack . . . . . . . . . . . . . . . . . . . . . .16 Attaching the Sliding Plates . . . . . . . . . . . . . . . . . . . . . . . .17 Installing the Subsystem into the Rack . . . . . . . . . . . . . . . .17 Installing Physical Drives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19 Number of Drives Required . . . . . . . . . . . . . . . . . . . . . . . . . . .19 Drive Slot Numbering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19 Installing Your Drives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20 Making Management and Data Connections . . . . . . . . . . . . . . . . .23 Fibre Channel SAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23 Data Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24 Management Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24 Fibre Channel DAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25 Data Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25 Management Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25 Fibre Channel JBOD Expansion . . . . . . . . . . . . . . . . . . . . . . . .27 Fibre Channel SAN No Single Point of Failure . . . . . . . . . . .28 Data Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28 JBOD Expansion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28 Management Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30 Setting Up Serial Cable Connections . . . . . . . . . . . . . . . . . . . . . . .31 Optional UPS Serial Connection . . . . . . . . . . . . . . . . . . . . . . . .31
iv
Contents
Chapter 3: Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33 Connecting the Power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33 Drive Status Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35 Setting up the Management Ports . . . . . . . . . . . . . . . . . . . . . . . . .36 Setting up the Serial Connection . . . . . . . . . . . . . . . . . . . . . . .36 Choosing DHCP or a Static IP Address . . . . . . . . . . . . . . . . . .36 VTrak Default IP Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . .37 Virtual Management Port . . . . . . . . . . . . . . . . . . . . . . . . . .37 Physical Management Ports . . . . . . . . . . . . . . . . . . . . . . . .37 Setting up VTrak with the CLI . . . . . . . . . . . . . . . . . . . . . . . . . .37 Setting up VTrak with the CLU . . . . . . . . . . . . . . . . . . . . . . . . .39 Setting system date and time . . . . . . . . . . . . . . . . . . . . . . .40 Making Management Port settings Manual IP settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40 Making Management Port settings Automatic IP settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40 Viewing IP address and settings . . . . . . . . . . . . . . . . . . . .40 Making Controller Maintenance Mode Settings . . . . . . . . .40 Making Automatic Settings . . . . . . . . . . . . . . . . . . . . . . . . .41 Making Manual Settings . . . . . . . . . . . . . . . . . . . . . . . . . . .41 Exiting the CLU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41 Logging into WebPAM PROe . . . . . . . . . . . . . . . . . . . . . . . . . . . . .42 Regular Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .42 Secure Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .42 Creating Disk Arrays and Logical Drives . . . . . . . . . . . . . . . . . . . . .44 Automatic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45 Express . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .46 Advanced . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47 Enabling LUN Mapping and Masking . . . . . . . . . . . . . . . . . . . .48 Logging out of WebPAM PROe . . . . . . . . . . . . . . . . . . . . . . . . . . . .49 Using WebPAM PROe over the Internet . . . . . . . . . . . . . . . . . .49 Chapter 4: Management with WebPAM PROe . . . . . . . . . . . . . . . . . .51 Logging into WebPAM PROe . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51 Regular Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51 Secure Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52 Choosing the Display Language . . . . . . . . . . . . . . . . . . . . . . . . . . .53 Perusing the Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55 Logging out of WebPAM PROe . . . . . . . . . . . . . . . . . . . . . . . . . . . .57
Chapter 4: Management with WebPAM PROe, cont. Viewing the Storage Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . .58 Logging onto a Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . .58 Filtering the Subsystem List . . . . . . . . . . . . . . . . . . . . . . . . . . .58 Refreshing the List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .58 Managing Subsystems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59 Viewing Subsystem Information . . . . . . . . . . . . . . . . . . . . . . . .59 Making Subsystem Settings . . . . . . . . . . . . . . . . . . . . . . . . . . .60 Locking or Unlocking the Subsystem . . . . . . . . . . . . . . . . . . . .60 Setting the Lock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60 Resetting the Lock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60 Releasing the Lock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60 Releasing a Lock set by another user . . . . . . . . . . . . . . . .61 Restoring Factory Default Settings . . . . . . . . . . . . . . . . . . . . . .61 Automatic Restart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .62 Clearing Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63 Saving a Service Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63 Importing a Configuration Script . . . . . . . . . . . . . . . . . . . . . . . .66 Exporting a Configuration Script . . . . . . . . . . . . . . . . . . . . . . . .66 Restarting a Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67 Shutting Down the Subsystem . . . . . . . . . . . . . . . . . . . . . . . . .67 Restarting a Subsystem after a Shutdown . . . . . . . . . . . . . . . .68 Managing RAID Controllers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .69 Viewing Controller Information . . . . . . . . . . . . . . . . . . . . . . . . .69 Making Controller Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . .70 Viewing Controller Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . .71 Locating a Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72 Viewing the Flash Image Information . . . . . . . . . . . . . . . . . . . .72 Updating Firmware on a RAID Subsystem . . . . . . . . . . . . . . . .73 Viewing Battery Information . . . . . . . . . . . . . . . . . . . . . . . . . . .73 Reconditioning a Battery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .74 Making Schedule Changes . . . . . . . . . . . . . . . . . . . . . . . . .74 Making Buzzer Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .75 Silencing the Buzzer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .75 Managing Enclosures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .76 Viewing Enclosure Topology . . . . . . . . . . . . . . . . . . . . . . . . . . .76 Viewing the Enclosures Summary . . . . . . . . . . . . . . . . . . . . . .76 Viewing Enclosure Information . . . . . . . . . . . . . . . . . . . . . . . . .77 Making Enclosure Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . .77 Viewing FRU VPD Information . . . . . . . . . . . . . . . . . . . . . . . . .78
vi
Contents
Chapter 4: Management with WebPAM PROe, cont. Managing Enclosures, cont. Viewing Power Supply Status . . . . . . . . . . . . . . . . . . . . . . . . . .78 Viewing Fan Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .78 Viewing Temperature Sensor Status . . . . . . . . . . . . . . . . . . . .79 Viewing Voltage Sensor Status . . . . . . . . . . . . . . . . . . . . . . . . .79 Managing UPS Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .80 Viewing a List of UPS Units . . . . . . . . . . . . . . . . . . . . . . . . . . .80 Making UPS Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .81 Viewing UPS Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . .82 Managing Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .83 Viewing User Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . .83 Creating a User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .83 Setting User Event Subscriptions . . . . . . . . . . . . . . . . . . . . . . .84 Making User Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .85 Making LDAP Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .86 Changing User Passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . .87 Deleting a User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .88 Importing a User Database . . . . . . . . . . . . . . . . . . . . . . . . . . . .88 Exporting a User Database . . . . . . . . . . . . . . . . . . . . . . . . . . . .89 Managing Background Activities . . . . . . . . . . . . . . . . . . . . . . . . . . .90 Viewing Current Background Activities . . . . . . . . . . . . . . . . . . .90 Viewing Scheduled Background Activities . . . . . . . . . . . . . . . .90 Adding a Scheduled Background Activity . . . . . . . . . . . . . . . . .91 Changing a Background Activity Schedule . . . . . . . . . . . . . . . .92 Enabling or Disabling a Scheduled Background Activity . . . . .93 Deleting a Scheduled Background Activity . . . . . . . . . . . . . . . .93 Media Patrol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .94 Making Media Patrol Settings . . . . . . . . . . . . . . . . . . . . . . .94 Redundancy Check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .94 Making Redundancy Check Settings . . . . . . . . . . . . . . . . .94 Initialization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .95 Making Initialization Settings . . . . . . . . . . . . . . . . . . . . . . .95 Rebuild . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .96 Making Rebuild Settings . . . . . . . . . . . . . . . . . . . . . . . . . . .96 Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .96 Making Migration Settings . . . . . . . . . . . . . . . . . . . . . . . . .97 PDM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .97 Making PDM Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . .97 Transition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .98 Making Transition Settings . . . . . . . . . . . . . . . . . . . . . . . . .98
vii
Chapter 4: Management with WebPAM PROe, cont. Managing Background Activities, cont. Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .98 Making Synchronization Settings . . . . . . . . . . . . . . . . . . . .99 Battery Reconditioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .99 Spare Check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .99 Managing Storage Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . .100 Viewing a List of Services . . . . . . . . . . . . . . . . . . . . . . . . . . . .100 Email Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .100 Stopping Email Service . . . . . . . . . . . . . . . . . . . . . . . . . .100 Restarting Email Service . . . . . . . . . . . . . . . . . . . . . . . . .101 Making Email Settings . . . . . . . . . . . . . . . . . . . . . . . . . . .101 SLP Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .101 Stopping SLP Service . . . . . . . . . . . . . . . . . . . . . . . . . . . .102 Restarting SLP Service . . . . . . . . . . . . . . . . . . . . . . . . . .102 Making SLP Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . .102 Webserver Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .102 Stopping Webserver Service . . . . . . . . . . . . . . . . . . . . . .102 Restarting Webserver Service . . . . . . . . . . . . . . . . . . . . .103 Making Webserver Settings . . . . . . . . . . . . . . . . . . . . . . .103 Telnet Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .103 Stopping Telnet Service . . . . . . . . . . . . . . . . . . . . . . . . . .103 Restarting Telnet Service . . . . . . . . . . . . . . . . . . . . . . . . .104 Making Telnet Settings . . . . . . . . . . . . . . . . . . . . . . . . . . .104 SSH Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .104 Stopping SSH Service . . . . . . . . . . . . . . . . . . . . . . . . . . .104 Restarting SSH Service . . . . . . . . . . . . . . . . . . . . . . . . . .105 Making SSH Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . .105 SNMP Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .105 Stopping SNMP Service . . . . . . . . . . . . . . . . . . . . . . . . . .105 Restarting SNMP Service . . . . . . . . . . . . . . . . . . . . . . . . .106 Making SNMP Settings . . . . . . . . . . . . . . . . . . . . . . . . . . .106 Adding an SNMP Trap Sink . . . . . . . . . . . . . . . . . . . . . . .106 Deleting an SNMP Trap Sink . . . . . . . . . . . . . . . . . . . . . .107 CIM Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .107 Stopping CIM Service . . . . . . . . . . . . . . . . . . . . . . . . . . . .107 Restarting CIM Service . . . . . . . . . . . . . . . . . . . . . . . . . . .108 Making CIM Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . .108
viii
Contents
Chapter 4: Management with WebPAM PROe, cont. Managing Storage Services, cont. Netsend Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .108 Starting Netsend Service . . . . . . . . . . . . . . . . . . . . . . . . .109 Stopping Netsend . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .109 Restarting Netsend Service . . . . . . . . . . . . . . . . . . . . . . .109 Making Netsend Settings . . . . . . . . . . . . . . . . . . . . . . . . .109 Adding Netsend Server Accounts . . . . . . . . . . . . . . . . . . .109 Deleting Netsend Server Accounts . . . . . . . . . . . . . . . . . .110 Monitoring Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .111 Monitoring I/O Performance . . . . . . . . . . . . . . . . . . . . . . . . . .111 Monitoring PSU Wattage . . . . . . . . . . . . . . . . . . . . . . . . . . . .112 Managing Physical Drives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .114 Viewing a List of Physical Drives . . . . . . . . . . . . . . . . . . . . . .114 Viewing Physical Drive Information . . . . . . . . . . . . . . . . . . . . .114 Making Global Physical Drive Settings . . . . . . . . . . . . . . . . . .116 Making Individual Physical Drive Settings . . . . . . . . . . . . . . .117 Viewing Physical Drive Statistics . . . . . . . . . . . . . . . . . . . . . .117 Viewing Physical Drive SMART Log Information . . . . . . . . . .118 Saving the Physical Drive SMART Log . . . . . . . . . . . . . . . . . .118 Locating a Physical Drive . . . . . . . . . . . . . . . . . . . . . . . . . . . .119 Forcing a Physical Drive Offline . . . . . . . . . . . . . . . . . . . . . . .119 Clearing a Stale or a PFA Condition . . . . . . . . . . . . . . . . . . . .120 Updating Firmware on a Physical Drive . . . . . . . . . . . . . . . . .120 Managing Disk Arrays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .121 Viewing a List of Disk Arrays . . . . . . . . . . . . . . . . . . . . . . . . .121 Viewing Disk Array Information . . . . . . . . . . . . . . . . . . . . . . . .121 Creating a Disk Array Manually . . . . . . . . . . . . . . . . . . . . . . .122 Creating a Disk Array with the Wizard . . . . . . . . . . . . . . . . . .123 Wizard: Automatic Configuration . . . . . . . . . . . . . . . . . . .123 Wizard: Express Configuration . . . . . . . . . . . . . . . . . . . . .124 Wizard: Advanced Configuration . . . . . . . . . . . . . . . . . . .125 Deleting a Disk Array . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .127 Making Disk Array Settings . . . . . . . . . . . . . . . . . . . . . . . . . . .128 Locating a Disk Array . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .128 Running Media Patrol on a Disk Array . . . . . . . . . . . . . . . . . .129 Running Media Patrol . . . . . . . . . . . . . . . . . . . . . . . . . . . .129 Stopping, Pausing or Resuming Media Patrol . . . . . . . . .129
ix
Chapter 4: Management with WebPAM PROe, cont. Managing Disk Arrays, cont. Running PDM on a Disk Array . . . . . . . . . . . . . . . . . . . . . . . .129 Running PDM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .129 Stopping, Pausing or Resuming PDM . . . . . . . . . . . . . . .130 Preparing a Disk Array for Transport . . . . . . . . . . . . . . . . . . .130 Rebuilding a Disk Array . . . . . . . . . . . . . . . . . . . . . . . . . . . . .130 Performing a Manual Rebuild . . . . . . . . . . . . . . . . . . . . . .131 Stopping, Pausing or Resuming a Rebuild . . . . . . . . . . . .131 Managing Logical Drives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .132 Viewing a List of Logical Drives . . . . . . . . . . . . . . . . . . . . . . .132 Viewing Logical Drive Information . . . . . . . . . . . . . . . . . . . . . .132 Viewing Logical Drive Statistics . . . . . . . . . . . . . . . . . . . . . . .133 Viewing Logical Drive Check Tables . . . . . . . . . . . . . . . . . . . .134 Creating a Logical Drive Manually . . . . . . . . . . . . . . . . . . . . .135 Deleting a Logical Drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . .136 Making Logical Drive Settings . . . . . . . . . . . . . . . . . . . . . . . . .136 Locating a Logical Drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . .137 Initializing a Logical Drive . . . . . . . . . . . . . . . . . . . . . . . . . . . .137 Stopping, Pausing or Resuming an Initialization . . . . . . .138 Redundancy Check on a Logical Drive . . . . . . . . . . . . . . . . . .138 Stopping, Pausing or Resuming a Redundancy Check . .138 Migrating a Logical Drives RAID Level . . . . . . . . . . . . . . . . . .139 Migrating a Logical Drive . . . . . . . . . . . . . . . . . . . . . . . . .139 Managing Spare Drives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .141 Viewing a List of Spare Drives . . . . . . . . . . . . . . . . . . . . . . . .141 Viewing Spare Drive Information . . . . . . . . . . . . . . . . . . . . . .141 Creating a Spare Drive Manually . . . . . . . . . . . . . . . . . . . . . .142 Deleting a Spare Drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .143 Making Spare Drive Settings . . . . . . . . . . . . . . . . . . . . . . . . .143 Locating a Spare Drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .143 Running Spare Check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .144 Running a Transition on a Spare Drive . . . . . . . . . . . . . . . . . .144 Running a Transition . . . . . . . . . . . . . . . . . . . . . . . . . . . .144 Stopping, Pausing or Resuming a Transition . . . . . . . . . .145 Managing LUNs and Initiators . . . . . . . . . . . . . . . . . . . . . . . . . . . .146 Viewing a List of LUN Maps . . . . . . . . . . . . . . . . . . . . . . . . . .146 LUN Mapping and Masking . . . . . . . . . . . . . . . . . . . . . . . . . . .146 Adding a LUN Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .146 Editing a LUN Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .147
Contents
Chapter 4: Management with WebPAM PROe, cont. Managing LUNs and Initiators, cont. Deleting a LUN Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .147 Enabling and Disabling LUN Masking . . . . . . . . . . . . . . . . . . .148 Viewing a List of Initiators . . . . . . . . . . . . . . . . . . . . . . . . . . . .148 Managing Fibre Channel Connections . . . . . . . . . . . . . . . . . . . . .149 Viewing FC Node Information . . . . . . . . . . . . . . . . . . . . . . . . .149 Viewing FC Port Information . . . . . . . . . . . . . . . . . . . . . . . . . .149 Making FC Port Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . .150 Port Setting Information . . . . . . . . . . . . . . . . . . . . . . . . . .150 Viewing FC Port Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . .151 Viewing a List of FC Initiators on the Fabric . . . . . . . . . . . . . .151 Viewing a List of FC Logged-in Devices . . . . . . . . . . . . . . . . .151 Viewing a List of FC SFPs . . . . . . . . . . . . . . . . . . . . . . . . . . .151 Adding an FC Initiator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .152 Deleting an FC Initiator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .152 Managing SAS Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . .153 Viewing SAS Port Information . . . . . . . . . . . . . . . . . . . . . . . . .153 Viewing SAS Port Statistics . . . . . . . . . . . . . . . . . . . . . . . . . .153 Making SAS Port Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . .153 Viewing a List of SAS Initiators . . . . . . . . . . . . . . . . . . . . . . . .154 Adding a SAS Initiator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .154 Deleting a SAS Initiator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .154 Chapter 5: Management with the CLU . . . . . . . . . . . . . . . . . . . . . . .155 Initial Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .156 Making a Serial Connection . . . . . . . . . . . . . . . . . . . . . . . . . .156 Making a Telnet Connection . . . . . . . . . . . . . . . . . . . . . . . . . .157 Making a SSH Connection . . . . . . . . . . . . . . . . . . . . . . . . . . .157 Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .157 Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .157 Logging Into the CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .158 Accessing Online Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .159 Exiting the CLU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .159 Logging Out of the CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .160 Logging Back Into the CLI and CLU . . . . . . . . . . . . . . . . . . . .160 Running Quick Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .161
xi
Chapter 5: Management with the CLU, cont. Managing the Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .162 Making Subsystem Settings . . . . . . . . . . . . . . . . . . . . . . . . . .162 Running Media Patrol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .162 Locking or Unlocking the Subsystem . . . . . . . . . . . . . . . . . . .163 Setting the Lock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .163 Resetting the Lock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .163 Releasing the Lock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .163 Releasing a Lock set by another user . . . . . . . . . . . . . . .163 Setting Subsystem Date and Time . . . . . . . . . . . . . . . . . . . . .163 Making NTP Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .164 Synchronizing with a NTP Server . . . . . . . . . . . . . . . . . . . . . .165 Managing the Controllers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .166 Viewing Controller Information . . . . . . . . . . . . . . . . . . . . . . . .166 Clearing Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .166 Clearing an Orphan Watermark . . . . . . . . . . . . . . . . . . . . . . .166 Making Controller Settings . . . . . . . . . . . . . . . . . . . . . . . . . . .167 Locating the Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .168 Managing the Enclosure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .170 Viewing the Enclosures Summary . . . . . . . . . . . . . . . . . . . . .170 Viewing Enclosure Information . . . . . . . . . . . . . . . . . . . . . . . .170 Adjustable items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .171 Making Enclosure Settings . . . . . . . . . . . . . . . . . . . . . . . . . . .171 Viewing FRU VPD Information . . . . . . . . . . . . . . . . . . . . . . . .171 Viewing Power Supply Status . . . . . . . . . . . . . . . . . . . . . . . . .171 Locating a Power Supply . . . . . . . . . . . . . . . . . . . . . . . . . . . .172 Viewing Cooling Unit Status . . . . . . . . . . . . . . . . . . . . . . . . . .172 Viewing Temperature Sensor Status . . . . . . . . . . . . . . . . . . .172 Viewing Voltage Sensor Status . . . . . . . . . . . . . . . . . . . . . . . .173 Viewing Battery Information . . . . . . . . . . . . . . . . . . . . . . . . . .173 Battery Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .173 Reconditioning a Battery . . . . . . . . . . . . . . . . . . . . . . . . . . . . .174 Locating an Enclosure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .174 Viewing Enclosure Topology . . . . . . . . . . . . . . . . . . . . . . . . . .174 Managing Physical Drives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .176 Viewing a List of Physical Drives . . . . . . . . . . . . . . . . . . . . . .176 Making Global Physical Drive Settings . . . . . . . . . . . . . . . . . .176 Viewing Physical Drive Information . . . . . . . . . . . . . . . . . . . . .177 Viewing Physical Drive Statistics . . . . . . . . . . . . . . . . . . . . . .177 Clearing Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .177
xii
Contents
Chapter 5: Management with the CLU, cont. Managing Physical Drives, cont. Setting an Alias . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .178 Clearing Stale and PFA Conditions . . . . . . . . . . . . . . . . . . . .178 Forcing a Physical Drive Offline or Online . . . . . . . . . . . . . . .178 Locating a Physical Drive . . . . . . . . . . . . . . . . . . . . . . . . . . . .179 Managing Disk Arrays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .180 Viewing a List of Disk Arrays . . . . . . . . . . . . . . . . . . . . . . . . .180 Creating a Disk Array . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .180 Creating a Disk Array Automatic . . . . . . . . . . . . . . . . . . . . .181 Creating a Disk Array Express . . . . . . . . . . . . . . . . . . . . . . .182 Creating a Disk Array Advanced . . . . . . . . . . . . . . . . . . . . .183 Deleting a Disk Array . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .184 Making Disk Array Settings . . . . . . . . . . . . . . . . . . . . . . . . . . .184 Viewing Disk Array Information . . . . . . . . . . . . . . . . . . . . . . . .185 Disk Array Operational Status . . . . . . . . . . . . . . . . . . . . .185 Accepting an Incomplete Array . . . . . . . . . . . . . . . . . . . . . . . .186 Enabling Media Patrol, PDM, and Power Management on a Disk Array . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .186 Preparing the Disk Array for Transport . . . . . . . . . . . . . . . . . .187 Rebuilding a Disk Array . . . . . . . . . . . . . . . . . . . . . . . . . . . . .187 Migrating a Disk Array . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .187 Running PDM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .188 Running Transition on a Disk Array . . . . . . . . . . . . . . . . . . . .190 Locating a Disk Array . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .190 Creating a Logical Drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . .190 Deleting a Logical Drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . .192 Managing Spare Drives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .193 Viewing a list of Spare Drives . . . . . . . . . . . . . . . . . . . . . . . . .193 Creating a Spare Drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .193 Making Spare Drive Settings . . . . . . . . . . . . . . . . . . . . . . . . .194 Running Spare Check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .194 Deleting a Spare Drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .195 Managing Logical Drives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .196 Viewing Logical Drive Information . . . . . . . . . . . . . . . . . . . . . .196 Viewing Logical Drive Statistics . . . . . . . . . . . . . . . . . . . . . . .196 Clearing Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .196 Viewing the Logical Drive Check Table . . . . . . . . . . . . . . . . .197 Making Logical Drive Settings . . . . . . . . . . . . . . . . . . . . . . . . .197
xiii
Chapter 5: Management with the CLU, cont. Managing Logical Drives, cont. Initializing a Logical Drive . . . . . . . . . . . . . . . . . . . . . . . . . . . .197 Running Redundancy Check . . . . . . . . . . . . . . . . . . . . . . . . .198 Locating a Logical Drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . .199 Managing the Network Connection . . . . . . . . . . . . . . . . . . . . . . . .200 Making Virtual Management Port Settings . . . . . . . . . . . . . . .200 Making Automatic Settings . . . . . . . . . . . . . . . . . . . . . . . .200 Making Manual Settings . . . . . . . . . . . . . . . . . . . . . . . . . .200 Making Controller Management Port Settings . . . . . . . . . . . .200 Making Automatic Settings . . . . . . . . . . . . . . . . . . . . . . . .201 Making Manual Settings . . . . . . . . . . . . . . . . . . . . . . . . . .201 Managing Fibre Channel Connections . . . . . . . . . . . . . . . . . . . . .202 Viewing Node Information . . . . . . . . . . . . . . . . . . . . . . . . . . . .202 Viewing Fibre Channel Logged-in Devices . . . . . . . . . . . . . . .202 Making Fibre Channel Port Settings . . . . . . . . . . . . . . . . . . . .202 Viewing SFP Information . . . . . . . . . . . . . . . . . . . . . . . . . . . .203 Viewing Fibre Channel Port Statistics . . . . . . . . . . . . . . . . . . .204 Clearing Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .204 Property Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . .204 Clearing Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .205 Viewing Fibre Channel Initiators . . . . . . . . . . . . . . . . . . . . . . .205 Adding a Fibre Channel Initiator . . . . . . . . . . . . . . . . . . . . . . .205 Managing SAS Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . .206 Viewing SAS Port Information . . . . . . . . . . . . . . . . . . . . . . . . .206 Making SAS Port Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . .206 Viewing SAS Port Statistics . . . . . . . . . . . . . . . . . . . . . . . . . .207 Clearing Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .207 Viewing SAS Initiators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .207 Adding a SAS Initiator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .207 Managing Background Activity . . . . . . . . . . . . . . . . . . . . . . . . . . .208 Viewing Current Background Activities . . . . . . . . . . . . . . . . . .208 Making Background Activity Settings . . . . . . . . . . . . . . . . . . .208 Working with the Event Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . .210 Viewing Runtime Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . .210 Clearing Runtime Events . . . . . . . . . . . . . . . . . . . . . . . . . . . .210 Viewing NVRAM Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . .210 Clearing NVRAM Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . .211
xiv
Contents
Chapter 5: Management with the CLU, cont. Working with LUN Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .212 Viewing a List of Initiators . . . . . . . . . . . . . . . . . . . . . . . . . . . .212 Enabling LUN Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .212 Adding an Initiator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .212 Mapping a LUN to an Initiator . . . . . . . . . . . . . . . . . . . . . . . . .213 Deleting an Initiator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .213 Managing UPS Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .214 Viewing a List of UPS Units . . . . . . . . . . . . . . . . . . . . . . . . . .214 Making UPS Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .215 Viewing UPS Information . . . . . . . . . . . . . . . . . . . . . . . . . . . .216 Managing Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .217 Viewing User Information . . . . . . . . . . . . . . . . . . . . . . . . . . . .217 Creating a User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .217 Changing Another Users Settings . . . . . . . . . . . . . . . . . . . . .218 Changing Your Own User Settings . . . . . . . . . . . . . . . . . . . . .219 Changing Another Users Password . . . . . . . . . . . . . . . . . . . .219 Changing Your Own Password . . . . . . . . . . . . . . . . . . . . . . . .219 Deleting a User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .220 Working with Software Management . . . . . . . . . . . . . . . . . . . . . . .221 Making Email Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .221 Making SLP Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .222 Making Webserver Settings . . . . . . . . . . . . . . . . . . . . . . . . . .222 Making Telnet Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .223 Making SSH Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .223 Making SNMP Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .224 Managing SNMP Trap Sinks . . . . . . . . . . . . . . . . . . . . . . . . . .224 Viewing a List of Trap Sinks . . . . . . . . . . . . . . . . . . . . . . .224 Adding a Trap Sink . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .224 Deleting a Trap Sink . . . . . . . . . . . . . . . . . . . . . . . . . . . . .225 Making CIM Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .225 Making Netsend Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . .227 Managing Netsend Recipients . . . . . . . . . . . . . . . . . . . . . . . .227 Netsend Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . .227 Adding Netsend recipients . . . . . . . . . . . . . . . . . . . . . . . .227 Deleting Netsend Recipients . . . . . . . . . . . . . . . . . . . . . .228 Flashing through TFTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .229 Viewing Flash Image Information . . . . . . . . . . . . . . . . . . . . . . . . .230 Clearing Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .231 Restoring Factory Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .232
xv
Chapter 5: Management with the CLU, cont. Shutting Down the Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . .233 Shutting down the VTrak Telnet Connection . . . . . . . . . . . .233 Shutting down the VTrak SSH Connection . . . . . . . . . . . . .233 Shutting down the VTrak Serial Connection . . . . . . . . . . . .234 Starting Up After Shutdown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .235 Starting up the VTrak Telnet Connection . . . . . . . . . . . . . . .235 Starting up the VTrak SSH Connection . . . . . . . . . . . . . . . .235 Starting up the VTrak Serial Connection . . . . . . . . . . . . . . .236 Restarting the Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .237 Restarting VTrak Telnet Connection . . . . . . . . . . . . . . . . . .237 Restarting VTrak SSH Connection . . . . . . . . . . . . . . . . . . .237 Restarting VTrak Serial Connection . . . . . . . . . . . . . . . . . . .238 Making Buzzer Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .239 Chapter 6: Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .241 Updating the Subsystem Firmware . . . . . . . . . . . . . . . . . . . . . . . .241 Updating with WebPAM PROe . . . . . . . . . . . . . . . . . . . . . . . .241 Automatic Restart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .242 Manual Restart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .242 Updating with the CLU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .244 Automatic Restart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .245 Manual Restart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .245 Updating with USB Support . . . . . . . . . . . . . . . . . . . . . . . . . .246 Automatic Restart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .247 Failed Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .247 Updating Physical Drive Firmware . . . . . . . . . . . . . . . . . . . . . . . .248 WebPAM PROe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .248 Restarting a Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . .249 Replacing a Power Supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .250 E830f and E630f . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .250 Removing the Old Power Supply . . . . . . . . . . . . . . . . . . .250 Installing a New Power Supply . . . . . . . . . . . . . . . . . . . . .250 E330f . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .251 Removing the Old Power Supply . . . . . . . . . . . . . . . . . . .251 Installing a New Power Supply . . . . . . . . . . . . . . . . . . . . .251 Replacing a Cache Backup Battery . . . . . . . . . . . . . . . . . . . . . . . .252 E830f and E630f . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .252 Removing the Old Battery . . . . . . . . . . . . . . . . . . . . . . . .252 Installing a New Battery . . . . . . . . . . . . . . . . . . . . . . . . . .252
xvi
Contents
Chapter 6: Maintenance, cont. Replacing a RAID Controller Dual Controllers . . . . . . . . . . . . . .254 Removing the Old Controller . . . . . . . . . . . . . . . . . . . . . . . . . .254 Installing the New Controller . . . . . . . . . . . . . . . . . . . . . . . . . .255 Replacing a RAID Controller Single Controller . . . . . . . . . . . . . .256 Removing the Old Controller . . . . . . . . . . . . . . . . . . . . . . . . . .256 Installing the New Controller . . . . . . . . . . . . . . . . . . . . . . . . . .257 Resetting the Default Password . . . . . . . . . . . . . . . . . . . . . . . . . .258 Chapter 7: Technology Background . . . . . . . . . . . . . . . . . . . . . . . .259 Disk Arrays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .259 Media Patrol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .259 PDM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .259 Power Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .260 Logical Drives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .261 RAID Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .261 RAID 0 Stripe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .261 RAID 1 Mirror . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .263 RAID 1E Enhanced Mirror . . . . . . . . . . . . . . . . . . . . . . .265 RAID 5 Block and Parity Stripe . . . . . . . . . . . . . . . . . . .266 RAID 6 Block and Double Parity Stripe . . . . . . . . . . . . .267 RAID 10 Mirror + Stripe . . . . . . . . . . . . . . . . . . . . . . . . .268 RAID 50 Striping of Distributed Parity . . . . . . . . . . . . . .270 RAID 50 Axles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .270 RAID 60 Striping of Double Parity . . . . . . . . . . . . . . . . .273 RAID 60 Axles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .273 RAID Level Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .275 Migration Requirements . . . . . . . . . . . . . . . . . . . . . . . . . .275 Source and Target RAID Levels . . . . . . . . . . . . . . . . . . . .275 RAID 0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .276 RAID 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .277 RAID 1E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .277 RAID 5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .278 RAID 6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .278 RAID 10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .279 RAID 50 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .280 RAID 60 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .280 Stripe Size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .281 Sector Size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .281
xvii
Chapter 7: Technology Background, cont. Logical Drives, cont. Preferred Controller ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .281 Initialization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .282 Partition and Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .282 Spare Drives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .283 Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .283 Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .283 Transition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .284 Running a Transition . . . . . . . . . . . . . . . . . . . . . . . . . . . .284 Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .285 Automatic Transition . . . . . . . . . . . . . . . . . . . . . . . . . . . . .287 Manual Transition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .287 RAID Controllers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .289 LUN Affinity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .289 Cache Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .289 Read Cache Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .289 Write Cache Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .289 Forced Read-Ahead Cache . . . . . . . . . . . . . . . . . . . . . . .290 Adaptive Writeback Cache . . . . . . . . . . . . . . . . . . . . . . . .290 Preferred Controller ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .291 Power Saving . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .291 Capacity Coercion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .291 Chapter 8: Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .293 VTrak is Beeping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .293 Silencing the Buzzer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .294 LEDs Display Amber or Red . . . . . . . . . . . . . . . . . . . . . . . . . . . . .295 Front Panel LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .295 Drive Carrier LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .296 Back Panel LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .297 Checking Component Installation . . . . . . . . . . . . . . . . . . . . . .299 CLU Reports a Problem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .300 Viewing Runtime Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . .300 Viewing NVRAM Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . .300 Checking a Reported Component . . . . . . . . . . . . . . . . . . . . . .301 WebPAM PROe Reports a Problem . . . . . . . . . . . . . . . . . . . . . . .303 USB Support Reports a Problem . . . . . . . . . . . . . . . . . . . . . . . . . .307
xviii
Contents
Chapter 8: Troubleshooting, cont. Enclosure Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .308 Diagnosing an Enclosure Problem . . . . . . . . . . . . . . . . . . . . .308 Overheating . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .310 Fan Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .310 Inadequate Air Circulation . . . . . . . . . . . . . . . . . . . . . . . .310 Power Supplies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .310 Batteries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .311 Controller Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .312 Maintenance Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .312 Finding and Correcting the Cause of the Problem . . . . . . . . .312 Taking a Controller out of Maintenance Mode . . . . . . . . . . . .313 Serial Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .313 Telnet Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .314 Unsaved Data in the Controller Cache . . . . . . . . . . . . . . . . . .314 Physical Drive Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .316 Disk Array and Logical Drive Problems . . . . . . . . . . . . . . . . . . . . .317 Disk Array Degraded/Logical Drive Critical . . . . . . . . . . . . . .317 Disk Array Offline/Logical Drive Offline . . . . . . . . . . . . . . . . .318 Repairing an Offline Disk Array or Logical Drive . . . . . . . . . . .319 RAID 1, 1E, 5, 6, 10, 50, and 60 Logical Drives . . . . . . . .319 RAID 0 Logical Drives . . . . . . . . . . . . . . . . . . . . . . . . . . .319 Rebuilding a Disk Array . . . . . . . . . . . . . . . . . . . . . . . . . . . . .319 Incomplete Array . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .320 Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .320 Transport . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .320 Connection Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .322 Serial Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .322 Network Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .323 Fibre Channel Connections . . . . . . . . . . . . . . . . . . . . . . . . . .323 SAS Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .324 Blocked Cable Connectors . . . . . . . . . . . . . . . . . . . . . . . .324 Faulty Cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .324 Faulty Controller or I/O Module Connector . . . . . . . . . . . .324 Browser Does Not Connect to WebPAM PROe . . . . . . . . . . .325 Power Cycling the Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . .326 Event Notification Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . .327
xix
Chapter 9: Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .345 Frequently Asked Questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . .345 Contacting Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . .351 Limited Warranty . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .354 Returning the Product For Repair . . . . . . . . . . . . . . . . . . . . . . . . .356 Appendix A: Useful Information . . . . . . . . . . . . . . . . . . . . . . . . . . . .359 SNMP MIB Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .359 Adding a Second RAID Controller . . . . . . . . . . . . . . . . . . . . . . . . .359 Installing a Second RAID Controller . . . . . . . . . . . . . . . . . . . . . . .360 RAID Controller in Maintenance Mode . . . . . . . . . . . . . . . . . .360 New Settings for Dual Controllers . . . . . . . . . . . . . . . . . . . . . .361 Dual Controllers and SATA Drives . . . . . . . . . . . . . . . . . . . . .361 Appendix B: Multipathing on Windows . . . . . . . . . . . . . . . . . . . . . .363 Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .363 Installing PerfectPath . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .364 Verifying Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .365 Start Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .365 Services List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .365 Device Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .365 Running Perfect Path View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .367 Starting PerfectPath View . . . . . . . . . . . . . . . . . . . . . . . . . . . .367 Quitting PerfectPath View . . . . . . . . . . . . . . . . . . . . . . . . . . . .367 Monitoring Your LUNs and Paths . . . . . . . . . . . . . . . . . . . . . . . . .368 Viewing LUN Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . .368 Viewing Path Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . .369 Viewing LUN Performance Statistics . . . . . . . . . . . . . . . . . . .370 Viewing Path Performance Statistics . . . . . . . . . . . . . . . . . . .371 Viewing Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .373 Clearing Path Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .373 Features and Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .374 Automatic Load Balancing for Failover Policy . . . . . . . . . . . . .374 Enabling Automatic Load Balancing . . . . . . . . . . . . . . . . .374 Load Balance Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .375 Changing Load Balance Policy Settings . . . . . . . . . . . . . .375 Path Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .376 Changing Path Verification Settings . . . . . . . . . . . . . . . . .376 PDO Removal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .377 Changing PDO Removal Settings . . . . . . . . . . . . . . . . . .377
xx
Contents
Appendix B: Multipathing on Windows, cont. Features and Settings, cont. Performance Tab Refresh Rate . . . . . . . . . . . . . . . . . . . . . . .378 Changing Refresh Rate Settings . . . . . . . . . . . . . . . . . . .378 Round Robin Count . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .378 Changing the Round Robin Count . . . . . . . . . . . . . . . . . .378 Refreshing the Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .379 Viewing System Information . . . . . . . . . . . . . . . . . . . . . . . . . .379 Saving System Information . . . . . . . . . . . . . . . . . . . . . . . . . . .380 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .381 Updating PerfectPath . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .382 Repairing PerfectPath . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .383 Removing PerfectPath . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .384 Preferred Method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .384 Alternate Method 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .384 Alternate Method 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .384 Appendix C: Multipathing on Linux . . . . . . . . . . . . . . . . . . . . . . . . .385 Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .385 Check Initial Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .386 Task 1: Meeting Package Requirements . . . . . . . . . . . . . . . . . . . .387 Installing Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .387 Verifying Packages RedHat . . . . . . . . . . . . . . . . . . . . . . . . .388 Verifying Packages SuSE . . . . . . . . . . . . . . . . . . . . . . . . . .388 Task 2: Preparing the Configuration File . . . . . . . . . . . . . . . . . . . .390 RedHat Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .390 SuSE Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .390 Editing a Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . .390 Task 3: Making Initial Host Settings . . . . . . . . . . . . . . . . . . . . . . .392 Setting the Daemon to Run . . . . . . . . . . . . . . . . . . . . . . . . . . .392 RHEL 5.3, 5.4, 5.5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .392 SLES 10 SP2, 10 SP3, 11, 11 SP1 . . . . . . . . . . . . . . . . .392 Verifying the Modules are Loaded . . . . . . . . . . . . . . . . . . . . .392 Verifying the Daemon is Running . . . . . . . . . . . . . . . . . . . . . .393 Task 4: Create and Configure Devices . . . . . . . . . . . . . . . . . . . . .394
xxi
Appendix C: Multipathing on Linux, cont. Task 5: Setting-up ALUA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .395 RedHat Linux RHEL 5.4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . .395 Default Kernel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .395 Kernel with XEN or PAE support . . . . . . . . . . . . . . . . . . .395 RedHat Linux RHEL 5.5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . .396 Default Kernel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .396 Kernel with XEN or PAE support . . . . . . . . . . . . . . . . . . .397 SuSE Linux SLES 10 SP3 . . . . . . . . . . . . . . . . . . . . . . . . . . .397 SuSE Linux SLES 11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .398 SuSE Linux SLES 11 SP1 . . . . . . . . . . . . . . . . . . . . . . . . . . .399 Updated with Novell SP1 patches . . . . . . . . . . . . . . . . . .399 Fibre Channel HBA to VTrak . . . . . . . . . . . . . . . . . . . . . .399 RPM Packages and Documents for Linux MPIO . . . . . . . . . . . . . .400 Linux MPIO: Known Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .402 Sample multipath.conf File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .403 Index. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .405
xxii
Chapter 1: Introduction
This chapter covers the following topics: About This Manual (below) VTrak Overview (page 2) Architectural Description (page 3) Features (page 6) General Specifications (page 9) Safety and Environmental (page 11) Warranty and Support (page 12)
About This Manual

This Product Manual describes how to setup, use, and maintain the VTrak E830f, E630f, and E330f external disk array subsystems. It describes how to use the: Built-in command-line interface (CLI) Built-in command-line utility (CLU) Embedded Web-based Promise Array Management Professional (WebPAM PROe) software.
This manual includes a full table of contents, index, chapter task lists and numerous cross-references to help you find the specific information you are looking for. Also included are four levels of notices: Warning A Warning notifies you of probable equipment damage or loss of data, or the possibility of physical injury, and how to avoid them. Caution A Caution informs you of possible equipment damage or loss of data and how to avoid them. Important An Important message calls attention to an essential step or point required to complete a task, including things often missed.
Note A Note provides helpful information such as hints or alternative ways of doing a task.
VTrak Overview
The PROMISE VTrak Ex30f is coupled with high speed 8 Gb/s Fibre Channel host connectivity, support for 6 Gb/s SAS and SATA disks and a next-generation embedded storage I/O processing platform out to set a new performance standard while providing a reliable, flexible and easy to manage RAID storage system.
Performance
The PROMISE VTrak Ex30f is built using the Intels next-generation storage platform, the Intel Xeon processor C5500/C3500 series to keep pace with performance demands with four 8 Gb/s Fibre Channel ports per controller and support for 6 Gb/s SAS and SATA hard disk drives and solid state drives. Delivered in a Storage Bridge Bay (SBB) 2.0 compliant package, the Ex30f offers the full redundancy that is expected of an enterprise solution. Dual active-active controller modules with cache mirroring over a PCIe Gen 2 link allow for redundant data paths to ensure data availability while dual power supply/cooling units minimize downtime and any disruption to business continuity.
GreenRAID
PROMISE cares about the environment. VTrak products utilize environmentally friendly production methods and materials and are designed with high-efficiency in mind. Powered by 80Plus certified power supplies that offer up to 85% power efficiency, all VTrak Ex30 products improve total cost of ownership by conserving power, reducing heat output and improving cooling costs. Additionally, the PROMISE as GreenRAID story includes advanced power management support for hard disk drives providing up to 65% energy savings.
Service and Support

Every VTrak Ex30 subsystem is backed by the PROMISE Three-Year limited warranty with 24-hour, 7-day telephone and e-mail support. In addition to our industry leading warranty, PROMISE offers extended warranty and onsite parts replacement options with service levels with response times as low four hours.
Architectural Description
The VTrak E830f, E630f, and E330f are Fibre Channel subsystems suitable for Direct Attached Storage (DAS), Storage Area Network (SAN), and Expanded Storage. Model VTE830fS VTE830fD VTE630fS VTE630fD VTE330fS VTE330fD RAID Controllers 1 2 1 2 1 2 Drives Supported 24 24 16 16 12 12 Rack Units 4U 4U 3U 3U 2U 2U
Figure 1. VTrak E830f front view Drive Carrier LEDs
Drive Carriers
Power and Status LEDs
Figure 2. VTrak E630f front view Drive Carrier LEDs
Drive Carriers Figure 3. VTrak E330f front view Drive Carrier LEDs
Drive Carriers Figure 4. VTrak E830f back view RAID Controller 1
RAID Controller 2
UPS
Mgmt
UPS
Mgmt
FC 1
115200 8N1
FC 2
FC 3
FC 4
115200 8N1
FC 1
8 4 2 Gb/s
FC 2
FC 3
FC 4
8 4 2 Gb/s
Power Supply 1
Power Supply 2
Figure 5. VTrak E630f back view RAID Controller 1 RAID Controller 2
UPS
Mgmt
UPS
Mgmt
FC 1
115200 8N1
FC 2
FC 3
FC 4
115200 8N1
FC 1
8 4 2 Gb/s
FC 2
FC 3
FC 4
8 4 2 Gb/s
Power Supply 1 Figure 6. VTrak E330f back view RAID Controller 1
Power Supply 2
RAID Controller 2
Power Supply 1
Power Supply 2
Features
Controller Module Features
Drive Support
3.5-inch and 2.5-inch form factor Hard disk drives (HDDs) and Solid State drives (SSDs) SAS, 6 Gb/s and 3 Gb/s SATA, 6 Gb/s and 3 Gb/s Supports any mix of SAS and SATA drives simultaneously in the same enclosure For a list of supported drives, go to PROMISE support: http://www.promise.com/support/ SATA physical drives require a SAS-to-SATA adapter, available from PROMISE.
External I/O Ports

(per controller) Four 8 Gb/s Fibre Channel ports, compatible with 4 Gb/s and 2 Gb/s One external SAS port with an SFF-8088 SAS connector, supports up to 7 cascading JBOD expansion units
Data Cache
2 GB data cache per controller. A portion of the data cache is shared with the controller firmware Protected with hot-swappable battery backup unit (BBU)
Operational Features
RAID Level Support
0, 1, 1E, 5, 6, 10, 50, and 60
RAID Stripe Size Support

64K, 128K, 256K, 512K, and 1MB
Hot Spare Drives

Global Dedicated Revertible option
Features
Maximum LUNs Supported

LUNs: 1024 Array: 32
Advanced Storage Features

Advanced Cache Mirroring over PCIe Gen2 Simple, drag-and-drop LUN Masking and Mapping Asymmetric LUN Unit Access (ALUA) Volume Copy PerfectFlash - Non-Disruptive Software Update I/O performance & power monitoring tools Guaranteed Latency Technology (an advanced OEM feature) USB Service Log LDAP Support for central user management
Background Activities
Media Patrol Background Synchronization Foreground Initialization Rebuild Redundancy Check Disk SMART Polling Online Capacity Expansion (OCE) RAID Level Migration (RLM) UPS Monitoring Feature rich task scheduler for background activities
PerfectRAID Features
Predictive Data Migration (PDM) Intelligent Bad Sector Remapping SMART Error Handling NVRAM Error Logging Disk Slot Power Control Read/Write Check Table Write Hole Table
GreenRAID Features
Four levels of advanced power management disk drive (MAID) support Efficient 80Plus Bronze Certified power supplies
System Management
Management Interfaces
Browser-based management with WebPAM PROe over Ethernet Command Line Interface (CLI) over Serial Port, Ethernet via Telnet, or SSH Command Line Utility (CLU) over Serial Port, Ethernet via Telnet, or SSH Third Party Management Support via SNMP and CIM
Supported Browsers
The Host PC, from which you monitor and manage the VTrak subsystem, install the latest version of: Internet Explorer Firefox For a list of supported browsers, go to PROMISE support: http://www.promise.com/support/
General Specifications
General Specifications
Power Supplies
4U/24 Bay: Dual 750W, 100-240 Vac auto-ranging, 50-60 Hz, dual hot swap and redundant with PFC, N+1 design. Meets 80Plus bronze. 3U/16 Bay: Dual 580W, 100-240 Vac auto-ranging, 50-60 Hz, dual hot swap and redundant with PFC, N+1 design. Meets 80Plus bronze. 2U/12 Bay: Dual 550W, 100-240 VAC auto-ranging, 50-60Hz, dual hot swap and redundant with PFC, N+1 design. Meets 80Plus gold.
Voltage
100-240 VAC Auto-Ranging
Current (Maximum)
10 A @ 100 VAC 5 A @ 200 VAC
Power Conversion Efficiency

>80% @ 110V (>20% load) >80% @ 240V (>20% load)
Operating Environment
Temperature Range
Operational: 5 to 35C (41 to 95F) Non-Operational: -40 to 60C (-40 to 140F)
Humidity Range
Operational: 10% to 90% (Non-Condensing) Non-Operational: 5% to 95% (Non-Condensing)
Noise, Shock, and Vibration

Acoustic Noise Levels
Typical: 55 dB Maximum: 65 dB
Shock
Operational: 5G, 11 ms duration Non-Operational: 10G, 11ms duration
Vibration
Operational: 0.3G, 5 to 500 Hz Non-Operational: 1G, 5 to 500 Hz
Dimensions
(Height, Width, Depth) 4U/24 Bay: 17.4 x 44.7 x 50.7 cm (6.9 x 17.6 x 19.96 in) 3U/16 Bay: 13.1 x 44.7 x 50.7 cm (5.2 x 17.6 x 19.96 in) 2U/12 Bay: 8.6 x 44.7 x 50.7 cm (3.4 x 17.6 x 19.96 in)
Weight
4U/24 Bay: 27 kg / 60 lbs (w/o drives) 3U/16 Bay: 25 kg / 56 lbs (w/o drives) 2U/12 Bay: 22 kg / 49 lbs (w/o drives)
10
Safety and Environmental
Safety and Environmental

Safety Standards
BSMI Class A CB CE C-Tick FCC Class A GOST-R IRAM KCC NOM TUV UL/cUL VCCI Class A
Environmental Standards
RoHS GreenPC WEEE
11
Warranty and Support

Warranty
Three year complete system limited warranty with advanced parts replacement Optional extended warranty Optional onsite parts replacement program
Support
24 hour, 7 days a week e-mail and phone support (English only) 24 hour, 7 days a week access to PROMISE support site Firmware and compatibility lists
12
Chapter 2: Installation
This chapter covers the following topics: Unpacking the VTrak (below) Mounting VTrak in a Rack (page 14) Installing Physical Drives (page 19) Making Management and Data Connections (page 23) Setting Up Serial Cable Connections (page 31)
Unpacking the VTrak

The VTrak box contains the following items: VTrak Unit Left and right mounting rails RJ11-to-DB9 serial data cable Screws for physical drives (VTraks that ship without drives) 1.5m (4.9 ft) Power cords (2) CD with SNMP files, MPIO files, RAID console.inf file, Product Manual, and Quick Start Guide
Warning The electronic components within the VTrak disk array are sensitive to damage from Electro-Static Discharge (ESD). Observe appropriate precautions at all times when handling the VTrak or its subassemblies. Important Existing VTrak J330s, J630s, or J830s JBOD expansion units require two critical updates to support the VTrak E330f, E630f, and E830f RAID subsystems: If you have SATA drives, replace the existing AAMUX adapters with the new SAS-to-SATA adapters, available from PROMISE Technology at http://www.promise.com Download the latest firmware image file available from PROMISE support: http://www.promise.com/support/ and flash your existing VTrak JBOD units. Follow the instructions in Chapter 6 of the VTrak E-Class E610f, E610s, E310f, E310s Product Manual.
13
Mounting VTrak in a Rack

Cautions At least two persons are required to safely lift, place, and attach the VTrak unit into a rack system. Do not lift or move the VTrak unit by the handles, power supplies or the controller units. Hold the subsystem itself. Do not install the VTrak unit into a rack without rails to support the subsystem. Do not lay one VTrak enclosure on top of another. Mount each enclosure supported by its own set of rails. Performance can be adversely affected if the VTrak unit is improperly installed. Only a qualified technician who is familiar with the installation procedure should mount and install the VTrak unit. Be sure all switches are OFF before installing the VTrak unit or exchanging components. Mount the rails to the rack using the appropriate screws and flange nuts, fully tightened, at each end of the rail. Do not load the rails unless they are installed with screws as instructed. The rails that ship with the PROMISE VTrak unit are designed to safely support that PROMISE VTrak unit when properly installed. Additional loading on the rails is at the customers risk. PROMISE Technology, Inc. cannot guarantee that the mounting rails will support your PROMISE VTrak unit unless you install them as instructed. Note To lighten the VTrak enclosure, remove the power supplies. If your VTrak shipped with physical drives installed, remove all of the drive carriers, also. Replace the power supplies and drive carriers after the VTrak unit is mounted in your rack.
14
Mounting VTrak E830f/s and E630f/s in a Rack

The VTrak subsystem installs into your rack using the supplied mounting rails. Figure 1. VTrak E630f/s mounted in a rack with the supplied rails Vertical Rack Post Attaching screw & flange nut one each side VTrak E630f/s
Handles mount outside the rack post
Mounting rails (included) mount outside the rack post
To install the VTrak subsystem into a rack with the supplied mounting rails: 1. 2. Check the fit of the mounting rails in your rack system. See page 16, Figure 2. Adjust the length of the mounting rails as needed. The rear rail slides inside the front rail. The rail halves are riveted together and use no adjustment screws. 3. Attach the mounting rail assemblies to the outside of the rack posts, using the attaching screws and flange nuts from your rack system. Be sure the front rail support is on the bottom facing inward. The alignment pins fit into the rack holes above and below the attaching screws. Use the attaching screws and flange nuts from your rack system. Tighten the screws and flange nuts according to your rack system instructions. 4. 5. Place the VTrak subsystem onto the rails. Secure the VTrak subsystem to the rack. Use the attaching screws and flange nuts from your rack system, one set each side. Tighten the screws and flange nuts according to your rack system instructions.
15
Figure 2. VTrak E830f/s and E630f/s rack mount assembly Rack front post Alignment pins two on each flange Front rail Rear rail Rack rear post
Support for subsystem
Inside of post
Rail attaching screws (not included)
Inside of post
Note that only the front rail has a support for the subsystem.
Mounting VTrak E330f/s in a Rack

The VTrak subsystem installs to the rack using the supplied mounting rails. Figure 3. VTrak E330f/s mounted in a rack with the supplied rails Vertical Rack Post Attaching screw & flange nut one each side VTrak E330f/s
Handles mount outside the rack post
Mounting rails (included) mount outside the rack post
16
Attaching the Sliding Plates

To install the side plates onto VTrak subsystem: 1. 2. Slide the plates out of the mounting rails. Attach one plate to each side of the VTrak subsystem. Line-up the six holes in the plate with the corresponding holes in the subsystem. Attach each plate with six screws (included). See Figure 4. Figure 4. VTrak E330f/s sliding flange installation Rear (connector end) of the subsystem VTrak E330f/s
Sliding plate
Screws (6 each side)
Installing the Subsystem into the Rack

To install the VTrak subsystem into a rack with the supplied mounting rails: 1. 2. 3. 4. 5. 6. Check the fit of the mounting rails in your rack system. See page 18, Figure 5. Slide one of the rails over the plate on one side of the enclosure. The rail is designed to slide freely over the plate. Attach a flange to each end of the rail, with the rail on the opposite side of the flange from the two-hole bracket. Install the rail adjustment screws (included) through the flange into the rail. There are four screws for each flange. See page 19, Place the subsystem with mounting rails into your rack system. Attach the mounting rail assemblies to the outside of the rack posts, using the attaching screws from your rack system.
17
7. 8. 9.
Square the rail assemblies in the rack. Tighten the adjustment screws and the attaching screws. Secure the VTrak subsystem to the rack through each handle, using the attaching screws from your rack system.
Figure 5. VTrak E330f/s rack mount assembly Rack front post Rail adjustment screw Mounting Rail Sliding plate Rack back post
Rail attaching screw (not included) Inside of post
Rail attaching screw (not included) Inside of post
18
Installing Physical Drives

The VTrak Ex30 RAID subsystems and JBOD expansion units support: SAS and SATA physical drives 2.5-inch and 3.5-inch physical drives Hard disk drives (HDD) and solid state drives (SSD)
For a list of supported physical drives, download the latest compatibility list from PROMISE support: http://www.promise.com/support/.
Number of Drives Required

The table below shows the number of drives required for each RAID level Level RAID 0 RAID 1 RAID 1E RAID 5 Number of Drives 1 or more 2 only 2 or more 3 to 32* Level RAID 6 RAID 10 RAID 50 RAID 60 Number of Drives 4 to 32* 4 or more** 6 or more 8 or more
* E330f/s: Drive counts above 12 require a JBOD expansion unit. ** Must be an even number of drives.
Drive Slot Numbering

You can install any suitable disk drive into any slot in the enclosure. The diagram below shows how VTraks drive slots are numbered. Slot numbering is reflected in the WebPAM PROe and CLU user interfaces. Figure 6. VTrak E830f/s drive slot numbering
1 5 9 13 17 21
2 6 10 14 18 22
3 7 11 15 19 23
4 8 12 16 20 24
19
Figure 7. VTrak E630f/s drive slot numbering
1 5 9 13
2 6 10 14
3 7 11 15
4 8 12 16
Figure 8. VTrak E330f/s drive slot numbering
1 5 9
2 6 10
3 7 11
4 8 12
Install all of the drive carriers into the VTrak enclosure to ensure proper airflow, even if you do not populate all the carriers with physical drives.
Installing Your Drives

The VTrak drive carrier accommodates 2.5-inch and 3.5-inch drives, with or without a SAS-to-SATA adapter. Cautions Swing open the drive carrier handle before you insert the drive carrier into the enclosure. To avoid hand contact with an electrical hazard, remove only one drive carrier a time. Important SATA drives require a SAS-to-SATA adapter, available from PROMISE Technology at http://www.promise.com SAS drives do not require adapters. 1. 2. Press the drive carrier release button. The handle springs open. Grasp the handle and gently pull the empty drive carrier out of the enclosure.
20
Figure 9. Drive carrier front view
Handle 3. 4. 5.
Release button
If you are installing SATA drives, attach a SAS-to-SATA adapter onto the power and data connectors of each drive. Carefully lay the drive into the carrier with the power and data connectors facing away from the carrier handle. Position the drive in the carrier so the mounting holes line up. 2.5-inch drive mounting screws go through the bottom of the carrier. SAS-to-SATA adapter mounting screws go through the bottom of the carrier. 3.5-inch drive mounting screws go through the sides of the carrier.
Figure 10.Drive carrier bottom view SAS-to-SATA adapter mounting holes (total of 2) 2.5-inch SATA drive mounting holes (total of 4)
2.5-inch SAS drive mounting holes (total of 4) drive carrier handle
21
Figure 11. Drive carrier side view 3.5-inch SATA drive mounting holes (two each side)
3.5-inch SAS drive mounting holes (two each side) drive carrier handle 6. Insert the screws through the proper holes in the carrier and into the drive or adapter. 7. Use the screws supplied with the VTrak or the SAS-to-SATA adapter. Install four screws per drive. Install two screws per adapter. Snug each screw. Be careful not to over tighten.
With the drive carrier handle in open position, gently slide the drive carrier into the enclosure. Important Press the release button to push the drive carrier into position. Do not push the handle. See page 21, Figure 9. Proper drive installation ensures adequate grounding and minimizes vibration. Always attach the drive to the carrier with four screws.
22
Making Management and Data Connections

Examples of VTrak configurations include: Fibre Channel SAN (below) Fibre Channel DAS (page 25) Fibre Channel JBOD Expansion (page 27) Fibre Channel SAN No Single Point of Failure (page 28)
Fibre Channel SAN

Important For a list of supported FC HBAs, Switches and SFPs, download the latest compatibility list from PROMISE support: http://www.promise.com/support/. A Fibre Channel storage area network (SAN) requires: A Fibre Channel switch A Fibre Channel HBA card in each Host PC or Server A network switch A network interface card (NIC) in each Host PC or Server
Figure 12.FC controller data and management ports Management port SAS expansion port (to JBOD)
Fibre Channel data ports
23
Data Path
To establish the data path: 1. 2. 3. Connect an FC data port on the left controller to your FC switch. See Figure 13. Connect an FC data port on the right controller to your FC switch. Connect your FC switch to the FC HBA cards in both Host PCs or Servers. For multipathing (MPIO) applications, see the VTrak E-Class Product Manual on the CD.
Management Path
To establish the management path: 1. 2. Connect the Management port on each controller to your network switch. See Figure 13. Connect each Host PCs or Servers NIC to your network switch.
Figure 13.FC SAN data and management connections Network Switch
FC Switch
VTrak
Host PC or Server
Host PC or Server
Also see the FC controller close-up, on page 23, Figure 12.
24
Fibre Channel DAS

Important For a list of supported FC HBAs, Switches and SFPs, download the latest compatibility list from PROMISE support: http://www.promise.com/support/. Fibre Channel direct attached storage (DAS) requires: Two FC HBA cards in the Host PC or Server A network switch A network interface card (NIC) in the Host PC or Server
Data Path
To establish the data path: 1. Connect an FC data port on the left controller of the RAID subsystem to one of the FC HBA cards in your Host PC or Server. See page 26, Figure 14. 2. Connect an FC data port on the right controller of the RAID subsystem to the other FC HBA card in your Host PC or Server. For multipathing (MPIO) applications, see the VTrak E-Class Product Manual on the CD.
Management Path
To establish the management path: 1. 2. Connect the Management ports of both controllers to your network switch. See page 26, Figure 14. Connect the Host PCs or Servers NIC to your network switch.
25
Figure 14.FC DAS data and management connections Network Switch
VTrak
Host PC or Server Also see the FC controller close-up, on page 23, Figure 12.
26
Fibre Channel JBOD Expansion

To add JBOD units: 1. Connect the SAS expansion port on the left controller of the RAID subsystem to the SAS data IN port on the left I/O module of the first JBOD unit. See Figure 15. 2. Connect the SAS expansion port on the right controller of the RAID subsystem to the SAS data IN port on the right I/O module of the first JBOD unit. Connect the SAS data OUT port on left I/O module of the first JBOD unit to the SAS data IN port on the left I/O module of the second JBOD unit. Connect the SAS data OUT port on right I/O module of the first JBOD unit to the SAS data IN port on the right I/O module of the second JBOD unit. Connect the remaining JBOD units in the same manner. Keep your data paths organized to ensure redundancy. JBOD expansion supports up to seven JBOD units. Figure 15.FC JBOD expansion connections SAS expansion port E330f
SAS IN SAS OUT SAS IN SAS OUT
115200 8 N 1 115200 8 N 1
3. 4. 5.
SAS data OUT port
J630s
SAS IN SAS OUT SAS IN SAS OUT
115200 8 N 1 115200 8 N 1
SAS data IN port
J630s Also see the FC controller close-up, on page 23, Figure 12.
27
Fibre Channel SAN No Single Point of Failure

Important For a list of supported FC HBAs, Switches and SFPs, download the latest compatibility list from PROMISE support: http://www.promise.com/support/. An FC SAN with no single point of failure requires: Two FC switches An FC HBA card in each Host PC or Server A network switch A network interface card (NIC) in each Host PC or Server
Data Path
To establish the data path: 1. Connect an FC data port on the left controller to the FC HBA card in one of the Host PCs or Servers. See page 29, Figure 16. 2. 3. 4. Connect another FC data port on the left controller to the FC HBA card in the other Host PC or Server. Connect an FC data port on the right controller to the FC HBA card in one of the Host PCs or Servers. Connect another FC data port on the right controller to the FC HBA card in the other Host PC or Server. Keep your data paths organized to ensure redundancy. For multipathing (MPIO) applications, see the VTrak E-Class Product Manual on the CD.
JBOD Expansion
To add JBOD units: 1. Connect the SAS expansion port on the left controller of the RAID subsystem to the SAS data IN port on left I/O module of the first JBOD unit. See page 29, Figure 16. 2. 3. 4. Connect the SAS expansion port on the right controller RAID subsystem to the SAS data IN port on right I/O module of the first JBOD unit. Connect the SAS data OUT port on left I/O module of the first JBOD unit to the SAS data IN port on left I/O module of the second JBOD unit. Connect the SAS data OUT port on right I/O module of the first JBOD unit to the SAS data IN port on right I/O module of the second JBOD unit.
28
5.
Connect the remaining JBOD units in the same manner. Keep your data paths organized to ensure redundancy. JBOD expansion supports up to seven JBOD units.
Figure 16.FC no single point of failure data connections Host PCs or Servers
Fibre Channel Switches
E330f
SAS IN
SAS OUT
SAS IN
SAS OUT
115200 8 N 1
115200 8 N 1
J630s
SAS IN
SAS OUT
SAS IN
SAS OUT
115200 8 N 1
115200 8 N 1
J630s
SAS IN
SAS OUT
SAS IN
SAS OUT
115200 8 N 1
115200 8 N 1
J630s
Also see the FC controller close-up, on page 23, Figure 12.
29
Management Path
To establish the management path: 1. 2. Connect the Management ports on both controllers to your network switch. Connect the NICs in both Host PCs or Servers to your network switch.
Figure 17.FC no single point of failure management connections Host PCs or Servers
Network Switch
RAID subsystem Also see the FC controller close-up, on page 23, Figure 12.
30
Setting Up Serial Cable Connections
Setting Up Serial Cable Connections

Serial communication enables the Command Line Interface (CLI) and Command Line Utility (CLU) on your PC to monitor to control the VTrak. The VTrak package includes one RJ11-to-DB9 serial data cable for each controller. All VTrak models have the same serial connection. Figure 18. UPS and Serial connectors are located on each controller UPS connector Serial connector
To set up a serial cable connection: 1. 2. Attach the RJ11 end of the serial data cable to the RJ11 serial connector on one of the controllers. Attach the DB9 end of the serial data cable to a serial port on the Host PC or Server.
Optional UPS Serial Connection

If your deployment plan calls for one or more UPS units and management via serial communication, connect a UPS control cable to the UPS connector on the VTrak controller. See Figure 18. The UPS control cables are available from PROMISE Technology at http://www.promise.com When your subsystem is running, see Making UPS Settings on page 81 or page 215 to complete the UPS management setup.
31
32
Chapter 3: Setup
This chapter covers the following topics: Connecting the Power (below) Setting up the Management Ports (page 36) Logging into WebPAM PROe (page 42) Creating Disk Arrays and Logical Drives (page 44) Logging out of WebPAM PROe (page 49)
Connecting the Power

Plug the power cords and turn on the switches on both power supplies. Important If you have a SAN, DAS, or Cascade with JBOD Expansion, always power on the JBOD expansion units first. When the power is switched on, the LEDs on the right handle light up. Figure 1. Front panel LED display
Power FRU Status Logical Drive Status Controller 1 Activity Controller 2 Activity Controller Heartbeat
When boot-up is finished and the VTrak is functioning normally: Power, FRU, and Logical Drive LEDs display steady green.
Each controller activity LED flashes green when there is activity on that controller. The controller heartbeat LED blinks green once per second for five seconds, goes dark for ten seconds, then blinks green once per second for five seconds again. Steady means the LED is on. Blinking means a regular on/off pattern. Flashing means an intermittent and irregular on/off pattern. See the table below. Enclosure Front LEDs State Dark Steady green Blinking green Flashing green Amber Red Power No power Normal FRU No power Normal Problem* Failure* Logical Drive Normal Critical Offline Controller Activity No Activity Activity Controller Heartbeat Normal**
* Check the LEDs on the back of the VTrak enclosure. ** Blinks blinks green once per second for five seconds, goes dark for ten seconds, then blinks green once per second for five seconds again.
34
Chapter 3: Setup
Drive Status Indicators

The VTrak spins up the disk drives sequentially to equalize power draw during start-up. After a few moments: The Power/Activity LED displays blue when a physical drive is present. The Drive Status LED displays green when the physical drive is configured as a member of a disk array or as a spare. When the physical drive is unconfigured, the LED is dark. Steady means the LED is on. Blinking means a regular on/off pattern. Flashing means intermittent and irregular on/off pattern. See the table on the next page. Figure 2. Drive carrier LEDs Drive Status
Power/Activity Drive Carrier LEDs State Dark Steady Blue Flashing Blue Steady green Blinking green Amber Red Power/Activity No drive in carrier Drive is present Activity on drive Drive Status Drive is unconfigured Drive is configured Locator feature Drive is rebuilding Drive error or failure
* Configured means the physical drive either belongs to an array or it is assigned as a spare drive.
35
Setting up the Management Ports

Setting up the Management Ports consists of the following actions: Setting up the Serial Connection (below) Choosing DHCP or a Static IP Address (page 36) VTrak Default IP Addresses (page 37) Setting up VTrak with the CLI (page 37) Setting up VTrak with the CLU (page 39)
Setting up the Serial Connection

VTrak has a Command Line Interface (CLI) to manage all of its functions, including customization. A subset of the CLI is the Command Line Utility (CLU), a user-level interface that manages your VTrak via your PCs terminal emulation program, such as Microsoft HyperTerminal. This procedure uses the serial cable connection you made. See Setting Up Serial Cable Connections on page 31. 1. Change your terminal emulation program settings to match the following specifications: 2. 3. 4. 5. Bits per second: 115200 Data bits: 8 Parity: None Stop bits: 1 Flow control: none
Start your PCs terminal VT100 or ANSI emulation program. Press Enter once to launch the CLI. At the Login prompt, type administrator and press Enter. At the Password prompt, type password and press Enter. At this point, you are in the CLI. You can continue using the CLI to make network settings or you can switch to the CLU. Go to: Setting up VTrak with the CLI (page 37) Setting up VTrak with the CLU (page 39)
Choosing DHCP or a Static IP Address

When you setup your VTrak, you have the option of: Enabling DHCP and letting your DHCP server assign the IP address to the VTraks virtual management port. Specifying a static IP address for the VTraks virtual management port.
36
Chapter 3: Setup
If you choose to enable DHCP, have your Network Administrator dedicate an IP address for the VTrak, linked to the VTraks MAC address. This action prevents the DHCP server from assigning a new IP address when the VTrak restarts, with the result that users can no longer log in. To access the MAC address for VTraks virtual management port: In the CLI, type net -v and press Enter. In the CLU Main Menu, highlight Network Management and press Enter. Then highlight Virtual and press Enter.
VTrak Default IP Addresses

VTrak uses virtual and physical IP addresses. This arrangement enables you to access a VTrak with two RAID controllers over your network using a single IP address.
Virtual Management Port

The default virtual management port IP address is set to 10.0.0.1. The virtual management port IP address belongs to the VTrak subsystem, not to the RAID controller. Use the virtual management port IP address to log into the VTrak over your network. See Logging into WebPAM PROe on page 42.
Physical Management Ports

The default physical management port IP addresses are set to: Controller 1 10.0.0.2 Controller 2 10.0.0.3
The physical management port IP address belongs to the RAID controller, not to the VTrak subsystem. Use the physical management port IP address only when a controller is in maintenance mode.
Setting up VTrak with the CLI

1. Type the following string to set the system date and time, then press Enter. administrator@cli> date -a mod -d 2009/06/25 -t 14:50:05 In the above example, the date and time are included as examples only. Use yyyyy/mm/dd for the date and a 24-hour clock for the time. 2. Type the following string to set the Virtual Management Port IP address and other settings, then press Enter. administrator@cli> net -a mod -t mgmt -s "primaryip=192.168.10.85, primaryipmask=255.255.255.0, gateway=192.168.10.1"
37
In the above example, the IP addresses and subnet mask are included as examples only. If you prefer to let your DHCP server assign the Virtual Management Port IP address, type the following string, then press Enter. administrator@cli> net -a mod -t mgmt -s "dhcp=enable" Note that the IP address described above belongs to the VTrak subsystem, not to the RAID controller. Use this IP address to log into the VTrak over your network. 3. To verify the settings, type net and press Enter. administrator@cli> net =========================================== CId Port Type IP Mask Gateway Link =========================================== Virtual Mgmt 192.168.10.85 255.255.255.0 192.168.10.1 Up Each RAID controller has an IP addresses for access when the controller goes into maintenance mode. Maintenance mode is only for remedial action in the event of a problem with the controller. 4. Type the following string to set the Maintenance Mode IP address and other settings, then press Enter. You must set each controller separately. administrator@cli> net -a mod -t mgmt -m -c 1 -s "primaryip=192.168.10.101, primaryipmask=255.255.255.0, gateway=192.168.10.1" administrator@cli> net -a mod -t mgmt -m -c 2 -s "primaryip=192.168.10.102, primaryipmask=255.255.255.0, gateway=192.168.10.1" In the above example, the Maintenance Mode IP addresses and subnet mask are included as examples only. If you prefer to let your DHCP server assign the IP addresses, type the following strings, then press Enter. administrator@cli> net -a mod -t mgmt -m -c 1 -s "dhcp=enable" administrator@cli> net -a mod -t mgmt -m -c 2 -s "dhcp=enable" Note that the IP address described above belongs to the RAID controller, not to the VTrak subsystem. Use this IP address to log into the controller over your network. 5. To verify the maintenance mode settings, type net -m and press Enter.
38
Chapter 3: Setup
administrator@cli> net -m CtrlId: 1 Port: 1 Type: Management Ethernet IPType: IPv4 IP: 192.168.10.101 IPMask: 255.255.255.0 MAC: 00:01:55:AE:02:AE DNS: 0.0.0.0 Gateway: 192.168.10.1 DHCP: Disabled This completes the Management port setup. Go to Logging into WebPAM PROe on page 42. To see the full set of CLI commands, at the admin@cli> prompt, type help and press Enter.
Setting up VTrak with the CLU

1. At the administrator@cli> prompt, type menu and press Enter. The CLU main menu appears. Figure 3. CLU main menu
2.
Highlight Quick Setup and press Enter. The first Quick Setup screen enables you to make Date and Time settings.
39
Setting system date and time

1. 2. 3. 4. 5. Press the arrow keys to highlight System Date. Press the backspace key to erase the current date. Type the new date. Follow the same procedure to set the System Time. Press Ctrl-A to save these settings and move to the Management Port configuration screen.
Making Management Port settings Manual IP settings

To make Management Port settings manually: 1. 2. 3. 4. Press the arrow keys to highlight IP Address. Press the backspace key to erase the current IP address. Type the new Management Port IP address. Follow the same procedure to specify the Subnet Mask, Gateway IP Address and DNS Server IP Address. If you do not have a DNS server, skip the DNS Server IP address. 5. Press Ctrl-A to save your settings.
Making Management Port settings Automatic IP settings

To make Management Port settings automatically: 1. 2. 3. Press the arrow keys to highlight DHCP. Press the spacebar to toggle to Enable. Press Ctrl-A to save these settings.
Viewing IP address and settings

To view the current IP address and network settings when using DHCP: 1. 2. 3. 4. Press the arrow keys to highlight DHCP. Press the spacebar to toggle to Disable. The current Management Port settings are displayed. Press the spacebar to toggle DHCP back to Enable. Press Ctrl-A to save these settings and move to the RAID configuration screen.
Making Controller Maintenance Mode Settings

Each RAID controller has an IP addresses for access when the controller goes into maintenance mode. Maintenance mode is only for remedial action in the event of a problem with the controller.
40
Chapter 3: Setup
Making Automatic Settings

1. 2. 3. 4. 5. From the CLU Main Menu, highlight Network Management and press Enter. Highlight Maintenance Mode Network Configuration and press Enter. Highlight the controller you want and press Enter. Highlight DHCP and press the spacebar to toggle to Enabled. Press Ctrl-A to save your settings.
Making Manual Settings

1. 2. 3. 4. 5. From the CLU Main Menu, highlight Network Management and press Enter. Highlight Maintenance Mode Network Configuration and press Enter. Highlight the controller you want and press Enter. Highlight DHCP and press the spacebar to toggle to Disabled. Highlight each of the following and press the backspace key to erase the current value, then type the new value. 6. IP address Subnet Mask Default Gateway IP Address DNS Server IP Address
Press Ctrl-A to save your settings.
Exiting the CLU

1. 2. Highlight Skip the Step and Finish and press Enter. Highlight Return to CLI and press Enter.
This completes the Management Port setup. Go to Logging into WebPAM PROe on page 42.
41
Logging into WebPAM PROe

1. 2. Launch your browser. In the browser address field, type in the virtual IP address of the VTrak subsystem. Use the virtual IP address you set in the CLI (page 37) or CLU (page 39). Note that the IP address shown below is only an example.
Regular Connection
WebPAM PROe uses an HTTP connection. . . . . . . . . . . . . . . .http:// Enter the IP address of the VTrak . . . . . . . . . . . . . . . 192.168.10.85 http://192.168.10.85
Together, your entry looks like this:
Secure Connection
WebPAM PROe uses a secure HTTP connection . . . . . . . . . .https:// Enter the IP address of the VTrak . . . . . . . . . . . . . . . 192.168.10.85 https://192.168.10.85 Note Whether you choose a regular or a secure connection, your login to WebPAM PROe and your user password are always secure. 3. When the log-in screen appears: 4. Type administrator in the User Name field. Type password in the Password field. Click the Login button.
The User Name and Password are case sensitive. Optional. Choose a display language from the dropdown menu. WebPAM PROe displays in English, German, French, Italian, Spanish, Russian, Japanese, Traditional Chinese, Simplified Chinese, and Korean. 5. Click the Login button.
42
Chapter 3: Setup
Figure 4. WebPAM PROe log-in screen
Important PROMISE recommends that you change the Administrators default password immediately after setup is completed. See Changing User Passwords on page 87 or page 219. Note Make a Bookmark (Firefox) or set a Favorite (Internet Explorer) of the Login Screen so you can access it easily next time. After log-in, the WebPAM PROe opens with the Dashboard tab. See page 44, Figure 5.
43
Figure 5. WebPAM PROe Dashboard tab
Creating Disk Arrays and Logical Drives

On a newly activated RAID system, there are no disk arrays or logical drives. The term disk array includes arrays composed of solid state drives. To create your disk arrays and logical drives: 1. Click the Storage tab, then click the Wizard option. Or, click Disk Array under System Status. The Wizard screen appears with three creation alternatives: 2. Automatic See page 45. Express See page 46. Advanced See page 47.
Click one of these buttons to continue.
44
Chapter 3: Setup
Figure 6. The configuration wizard
Automatic
When you choose the Automatic option, the following parameters appear on the screen: Disk Arrays The number of logical drives, number of physical drives, ID of each physical drive, configurable capacity, and the media type (hard disk drives or solid state drives). Logical Drives The ID numbers of the logical drives, their RAID levels, capacity, sector size, and stripe size. Spare Drives The ID numbers of the logical drives, type (global or dedicated) revertible option (enabled or disabled) and media type. A hot spare drive is created for all RAID levels except RAID 0, when five or more unconfigured physical drives are available
If you do NOT accept these parameters, use the Express (below) or Advanced (page 47) option to create your disk array. If you accept these parameters, click the Submit button, and then click the Finish button. The new disk array appears in the Disk Array List on the Storage tab, Disk Array option.
45
Express
When you choose the Express option, a set of characteristics and options appears on the screen. 1. Check the boxes to choose any one or a combination of: Redundancy The array remains available if a physical drive fails Capacity The greatest possible amount of data capacity Performance The highest possible read/write speed Spare Drive A hot spare drive is created when you choose Redundancy, Spare Drive, and five or more unconfigured physical drives are available Mixing SATA/SAS Drive Check this box if you want to use both SATA and SAS drives in the same disk array If the box is unchecked, and you have both SATA and SAS drives, different arrays are created for each type of drive. 2. In the Number of Logical Drives field, enter the number of logical drives you want to make from this disk array. VTrak supports up to 32 logical drives per disk array. 3. From the Application Type menu, choose an application that best describes your intended use for this disk array: 4. 5. File Server Video Stream Transaction Data Transaction Log Other
Click the Next button to continue. The Summary screen appears with information on disk arrays, logical drives, and spare drives you are about to create. If you accept these parameters, proceed to the next step. If you do NOT accept these parameters, review and modify your selections in the previous steps.
6.
When you are done, click the Submit button, and then click the Finish button. The new disk array appears in the Disk Array List on the Storage tab, Disk Array option.
46
Chapter 3: Setup
Advanced
Note For an explanation of the parameters under the Advanced option, see Chapter 7: Technology Background on page 259. When you choose the Advanced option, the Create Disk Array screen appears. Step 1 Disk Array Creation 1. Enter your information and choose your options. 2. Enter a disk array alias in the field provided. Check the box to enable Media Patrol Check the box to enable Predictive Data Migration (PDM) Check the box to enable Power Management Choose a media type Hard disk drive (HDD) or solid state drive (SSD)
Mouse-over the enclosure graphic to view information about physical drives. Look for drives with a green LED dark, a blue LED lit, and no crosshatching over the carrier.
3. 4.
Click a physical drive to select it for your array. The physical drives ID number is added to the Selected list. Click the Next button to continue. The Create Logical Drive screen appears.
Step 2 Logical Drive Creation 1. Enter your information and choose your options. Enter a logical drive alias in the field provided. Choose a RAID level from the dropdown menu. The choice of RAID levels depends on the number of physical drives in your array. Note the Max: capacity value. Then enter a capacity value the field provided and choose a unit of measure from the dropdown menu. Choose a stripe size from the dropdown menu. The choices are 64 KB, 128 KB, 256 KB, 512 KB, and 1 MB. Choose a sector size from the dropdown menu. The choices are 512 B, 1 KB, 2 KB, and 4 KB. Choose the Read Cache Policy from the dropdown menu The choices are Read Cache, Read Ahead (cache), and None. Choose the Write Cache Policy from the dropdown menu
47
The choices are WriteThru (write through) and WriteBack. Write back requires a Read Cache or Read Ahead Read Cache Policy. 2. 3. Click the Add button to continue. The logical drive you just created appears in the New Logical Drives list. Click the Next button to continue. The Create Spare Drive screen appears. Step 3 Spare Drive Creation Creating a spare drive is optional but highly recommended. 1. Enter your information and choose your options. Check the Revertible box if you want this spare drive to be revertible. For more information see the VTrak E-Class Product Manual. Choose the option for the type spare drive you want. Global Replaces a failed drive in any disk array. Dedicated Replaces the failed drive only in the assigned disk array. 2. 3. 4. Mouse-over the enclosure graphic to view information about physical drives. Click a physical drive to select it for your spare drive. The physical drives ID number is added to the Selected list. Click the Next button to continue. The Summary screen appears. Step 4 Summary The Summary screen lists the disk arrays, logical drives, and spare drives that you specified. If you accept these parameters, click the Submit button. If you do NOT accept these parameters, review and modify your selections in the previous steps.
Enabling LUN Mapping and Masking

These features are optional for each logical drive. The Enable LUN Mapping dialog box appears after you create a logical drive. To enable LUN Mapping: 1. 2. 3. Click the OK button in the Enable LUN Mapping dialog box. The LUN Mapping & Masking screen appears. Check the Enable LUN Masking box to enable LUN Masking. Click the LUN Mapping button to continue. The initiator list screen displays.
48
Chapter 3: Setup
4.
Choose the initiators you want to use from the dropdown menu and click the Next button. The screen displays a list of initiators and a list of logical drives. Click and drag a logical drive from the logical drives list to the initiators list. Click the Next button when you are done. The screen displays a list of initiator IDs and corresponding LUN maps that you specified.
5. 6.
7.
Click the Submit button to create the LUN map. The screen displays a list of initiator IDs and corresponding LUN maps. You can also set LUN mapping and masking at a later time. Click the AdminTools tab, then click the LUN Mapping & Masking option.
Logging out of WebPAM PROe

There are two ways to log out of WebPAM PROe: Close your browser window Click Logout on the WebPAM PROe banner
Figure 7. Clicking Logout on the WebPAM PROe banner
Clicking Logout brings you back to the Login Screen. See page 43. After logging out, you must enter your user name and password in order to log in again.
Using WebPAM PROe over the Internet

The above instructions cover connections between VTrak and your company network. It is also possible to connect to a VTrak from the Internet. Your MIS Administrator can tell you how to access your network from outside the firewall. Once you are logged onto the network, you can access the VTrak using its IP address.
49
50
Chapter 4: Management with WebPAM PROe

This chapter contains the following topics: Logging into WebPAM PROe (below) Choosing the Display Language (page 53) Perusing the Interface (page 55) Logging out of WebPAM PROe (page 57) Viewing the Storage Network (page 58) Managing Subsystems (page 59) Managing RAID Controllers (page 69) Managing Enclosures (page 76) Managing UPS Units (page 80) Managing Users (page 83) Managing Background Activities (page 90) Managing Storage Services (page 100) Monitoring Performance (page 111) Managing Physical Drives (page 114) Managing Disk Arrays (page 121) Managing Logical Drives (page 132) Managing Spare Drives (page 141) Managing LUNs and Initiators (page 146) Managing Fibre Channel Connections (page 149) Managing SAS Connections (page 153)
Logging into WebPAM PROe

1. 2. Launch your browser. In the browser address field, type in the virtual IP address of the VTrak subsystem. Use the virtual IP address you set in the CLI (page 32) or CLU (page 34). Note that the IP address shown below is only an example.
Regular Connection
WebPAM PROe uses an HTTP connection. . . . . . . . . . . . . . . .http:// Enter the IP address of the VTrak . . . . . . . . . . . . . . . 192.168.10.85 http://192.168.10.85
51
Secure Connection
WebPAM PROe uses a secure HTTP connection . . . . . . . . . .https:// Enter the IP address of the VTrak . . . . . . . . . . . . . . . 192.168.10.85 https://192.168.10.85 Note Whether you choose a regular or a secure connection, your login to WebPAM PROe and your user password are always secure. 3. When the login screen appears: 4. Type administrator in the User Name field. Type password in the Password field. Click the Login button.
The User Name and Password are case sensitive. Optional. Choose a display language from the dropdown menu. WebPAM PROe displays in English, German, French, Italian, Spanish, Russian, Japanese, Traditional Chinese, Simplified Chinese, and Korean. 5. Click the Login button.
52
Figure 1. WebPAM PROe login screen
After login, the WebPAM PROe opening screen appears.
Choosing the Display Language

WebPAM PROe displays in multiple languages. You choose the display language when you log in. If you are already logged in and you want to change the display language: 1. Click Logout at the top right corner of the screen.
The Login screen appears.
53
2.
Click the Language dropdown menu and highlight the language you prefer.
3. 4.
Reenter your user name and password. Click the Login button. WebPAM PROe opens in the language you chose.
54
Perusing the Interface

The WebPAM PROe interface consists of a header and four tabs, each with specific functions. Header Top left corner of the window: Name of logged-in user IP address Virtual IP address of the RAID subsystem
Top right corner of the window Save Service Report Gathers information and saves a detailed report to your Host PC Help Accesses the Help Welcome screen Contact Us Technical support contact information About Information about WebPAM PROe
Discovery tab Displays other RAID systems on your network Enables direct login to other RAID systems
Dashboard tab RAID subsystem System status Event information System overview
Device tab Enclosure front and back views Topology Enclosure component list and settings Physical drive management UPS (unlimited power supply) management
Storage tab Wizard Automatic, Express, or Advanced configuration Disk array management Logical drive management
55
AdminTool tab Subsystem settings, clearing statistics, NTP, and controller lock User management Software services Runtime and NVRAM event logs Background activity, settings and schedules Firmware updates Image version Performance monitor PSU wattage monitor Restore factory default settings Initiator management LUN masking and mapping Import/Export user database and configuration script
56
Logging out of WebPAM PROe

There are two ways to log out of WebPAM PROe: Close your browser window Click Logout on the WebPAM PROe banner
Figure 2. Clicking Logout on the WebPAM PROe banner
Clicking Logout brings you back to the Login Screen. See page 53. After logging out, you must enter your user name and password in order to log in again.
57
Viewing the Storage Network

To view the other subsystems on your Storage Network, click the Discovery tab at the left edge of the WebPAM PROe window.
Logging onto a Subsystem

To log onto a subsystem in the list, double-click the subsystem. Caution The new subsystem displays in the same browser tab. Click your browsers back button to return to the original subsystem.
Filtering the Subsystem List

To filter the list, so it shows only specific subsystems, enter a characteristic into the Filter By field and press Enter.
Refreshing the List

To refresh the list, click the Refresh link.
58
Managing Subsystems
Subsystem management includes: Viewing Subsystem Information (below) Making Subsystem Settings (page 60) Locking or Unlocking the Subsystem (page 60) Restoring Factory Default Settings (page 61) Clearing Statistics (page 63) Saving a Service Report (page 63) Importing a Configuration Script (page 66) Exporting a Configuration Script (page 66) Restarting a Subsystem (page 67) Shutting Down the Subsystem (page 67) Restarting a Subsystem after a Shutdown (page 68)
Viewing Subsystem Information

To view subsystem information, click the AdminTool tab. The list of subsystems and host controllers displays. Subsystem information includes: Alias, if assigned Vendor Model WWN World Wide Number Serial number Part number Revision number Number of JBOD expansion units connected Maximum number of JBOD expansion units supported Number of controllers present Maximum number of controllers supported Redundancy status Redundancy type System date and time
59
Making Subsystem Settings

To make subsystem settings: 1. 2. 3. 4. Click the AdminTool tab. Click the Subsystem Information icon. Click the Settings button. Make changes as required: 5. Enter an alias or change the existing alias in the field provided. Choose a redundancy type from the dropdown menu. The choices are Active-Active and Active-Standby Check the box to enable cache mirroring. Click the Save button.
Locking or Unlocking the Subsystem

The lock prevents other sessions (including sessions with the same user) from making a configuration change to the controller until the lock expires or a forced unlock is done. When the user who locked the controller logs out, the lock is automatically released.
Setting the Lock

To set the lock: 1. 2. 3. 4. 5. Click the AdminTools tab. Click the Subsystem Information icon. Click the Lock/Unlock button. In the Lock Time field, type a lock time in minutes. 1440 minutes = 24 hours Click the Lock button.
Resetting the Lock

To reset the lock with a new time: 1. 2. 3. 4. 5. Click the AdminTools tab. Click the Subsystem Information icon. Click the Lock/Unlock button. In the Lock Time field, type a new lock time in minutes. 1440 minutes = 24 hours Click the Lock button.
Releasing the Lock

1. Click the AdminTools tab.
60
2. 3. 4.
Click the Subsystem Information icon. Click the Lock/Unlock button. Click the Unlock button.
Releasing a Lock set by another user

To release somebody elses lock: 1. 2. 3. 4. 5. Click the AdminTools tab. Click the Subsystem Information icon. Click the Lock/Unlock button. Check the Force Unlock box. Click the Unlock button.
Restoring Factory Default Settings

This feature restores settings to their default values. Caution Use this feature only when required and only on the settings that you must reset to default in order to set them correctly. To restore all settings to their default values: 1. 2. 3. Click the AdminTool tab. Click the Restore Factory Default icon. In the Restore factory default settings screen, check the boxes beside the settings you want to reset to default value:
61
Firmware Factory Default Settings Software Factory Default Settings Background activity settings Controller settings Enclosure settings FC port settings SAS port settings Management network settings Physical drive settings Subsystem settings BGA scheduler settings Service settings Webserver settings SNMP settings Telnet settings SSH settings Email settings Netsend settings CIM settings NTP settings User settings UPS settings LDAP settings Note Restart the Webserver and Email services for their new settings to take effect. 4. 5. Click the Submit button. In the Confirmation box, type the word confirm in the field provided and click the Confirm button. The progress of the update displays. Warning Do NOT power off the RAID subsystem during the update! Do NOT move to any other screen until the firmware update operation is completed!
When the update is completed a message tells you to reboot the subsystem. 6. Click the OK button.
Automatic Restart
If you did NOT check the NDIU box, the RAID subsystem and JBOD expansion units automatically restart. That action temporarily disrupts I/O operations and drops your WebPAM PROe connection.
62
To reestablish your WebPAM PROe connection: 1. 2. Wait no less than two minutes. Click Logout in the WebPAM PROe Header, then log in again. If you cannot log in, wait 30 seconds and try again.
Clearing Statistics
This function clears statistical data on the RAID controllers, Fibre Channel ports, SAS ports, physical drives, and logical drives. To clear subsystem statistics: 1. 2. 3. 4. 5. Click the AdminTool tab. Click the Subsystem Information icon. Click the Clear Statistics button. Type confirm in the field provided. Click the Confirm button.
Saving a Service Report

A Service Report is a detailed report covering the configuration and status of all components in your RAID system. A support technician or field engineer might request a service report for the purpose of diagnosis and troubleshooting. To save a system configuration file: 1. Click Save Service Report in the Header. Information for the report is gathered and compiled. This action takes up to a few minutes, depending on the size of your RAID system 2. 3. 4. Click the Save File option, then click the Save button. The report saves to your Host PC as a compressed HTML file. Double-click the downloaded file to decompress it. Double-click the report to open it in your default browser. The Service Report includes the following topics: About Report utility Battery Info Cache backup batteries BBM Info Bad Block Manager BGA Summary Status and settings BGA Schedules Scheduled activities Buzzer Info Controller Info
63
The Service Report includes the following topics, continued:
Debug Syslog Diagnostic information Disk Array Info ID, alias, and capacities only Disk Array Dump Info Diagnostic information Disk Array Verbose Info All disk array information Enclosure Info Error Table Info Read check, write check, and inconsistent blocks Event Info NVRAM List of NVRAM events Event Info Runtime List of Runtime events FC Node Info FC Device Info FC Initiator Info FC Port Info FC SFP Info FC Stats Info Flash Image Version Info iSCSI Info LDAP Info LogDrive Info Basic logical drive information LogDrive Dump Info Diagnostic information Logical Drive Verbose Info Full logical drive information Lunmap Info LUN map type, LUN masking status, and LUN entries Network Info Virtual port Network Maintenance Info Maintenance mode ports Phydriv Info Basic physical drive information Phydriv Verbose Info Full physical drive information PD SMART Info Physical drive ID, model, type, and SMART status PSU Wattage Info Enclosure power consumption, power supply input and output, and power on time SAS Enclosure Topology Info SAS expansion connections SAS Diagnostic Info Diagnostic information SWMGT Info Software management Service Setting CIM Service Setting Email Service Setting Netsend
The Service Report includes the following topics, continued:
64
Service Setting NTP Service Setting SLP Service Setting SNMP Service Setting SSH Service Setting Telnet Service Setting Webserver Sessions Info Spare Info Basic spare drive information Spare Dump Info Diagnostic information Spare Verbose Info Full spare drive information Statistic Info Subsystem info UPS Info User Info
65
Importing a Configuration Script

You can write a CLI configuration script to automatically configure your VTrak subsystem. The script must be a plain, non-encrypted text file. From there, you can import the script from the Host PC and perform the configuration automatically. Cautions Do NOT attempt to write or modify a configuration script until you receive guidance from Technical Support. See page 351. Importing a configuration script overwrites the current settings on your VTrak subsystem.
Or you can save the configuration from one VTrak RAID subsystem, export it, and then import it to automatically configure your other VTrak RAID subsystems.To import a configuration script: 1. 2. 3. 4. 5. 6. Click the AdminTool tab. Click the Import/Export icon. Click the Import option. Choose Configuration Script from the Type dropdown menu. Click the Browse button and navigate to the configuration script and click the OK button. Click the Next button. The system verifies that the file is a valid configuration script and displays any errors or warnings. 7. 8. Click the Submit button to continue. In the Confirmation box, type the word confirm in the field provided and click the Confirm button. The configuration script is imported and applied automatically.
Exporting a Configuration Script

You can save the configuration from one VTrak RAID subsystem, export it, and then import it to automatically configure your other VTrak RAID subsystems. To export a configuration script: 1. 2. 3. 4. Click the AdminTool tab. Click the Import/Export icon. Click the Export option. Choose Configuration Script from the Type dropdown menu.
66
5. 6.
Click the Submit button. In the Open dialog box, click the Save File option, then click the OK button. The file is saved to your PC as Configscript.txt. Caution Do NOT attempt to write or modify a configuration script until you receive guidance from Technical Support. See page 351.
Restarting a Subsystem
This function shuts down the subsystem and then restarts it. Important Do NOT turn off the power supply switches on the RAID subsystem or JBOD expansion units. To restart the subsystem: 1. 2. 3. 4. 5. 6. 7. 8. Click the AdminTool tab. Click the Subsystem Information icon. Click the Shutdown/Restart button. Click the Restart button. Type confirm in the field provided. Click the Confirm button. When the controller shuts down, your WebPAM PROe connection is lost. Wait no less than two minutes. In your browser, click Logout in the WebPAM PROe Header, then log in again. If you cannot log in immediately, wait 30 seconds and try again.
Shutting Down the Subsystem

This function shuts down the RAID subsystem without restarting it. To shutdown the subsystem: 1. 2. 3. 4. 5. Click the AdminTool tab. Click the Subsystem Information icon. Click the Shutdown/Restart button. Click the Shutdown button. Type confirm in the field provided.
67
6. 7. 8.
Click the Confirm button. When the controller shuts down, your WebPAM PROe connection is lost. Wait no less than two minutes. Manually turn OFF the switches on both power supplies. Important If your RAID subsystem manages JBOD expansion units, you must follow the proper startup procedure.
Restarting a Subsystem after a Shutdown

Important If your RAID subsystem manages JBOD expansion units, always power on the JBOD expansion units first. Then power on the RAID subsystem. To start the RAID subsystem: 1. 2. 3. Manually turn ON the power supply switches on the back of the subsystem. Wait no less than two minutes. Open your browser and log into WebPAM PROe. If you cannot log in immediately, wait 30 seconds and try again.
68
Managing RAID Controllers

RAID controller management includes: Viewing Controller Information (below) Making Controller Settings (page 70) Viewing Controller Statistics (page 71) Locating a Controller (page 72) Viewing the Flash Image Information (page 72) Updating Firmware on a RAID Subsystem (page 73) Viewing Battery Information (page 73) Reconditioning a Battery (page 74) Making Buzzer Settings (page 75) Silencing the Buzzer (page 75)
Viewing Controller Information

To view controller information: 1. 2. 3. Click the Device tab. Click the Component List icon. Mouse-over the controller you want and click the View button. Controller information includes: 4. Controller ID Readiness Status Power On Time Part Number Hardware Revision Cache Usage Percentage Boot Loader Version Firmware Version Software Version Alias If assigned * Operational Status SCSI Protocol Supported Serial Number WWN Worldwide Number Dirty Cache Usage Percentage Boot Loader Version Firmware Build Date Software Build Date
Click the Advanced Information tab.
69
Advanced controller information includes: Slot 1 Memory Type Slot 2 Memory Type LUN Affinity * Controller Role Flash Size NVRAM Size Coercion * SMART * Write Back Cache Flush Interval * Adaptive Writeback Cache * Slot 1 Memory Size Slot 2 Memory Size ALUA * Flash Type NVRAM Type Preferred Cache Line Size Coercion Method * SMART Polling Interval * Enclosure Polling Interval * Host Cache Flushing * Power Saving Idle Time * Power Saving Stopped Time *
Forced Read Ahead (cache) * Power Saving Standby Time * Cache Line Size
Items with an asterisk (*) are adjustable under Controller Settings.
Making Controller Settings

In a dual-controller RAID subsystem, settings made to one controller are applied to both controllers. To make controller settings: 1. 2. 3. 4. Click the Device tab. Click the Component List icon. Mouse-over the controller you want and click the Settings button. Make setting changes as required: Enter, change or delete the alias in the Alias field. LUN Affinity Check the box to enable or uncheck to disable. SMART Log Check the box to enable or uncheck to disable. SMART Polling Interval Enter a value into the field, 1 to 1440 minutes HDD Power Saving Choose time periods from the dropdown menus. After an HDD has been idle for the set period of time: Power Saving Idle Time - Parks the read/write heads. Power Saving Standby Time Lowers disk rotation speed.
70
Power Saving Stopped Time Spins down the disk (stops rotation).
Coercion Check the box to enable or uncheck to disable. Coercion Method Choose a method from the dropdown menu: GBTruncate 10GBTruncate GrpRounding TableRounding
5.
Write Back Cache Flush Interval Enter a value into the field, 1 to 12 seconds. Enclosure Polling Interval 15 to 255 seconds. Adaptive Writeback Cache Check the box to enable or uncheck to disable. See Adaptive Writeback Cache on page 290. Host Cache Flushing Check the box to enable or uncheck to disable. Forced Read Ahead (cache) Check the box to enable or uncheck to disable. See Forced Read-Ahead Cache on page 290.
Click the Save button. Notes Power Management must be enabled on the disk array for the HDD Power Saving settings to be effective. See Making Disk Array Settings on page 128. Power Management functions are limited to the features your HDDs actually support.
Viewing Controller Statistics

To view controller statistics: 1. 2. 3. 4. Click the Device tab. Click the Component List icon. Mouse-over the controller you want and click the View button. Click the Statistics tab.
71
Controller statistics include: Data Transferred Read Data Transferred Write Data Transferred Errors Non-Read/Write Errors Read Errors Write Errors IO Requests Non-Read/Write Requests Read IO Requests Write IO Requests Statistics Start date and time Statistics Collection date and time Note To clear controller statistics, see Clearing Statistics on page 63.
Locating a Controller
This feature causes the controller LEDs to blink for one minute to assist you in locating the controller on a RAID subsystem or JBOD expansion unit. To locate a controller: 1. 2. 3. Click the Device tab. Click the Component List icon. Mouse-over the controller you want and click the Locate button. The controller LEDs blink for one minute. Figure 3. FC RAID controller LEDs Dirty Cache LED Controller Status LED
Viewing the Flash Image Information

To view the flash image information for the RAID subsystem enclosure: 1. 2. 3. Click the AdminTool tab. Click the Image Version icon. Mouse-over the Enclosure you want to see and click the triangular button.
72
RAID subsystems have the following components in their flash image: Kernel Firmware Software Ramdisk SEP Firmware OEM Customization BIOS 6G Expander System Libraries Applications Mount Scripts PLX EEPROM Image
Running The version that is currently running on the subsystem or expansion unit. Flashed This version was updated but does not run until the subsystem restarts.
See Updating Firmware on a RAID Subsystem on page 73. JBOD expansion units have only one component in their flash image, SEP firmware. It only appears as running.
Updating Firmware on a RAID Subsystem

Use this function to flash (update) the firmware on the VTrak. See page 241 for the procedure.
Viewing Battery Information

Batteries maintain power to the controller cache in the event of a power failure, thus protecting any data that has not been written to a physical drive. To view battery information: 1. 2. 3. Click the Device tab. Click the Component List icon. Mouse-over the battery you want and click the View button. Battery information includes: Battery ID Operational status Fully charged, recondition means a reconditioning is in process Battery chemistry LiON, etc. Remaining capacity Battery capacity as a percentage Battery cell type Number of cells Estimated hold time Time in hours that the battery can power the cache
73
Temperature threshold discharge Maximum temperature allowed when the battery is discharging Temperature threshold charge Maximum temperature allowed when the battery is charging Battery temperature Actual battery temperature Cycle count Number of times the battery was reconditioned Voltage in millivolts Current in milliamps
Reconditioning a Battery
Batteries maintain power to the controller cache in the event of a power failure, thus protecting any data that has not been written to a physical drive. Reconditioning is the action of discharging and recharging a battery to preserve its capacity and performance. Reconditioning is a background activity and does not affect I/O performance. When the recondition is completed, the batterys cycle count increments by one. By default, each battery is reconditioned every two months. You can change the reconditioning schedule. Caution Disabling or deleting the battery recondition schedule is NOT recommended. To recondition a battery immediately: 1. 2. 3. Click the Device tab. Click the Component List icon. Mouse-over the battery you want and click the Recondition button.
Battery operations status changes to Recondition and the batterys remaining capacity and estimated hold time fall and rise reflecting the discharge and recharge cycles of the reconditioning. That behavior is normal.
Making Schedule Changes

To make changes the scheduled battery reconditioning: 1. 2. 3. 4. Click the AdminTool tab. Click the Background Activities icon. The list of Background Activities displays. Click the Scheduler button. Mouse-over Battery Reconditioning and click the Settings button.
74
5.
Make setting changes as required: Start Time Uncheck the Enable This Schedule box to disable this activity. Recurrence Pattern Start From End On
6.
Click the Save button to apply the new settings.
Making Buzzer Settings

To make buzzer settings: 1. 2. 3. 4. 5. Click the Device tab. Click the Component List icon. Mouse-over the Buzzer and click the Settings button. Check the Enable Buzzer box to enable the buzzer. Or uncheck the box to disable. Click the Save button.
Silencing the Buzzer

Caution This action disables the buzzer for all events.
To silence the buzzer: 1. 2. 3. 4. 5. Click the Device tab. Click the Component List icon. Mouse-over the Buzzer and click the Settings button. Uncheck the Enable Buzzer box. Click the Save button.
75
Managing Enclosures
Enclosure management includes the following functions: Viewing the Enclosures Summary (page 76) Making Enclosure Settings (page 77) Viewing FRU VPD Information (page 78) Viewing Power Supply Status (page 78) Viewing Fan Status (page 78) Viewing Temperature Sensor Status (page 79) Viewing Voltage Sensor Status (page 79)
Viewing Enclosure Topology

This feature displays the connection topology of the VTrak subsystem. Topology refers to the manner in which the data paths among the enclosures are connected. There are three methods: Individual Subsystem A single subsystem JBOD Expansion Managed through one subsystem or head unit RAID Subsystem Cascading Managed through one subsystem or head unit
For more information about connections, see Making Management and Data Connections on page 23. To view enclosure topology: 1. 2. Click the Device tab. Click the Topology icon. The topology or data connections of your system displays.
Viewing the Enclosures Summary

Enclosure Management includes information, status, settings and location. To access Enclosure Management: 1. 2. Click the Device tab. Click the Component List icon. The following information is shown: Enclosure ID number Status Enclosure Type Status Description (specific components in need of attention, if any)
76
Viewing Enclosure Information

To view enclosure information: 1. 2. 3. Click the Device tab. Click the Component List icon. Mouse-over the Enclosure and click the View button. Enclosure information includes: Enclosure ID Enclosure Type Enclosure Warning Temperature Threshold Enclosure Critical Temperature Threshold Controller Warning Temperature Threshold Controller Critical Temperature Threshold Max Number of Controllers Max Number of Physical Drive Slots Max Number of Fans Max Number of Blowers Max Number of Temperature Sensors Max Number of Power Supply Units Max Number of Batteries Max Number of Voltage Sensors
For information on Enclosure problems, see See Diagnosing an Enclosure Problem on page 308.
Making Enclosure Settings

To make Enclosure settings: 1. 2. 3. Click the Device tab. Click the Component List icon. Mouse-over the Enclosure and click the Settings button. Enclosure settings include: 4. Enclosure Warning Temperature Threshold Enclosure Critical Temperature Threshold Controller Warning Temperature Threshold Controller Critical Temperature Threshold
In the field provided, type the temperature in degrees C for each threshold value.
77
5.
Click the Save button.
Viewing FRU VPD Information

FRU VPD refers to Vital Product Data (VPD) information about Field Replaceable Units (FRU) in the enclosure. The number and type of FRU depends on the subsystem model. To view FRU VPD information: To make Enclosure settings: 1. 2. 3. Click the Device tab. Click the Component List icon. Mouse-over the Enclosure and click the FRU VPD button. Use this information when communicating with Technical Support and when ordering replacement units. For contact information, see Contacting Technical Support on page 351.
Viewing Power Supply Status

To view the status of the power supplies: 1. 2. 3. 4. Click the Device tab. Click the Component List icon. Mouse-over the Enclosure and click the View button. Scroll down to view the power supplies. The screen displays the operational and fan status of VTraks two power supplies. If any status differs from normal or the fan speed is below the Healthy Threshold value, there is a fan/power supply malfunction. See Replacing a Power Supply on page 250.
Viewing Fan Status

The fans are located on the power supplies. To view the status of the power supply fans: 1. 2. 3. 4. Click the Device tab. Click the Component List icon. Mouse-over the Enclosure and click the View button. Scroll down to view the Fans. The screen displays the status and speed of the fans on the power supplies. If fan speed is below the Healthy Threshold, there is a malfunction. See Diagnosing an Enclosure Problem on page 308.
78
Viewing Temperature Sensor Status

To view the status of the temperature sensors: 1. 2. 3. 4. Click the Device tab. Click the Component List icon. Mouse-over the Enclosure and click the View button. Scroll down to view the Temperature Sensors. If any temperature exceeds the Healthy Threshold value, there is an overheat condition in the enclosure. See Making Enclosure Settings on page 77 and See Diagnosing an Enclosure Problem on page 308.
Viewing Voltage Sensor Status

To view the status of the voltage sensors: 1. 2. 3. 4. Click the Device tab. Click the Component List icon. Mouse-over the Enclosure and click the View button. Scroll down to view the Voltage Sensors. If any voltage is outside the Healthy Threshold values, there is a voltage malfunction in the enclosure. See Diagnosing an Enclosure Problem on page 308.
79
Managing UPS Units

Uninterruptible Power Supply (UPS) Management includes the following functions: Viewing a List of UPS Units (below) Making UPS Settings (page 81) Viewing UPS Information (page 82)
Viewing a List of UPS Units

To view a list of UPS units supporting the VTrak: 1. 2. Click the Device tab. Click the UPS icon. Information in the UPS List includes: ID The ID number of the UPS Status OK means Normal. On AC means the UPS is connected to a viable external AC power source. On Battery means the external AC power source is offline and the UPS is running on battery power. Model Model name of the UPS Battery Capacity Backup capacity expressed as a percentage. Loading Ratio Actual output of UPS as a percentage of the rated output. See the Note below. Remaining Minutes Number of minutes the UPS is expected to power your system in the event of a power failure. Note The maximum recommended Loading Ratio varies among models of UPS units. The general range is 60% to 80%. If the reported Loading Ratio exceeds the recommended value for your UPS unit: Have fewer subsystems or peripherals connected to this UPS unit. Add more UPS units, or use a higher-capacity UPS unit, to protect your RAID systems.
80
Making UPS Settings

These settings control how the VTrak subsystem detects the UPS unit and responds to data reported by the UPS unit. To make UPS settings: 1. 2. 3. 4. Click the Device tab. Click the UPS icon. Click the UPS Settings button. Perform the following actions as required: Verify the Current UPS Communication method. See Note 1: SNMP Network connection. Serial Serial connection. Unknown No connection. Automatic Default. If a UPS is detected when the subsystem boots, the setting changes to Enable. Enable Monitors UPS. Settings changes, reports warnings, and logs events. Disable Monitors UPS only. Running Time Remaining Threshold Actual time below this value resets adaptive writeback cache to writethrough. Warning Temperature Threshold Actual temperature above this value triggers a warning and logs an event. Loading Ratio Threshold Actual loading ratio (percentage) above this threshold triggers a warning and logs an event. See Note 3.
Choose a Detection Setting from the dropdown menu:
Type values into the Threshold fields. See Note 2:
5.
For UPS units with network cards, type the IP addresses or DNS names in fields UPS 1 and UPS 2. See Note 4.
Press Ctrl-A to save your settings. Note 1: VTrak supports multiple UPS units using network or serial connections, but not a combination of both methods. Note 2: Detection Setting must be set to Auto. If a UPS is detected, the setting changes to Enable. Note 3: The maximum recommended Loading Ratio varies among models of UPS units. The general range is 60% to 80%. Note 4: To specify UPS units by DNS names, ask your IT administrator to add the DNS names to the DNS server, before you make UPS settings.
81
Viewing UPS Information

To view information about a specific UPS unit: 1. 2. 3. Click the Device tab. Click the UPS icon. Mouse-over UPS and click the View button. UPS information includes: UPS ID Model Name Serial Number Firmware Version Manufacture Date Voltage Rating Output voltage of the UPS. Battery Capacity Backup capacity expressed as a percentage. Remaining Backup Time Number of minutes the UPS is expected to power your system in the event of a power failure. Loading Ratio Actual output of UPS as a percentage of the rated output. See the Note below. Temperature Reported temperature of the UPS unit. Note The maximum recommended Loading Ratio varies among models of UPS units. The general range is 60% to 80%. If the reported Loading Ratio exceeds the recommended value for your UPS unit: Have fewer subsystems or peripherals connected to this UPS unit. Add more UPS units, or use a higher-capacity UPS unit, to protect your RAID systems.
82
Managing Users
User management includes: Viewing User Information (below) Creating a User (page 83) Setting User Event Subscriptions (page 84) Making User Settings (page 85) Making LDAP Settings (page 86) Changing User Passwords (page 87) Deleting a User (page 88) Importing a User Database (page 88) Exporting a User Database (page 89)
The Administrator or a Super User can perform these tasks.
Viewing User Information

To view user information: 1. 2. Click the AdminTool tab. Click the User Management icon. The list of users displays. User information includes: User name Status Privilege level Display name Email address User Type local or LDAP user
Creating a User
This action requires Administrator or Super User privileges. To create a user: 1. 2. 3. 4. Click the AdminTool tab. Click the User Management icon. Click the Add User button. In the Add User dialog box, enter the information in the fields provided: Name This is the user's login name Display Name Password
83
5. 6. 7.
Retype Password User Email Required for event notification
Choose a privilege level from the dropdown menu. See the table below. (Optional) Uncheck the Enable box to disable this User account. Click the Save button. The user is added to the list. Important For this user to receive event notification, mouse-over the new user and click the Subscription button. For this user to be an LDAP User, click the LDAP Settings button, enter information and make settings as required. Permission Allows the user full access to all functions including create and delete users and changing the settings of other users, and delete disk arrays and logical drives. The default administrator account is a Super User. Allows the user to create (but not delete) disk arrays and logical drives, change RAID levels, change stripe size; change settings of components such as disk arrays, logical drives, physical drives and the controller. Allows the user to perform maintenance tasks including Rebuilding, PDM, Media Patrol and Redundancy Check Allows the user to see all status and settings but not to make any changes
Privilege Super
Power
Maintenance View
Setting User Event Subscriptions

By default, all users have event notification: Enabled Set to the Major (severity) level for all events
84
Subscribing users receive notification of events at the chosen severity level and all higher levels. Note Each user must have a valid Email address to receive events. See User Settings and Email Settings. Changing a user subscription requires Administrator or Super User privileges. To set a user event subscription: 1. 2. 3. 4. Click Global Management. Click the User icon. In the User list, mouse-over the user you want and click Subscription. Make setting changes as required: 5. For the Enable Event Notification box, check to enable for this user, uncheck to disable. Click to change the priority options for each category of event.
Click the Save button. Severity Level Description Non-recoverable error or failure has occurred. Action is needed now and the implications of the condition are serious. Action is needed now. Action is needed but the condition is not a serious at this time. User can decide whether or not action is required. Information only, no action is required.
Fatal Critical Major Minor Warning Information
Making User Settings

This action requires Administrator or a Super User privileges. To make user settings: 1. 2. 3. 4. Click the AdminTool tab. Click the User Management icon. In the User list, mouse-over the user you want and click Settings. Make setting changes as required: For the Enable box, check to enable this user account, uncheck to disable this user account
85
5.
In the User Settings dialog box, enter a new Display Name or User Email address Choose a new Privilege level from the dropdown menu. See the table on the next page. Permission Allows the user full access to all functions including create and delete users and changing the settings of other users, and delete disk arrays and logical drives. The default administrator account is a Super User. Allows the user to create (but not delete) disk arrays and logical drives, change RAID levels, change stripe size; change settings of components such as disk arrays, logical drives, physical drives and the controller. Allows the user to perform maintenance tasks including Rebuilding, PDM, Media Patrol and Redundancy Check Allows the user to see all status and settings but not to make any changes
Click the Save button. Privilege
Super
Power
Maintenance View
Making LDAP Settings

Lightweight Directory Access Protocol (LDAP) is a protocol used to access a directory listings. This action requires Administrator or a Super User privileges. To make user LDAP settings: 1. 2. 3. 4. Click the AdminTool tab. Click the User Management icon. Click the LDAP Settings button. Enter information and make settings as required: Enable LDAP box Check to enable LDAP. Email notification for Event box Check to enable an email subscription for an LDAP authenticated user. Response Time Out Maximum time to allowed for communication with LDAP server. Base DN Search domain limit of LDAP query. dc=example, dc=com is the default. LDAP Server Hostname or IP address of the LDAP server. 127.0.0.1 is the default. LDAP Port The port number of the LDAP server. 389 is the default.
86
5.
Anonymous Bind Allows the system to bind to an LDAP server without providing Bind DN and password. Bind DN Authenticates communication between subsystem and LDAP server. No default value. Bind Password Password for BindDN. No default value. Default Privilege Choose a level from the dropdown menu. See the table on the previous page. User Name Filter Filters specific user information from LDAP server. &(objectClass=person) is the default. UID Attribute Store users ID in LDAP server. For Windows, a typical value is sAMAccountName. Full Name Attribute Store user's full name in LDAP server. displayName is the default. Email Address Attribute Store user's email address in LDAP server. mail is the default. Enable SSL box Enables encrypted communication between subsystem and LDAP server.
Click the Save button. When LDAP is applied to a user, the User Type is LDAP User. When LDAP is NOT applied to a user, the User Type is local.
Changing User Passwords

This action requires Administrator or Super User privileges. To change a users password: 1. 2. 3. 4. Click the AdminTool tab. Click the User Management icon. In the User list, mouse-over the user you want and click Change Password. In the Change Password dialog box, enter the information in the fields provided: 5. New Password Retype Password
Click the Save button. Note To reset the Administrators password to the factory default, see Resetting the Default Password on page 258.
87
Deleting a User
This action requires Administrator or Super User privileges. Note You cannot delete the Administrator.
To delete a user: 1. 2. 3. 4. Click the AdminTool tab. Click the User Management icon. In the User list, mouse-over the user you want and click the Delete button. In the Confirmation box, type the word confirm in the field provided and click the Confirm button.
Importing a User Database

You can save the user information and settings from one VTrak RAID subsystem, export it, and then import it to automatically configure your other VTrak RAID subsystems. Caution Importing a user database overwrites the current users and user settings on your VTrak subsystem. To import a user database: 1. 2. 3. 4. 5. 6. Click the AdminTool tab. Click the Import/Export icon. Click the Import option. Choose User Database from the Type dropdown menu. Click the Browse button and navigate to the user database file and click the OK button. Click the Next button. The system verifies that the file is a valid user database and displays any errors or warnings. 7. 8. Click the Submit button to continue. In the Confirmation box, type the word confirm in the field provided and click the Confirm button. The user database is imported and applied automatically.
88
Exporting a User Database

You can save the user information and settings from one VTrak RAID subsystem, export it, and then import it to automatically configure your other VTrak RAID subsystems. To export a user database: 1. 2. 3. 4. 5. 6. Click the AdminTool tab. Click the Import/Export icon. Click the Export option. Choose User Database from the Type dropdown menu. Click the Submit button. In the Open dialog box, click the Save File option, then click the OK button. The file is saved to your PC as User.dat. Note The user database file is not designed to be opened or edited in the field.
89
Managing Background Activities

Background activity management includes: Viewing Current Background Activities (page 90) Viewing Scheduled Background Activities (page 90) Adding a Scheduled Background Activity (page 91) Changing a Background Activity Schedule (page 92) Enabling or Disabling a Scheduled Background Activity (page 93) Deleting a Scheduled Background Activity (page 93) Media Patrol (page 94) Redundancy Check (page 94) Initialization (page 95) Rebuild (page 96) Migration (page 96) PDM (page 97) Transition (page 98) Synchronization (page 98) Battery Reconditioning (page 99) Spare Check (page 99)
Background activities perform a variety of preventive and remedial functions on your physical drives, disk arrays, logical drives, and other components. You can run a background activity immediately or schedule it to run at a later time. Scheduling options are described below. Setting options for each activity are listed after the scheduling options. These settings determine how the background activity affects I/O performance.
Viewing Current Background Activities

To view a list of scheduled background activities: 1. 2. Click the AdminTool tab. Click the Background Activities icon. The list of background appears. Currently running activities show a progress bar.
Viewing Scheduled Background Activities

To view a list of scheduled background activities: 1. Click the AdminTool tab.
90
2. 3.
Click the Background Activities icon. The list of background appears. Click the Scheduler button. The list of currently scheduled background activities appears.
Adding a Scheduled Background Activity

To add a new scheduled background activity: 1. 2. 3. 4. 5. 6. 7. Click the AdminTool tab. Click the Background Activities icon. The list of background appears. Click the Scheduler button. The list of currently scheduled background act it viti es appears. Click the Add Schedule button. Check the Enable Media Patrol box to enable, uncheck to disable. This settings enables or disables Media Patrol for your entire RAID system. Click the Confirm button. Choose the option for the activity you want: 8. 9. Media Patrol Redundancy Check Spare Check Battery Recondition
Choose a Start Time from the dropdown menus. The menus have a 24-hour clock. Choose a Recurrence Pattern option, daily, weekly, or monthly. For the Daily option, enter an interval in the Every field. For the Weekly option, enter an interval in the Every field and choose one or more days of the week. For the Monthly option, choose, Day of the Month option then choose a number from the dropdown menu. The day of the week option then choose the day of the month from the dropdown menus.
10. Choose a Start From date from the dropdown menus. 11. Choose an End On option, No end date or perpetual. End after a specific number of activity actions.
91
Until date from the dropdown menus. Auto Fix option Attempts to repair the problem when it finds an error. Check to enable Pause on Error option The process stops when it finds a nonrepairable error. Check to enable Select LD Check the boxes for the logical drives to run Redundancy Check. Check at least one logical drive
12. For Redundancy Check, choose,
13. Click the Save button.
Changing a Background Activity Schedule

Caution Disabling the battery recondition schedule is NOT recommended.
To change an existing scheduled background activity: 1. 2. 3. 4. 5. Click the AdminTool tab. Click the Background Activities icon. The list of background appears. Click the Scheduler button. The list of currently scheduled background act it viti es appears. Mouse-over the background activity and click the Settings button. Make settings changes as required: Choose a Start Time from the dropdown menus. The menus have a 24-hour clock. Choose a Recurrence Pattern option, daily, weekly, or monthly. For the Daily option, enter an interval in the Every field. For the Weekly option, enter an interval in the Every field and choose one or more days of the week. For the Monthly option, choose the Day of the Month option or the day of the week option, and choose the day from the dropdown menu.
Choose a Start From date from the dropdown menus. Choose an End On option, No end date or perpetual. End after a specific number of activity actions.
92
6.
Until date from the dropdown menus. Auto Fix option Attempts to repair the problem when it finds an error. Check to enable Pause on Error option The process stops when it finds a nonrepairable error. Check to enable Select LD Check the boxes for the logical drives to run Redundancy Check. Check at least one logical drive
For Redundancy Check, choose,
Enabling or Disabling a Scheduled Background Activity

Background activity schedules are enabled by default when you create the schedule. If you want to stop a background activity now but plan to use it again in the future, disable the scheduled activity rather than deleting it. Caution Disabling the battery recondition schedule is NOT recommended.
To enable or disable change an existing scheduled background activity: 1. 2. 3. 4. 5. 6. Click the AdminTool tab. Click the Background Activities icon. The list of background appears. Click the Scheduler button. The list of currently scheduled background act it viti es appears. Mouse-over the background activity and click the Settings button. Uncheck the Enable This Schedule box to disable this schedule. Check the box to enable this schedule. Click the Save button.
Deleting a Scheduled Background Activity

Caution Deleting the battery recondition schedule is NOT recommended.
To change an existing scheduled background activity: 1. Click the AdminTool tab.

93
2. 3. 4. 5.
Click the Background Activities icon. The list of background appears. Click the Scheduler button. The list of currently scheduled background act it viti es appears. Mouse-over the background activity and click the Delete button. In the confirmation box, click the confirm button.
Media Patrol
Media Patrol is a routine maintenance procedure that checks the magnetic media on each disk drive. Media Patrol checks are enabled by default on all disk arrays and spare drives. Media Patrol is concerned with the media itself, not the data recorded on the media. If Media Patrol encounters a critical error, it triggers PDM if PDM is enabled on the disk array. See Making Disk Array Settings on page 128, Running Media Patrol on a Disk Array on page 129, and Media Patrol on page 259.
Making Media Patrol Settings

To make Media Patrol settings: 1. 2. 3. 4. 5. Click the AdminTool tab. Click the Background Activities icon. The list of background appears. Click the Settings button. Check the Enable Media Patrol box to enable, uncheck to disable. This settings enables or disables Media Patrol for your entire RAID system. Click the Confirm button. You can also enable or disable Media Patrol on individual disk arrays.
Redundancy Check
Redundancy Check is a routine maintenance procedure for fault-tolerant disk arrays (those with redundancy) that ensures all the data matches exactly. Redundancy Check can also correct inconsistencies. See Redundancy Check on a Logical Drive on page 138.
Making Redundancy Check Settings

To make Redundancy Check settings: 1. 2. Click the AdminTool tab. Click the Background Activities icon. The list of background activities appears.
94
3. 4.
Click the Settings button. Click the Redundancy Check Rate dropdown menu and choose a rate: Low Fewer system resources to Redundancy Check, more to data read/write operations. Medium Balances system resources between Redundancy Check and data read/write operations. High More system resources to Redundancy Check, fewer to data read/write operations.
5.
Click the Confirm button.
Initialization
Technically speaking, Initialization is a foreground activity, as you cannot access a logical drive while it is initiating. Initialization is normally done to logical drives after they are created from a disk array. Initialization sets all data bits in the logical drive to zero. The action is useful because there may be residual data on the logical drives left behind from earlier configurations. For this reason, Initialization is recommended whenever you create a logical drive. See Initializing a Logical Drive on page 137 and Initialization on page 282.
Making Initialization Settings

To make initialization settings: 1. 2. 3. 4. Click the AdminTool tab. Click the Background Activities icon. Click the Settings button. Click the Logical Drive Initialization Rate dropdown menu and choose a rate: 5. Low Fewer system resources to Initialization, more to data read/write operations. Medium Balances system resources between Initialization and data read/write operations. High More system resources to Initialization, fewer to data read/write operations.
95
Rebuild
When you rebuild a disk array, you are actually rebuilding the data on one physical drive. When a physical drive in a disk array fails and a spare drive of adequate capacity is available, the disk array begins to rebuild automatically using the spare drive. If there is no spare drive of adequate capacity, but the Auto Rebuild function is ENABLED, the disk array begins to rebuild automatically as soon as you remove the failed physical drive and install an unconfigured physical drive in the same slot. See Making Rebuild Settings on page 96. If there is no spare drive of adequate capacity and the Auto Rebuild function is DISABLED, you must replace the failed drive with an unconfigured physical drive, then perform a Manual Rebuild.
See Rebuilding a Disk Array on page 130 and page 319 and Spare Drives on page 283. Also see Disk Array Degraded/Logical Drive Critical on page 317 and Disk Array Offline/Logical Drive Offline on page 318.
Making Rebuild Settings

1. 2. 3. 4. Click the AdminTool tab. Click the Background Activities icon. The list of background activities appears. Click the Settings button. Click the Rebuild Rate dropdown menu and choose a rate: 5. 6. Low Fewer system resources to the Rebuild, more to data read/write operations. Medium Balances system resources between the Rebuild and data read/write operations. High More system resources to the Rebuild, fewer to data read/write operations.
Check the Enable Auto Rebuild box to enable Auto Rebuild (rebuilds when you swap out the failed drive with a new one). Click the Confirm button.
Migration
The term Migration means either or both of the following: Change the RAID level of a logical drive. Expand the storage capacity of a logical drive.
96
See Migrating a Logical Drives RAID Level on page 139 and RAID Level Migration on page 275.
Making Migration Settings

To make migration settings: 1. 2. 3. 4. Click the AdminTool tab. Click the Background Activities icon. The list of background activities appears. Click the Settings button. Click the Migration Rate dropdown menu and choose a rate: 5. Low Fewer system resources to Migration, more to data read/write operations. Medium Balances system resources between Migration and data read/write operations. High More system resources to Migration, fewer to data read/write operations.
PDM
Predictive Data Migration (PDM) is the migration of data from the suspect disk drive to a spare disk drive, similar to rebuilding a logical drive. But unlike Rebuilding, PDM constantly monitors your disk drives and automatically copies your data to a spare disk drive BEFORE the disk drive fails and your logical drive goes Critical. See Running PDM on a Disk Array on page 129 and PDM on page 259.
Making PDM Settings

To make PDM settings: 1. 2. 3. 4. Click the AdminTool tab. Click the Background Activities icon. The list of background activities appears. Click the Settings button. Make the following settings are required: Click the PDM Rate dropdown menu and choose a rate: Low Fewer system resources to PDM, more to data read/write operations. Medium Balances system resources between PDM and data read/write operations.
97
High More system resources to PDM, fewer to data read/write operations.
Highlight the current values in the block threshold fields and input new values. Reassigned block threshold range is 1 to 512 blocks. Error block threshold range is 1 to 2048 blocks.
5.
Transition
Transition is the process of replacing a revertible spare drive that is currently part of a disk array with an unconfigured physical drive or a non-revertible spare drive. See Running a Transition on a Spare Drive on page 144 and Transition on page 284.
Making Transition Settings

To make Transition settings: 1. 2. 3. 4. Click the AdminTool tab. Click the Background Activities icon. The list of background activities appears. Click the Settings button. Click the Transition Rate dropdown menu and choose a rate: 5. Low Fewer system resources to Transition, more to data read/write operations. Medium Balances system resources between Transition and data read/write operations. High More system resources to Transition, fewer to data read/write operations.
Synchronization
Synchronization is automatically applied to logical drives when they are created. Synchronization recalculates the redundancy data to ensure that the working data on the physical drives is properly in sync. Mouse-over on the logical drive, click the View button, and look under Logical Drive Information beside the line that says Synchronized. A Yes means the logical drive was synchronized. See Viewing Logical Drive Information on page 132.
98
Making Synchronization Settings

To make Synchronization settings: 1. 2. 3. 4. Click the AdminTool tab. Click the Background Activities icon. The list of background activities appears. Click the Settings button. Click the Synchronization Rate dropdown menu and choose a rate: 5. Low Fewer system resources to Synchronization, more to data read/ write operations. Medium Balances system resources between Synchronization and data read/write operations. High More system resources to Synchronization, fewer to data read/ write operations.
Battery Reconditioning
Batteries maintain power to the controller cache in the event of a power failure, thus protecting any data that has not been written to a physical drive. Reconditioning is the action of discharging and recharging a battery to preserve its capacity and performance. By default, each battery is reconditioned every two months. When the recondition is completed, the batterys cycle count increments by one. Caution Disabling or deleting the battery recondition schedule is NOT recommended. See Reconditioning a Battery on page 74.
Spare Check
Spare Check verifies the status of your spare drives. Because spare drives are not currently handling data, there are no settings for Spare Check. See Running Spare Check on page 144.
99
Managing Storage Services

Storage service management includes: Viewing a List of Services (below) Email Service (page 100) SLP Service (page 101) Webserver Service (page 102) Telnet Service (page 103) SSH Service (page 104) SNMP Service (page 105) CIM Service (page 107) Netsend Service (page 108)
Viewing a List of Services

This feature displays all software services running on the RAID subsystem. See the table below. To view the list of software services: 1. 2. Click the AdminTool tab. Click the Services icon. The list of services includes, Service Name Start type Automatic or Manual
Email Service
Email service enables the RAID subsystem to send you Email messages about events and status changes. By default, Email service is set to Automatic.
Stopping Email Service

To stop the Email service: 1. 2. 3. 4. Click the AdminTool tab. Click the Services icon. Mouse-over the Email service and click the Stop button. Click the Confirm button.
To start the Email service after stopping it: 1. 2. 3. Click the AdminTool tab. Click the Services icon. Mouse-over the Email service and click the Start button.
100
Restarting Email Service

To restart the Email service: 1. 2. 3. Click the AdminTool tab. Click the Services icon. Mouse-over the Email service and click the Restart button.
Making Email Settings

To change Email service settings: 1. 2. 3. 4. Click the AdminTool tab. Click the Services icon. Mouse-over the Email service and click the Settings button. Make settings changes as required: Choose a startup type, 5. 6. Automatic (default) Starts and runs with the subsystem. Manual You start the service when you need it.
SMTP Server IP address. SMTP Authentication The Yes option enables authentication. The No option disables. SMTP Authentication Username Required if SMTP authentication is enabled. SMTP Authentication Password Required if SMTP authentication is enabled. Email Sender (From) Address The senders name shown on notification messages. Email Subject The subject line of the notification message.
Click the Save button. Click the Confirm button. Note To verify your settings, send a test message.
SLP Service
Service Location Protocol (SLP) discovers services over the Internet. SLP applies to IPv4 protocol only.
101
Stopping SLP Service

To stop the SLP service: 1. 2. 3. 4. Click the AdminTool tab. Click the Services icon. Mouse-over the SLP service and click the Stop button. Click the Confirm button.
To start the SLP service after stopping it: 1. 2. 3. Click the AdminTool tab. Click the Services icon. Mouse-over the SLP service and click the Start button.
Restarting SLP Service

To restart the SLP service: 1. 2. 3. Click the AdminTool tab. Click the Services icon. Mouse-over the SLP service and click the Restart button.
Making SLP Settings

To change SLP service settings: 1. 2. 3. 4. Click the AdminTool tab. Click the Services icon. Mouse-over the SLP service and click the Settings button. Choose a startup type: 5. 6. Automatic (default) Starts and runs with the subsystem. Manual You start the service when you need it.
Click the Save button. Click the Confirm button.
Webserver Service
Webserver service connects the WebPAM PROe interface to the RAID subsystem though your browser.
Stopping Webserver Service

To stop the Webserver service: 1. 2. 3. Click the AdminTool tab. Click the Services icon. Mouse-over the Webserver service and click the Stop button.
102
4.
To start the Webserver service after stopping it: 1. 2. 3. Click the AdminTool tab. Click the Services icon. Mouse-over the Webserver service and click the Start button.
Restarting Webserver Service

1. 2. 3. Click the AdminTool tab. Click the Services icon. Mouse-over the Webserver service and click the Restart button.
Making Webserver Settings

To change Webserver service settings: 1. 2. 3. 4. Click the AdminTool tab. Click the Services icon. Mouse-over the Webserver service and click the Settings button. Make settings changes as required: Choose a startup type, 5. 6. Automatic (default) Starts and runs with the subsystem. Manual You start the service when you need it.
Session Time Out Default is 24 minutes. HTTP Port number Default is 80. Enable SSL Security protocol used with HTTPS. Default is enabled (checked). HTTPs Port number Default is 443.
Telnet Service
Telnet service enables you to access the RAID subsystems Command Line Interface (CLI) through a network connection.
Stopping Telnet Service

To stop the Telnet service: 1. 2. 3. Click the AdminTool tab. Click the Services icon. Mouse-over the Telnet service and click the Stop button.
103
4.
To start the Telnet service after stopping it: 1. 2. 3. Click the AdminTool tab. Click the Services icon. Mouse-over the Telnet service and click the Start button.
Restarting Telnet Service

To restart the Telnet service: 1. 2. 3. Click the AdminTool tab. Click the Services icon. Mouse-over the Telnet service and click the Restart button.
Making Telnet Settings

To change Telnet service settings: 1. 2. 3. 4. Click the AdminTool tab. Click the Services icon. Mouse-over the Telnet service and click the Settings button. Make settings changes as required: Choose a startup type, 5. 6. Automatic (default) Starts and runs with the subsystem. Manual You start the service when you need it.
Port number Default is 2300. Max Number of Concurrent Connections Default is 4. Maximum number is 4. Session Time Out Default is 24 minutes.
SSH Service
Secure Shell (SSH) service enables you to access the subsystems Command Line Interface (CLI) through a network connection.
Stopping SSH Service

To stop the SSH service: 1. 2. 3. Click the AdminTool tab. Click the Services icon. Mouse-over the SSH service and click the Stop button.
104
4.
To start the SSH service after stopping it: 1. 2. 3. Click the AdminTool tab. Click the Services icon. Mouse-over the SSH service and click the Start button.
Restarting SSH Service

To restart the SSH service: 1. 2. 3. Click the AdminTool tab. Click the Services icon. Mouse-over the SSH service and click the Restart button.
Making SSH Settings

To change SSH service settings: 1. 2. 3. 4. Click the AdminTool tab. Click the Services icon. Mouse-over the SSH service and click the Settings button. Make settings changes as required: Choose a startup type, 5. 6. Automatic (default) Starts and runs with the subsystem. Manual You start the service when you need it.
Port number - Default is 22. Max Number of Concurrent Connections Default is 4. Maximum number is 4. Session Time Out - Default is 24 minutes.
SNMP Service
Simple Network Management Protocol (SNMP) service enables the SNMP browser to obtain information from the RAID subsystem. The Trap Sink is where SNMP events are sent and can be viewed.
Stopping SNMP Service

To stop the SNMP service: 1. 2. 3. Click the AdminTool tab. Click the Services icon. Mouse-over the SNMP service and click the Stop button.
105
4.
To start the SNMP service after stopping it: 1. 2. 3. Click the AdminTool tab. Click the Services icon. Mouse-over the SNMP service and click the Start button.
Restarting SNMP Service

To restart the SNMP service: 1. 2. 3. Click the AdminTool tab. Click the Services icon. Mouse-over the SNMP service and click the Restart button.
Making SNMP Settings

To change SNMP service settings: 1. 2. 3. 4. Click the AdminTool tab. Click the Services icon. Mouse-over the SNMP service and click the Settings button. Make settings changes as required: Choose a startup type, 5. 6. Automatic (default) Starts and runs with the subsystem. Manual You start the service when you need it.
Port Number Default is 161. System Name No default. System Location Default is USA. System Contact Default is admin@yourcompany.com. Read Community Default is public. Write Community Default is private. No changes are possible.
Adding an SNMP Trap Sink

To add a trap sink: 1. 2. 3. 4. 5. Click the AdminTool tab. Click the Services icon. Mouse-over the SNMP service and click the Settings button. Enter a trap sink server IP address in the field provided. Choose a trap filter (event severity level).
106
See the table on the next page. 6. 7. Click the Add button. Click the Confirm button. Severity Level Fatal Critical Major Minor Warning Information Description Non-recoverable error or failure has occurred. Action is needed now and the implications of the condition are serious. Action is needed now. Action is needed but the condition is not a serious at this time. User can decide whether or not action is required. Information only, no action is required.
Deleting an SNMP Trap Sink

To delete a trap sink: 1. 2. 3. 4. 5. 6. 7. Click the AdminTool tab. Click the Services icon. Mouse-over the SNMP service and click the Settings button. In the Trap Sink list and click the Trap Sink you want to delete. Click the Trash icon. The trap sink is deleted. Click the Save button. Click the Confirm button.
CIM Service
The Common Information Model (CIM) service provides a database for information about computer systems and network devices.
Stopping CIM Service

To stop the CIM service: 1. 2. 3. 4. Click the AdminTool tab. Click the Services icon. Mouse-over the CIM service and click the Stop button. Click the Confirm button.
To start the CIM service after stopping it: 1. 2. Click the AdminTool tab. Click the Services icon.
107
3.
Mouse-over the CIM service and click the Start button.
Restarting CIM Service

To restart the CIM service: 1. 2. 3. Click the AdminTool tab. Click the Services icon. Mouse-over the CIM service and click the Restart button.
Making CIM Settings

To change CIM service settings: 1. 2. 3. 4. Click the AdminTool tab. Click the Services icon. Mouse-over the CIM service and click the Settings button. Make settings changes as required: Choose a startup type, Automatic (default) Starts and runs with the subsystem. Manual You start the service when you need it.
CIM HTTP Enabled Default is Yes. CIM HTTP Port number Default is 5988. CIM HTTPS Enabled Default is No. CIM HTTPS Port number Default is 5989. CIM Authentication Default is No.
When CIM Authentication is Yes, these fields appear, Change Password Default is No. CIM User Name Default is cim. No changes are possible.
When Change Password is Yes, these fields appear, 5. 6. Old User Password New User Password Retype (new user) Password
Netsend Service
Netsend service sends RAID subsystem events in the form of text messages to the Host PC and other networked PCs configured to receive Netsend event messages by setting up Netsend server accounts.
108
This service is set to Manual startup by default. It does not run unless you start it manually or change the startup type to Automatic.
Starting Netsend Service

To restart the Netsend service: 1. 2. 3. Click the AdminTool tab. Click the Services icon. Mouse-over the Netsend service and click the Start button.
Stopping Netsend
To stop the Netsend service: 1. 2. 3. 4. Click the AdminTool tab. Click the Services icon. Mouse-over the Netsend service and click the Stop button. Click the Confirm button.
Restarting Netsend Service

To start the Netsend service after stopping it: 1. 2. 3. Click the AdminTool tab. Click the Services icon. Mouse-over the Netsend service and click the Start button.
Making Netsend Settings

To change Netsend service settings: 1. 2. 3. 4. Click the AdminTool tab. Click the Services icon. Mouse-over the Netsend service and click the Settings button. Choose a startup type, 5. 6. Automatic Starts and runs with the subsystem. Manual (default) You start the service when you need it.
Adding Netsend Server Accounts

To add a Netsend server account: 1. 2. 3. 4. Click the AdminTool tab. Click the Services icon. Mouse-over the Netsend service and click the Settings button. Enter the recipient server IP address in the field provided.
109
5. 6. 7. 8.
Choose a recipient filter (event severity level). See the table on the next page. Click the Add button. The recipient server is added to the list. Click the Save button. Click the Confirm button. Severity Level Description Non-recoverable error or failure has occurred. Action is needed now and the implications of the condition are serious. Action is needed now. Action is needed but the condition is not a serious at this time. User can decide whether or not action is required. Information only, no action is required.
Fatal Critical Major Minor Warning Information
Deleting Netsend Server Accounts

To delete a Netsend server account: 1. 2. 3. 4. 5. 6. 7. Click the AdminTool tab. Click the Services icon. Mouse-over the Netsend service and click the Settings button. In the Message Event Severity Filter list and click the recipient server you want to delete. Click the Trash icon. The recipient server is deleted. Click the Save button. Click the Confirm button.
110
Monitoring Performance
Performance monitoring includes: Monitoring I/O Performance (below) Monitoring PSU Wattage (page 112)
Monitoring I/O Performance

The Performance Monitor displays real-time performance statistics for logical drives, physical drives, and Fibre Channel or SAS data ports. The vertical scale adjusts dynamically to accommodate the statistical data. Because it reports performance in real-time, to see data in the monitor, there must be I/O data activity taking place between the VTrak subsystem and the Host. To monitor performance: 1. 2. 3. Click the AdminTool tab. Click the Performance Monitor icon. Under Logical Drive, Choose the metric you want to see from the Measurement dropdown menu: Bandwidth in MB/s Cache usage by % Dirty cache usage by % Maximum latency in ms Average latency in ms Minimum latency in ms I/Os per second
Click the Select Logical Drives button and check the boxes for the logical drives you want to see: Total of all logical drives Up to 8 individual logical drives
4.
Under Physical Drive, Choose the metric you want to see from the Measurement dropdown menu: Bandwidth in MB/s Maximum latency in ms Average latency in ms Minimum latency in ms
111
I/Os per second
Click the Select Physical Drives button and check the boxes for the physical drives you want to see: Total of all physical drives Up to 8 individual physical drives
5.
Under Port, Choose the metric you want to see from the Measurement dropdown menu: Bandwidth in MB/s Maximum latency in ms Average latency in ms Minimum latency in ms I/Os per second
Click the Select Ports button and check the boxes for the ports you want to see: Total of all ports Up to 8 individual ports
Since the Performance Monitor is a real-time display, it does not accumulate information and there is no clear or save function. To save performance statistics for analysis or troubleshooting, save a Service Report, open the report, and look under Statistic Info. See Saving a Service Report on page 63.
Monitoring PSU Wattage

The PSU Wattage Monitor displays real-time performance statistics for logical drives, the input power of all enclosures and the input power of an individual. The vertical scale adjusts dynamically to accommodate the statistical data. Because it reports performance in real-time, to see data in the monitor, there must be I/O data activity taking place between the VTrak subsystem and the Host. To monitor performance and power use: 1. 2. 3. Click the AdminTool tab. Click the PSU Wattage Monitor icon. Under Logical Drive, Choose the metric you want to see from the Measurement dropdown menu: Bandwidth in MB/s
112
Cache usage by % Dirty cache usage by % Maximum latency in ms Average latency in ms Minimum latency in ms I/Os per second
Click the Select Logical Drives button and check the boxes for the logical drives you want to see: Total of all logical drives Up to 8 individual logical drives
4.
Under Input Power of an individual Enclosure, click the Select Enclosures button and check the boxes for the enclosures you want to see.
Since the PSU Wattage Monitor is a real-time display, it does not accumulate information and there is no clear or save function. To save performance and power statistics for analysis or troubleshooting, save a Service Report, open the report, and look under PSU Wattage Info. See Saving a Service Report on page 63.
113
Managing Physical Drives

Physical drive management includes: Viewing a List of Physical Drives (below) Viewing Physical Drive Information (page 114) Making Global Physical Drive Settings (page 116) Making Individual Physical Drive Settings (page 117) Viewing Physical Drive Statistics (page 117) Viewing Physical Drive SMART Log Information (page 118) Saving the Physical Drive SMART Log (page 118) Locating a Physical Drive (page 119) Forcing a Physical Drive Offline (page 119) Clearing a Stale or a PFA Condition (page 120) Clearing a Stale or a PFA Condition (page 120) Updating Firmware on a Physical Drive (page 120) Managing Physical Drive Problems, see Physical Drive Problems on page 316
Viewing a List of Physical Drives

To view a list of physical drives in the RAID system: 1. 2. Click the Device tab. Click the Physical Drive icon. The list of enclosures and the physical drives inside them displays. Physical drive information includes: ID ID number of the physical drive Status Green check , yellow ! , and red X icons
Model Make and model of the drive Type SAS or SATA, HDD or SSD Location Enclosure number and slot number Configuration Array number and sequence number, spare number, unconfigured, or stale configuration Capacity In GB
Viewing Physical Drive Information

To view physical drive information: 1. Click the Device tab.
114
2. 3.
Click the Physical Drive icon. Mouse-over the physical drive you want and click the View button. Physical drive information includes: Physical Drive ID ID number of the physical drive Location Enclosure number and slot number Alias If assigned Physical Capacity Total capacity in GB Configurable Capacity Usable capacity in GB Used Capacity Capacity actually used in GB Block Size Typically 512 Bytes Operational Status OK is normal, Stale, PFA, Dead Configuration Array number and sequence number, spare number, Model Make and model of the drive Drive Interface SATA 1.5Gb/s or 3Gb/s, SAS 3Gb/s Serial Number Serial number of the drive Firmware Version Firmware version on the drive Protocol Version ATA/ATAPI protocol version Visible To Controllers that can access this physical drive Write Cache Enabled or disabled Read Look Ahead Cache Enabled or disabled Read Cache Support Yes or No SMART Feature Set Yes or No SMART Self Test Yes or No SMART Error Logging Yes or No Command Queuing Support TCQ or NCQ Command Queuing Enabled or disabled Queue Depth - Number of commands Maximum Multiple DMA Mode Supported Maximum Ultra DMA Mode Supported DMA Mode Power Saving Level Enabled or disabled ARM Support Standby or Active Medium Error Threshold Drive Temperature
Advanced information for SATA physical drives includes:
115
Drive Reference Temperature Read Cache Enabled or disabled Read Cache Support Yes or No Write Cache Enabled or disabled Write Cache Support Yes or No Enable Read Look Ahead Support Yes or No Read Look Ahead Cache Enabled or disabled Command Queuing Enabled or disabled Command Queuing Support Yes or No WWN Worldwide Number Port 1 Negotiated Physical Drive Speed Port 1 SAS Address Port 2 Negotiated Physical Drive Speed Port 2 SAS Address Drive Temperature in C Drive Reference Temperature in C Power Saving Level Enabled or disabled Medium Error Threshold SAS SATA Bridge Firmware Version SAS SATA Bridge Boot Loader Version
Advanced information for SAS physical drives includes:
Making Global Physical Drive Settings

To make global physical drive settings: 1. 2. 3. 4. Click the Device tab. Click the Physical Drive icon. Click the Global Physical Drive Settings button. Check the boxes to enable, uncheck to disable. For SATA drives: Enable Write Cache Enable Read Look Ahead Cache Enable Command Queuing
For SAS drives: Enable Write Cache Enable Read Look Ahead Cache
116
5.
Enable Read Cache
Making Individual Physical Drive Settings

To make individual physical drive settings: 1. 2. 3. 4. 5. 6. Click the Device tab. Click the Physical Drive icon. Mouse-over the physical drive you want and click the Settings button. On the Settings tab: Enter, change, or delete the alias in the Alias field. Check the box to enable the SMART log. On the SMART Log Settings tab: Click the Save button.
Viewing Physical Drive Statistics

To view physical drive statistics: 1. 2. 3. 4. Click the Device tab. Click the Physical Drive icon. Mouse-over the physical drive you want and click the View button. Click the Statistics tab. Physical drive statistics include: Data Transferred Read Data Transferred Write Data Transferred Errors - Number of errors Non Read/Write Errors Read Errors Write Errors I/O Request Number of requests Non Read/Write Request Number of requests Read I/O Request Number of requests Write I/O Request Number of requests Statistics Start Time Time and date Statistics Collection Time Time and date Avg Response Time Ctrl 1 Controller 1 average response time
117
Avg Response Time Ctrl 2 Controller 2 average response time Max Response Time Ctrl 1 Controller 1 maximum response time Max Response Time Ctrl 2 - Controller 2 maximum response time
To clear physical drive statistics, see Clearing Statistics on page 63.
Viewing Physical Drive SMART Log Information

To view physical drive SMART Log information: 1. 2. 3. 4. Click the Device tab. Click the Physical Drive icon. Mouse-over the physical drive you want and click the View button. Click the SMART Log tab. SMART Log information includes: In progress SMART Support Yes or no, depends on the drive SMART Log Enabled Enabled or disabled, see Note below SMART Health status OK is normal SCT Status Version SCT Version SCT Support Level Device State Current Temperature Power Cycle Min Temperature Power Cycle Max Temperature Lifetime Min Temperature Lifetime Max Temperature Under Temperature Limit Count Over Temperature Limit Count
If the SMART Log is disabled, see Making Controller Settings on page 70.
Saving the Physical Drive SMART Log

To save the physical drive SMART Log: 1. 2. 3. 4. Click the Device tab. Click the Physical Drive icon. Mouse-over the physical drive you want and click the View button. Click the SMART Log tab.
118
5.
Click the Save Advanced SMART Log button. Your browser saves a text file containing the SMART Log to its designated download folder.
Locating a Physical Drive

This feature causes the drive carrier LEDs to blink for one minute to assist you in locating the physical drive, and is supported by RAID subsystems and JBOD expansion units. To locate a physical drive: 1. 2. 3. Click the Device tab. Click the Physical Drive icon. Mouse-over the physical drive you want and click the Locate button. The drive carrier LED flashes for one minute. Green LED flashes
Forcing a Physical Drive Offline

This feature applies only to physical drives assigned to disk arrays. Caution Forcing a physical drive offline or online is likely to cause data loss. Back up your data before you proceed. Use these functions only when required. Important Forcing a physical drive offline causes your logical drives to become degraded. If Auto Rebuild is enabled and a spare drive is available, the disk array begins rebuilding itself automatically. To force a physical drive offline: 1. 2. 3. 4. Click the Device tab. Click the Physical Drive icon. Click the down arrow button to list the physical drives in the enclosure. Mouse over the physical drive you want to force offline.
119
5. 6.
Click the Force Offline button. In the Confirmation box, type the word confirm in the field provided and click the Confirm button.
Clearing a Stale or a PFA Condition

Stale The physical drive contains obsolete disk array information. PFA The physical drive has errors resulting in a prediction of failure. Be sure you have corrected the condition by a physical drive replacement, rebuild operation, etc., first. Then clear the condition. To clear a Stale or a PFA condition: 1. 2. 3. Click the Device tab. Click the Physical Drive icon. Mouse-over the physical drive you want and click the Clear PFA/Stale button. If the physical drive has both a Stale condition and a PFA condition, the first click removes the Stale condition. Click the Clear PFA/Stale button a second time to remove the PFA condition.
Updating Firmware on a Physical Drive

This feature applies only to PROMISE-supported physical drives. For a list of supported drives, go to PROMISE support http://www.promise.com/support/. Then see Updating Physical Drive Firmware on page 248. If you have physical drives in your RAID system that are not PROMISEsupported, follow the firmware update procedure from the drive manufacturer.
120
Managing Disk Arrays

Disk array management includes: Viewing a List of Disk Arrays (below) Viewing Disk Array Information (page 121) Creating a Disk Array Manually (page 122) Creating a Disk Array with the Wizard (page 123) Deleting a Disk Array (page 127) Making Disk Array Settings (page 128) Locating a Disk Array (page 128) Running Media Patrol on a Disk Array (page 129) Running PDM on a Disk Array (page 129) Preparing a Disk Array for Transport (page 130) Rebuilding a Disk Array (page 130)
Also see Disk Array and Logical Drive Problems (page 317).
Viewing a List of Disk Arrays

To view a list of disk arrays: 1. 2. Click the Storage tab. Click the Disk Array icon. The list of disk arrays appears. Disk array information includes: ID DA0, DA1, DA2, etc. Alias If assigned Status A green check icon means OK
Capacity Data capacity of the array Free Capacity Unconfigured or unused capacity on the physical drives Media Patrol Enabled or disabled on this array No. of Logical Drives The number of logical drives on this array
Viewing Disk Array Information

To view disk array information: 1. 2. Click the Storage tab. Click the Disk Array icon.
121
The list of disk arrays appears. 3. Mouse-over the disk array you want and click the View button. Array information displays, including: ID DA0, DA1, DA2, etc. Alias If assigned Operational Status OK is normal Media Patrol Enabled or disabled on this array PDM Enabled or disabled on this array Total Capacity Data capacity of the array Configurable Capacity Maximum usable capacity of the array Free Capacity Unconfigured or unused capacity on the physical drives Number of Physical Drives The number of physical drives in this array Number of Logical Drives The number of logical drives on this array Max Contiguous Free Capacity Unconfigured or unused capacity in contiguous sectors on the physical drives Available RAID Levels RAID levels you can specify on this array
Creating a Disk Array Manually

This feature creates a disk array only. You can also use the Wizard to create a disk array with logical drives and spare drives at the same time. This action requires Super User or Power User privileges. To create a disk array: 1. 2. 3. 4. Click the Storage tab. Click the Disk Array icon. Click the Create Disk Array button. Accept the defaults or make changes: Enter an alias in the Alias field Maximum of 32 characters; letters, numbers, space between characters, and underline. Media Patrol Uncheck to disable on this array. For more information, see Media Patrol on page 259. PDM Uncheck to disable on this array. For more information, see PDM on page 259. Power management Uncheck to disable on this array.
122
Choose a media type Hard disk drive (HDD) or solid state drive (SSD) You cannot mix drive types in the same array.
5.
In the Select Physical Drives diagram, click the drives to add them to your array. The ID numbers of the chosen drives appear in the field below the diagram. When you have finished your settings and choices, click the Submit button. The new array appears in the list. If you are done creating disk arrays, click the Finish button. To create additional disk arrays, click the Create More button. After you create a disk array, create a logical drive on it. See Creating a Logical Drive Manually on page 135.
6.
Creating a Disk Array with the Wizard

The Wizard creates disk arrays and logical drives automatically. It has three options. Automatic Creates a new disk array following a default set of parameters. Creates a hot spare drive for all RAID levels except RAID 0, when five or more unconfigured physical drives are available. You can accept or reject the proposed arrangement but you cannot modify it. Express You choose the parameters for a new disk array by specifying the characteristics you want. You can create multiple logical drives at the same time, however they are all identical. Creates a hot spare drive for all RAID levels except RAID 0. Advanced Enables you to specify all parameters for a new disk array, logical drives and spare drives.
Wizard: Automatic Configuration

This option proposes a disk array and logical drive arrangement. You can accept or reject the proposed arrangement but you cannot modify it. This action requires Super User or Power User privileges. To use the Automatic Configuration Wizard: 1. 2. 3. Click the Storage tab. Click the Wizard icon. Click the Automatic button. When you choose the Automatic option, the following parameters appear on the screen:
123
Disk Arrays The number of logical drives, number of physical drives, ID of each physical drive, configurable capacity, and the media type (hard disk drives or solid state drives). Logical Drives The ID numbers of the logical drives, their RAID levels, capacity, sector size, and stripe size. Spare Drives The ID numbers of the logical drives, type (global or dedicated) revertible option (enabled or disabled) and media type. A hot spare drive is created for all RAID levels except RAID 0, when five or more unconfigured physical drives are available.
4. 5.
To accept the proposed configuration, click the Submit button. Click the Finish button to clear the Automatic Configuration box. Note If you disagree with the proposed configuration, click the Cancel button, then click the Express button or the Advanced button and input your parameters manually.
Wizard: Express Configuration

When you choose the Express option, a set of characteristics and options appears on the screen. This action requires Super User or Power User privileges. To use the Express Configuration Wizard: 1. 2. 3. 4. Click the Storage tab. Click the Wizard icon. Click the Express button. Check the boxes to choose any one or a combination of: Redundancy The array remains available if a physical drive fails. Capacity The greatest possible amount of data capacity. Performance The highest possible read/write speed. Spare Drive A hot spare drive is created when you choose Redundancy, Spare Drive, and five or more unconfigured physical drives are available. Mixing SATA/SAS Drive Check this box if you want to use both SATA and SAS drives in the same disk array. If the box is unchecked, and you have both SATA and SAS drives, a separate array is created for each type of drive. 5. In the Number of Logical Drives field, enter the number of logical drives you want to make from this disk array.
124
VTrak supports up to 32 logical drives per disk array. 6. From the Application Type menu, choose an application that best describes your intended use for this disk array: 7. File Server Video Stream Transaction Data Transaction Log Other
Click the Next button to continue. The Summary screen appears with information on disk arrays, logical drives, and spare drives you are about to create.
8. 9.
To accept the proposed configuration, click the Submit button. Click the Finish button to clear the Express Configuration box. Note If you disagree with the proposed configuration, review and modify your selections in the previous steps.
Wizard: Advanced Configuration

This option enables you to directly specify all parameters for a new disk array, logical drives, and spare drives. This action requires Super User or Power User privileges. To use the Advanced Configuration Wizard: 1. 2. 3. Click the Storage tab. Click the Wizard icon. Click the Advanced button. The Create Disk Array screen displays. Task 1 Disk Array Creation To create your disk array: 1. Accept the defaults or make changes: Enter an alias in the Alias field. Media Patrol Uncheck to disable on this array. For more information, see Media Patrol on page 259. PDM Uncheck to disable on this array. For more information, see PDM on page 259. Power management Uncheck to disable on this array
125
2.
Choose a media type Hard disk drive (HDD) or solid state drive (SSD)
Mouse-over the enclosure graphic to view information about physical drives. Look for drives with a green LED dark, a blue LED lit, and no crosshatching over the carrier. Green LED dark Blue LED lit
3. 4.
Click a physical drive to select it for your array. The physical drives ID number is added to the Selected list. Click the Next button to continue. The Create Logical Drive screen displays.
Task 2 Logical Drive Creation To create your logical drive: 1. Enter your information and choose your options. Enter a logical drive alias in the field provided Choose a RAID level from the dropdown menu. Note the Max: capacity value. Then enter a capacity value the field provided and choose a unit of measure from the dropdown menu. Choose a Stripe size. 64 KB, 128 KB, 256 KB, 512 KB, and 1 MB are available. Choose a Sector size. 512 B, 1 KB, 2 KB, and 4 KB are available. Choose a Read (cache) Policy. The choices are Read Cache, Read Ahead (cache), and None. Choose a Write (cache) Policy. The choices are WriteThru (write through) and WriteBack. Write back requires a Read Cache or Read Ahead Read Cache Policy. RAID 6 and 60 only. Choose a scheme from the dropdown menu. The choices are P+Q and Q+Q. If in doubt, use the default P+Q. Choose a preferred controller ID from the dropdown menu. The choices are Controller 1, Controller 2, and Automatic. If in doubt, use the default Automatic. 2. Click the Add button. The new logical drive appears on the list at the right.
126
If there is capacity remaining, you can create an additional logical drive. 3. Click the Next button to continue. The Create Spare Drive screen displays. Task 3 Spare Drive Creation To create your spare drive: 1. For each of the following items, accept the default or change the settings as required: Check the Revertible box if you want a revertible spare drive. A revertible spare drive returns to its spare drive assignment after you replace the failed physical drive in the disk array and run the Transition function. 2. Global Can be used by any disk array Dedicated to newly created disk array The disk array you are now creating.
In the Select Physical Drives diagram, click a drive to choose it for your spare. The ID number for chosen drive appears in the field below the diagram. Click the Next button. The Summary screen displays.
3.
Task 4 Summary Review your choices of disk array, logical drives, and spare drive. To make a change, click the Back button to reach the appropriate screen. To accept, click the Submit button.
Click the Finish button to clear the Summary screen.
Deleting a Disk Array

Caution If you delete a disk array, you also delete any logical drives that belong to it, along with the data in those logical drives. Back up any important data before deleting a disk array. This action requires Administrator or Super User privileges. To delete a disk array: 1. 2. Click the Storage tab. Click the Disk Array icon.
127
3. 4.
Mouse-over the disk array you want and click the Delete button. In the Confirmation box, type the word confirm in the field provided and click the Confirm button.
Making Disk Array Settings

To make disk array settings: 1. 2. 3. 4. Click the Storage tab. Click the Disk Array icon. The list of disk arrays appears. Mouse-over the disk array you want and click the Settings button. Make setting changes as required: Enter, change or delete the alias in the Alias field Maximum of 32 characters; letters, numbers, space between characters, and underline. 5. Media Patrol Check to enable, uncheck to disable on this array. PDM Check to enable, uncheck to disable on this array. Power Management Check to enable, uncheck to disable on this array.
Click the Save button. Note You can also enable or disable Media Patrol for the entire RAID system. See Making Media Patrol Settings on page 94. Notes HDD Power Saving must be enabled on the RAID controller for the Power Management settings to be effective. See Making Controller Settings on page 70. Power Management functions are limited to the features your HDDs actually support.
Locating a Disk Array

This feature causes the drive carrier LEDs to flash for one minute to assist you in locating the physical drives that make up this disk array. To locate a disk array: 1. Click the Storage tab.
128
2. 3.
Click the Disk Array icon. The list of disk arrays appears. Mouse-over the disk array you want and click the Locate button. The drive carrier LEDs flash for one minute. Green LEDs flash
Running Media Patrol on a Disk Array

Media Patrol is a routine maintenance procedure that checks the magnetic media on each disk drive. If Media Patrol encounters a critical error, it triggers PDM if PDM is enabled on the disk array. For more information, see Media Patrol on page 94 and page 259. Also see PDM on page 97 and page 259.
Running Media Patrol

To run Media Patrol: 1. 2. 3. Click the AdminTool tab. Click the Background Activities icon. The list of background activities appears. Mouse-over Media Patrol and click the Start button.
Stopping, Pausing or Resuming Media Patrol

To stop, pause or resume Media Patrol: 1. 2. 3. Click the AdminTool tab. Click the Background Activities icon. The list of background appears. Mouse-over Media Patrol and click the Stop, Pause or Resume button.
Running PDM on a Disk Array

Predictive Data Migration (PDM) is the migration of data from the suspect disk drive to a spare disk drive. For more information PDM on page 97 and page 259.
Running PDM
To run PDM on a disk array: 1. Click the AdminTool tab.
129
2. 3. 4. 5. 6.
Click the Background Activities icon. The list of background activities appears. Mouse-over PDM and click the Start button. From the Source Physical Drive dropdown menu, choose a Source disk array and physical drive. From the Target Physical Drive dropdown menu, choose a Target physical drive. Click the Confirm button.
Stopping, Pausing or Resuming PDM

To stop, pause or resume PDM: 1. 2. 3. Click the AdminTool tab. Click the Background Activities icon. The list of background activities appears. Mouse-over PDM and click the Stop, Pause, or Resume button.
You can also enable or disable PDM on individual disk arrays. See Making Disk Array Settings on page 128.
Preparing a Disk Array for Transport

This feature prepares the physical drives that make up the disk array to be removed from the enclosure and installed in a different location. To prepare a disk array for transport: 1. 2. 3. 4. 5. Click the Storage tab. Click the Disk Array icon. The list of disk arrays appears. Mouse-over the disk array you want and click the Transport button. Click the Confirm button. The status changes to Transport Ready. Remove the physical drives and install them in their new location. See the Installing Physical Drives on page 19 for more information.
Rebuilding a Disk Array

When you rebuild a disk array, you are actually rebuilding the data on one physical drive. If there is no spare drive of adequate capacity and the Auto Rebuild function is DISABLED, you must replace the failed drive with an unconfigured physical
130
drive, then perform a Manual Rebuild. See Making Rebuild Settings on page 96 Important If your replacement disk drive was formerly part of a different disk array or logical drive, you must clear the configuration data on the replacement drive before you use it. See Clearing a Stale or a PFA Condition on page 120.
Performing a Manual Rebuild

To perform a manual rebuild: 1. 2. 3. 4. Click the AdminTool tab. Click the Background Activities icon. The list of background activities appears. Mouse-over Rebuild and click the Start button. From the Source Physical Drive dropdown menu, choose a Source disk array and physical drive. Arrays have an ID No. Physical drives have a Seq. No.(sequence number) 5. 6. From the Target Physical Drive dropdown menu, choose a Target physical drive. Click the Confirm button.
Stopping, Pausing or Resuming a Rebuild

To stop, pause or resume a Rebuild: 1. 2. 3. Click the AdminTool tab. Click the Background Activities icon. The list of background appears. Mouse-over Rebuild and click the Stop, Pause, or Resume button.
131
Managing Logical Drives

Logical drive management includes: Viewing a List of Logical Drives (below) Viewing Logical Drive Information (page 132) Viewing Logical Drive Statistics (page 133) Viewing Logical Drive Check Tables (page 134) Creating a Logical Drive Manually (page 135) Deleting a Logical Drive (page 136) Making Logical Drive Settings (page 136) Locating a Logical Drive (page 137) Locating a Logical Drive (page 137) Initializing a Logical Drive (page 137) Redundancy Check on a Logical Drive (page 138) Migrating a Logical Drives RAID Level (page 139)
Also see Disk Array and Logical Drive Problems (page 317).
Viewing a List of Logical Drives

To view a list of logical drives: 1. 2. Click the Storage tab. Click the Logical Drive icon. The list of logical drives appears. Logical Drive information includes: ID LD0, LD1, LD2, etc. Alias If assigned. Status A green check icon means OK. Capacity Data capacity of the logical drive. RAID Level Set when the logical drive was created. Stripe Set when the logical drive was created. Cache Policy Read cache and Write cache settings. Array ID ID number of the disk array where this logical drive was created.
Viewing Logical Drive Information

To view logical drive information: 1. Click the Storage tab.
132
2. 3.
Click the Logical Drive icon. The list of logical drives appears. Mouse-over the logical drive you want and click the View button. Logical Drive information displays, including: ID LD0, LD1, LD2, etc. Alias If assigned Array ID - ID number of the disk array where this logical drive was created RAID Level Set when the logical drive was created Operational Status OK means normal Capacity Data capacity of the logical drive Number of Axles For RAID 10, 2 axles. For RAID 50 and 60, 2 or more axles Physical Capacity Data capacity of the physical drives Number of Physical Drives The number of physical drives in the disk array Stripe size Set at logical drive creation Read Policy Adjustable Sector size Set at logical drive creation Write Policy Adjustable Preferred Controller ID For RAID subsystems with dual controllers Tolerable Number of Dead Drives Number of physical drives that can fail without the logical drive going offline Synchronized A new logical drive shows No until synchronizing is completed. See Synchronization on page 98 Parity Pace Pertains to some RAID levels WWN Worldwide Number, a unique identifier assigned to this logical drive Codec Scheme Pertains to some RAID levels Serial Number Assigned to this logical drive
Viewing Logical Drive Statistics

To view logical drive statistics: 1. 2. 3. Click the Storage tab. Click the Logical Drive icon. The list of logical drives appears. Mouse-over the logical drive you want and click the View button.
133
4.
Click the Statistics tab. Logical Drive statistics display, including: Data Transferred In bytes Read Data Transferred In bytes Write Data Transferred In bytes Errors Read Errors Write Errors I/O Requests Non-Read/Write I/O Requests Read I/O Requests Write I/O Requests Statistics Start Time Statistics Collection Time
To clear physical drive statistics, see Clearing Statistics on page 63.
Viewing Logical Drive Check Tables

This feature enables you to view error tables. Use this information to evaluate the integrity of the logical drive and to determine whether corrective action is needed. To view logical drive check tables: 1. 2. 3. 4. Click the Storage tab. Click the Logical Drive icon. The list of logical drives appears. Mouse-over the logical drive you want and click the Check Table button. Choose an option: All All errors. The default choice. Read Check Read errors for this logical drive. Write Check Write errors for this logical drive. Inconsistent Block Inconsistent blocks for this logical drive. Mirror data for RAID Levels 1, 1E and 10 or Parity data for RAID Levels 5, 6, 50, and 60. Identified by the Redundancy Check. Entry Number A number assigned to each block of entry. Table Type Read Check, Write Check or Inconsistent Block. Start Logical Block Address LBA of the first block for this entry. Count Number of errors or continuous blocks starting from this LBA.
134
The Check Table lists:
To clear the check tables, see Clearing Statistics on page 63.
Creating a Logical Drive Manually

This feature creates a logical drive only. You can also use the Wizard to create a disk array with logical drives and spare drives at the same time. See Creating a Disk Array with the Wizard on page 123. This action requires Super User or Power User privileges. To create a logical drive manually: 1. 2. 3. 4. 5. Click the Storage tab. Click the Logical Drive icon. Click the Create Logical Drive button. Click the option button of the disk array you want to use and click the Next button. Optional. Enter an alias in the Alias field. Maximum of 32 characters; letters, numbers, space between characters, and underline. 6. Choose a RAID level. The choice of RAID levels depends the number of physical drives in the disk array. 7. 8. RAID 50 and 60 only. Specify the number of axles for your array. In the Capacity field, accept the default maximum capacity or enter a lesser capacity and size in MB, GB or TB. Any remaining capacity is available for an additional logical drive. 9. For each of the following items, accept the default or change the settings as required: Choose a Stripe size. 64 KB, 128 KB, 256 KB, 512 KB, and 1 MB are available. Choose a Sector size. 512 B, 1 KB, 2 KB, and 4 KB are available. Choose a Read (cache) Policy. Read Cache, Read Ahead, and No Cache are available. Choose a Write (cache) Policy. Write Back and Write Through (Thru) are available. 10. Click the Add button. The new logical drive appears on the list at the right. If there is capacity remaining, you can create an additional logical drive.
135
11. When you are finished, click the Submit button. The new logical drive or drives appear in the logical drive list. New logical drives are automatically synchronized. See Synchronization on page 98. You can access the logical drive during synchronization.
Deleting a Logical Drive

Caution If you delete a logical drive, you also delete all the data in the logical drive. Back up any important data before deleting the logical drive. This action requires Administrator or Super User privileges. To delete a logical drive: 1. 2. 3. 4. Click the Storage tab. Click the Logical Drive icon. Mouse-over the logical drive you want and click the Delete button. In the Confirmation box, type the word confirm in the field provided and click the Confirm button.
Making Logical Drive Settings

To make logical drive settings: 1. 2. 3. 4. Click the Storage tab. Click the Logical Drive icon. The list of logical drives appears. Mouse-over the logical drive you want and click the Settings button. Make setting changes as required: Enter, change, or delete the alias in the Alias field. Maximum of 32 characters; letters, numbers, space between characters, and underline. 5. Choose a Read (cache) Policy. Read Cache, Read Ahead, and No Cache are available. Choose a Write (cache) Policy. Write Back and Write Through (Thru) are available. Click the Save button.
136
For more information, see Cache Policy on page 289. Note The Write Cache is always set to WriteThru when Read Cache is set to NoCache.
Locating a Logical Drive

This feature causes the drive carrier LEDs to flash for one minute to assist you in locating the physical drives that make up this logical drive. To locate a logical drive: 1. 2. 3. Click the Storage tab. Click the Logical Drive icon. The list of logical drives appears. Mouse-over the logical drive you want and click the Locate button. The drive carrier LEDs flash for one minute.Locating a logical drive. Green LEDs flash
Initializing a Logical Drive

Initialization is normally done to logical drives after they are created from a disk array. Warning When you initialize a logical drive, all the data on the logical drive is lost. Backup any important data before you initialize a logical drive. To initialize a logical drive: 1. 2. 3. 4. 5. Click the AdminTool tab. Click the Background Activities icon. The list of background activities appears. Mouse-over Initialization and click the Start button. Check the box to the left of the logical drive you want to initialize. Choose the initialization option you want:
137
Quick Initialization Check the box and enter a value in the Quick Initialization Size field. This value is the size of the initialization blocks in MB. Full Initialization Do not check the box. Enter a hexadecimal value in the Initialization Pattern in Hex field or use the default 00000000 value.
6.
Stopping, Pausing or Resuming an Initialization

To stop, pause or resume Initialization: 1. 2. 3. Click the AdminTool tab. Click the Background Activities icon. The list of background activities appears. Mouse-over Initialization and click the Stop, Pause, or Resume button.
Redundancy Check on a Logical Drive

Redundancy Check is a routine maintenance procedure for fault-tolerant disk arrays (those with redundancy) that ensures all the data matches exactly. Redundancy Check can also correct inconsistencies. To run Redundancy Check on a logical drive: 1. 2. 3. 4. 5. Click the AdminTool tab. Click the Background Activities icon. The list of background activities appears. Mouse-over Redundancy Check and click the Start button. Check the boxes to the left of the logical drives you want to run. Check the options you want: 6. Auto Fix Attempts to repair the problem when it finds an error Pause on Error The process stops when it finds a non-repairable error
Stopping, Pausing or Resuming a Redundancy Check

To stop, pause or resume Redundancy Check: 1. 2. 3. Click the AdminTool tab. Click the Background Activities icon. The list of background activities appears. Mouse-over Redundancy Check and click the Stop, Pause, or Resume button.
138
Migrating a Logical Drives RAID Level

Before you begin a migration, examine your current disk array to determine whether: The physical drives in your array can support the target RAID level. There is sufficient capacity to accommodate the target logical drive size.
If you need to add physical drives to your array, be sure there are unassigned physical drives are installed in your RAID system before you begin migration. See Migration on page 96, RAID Levels on page 261 and RAID Level Migration on page 275.
Migrating a Logical Drive

To migrate a logical drive: 1. 2. 3. 4. 5. Click the AdminTool tab. Click the Background Activities icon. The list of background activities appears. Mouse-over Migrate and click the Start button. In the Select Disk Array dropdown menu, choose the source disk array. In the Select Physical Drives diagram, click the drives to add them to your array. The ID numbers of the chosen drives appear in the field below the diagram. 6. 7. 8. Click the Next button. Check the box next to the logical drive you want to modify. From the dropdown menu, choose a target RAID level. The choice of RAID levels depends the number of physical drives in the disk array. See the Note below. 9. In the Capacity field, accept the current capacity. Or check the Expand Capacity box and enter a greater capacity and size in MB, GB or TB. If there is capacity remaining, you can create an additional logical drive. 10. Click the Next button. The logical drive ID numbers, with the original and target RAID levels and capacities are shown
139
11. To accept the proposed target values, click the Confirm button. Note When you add physical drives to a RAID 10 array, it becomes a RAID 1E array by default. If you are adding an even number of physical drives to a RAID 10 array and you want the target array to be RAID 10, you must specify RAID 10 under RAID level.
140
Managing Spare Drives

Spare drive management includes: Viewing a List of Spare Drives (below) Viewing Spare Drive Information (page 141) Creating a Spare Drive Manually (page 142) Creating a Spare Drive with the Wizard, see Creating a Disk Array with the Wizard on page 123 Deleting a Spare Drive (page 143) Making Spare Drive Settings (page 143) Locating a Spare Drive (page 143) Running Spare Check (page 144) Running a Transition on a Spare Drive (page 144)
Viewing a List of Spare Drives

To view a list of spare drives: 1. 2. Click the Storage tab. Click the Spare Drive icon. Spare Drive information displays, including: ID Spare0, Spare1, etc. Operational Status OK means normal Configurable Capacity Usable capacity of the spare drive Physical Drive ID ID number of the physical drive chosen for this spare Revertible Yes or No Spare Type Global or Dedicated Dedicated to Array ID number of the disk array to which the spare is dedicated
Viewing Spare Drive Information

To view spare drive information: 1. 2. 3. Click the Storage tab. Click the Spare Drive icon. The list of spare drives appears. Mouse-over the spare drive you want and click the View button. Spare Drive information displays, including: Spare Drive ID Spare0, Spare1, etc.
141
Physical Drive ID ID number of the physical drive chosen for this spare Operational Status OK means normal Spare Type Global or Dedicated Physical Capacity Total data capacity of the spare drive Revertible Yes or No Configurable Capacity Usable capacity of the spare drive Spare Check Status Not Checked or Healthy Media Patrol Enabled or Not Enabled Dedicated to Array ID number of the disk array to which the spare is dedicated
For more information, see Spare Drives on page 283.
Creating a Spare Drive Manually

This feature creates a spare drive only. You can also use the Wizard to create a disk array with logical drives and spare drives at the same time. See Spare Drives for more information. This action requires Super User or Power User privileges. To create a spare drive: 1. 2. 3. 4. Click the Storage tab. Click the Spare Drive icon. Click the Create Spare Drive button. For each of the following items, accept the default or change the settings as required: Check the Revertible box if you want a revertible spare drive. A revertible spare drive returns to its spare drive assignment after you replace the failed physical drive in the disk array and run the Transition function. 5. Global Can be used by any disk array Dedicated to newly created disk array The disk array you are now creating.
In the Select Physical Drives diagram, click a drive to choose it for your spare. The ID number for chosen drive appears in the field below the diagram. Click the Submit button. If you are done creating spare drives, click the Finish button. To create another spare drive, click the Create More button.
142
6.
Deleting a Spare Drive

This action requires Administrator or a Super User privileges. To delete a spare drive: 1. 2. 3. 4. Click the Storage tab. Click the Spare Drive icon. Mouse-over the spare drive you want and click the Delete button. In the Confirmation box, type the word confirm in the field provided and click the Confirm button.
Making Spare Drive Settings

For more information on settings options, see Spare Drives on page 283. To make spare drive settings: 1. 2. 3. 4. Click the Storage tab. Click the Spare Drive icon. Mouse-over the spare drive you want and click the Settings button. For each of the following items, accept the default or change the settings as required: 5. In the Revertible dropdown menu, choose Yes or No. Check the Media Patrol box to enable Media Patrol on this spare drive. Uncheck to disable. In the Spare Type dropdown menu, choose Global or Dedicated. If you use chose a Dedicated spare, check the box beside the disk array to which this spare drive is assigned.
Locating a Spare Drive

Spare drives are located the same as individual physical drives. To locate a spare drive: 1. 2. 3. 4. 5. Click the Storage tab. Click the Spare Drive icon. The list of spare drives appears. In the spare drive list, identify the physical drive ID number. Click the Device tab. Click the Physical Drive icon. The list of physical drives appears.
143
6.
Mouse-over the physical drive with the matching ID number and click the Locate button. The drive carrier LED blinks for one minute. Green LEDs flash
Running Spare Check

Spare Check verifies the status of your spare drives. To run spare check: 1. 2. 3. 4. Click the Storage tab. Click the Spare Drive icon. The list of spare drives appears. Mouse-over the spare drive you want and click the Spare Check button. Click the Confirm button. After the Spare Check completed message appears, click the View button to see Spare Check Status.
Running a Transition on a Spare Drive

Transition is the process of replacing a revertible spare drive that is currently part of a disk array with an unconfigured physical drive or a non-revertible spare. You must specify an unconfigured physical drive of the same or larger capacity and same media type as the revertible spare drive. See Transition on page 98 and page 284.
Running a Transition
To run a transition on a revertible spare drive: 1. 2. 3. 4. Click the AdminTool tab. Click the Background Activities icon. The list of background activities appears. Mouse-over Transition and click the Start button. From the Source Physical Drive dropdown menu, choose a Source disk array and the revertible spare drive. Arrays have an ID No. The revertible spare has a Seq. No. (sequence number).
144
5. 6.
From the Target Physical Drive dropdown menu, choose a Target unconfigured drive. Click the Confirm button.
Stopping, Pausing or Resuming a Transition

To stop, pause or resume Transition: 1. 2. 3. Click the AdminTool tab. Click the Background Activities icon. The list of background activities appears. Mouse-over Transition and click the Stop, Pause, or Resume button.
145
Managing LUNs and Initiators

LUN and initiator management includes: Viewing a List of LUN Maps (below) LUN Mapping and Masking (page 146) Adding a LUN Map (page 146) Editing a LUN Map (page 147) Deleting a LUN Map (page 147) Enabling and Disabling LUN Masking (page 148) Viewing a List of Initiators (page 148)
Viewing a List of LUN Maps

To view a list of LUN maps: 1. 2. Click the AdminTool tab. Click the LUN Mapping & Masking icon. The list of LUN maps appears.
LUN Mapping and Masking

This feature applies to Fibre Channel and SAS subsystems and controls user access to storage resources. 1. 2. LUN Mapping Maps LUNs to an initiators, so that the initiator can only access only the specified LUNs. LUN Masking The process of applying a LUN Map. Click the AdminTools tab. Click the LUN Masking & Mapping icon. On this screen, you can: Add an FC or SAS initiator to the VTrak's initiator list. Enable LUN masking. Map a LUN to one or more initiators.
To access LUN mapping:
Adding a LUN Map

LUN masking must be enabled in order to assign LUNs to logical drives. At least one initiator is required to create a LUN map. You can add FC or SAS initiators from a list. Or input the initiator address manually.
146
To add a LUN map: 1. 2. 3. 4. 5. 6. 7. 8. Click the AdminTool tab. Click the LUN Mapping & Masking icon. Click the LUN Mapping button. The first LUN Mapping screen appears. Choose an initiator from the Select Initiator dropdown list. Or choose All Initiators from the list. Click the Next button. The second LUN Mapping screen appears. Drag a logical drive from the Logical Drive list and drop it onto the Initiator list. Click the Next button. The final LUN Mapping screen appears showing the initiator and LUN map. Click the Submit button. The new LUN map is created.
Editing a LUN Map

Editing a LUN map is the action of assignment of a logical drive or LUN to an initiator. By changing the assignment, you change the initiator's access. To edit a LUN map: 1. 2. 3. 4. 5. 6. Click the AdminTool tab. Click the LUN Mapping & Masking icon. The list of LUN maps appears. Mouse-over the LUN map you want and click the Setting button. Drag a logical drive from the Logical Drive list and drop it onto the Initiator list. Click the Next button. The LUN Mapping screen shows the edited LUN map. Click the Submit button.
Deleting a LUN Map

Deleting a LUN map prevents the initiator from accessing the LUN while LUN masking is enabled. This action requires Administrator or Super User privileges. To delete a LUN map: 1. Click the AdminTool tab.
147
2. 3. 4.
Click the LUN Mapping & Masking icon. The list of LUN maps appears. Mouse-over the LUN map you want and click the Delete button. In the Confirmation box, type the word confirm in the field provided and click the Confirm button.
Enabling and Disabling LUN Masking

LUN masking must be enabled in order to assign LUNs to logical drives. Disabling LUN masking allows all initiators to access all LUNs in your data storage. However, it does not delete existing LUN maps. These actions require Administrator or Super User privileges. To enable or disable LUN masking: 1. 2. 3. Click the AdminTool tab. Click the LUN Mapping & Masking icon. Check the box to enable LUN Masking. Or uncheck the box to disable LUN Masking. LUN Masking starts or stops as soon as you make your setting.
Viewing a List of Initiators

The VTraks initiator list displays initiators available for use to create a LUN for your logical drive. To view a list of initiators: 1. 2. Click the AdminTool tab. Click the Initiator icon. The list of initiators appears. Initiator information includes: Index number Initiator 0, Initiator 1, Initiator 2, etc. WWPN Worldwide Port Number of the port where this initiator is connected
Click the Add Initiator button to add more initiators. See also Adding an FC Initiator on page 152 and
148
Managing Fibre Channel Connections

Fibre Channel management includes: Viewing FC Node Information (below) Viewing FC Port Information (page 149) Making FC Port Settings (page 150) Viewing FC Port Statistics (page 151) Viewing a List of FC Initiators on the Fabric (page 151) Viewing a List of FC Logged-in Devices (page 151) Viewing a List of FC SFPs (page 151) Adding an FC Initiator (page 152) Deleting an FC Initiator (page 152)
Viewing FC Node Information

To view Fibre Channel node information: 1. 2. 3. Click the Device tab. Click the FC Management icon. Click the Node tab. Node information includes: Worldwide Node Number (WWNN) Maximum Frame Size Supported FC Class Supported speeds
Viewing FC Port Information

To view Fibre Channel port information: 1. 2. 3. 4. Click the Device tab. Click the FC Management icon. Click the Port tab. Mouse-over an FC port to access and click the View button. Port information includes: FC Port ID number Controller ID number Identifier (hexadecimal) Link status Hard ALPA
149
Worldwide Port Number (WWPN)
Making FC Port Settings

To make Fibre Channel port settings: 1. 2. 3. 4. 5. Click the Device tab. Click the FC Management icon. Click the Port tab. Mouse-over the FC port you want to access and click the Settings button. Make these changes as required: 6. Choose a configured link speed from the dropdown menu. The choices are Auto (default), 2 Gb/s, 4 Gb/s, and 8 Gb/s. Choose a topology from the dropdown menu. Enter a Hard ALPA in the field provided. Enter 255 to disable Hard ALPA. Click the Save button.
Port Setting Information

The table below shows the type of attached topology you achieve based on your connection type and the configured topology you select. Fibre Channel Attached Topology Configured Topology Connection Type Switch Direct N-Port Fabric Direct Point-to-Point NL-Port Public Loop Private Loop
Example 1: If you connect the VTrak to an FC switch and choose NL-Port topology, you create a Public Loop attached topology. Example 2: If you have a Point-to-Point attached topology, you made a direct connection (no FC switch) and selected N-port topology. Note In some cases, HBA settings to N-Port only work if connected to the switch. Refer to your HBA manual for more information.
150
Viewing FC Port Statistics

To view Fibre Channel port statistics: 1. 2. 3. 4. Click the Device tab. Click the FC Management icon. Click the Statistics tab. Mouse over the FC port you want to access and click the View button.
To clear FC port statistics, see Clearing Statistics on page 63.
Viewing a List of FC Initiators on the Fabric

To view a list Fibre Channel initiators on the fabric: 1. 2. 3. Click the Device tab. Click the FC Management icon. Click the Initiators on Fabric tab.
Viewing a List of FC Logged-in Devices

Logged-in devices refers to all Fibre Channel devices currently logged into the VTrak. The device list includes: FC ports FC switches, if attached FC initiators
To view a list FC logged-in devices: 1. 2. 3. Click the Device tab. Click the FC Management icon. Click the Logged In Device tab.
Viewing a List of FC SFPs

The term SFP refers to Small Form Pluggable transceivers used in Fibre Channel ports. The SFPs convert electrical signals to optical signals and send them over the Fibre Channel fabric, where another transceiver converts the optical signal back to an electrical signal again. To view a list FC SFPs: 1. 2. 3. Click the Device tab. Click the FC Management icon. Click the SFP tab. SFP information includes: FC port ID
151
Controller ID Connector type Transceiver type Transceiver code Vendor name
Adding an FC Initiator
You must add an initiator to the VTraks initiator list in order to use the initiator to create a LUN for your logical drive. To add a Fibre Channel initiator from a list: 1. 2. 3. 4. 5. Click the Device tab. Click the FC Management icon. Click the Initiators on Fabric tab. Check the box to the left of the initiator you want to add. Click the Add to Initiator List button. The initiator is added, and its check box grays out.
Deleting an FC Initiator
Caution If you delete an initiator, you delete the LUN associated with that initiator. Verify that the LUN is no longer needed before deleting the initiator. This action requires Administrator or Super User privileges. To delete an initiator: 1. 2. 3. 4. Click the AdminTool tab. Click the Initiator icon. Mouse-over the initiator you want and click the Delete button. In the Confirmation box, type the word confirm in the field provided and click the Confirm button. The initiator is removed from VTraks initiator list.
152
Managing SAS Connections

SAS management includes: Viewing SAS Port Information (below) Viewing SAS Port Statistics (page 153) Making SAS Port Settings (page 153) Viewing a List of SAS Initiators (page 154) Viewing a List of SAS Initiators (page 154) Adding a SAS Initiator (page 154) Deleting a SAS Initiator (page 154)
Viewing SAS Port Information

To view SAS port information: 1. 2. 3. 4. Click the Device tab. Click the SAS Management icon. Click the Information tab. Mouse over the SAS port you want to access and click the View button.
Viewing SAS Port Statistics

To view SAS port statistics: 1. 2. 3. 4. Click the Device tab. Click the SAS Management icon. Click the Statistics tab. Mouse over the SAS port you want to access and click the View button.
To clear SAS port statistics, see Clearing Statistics on page 63.
Making SAS Port Settings

To make settings on the SAS ports: 1. 2. 3. 4. Click the Device tab. Click the SAS Management icon. Mouse over the SAS port you want to access and click the Settings button. Enter a value in the Cable Signal Strength field. The range is 1 to 8. 1 is the default. Signal strength correlates to cable length in meters. Example: If you have a 2 m SAS cable, set signal strength to 2. If performance is unsatisfactory (see Viewing SAS Port Statistics above), try settings of 1 and 3, then use the best setting for your system. 5. Click the Save button.
153
Viewing a List of SAS Initiators

To view SAS port initiators: 1. 2. 3. Click the Device tab. Click the SAS Management icon. Click the Initiators tab.
Adding a SAS Initiator

You must add an initiator to the VTraks initiator list in order to use the initiator to create a LUN for your logical drive. To add a SAS initiator: 1. 2. 3. 4. 5. Click the Device tab. Click the SAS Management icon. Click the Initiators tab. Check the box to the left of the initiator you want to add. Click the Add to Initiator List button. The initiator is added, and its check box grays out.
Deleting a SAS Initiator

Caution If you delete an initiator, you delete the LUN associated with that initiator. Verify that the LUN is no longer needed before deleting the initiator. This action requires Administrator or Super User privileges. To delete an initiator: 1. 2. 3. 4. Click the AdminTool tab. Click the Initiator icon. Mouse-over the initiator you want and click the Delete button. In the Confirmation box, type the word confirm in the field provided and click the Confirm button. The initiator is removed from VTraks initiator list.
154
Chapter 5: Management with the CLU

This chapter covers the following topics: Initial Connection (page 156) Running Quick Setup (page 161) Managing the Subsystem (page 162) Managing the Controllers (page 166) Managing the Enclosure (page 170) Managing Physical Drives (page 176) Managing Disk Arrays (page 180) Managing Spare Drives (page 193) Managing Logical Drives (page 196) Managing the Network Connection (page 200) Managing Fibre Channel Connections (page 202) Managing SAS Connections (page 206) Managing Background Activity (page 208) Working with the Event Viewer (page 210) Working with LUN Mapping (page 212) Managing UPS Units (page 214) Managing Users (page 217) Working with Software Management (page 221) Flashing through TFTP (page 229) Viewing Flash Image Information (page 230) Clearing Statistics (page 231) Restoring Factory Defaults (page 232) Shutting Down the Subsystem (page 233) Starting Up After Shutdown (page 235) Restarting the Subsystem (page 237) Making Buzzer Settings (page 239)
For information about the VTrak audible alarm and LEDs, see Chapter 8: Troubleshooting on page 307.
155
Initial Connection
Making an initial connection includes the following functions: Making a Serial Connection (page 156) Making a Telnet Connection (page 157) Making a SSH Connection (page 157) Logging Into the CLI (page 158) Accessing Online Help (page 159) Exiting the CLU (page 159) Logging Out of the CLI (page 160) Logging Back Into the CLI and CLU (page 160)
Making a Serial Connection

Before you begin, be sure the RJ11-to-DB9 serial data cable is connected between the Host PC and VTrak, and that both machines are booted and running. Figure 1. Serial port on the controller Serial port
Then do the following actions: 1. Change your terminal emulation program settings to match the following specifications: 2. 3. Bits per second: 115200 Data bits: 8 Parity: None Stop bits: 1 Flow control: none
Start your PCs terminal VT100 or ANSI emulation program. Press Enter once to launch the CLI.
156
Making a Telnet Connection

A Telnet connection requires a network connection between the Host PC and the Management (Ethernet) port on the VTrak controller. Figure 2. Management port on the RAID controller Management port
To start the telnet program: 1. 2. Go to the command line prompt (Windows) or click the terminal icon (Linux). Type telnet 192.168.1.56 2300 and press Enter. The IP address above is only an example. Use the Management port IP address of your VTrak. The Telnet default port number is 2300. 3. Press Enter once to launch the CLI.
Making a SSH Connection

A Secure Shell (SSH) connection requires a network connection between the Host PC and the Management (Ethernet) port on the VTrak controller. See above, Figure 2. Windows PCs require you to install a SSH application on the PC.
Windows
To start the Windows SSH program: 1. 2. Open the SSH application from the Start menu. Enter the IP address and SSH port number of the VTrak in the fields provided. The SSH default port number is 22. 3. Press Enter once to launch the CLI.
Linux
To start the Linux SSH program: 1. 2. Click the terminal icon. Type ssh 192.168.1.56 22 and press Enter.
157
The IP address above is only an example. Use the Management port IP address of your VTrak. The SSH default port number is 22. 3. Press Enter once to launch the CLI.
Logging Into the CLI

1. 2. At the Login prompt, type the user name and press Enter. The default user name is administrator. At the Password prompt, type the password and press Enter. The default password is password. The CLI screen appears. 3. At the administrator@cli> prompt, type menu and press Enter. The CLU Main Menu appears. Figure 4. CLU main menu
Quick Setup A sequence of four steps to setup system date and time, Management port, and RAID configuration. Subsystem Management Subsystem settings, Controller settings, statistics, lock/unlock the subsystem, set date and time, Enclosure settings, FRUs and Topology.
158
Physical Drive Management Assign an alias, force a physical drive offline or online, clear a Stale or PFD condition, change global physical drive settings, and locate a physical drive. Disk Array Management Assign an alias, view array information, create and delete disk arrays, transport, rebuild, PDM, and transition functions, accept and incomplete array, locate a disk array, create, and delete logical drives. Spare Drive Management View a list of spare drives, create, modify, and delete spare drives, and run Spare Check. Logical Drive Management Assign an alias, set cache policies, view logical drive information, run initialization and Redundancy Check, create a LUN clone, and locate a logical drive. Network Management Set IP addresses for Virtual and Maintenance Mode Ports, gateway, and DNS server; subnet mask. Fibre Channel Management Node information, Port information, settings and statistics, list of logged-in devices, list of initiators. SAS Management Node information, Port information, settings, status, and statistics; SFP information, list initiators. Background Activities Summary of running and scheduled activity, settings for Media Patrol, Auto Rebuild, Rebuild, Migration, PDM, Transition, Synchronization, Initialization, Redundancy Check rate, and thresholds. Event Viewer View runtime and NVRAM event logs. Additional Info and Management LUN mapping, UPS management, User management, Software services management, Flash through TFTP (Firmware update), Clear Statistics, Restore Default Settings, Shutdown or Restart the subsystem. Buzzer Enable, disable or silence the buzzer (audible alarm).
Accessing Online Help

To access online help on any CLU screen, press Ctrl-E. To return to the CLU, press Enter.
Exiting the CLU

1. 2. 3. Highlight Return to Previous Menu and press Enter. Repeat this action until you arrive at the Main Menu. From the Main Menu, highlight Return to CLI and press Enter to exit Close the terminal emulation, Telnet, SSH, or terminal window.
159
Logging Out of the CLI

When you shut down or restart the VTrak subsystem, you are automatically logged out of the CLI. To manually log out of the CLI (no shut down or restart): At the username@cli> prompt, type logout and press Enter. The prompt changes to cli>.
Logging Back Into the CLI and CLU

To log into the CLI and CLU after a manual logout: 1. 2. 3. At the cli:> prompt, type login followed by your user name and press Enter. At the Password: prompt, type your password and press Enter. At the username@cli> prompt, type menu and press Enter to open the CLU.
160
Running Quick Setup

Quick Setup is discussed under Setting up VTrak with the CLU on page 39.
161
Managing the Subsystem

Subsystem Management includes the following functions: Making Subsystem Settings (page 162) Running Media Patrol (page 162) Locking or Unlocking the Subsystem (page 163) Setting Subsystem Date and Time (page 163) Making NTP Settings (page 164) Synchronizing with a NTP Server (page 165)
Making Subsystem Settings

An alias is optional. To set an Alias for this subsystem: 1. 2. 3. From the Main Menu, highlight Subsystem Management and press Enter. Highlight Subsystem Settings and press Enter. Make changes as required: Type and alias into the Alias field. Maximum of 48 characters. Use letters, numbers, space between words and underscore. Highlight Redundancy Type and press the spacebar to toggle between Active-Active and Active-Standby. Active-Active Both RAID controllers are active and can share the load Active-Standby One RAID controller is in standby mode and goes active if the other fails 4. Highlight Cache Mirroring and press the spacebar to toggle between Enabled and Disabled.
Running Media Patrol

Media Patrol is a routine maintenance procedure that checks the magnetic media on each disk drive. Media Patrol checks all physical drives assigned to disk arrays and spare drives. It does not check unconfigured drives. To start, stop, pause or resume Media Patrol: 1. 2. 3. 4. From the Main Menu, highlight Subsystem Management and press Enter. Highlight Media Patrol and press enter. Highlight Start, Stop, Pause, or Resume and press Enter. If you chose Stop, press Y to confirm.
162
Locking or Unlocking the Subsystem

The lock prevents other sessions (including sessions with the same user) from making a configuration change to the controller until the lock expires or a forced unlock is done. When the user who locked the controller logs out, the lock is automatically released.
Setting the Lock

To set the lock: 1. 2. 3. 4. From the Main Menu, highlight Subsystem Management and press Enter. Highlight Lock Management and press Enter. In the Lock Time field, type a lock time in minutes. 1440 minutes = 24 hours Highlight Lock and press Enter.
Resetting the Lock

To reset the lock with a new time: 1. 2. 3. 4. From the Main Menu, highlight Subsystem Management and press Enter. Highlight Lock Management and press Enter. In the Lock Time field, type a lock time in minutes. 1 to 1440 minutes (24 hours) Highlight Renew and press Enter.
Releasing the Lock

1. 2. 3. From the Main Menu, highlight Subsystem Management and press Enter. Highlight Lock Management and press Enter. Highlight Unlock and press Enter.
Releasing a Lock set by another user

To release somebody elses lock: 1. 2. 3. 4. From the Main Menu, highlight Subsystem Management and press Enter. Highlight Lock Management and press Enter. Highlight Force Unlock and press the Spacebar to change to Yes. Highlight Unlock and press Enter.
Setting Subsystem Date and Time

Use this screen to make Date and Time settings: 1. 2. From the Main Menu, highlight Subsystem Management and press Enter. Highlight Modify System Date & Time and press Enter.
163
3. 4. 5. 6.
Highlight the System Date or System Time setting. Press the backspace key to erase the current value. Type in a new value. Press Ctrl-A to save your settings.
Making NTP Settings

After you have made Network Time Protocol (NTP) settings, the VTrak subsystem synchronizes with a NTP server. At startup Every night When you synchronize manually
To make NTP settings for the subsystem: 1. 2. 3. 4. From the Main Menu, highlight Subsystem Management and press Enter. Highlight NTP Management and press Enter. Highlight NTP Settings and press Enter. Make the following settings as required: Highlight NTP Service and press the spacebar to toggle between Enabled and Disabled. Highlight Time Server (1), Time Server (2), or Time Server (3) and type a server name. Example: 0.us.pool.ntp.org You can have up to 3 NTP servers. Highlight Time Zone and press the spacebar to toggle through GMT, GMT+, and GMT-. For GMT+ and GMT-, type the hour from 0:00 to 13:00 GMT for your time zone. Highlight Daylight Savings Time and press the spacebar to toggle between Enable and Disable. If Daylight Savings Time is Enabled, highlight the Start Month and End Month and enter a number from 1 to 12. Then highlight the Week and Day and toggle to make your choices. 5. Press Ctrl-A to save your settings. Notes The NTP server name shown is an example only. You must find and enter your local NTP server name. GMT is the older designation for UTC.
164
Synchronizing with a NTP Server

The VTrak subsystem automatically synchronizes with a NTP server every night and a startup. You have the option of synchronizing manually at any time. To manually synchronize the VTrak with a NTP server: 1. 2. 3. 4. From the Main Menu, highlight Subsystem Management and press Enter. Highlight NTP Management and press Enter. Highlight Start Time Sync and press Enter. Press Y to confirm.
To verify, check Last Synchronization Time and Last Synchronization Result.
165
Managing the Controllers

Controller Management includes the following functions: Viewing Controller Information (page 166) Clearing an Orphan Watermark (page 166) Making Controller Settings (page 167) Locating the Controller (page 168)
Viewing Controller Information

Controller Management includes information, settings and statistics. To access Controller Management: 1. 2. From the Main Menu, highlight Subsystem Management and press Enter. Highlight Controller Management and press Enter. The Controller summary information includes: 3. Controller ID 1 or 2 Alias if assigned Operational Status OK means normal. Might show BGA running. Not present indicates a malfunction or no controller is installed Readiness Status Active or Standby is normal. N/A means not accessible
Highlight the controller you want and press Enter.
To access additional controller information, highlight Advanced Information and press Enter. To access controller statistics, highlight Controller Statistics and press Enter.
Clearing Statistics
To clear controller statistics, see Clearing Statistics on page 231.
Clearing an Orphan Watermark

This condition is the result of a disk drive failure during an NVRAM RAID level migration on a disk array. To clear an orphan watermark: 1. 2. 3. 4. From the Main Menu, highlight Subsystem Management and press Enter. Highlight Controller Management and press Enter. Highlight one of the controllers and press Enter. Highlight Clear Orphan Watermark and press Enter.
166
The condition is cleared. See Physical Drive Problems on page 316 for more information.
Making Controller Settings

If your subsystem has two controllers, any settings you make to one controller automatically apply to the other controller. To make Controller settings: 1. 2. 3. 4. 5. From the Main Menu, highlight Subsystem Management and press Enter. Highlight Controller Management and press Enter. Highlight the controller you want and press Enter. Highlight Controller Settings and press Enter. Make the following settings as required: Type an alias into the Alias field. Maximum of 48 characters. Use letters, numbers, space between words and underscore. An alias is optional. Highlight LUN Affinity and press the spacebar to toggle between Enabled and Disabled. If your subsystem has two controllers and Cache Mirroring is disabled, LUN Affinity is enabled automatically. Highlight Coercion and press the spacebar to toggle between Enabled and Disabled. For more information, see Capacity Coercion on page 291. Highlight Coercion Method and press the spacebar to toggle through: GB Truncate Reduces the capacity to the nearest 1 GB boundary. 10 GB Truncate Reduces the capacity to the nearest 10 GB boundary. Grp (group) Rounding Uses an algorithm to determine truncation. Results in the maximum amount of usable drive capacity. Table Rounding Applies a predefined table to determine truncation. Highlight Host Cache Flushing and press the spacebar to toggle between Enable and Disable. Highlight Cache Flush Interval and press the backspace key to erase the current value. Type a new interval value. The range is 1 to 12 seconds. For more information, see Cache Policy on page 289. Highlight SMART and press the spacebar to toggle between Enable and Disable.
167
Highlight SMART Poll Interval and press the backspace key to erase the current value. Type a new interval value (1 to 1440 minutes). Highlight Poll Interval and press the backspace key to erase the current value. Type a new interval value (15 to 255 seconds). Highlight Adaptive Writeback Cache and press the spacebar to toggle between Enabled and Disabled. For more information, see Adaptive Writeback Cache on page 290. Highlight Forced Read Ahead Cache and press the spacebar to toggle between Enabled and Disabled. For more information, see Forced Read-Ahead Cache on page 290. Highlight HDD Power Saving and the spacebar to choose a time period. After an HDD has been idle for a set period of time: Power Saving Idle Time Parks the read/write heads Power Saving Standby Time Lowers disk rotation speed Power Saving Stopped Time Spins down the disk (stops rotation) You must also enable Power Management on the disk array. See Creating a Disk Array Advanced on page 183 and Enabling Media Patrol, PDM, and Power Management on a Disk Array on page 186.
6.
Press Ctrl-A to save your settings. Notes Power Management must be enabled on the disk array for the HDD Power Saving settings to be effective. SeeMaking Disk Array Settings on page 184. Power management is limited to the features your HDDs actually support.
Locating the Controller

To locate this controller: 1. 2. 3. 4. 5. From the Main Menu, highlight Subsystem Management and press Enter. Highlight Controller Management and press Enter. Highlight the controller you want and press Enter. Highlight Controller Settings and press Enter. Highlight Locate Controller and press Enter.
168
Controller Dirty Cache LED and Status Controller, flash for one minute. Dirty Cache LED
LED, on the back of the
Controller Status LED
169
Managing the Enclosure

Enclosure Management includes the following functions: Viewing the Enclosures Summary (page 170) Viewing Enclosure Information (page 170) Making Enclosure Settings (page 171) Viewing FRU VPD Information (page 171) Viewing Power Supply Status (page 171) Locating a Power Supply (page 172) Viewing Cooling Unit Status (page 172) Viewing Temperature Sensor Status (page 172) Viewing Voltage Sensor Status (page 173) Viewing Battery Information (page 173) Reconditioning a Battery (page 174) Locating an Enclosure (page 174) Viewing Enclosure Topology (page 174)
Viewing the Enclosures Summary

Enclosure Management includes information, status, settings and location. To access Enclosure Management: 1. 2. From the Main Menu, highlight Subsystem Management and press Enter. Highlight Enclosure Management and press Enter. The following information is shown: Enclosure ID number Enclosure Type Operational Status Status Description (specific components in need of attention, if any)
Viewing Enclosure Information

To view enclosure information: 1. 2. 3. From the Main Menu, highlight Subsystem Management and press Enter. Highlight Enclosure Management and press Enter. Highlight the enclosure you want and press Enter. You can monitor power supplies, cooling units, enclosure temperatures and voltages, and the battery.
170
Adjustable items
You can set or adjust the following items: Enclosure Warning and Critical temperature thresholds Controller Warning and Critical temperature thresholds
See Making Enclosure Settings below. For information on Enclosure problems, see Enclosure Problems on page 308.
Making Enclosure Settings

To make Enclosure settings: 1. 2. 3. 4. 5. 6. 7. 8. From the Main Menu, highlight Subsystem Management and press Enter. Highlight Enclosure Management and press Enter. Highlight the enclosure you want and press Enter. Highlight Enclosure Settings and press Enter. Highlight the Temperature Warning threshold you want to change. Press the backspace key to erase the current value. Type a new interval value in degrees C. Press Ctrl-A to save your settings.
Viewing FRU VPD Information

FRU VPD refers to Vital Product Data (VPD) information about Field Replaceable Units (FRU) in the enclosure. The number and type of FRU depends on the subsystem model. To view FRU VPD information: 1. 2. 3. 4. From the Main Menu, highlight Subsystem Management and press Enter. Highlight Enclosure Management and press Enter. Highlight the enclosure you want and press Enter. Highlight FRU VPD Information and press Enter. Use this information when communicating with Technical Support and when ordering replacement units. For contact information, see Contacting Technical Support on page 351.
Viewing Power Supply Status

To view the status of the power supplies: 1. 2. From the Main Menu, highlight Subsystem Management and press Enter. Highlight Enclosure Management and press Enter.
171
3. 4.
Highlight the enclosure you want and press Enter. Highlight Power Supplies and press Enter. The screen displays the operational and fan status of VTraks two power supplies. If any status differs from normal or the fan speed is below the Healthy Threshold value, there is a fan/power supply malfunction. See Replacing a Power Supply on page 250.
Locating a Power Supply

To locate a power supply: 1. 2. 3. 4. 5. From the Main Menu, highlight Subsystem Management and press Enter. Highlight Enclosure Management and press Enter. Highlight the enclosure you want and press Enter. Highlight Power Supplies and press Enter. Highlight Locate Power Supply and press Enter. The LED on the selected power supply blinks for one minute.
Viewing Cooling Unit Status

To view the status of the power supply fans: 1. 2. 3. 4. From the Main Menu, highlight Subsystem Management and press Enter. Highlight Enclosure Management and press Enter. Highlight the enclosure you want and press Enter. Highlight Cooling Units and press Enter. The screen displays the status and speed of VTraks cooling units, which are the power supply fans. If fan speed is below the Healthy Threshold, there is a malfunction. See Power Supplies on page 310.
Viewing Temperature Sensor Status

To view the status of the temperature sensors: 1. 2. 3. 4. From the Main Menu, highlight Subsystem Management and press Enter. Highlight Enclosure Management and press Enter. Highlight the enclosure you want and press Enter. Highlight Temperature Sensors and press Enter. If any temperature exceeds the Healthy Threshold value, there is an overheat condition in the enclosure. See Making Enclosure Settings on page 171 and See Diagnosing an Enclosure Problem on page 308.
172
Viewing Voltage Sensor Status

To view the status of the voltage sensors: 1. 2. 3. 4. From the Main Menu, highlight Subsystem Management and press Enter. Highlight Enclosure Management and press Enter. Highlight the enclosure you want and press Enter. Highlight Voltage Sensors and press Enter. If any voltage is outside the Healthy Threshold values, there is a voltage malfunction in the enclosure. See Diagnosing an Enclosure Problem on page 308.
Viewing Battery Information

This feature enables you monitor and recondition the subsystem battery or batteries. 1. 2. 3. 4. 5. From the Main Menu, highlight Subsystem Management and press Enter. Highlight Enclosure Management and press Enter. Highlight the enclosure you want and press Enter. Highlight Batteries and press Enter. Highlight the battery you want to monitor and press Enter.
Battery Notes
If a battery does not reflect normal conditions and it is not currently under reconditioning, run the Recondition function before you replace the battery. See Reconditioning a Battery on page 174. Reconditioning fully discharges, then fully recharges the battery. During reconditioning, if the Adaptive Writeback Cache function is enabled, the controller cache is set to Write Thru. After reconditioning, the cache is reset to Write Back. See Making Controller Settings on page 167. If a battery reaches the threshold temperature while charging or discharging, the charge or discharge pauses and the blower runs at high speed until the battery temperature falls below the threshold. If the battery does not maintain normal values after a Recondition, replace the battery. See Replacing a Cache Backup Battery on page 252. By default, VTrak automatically reconditions the batteries every two months. When you install a new battery, the cycle count shows 0. VTrak automatically runs a recondition on the battery to verify it. If you restart the subsystem or controller before reconditioning is finished, the battery is charged to 100%, then reconditioning starts again.
173
Reconditioning a Battery
To recondition the subsystem battery: 1. 2. 3. 4. 5. 6. 7. From the Main Menu, highlight Subsystem Management and press Enter. Highlight Enclosure Management and press Enter. Highlight the enclosure you want and press Enter. Highlight Batteries and press Enter. Highlight the battery you want to recondition and press Enter. Highlight Start Reconditioning and press Enter. Press Y to confirm. Reconditioning fully discharges, then fully recharges the battery. During reconditioning, if the Adaptive Writeback Cache function is enabled, the controller cache is set to Write Thru. After reconditioning, the cache is reset to Write Back. See Making Controller Settings on page 167.
Locating an Enclosure
This feature helps you identify the physical VTrak enclosure you are working with through the CLU. 1. 2. 3. 4. From the Main Menu, highlight Subsystem Management and press Enter. Highlight Enclosure Management and press Enter. Highlight the enclosure you want and press Enter. Highlight Locate Enclosure and press Enter. The LEDs on the front of the VTrak blink for one minute.
Viewing Enclosure Topology

This feature displays the connection topology of the VTrak subsystem. Topology refers to the manner in which the data paths among the enclosures are connected. There are three methods: Individual Subsystem A single subsystem JBOD Expansion Managed through one subsystem or head unit RAID Subsystem Cascading Managed through one subsystem or head unit
For more information about connections, see Making Management and Data Connections on page 23. To view enclosure topology: 1. 2. From the Main Menu, highlight Subsystem Management and press Enter. Highlight Enclosure Topology and press Enter.
174
The following information applies to the Head Unit: Enclosure number 1 Controller number 1 or 2 Port number Status OK is normal. N/C is not connected Link Width
The following information applies to RAID cascaded units or JBOD expansion units: Connected EnclWWN The subsystem identified by its World Wide Number (WWN) Connected(Encl,Ctrl,Port) The subsystems enclosure, controller, and port numbers where the data connection was made If there is no connection, the value shows N/A.
175
Managing Physical Drives

Physical Drive Management includes the following functions: Viewing a List of Physical Drives (page 176) Making Global Physical Drive Settings (page 176) Viewing Physical Drive Information (page 177) Viewing Physical Drive Statistics (page 177) Setting an Alias (page 178) Clearing Stale and PFA Conditions (page 178) Forcing a Physical Drive Offline or Online (page 178) Locating a Physical Drive (page 179)
Viewing a List of Physical Drives

To view a list of physical drives: From the Main Menu, highlight Physical Drive Management and press Enter. The list of physical drives displays.
Making Global Physical Drive Settings

All physical drive settings are made globally, except for setting an alias, which applies to individual drives. To make global physical drive settings: 1. 2. 3. From the Main Menu, highlight Physical Drive Management and press Enter. Highlight Global Physical Drives Settings and press Enter. Change the following settings as required. For SATA drives: Highlight Write Cache and press the spacebar to toggle between Enabled and Disabled. Highlight Read Look Ahead Cache and press the spacebar to toggle between Enabled and Disabled. Highlight CmdQueuing and press the spacebar to toggle between Enabled and Disabled. Highlight MediumErrorThreshold and press the backspace key to remove the current value, then type a new smaller value. See the comments on the next page. Highlight DMA Mode and press the spacebar to toggle through UDMA 0 to 6 and MDMA 0 to 2.
176
For SAS drives: Highlight Write Cache and press the spacebar to toggle between Enabled and Disabled. Highlight Read Look Ahead Cache and press the spacebar to toggle between Enabled and Disabled. Highlight CmdQueuing and press the spacebar to toggle between Enabled and Disabled. Highlight MediumErrorThreshold and press the backspace key to remove the current value, then type a new smaller value. See the comments below. 4. Highlight Read Cache and press the spacebar to toggle between Enabled and Disabled.
Press Ctrl-A to save your settings. See Viewing Physical Drive Information below to determine which functions your physical drives support. Medium Error Threshold is the number of bad blocks tolerated before the controller marks the drive as Dead. The default setting is 64 blocks. A setting of zero disables the function. When disabled, no drives are marked offline even when errors are detected.
Viewing Physical Drive Information

To view information about a physical drive: 1. 2. 3. From the Main Menu, highlight Physical Drive Management and press Enter. Highlight the physical drive you want and press Enter. Basic information displays. Highlight Advanced Information and press Enter. Advanced information displays.
Viewing Physical Drive Statistics

To view the statistics for the selected physical drive: 1. 2. 3. From the Main Menu, highlight Physical Drive Management and press Enter. Highlight the physical drive you want and press Enter. Highlight Physical Drive Statistics and press Enter.
Clearing Statistics
To clear physical drive statistics, see Clearing Statistics on page 231
177
Setting an Alias
An alias is optional. To set an Alias for a physical drive: 1. 2. 3. From the Main Menu, highlight Physical Drive Management and press Enter. Highlight the physical drive you want and press Enter. Type an alias into the field provided. Maximum of 32 characters. Use letters, numbers, space between words and underscore. 4. Press Ctrl-A to save your settings.
Clearing Stale and PFA Conditions

The Clear Stale and Clear PFA functions only appear when those conditions exist on the physical drive. To clear a Stale or PFA condition on a physical drive: 1. 2. 3. From the Main Menu, highlight Physical Drive Management and press Enter. Highlight the physical drive you want and press Enter. Highlight Clear Stale or Clear PFA and press Enter. If a physical drive is still online and shows a PFA error but Clear PFA does not appear, use PDM to copy the data to a new physical drive. See Running PDM on page 188. If a physical drive is offline and shows a PFA error, rebuild the disk array. See Rebuilding a Disk Array on page 187. After rebuilding, the drive shows Stale. Run Clear Stale then run Clear PFA. If the physical drive with a PFA error is a spare, you must delete the drive as a spare, then Clear PFA is available. After you clear a PFA error, watch for another PFA error to appear. If it does, replace the physical drive.
Forcing a Physical Drive Offline or Online

This function enables you to force an: Online physical drive to go Offline Offline physical drive to go Online
178
The Force Offline/Online function appears only for physical drives that are assigned to disk arrays. Caution Forcing a physical drive offline or online is likely to cause data loss. Back up your data before you proceed. Use these functions only when required. To force a physical drive offline or online: 1. 2. 3. 4. 5. From the Main Menu, highlight Physical Drive Management and press Enter. Highlight Global Physical Drives Settings and press Enter. Highlight the physical drive you want and press Enter. Highlight Force Offline or Force Online and press Enter. Press Y to confirm.
Locating a Physical Drive

This feature helps you identify a physical drive within the VTrak enclosure you are working with through the CLU. To locate a physical drive: 1. 2. 3. 4. From the Main Menu, highlight Physical Drive Management and press Enter. Highlight Global Physical Drives Settings and press Enter. Highlight the physical drive you want and press Enter. Highlight Locate Physical Drive and press Enter. The drive carrier LEDs on the front of the VTrak blink for one minute. Green LED flashes
179
Managing Disk Arrays

Disk Array Management includes the following functions: Viewing a List of Disk Arrays (page 180) Creating a Disk Array (page 180) Deleting a Disk Array (page 184) Making Disk Array Settings (page 184) Viewing Disk Array Information (page 185) Enabling Media Patrol, PDM, and Power Management on a Disk Array (page 186) Preparing the Disk Array for Transport (page 187) Rebuilding a Disk Array (page 187) Migrating a Disk Array (page 187) Running PDM (page 188) Running Transition on a Disk Array (page 190) Locating a Disk Array (page 190) Locating a Disk Array (page 190) Creating a Logical Drive (page 190) Deleting a Logical Drive (page 192)
Viewing a List of Disk Arrays

To view a list of disk arrays: From the Main Menu, highlight Disk Array Management and press Enter. The list of disk arrays displays.
Creating a Disk Array

The CLU provides three methods of creating a disk array: Automatic Creates a new disk array following a default set of parameters. Creates a hot spare drive for all RAID levels except RAID 0, when five or more unconfigured physical drives are available. You can accept or reject the proposed arrangement but you cannot modify it. See Creating a Disk Array Automatic on page 181. Express You choose the parameters for a new disk array by specifying the characteristics you want. You can create multiple logical drives at the same time, however they are all identical. Creates a hot spare drive for all RAID levels except RAID 0. See Creating a Disk Array Express on page 182.
180
Advanced Enables you to specify all parameters for a new disk array, logical drives and spare drives. See Creating a Disk Array Advanced on page 183.
Creating a Disk Array Automatic

To create a disk array using the Automatic feature: 1. 2. 3. 4. 5. From the Main Menu, highlight Disk Array Management and press Enter. Highlight Create New Array and press Enter. Highlight Configuration Method and press the spacebar to toggle to Automatic. Press Ctrl-A to save your settings and move to the next screen. Review the proposed configuration of disk array and logical drives. To accept the proposed configuration and create the disk array and logical drives, highlight Save Configuration and press Enter. To reject the proposed configuration, highlight Cancel Array Configuration and press Enter. You return to the Disk Arrays Summary screen. To create a disk array with different characteristics, repeat the steps above specifying different parameters but choose the Express or Advanced option.
181
Creating a Disk Array Express

To create a disk array using the Express feature: 1. 2. 3. 4. From the Main Menu, highlight Disk Array Management and press Enter. Highlight Create New Array and press Enter. Highlight Configuration Method and press the spacebar to toggle to Express. Highlight the following options and press to spacebar to choose Yes or No: Redundancy Capacity Performance Spare Drive Mixing SATA/SAS Drive If you choose No, and you have both SATA and SAS drives, a separate array is created for each type of drive. 5. 6. Highlight Number of Logical Drives and press the backspace key to erase the current value, then enter the number of logical drives you want. Highlight Application Type and press the spacebar to toggle though the applications and choose the best one for your disk array. 7. 8. File Server Video Stream Transaction Data Transaction Log Other
Press Ctrl-A to save your settings and move to the next screen. Review the proposed configuration of disk array and logical drives. To accept the proposed configuration and create the disk array and logical drives, highlight Save Configuration and press Enter. To reject the proposed configuration, highlight Cancel Array Configuration and press Enter. You return to the Disk Arrays Summary screen. To create a disk array with different characteristics, highlight Create New Array and press Enter. Repeat the steps above specifying different parameters. Or choose the Advanced option.
182
Creating a Disk Array Advanced

For more information on the choices below, see Chapter 7: Technology Background on page 259. To create a disk array using the Advanced feature: 1. 2. 3. From the Main Menu, highlight Disk Array Management and press Enter. Highlight Create New Array and press Enter. Highlight Configuration Method and press the spacebar to toggle to Advanced. If you want to specify an alias to the disk array, highlight Alias and type a name. Maximum of 32 characters. Use letters, numbers, space between words and underscore. 2. 3. 4. 5. Choose whether to enable Media Patrol, PDM, and Power Management. Choose a Media Type, HDD or SSD. Highlight Save Settings and Continue and press Enter. Highlight a physical drive you want to add to your array and press the spacebar to choose it. Repeat this action until you have selected all the physical drives for your array. 6. 1. Highlight Save Settings and Continue and press Enter. If you want to specify an alias to the logical drive, highlight Alias and type a name. Maximum of 32 characters. Use letters, numbers, space between words and underscore. 2. 3. 4. Highlight RAID Level and press the spacebar to toggle though a list of available RAID levels. If you want to create multiple logical drives, highlight Capacity, press the backspace key to remove the current value, then type a new smaller value. RAID 50 and 60 only. Highlight Number of Axles and press the spacebar to choose the number of axles. See RAID 50 Axles on page 270 or RAID 60 Axles on page 273. 5. For the following items, accept the default value or highlight and press the spacebar to choose a new value: Highlight Stripe and press the spacebar to toggle through stripe sizes and choose 64 KB, 128 KB, 256 KB, 512 KB, or 1 MB.
183
Step 1 Disk Array Creation 1.
Step 2 Logical Drive Creation
Highlight Sector and press the spacebar to toggle through sector sizes and choose 512 B, 1 KB, 2 KB, or 4 KB. Highlight Write Policy and press the spacebar to toggle write cache policy between WriteBack and WriteThru (write though). Highlight Read Policy and press the spacebar to toggle read cache policy though ReadCache, ReadAhead, and NoCache. Highlight Preferred Controller ID and press the spacebar to toggle among 1, 2, or Automatic. Applies to dual-controller capable Fibre Channel models only.
6.
Highlight Save Logical Drive and press Enter.
Step 3 Summary Review logical drives you are about to create for your new array. Then do one of the following actions: If you agree with the logical drives as specified, highlight Complete Disk Array Creation and press Enter. If you specified less than the full capacity for the logical drive in the previous screen, and you want to add another logical drive now, highlight Create New Logical Drive and press Enter. If you do not agree with the logical drives, highlight Return to Previous Screen and press Enter to begin the process again.
Deleting a Disk Array

Caution When you delete a disk array, you delete all the logical drives and the data they contain. Back up all important data before deleting a disk array. 1. 2. 3. 4. 5. From the Main Menu, highlight Disk Array Management and press Enter. Highlight the disk array you want to delete and press the spacebar to mark it. The mark is an asterisk (*) to the left of the listing. Highlight Delete Marked Arrays and press Enter. Press Y to confirm the deletion. Press Y again to reconfirm.
Making Disk Array Settings

To make disk array settings: 1. From the Main Menu, highlight Disk Array Management and press Enter. The list of disk arrays appears.
184
2. 3.
Highlight the disk array you want and press the Enter. Make setting changes as required: Enter, change or delete the alias in the Alias field Maximum of 32 characters; letters, numbers, space between characters, and underline. Media Patrol Highlight and press the spacebar to toggle between enable and disable. PDM Highlight and press the spacebar to toggle between enable and disable. Power Management Highlight and press the spacebar to toggle between enable and disable.
4.
Press Ctrl-A to save your settings. Note You can also enable or disable Media Patrol for the entire RAID system. See Making Background Activity Settings on page 208. Notes Power Management must be enabled on the disk array for the HDD Power Saving settings to be effective. See Making Disk Array Settings on page 184. Power management is limited to the features your HDDs actually support.
Viewing Disk Array Information

1. 2. 3. From the Main Menu, highlight Disk Array Management and press Enter. Highlight the disk array you want and press Enter. The information and settings screen appears. Highlight any of the following and press Enter to view a list of: Physical drives in this array Logical drives in this array Spare drives in this array, dedicated and global
Disk Array Operational Status

OK This is the normal state of a logical drive. When a logical drive is Functional, it is ready for immediate use. For RAID Levels other than RAID 0 (Striping), the logical drive has full redundancy.
185
Synchronizing This condition is temporary. Synchronizing is a maintenance function that verifies the integrity of data and redundancy in the logical drive. When a logical drive is Synchronizing, it functions and your data is available. However, access is slower due to the synchronizing operation. Critical/Degraded This condition arises as the result of a physical drive failure. A degraded logical drive still functions and your data is still available. However, the logical drive has lost redundancy (fault tolerance). You must determine the cause of the problem and correct it. Rebuilding This condition is temporary. When a physical drive has been replaced, the logical drive automatically begins rebuilding in order to restore redundancy (fault tolerance). When a logical drive is rebuilding, it functions and your data is available. However, access is slower due to the rebuilding operation. Transport Ready After you perform a successful Prepare for Transport operation, this condition means you can remove the physical drives of this disk array and move them to another enclosure or different drive slots. After you relocate the physical drives, the disk array status shows OK.
Accepting an Incomplete Array

This condition is the result of a missing physical drive. See Incomplete Array on page 320 before you use this function. To accept an incomplete array: 1. 2. 3. From the Main Menu, highlight Disk Array Management and press Enter. Highlight the disk array you want and press Enter. Highlight Accept Incomplete Array and press Enter.
Enabling Media Patrol, PDM, and Power Management on a Disk Array

Media Patrol checks the magnetic media on physical drives. Predictive Data Migration (PDM) migrates data from the suspect physical drive to a spare physical drive before the disk drive fails. Power Management parks the heads, spins down, and stops rotation after a set period of time to reduce power consumption. Media Patrol, PDM, and Power Management are enabled by default. Enabled is the recommended setting for both features. To enable Media Patrol, PDM, and Power Management on a disk array: 1. 2. From the Main Menu, highlight Disk Array Management and press Enter. Highlight the disk array you want and press Enter.
186
3. 4. 5. 6.
Highlight Media Patrol and press the spacebar to toggle between Enable and Disable. Highlight PDM and press the spacebar to toggle between Enable and Disable. Highlight Power Management and press the spacebar to toggle between Enable and Disable. Press Ctrl-A to save your settings.
See Running PDM on page 188 and Making Background Activity Settings on page 208. For Power Management settings, see Making Controller Settings on page 167.
Preparing the Disk Array for Transport

To run the Transport function on a disk array: 1. 2. 3. 4. From the Main Menu, highlight Disk Array Management and press Enter. Highlight the disk array you want and press Enter. Highlight Transport and press Enter. Press Y to confirm.

Before you can rebuild, you must have a replacement or target physical drive of adequate capacity for your disk array. To rebuild a disk array: 1. 2. 3. 4. 5. 6. From the Main Menu, highlight Disk Array Management and press Enter. Highlight the disk array you want and press Enter. Highlight Background Activities and press Enter. Highlight Rebuild and press Enter. Default source and target drives are shown with possible alternative choices. To choose different drive, highlight the drive, press the backspace key to remove the current number, then type a new number. Highlight Start and press Enter.
For rebuild rate, see Making Background Activity Settings on page 208.
Migrating a Disk Array

In order to migrate RAID level, you may have to add physical drives. For more information, see RAID Level Migration on page 275.
187
To migrate a disk array: 1. 2. 3. 4. 5. From the Main Menu, highlight Disk Array Management and press Enter. Highlight the disk array you want and press Enter. Highlight Background Activities and press Enter. Highlight Migration and press Enter. Highlight the physical drives you want to add and press the spacebar to choose them. Notes You can add physical drives to a RAID 50 or 60 array but you cannot change the number of axles. If you add an odd number of physical drives to a RAID 10 array, it becomes a RAID 1E array by default.
6. 7. 8. 9.
Highlight Save Settings and Continue and press Enter. Highlight a logical drive in the list that you want to migrate and press Enter. Highlight RAID Level and press the spacebar to toggle through the available RAID levels. Optional. If you want to increase capacity of the logical drive, highlight Expand Capacity and press the spacebar to toggle to Yes. Highlight Capacity, press the backspace key to erase the current capacity and type in the new value. The new value must be equal or larger than the current capacity.
10. Highlight Save Logical Drive and press Enter. The screen returns to Disk Array Migration Logical Drives. At this point, if you have other logical drives in the same disk array, you can choose them for migration at the same time. 11. Highlight Complete Disk Array Migration and press Enter. 12. Press Y to confirm. The screen returns to Disk Arrays Summary. For migration rate, see Making Background Activity Settings on page 208.
Running PDM
Predictive Data Migration (PDM) migrates data from the suspect physical drive to a spare physical drive before the disk drive fails. Before you can run PDM, you must have a replacement or target physical drive of adequate capacity for your disk array.
188
To run PDM on a disk array: 1. 2. 3. 4. 5. 6. From the Main Menu, highlight Disk Array Management and press Enter. Highlight the disk array you want and press Enter. Highlight Background Activities and press Enter. Highlight Predictive Data Migration and press Enter. Default source and target drives are shown with possible alternative choices. To choose different drive, highlight the drive, press the backspace key to remove the current number, then type a new number. Highlight Start and press Enter.
See Enabling Media Patrol, PDM, and Power Management on a Disk Array on page 186. For PDM rate, see Making Background Activity Settings on page 208.
189
Running Transition on a Disk Array

Transition is the process of replacing a revertible spare drive that is currently part of a disk array with an unconfigured physical drive or a non-revertible spare drive. For more information, see Transition on page 284. In order to run Transition: The spare drive must be Revertible. You must have an unconfigured physical drive of the same or larger capacity to replace the spare drive.
To run Transition on a disk array: 1. 2. 3. 4. 5. 6. From the Main Menu, highlight Disk Array Management and press Enter. Highlight the disk array you want and press Enter. Highlight Background Activities and press Enter. Highlight Transition and press Enter. Default source and target drives are shown with possible alternative choices. To choose different drive, highlight the drive, press the backspace key to remove the current number, then type a new number. Highlight Start and press Enter.
For transition rate, see Making Background Activity Settings on page 208.
Locating a Disk Array

This feature helps you identify the physical drives assigned to the disk array you are working with in the CLU. To locate a disk array: 1. 2. 3. From the Main Menu, highlight Disk Array Management and press Enter. Highlight the disk array you want and press Enter. Highlight Locate Disk Array and press Enter. The drive carrier LEDs pertaining to this disk array blink for one minute. Green LED flashes
Creating a Logical Drive

You can create logical drives on existing disk arrays if there is available space in the array. For more information on the choices below, see Logical Drives on page 261.
190
To create a logical drive from an existing disk array: 1. 2. 3. 4. From the Main Menu, highlight Disk Array Management and press Enter. Highlight the disk array in which you want to create a logical drive and press Enter. Highlight Logical Drives in the Disk Array and press Enter. Highlight Create New Logical Drive and press Enter. The Disk Array ID number and Maximum capacity available for the new logical drive are displayed. 5. Highlight the following parameters and press the backspace key to erase the current value: Alias Type an alias into the field, if desired. Maximum of 32 characters. Use letters, numbers, space between words and underscore. Capacity Maximum capacity shown. Enter a smaller capacity if desired.
6.
Highlight the following parameters and press the spacebar to toggle though the available choices: Stripe size Press the spacebar to choose: 64 KB, 128 KB, 256 KB, 512 KB, or 1 MB. Sector size Press the spacebar to choose: 512 B; 1 KB, 2 KB, or 4 KB. Write Policy Press spacebar to choose: Write Back or Write Through. Read Policy Press spacebar to choose: No Cache, Read Cache, or Read Ahead Cache.
7.
Highlight Preferred Controller ID and press the spacebar to toggle among 1, 2, or Automatic. Applies to dual-controller capable Fibre Channel models only. RAID 50 and 60 only. Highlight Number of Axles and press the spacebar to choose the number of axles. Highlight Save Logical Drive and press Enter. Note If you did not use all of the available capacity of the disk array, you can create an additional logical drive at this point.
8. 9.
191
Deleting a Logical Drive

Caution When you delete a logical drive, you delete all the data it contains. Back up all important data before deleting a logical drive. To delete a logical drive from a disk array: 1. 2. 3. 4. From the Main Menu, highlight Disk Array Management and press Enter. Highlight the disk array that contains the logical drive you want to delete and press Enter. Highlight Logical Drives in the Disk Array and press Enter. Highlight the logical drive you want to delete and press the spacebar to mark it. The mark is an asterisk (*) to the left of the listing. 5. 6. 7. Highlight Delete Marked Logical Drives and press Enter. Press Y to confirm the deletion. Press Y again to re-confirm.
192
Managing Spare Drives

Spare Drive Management includes the following functions: Viewing a list of Spare Drives (page 193) Creating a Spare Drive (page 193) Making Spare Drive Settings (page 194) Running Spare Check (page 194) Deleting a Spare Drive (page 195)
Viewing a list of Spare Drives

To view a list of spare drives: From the Main Menu, highlight Spare Drive Management and press Enter. A list of the current spare drives appears, including the following parameters: ID number Operational Status Physical Drive ID number Configured Capacity Revertible The spare drive returns to spare status after you replace the failed drive in the disk array. See Transition on page 284 for more information. Type Global (all disk arrays) or Dedicated (to specified disk arrays) Dedicated to Array The array to which a dedicated spare is assigned
For more information, see Spare Drives on page 283.
Creating a Spare Drive

Only unconfigured physical drives can be used to make spares. Check your available drives under Physical Drive Management. See Managing Physical Drives on page 176. 1. 2. 3. 4. From the Main Menu, highlight Spare Drive Management and press Enter. Highlight Create New Spare Drive and press Enter. A default physical drive is shown with possible alternative choices. To choose different drive, highlight the drive, press the backspace key to remove the current number, then type a new number. Highlight Revertible and press the spacebar to toggle between Yes and No. A revertible drive can be returned to spare status after you replace the failed drive in a disk array. See Transition on page 303 for more information.
193
5.
Highlight Spare Type and press the spacebar to toggle between Dedicated and Global. Dedicated means this spare drive can only be used with the specified disk arrays. Global means this spare drive can be used by any disk array. If you chose Dedicated, a default disk array is shown with possible alternative choices. To choose different array, highlight the array and press the backspace key to erase the current number, then type the new number.
6.
Press Ctrl-A to save the spare drive.
Making Spare Drive Settings

To change spare drive settings: 1. 2. 3. From the Main Menu, highlight Spare Drive Management and press Enter. A list of the current spare drives appears, including the following parameters: Highlight the spare drive you want to change and press Enter. Highlight the setting you want to change: Revertible A revertible drive can be returned to spare status after you replace the failed drive in a disk array. See Transition on page 303 for more information. Type Dedicated means this spare drive can only be used with the specified disk arrays. Global means this spare drive can be used by any disk array.
4. 5. 6.
Press the spacebar to toggle between the choices. For dedicated spares, type the array number the spare is assigned to. Press Ctrl-A to save your settings.
Running Spare Check

To run Spare Check: 1. 2. 3. From the Main Menu, highlight Spare Drive Management and press Enter. A list of the current spare drives appears. Highlight the spare drive you want to check and press Enter. Highlight Start Spare Check and press Enter. The results appear next to Spare Check Status in the same window. Healthy means normal.
194
Deleting a Spare Drive

Caution If the spare drive you delete is the only spare, the controller does not rebuild a critical array until you provide a new spare drive. To delete a spare drive: 1. 2. From the Main Menu, highlight Spare Drive Management and press Enter. A list of the current spare drives appears. Highlight the spare drive you want to delete and press the spacebar to mark it. The mark is an asterisk (*) to the left of the listing. 3. 4. Highlight Delete Marked Spare Drives and press Enter. Press Y to confirm the deletion.
195
Managing Logical Drives

Logical drive management includes: Viewing Logical Drive Information (page 196) Viewing Logical Drive Statistics (page 196) Viewing the Logical Drive Check Table (page 197) Making Logical Drive Settings (page 197) Initializing a Logical Drive (page 197) Running Redundancy Check (page 198) Locating a Logical Drive (page 199)
To create or delete a logical drive, see Managing Disk Arrays on page 180. For LUN mapping, see Working with LUN Mapping on page 212.
Viewing Logical Drive Information

To view logical drive information: 1. 2. 3. From the Main Menu, highlight Logical Drive Management and press Enter. Highlight the logical drive you want and press Enter. The information and settings screen appears. Highlight any of the following and press Enter to view more information: Check Table Read Check, Write Check, and Inconsistency Check Tables Logical Drive Statistics
Viewing Logical Drive Statistics

To view logical drive information: 1. 2. 3. From the Main Menu, highlight Logical Drive Management and press Enter. Highlight the logical drive you want and press Enter. The information and settings screen appears. Highlight Logical Drive Statistics and press Enter. The statistics screen appears.
Clearing Statistics
To clear logical drive statistics, see Clearing Statistics on page 231.
196
Viewing the Logical Drive Check Table

To view logical drive information: 1. 2. 3. 4. From the Main Menu, highlight Logical Drive Management and press Enter. Highlight the logical drive you want and press Enter. Highlight Check Table and press Enter. Highlight one of the following options and press Enter: Show All Records Read Check Table Write Check Table Inconsistent Check Table
Making Logical Drive Settings

To make Logical Drive settings: 1. 2. 3. From the Main Menu, highlight Logical Drive Management and press Enter. Highlight the logical drive you want and press Enter. For the following items, accept the existing setting choose a new one: Highlight Alias and type an alias into the field provided. Maximum of 32 characters. Use letters, numbers, space between words and underscore. An alias is optional. 4. Highlight WritePolicy and press the spacebar to toggle between WriteBack and WriteThru (write though). Highlight ReadPolicy and press the spacebar to toggle though ReadCache, ReadAhead and None. Highlight Preferred Controller ID and press the spacebar to toggle between 1 and 2.
Initializing a Logical Drive

This function sets all data bits in the logical drive to zero. Caution When you initialize a logical drive, you delete all the data it contains. Back up all important data before initializing a logical drive.
197
To initialize a logical drive: 1. 2. 3. 4. From the Main Menu, highlight Logical Drive Management and press Enter. Highlight the logical drive you want and press Enter. Highlight Background Activities and press Enter. Highlight Start Initialization and press Enter. The initialization parameters appear. Initialization pattern The default 00000000 is best for most applications Quick Initialization Yes means only the first and last sections of the logical drives are initialized. No means the entire logical drive is initialized.
To change a parameter, highlight it and press the backspace key to erase the current value, then type the new value. 5. Highlight Start and press Enter. If necessary, you can pause and resume or stop and restart the Initialization. You cannot access the logical drive until Initialization has finished. For initialization rate, see Making Background Activity Settings on page 208.
Running Redundancy Check

Redundancy Check is a maintenance procedure for logical drives in fault-tolerant disk arrays that ensures all the data matches exactly. To run Redundancy Check: 1. 2. 3. 4. From the Main Menu, highlight Logical Drive Management and press Enter. Highlight the logical drive you want and press Enter. Highlight Background Activities and press Enter. Highlight Start Redundancy Check and press Enter. The redundancy check parameters appear. Auto Fix Corrects inconsistencies automatically Pause On Error Pauses the Redundancy Check when an error is found
To change a parameter, highlight it and press the backspace toggle between Yes and No. 5. Highlight Start and press Enter. If necessary, you can pause and resume or stop and restart the Redundancy Check. You can use the logical drive while Redundancy Check is running.
198
For Redundancy Check rate, see Making Background Activity Settings on page 208.
Locating a Logical Drive

This feature helps you identify the physical drives assigned to the logical drive you are working with in the CLU. To locate a logical drive: 1. 2. 3. From the Main Menu, highlight Logical Drive Management and press Enter. Highlight the disk array you want and press Enter. Highlight Locate Logical Drive and press Enter. The drive status LEDs for the physical drives in this logical drive blink for one minute. Green LED flashes
199
Managing the Network Connection

Network Management deals with network connections and settings for the VTraks Management ports. Each Management Port can be configured: Making Virtual Management Port Settings (page 200) Making Controller Management Port Settings (page 200)
Making Virtual Management Port Settings

The VTrak subsystem has a virtual management port. When you log into the VTrak over your network, you use the virtual management port, enabling you to log into a VTrak with two controllers using one IP address. Before you change settings, please see Choosing DHCP or a Static IP Address on page 36.

1. 2. 3. 4. 5. From the Main Menu, highlight Network Management and press Enter. Highlight the Virtual management port and press Enter. Highlight NetMgmt Ethernet Port Settings and press Enter Highlight DHCP and press the spacebar to toggle to Enabled. Press Ctrl-A to save your settings.

1. 2. 3. 4. 5. From the Main Menu, highlight Network Management and press Enter. Highlight the Virtual management port and press Enter. Highlight NetMgmt Ethernet Port Settings and press Enter Highlight DHCP and press the spacebar to toggle to Disabled. Highlight each of the following and press the backspace key to erase the current value, then type the new value. 6. IP Address Subnet Mask Default Gateway IP Address DNS Server IP Address
Making Controller Management Port Settings

Each RAID controller has an IP addresses for access when the controller goes into maintenance mode. Maintenance mode is only for remedial action in the event of a problem with the controller. See Maintenance Mode on page 312 for more information.
200
Before you change settings, please see Choosing DHCP or a Static IP Address on page 36.

1. 2. 3. 4. 5. From the Main Menu, highlight Network Management and press Enter. Highlight Maintenance Mode Network Configuration and press Enter. Highlight the controller you want and press Enter. Highlight DHCP and press the spacebar to toggle to Enabled. Press Ctrl-A to save your settings.

1. 2. 3. 4. 5. From the Main Menu, highlight Network Management and press Enter. Highlight Maintenance Mode Network Configuration and press Enter. Highlight the controller you want and press Enter. Highlight DHCP and press the spacebar to toggle to Disabled. Highlight each of the following and press the backspace key to erase the current value, then type the new value. 6. IP Address Subnet Mask Default Gateway IP Address DNS Server IP Address
201
Managing Fibre Channel Connections

The Fibre Channel Management option appears only with VTrak Fibre Channel models. Fibre Channel Management includes the following functions: Viewing Node Information (page 202) Viewing Fibre Channel Logged-in Devices (page 202) Making Fibre Channel Port Settings (page 202) Viewing SFP Information (page 203) Viewing Fibre Channel Port Statistics (page 204) Viewing Fibre Channel Initiators (page 205) Adding a Fibre Channel Initiator (page 205)
Viewing Node Information

These functions affect both VTrak Fibre Channel ports. 1. 2. From the Main Menu, highlight Fibre Channel Management and press Enter. Highlight Fibre Channel Node and press Enter. Node information appears. There are no user settings on this screen.
Viewing Fibre Channel Logged-in Devices

To view a list of logged-in devices: 1. 2. 3. 4. From the Main Menu, highlight Fibre Channel Management and press Enter. Highlight Fibre Channel Ports and press Enter. Highlight the port you want and press Enter. Highlight Logged In Devices and press Enter. If a Fibre Channel switch is attached, it also appears in this list.
Making Fibre Channel Port Settings

To make Fibre Channel port settings: 1. 2. 3. 4. 5. From the Main Menu, highlight Fibre Channel Management and press Enter. Highlight Fibre Channel Ports and press Enter. Highlight the port you want and press Enter. Highlight Fibre Channel Port Settings and press Enter. Highlight the following parameters and press the spacebar to toggle though the choices:
202
6.
Configured Link Speed 8 Gb/s, 4 Gb/s, 2 Gb/s, or Automatic selection Configured Topology NL-Port (Arbitrated Loop), N-Port (Point to Point) or Automatic selection
Highlight Hard ALPA and press the backspace key to erase the current value, then type the new value. The range is 0 to 255. 255 disables this feature. Press Ctrl-A to save your settings.
7.
The table below shows the type of attached topology you achieve based on your connection type and the configured topology you choose: Fibre Channel Attached Topology Configured Topology Connection Type Switch Direct N-Port Fabric Direct Point-to-Point NL-Port Public Loop Private Loop
Example 1: If you connect the VTrak to a Fibre Channel switch and choose NL-Port topology, you create a Public Loop attached topology. Example 2: If you have a Point to Point attached topology, you made a direct connection (no switch) and chose N-port topology. Note In some cases, HBA settings to N-Port only work if connected to the switch. Refer to your HBA manual for more information.
Viewing SFP Information

To view information about the SFPs (small form-factor pluggable transceivers): 1. 2. 3. 4. From the Main Menu, highlight Fibre Channel Management and press Enter. Highlight Fibre Channel Ports and press Enter. Highlight the port you want and press Enter. Highlight Fibre Channel Port SFP and press Enter. The screen displays information about the SFP transceiver. There are no user settings on this screen.
203
Viewing Fibre Channel Port Statistics

To view port statistics: 1. 2. 3. 4. From the Main Menu, highlight Fibre Channel Management and press Enter. Highlight Fibre Channel Ports and press Enter. Highlight the port you want and press Enter. Highlight Fibre Channel Port Statistics and press Enter. This screen displays statistics for this port. There are no user settings on this screen.
Clearing Statistics
To clear Fibre Channel statistics, see Clearing Statistics on page 231.
Property Definitions
Definitions of the properties for which statistical information is reported appears in the list below. TimeLastReset Time in minutes since the system has been running. FramesSent Number of frames sent since last reset. FramesReceived Number of frames received since last reset. WordsSent Number of words sent since last reset. WordsReceived Number of words received since last reset. LIPCount Loop Initialization Primitive Sequence. This primitive sequence applies only to the arbitrated loop topology. It is transmitted by an L_Port to initialize or re-initialize the loop. NOSCount Not Operational Primitive Sequence. This primitive sequence is used during link initialization between two N_Ports in the point-to-point topology or an N_Port and an F_Port in the fabric topology. NOS is sent to indicate that the transmitting port has detected a link failure or is offline. The expected response to a port sending NOS is the OLS primitive sequence. ErrorFrames FC devices propagate handshake signals back-and-forth requesting and acknowledging each byte transferred. FC transfers occur in one frame of data at a time. In this case, the value reflects the number of frames with errors. DumpedFrames This field specifies the number of frames dumped due to a lack of host buffers. LinkFailureCount Number of times the link has failed. Can be caused by a disconnected link or a bad fiber element.
204
LossSyncCount Number of times a loss of sync has occurred since last reset. PrimitiveSeqErrorCount An ordered set transmitted repeatedly and used to establish and maintain a link. LR, LRR, NOS, and OLS are primitive sequences used to establish an active link in a connection between two N_Ports or an N_Port and an F_Port. LIP, LPB, and LPE are primitive sequences used in the Arbitrated Loop topology for initializing the loop and enabling or disabling an L_Port.
InvalidWordSentCount Number of invalid words sent since last reset. InvalidCRCCount Invalid Cyclical Redundancy Count. Number of frames received with an invalid CRC since last reset. InitiatorIOCount I/O Count on the initiator on the host side.
Clearing Statistics
To clear statistics, see Clearing Statistics on page 231.
Viewing Fibre Channel Initiators

LUN Mapping must be enabled in order for VTrak to recognize a Fibre Channel. See Enabling LUN Mapping on page 212. To view Fibre Channel initiators: 1. 2. From the Main Menu, highlight Fibre Channel Management and press Enter. Highlight Fibre Channel Initiators and press Enter. A list of all currently logged-in initiators appears on the screen.
Adding a Fibre Channel Initiator

LUN Mapping must be enabled in order for VTrak to add a Fibre Channel. See Enabling LUN Mapping on page 212. You must add an initiator to the VTraks initiator list in order to use the initiator to create a LUN for your logical drive. To add an initiator: 1. 2. 3. 4. From the Main Menu, highlight Fibre Channel Management and press Enter. Highlight Fibre Channel Initiators and press Enter. Highlight the initiator you want to add and press the spacebar to choose it. Highlight Add Marked Initiators and press Enter. The initiator is added to VTraks initiator list.
205
Managing SAS Connections

The SAS Management option appears only with VTrak Serial Attached SCSI models. SAS Management includes the following functions: Viewing SAS Port Information (page 206) Making SAS Port Settings (page 206) Viewing SAS Port Statistics (page 207) Viewing SAS Initiators (page 207) Adding a SAS Initiator (page 207)
Viewing SAS Port Information

There are two SAS ports on each controller. To view information about the SAS ports: 1. 2. 3. From the Main Menu, highlight SAS Management and press Enter. Highlight SAS Ports and press Enter. Highlight the port you want to see and press Enter. The port information appears on the screen.
Making SAS Port Settings

There are two SAS ports on each controller. To make settings to the SAS ports: 1. 2. 3. 4. 5. From the Main Menu, highlight SAS Management and press Enter. Highlight SAS Ports and press Enter. Highlight the port you want to see and press Enter. Highlight SAS Port Settings and press Enter. Highlight Cable Signal Strength, press the backspace key to erase the current value, then type in the new value. The range is 1 to 8. 1 is the default. Signal strength correlates to cable length in meters. Example: If you have a 2 m SAS cable, set signal strength to 2. If performance is unsatisfactory (see Viewing SAS Port Statistics on page 207), try settings of 1 and 3, then use the best setting for your system. 6. Press Ctrl-A to save your settings.
206
Viewing SAS Port Statistics

There are two SAS ports on each controller. To view information about the SAS ports: 1. 2. 3. 4. From the Main Menu, highlight SAS Management and press Enter. Highlight SAS Ports and press Enter. Highlight the port you want to see and press Enter. Highlight SAS Port Statistics and press Enter. The statistics for the selected port appear on the screen.
Clearing Statistics
To clear SAS port statics, see Clearing Statistics on page 231.
Viewing SAS Initiators

LUN Mapping must be enabled in order for VTrak to recognize a SAS initiator. See Enabling LUN Mapping on page 212. There are two SAS ports on each controller, for a total of four SAS ports. To a view a list of logged-in initiators: 1. 2. From the Main Menu, highlight SAS Management and press Enter. Highlight SAS Initiators and press Enter. A list of all currently logged-in initiators appears on the screen.
Adding a SAS Initiator

LUN Mapping must be enabled in order for VTrak to add a SAS initiator. See Enabling LUN Mapping on page 212. You must add an initiator to the VTraks initiator list in order to use the initiator to create a LUN for your logical drive. To add an initiator: 1. 2. 3. 4. From the Main Menu, highlight SAS Management and press Enter. Highlight SAS Initiators and press Enter. Highlight the initiator you want to add and press the spacebar to choose it. Highlight Add Marked Initiators and press Enter. The initiator is added to VTraks initiator list.
207
Managing Background Activity

Background activity refers to any of several functions that take place in the background while normal operation of the VTrak continues. Background activities work in conjunction with disk arrays and logical drives. See Managing Disk Arrays on page 180 and Managing Logical Drives on page 196 for more information about how and when to use background activities. Background Activity Management includes the following functions: Viewing Current Background Activities (page 208) Making Background Activity Settings (page 208)
Viewing Current Background Activities

From the Main Menu, highlight Background Activities and press Enter. A count of current background activities appears, including: Rebuild PDM (Predictive Data Migration) Synchronization Redundancy Check Migration Transition Initialization Media Patrol
Making Background Activity Settings

1. 2. 3. From the Main Menu, highlight Background Activities and press Enter. Highlight Background Activity Settings and press Enter. Highlight following and press the spacebar to toggle between Enabled and Disabled. Media Patrol Checks the magnetic media on physical drives Auto Rebuild When enabled and no spare drive is available, the disk array begins to rebuild as soon as you replace the failed physical drive with an unconfigured physical drive of equal or greater size
4.
Highlight following and press the spacebar to toggle through Low, Medium, and High rates: Rebuild Rebuilds data to a replacement physical drive in a disk array Migration Change RAID level or add physical drives to disk arrays
208
PDM Migrates data from a suspect physical drive to a replacement drive in a disk array Transition Returns a revertible spare drive to spare status Synchronization Checks the data integrity on disk arrays Initialization Full initialization sets all data bits in the logical drive to a specified pattern, such as all zeros Redundancy Check Checks, reports and can correct data inconsistencies in logical drives Low Fewer resources to activity, more to data read/write. Medium Balance of resources to activity and data read/write. High More resources to activity, fewer to data read/write.
The rates are defined as follows: 5.
Highlight the following PDM trigger settings and press the backspace key to erase the current value: BBM Threshold 1 to 2048 reassigned blocks Media Patrol Threshold 1 to 2048 error blocks
6.
209
Working with the Event Viewer

The Event Viewer displays log of subsystem events. Events are classified as: Runtime Events A list of and information about the 1023 most recent runtime events recorded since the subsystem was started NVRAM Events A list of and information about the most important events over multiple subsystem startups. NVRAM events are stored in non-volatile memory
Working with the Event Viewer includes the following functions: Viewing Runtime Events (page 210) Clearing Runtime Events (page 210) Viewing NVRAM Events (page 210) Clearing NVRAM Events (page 211)
Viewing Runtime Events

To display Runtime Events: 1. From the Main Menu, highlight Event Viewer and press Enter. The log of Runtime Events appears. Events are added to the top of the list. Each item includes: 2. Sequence number Begins with 0 at system startup. Device Disk Array, Logical Drive, Physical Drive by its ID number. Severity See Table 1 on page 211 Timestamp Date and time the event happened. Description A description of the event in plain language.
Press the up and down arrow keys to scroll through the log.
Clearing Runtime Events

To clear the Runtime Event log: 1. 2. 3. From the Main Menu, highlight Event Viewer and press Enter. Highlight Clear Runtime Event Log and press Enter. Press Y to confirm.
Viewing NVRAM Events

This screen displays a list of and information about the most important events over multiple subsystem startups. To display NVRAM events: 1. From the Main Menu, highlight Event Viewer and press Enter.
210
2.
Highlight NVRAM Events and press Enter. The log of NVRAM Events appears. Events are added to the top of the list. Each item includes: Sequence number Begins with 0 at system startup. Device Disk Array, Logical Drive, Physical Drive by its ID number. Severity See Table 1 Timestamp Date and time the event happened. Description A description of the event in plain language.
3.
Clearing NVRAM Events

To clear the Runtime Event log: 1. 2. 3. 4. From the Main Menu, highlight Event Viewer and press Enter. Highlight NVRAM Events and press Enter. Highlight Clear NVRAM Event Log and press Enter. Press Y to confirm.
Table 1 Event severity levels Level Fatal Critical Major Minor Warning Information Meaning Non-Recoverable error or failure has occurred Action is needed now and the implications of the condition are serious Action is needed now Action is needed but the condition is not a serious at this time User can decide whether or not action is required Information only, no action is required
211
Working with LUN Mapping

LUN Mapping includes the following functions: Viewing a List of Initiators (page 212) Enabling LUN Mapping (page 212) Adding an Initiator (page 212) Mapping a LUN to an Initiator (page 213) Deleting an Initiator (page 213)
Viewing a List of Initiators

LUN Mapping must be enabled in order for VTrak to recognize an initiator. To view a list of initiators: 1. 2. From the Main Menu, highlight Additional Info and Management and press Enter. Highlight LUN Mapping and press Enter. A list of the current initiators appears.
Enabling LUN Mapping

LUN Mapping must be enabled in order for VTrak to recognize an initiator. To enable LUN mapping: 1. 2. 3. From the Main Menu, highlight Additional Info and Management and press Enter. Highlight LUN Mapping and press Enter. Press Y to confirm. A list of the current Fibre Channel or SAS initiators appears.
Adding an Initiator
You must add an initiator to the VTraks initiator list in order to use the initiator to create a LUN. You can also add initiators from a list under Fibre Channel Management, see page 205, or SAS Management, see page 207. To add a new initiator: 1. 2. 3. From the Main Menu, highlight Additional Info and Management and press Enter. Highlight LUN Mapping and press Enter. Highlight Create New Initiator and press Enter.
212
4.
Type the name of the initiator. Fibre Channel A Fibre Channel initiator name is the World Wide Port Name of the device and is composed of a series of eight, two-digit hexadecimal numbers. SAS A SAS initiator name is the SAS address of the HBA card in the Host PC. Obtain the initiator name from the initiator utility on your host system.
Obtain the initiator name from the initiator utility on your host system. The initiator name you input must match exactly for the connection to work. 5. Press Ctrl-A to save the initiator.
Mapping a LUN to an Initiator

You must add an initiator to the VTraks initiator list in order to map the initiator to a LUN. See Enabling LUN Mapping and Adding an Initiator on page 212. To map a LUN to an initiator: 1. 2. 3. 4. From the Main Menu, highlight Additional Info and Management and press Enter. Highlight LUN Mapping and press Enter. Highlight an existing Initiator and press Enter. A list of logical drives displays. In the LUN field, press the backspace key to erase the current value, then type the LUN you want to assign to this initiator, from 0 to 255. If you make a error, press Ctrl-R to restore the current LUN. 5. Press Ctrl-A to save the LUN map.
Deleting an Initiator
To delete an initiator: 1. 2. 3. 4. 5. From the Main Menu, highlight Additional Info and Management and press Enter. Highlight LUN Mapping and press Enter. Highlight the initiator you want to delete and press the spacebar to mark it. The mark is an asterisk (*) to the left of the listing. Highlight Delete Marked Initiators and press Enter. Press Y to confirm the deletion.
213
Managing UPS Units

Uninterruptible Power Supply (UPS) Management includes the following functions: Viewing a List of UPS Units (below) Making UPS Settings (page 215) Viewing UPS Information (page 216)
Viewing a List of UPS Units

To view a list of UPS units supporting the VTrak: 1. 2. From the Main Menu, highlight Additional Info and Management and press Enter. Highlight UPS Management and press Enter. Information in the UPS List includes: Operational Status OK means Normal. On AC means the UPS is connected to a viable external AC power source. On Battery means the external AC power source is offline and the UPS is running on battery power. Capacity Backup capacity expressed as a percentage. Remaining Minutes Number of minutes the UPS is expected to power your system in the event of a power failure. Loading Actual output of UPS as a percentage of the rated output. See the Note below. Note The maximum recommended Loading Ratio varies among models of UPS units. The general range is 60% to 80%. If the reported Loading Ratio exceeds the recommended value for your UPS unit: Have fewer subsystems or peripherals connected to this UPS unit. Add more UPS units, or use a higher-capacity UPS unit, to protect your RAID systems.
214
Making UPS Settings

These settings control how the VTrak subsystem detects the UPS unit and responds to data reported by the UPS unit. To make UPS settings: 1. 2. 3. 4. From the Main Menu, highlight Additional Info and Management and press Enter. Highlight UPS Management and press Enter. Highlight UPS Settings and press Enter. Perform the following actions as required: Verify the Current UPS Communication method. See Note 1: SNMP Network connection. Serial Serial connection. Unknown No connection. Automatic Default. If a UPS is detected when the subsystem boots, the setting changes to Enable. Enable Monitors UPS. Settings changes, reports warnings, and logs events. Disable Monitors UPS only. Running Time Remaining Threshold Actual time below this value resets adaptive writeback cache to writethrough. Warning Temperature Threshold Actual temperature above this value triggers a warning and logs an event. Loading Ratio Threshold Actual loading ratio (percentage) above this threshold triggers a warning and logs an event. See Note 3. Battery Charge Remaining Threshold Reserve capacity below this percentage triggers a warning and logs an event.
Choose a Detection Setting from the dropdown menu:
Type values into the Threshold fields. See Note 2:
5.
For UPS units with network cards, type the IP addresses or DNS names in fields UPS 1 and UPS 2. See Note 4.
Press Ctrl-A to save your settings. Note 1: VTrak supports multiple UPS units using network or serial connections, but not a combination of both methods. Note 2: Detection Setting must be set to Auto. If a UPS is detected, the setting changes to Enable.
215
Note 3: The maximum recommended Loading Ratio varies among models of UPS units. The general range is 60% to 80%. Note 4: To specify UPS units by DNS names, ask your IT administrator to add the DNS names to the DNS server, before you make UPS settings.
Viewing UPS Information

To view information about a specific UPS unit: 1. 2. 3. From the Main Menu, highlight Additional Info and Management and press Enter. Highlight UPS Management and press Enter. Highlight the UPS unit you want and press Enter. UPS information includes: UPS ID Model Name Serial Number Firmware Version Manufacture Date Voltage Rating Output voltage of the UPS. Battery Capacity Backup capacity expressed as a percentage. Remaining Backup Time Number of minutes the UPS is expected to power your system in the event of a power failure. Loading Ratio Actual output of UPS as a percentage of the rated output. See the Note below. Temperature Reported temperature of the UPS unit. Note The maximum recommended Loading Ratio varies among models of UPS units. The general range is 60% to 80%. If the reported Loading Ratio exceeds the recommended value for your UPS unit: Have fewer subsystems or peripherals connected to this UPS unit. Add more UPS units, or use a higher-capacity UPS unit, to protect your RAID systems.
216
Managing Users
User Management includes the following functions: Viewing User Information (page 217) Creating a User (page 217) Changing Another Users Settings (page 218) Changing Your Own User Settings (page 219) Changing Another Users Password (page 219) Changing Your Own Password (page 219) Deleting a User (page 220)
Viewing User Information

Each user types their user name and password to log into the CLI. To view a list of current user accounts: 1. 2. From the Main Menu, highlight Additional Info and Management and press Enter. Highlight User Management and press Enter. A list of the current users appears.
Creating a User
To create a new user account: 1. 2. 3. 4. From the Main Menu, highlight Additional Info and Management and press Enter. Highlight User Management and press Enter. Highlight Create New User and press Enter. Highlight each field and type in the appropriate information: 5. 6. User name (Maximum 31 characters. Use letters, numbers, and underscore. No spaces.) Password (Optional. Maximum 31 characters. Use letters, numbers, and underscore.) Display name (Optional) Users email address
Highlight Privilege and press the space bar to toggle though the options. See Table 2 on page 218. Press Ctrl-A to save the user.
217
Table 2 User Privileges Level View Maintenance Power Meaning Allows the user to see all status and settings but not to make any changes Allows the user to perform maintenance tasks including Rebuilding, PDM, Media Patrol, and Redundancy Check Allows the user to create (but not delete) disk arrays and logical drives, change RAID levels, change stripe size; change settings of components such as disk arrays, logical drives, physical drives, and the controller Allows the user full access to all functions including create and delete users and changing the settings of other users, and delete disk arrays and logical drives. The default administrator account is a Super User
Super
Changing Another Users Settings

The Administrator or a Super User can change other users settings. To change user settings: 1. 2. 3. 4. 5. 6. From the Main Menu, highlight Additional Info and Management and press Enter. Highlight User Management and press Enter. Highlight the User whose settings you want to change and press Enter. Highlight Privilege and press the space bar to toggle though the options. See Table 2. Highlight Status and press the space bar to toggle between Enabled and Disabled. Highlight the items you want and press the backspace key to erase the current value, then type the new value: 7. User name Email address
Press Ctrl-A to save the settings. Important If a user is logged-in when his account is disabled, the user is immediately logged-out.
218
Changing Your Own User Settings

Each user can change their display name and email address. To change your user settings: 1. 2. 3. 4. From the Main Menu, highlight Additional Info and Management and press Enter. Highlight User Management and press Enter. Highlight your name and press Enter. Highlight the items you want and press the backspace key to erase the current value, then type the new value: 5. User name Email address
Press Ctrl-A to save the settings.
Changing Another Users Password

The Administrator or a Super User can change other users passwords. To change a password: 1. 2. 3. 4. 5. 6. 7. From the Main Menu, highlight Additional Info and Management and press Enter. Highlight User Management and press Enter. Highlight the User whose password you want to change and press Enter. Highlight Change Password... and press Enter. Highlight New Password and type a new password. Maximum 31 characters. Use letters, numbers, and underscore. Highlight Retype Password and type the new password again to verify. Press Ctrl-A to save the new password. Note To reset the Administrators password to the factory default, see Resetting the Default Password on page 258.
Changing Your Own Password

Each user can change their own password. To change your password: 1. From the Main Menu, highlight Additional Info and Management and press Enter.
219
2. 3. 4. 5. 6. 7. 8.
Highlight User Management and press Enter. Highlight your name and press Enter. Highlight Change Password... and press Enter. Highlight Old Password and type your current password. Highlight New Password and type a new password. Maximum 31 characters. Use letters, numbers, and underscore. Highlight Retype Password and type the new password again to verify. Press Ctrl-A to save the new password.
Deleting a User
The Administrator or a Super User can delete other users. You cannot delete the account you used to log in. There must always be one Super User account. Rather than deleting a user, consider disabling a user account. See Changing Another Users Settings on page 218. To delete a user: 1. 2. 3. 4. 5. 6. Log in under a user name other than the one you want to delete. From the Main Menu, highlight Additional Info and Management and press Enter. Highlight User Management and press Enter. Highlight the user you want to delete and press the spacebar to mark it. The mark is an asterisk (*) to the left of the listing. Highlight Delete Marked Users and press Enter. Press Y to confirm the deletion.
220
Working with Software Management

Software Management includes the following functions: Making Email Settings (page 221) Making SLP Settings (page 222) Making Webserver Settings (page 222) Making Telnet Settings (page 223) Making SSH Settings (page 223) Making SNMP Settings (page 224) Managing SNMP Trap Sinks (page 224) Making CIM Settings (page 225) Making Netsend Settings (page 227) Managing Netsend Recipients (page 227)
Making Email Settings

By default, Email service is set to Automatic and its normal status is Started. To make Email service settings: 1. 2. 3. 4. 5. From the Main Menu, highlight Additional Info and Management and press Enter. Highlight Software Management and press Enter. Highlight Email and press Enter. Highlight Startup Type and press the spacebar to toggle between Automatic and Manual. Highlight the following and press the backspace key to erase the current value, then type the new value: 6. SMTP server IP address or server name Server Port number (25 is the default)
Highlight Authentication and press the spacebar to toggle between Yes and No. If you selected Yes, type in a User name and Password in the fields provided.
7.
The following items are optional but recommended. Highlight and press the backspace key to erase the current value, then type the new value: Senders email address Subject Line for the email message
8.
221
To start, stop or restart the Email service, highlight Start, Stop or Restart and press Enter.
Making SLP Settings

By default, SLP service is set to Automatic and its normal status is Started. To make SLP service settings: 1. 2. 3. 4. 5. From the Main Menu, highlight Additional Info and Management and press Enter. Highlight Software Management and press Enter. Highlight SLP and press Enter. Highlight Startup Type and press the spacebar to toggle between Automatic and Manual. Press Ctrl-A to save your settings.
To start, stop or restart the SLP service, highlight Start, Stop, or Restart and press Enter.
Making Webserver Settings

By default, Webserver service is set to Automatic and its normal status is Started. To make Webserver service settings: 1. 2. 3. 4. 5. From the Main Menu, highlight Additional Info and Management and press Enter. Highlight Software Management and press Enter. Highlight Webserver and press Enter. Highlight Startup Type and press the spacebar to toggle between Automatic and Manual. Highlight the following and press the backspace key to erase the current value, then type the new value: 6. 7. 8. HTTP Port (80 is the default) Session Time Out (24 minutes is the default. 1440 minutes = 24 hours)
Highlight SSL and press the spacebar to toggle between Enabled and Disabled. Highlight HTTPS Port and press the backspace key to erase the current value, then type the new value. 443 is the default. Press Ctrl-A to save your settings.
To start, stop or restart the Webserver service, highlight Start, Stop, or Restart and press Enter.
222
Making Telnet Settings

By default, Telnet service is set to Automatic and its normal status is Started. To make Telnet service settings: 1. 2. 3. 4. 5. From the Main Menu, highlight Additional Info and Management and press Enter. Highlight Software Management and press Enter. Highlight Telnet and press Enter. Highlight Startup Type and press the spacebar to toggle between Automatic and Manual. Highlight the following and press the backspace key to erase the current value, then type the new value: 6. Port number (2300 is the default) Session Time Out (24 minutes is the default. 1440 minutes = 24 hours) Maximum number of connections (4 is the default)
To start, stop or restart the Telnet service, highlight Start, Stop, or Restart and press Enter.
Making SSH Settings

By default, Secure Shell (SSH) service is set to Automatic and its normal status is Started. To make SSH settings: 1. 2. 3. 4. 5. From the Main Menu, highlight Additional Info and Management and press Enter. Highlight Software Management and press Enter. Highlight SSH and press Enter. Highlight Startup Type and press the spacebar to toggle between Automatic and Manual. Highlight the following and press the backspace key to erase the current value, then type the new value: 6. Port number (22 is the default) Session Time Out (24 minutes is the default. 1440 minutes = 24 hours) Maximum number of connections (4 is the default)
223
Making SNMP Settings

By default, Simple Network Management Protocol (SNMP) service is set to Automatic and its normal status is Started. To make SNMP service settings: 1. 2. 3. 4. 5. From the Main Menu, highlight Additional Info and Management and press Enter. Highlight Software Management and press Enter. Highlight SNMP and press Enter. Highlight Startup Type and press the spacebar to toggle between Automatic and Manual. Highlight the following and press the backspace key to erase the current value, then type the new value: 6. Port Number 161 is the default System Name (optional) Type a system name in this field System Location Type a country name in this field System Contact Type the email address of your system administrator in this field Read Community Type a community name in this field Write Community private (no change possible)
To start, stop or restart the SNMP service, highlight Start, Stop, or Restart and press Enter.
Managing SNMP Trap Sinks

Viewing a List of Trap Sinks
To create a trap sink: 1. 2. 3. 4. From the Main Menu, highlight Additional Info and Management and press Enter. Highlight Software Management and press Enter. Highlight SNMP and press Enter. Highlight Trap Sinks and press Enter. A list of the current trap sinks appears.
Adding a Trap Sink

To add a trap sink: 1. From the Main Menu, highlight Additional Info and Management and press Enter.
224
2. 3. 4. 5. 6. 7.
Highlight Software Management and press Enter. Highlight SNMP and press Enter. Highlight Trap Sinks and press Enter. Highlight Create New Trap Sink and press Enter Highlight Trap Sink IP address and press the backspace key to erase the current value, then type the new IP address in this field. Highlight Trap Filter and press the spacebar to toggle through the severity levels. See Table 3 on page 225. Press Ctrl-A to save the Trap Sink.
8.
Deleting a Trap Sink

To delete a trap sink: 1. 2. 3. 4. 5. 6. From the Main Menu, highlight Additional Info and Management and press Enter. Highlight Software Management and press Enter. Highlight SNMP and press Enter. Highlight Trap Sinks and press Enter. Highlight the trap sink you want to delete and press the spacebar to mark it. The mark is an asterisk (*) to the left of the listing. Highlight Delete Marked Entries and press Enter.
Making CIM Settings

By default, Common Information Model (CIM) service is set to Automatic and its normal status is Started.
225
To make CIM service settings: 1. 2. 3. 4. From the Main Menu, highlight Additional Info and Management and press Enter. Highlight Software Management and press Enter. Highlight CIM and press Enter. Enter information or change settings as required. Highlight Startup Type and press the spacebar to toggle between Automatic and Manual. To use a HTTP connection, highlight HTTP and press the spacebar to toggle to Enabled and accept the 5988 is the default port number or highlight HTTP Port, press the backspace key to erase, type new value. To use a HTTPS connection, highlight HTTPS and press the spacebar to toggle to Enabled accept the 5989 is the default port number or highlight HTTPS Port, press the backspace key to erase, type new value. To use CIM authentication, highlight Authentication and press the spacebar to toggle to Enabled. Enter the old password and a new password into the fields provided. The default password is password. There is only one user. The default name is cim. No changes are possible. 5. 6. Press Ctrl-A to save your settings. Press Y to confirm.
To start, stop or restart the CIM service, highlight Start, Stop, or Restart and press Enter.
226
Making Netsend Settings

By default, Netsend service is set to Manual and its normal status is Stopped. To make Netsend service settings: 1. 2. 3. 4. 5. From the Main Menu, highlight Additional Info and Management and press Enter. Highlight Software Management and press Enter. Highlight Netsend and press Enter. Highlight Startup Type and press the spacebar to toggle between Automatic and Manual. Press Ctrl-A to save your settings.
To start, stop or restart the Netsend service, highlight Start, Stop, or Restart and press Enter.
Managing Netsend Recipients

VTraks Netsend service sends VTrak subsystem events in the form of text messages to your Host PC and other networked PCs. See Making Netsend Settings on page 227.
Netsend Requirements
In order to use Netsend: NetSend must be running the VTrak You must provide the IP address for each recipient PC The Messenger service must be running on each recipient PC
If your Netsend and Messenger service settings are correct but the recipient PC does not receive event messages, check the recipient PCs Firewall settings. Refer to your OS documentation for more information.
Adding Netsend recipients

To add a Netsend recipient: 1. 2. 3. 4. 5. 6. 7. From the Main Menu, highlight Additional Info and Management and press Enter. Highlight Software Management and press Enter. Highlight Netsend and press Enter. Highlight Message Recipients and press Enter. Highlight Create New Message Recipient and press Enter. Type the recipients IP address into the field provided. Highlight Message Event Severity Filter and press the spacebar to change severity levels.
227
The selected level and all higher severity levels of severity are reported. See Table 4 on page 228. 8. Press Ctrl-A to save your settings.
Deleting Netsend Recipients

To delete a Netsend recipient: 1. 2. 3. 4. 5. 6. From the Main Menu, highlight Additional Info and Management and press Enter. Highlight Software Management and press Enter. Highlight Netsend and press Enter. Highlight Message Recipients and press Enter. Highlight the recipient you want to delete and press the spacebar to mark it. The mark is an asterisk (*) to the left of the listing Highlight Delete Marked Entries and press Enter.
228
Flashing through TFTP

Use this function to flash (update) the firmware on the VTrak. See page 244 for the procedure.
229
Viewing Flash Image Information

Flash image information refers to the package of firmware components running on your VTrak controller or controllers. To view flash image information: 1. 2. From the Main Menu, highlight Additional Info and Management, and press Enter. Highlight Flash Image Version Info and press Enter. The flash image information displays on the screen: Enclosure Number 1 (one) is the Head Unit. Other numbers are cascaded or expanded subsystems Running Image Info Firmware currently running on the controllers Flashed Image Info Firmware flashed to memory Image Type A specific component Controller ID 1 or 2 Version number Build date Flash (installation) date
If the Running and Flashed Images do not match, the VTrak has not restarted since the firmware was last updated. Restart the VTrak to run the Flashed firmware package. See Restarting the Subsystem on page 237. Note that all of these components are upgraded together in a package. See Updating the Subsystem Firmware on page 241.
230
Clearing Statistics
This function clears the statistical counts for the RAID controller, Fibre Channel ports, SAS ports, physical drives, and logical drives. To clear statistics: 1. 2. 3. From the Main Menu, highlight Additional Info and Management and press Enter. Highlight Clear Statistics and press Enter. Press Y to confirm the deletion.
231
Restoring Factory Defaults

This function restores the factory default settings to the firmware and software items you select. Caution Restoring default settings can disrupt your VTrak functions. Use this feature only when necessary. If you restore Management Network settings, you lose your network connection to the VTrak. 1. 2. 3. From the Main Menu, highlight Additional Info and Management and press Enter. Highlight Restore Factory Defaults and press Enter. Highlight the setting groups you want to restore and press the spacebar to toggle between Yes and No. Yes means this setting is restored to the default value. No means the current setting remains untouched. 4. 5. Highlight Restore Factory Defaults and press Enter. Press Y to confirm the reset.
232
Shutting Down the Subsystem

There are two methods for shutting down the subsystem. Choose one of the following procedures: Shutting down the VTrak Telnet Connection (page 233) Shutting down the VTrak SSH Connection (page 233) Shutting down the VTrak Serial Connection (page 234)
Shutting down the VTrak Telnet Connection

This function shuts down the VTrak subsystem on a Telnet connection. Additional action is required, as described below. Important If you have a JBOD Expansion, always power off the RAID subsystem first. Then power off the JBOD subsystems. To shutdown the RAID subsystem: 1. 2. 3. 4. 5. 6. 7. From the Main Menu, highlight Additional Info and Management and press Enter. Highlight Shutdown or Restart and press Enter. Highlight Option and press the spacebar to display Shutdown. Highlight Submit and press Enter. A warning message appears. Press Y to continue. The screen goes blank. Wait for no less than two minutes. Manually turn off the power supply switches on the back of the subsystem.
Shutting down the VTrak SSH Connection

This function shuts down the VTrak subsystem on a SSH connection. Additional action is required, as described below. Important If you have a JBOD Expansion, always power off the RAID subsystem first. Then power off the JBOD subsystems.
233
To shutdown the RAID subsystem: 1. 2. 3. 4. 5. 6. 7. 8. From the Main Menu, highlight Additional Info and Management and press Enter. Highlight Shutdown or Restart and press Enter. Highlight Option and press the spacebar to display Shutdown. Highlight Submit and press Enter. A warning message appears. Press Y to continue. Close your SSH session. Wait for no less than two minutes. Manually turn off the power supply switches on the back of the subsystem.
Shutting down the VTrak Serial Connection

This function shuts down the VTrak subsystem on a serial connection. Additional action is required, as described below. Important If you have a JBOD Expansion, always power off the RAID subsystem first. Then power off the JBOD subsystems. To shutdown the RAID subsystem: 1. 2. 3. 4. 5. 6. 7. From the Main Menu, highlight Additional Info and Management and press Enter. Highlight Shutdown or Restart and press Enter. Highlight Shutdown or Restart and press Enter. Highlight Option and press the spacebar to display Shutdown. Highlight Submit and press Enter. A warning message appears. Press Y to continue. Turn off the power supply switches when you see the following message: Shutdown complete. It is now safe to power off the subsystem.
234
Starting Up After Shutdown

There are two methods for shutting down the subsystem. Choose one of the following procedures: Starting up the VTrak Telnet Connection (page 235) Starting up the VTrak SSH Connection (page 235) Starting up the VTrak Serial Connection (page 236)
Starting up the VTrak Telnet Connection

Important If you have a JBOD Expansion, always power on the JBOD subsystems first. Then power on the RAID subsystem. To start the RAID subsystem: 1. 2. 3. Manually turn on the power supply switches on the back of the subsystem. Wait about two minutes. Establish a Telnet connection to the VTrak. See Making a Telnet Connection on page 157. If you cannot log in, wait 30 seconds and try again. 4. Type menu and press Enter to open the CLU.
Starting up the VTrak SSH Connection

Important If you have a JBOD Expansion, always power on the JBOD subsystems first. Then power on the RAID subsystem. To start the RAID subsystem: 1. 2. 3. Manually turn on the power supply switches on the back of the subsystem. Wait about two minutes. Establish a SSH connection to the VTrak. See Making a SSH Connection on page 157. If you cannot log in, wait 30 seconds and try again. 4. Type menu and press Enter to open the CLU.
235
Starting up the VTrak Serial Connection

Important If you have a JBOD Expansion, always power on the JBOD subsystems first. Then power on the RAID subsystem. To start the RAID subsystem: 1. 2. 3. Manually turn on the power supply switches on the back of the subsystem. Wait about two minutes. Establish a serial connection to the VTrak. See Making a Serial Connection on page 156. When the Login: prompt appears, the start up is finished. 4. Type menu and press Enter to open the CLU.
236
Restarting the Subsystem

There are two methods for restarting the subsystem. Choose one of the following procedures: Restarting the Subsystem (page 237) Restarting VTrak SSH Connection (page 237) Restarting VTrak Serial Connection (page 238) Note If you have a JBOD Expansion, you are not required to restart the JBOD subsystems when you restart the RAID subsystem.
Restarting VTrak Telnet Connection

To restart the RAID subsystem: 1. 2. 3. 4. 5. 6. 7. From the Main Menu, highlight Additional Info and Management and press Enter. Highlight Shutdown or Restart and press Enter. Highlight Option and press the spacebar to display Restart. Highlight Submit and press Enter. A warning message appears. Press Y to continue. The screen goes blank. Wait about two minutes. Re-establish your Telnet connection to the VTrak CLU. See Making a Telnet Connection on page 157. If you cannot re-establish a connection, wait 30 seconds and try again.
Restarting VTrak SSH Connection

To restart the RAID subsystem: 1. 2. 3. 4. 5. From the Main Menu, highlight Additional Info and Management and press Enter. Highlight Shutdown or Restart and press Enter. Highlight Option and press the spacebar to display Restart. Highlight Submit and press Enter. A warning message appears. Press Y to continue.
237
6. 7. 8.
Close your SSH session. Wait about two minutes. Re-establish your SSH connection to the VTrak CLU. See Making a SSH Connection on page 157. If you cannot re-establish a connection, wait 30 seconds and try again.
Restarting VTrak Serial Connection

To restart the RAID subsystem: 1. 2. 3. 4. 5. 6. From the Main Menu, highlight Additional Info and Management and press Enter. Highlight Shutdown or Restart and press Enter. Highlight Option and press the spacebar to display Restart. Highlight Submit and press Enter. A warning message appears. Press Y to continue. The screen displays shutdown and startup functions. When the Login: prompt appears, log into the CLU again.
238
Making Buzzer Settings

The buzzer sounds to inform you that the VTrak needs attention. See VTrak is Beeping on page 293 for more information. To change buzzer settings: 1. 2. 3. 4. From the Main Menu, highlight Buzzer and press Enter. A list of Controllers appears with the current buzzer setting and status. Highlight the Controller whose buzzer you want to set and press Enter. Highlight Enabled and press the spacebar to toggle between Yes and No. Press Ctrl-A to save your settings.
239
240
Chapter 6: Maintenance
This chapter covers the following topics: Updating the Subsystem Firmware (below) Updating Physical Drive Firmware (page 248) Replacing a Power Supply (page 250) Replacing a Cache Backup Battery (page 252) Replacing a RAID Controller Dual Controllers (page 254) Replacing a RAID Controller Single Controller (page 256) Resetting the Default Password (page 258)
Updating the Subsystem Firmware

This procedure applies to VTrak RAID subsystems and VTrak JBOD expansion units managed by a VTrak RAID subsystem. There are three methods: WebPAM PROe (page 241) CLU (page 244) USB Support (page 246)
Updating with WebPAM PROe

Download the latest firmware image file from PROMISE support: http://www.promise.com/support/ and save it to your Host PC or TFTP server. Important Verify that no background activities are running on the RAID subsystem. To update the firmware on the RAID subsystem and JBOD expansion units: 1. 2. 3. Click the AdminTool tab. Click the Firmware Update icon. Click the Controller Firmware Update tab. The Controller Firmware Update screen appears showing the current Image Version Number and Build Date. 4. Choose a download option: Local File through HTTP Click the Browse button, locate the firmware image file, click the file to choose it, then click the Open button.
241
5.
TFTP Server Enter the TFTP Server host name or IP address, port number and file name.
Optional. Check the Non-disruptive Image Update (NDIU) box. NDIU updates the RAID controllers and I/O modules one at a time, enabling I/O operations continue during the firmware update. Updates with this option take a longer period of time to complete. Only VTrak x30 models support this feature.
6.
Click the Next button. The next screen shows the Flash Image (firmware image file) Version Number and Build Date.
7.
Click the Submit button. The progress of the update displays. Warning Do NOT power off the RAID subsystem during the update! Do NOT move to any other screen until the firmware update operation is completed!
When the update is completed a message tells you to reboot the subsystem, 8. Click the OK button.
Automatic Restart
If you did NOT check the NDIU box, the RAID subsystem and JBOD expansion units automatically restart. That action temporarily disrupts I/O operations and drops your WebPAM PROe connection. To reestablish your WebPAM PROe connection: 1. 2. Wait no less than two minutes. Click Logout in the WebPAM PROe Header, then log in again. If you cannot log in, wait 30 seconds and try again.
Manual Restart
If you checked the NDIU box, you must restart the RAID subsystem and JBOD expansion units.
242
243
Updating with the CLU

Download the latest firmware image file from PROMISE support: http://www.promise.com/support/ and save it to your Host PC or TFTP server. Important Verify that no background activities are running on the RAID subsystem. To update the firmware on the RAID subsystem and JBOD expansion units: 1. 2. 3. 4. From the Main Menu, highlight Additional Info and Management, and press Enter. Highlight Flash through TFTP and press Enter. Highlight TFTP Server and type the IP address of your TFTP server in the field provided. Highlight Port Number and press the backspace key to erase the current value, then type the new value. 69 is the default. A list of the current users appears. 5. 6. Highlight File Name and type the file name of the firmware image file in the field provided. Highlight Flash Method and press the spacebar to toggle between: Disruptive Updates the RAID controllers and I/O modules simultaneously. I/O operations stop during the firmware update. Non Disruptive (NDIU) Updates the RAID controllers and I/O modules one at a time, enabling I/O operations continue during the firmware update. Updates with this option take a longer period of time to complete. Only VTrak x30 models support this feature.
7.
Highlight Start and press Enter. Warning Do NOT power off the RAID subsystem during the update! Do NOT move to any other screen until the firmware update operation is completed!
A message appears to tell you to reboot the VTrak. If you chose the Disruptive Flash Method, the RAID subsystem and JBOD expansion units automatically restart. If you chose the Non-Disruptive Flash Method, you must restart the RAID subsystem and JBOD expansion units.
244
Automatic Restart
If you chose the Disruptive Flash Method, the RAID subsystem and JBOD expansion units automatically restart. That action temporarily disrupts I/O operations and drops your CLU connection. After the screen goes blank, wait about two minutes, then re-establish your Telnet connection to the CLU. If you cannot re-establish a connection, wait 30 seconds and try again.
Manual Restart
If you chose the Non-Disruptive Flash Method, you must restart the RAID subsystem and JBOD expansion units. Important Do NOT turn off the power supply switches on the RAID subsystem or JBOD expansion units. To restart the subsystem: 1. 2. 3. 4. 5. 6. From the Main Menu, highlight Additional Info and Management, and press Enter. Highlight Shutdown or Restart and press Enter. Press the spacebar to display Restart then press Enter. A warning message appears. Press Y to continue. The screen goes blank. If you are using SSH, close your session. Wait about two minutes, then re-establish your Telnet or SSH connection to the VTrak CLU. If you cannot re-establish a connection, wait 30 seconds and try again.
245
Updating with USB Support

USB support uses the disruptive flash method only. Both RAID controllers and all JBOD I/O modules are updated at the same time and momentarily go offline when the RAID subsystem and JBOD unit reboot. This procedure requires a USB flash device: Formatted to FAT 32 At least 50 MB of free space
Download the latest OPAS_xxxxx.sbb firmware image file from PROMISE support: http://www.promise.com/support/ and save it the root folder of the USB flash device. Important Verify that no background activities are running on the RAID subsystem. To update the subsystem firmware using VTraks USB Support feature: 1. Insert the USB flash device into one of the USB ports on one of the RAID controllers.
Figure 1. FC RAID controller LEDs USB ports Controller Status LED
The controller status LED blinks green in half-second intervals. 2. Wait until the controller activity LED stops blinking green and starts blinking amber. Warning Do NOT power off the RAID subsystem during the update! Do NOT remove your USB flash device until the LED changes color!
3.
Within 30 seconds, remove the USB flash device, then insert the USB flash device back into the same RAID controller. The remove and insert action confirms that you want to update the firmware.
246
You can insert the USB flash device back into either USB port but it must be the same RAID controller as step 1. 4. 5. Wait until the controller activity LED displays steady green. Remove the USB flash device.
Automatic Restart
After you remove the USB flash device from the RAID controller, the RAID subsystem and any JBOD expansion units automatically restart. That action temporarily disrupts I/O operations and drops your WebPAM PROe or CLU connection. To reestablish your WebPAM PROe connection: 1. 2. Wait no less than two minutes. Click Logout in the WebPAM PROe Header, then log in again. If you cannot log in, wait 30 seconds and try again. To reestablish your CLU connection: After the screen goes blank, wait about two minutes, then re-establish your Telnet connection to the CLU. If you cannot re-establish a connection, wait 30 seconds and try again. If you have a serial connection to the RAID subsystem, the connection remains during the shut-down and restart. No reconnect is required.
Failed Update
If the firmware update fails, the controller status LED displays red. See page 246, Figure 1. 1. 2. 3. Remove the USB flash device. Insert the USB flash device into a USB port on your PC. Go to the OPAX_xxxxxx folder to obtain the report and log. Possible causes for an update failure include: Less than 50 MB free space on the USB flash device. The SBB firmware image is invalid. A background activity is running.
See Contacting Technical Support on page 351.
247
Updating Physical Drive Firmware

This feature applies only to PROMISE-supported physical drives. For a list of supported drives, go to PROMISE support: http://www.promise.com/support/. If you have physical drives in your RAID system that are not PROMISEsupported, follow the firmware update procedure from the drive manufacturer.
WebPAM PROe
Download the latest firmware image file from PROMISE support: http://www.promise.com/support/ and save it to your Host PC or TFTP server. To update the firmware on PROMISE-supported physical drives: 1. 2. 3. 4. Click the AdminTool tab. Click the Firmware Update icon. Click the PD Firmware Update tab. Choose a download option: Local File through HTTP Click the Browse button, locate the firmware image file, click the file to choose it, then click the Open button. TFTP Server Enter the TFTP Server host name or IP address, port number and file name.
5. 6.
Click the Next button. Click the Submit button. The progress of the update displays. Warning Do NOT power off the RAID subsystem during the update! Do NOT move to any other screen until the firmware update operation is completed!
When the update is completed a message tells you to reboot the subsystem. 7. Click the OK button. Restart the RAID subsystem. See Restarting a Subsystem on the next page.
248
Restarting a Subsystem
249
Replacing a Power Supply

The power supply and its fans are replaced as one unit. There are no individually serviceable parts. No tools are required for this procedure.
E830f and E630f

Removing the Old Power Supply
To remove the power supply: 1. 2. 3. 4. 5. Verify that the status LED is amber or red. See Figure 2. Switch off the power. Unplug the power cord. Turn the two set screws counter-clockwise to loosen them. The screws are retained on the power supply housing. Grasp the handle and pull the power supply out of the enclosure.
Figure 2. Power supply for VTrak E830f and E630f
Status LED Set screw
On/Off Switch Set screw
Handle
Installing a New Power Supply

To install the power supply: 1. 2. 3. 4. 5. Carefully slide the power supply into the enclosure. Turn the two set screws clockwise to tighten them. Plug in the power cord. Switch on the power supply. Verify that the new power supply LED is green. See Figure 2.
250
E330f
Removing the Old Power Supply
To remove the power supply: 1. 2. 3. 4. 5. 6. Verify that the status LED is amber or red. See Figure 3. Switch off the power. Unplug the power cord. Turn the set screw counter-clockwise to loosen it. The screw is are retained on the handle. Grasp the handle and swing it out and to the right. Pull the power supply out of the enclosure.
Figure 3. Power supply for VTrak E330f Status LED
Handle
Set screw
On/Off switch
Installing a New Power Supply

To install the power supply: 1. 2. 3. 4. 5. 6. Carefully slide the power supply into the enclosure. Press the handle in to secure the power supply. Turn the set screw clockwise to tighten it. Plug in the power cord. Switch on the power supply. Verify that the new power supply status LED is green. See Figure 3.
251
Replacing a Cache Backup Battery

The cache backup battery, also called a Battery Backup Unit (BBU) powers the cache to preserve data that has not been written the physical drives. The battery is located inside the RAID controller. Each RAID controller has its own battery. Cautions Try reconditioning the battery before you replace it. See Reconditioning a Battery on page 74 or page 174 for more information. The battery assembly is replaced as a unit. Do not attempt to disconnect the battery by itself. Installing the wrong replacement battery can result in an explosion. Dispose of used batteries according to the instructions that accompany the battery. While the battery is removed, your system is vulnerable to data loss if the power fails while data is being written to the logical drives. If power service has failed, do not remove the battery if the RAID controllers dirty cache LED is flashing. See page 253, Figure 4.
The cache backup battery is replaced as an assembly. You do not have to power down the RAID subsystem nor disconnect any cables from the RAID controller. You need a No. 1 Phillips screwdriver for this procedure.
E830f and E630f

Removing the Old Battery
To remove a battery: 1. 2. 3. Verify that the battery LED is amber or red. See page 253, Figure 4. Loosen and remove the set screw. Grasp the handle and pull the battery out of the RAID controller.
Installing a New Battery

To install the battery: 1. 2. 3. Carefully slide the battery into the RAID controller. Replace and tighten the set screw. Verify that the battery LED is green.
252
Figure 4. Cache backup battery Dirty cache LED Battery LED Set screw
VTrak E830f and E630f Dirty cache LED Battery LED Set screw
VTrak E330f
253
Replacing a RAID Controller Dual Controllers

The RAID controller monitors and manages the logical drives. When the RAID controller is replaced, all of your logical drive data and configurations remain intact because logical drive information is stored on the physical drives. Important Do not replace the RAID controller based on LED colors alone. Only replace the RAID controller when directed to do so by PROMISE Technical Support. See page 351. The firmware version and amount of SDRAM must be the same on the replacement RAID controller and the other RAID controller in the subsystem. To obtain firmware and SDRAM information for an installed RAID controller, in WebPAM PROe, click the AdminTool button then click the Image Version icon. Replacement RAID controllers to not come with a BBU. Remove the BBU from the old controller and install it into the new one. See Replacing a Cache Backup Battery on page 252. Note On subsystems with dual RAID controllers, you can hot-swap a controller while the subsystem is running.
Removing the Old Controller

To remove a RAID controller: 1. Disconnect all attached cables from the RAID controller, 2. 3. Fibre Channel cables SAS cable Ethernet (management) cables Serial cable USB cable UPS control cable
On the controller handle, squeeze the release tab and pull the handle outward. See page 255, Figure 5. Pull the RAID controller out of the subsystem enclosure.
254
Figure 5. RAID controllers Release tab and handle
VTrak E830f and E630f Release tab and handle
VTrak E330f
Installing the New Controller

To install the new RAID controller: 1. 2. 3. Carefully slide the RAID controller into the enclosure. Gently swing the handle in and press the handle until it locks. Reconnect all cables that were attached to the RAID controller, Fibre Channel cables SAS cable Ethernet (management) cables Serial cable USB cable UPS control cable
If one of the controllers goes into maintenance mode, see Maintenance Mode on page 312.
255
Replacing a RAID Controller Single Controller

The RAID controller monitors and manages the logical drives. When the RAID controller is replaced, all of your logical drive data and configurations remain intact because logical drive information is stored on the physical drives. Caution The RAID controller is NOT hot-swappable if your VTrak has only one controller. Power-down the VTrak before removing it. Important Do not replace the RAID controller based on LED colors alone. Only replace the RAID controller when directed to do so by PROMISE Technical Support. See page 351. Important The firmware on the replacement RAID controller must be the same version as the original RAID controller or a later version. The amount of SDRAM in the replacement RAID controller must be the same as the original RAID controller or greater. To obtain firmware and SDRAM information for the currently installed RAID controller, click the AdminTool button then click the Image Version icon.
Removing the Old Controller

To remove the RAID controller: 1. 2. 3. Shutdown the VTrak. See Shutting Down the Subsystem on page 67 (WebPAM PROe) or page 233 (CLU). Switch off the power. Disconnect all attached cables from the RAID controller, 4. 5. Fibre Channel cables SAS cable Ethernet (management) cables Serial cable USB cable UPS control cable
On the controller handle, squeeze the release tab and pull the handle outward. See page 255, Figure 5. Pull the RAID controller out of the subsystem enclosure.
256
Installing the New Controller

To install the new RAID controller: 1. 2. 3. Carefully slide the RAID controller into the enclosure. Gently swing the handle in and press the handle until it locks. Reconnect all cables that were attached to the RAID controller, 4. Fibre Channel cables SAS cable Ethernet (management) cables Serial cable USB cable UPS control cable
Turn on the power supply switches. The VTrak restarts. For more information about VTraks start-up behavior, see Connecting the Power on page 33.
5.
Log into the VTrak. For more information, see Logging into WebPAM PROe on page 51 or Initial Connection on page 156.
257
Resetting the Default Password

This feature resets the Administrators password to the default factory setting, password. Use this feature when you have forgotten Administrators password or a new Administrator has been appointed. The reset applies to the Administrators login for WebPAM PROe, the CLI, and the CLU. No other user passwords are affected. To reset the Administrators default password: 1. 2. 3. Verify that the VTrak has fully booted. See page 33 or page 295 for more information. For one of the RAID controllers, locate the password reset switch. See Figure 6. Insert a pin or a straightened paper clip into the opening and momentarily depress password reset switch. You only need to press the reset switch on one RAID controller. Figure 6. FC RAID controller password reset Password reset switch
The next time the Administrator logs in, use the default password, password. For more information, see Logging into WebPAM PROe on page 51 and Logging Into the CLI on page 158. Important PROMISE recommends that you change the Administrators default password immediately after reset. See Changing User Passwords on page 87 or page 219.
258
Chapter 7: Technology Background

This chapter covers the following topics: Disk Arrays (below) Logical Drives (page 261) Spare Drives (page 283) RAID Controllers (page 289)
Disk Arrays
Media Patrol
Media Patrol is a routine maintenance procedure that checks the magnetic media on each disk drive. Media Patrol checks all physical drives assigned to disk arrays and spare drives. Media Patrol does not check unconfigured drives. Media Patrol checks are enabled by default on all disk arrays and spare drives. You can disable Media Patrol in the disk array and spare drive settings, however that action is not recommended. Unlike Synchronization and Redundancy Check, Media Patrol is concerned with the condition of the media itself, not the data recorded on the media. If Media Patrol encounters a critical error, it triggers PDM, if PDM is enabled on the disk array. Media Patrol has three status conditions: Running Normal. You can access your logical drives at any time. Yield Temporary pause while a read/write operation takes place. Paused Temporary pause while another background runs. Or a pause initiated by the user. See Running Media Patrol on a Disk Array on page 129
PDM
Predictive Data Migration (PDM) is the migration of data from the suspect disk drive to a spare disk drive, similar to rebuilding a logical drive. But unlike Rebuilding, PDM constantly monitors your disk drives and automatically copies your data to a spare disk drive BEFORE the disk drive fails and your logical drive goes Critical. The following actions trigger PDM: A disk drive with unhealthy status (see below) Media Patrol finds a disk critical error
259
You initiate PDM manually
PDM also counts the number of media errors reported by Media Patrol. A disk drive becomes unhealthy when: A SMART error is reported The bad sector remapping table fills to the specified level.
Because data would be lost if written to a bad sector, when a bad sector is detected, the disk drive creates a map around it. These maps are saved in the bad sector remapping table, which have a capacity of 512 reassigned blocks and 2048 error blocks. See Making PDM Settings. You can specify the maximum levels for the reassigned and error blocks in PDM settings. When the table fills to a specified value, PDM triggers a migration of data from the suspect drive (the disk drive with the bad sectors) to a replacement physical drive. During data migration, you have access to your logical drives but they respond more slowly to read/write tasks because of the additional operation. The time required for data migration depends on the size of the disk drives. PDM is enabled on all disk arrays by default. You can disable PDM in the disk array settings, however that action is not recommended. See Running PDM on a Disk Array on page 129 or page 188.
Power Management
See Power Saving on page 291.
260
Logical Drives
RAID Levels
RAID (Redundant Array of Independent Disks) allows multiple physical drives to be combined together in a disk array. Then all or a portion of the disk array is formed into a logical drive. The operating system sees the logical drive as a single storage device, and treats it as such.
RAID 0 Stripe
When a logical drive is striped, the read and write blocks of data are interleaved between the sectors of multiple physical drives. Performance is increased, since the workload is balanced between drives or members that form the logical drive. Identical drives are recommended for performance as well as data storage efficiency. Figure 1. RAID 0 Striping interleaves data across multiple drives Data Stripe
Physical Drives The disk arrays data capacity is equal to the number of disk drive members multiplied by the smallest drives capacity. For example, one 100 GB and three 120 GB drives form a 400 GB (4 x 100 GB) disk array instead of 460 GB. If physical drives of different capacities are used, there is unused capacity on the larger drives. RAID 0 logical drives on VTrak consist of one or more physical drives.
261
Advantages Implements a striped disk array, the data is broken down into blocks and each block is written to a separate disk drive I/O performance is greatly improved by spreading the I/O load across many channels and drives No parity calculation overhead is involved
Disadvantages Not a true RAID because it is not fault-tolerant The failure of just one drive results in all data in an disk array being lost Should not be used in mission critical environments
Recommended Applications for RAID 0: Image Editing Pre-Press Applications Any application requiring high bandwidth
262
RAID 1 Mirror
When a logical drive is mirrored, identical data is written to a pair of physical drives, while reads are performed in parallel. The reads are performed using elevator seek and load balancing techniques where the workload is distributed in the most efficient manner. Whichever drive is not busy and is positioned closer to the data is accessed first. With RAID 1, if one physical drive fails or has errors, the other mirrored physical drive continues to function. Moreover, if a spare physical drive is present, the spare drive is used as the replacement drive and data begins to mirrored to it from the remaining good drive. Figure 2. RAID 1 Mirrors identical data to two drives Data Mirror
Physical Drives The logical drives data capacity equals the smaller physical drive. For example, a 100 GB physical drive and a 120 GB physical drive have a combined capacity of 100 GB in a mirrored logical drive. If physical drives of different capacities are used, there is unused capacity on the larger drive. RAID 1 logical drives on VTrak consist of two physical drives. If you want a mirrored logical drive with more than two physical drives, see RAID 1E Enhanced Mirror on page 265.
263
Advantages Simplest RAID storage subsystem design Can increase read performance by processing data requests in parallel since the same data resides on two different drives
Disadvantages Very high disk overhead uses only 50% of total capacity
Recommended Applications for RAID 1: Accounting Payroll Financial Any application requiring very high availability
264
RAID 1E Enhanced Mirror

RAID 1E offers the security of mirrored data provided by RAID 1 plus the added capacity of more than two physical drives. It also offers overall increased read/ write performance plus the flexibility of using an odd number of physical drives. With RAID 1E, each data stripe is mirrored onto two physical drives. If one drive fails or has errors, the other drives continue to function, providing fault tolerance. Figure 3. RAID 1E can mirror data over an odd number of drives Enhanced Data Mirrors
Physical Drives The advantage of RAID 1E is the ability to use an odd number of physical drives, unlike RAID 1 and RAID 10. You can also create a RAID 1E Logical Drive with an even number of physical drives. However, with an even number of drives, you obtain somewhat greater security with comparable performance using RAID 10. RAID 1E logical drives consist of three or more physical drives. You can create an array with just two physical drives and specify RAID 1E. But the resulting array is actually a RAID 1. Advantages Implemented as a mirrored disk array whose segments are RAID 0 disk arrays High I/O rates are achieved thanks to multiple stripe segments Can use an odd number of disks Disadvantages Very high disk overhead uses only 50% of total capacity
Recommended Applications for RAID 1E: Imaging applications Database servers General fileserver
265
RAID 5 Block and Parity Stripe

RAID 5 organizes block data and parity data across the physical drives. Generally, RAID Level 5 tends to exhibit lower random write performance due to the heavy workload of parity recalculation for each I/O. RAID 5 is generally considered to be the most versatile RAID level. It works well for file, database, application and web servers. Figure 4. RAID 5 stripes all drives with data and parity information Distributed Parity Data Blocks
Physical Drives The capacity of a RAID 5 logical drive equals the smallest physical drive times the number of physical drives, minus one. Hence, a RAID 5 logical drive with four 100 GB physical drives has a capacity of 300 GB. A RAID 5 logical drive with two 120 GB physical drives and one 100 GB physical drive has a capacity of 200 GB. RAID 5 is generally considered to be the most versatile RAID level. A RAID 5 on VTrak consists of 3 to 32 physical drives. Advantages High Read data transaction rate Medium Write data transaction rate Good aggregate transfer rate Most versatile RAID level Disadvantages Disk failure has a medium impact on throughput
Recommended Applications for RAID 5: File and Application servers WWW, E-mail, and News servers Intranet servers
266
RAID 6 Block and Double Parity Stripe

RAID level 6 stores dual parity data is rotated across the physical drives along with the block data. A RAID 6 logical drive can continue to accept I/O requests when any two physical drives fail. Figure 5. RAID 6 stripes all drives with data and dual parity Data Blocks Double Distributed (Wide-space Q+Q) Parity
Physical Drives Hence, a RAID 6 logical drive with (7) 100 GB physical drives has a capacity of 500 GB. A RAID 6 logical drive with (4) 100 GB physical drives has a capacity of 200 GB. RAID 6 becomes more capacity efficient in terms of physical drives as the number of physical drives increases. RAID 6 provides double fault tolerance. Your logical drive remains available when up to two physical drives fail. RAID 6 is generally considered to be the safest RAID level. A RAID 6 on VTrak consists of 4 to 32 physical drives. Advantages High Read data transaction rate Medium Write data transaction rate Good aggregate transfer rate Safest RAID level, except for RAID 60 Disadvantages High disk overhead equivalent of two drives used for parity Slightly lower performance than RAID 5
Recommended Applications for RAID 6: Accounting and Financial Database servers Any application requiring very high availability
267
RAID 10 Mirror + Stripe

Mirror + Stripe combines both of the RAID 1 and RAID 0 logical drive types. RAID 10 can increase performance by reading and writing data in parallel or striping, and duplicating the data, or mirroring. PROMISE implements RAID 10 by creating a data stripe over one pair of disk drives, then mirroring the stripe over a second pair of disk drives. Some applications refer to this method as RAID 0+1. Figure 6. PROMISE RAID 10 starts with a data stripe, then mirrors it 1. Data Stripe
2. Data Mirror
Disk Drives The data capacity RAID 10 logical drive equals the capacity of the smallest physical drive times the number of physical drives, divided by two. In some cases, RAID 10 offers double fault tolerance, depending on which physical drives fail. RAID 10 arrays require an even number of physical drives and a minimum of four. For RAID 10 characteristics using an odd number of physical drives, choose RAID 1E.
268
Advantages Implemented as a mirrored disk array whose segments are RAID 0 disk arrays High I/O rates are achieved thanks to multiple stripe segments
Disadvantages Very high disk overhead uses only 50% of total capacity
Recommended Applications for RAID 10: Imaging applications Database servers General fileserver
269
RAID 50 Striping of Distributed Parity

RAID 50 combines both RAID 5 and RAID 0 features. Data is striped across physical drives as in RAID 0, and it uses distributed parity as in RAID 5. RAID 50 provides data reliability, good overall performance, and supports larger volume sizes. Figure 7. RAID 50 is a combination of RAID 5 and RAID 0 Distributed Parity
Axle 1 Data Stripes
Axle 2
Disk Drives The data capacity RAID 50 logical drive equals the capacity of the smallest physical drive times the number of physical drives, minus two. RAID 50 also provides very high reliability because data is still available even if multiple physical drives fail (one in each axle). The greater the number of axles, the greater the number of physical drives that can fail without the RAID 50 logical drive going offline. Component Number of Axles Physical Drives per Axle Physical Drives per Logical Drive Minimum 2 3 6 Maximum 16 32 256
RAID 50 Axles
When you create a RAID 50, you must specify the number of axles. An axle refers to a single RAID 5 logical drive that is striped with other RAID 5 logical drives to make RAID 50. An axle can have from 3 to 32 physical drives, depending on the number of physical drives in the logical drive.
270
The chart below shows RAID 50 logical drives with 6 to 32 physical drives, the available number of axles, and the resulting distribution of physical drives on each axle. RAID 50 Logical Drive No. of Drives 6 7 8 9 No. of Axles 2 2 2 2 3 10 2 3 11 2 3 12 2 3 4 13 2 3 4 Drives per Axle 3,3 3,4 4,4 4,5 3,3,3 5,5 3,3,4 5,6 3,4,4 6,6 4,4,4 3,3,3,3 6,7 4,4,5 3,3,3,4 16 15 No. of Drives 14 No. of Axles 2 3 4 2 3 4 5 2 3 4 5 Drives per Axle 7,7 4,5,5 3,3,4,4 7,8 5,5,5 3,4,4,4 3,3,3,3,3 8,8 5,5,6 4,4,4,4 3,3,3,3,4
Advantages High Read data transaction rate Medium Write data transaction rate Good aggregate transfer rate High reliability Supports large volume sizes
Disadvantages Higher disk overhead than RAID 5
271
Recommended Applications for RAID 50: File and Application servers Transaction processing Office application with many users accessing small files
272
RAID 60 Striping of Double Parity

RAID 60 combines both RAID 6 and RAID 0 features. Data is striped across disks as in RAID 0, and it uses double distributed parity as in RAID 6. RAID 60 provides data reliability, good overall performance and supports larger volume sizes. Figure 8. RAID 60 is a combination of RAID 6 and RAID 0 Double Distributed Parity
Axle 1 Data Stripes Axle 2
Disk Drives The total capacity of a RAID 60 logical drive is the smallest physical drive times the number of physical drives, minus four. RAID 60 also provides very high reliability because data is still available even if multiple physical drives fail (two in each axle). The greater the number of axles, the greater the number of physical drives that can fail without the RAID 60 logical drive going offline. Component Number of Axles Physical Drives per Axle Physical Drives per Logical Drive Minimum 2 4 8 Maximum 16 32 256
RAID 60 Axles
When you create a RAID 60, you must specify the number of axles. An axle refers to a single RAID 6 logical drive that is striped with other RAID 6 logical drives to make RAID 60. An axle can have from 4 to 32 physical drives, depending on the number of physical drives in the logical drive.
273
RAID 60 Logical Drive No. of Drives 8 9 10 11 12 No. of Axles 2 2 2 2 2 3 13 2 3 14 2 3 15 2 3 16 2 3 4 Advantages High Read data transaction rate Medium Write data transaction rate Good aggregate transfer rate Safest RAID level Drives per Axle 4,4 4,5 5,5 5,6 6,6 4,4,4 6,7 4,4,5 7,7 4,5,5 7,8 5,5,5 8,8 5,5,6 4,4,4,4 Disadvantages High disk overhead equivalent of two drives used for parity Slightly lower performance than RAID 50 20 19 18 No. of Drives 17 No. of Axles 2 3 4 2 3 4 2 3 4 2 3 4 5 Drives per Axle 8,9 5,6,6 4,4,4,5 9,9 6,6,6 4,4,5,5 9,10 6,6,7 4,5,5,5 10,10 6,7,7 5,5,5,5 4,4,4,4,4
Recommended Applications for RAID 60: Accounting and Financial Database servers Any application requiring very high availability
274
RAID Level Migration

On VTrak, RAID level migration is performed on the disk array but it applies to the logical drives. Migration does not disturb your data. You can access the data while the migration is in progress. When migration is done, your disk array has a different RAID level and/or a larger capacity.
Migration Requirements
The following conditions affect RAID level migration: The disk array and logical drive must show a green check icon.
The Target disk array may require more physical drives than the Source disk array. If the Target disk array requires an EVEN number of physical drives but the Source disk array has an ODD number, ADD a physical drive as part of the migration process. You cannot reduce the number of physical drives in your disk array, even if the Target disk array requires fewer physical drives than the Source disk array. RAID 1 (mirroring) works with two drives only. Only a single-drive RAID 0 disk array can migrate to RAID 1. Other RAID Levels use too many drives to migrate. You cannot migrate a disk array when it is Critical or performing activities such as Synchronizing, Rebuilding, and PDM. For RAID 6 or RAID 60, you can only migrate between these two RAID levels. Destination RAID 60 axles can have up to 16 physical drives. Other limitations might apply.
Source and Target RAID Levels

The tables on the following pages show the migration options for each source logical drive by its RAID level. The available target RAID levels are shown with their requirements.
275
RAID 0
A RAID 0 source logical drive can migrate to the following target logical drives: Target RAID 0 RAID 1 Add physical drives. 2 physical drives only. Only a single-drive RAID 0 can migrate to RAID 1 by adding 1 physical drive. 3 or more physical drives. If existing physical drives have no unused space, add 1 or more physical drives. 3 physical drives minimum, 32 maximum. RAID 0 must have less than 16 physical drives. If existing physical drives have no unused space, add 1 or more physical drives. 4 physical drives minimum, 32 maximum. If existing physical drives have no unused space, add 1 or more physical drives. 4 physical drives minimum. Even number of physical drives. If existing physical drives have no unused space, add 1 or more physical drives. 6 physical drives minimum, 32 per axle maximum. If existing physical drives have no unused space, add 1 or more physical drives. 8 physical drives minimum, 32 per axle maximum. If existing physical drives have no unused space, add 1 or more physical drives. Requirements
RAID 1E
RAID 5
RAID 6
RAID 10
RAID 50
RAID 60
276
RAID 1
A RAID 1 Source logical drive can migrate to the following Target logical drives: Target RAID 0 RAID 1E RAID 5 None. 3 or more physical drives. Add 1 or more physical drives. 3 physical drives minimum, 32 maximum. RAID 1 must have less than 32 physical drives. Add 1 or more physical drives. 4 physical drives minimum. Even number of physical drives. Add 2 or more physical drives. 6 physical drives minimum, 32 per axle maximum. Add 4 or more physical drives. Requirements
RAID 10
RAID 50
RAID 1E
A RAID 1E Source logical drive can migrate to the following Target logical drives: Target RAID 0 RAID 1E RAID 5 None. Add physical drives. 3 physical drives minimum, 32 maximum. RAID 1E must have less than 32 physical drives. If existing physical drives have no unused space, add 1 or more physical drives. 4 physical drives minimum. Even number of physical drives. If existing physical drives have no unused space, add 1 or more physical drives. 6 physical drives minimum, 32 per axle maximum. Requirements
RAID 10
RAID 50
277
RAID 5
A RAID 5 Source logical drive can migrate to the following Target logical drives: Target RAID 0 RAID 1E RAID 5 RAID 6 None. None. Add physical drives. 32 maximum. 4 physical drives minimum, 32 maximum. If existing physical drives have no unused space, add 1 or more physical drives. 4 physical drives minimum. Even number of physical drives. If existing physical drives have no unused space, add 1 or more physical drives. 6 physical drives minimum, 32 per axle maximum. If existing physical drives have no unused space, add 1 or more physical drives. 8 physical drives minimum, 32 per axle maximum. If existing physical drives have no unused space, add 1 or more physical drives. Requirements
RAID 10
RAID 50
RAID 60
RAID 6
A RAID 6 Source logical drive can migrate to the following Target logical drives: Target RAID 6 RAID 60 Requirements Add physical drives. 32 maximum. 8 physical drives minimum, 32 per axle maximum. If existing physical drives have no unused space, add 1 or more physical drives.
278
RAID 10
A RAID 10 Source logical drive can migrate to the following Target logical drives: Target RAID 0 RAID 1E RAID 5 RAID 6 None. None. 3 physical drives minimum, 32 maximum. RAID 10 must have less than 16 physical drives. 4 physical drives minimum, 32 maximum. RAID 10 must have less than 32 physical drives. If existing physical drives have no unused space, add 1 or more physical drives. Add physical drives. Even number of physical drives. 6 physical drives minimum, 32 per axle maximum. 8 physical drives minimum, 32 per axle maximum. If existing physical drives have no unused space, add 1 or more physical drives. Requirements
RAID 10 RAID 50 RAID 60
When you migrate RAID 10 logical drive, it becomes RAID 1E by default. If you want a RAID 10 logical drive, there must be an even number of physical drives and you must specify RAID 10 for the target logical drive.
279
RAID 50
A RAID 50 Source logical drive can migrate to the following Target logical drives: Target RAID 0 RAID 1E RAID 5 RAID 6 None. None. 32 physical drives maximum. RAID 50 must have less than 32 physical drives. 32 physical drives maximum. RAID 50 must have less than 32 physical drives. If existing physical drives have no unused space, add 1 or more physical drives. Even number of physical drives. Add physical drives. 32 per axle maximum. 8 physical drives minimum, 32 per axle maximum. If existing physical drives have no unused space, add 1 or more physical drives. Requirements
RAID 10 RAID 50 RAID 60
You can add physical drives to a RAID 50 array but you cannot change the number of axles.
RAID 60
A RAID 60 Source logical drive can migrate to the following Target logical drives: Target RAID 6 Requirements 32 physical drives maximum. RAID 60 must have less than 32 physical drives. If existing physical drives have no unused space, add 1 or more physical drives. Add physical drives. 32 per axle maximum.
RAID 60
You can add physical drives to a RAID 60 array but you cannot change the number of axles.
280
Stripe Size
Stripe Size, also called Stripe Block Size, refers to the size of the data blocks written to, and read from, the physical drives. Stripe Size is specified when you create a logical drive. You can choose Stripe Size directly when you use the Wizard Advanced Configuration function to create a logical drive. You cannot change the Stripe Size of an existing logical drive. You must delete the logical drive and create a new one. The available Stripe Sizes are 64 KB, 128 KB, 256 KB, 512 KB, and 1 MB. 64 KB is the default. There are two issues to consider when choosing the Stripe Size: You should choose a Stripe Size equal to, or smaller than, the smallest cache buffer found on any physical drive in the disk array. Selecting a larger value slows read/write performance because physical drives with smaller cache buffers need more time for multiple accesses to fill their buffers. If your data retrieval consists of fixed data blocks, such as with some database or video applications, then you should choose that size as your Stripe Size.
If you do not know the cache buffer or fixed data block sizes, choose 64 KB as your Stripe Size. Generally speaking, Email, POS, and web servers prefer smaller stripe sizes. Video and database applications prefer larger stripe sizes.
Sector Size
A sector is the smallest addressable area on a physical drive. Sector size refers to the number of data bytes a sector can hold. A smaller sector size is a more efficient use of a physical drives capacity. 512 bytes (512 B) is the most common sector size, and the default in WebPAM PROe.
Preferred Controller ID
When you create a logical drive using the Advanced method of disk array creation, you can specify the Preferred Controller ID: Controller 1 Assign all logical drives to Controller 1 Controller 2 Assign all logical drives to Controller 2. Automatic Alternate logical drive assignments between Controllers 1 and 2.
Automatic is the default and preferred setting because it balances the logical drive assignments for you. See Creating a Disk Array Manually on page 122, Creating a Disk Array with the Wizard on page 123, and Creating a Disk Array Advanced on page 183.
281
Initialization
Initialization is done to logical drives after they are created from a disk array. Full initialization sets all data bits in the logical drive to a specified pattern, such as all zeros. The action is useful because there may be residual data on the logical drives left behind from earlier configurations. For this reason, Initialization is recommended for all new logical drives. See Initializing a Logical Drive on page 137 or page 197. Caution When you initialize a logical drive, all the data on the logical drive is lost. Backup any important data before you initialize a logical drive.
Partition and Format

Like any other type of fixed disk media in your system, a RAID logical drive must also be partitioned and formatted before use. Use the same method of partitioning and formatting on an logical drive as you would any other fixed disk. Depending on the operating system you use, there may or may not be various capacity limitations applicable for the different types of partitions.
282
Spare Drives
A spare drive is a physical drive that you designate to automatically replace the failed physical drive in a disk array. See Creating a Spare Drive Manually on page 142. The general recommendation is to: Provide at least one spare drive for every 16 physical drives in the RAID system Configure the spares as global revertible spare drives
Options
There are several options you can specify for a spare drive: System Options Revertible Returns to its spare drive assignment after you replace the failed physical drive in the disk array and run the Transition function. Media Patrol By default, Media Patrol runs on spare drives unless you disable it. Global Can be used by any disk array Dedicated Can be used only by the assigned disk array Hard Disk Drive (HDD) Solid State Drive (SSD)
Spare Type
Media Type (type of physical drive)
Requirements
The spare drive must: Have adequate capacity to replace the largest physical drive in your disk arrays. Be the same media type as the physical drives in your disk arrays.
A revertible spare drive requires: You to replace the failed physical drive in the disk array You to run the Transition function
283
Transition
Transition is the process of replacing a revertible spare drive that is currently part of a disk array with an unconfigured physical drive or a non-revertible spare. The revertible spare drive returns to its original status. In order to run the Transition function, the spare drive must be revertible. In addition, you must specify an unconfigured physical drive of the same or larger capacity and same media type as the revertible spare drive.
Running a Transition
The Transition feature enables you to specify permanent spare drives for your VTrak subsystem. Transition is the process of replacing a revertible spare drive that is currently part of a disk array with an unconfigured physical drive or a nonrevertible spare. The revertible spare drive returns to its original status. Transition happens automatically when the following sequence of events takes place: You create a revertible spare drive. See Creating a Spare Drive Manually on page 142 or page 193. A physical drive assigned to your disk array fails and the array goes critical or degraded. VTrak automatically rebuilds your array to the revertible spare drive and the array becomes functional again. You replace the failed physical drive with a new physical drive of equal or greater capacity. VTrak automatically transitions (moves) the data from the revertible spare to the new physical drive. The new physical drive becomes part of the array and the revertible spare drive returns to its original spare status.
Transition happens manually when you specify a different unconfigured physical drive to transition (move) the data from the revertible spare drive. See the example on the following pages.
284
Example
Following is an example to explain the Transition function.
1 2 3 4 5 6 Spare Drive Array Drives
In the example above, there is a four-drive RAID 5 disk array and a global spare drive. Physical drives 1, 2, 3, and 4 belong to the disk array. Physical drive 5 remains unconfigured. Physical drive 6 is a revertible spare drive.
1 2 3 4 5 6 Rebuild to Spare Failed Drive
If a physical drive fails in a disk array and there is a spare drive of adequate capacity available, the controller automatically rebuilds the array using the spare
285
drive. In this example, physical drive 3 failed and the array is rebuilt using physical drive 6, the revertible spare drive.
1 2 3 4 5 6
When the rebuild is complete, the spare drive has replaced the failed drive. In this example, failed drive 3 was replaced by spare drive 6. The disk array now consists of physical drives 1, 2, 4, and 6. There is no spare drive at this moment. Even if physical drive 5 is of adequate capacity, it has not been designated as a spare, therefore the controller cannot use it as a spare.
Array Drives
286
Automatic Transition
At this juncture, you would replace the failed drive in slot 3 with a new one of the same or greater capacity.
When the VTrak controller detects the new drive in slot 3, the controller: Automatically transitions the data on drive 6 to drive 3 Returns drive 6 to spare status
When the Automatic Transition is finished, physical drives 1, 2, 3, and 4 belong to the disk array and physical drive 6 is a revertible spare drive. The original configuration is restored.
Manual Transition
If you wanted to use the drive in slot 5 as a member of the disk array, rather than the drive in slot 3, you would run the Transition function manually. See Running a Transition on a Spare Drive on page 144 or Running Transition on a Disk Array on page 190.
287
When the Manual Transition is finished, physical drives 1, 2, 4, and 5 belong to the disk array and physical drive 6 is a revertible spare drive. At this point, you would replace the drive in slot 3. The new drive in slot 3 remains unconfigured until you assign it to a disk array or as a spare.
288
RAID Controllers
LUN Affinity
VTrak subsystems with two controllers include a LUN Affinity feature. Normally, either controller can access all logical drives. LUN Affinity enables you to specify which controller can access each logical drive. Use this feature to balance the load of your logical drives between the two controllers. To use LUN Affinity you must: Have two controllers in the subsystem Enable LUN Affinity under controller settings.
On subsystems with two controllers, when Cache Mirroring is disabled, LUN Affinity is enabled automatically.
Cache Policy
As it is used with VTrak, the term cache refers to any of several kinds of highspeed, volatile memory that hold data moving from your computer to the physical drives or vice-versa. Cache is important because it can read and write data much faster than a physical drive. There are read caches, which hold data as it is read from a physical drive; and write caches, which hold data as it is written to a physical drive. In order to tune the cache for best performance in different applications, useradjustable settings are provided. Cache settings are made in when you create a logical drive. you can also change them under logical drive settings.
Read Cache Policy

Read Cache The read cache is enabled but no pre-fetch action. Read Ahead The read cache and predictive pre-fetch feature are enabled. Read-ahead anticipates the next read and performs it before the request is made. Can increase read performance. Forced Read Ahead The read cache and aggressive pre-fetch feature are enabled. See Forced Read-Ahead Cache below. No Cache The read cache is disabled.
Write Cache Policy

Write Back Data is written first to the cache, then to the logical drive. Better performance. VTrak has a cache backup battery to protect data in the cache from a sudden power failure. Adaptive Writeback See Adaptive Writeback Cache below.
289
Write Thru Also Write Through. Data is written to the cache and the logical drive at the same time. Safer.
If your write cache policy is set to Write Back, the write policy automatically changes to Write Thru when all of the following conditions occur: The logical drive write policy is set to Write Back The Adaptive Writeback Cache feature is enabled The cache backup battery goes offline
When the battery comes back online, the write policy automatically changes back to Write Back. Also see Viewing Battery Information on page 73 or page 173.
Forced Read-Ahead Cache

On the VTrak subsystem, you can set the logical drive read cache policy to Forced Read Ahead an enable the aggressive pre-fetch feature. The Forced Read-Ahead cache policy setting provides predictive pre-fetching of data requests, allowing the controller to aggressively buffer large chunks of data in cache memory to prevent frame drops on high-bandwidth video playback. Not normally enabled for non-video applications.
Adaptive Writeback Cache

On the VTrak subsystem, you can set the logical drive write cache policy to Write Thru or Write Back. If you set the write cache policy to Write Back, your data is first written to the controller cache, and later to the logical drive. This action improves performance. To preserve the data in the cache in the event of a power failure, the subsystem has a backup battery that powers the cache. To see an estimate of how long the battery can power the cache, see Viewing Battery Information on page 73 or Viewing Battery Information on page 173. The Adaptive Writeback Cache feature protects your data by changing the write cache settings while the cache backup battery is offline. When all of the following conditions occur: The logical drive write policy is set to Write Back. The Adaptive Writeback Cache feature is enabled. The cache backup battery goes offline.
The write policy automatically changes to Write Thru. When the battery comes back online, the write policy automatically changes back to Write Back. To enable the Adaptive Writeback Cache option, see Making Controller Settings on page 70 or page 167.
290
Preferred Controller ID
See Preferred Controller ID on page 281.
Power Saving
Power saving is a method of conserving energy by applying specific actions to hard disk drives (HDD). After an HDD has been idle for the set period of time, you can elect to: Parking the read/write heads Referred to as Power Saving Idle Time on VTrak. Reducing disk rotation speed Referred to as Power Saving Standby Time on VTrak. Spinning down the disk (stop rotation) Referred to as Power Saving Stopped Time on VTrak.
Power management must be: Set on the RAID controller. See Making Controller Settings on page 70 or page 167. Enabled on each HDD. See Making Disk Array Settings on page 128 or page 184.
Capacity Coercion
This feature is designed for fault-tolerant logical drives (RAID 1, 1E, 5, 10, 50, and 60). It is generally recommended to use physical drives of the same size in your disk arrays. When this is not possible, the system adjusts for the size differences by reducing or coercing the capacity of the larger drives to match the smaller ones. With VTrak, you can choose to enable capacity coercion and any one of four methods. Enable capacity coercion and choose the method in the Controller Settings menu. See page 122 or page 177. The choices are: GB Truncate (Default) Reduces the useful capacity to the nearest 1,000,000,000 byte boundary. 10GB Truncate Reduces the useful capacity to the nearest 10,000,000,000 byte boundary. Group Rounding Uses an algorithm to determine how much to truncate. Results in the maximum amount of usable drive capacity. Table Rounding Applies a predefined table to determine how much to truncate.
Capacity coercion also affects a replacement drive used in a disk array. Normally, when an physical drive fails, the replacement drive must be the same capacity or larger. However, the capacity coercion feature permits the installation of a
291
replacement drive that is slightly smaller (within 1 gigabyte) than the remaining working drive. For example, the remaining working drives can be 80.5 GB and the replacement drive can be 80.3, since all are rounded down to 80 GB. This permits the smaller drive to be used. Without capacity coercion, the controller does not permit the use of a replacement physical drive that is slightly smaller than the remaining working drives.
292
Chapter 8: Troubleshooting
This chapter contains the following topics: VTrak is Beeping (below) LEDs Display Amber or Red (page 295) CLU Reports a Problem (page 300) WebPAM PROe Reports a Problem (page 303) USB Support Reports a Problem (page 307) Enclosure Problems (page 308) Controller Problems (page 312) Disk Array and Logical Drive Problems (page 317) Physical Drive Problems (page 316) Connection Problems (page 322) Power Cycling the Subsystem (page 326) Event Notification Response (page 327)
VTrak is Beeping
VTraks alarm has five different patterns, as shown below. Figure 1. Audible alarm sound patters
1 2 3 4 5
.25s .25s .25s
1x
.25s .75s .25s 2.5s
.25s
.75s
.25s
.5s
.25s
6s
.25s .25s .25s
.5s
.25s
.75s
.25s
1s
.25s
1.25s
.25s
3s
2x
When you first power-up the VTrak, it beeps twice to show normal operation. The audible alarm sounds at other times to inform you that the VTrak needs attention. But the alarm does not specify the condition. When the alarm sounds: Check the front and back of VTrak enclosure for red or amber LEDs. If email notification is enabled, check for new messages.
293
Check for yellow ! Check the event log.
red X
icons.
See Viewing Runtime Events on page 300 and Viewing NVRAM Events on page 300. When a continuous tone sounds, there are multiple alarm patterns sounding at the same time.
Silencing the Buzzer

Caution This action disables the buzzer for all events.
To silence the buzzer: 1. 2. 3. 4. 5. Click the Device tab. Click the Component List icon. Mouse-over the Buzzer and click the Settings button. Uncheck the Enable Buzzer box. Click the Save button.
294
LEDs Display Amber or Red

LEDs are used on VTraks: Front Panel LEDs (page 295) Drive Carrier LEDs (page 296) Back Panel LEDs (page 297)
Front Panel LEDs

When the power is switched on, the LEDs on the front of the VTrak light up. Figure 1. Front panel LED display
Power FRU Status Logical Drive Status Controller 1 Activity Controller 2 Activity Controller Heartbeat
When boot-up is finished and the VTrak is functioning normally: Power, FRU, and Logical Drive LEDs display steady green. Each controller activity LED flashes green when there is activity on that controller. The controller heartbeat LED blinks green once per second for five seconds, goes dark for ten seconds, then blinks green once per second for five seconds again. Steady means the LED is on. Blinking means a regular on/off pattern. Flashing means an intermittent and irregular on/off pattern. Dark means the LED is off.
295
See the table below. Enclosure Front LEDs State Dark Steady Green Blinking Green Flashing Green Amber Red Power No power Normal FRU No power Normal Problem* Failure* Logical Drive Normal Critical Offline Controller Activity No Activity Activity Controller Heartbeat Normal**
* Check the LEDs on the back of the VTrak enclosure. ** Blinks blinks green once per second for five seconds, goes dark for ten seconds, then blinks green once per second for five seconds again. See Enclosure Problems on page 308, Controller Problems on page 312, and Disk Array and Logical Drive Problems on page 317 for more information. The Locator feature is triggered from WebPAM PROe or the CLU. It causes the LEDs to blink on and off for one minute. That action helps you find the physical component.
Drive Carrier LEDs

The VTrak spins up the disk drives sequentially to equalize power draw during start-up. After a few moments: The Power/Activity LED displays blue when a physical drive is present. The Drive Status LED displays green when the physical drive is configured as a member of a disk array or as a spare. When the physical drive is unconfigured, the LED is dark. See the diagram and table on the next page.
296
Figure 2. Drive carrier LEDs Drive Status
Power/Activity Drive Carrier LEDs State Dark Steady Blue Flashing Blue Steady green Blinking green Amber Red Power/Activity No drive in carrier Drive is present Activity on drive Drive Status Drive is unconfigured Drive is configured Locator feature Drive is rebuilding Drive error or failure
See Physical Drive Problems on page 316 for a discussion of rebuilding and failed physical drives for more information. The Locator feature is triggered from WebPAM PROe or the CLU. It causes the LEDs to blink on and off for one minute. That action helps you find the specific drive.
Back Panel LEDs

When the FRU Status LED on VTraks front panel shows amber or red, check the LEDs on the back of VTrak. These LEDs give the status of the field replaceable units: RAID controller Cache backup battery Power supply
Under normal conditions, the Controller Status LED (marked with icon) and Battery Status LED display green. The Dirty Cache LED (marked with icon) is dark.
297
Figure 3. FC RAID controller LEDs Dirty Cache LED Controller Status LED
Battery Status LED Under normal conditions, the power supply status LEDs display green. Figure 4. Power supply LED for E830f and E630f models Status LED
Figure 5. Power supply LED for E330f model Status LED
298
Enclosure Back LEDs State Dark Steady Green Blinking Green Steady Amber Flashing Amber Steady Red Flashing Red Status No power Normal Locator feature Surviving Failed Maintenance Mode Dirty Cache Normal Locator feature Battery No power or Failed Normal Power Supply No power Normal Locator feature Failed
Unsaved data Less than 72 in cache hours reserve Normal Failed
See Enclosure Problems on page 308 and Controller Problems on page 312 for more information. The Locator feature is triggered from WebPAM PROe or the CLU. It causes the LEDs to blink on and off for one minute. That action helps you find the physical component.
Checking Component Installation

To check a components installation, remove the component, then reinstall the component in its original location. In most cases, this action fixes a bad connection and allows VTrak to detect the component. If this action does not correct the problem, replace the unit. See page 249 for instructions. On VTraks with dual controllers, when one controllers Status LED is amber and the other controllers Status LED is flashing red, it means that the controller with the flashing red LED has entered maintenance mode. See Controller Problems on page 312. If the Controller Status LED continues to display amber after startup, contact PROMISE Technical Support. See Contacting Technical Support on page 359. The Dirty Cache LED flashes during input/output operation. If the LED shines amber and the power is off, there is unsaved data in the cache. Do NOT power down the VTrak while this LED is on.
299
CLU Reports a Problem

The CLU reports information passively, that is you must determine which functions to check based on the sound of the VTraks audible alarm and any amber or red LEDs. See VTrak is Beeping on page 293 and LEDs Display Amber or Red on page 295 for more information. Check the event logs first. Then check the reported component.
Viewing Runtime Events

To display Runtime Events: 1. From the Main Menu, highlight Event Viewer and press Enter. The log of Runtime Events appears. Events are added to the top of the list. Each item includes: 2. Sequence number Begins with 0 at system startup. Device Disk Array, Logical Drive, Physical Drive by its ID number. Severity (lowest to highest) Information, Warning, Minor, Major, Critical and Fatal Timestamp Date and time the event happened. Description A description of the event in plain language.
Viewing NVRAM Events

This screen displays a list of and information about 63 most important events over multiple subsystem startups. To display NVRAM events: 1. 2. From the Main Menu, highlight Event Viewer and press Enter. Highlight NVRAM Events and press Enter. The log of NVRAM Events appears. Events are added to the top of the list. Each item includes: 3. Sequence number Begins with 0 at system startup. Device Disk Array, Logical Drive, Physical Drive by its ID number. Severity See Table 1 on page 301 Timestamp Date and time the event happened. Description A description of the event in plain language.
300
Checking a Reported Component

In this example, let us check disk array status. 1. 2. 3. Open the CLU. Highlight Disk Array Management and press Enter. Observe the status of your disk arrays. DaId Alias OpStatus CfgCapacity FreeCapacity MaxContiguousCap ------------------------------------------------------------------------------------------0 DA0 OK 75.44GB 66.06GB 66.06GB 1 DA1 Degraded 189.06GB 179.68GB 179.68GB 2 DA2 OK 73.57GB 64.20GB 64.20GB At this point, you can highlight the Degraded array and press Enter to see more information. See below. Disk Array ID : OperationalStatus : FreeCapacity : SupportedRAIDLevels: Disk Array Alias MediaPatrol PDM 1 Degraded 179.68 GB 0 5 10 1E Physical Capacity : 189.06GB MaxContiguousCapacity : 11.18GB ConfigurableCapacity : 179.68GB
: DA1 : Enabled : Enabled
Transport Rebuild Predictive Data Migration Transition Dedicated Spare Drives in the Array Physical Drives in the Array Logical Drives in the Array
301
[Locate Disk Array] Save Settings [CTRL-A] Restore Settings [CTRL-R] Return to Previous Menu From this screen: Highlight Physical Drives in the Array and press Enter to identify the failed disk drive Highlight Rebuild and press Enter to rebuild the array after you replace the failed disk drive
For more information, see Enclosure Problems on page 308.
302
WebPAM PROe Reports a Problem

WebPAM PROe reports these conditions in the following places: Dashboard Tab System Status
Yellow ! and red X icons identify components that need attention
Event Information
303
Device Tab Front View, showing the drive carrier icons. Drive Rebuilding Drive Configured Drive Offline
Drive Unconfigured
Rear View, with Show Internal Components option. Battery Failure Overheating Power Supply Offline
Physical Drive View, physical drive shown dead or offline and marked with a red X icon. Physical Drive Offline
304
Storage Tab Disk Arrays Disk Array Rebuilding
Disk Array Offline
Logical Drives Logical Drive Offline
Logical Drive Rebuilding
305
AdminTool Tab Events
Header displays popup messages, per your configuration.
Also see these troubleshooting topics: Event Notification Response on page 327 Enclosure Problems on page 308 Frequently Asked Questions on page 357
306
USB Support Reports a Problem

This procedure requires a USB flash device: Formatted to FAT 32 At least 50 MB of free space Caution Verify that there is no firmware image file on the USB flash device. If a firmware image file is present, the RAID controller might attempt a firmware update. See page 246. To collect a service report using the USB Support feature: 1. Insert the USB flash device into one of the USB ports on one of the RAID controllers. The controller status LED blinks green in half-second intervals. USB ports Controller Status LED
2. 3. 4. 5.
Wait until the controller activity LED stops blinking green and displays steady green. Remove the USB flash device. Insert the USB flash device into a USB port on your PC. On the USB flash device, open the OPAX_xxxxxx folder to obtain the report and log.
307
Enclosure Problems
Enclosure Problems include: Diagnosing an Enclosure Problem (below) Overheating (page 310) Power Supplies (page 310) Batteries (page 311)
Diagnosing an Enclosure Problem

Check System Status on the Dashboard tab. If a yellow ! appears in the System Status box: 1. Click the name link of the component with the red X or red X
icon.
Click the link beside the red X icon
The Components List of the Device tab displays. 2. Mouse-over Enclosure with the red X icon and click the View button.
308
Note the red X icon
Click the View button
The components list expands and shows the power supply fans, which server as the Cooling Unit of the VTrak Ex30 enclosure.
Note the red X icons Note that the fans for power supply 2 (PSU 2) have failed. 3. 4. Click the Back View icon on the Device tab. Mouse-over the picture of the enclosure. A popup messages displays the status of each component.
When a power supply fan fails, you must replace the power supply. See Replacing a Power Supply on page 250 for more information. If the system reports a fan malfunction, contact Technical Support (see page 351) immediately to schedule replacement of the suspect power supply as soon as possible. Running the unit in this condition for more than three weeks may shorten subsystem life and void your warranty.
309
Overheating
Overheating is a potentially serious condition because the excessively high temperatures can lead to physical drive failure and controller malfunction. Overheating usually results from: Fan failure Inadequate air circulation around the enclosure
Fan Failure
In the Ex30 series VTrak subsystems, the power supply fans are the Cooling Units for the enclosure. When a power supply fan fails, you must replace the power supply. See Replacing a Power Supply on page 250 for more information.
Inadequate Air Circulation

Air circulation around the VTrak enclosure might be a more complex problem. Use the thermometer icons to help you locate the specific hot spot. Check for these conditions: Accumulated dust or objects blocking the fans Less than a minimum of 13 cm (5 inches) space between the back of the enclosure and the wall or other object Ambient temperature above 35C (95F) where the subsystem is operating
To cool down an enclosure: Correct any problems identified above. Power it down and let it sit for an hour or longer. See Shutting Down the Subsystem on page 67.
Power Supplies
VTrak subsystems are equipped with redundant power supplies. The advantage of dual power supplies is that, should one fail, the other continues to power the subsystem until the faulty one can be replaced. The subsystem is capable of operating on a single power supply. The power supplies are hot-swappable, meaning you can leave the subsystem running when you replace the bad one. Be careful, however, to remove the faulty power supply and not the good one, or the subsystem comes to an immediate stop and your data is unavailable until the subsystem is powered and booted again. See Replacing a Power Supply on page 250 for more information.
310
Batteries
The RAID controllers in the VTrak subsystem use a battery for backup power to protect data in the cache. Should a power failure occur, the battery enables the cache to hold data up to 72 hours. The battery recharges during normal subsystem operation. In most cases, installing a replacement battery corrects a marginal or failed condition. The battery is located inside the RAID controller housing. You can remove and replace the battery without removing the RAID controller. The battery is hot-swappable. No tools are required for the procedure. See Replacing a Cache Battery on page 265. Also see Reconditioning a Battery on page 128 or page 183.
311
Controller Problems
Controller problems include: Maintenance Mode (page 312) Finding and Correcting the Cause of the Problem (page 312) Taking a Controller out of Maintenance Mode (page 313) Unsaved Data in the Controller Cache (page 314)
Controller problems occur when one of the controllers goes into maintenance mode.
Maintenance Mode
For VTraks with two controllers, one of the controllers enters maintenance mode in the event of a problem with the controller. When a controller enters maintenance mode, it goes offline and it displays N/A (not accessible) under Readiness Status. You must take the following actions: Find and correct the cause of the problem (see below) Take the controller out of maintenance mode (see page 313)
Finding and Correcting the Cause of the Problem

Make the following external checks to your VTrak system. Be sure that: Both controllers are present, fully inserted into their slots, and locked into place. The controllers match, meaning both are Fibre Channel or both are SAS. All data cables to external JBOD enclosures in good condition and are securely attached. A disconnected data cable to an external JBOD enclosure causes the two controllers to see a different set of configured drives. This condition is the most common cause of a controller entering maintenance mode. If all external checks are OK, take the following actions: 1. 2. 3. 4. 5. Shut down the VTrak. Remove one of the controllers. Restart the VTrak. After the VTrak is fully booted, access the CLI, the CLU, or WebPAM PROe. Observe and record the following information about the first controller: Memory size Hardware version
312
Firmware version icon,
To view this information in WebPAM PROe, click the Controller Information tab. 6. 7. 8. 9. Shut down the VTrak. Remove the first controller and install the second controller. Repeat steps 3 through 6. Compare your records.
10. Correct any differences between the two controllers.
Taking a Controller out of Maintenance Mode

If you shut down the VTrak in the process of correcting the problem, the controller boots into normal mode when the VTrak restarts. No further action is required. If you corrected the problem without shutting down the VTrak, choose one of the following methods to take the controller out of maintenance mode: Reboot the VTrak Establish a serial connection, then use the CLI (see below) Establish a Telnet connection, then use the CLI (see page 314)
Serial Connection
To clear maintenance mode using a serial connection: 1. Change your terminal emulation program settings to match the following specifications: 2. 3. Bits per second: 115200 Data bits: 8 Parity: None Stop bits: 1 Flow control: none
Start your PCs terminal VT100 or ANSI emulation program. Press Enter once to launch the CLI. The login screen appears. The following steps show the default Administrator user name and password. Use your own user name and password if you have changed these.
4. 5.
At the Login prompt, type administrator and press Enter. At the Password prompt, type password and press Enter. The CLI screen appears.
313
The prompt should display MAINTENANCE MODE@cli>. If the prompt displays your login name, such as administrator@cli>, log into the other controller. 6. At the MAINTENANCE MODE@cli> prompt, type maintenance -a exit and press Enter. The controller reboots. The login screen again appears. 7. Close the Serial connection.
Telnet Connection
This procedure requires you to know the IP address of the controller. To clear maintenance mode using a Telnet connection: 1. Go to the command line prompt (Windows) or click the terminal icon (Linux), then run: telnet 192.168.1.56 2300 The IP address above is only an example. 2300 is the Telnet port for VTrak. The login screen appears. The following steps show the default Administrator user name and password. Use your own user name and password if you have changed these. 2. 3. At the Login prompt, type administrator and press Enter. At the Password prompt, type password and press Enter. The CLI screen appears. The prompt should display MAINTENANCE MODE@cli>. If the prompt displays your login name, such as administrator@cli>, log into the other controller. 4. At the MAINTENANCE MODE@cli> prompt, type maintenance -a exit and press Enter. The controller reboots. The Telnet session ends.
Unsaved Data in the Controller Cache

An LED (marked with the icon) is provided to inform you that there is data in the cache that has not been saved to non-volatile memory. Such data is sometimes called dirty, not to suggest it is corrupted in some way but because it has not been saved to a disk drive.
314
Figure 6. FC RAID controller LEDs Dirty Cache LED
Caution If there is unsaved data in the controllers cache, the Dirty Cache LED shines amber. During this time, do NOT power down the VTrak. Wait until the LED goes dark.
315
Physical Drive Problems

Physical drives are the foundation of data storage. A physical drive problem can affect your entire RAID system. When a yellow ! icon or a red X check the drive's operational status: 1. 2. 3. Click the Device tab. Click the Physical Drive icon. Mouse-over the physical drive you want and click the View button. Look under Operational Status for the condition of the physical drive. Offline Check the drive for: PFA Condition Caused by a bad block or sector. See Note 1 below. Stale Condition Caused by obsolete array information on the physical drive. See Note 2 below. Two controllers in your RAID subsystem and a SATA drive without a SAS-to-SATA adapter. See Note 3 below. A missing or defective SAS cable between the RAID subsystem and a JBOD expansion unit. icon appears beside a physical drive,
Not Usable This condition occurs when you have:
Drive Failed or Dead The physical drive cannot be repaired. You must replace the failed drive. See Note 4 below.
Note 1: Clear the error condition. Then the physical drive is available. See Clearing a Stale or a PFA Condition on page 120. Note 2: Identify the disk array to which the physical drive belongs. Then delete the disk array. If the error condition remains on the physical drive, clear the error condition. Note 3: Obtain SAS-to-SATA adapters though PROMISE Technology, at http://www.promise.com. See Installing Physical Drives on page 19 for installation instructions. Note 4: You can set the number of bad blocks tolerated before the controller marks a physical drive as Dead. See Making PDM Settings on page 97 or Making Background Activity Settings on page 208. See also: Media Patrol on page 259 and Disk Array Degraded. Disk Array Degraded/Logical Drive Critical on page 317.
316
Disk Array and Logical Drive Problems

Disk array and logical drive problems include: Disk Array Degraded/Logical Drive Critical (page 317) Disk Array Offline/Logical Drive Offline (page 318) Repairing an Offline Disk Array or Logical Drive (page 319) Rebuilding a Disk Array (page 319) Incomplete Array (page 320)
Disk array problems typically result from a physical drive failure. The most common problem is a degraded disk array. The RAID controller can rebuild a degraded disk array. See Rebuilding a Disk Array on page 319.
Disk Array Degraded/Logical Drive Critical

Disk arrays are made up of physical drives. Logical drives are created on the disk array. When one of the physical drives in a disk array fails: The operational status of the disk array becomes Degraded. The operational status of the logical drives becomes Critical. The operational status of the physical drive becomes Dead or Offline.
WebPAM PROe reports these conditions in the following places: Dashboard Tab A yellow ! icon beside the disk arrays, logical drives, and physical drives under System Status. Major event for the logical drive under Event Information Warning event for the physical drive under Event Information. Device Tab Front View, physical drive shown dead, offline and marked with a red X icon; or missing. Physical Drive View, physical drive shown dead or offline and marked with a red X icon; or missing.
Storage Tab Disk Array and Logical Drive are marked with a yellow ! icon.
317
RAID 6 and RAID 60 logical drives show Degraded status and a green check icon. icon.
RAID 0 logical drives show Offline status and a red X
If there is no spare drive or unconfigured drive in the RAID system, you must provide the replacement drive. See Installing Your Drives on page 20. AdminTool Tab Depending on your settings and availability of a replacement drive, your system automatically rebuilds the degraded disk array. See Rebuilding a Disk Array on page 319. The system sends an Email message about the incident to subscribing users, depending on user settings. See Setting User Event Subscriptions on page 84.
Disk Array Offline/Logical Drive Offline

Disk arrays are made up of physical drives. Logical drives are created on the disk array. When a disk array and its logical drives go Offline, the data stored in the logical drives is no longer accessible. Logical drives based on fault-tolerant disk arrays, RAID 1, 1E, 5, 6, 10, 50, and 60, go Offline when two physical drives are removed or fail. Logical drives based on non-fault tolerant disk arrays, RAID 0, go Offline when one physical drive is removed or fails. WebPAM PROe reports these conditions in the following places: Dashboard Tab A red X icon appears beside the disk arrays, logical drives, and physical drives under System Status. Major event for the logical drive under Event Information Warning event for the physical drive under Event Information. Device Tab Front View, physical drive shown dead, offline, or missing. Physical Drive View, physical drive shown dead, offline, or missing. Storage Tab Disk Array and Logical Drive are marked with a red X
318
icon.
AdminTool Tab Under Background Activities, no Rebuild takes place. See Repairing, below. The system sends an Email message about the incident to subscribing users, depending on user settings. See Setting User Event Subscriptions on page 84.
Repairing an Offline Disk Array or Logical Drive

RAID 1, 1E, 5, 6, 10, 50, and 60 Logical Drives
If a fault-tolerant logical drive, RAID 1, 1E, 5, 6, 10, 50, and 60, goes offline, it may be possible to recover your data. Warning Take no further corrective action until you have consulted with Technical Support!
RAID 0 Logical Drives

If a logical drive based on a non-fault-tolerant disk array, RAID 0, goes offline, all of the data on the logical drive is lost. To recreate your logical drive: 1. 2. 3. 4. Identify the failed physical drive. See Locating a Physical Drive on page 119. Replace the failed drive. See Installing Your Drives on page 20. If the disk array had more than one physical drive, delete the disk array and re-create it. See Deleting a Disk Array on page 127 and Creating a Disk Array Manually on page 122. 5. Restore the data from your backup source.

When you rebuild a disk array, you are actually rebuilding the data on one physical drive. When a physical drive in a disk array fails and a spare drive of adequate capacity is available, the disk array begins to rebuild automatically using the spare drive. If there is no spare drive of adequate capacity, but the Auto Rebuild function is ENABLED, the disk array begins to rebuild automatically as soon as you
319
remove the failed physical drive and install an unconfigured physical drive in the same slot. See Making Rebuild Settings on page 96. If there is no spare drive of adequate capacity and the Auto Rebuild function is DISABLED, you must replace the failed drive with an unconfigured physical drive, then perform a Manual Rebuild. See Rebuilding a Disk Array on page 130. Important If your replacement disk drive was formerly part of a different disk array or logical drive, you must clear the configuration data on the replacement drive before you use it. See Clearing a Stale or a PFA Condition on page 120.
Incomplete Array
A more serious, but far less common problem is an Incomplete Array. An incomplete array results from a physical drive that fails or becomes missing during: RAID level migration Disk array transport
Migration
Normally, if a physical drive or the controller fails during migration, the disk array goes degraded, and you can rebuild it.
Transport
Transport is the action of moving the physical drives of a disk array: To different slots in the same enclosure From one enclosure to another
If a physical drive fails during a transport, or you do not move all of the physical drives to their new locations, WebPAM PROe displays an incomplete array. When WebPAM PROe discovers an incomplete array, it displays a dialog box asking you to: Click the OK button to accept the incomplete array. Click the Cancel button to reject the incomplete array.
Before you accept the incomplete array, be sure all of the physical drives are present and that their drive carriers are properly installed into the enclosure. See Installing Your Drives on page 20.
320
If you choose to accept the incomplete array: 1. 2. Click OK in the incomplete array dialog box. Check the operational status of the logical drives in the array. 3. If the logical drives are Critical, proceed with a rebuild. If the logical drives are Offline, contact Technical Support. See page 351.
Restore your data from a backup source.
If you choose NOT to accept the incomplete array: 1. 2. Click Cancel in the incomplete array dialog box. Do one of the following: Delete the array. This action deletes all logical drives on the array. Replace the missing physical drive.
321
Connection Problems
Connection problems include: Serial Connections (page 322) Network Connections (page 323) Fibre Channel Connections (page 323) SAS Connections (page 324) Browser Does Not Connect to WebPAM PROe (page 325)
Connection problems cause a majority of failures in almost any electrical system. While the installation of the cables and components was correct, they don't function properly, or at all, because: A connector is dirty or corroded A connector is loose or damaged A cable looks OK outside but has an open circuit inside The wrong cable was used
VTraks ship with a full set of new cables, as required for each specific model. Be sure to use these components because: 1.) They are the proper ones for your RAID subsystem, 2.) They are in brand-new condition, and 3.) You paid for them with the purchase of your subsystem.
Serial Connections
VTrak uses a serial connection for the command line interface (CLI) and the command line utility (CLU). After you set the IP address, you can access the CLI and CLU through a network connection, also. Normally, users prefer WebPAM PROe because of its graphic user interface. But the CLI and CLU can do the same jobs. And they work when your network connection is down. For VTrak, you must use the CLI or CLU to set the Management Port IP address in order for WebPAM PROe to connect with it. See Setting up the Serial Connection on page 39. This issue is discussed further under Network Connections, below. See Setting Up Serial Cable Connections on page 36 for more information on making the connection. The CLI and CLU control and manage but they do not move data. They communicates through a null-modem cable, supplied with the VTrak. A straightthrough serial cable does not work for this purpose. You may choose not use the CLI or CLU often and want to disconnect and store the cable. Consider leaving it connected, so you know where it is the next time you need it.
322
Network Connections
Each controller has an Ethernet (RJ45) Management Port connector on the back of the enclosure. This is a Gigabit Ethernet connector designed to connect to your network. The VTrak becomes a node on your network like any other PC, server or other component with an IP address. VTrak ships from the factory IP addresses of 10.0.0.1, 10.0.0.2, and 10.0.0.3. You must change these addresses to ones that work on your network. You make the initial IP address setting using the CLI or CLU. See Setting up the Serial Connection on page 39. Figure 3. Management port connection on the RAID controller
Mgmt
Activity LED
Connectivity LED
Management Port LEDs State Dark Steady green Flashing green Amber Activity No activity Activity Connectivity 10BaseT 100BaseT 1000BaseT
Note that VTraks virtual and maintenance ports can accept IP address assignments from a DHCP server. Use VTraks Command Line Utility (CLU) to enable this feature. If you manually assigned an IP address to the VTrak but there is a DHCP server on your network, there is a chance that the server might assign the VTraks IP address to another node. You might see a warning to this effect on your PCs monitor. If this happens, WebPAM PROe may not be able to connect. See your network administrator to work out a suitable arrangement.
Fibre Channel Connections

When there is a connection failure, use WebPAM PROe to verify that VTrak sees the initiators. See Viewing Fibre Channel Initiators on page 88 or page 213.
323
If VTrak sees some initiators but not the one you want, the problem is most likely elsewhere in the loop or fabric. If VTrak does not see any initiators: Check all of the Fibre Channel connections Verify that all nodes are properly connected and powered Verify that the fabric router or switch is properly connected powered
For more information, see Managing Fibre Channel Connections on page 84 or page 210.
SAS Connections
Faulty SAS connections are suspected when the link port counter reports a large number of bad link errors. See Viewing SAS Port Statistics on page 91 or page 215. Link errors can be caused by: Debris blocking the SAS cable connector A faulty SAS cable A faulty controller or I/O module SAS connector
Blocked Cable Connectors

To check for debris blocking the SAS cable connector: 1. 2. 3. 4. Power down the RAID head and JBOD subsystems. Remove the SAS cable and check all SAS connectors for debris. Clean the connectors as required and reconnect the SAS cable. Power up the subsystems and monitor the link port counter for changes in the rate of link error accumulation.
Faulty Cable
To check for a faulty SAS cable: 1. 2. 3. Power down the RAID head and JBOD subsystems. Replace the SAS cable with a new one. Power up the subsystems and monitor the link port counter for changes in the rate of link error accumulation.
Faulty Controller or I/O Module Connector

To check for a bad controller or I/O module SAS connector: 1. With the subsystems online and I/Os running, access the CLI via serial or Telnet. See Initial Connection on page 166. 2. At the administrator@cli> prompt, type the following command and press Enter.
324
sasdiag -a errorlog -l expander -e 1 -i 1 3. At the administrator@cli> prompt, type the following command and press Enter. sasdiag -a errorlog -l c2cport By interpreting the two error logs, you can verify which controller or I/O module SAS port is accumulating link errors.
Browser Does Not Connect to WebPAM PROe

If you successfully setup and connected to WebPAM PROe, then suddenly you can no longer connect, it might be the result of the following three conditions: DHCP is enabled on your VTraks virtual management port The DHCP server does not have a dedicated IP address for the VTrak The VTrak restarted and your DHCP server assigned a new IP address
You must obtain the new IP Address for the virtual management port in order to direct your browser to the VTrak and start WebPAM PROe. To access the new IP address: 1. 2. 3. 4. 5. Start your PCs terminal VT100 or ANSI emulation program. Press Enter once to launch the CLI. At the Login prompt, type administrator and press Enter. At the Password prompt, type password and press Enter. Type net and press Enter. administrator@cli> net =========================================== CId Port Type IP Mask Gateway Link =========================================== Virtual Mgmt 192.168.10.85 255.255.255.0 192.168.10.1 Up The new virtual management port IP address and other network settings display. 6. Enter the new IP address into your browser to log into WebPAM PROe.
For more information, see Setting up the Serial Connection on page 39 and Logging into WebPAM PROe on page 46.
325
Power Cycling the Subsystem

To power cycle a RAID subsystem means to: Shut down Turn off the power Turn on the power Restart
Power cycling is sometimes required as a remedial action but only when prompted by a message from software or when directed by Technical Support. To power cycle the RAID subsystem: 1. Shut down the subsystem. See Shutting Down the Subsystem on page 67 or page 233. When the controller shuts down, your network connection is lost. 2. 3. 4. 5. 6. 7. Manually turn OFF the switches on both power supplies of the RAID subsystem and all attached JBOD expansion units. Wait at least 10 seconds. Manually turn ON the switches on both power supplies of the JBOD units. Manually turn ON the switches on both power supplies of the RAID subsystem. Wait no less than two minutes. Do one of the following actions: Open your browser and log into WebPAM PROe. Re-establish your Telnet or SSH connection to the subsystem and open the CLU.
If you cannot log in immediately, wait 30 seconds and try again. Important If your RAID subsystem manages JBOD expansion units, always power on the JBOD expansion units first. Then power on the RAID subsystem.
326
Event Notification Response

When you choose Event Notification, WebPAM PROe sends popup and/or email messages regarding its status. The messages you see depend on your notification selection and what is currently happening in the VTrak. See Settingup Event Notification on page 77. The table below cites: Reported Events Events that require you to take action Corrective Actions The action you should take in response to the event
A list of event categories is shown below. Battery (page 328) BBU (page 328) Blade Server (page 328) Cache (page 328) Controller (page 329) CRC (page 331) Disk Array (page 331) Drive Interface (page 331) Enclosure (page 332) Event Log (page 332) Fibre Channel (page 332) Firmware Update (page 333) Host Interface (page 333) Initiator (page 334) JBOD (page 335) Logical Drive (page 335) Media Patrol (page 336) Online Capacity Expansion (page 336) Parity (page 337) PDM (page 337) Physical Disk (Physical Drive) (page 337) PSU (Power Supply Units) (page 339) PSU Fans (page 340) RAID Level Migration (page 340) Rebuild (page 341) Redundancy Check (page 341) Resource (page 342) SCSI (page 342) SEP (page 342) Spare Check (page 342) Spare Drives (page 342) SMART (page 342) Stripe Level Migration (page 343) Synchronization (page 343) Subsystem (VTrak) (page 343) Transition (page 344) Unknown (page 344) Zoning (page 344)
327
Reported Event Battery Battery is inserted Battery charging has failed Battery reconditioning has started Battery reconditioning has been terminated The write policy of writeback logical drive switched from writeback to writethru The write policy of writeback logical drive switched from writethru to writeback
Corrective Action
No action is required. Replace the battery. No action is required. Replace the battery. Check the event log to see whether battery is re-conditioning. No action is required.
Battery is charging in high temperature Monitor the condition. Contact Tech Support if the problem persists. Battery cannot function with the enclosure or with the attached battery board Logical drive writeback cache maybe enabled without battery support Battery is fully charged Battery is not present Battery is not accessible BBU BBU flushing has started BBU flushing has ended BBU flushing has failed Blade Server Blade Server Inserted Blade Server Removed Cache Not available Contact Tech Support. No action is required. No action is required. Contact Tech Support if the condition persists. Install a battery or verify that the battery is properly connected. Connect the battery properly or replace the battery. Wrong battery installed. Contact Tech Support for assistance.
No action required.
328
Reported Event Controller The controller parameter(s) are changed by user The controller is reset by Watch Dog timer The controller has new crash information The controllers heart beat has started The controllers heart beat has stopped The partner controllers heart beat has started The partner controllers heart beat has stopped The partner controllers heart beat has skipped The controllers main scheduler has frozen Controller has entered maintenance mode since configured physical disk seen by partner controller is not seen here
Corrective Action
No action is required. Result of a firmware update. If the condition persists, replace the controller. Contact Tech Support.
No action is required.
Contact Tech Support if the condition persists. Verify that all SATA drives have an SAS-to-SATA adapter installed.
Controller has entered maintenance Check and correct SAS cabling and mode due to mismatch of physical disks connections as needed. types Controller has entered maintenance Update to the latest firmware. If the mode due to mismatch of physical disk condition persists, replace the WWN controller. Controller has entered maintenance mode due to mismatch of SATA Disks Controller has entered maintenance mode due to mismatch of Disk IDs Controller has entered maintenance mode since no physical disks are seen as seen by Partner controller Check and correct data cabling and connections as needed.
329
Reported Event Controller is started Controller is set to Active Mode Controller is set to Standby Mode Controller Failed Over as partner is removed Controller Failed Over as heart beat stopped
Corrective Action
Verify that the partner controller is properly installed and all cables are connected.
Controller Firmware mismatch with that Auto Firmware synchronization of the partner controller upgrades or downgrades the firmware. Controller set to Maintenance Mode because of hardware mismatch with partner (controller) Controller set to Maintenance Mode because of firmware mismatch with partner controller Controller set to Maintenance Mode because Firmware is flashing in the partner controller Controller set to Maintenance Mode because of flash image version mismatch with partner (controller) Compare controller types and amount of memory installed. Correct or update as needed. Update this controller to the same firmware version as the partner controller. Exit out of Maintenance mode after firmware flashing is complete. Update this controller to the same flash image version as the partner controller.
Controller has been set to Maintenance Replace this controller with the same mode because there is a mismatch in Model and Hardware version as the the Controller Model or Hardware partner controller. version with that of the partner controller Controller has been set to Maintenance Replace this controllers memory with mode because there is a mismatch in the same memory size as the partner the memory size with that of the partner controller controller Partner Controller has entered maintenance mode to protect user data since one of the configured physical drives was disconnected in the partner controller Check and correct cable connections to external JBOD enclosures. Rebuild any critical logical drives. Back up array data. Replace the physical drive. Bring controller out of maintenance mode.
330
Reported Event Controller was placed on reset during Fail Over processing Partner Controller was placed on reset during Fail Over processing Controller was reset as it was not able to join the running partner controller The controller has reset because it encountered a firmware problem Controller temperature is above the warning threshold The controller temperature is above controller critical threshold Controller temperature is within the normal range CRC CRC error is detected while receiving CMD information unit CRC error is detected during Data Out phase Disk Array New disk array has been created Disk array has been deleted Disk array has been added Disk array has been removed Disk array settings have been changed Disk array is transport ready
Corrective Action
Verify that the controller is running. If the condition persists, replace the controller. If resets happen frequently, update to new firmware or replace the controller. Check airflow around the VTrak. Check blowers and fans. No action is required.
If this message appears repeatedly, contact Tech Support.
Remove physical drives in disk array and insert them into a different subsystem. To cancel Transport Ready Status, remove and reinsert the drives in their original slots. No action is required.
Drive Interface Drive-interface controller is found Drive-interface controller is NOT found Restart the VTrak. If this message appears repeatedly, contact Tech Support.
331
Reported Event
Corrective Action
Drive-interface diagnostics has passed No action is required. Drive-interface diagnostics has failed Restart the VTrak. If this message appears repeatedly, contact Tech Support.
Drive-interface controller has generated a general parity error If this message appears repeatedly, Drive-interface controller has generated contact Tech Support. a data parity error Enclosure Enclosure temperature is above the threshold Enclosure temperature is above the warning threshold Enclosure temperature is above the critical threshold Enclosure temperature is within the normal range Shut down PSUs due to enclosure or controller temperature over threshold Event Log Event logging is enabled Event logging is disabled Event log buffer is cleared in RAM Event log buffer is cleared in NVRAM Event log buffer is cleared in MDD Fibre Channel Fibre Channel controller has detected bus reset If this message appears repeatedly, contact Tech Support. No action is required. Check blowers and fans.
Check airflow around the VTrak. Check blowers and fans. No action is required. Shut down the VTrak and see Enclosure Problems on page 308.
Fibre Channel controller has received a No action is required. LUN reset command. Fibre Channel controller has encountered a fatal error Restart the VTrak. If this message appears repeatedly, contact Tech Support.
332
Reported Event Fibre Channel link is up Fibre Channel link is down Fibre Channel controller settings have changed Firmware Update Firmware update is started Firmware update is complete Firmware update is fail Back-end expander firmware upgrade is started Back-end expander firmware upgrade is completed Back-end expander firmware upgrade failed Front-end expander firmware upgrade is started Front-end expander firmware upgrade is completed Front-end expander firmware upgrade failed Host Interface Host interface controller has detected bus reset Host interface controller has encountered an unrecoverable error Host interface controller has received an abort task command. Host interface controller has received an abort task set command.
Corrective Action
No action is required. Try the update again. If this message repeats, contact Tech Support.
Try the update again. If this message repeats, contact Tech Support.
Try the update again. If this message repeats, contact Tech Support. If this message appears repeatedly, contact Tech Support. Restart the VTrak. If this message appears repeatedly, contact Tech Support.
Host interface controller has received a If this message appears repeatedly, clear ACA command. contact Tech Support.
333
Reported Event Host interface controller has received a clear task set command. Host interface controller has received a LUN reset command. Host interface controller is informed that the initiator has detected an error Host interface controller has received illegal secondary identification
Corrective Action
If this message appears repeatedly, Host interface controller has received a contact Tech Support. message parity error Host interface controller has received a bus reboot Host interface link is up Host interface link is down Host interface controller has encountered an unknown error Host interface controller has encountered a system error Host interface controller has encountered a fatal error Host interface controller settings have changed Host interface controller has received a WARM reset command Host interface controller has received a COLD reset command Host Interface controller, MU handshake failed Host Interface controller, HMU has stopped Host Interface controller, FMU has unloaded Initiator Initiator sent message for detecting an error
334
No action is required. Check connections. If this message appears repeatedly, contact Tech Support. Restart the VTrak. If this message appears repeatedly, contact Tech Support. No action is required.
Reported Event JBOD JBOD system connected JBOD system either is removed or malfunctioned Logical Drive Logical drive initialization has started Logical drive Initialization is in progress Logical drive initialization has completed Logical drive initialization has paused Logical drive initialization has stopped Logical drive initialization marks the logical drive offline
Corrective Action
No action is required. Check Expander firmware and SAS connections.
Resume the initialization when ready. If this action was not intentional, check the logical drives status. Replace the failed physical drive. Delete and recreate the logical drive.
Logical drive initialization has resumed No action is required.
Logical drive initialization is aborted due Reduce system load on the VTrak. to an internal error. Logical drive initialization is queued Quick logical drive initialization has started Quick logical drive initialization has completed Quick logical drive initialization has paused Quick logical drive initialization has resumed Quick logical drive initialization has stopped Quick logical drive initialization marks the logical drive offline Quick logical drive Initialization is aborted due to an internal error Resume the initialization when ready. No action is required. If this action was not intentional, check the logical drives status. Replace the failed physical drive. Delete and recreate the logical drive. Reduce system load on the VTrak. No action is required.
335
Reported Event Quick logical drive initialization is queued A new logical drive has been created Logical drive has been deleted Logical drive has been placed online Logical drive has been placed online. Possible data loss Logical drive has been set to critical. Logical drive has been set to degrade Rebuild marks the logical drive synchronized upon rebuild completion Logical drive settings has been changed through a user command One of the error tables of a logical drive has been cleared by the user Logical drive axle has been placed online Media Patrol Media patrol is started Media patrol is in progress Media patrol is completed Media patrol is paused Media patrol is resumed Media patrol is stopped Media patrol is aborted due to an internal error. Media patrol is queued Media patrol is stopped internally Online Capacity Expansion Online capacity expansion has started Online capacity expansion has completed
Corrective Action
Check the state of the physical drives, replace any bad drives. Rebuild logical drive.
No action is required. Resume Media Patrol when ready. No action is required. If this action was not intentional, check the logical drives status. Reduce system load on the VTrak.
Online capacity expansion has paused Resume OCE when ready.

336
Reported Event Online capacity expansion has resumed
Corrective Action No action is required.
Online capacity expansion has stopped If this action was not intentional, check the logical drives status. Online capacity expansion has encountered a physical disk error Online capacity expansion is aborted due to an internal error. Online capacity expansion is queued Parity Parity error is detected during Data Out If this message appears repeatedly, phase contact Tech Support. PDM PDM is started PDM is in progress PDM is completed PDM is paused PDM is resumed PDM is stopped PDM is switched to rebuild. PDM is stopped internally Physical Disk (Physical Drive) Physical disk is marked online Physical disk is marked offline Physical disk is marked as DEAD. Physical disk has been reset Replace the physical drive. No action is required. Resume PDM when ready. No action is required. If this action was not intentional, check the disk arrays status. Replace the dead physical drive or reinstall the missing drive. The destination drive was removed or used for a rebuild. No action is required. Check the physical drive check table after OCE is finished. Reduce system load on the VTrak. No action is required.
337
Reported Event Physical disk assigned as global spare Global Spare has been deleted Physical Disk is no longer assigned as a global spare Physical disk assigned as dedicated spare Dedicated Spare has been deleted Physical Disk is no longer assigned as a dedicated spare Physical disk has been inserted Physical disk has been removed Command on physical disk has been re-tried Physical disk ECC error is detected Physical disk CRC error is detected Bad sector is found on physical disk Error is detected in remap sectors Command times out on physical drive Physical disk negotiation speed is decreased.
Corrective Action
Insert the physical drive back into the system. If this message appears repeatedly, replace the physical drive Replace the physical drive.
If this message appears repeatedly, replace the physical drive.
Previously configured disk is no longer Insert the physical drive back into the found system. A physical disk has encountered an unknown (non-ECC) media error. A physical disk has encountered PFA condition A configured dead physical drive has been inserted If this message appears repeatedly, replace the physical drive. Clear the PFA condition. If this message appears repeatedly, replace the physical drive. Replace the physical drive.
338
Reported Event A physical drive page 0 settings have been changed A physical drive page 1 settings have been changed (SATA drives) A physical drive page 3 settings have been changed (SAS drives) Physical disk is marked as DEAD due to removal Physical disk is marked as DEAD due to failure of reassign sectors command Physical disk is marked as DEAD due to PFA condition Physical disk is marked as DEAD due to forced offline state
Corrective Action
Replace the physical drive.
Physical disk seen by partner controller Check and correct SAS connections. not seen here Verify that SAS-to-SATA adapters are installed on all SATA drives. Single ported physical disk seen by Partner controller not seen here Physical disk reported not ready PSU (Power Supply Units) PSU is not inserted PSU is off PSU is on PSU is installed and turned on PSU is functional and turned on PSU is installed and turned off PSU is functional and turned off PSU is malfunctioning and turned on PSU is malfunctioning and turned off PSU has been removed PSU 12V/5V/3.3V power is out of the threshold range Replace the power supply unit. Turn on the power supply or plug in the power cable. No action is required. Reinstall the power supply unit. Turn on the power supply or plug in the power cable. Install an SAS-to-SATA adapter on the SATA drive. Replace the physical drive.
339
Reported Event PSU 12V/5V/3.3V power is within the normal range PSU is critical. This may cause instability of the system PSU Fans PSU fan or blower has turned on PSU fan or blower has turned off PSU fan or blower speed is increased PSU fan or blower speed is decreased PSU fan or blower is malfunctioning PSU fan or blower is inserted PSU fan or blower is functioning normally PSU fan or blower is NOT installed PSU fan status is unknown.
Corrective Action No action is required. Check the power to the PSU. Verify that the correct PSU is installed.
Replace the power supply. No action is required. Check fans or blowers. Check for proper installation and turn on the power supply. If the condition persists, replace the power supply.
RAID Level Migration RAID level migration is started RAID migration is in progress RAID level migration is completed RAID level migration is paused RAID level migration is resumed RAID level migration is stopped Resume migration when ready. No action is required. If this action was not intentional, check the logical drives status. No action is required.
RAID level migration has encountered a Check the disk drive check table after physical disk error migration and replace disk drive as needed. RAID level migration is aborted due to an internal error. RAID level migration is queued Migration has detected stale NV Watermark Reduce system load on the VTrak. No action is required. Wait to see if the watermark clears.
340
Reported Event Migration has cleared stale NV Watermark Array was made incomplete due to missing NV Watermark User has accepted Incomplete Array. (Caused by a missing NV Watermark) Rebuild Rebuild is started Rebuild is in progress Rebuild is completed Rebuild is paused Rebuild is resumed Rebuild is stopped Rebuild stopped internally Rebuild is aborted Rebuild is queued Auto rebuild cannot start Redundancy Check Redundancy Check is started Redundancy Check is completed Redundancy Check is paused Redundancy Check is resumed Redundancy Check is stopped Redundancy Check is aborted due to internal error Redundancy Check encountered inconsistent block(s) Redundancy Check task is queued Redundancy check is in progress
Corrective Action No action is required. If the array is online, try migration again. If the array is offline, delete and recreate the array. Rebuild the disk array.
No action is required. Resume rebuild when ready. No action is required. If this action was not intentional, check the logical drives status. Contact Tech Support. Reduce system load on the VTrak. No action is required. Install a target physical drive of adequate capacity.
No action is required. Resume Redundancy Check when ready. No action is required. Reduce system load on the VTrak. Check the disk drive check table after RC and replace disk drive as needed. No action is required.
341
Reported Event Redundancy Check task is stopped internally Redundancy check is started on unsynchronized logical drive Resource Resource is NOT available SCSI SCSI host interface controller settings have changed SEP SEP is found SEP is NOT found SEP I2C device access failure
Corrective Action Restore the disk array to functional status. No action is required.
Reduce system load on the VTrak. No action is required.
No action is required. Insert or replace SEP hardware.
If this message appears repeatedly, SEP I2C device access recovered from contact Tech Support. failure Spare Check Spare check started on the given spare drive Spare check completed successfully on the given spare drive Spare Drives Physical disk assigned as global spare Physical disk is no longer assigned as global spare Global Spare has been deleted Physical disk assigned as dedicated spare Physical disk is no longer assigned as dedicated spare Dedicated Spare has been deleted SMART SMART error is received If this message appears repeatedly, replace the physical drive. No action is required.
342
Reported Event Stripe Level Migration Stripe Level migration is started Stripe Level migration is completed Stripe Level migration is paused Stripe Level migration is resumed Stripe Level migration is stopped
Corrective Action
No action is required. Resume SLM when ready. No action is required. If this action was not intentional, check the logical drives status.
Stripe Level migration has encountered Check the physical drive check table a physical disk error after OCE is finished. Stripe Level migration is aborted due to Reduce system load on the VTrak. an internal error. Stripe Level migration is queued Synchronization Synchronization is started Synchronization is completed Synchronization is paused Synchronization is resumed Synchronization is stopped Synchronization is aborted due to an internal error. Synchronization is queued Synchronization is stopped internally Subsystem (VTrak) The Subsystem is started The Subsystem is stopped Subsystem parameter(s) are changed by user System is set to Redundant mode System is set to Critical mode Check controller operation. System is set to Non-Redundant mode If your system has two controllers, check controller operation. No action is required. No action is required. No action is required. Resume synchronization when ready. No action is required. Reduce system load on the VTrak. No action is required.
343
Reported Event Transition Transition is started Transition is completed Transition is paused Transition is resumed Transition is stopped Transition was switched to rebuild Unknown Unknown priority reason is detected Zoning Zoning permission settings with the expander has been reset to defaults Zoning expander has been rebooted. Zoning permission settings with the expander different than expected
Corrective Action
No action is required. Resume transition when ready. No action is required. If this action was not intentional, check the disk arrays status. Replace the dead physical drive or reinstall the missing drive. If this message appears repeatedly, contact Tech Support.
No action is required. Settings have been updated correctly. No action is required.
344
Chapter 9: Support
This chapter contains the following topics: Frequently Asked Questions (below) Contacting Technical Support (page 351) Limited Warranty (page 354) Returning the Product For Repair (page 356)
Frequently Asked Questions

Physical Drives
What kind of disk drives can I use with VTrak? VTrak E-Class supports: 3.5-inch and 2.5-inch form factor Hard disk drives (HDDs) and Solid State drives (SSDs) SAS, 6 Gb/s and 3 Gb/s SATA, 6 Gb/s, 3 Gb/s, and 1.5 Gb/s Supports any mix of SAS and SATA drives simultaneously in the same enclosure
For a list of compatible drives, go to PROMISE support: http://www.promise.com/support/. VTrak E-Class does not support Parallel ATA (PATA) disk drives. Why are all the disk drives in my JBOD marked Dead? This condition happens when the JBOD expansion subsystem is disconnected from the RAID subsystem, powered off while the RAID subsystem is running, or powered on after the RAID subsystem was powered on. Use the force online function to restore the disk drives. See Clearing a Stale or a PFA Condition on page 120 or page 178. See Making Webserver Settings on Making Webserver Settings on page 103 or page 222. With some RAID subsystems, I used a servers IP address to log in. Why is VTrak E-Class different? VTrak E-Class has the server software embedded. With the E-Class, you point your browser directly to the VTrak subsystem. WebPAM PROe is preinstalled on the VTrak and launches automatically.
345
I can access the VTrak over my companys intranet. But I cant access it from an outside Internet connection. How do I make the Internet connection work? This condition is not related to VTrak, but is due to your firewall and network connection protocol. Contact your MIS Administrator. Why can a RAID 1 logical drive on VTrak consist of only two disk drives? RAID 1 logical drives work in mirrored physical drive pairs. You could create up to eight RAID 1 logical drives. Or you can create a single RAID 1E or RAID 10 logical drive with data mirroring and up to 16 physical drives. See Installing Disk Drives on page 15 and RAID Levels on page 261 for more information on the number of physical drives you can use for each RAID level. Are logical drives on VTrak limited to 2 TB? No. But verify that your operating system supports logical drives over 2 TB. Also, for the operating system to recognize the full capacity of logical drives over 2 TB, you must specify a sector size of 1 KB or larger when you create the logical drive. See Sector Size on page 281 for more information. How can I be sure everything is working OK on the VTrak? Locally: The VTrak enclosure has LEDs on the front to monitor the status of power, field replaceable units (FRUs) and logical drives. When these are green, VTrak is functioning normally. See Front Panel LEDs on page 295. Remotely: Check the Dashboard tab in WebPAM PROe. See WebPAM PROe Reports a Problem on page 303. If there are no yellow ! functioning normally. or red X warning icons displayed, VTrak is
Can VTrak run using just one power supply? Yes, it is possible to run VTrak on a single power supply. There are redundant power supplies so that VTrak can continue running if one of them fails. But deliberately leaving one power supply off negates this advantage. In addition, leaving one power supply off reduces air flow through the VTrak enclosure and can contribute to overheating. Always switch on both power supplies. Also see
346
Chapter 9: Support
What happens if a fan fails? If the system reports a fan malfunction, contact Technical Support (see page 351) immediately to schedule replacement of the suspect power supply as soon as possible. Running the unit in this condition for more than three weeks may shorten subsystem life and void your warranty. What happens if a logical drive goes critical? On the front of VTrak, the logical drive LED turns amber and the buzzer sounds (if enabled). See VTrak is Beeping on page 293 and LEDs Display Amber or Red on page 295. VTraks Netsend service does not report all events to Windows PCs. This condition results from a shortcoming in Windows Messenger that causes miscommunication with Netsend. PROMISE is developing a workaround at the time of this writing. Note that all events are correctly reported in the Event Viewer.
Startup
How can I tell when the VTrak has fully booted? When the VTrak is fully booted up, the Power and FRU LEDs light up green. If a disk array is present, the Logical Drive LED lights up green also. The Controller heartbeat LED blinks green once per second for five seconds, goes dark for ten seconds, then blinks green once per second for five seconds again. See Front Panel LEDs on page 295.
Logging In
Why am I not able to log in? Check the spelling and case. User names and passwords are case sensitive. I have entered correct user name and password, but still I am not able to log in. The Administrator may have deleted or disabled your user name. The login screen says Login failed: the requested service is busy. The subsystem might still be booting or rebooting. Dual controller subsystems take longer because the controllers boot individually, then they synch to each other. Wait a few moments, then try again.
347
Connection
Why cant I connect to my RAID System? Be sure you are using the correct IP address and entry text for the VTrak RAID subsystem. For more information, see Logging into WebPAM PROe on page 51. I verified the IP address and entry text but I still cannot connect. Check the physical network connections on the VTrak RAID subsystem. If these are OK, report the problem to your network administrator. I can access the VTrak over my company's intranet. But I cant access it from an outside Internet connection. How do I make the Internet connection work? This condition is not related to the VTrak or WebPAM PROe. The problem is caused by your firewall or network connection protocol. Contact your network administrator for help. I tried to log into WebPAM PROe but my browser showed the message cannot be displayed. What is the problem? The browser decided prematurely that WebPAM PROe was not responding. Click the browsers Refresh button. This action usually brings up the login screen.
Timeouts
WebPAM PROe was working OK. But then it timed out. What do I do now? WebPAM PROe times out when 24 minutes have passed with no user activity. User activity means any action you do in WebPAM PROe to view or manage the subsystem. This feature is included for security purposes. Have your administrator change the Webserver timeout interval. See page 102. Or to prevent WebPAM PROe from timing out, periodically click the interface with your mouse.
Email Messages
Why dont I receive email messages from WebPAM PROe? Check your User Event Subscription and User Email settings. See pages 84 and 85. If these are correct, see your network administrator for assistance with the mail server setup, email accounts, and other issues.
348
Chapter 9: Support
User Management
Why cant I create a new User? Only the Administrator or a Super User can create a User. If you are the Administrator or a Super User and cannot create a User, be sure the user name is not already in use. If you still cannot create a User, contact Technical Support. See page 351. Can I change my access rights? Only the Administrator or a Super User can change user access rights. See page 85 or page 218.
Lock
Person xyz set the lock and is not available. How do I unlock it? Ask your Administrator to release the lock. Note: The lock automatically releases after the set amount of time has passed.
Creating a Disk Array or Logical Drive

Why cant I see all RAID Levels in RAID Level dropdown menu? The selection of RAID Levels shown depends on number of physical drives available to the controller. For example, if there are only two physical drives, then you cannot see RAID 10, which requires four physical drives or RAID 50 that requires at least six. See RAID Levels on page 261. Why cant I create more than one logical drive on my disk array? If your logical drive takes up the entire capacity of the disk array, there is no room for another logical drive. Backup your important data, then delete the existing logical drive and create multiple smaller logical drives on the disk array. See Deleting a Logical Drive on page 136 or page 192 and Creating a Logical Drive Manually on page 135 or page 190.
Disk Array Degraded

According to WebPAM PROe, my disk array is degraded. What am I supposed to do? If the Auto Rebuild option is enabled and a hot spare drive is available, your disk array begins rebuilding automatically. Also see Disk Array Degraded/ Logical Drive Critical on page 317. When an disk array becomes degraded, can I still access the data on it? Yes, but reads and writes take longer while rebuilding is in progress.
349
Deleting a Disk Array or Logical Drive

Why cant I select Delete Disk Array or Delete Logical Drive? You must have Power or Super User Rights to delete a disk array or logical drive. See your Administrator about upgrading your access rights, if necessary. Also see Making User Settings on page 85 or page 218. Can I delete a Logical Drive without deleting the Disk Array? Yes. See Deleting a Logical Drive on page 136.

I replaced a failed physical drive with a used but known-good drive. The system does not rebuild to it. Why not? The replacement drive was previously used in a different disk array or logical drive. You must clear (erase) the Reserve Sector of the replacement disk drive before the system can rebuild to it. Clearing a Stale or a PFA Condition on page 120 or page 178.
Migrating a Disk Array

When I try to migrate a disk array from one RAID level to another, why doesn't the controller let me do it? Most RAID levels have a minimum and maximum number of physical drives. Be sure you have the correct number of drives available for the target disk array. See RAID Levels on page 261 and RAID Level Migration on page 275. I want to add two more drives to my RAID 1 disk array. Why won't the controller let me migrate it? A RAID 1 disk array uses only two disk drives. In this case, you can add two physical drives, then convert to a RAID 10 disk array. Most RAID levels have a minimum and maximum number of disk drives. See RAID Levels on page 261.
Media Patrol and PDM

Media Patrol and PDM are enabled on my system. But they never report anything. This is a good sign. Media Patrol and PDM operate transparently until they find a problem on a physical drive.
350
Chapter 9: Support
Contacting Technical Support

PROMISE Technical Support provides several support options for PROMISE users to access information and updates. We encourage you to use one of our electronic services, which provide product information updates for the most efficient service and support. If you decide to contact us, please have the following information available: Product model and serial number BIOS, firmware, and driver version numbers A description of the problem / situation System configuration information, including: motherboard and CPU type, hard drive models, SAS/SATA/ATA/ATAPI drives & devices, and other controllers.
Technical Support Services

PROMISE support http://www.promise.com/support/ (technical documents, drivers, utilities, etc.)
United States
E-mail Support Fax Support Phone Support If you wish to write us for support: e-Support On-Line +1 408 228 1100 Attn: Technical Support +1 408 228 1400 option 4 PROMISE Technology, Inc. 580 Cottonwood Drive Milpitas, CA 95035, USA
The Netherlands
E-mail Support Fax Support Phone Support If you wish to write us for support: e-Support On-Line +31 0 40 256 9463 Attn: Technical Support +31 0 40 235 2600 PROMISE Technology Europe B.V. Science Park Eindhoven 5228 5692 EG Son, The Netherlands
351
Germany
E-mail Support Fax Technical Support Phone Technical Support If you wish to write us for support: e-Support On-Line +49 0 2 31 56 76 48 29 Attn: Technical Support +49 0 2 31 56 76 48 10 PROMISE Technology Germany Europaplatz 9 44269 Dortmund, Germany
Italy
E-mail Support Fax Support Phone Support If you wish to write us for support: e-Support On-Line +39 0 6 367 124 00 Attn: Technical Support +39 0 6 367 126 26 PROMISE Technology Italy Piazza del Popolo 18 00187 Roma, Italia
Taiwan
E-mail Support Fax Support Phone Support If you wish to write us for support: e-Support On-Line +886 3 578 2390 Attn: Technical Support +886 3 578 2395 ext. 8845 or 8846 PROMISE Technology, Inc. 2F, No. 30, Industry E. Rd. IX Science-based Industrial Park Hsin-Chu 30075, Taiwan, R.O.C.
352
Chapter 9: Support
China
E-mail Support Fax Support Phone Support If you wish to write us for support: e-Support On-Line +86 10 8857 8015 Attn: Technical Support +86 10 8857 8085 or 8095 PROMISE Technology China Beijing 1108 West Wing, Shi Chuang Plaza 22 Information Rd, Shangdi IT Park Hai Dian District Beijing 100081, China
E-mail Support Fax Support Phone Support If you wish to write us for support:
e-Support On-Line +86 21 6249 4627 Attn: Technical Support +86 21 6249 4192, 4193, or 4199 PROMISE Technology China Shanghai Room 508, Leader Tower 1189 West Wu Ding Road Jing An District Shanghai 200042, China
Japan
E-mail Support Fax Support Phone Support If you wish to write us for support: e-Support On-Line +81 3 6801-8063 Attn: Technical Support +81 3 6801-8064 PROMISE Technology, Inc. 3F, Muramatsu Bldg 3-8-5 Hongo Bunkyo-ku, Tokyo 113-0033 Japan
353
Limited Warranty
PROMISE Technology, Inc. (PROMISE) warrants that this product, from the time of the delivery of the product to the original end user: a) b) c) d) all components, except the cache backup battery, for a period of three (3) years; the cache backup battery, for a period of one (1) year; will conform to PROMISEs specifications; will be free from defects in material and workmanship under normal use and service.
This warranty: a) b) c) d) applies only to products which are new and in cartons on the date of purchase; is not transferable; is valid only when accompanied by a copy of the original purchase invoice. Is not valid on spare parts.
This warranty shall not apply to defects resulting from: a) b) c) improper or inadequate maintenance, or unauthorized modification(s), performed by the end user; operation outside the environmental specifications for the product; accident, misuse, negligence, misapplication, abuse, natural or personal disaster, or maintenance by anyone other than a PROMISE or a PROMISE-authorized service center.
Disclaimer of other warranties

This warranty covers only parts and labor, and excludes coverage on software items as expressly set above. Except as expressly set forth above, PROMISE DISCLAIMS any warranties, expressed or implied, by statute or otherwise, regarding the product, including, without limitation, any warranties for fitness for any purpose, quality, merchantability, non-infringement, or otherwise. PROMISE makes no warranty or representation concerning the suitability of any product for use with any other item. You assume full responsibility for selecting products and for ensuring that the products selected are compatible and appropriate for use with other goods with which they will be used.
354
Chapter 9: Support
PROMISE DOES NOT WARRANT that any product is free from errors or that it will interface without problems with your computer system. It is your responsibility to back up or otherwise save important data before installing any product and continue to back up your important data regularly. No other document, statement or representation may be relied on to vary the terms of this limited warranty. PROMISEs sole responsibility with respect to any product is to do one of the following: a) b) replace the product with a conforming unit of the same or superior product; repair the product.
PROMISE shall not be liable for the cost of procuring substitute goods, services, lost profits, unrealized savings, equipment damage, costs of recovering, reprogramming, or reproducing of programs or data stored in or used with the products, or for any other general, special, consequential, indirect, incidental, or punitive damages, whether in contract, tort, or otherwise, notwithstanding the failure of the essential purpose of the foregoing remedy and regardless of whether PROMISE has been advised of the possibility of such damages. PROMISE is not an insurer. If you desire insurance against such damage, you must obtain insurance from another party. Some states do not allow the exclusion or limitation of incidental or consequential damages for consumer products, so the above limitation may not apply to you. This warranty gives specific legal rights, and you may also have other rights that vary from state to state. This limited warranty is governed by the State of California.
Your Responsibilities
You are responsible for determining whether the product is appropriate for your use and will interface with your equipment without malfunction or damage. You are also responsible for backing up your data before installing any product and for regularly backing up your data after installing the product. PROMISE is not liable for any damage to equipment or data loss resulting from the use of any product.
355
Returning the Product For Repair

If you suspect a product is not working properly, or if you have any questions about your product, contact our Technical Support staff through one of our Technical Services, making sure to provide the following information: Product model and serial number (required) Return shipping address Daytime phone number Description of the problem Copy of the original purchase invoice
The technician help you determine whether the product requires repair. If the product needs repair, the technician issues an RMA (Return Merchandise Authorization) number. Important Obtain an RMA number from Technical Support before you return the product and write the RMA number on the label. The RMA number is essential for tracking your product and providing the proper service. Return ONLY the specific product covered by the warranty. Do not ship cables, manuals, diskettes, etc. USA and Canada: PROMISE Technology, Inc. Customer Service Dept. Attn.: RMA # ______ 47654 Kato Road Fremont, CA 94538 Return the product to your dealer or retailer. Contact them for instructions before shipping the product. You must follow the packaging guidelines for returning products: Use the original shipping carton and packaging Include a summary of the products problem(s) Write an attention line on the box with the RMA number Include a copy of your proof of purchase
Other Countries:
356
Chapter 9: Support
You are responsible for the cost of insurance and shipment of the product to PROMISE. Note that damage incurred due to improper transport or packaging is not covered under the Limited Warranty. When repairing returned product(s), PROMISE may replace defective parts with new or reconditioned parts, or replace the entire unit with a new or reconditioned unit. In the event of a replacement, the replacement unit is under warranty for the remainder of the original warranty term from purchase date, or 30 days, whichever is longer. PROMISE pays for standard return shipping charges only. You must pay for any additional shipping options, such as express shipping.
357
358
Appendix A: Useful Information

The appendix covers the following topics: SNMP MIB Files (below) Adding a Second RAID Controller (page 359) Installing a Second RAID Controller (page 360)
SNMP MIB Files

PROMISE supplies two MIB files to integrate the VTrak E830f, E630f, or E330f subsystem into your SNMP system. These files are in the SNMP folder on the Software CD. The MIB files are: FCMGMT-MIB.mib raidv4.mib
For help loading the MIB files, see the instructions that came with your MIB browser.
Adding a Second RAID Controller

If your VTrak E-Class subsystem shipped with one RAID controller, you can add a second RAID controller. The second controller must have: The same firmware version as the currently installed controller The same amount of SDRAM as the currently installed controller
To obtain information for the currently installed controller: 1. 2. 3. 4. 5. 6. 7. Click the Device tab. Click the Component List icon. Mouse-over the Controller and click the View button. On the Information tab, note the Firmware Version. Click the Advanced information tab. Note the Slot 1 and Slot 2 Memory Size. Contact contact PROMISE Technical Support to order your second controller.
PROMISE Technical Support prepares the new controller with firmware and SDRAM to match the existing controller in your VTrak subsystem.
359
Installing a Second RAID Controller

To install a second RAID controller in your VTrak subsystem: 1. 2. 3. 4. Shut down the subsystem. Remove the blank cover from the right controller slot. Carefully slide the new controller into the slot until the handle locks in place. Attach your data and management cables to the new controller, as needed. See the Making Management and Data Connections on page 19 for cable connection information. 5. 6. Power up the subsystem and launch WebPAM PROe. In WebPAM PROe, click the Dashboard tab and look under System Status. If the new controller has a green check icon, the installation is completed. Go to New Settings for Dual Controllers on page 361. If the new controller has a yellow ! icon, one of the controllers went into maintenance mode because its firmware or memory do not match the other controller. See RAID Controller in Maintenance Mode, below.
RAID Controller in Maintenance Mode

To manage a RAID controller in maintenance mode: 1. 2. 3. 4. Click the AdminTool tab. Click the Firmware Update icon. Click the Controller Firmware Update option. Compare the Firmware version on Controller 1 and Controller 2. If the firmware versions are different, go to Updating the Subsystem Firmware on page 241. If the firmware versions match, contact PROMISE Technical Support for help installing the correct memory into the controller.
360
Installing a Second RAID Controller
New Settings for Dual Controllers

With the second controller successfully installed, make the following settings: Redundancy Type Set to Active-Active or Active-Standby. See Making Subsystem Settings on page 60 or page 162. LUN Affinity If you choose Active-Active redundancy. See Making Controller Settings on page 70 or page 167. Note The VTrak subsystem boots its RAID controllers sequentially. With a second controller installed, your subsystem takes about a minute longer to boot. This condition is normal.
Dual Controllers and SATA Drives

If your VTrak subsystem has SATA disk drives installed, you must install a SASto-SATA adapter on each of the SATA drives. Without the SAS-to-SATA adapter, SATA drives display a red X Usable status. Obtain SAS-to-SATA adapters from PROMISE Technology at http://www.promise.com. SAS drives do not require adapters. Also see Installing Disk Drives on page 15 and Contacting Technical Support on page 351. icon and Not
361
362
Appendix B: Multipathing on Windows

The appendix covers the following topics: Before You Begin (below) Installing PerfectPath (page 364) Verifying Installation (page 365) Running Perfect Path View (page 367) Monitoring Your LUNs and Paths (page 368) Features and Settings (page 374) Troubleshooting (page 381) Updating PerfectPath (page 382) Repairing PerfectPath (page 383) Removing PerfectPath (page 384)
PerfectPath is a multipathing software designed for use with PROMISE VTrak EClass RAID subsystem products and includes: GUI Graphic user interface, PerfectPath View, for easy monitoring and settings. DSM Device-Specific Module driver. Events Service Notification service posts events to the application log.
PerfectPath supports Fibre Channel and Serial Attached SCSI (SAS) technologies. PerfectPath runs on Windows Server 2008 and 2008 R2 operating systems, on both x86 and x64 platforms. For a list of supported OSes, download the latest compatibility list from PROMISE support: http://www.promise.com/support/.
Before You Begin

Before you install PerfectPath on your Windows Host PC, you must: Install your Fibre Channel or SAS HBA cards and their device drivers. Close all computer and storage management applications, including Computer Management, Device Manager, Disk Management, and the Registry Editor.
363
Note If you have a complex configuration, such as multiple HBAs connected with multiple LUNs and paths to your PC, installation can take a long time. You can choose to temporarily disconnect your storage, install PerfectPath, then reconnect your storage to reduce installation time.
Installing PerfectPath
To install the PerfectPath software: 1. Download the PerfectPath installer file from PROMISE support: http://www.promise.com/support/ and save the installer file to your Windows desktop. Double-click the PerfectPath.exe installer file to start the installer. In the Welcome screen, click the Next button. In the License Agreement screen, click the I accept the terms of this license agreement option, then click the Next button. In the Close All Disk Management Applications screen, click the Next button. In the Ready to Install the Program screen, click the Install button. Optional. If the installer displays a Security Alert message about an unsigned driver, click the Yes button to continue installation. The software files install onto the system drive in the Program Files\Promise\PerfectPath folder. There is no optional install location. 8. 9. In the Install Completed screen, click the Finish button. In the Restart message box, click the Yes button to restart your PC. Important Save the PerfectPath installer file in case you need to repair your PerfectPath software in the future. See Repairing PerfectPath on page 383.
2. 3. 4. 5. 6. 7.
364
Verifying Installation
Verifying Installation
Before you can verify PerfectPath installation: Your Host PC must have multiple data-path connections to the VTrak subsystem. The VTrak must be fully booted. The VTrak must have at least one logical drive.
See Making Management and Data Connections on page 19 for information about making data connections. See Creating a Disk Array Manually on page 122 or Creating a Disk Array on page 180 for information about creating RAID arrays and logical drives. You can verify Perfect Path installation on the Host PC in one of three ways: Start Menu Services List Device Manager
Start Menu
To verify PerfectPath installation in the Start menu: From the Start menu, choose All Programs > PerfectPath > PerfectPath View. The PerfectPath View software starts.
Services List
To verify PerfectPath installation in the Services list: 1. 2. 3. 4. From the Start menu, right-click the Computer icon and choose Manage from the popup menu. In the Server Management tree, click the + icon beside Configuration. Click the Services icon. In the Services window, look for the PerfectPath Events Service. If the PerfectPath Events Service is present, PerfectPath has been installed. The Service should be Started and set to Automatic on the Local System.
Device Manager
To verify PerfectPath installation in the Device Manager: 1. 2. 3. From the Windows desktop, right-click the Computer icon and choose Manage from the dropdown menu. In the Server Management tree, click the + icon beside Diagnostics. Under Diagnostics, click the Device Manager.
365
4. 5.
In the Device Manager window, click Disk drives. Under Disk drives, look for Promise VTrak Multi-Path Disk Device in the Disk drives list. See Figure 1.
Figure 1. Device manager window
366
Running Perfect Path View
Running Perfect Path View

Running PerfectPath View includes these functions: Starting PerfectPath View (page 367) Quitting PerfectPath View (page 367)
Starting PerfectPath View

To start PerfectPath View: From the Start menu, choose All Programs > PerfectPath > PerfectPath View. The PerfectPath View window opens. See Figure 2. Figure 2. PerfectPath View window
Quitting PerfectPath View

To quit the PerfectPath View application, do one of the following actions: From the System menu, choose Exit. Click the Close icon on the PerfectPath View window.
367
Monitoring Your LUNs and Paths

Monitoring your LUNs and Paths includes these functions: Viewing LUN Properties (page 368) Viewing Path Properties (page 369) Viewing LUN Performance Statistics (page 370) Viewing Path Performance Statistics (page 371) Viewing Events (page 373) Clearing Path Statistics (page 373)
Viewing LUN Properties

To view a list of all LUNs: 1. 2. Click a Server in Tree View.
Click the Properties tab. The Properties tab reports: System Name, OS type, and version LUNs Name, size, serial number, and load balance policy
368
Move the scroll bar or expand the window to see all of the reported information. To view a single LUN and all of its Paths: 1. 2. Click the LUN in Tree View.
Click the Properties tab. The Properties tab reports: LUNs Name, size, and load balance policy Paths Path ID, state, and adapter name
Move the scroll bar or expand the window to see all of the reported information. See also: Load Balance Policy on page 375 Refreshing the Objects on page 379
Viewing Path Properties

To view Path properties: 1. 2. Click a Path in Tree View.
Click the Properties tab. The Properties tab reports: SCSI Port number SCSI Path ID SCSI Target SCSI LUN
369
See also: Load Balance Policy on page 375 Refreshing the Objects on page 379
Viewing LUN Performance Statistics

To view performance statistics for a LUN: 1. 2. Click the LUN in Tree View.
Click the Performance tab. The Performance tab reports the state and cumulative counts for each path to that LUN.
370
Move the scroll bar or expand the window to see all of the reported statistics. The Performance tab reports the following data for each path: Path ID State (Active or not) Read Requests Write Requests Bytes Read Bytes Written Non-IO Requests Queue Depth Retries Count Failure Count
An Active state indicates this path is available to handle I/O requests. If Active does not appear, the path is designated as Standby. Active and Standby states are determined by Load Balance Policy. See also: Viewing Path Performance Statistics on page 371 Load Balance Policy on page 375
Viewing Path Performance Statistics

To view performance statistics for a Path: 1. 2. Click a Path in Tree View.
Click the Performance tab.
371
The Performance tab reports the state and cumulative counts for a specific path.
Move the scroll bar or expand the window to see all of the reported statistics. The Performance tab reports the following data for each path: Path ID State (Active or not) Read Requests Write Requests Bytes Read Bytes Written Non-IO Requests Queue Depth Retries Count Failure Count
An Active state indicates this path is available to handle I/O requests. If Active does not appear, the path is designated as Standby. Active and Standby states are determined by Load Balance Policy. See also: Viewing Path Performance Statistics on page 371 Load Balance Policy on page 375
372
Viewing Events
Click the Events tab to view MPIO related events. The data includes: Type Error, Warning, or Information Time Date Server Message
Move the scroll bar or expand the window to see all of the reported information. Use this information to verify that settings changes took place and diagnose problems. See also: Automatic Load Balancing for Failover Policy on page 374 Load Balance Policy on page 375 Path Verification on page 376 PDO Removal on page 377 Refreshing the Objects on page 379
Clearing Path Statistics

You can Clear Path Statistics for all paths as needed for monitoring and diagnostic purposes. To clear the statistics for ALL paths, do one of the following actions: From the Operations menu, choose Clear Path Statistics. In the Tree, right-click the LUN from the popup menu. icon, and choose Clear Path Statistics
373
Features and Settings

Features and Settings include the following functions: Automatic Load Balancing for Failover Policy (page 374) Load Balance Policy (page 375) Path Verification (page 376) PDO Removal (page 377) Performance Tab Refresh Rate (page 378) Round Robin Count (page 378) Refreshing the Objects (page 379) Viewing System Information (page 379) Saving System Information (page 380)
Automatic Load Balancing for Failover Policy

The PROMISE MPIO solution can load balance the paths for your LUNs with load balance policy set to Failover. With Automatic Load Balancing enabled, the LUNs set to Failover policy are automatically redistributed among all available paths when: A path fails A failed path comes back online A new path is added
Automatic Load Balancing, when enabled, provides optimal data throughput for LUNs set to Failover policy. Note that Automatic Load Balancing has NO effect upon LUNs set to Round Robin, Round Robin with Subset, or Least Queue Depth.
Enabling Automatic Load Balancing

To enable automatic load balancing: From the Operations menu, choose Auto Load Balance. When you see a check mark beside Auto Load Balance in the Operations menu, this feature is enabled. See also: Viewing LUN Properties on page 368 Viewing LUN Performance Statistics on page 370 Load Balance Policy on page 375
374
Load Balance Policy

Load Balance Policy is a method of equalizing the I/O traffic over each path by systematically dividing the load among multiple paths. Failover Policy No load balancing. With Automatic Load Balancing disabled, the first path discovered is the primary path. I/Os follow the active path until it fails, then they change to next available path. Each LUN uses only one active path. See Automatic Load Balancing for Failover Policy on page 374. Round Robin Policy I/Os follow all active paths, changing paths at the specified I/O count. You can set the I/O count in the General tab of the Advanced Settings dialog box. If LUN Affinity is enabled do NOT use Round Robin. See Making Controller Settings on page 70 or page 167. Round Robin with Subset Policy One or more paths are designated as standby. I/Os follow all active paths, changing at the specified I/O count. You can set the I/O count in the General tab of the Advanced Settings dialog box. If LUN Affinity is enabled, you can use Round Robin with Subset. See Making Controller Settings on page 70 or page 167. Least Queue Depth Policy I/Os follow the path with the least number of requests queued.
Note that you can enable Automatic Load Balancing for LUNs with policy set to Failover. See Automatic Load Balancing for Failover Policy on page 374.
Changing Load Balance Policy Settings

To change load balance policy settings: 1. Do one of the following actions: From the Operations menu, choose Change Load Balance Policy. In Tree View, highlight a LUN Policy icon. and choose Change Load Balance and click the Change Load Balance
In Tree View, right-click a a LUN Policy from the popup menu.
The Change Load Policy dialog box appears with the Load Balance Policy tab displayed. 2. Click the option button for one of the Load Policies. Failover Policy Round Robin Policy Round Robin with Subset Policy Least Queue Depth Policy
375
3. 4.
Click the Next button. The Path Selection tab displays. Take the action appropriate for your policy selection. For Round Robin and Least Queue Depth, no action is required. Skip to step 5. For Failover, move the path you want to be active to the Primary Path Selected pane. Move all other paths to the Path Available pane. For Round Robin with Subset, move the paths you want to be active to the Primary Path Selected pane. Move the paths you want as standby to the Path Available pane. You can have all paths in the Subset.
5. 6.
Click the Next button. The Summary tab displays the current and selected (new) policy. Click the Finish button to apply your settings. The new settings take effect immediately.
See also: Round Robin Count on page 378 Refreshing the Objects on page 379
Path Verification
Path verification monitors any failed paths and automatically verifies them if they become available again. There are two Path Verification Settings: Enable / disable Verification period in seconds
Changing Path Verification Settings

To make path verification settings: 1. Do one of the following actions: Click the Advanced Settings icon.
From the Operations menu, choose Advanced Settings.
The Advanced Settings dialog box appears with the MPIO Parameters tab displayed. 2. Check the Enable Path Verification box to enable path verification. Uncheck to disable.
376
3.
Click the arrows or type a new value in the Path Verification Period field to change the interval. 30 seconds is the default value. Click the Apply button. Click the OK button in the confirmation box. The new setting takes effect immediately.
4. 5.
See also: Load Balance Policy on page 375 PDO Removal on page 377 Refreshing the Objects on page 379
PDO Removal
PDO removal refers to the action of deleting a multipath input/output (MPIO) disk from the Windows Device Manager after all paths to a physical device object (PDO) have failed. PDO removal interval refers to the period of time in seconds between the moment all paths to a PDO are disconnected and the MPIO disk disappears from the Device Manager.
Changing PDO Removal Settings

To change PDO removal settings: 1. Do one of the following actions: Click the Advanced Settings icon.
The Advanced Settings dialog box appears with the MPIO Parameters tab displayed. 2. Click the arrows or type a new value in the PDO Remove Period field to change the interval. 120 seconds is the PROMISE-recommended default value. 3. 4. Click the Apply button. Click the OK button in the confirmation box. The new setting takes effect immediately. See also Path Verification on page 376.
377
Performance Tab Refresh Rate

Refresh Rate refers to the number of seconds between refreshes of the data reported on the Performance tab.
Changing Refresh Rate Settings

To change the refresh rate on the Performance tab: 1. Do one of the following actions: Click the Advanced Settings icon.
The Advanced Settings dialog box appears with the MPIO Parameters tab displayed. 2. 3. Click the General tab. Under Refresh Rate, click the arrows or type a new value in the Seconds field to change the interval. 5 seconds is the default value. 4. Click the Apply button. The new setting takes effect immediately. See also: Viewing LUN Performance Statistics on page 370 Viewing Path Performance Statistics on page 371
Round Robin Count

When you set your path Load Balance Policy to Round Robin, the I/Os follow all active paths, changing paths at the specified I/O count. You can set the I/O count in the General tab of the Advanced Settings dialog box.
Changing the Round Robin Count

To change Round Robin Count settings: 1. Do one of the following actions: Click the Advanced Settings icon. icon.
From the Operations menu, choose Settings
The Advanced Settings dialog box appears with the MPIO Parameters tab displayed. 2. 3. Click the General tab. Under Round Robin Count, click the arrows or type a new value in the I/Os per Path field to change the count.
378
10 I/Os is the default value. 4. Click the Apply button. The new setting takes effect immediately. See also: Load Balance Policy on page 375 Viewing LUN Performance Statistics on page 370 Viewing Path Performance Statistics on page 371
Refreshing the Objects

Use this function after making an addition or deletion to your LUNs or paths. To refresh the objects, do one of the following actions: From the Operations menu, choose Refresh. Click the Refresh icon.
PerfectPath automatically displays all reported changes. However, some actions are not reported. The Refresh action enables you to see the latest information. See also: Automatic Load Balancing for Failover Policy on page 374 Load Balance Policy on page 375 Path Verification on page 376 PDO Removal on page 377
Viewing System Information

To view System information and settings, do one of the following actions: From the System menu, choose System Information. Click the System Information icon.
The System Information dialog box displays.
379
System information supplies information about the Host PC or Server, including: Host Name Operating System OS Version OS Manufacturer IP Address Storport File Storport Version MPIO File Note File information includes the file name and location of the installed file in the servers file system. MPIO Version MPDEV File MPDEV Version MPSPFLTR File MPSPFLTR Version DSM File DSM Version
Saving System Information

To save the current System information and settings data to a text file: 1. Do one of the following actions: From the System menu, choose System Information. Click the System Information icon.
The System Information dialog box displays. 2. 3. 4. 5. 6. From the System Information dialog box, click the Save button. In the Save As dialog box, navigate to the folder where you want to save the file. Type a file name into the File name field. Append the file name with a .txt suffix. Click the Save button. Click the OK button in the confirmation box. Your information and settings data are saved to a text file in the folder you designated.
380
Troubleshooting
Troubleshooting
If you see no LUNs in the PerfectPath GUI, or no Multi-Path Disk Devices under Disk drives (see Figure 3), do the following actions: Verify that there is at least one logical drive on the VTrak Check your HBA cards and driver installation Check your data connections
Make any needed corrections and reboot your Host PC as needed. Figure 3. Device manager window
381
Updating PerfectPath
To update your PerfectPath software to the latest version: 1. Download the new PerfectPath installation file from PROMISE support: http://www.promise.com/support/ and save the installation file to your Windows desktop. Manually remove the current PerfectPath installation. See Removing PerfectPath on page 384. 3. Install the new PerfectPath software. See Installing PerfectPath on page 364.
2.
382
Repairing PerfectPath
Repairing PerfectPath
To implement this procedure, you must use the same PerfectPath.exe installer file that you used to install the PerfectPath software onto your PC. The installers version number is part of its file name. However, there is no corresponding number in the PerfectPath software. To repair the PerfectPath software: 1. 2. 3. 4. 5. 6. Double-click the PerfectPath.exe file to start the installer. In the Welcome screen, click the Next button. In the Program Maintenance screen, choose the Repair option, then click the Next button. In the Ready to Repair the Program screen, click the Install button. In the Install Completed screen, click the Finish button. In the Restart message box, click the Yes button to restart your PC.
383
Removing PerfectPath
Preferred Method
This procedure uses the uninstaller included with PerfectPath. To remove the PerfectPath software: 1. 2. 3. 4. 5. 6. From the Start menu, choose All Programs > PerfectPath > Uninstall PerfectPath. In the Welcome screen, click the Next button. In the Program Maintenance screen, choose the Remove option, then click the Next button. In the Remove the Program screen, click the Remove button. In the Completed screen, click the Finish button. In the Restart message box, click the Yes button to restart your PC.
Alternate Method 1
This procedure uses the Windows uninstaller. To remove the PerfectPath software: 1. 2. 3. 4. In the Start menu, choose Control Panel, then choose Programs and Features. Right-click Perfect Path, and choose Uninstall from the popup menu. In the Confirmation box, click the Yes button. In the Restart message box, click the Yes button to restart your PC.
Alternate Method 2
To use this procedure, the PerfectPath.exe installer file must be the same version number as the PerfectPath software installed on your PC. To remove the PerfectPath software: 1. 2. 3. 4. 5. 6. Double-click the PerfectPath.exe file to start the installer. In the Welcome screen, click the Next button. In the Program Maintenance screen, choose the Remove option, then click the Next button. In the Remove the Program screen, click the Remove button. In the Completed screen, click the Finish button. In the Restart message box, click the Yes button to restart your PC.
384
Appendix C: Multipathing on Linux

The appendix covers the following topics: Before You Begin (below) Task 1: Meeting Package Requirements (page 387) Task 2: Preparing the Configuration File (page 390) Task 3: Making Initial Host Settings (page 392) Task 4: Create and Configure Devices (page 394) Task 5: Setting-up ALUA (page 395) RPM Packages and Documents for Linux MPIO (page 400) Linux MPIO: Known Issues (page 402) Sample multipath.conf File (page 403)
PROMISE has fully tested VTrak multipathing on RedHat RHEL 5.3, 5.4, and 5.5; and SuSE SLES 10 SP2, 10 SP3, 11, and 11 SP1. Coverage in this Product Manual is limited to those OSes. Multipathing is possible on other Linux OSes. PROMISE has not tested every possible combination and therefore does not attempt to cover them here. For a list of supported OSes, download the latest compatibility list from PROMISE support: http://www.promise.com/support/.
Before You Begin

Before you can set up multipathing on your Linux Host PC, you must: Install your Fibre Channel or SAS HBA card into the Host PC. Install the HBA card drivers onto the Host PC Setup your VTrak, install your physical drives and create your logical drives. Attach your Fibre Channel or SAS cables from the HBA card to the VTrak RAID subsystem. Install RHEL 5.x with the linux mpath option. For ALUA, refer to the PROMISE Linux support packages. See page 400.
Refer to the Linux Administration Manual, your HBA documentation, and this Appendix as needed for more information.
385
Check Initial Setup

To check your initial setup, verify that you can view the logical drives on your VTrak from your Linux desktop or terminal window. Refer to the Linux Administration Manual for the procedure on your system. If you can see your logical drives, the system is properly configured. Go to Task 1: Meeting Package Requirements on page 387. If you cannot see your logical drives, make the necessary adjustments and check again.
386
Task 1: Meeting Package Requirements

The latest device mapper and multipath packages must be loaded onto your Linux host before configuring Device Mapper Multipath (DM-MP). When this document was written, the current versions were: For RHEL 5.3 device-mapper-1.02.28-2.el5 device-mapper-multipath-0.4.7-23.el5 device-mapper-1.02.32-1.el5 device-mapper-multipath-0.4.7-30.el5 device-mapper-1.02.39-1.el5 device-mapper-multipath-0.4.7-34.el5 device-mapper-1.02.13-6.14 multipath-tools-0.4.7-34.38 device-mapper-1.02.13-6.14 multipath-tools-0.4.7-34.50.10 device-mapper-1.02.27-8.6 multipath-tools-0.4.8-40.1 device-mapper-1.02.27-8.20 multipath-tools-0.4.8-40.21.1
For RHEL 5.4
For RHEL 5.5
For SLES 10 SP2
For SLES 10 SP3
For SLES 11
For SLES 11 SP1
Installing Packages
The easiest and most effective way to install the device mapper and multipath tool is during OS installation. The device mapper installs by default, regardless of the configuration you select. However, you must manually specify the multipath tool, as it does not install as a part of any of the configurations of either OS. The multipath tool is listed as an option under Base System. For hosts with the OS already installed, you can add the device mapper and multipath tool, if they are missing. Example: To add the multipath tool for RHEL 5.x, do the following actions: 1. Open a terminal window.
387
2.
Type the following command and press Enter: # rpm -ivh device-mapper-multipath-0.4.7-8.el5.i386.rpm The system returns the following lines: Preparing... ##################### [100%] 1:device-mapper-multipath##################### [100%] # (or a similar message) Important Where possible, obtain the device mapper and multipath tool from the original installation CDs to ensure full compatibility with your existing OS. Refer to your OS documentation for more information.
Verifying Packages RedHat

To verify that the required packages are installed on the host, do the following actions: 1. 2. Open a terminal window. Type the following command and press Enter: # rpm -qa | grep device-mapper If the required packages are present, the system returns the following lines. RHEL 5.3: device-mapper-1.02.28-2.el5 device-mapper-multipath-0.4.7-23.el5 RHEL 5.4: device-mapper-1.02.32-1.el5 device-mapper-multipath-0.4.7-30.el5 RHEL 5.5: device-mapper-1.02.39-1.el5 device-mapper-multipath-0.4.7-34.el5 Note that the actual version number might be different, depending on your configuration.
Verifying Packages SuSE

To verify that the required packages are installed on the host, do the following actions: 1. Open a terminal window.
388
2.
Type the following command and press Enter: # rpm -qa | grep device-mapper If the required package is present, the system returns the following line. SLES 10 SP2: device-mapper-1.02.13-6.14 SLES 10 SP3: device-mapper-1.02.13-6.14 SLES 11: device-mapper-1.02.27-8.6 SLES 11 SP1: device-mapper-1.02.27-8.17.20 Note that the actual version number might be different, depending on your configuration.
3.
Type the following command and press Enter: # rpm -qa | grep multipath-tools If the required package is present, the system returns the following line. SLES 10 SP2: multipath-tools-0.4.7-34.38 SLES 10 SP3: multipath-tools-0.4.7-34.50.10 SLES 11: multipath-tools-0.4.8-40.1 SLES 11 SP1: multipath-tools-0.4.8-40.21.1 Note that the actual version number might be different, depending on your configuration.
389
Task 2: Preparing the Configuration File

To setup multipathing with VTrak, or any other subsystem, you must provide the required device attributes in a configuration file. The multipath configuration file is named multipath.conf. The functional version of the file is saved in the /etc directory.
RedHat Systems
For RedHat systems, there is a default /etc/multipath.conf file. However, the default file does not have the required device attributes to work with VTrak. There are also sample configuration files in the /usr/share/doc/device-mappermultipath-[version] directory: multipath.conf.annotated multipath device attributes listed and defined multipath.conf.synthetic multipath device attributes listed only
SuSE Systems
For SuSE systems, there is no default /etc/multipath.conf file. There are sample multipath configuration files in the /usr/share/doc/packages/ multipath-tools directory: multipath.conf.annotated multipath device attributes listed and defined multipath.conf.synthetic multipath device attributes listed only
Editing a Configuration File

You must provide a configuration file with required device attributes to work with VTrak. See the sample configuration file on page 403. Take the following actions to prepare a configuration file: 1. 2. 3. Choose an existing multipath.conf file and open the file in a text editor. Save a working copy of the file under another name. Edit the file to include the following line under defaults: defaults { user_friendly_names yes }
390
Task 2: Preparing the Configuration File
4.
Edit the file to include the following lines under devices: devices { device { vendor product path_grouping_policy getuid_callout path_checker path_selector hardware_handler failback rr_weight rr_min_io no_path_retry features product_blacklist } } "Promise" "VTrak" multibus "/sbin/scsi_id -g -u -s /block/%n" readsector0 "round-robin 0" "0" immediate uniform 100 20 "1 queue_if_no_path" "VTrak V-LUN"
5.
Edit the file to include the following lines under devnode_blacklist: devnode_blacklist { devnode "^sda$" devnode "^(ram|raw|loop|fd|md|dm-|sr|scd|st)[0-9]*" devnode "^hd[a-z]" devnode "^cciss!c[0-9]d[0-9]*" }
6. 7. 8.
Be sure all the relevant lines of your configuration file are uncommented. Remove the # character from the beginning of the line. Save the file as multipath.conf. Place a copy of the multipath.conf file into the Hosts /etc directory.
391
Task 3: Making Initial Host Settings

After the packages and configuration file are installed, the Host is ready to accept multipath settings.
Setting the Daemon to Run

RHEL 5.3, 5.4, 5.5
This action requires RHEL installation with the linux mpath Option. See Before You Begin on page 385. To set the MP daemon to run at boot time: 1. 2. Open a terminal window. Verify that /etc/rc.d/rc[3~5].d/ has a symbolic link to /etc/rc.d/init.d/multipathd. Also see the Note below. Run the command: # ls -al /etc/rc.d/rc[3~5].d/ | grep multipathd 3. If there is no symbolic link, run the command: # cd /etc/rc.d/rc[3~5].d/ Then run the command: # ln -s /etc/rc.d/init.d/multipathd S13multipathd Note: /etc/rc.d/rc[3~5].d saves a link to start at each run level. Run level 3 is for a single user. Run level 4 is for multiple users. Run level 5 is for multiple users on X Windows.
SLES 10 SP2, 10 SP3, 11, 11 SP1

To set the MP daemon to run at boot time: 1. 2. Open a terminal window. Set the daemon to run at boot time. # chkconfig multipathd on The system does not return anything.
Verifying the Modules are Loaded

To verify that the DM-MP modules are loaded: 1. 2. Open a terminal window. Verify that the multipath module is loaded. # lsmod | grep dm_multipath
392
Task 3: Making Initial Host Settings
If the module is loaded, the system returns: dm_multipath 215770 (or a similar message) 3. Verify that the device mapper module is loaded. # lsmod | grep dm_mod If the module is loaded, the system returns: dm_mod 56537 8 dm_snapshot... (or a similar message)
Verifying the Daemon is Running

To verify that the MP daemon is running: 1. 2. 3. Open a terminal window. Check the daemons status. # /etc/init.d/multipathd status Do one of the following actions: If the system returns: multipathd is running (or a similar message) Go to Task 4: Create and Configure Devices on page 394. If the system returns: multipathd is stopped (or a similar message) Start the MP daemon. # /etc/init.d/multipathd start Then go to Task 4: Create and Configure Devices on page 394.
393
Task 4: Create and Configure Devices

This step applies the settings from the multipath.config file to the Host. 1. 2. Open a terminal window. Type the following command and press Enter: #multipath -v3 The system returns: ... ==== paths list ==== uuid hcil dev dev_t pri dm_st chk_st vend... 222490001555459b3b 2:0:0:0 sdb 8:16 1 [undef][undef] Prom... 222b40000155a75b49 2:0:0:2 sbc 8:32 1 [undef][undef] Prom... 20efcff5501000121a 3:0:0:0 sbd 8:48 1 [undef][undef] Prom... 222b44000155ebf0c 3:0:0:1 sde 8:64 1 [undef][undef] Prom... params = 1 que_if_no_path 0 1 1 round-robin 0 1 1 8:64 100 status = 1 0 0 1 1 A 0 1 0 8:64 A 0 sde: mask = 0x4 sde: path checker = readsector0 (controller setting) sde: state = 2 ... (or a similar message) 3. Restart the MP daemon. #/etc/init.d/multipathd restart The system returns: Stopping multipathd daemon (or a similar message) Starting multipathd daemon (or a similar message) For more information about path monitoring functions, type help and press Enter.
394
Task 5: Setting-up ALUA

VTrak supports Asymmetric Logical Unit Access (ALUA) on the latest Linux distributions: RedHat Linux RHEL 5.4 RedHat Linux RHEL 5.5 SuSE Linux SLES 10 SP3 SuSE Linux SLES 11 SuSE Linux SLES 11 SP1
PROMISE provides RPM packages and multipath.conf files for ALUA. See RPM Packages and Documents for Linux MPIO on page 400.
RedHat Linux RHEL 5.4

Default Kernel
To support ALUA within RHEL 5.4 using the default kernel without XEN or PAE support: 1. 2. 3. Install RHEL 5.4. When the CD is chosen for installation, immediately type linux mpath. Copy the PROMISE-supplied multipath.conf file to the /etc directory. cp multipath.conf-vtrak-alua-rhel5-4 /etc/multipath.conf Install the appropriate scsi_dh_alua driver module. i386 cd /usr/src/redhat/RPM/i386 rpm -ivh scsi_dh_alua_VTrak-1-1.i386.rpm x86_64 cd /usr/src/redhat/RPM/x86_64 rpm -ivh scsi_dh_alua_VTrak-1-1.x86_64.rpm 4. Check the multipath configuration. Multipath -ll (multipath -v4)
Kernel with XEN or PAE support

To support ALUA within RHEL 5.4 using kernel with XEN or PAE support: 1. 2. Install RHEL 5.4. When the CD is chosen for installation, immediately type linux mpath. Copy the PROMISE-supplied multipath.conf file to the /etc directory. cp multipath.conf-vtrak-alua-rhel5-4 /etc/multipath.conf
395
3. 4.
Install this patched alua_dh_scsi source module. rpm -ivh scsi_dh_alua_VTrak-1-1.src.rpm Make your own rpm. cd /usr/src/redhat/SPEC rpmbuild -ba scsi_dh_alau.spec
5. 6.
Determine your system architecture, x86_64 or i386. uname -a Install the appropriate scsi_dh_alua driver module. i386 cd /usr/src/redhat/RPM/i386 rpm -ivh scsi_dh_alua_VTrak-1-1.i386.rpm x86_64 cd /usr/src/redhat/RPM/x86_64 rpm -ivh scsi_dh_alua_VTrak-1-1.x86_64.rpm
7.
Check the multipath configuration. Multipath -ll (multipath -v4)
RedHat Linux RHEL 5.5

Default Kernel
To support ALUA within RHEL 5.5 using the default kernel without XEN or PAE support: 1. 2. 3. Install RHEL 5.5. When the CD is chosen for installation, immediately type linux mpath. Copy the PROMISE-supplied multipath.conf file to the /etc directory. cp multipath.conf.alua-rhel5.5 /etc/multipath.conf Install this patched scsi_dh_alua driver module. i386 cd /usr/src/redhat/RPM/i386 rpm -ivh scsi_dh_alua_VTrak-2-1.i386.rpm x86_64 cd /usr/src/redhat/RPM/x86_64 rpm -ivh scsi_dh_alua_VTrak-2-1.x86_64.rpm 4. Check the multipath configuration. Multipath -ll (multipath -v4)
396
Kernel with XEN or PAE support

To support ALUA within RHEL 5.5 using kernel with XEN or PAE support: 1. 2. 3. 4. Install RHEL 5.5. When the CD is chosen for installation, immediately type linux mpath. Copy the PROMISE-supplied multipath.conf file to the /etc directory. cp multipath.conf.alua-rhel5.5 /etc/multipath.conf Install this patched alua_dh_scsi driver module. rpm -ivh scsi_dh_alua_VTrak-2-1.src.rpm Make your own rpm. cd /usr/src/redhat/SPEC rpmbuild -ba scsi_dh_alau.spec 5. 6. Determine your system architecture, x86_64 or i386. uname -a Install the appropriate scsi_dh_alua driver module. i386 cd /usr/src/redhat/RPM/i386 rpm -ivh scsi_dh_alua_VTrak-2-1.i386.rpm x86_64 cd /usr/src/redhat/RPM/x86_64 rpm -ivh scsi_dh_alua_VTrak-2-1.x86_64.rpm 7. Check the multipath configuration. Multipath -ll (multipath -v4)
SuSE Linux SLES 10 SP3

To support ALUA within SLES10 SP3: 1. 2. Determine your system architecture, i586 or x86_64. #> uname -a Do one of the following actions: Remove the currently installed multipath tool. rpm -ev multipath-tools Install the appropriate new multipath-tool RPM package. i586 rpm -ivh multipath-tools-0.4.7-34.50.10.ass.fix.i586.rpm x86_64 rpm -ivh multipath-tools-0.4.7-34.50.10.ass.fix.x86_64.rpm
397
Force install the appropriate new multipath-tool RPM package. i586 #> rpm -ivh -force multipath-tools-0.4.7-34.50.10.ass.fix.i586.rpm x86_64 #> rpm -ivh -force multipath-tools-0.4.7-34.50.10.ass.fix.x86_64.rpm
3. 4.
Copy the PROMISE-supplied multipath.conf file to the /etc directory. #> cp multipath.conf-vtrak-alua-sles10-sp3 /etc multipath.conf Check the multipath configuration. chkconfig multipathd on chkconfig multipathd (shows the status of multipathd) chkconfig boot.multipath on chkconfig boot.multipath (shows the status of boot.multipath)
5. 6.
Reboot the VTrak. Check the multipath configuration. Multipath -ll (multipath -v4)
SuSE Linux SLES 11

To support ALUA within SLES 11: 1. 2. Determine your system architecture, i586 or x86_64. #> uname -a Install the appropriate path priority tool library. 3. 4. i586 #> rpm -ivh multipath-promise-suse11-0.4.8-1.i586.rpm x86_64 #> rpm -ivh multipath-promise-suse11-0.4.8-1.x86_64.rpm Copy the PROMISE-supplied multipath.conf file to the /etc directory. #> cp multipath.conf-vtrak-alua-sles11 /etc multipath.conf Check the multipath configuration. chkconfig multipathd on chkconfig multipathd (shows the status of multipathd) 5. 6. Reboot the VTrak. Check the multipath configuration. Multipath -ll (multipath -v4)
398
SuSE Linux SLES 11 SP1

Not updated with Novell SP1 patches
If you did NOT update with Novell SLES 11 SP1 patches: 1. 2. Determine your system architecture, i586 or x86_64. #> uname -a Install the appropriate patched scsi_dh_alua.ko device handler. 3. 4. i586 #> rpm -ivh --force scsi_dh_alua_sles11sp1-2-1.i586.rpm x86_64 #> rpm -ivh --force scsi_dh_alua_sles11sp1-2-1.x86_64.rpm Copy the PROMISE-supplied multipath.conf file to the /etc directory. #> cp multipath.conf.alua-sles11sp1 /etc multipath.conf Check the multipath configuration. chkconfig multipathd on chkconfig multipathd (shows the status of multipathd) 5. 6. Reboot the VTrak. Check the multipath configuration. Multipath -ll (multipath -v4)
Updated with Novell SP1 patches

If you updated with Novell SLES 11 SP1 patches: 1. 2. Copy the PROMISE-supplied multipath.conf file to the /etc directory. #> cp multipath.conf.alua-sles11sp1 /etc multipath.conf Check the multipath configuration. chkconfig multipathd on chkconfig multipathd (shows the status of multipathd) 3. 4. Reboot the VTrak. Check the multipath configuration. Multipath -ll (multipath -v4)
Fibre Channel HBA to VTrak

If you plan to use connect a Fibre Channel HBA card to VTrak RAID subsystem, you must change the remote port (rport) configuration. 1. 2. Change the dev_loss_tmo value as large as possible. Example: 0x7fffffff. Change the fast_io_fail_tmo value as 30.
399
RPM Packages and Documents for Linux MPIO

PROMISE provides RPM packages and multipath.conf files for Linux on the support: http://www.promise.com/support/. A PROMISE Linux package contains: package folder RPM packages for the Linux OS multipath-conf folder ALUA folder Configuration file and instructions for ALUA, if supported normal folder Configuration file for general multipathing Important Please read the How to Configure document in the ALUA folder for the latest information before beginning your setup. The table below lists the content of each PROMISE Linux package: Package SLES10-SP2 SLES10-SP3 Folder normal package Contents multipath.conf-vtrak-normal-sles10-sp2 multipath-tools-0.4.7-34.50.10.ass.fix.i586.rpm multipath-tools-0.4.734.50.10.ass.fix.x86_64.rpm multipath-conf-vtrak-alua-sles10-sp3 How to Configure MPIO SLES10 SP3.doc multipath-conf-vtrak-normal-sles10-sp3 multipath-promise-suse11-0.4.8-i586.rpm multipath-promise-suse11-0.4.8-x86_64.rpm multipath-conf-vtrak-alua-sles11 How to Configure MPIO SLES 11.doc multipath-conf-vtrak-normal-sles11
ALUA normal SLES11 packages ALUA normal
400
RPM Packages and Documents for Linux MPIO
Package SLES11-SP1
Folder packages
Contents scsi_dh_alua_sles11sp1-2-1.i586.rpm scsi_dh_alua_sles11sp1-2-1.x86_64.rpm scsi_dh_alua_sles11sp1-2-1.src.rpm multipath.conf.alua-sles11sp1 How to Configure MPIO SLES 11sp1.doc multipath.conf-vtrak-normal-sles11sp1 How to Configure MPIO SLES 11sp1.doc multipath.conf-vtrak-normal-rhel5-3 scsi_dh_alua_Vtrak-1-1.i386.rpm scsi_dh_alua_Vtrak-1-1.x86_64.rpm scsi_dh_alua_Vtrak-1-1.src.rpm multipath.conf-vtrak-alua-rhel5-4 How to Configure MPIO RHEL 5.4.doc multipath.conf-vtrak-normal-rhel5-4 scsi_dh_alua_Vtrak-2-1.i386.rpm scsi_dh_alua_Vtrak-2-1.x86_64.rpm scsi_dh_alua_Vtrak-2-1.src.rpm multipath.conf.alua-rhel5.5 How to Configure MPIO RHEL 5.5.doc multipath.conf-normal-rhel5.5
ALUA normal RHEL-5.3 RHEL-5.4 normal package
ALUA normal RHEL-5.5 packages
ALUA normal
401
Linux MPIO: Known Issues

Issue 1 2 3 OS SLES 11 GMC SLES 11 GMC RHEL 5.4 Description OS multipath with SAS interface makes kernel panic. OS sets default rports dev_loss_tmo value at 10 seconds resulting in loss of the path during failover/failback. With FC switch, HBA driver (such as Emulex 4g, QLogic 8g) sets rports dev_loss_tmo value too small, resulting in loss of the path during failover/failback. To fix this problem, increase the value to 60 seconds. 4 SLES 10 SP3 With FC switch, HBA driver (such as Emulex 4g, QLogic 8g) sets rports dev_loss_tmo value too small, resulting in loss of the path during failover/failback. To fix this problem, increase the value to 60 seconds. 5 SLES 11 SP1 With a FC HBA, set rports dev_loss_tmo as large as possible, such as 0x7fffffff. Set fast_io_failure_tmo to 30 seconds. Without these settings, the system does not recognize device or the systems hang during boot and failover/failback. Download and update the latest SLES11 SP1 patches from Novell. Without these patches, the system hangs during failover/failback.
With a Fibre Channel switch, a dev_loss_tmo value set too small can result in loss of the path during failover/failback. Linux maintains the rports dev_loss_tmo value in the /sys/class/ fc_remote_port/rport-xxxx/dev_loss_tmo file. The Fibre Channel HBA driver sets this value at loading time. To change the dev_loss_tmo value to the recommended 60 seconds, during runtime type the echo command: echo 60 > /sys/class/fc_remote_port/rpot-1:0:0/dev_loss_tmo
402
Sample multipath.conf File
Sample multipath.conf File

Below is a complete multipath.conf file for VTrak. If you have no other multipath devices on your Host, you can use this multipath.conf file as shown. If you have other multipath devices, add these settings to your existing multipath.conf file. ## ## This is a template multipath-tools configuration file ## for the Promise VTrak subsystem ## defaults { user_friendly_names yes } blacklist { devnode "^sda$" devnode "^(ram|raw|loop|fd|md|dm-|sr|scd|st)[0-9]*" devnode "^hd[a-z][[0-9]*]" devnode "^cciss!c[0-9]d[0-9]*[p[0-9]*]" } devices { device { vendor "Promise" product "VTrak" path_grouping_policy multibus getuid_callout "/sbin/scsi_id -g -u -s /block/%n" path_checker readsector0 path_selector "round-robin 0" hardware_handler "0" failback immediate rr_weight uniform rr_min_io 100 no_path_retry 20 features "1 queue_if_no_path" product_blacklist "VTrak V-LUN" } }
403
404
Index
A
about this manual 1 adaptive writeback cache 290 add Fibre Channel initiator 152 LUN map 213 alarm cancel 239 sounds 293 alias controller 70, 167 disk array 128, 185 logical drive 136 physical drive 117, 178 Auto Fix 138, 198 auto rebuild, enable 96, 208 cache adaptive writeback 290 forced read ahead 290 read 289 reported events 328 settings 70, 167 write thru 290 writeback 289 cancel alarm 239 capacity coercion explained 291 setting 71, 167 change RAID level 139, 275 check table, logical drive 134, 197 CIM service 107, 226 settings 108, 225 clear PFA condition 120, 178 stale condition 120, 178 statistics 63, 231 CLI 36 log in 158 log out 160 serial connection 156 CLU exit 159 log in 158 online help 159 problem reporting 300 serial connection 36, 156 SSH connection 157 Telnet connection 157 Command Line Interface, see CLI Command Line Utility, see CLU configuration script export 66 import 66
B
background activity management
90, 208
battery reconditioning 74, 99, 174 replace 252 reported events 328 view information 73, 173 BBU, reported events 328 blade server, reported events 328 boot the subsystem 235 browser, does not connect 325 buzzer settings 75, 239 sounding 293
C
cable RJ11-to-DB9 31, 156 UPS control 31
405
connection data 2330 Fibre Channel 2330 management 2330 power 33 serial 31 connector RJ11 31 RJ45 323 controller alias 70, 167 dual controllers and SATA drive 361 heartbeat LED 34, 295 information 69, 166 locate 72, 168 maintenance mode 312 management port settings 200 N/A status 166, 312 power saving 70, 168 replace 254, 256 reported events 329331 settings 70, 167 statistics 71 unsaved data in cache 314 CRC, reported events 331 create disk array 123, 180 LUN map 146 spare drive 142, 193 user 217
delete disk array 184 Fibre Channel initiator 152 initiator 213 logical drive 136, 192 LUN map 147 SAS initiator 154 spare drive 143, 195 user 220 DHCP server changed IP address
325
dirty cache LED 297 Discovery tab 58 disk array advanced creation 47,
125,
183 alias 128, 185

automatic creation
45, 123,
181 create 123, 180

create manually 122 critical 317 delete 127, 184 express creation 46, 124, 182 incomplete 320 information 121, 185 locate 128, 190 Media Patrol 129 migrate 187 operational status 185 PDM 129, 188 rebuild 130 rebuilding 187 reported events 331 settings 128, 184, 186 transport 130, 187 disk status LED 35, 296 display language, choose 53 DMA mode, SATA drives 115, 176 DNS server, UPS unit 81, 215
D
DAS, Fibre Channel 25 data connections 2330 date and time, subsystem
37, 40,
163
dedicated spare drive 193, 283 default settings, restore 232 definitions, FC properties 204
406
Index
drive interface, reported events
331332
drive slot numbering 19
E
edit LUN map 147, 213 email service setting 221 user setting 219 enable LUN masking 148, 212 enclosure information 77, 170 locate 174 reported events 332 settings 77, 171 temperature 170 topology 76, 174 view 76, 170 voltage 79, 170, 173 event log clear 210, 211 NVRAM 210, 300 reported events 332 runtime 210, 300 event notification response 327344 severity 228 expand logical drive 139, 187 export configuration script 66
Fibre Channel, cont. initiators on the fabric 151 JBOD expansion 27 logged-in devices 151, 202 no single point of failure 28 node information 149, 202 port information 149 port settings 150, 202 port statistics 151, 204 reported events 332 SAN 23 SAN No Single Point of Failure
28
SFPs 151 switch 23, 28 topology 150 firmware update CLU 244, 246 reported event 333 WebPAM PROe 241 firmware version 230 flash image information 72, 230 force online/offline 178 forced read ahead cache 290 forced unlock 163 FRU status LED 33, 295, 297 VPD 78, 171
G F
Fibre Channel connections 2330, 323 DAS 25 definitions 204 HBA card 23, 25, 28 initiator 205 initiator, add 152 initiator, delete 152 global spare drive
193, 283 23, 25,
H
HBA card, Fibre Channel
28
Head Unit 76, 175 heartbeat LED 34, 295 host interface, reported events 333
407
I
import configuration script 66 information controller 69, 166 disk array 185 enclosure 77, 170 Fibre Channel node 149, 202 flash image 72, 230 FRU VPD 78, 171 logical drive statistics 133 physical drive 114, 177 SAS ports 153, 206 spare drives 141 subsystem 59 UPS unit 82, 216 initialization logical drive 137, 197 settings 95, 209 initiator delete 213 Fibre Channel 205 Fibre Channel, add 152, 205,
IP address, cont. virtual management port
37, 40, 41, 42, 51, 200, 323, 325
J
JBOD expansion 27, 28, 175 JBOD, reported events 335
L
language, choose 53 LED controller 34, 295 controller status 169 dirty cache 169, 297, 314 disk status 35, 296 FRU status 33, 295, 297 heartbeat 34, 295 logical drive 33, 295 power 33, 295 power/activity 35, 296 red or amber 295 list Fibre Channel initiators 151 Fibre Channel logged-in devices 151 Fibre Channel SFPs 151 initiators 148 logical drives 132, 196 LUN maps 146 SAS port initiators 154 spare drives 141 locate controller 72, 168 disk array 128, 190 enclosure 174 logical drive 137, 199 physical drive 179 power supply 170, 172 spare drive 143
408
212
Fibre Channel, delete 152 list 148 reported events 334 SAS 154, 207 SAS, add 207, 212 installing physical drives 19 interface, WebPAM PROe 55 Internet access, WebPAM PROe
49
IP address defaults 37 DHCP or static 36 DHCP server changed 325 email server 221 maintenance mode 38, 201 Netsend recipient 227 UPS unit 81, 215
Index
lock releasing 60, 163 renewing 60, 163 setting 60, 163 subsystem 60, 163 view status 60, 163 log in CLI 36, 313, 314, 325 WebPAM PROe 42, 51 log out CLI 160 WebPAM PROe 49, 57 logged-in devices, Fibre Channel
M
MAC address 37 maintenance mode
38, 40, 200,
312
management connections 2330 port, physical 37 port, virtual 37 manual rebuild 131 Media Patrol enable 186 reported events 336 run 162 running 129 settings 94 medium error threshold, physical drives 176 migrate disk array 187 logical drive 139 reported events 340341 settings 97 mixing SATA and SAS drives 182
202
logical drive check tables 134, 197 create manually 135, 190 delete 136, 192 expand 139 information 132, 196 initialize 137, 197 LED 33, 295 list 132, 196 locate 137, 199 migrate 139, 187 Redundancy Check 138, 198 reported events 335336 settings 136, 197 statistics 133, 196 synchronization 98, 209 LUN map, add 146, 213 map, delete 147 map, edit 147, 213 map, view 146, 212 masking & mapping 146 masking, enable 148, 212
N
Netsend recipients 227 requirements 227 service 227 settings 227 network interface card (NIC) 23, 25, 28 switch 23, 25, 28 no single point of failure 28 node, Fibre Channel 149, 202 NTP settings 164 synchronizing 165 numbering drive slots 19 NVRAM event log 210, 300
409
O
online capacity expansion defined 275 reported events 336, 337 online help, CLU 159 operational status, disk array 185 orphan watermark 166
port Fibre Channel 149 SAS data IN 27, 28 SAS data OUT 27, 28 SAS expansion 27, 28 port settings Fibre Channel 150, 202 SAS 153, 206 port statistics Fibre Channel 151, 204 SAS 153, 207 power connection 33 LED 33, 295 power cycle the subsystem 326 power management, enable 128,
P
parity error, reported events 337 password CLI/CLU 36 CLU 219 reset Administrator to factory default 258 WebPAM PROe 42, 52 Pause On Error 198 PDM enable 186 reported events 337 running 129, 188 settings 97 triggers 209 physical drive alias 178 capacity coercion 71 configuration status 177 DMA mode 176 force offline or online 178 global settings 176 information 114, 177 list 176 locate 179 medium error threshold 176 operational status 177 reported events 337339 settings 178 stale and PFA condition 178 statistics 177 physical drives, installing 19
410
186
power saving 70, 168, 291 power supply locate 170, 172 replace 250 reported events 339340 status 78, 170, 171 power supply fan reported events
340
power/activity LED 35, 296 preferred controller ID, explained
281
privileges CLU user 218 WebPAM PROe user problem reporting CLU 300 USB Support 307 WebPAM PROe 303
84
R
rackmount E330f 16 E630f 15 E830f 15
Index
RAID levels, changing
139, 187,
275
read cache 289 rebuild disk array 96, 130, 187 manual 131 reported events 341 settings 96 rebuild disk array 96 recipients, Netsend 227 recondition a battery 74, 99, 174 Redundancy Check 198 logical drive 138 reported events 341342 settings 94 releasing lock 60, 163 renewing lock 60, 163 replace battery 252 controller 254, 256 power supply 250 reported events 327344 battery 328 BBU 328 blade server 328 cache 328 controller 329331 CRC 331 disk array 331 drive interface 331332 enclosure 332 event log 332 Fibre Channel 332 firmware update 333 host interface 333 initiator 334 JBOD 335 logical drive 335336 Media Patrol 336 online capacity expansion 336,
reported events, cont. parity error 337 PDM 337 physical drive 337339 power supply 339340 power supply fan 340 RAID level migration 340341 rebuild 341 Redundancy Check 341342 resource not available 342 SCSI 342 SEP 342 SMART error 342 Spare Check 342 spare drive 342 stripe level migration 343 subsystem 343 synchronization 343 transition 344 unknown 344 zoning 344 requirements for spare drives 283 resource not available reported event 342 restart the subsystem 67, 237 restore default settings 61, 232 returning product for repair 356 revertible spare drive 193, 283 RJ11-to-DB9 cable 13, 31, 156 RJ45 connector 323 runtime event log 210, 300
S
SAN Fibre Channel 23 no single point of failure SAS connections 324 data IN port 27, 28 data OUT port 27, 28 expansion port 27, 28
411
28
337
SAS, cont. initiator 207 initiator, delete 154 port information 153, 206 port initiators 154 port settings 153, 206 port statistics 153, 207 SAS-to-SATA adapter 20, 361 SATA and SAS drives, mixing 182 SCSI, reported events 342 SEP, reported events 342 serial connection cable 31 setting up 36, 156 service report, save 63 setting capacity coercion 167 setting the lock 60, 163 settings background activities 90, 208 buzzer 75, 239 cache 70, 167, 290 CIM 108, 225 controller 70, 167 controller management port
200
disk array 128, 184, 186 email 221 enclosure 77, 171 Fibre Channel port 150 Fibre Channel ports 202 initialization 95, 209 logical drive 136, 197 Media Patrol 94 migration 97 Netsend 227 NTP 164 PDM 97 physical drive 178 physical drives 176 power saving 70, 168
412
settings, cont. rebuild 96 Redundancy Check 94 restore default 61, 232 SAS ports 153 SLP 222 SNMP 224 spare drive 143, 194 SSH 223 subsystem 60, 162 synchronization 98 Telnet 223 temperature 77, 171 transition 98 UPS units 81, 215 user 218, 219 virtual management port 200 Web Server 222 severity of events 228 SFP information 203 shut down the subsystem 67, 233 SLP service 222 settings 222 SMART error 342 setting 167 SNMP service 224 settings 224 trap sinks 224 Spare Check reported events 342 run 144, 194 spare drive create 193 create manually 142 dedicated 283 delete 143, 195 global 283 information 141
Index
spare drive, cont. list 141 locate 143 reported events 342 requirements 283 revertible 283 settings 143, 194 Spare Check 144, 194 transition 144, 284 SSH connection 157 service 223 settings 223 statistics clear 231 controller 71, 166 Fibre Channel 204 Fibre Channel port 151 logical drive 196 physical drive 177 SAS 207 SAS port 153 status controller 166 physical drive 177 power supply 78, 170, 171 subsystem lock 60, 163 storage 23 storage network 58 stripe level migration reported event 343 subsystem cascading 175 date and time 37, 40, 163 information 59 list 58 lock 60, 163 maintenance 241 management port settings 200 power cycle 326
subsystem, cont. reported events 343 restart 67, 237 settings 60, 162 shut down 67 shutdown 233 startup after shutdown 235 synchronization logical drive 98 reported events 343 settings 98 synchronizing NTP 165
T
Technical Support, contact 351 Telnet connection 157 service 223 settings 223 temperature enclosure 170 settings 77, 171 thresholds 79, 172 terminal emulation program 36,
156
topology enclosure 76, 174 Fibre Channel 150 transition automatic 287 explained 284 manual 287 reported event 344 settings 98 spare drive 144 transport disk array 130, trap sinks 224
187
U
unknown, reported event
413
344
UPS control cable 31 information 82, 216 list of units 80, 214 serial connection 31 settings 81, 215 USB Support firmware update 246 problem reporting 307 user create 217 delete 220 enable/disable 218 password, change 219 privileges 218 settings 218, 219 view 217 username and password CLI/CLU 36 WebPAM PROe 42, 52
view, cont. scheduled activities 208 SFP information 203 spare drives 193 storage network 58 subsystem information 59 users 217 virtual management port 37, 200,
325
voltage, enclosure 79, 170, VTrak beeping 293 rackmount E330f 16 rackmount E630f 15 rackmount E830f 15 warranty 354
173
W
warranty, VTrak 354 watermark, orphan 166 Web Server service 222 settings 222 WebPAM PROe access over the Internet 49 Discovery tab 58 interface 55 language 53 log in 42, 51 log out 49, 57 no browser connection 325 problem reporting 303 username and password 42,
V
view background activities 208 battery information 73 controllers 166 disk arrays 180 enclosure 76, 170 Fibre Channel logged in devices 202 Fibre Channel port settings
202
Fibre Channel port statistics
204
flash image 72 list of logical drives 132, 196 lock status 60, 163 logical drive information 132 LUN map 212 physical drives 176
414
52
wizard 123 write thru cache 290 writeback cache 289
Z
zoning, reported events
344

VTrak E-Class SBB PM v1.0

Uploaded by

Copyright:

Available Formats

VTrak E-Class SBB PM v1.0

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

VTrak E-Class SBB PM v1.0

Uploaded by

Copyright:

Available Formats

VTRAK

E830f, E630f, E330f

VTrak E-Class Product Manual

Important data protection information

VTrak E-Class Product Manual

VTrak E-Class Product Manual

VTrak E-Class Product Manual

VTrak E-Class Product Manual

VTrak E-Class Product Manual

VTrak E-Class Product Manual

VTrak E-Class Product Manual

VTrak E-Class Product Manual

VTrak E-Class Product Manual

VTrak E-Class Product Manual

About This Manual

VTrak E-Class Product Manual

Service and Support

Figure 1. VTrak E830f front view Drive Carrier LEDs

Power and Status LEDs

VTrak E-Class Product Manual

Figure 2. VTrak E630f front view Drive Carrier LEDs

Power and Status LEDs

Drive Carriers Figure 4. VTrak E830f back view RAID Controller 1

Power and Status LEDs

Figure 5. VTrak E630f back view RAID Controller 1 RAID Controller 2

Power Supply 1 Figure 6. VTrak E330f back view RAID Controller 1

VTrak E-Class Product Manual

External I/O Ports

RAID Stripe Size Support

Hot Spare Drives

Maximum LUNs Supported

Advanced Storage Features

VTrak E-Class Product Manual

Power Conversion Efficiency

Noise, Shock, and Vibration

VTrak E-Class Product Manual

Safety and Environmental

Safety and Environmental

VTrak E-Class Product Manual

Warranty and Support

Unpacking the VTrak

VTrak E-Class Product Manual

Mounting VTrak in a Rack

Mounting VTrak in a Rack

Mounting VTrak E830f/s and E630f/s in a Rack

Handles mount outside the rack post

Mounting rails (included) mount outside the rack post

VTrak E-Class Product Manual

Support for subsystem

Rail attaching screws (not included)

Mounting VTrak E330f/s in a Rack

Handles mount outside the rack post

Mounting rails (included) mount outside the rack post

Mounting VTrak in a Rack

Attaching the Sliding Plates

Screws (6 each side)

Installing the Subsystem into the Rack

VTrak E-Class Product Manual

Rail attaching screw (not included) Inside of post