VTrak M610i - Server Promise Technology - Free user manual and instructions

Product Type	RAID Storage Subsystem
Form Factor	2U Rackmount
Supported Drives	Up to 16 SATA/SAS hard drives
RAID Levels	0, 1, 5, 6, 10, 50, 60
Processor	Intel IOP348 Dual Core 1.2 GHz
Cache Memory	512 MB DDR2 ECC (upgradable to 2 GB)
Host Interface	2 x Mini-SAS SFF-8088 (4-lane)
Management Interface	1 x RJ-45 10/100/1000 Ethernet
Dimensions (W x D x H)	19.0 x 25.0 x 3.5 inches (48.3 x 63.5 x 8.9 cm)
Weight	36 lbs (16.3 kg) without drives
Power Supply	Dual redundant 500W hot-swappable
Input Voltage	100-240 VAC, 50-60 Hz
Cooling	3 x hot-swappable fans
Operating Temperature	41°F to 95°F (5°C to 35°C)
Storage Temperature	-40°F to 158°F (-40°C to 70°C)
Operating Humidity	20% to 80% non-condensing
Management Software	WebPAM PRO (Web-based RAID management)
Supported RAID Features	Online capacity expansion, RAID level migration, hot spare
LED Indicators	Power, fan, temperature, disk activity, link/activity per host port
Safety Certifications	UL, CE, FCC, VCCI

Frequently Asked Questions - VTrak M610i Promise Technology

How do I initialize the VTrak M610i for first use?

Connect the power and network cables, then access the management interface via a web browser using the default IP or DHCP-assigned address. Use WebPAM PRO to create a logical drive and initialize it.

What RAID levels are supported by the VTrak M610i?

The VTrak M610i supports RAID levels 0, 1, 5, 6, 10, 50, and 60. It also supports online capacity expansion and RAID level migration.

How can I replace a failed hard drive?

The system supports hot-swappable drives. Simply remove the failed drive and insert a new one of the same or larger capacity. The RAID will automatically rebuild if a hot spare is configured or you can manually assign the drive as a replacement.

What should I do if the VTrak M610i does not power on?

First, check that both power supplies are connected and the power cables are secure. If using a single PSU, ensure it's plugged into a working outlet. Also check the front panel power button and LED indicators.

How do I access the web-based management interface?

Connect a computer to the same network as the VTrak M610i's management port. Open a web browser and enter the IP address of the unit. The default login credentials are usually admin/password (check the manual).

What is the maximum storage capacity supported?

Using 16 large-capacity drives (e.g., 18TB each), the raw capacity can reach up to 288 TB before RAID overhead. However, check the compatibility list for supported drive models.

Can I expand the cache memory?

Yes, the cache memory is upgradable. The standard is 512 MB DDR2 ECC, and it can be expanded up to 2 GB using compatible memory modules.

How do I update the firmware on the VTrak M610i?

Download the latest firmware from Promise Technology's support site. Log into WebPAM PRO, go to Maintenance > Firmware Update, and upload the firmware file. The system will reboot automatically.

What kind of disks are compatible?

The VTrak M610i supports both SATA and SAS hard drives of standard form factor (3.5-inch). For optimal performance, use enterprise-grade drives. Always consult the compatibility list on Promise's website.

How do I configure email alerts?

In WebPAM PRO, navigate to Settings > Notification. Enable email alerts and enter the SMTP server details, recipient email addresses, and test the configuration. You can set alerts for events like disk failure, temperature warnings, etc.

USER MANUAL VTrak M610i Promise Technology

VTRAK M610i, M310i, M210i Product Manual

Version 1.0

Copyright

© 2007 Promise Technology, Inc. All Rights Reserved.

Copyright by Promise Technology, Inc. (Promise Technology). No part of this manual may be reproduced or transmitted in any form without the expressed, written permission of Promise Technology.

Trademarks

Promise, and the Promise logo are registered in U.S. Patent and Trademark Office. All other product names mentioned herein may be trademarks or registered trademarks of their respective companies.

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 manual, 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 the Product Manual 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.

Contents

Chapter 1: Introduction to VTrak .....1

About This Manual....1

VTrak Overview 2

Architectural Description ....3

Features and Benefits 4

Highlights 4

Subsystem and Controller Features ....5

Operational Features 5

Management 6

Specifications 6

Warranty and Support ....7

FCC Statement 7

Chapter 2: VTrak Installation .....9

Unpacking the VTrak 9

Mounting VTrak M610i in a Rack 10

Mounting VTrak M310i or M210i in a Rack .....12

Installing Disk Drives 15

Drive Slot Numbering 15

Installing Disk Drives 16

Making Management and Data Connections .....18

Configuring an IP Storage Area Network .....18

Configuring Direct Attached Storage .....19

Making Serial Cable Connections .....20

Connecting the Power 21

Chapter 3: VTrak Setup .....23

Setting up the Serial Connection .....23

Choosing DHCP or a Static IP Address .....24

Viewing MAC and IP Addresses in the CLI .....24

Viewing MAC and IP Addresses in the CLU .....24

Setting up VTrak with the CLI 25

Setting up VTrak with the CLU .....27

Creating Disk Arrays with WebPAM PROe .....29

Logging into WebPAM PROe .....29

Selecting a Language 31

Creating a Disk Array ....31

Logging out of WebPAM PROe 35

Using WebPAM PROe over the Internet .....36

Obtaining a Security Certificate ....36

Chapter 4: Management with WebPAM PROe .....37

Logging into WebPAM PROe 38

Selecting a Language .....40

Perusing the Interface 41

Using the Header 42

Using Tree View 43

Using Management View ....44

Viewing the Event Frame 44

Logging out of WebPAM PROe .....45

Working with the Storage Network 46

Viewing Other Subsytems ....46

Updating the List of Subsystems 46

Logging into a Subsystem .....46

Hiding the Other Subsystems .....46

Working with Subsystems 47

Viewing Subsystem Information .....47

Setting an Alias for the Subsystem .....47

Setting Subsystem Date and Time 48

Viewing the Runtime Event Log ....48

Saving the Runtime Event Log 49

Clearing the Runtime Event Log 49

Viewing NVRAM Events 49

Saving NVRAM Events 50

Clearing NVRAM Events ....50

Viewing Current Background Activities 50

Making Background Activity Settings .....51

Running Background Activities .....52

Running Media Patrol 52

Running PDM 52

Viewing Scheduled Activities 53

Scheduling an Activity ....53

Deleting a Scheduled Activity .....54

Viewing Lock Status ....54

Setting the Lock 55

Renewing the Lock 55

Releasing the Lock 55

Managing Users 57

Viewing User Information 57

Making User Settings 57

Making Your Own User Settings ....58

Setting-up User Event Subscriptions .....58

Chapter 4: Management with WebPAM PROe, cont.

Managing Users, cont.

Changing Another User's Password .59

Changing Your Own Password ....59

Creating a User 60

Deleting a User 61

Viewing User Sessions 61

Logging out Other Users ....61

Managing the Network Connection ....62

Making Subsystem Management Port Settings .....62

Making iSCSI Data Port Settings 62

Viewing VLAN Entries 63

Creating a VLAN Entry .63

Changing a VLAN Entry .64

Deleting a VLAN Entry 65

Viewing Link Aggregation Entries 65

Creating a Link Aggregation Entry .65

Changing a Link Aggregation Entry 66

Deleting a Link Aggregation Entry .66

Managing iSCSI Connections .....67

Viewing Node Information ....67

Making Node Settings .68

Viewing Target Port Information 69

Viewing Data Port Statistics 69

Viewing Portal Information 70

Viewing Session Information ....70

Viewing iSNS Information 70

Making iSNS Settings 71

Viewing CHAPs....71

Adding CHAPs 71

Editing CHAPs 72

Deleting CHAPs 72

Pinging iSCSI Connections .....72

Managing Storage Services 73

Adding an Initiator 73

Deleting an Initiator 73

Viewing a LUN Map 74

Enabling LUN Masking 74

Adding a LUN Map 74

Chapter 4: Management with WebPAM PROe, cont.

Managing Software Services ....76

Making Email Settings 76

Making SLP Settings ....77

Making Web Server Settings 77

Making Telnet Settings 79

Making SNMP Settings 79

Making CIM Settings ....81

Making Netsend Settings 82

Exporting the User Database 84

Importing a User Database ....85

Updating the Firmware 86

Restoring Factory Defaults 87

Clearing Statistics 88

Shutting Down the Subsystem 89

Monitoring the Shutdown 89

Restarting the Subsystem 90

Monitoring the Restart .90

Managing Controllers 91

Viewing the Controller 91

Locating a Controller....91

Viewing Controller Information 92

Viewing Controller Statistics 93

Making Controller Settings .93

Managing Enclosures 95

Viewing the Enclosures .....95

Locating an Enclosure 95

Viewing Enclosure Information .....96

Making Enclosure Settings 97

Viewing FRU VPD Information .....97

Checking the Batteries 97

Reconditioning a Battery .98

Silencing the Buzzer 99

Making Buzzer Settings 99

Testing the Buzzer 99

Managing Physical Drives 100

Viewing a List of Physical Drives 100

Identifying a Physical Drive ....100

Making Global Physical Drive Settings 100

Viewing Physical Drive Information .....101

Viewing Physical Drive Statistics 102

Chapter 4: Management with WebPAM PROe, cont.

Managing Physical Drives, cont.

Making Physical Drive Settings .....102

Clearing Stale and PFA Conditions .....102

Forcing a Physical Drive Offline or Online .....103

Managing Disk Arrays ....105

Viewing Disk Arrays 105

Creating a Disk Array ....105

Creating a Disk Array – Automatic .....106

Creating a Disk Array – Express .....106

Creating a Disk Array – Advanced .....108

Deleting a Disk Array 109

Locating a Disk Array 110

Viewing Disk Array Information .....110

Making Disk Array Settings .....111

Creating a Logical Drive ....111

Deleting a Logical Drive ....113

Migrating a Disk Array ....113

Rebuilding a Disk Array 114

Running Media Patrol on a Disk Array 115

Running PDM on a Disk Array 116

Transitioning a Disk Array 116

Preparing a Disk Array for Transport .....117

Managing Logical Drives 118

Viewing Information for All Logical Drives .....118

Locating a Logical Drive ....119

Viewing Logical Drive Information .....119

Viewing Logical Drive Statistics 120

Making Logical Drive Settings .....120

Initializing a Logical Drive ....121

Running Redundancy Check 122

Viewing the Logical Drive Check Table .....123

Making Logical Drive LUN Settings 123

Managing Spare Drives 125

Viewing a List of Spare Drives .....125

Locating a Spare Drive ....125

Creating a Spare Drive ....126

Deleting Spare Drive ....127

Making Spare Drive Settings 127

Running Spare Check 128

Chapter 4: Management with WebPAM PROe, cont.

Working with the Logical Drive Summary .....129

Viewing a List of All Logical Drives .....129

Viewing Individual Logical Drive Information .....129

Chapter 5: Management with the CLU .....131

Logging into the CLU 132

Making a Serial Connection ....132

Making a Telnet Connection .....132

Accessing Online Help 134

Logging out of the CLU .....134

Running Quick Setup ....135

Managing the Subsystem 136

Setting an Alias for the Subsystem .....136

Running Media Patrol 136

Locking or Unlocking the Subsystem .....136

Setting Subsystem Date and Time ....137

Managing the Controllers ....138

Viewing Controller Information 138

Making Controller Settings 138

Locating the Controller ....139

Managing the Enclosure ....140

Viewing Enclosure Information .....140

Viewing Power Supply Status 140

Locating a Power Supply 140

Viewing Blower Status 141

Viewing Voltage Sensor Status .....141

Viewing Temperature Sensor Status 141

Setting Temperature Thresholds 141

Checking the Batteries .....142

Reconditioning a Battery ....142

Locating an Enclosure 143

Managing Physical Drives ....144

Viewing a List of Physical Drives .....144

Making Global Physical Drive Settings .....144

Setting an Alias 145

Viewing Advanced Information .....145

Viewing Physical Drive Statistics .....145

Clearing Stale and PFA Conditions .....145

Forcing a Physical Drive Offline or Online .....146

Locating a Physical Drive ....146

Chapter 5: Management with the CLU, cont.

Managing Disk Arrays ....147

Creating a Disk Array ....147

Creating a Disk Array – Automatic .....148

Creating a Disk Array – Express .....149

Creating a Disk Array – Advanced 150

Deleting a Disk Array 151

Viewing Disk Array Information .....152

Setting an Alias for a Disk Array ....152

Accepting an Incomplete Array .....153

Enabling Media Patrol on a Disk Array 153

Enabling PDM on a Disk Array ....153

Preparing the Disk Array for Transport .....153

Rebuilding a Disk Array 154

Migrating a Disk Array ....154

Running PDM 155

Running Transition on a Disk Array 155

Locating a Disk Array ....156

Creating a Logical Drive ....156

Deleting a Logical Drive 157

Managing Logical Drives ....158

Viewing Logical Drive Information .....158

Setting an Alias for a Logical Drive .....159

Setting Write Cache Policy 159

Setting Read Cache Policy ....159

Initializing a Logical Drive .....160

Running Redundancy Check 160

Locating a Logical Drive ....161

Managing the Network Connection ....162

Making Management Port Settings .....162

Making iSCSI Data Port Settings 163

Viewing VLAN Entries .....164

Creating a VLAN Entry 164

Changing a VLAN Entry 165

Deleting a VLAN Entry 165

Viewing Link Aggregation Entries .....165

Creating a Link Aggregation Entry 166

Changing a Link Aggregation Entry 166

Deleting a Link Aggregation Entry 166

Chapter 5: Management with the CLU, cont.

Managing iSCSI Connections .....167

Viewing Node Information ....167

Viewing Node Statistics 167

Making Node Settings .....168

Viewing Target Port Information 168

Viewing Data Port Statistics 169

Viewing Portal Information 169

Viewing Session Information .....169

Viewing iSNS Information 169

Making iSNS Settings 170

Viewing CHAPs 170

Adding CHAPs 170

Editing CHAPs 171

Deleting CHAPs 171

Pinging iSCSI Connections .....171

Managing Background Activity 172

Viewing Current Background Activities .....172

Making Background Activity Settings .....172

Working with the Event Viewer .....174

Viewing Runtime Events 174

Clearing Runtime Events 174

Viewing NVRAM Events 174

Clearing NVRAM Events 175

Managing Spare Drives 176

Viewing a list of Spare Drives .....176

Creating a Spare Drive ....176

Making Spare Drive Settings 177

Running Spare Check....177

Deleting a Spare Drive ....178

Working with LUN Mapping 179

Viewing Initiators 179

Enabling LUN Mapping .....179

Creating Initiators ....179

Deleting Initiators 180

Mapping LUNs to Initiators ....180

Managing Users 181

Viewing User Information ....181

Creating a User 181

Changing a User's Password ....182

Changing a User's Display Name and Email Address .....182

Chapter 5: Management with the CLU, cont.

Managing Users, cont.

Changing a User's Privilege and Status .....183

Deleting a User 183

Working with Software Management ....184

Making Email Settings 184

Making SLP Settings....185

Making Webserver Settings 185

Making Telnet Settings ....186

Making SNMP Settings 186

Managing SNMP Trap Sinks .....187

Making CIM Settings....188

Making Netsend Settings 188

Managing Netsend Recipients 189

Flashing through TFTP 191

Clearing Statistics ....192

Restoring Factory Defaults 193

Shutting Down the Subsystem 194

Shutting down the VTrak – Telnet Connection .....194

Shutting down the VTrak – Serial Connection .....194

Restarting the Subsystem .....196

Restarting VTrak – Telnet Connection .....196

Restarting VTrak – Serial Connection .....196

Working with the Buzzer 197

Silencing the Buzzer 197

Making Buzzer Settings 197

Testing the Buzzer 197

Chapter 6: Maintenance ....199

Updating the Firmware in WebPAM PROe .....199

Downloading the Firmware Image File .....199

Updating Firmware from TFTP Server 199

Updating Firmware from your PC .200

Restarting the Subsystem .....201

Updating the Firmware in the CLU .....202

Downloading the Firmware Image File .....202

Updating the Firmware .....202

Restarting Subsystem over a Telnet Connection .....202

Restarting Subsystem over a Serial Connection .....203

Chapter 6: Maintenance, cont.

Replacing a Power Supply 204

Remove the Old Power Supply .....204

Install a New Power Supply .....204

Replacing a Cooling Unit Fan or Blower .....205

Replacing a Cache Battery .....211

Replacing a RAID Controller .....216

Removing the old controller .....216

Installing the new controller .....216

Chapter 7: Technology Background .....219

Introduction to RAID 219

RAID 0 – Stripe .....220

RAID 1 – Mirror .....221

RAID 1E – Enhanced Mirror .....222

RAID 5 – Block and Parity Stripe .....223

RAID 6 – Block and Double Parity Stripe .....224

RAID 10 - Mirror + Stripe .....225

RAID 50 – Striping of Distributed Parity .....226

Choosing a RAID Level .....228

RAID 0 .228

RAID 228

RAID 1E 229

RAID 5 .229

RAID 6 .229

RAID 10 .230

RAID 50 .230

Choosing Stripe Size .....231

Choosing Sector Size ....231

Cache Policy 232

Read Cache Policy .232

Write Cache Policy ....232

Adaptive Writeback Cache .....232

Capacity Coercion 233

Initialization 234

Hot Spare Drive(s)....234

Partition and Format the Logical Drive .....235

RAID Level Migration .....235

Ranges of Disk Array Expansion .....237

Media Patrol ....238

Chapter 7: Technology Background, cont.

Predictive Data Migration (PDM) .....238

PDM Triggers 238

Transition....239

Example 240

Chapter 8: Troubleshooting .....243

VTrak is Beeping .....244

LEDs Display Amber or Red .....245

Front Panel 245

Drive Status Indicators .....246

Back of Enclosure .....247

CLU Reports a Problem .....250

Viewing Runtime Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250

Viewing NVRAM Events .....250

Checking a Reported Component .....251

WebPAM PROe Reports a Problem .252

Event Notification Response .....255

Critical & Offline Disk Arrays .....269

When a Physical Drive Fails .....269

With a Hot Spare Drive .....269

Without a Hot Spare Drive .....270

Rebuild Operation .....270

Incomplete Array 272

Physical Drive Problems .....273

Physical Drive Offline .....273

Physical Drive Failed 273

Enclosure Problems 275

Connection Problems 278

Serial Connections 278

Network Connections 278

iSCSI Connections .....279

Browser Does Not Connect to WebPAM PROe .....280

Unsaved Data in the Controller Cache .....281

Chapter 9: Support .....283

Frequently Asked Questions ....283

Contacting Technical Support .....285

Limited Warranty ....288

Returning Product For Repair ....289

Appendix A: Useful Information .....291

Serial Connector Pinout .....291

SNMP MIB Files 292

Loading MIB Files .....292

Index. 293

Chapter 1: Introduction to VTrak

This chapter covers the following topics:

• About This Manual (below)
  • VTrak Overview (page 2)
  • Architectural Description (page 3)
• Specifications (page 6)

Thank you for purchasing Promise Technology's VTrak M610i, M310i, or M210i external disk array subsystem.

About This Manual

This Product Manual describes how to setup, use and maintain the VTrak M-Class external disk array subsystem. It also describes how to use the built-in command-line interface (CLI), command-line utility (CLU) and 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:

Note

A Note provides helpful information such as hints or alternative ways of doing a task.

Important

An Important calls attention to an essential step or point required to complete a task. Important items include things often missed.

Caution

A Caution informs you of possible equipment damage or loss of data and how to avoid them.

Warning

A Warning notifies you of probable equipment damage or loss of data, or the possibility of physical injury, and how to avoid them.

VTrak Overview

VTrak provides data storage solutions for applications where high performance and data protection are required. The failure of any single drive will not affect data integrity or accessibility of the data in a RAID protected logical drive.

Figure 1. VTrak M610i front view

Figure 2. VTrak M310i front view (M210i is similar)

A defective drive may be replaced without interruption of data availability to the host computer. If so configured, a hot spare drive will automatically replace a failed drive, securing the fault-tolerant integrity of the logical drive. The self-contained hardware-based RAID logical drive provides maximum performance in a compact external chassis.

Figure 3. VTrak M610i rear view

Figure 4. VTrak M310i and M210i rear view

Architectural Description

The VTrak M610i is a 3U enclosure designed for an IP-based Storage Area Network (IP SAN) and Direct Attached Storage (DAS). The M310i and M210i are 2U enclosures designed for an IP SAN or DAS.

The M610i, M310i, and M210i subsystems support:

• 1.5 Gb/s SATA disk drives
• 3.0 Gb/s SATA disk drives

All M-Class enclosures include a mid-plane, RAID controller, power and cooling units, and enclosure processor all in one cable-less chassis design. Multiple fans and power supplies provide redundancy to ensure continued usage during component failure. The RAID controller is hardware based and controls all logical drive functions transparently to the host system. VTrak appears to the computer's operating system as a standard SCSI drive or drives.

Features and Benefits

Highlights

• M610i: 16 hot-swappable drive bays in a robust 3U rackmount chassis with redundant, hot-swappable power and cooling modules
• M310i:12 hot-swappable drive bays in a robust 2U rackmount chassis with redundant, hot-swappable power and cooling modules
• M210i: 8 hot-swappable drive bays in a robust 2U rackmount chassis with redundant, hot-swappable power and cooling modules
  • Supports Serial ATA (SATA) 1.5 Gb/s and 3 Gb/s drives simultaneously in the same system
• Dual 1 Gb/s iSCSI host ports provide high-availability IP SAN
• Simplified remote management with a comprehensive embedded web-based management via Ethernet—WebPAM PROe. Command Line Interface/Utility via DB9 Serial Port
• Three years complete system limited warranty includes 24 x 7 email and phone support with highly experienced technical support technicians and an advanced replacements program
• Support for the latest RAID technology—RAID 6—Protection from a catastrophic double drive failure
• Resilient data protection features such as Predictive Data Migration™ and PerfectRAID™ provide rock solid data protection
• LUN Mapping and Masking bring flexibility for multiple application and OS support on the same storage subsystem
• Open architecture, industry's most comprehensive support for SATA hard drives and standards-based management interfaces including SNMP, CIM, and WBEM
• Support for the industry standard Disk Data Format (DDF from SNIA) ensures interoperability and drive roaming even among different RAID vendors

Subsystem and Controller Features

Drive Support: 3.5" x 1" hard disk drives: SATA II 3Gb/s and 1.5Gb/s.

Supports any mix of SATA II 3 Gb/s or 1.5 Gb/s drives simultaneously in the same system. Staggered physical drive spin-up.

External I/O Ports: Dual iSCSI 1 Gb/s host ports.

Data Cache: Shared 256 MB predictive data cache (expandable to 1 GB); Automatic write cache destaging.

Optional Battery Backup Unit (BBU) powers the data cache up to 72-hours in the event of a power failure.

Operational Features

RAID Levels: RAID 0, 1, 1E, 5, 6, 10, and 50 – Any combination of these RAID levels can exist at the same time.

Configurable RAID stripe size: 64 KB, 128 KB, 256 KB, 512 KB, and 1 MB stripe size per logical drive.

Background task priority tuning: Adjustment of minimum I/O reserved for server use during all background tasks.

Hot spares: Multiple global or dedicated hot-spare drives with revert option.

Maximum LUNs per subsystem: 256 in any combination of RAID levels.

Maximum LUNs per array: 32 logical drives (LUNs). Supports LUN carving by allowing an array to be divided into multiple logical drives. Supports out-of-order logical drive deletion and re-creation.

Max LUNs per Target ID: Up to 64, depending on host side driver and operating system.

LUN Masking and Mapping: Supports multiple hosts.

Disk Data Formats: Supports Disk Data Format (DDF) for industry-wide standardization and drive roaming between VTrak systems.

Background Activities: Media Patrol, background synchronizing, disk array rebuild, Redundancy Check, SMART condition pooling, Online Capacity Expansion (OCE), RAID Level Migration (RLM). Includes priority control, rate control, and watermarking per BGA in disk and NVRAM.

Foreground Activities: Disk array initialization.

Physical Drive Error Recovery: Predictive Data Migration (PDM), replaces unhealthy disk member in array, while maintaining normal array status during the

data transition. Bad Sector Mapping, Media Patrol, SMART, Hard/Soft Reset to recover HD from bad status, HD Power-control to recover HD from hung status.

Array Error Recovery: Data recovery from bad sector or failed HD for redundant RAID, RAID 5/6 inconsistent data Prevent (Write Hole Table), Data content Error Prevent (Read/Write Check Table) NVRAM event logging.

SCSI Commands: Supports extensive SCSI command set equivalent to SCSI/FC hard disk drives. Variable sector size (512 byte to 4 KB) to break OS 2TB limitation. 16 byte CDB support for 64-bit LBA addressing.

Management

Supported Operating Systems: Windows 2000 Server, Windows 2003 Server, Windows XP, Linux (Red Hat, SuSE), Macintosh OS X, Solaris.

Management Tools: WebPAM PROe via out-of-band Ethernet. OS independent, localized in multiple languages, SSL Security support. Command Line Interface (CLI) and Command Line Utility (CLU) via DB9 Serial Port or Telnet.

Standard Management Protocols: SNMP, WBEM/CIM

RAID Creation: Automatic, Express, and Advanced configuration support for novice to skilled users.

Management Interfaces: WebPAM PROe, CLU, CLI, audible (buzzer) and visible (LEDs) alarms.

Management Protocols: Embedded web server and management support—no host agent needed. Ethernet, DB9 serial port, SNMP, SSL, Telnet, Email.

Specifications

Current (maximum): 8 A @ 100 VAC or 4 A @ 240 VAC Current rating with two power cords.

Power Consumption: 73 W (not including disk drives).

Power Supply: M610i, 400 W; M310i, 360 W; M210i, 260 W

Dual power supplies, 100-240 VAC auto-ranging, 50-60 Hz, dual hot swap and redundant with PFC, N+1 design.

Operating Temperature: 5° to 40°C operational (-40° to 60°C non-operational)

Relative Humidity: Maximum 95 percent.

Vibration: Random, 0.21 grms, 5-500Hz, 30 Mins, X, Y, Z axis.

Dimensions (H x W x D):

M610i, 13.1 x 44.6 x 56.1 cm (5.2 x 17.6 x 22.1 in)

M210i, M310i, 8.9 x 44.6 x 56.1 cm (3.5 x 17.6 x 22.1 in)

M610i, 26.7 kg (58.7 lb) without drives, 34.7 kg (76.3 lb) with 16 drives, assuming 0.5 kg (1.1 lb) per drive.

M310i, 25.00 kg (55.12 lbs) without drives; 30.0 kg (66.1 lbs) with 12 drives, assuming 0.5 kg (1.1 lb) per drive.

M210i, 23.0 kg (50.7 lbs) without drives; 28.0 kg (61.7 lbs) with 8 drives, assuming 0.5 kg (1.1 lb) per drive.

Gross Weight (including carton):

M610i, 30 kg (66.1 lb) without drives.

M310i,

M210i,

Safety: FCC Class B, VCCI, C-Tick, cUL, TUV, CB, BSMI.

Warranty and Support

Warranty: Three years complete system limited warranty.

Support: 24 x 7 email and phone support (Americas and EMEA only). 24 x 7 access to Promise support site for drivers, firmware, compatibility. Advanced replacements program.

FCC Statement

This device complies with Part 15 of the FCC Rules. Operation is subject to the following two conditions: (1) this device may not cause harmful interference, and (2) this device must accept any interference received, including interference that may cause undesired operation.

Chapter 2: VTrak Installation

This chapter covers the following topics:

• Unpacking the VTrak (below)
• Mounting VTrak M610i in a Rack (page 10)
• Mounting VTrak M310i or M210i in a Rack (page 12)
• Installing Disk Drives (page 15)
• Making Management and Data Connections (page 18)
• Making Serial Cable Connections (page 20)
• Connecting the Power (page 21)

Unpacking the VTrak

The VTrak box contains the following items:

• V T r a k U • Q u i c k S

• Null Modem Cable
• Left and right center-mount brackets

• Left and right mounting rails

• Screws for disk drives
  a (36 for t M210i; 52 for M310i; 70 for M610i; including 4 spares)
  • 1.5m (4.9 ft) Power cords (2 for US and 2 for Europe)
  • CD with SNMP files, 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

Use the following categories of network cables with VTrak:

• Cat 6, preferred
• Cat 5E, minimum

Mounting VTrak M610i in a Rack

The M610i subsystem installs to the rack using the supplied mounting rails. You can also use your existing rails.

Figure 1. VTrak M610i mounted in a rack with the supplied rails

Cautions

• At least two persons are required to safely lift, place, and attach the VTrak subsystem into a rack system.
• Do not lift or move the VTrak subsystem by the handles, power supplies or the controller units. Hold the subsystem itself.
• Do not install the VTrak subsystem into a rack without rails to support the subsystem.
• Only a qualified electrician who is familiar with the installation procedure should mount and install the VTrak subsystem.
• Be sure all switches are OFF before installing the VTrak subsystem or exchanging components.

To install the M610i subsystem into a rack with the supplied mounting rails:

1. Check the fit of the mounting rails in your rack system. See Figure 2.
2. Adjust the length of the mounting rails as needed.

3. Attach the mounting rail assemblies to the outside of the rack posts, using the attaching screws from your rack system.
   Be sure the support is on the bottom facing inward.

4. Square the rail assemblies in the rack.

5. Tighten the adjustment screws and the attaching screws.
6. Place the VTrak subsystem onto the rails.
7. Secure the VTrak subsystem to the rack through each handle, using the attaching screws from your rack system.

Figure 2. Rack mount assembly diagram

Mounting VTrak M310i or M210i in a Rack

The VTrak M310i or M210i subsystem installs to the rack using the supplied mounting rails. You can also use your existing rails.

Figure 3. Rackmounted VTrak M310i (M210i is similar)

Cautions

• At least two persons are required to safely lift, place, and attach the VTrak subsystem into a rack system.
• Do not lift or move the VTrak subsystem by the handles, power supplies or the controller units. Hold the subsystem itself.
• Do not install the VTrak subsystem into a rack without rails to support the subsystem.
• Only a qualified electrician who is familiar with the installation procedure should mount and install the VTrak subsystem.
• Be sure all switches are OFF before installing the VTrak subsystem or exchanging components.

To install the M310i or M210i subsystem into a rack with the supplied mounting rails:

1. Check the fit of the mounting rails in your rack system. See Figure 5.
2. Slide the plates out of the mounting rails.

3. 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.

4. Slide one of the rails over the plate on one side of the enclosure.

The rail is designed to slide freely over the plate.

1. Attach a flange to each end of the rail, with the rail on the opposite side of the flange from the two-hole bracket.

2. Install the rail adjustment screws (included) through the flange into the rail. There are four screws for each flange. See Figure 5.

3. Place the subsystem with mounting rails into your rack system.

4. Attach the mounting rail assemblies to the outside of the rack posts, using the attaching screws from your rack system.

5. Square the rail assemblies in the rack.

6. Tighten the adjustment screws and the attaching screws.

7. Place the VTrak subsystem onto the rails.

8. Secure the VTrak subsystem to the rack through each handle, using the attaching screws from your rack system.

Figure 4. Sliding flange installation

Figure 5. Mounting rail installation

Installing Disk Drives

You can populate the VTrak with 3.5-inch, 1.5 Gb/s or 3.0 Gb/s SATA drives. For optimal performance, install physical drives of the same model and capacity. The drives' matched performance allows the logical drive to function better as a single drive. The table below shows the number of drives required for each RAID level.

Level Number of Drives Level		Number of Drives
RAID 0 1 or more RAID 6 4 to 16
RAID 1 2 only RAID 10 4 or more*
RAID 1E 2 or more RAID 50 6 or more
RAID 5 3 to 16
* Must be an even number of drives.

Note

Unlike other VTrak models, the M610i, M310i, and M210i do not support Parallel ATA disk drives. There is no PATA-to-SATA adapter available for these models.

Drive Slot Numbering

You can install any suitable disk drive into any slot in the enclosure. The diagram below shows how VTrak's drive slots are numbered. Slot numbering is reflected in the WebPAM PROe and CLU user interfaces.

Figure 6. VTrak M610i drive slot numbering

Figure 7. VTrak M310i drive slot numbering. The M210i is similar, with 8 drive carriers

1

Install all of the drive carriers into the VTrak enclosure to ensure proper airflow, even if you do not populate all the carriers with disk drives.

Installing Disk Drives

1. Remove a disk drive carrier.
2. Carefully lay the disk drive into the drive carrier at the front, so that the screw holes on the bottom line up.
3. Insert the screws through the holes in the drive carrier and into the bottom of the disk drive. See Figure 8.

• Install only the counter-sink screws supplied with the VTrak.
• Install four screws per drive.
- Snug each screw. Be careful not to over-tighten.

1. Reinstall the drive carrier into the VTrak chassis.

Repeat steps 1 through 4 until all of your disk drives are installed.

Figure 8. VTrak drive carrier mounting holes

Figure 9. SATA Disk Drives mount at the front of the carrier

Making Management and Data Connections

Configuring an IP Storage Area Network

• A Gigabit Ethernet network interface card (GbE NIC) with iSCSI support (in hardware or software)
• A GbE Switch with iSCSI support
- A network switch
• A network interface card (NIC) in the PC

Data Path

To establish an isolated data path:

1. Connect the 1 GbE (iSCSI) NIC to your GbE switch.
2. Connect the VTrak Data Ports to your GbE switch.

Management Path

To establish the management path:

Connect the PC's standard network card and VTrak Management Port to your network switch.

Figure 10. VTrak IP SAN connections

As an alternative, you can use the same GbE (iSCSI) NIC for your PC for management and data connections. However, combining management and data paths this way will reduce performance.

Configuring Direct Attached Storage

This arrangement requires:

• A Gigabit Ethernet network interface card (GbE NIC) with iSCSI support (in hardware or software)
- A network switch
• A network interface card (NIC) in the PC

Data Path

To establish the data path:

Connect the GbE (iSCSI) NIC in your PC to one of the VTrak Data Ports.

Management Path

To establish the management path:

Connect the PC's standard NIC and VTrak's Management Port to your network switch.

Figure 11.VTrak DAS connections

Making Serial Cable Connections

The RS-232 Serial connection enables the Command Line Interface (CLI) and Command Line Utility (CLU) on your PC to monitor and control VTrak.

Figure 12.Serial connector for VTrak M310i. The M610i and M210i are similar

To set up a serial cable connection:

1. Attach a null-modem cable to the DB-9 connector on the VTrak.
2. Attach the other end of the null-modem cable to a serial port on the Host PC or Server.

You will establish a serial connection on the Host PC or Server (see page 23). At this time, continue with “Connecting the Power” on page 21.

Connecting the Power

Plug the power cords and switch on both power supplies on. When the power is switched on, the LEDs on the front of the VTrak will light up.

When boot-up is finished and the VTrak is functioning normally:

• Controller Heartbeat LED blinks green seven times in three seconds, goes dark for six seconds, then repeats the blink pattern.
• Power, FRU, and Logical Drive Status LEDs display green continuously.
• RAID Controller LED flashes green if there is activity on a iSCSI port.

Figure 13. VTrak front panel LED display. The M610i is shown

There are two LEDs on each Drive Carrier. They report the presence of power and a disk drive, and the current condition of the drive.

Figure 14.VTrak disk carrier LEDs

After a few moments the Power/Activity should display Green.

If there is no disk drive in the carrier, the Disk Status LED and the Power/Activity LED will remain dark.

The Power/Activity LED flashes during drive activity.

The Disk Status LED displays Green when a drive is present and configured.

Chapter 3: VTrak Setup

This chapter covers the following topics:

• Setting up the Serial Connection (below)
• Choosing DHCP or a Static IP Address (page 24)
• Setting up VTrak with the CLI (page 25)
• Setting up VTrak with the CLU (page 27)
• Creating Disk Arrays with WebPAM PROe (page 29)

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 PC's terminal emulation program, such as Microsoft HyperTerminal. This procedure uses the serial cable connection you made. See “Making Serial Cable Connections” on page 20.

To set up the serial connection:

1. Change your terminal emulation program settings to match the following specifications:

2. Bits per second: 115200

3. Data bits: 8
4. Parity: None
5. Stop bits: 1

6. Flow control: none

7. Start your PC's terminal VT100 or ANSI emulation program.

8. Press Enter once to launch the CLI.
9. At the Login prompt, type administrator and press Enter.
10. 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 25)
• Setting up VTrak with the CLU (page 27)

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 VTrak's Management Port.
• Specifying a static IP address for the VTrak's management port.

If you choose to enable DHCP, have your Network Administrator dedicate an IP address for the VTrak, linked to the VTrak's MAC address. This action will prevent the DHCP server from assigning a new IP address when the VTrak restarts, with the result that users can no longer log in.

Viewing MAC and IP Addresses in the CLI

To access the MAC and IP addresses for VTrak's Management Port using a serial connection and the CLI:

1. Start your PC's terminal VT100 or ANSI emulation program.
2. Press Enter once to launch the CLI.
3. At the Login prompt, type administrator and press Enter.
4. At the Password prompt, type password and press Enter.
5. At the administrator@cli> prompt, type net -v and press Enter.

All of the networking information displays, including the MAC and IP addresses.

Viewing MAC and IP Addresses in the CLU

To access the MAC and IP addresses for VTrak's Management Port using a serial connection and the CLU:

1. Start your PC's terminal VT100 or ANSI emulation program.
2. Press Enter once to launch the CLI.
3. At the Login prompt, type administrator and press Enter.
4. At the Password prompt, type password and press Enter.
5. At the administrator@cli> prompt, type menu and press Enter.
6. From the CLU Main Menu, highlight Network Management and press Enter. The network port summary screen displays a list of components, including the IP address.
7. From the list of entries, highlight the Mgmt entry and press Enter.

All of the information for the Management Port displays, including the MAC address.

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 2007/05/29 -t 14:50:05

In the above example, the date and time are included as examples only. Your values will be different. Use yyyy/mm/dd for the date and a 24-hour clock for the time.

1. Type the following string to set the Management Port IP address and other settings, then press Enter.

administrator@cli> net -a mod -t mgmt -s "primaryip=192.168.10.87, primaryipmask=255.255.255.0, gateway=192.168.10.1"

In the above example, the IP addresses and subnet mask are included as examples only. Your values will be different.

If you prefer to let your DHCP server assign the 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.

1. To verify the settings, type net and press Enter.

administrator@cli> net

CId Port Type IP Mask Gateway Link

1 1 Mgmt 192.168.10.87 255.255.255.0 192.168.10.1 Up

1 1 iSCSI 10.0.10.1 255.0.0.0 0.0.0.0 Down

1 2 iSCSI 10.0.10.2 255.0.0.0 0.0.0.0 Down

1. Type the following string to set the iSCSI Port IP address and other settings, then press Enter.

administrator@cli> net -a mod -t iSCSI -p 1 -s

"primaryip=192.168.10.88, primaryipmask=255.255.255.0, gateway=192.168.10.3"

If you prefer to let your DHCP server assign the IP address, type the following string, then press Enter.

administrator@cli> net -a mod -t iSCSI -p 1 -s "dhcp=enable"

1. To verify the settings, type net, and press Enter.

administrator@cli> net

CId Port Type IP Mask Gateway Link

1 1 Mgmt 192.168.10.87 255.255.255.0 192.168.10.1 Up
1 1 iSCSI 192.168.10.88 255.255.255.0 192.168.10.1 Up
1 2 iSCSI 10.0.10.2 255.0.0.0 0.0.0.0 Down

1. Repeat steps 3 and 4 to set the other iSCSI port. Use -p 2 in place of -p 1.

To see the full set of CLI commands, at the administrator@cli> prompt, type help and press Enter.

This completes the Management and iSCSI Port setup. Go to “Creating Disk Arrays with WebPAM PROe” on page 29.

Setting up VTrak with the CLU

1. At the administrator@cli> prompt, type menu and press Enter. The CLU main menu appears.

Figure 1. CLU main menu

1. With Quick Setup highlighted, press Enter.

The first Quick Setup screen enables you to make Date and Time settings.

Setting system date and time

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

Making Management Port settings

By default, DHCP is disabled on VTrak and the default Management Port IP address is set to 10.0.0.1. The TCP Port is set to 2300.

Use a new Management Port IP address to log into the VTrak over your network.

Manual IP settings

To make Management Port settings manually:

1. Press the arrow keys to highlight IP Address.
2. Press the backspace key to erase the current IP Address.

3. Type the new IP Address.

4. 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.

1. Press Ctrl-A to save these settings and move to the iSCSI Port 1 screen.

Automatic IP settings

To make Management Port settings automatically:

1. Press the arrow keys to highlight DHCP.
2. Press the spacebar to toggle to Enable.
3. Press Ctrl-A to save these settings and move to the iSCSI Port 1 screen.

Making iSCSI Data Port settings

Manual IP settings

To make iSCSI Data Port settings manually:

1. Press the arrow keys to highlight IP Address.
2. Press the backspace key to erase the current IP Address.
3. Type the new IP Address.
4. 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 these settings and move to the iSCSI Port 2 screen.
6. Follow the same procedure to make settings for iSCSI Port 2.
7. Press Ctrl-A to save these settings.

Automatic IP settings

To make iSCSI Data Port settings automatically:

1. Press the arrow keys to highlight DHCP.
2. Press the spacebar to toggle to Enable.
3. Press Ctrl-A to save these settings and move to the iSCSI Port 2 screen.
4. Follow the same procedure to make settings for iSCSI Port 2.
5. Press Ctrl-A to save these settings.

Exiting the CLU

1. Highlight Skip the Step and Finish and press Enter.
2. Highlight Return to CLI and press Enter.
   This completes the Management and iSCSI Port setup. Go to "Creating Disk Arrays with WebPAM PROe" on page 29.

Creating Disk Arrays with WebPAM PROe

Note

You can also use the CLU to create disk arrays and logical drives. See “Creating a Disk Array” on page 147 for more information.

Setting up disk arrays with WebPAM PROe consists of the following actions:

• Logging into WebPAM PROe (below)
• Selecting a Language (page 31)
• Creating a Disk Array (page 31)
• Logging out of WebPAM PROe (page 35)
  • Using WebPAM PROe over the Internet (page 36)
• Optional. Obtaining a Security Certificate (page 36)

Logging into WebPAM PROe

1. Launch your Browser.
2. In the Browser address field, type in the IP address of the VTrak subsystem. Use the IP address you set in the CLI (page 25) or CLU (page 27). Note that the IP address shown below is only an example. The IP address you type into your browser will be different.

Regular Connection

• WebPAM PROe uses an HTTP connection....http://
• Enter the VTrak's Management Port IP address . . . 192.168.1.105
  Together, your entry looks like this:

http://192.168.1.105

Secure Connection

• WebPAM PROe uses a secure HTTP connection....https://
• Enter the VTrak's Management Port IP address . . . 192.168.1.105
  Together, your entry looks like this:

https://192.168.1.105

Note

Whether you select a regular or a secure connection, your login to WebPAM PROe and your user password are always secure.

1. When the log-in screen (Figure 2) appears:

- T y p e

administrator in the User Name field.

- T y p e

password in the Password field.

- Click the Login button.

The User Name and Password are case sensitive.

1. Click the Login button.

Figure 2. WebPAM PROe log-in screen

After sign-in, the WebPAM PROe opening screen appears. If there are any unconfigured physical drives in the enclosure, an Array Configuration menu will also appear. See page 31.

Note

Make a Bookmark (Netscape Navigator) or set a Favorite (Internet Explorer) of the Login Screen so you can access it easily next time.

Selecting a Language

WebPAM PROe displays in English, German, French, Italian, Japanese, Chinese Traditional, Chinese Simple, and Korean.

1. Click Language in the WebPAM PROe Header.

The language list appears in the Header.

1. Click the language you prefer.

The WebPAM PROe user interface displays in the selected language.

Figure 3. Clicking "Language" in the WebPAM PROe Header

Creating a Disk Array

On a newly activated VTrak subsystem, there are no disk arrays or logical drives. To create a disk array:

1. Click the Disk Arrays icon, then click the Create tab.

The Array Configuration menu appears. See Figure 4.

1. Choose one of the options:

2. Automatic – Creates a new disk array based on a default set of parameters, including one logical drive. The number of unconfigured physical drives available determines the RAID level of the disk array and whether a spare drive is created. See page 32.

3. Express – Creates a new disk array based on the characteristics you specify. You can create multiple logical drives. However, all of the logical drives will be the same size and RAID level. See page 33.

4. Advanced – Enables you to directly specify all parameters for a new disk array and its logical drives. See page 34.

5. Click the Next button.

Figure 4. The Array Configuration menu

Automatic

When you choose the Automatic option, the following parameters appear on the screen:

• Disk Arrays – The number of physical drives in the disk array, their ID numbers, configurable capacity, and the number of logical drives to be created
• Logical Drives – The ID number of the logical drive(s), their RAID level, capacity, and stripe size
• Spare Drives – The physical drive slot number of the dedicated hot spare assigned to this disk array. A hot spare drive is created for all RAID levels except RAID 0, when five or more unconfigured physical drives are available

If you accept these parameters, click the Submit button.

The new disk array appears in the Disk Array List on the Information tab.

If you do NOT accept these parameters, use the Express (page 33) or Advanced (page 34) option to create your disk array.

Express

When you choose the Express option, a set of characteristics and options appears on the screen.

1. Check the boxes to select any one or a combination of:

2. Redundancy – The array will remain available if a physical drive fails
   • Capacity – The greatest possible amount of data capacity

3. Performance – The highest possible read/write speed

4. Spare Drive – A hot spare drive is created when you select Redundancy, Spare Drive, and five or more unconfigured physical drives are available

5. In the Number of Logical Drives field, enter the number of logical drives you want to make from this disk array.

The maximum possible number of logical drives appears to the right of this field.

1. From the Application Type menu, select an application that best describes your intended use for this disk array:

2. F i l e S e r v e r

3. Video Stream
4. Transaction Data
5. Transaction Log

6. Other

7. Click the Update button.

Or check the Automatic Update box and updates will occur automatically.

The following parameters display:

• Disk Arrays – The number of physical drives in the disk array, their ID numbers, configurable capacity, and the number of logical drives to be created
• Logical Drives – The ID number of the logical drive(s), their RAID level, capacity, and stripe size
• Spare Drives – The physical drive ID number of the dedicated hot spare assigned to this disk array (all RAID levels except RAID 0)

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.

1. When you are done, click the Submit button.

The new disk array appears in the Disk Array List on the Information tab.

Advanced

Note

For an explanation of the parameters under the Advanced option, see “Chapter 7: Technology Background” on page 219.

When you choose the Advanced option, the Step 1 – Disk Array Creation screen displays.

Step 1 – Disk Array Creation

1. Enter a name for the disk array in the field provided.
2. Check the box if you want to enable Media Patrol.

For more information, see "Media Patrol" on page 238.

1. Check the box if you want to enable PDM.

For more information, see "Predictive Data Migration (PDM)" on page 238.

1. Highlight physical drives you want in the disk array from the Available list and press the >> button to move them to the Selected list.

You can also double-click them to move them.

1. When you are done, click the Next button.

Step 2 – Logical Drive Creation

Logical Drive Creation enables you to specify logical drives under the new disk array. Enter the information for a logical drive, then click the Update button. If there is free capacity remaining, you can specify another logical drive now or wait until later.

1. Enter an alias for the logical drive in the field provided.
2. Choose a RAID level for the logical drive from the dropdown menu.

The choice of RAID levels depends the number of physical drives you selected.

1. RAID 50 only – Specify the number of axles for your array.

For more information on axles, see "RAID 50 Axles" on page 226.

1. Specify a Capacity and the unit of measure (MB, GB, TB).

This value will be the data capacity of the first logical drive in your new disk array. If you specify less than disk array's maximum capacity, the remainder will be available for additional logical drives which you can create later.

1. Specify a Stripe size from the dropdown menu.

64 KB, 128 KB, 256 KB, 512 KB, and 1 MB are available. 64 KB is the default.

1. Specify a Sector size from the dropdown menu.

For iSCSI, use the 512 B default.

1. Specify a Read (cache) Policy from the dropdown menu.

Read Cache, Read Ahead Cache, and No Cache are available. Read Ahead is the default.

1. Specify a Write (cache) Policy from the dropdown menu.

Write Back and Write Through (Thru) are available. Write Back is the default.

1. Click the Update button.

A new logical drive is displayed under New Logical Drives.

Repeat the above steps to specify additional logical drives as desired.

1. When you are done specifying logical drives, click the Next button.

Step 3 – Summary

The Summary lists the disk array and logical drive information you specified.

1. To proceed with disk array and logical drive creation, click the Submit button.

Logging out of WebPAM PROe

There are two ways to log out of WebPAM PROe:

- Close your browser window

• C l i c k

Logout in the WebPAM PROe banner

Figure 5. Clicking "Logout" in the WebPAM PROe banner

Clicking Logout brings you back to the Login Screen. See page 30.

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.

While only a iSCSI-capable PC can read and write data to the logical drives on the VTrak, other PCs can monitor the VTrak from virtually any location.

Obtaining a Security Certificate

Promise Technology provides a default security certificate for the web server as well as for internal data communication. However, in most cases it is better to install and verify your own certificate. And, if possible, verify your certificate through a certificate authority, such as Verisign or Thwate. See your MIS Administrator for guidance.

To download your security certificate to WebPAM PROe, see "Making Web Server Settings" on page 77.

Chapter 4: Management with WebPAM PROe

This chapter covers the following topics:

• Logging into WebPAM PROe (page 38)
• Selecting a Language (page 40)
  • Perusing the Interface (page 41)
• Logging out of WebPAM PROe (page 45)
  • Working with the Storage Network (page 46)
  • Working with Subsystems (page 47)
• Managing Users (page 57)
• Managing the Network Connection (page 62)
• Managing iSCSI Connections (page 67)
• Managing Storage Services (page 73)
• Managing Software Services (page 76)

• Exporting the User Database (page 84)

• Importing a User Database (page 85)

• Updating the Firmware (page 86)
• Restoring Factory Defaults (page 87)
• Clearing Statistics (page 88)
• Shutting Down the Subsystem (page 89)
• Restarting the Subsystem (page 90)
• Managing Controllers (page 91)
• Managing Enclosures (page 95)
• Managing Physical Drives (page 100)
• Managing Disk Arrays (page 105)
• Managing Logical Drives (page 118)
• Managing Spare Drives (page 125)
  • Working with the Logical Drive Summary (page 129)

For information about VTrak's audible alarm and LEDs, see "Chapter 8: Troubleshooting" on page 243.

Logging into WebPAM PROe

In order to log into WebPAM PROe, you must first setup a network connection between your Host PC and the VTrak subsystem, as described in “Chapter 3: VTrak Setup” on page 23.

To log into WebPAM PROe:

1. Launch your Browser.
2. In the Browser address field, type in the IP address of the VTrak Management port.

Note that the IIP address shown below is only an example. The IP address you type into your browser will be different.

Regular Connection

• WebPAM PROe uses an HTTP connection....http://
• Enter the VTrak's Management Port IP address . . . 192.168.1.105

Together, your entry looks like this:

http://192.168.1.105

Secure Connection

• WebPAM PROe uses a secure HTTP connection. . . . . . . . .https://
• Enter the VTrak's Management Port IP address . . . . 192.168.1.105

Together, your entry looks like this:

https://192.168.1.105

Note

Whether you select a regular or a secure connection, your login to WebPAM PROe and your user password are always secure.

1. When the log-in screen (Figure 1) appears:

2. Type e administrator in the User Name field.

3. Type e password in the Password field.
4. Click the Login button.

The User Name and Password are case sensitive.

1. Click the Login button.

Figure 1. The WebPAM PROe log-in screen

Selecting a Language

WebPAM PROe displays in English, German, French, Italian, Japanese, Chinese Traditional, Chinese Simple, and Korean.

1. Click Language the WebPAM PROe Header.

The language list appears in the Header.

1. Click the language you prefer.

The WebPAM PROe user interface displays in the selected language.

Figure 2. Clicking "Language" in the Header

Perusing the Interface

WebPAM PROe is browser-based RAID management software with a graphic user interface.

Figure 3. WebPAM PROe interface

There are four major parts to the graphic user interface:

• Header (see page 42)
• Tree (see page 43)
  • Management View (see page 44)
  • Event Frame (see page 44)

Using the Header

The Header contains the following items:

• Language – To change languages, see “Selecting a Language” on page 40.
- View – To view the Event Frame, see “Viewing the Event Frame” on page 44.
- Storage Network – To view all of the VTrak subsystem enclosures currently accessible the network, see “Working with the Storage Network” on page 46.
- Contact Us – Click Contact Us for a list of contact information, including Technical Support. Also see “Contacting Technical Support” on page 285.
- Logout – To logout of WebPAM PROe, see “Logging out of WebPAM PROe” on page 45
- Help – Click Help in the Header to access the main online help menu.
- About – Click About in the Header to display the WebPAM PROe software version and build date.

Using Tree View

Tree View enables you to navigate around all components of the Subsystem, including iSCSI management, network and service management, RAID controller, enclosure, physical drives, disk arrays, logical drives, and spare drives. The figure below shows the components of Tree View.

Figure 4. WebPAM PROe Tree View

The Administrative Tools section is different for the Super User than for other users. The remainder of the Tree is the same for all users.

Management View displays information according to the item you select in Tree View.

Using Management View

Management View provides the actual user interface with the VTrak, including creation, maintenance, deletion, and monitoring of disk arrays and logical drives.

Function Tabs control specific actions and processes. This window changes depending on which item you select in Tree View and which tab you select in Management View itself.

Click the Help button in Management View to access online help for the function that is currently displayed.

Viewing the Event Frame

To view the Event Frame:

1. Click View in the Header.
2. Click the Show Event Frame popup option.

The VTrak user interface will display the Event Frame below Management View.

1. Click View again to hide the Event Frame.

In the event frame, events are listed and sorted by:

• Item Number – A consecutive decimal number assigned to a specific event
  • Device – Battery, controller, logical drive, physical drive, port, etc.
  • Event ID – The hexadecimal number that identifies the specific type of event
• Severity – Information, Warning, Minor, Major, Critical, and Fatal. The severity level is user-specified. See “Setting-up User Event Subscriptions” on page 58.
• Time – Time and date of the occurrence
• Description – A brief description of the event

Sorting Events

You can sort the events by Item Number, Device, Event ID, Severity, Time and Date, or Description.

Click the link at the top of the column by which you want to sort the events. After you click the item, a triangle icon appears.

• If the triangle points upward, the column is sorted low-to-high or old-to-new.
• If the triangle points downward, the column is sorted high-to-low or new-to-old.

Click the link a second time to change to flip the triangle and reverse the sort sequence.

Logging out of WebPAM PROe

There are two ways to log out of WebPAM PROe:

• Close your browser window
• Click Logout the WebPAM PROe banner (below

Figure 8. Clicking "Logout" in the Header)

Clicking Logout brings you back to the Login Screen. After logging out, you must enter your user name and password in order to log in again.

Working with the Storage Network

When you log into WebPAM PROe, you access a specific VTrak subsystem. See "Logging into WebPAM PROe" on page 38.

The Storage Network feature enables you to access all of the VTrak subsystems with a Management Port connection to your network.

Each VTrak subsystem is identified by its Management Port IP address.

Storage Network functions include:

• Viewing other subsystems
• Updating the list of subsystems
• Logging into a subsystem
• Hiding the other subsystems

Viewing Other Subsytems

To view the other VTrak subsystems the Storage Network:

1. Click Storage Network in the Header.
2. Click the Show Network Subsystems popup option.
   The list will show all subsystems the network at the time the GUI was launched.

Updating the List of Subsystems

To update the list of the VTrak subsystems the Storage Network: Click the Discover button at the bottom of the subsystem list.

Logging into a Subsystem

To log into any of the displayed VTrak subsystems:

1. In Tree View, click the Subsystem
   icon of the subsystem you want to see.
   If your user name and password do not match the subsystem you are logging into, the log in screen will appear.

2. Log into the new subsystem, as needed.

Hiding the Other Subsystems

To hide the other VTrak subsystems the Storage Network:

1. Click Storage Network in the Header.
2. Click the Hide Network Subsystems popup option.

Working with Subsystems

A VTrak subsystem is identified by its Management Port IP address. Subsystem functions include:

• Viewing Subsystem Information (page 47)
• Setting an Alias for the Subsystem (page 47)
• Setting Subsystem Date and Time (page 48)
• Viewing the Runtime Event Log (page 48)
• Saving the Runtime Event Log (page 49)
• Clearing the Runtime Event Log (page 49)
  • Viewing NVRAM Events (page 49)
• Saving NVRAM Events (page 50)
• Clearing NVRAM Events (page 50)
• Viewing Current Background Activities (page 50)
• Making Background Activity Settings (page 51)
• Running Background Activities (page 52)
• Running Media Patrol (page 52)
• Running PDM (page 52)
  • Viewing Scheduled Activities (page 53)
• Scheduling an Activity (page 53)
• Deleting a Scheduled Activity (page 54)
• Viewing Lock Status (page 54)
• Setting the Lock (page 55)
• Renewing the Lock (page 55)
• Releasing the Lock (page 55)

Viewing Subsystem Information

To view information about a subsystem, click the Subsystemicon in Tree View. Management View displays the subsystem information.

Setting an Alias for the Subsystem

An alias is optional. To set an alias for this subsystem:

1. In Tree View, click the Subsystem icon.
2. In Management View, click the Settings tab.
3. Enter a name into the Alias field.

Maximum of 48 characters. Use letters, numbers, space between words, and underscore.

1. Click the Submit button.

Setting Subsystem Date and Time

To set a Date and Time for this subsystem:

1. In Tree View, click the Subsystem
2. In Management View, click the Settings tab dropdown menu and select Date and Time Settings.
3. Under Subsystem Date, select the Month and Day from the dropdown menus.
4. Type the current year into the Year field.
5. Under Subsystem Time, select the Hour, Minutes and Seconds from the dropdown menus.
6. Click the Submit button.

Viewing the Runtime Event Log

Runtime Events lists information about the 1024 most recent runtime events recorded since the system was started. To view runtime events:

1. In Tree View, click the Subsystem

1. In Management View, click the Events tab dropdown menu and select Runtime Events.

Events are displayed by:

• Item Number – A consecutive decimal number assigned to a specific event
  • Device – Battery, controller, logical drive, physical drive, port, etc.
• Event ID – The hexadecimal number that identifies the specific type of event
• Severity – Information, Warning, Minor, Major, Critical, and Fatal. The severity level is user-specified. See “Setting-up User Event Subscriptions” on page 58.

- Time – Time and date of the occurrence

- Description – A brief description of the event

1. Click the link at the top of the column by which you want to sort the events. After you click the item, a triangle icon appears.

- If the triangle points upward, the column is sorted low-to-high or old-to-new.

- If the triangle points downward, the column is sorted high-to-low or new-to-old.

Click the link a second time to change to flip the triangle and reverse the sort sequence.

Saving the Runtime Event Log

To save the runtime event log as a text file:

1. In Tree View, click the Subsystem
2. In Management View, click the Events tab dropdown menu and select Runtime Events.
3. Click the Save Event Log button.
4. In the File Download dialog box, click the Save button.
5. In the Save dialog box, name the file, navigate to the folder where you want to save the log file, and click the Save button.

Clearing the Runtime Event Log

To clear the runtime event log:

1. In Tree View, click the Subsystem
2. In Management View, click the Events tab dropdown menu and select Runtime Events.
3. Click the Clear Event Log button.
4. In the Confirmation dialog box, type confirm and click the OK button.

Viewing NVRAM Events

NVRAM Events lists information about the 191 most recent important events. NVRAM events are stored in non-volatile memory. To view runtime events:

1. In Tree View, click the Subsystem

1. In Management View, click the Events tab dropdown menu and select System Events in NVRAM.

Events are displayed by:

• Item Number – A consecutive decimal number assigned to a specific event
  • Device – Battery, controller, logical drive, physical drive, port, etc.

• Event ID – The hexadecimal number that identifies the specific type of event

• Severity – Information, Warning, Minor, Major, Critical, and Fatal. The severity level is user-specified. See “Setting-up User Event Subscriptions” on page 58.

• Time – Time and date of the occurrence

• Description – A brief description of the event

• Click the link at the top of the column by which you want to sort the events. After you click the item, a triangle icon appears.

• If the triangle points upward, the column is sorted low-to-high or old-to-new.

• If the triangle points downward, the column is sorted high-to-low or new-to-old.

Click the link a second time to change to flip the triangle and reverse the sort sequence.

Saving NVRAM Events

To save the NVRAM event log as a text file:

1. In Tree View, click the Subsystem icon.
2. In Management View, click the Events tab dropdown menu and select System Events in NVRAM.
3. Click the Save Event Log button.
4. In the File Download dialog box, click the Save button.
5. In the Save dialog box, name the file, navigate to the folder where you want to save the log file, and click the Save button.

Clearing NVRAM Events

To clear the NVRAM event log:

1. In Tree View, click the Subsystem icon.
2. In Management View, click the Events tab dropdown menu and select System Events in NVRAM.
3. Click the Clear Event Log button.
4. In the Confirmation dialog box, type confirm and click the OK button.

Viewing Current Background Activities

To view the current background activities:

1. In Tree View, click the Subsystem icon.

2. In Management View, click the Background Activities tab.
   A list of current background activities appears, including:

3. Rebuild

4. PDM – Predictive Data Migration
5. Synchronization
6. Redundancy Check
7. M i g r a t i o n
8. Transition
9. Initialization
10. Media Patrol

Making Background Activity Settings

To make settings for background activities:

1. In Tree View, click the Subsystem

1. In Management View, click the Background Activities tab and select Settings from the dropdown menu.

2. Click the dropdown menu to choose a priority of Low, Medium, and High for the following functions:

3. Rebuild – Rebuilds the data from a failed drive in a disk array

4. Synchronization – Checks the data integrity on disk arrays
5. Initialization – Sets all data bits in the logical drive to zero
6. Redundancy Check – Checks, reports and can correct data inconsistencies in logical drives
7. Migration – Change RAID level or add physical dries to disk arrays
8. PDM – Looks for bad blocks the physical drives of disk arrays
9. Transition – Returns a revertible spare drive to spare status

The rates are defined as follows:

• 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.

• Highlight the following PDM trigger settings and type a value into the corresponding field:

• Reassigned Block Threshold – 1 to 512 blocks

• Error Block Threshold – 1 to 1024 blocks

• Check to enable or uncheck to disable the following functions:

• Media Patrol – Checks the magnetic media on physical drives

• Auto Rebuild – If there is a spare drive of adequate capacity, a critical disk array will begin to rebuild automatically. If not spare drive is

available, the disk array will begin to rebuild as soon as you replace the failed physical drive with an unconfigured physical drive of equal or greater size.

1. Click the Submit button to save your settings.

Running Background Activities

To run a background activity from the Background Activities tab:

1. In Tree View, click the Subsystem
2. In Management View, click the Background Activities tab and select one of the following from the dropdown menu.
   • Media Patrol – See “Running Media Patrol” on page 52
3. Rebuild – See “Rebuilding a Disk Array” on page 114
4. PDM – See “Running PDM” on page 52
5. Transition – See “Transitioning a Disk Array” on page 116
6. Initialization – See “Initializing a Logical Drive” on page 121
7. Redundancy Check – See “Running Redundancy Check” on page 122

1. In the next screen, make the choices as requested.

2. Click the Start button.

Running Media Patrol

Media Patrol checks the magnetic media on physical drives. When it finds the specified number of bad blocks, it will trigger PDM. See “Making Background Activity Settings” on page 51 and “Running PDM” on page 52.

You can schedule Media Patrol to run automatically, see “Scheduling an Activity” on page 53.

To run Media Patrol:

1. In Tree View, click the Subsystem
2. From the dropdown menu on the Background Activities tab, select Start Media Patrol.
3. In the next screen, click the Start button.

Running PDM

Predictive Data Migration (PDM) migrates data from the suspect physical drive to a spare disk drive, similar to Rebuilding. But unlike Rebuilding, PDM acts before the disk drive fails and your Logical Drive goes Critical.

You an also run PDM on a specific disk array, see “Running PDM on a Disk Array” on page 116.

Also see "Predictive Data Migration (PDM)" on page 238.

To run PDM:

1. In Tree View, click the Subsystem icon.
2. In Management View, click the Background Activities tab and select Start Media Patrol from the dropdown menu.
3. In the next screen, select the Source and Target physical drives.
   The suspect physical drive is the source. The replacement physical drive is the target.
4. Click the Start button.

Viewing Scheduled Activities

To view scheduled activities for this subsystem:

1. Click the Subsystem icon Tree View.
2. Click the Scheduler tab in Management View.

Scheduling an Activity

To set a scheduled activity for this subsystem:

1. Click the Subsystem icon Tree View.
2. From the dropdown menu on the Scheduler tab, choose an item:
   • Media Patrol. See “Running Media Patrol” on page 52
3. Redundancy Check. See "Running Redundancy Check" on page 122
4. Battery Reconditioning. See “Reconditioning a Battery” on page 98

5. Spare Drive Check. See "Running Spare Check" on page 128

6. In the Scheduler dialog box, check the Enable This Schedule box.

7. Select a start time (24-hour clock).

8. Select a Recurrence Pattern.

9. Daily – Enter the number of days between events.

10. Weekly – Enter the number of weeks between events and select which days of the week.
11. Monthly – Select a calendar day of the month (1 – 31).

If you select a higher number than there are days in the current month, the actual start date will occur at the beginning of the following month.

Or, select a day of the week and select the first, second, third, fourth, or last occurrence of that day in the month.

Then, select the months in which you want the activity to occur.

1. Select a Range of Occurrence.

2. Start-from date. The default is today's date.

3. End-on date.

Select No End Date (perpetual).

Or, select a number of occurrences for this activity.

Or, select a specific end date. The default is today's date.

1. For Redundancy Check only:

2. Choose the Auto Fix option. This feature attempts to repair the problem when it finds an error.

3. Choose the Pause on Error option. This feature stops the process when it finds an error
4. Check the boxes beside the logical drives (all except RAID 0) to which this activity will apply.

Each logical drive can have only one scheduled Redundancy Check.

Note

You can schedule only ONE Redundancy Check for each logical drive.

1. Click the Submit button.

Deleting a Scheduled Activity

To delete a scheduled activity for this subsystem:

1. Click the Subsystem icon Tree View.
2. From the dropdown menu on the Scheduler tab, choose Delete Schedules.
3. Check the box to the left of the schedule you want to delete.
4. Click the Submit button.

Viewing Lock Status

The lock prevents other sessions (including by the same user) from making a configuration change to the controller until the lock expires or a forced unlock is done.

To view the lock status for this subsystem:

1. Click the Subsystem icon Tree View.
2. Click the Lock tab in Management View.

The following information is displayed:

- Lock Status – The User who set (owns) the current lock.

- Expiration Time – Amount of time left until the lock automatically releases.

- Expire At Time – The date and time when the lock will automatically release.

Setting the Lock

The lock prevents other sessions (including by the same user) from making a configuration change to the controller until the lock expires or a forced unlock is done.

You can set the lock to last from one minute to one day. To set the lock for this subsystem:

1. Click the Subsystem icon Tree View.

2. Click the Lock tab in Management View.

3. Click the Lock option.

4. Enter a time interval between 1 and 1440 minutes (one day) that you want the lock to stay active.

5. Click the Submit button.

Renewing the Lock

The lock prevents other sessions (including by the same user) from making a configuration change to the controller until the lock expires or a forced unlock is done.

Renewing the lock extends the period of time the controller remains locked. To renew an existing lock for this subsystem:

1. Click the Subsystem icon Tree View.

2. Click the Lock tab in Management View.

3. Click the Renew option.

4. Enter a time interval between 1 and 1440 minutes (one day) that you want the lock to stay active.

The renew time replaces the previous Expiration Time.

1. Click the Submit button.

Releasing the Lock

The lock prevents other sessions (including by 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. You can also release the lock before the scheduled time.

To release the lock for this subsystem:

1. Click the Subsystem icon Tree View.
2. Click the Lock tab in Management View.

If you are the User who set the lock, click the Unlock option.

If another User set the lock and you are a Super User, click the Unlock option and check the Force Unlock box.

1. Click the Submit button.

Managing Users

User Management includes all functions dealing with user accounts. Functions include:

• Viewing User Information (page 57)
• Making User Settings (page 57)
• Making Your Own User Settings (page 58)
• Setting-up User Event Subscriptions (page 58)
• Changing Another User's Password (page 59)
• Changing Your Own Password (page 59)
• Creating a User (page 60)
• Deleting a User (page 61)
• Viewing User Sessions (page 61)
• Logging out Other Users (page 61)

Viewing User Information

The view a list of users, their status, access privileges, display name, and email address:

1. Click the Subsystem icon in Tree View.
2. Click the Administrative Tools icon.
3. Click the User Management icon.

The Information tab appears in Management View.

Making User Settings

To change settings of other users:

1. Log into WebPAM PROe as the Administrator or a Super User.
2. Click the Subsystem icon in Tree View.
3. Click the Administrative Tools icon.
4. Click the User Management icon.

5. On the Information tab, click the link of the user whose settings you want to change.
   The Settings screen for the selected user displays.

6. Make the following settings as needed.

7. Check the Enable box to enable this user.

8. Uncheck the box to disable this user.

9. Enter or change the display name.

10. Enter or change the email address.

11. From the Privilege dropdown menu, choose a new level. See “List of User Privileges” on page 60

7. Click the Submit button.

The Administrator or Super User can change another user's password. See "Changing Another User's Password" on page 59 for more information.

Making Your Own User Settings

To change your own user settings:

1. Log into WebPAM PROe under your own user name.
2. Click the Subsystem icon in Tree View.
3. Click the Administrative Tools icon.
4. Click the User Management icon.
5. Click the Settings tab in Management View.
6. Enter or change the display name or mail address.
7. Click the Submit button.

Setting-up User Event Subscriptions

An event subscription enables a user to receive email messages about events taking place in the VTrak subsystem. To make or change user event subscriptions:

1. Click the Subsystem icon in Tree View.
2. Click the Administrative Tools icon.
3. Click the User Management icon.
4. Click the Event Subscription tab in Management View.
5. Check the box to enable event notification.
6. Under the subheadings, select the lowest level of Severity to be reported for each event. The selected level plus all higher levels of Severity will be reported.
7. Information – Information only, no action is required
8. Warning – User can decide whether or not action is required
9. Minor – Action is needed but the condition is not a serious at this time
   • Major – Action is needed now

10. Critical – Action is needed now and the implications of the condition are serious

11. Fatal – Non-Recoverable error or failure has occurred

12. None – Deactivates this event for notification purposes

7. Click the Submit button.

The user's account must have an email address. See "Making User Settings" on page 57.

For information about the email service, see "Making Email Settings" on page 76.

To send a test message to the email address in the listed under General Info, click the Test Email button.

Changing Another User's Password

To change a user's password:

1. Log into WebPAM PROe as the Administrator or a Super User.
2. Click the Subsystem icon in Tree View.
3. Click the Administrative Tools icon.
4. Click the User Management icon.
5. In the list of users, click the link of the user whose settings you want to change.

The Settings screen for the selected user displays.

1. Click the Password tab in Management View.
2. Enter the new password in the New Password field.
3. Enter the new password in the Retype Password field.
4. Click the Submit button.

Changing Your Own Password

To set or change your own password:

1. Log into WebPAM PROe under your own user name.
2. Click the Subsystem icon in Tree View.
3. Click the Administrative Tools icon.
4. Click the User Management icon.
5. Click the Password tab in Management View.
6. Enter the current password in the Old Password field.

If you do not have a password, leave this field blank.

1. Enter the new password in the New Password field.

2. Enter the new password in the Retype Password field.

3. Click the Submit button.

Creating a User

To create a user:

1. Log into WebPAM PROe as the Administrator or a Super User.
2. Click the Subsystem icon in Tree View.
3. Click the Administrative Tools icon.
4. Click the User Management icon.
5. Click the Create tab in Management View.
6. Enter a user name in the User Name field.
7. Enter a password for this user in the New Password and Retype Password fields.

A password is optional. If you do not specify a password, log into WebPAM PROe with the User Name and leave the password field blank.

1. Enter a display name in the Display Name field.
   A display name is optional.
2. Enter the user's email address in the Email Address field.
   An email address is required in order to receive email event notification.
3. Select a privilege level from the Privilege dropdown menu.
   For definitions of each privilege level, see the List of User Privileges below.
4. Check the Enabled box to enable this user on this subsystem.
5. Click the Submit button.

List of User Privileges

• View – Allows the user to see all status and settings but not to make any changes
• Maintenance – Allows the user to perform maintenance tasks including Rebuilding, PDM, Media Patrol, and Redundancy Check
• Power – 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.
• Super – 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.

Deleting a User

There will always be at least one Super User account. You cannot delete the user account you used to log in.

To delete a user:

1. Log into WebPAM PROe as the Administrator or a Super User.
2. Click the Subsystem icon in Tree View.
3. Click the Administrative Tools icon.
4. Click the User Management icon.
5. Click the Delete tab in Management View.
6. Check the box to the left of the user you want to delete.
7. Click the Submit button.
8. Click OK in the confirmation box.

Viewing User Sessions

To view the current sessions:

1. Click the Subsystem icon in Tree View.
2. Click the Administrative Tools icon.
3. Click the User Management icon.
4. Click the Sessions tab in Management View.

Logging out Other Users

To logout other users:

1. Log into WebPAM PROe as the Administrator or a Super User.
2. Click the Subsystem icon in Tree View.
3. Click the Administrative Tools icon.
4. Click the User Management icon.
5. Click the Sessions tab in Management View.
6. Check the box to the left of the user you want to log out.
7. Click the Logout button.
8. Click OK in the confirmation box.

Managing the Network Connection

The network connection deals with network connections to the VTrak's Management Ports. Functions include:

• Making Subsystem Management Port Settings (page 62)
• Making iSCSI Data Port Settings (page 62)
• Viewing VLAN Entries (page 63)
• Creating a VLAN Entry (page 63)
• Changing a VLAN Entry (page 64)
• Deleting a VLAN Entry (page 65)
• Viewing Link Aggregation Entries (page 65)
• Creating a Link Aggregation Entry (page 65)
• Changing a Link Aggregation Entry (page 66)
• Deleting a Link Aggregation Entry (page 66)

Making Subsystem Management Port Settings

When you log into the VTrak over your network, you use the management port. Before you change settings, please see "Choosing DHCP or a Static IP Address" on page 24.

To make changes to the Subsystem Management Port settings:

1. Click the Subsystem icon in Tree View.
2. Click the Administrative Tools icon.
3. Click the Network Management icon.
4. Click the Port Configuration link in Management View.
5. To enable DHCP, check the DHCP box.
   When DHCP is NOT enabled, enter:
6. IP address
7. Subnet mask
8. Gateway IP address

9. Enter a DNS server IP address

10. Click the Submit button.

Making iSCSI Data Port Settings

The network settings for the iSCSI data ports are located under the Network Management and are described below. For the iSCSI settings for the iSCSI data ports, see “Managing iSCSI Connections” on page 67.

To make changes to the iSCSI Data Port settings:

1. Click the Subsystem icon in Tree View.
2. Click the Administrative Tools icon.
3. Click the Network Management icon.
4. Click the iSCSI Ports tab in Management View.
5. Click the Port Configuration – Port 1 link or the Port Configuration – Port 2 link.
6. To enable DHCP, check the DHCP box.

When DHCP is NOT enabled, enter:

• IP address
• Subnet mask

• Gateway IP address

• To enable jumbo frames, check the Jumbo Frame box.

• Enter a TCP port number.

The default is 3260.

1. Click the Submit button.

Viewing VLAN Entries

To view the current VLAN entries:

1. Click the Subsystem icon in Tree View.
2. Click the Administrative Tools icon.
3. Click the Network Management icon.
4. Click the VLAN tab in Management View.

The Member Interface refers to an iSCSI data port or to the link aggregate trunk number.

Creating a VLAN Entry

This feature enables you to create a virtual local area network (VLAN) using an iSCSI data port on your subsystem.

If you plan to aggregate the iSCSI ports, create a link aggregation before you create the VLAN. See “Creating a Link Aggregation Entry” on page 65.

If you plan to use jumbo frames for the VLAN, enable jumbo frames for the iSCSI ports before you create the VLAN. See “Making iSCSI Data Port Settings” on page 62.

To create a VLAN entry:

1. Click the Subsystem icon in Tree View.
2. Click the Administrative Tools icon.
3. Click the Network Management icon.
4. In Management View, from the dropdown menu on the VLAN tab, choose Create VLAN Entry.
5. Enter a name into the VLAN Name field. Maximum of 15 characters. Use letters, numbers, space between words and underscore.
6. Enter the following information the respective boxes:

• VLAN Tag number (2 to 4094)
• IP Address of the VLAN
- Subnet Mask of the VLAN. (255.255.255.0 is the default)
- TCP Port number. (3260 is the default)

1. To enable jumbo frames on the VLAN, check the Jumbo Frame box.
2. From the dropdown menu, choose a Member Interface.

If you have link aggregation, choose the Trunk number.

If you do NOT have a link aggregation, choose an iSCSI port number.

1. Click the Submit button.

Changing a VLAN Entry

To change a VLAN entry:

1. Click the Subsystem icon in Tree View.
2. Click the Administrative Tools icon.
3. Click the Network Management icon.
4. In Management View, click the VLAN tab.
5. Click the VLAN Tag link of the VLAN you want to change.
6. Enter the following information the respective boxes:

• VLAN Tag number (2 - 4094)
• IP Address of the VLAN
- Subnet Mask of the VLAN. 255.255.255.0 is the default
- TCP Port number. 3260 is the default

1. To enable jumbo frames on the VLAN, check the Jumbo Frame box.
2. From the dropdown menu, choose a Member Interface.

If you have link aggregation, choose the Trunk number. If you do not have a link aggregation, choose an iSCSI port number.

1. Click the Submit button.

Deleting a VLAN Entry

To delete a VLAN entry:

1. Click the Subsystem icon in Tree View.
2. Click the Administrative Tools icon.
3. Click the Network Management icon.
4. In Management View, from the dropdown menu on the VLAN tab, choose Delete VLAN Entry.
5. Check the box to the left of the VLAN entry you want to delete.
6. Click the Submit button.

Viewing Link Aggregation Entries

To view the current Link Aggregation entries:

1. Click the Subsystem icon in Tree View.
2. Click the Administrative Tools icon.
3. Click the Network Management icon.
4. Click the Link Aggregation tab in Management View.

Creating a Link Aggregation Entry

This feature enables you to aggregate the iSCSI data ports on your subsystem to increase bandwidth.

If an iSCSI port is part of a VLAN, you must delete the VLAN entry before you can use the iSCSI port to create a link aggregation. See “Deleting a VLAN Entry” on page 65.

To create a link aggregation entry:

1. Click the Subsystem icon in Tree View.
2. Click the Administrative Tools icon.
3. Click the Network Management icon.
4. In Management View, from the dropdown menu on the Link Aggregation tab, choose Create Link Aggregation Entry.
5. Enter a Trunk ID number.

Use 1 to 32.

1. From the Master Port dropdown menu, choose an iSCSI port number.
2. From the Slave Port dropdown menu, choose the other iSCSI port number.
3. Click the Submit button.

Changing a Link Aggregation Entry

To change a link aggregation entry:

1. Click the Subsystem icon in Tree View.
2. Click the Administrative Tools icon.
3. Click the Network Management icon.
4. In Management View, click the Link Aggregation tab.
5. Click the ID link of the link aggregation you want to change.
6. From the Master Port dropdown menu, choose an iSCSI port number.
7. From the Slave Port dropdown menu, choose the other iSCSI port number.
8. Click the Submit button.

Deleting a Link Aggregation Entry

To delete a link aggregation entry:

1. Click the Subsystem icon in Tree View.
2. Click the Administrative Tools icon.
3. Click the Network Management icon.
4. In Management View, from the dropdown menu on the Link Aggregation tab, choose Delete Link Aggregation Entry.
5. Check the box to the left of the link aggregation entry you want to delete.
6. Click the Submit button.

Managing iSCSI Connections

A detailed explanation of these iSCSI functions, how and when they are used, and their relationship to one another is beyond the scope of this document. For more information, contact the Internet Engineering Task Force at http://www.ietf.org/.

Functions include:

• Viewing Node Information (page 67)
• Making Node Settings (page 68)
• Viewing Target Port Information (page 69)
  • Viewing Data Port Statistics (page 69)
  • Viewing Portal Information (page 70)
• Viewing Session Information (page 70)
• Viewing iSNS Information (page 70)
• Making iSNS Settings (page 71)
• Viewing CHAPs (page 71)
• Adding CHAPs (page 71)
• Editing CHAPs (page 72)
• Deleting CHAPs (page 72)
• Pinging iSCSI Connections (page 72)

Viewing Node Information

To view iSCSI node information:

1. Click the Subsystem icon in Tree View.
2. Click the Administrative Tools icon.
3. Click the iSCSI Management icon.

The iSCSI Management-iSCSI Node tab enables you to see the current Data Port settings on the Controller, including:

• Maximum number of nodes supported
• Number of nodes present
• Number of failed nodes
- Node ID
- Node Name – An iSCSI node is identified by its name
- Node Alias – Maximum of 32 characters. Use letters, numbers, space between words, and underscore. An alias is optional

• Max outstanding R2T – Sets the maximum number of outstanding ready to transfer PDUs (a number)
• Maximum burst length – Maximum length of a solicited data sequence 128 KB to 16,776,704 bytes (16 MB - 512 KB)
• Maximum number of connections – Maximum number of connections supported
• Default time to wait – After a dropped connection, the number of seconds to wait before attempting to reconnect
• Default time to retain – Number of seconds after time to wait (above) before reassigning outstanding commands
• Error recovery level – Error recovery level supported
• Initial R2T – Allows initiator to begin sending data to a target without receiving a ready to transfer command
• Header Digest – Enables the use of Header Digest (CRC). See note below
• Data Digest – Enables the use of a Data Digest (CRC). See note below
• Data PDU in order – Enables placement of data in PDU order
• Data sequence in order – Enables placement of data in sequence order
• Uni-directional CHAP Authentication – Enables Challenge Handshake Authentication Protocol
• Bi-directional CHAP Authentication – Enables bi-directional and unidirectional CHAP authentication

Making Node Settings

The settings made here apply to both iSCSI data ports.

To make iSCSI data port settings:

1. Click the Subsystem icon in Tree View.
2. Click the Administrative Tools icon.
3. Click the iSCSI Management icon.
4. Click the iSCSI Node 1 link in Management View.

5. Optional. Type an alias in the Alias field. Maximum of 32 characters. Use letters, numbers, space between words, and underscore. An alias is not required.

6. Enter the values in the fields as required.

7. Check the boxes to enable features as required.
8. Click the Submit button.

Notes

Header Digest and Data Digest work best with initiators equipped with a TCP Offload Engine (TOE). Refer to your iSCSI HBA user manual for more information.

For iSCSI network settings on the Data Ports, see "Making iSCSI Data Port Settings" on page 62.

Viewing Target Port Information

To view iSCSI port target information:

1. Click the Subsystem icon in Tree View.
2. Click the Administrative Tools icon.
3. Click the iSCSI Management icon.
4. Click the Port Target tab in Management View.

Information (in GUI order):

• Controller ID - 1
• Port ID - 1 or 2
• Max Receive Data Segment Length – 8 KB is the default
• Number of Active Sessions – Number of sessions logged into this port
• Primary Header Digest Method – CRC-32
  • Primary Data Digest Method – CRC-32
• iSCSI Receive Marker – None

Viewing Data Port Statistics

To view iSCSI port statistics:

1. Click the Subsystem icon in Tree View.
2. Click the Administrative Tools icon.
3. Click the iSCSI Management icon.
4. From the Port Target tab dropdown menu in Management View, choose Port Statistics.

The data port statistics are displayed.

Viewing Portal Information

To view iSCSI portal information:

1. Click the Subsystem icon in Tree View.
2. Click the Administrative Tools icon.
3. Click the iSCSI Management icon.
4. Click the Portal tab in Management View.

Information (in GUI order):

• Portal ID - 1 to 34
• IIP Address – IP address of the port or VLAN
• Associated Type – iSCSI or VLAN
• Interface Name – Port number or VLAN name
• TCP port number – 3260 is the default

Also see “Making iSCSI Data Port Settings” on page 62 and “Viewing VLAN Entries” on page 63.

Viewing Session Information

To view iSCSI session information:

1. Click the Subsystem icon in Tree View.
2. Click the Administrative Tools icon.
3. Click the iSCSI Management icon.
4. Click the Sessions tab in Management View.

The window displays session information.

Viewing iSNS Information

Internet Storage Name Service (iSNS) is a protocol used to facilitate the automated discovery, management, and configuration of iSCSI and Fibre Channel devices on a TCP/IP network.

To view iSCSI iSNS information:

1. Click the Subsystem icon in Tree View.
2. Click the Administrative Tools icon.
3. Click the iSCSI Management icon.
4. Click the iSNS tab in Management View.

Making iSNS Settings

To make iSCSI iSNS settings:

1. Click the Subsystem icon in Tree View.
2. Click the Administrative Tools icon.
3. Click the iSCSI Management icon.
4. Click the iSNS tab in Management View.
5. Click the iSNS link.
6. Check the box to enable iSNS.
7. Enter the iSNS server IP address.
8. Enter a new iSNS Port number if required.
   Use 1 to 65535.
9. Click the Submit button.

Viewing CHAPs

Challenge Handshake Authentication Protocol (CHAP) is an authentication agent (typically a network server) sends the client program a random value and an ID value. Both the sender and peer share a predefined secret. The peer concatenates the random value, the ID, and the secret and calculates a one-way hash value. The hash value is sent to the authenticator, which in turn builds that same string on its side, calculates the sum, and compares the result with the value received from the peer. If the values match, the peer is authenticated.

To view iSCSI CHAPs:

1. Click the Subsystem icon in Tree View.
2. Click the Administrative Tools icon.
3. Click the iSCSI Management icon.
4. Click the CHAP tab in Management View.
   The window displays CHAP information.

Adding CHAPs

1. Click the Subsystem icon in Tree View.
2. Click the Administrative Tools icon.
3. Click the iSCSI Management icon.
4. Click the CHAP tab in Management View.

Editing CHAPs

1. Click the Subsystem icon in Tree View.
2. Click the Administrative Tools icon.
3. Click the iSCSI Management icon.
4. From the CHAP tab dropdown menu, choose Add CHAP.
5. Enter a name in the Name field.
6. Enter a secret of 16 or more characters in the Secret field.
7. Enter the secret again in the Retype Secret field.
8. Select the CHAP type.

Peer to peer is one-way authentication. Local is bi-directional authentication.

1. Click the Submit button.

Deleting CHAPs

1. Click the Subsystem icon in Tree View.
2. Click the Administrative Tools icon.
3. Click the iSCSI Management icon.
4. From the CHAP tab dropdown menu, choose Delete CHAP.
5. Check the box to the left of the CHAP you want to delete.
6. Click the Submit button.

Pinging iSCSI Connections

This function enables you to ping other network nodes (PCs, servers, etc.) through VTrak's iSCSI data ports.

To ping an iSCSI connection:

1. Click the Subsystem icon in Tree View.
2. Click the Administrative Tools icon.
3. Click the iSCSI Management icon.
4. Click the Ping tab in Management view.
5. Enter the IP address you want to ping in the IP Address field.
6. Select the data port (1 or 2) from the Ping Through Port dropdown menu.
7. Click the Submit button.

After a few moments, the result displays in the iSCSI Ping Operation header.

Managing Storage Services

The Storage Services–LUN Map tab displays the Target IDs and LUNs assigned to each logical drive.

For iSCSI, LUN masking is the process of applying a LUN Map so that each initiator can only access the LUNs specified for it.

Features include:

• Adding an Initiator (page 73)
• Deleting an Initiator (page 73)
• Viewing a LUN Map (page 74)
• Enabling LUN Masking (page 74)
• Adding a LUN Map (page 74)

Adding an Initiator

To add an initiator:

1. Click the Subsystem icon in Tree View.
2. Click the Administrative Tools icon.
3. Click the Storage Services icon.
4. From the Initiators tab dropdown menu, choose Add Initiator.
5. Enter the initiator's initiator's name in the Initiator Name field.

An iSCSI initiator name is the iSCSI name of the initiator device and is composed of a single text string. iSCSI WWNs are somewhat different from regular WWNs.

Obtain the initiator name from the initiator utility on your host system.

Note that the initiator name you input must match exactly in order for the connection to work.

1. Click the Submit button.

Deleting an Initiator

To delete an initiator:

1. Click the Subsystem icon in Tree View.
2. Click the Administrative Tools icon.

3. Click the Storage Services icon.

4. From the Initiators tab dropdown menu, choose Delete Initiator.

5. Check the box to the left of the initiator you want to delete.

6. Click the Submit button.

Viewing a LUN Map

To view the current LUN Map:

1. Click the Subsystem icon in Tree View.
2. Click the Administrative Tools icon.
3. Click the Storage Services icon.
4. Click the LUN Map tab in Management View.

Enabling LUN Masking

LUN Masking is the process of applying a LUN Map so that each initiator can only access the LUNs specified for it.

To enable LUN Masking:

1. Click the Subsystem icon in Tree View.
2. Click the Administrative Tools icon.
3. Click the Storage Services icon.
4. Click the LUN Map tab in Management View.
5. Check the Enable LUN Masking box.
6. Click the Submit button.

Adding a LUN Map

To add a LUN map:

1. Click the Subsystem icon in Tree view.
2. Click the Administrative Tools icon.
3. Click the Storage Services icon.
4. in Management View, from the LUN Map tab dropdown menu, choose Add LUN Map.
5. Select an initiator from the Initiator dropdown menu.
   Or enter the initiator's WWN in the Initiator Name field.
   Obtain the initiator name from the initiator utility on your host system.
   Note that the initiator name you input must match exactly in order for the connection to work.
6. Click the Submit button.

• Initiator – The iSCSI card in the Host system that initiates commands to the target (VTrak)
• Initiator Name – A World Wide Name (WWN), used to identify the Initiator. An iSCSI initiator name is the iSCSI name of the initiator device and is composed of a single text string. iSCSI WWNs are somewhat different from regular WWNs.
• Logical Drive ID – The disk array ID number
• RAID Level – RAID Level of the logical drive
• Capacity – Capacity of the logical drive
• Serial Number – Serial number of the logical drive
• WWN – World Wide Name, used for the Initiator name
• LUN – Logical Unit Number on this logical drive for the selected initiator. Each logical drive has a unique LUN

Managing Software Services

Software Services include the following functions:

• Making Email Settings (page 76)
• Making SLP Settings (page 77)
• Making Web Server Settings (page 77)
• Making Telnet Settings (page 79)
• Making SNMP Settings (page 79)
• Making CIM Settings (page 81)
• Making Netsend Settings (page 82)

Making Email Settings

The Email sends notification messages to users. See Setting-up User Event Subscriptions (page 58).

To make Email service settings:

1. Click the Subsystem icon in Tree View.
2. Click the Administrative Tools icon.
3. Click the Email Setting link in Management View.
4. Enter the IP address for your SMTP server.
5. Enter server port number for your SMTP server. 25 is the default.
6. Select Yes to enable SMTP authentication or No to Yes.
7. If you selected Yes for SMTP authentication, enter a Username and Password in the fields provided.
8. Enter an Email sender address (example: [e-mail]).
9. Enter an Email subject (example: VTrak Status).
10. Click the Submit button.

Sending a Test Message

To send one test message to the User currently logged into WebPAM PROe:

1. Under Test Email, check the "Send A Test Email" box.

2. Click the Submit button.

If you do not receive the Test Email message, see your Network Administrator for assistance with the mail server setup, email accounts, and other issues.

Changing the Startup Setting

1. Under Startup Type:

2. Click the Automatic option to start the service automatically during system startup. Recommended.

3. Click the Manual option to start the service manually (the service does not start during system startup).

4. Click the Submit button.

Stopping Email service

To stop the Email service:

1. Click the Stop button.
2. Click OK in the confirmation box.

Starting or Restarting Email service

To start or restart the Email service, click the Start or Restart button.

Making SLP Settings

VTrak's SLP service discovers services available over the Internet. To make SLP service settings:

1. Click the Subsystem icon in Tree View.
2. Click the Administrative Tools icon.
3. Click the Software Management icon.
4. Click the SLP link.
5. Choose the Startup Type.

- Click the Automatic option to start the service automatically during system startup. Recommended.

- Click the Manual option to start the service manually (the service does not start during system startup).

1. Click the Submit button.

Stopping SLP service

To stop the SLP service:

1. Click the Stop button.
2. Click OK in the confirmation box.

Starting or Restarting SLP service

To start or restart the SLP service, click the Start or Restart button.

Making Web Server Settings

VTrak's Web Server service connects the VTrak GUI to the VTrak subsystem though your browser.

To make Web Server settings:

1. Click the Subsystem icon in Tree View.
2. Click the Administrative Tools icon.
3. Click the Web Server Setting link in Management View.
4. Enter the HTTP Port number.

80 is the default.

1. Enter Session Time Out interval.

This setting causes WebPAM PROe to timeout after a period of inactivity. 24 minutes is the default. The range is 1 to 1440 minutes (one day).

1. If you want to use a secure connection, check the Enable SSL box.
2. If you checked the Enable SSL box, enter a HTTPS Port number.

443 is the default.

1. If you want to download a SSL Certificate, check the Download Certificate box.
2. If you checked the Download Certificate box, enter the Certificate filename or click the Browse... button to locate it.
3. Click the Submit button.
4. Click OK in the confirmation box to restart the Web Server service with your changes.

Changing the Startup Setting

1. Under Startup Type:

2. Click the Automatic option to start the service automatically during system startup. Recommended.

3. Click the Manual option to start the service manually (the service does not start during system startup).

4. Click the Submit button.

Stopping Web Server service

To stop the Web Server service:

1. Click the Stop button.
2. Click OK in the confirmation box.

Starting or Restarting Web Server service

To start or restart the Web Server service, click the Start or Restart button.

Making Telnet Settings

VTrak's Telnet service enables you to access VTrak's Command Line Interface (CLI) through a network connection. To make Telnet settings:

1. Click the Subsystem icon in Tree View.
2. Click the Administrative Tools icon.
3. Click the Telnet Setting link in Management View.
4. Enter the Telnet Port number.

2300 is the default.

1. Enter the Maximum Number of Connections.
   4 is the default.
2. Enter the Session Time Out interval.
   24 minutes is the default.
3. Click the Submit button.
4. Click OK in the confirmation box to restart the Telnet service with your changes.

Changing the Startup Setting

1. Under Startup Type:

2. Click the Automatic option to start the service automatically during system startup. Recommended.

3. Click the Manual option to start the service manually (the service does not start during system startup).

4. Click the Submit button.

Stopping Telnet service

To stop the Telnet service:

1. Click the Stop button.
2. Click OK in the confirmation box.

Starting or Restarting Telnet service

To start or restart the Telnet service, click the Start or Restart button.

Making SNMP Settings

VTrak's SNMP service enables the SNMP browser to obtain information from the VTrak. The Trap Sink is where SNMP events are sent and can be viewed.

To change the SNMP settings:

1. Click the Subsystem icon in Tree View.
2. Click the Administrative Tools icon.
3. Click the SNMP Management link in Management View.
4. Enter the SNMP Port number.

161 is the default.

1. Enter a System Name.
   There is no default name.
2. Enter a System Location.

USA is the default.

1. Enter a System Contact (the email address of the administrator or other individual).
2. Enter the Read Community.

Public is the default.

The Write Community is always Private.

To add a Trap Sink, see "Adding Trap Sinks" below.

1. Click OK in the confirmation box to restart the SNMP service with your changes.

Adding Trap Sinks

To add a trap sink:

1. Enter a Trap Sink IP address.
2. Select a Trap Filter, select the lowest level of Severity to be reported for each event.

See “Setting-up User Event Subscriptions” on page 58 for an explanation of the Severity levels.

1. Click the Update button.

The new trap sink appears in the Trap Sinks list.

1. Click the Submit button.
2. Click OK in the confirmation box.

Deleting Trap Sinks

To delete a trap sink:

1. Highlight the trap sink you want to delete from the list.
2. Click the Delete button to remove the trap sink from the list.
3. Click the Submit button.
4. Click OK in the confirmation box.

Changing the Startup Setting

1. Under Startup Type:

• Click the Automatic option to start the service automatically during system startup. Recommended.

• Click the Manual option to start the service manually (the service does not start during system startup).

• Click the Submit button.

Stopping SNMP service

To stop the SNMP service:

1. Click the Stop button.
2. Click OK in the confirmation box.

Starting or Restarting SNMP service

To start or restart the SNMP service, click the Start or Restart button.

Making CIM Settings

VTrak's CIM (Common Information Model [a protocol]) service provides a database for information about computer systems and network devices.

To change the CIM settings:

1. Click the Subsystem icon in Tree View.
2. Click the Administrative Tools icon.
3. Click the CIM Setting link in Management View.
4. Click the Start button to start the CIM service.

5. To enable CIM using a HTTP connection:

6. Choose the Yes option

7. Enter a port number in the field provided (5988 is the default)

8. To enable CIM using a HTTPS connection:

9. Choose the Yes option

10. Enter a port number in the field provided (5989 is the default)

11. To enable authentication for your CIM connection(s):

12. Choose the Yes option

13. Enter the old password in the field provided (password is the default)
14. Enter a new password in the field provided

To change your password, the CIM service must be running. See “Starting or Restarting CIM service” on page 82.

There is only one user. The default name is "cim." No changes are possible.

1. Click the Submit button.

Changing the Startup Setting

1. Under Startup Type:

2. Click the Automatic option to start the service automatically during system startup. Recommended.

3. Click the Manual option to start the service manually (the service does not start during system startup).

4. Click the Submit button.

Stopping CIM service

To stop the CIM service:

1. Click the Stop button.
2. Click OK in the confirmation box.

Starting or Restarting CIM service

To start or restart the CIM service, click the Start or Restart button.

Making Netsend Settings

VTrak's Netsend service sends VTrak subsystem events in the form of text messages to your Host PC and other networked PCs. This service is normally Stopped and set to Manual start. See “Netsend Requirements” on page 83.

To change the Netsend settings:

1. Click the Subsystem icon in Tree View.
2. Click the Administrative Tools icon.
3. Click the Netsend link.
4. Click the Start button to start the Netsend service.
5. Click the Submit button.

Adding Netsend recipients

See "Netsend Requirements" on page 83. To add a Netsent recipient:

1. In the Recipient Address field, type the IP address of the recipient PC.

2. Under Recipient filter, select the lowest level of Severity to be reported for each event.
   See “Setting-up User Event Subscriptions” on page 58 for an explanation of the Severity levels.

3. Click the Update button to add the new recipient to the list

4. Click the Submit button.

5. Click OK in the confirmation box.

Deleting Netsend Recipients

To delete a Netsend recipient:

1. Highlight the recipient you want to delete in the recipient list.
2. Click the Delete button to remove the recipient from the list.
3. Click the Submit button.
4. Click OK in the confirmation box.

Changing the Startup Setting

1. Under Startup Type:

2. Click the Automatic option to start the service automatically during system startup. Recommended if you plan to use this feature.

3. Click the Manual option to start the service manually (the service does not start during system startup). The default setting.

4. Click the Submit button.

Stopping Netsend service

To stop the Netsend service:

1. Click the Stop button.
2. Click OK in the confirmation box.

Starting or Restarting Netsend service

To start or restart the Netsend service, click the Start or Restart button.

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 PC's Firewall settings. Refer to your OS documentation for more information.

Exporting the User Database

You can export the User Database file to share user information and settings among multiple VTrak subsystems.

The Export action saves a text file a designated folder the Host PC. From there, you can import the User Database file to other VTrak subsystems.

To export the User Database file:

1. Click the Subsystem icon in Tree View.
2. Click the Administrative Tools icon.
3. Click the Export link in Management View.
4. Click the Export button.
5. In the Opening export dialog box, click the Save to Disk option.
6. Click the OK button.

The user database file is saved to the Host PC from which you access WebPAM PROe.

Note

The Encryption box is grayed out. Encryption is always enabled.

Importing a User Database

Caution

Do NOT use this function to update the VTrak firmware.

The Software Management–Import tab enables you to import the User Database file from the Host PC's file system to the VTrak subsystem. When you make user settings to one VTrak, you can export the User Database file to the Host PC. From there, you can import the User Database file to other VTrak s so that all have the same User information and settings.

To import the User Database file to this subsystem:

1. Click the Subsystem icon in Tree View.
2. Click the Administrative Tools icon.
3. Click the Software Management icon.
4. Click the Import tab.
5. Under the Type dropdown list, choose User Database.
6. Enter the name of the file to be imported.

Or, click the Browse... button to search for the file.

Look for a file called export.

1. Click the Submit button.
2. Click the Next button.

If the imported file is a valid user database, an warning will appear to inform you that it will overwrite the previous settings.

1. In the Warning box, click the OK button.

This user settings are applied to this VTrak subsystem.

Note

The Decryption box is grayed out. Decryption is always enabled.

Updating the Firmware

This procedure is covered in Chapter 6: Maintenance. See “Updating the Firmware in WebPAM PROe” on page 199 for instructions.

Restoring Factory Defaults

VTrak includes a function to restore the default settings to its Firmware and Software settings.

Caution

The action of restoring default settings can disrupt your VTrak functions. Use this feature only when necessary and only the settings that must reset to default in order to set them correctly.

To access the Restore Defaults feature:

1. Click the Subsystem icon in Tree View.
2. Click the Administrative Tools icon.

The Administrative Tools list appears.

1. Click the Restore Factory Defaults link at the bottom of the list in Management View.

The Restore Factory Defaults screen appears.

1. Check the Firmware and Software functions you want to restore to default settings.
2. Click the Submit button.
3. In the confirmation box, type the word confirm in the field provided.
4. Click the OK button.

The functions you selected will be automatically restored to their default settings.

Clearing Statistics

The Clear Statistics function clears statistical data on controllers, iSCSI ports, physical drives, and logical drives. To clear statistical data:

1. Click the Subsystem icon in Tree View.
2. Click the Administrative Tools icon.
3. Click the Clear Statistics link.

The Clear Statistics tab appears in Management View.

1. Click the Submit button.
2. In the confirmation box, type the word confirm in the field provided.
3. Click the OK button.

Shutting Down the Subsystem

You can only do part of this function in WebPAM PROe. Additional action is required, as described below. To shutdown the subsystem:

1. Click the Subsystem icon in Tree View.
2. Click the Administrative Tools icon.
3. Click the Shutdown link in Management View.

A Shutdown or Restart tab will appear.

1. On the Shutdown or Restart tab, choose Shutdown from the dropdown menu.
2. Click the Submit button.
3. In the confirmation box, type the word confirm in the field provided.
4. Click the OK button.

When the controller shuts down, your WebPAM PROe connection will be lost.

1. Wait for no less than two minutes.
2. Manually turn off the power supply switches the back of the subsystem.

Monitoring the Shutdown

To monitor a shutdown, you must use the Command Line Interface (CLI) though a serial connection to the VTrak.

At the "administrator@CLI>" prompt, type shutdown -a shutdown.

When the “Shutdown complete. It is now safe to power off the subsystem.” message appears, turn off the power supply switches.

Restarting the Subsystem

You can only do part of this function in WebPAM PROe. Additional action is required, as described below. To restart the subsystem

1. Click the Subsystem icon in Tree View.
2. Click the Administrative Tools icon.
3. Click the Shutdown link in Management View.

A Shutdown or Restart tab will appear.

1. On the Shutdown or Restart tab, choose Restart from the dropdown menu.
2. Click the Submit button.
3. In the warning box, click the OK button.
4. In the confirmation box, type the word confirm in the field provided.
5. Click the OK button.

When the controller shuts down, your WebPAM PROe connection will be lost.

1. Wait for two to three minutes.
2. In your browser, log into WebPAM PROe once again.

If you cannot log in, wait for 30 seconds, and try again. Repeat until login is successful.

Monitoring the Restart

To monitor a restart, you must use the Command Line Interface (CLI) though a serial connection to the VTrak.

At the “administrator@CLI>” prompt, type shutdown -a restart.

When the "Login:" prompt appears, the restart is finished.

Managing Controllers

The RAID controller is are the heart of the VTrak subsystem. Controller Management includes the following functions:

• Viewing the Controller (page 91)
• Locating a Controller (page 91)
• Viewing Controller Information (page 92)
  • Viewing Controller Statistics (page 93)
• Making Controller Settings (page 93)

Viewing the Controller

To view information about the controller:

1. Click the Subsystem icon in Tree View.
2. Click the Controllers icon.
   The controller information appears under the Information tab in Management View. Controller information includes:
3. Controller ID (1)
4. Alias, if assigned
5. Model, if applicable
6. Status – OK means normal
7. Readiness Status – Active or Standby
8. Locate – Click the button to locate the controller. See below

VTrak subsystems, such as the M610i, M310i, and M210i, with only one controller will always show that the second controller is “Missing.”

Locating a Controller

To identify a specific controller in the VTrak subsystem:

1. Click the Subsystem icon in Tree View.
2. Click the Controllers icon.
3. In Management View, click the Locate Controller button.
4. The Controller Dirty Cache LED and Status LED on the back of the Controller, will flash for one minute. See the illustrations below.

Figure 9. The VTrak M610i controller LEDs

Viewing Controller Information

To view Controller information:

1. Click the Subsystem icon in Tree View.
2. Click the Controllers icon.
3. Click the Controller icon.

The controller information appears the Information tab in Management View.

Adjustable items

You can set or adjust the following items:

• Alias, if assigned
  • Coercion, enable or disable
• Coercion Method
• SMART – Self-Monitoring, Analysis, and Reporting System for physical drives.
  • SMART Polling Interval
  • Write Back Cache Flush Interval
  • Enclosure Polling Interval
  See "Making Controller Settings" on page 93.

Upgradable items

You can upgrade the following items:

• Boot loader Version
• Firmware Version number
• Software Version number
• Memory Size

See "Chapter 6: Maintenance" on page 199.

Viewing Controller Statistics

To view controller statistics:

1. Click the Subsystem icon in Tree View.
2. Click the Controllers icon.
3. Click the Controller icon.
4. Click the Information tab in Management View and choose Statistics from dropdown menu.

Clearing Statistics

To clear statistics, see "Clearing Statistics" on page 88.

Making Controller Settings

To make Controller settings:

1. Click the Subsystem icon in Tree View.
2. Click the Controllers icon.
3. Click the Controller icon.
4. Click the Settings tab in Management View.
5. Make the following settings as needed:

- Enter a name into the Alias field.

Maximum of 48 characters. Use letters, numbers, space between words, and underscore. An alias is optional.

• Check the SMART Log box to enable the Self-Monitoring, Analysis, and Reporting System (SMART).
• Enter a polling interval (1 to 1440 minutes) in SMART Polling Interval field.
• Check the Coercion Enabled box to enable disk drive capacity coercion.

When disk drives of different capacities are used in the same array, coercion reduces the usable capacity of the larger disk drive(s) in order to match the smallest capacity drive.

For more information, see "Capacity Coercion" on page 233.

- Select a coercion method from the Coercion Method dropdown menu. 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.

- Enter a time interval (1 to 12 seconds) in the Write Back Cache Flush Interval field.

For more information, see "Cache Policy" on page 232.

- Enter a time interval (15 to 255 seconds) in the Enclosure Polling Interval field.

- Check the Adaptive Writeback Cache box to enable the Adaptive Writeback Cache feature.

For more information, see “Adaptive Writeback Cache” on page 232.

1. Click the Submit button.

The changes take effect immediately.

Managing Enclosures

Enclosure Management includes the following functions:

• Viewing the Enclosures (page 95)
- Locating an Enclosure (page 95)
- Viewing Enclosure Information (page 96)
- Making Enclosure Settings (page 97)
• Viewing FRU VPD Information (page 97)
- Checking the Batteries (page 97)
- Reconditioning a Battery (page 98)
• Silencing the Buzzer (page 99)
- Making Buzzer Settings (page 99)
- Testing the Buzzer (page 99)

Viewing the Enclosures

To view information about the enclosures:

1. Click the Subsystem icon in Tree View.
2. Click the Enclosures icon.

The following information is shown:

• Enclosure ID number
• Enclosure Type
• Operational Status
• Status Description – Specific components in need of attention, if any

Locating an Enclosure

To locate an enclosure (subsystem):

1. Click the Subsystem icon in Tree View.
2. Click the Enclosures icon.
3. Click the Locate Enclosure button.

The Disk Status LEDs on the front of the enclosure will flash for one minute. See the illustrations below.

Figure 11. VTrak M610i front view

Figure 12. VTrak drive carrier LEDs

Viewing Enclosure Information

To view enclosure information:

1. Click the Subsystem icon in Tree View.
2. Click the Enclosures icon.
3. Click the Enclosure icon.

Enclosure information appears the Information tab in Management View. You can monitor power supplies, cooling units, enclosure temperatures and voltages, and the battery.

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" on page 97.

For information on Enclosure problems, see "Chapter 8: Troubleshooting" on page 243.

Making Enclosure Settings

To make Enclosure settings:

1. Click the Subsystem icon in Tree View.
2. Click the Enclosures icon.
3. Click the Enclosure icon.
4. Click the Settings tab in Management View.
5. Enter a value in the following fields as necessary:

• Enclosure Warning Temperature Threshold
• Enclosure Critical Temperature Threshold
- Controller Warning Temperature Threshold
- Controller Critical Temperature Threshold

1. Click the Submit button.

The changes take effect immediately.

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. Click the Subsystem icon in Tree View.
2. Click the Enclosures icon.
3. Click the Enclosure icon.
4. Click the FRU VPD tab in Management View.

Use this information when communicating with Technical Support and when ordering replacement units. For contact information, see “Contacting Technical Support” on page 285.

Checking the Batteries

The Enclosure–Battery tab displays information about the cache backup battery (or batteries) in the VTrak subsystem enclosure. To check the batteries:

1. Click the Subsystem icon in Tree View.
2. Click the Enclosures icon.
3. Click the Enclosure icon.
4. Click the Battery tab in Management View.

Battery Notes

Each battery works with a controller. If the battery is present in the subsystem but the corresponding controller is not present, the battery will not appear in the interface.

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 98.

During reconditioning, the battery is fully discharged then fully recharged. During that time, if the Adaptive Writeback Cache function is enabled, the controller cache is reset to Write Thru. After conditioning, the cache is set to Write Back. See “Making Controller Settings” on page 93.

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 Battery” on page 211.

VTrak automatically reconditions the battery every two months. To set the schedule, see “Scheduling an Activity” on page 53.

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.

Reconditioning a Battery

To recondition the battery:

1. Click the Subsystem icon in Tree View.
2. Click the Enclosures icon.
3. Click the Enclosure icon.
4. In Management View, from the Battery tab dropdown menu, choose Recondition.
5. Click the Submit button.

During reconditioning, Battery status can show “discharging” and “recharging”, and a value will display next to Current. During that time, the controller cache is reset to Write Thru. Reconditioning runs in the background and stops automatically upon completion.

VTrak automatically reconditions the battery every two months. To set the recondition schedule, see “Scheduling an Activity” on page 53.

Silencing the Buzzer

The buzzer sounds to inform you that the VTrak needs attention. See “VTrak is Beeping” on page 244 for more information.

You can silence the buzzer for the current trigger event.

To silence the Buzzer:

1. Click the Subsystem icon in Tree View.
2. Click the Enclosures icon.
3. Click the Enclosure icon.
4. Click the Buzzer tab in Management View.
5. Click the Mute button.

The buzzer goes silent. If another trigger event occurs, the buzzer will sound again.

Making Buzzer Settings

To make buzzer settings:

1. Click the Subsystem icon in Tree View.
2. Click the Enclosures icon.
3. Click the Enclosure icon.
4. In Management View, from the Buzzer tab dropdown menu, choose Settings.
5. Check the Buzzer Enable box to enable the buzzer. Uncheck the Buzzer Enable box if you do not want the buzzer to sound.
6. Click the Submit button.

Testing the Buzzer

To test buzzer function:

1. Click the Subsystem icon in Tree View.
2. Click the Enclosures icon.
3. Click the Enclosure icon.
4. Click the Buzzer tab in Management View.
5. Click the Sound button.

The buzzer will sound for one minute.

Managing Physical Drives

Managing Physical Drives deals with the physical disk drives installed in the VTrak subsystem enclosure, including the following functions:

• Viewing a List of Physical Drives (page 100)
• Identifying a Physical Drive (page 100)
• Making Global Physical Drive Settings (page 100)
• Viewing Physical Drive Information (page 101)
• Viewing Physical Drive Statistics (page 102)
• Making Physical Drive Settings (page 102)
• Clearing Stale and PFA Conditions (page 102)
• Forcing a Physical Drive Offline or Online (page 103)

Viewing a List of Physical Drives

To view a list of physical drives in this enclosure:

1. Click the Subsystem icon in Tree View.
2. Click the Enclosures icon.
3. Click the Enclosure icon.
4. Click the Physical Drives icon.

The list of physical drives appears in Management View.

Identifying a Physical Drive

To identify physical drive in the VTrak subsystem enclosure:

1. Click the Subsystem icon in Tree View.
2. Click the Enclosures icon.

3. Click the Enclosure icon.

4. Click the Physical Drives icon.

5. In Management View, click the physical drives in the graphic.

The location of the physical drive is highlighted in the Enclosure Front View diagram.

Making Global Physical Drive Settings

Global settings apply to all of the physical disk drives installed in the VTrak subsystem enclosure. To make global physical drive settings:

1. Click the Subsystem icon in Tree View.

2. Click the Enclosures icon.

3. Click the Enclosure icon.

4. Click the Physical Drives icon.

5. Click the Global Settings tab in Management View.

6. Make the settings as needed.

Check the boxes to enable:

• Write Cache
• Read Look Ahead Cache
• Command Queuing (for disk drives that support Command Queuing)

• From the DMA Mode dropdown menu, select a DMA mode.

• Click the Submit button.

The functions you enable here depend on whether the physical drives support those functions. See “Viewing Physical Drive Information” on page 101 to determine which functions a particular drive supports.

Viewing Physical Drive Information

To view physical drive information:

1. Click the Subsystem icon in Tree View.
2. Click the Enclosures icon.
3. Click the Enclosure icon.
4. Click the Physical Drives icon.
5. Click a Physical Drive icon.

Useful information provided here includes:

• The location of the physical drive is highlighted in the Enclosure Front View diagram.
• Operational Status – OK is normal. Can also show Rebuilding, Forced Online, Forced Offline, Transition Running, PDM Running, Media Patrol Running, Stale, PFA, Offline, or Dead.
• Configuration Status – The array to which the drive is assigned or its spare designation, including Unconfigured, Stale, PFA, Global Spare, Dedicated Spare, Revertible Global Spare, Revertible Dedicated Spare.

Adjustable Items

• Write Cache
• Read Look Ahead Cache
• Command Queuing

- DMA Mode

See "Making Global Physical Drive Settings" on page 100.

Viewing Physical Drive Statistics

To view physical drive statistics:

1. Click the Subsystem icon in Tree View.
2. Click the Enclosures icon.
3. Click the Enclosure icon.
4. Click the Physical Drives icon.
5. Click a Physical Drive icon.
6. From the dropdown menu on the Information tab, choose Statistics.

Clearing Statistics

To clear statistics, see "Clearing Statistics" on page 88.

Making Physical Drive Settings

An alias is the only setting you can make to an individual physical drive. All other settings are global. See “Making Global Physical Drive Settings” on page 100.

To make physical drive settings:

1. Click the Subsystem icon in Tree View.
2. Click the Enclosures icon.
3. Click the Enclosure icon.
4. Click the Physical Drives icon.
5. Click a Physical Drive icon.
6. Click the Settings tab in Management View.
7. Type an alias into the Physical Drive Alias field.
   Maximum of 32 characters. Use letters, numbers, space between words, and underscore. An alias is optional.
8. Click the Submit button.

Clearing Stale and PFA Conditions

The Clear tab only appears when those conditions are present.

• 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. See “Physical Drive Problems” on page 273 for more information.

To clear a Stale or PFA status from a physical drive:

1. Click the Subsystem icon in Tree View.
2. Click the Enclosures icon.
3. Click the Enclosure icon.
4. Click the Physical Drives icon.
5. Click a Physical Drive icon.
6. in Management View, click the Clear tab.
7. In the Confirmation box, click OK to confirm.

Note

If a physical drive has both a Stale and a PFA condition, click the Clear tab once to clear the Stale condition, then click again to clear the PFA condition.

Forcing a Physical Drive Offline or Online

The Physical Drive–Force Offline/Online tab enables you to force an:

• Online physical drive to go Offline
- Offline physical drive to go Online

The Force Offline/Online tab 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.

Important

Forcing a physical drive offline will cause your logical drives to become degraded. If Auto Rebuild is enabled and a spare drive is available, the disk array will begin rebuilding itself automatically.

To force a physical drive offline or online:

1. Click the Subsystem icon in Tree View.

2. Click the Enclosures icon.

3. Click the Enclosure icon.

4. Click the Physical Drives icon.

5. Click a Physical Drive icon.

6. Click the Force Offline/Online tab in Management View.

7. Click the Submit button.

8. In the confirmation box, type the word confirm in the field provided.

9. Click the OK button.

Managing Disk Arrays

Disk Array Management includes the following functions:

• Viewing Disk Arrays (page 105)
• Creating a Disk Array (page 105)
• Deleting a Disk Array (page 109)
• Locating a Disk Array (page 110)
• Viewing Disk Array Information (page 110)
• Making Disk Array Settings (page 111)
• Creating a Logical Drive (page 111)
• Deleting a Logical Drive (page 113)
• Migrating a Disk Array (page 113)
• Rebuilding a Disk Array (page 114)
• Running PDM on a Disk Array (page 116)
  • Transitioning a Disk Array (page 116)
  • Preparing a Disk Array for Transport (page 117)

Viewing Disk Arrays

To view the disk arrays in this enclosure plus any expanded or cascaded enclosures:

1. Click the Subsystem icon in Tree View.

2. Click the Disk Arrays icon.

A list of disk arrays appears in Management View.

Click the DA link to view a specific disk array. See "Viewing Disk Array Information" on page 110.

Creating a Disk Array

The CLU provides three methods of creating a disk array:

• Automatic – Creates a default disk array and logical drive based on unconfigured physical drives in the system. No user choices. See “Creating a Disk Array – Automatic” on page 106.
• Express – You select the RAID characteristics and type of application. Creates a disk array and logical drive(s) based on your input. See “Creating a Disk Array – Express” on page 106.
• Advanced – You specify all parameters for a new disk array. One logical drive will be made automatically when you create the disk array. If you select less than the total available capacity, you can use the remaining space to

create additional logical drives at a later time. See "Creating a Disk Array – Advanced" on page 108.

Creating a Disk Array – Automatic

The Disk Array Automatic Creation option enables you to create a new disk array following a default set of parameters. One logical drive will be made automatically when you create the disk array. To create a Disk Array using the Automatic function:

1. Click the Subsystem icon in Tree View.
2. Click the Disk Arrays icon.
3. Click the Create tab in Management View.
4. From the Create tab dropdown menu, select Automatic.

The following parameters display:

• Disk Arrays – The number of physical drives in the disk array, their slot numbers, configurable capacity, and the number of logical drives to be created
• Logical Drives – The ID number of the logical drive(s), their RAID level, capacity, and stripe size

• Spare Drives – The physical drive slot number of the dedicated hot spare assigned to this disk array. A hot spare drive is created for all RAID levels except RAID 0, when five or more unconfigured physical drives are available

• If you accept these parameters, click the Submit button.

The new disk array appears in the Disk Array List the Information tab.

If you do NOT accept these parameters, use the Advanced option to create your disk array.

Creating a Disk Array – Express

The Disk Array Express Creation option enables you to choose the parameters for a new disk array by specifying the characteristics you want. With this method, you can create multiple logical drives at the same time you create your disk array. However, all of the logical drives will be the same.

If you prefer to specific the parameters directly, use the Advanced option to create your disk array.

If you are uncertain about choosing parameters for your disk array, use the Automatic option.

To create a new disk array:

1. Click the Subsystem icon in Tree View.
2. Click the Disk Arrays icon.
3. Click the Create tab in Management View.
4. From the Create tab dropdown menu, select Express.

5. Check the boxes to select any one or combination of:

6. Redundancy – The array will remain available if a physical drive fails
   • Capacity – The greatest possible amount of data capacity

7. Performance – The highest possible read/write speed

8. Spare Drive – A hot spare drive is created when you select Redundancy, Spare Drive, and five or more unconfigured physical drives are available

9. In the Number of Logical Drives field, enter the number of logical drives you want to make from this disk array.

10. From the Application Type menu, select an application that best describes your intended use for this disk array:

• Video Stream
• Transaction Data
• Transaction Log

• Other

• Click the Update button.

Or check the Automatic Update box and updates will occur automatically.

The following parameters display:

• Disk Arrays – The number of physical drives in the disk array, their slot numbers, configurable capacity, and the number of logical drives to be created
• Logical Drives – The slot number of the logical drive(s), their RAID level, capacity, and stripe size
• Spare Drives – The physical drive slot number of the dedicated hot spare assigned to this disk array (all RAID levels except RAID 0)

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.

1. When you are done, click the Submit button.

The new disk array appears in the Disk Array List the Information tab.

Creating a Disk Array – Advanced

The Disk Array Advanced Creation option enables you to directly specify all parameters for a new disk array. One logical drive will be made automatically when you create the disk array. If you select less than the total available capacity, you can use the remaining space to create additional logical drives at a later time.

If you are uncertain about choosing parameters for your disk array, use the Express or Automatic option to create your disk array.

To create a new disk array:

1. Click the Subsystem icon in Tree View.
2. Click the Disk Arrays icon.
3. From the Create tab dropdown menu, select Advanced.

Step 1 – Disk Array Creation

1. Enter an alias for the disk array in the field provided.
2. Check the box if you want to enable Media Patrol.

For more information, see "Media Patrol" on page 238.

1. Check the box if you want to enable PDM.

For more information, see "Predictive Data Migration (PDM)" on page 238.

1. Highlight physical drives you want in the disk array from the Available list and press the >> button to move them to the Selected list.

You can also double-click them to move them.

1. When you are done, click the Next button.

Step 2 – Logical Drive Creation

Logical Drive Creation enables you to specify logical drives under the new disk array. Enter the information for a logical drive, then click the Update button. If there is free capacity remaining, you can specify another logical drive now or wait until later.

1. Enter an alias for the logical drive in the field provided.
2. Choose a RAID level for the logical drive from the dropdown menu.

The choice of RAID levels depends the number of physical drives you selected.

1. RAID 50 – Specify the number of axles for your array.

For more information on axles, see "RAID 50 Axles" on page 226.

1. Specify a Capacity and the unit of measure (MB, GB, TB).

This value will be the data capacity of the first logical drive in your new disk array. If you specify less than disk array's maximum capacity, the remainder will be available for additional logical drives which you can create later.

1. Specify a Stripe size from the dropdown menu.

64 KB, 128 KB, 256 KB, and 1 MB are available. 64 KB is the default.

1. Specify a Sector size from the dropdown menu.

For iSCSI, use the 512 B default. See "Choosing Sector Size" on page 231.

1. Specify a Read (cache) Policy from the dropdown menu.

Read Cache, Read Ahead Cache, and No Cache are available. Read Ahead is the default.

1. Specify a Write (cache) Policy from the dropdown menu.

Write Back and Write Through (Thru) are available. Write Back is the default.

1. Click the Update button.

A new logical drive is displayed under New Logical Drives.

Repeat the above steps to specify additional logical drives as desired.

1. When you are done specifying logical drives, click the Next button.

Step 3 – Summary

The Summary lists the disk array and logical drive information you specified.

1. To proceed with disk array and logical drive creation, click the Submit button.

The new disk array appears in the Disk Array List the Information tab.

Note

This function does not automatically create a hot spare drive. After the disk array is created, you can create a hot spare drive for it. For more information, see “Creating a Spare Drive” on page 126.

Deleting a Disk Array

The Disk Arrays–Delete tab enables you to delete existing disk arrays.

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.

To delete a disk array:

1. Click the Subsystem icon in Tree View.

2. Click the Disk Arrays icon.

3. Click the Delete tab in Management View.

4. Check the box to the left of the disk array you want to delete.

5. Click the Submit button.
6. In the confirmation box, type the word confirm in the field provided.
7. Click the OK button.

The selected disk array disappears from the Disk Array List the Information tab.

Locating a Disk Array

To locate a Disk Array:

1. Click the Subsystem icon in Tree View.
2. Click the Disk Arrays icon.
3. Click the Disk Array icon.

In the diagram at the top of Management View, the crosshatched physical drives belong to the disk array.

1. Click the crosshatch pattern.

The disk status LEDs will blink for one minute.

Viewing Disk Array Information

To view Disk Array information:

1. Click the Subsystem icon in Tree View.
2. Click the Disk Arrays icon.
3. Click the Disk Array icon.

The disk array information is shown in Management View.

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.
• 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 will function and your data is available. However, access will be slower due to the synchronizing operation.

• Critical/Degraded – This condition arises as the result of a physical drive failure. A degraded logical drive will still function 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 will function and your data is available. However, access will be 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 will show OK.

Adjustable Items

• Alias – Optional.
  • Media Patrol – Enabled or disabled.
• PDM – Enabled or disabled.

See "Making Disk Array Settings" on page 111.

Making Disk Array Settings

To make Disk Array settings:

1. Click the Subsystem icon in Tree View.
2. Click the Disk Arrays icon.
3. Click the Disk Array icon.
4. Click the Settings tab in Management View.
5. Optional. Enter an alias in the Disk Array Alias field. Maximum of 32 characters. Use letters, numbers, space between words, and underscore. An alias is optional.
6. To enable Media Patrol support, check the Media Patrol box.
7. To enable PDM support, check the PDM box.
8. Click the Submit button.

Creating a Logical Drive

When you create a disk array, you automatically create one logical drive also. If the initial logical drive used less than the full capacity of the disk array, you can create additional logical drives from the same disk array.

To create a logical drive:

1. Click the Subsystem icon in Tree View.
2. Click the Disk Arrays icon.

1. Click the Disk Array
2. Click the Create LD tab in Management View.
3. Enter an alias (name) in the Alias field.

Maximum of 32 characters. Use letters, numbers, space between words, and underscore. An alias is optional.

1. From the RAID Level dropdown list, select a RAID level for this logical drive.
   All RAID levels supported by the disk array appear in the list. See “Choosing a RAID Level” on page 228.
2. RAID 50 – Specify the number of axles for your array.
   For more information on axles, see "RAID 50 Axles" on page 226.
3. Enter a capacity and select unit of measure (MB, GB, TB).
   The default value is the available capacity of the disk array. You can use this value or any lesser amount.
4. From the Stripe dropdown menu, select a Stripe size for this logical drive.
   The choices are 64 KB, 128 KB, 256 KB, 512 KB, and 1 MB. 64 KB is the default. See “Choosing Stripe Size” on page 231.
5. From the Sector dropdown menu, select a Sector size for this logical drive.
   For iSCSI, use the 512 B default. See “Choosing Sector Size” on page 231.
6. From the Read Policy dropdown menu, select a Read Cache policy for this logical drive.
   The choices are Read Cache, Read Ahead, and No (read) Cache. Read Ahead is the default. See “Cache Policy” on page 232.
7. From the Write Policy dropdown menu, select a Write Cache policy for this logical drive.
   The choices are Write Through (thru) and Write Back. Write Back is the default. If you selected No Cache under Read Cache, this setting will be Write Through. See “Cache Policy” on page 232.
8. Click the Update button to enter the logical drive parameters.
9. Review the results. If there is remaining space the disk array, you can create another logical drive, following the steps above. Each logical drive can have a different set of parameters.
10. Click the Next button when you are done.

A new window displays with the disk array information and the proposed logical drives with their parameters.

1. Click the Submit button create the logical drives.

The new logical drive appears in the Logical Drive List the Information tab.

If you created a fault-tolerant logical drive (any RAID level except RAID 0), the Operational Status of new logical drive will display Synchronizing for several minutes after creation. You can use the logical drive during this period but read/write performance could be slower than normal.

Deleting a Logical Drive

Caution

All data the logical drive will be lost. Back up any valuable data before deleting the logical drive.

To delete a logical drive:

1. Click the Subsystem icon in Tree View.
2. Click the Disk Arrays icon.
3. Click the Disk Array icon.
4. Click the Delete LD tab in Management View.
5. Check the box to the left of the logical drive you want to delete.
6. Click the Submit button.

In the confirmation box, type the word confirm in the field provided.

1. Click the OK button.

The selected logical disappears from the Logical Drive List the Information tab.

Migrating a Disk Array

The action of migrating a disk array means either or both:

• Change the RAID Level
• Expand the storage capacity

For a list of Migration options and other important information, see “RAID Level Migration” on page 235.

Notes

• You can add physical drives to a RAID 50 array but you cannot change the number of axles.
• If you add an odd number of physical drives to a RAID 10 array, it will become a RAID 1E array by default.

To Migrate an existing disk array:

1. Click the Subsystem icon in Tree View.
2. Click the Disk Arrays icon.
3. Click the Disk Array icon.
4. From the dropdown menu the Background Activities tab, select Start Migration.
5. Highlight physical drives you want in the disk array from the Available list and press the >> button to move them to the Selected list.

You can also double-click them to move them.

1. When you are done, click the Next button.
2. Select a new RAID Level, if desired.
3. To expand the disk array's capacity, check the Expand Capacity box.
4. If you checked the Expand Capacity box, enter a number into the Capacity field and select the appropriate unit of measure (MB, GB, TB).
5. Under Capacity Usage, highlight the logical drive whose RAID level you want to change or whose capacity you want to expand.
6. Click the Update button.

The logical drive changes to reflect your choices.

1. Update other logical drives using the same method.
2. When you are done making the changes, click the Next button.
3. Click the Submit button to begin Migration.

To set Migration priority, see “Making Background Activity Settings” on page 51.

Rebuilding a Disk Array

When you rebuild a disk array, you are actually rebuilding the data on a replacement physical drive.

Rebuilding Automatically

Normally, a disk array would rebuild itself using a hot disk drive, after going Critical. However, if the Auto Rebuild function is disabled or no spare drives are available, you must initiate the procedure.

To enable Auto Rebuild, see "Making Background Activity Settings" on page 51.

To create a spare drive, see "Creating a Spare Drive" on page 126.

For more information, see "Hot Spare Drive(s)" on page 234.

Rebuilding Manually

If a physical drive has failed, identify and replace the drive, then rebuild the disk array as described below:

1. Click the Subsystem icon in Tree View.
2. Click the Disk Arrays icon.
3. Click the Disk Array icon.

If there are multiple disk arrays, choose the icon with the yellow !.

1. From the dropdown menu the Background Activity tab, select Start Rebuild.

2. Select the Source physical drive.

This is a remaining functional physical drive in the disk array.

1. Select the Target physical drive.

This is the replacement physical drive.

1. Click the Submit button.

The Disk Array Background Activity tab shows the rebuild progress on the replacement (target) physical drive. Depending the size of the physical disk involved, this process will take some time.

To view more information, click the Rebuild on PDx link.

To set Rebuild priority, see "Making Background Activity Settings" on page 51.

Running Media Patrol on a Disk Array

Media Patrol checks the magnetic media on physical drives. When it finds the specified number of bad blocks, it will trigger PDM. See “Making Background Activity Settings” on page 51 and “Running PDM” on page 52.

You can schedule Media Patrol to run automatically, see “Scheduling an Activity” on page 53.

To start Media Patrol:

1. Click the Subsystem icon in Tree View.

2. Click the Disk Arrays icon.

3. Click the Disk Array icon.

4. From the dropdown menu the Background Activities tab, choose Start Media Patrol.

5. Click the Start button.

Running PDM on a Disk Array

Predictive Data Migration (PDM) migrates data from the suspect physical drive to a spare physical drive, similar to Rebuilding. But unlike Rebuilding, PDM acts before the disk drive fails and your Logical Drive goes Critical.

See "Predictive Data Migration (PDM)" on page 238.

To start PDM:

1. Click the Subsystem icon in Tree View.
2. Click the Disk Arrays icon.
3. Click the Disk Array icon.
4. Click the Background Activities tab in Management View.
5. From the dropdown menu the Background Activities tab, choose Start PDM.
6. In the next screen, select the Source and Target physical drives.

The suspect physical drive is the source. The replacement physical drive is the target.

1. Click the Start button.

Transitioning 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. The revertible spare drive returns to its original status. For more information, see “Transition” on page 239.

In order to run the Transition function:

• The spare drive must be Revertible.
• You must specify an unconfigured physical drive of the same or larger capacity to replace the revertible spare drive.

To run Transition:

1. Click the Subsystem icon in Tree View.
2. From the dropdown menu on the Background Activities tab, select Start Transition.
3. Select an unconfigured physical drive from the list of available drives.
4. From the Target Physical Drive dropdown menu, choose an unconfigured physical drive.
5. Click the Submit button.

After Transition is completed, refresh the screen. The revertible spare drive will be listed under the Spare Drives icon and the disk array's operational status will show OK.

To set Transition priority, see “Making Background Activity Settings” on page 51.

Preparing a Disk Array for Transport

Transport is the action of moving the physical drives of a disk array:

• To different slots in the same VTrak enclosure
• From one VTrak enclosure to another

Important

Before you can use this feature:

• There must be a dedicated spare disk drive assigned to this disk array.
• The disk array's Operational Status must be OK.

To prepare a disk array for transport:

1. Click the Subsystem icon in Tree View.
2. Click the Disk Arrays icon.
3. Click the Disk Array icon.
4. Click the Transport tab in Management View.
5. Click the Submit button.
6. In the confirmation box, type the word confirm in the field provided.
7. Click the OK button.
8. After the Transition is complete, move the physical drives comprising the disk array to their new locations.
9. Click the Refresh button in your Browser. The drives appear in their new locations and disk array status displays OK.

Managing Logical Drives

Logical drives are made from disk arrays. In the Tree, you can see a graphic representation of the logical drives that belong to each array. You can see a summary of all logical drives in the subsystem under Logical Drive Summary.

Logical drive management includes the following functions:

• Viewing Information for All Logical Drives (page 118)
• Locating a Logical Drive (page 119)
• Viewing Logical Drive Information (page 119)
  • Viewing Logical Drive Statistics (page 120)
• Making Logical Drive Settings (page 120)
• Initializing a Logical Drive (page 121)
• Running Redundancy Check (page 122)
• Viewing the Logical Drive Check Table (page 123)
• Making Logical Drive LUN Settings (page 123)

Viewing Information for All Logical Drives

To view information about all logical drives in a disk array:

1. Click the Subsystem icon in Tree View.
2. Click the Disk Arrays icon.
3. Click the Disk Array icon.
4. Click the Logical Drives icon

Logical Drive 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.
• 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 will function and your data is available. However, access will be slower due to the synchronizing operation.

• 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 will function and your data is available. However, access will be slower due to the rebuilding operation.

• Critical – This condition arises as the result of a physical drive failure. A degraded logical drive will still function 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.

• Offline – This condition arises as the result of a second physical drive failure. An Offline logical drive is not accessible but some or all of your data may remain intact. You must determine the cause of the problem and correct it.
• 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 will show OK.

To create a logical drive, see “Creating a Logical Drive” on page 111.

To delete a logical drive, see "Deleting a Logical Drive" on page 113.

For a Degraded or Offline logical drive, see “Critical & Offline Disk Arrays” on page 269.

Locating a Logical Drive

To locate a logical drive:

1. Click the Subsystem icon in Tree View.
2. Click the Disk Arrays icon.
3. Click the Disk Array icon.
4. Click the Logical Drives icon
5. Click the Logical Drive icon.

In the diagram at the top of Management View, the crosshatched physical drives belong to the logical drive.

1. Click the crosshatch pattern.

The disk status LEDs will blink for one minute.

Viewing Logical Drive Information

To view information for a single logical drive:

1. Click the Subsystem icon in Tree View.
2. Click the Disk Arrays icon.
3. Click the Disk Array icon.

4. Click the Logical Drives icon

5. Click the Logical Drive icon.

To specify an Alias or set the Read and Write Policies, click the Settings tab.

Logical Drive Status

See "Logical Drive Status" on page 118.

Logical Drive Synchronization

Synchronization is an automatic procedure applied to logical drives when they are created. Yes means the logical drive was synchronized.

Adjustable Items

• Alias – Optional.
• Read Policy
• Write Policy

See "Making Logical Drive Settings" on page 120.

Viewing Logical Drive Statistics

To view information for a single logical drive:

1. Click the Subsystem icon in Tree View.
2. Click the Disk Arrays icon.
3. Click the Disk Array icon.
4. Click the Logical Drives icon
5. Click the Logical Drive icon.
6. In Management View, Click the dropdown menu on the Information tab and choose Statistics.

Clearing Statistics

To clear statistics, see "Clearing Statistics" on page 88.

Making Logical Drive Settings

To make Logical Drive settings:

1. Click the Subsystem icon in Tree View.
2. Click the Disk Arrays icon.
3. Click the Disk Array icon.

4. Click the Logical Drives icon

5. Click the Logical Drive icon.

6. Click the Settings tab in Management View.
7. Optional. Enter an alias in the Logical Drive Alias field.

Maximum of 32 characters. Use letters, numbers, space between words, and underscore. An alias is optional.

1. From the Read Policy dropdown menu, select a Read Cache policy.

The choices are Read Cache, Read Ahead, and No Cache.

1. From the Write Policy dropdown menu, select a Write Cache policy.

The choices are Write Back and Write Through (Thru). If you select No Read Cache, Write policy is automatically Write Through.

1. Click the Submit button.

Initializing a Logical Drive

Initialization is 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 the logical drives left behind from earlier configurations. For this reason, Initialization is recommended for all new logical drives.

Caution

When you initialize a logical drive, all the data the logical drive will be lost. Backup any important data before you initialize a logical drive.

Initialize a Logical Drive:

1. Click the Subsystem icon in Tree View.
2. Click the Logical Drive Summary icon.
3. Click the icon of the logical drive you want to Initialize.

You can also start Initialization from the Subsystem icon Background Activities tab

1. Click the Background Activities tab in Management View.
2. From the Background Activities dropdown menu, select Initialization.
3. To select Quick Initialization, check the box.

If you checked the box, enter a value in the Quick Initialization Size field. This value is the size of the initialization blocks in MB.

1. If you did not select Quick Initialization, enter a hexadecimal value in the Initialization Pattern in Hex field or use the default 00000000 value.

2. Click the Submit button.

3. In the confirmation box, type the word confirm in the field provided.
4. Click the OK button.

To view the progress of the Initialization, click the Background Activity tab.

To set Initialization priority, see “Making Background Activity Settings” on page 51.

Running Redundancy Check

Redundancy Check is a routine maintenance procedure for fault-tolerant logical drives (those with redundancy) that ensures all the data matches exactly.

Redundancy Check can also correct inconsistencies. You can also schedule a Redundancy Check. See "Scheduling an Activity" on page 53.

Redundancy Check a Logical Drive:

1. Click the Subsystem icon in Tree View.
2. Click the Logical Drive Summary icon.
3. Click the icon of the logical drive you want to Initialize.

You can also start Redundancy check from the SubsystemIcon Background Activities tab

1. From the dropdown menu on the Background Activities tab, select Redundancy Check.
2. To select Auto Fix, check the box.

This feature attempts to repair the problem when it finds an error.

1. To select Pause On Error, check the box.

This feature stops the process when it finds an error.

If Auto Fix is also checked, the process stops only when it finds a non-repairable error.

1. Click the Submit button.

To view the progress of the Redundancy Check, click the Background Activity tab.

To set Redundancy Check priority, see “Making Background Activity Settings” on page 51.

Viewing the Logical Drive Check Table

The Logical Drive Check Table displays errors related to a logical drive. Use this information to evaluate the integrity of the logical drive and to determine whether corrective action is needed. To View the tables:

1. Click the Subsystem icon in Tree View.
2. Click the Disk Arrays icon.
3. Click the Disk Array icon.
4. Click the Logical Drives icon
5. Click the Logical Drive icon.
6. Click the Check Table tab in Management View.
7. Click the option for the table you want to see.

The default is All tables.

If there are entries, they are listed as follows:

• Entry Number – A number assigned to each block of entry.
• Table Type – Read Check, Write Check or Inconsistent Block (see below).
• Start Logical Block Address – LBA of the first block for this entry.
• Count – Number of continuous blocks starting from this LBA.

Table Definitions

• Read Check Table – Contains a list of read errors for this logical drive.
• Write Check Table – Contains a list of write errors for this logical drive.
• Inconsistent Block Table – Contains a list of inconsistent blocks for this logical drive. Mirror data for RAID Levels 1, 1E, and 10 or Parity data for RAID Levels 5, 6, and 50 identified by the Redundancy Check (a background function).

Making Logical Drive LUN Settings

For iSCSI, LUN Masking is the process of applying a LUN Map so that each initiator can only access the LUNs specified for it.

Before you can specify an initiator for your LUN map, you must add an initiator to the VTrak's initiator list. See "Adding an Initiator" on page 73.

Obtain the initiator name from the initiator utility on your host system.

You must enable LUN Masking in order apply a LUN map to your logical drive. See “Enabling LUN Masking” on page 74.

To specify a iSCSI LUN Map:

1. Click the Subsystem icon in Tree View.
2. Click the Disk Arrays icon.
3. Click the Disk Array icon.
4. Click the Logical Drives icon
5. Click the Logical Drive icon.
6. Click the LUN Map tab in Management View.
7. From the Initiator dropdown menu, choose an initiator for your LUN.

Or type the initiator name into the Initiator Name field.

1. Note that the initiator name you input must match exactly in order for the connection to work.
2. Type a LUN into the Map to LUN field.
3. Click the Assign button.

The initiator appears in the Assigned Initiator List.

1. Click the Submit button.

• Initiator Name – A World Wide Name (WWN), used to identify the Initiator. An iSCSI initiator name is the iSCSI name of the initiator device and is composed of a single text string. iSCSI WWNs are somewhat different from regular WWNs.
• Alias – Optional. A common name for an iSCSI initiator
• Symbolic Name – Optional
• IP Address – IP address of the iSCSI port for this initiator
• Port ID – Port ID of the Fibre Channel port for this initiator
• LUN – Logical Unit Number on this logical drive for the selected initiator You must enter different LUN numbers for each logical drive

Managing Spare Drives

When a physical drive in a disk array fails and a spare drive of adequate capacity is available, the disk array will begin to rebuild automatically using the spare drive. See “Critical & Offline Disk Arrays” on page 269.

Spare drive management includes the following functions:

• Viewing a List of Spare Drives (page 125)
• Locating a Spare Drive (page 125)
• Creating a Spare Drive (page 126)
• Deleting Spare Drive (page 127)
• Making Spare Drive Settings (page 127)
• Running Spare Check (page 128)

Viewing a List of Spare Drives

To view a list of spare drives:

1. Click the Subsystem icon in Tree View.
2. Click the Spare Drives icon.

The information includes:

• ID – The unique ID number assigned to the spare drive.
• Operational Status – OK is normal. Can also show Rebuilding, Transition Running, PDM Running, or Offline.
• Physical Drive ID – The ID number of the physical drive in the subsystem enclosure.
• Capacity – The data storage capacity of this spare drive.
• Revertible – Yes or No. A revertible spare drive automatically returns to its spare drive assignment after the failed physical drive in the disk array is replaced.
• Type – Global, can be used by any disk array. Dedicated, can only be used by the assigned disk array.
• Dedicated to Array – For dedicated spares, the disk array to which it is assigned. Global spares show N/A.

Locating a Spare Drive

To locate a physical drive assigned as a spare drive in the VTrak subsystem enclosure:

1. Click the Subsystem icon in Tree View.

2. Click the Spare Drives icon.

3. Click the Spare Drive icon.

In Management View, the Enclosure Front View diagram appears with the location of the spare drive highlighted.

Creating a Spare Drive

Important

- There must be an unconfigured physical drive available for selection as a spare drive. See “Viewing a List of Physical Drives” on page 100.

- Be sure the unconfigured physical drive has adequate capacity to replace the largest drive in the disk array.

To create a spare drive:

1. Click the Subsystem icon in Tree View.
2. Click the Spare Drives icon.
3. Click the Create tab in Management View.
4. Select a spare type, Global or Dedicated.

Global can be used by any disk array. Dedicated can only be used by the assigned disk arrays

1. To make a revertible spare drive, check the Revertible box.
   A reversible spare drive can be returned to spare drive status after it replaces a failed drive in a disk array. See “Transition” on page 239 for more information.
2. In the Physical drives field, highlight the physical drive you want to assign as a spare drive in the Available list and press the >> button to move the drive to the Selected list.

You can also double-click drives to move them.

1. If you selected a Dedicated spare drive, in the Dedicated to Disk Arrays field, highlight disk arrays to which you want assign the spare drive from the Available list and press the >> button to move the array to the Selected list.

You can also double-click arrays to move them.

1. Click the Update button.

Your choices are displayed under New Hot Spare Drives.

1. If you agree with the proposed choices, click the Submit button.

Deleting Spare Drive

Note

If an existing spare drive has the wrong parameters for your needs, click the Settings tab to change the parameters rather than delete the spare drive and create a new one.

To delete a spare drive:

1. Click the Subsystem icon in Tree View.
2. Click the Spare Drives icon.
3. Click the Delete tab in Management View.
4. Check the box to the left of the spare drive you want to delete.
5. Click the Submit button.

In the confirmation box, type the word confirm in the field provided.

1. Click the OK button.

Making Spare Drive Settings

The Spare Drive—Settings tab enables you to change the settings of an existing spare drive. To change spare drive settings:

1. Click the Subsystem icon in Tree View.
2. Click the Spare Drives icon.
3. Click the Spare Drive icon.
4. Click the Settings tab in Management View.
5. Select a spare type, Global or Dedicated.

Global can be used by any disk array. Dedicated can only be used by the assigned disk arrays

1. To make a revertible spare drive, check the Revertible box.

A reversible spare drive automatically returns to its spare drive assignment after the failed physical drive in the disk array is replaced.

1. If you selected a Dedicated spare drive, in the Dedicated to Disk Arrays field, highlight the disk arrays to which you want assign the spare drive from the Available list and press the >> button to move them to the Selected list.

You can also double-click array to move it.

1. Click the Submit button.

Running Spare Check

Spare Check verifies the operational status of your spare drives. You can also schedule a Spare Check. See “Scheduling an Activity” on page 53.

To check a spare drive:

1. Click the Subsystem icon in Tree View.
2. Click the Spare Drives icon.
3. Click the Spare Check tab in Management View.
4. From the Physical Drive dropdown menu, select the spare drive you want to check.

Or select All to check all the spare drives at the same time.

1. Click the Submit button.

The results of the Spare Check appear under Spare Check Status in the Information tab. "Healthy" means normal condition.

Working with the Logical Drive Summary

The Logical Drive Summary displays a list of all logical drives in the VTrak enclosure plus the expanded or cascaded enclosures. This list does not arrange the logical drives under the disk array to which they belong nor under the enclosure in which they are located.

Logical Drive Summary includes the following functions:

• Viewing a List of All Logical Drives (page 129)
• Viewing Individual Logical Drive Information (page 129)

Viewing a List of All Logical Drives

To view a list of all logical drives in all enclosures:

1. Click the Subsystem icon in Tree View.

2. Click the Drive Summary icon.

Viewing Individual Logical Drive Information

1. Click the Subsystem icon in Tree View.
2. Click the Drive Summary icon.
3. Click the Logical Drive icon.

The information and location for the logical drive appear in Management View. See Viewing Logical Drive Information (page 119).

Chapter 5: Management with the CLU

This chapter covers the following topics:

• Logging into the CLU (page 132)
• Running Quick Setup (page 135)
• Managing the Subsystem (page 136)
• Managing the Controllers (page 138)
• Managing the Enclosure (page 140)
• Managing Physical Drives (page 144)
• Managing Disk Arrays (page 147)
• Managing Logical Drives (page 158)
• Managing the Network Connection (page 162)
• Managing iSCSI Connections (page 167)

• Managing Background Activity (page 172)
  • Working with the Event Viewer (page 174)

• Managing Spare Drives (page 176)
  • Working with LUN Mapping (page 179)

• Managing Users (page 181)
  • Working with Software Management (page 184)
• Flashing through TFTP (page 191)
• Clearing Statistics (page 192)
• Restoring Factory Defaults (page 193)
• Shutting Down the Subsystem (page 194)
• Restarting the Subsystem (page 196)
  • Working with the Buzzer (page 197)

For information about VTrak's audible alarm and LEDs, see "Chapter 8: Troubleshooting" on page 243.

Logging into the CLU

There are two connections methods for the CLU:

• Serial – Requires a null-modem cable to connect the serial ports on the Host PC and VTrak
• Telnet – Requires a network connection between the Host PC and VTrak's Management Port

Making a Serial Connection

Before you begin, be sure the null modem cable is connected between the Host PC and VTrak, and that both machines are booted and running. Then do the following actions:

1. Start your PC's terminal emulation program.
2. Press Enter once to launch the CLU.

Making a Telnet Connection

If your Telnet connection has not been setup, refer to "Making Serial Cable Connections" on page 20.

To start the telnet program:

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. Use your VTrak's Management port IP address. 2300 is the Telnet port for the VTrak.

The telnet login screen appears:

1. At the Login prompt, type the user name and press Enter.

The default user name is administrator.

1. At the Password prompt, type the password and press Enter.

The default password is password.

The CLI screen appears.

1. At the CLI prompt, type menu and press Enter

The CLU Main Menu appears.

Figure 4. The CLU main menu

Quick Setup – A sequence of four steps to setup System Date & Time, Management Port, and RAID Configuration.

Subsystem Management – View controller information, lock/unlock the controller, set date and time, and monitor the enclosure.

Physical Drive Management – View disk drive assignments and parameters, change disk drive cache settings and command queuing, and locate a physical drive.

Disk Array Management – View disk array information, create and delete disk arrays, transport, rebuild, PDM, and transition functions, and locate a disk array, create and delete logical drives.

Logical Drive Management – View logical drive information, name logical drives, initialization and redundancy check, and locate a logical drive.

Network Management – Set the IP address for Management Port, gateway, and DNS server; subnet mask.

iSCSI Management – Node settings, Port statistics, Session information, iSNS options, CHAPs, and Ping function.

Background Activity – Settings for Media Patrol, Auto Rebuild, Rebuild, Migration, PDM, Transition, Synchronization, Initialization, Redundancy Check rate, and thresholds.

Event Viewer – View the event logs.

Additional Info and Management – Spare Drives, LUN Mapping, User management, EMail, SLP, Webserver, Telnet, SNMP, CIM, and Netsend settings, firmware flash, clear statistics and restore factory default settings.

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.

Logging out of the CLU

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

Running Quick Setup

Quick Setup is discussed under “Setting up the Serial Connection” on page 23.

Managing the Subsystem

Subsystem Management includes the following functions:

• Setting an Alias for the Subsystem (page 136)
• Running Media Patrol (page 136)
• Locking or Unlocking the Subsystem (page 136)
• Setting Subsystem Date and Time (page 137)

Setting an Alias for the Subsystem

An alias is optional. To set an Alias for this subsystem:

1. From the Main Menu, highlight Subsystem Management and press Enter.
2. Type and alias into the Alias field.
   Maximum of 48 characters. Use letters, numbers, space between words and underscore.
3. Press Ctrl-A to save your settings.

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. From the Main Menu, highlight Subsystem Management and press Enter.
2. Highlight Media Patrol and press enter.
3. Highlight Start, Stop, Pause, or Resume and press Enter.
4. If you chose Stop, press Y to confirm.

Locking or Unlocking the Subsystem

The lock prevents other sessions (including by 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. From the Main Menu, highlight Subsystem Management and press Enter.
2. Highlight Lock Management and press Enter.
3. In the Lock Time field, type a lock time in minutes.

1440 minutes = 24 hours

1. Highlight Lock and press Enter.

Resetting the Lock

To reset the lock with a new time:

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

Releasing the Lock

1. From the Main Menu, highlight Subsystem Management and press Enter.
2. Highlight Lock Management and press Enter.
3. Highlight Unlock and press Enter.

Releasing a Lock set by another user

To release somebody else's lock:

1. From the Main Menu, highlight Subsystem Management and press Enter.
2. Highlight Lock Management and press Enter.
3. Highlight Force Unlock and press the Spacebar to change to Yes.
4. Highlight Unlock and press Enter.

Setting Subsystem Date and Time

Use this screen to make Date and Time settings:

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

Managing the Controllers

Controller Management includes the following functions:

• Viewing Controller Information (page 138)
• Making Controller Settings (page 138)
• Locating the Controller (page 139)

Viewing Controller Information

Controller Management includes information, settings and statistics.

To access Controller Management:

1. From the Main Menu, highlight Subsystem Management and press Enter.
2. Highlight Controller Management and press Enter.
3. Highlight the controller you want and press Enter.
   Basic Controller information displays.

To access additional controller information, highlight Advanced Information and press Enter.

To access controller statistics, highlight Controller Statistics and press Enter.

Making Controller Settings

An alias is optional. To set an Alias for this controller:

1. From the Main Menu, highlight Subsystem Management and press Enter.
2. Highlight Controller Management and press Enter.
3. Highlight the controller you want and press Enter.
4. Highlight Controller Settings and press Enter.
5. Make the following settings as required:

- Type and alias into the Alias field. Maximum of 48 characters. Use letters, numbers, space between words and underscore. An alias is optional.

- Highlight Coercion and press the spacebar to toggle between Enable and Disable.

- 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 Cache Flush Interval and press the backspace key to erase the current value. Type a new interval value (1 to 12 seconds).
• Highlight SMART and press the spacebar to toggle between Enable and Disable.
• Highlight SMART Poll Interval and press the backspace key to erase the current value. Type a new interval value (1 to 1440 minutes).

• Highlight Adaptive Writeback Cache and press the spacebar to toggle between Enabled and Disabled.

• Press Ctrl-A to save your settings.

Locating the Controller

To locate this controller:

1. From the Main Menu, highlight Subsystem Management and press Enter.
2. Highlight Controller Management and press Enter.
3. Highlight the controller you want and press Enter.
4. Highlight Controller Settings and press Enter.
5. Highlight Locate Controller and press Enter.

Controller Dirty Cache LED and Status LED, on the back of the Controller, will flash for one minute.

Managing the Enclosure

Enclosure Management includes the following functions:

• Viewing Enclosure Information (page 140)
  • Viewing Power Supply Status (page 140)
• Locating a Power Supply (page 140)
• Viewing Blower Status (page 141)
• Viewing Voltage Sensor Status (page 141)
  • Viewing Temperature Sensor Status (page 141)
• Setting Temperature Thresholds (page 141)
• Checking the Batteries (page 142)
• Reconditioning a Battery (page 142)
• Locating an Enclosure (page 143)

Viewing Enclosure Information

Enclosure Management includes information, status, settings and location. To access Enclosure Management:

1. From the Main Menu, highlight Subsystem Management and press Enter.
2. Highlight Enclosure Management and press Enter.

To access FPU VPD information (vital product data on field replaceable units), highlight FPU VPD Information and press Enter.

To access the current status of the power supplies, blowers, temperature or voltage sensors, highlight the item you want and press Enter.

Viewing Power Supply Status

To view the status of the power supplies:

1. From the Main Menu, highlight Subsystem Management and press Enter.
2. Highlight Enclosure Management and press Enter.
3. Highlight Power Supplies and press Enter.

The screen displays the operational and fan status of VTrak's 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 204.

Locating a Power Supply

To locate a power supply:

1. From the Main Menu, highlight Subsystem Management and press Enter.

2. Highlight Enclosure Management and press Enter.

3. Highlight Power Supplies and press Enter.
4. Highlight Locate Power Supply and press Enter.

The LED on the selected power supply blinks for one minute.

Viewing Blower Status

To view the status of the blowers:

1. From the Main Menu, highlight Subsystem Management and press Enter.
2. Highlight Enclosure Management and press Enter.
3. Highlight Blowers and press Enter.

The screen displays the status and speed of VTrak's blowers. There is one blower in each cooling unit. If blower speed is below the Healthy Threshold, there is a blower malfunction. See “Replacing a Cooling Unit Fan or Blower” on page 205.

Viewing Voltage Sensor Status

To view the status of the voltage sensors:

1. From the Main Menu, highlight Subsystem Management and press Enter.
2. Highlight Enclosure Management and press Enter.
3. Highlight Voltage Sensors and press Enter.

If any voltage is outside the Healthy Threshold values, there is a voltage malfunction in the enclosure. See “Chapter 8: Troubleshooting” on page 243.

Viewing Temperature Sensor Status

To view the status of the temperature sensors:

1. From the Main Menu, highlight Subsystem Management and press Enter.
2. Highlight Enclosure Management and press Enter.
3. Highlight Temperature Sensors and press Enter.

If any temperature exceeds the Healthy Threshold value, there is an overheat condition in the enclosure. See “Setting Temperature Thresholds” on page 141 and “Chapter 8: Troubleshooting” on page 243.

Setting Temperature Thresholds

To change temperature thresholds:

1. From the Main Menu, highlight Subsystem Management and press Enter.

2. Highlight Enclosure Management and press Enter.

3. Highlight Enclosure Settings and press Enter.

4. Highlight the Temperature Warning threshold you want to change.
5. Press the backspace key to erase the current value.
6. Type a new interval value in degrees C.
7. Press Ctrl-A to save your settings.

Checking the Batteries

This feature enables you monitor and recondition the subsystem battery or batteries.

1. From the Main Menu, highlight Subsystem Management and press Enter.
2. Highlight Enclosure Management and press Enter.
3. Highlight Batteries and press Enter.
4. Highlight the battery you want to monitor and press Enter.

Battery Notes

Each battery works with a controller. If the battery is present in the subsystem but the corresponding controller is not present, the battery will not appear in the interface.

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 142.

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 Battery” on page 211.

VTrak automatically reconditions the battery 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.

Reconditioning a Battery

To recondition the subsystem battery:

1. From the Main Menu, highlight Subsystem Management and press Enter.
2. Highlight Enclosure Management and press Enter.

3. Highlight Batteries and press Enter.

4. Highlight the battery you want to monitor and press Enter.

5. Highlight Recondition Battery and press Enter.
6. Press Y to confirm.

During reconditioning, Battery status can show “discharging” and “recharging”, and a value will display next to Current. During that time, the controller cache is reset to Write Thru. Reconditioning runs in the background and stops automatically upon completion.

VTrak automatically reconditions the battery every two months.

Locating an Enclosure

This feature helps you identify the physical VTrak enclosure you are working with through the CLU.

1. From the Main Menu, highlight Subsystem Management and press Enter.
2. Highlight Enclosure Management and press Enter.
3. Highlight Locate Enclosure and press Enter.

The LEDs on the front of the VTrak will blink for one minute.

Managing Physical Drives

Physical Drive Management includes the following functions:

• Viewing a List of Physical Drives (page 144)
• Making Global Physical Drive Settings (page 144)
• Setting an Alias (page 145)
  • Viewing Advanced Information (page 145)
  • Viewing Physical Drive Statistics (page 145)
• Clearing Stale and PFA Conditions (page 145)
• Forcing a Physical Drive Offline or Online (page 146)
• Locating a Physical Drive (page 146)

Viewing a List of Physical Drives

To view a list of physical drives:

1. From the Main Menu, highlight Physical Drive Management and press Enter.
2. Highlight Global Physical Drives Settings and press Enter.

The list of physical drives appears.

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. From the Main Menu, highlight Physical Drive Management and press Enter.

2. Highlight Global Physical Drives Settings and press Enter.

3. Change the following settings as required:

4. Highlight Write Cache and press the spacebar to toggle between Enabled and Disabled.

5. Highlight Read Look Ahead Cache and press the spacebar to toggle between Enabled and Disabled.
6. Highlight CmdQueuing and press the spacebar to toggle between Enabled and Disabled.

7. Highlight DMA Mode and press the spacebar to toggle through UDMA 0–5 and MDMA 0–2.

8. Press Ctrl-A to save your settings.

Setting an Alias

An alias is optional. To set an Alias for a physical drive:

1. From the Main Menu, highlight Physical Drive Management and press Enter.
2. Highlight the physical drive of your choice and press Enter.
3. Type an alias into the Alias field.
   Maximum of 32 characters. Use letters, numbers, space between words and underscore.
4. Press Ctrl-A to save your settings.

Viewing Advanced Information

To view advanced information about the selected physical drive:

1. From the Main Menu, highlight Physical Drive Management and press Enter.
2. Highlight the physical drive of your choice and press Enter.
3. Highlight Advanced Information and press Enter.

Viewing Physical Drive Statistics

To view the statistics for the selected physical drive:

1. From the Main Menu, highlight Physical Drive Management and press Enter.
2. Highlight the physical drive of your choice and press Enter.
3. Highlight Physical Drive Statistics and press Enter.

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. From the Main Menu, highlight Physical Drive Management and press Enter.
2. Highlight the physical drive of your choice and press Enter.
3. 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. Go to Disk Array Info and Settings.

If a physical drive is offline and shows a PFA error, rebuild the disk array. Go to Disk Array Info and Settings. After rebuilding, the drive will show 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 will be 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

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. From the Main Menu, highlight Physical Drive Management and press Enter.
2. Highlight Global Physical Drives Settings and press Enter.
3. Highlight the physical drive of your choice and press Enter.
4. Highlight Force Offline or Force Online and press Enter.
5. 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. From the Main Menu, highlight Physical Drive Management and press Enter.
2. Highlight Global Physical Drives Settings and press Enter.
3. Highlight the physical drive of your choice and press Enter.
4. Highlight Locate Physical Drive and press Enter.

The drive carrier LEDs on the front of the VTrak will blink for one minute.

Managing Disk Arrays

Disk Array Management includes the following functions:

• Creating a Disk Array (page 147)
• Deleting a Disk Array (page 151)
• Viewing Disk Array Information (page 152)
• Setting an Alias for a Disk Array (page 152)
• Enabling Media Patrol on a Disk Array (page 153)
• Enabling PDM on a Disk Array (page 153)
  • Preparing the Disk Array for Transport (page 153)
• Rebuilding a Disk Array (page 154)
• Migrating a Disk Array (page 154)
• Running PDM (page 155)
• Running Transition on a Disk Array (page 155)
• Locating a Disk Array (page 156)
• Locating a Disk Array (page 156)
• Creating a Logical Drive (page 156)
• Deleting a Logical Drive (page 157)

Creating a Disk Array

The CLU provides three methods of creating a disk array:

• Automatic – Creates a default disk array and logical drive based on unconfigured physical drives in the system. No user choices. See “Creating a Disk Array – Automatic” on page 148.
• Express – You select the RAID characteristics and type of application. Creates a disk array and logical drive(s) based on your input. See “Creating a Disk Array – Express” on page 149.
• Advanced – You specify all parameters for a new disk array. One logical drive will be made automatically when you create the disk array. If you select less than the total available capacity, you can use the remaining space to create additional logical drives at a later time. See “Creating a Disk Array – Advanced” on page 150.

Creating a Disk Array – Automatic

To create a disk array using the Automatic feature:

1. From the Main Menu, highlight Disk Array Management and press Enter.
2. Highlight Create New Array and press Enter.
3. Highlight Configuration Method and press the spacebar to toggle to Automatic.

4. Review the proposed configuration of disk array and logical drive(s).

5. To accept the proposed configuration and create the disk array and logical drive(s), highlight Save Configuration and press Enter.

6. To reject the proposed configuration, highlight Cancel Array Configuration and press Enter. You will 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.

Creating a Disk Array – Express

To create a disk array using the Express feature:

1. From the Main Menu, highlight Disk Array Management and press Enter.
2. Highlight Create New Array and press Enter.

3. Highlight Configuration Method and press the spacebar to toggle to Express.

4. Highlight Configuration Method and press to spacebar to select each of the following characteristics for your disk array:

5. Redundancy

6. Capacity
   • P e r f o r m a n c e

7. Spare Drive

8. Highlight Number of Logical Drives and press the backspace key to erase the current value.

9. Enter the number of logical drives you want.

10. Highlight Application Type and press the spacebar to toggle though the applications and select the best one for your disk array.

11. F i l e S e r v e r

12. Video Stream
13. Transaction Data

14. Transaction Log
    • Other

15. Press Ctrl-A to save your settings and move to the next screen.

16. Review the proposed configuration of disk array and logical drive(s).

To accept the proposed configuration and create the disk array and logical drive(s), highlight Save Configuration and press Enter.

To reject the proposed configuration, highlight Cancel Array Configuration and press Enter. You will 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.

Creating a Disk Array – Advanced

For more information on the choices below, see “Chapter 7: Technology Background” on page 219. To create a disk array using the Advanced feature:

1. From the Main Menu, highlight Disk Array Management and press Enter.
2. Highlight Create New Array and press Enter.
3. Highlight Configuration Method and press the spacebar to toggle to Advanced.

4. Choose whether to enable Media Patrol and PDM.

5. 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.

6. Highlight Save Settings and Continue and press Enter.

7. Highlight a physical drive you want to add to your array and press the spacebar to select it. Repeat this action until you have selected all the physical drives for your array.

8. Highlight Save Settings and Continue and press Enter.

9. 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.

10. Highlight RAID Level and press the spacebar to toggle though a list of available RAID levels.

11. 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.

12. Highlight Number of Axles and press the spacebar to select the number of axles. Applies to RAID 50 only.

13. Highlight Stripe and press the spacebar to toggle through stripe sizes and select 64 KB, 128 KB, 256 KB, 512 KB, or 1 MB.

14. Highlight Sector and press the spacebar to toggle through sector sizes. For iSCSI, use the 512 B default. See “Choosing Sector Size” on page 231.

15. Highlight Write Policy and press the spacebar to toggle write cache policy between WriteBack and WriteThru (write though).

16. Highlight Read Policy and press the spacebar to toggle read cache policy though ReadCache, ReadAhead, and NoCache.

17. Highlight Save Logical Drive and press Enter.

18. Review logical drive(s) you are about to create for your new array. Then do one of the following actions:

19. If you agree with the logical drive(s) as specified, highlight Complete Disk Array Creation and press Enter. A note will appear to remind you to set up LUN mapping for your new logical drive(s). Press any key to continue.

20. 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.
21. If you do not agree with the logical drive(s), 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. From the Main Menu, highlight Disk Array Management and press Enter.
2. 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.
3. Highlight Delete Marked Arrays and press Enter.
4. Press Y to confirm the deletion.

Viewing Disk Array Information

1. From the Main Menu, highlight Disk Array Management and press Enter.
2. Highlight the disk array you want and press Enter.

The information and settings screen appears.

1. Highlight any of the following and press Enter to view a list of:

2. Spare drives in this array, dedicated and global
   • Physical drives in this array

3. Logical drives in this array

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.
• 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 will function and your data is available. However, access will be slower due to the synchronizing operation.
• Critical/Degraded – This condition arises as the result of a physical drive failure. A degraded logical drive will still function 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 will function and your data is available. However, access will be 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 will show OK.

Setting an Alias for a Disk Array

This function sets an alias for the disk array. To set an alias:

1. From the Main Menu, highlight Disk Array Management and press Enter.
2. Highlight the disk array you want and press Enter.
3. To set an alias for this disk array, highlight Alias and type an alias into the field.

Maximum of 32 characters. Use letters, numbers, space between words and underscore. An alias is optional.

1. Press Ctrl-A to save your settings.

Accepting an Incomplete Array

This condition is the result of a missing physical drive. See “Incomplete Array” on page 272 before you use this function.

To accept an incomplete array:

1. From the Main Menu, highlight Disk Array Management and press Enter.
2. Highlight the disk array you want and press Enter.
3. Highlight Accept Incomplete Array and press Enter.

Enabling Media Patrol on a Disk Array

Media Patrol checks the magnetic media on physical drives.

To run Media Patrol on a disk array:

1. From the Main Menu, highlight Disk Array Management and press Enter.
2. Highlight the disk array you want and press Enter.
3. Highlight Media Patrol and press the spacebar to toggle between Enable and Disable.
4. Press Ctrl-A to save your settings.

Enabling PDM on a Disk Array

This function enables and disables Predictive Data Migration (PDM).

To enable or disable PDM:

1. From the Main Menu, highlight Disk Array Management and press Enter.
2. Highlight the disk array you want and press Enter.
3. Highlight PDM and press the spacebar to toggle between Enable and Disable.
4. Press Ctrl-A to save your settings.

See "Running PDM" on page 155.

Preparing the Disk Array for Transport

To run the Transport function on a disk array:

1. From the Main Menu, highlight Disk Array Management and press Enter.

2. Highlight the disk array you want and press Enter.

3. Highlight Transport and press Enter.

4. Press Y to confirm.

Rebuilding a Disk Array

Before you can rebuild, you must have a replacement physical drive of adequate capacity or your disk array. To rebuild a disk array:

1. From the Main Menu, highlight Disk Array Management and press Enter.
2. Highlight the disk array you want and press Enter.
3. Highlight Background Activities and press Enter.
4. Highlight Rebuild and press Enter.
5. Specify the source and target physical drives.
6. Highlight Start and press Enter.

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 235.

To migrate a disk array:

1. From the Main Menu, highlight Disk Array Management and press Enter.
2. Highlight the disk array you want and press Enter.
3. Highlight Background Activities and press Enter.
4. Highlight Migration and press Enter.
5. Highlight the physical drive you want to add and press the spacebar to select it.

Repeat this action to add more physical drives.

Notes

• You can add physical drives to a RAID 50 array but you cannot change the number of axles.

• If you add an odd number of physical drives to a RAID 10 array, it will become a RAID 1E array by default.

• Highlight Save Settings and Continue and press Enter.

• To change RAID level, Highlight the logical drive in the list and press Enter.
• Highlight RAID Level and press the spacebar to toggle through the available RAID levels.

• Optional. If you want to increase capacity, highlight Expand Capacity and press the spacebar to toggle to Yes.

• Optional. If you want to increase capacity, highlight Capacity, press the backspace key to erase the current logical drive capacity and type in the new value.

The new value must be equal or larger than the current capacity.

1. Highlight Save Logical Drive and press Enter.

The screen returns to Disk Array Migration Logical Drives.

1. Highlight Complete Disk Array Migration and press Enter.

2. In the confirmation message, press Y to confirm.

The screen jumps to Disk Arrays Summary.

Running PDM

Be sure PDM must be enabled. See “Enabling PDM on a Disk Array” on page 153.

To run Predictive Data Migration on a disk array:

1. From the Main Menu, highlight Disk Array Management and press Enter.
2. Highlight the disk array you want and press Enter.
3. Highlight Background Activities and press Enter.
4. Highlight Predictive Data Migration and press Enter.
5. Specify the source and target physical drives.
6. Highlight Start and press Enter.

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 239.

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. From the Main Menu, highlight Disk Array Management and press Enter.
2. Highlight the disk array you want and press Enter.
3. Highlight Background Activities and press Enter.
4. Highlight Transition and press Enter.
5. Specify the source and target physical drives.
6. Highlight Start and press Enter.

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. From the Main Menu, highlight Disk Array Management and press Enter.
2. Highlight the disk array you want and press Enter.
3. Highlight Locate Disk Array and press Enter.

The drive carrier LEDs pertaining to this disk array will blink for one minute.

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 "Chapter 7:

Technology Background" on page 219.

To create a logical drive from an existing disk array:

1. From the Main Menu, highlight Disk Array Management and press Enter.
2. Highlight the disk array in which you want to create a logical drive and press Enter.
3. Highlight Create New Logical Drive and press Enter.

The Disk Array ID number and Maximum capacity available for the new logical drive are displayed.

1. Highlight the following parameters and press the backspace key to erase the current value:

2. Alias - Type an alias into the field, if desired. Maximum of 32 characters. Use letters, numbers, space between words and underscore.

3. Capacity - Maximum capacity shown. Enter a smaller capacity if desired.

4. Highlight the following parameters and press the spacebar to toggle though the available choices:

5. Stripe size – Press the spacebar to select: 64 KB, 128 KB, 256 KB, 512 KB, or 1 MB

6. Sector size – For iSCSI, use the 512 B default.
7. Write Policy – Press spacebar to select: Write Back or Write Through

8. Read Policy – Press spacebar to select: No Cache, Read Cache, or Read Ahead Cache

9. Highlight Number of Axles and press the spacebar to select the number of axles. Applies to RAID 50 only.

10. Press Ctrl-A to save your settings.

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.

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. From the Main Menu, highlight Disk Array Management and press Enter.
2. Highlight the disk array that contains the logical drive you want to delete and press Enter.
3. 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.

1. Highlight Delete Marked Logical Drives and press Enter.

2. Press Y to confirm the deletion.

Managing Logical Drives

The Logical Drive Management function deals with settings and functions of existing logical drives. To create or delete a logical drive, see “Managing Disk Arrays” on page 147. Logical drive management includes:

• Viewing Logical Drive Information (page 158)
• Setting an Alias for a Logical Drive (page 159)
• Setting Write Cache Policy (page 159)
• Setting Read Cache Policy (page 159)
• Initializing a Logical Drive (page 160)
• Running Redundancy Check (page 160)
• Locating a Logical Drive (page 161)

Viewing Logical Drive Information

To view logical drive information:

1. From the Main Menu, highlight Logical Drive Management and press Enter.
2. Highlight the logical drive you want and press Enter.

The information and settings screen appears.

1. Highlight any of the following and press Enter to view more information:

- Check Table – Read Check, Write Check, and Inconsistent Block Tables

• Logical Drive Statistics

Logical Drive 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.
• 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 will function and your data is available. However, access will be slower due to the synchronizing operation.
• 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 will function and your data is available. However, access will be slower due to the rebuilding operation.

• Critical – This condition arises as the result of a physical drive failure. A degraded logical drive will still function 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.

• Offline – This condition arises as the result of a second physical drive failure. An Offline logical drive is not accessible but some or all of your data may remain intact. You must determine the cause of the problem and correct it.

• 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 will show OK.

Setting an Alias for a Logical Drive

To set an alias for a logical drive:

1. From the Main Menu, highlight Logical Drive Management and press Enter.
2. Highlight the logical drive you want and press Enter.
3. To set an alias for this disk array, highlight Alias and type an alias into the field.
   Maximum of 32 characters. Use letters, numbers, space between words and underscore. An alias is optional.
4. Press Ctrl-A to save your settings.

Setting Write Cache Policy

To set write cache policy on a logical drive:

1. From the Main Menu, highlight Logical Drive Management and press Enter.
2. Highlight the logical drive you want and press Enter.
3. To set write cache policy for this disk array, highlight WritePolicy and press the spacebar to toggle between WriteBack and WriteThru (write though).
4. Press Ctrl-A to save your settings.

Setting Read Cache Policy

To set read cache policy on a logical drive:

1. From the Main Menu, highlight Logical Drive Management and press Enter.
2. Highlight the logical drive you want and press Enter.
3. To set read cache policy for this disk array, highlight ReadPolicy and press the spacebar to toggle though ReadCache, ReadAhead and None.
4. Press Ctrl-A to save your settings.

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.

To initialize a logical drive:

1. From the Main Menu, highlight Logical Drive Management and press Enter.
2. Highlight the logical drive you want and press Enter.
3. Highlight Background Activity and press Enter.
4. 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 disk data format of the logical drives are initialized.
• Quick Initialization Rate – Enter a value or use the default 64 bits.

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.

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. From the Main Menu, highlight Logical Drive Management and press Enter.
2. Highlight the logical drive you want and press Enter.
3. Highlight Background Activity and press Enter.
4. 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.

1. 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.

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. From the Main Menu, highlight Logical Drive Management and press Enter.
2. Highlight the disk array you want and press Enter.
3. Highlight Locate Logical Drive and press Enter.

The drive status LEDs for the physical drives in this logical drive will blink for one minute.

Managing the Network Connection

Network Management deals with network connections and settings for the Management Port:

• Making Management Port Settings (page 162)
• Making iSCSI Data Port Settings (page 163)
• Viewing VLAN Entries (page 164)
• Creating a VLAN Entry (page 164)
• Changing a VLAN Entry (page 165)
• Deleting a VLAN Entry (page 165)
• Viewing Link Aggregation Entries (page 165)
• Creating a Link Aggregation Entry (page 166)
• Changing a Link Aggregation Entry (page 166)
• Deleting a Link Aggregation Entry (page 166)

Making Management Port Settings

Before you change settings, please see "Choosing DHCP or a Static IP Address" on page 24.

Making Automatic Settings

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

Making Manual Settings

1. From the Main Menu, highlight Network Management and press Enter.
2. Highlight the management port in the list and press Enter.
3. Highlight NetMgmt Ethernet Port Settings and press Enter
4. Highlight DHCP and press the spacebar to toggle to Disabled.

5. Highlight each of the following and press the backspace key to erase the current value, then type the new value.

6. IP Address

7. Subnet Mask

8. Gateway IP Address
   • DNS Server IP Address

9. Press Ctrl-A to save your settings.

Making iSCSI Data Port Settings

The network settings for the iSCSI data ports are located under the Network Management and are described below. For the iSCSI settings for the iSCSI data ports, see “Managing iSCSI Connections” on page 167.

Making Automatic Settings

1. From the Main Menu, highlight Network Management and press Enter.
2. Highlight the iSCSI port in the list and press Enter.
3. Highlight NetMgmt iSCSI Port Settings and press Enter.
4. Highlight DHCP and press the spacebar to toggle to Enable.
5. Highlight TCP Port Number, and press the backspace key to erase the current value, then type the new value.

Use 1 to 65535. The default is 3260.

1. Highlight Jumbo Frame and press the spacebar to toggle between Enabled and Disabled.
2. Press Ctrl-A to save your settings.

Making Manual Settings

1. From the Main Menu, highlight Network Management and press Enter.
2. Highlight the iSCSI port in the list and press Enter.
3. Highlight NetMgmt iSCSI Port Settings and press Enter.
4. Highlight DHCP and press the spacebar to toggle to Disabled.

5. Highlight each of the following and press the backspace key to erase the current value, then type the new value.

6. IP Address

7. Subnet Mask

8. Gateway IP Address

9. Highlight TCP Port Number, and press the backspace key to erase the current value, then type the new value.

The default is 3260.

1. Highlight Jumbo Frame and press the spacebar to toggle between Enabled and Disabled.
2. Press Ctrl-A to save your settings.

Viewing VLAN Entries

To view the current VLAN entries:

1. From the Main Menu, highlight Network Management and press Enter.
2. Highlight VLAN and press Enter.

The list of VLAN entries appears. The Member Interface refers to an iSCSI data port or to the link aggregate number.

Creating a VLAN Entry

This feature enables you to create a virtual local area network (VLAN) using the iSCSI data ports on your subsystem.

If you plan to aggregate the iSCSI ports, create a link aggregation before you create the VLAN. See “Creating a Link Aggregation Entry” on page 166.

If you plan to use jumbo frames for the VLAN, enable jumbo frames for the iSCSI ports before you create the VLAN. See "Making iSCSI Data Port Settings" on page 163.

To create a VLAN entry:

1. From the Main Menu, highlight Network Management and press Enter.
2. Highlight VLAN and press Enter.
3. Highlight Create New VLAN Entry and press Enter.
4. Highlight Member Interface and press the spacebar to toggle through iSCSI Port 1 or Port 2.
5. Highlight VLAN Name and type a name for your VLAN.

Maximum of 15 characters. Use letters, numbers, space between words and underscore.

1. Highlight VLAN Tag and type a tag number.

Use 2 though 4094.

1. Highlight Jumbo Frame and press the spacebar to toggle between Enabled and Disabled.
2. Highlight IP Address and type an IP address for your VLAN.
3. If you want to change the subnet mask, highlight Subnet Mask, press the backspace key to erase the default value, then enter a new value.
4. If you want to change the TCP port number, highlight TCP Port Number, press the backspace key to erase the default value, then enter a new value.
5. Press Ctrl-A to save your settings.

Changing a VLAN Entry

To change a VLAN entry:

1. From the Main Menu, highlight Network Management and press Enter.
2. Highlight VLAN and press Enter.
3. Highlight a VLAN entry from the list and press Enter.
4. If you want to change the tag number, highlight VLAN Tag, press the backspace key to erase the current value, then enter a new value. Use the numbers 2 though 4094.
5. If you want to change the IP address, highlight IP Address, press the backspace key to erase the current value, then enter a new value.
6. If you want to change the TCP port number, highlight TCP Port Number, press the backspace key to erase the default value, then enter a new value.
7. If you want to change the subnet mask, highlight Subnet Mask, press the backspace key to erase the current value, then enter a new value.
8. Highlight Jumbo Frame and press the spacebar to toggle between Enabled and Disabled.
9. Highlight Member Interface and press the spacebar to toggle through the choices.
10. Press Ctrl-A to save your settings.

Deleting a VLAN Entry

To delete a VLAN entry:

1. From the Main Menu, highlight Network Management and press Enter.
2. Highlight VLAN and press Enter.
3. Highlight a VLAN from the list and press the spacebar to mark it with an asterisk (*).
4. Highlight Delete Marked Entries and press Enter.
5. Press Y to confirm the deletion.

Viewing Link Aggregation Entries

To view the current Link Aggregation entries:

1. From the Main Menu, highlight Network Management and press Enter.
2. Highlight Link Aggregation and press Enter. The list of Link Aggregation entries appears.

Creating a Link Aggregation Entry

This feature enables you to aggregate the iSCSI data ports on your subsystem to increase bandwidth.

If an iSCSI port is part of a VLAN, you must delete the VLAN entry before you can use the iSCSI port to create a link aggregation. See “Deleting a VLAN Entry” on page 165.

To create a link aggregation entry:

1. From the Main Menu, highlight Network Management and press Enter.
2. Highlight Link Aggregation and press Enter.
3. Highlight Create New Link Aggregation Entry and press Enter.
4. Highlight Trunk ID and type a value.

Use the numbers 1 through 32.

1. Highlight Master Port and press the spacebar to toggle to one of the iSCSI port numbers.
2. Highlight Slave Port and press the spacebar to toggle to the other iSCSI port number.
3. Press Ctrl-A to save your settings.

Changing a Link Aggregation Entry

1. From the Main Menu, highlight Network Management and press Enter.
2. Highlight Link Aggregation and press Enter.
3. Highlight a Link Aggregation entry in the list and press Enter.
4. Highlight Master Port and press the spacebar to toggle to one of the iSCSI port numbers.
5. Highlight Slave Port and press the spacebar to toggle to the other iSCSI port number.
6. Press Ctrl-A to save your settings.

Deleting a Link Aggregation Entry

To delete a link aggregation entry:

1. From the Main Menu, highlight Network Management and press Enter.
2. Highlight Link Aggregation and press Enter.
3. Highlight a Link Aggregation entry from the list and press the spacebar to mark it with an asterisk (*).
4. Highlight Delete Marked Entries and press Enter.
5. Press Y to confirm the deletion.

Managing iSCSI Connections

A detailed explanation of these iSCSI functions, how and when they are used, and their relationship to one another is beyond the scope of this document. For more information, contact the Internet Engineering Task Force at http://www.ietf.org/.

Network connections and settings are discussed under “Making iSCSI Data Port Settings” on page 163.

Functions include:

• Viewing Node Information (page 167)
• Making Node Settings (page 168)
• Viewing Target Port Information (page 168)
  • Viewing Data Port Statistics (page 169)
  • Viewing Portal Information (page 169)
  • Viewing Session Information (page 169)
  • Viewing iSNS Information (page 169)
• Making iSNS Settings (page 170)
  • Viewing CHAPs (page 170)
• Adding CHAPs (page 170)
• Editing CHAPs (page 171)
• Deleting CHAPs (page 171)
• Pinging iSCSI Connections (page 171)

Viewing Node Information

To view iSCSI node information:

1. From the Main Menu, highlight iSCSI Management and press Enter.
2. Highlight iSCSI Node and press Enter.
   Node information appears.

Viewing Node Statistics

To view iSCSI node or iSCSI layer statistics:

1. From the Main Menu, highlight iSCSI Management and press Enter.
2. Highlight iSCSI Node and press Enter.
3. Highlight iSCSI Node Statistics and press Enter.
   The node statistics appear.

Making Node Settings

These settings affect both VTrak iSCSI data ports.

Note that Header and Data Digest work best with initiators that have a TCP Offload Engine (TOE).

To make iSCSI node settings:

1. From the Main Menu, highlight iSCSI Management and press Enter.
2. Highlight iSCSI Node and press Enter. Node information appears.
3. Highlight iSCSI Node Settings and press Enter. This screen enables you to make iSCSI Node Settings.

4. Highlight the items you want and press the backspace key to erase the current value, then type the new value:

5. Node Name

6. Node Alias – Maximum of 32 characters. Use letters, numbers, space between words and underscore. An alias is optional.
7. Outstanding R2T
   • Maximum Burst Length
8. Default Time to Wait

9. Default Time to Retain

10. Highlight the items you want to set and press the spacebar to toggle between Enabled and Disabled:

11. Header Digest

12. Data Digest
    • Unidirectional CHAP Authorization
    • Bidirectional CHAP Authorization

13. Press Ctrl-A to save your settings.

Viewing Target Port Information

To view iSCSI port target information:

1. From the Main Menu, highlight iSCSI Management and press Enter.
2. Highlight iSCSI Ports and press Enter.
3. Highlight Target Port 1 or Target Port 2 and press Enter. Port information appears.

Viewing Data Port Statistics

To view iSCSI port statistics:

1. From the Main Menu, highlight iSCSI Management and press Enter.
2. Highlight iSCSI Ports and press Enter.
3. Highlight Target Port 1 or Target Port 2 and press Enter.
4. Highlight one of the following and press Enter:

• MAC Layer Statistics
- IP Layer Statistics
- TCP Layer Statistics

Viewing Portal Information

To view iSCSI portal information:

1. From the Main Menu, highlight iSCSI Management and press Enter.
2. Highlight iSCSI Portal and press Enter.

The following information appears:

• Portal ID – 1 to 34
• IP address – IP address of the port or VLAN
• TCP Port number – 3260 is the default
• Associated Type – iSCSI or VLAN
• Interface Name – Port number or VLAN name

Also see “Making iSCSI Data Port Settings” on page 163 and “Viewing VLAN Entries” on page 164.

Viewing Session Information

To view iSCSI session information:

1. From the Main Menu, highlight iSCSI Management and press Enter.
2. Highlight iSCSI Sessions and press Enter.

A list of the current iSCSI sessions appears.

Viewing iSNS Information

Internet Storage Name Service (iSNS) is a protocol used to facilitate the automated discovery, management, and configuration of iSCSI and Fibre Channel devices on a TCP/IP network.

To view iSCSI iSNS information:

1. From the Main Menu, highlight iSCSI Management and press Enter.

2. Highlight iSCSI iSNS Options and press Enter.

The current iSNS settings appear.

Making iSNS Settings

To make iSCSI iSNS settings:

1. From the Main Menu, highlight iSCSI Management and press Enter.
2. Highlight iSCSI iSNS Options and press Enter.
3. Highlight iSNS Settings and press Enter.
4. Highlight iSNS and press the spacebar to toggle between Enable and Disable.

When Enable is displayed, the iSNS disabled, and you must provide an iSNS IP address and port number.

1. Highlight the items you want and press the backspace key to erase the current value, then type the new value:

2. iSNS IP address

3. iSNS Port number

4. Press Ctrl-A to save your settings.

Viewing CHAPs

To view a list of iSCSI CHAPs:

1. From the Main Menu, highlight iSCSI Management and press Enter.
2. Highlight iSCSI CHAPs and press Enter.

A list of the current CHAPs appears.

Adding CHAPs

To add an iSCSI CHAP:

1. From the Main Menu, highlight iSCSI Management and press Enter.
2. Highlight iSCSI CHAPs and press Enter.
3. Highlight Create New CHAP Entry and press Enter.
4. Highlight Name and type a name for the CHAP.
5. Highlight Type and press the spacebar to toggle between Peer and Local. Peer is one-way. Local is bi-directional.
6. Highlight Secret and type a name of 16 or more characters.
7. Highlight Retype Secret and type the secret again to verify.
8. Press Ctrl-A to save the CHAP.

Editing CHAPs

To edit an iSCSI CHAP:

1. From the Main Menu, highlight iSCSI Management and press Enter.
2. Highlight iSCSI CHAPs and press Enter.
3. Highlight the CHAP you want to edit and press Enter.
4. Highlight Name and press the backspace key to erase the current value, then type the new value
5. Highlight Type and press the spacebar to toggle between Peer and Local. Peer is one-way. Local is bi-directional.
6. Highlight Secret and type a name of 16 or more characters.
7. Highlight Retype Secret and type the secret again to verify.
8. Press Ctrl-A to save the CHAP.

Deleting CHAPs

To delete an iSCSI CHAP:

1. From the Main Menu, highlight iSCSI Management and press Enter.
2. Highlight iSCSI CHAPs and press Enter.
3. Highlight the CHAP you want to delete and press Enter to mark it. The mark is an asterisk (*) to the left of the listing.
4. Highlight Delete Marked Entries and press Enter.
5. Press Y to confirm the deletion.

Pinging iSCSI Connections

This function enables you to ping other network nodes (PCs, servers, etc.) through VTrak's iSCSI ports.

To ping an iSCSI connection:

1. From the Main Menu, highlight iSCSI Management and press Enter.
2. Highlight Ping and press Enter.
3. Type the IP address you want to ping in the IP Address field.
4. Highlight Ping Through and press the spacebar to select an iSCSI port.
5. Highlight Ping and press Enter.

The results of the ping are displayed on the screen.

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 147 and “Managing Logical Drives” on page 158 for more information about how and when to use background activities.

Background Activity Management includes the following functions:

• Viewing Current Background Activities (page 172)
• Making Background Activity Settings (page 172)

Viewing Current Background Activities

From the Main Menu, highlight Background Activity and press Enter. A count of current background activities appears, including:

• Rebuild
• PDM – Predictive Data Migration
• Synchronization
• Redundancy Check

- M i g r a t i o n

- Transition

- Initialization

- Media Patrol

Making Background Activity Settings

1. From the Main Menu, highlight Background Activity and press Enter.
2. Highlight Background Activity Settings and press Enter.
3. Highlight following and press the spacebar to toggle between Enabled and Disabled.
4. Media Patrol – Checks the magnetic media on physical drives

5. Auto Rebuild – If there is a spare drive of adequate capacity, a critical disk array will begin to rebuild automatically. If not spare drive is available, the disk array will begin to rebuild as soon as you replace the failed physical drive with an unconfigured physical drive of equal or greater size.

6. Highlight following and press the spacebar to toggle through Low, Medium, and High rates:

7. Rebuild – Checks the data integrity on disk arrays

8. Migration – Change RAID level or add physical dries to disk arrays

9. PDM – Looks for bad blocks on the physical drives of disk arrays

10. Transition – Returns a revertible spare drive to spare status
11. Synchronization – Checks the data integrity on disk arrays
12. Initialization – Sets all data bits in the logical drive to zero
13. Redundancy Check – Checks, reports and can correct data inconsistencies in logical drives

The rates are defined as follows:

• 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.

• Highlight the following PDM trigger settings and press the backspace key to erase the current value:

• Reassigned Block Threshold – 1 to 512 blocks

• Error Block Threshold – 1 to 1024 blocks

• Press Ctrl-A to save your settings.

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 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 174)
• Clearing Runtime Events (page 174)
  • Viewing NVRAM Events (page 174)
• Clearing NVRAM Events (page 175)

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:

• 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.

• Press the up and down arrow keys to scroll through the log.

Clearing Runtime Events

To clear the Runtime Event log:

1. From the Main Menu, highlight Event Viewer and press Enter.
2. Highlight Clear Runtime Event Log and press Enter.
3. Press Y to confirm.

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. From the Main Menu, highlight Event Viewer and press Enter.
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 – (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.

• Press the up and down arrow keys to scroll through the log.

Clearing NVRAM Events

To clear the Runtime Event log:

1. From the Main Menu, highlight Event Viewer and press Enter.
2. Highlight NVRAM Events and press Enter.
3. Highlight Clear NVRAM Event Log and press Enter.
4. Press Y to confirm.

Managing Spare Drives

Spare Drive Management includes the following functions:

• Viewing a list of Spare Drives (page 176)
• Creating a Spare Drive (page 176)
• Making Spare Drive Settings (page 177)
• Running Spare Check (page 177)
• Deleting a Spare Drive (page 178)

Viewing a list of Spare Drives

To view a list of spare drives:

1. From the Main Menu, highlight Additional Info and Management and press Enter.
2. 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 239 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

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 144.

1. From the Main Menu, highlight Additional Info and Management and press Enter.
2. Highlight Spare Drive Management and press Enter.
3. Highlight Create New Spare Drive and press Enter.
4. Highlight Physical Drive Number and press the backspace key to erase the current value, then type the new value.
   Specify the number of the physical drive you want for your spare. The available drive numbers are in parentheses.
5. Highlight Revertible and press the spacebar to toggle between Yes and No.

A reversible drive can be returned to spare status after you replace the failed drive in a disk array. See “Transition” on page 239 for more information.

1. 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.

1. If you chose Dedicated, highlight Dedicated to Arrays and press the backspace key to erase the current value, then type the new value.

Specify the number(s) of the disk array(s) you want to assign your spare. The current disk arrays are listed in parentheses.

1. Press Ctrl-A to save the spare drive.

Making Spare Drive Settings

To change spare drive settings:

1. From the Main Menu, highlight Additional Info and Management and press Enter.
2. Highlight Spare Drive Management and press Enter.

A list of the current spare drives appears, including the following parameters:

1. Highlight the spare drive you want to change and press Enter.

2. Highlight the setting you want to change:

3. Revertible – A revertible drive can be returned to spare status after you replace the failed drive in a disk array. See “Transition” on page 239 for more information.

4. Type – Dedicated means this spare drive can only be used with the specified disk array(s). Global means this spare drive can be used by any disk array.

5. Press the spacebar to toggle between the choices.

6. For dedicated spares, type the array number the spare is assigned to.
7. Press Ctrl-A to save your settings.

Running Spare Check

To run Spare Check:

1. From the Main Menu, highlight Additional Info and Management and press Enter.
2. Highlight Spare Drive Management and press Enter.

A list of the current spare drives appears.

1. Highlight the spare drive you want to check and press Enter.
2. Highlight Start Spare Check and press Enter.

The results appear next to Spare Check Status.

Deleting a Spare Drive

Caution

If the spare drive you delete is the only spare, the controller will not rebuild a critical array until you provide a new spare drive.

1. 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.

1. Highlight Delete Marked Spare Drives and press Enter.
2. Press Y to confirm the deletion.

Working with LUN Mapping

For iSCSI, LUN Masking is the process of applying a LUN Map so that each initiator can only access the LUNs specified for it.

Features include:

• Viewing Initiators (page 179)
- Enabling LUN Mapping (page 179)
- Creating Initiators (page 179)
- Deleting Initiators (page 180)
- Mapping LUNs to Initiators (page 180)

Viewing Initiators

To view a list of iSCSI initiators:

1. From the Main Menu, highlight Additional Info and Management and press Enter.
2. Highlight LUN Mapping and press Enter.

A list of the current initiators appears.

LUN Mapping must be enabled in order for VTrak to recognize the initiator. If LUN Mapping is currently disabled, highlight Enable LUN Mapping and press Enter.

Enabling LUN Mapping

In the CLU, LUN masking is called "LUN mapping."

To enable LUN Mapping:

1. From the Main Menu, highlight Additional Info and Management and press Enter.
2. Highlight LUN Mapping and press Enter.
3. Highlight Enable LUN Mapping and press Enter.

Creating Initiators

To create a new iSCSI initiator:

1. From the Main Menu, highlight Additional Info and Management and press Enter.
2. Highlight LUN Mapping and press Enter.
3. Highlight Create New Initiator and press Enter.
4. Type the name of the initiator.

An iSCSI initiator name is the iSCSI name of the initiator device and is composed of a single text string. iSCSI WWNs are somewhat different from regular WWNs.

Obtain the initiator name from the initiator utility on your host system.

Note that the initiator name you input must match exactly in order for the connection to work.

1. Press Ctrl-A to save the initiator.

Note

LUN Mapping must be enabled in order for VTrak to recognize the initiator.

Deleting Initiators

To delete an iSCSI initiator:

1. From the Main Menu, highlight Additional Info and Management and press Enter.
2. Highlight LUN Mapping and press Enter.
3. 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.
4. Highlight Delete Marked Initiators and press Enter.
5. Press Y to confirm the deletion.

Mapping LUNs to Initiators

To map a LUN to an iSCSI initiator:

1. From the Main Menu, highlight Additional Info and Management and press Enter.
2. Highlight LUN Mapping and press Enter.
3. Highlight an existing Initiator and press Enter.
   A list of logical drives displays.

4. 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.

Managing Users

User Management includes the following functions:

• Viewing User Information (page 181)
• Creating a User (page 181)
• Changing a User's Password (page 182)
• Changing a User's Display Name and Email Address (page 182)
• Changing a User's Privilege and Status (page 183)
• Deleting a User (page 183)

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. From the Main Menu, highlight Additional Info and Management and press Enter.
2. Highlight User Management and press Enter.

A list of the current users appears.

Creating a User

To create a new user account:

1. From the Main Menu, highlight Additional Info and Management and press Enter.
2. Highlight User Management and press Enter.

3. Highlight Create New User and press Enter.

4. Highlight each field and type in the appropriate information:

5. User name (no spaces)

6. Password (Optional. Maximum 32 characters. Use letters, numbers, space between words and underscore)

7. Display name (Optional)

8. Highlight Privilege and press the space bar to toggle though the options: For definitions of each privilege level, see the List of User Privileges below.

9. Highlight Status and press the space bar to toggle between the options:

- Enabled – Allows the user to log in to the system

- Disabled – Prevents the user from logging in to the system

1. Press Ctrl-A to save the user.

List of User Privileges

• View – Allows the user to see all status and settings but not to make any changes
• Maintenance – Allows the user to perform maintenance tasks including Rebuilding, PDM, Media Patrol, and Redundancy Check
• Power – 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.
• Super – 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.

Changing a User's Password

Each user can change their own password. A Super user can change other user's passwords. To change a user's password:

1. From the Main Menu, highlight Additional Info and Management and press Enter.
2. Highlight User Management and press Enter.
3. Highlight a User in the list and press Enter.
4. Highlight Change Password... and press Enter.
5. Highlight New Password and type the password.
6. Highlight Retype Password and type the password again to verify.
7. Press Ctrl-A to save the password.

Changing a User's Display Name and Email Address

Each user can change their display name and email address. To change a display name or email address:

1. From the Main Menu, highlight Additional Info and Management and press Enter.
2. Highlight User Management and press Enter.
3. Highlight a User in the list and press Enter.
4. Highlight Display Name and press Enter.
5. Highlight the items you want and press the backspace key to erase the current value, then type the new value:

• U s e r n a m e

- Email address

1. Press Ctrl-A to save the settings.

Changing a User's Privilege and Status

No user can change their own privilege or status. To change another user's privilege or status.

1. Log in as the Administrator or a Super user.
2. From the Main Menu, highlight Additional Info and Management and press Enter.
3. Highlight User Management and press Enter.
4. Highlight a User in the list and press Enter.

5. Highlight Display Name and press Enter.

6. Highlight Privilege and press the space bar to toggle though the options: For definitions of each privilege level, see "List of User Privileges" on page 182.

7. Highlight Status and press the space bar to toggle between the options:

8. Enabled – Allows the user to log in to the system

9. Disabled – Prevents the user from logging in to the system

10. Press Ctrl-A to save the settings.

Deleting a User

To delete a user:

1. Log in under a user name other than the one you want to delete.
2. From the Main Menu, highlight Additional Info and Management and press Enter.
3. Highlight User Management and press Enter.
4. 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.
5. Highlight Delete Marked Users and press Enter.
6. Press Y to confirm the deletion.

Working with Software Management

Software Management includes the following functions:

• Making Email Settings (page 184)
• Making SLP Settings (page 185)
• Making Webserver Settings (page 185)
• Making Telnet Settings (page 186)
• Making SNMP Settings (page 186)
• Managing SNMP Trap Sinks (page 187)
• Making CIM Settings (page 188)
• Making Netsend Settings (page 188)
• Managing Netsend Recipients (page 189)

Making Email Settings

By default, Email service is set to Automatic and its normal status is Started.

To make Email service settings:

1. From the Main Menu, highlight Additional Info and Management and press Enter.
2. Highlight Software Management and press Enter.
3. Highlight Email and press Enter.
4. Highlight Startup Type and press the spacebar to toggle between Automatic and Manual.

5. Highlight the following and press the backspace key to erase the current value, then type the new value:

6. Server IP address

7. Server Port number – 25 is the default

8. 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.

1. The following items are optional but recommended. Highlight and press the backspace key to erase the current value, then type the new value:

2. Sender's email address

3. Subject Line for the email message

4. Press Ctrl-A to save your settings.

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. From the Main Menu, highlight Additional Info and Management and press Enter.
2. Highlight Software Management and press Enter.
3. Highlight SLP and press Enter.
4. Highlight Startup Type and press the spacebar to toggle between Automatic and Manual.
5. 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. From the Main Menu, highlight Additional Info and Management and press Enter.
2. Highlight Software Management and press Enter.
3. Highlight Webserver and press Enter.
4. Highlight Startup Type and press the spacebar to toggle between Automatic and Manual.

5. Highlight the following and press the backspace key to erase the current value, then type the new value:

6. HTTP Port – 80 is the default

7. Session Time Out – 24 minutes is the default. 1440 minutes = 24 hours

8. Highlight SSL and press the spacebar to toggle between Enabled and Disabled.

9. Highlight HTTPS Port and press the backspace key to erase the current value, then type the new value. 443 is the default.

10. Press Ctrl-A to save your settings.

To start, stop or restart the Webserver service, highlight Start, Stop, or Restart and press Enter.

Making Telnet Settings

By default, Telnet service is set to Automatic and its normal status is Started. To make Telnet service settings:

1. From the Main Menu, highlight Additional Info and Management and press Enter.
2. Highlight Software Management and press Enter.
3. Highlight Telnet and press Enter.
4. Highlight Startup Type and press the spacebar to toggle between Automatic and Manual.

5. 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

7. Session Time Out – 24 minutes is the default. 1440 minutes = 24 hours

8. Maximum number of connections – 4 is the default

9. Press Ctrl-A to save your settings.

To start, stop or restart the Telnet service, highlight Start, Stop, or Restart and press Enter.

Making SNMP Settings

By default, SNMP (Simple Network Management Protocol) service is set to Automatic and its normal status is Started.

To make SNMP service settings:

1. From the Main Menu, highlight Additional Info and Management and press Enter.
2. Highlight Software Management and press Enter.
3. Highlight SNMP and press Enter.
4. Highlight Startup Type and press the spacebar to toggle between Automatic and Manual.

5. 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

7. System Name – (optional) Type a system name in this field

8. System Location – Type a country name in this field

9. System Contact – Type the email address of your system administrator in this field

10. Read Community – Type a community name in this field

11. Write Community – private (no change possible)

12. Press Ctrl-A to save your settings.

To start, stop or restart the SNMP service, highlight Start, Stop, or Restart and press Enter.

Managing SNMP Trap Sinks

Creating a SNMP trap sink

To create a trap sink:

1. From the Main Menu, highlight Additional Info and Management and press Enter.
2. Highlight Software Management and press Enter.
3. Highlight SNMP and press Enter.
4. 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.
2. Highlight Software Management and press Enter.
3. Highlight Create New Trap Sink and press Enter
4. Highlight Trap Sink IP address and press the backspace key to erase the current value, then type the new IP address in this field.

5. Highlight Trap Filter and press the spacebar to toggle through the severity levels.
   The Severity Levels are (lowest to highest) Information, Warning, Minor, Major, Critical and Fatal.

6. Press Ctrl-A to save the Trap Sink.

Deleting a trap sink

To delete a trap sink:

1. From the Main Menu, highlight Additional Info and Management and press Enter.
2. Highlight Software Management and press Enter.
3. 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.

1. Highlight Delete Marked Entries and press Enter.

Making CIM Settings

By default, CIM (Common Information Model [a protocol]) service is set to Automatic and its normal status is Started.

To make CIM service settings:

1. From the Main Menu, highlight Additional Info and Management and press Enter.
2. Highlight Software Management and press Enter.
3. Highlight CIM and press Enter.
4. Highlight Startup Type and press the spacebar to toggle between Automatic and Manual.
5. Highlight HTTP and press the spacebar to toggle between Enabled and Disabled.
6. Highlight HTTP Port, press the backspace key to erase, type new value. 5988 is the default port number.
7. Highlight HTTPS and press the spacebar to toggle between Enabled and Disabled.
8. Highlight HTTPS Port, press the backspace key to erase, type new value. 5989 is the default port number.
9. Highlight Authentication and press the spacebar to toggle between Enabled and Disabled.

Note: There is only one user. The default name is cim. No changes are possible.

Note: CIM service must be running to change the password.

The default password is password.

1. Highlight Change Password... and press Enter to change the password.

2. Highlight Old Password and type the current password.

3. Highlight New Password and type a new password.

4. Highlight Retype Password and type the new password again.

5. Press Ctrl-A to save your settings.

To start, stop or restart the CIM service, highlight Start, Stop, or Restart and press Enter.

Making Netsend Settings

By default, Netsend service is set to Manual and its normal status is Stopped.

To make Netsend service settings:

1. From the Main Menu, highlight Additional Info and Management and press Enter.
2. Highlight Software Management and press Enter.
3. Highlight Netsend and press Enter.
4. Highlight Startup Type and press the spacebar to toggle between Automatic and Manual.
5. 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

Note that the Messenger service must be running on the recipient PC in order to receive reports.

Adding a recipient

To add a recipient:

1. From the Main Menu, highlight Additional Info and Management and press Enter.
2. Highlight Software Management and press Enter.
3. Highlight Netsend and press Enter.
4. Highlight Message Recipient and press Enter.
5. Highlight Create New Message Recipient and press Enter.
6. Type the recipient's IP address into the field provided.
7. Highlight Message Event Severity Filter and press the spacebar to change severity levels.
   The selected level and all higher severity levels of severity will be reported. Severity levels (from lowest to highest) are: Info, Warning, Minor, Major, Critical, and Fatal.
8. Press Ctrl-A to save your settings.

Changing Recipient Settings

To change recipient settings:

1. From the Main Menu, highlight Additional Info and Management and press Enter.
2. Highlight Software Management and press Enter.
3. Highlight the recipient whose settings you want to change and press Enter.

4. Type the recipient's IP address into the field provided.

5. Highlight Message Event Severity Filter and press the spacebar to change severity levels.

6. Press Ctrl-A to save your settings.

Deleting a Recipient

To delete a recipient:

1. From the Main Menu, highlight Additional Info and Management and press Enter.
2. Highlight Software Management and press Enter.
3. 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
4. Highlight Delete Marked Entries and press Enter.

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 PC's Firewall settings. Refer to your OS documentation for more information.

Flashing through TFTP

Use this function to flash the VTrak's firmware. See "Updating the Firmware in the CLU" on page 202 for this procedure.

Clearing Statistics

This function clears the statistical counts for the RAID controller, iSCSI ports, physical drives, and logical drives. To clear statistics:

1. From the Main Menu, highlight Additional Info and Management and press Enter.
2. Highlight Clear Statistics and press Enter.
3. Press Y to confirm the deletion.

Restoring Factory Defaults

This function restores the factory default settings to the firmware and software items you select.

Caution

Use this function with care. Do not restore to default settings for any item unless you are sure this action is needed.

1. From the Main Menu, highlight Additional Info and Management and press Enter.
2. Highlight Restore Factory Defaults and press Enter.
3. Highlight the setting group you want and press the spacebar to toggle between Yes and No.
   Yes means this setting will be restored to the default value.
4. Highlight Restore Factory Defaults and press Enter.
5. Press Y to confirm the reset.

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 194)
• Shutting down the VTrak – Serial Connection (page 194)

Shutting down the VTrak – Telnet Connection

This function enables you to shutdown the VTrak subsystem on a Telnet connection. You can only do part of this procedure in the CLU. Additional action is required, as described below.

To shutdown the VTrak:

1. From the Main Menu, highlight Additional Info and Management and press Enter.
2. Highlight Shutdown or Restart and press Enter.
3. Highlight Shutdown or Restart and press Enter.
4. Highlight Option and press the spacebar to display Restart.

5. Highlight Submit and press Enter. A warning message appears.

6. Press Y to continue. The screen will go blank.

7. Wait for no less than two minutes.

8. Manually turn off the power supply switches on the back of the subsystem.

Shutting down the VTrak – Serial Connection

This function enables you to shutdown the VTrak subsystem on a serial connection. You can only do part of this procedure in the CLU. Additional action is required, as described below.

To shutdown the VTrak:

1. From the Main Menu, highlight Additional Info and Management and press Enter.
2. Highlight Shutdown or Restart and press Enter.
3. Highlight Shutdown or Restart and press Enter.
4. Highlight Option and press the spacebar to display Restart.
5. Highlight Submit and press Enter. A warning message appears.

6. Press Y to continue.

7. Turn off the power supply switches when you see the following message:

Shutdown complete. It is now safe to power off the subsystem.

Restarting the Subsystem

There are two methods for restarting the subsystem. Choose one of the following procedures:

• Restarting the Subsystem (page 196)
• Restarting VTrak – Serial Connection (page 196)

Restarting VTrak – Telnet Connection

This function enables you to restart the VTrak subsystem on a Telnet connection. You can only do part of this procedure in the CLU. Additional action is required, as described below. To restart the VTrak:

1. From the Main Menu, highlight Additional Info and Management and press Enter.
2. Highlight Shutdown or Restart and press Enter.
3. Highlight Option and press the spacebar to display Restart.

4. Highlight Submit and press Enter.
   A warning message appears.

5. Press Y to continue.

The screen will go blank.

1. Wait for no less than two minutes.

2. Re-establish your Telnet connection to the VTrak CLU.

If you cannot re-establish a connection, wait 30 seconds, then try again.

Restarting VTrak – Serial Connection

This function enables you to restart the VTrak subsystem on a serial connection. You can only do part of this procedure in the CLU. Additional action is required, as described below. To restart the VTrak:

1. From the Main Menu, highlight Additional Info and Management and press Enter.
2. Highlight Shutdown or Restart and press Enter.
3. Highlight Option and press the spacebar to display Restart.

4. Highlight Submit and press Enter.
   A warning message appears.

5. Press Y to continue.

The screen will display shutdown and startup functions.

1. When the Login: prompt appears, log into the CLU again.

Working with the Buzzer

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. The buzzer provides the audible alarm. See “VTrak is Beeping” on page 244.

Choose one of the following procedures:

• Silencing the Buzzer (page 197)
- Making Buzzer Settings (page 197)
- Testing the Buzzer (page 197)

Silencing the Buzzer

To change buzzer settings:

1. From the Main Menu, highlight Buzzer and press Enter.
   A list of Controllers appears with the current buzzer setting and status.
2. Highlight Mute and press Enter.
   The buzzer goes silent. If another trigger event occurs, the buzzer will sound again.

Making Buzzer Settings

This function enables the buzzer on the controller.

To change buzzer settings:

1. From the Main Menu, highlight Buzzer and press Enter.
   A list of Controllers appears with the current buzzer setting and status.
2. Highlight the Controller whose buzzer you want to set and press Enter.
3. Highlight Enabled and press the spacebar to toggle between Yes and No.
4. Press Ctrl-A to save your settings.

Testing the Buzzer

To test the buzzer:

1. From the Main Menu, highlight Buzzer and press Enter.
   A list of Controllers appears with the current buzzer setting and status.
2. Highlight Sound and press Enter.
   The buzzer sounds. Highlight Mute and press Enter to silence the buzzer.

Chapter 6: Maintenance

This chapter covers the following topics:

• Updating the Firmware in WebPAM PROe (page 199)
• Updating the Firmware in the CLU (page 202)
• Replacing a Power Supply (page 204)
• Replacing a Cooling Unit Fan or Blower (page 205)
• Replacing a Cache Battery (page 211)
• Replacing a RAID Controller (page 216)

Updating the Firmware in WebPAM PROe

A firmware update consists of the following actions:

• Downloading the Firmware Image File (page 199)
• Updating Firmware from TFTP Server (page 199) or Updating Firmware from your PC (page 200)
• Restarting the Subsystem (page 201)

Downloading the Firmware Image File

Go to the Promise website at http://www.promise.com/support and download the latest firmware image (.img) file to your TFTP server or your PC. The firmware update image file includes all of the files for the VTrak, including:

• F i r m w a r e
- Software
- Kernel
- RedBoot
- Other files

Updating Firmware from TFTP Server

To update the firmware from a TFTP server:

1. Click the Subsystem icon in Tree View.

2. Click the Administrative Tools icon.

3. Click the Software Management icon.

4. Click the Firmware Update tab.

5. Do one of the following actions:

- Click the Download from TFTP Server option, then click the Next button.

- From the Firmware Update tab dropdown menu, select Download from TFTP Server.

1. Enter the hostname or IP address of your TFTP server in the field provided.
2. Enter the port number of your TFTP server in the field provided (69 is the default).
3. Enter the filename of the Firmware Update file in the field provided.
4. Click the Submit button.
5. When the download is completed, click the Next button.

A popup message appears warning you not to reboot the VTrak during the firmware update procedure.

1. In the popup message, click the OK button.
   The update progress displays. Then a popup message appears to tell you to reboot the VTrak.
2. In the popup message, click the OK button.
3. Restart the VTrak. See "Restarting the Subsystem" on page 201.

Note

After you click the Submit button, if WebPAM PROe displays this message: error transferring image, you entered an incorrect file name or an incorrect location. Check the information and try again.

Updating Firmware from your PC

To update the firmware from your PC:

1. Click the Subsystem icon in Tree View.
2. Click the Administrative Tools icon.
3. Click the Software Management icon.
4. Click the Firmware Update tab.

5. Do one of the following actions:

6. Click the Download Flash File from Local File through HTTP option, then click the Next button.

7. From the Firmware Update tab dropdown menu, select Download from Local File.

8. Enter the filename of the Firmware Update file in the field provided.

Or, click the Browse... button and select the Firmware Update file in the Open dialog box.

1. Click the Submit button.

2. When the download is completed, click the Next button.

A popup message appears to warn you not to reboot the VTrak during the firmware update procedure.

1. In the popup message, click the OK button.

The update progress displays. Then a popup message appears to tell you to reboot the VTrak.

1. In the popup message, click the OK button.

2. Restart the VTrak. See "Restarting the Subsystem" on page 201.

Note

After you click the Submit button, if WebPAM PROe displays this message: error transferring image, you entered an incorrect file name or an incorrect location. Check the information and try again.

Restarting the Subsystem

Warning

Do not restart the VTrak during a firmware upgrade procedure. Wait until the upgrade is one and you are prompted to restart.

To restart the VTrak subsystem:

1. Click the Subsystem icon in Tree View.
2. Click the Administrative Tools icon.
3. Click the Shutdown link in Management View.

A Shutdown or Restart tab will appear.

1. On the Shutdown or Restart tab, select Restart from the dropdown menu.
2. Click the Submit button.
3. In the warning box, click the OK button.
4. In the confirmation box, type the word confirm in the field provided.
5. Click the OK button.

When the controller shuts down, your WebPAM PROe connection will be lost.

1. Wait for two to three minutes.
2. In your browser, log into WebPAM PROe once again.

If you cannot log in, wait for 30 seconds, and try again. Repeat until login is successful.

Updating the Firmware in the CLU

A firmware update consists of the following actions:

• Downloading the Firmware Image File (page 202)
• Updating the Firmware (page 202)
• Restarting Subsystem over a Telnet Connection (page 202)
• Restarting Subsystem over a Serial Connection (page 203)

Downloading the Firmware Image File

Go to the Promise website at http://www.promise.com/support and download the latest firmware image file to your TFTP server.

Updating the Firmware

To update the firmware file in the CLU:

1. From the Main Menu, highlight Additional Info and Management, and press Enter.
2. Highlight Flash through TFTP and press Enter.
3. Highlight TFTP Server and type the IP address of your TFTP server in the field provided.

4. 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. Highlight File Name and type the file name of the firmware image file in the field provided.

6. Highlight Start and press Enter.

A message appears to tell you to reboot the VTrak.

1. Restart the VTrak.

See “Restarting Subsystem over a Telnet Connection” on page 202 or “Restarting Subsystem over a Serial Connection” on page 203.

Restarting Subsystem over a Telnet Connection

Warning

Do not restart the VTrak during a firmware upgrade procedure. Wait until the upgrade is one and you are prompted to restart.

To restart the VTrak subsystem on a Telnet connection:

1. From the Main Menu, highlight Additional Info and Management, and press Enter.
2. Highlight Shutdown or Restart and press Enter.
3. Press the spacebar to display Restart then press Enter.
   A warning message appears.
4. Press Y to continue.
   The screen will go blank.
5. Wait for two to three minutes.
6. Re-establish your Telnet connection to the VTrak CLU.
   If you cannot re-establish a connection, wait 30 seconds, then try again.

Restarting Subsystem over a Serial Connection

Warning

Do not restart the VTrak during a firmware upgrade procedure. Wait until the upgrade is one and you are prompted to restart.

To restart the VTrak subsystem on a serial connection:

1. From the Main Menu, highlight Additional Info and Management, and press Enter.
2. Highlight Shutdown or Restart and press Enter.
3. Press the spacebar to display Restart then press Enter.
   A warning message appears.
4. Press Y to continue.
   The screen will display shutdown and startup functions.
5. When the Login: prompt appears, log into the CLU again.

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.

Remove the Old Power Supply

To remove the power supply:

1. Verify that the power supply LED is amber or red.
2. Switch off the power.
3. Unplug the power cord.

4. Pull the power supply out of the VTrak enclosure.

5. Press the release button and pull the handle downward as shown. See Figures 1 and 2.

Install a New Power Supply

To install the power supply:

1. Carefully slide the power supply into the enclosure.
2. Gently press the handle in and upward until it locks. See Figures 1 and 2.
3. Plug in the power cord.
4. Switch on the power supply.
5. Verify that the new power supply LED is green.

Figure 1. Replacing a M610i power supply

Close-up of a hand inserting a component into an electronic device (no visible text or symbols)

Close-up of a hand inserting a plastic clip into a server rack with visible power and circuit components (no text or symbols)

Close-up of a hand inserting a fan into an internal drive unit (no visible text or symbols)

Figure 2. Replacing a M310i/M210i power supply

Hand inserting a cable into a server rack with ports and connectors (no visible text or symbols)

Hand holding a device with internal components and ports, no visible text or symbols

Close-up of a hand inserting a fan into a computer drive module (no visible text or symbols)

This completes the power supply replacement procedure.

Replacing a Cooling Unit Fan or Blower

The fan or blower in each cooling unit is replaced as an individual part. No tools are required for this procedure.

1. Verify that the Fan LED is amber or red.

Figure 3. Fan LED (left: M610i, right: M310i/M210i)

1. Press the release button and pull the handle downward. See Figures 4 and 5.
2. Pull the cooling unit out of the VTrak enclosure.

Figure 4. Removing a cooling unit from the M610i

Hand inserting a hexagonal drive into a server rack (no visible text or symbols)

Hand holding a silver hard drive next to a server rack with hexagonal ventilation slots (no visible text or symbols)

Figure 5. Removing a cooling unit from the M310i/M210i

Close-up of a hand inserting a component into a server rack with a hexagonal mesh grille (no visible text or symbols)

Hand inserting a hexagonal heat sink into a server rack (no visible text or symbols)

1. Loosen the thumbscrew. A retainer keeps the thumbscrew in place.
2. Grasp the cover near the thumbscrews and lift it off. Remove the cover to access the fan or blower. See Figures 6 and 7.

Figure 6. Loosen the thumbscrews and remove the cover (M610i)

Figure 7. Loosen the thumbscrews and remove the cover (M310i/m210l)

Exterior view of a silver power supply unit with green circuit board and exposed components (no text or symbols visible)

Loosen the thumbscrews

Hand placing a component into an open electronic device with visible wiring and circuit board (no text or symbols)

Lift the cover

1. Lift the fan or blower off the mounting pins and detach the electrical connector. See Figures 8 and 9.

Figure 8. The M610i fan and its electrical connector

Interior view of an electronic device showing a green circuit board, cable, and fan (no visible text or symbols)

Electrical connector
Fan

Figure 9. The M310i/M210i blower and its electrical connector

1. Attach the electrical connector of the new fan or blower and set the fan or blower in place.

Be sure you position the fan or blower onto the mounting pins. See Figures 10 and 11.

Figure 10. Position the fan onto the mounting pins, pointed outward

Close-up of a server rack with hexagonal grid and rainbow-colored cable, marked by red circles (no text or symbols visible)

Close-up of a computer CPU fan with visible cooling fins and wiring, no text or symbols present

Figure 11. Position the blower onto the mounting pins, pointed outward

Close-up of a metallic cylindrical object with a red circular highlight on its surface (no text or symbols visible)

Interior view of an electronic device showing a green circuit board, black drive fan, and power connector (no readable text or symbols)

Be sure the fan points outward, towards the handle.

1. Place the top section of the cooling unit onto the bottom section and tighten the thumbscrews.
2. Carefully slide the cooling unit into the enclosure.
3. Gently press the handle in and upward until it locks.
   See Figure 12.

Figure 12. Locking the cooling unit handle (left: M610i, right: M310i/M210i

Hand inserting a hexagonal grid into a server rack (no visible text or symbols)

Hand pointing at a server rack with a hexagonal vent and port (no visible text or symbols)

1. Verify that the Fan LEDs are green.

This completes the fan replacement procedure.

Replacing a Cache Battery

The cache battery is located inside the Cooling Unit. The battery is replaced as an individual part.

Cautions

• Try reconditioning the battery before you replace it. See page 98 or page 142 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 will be 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 cooling unit if the Controller's Dirty Cache LED is flashing. See "Unsaved Data in the Controller Cache" on page 281.

To replace a cache battery:

1. Verify that the Battery LED is amber or red. See Figure 13.

Figure 13. Fan LED (left: M610i, right: M310i/M210i)

1. Press the release button and pull the handle downward as shown above.
2. Pull the cooling unit out of the VTrak enclosure. See Figures 14 and 15.

Figure 14. Removing the cooling unit from the M610i

Hand inserting a hexagonal grid into a server rack unit (no visible text or symbols)

Hand inserting a hexagonal mesh into a server rack with network ports (no visible text or symbols)

Figure 15. Removing the cooling unit from the M310i/M210i

Hand holding a pen inserted into a rack-mounted server unit with a hexagonal mesh grille and USB port (no visible text or symbols)

Hand inserting a hexagonal heat sink into a server rack (no visible text or symbols)

1. Loosen the thumbscrew. A retainer keeps the thumbscrew in place.
2. Grasp the cover near the thumbscrews and lift it off. Remove the cover to access the battery. See Figures 16 and 17.

Figure 16. Loosen the thumbscrews and remove the cover (M610i)

Figure 17. Loosen the thumbscrews and remove the cover (M310i/m210l)

Exterior view of a silver power supply unit with green circuit board and exposed components (no text or symbols visible)

Loosen the thumbscrews

Close-up of a hand installing or adjusting an electronic device into a green circuit board (no visible text or symbols)

Lift the cover

1. Remove the two screws holding the battery assembly in place.
2. Detach the connector on the circuit board.

Do not detach any other connectors. See Figures 18 and 19.

Figure 18. Removing the battery assembly screws and detaching the connector (M610i)

Remove this screwDetach this connector

Figure 19. Removing the battery assembly screws and detaching the connector (M310i/M210i)

1. Lift the battery assembly out of the cooling unit.
2. Place a new battery assembly into the cooling unit.
3. Attach the connector on the circuit board.
4. Install the two screws holding the battery assembly in place to the cooling unit.
5. Place the top section of the cooling unit onto the bottom section and tighten the thumbscrews.
6. Carefully slide the cooling unit into the enclosure.
7. Gently press the handle in and upward until it locks. See Figure 20.

Figure 20. Locking the cooling unit handle (left: M610i, right: M310i/M210i

Hand inserting a hexagonal grid into a server rack (no visible text or symbols)

Hand inserting a hexagonal heat sink into a server rack (no visible text or labels)

This completes the battery replacement procedure.

Replacing a RAID Controller

The RAID Controller monitors and manages the logical drives. When this controller is replaced, all of your logical drive data and configurations remain intact because this logical drive information is stored on the disk drives.

Caution

The RAID Controller is NOT a hot-swappable device. 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 285.

Removing the old controller

To remove the RAID Controller:

1. Shutdown the VTrak. See "Shutting Down the Subsystem" on page 89 (WebPAM PROe) or page 194 (CLU).
2. Switch off the power.
3. Disconnect the iSCSI cables, management, serial, and power cables.
4. On the controller handle, press the release button and pull the handle downward. See Figures 21 and 22.
5. Pull the controller out of the VTrak enclosure.

Installing the new controller

To install the new controller:

1. Carefully slide the controller into the enclosure.
2. Gently press the handle in and upward until it locks. See Figure 21.
3. Connect the iSCSI cables, management, serial, and power cables.
4. Switch on the power.

The VTrak will restart. For more information about VTrak's start-up behavior, see "Connecting the Power" on page 21.

Figure 21. Removing and replacing the controller (M610i)

Hand inserting a drive into a server rack with visible fan and ventilation (no text or symbols)

Close-up of a server rack with a hand pointing to a front panel, showing ports and ventilation fans (no visible text or labels)

Figure 22. Removing and replacing the controller (M310i/M210i)

Close-up of a hand inserting a drive into a server rack with multiple fans (no visible text or labels)

Close-up of a server rack with multiple ports and ventilation grilles, hand pointing to one (no visible text or labels)

This completes the controller replacement procedure.

Chapter 7: Technology Background

This chapter covers the following topics:

• Introduction to RAID (below)
• Choosing a RAID Level (page 228)
• Choosing Stripe Size (page 231)
• Choosing Sector Size (page 231)
• Cache Policy (page 232)
  • Capacity Coercion (page 233)
• Initialization (page 234)
  • Hot Spare Drive(s) (page 234)
  • RAID Level Migration (page 235)
  • Media Patrol (page 238)
  • Predictive Data Migration (PDM) (page 238)
  • Transition (page 239)

- Partition and Format the Logical Drive (page 235)

Introduction to RAID

RAID (Redundant Array of Independent Disks) allows multiple hard 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. The RAID software and/or controller handle all of the individual drives on its own. The benefits of a RAID can include:

• Higher data transfer rates for increased server performance
• Increased overall storage capacity for a single drive designation (such as, C, D, E, etc.)
• Data redundancy/fault tolerance for ensuring continuous system operation in the event of a hard drive failure

Different types of disk arrays use different organizational models and have varying benefits. Also see “Choosing a RAID Level” on page 228. The following outline breaks down the properties for each type of RAID disk array:

RAID 0 – Stripe

When a disk array is striped, the read and write blocks of data are interleaved between the sectors of multiple drives. Performance is increased, since the workload is balanced between drives or “members” that form the disk array. Identical disk drives are recommended for performance as well as data storage efficiency. The disk array’s data capacity is equal to the number of disk drive members multiplied by the smallest drive's capacity.

Disk Drives
Figure 1. RAID 0 Striping interleaves data across multiple drives

For example, one 100GB and three 120GB drives will form a 400GB (4 x 100GB) disk array instead of 460 GB.

RAID 0 arrays require one or more physical drives.

Recommended applications: Image Editing, Pre-Press Applications, other applications requiring high bandwidth.

RAID 1 – Mirror

When a disk array is mirrored, identical data is written to a pair of 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 will be accessed first. With RAID 1, if one drive fails or has errors, the other mirrored drive continues to function. This is called Fault Tolerance. Moreover, if a spare drive is present, the spare drive will be used as the replacement drive and data will begin to be mirrored to it from the remaining good drive.

Disk Drives
Figure 2. RAID 1 Mirrors identical data to two drives

Due to the data redundancy of mirroring, the drive capacity of the disk array is only the size of the smallest drive. For example, two 100GB drives which have a combined capacity of 200GB instead would have 100GB of usable storage when set up in a mirrored disk array. Similar to RAID 0 striping, if drives of different capacities are used, there will also be unused capacity on the larger drive.

RAID 1 arrays use two physical drives. You can create multiple RAID 1 disk arrays on the same Promise product.

Recommended applications: Accounting, Payroll, Financial, other applications requiring very high availability.

RAID 1E – Enhanced Mirror

RAID 1E offers the security of mirrored data provided by RAID 1 plus the added capacity of more than two disk drives. It also offers overall increased read/write performance plus the flexibility of using an odd number of disk drives. With RAID 1E, each data stripe is mirrored onto two disk drives. If one drive fails or has errors, the other drives continue to function, providing fault tolerance.

Enhanced Data Mirrors

Disk Drives

The advantage of RAID 1E is the ability to use an odd number of disk drives, unlike RAID 1 and RAID 10. You can also create a RAID 1E Logical Drive with an even number of disk drives. However, if you have an even number of disks, you will obtain greater security with comparable performance using RAID 10.

RAID 1E arrays 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 will actually be a RAID 1.

Recommended applications: Imaging Applications, Database Servers, General Fileservers.

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

Distributed Parity

Figure 3. RAID 5 Stripes all drives with data and parity information

The capacity of a RAID 5 disk array is the smallest drive size multiplied by the number of drives less one. Hence, a RAID 5 disk array with (4) 100 GB hard drives will have a capacity of 300GB. A disk array with (8) 120GB hard drives and (1) 100GB hard drive will have a capacity of 800GB.

RAID 5 requires a minimum of three physical drives and a maximum of 16.

Recommended applications: File and Application Servers; WWW, E-mail, News servers, Intranet Servers

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 disk logical drive can continue to accept I/O requests when any two physical drives fail.

Double Distributed (Wide-space Q+Q) Parity

The total capacity of a RAID 6 disk logical drive is the smallest physical drive times the number of physical drives, minus two.

Hence, a RAID 6 disk logical drive with (6) 100 GB hard drives will have a capacity of 400 GB. A disk logical drive with (4) 100 GB hard drives will have a capacity of 200GB.

RAID 6 becomes more capacity efficient in terms of physical drives as the number of physical drives increases.

RAID 6 offers 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.

RAID 6 requires a minimum of four physical drives and a maximum of 16.

Recommended applications: Accounting, financial, and database servers; any application requiring very high availability.

RAID 10 - Mirror + Stripe

Mirroring/striping combines both of the previous RAID 1 and RAID 0 disk array types. RAID 10 is similar though not identical to RAID 0+1. RAID 10 can increase performance by reading and writing data in parallel while protecting data with duplication. At least four drives are needed for RAID 10 to be installed. With four disk drives, the drive pairs are striped together with one pair mirroring the first pair. The data capacity is similar to a RAID 1 disk array, with half of the total storage capacity used for redundancy. An added plus for using RAID 10 is that, in many situations, such a disk array offers double fault tolerance. Double fault tolerance may allow your logical drive to continue to operate depending on which two disk drives fail.

Figure 4. RAID 10 takes a data mirror on one drive pair and stripes it over two drive pairs

RAID 10 arrays require an even number of physical drives and a minimum of four.

For RAID 10 characteristics with an odd number of disk drives, use RAID 1E.

Recommended applications: Imaging Applications, Database Servers, General Fileservers.

RAID 50 – Striping of Distributed Parity

RAID 50 combines both RAID 5 and RAID 0 features. Data is striped across disks 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.

Distributed Parity

Figure 5. RAID 50 Striping of Distributed Parity disk arrays

RAID 50 also provides high reliability because data is still available even if multiple disk drives fail (one in each axle). The greater the number of axles, the greater the number of disk drives that can fail without the RAID 50 array going offline.

RAID 50 arrays consist of six or more physical drives.

Recommended applications: File and Application Servers, Transaction Processing, Office applications with many users accessing small files.

RAID 50 Axles

When you create a RAID 50, you must specify the number of axles. An axle refers to a single RAID 5 array that is striped with other RAID 5 arrays to make RAID 50. An axle can have from 3 to 16 physical drives, depending on the number of physical drives in the array.

The chart below shows RAID 50 arrays with 6 to 16 physical drives, the available number of axles, and the resulting distribution of physical drives on each axle.

RAID 50 Array
No. of Drives No. of Axles Drives per Axle
6	2	3
7	2	3
8	2	4
9	2	4
	3	3
10 2 5,5
	3	3
11 2 5,6
	3	3
12 2 6,6
	3	4
	4 3,3,3,3
13 2 6,7
	3	4
	4 3,3,3,4
14 2 7,7
	3	4
	4 3,3,4,4
15 2 7,8
	3	5
	4 3,4,4,4
	5 3,3,3,3,3
16 2 8,8
	3	5
	4 4,4,4,4
	5 3,3,3,3,4

,		3
,		4
,		4
,		5
,		3
,		3
,		4
,		4
,		4
,		4
,		5
,		5
,		5
,		5

Choosing a RAID Level

There are several issues to consider when choosing the RAID Level for your VTrak disk array. The following discussion summarizes some advantages, disadvantages, and applications for each choice.

RAID 0

Advantages Disadvantages
Implements a striped disk array, the data is broken down into blocks and each block is written to a separate disk driveI/O performance is greatly improved by spreading the I/O load across many channels and drivesNo parity calculation overhead is involved	Not a true RAID because it is not fault-tolerantThe failure of just one drive will result in all data in an disk array being lostShould not be used in mission critical environments

Recommended Applications for RAID 0

• I m a g e E d i t i n g
  • Pre-Press Applications
• Any application requiring high bandwidth

RAID

Advantages Disadvantages
Simplest RAID storage subsystem designCan increase read performance by processing data requests in parallel since the same data resides on two different drives	Very high disk overhead - uses only 50% of total capacity

Recommended Applications for RAID 1

• Accounting
• Pay roll
  • F i n a n c i a l
• Any application requiring very high availability

RAID 1E

Advantages Disadvantages
Implemented as a mirrored disk array whose segments are RAID 0 disk arraysHigh I/O rates are achieved thanks to multiple stripe segmentsCan use an odd number of disks	Very high disk overhead - uses only 50% of total capacity

Recommended Applications for RAID 1E

• Imaging applications
• Database servers
• General fileserver

RAID 5

Advantages Disadvantages
High Read data transaction rateMedium Write data transaction rateGood aggregate transfer rate	Disk failure has a medium impact on throughput

Recommended Applications for RAID 5

- File and Application servers

- Intranet servers

- WWW, E-mail, and News servers

- Most versatile RAID level

RAID 6

Advantages Disadvantages
High Read data transaction rateMedium Write data transaction rateGood aggregate transfer rateSafest RAID level	High disk overhead – equivalent of two drives used for paritySlightly lower performance than RAID 5

Recommended Applications for RAID 6

• Accounting and Financial
- Database servers
- Any application requiring very high availability

RAID 10

Advantages Disadvantages
Implemented as a mirrored disk array whose segments are RAID 0 disk arraysHigh I/O rates are achieved thanks to multiple stripe segments	Very high disk overhead - uses only 50% of total capacity

Recommended Applications for RAID 10

• Imaging applications
• Database servers
• General fileserver

RAID 50

Advantages Disadvantages
High Read data transaction rateMedium Write data transaction rateGood aggregate transfer rateHigh reliabilitySupports large volume sizes	Higher disk overhead than RAID 5

Recommended Applications for RAID 50

• File and Application servers
• Transaction processing
  • Office application with many users accessing small files

Choosing 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 disk array. In order to change the Stripe Size of an existing disk array, you must delete the disk array and create a new one. You can select Stripe Size directly when you use the Advanced function to create a disk array. If you use the Express function to create a disk array, WebPAM PRO selects the Stripe Size when you choose an Application Type.

The available Stripe Sizes are 64, 128, 256 KB, 512 KB, and 1 MB. 64 KB is the default. There are two issues to consider when selecting the Stripe Size.

First, 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.

Second, 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, Promise suggests you select 64 KB as your Stripe Size. Generally speaking, email, POS, and webservers prefer smaller stripe sizes. Video and database applications prefer larger stripe sizes.

Choosing Sector Size

A sector is the smallest addressable area on a physical disk drive. Sector Size refers to the size of sector measured by the number of bytes of data it can hold. The most common sector size is 512 bytes (512 B). A smaller sector size results in a more efficient use of a disk drive's capacity. 512 B is the default sector size for logical drives on VTrak.

Important

For iSCSI, always use a 512-byte sector size.

• Larger sector sizes are incompatible with the Microsoft iSCSI initiator.
• Linux systems with the 2.4 kernel do not support variable sector sizes.
• Linux systems with the 2.6 kernel support 64-bit LBA and do not need larger sector sizes.

Cache Policy

As it is used with VTrak, the term cache refers to any of several kinds of high-speed, 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, user-adjustable settings are provided. Cache settings are made in conjunction with logical drives:

- When you create a logical drive. See “Creating a Logical Drive” on page 111 (WebPAM PROe) or page 156 (CLU).

- On an existing logical drive. See “Making Logical Drive Settings” on page 120 (WebPAM PROe) or page 159 (CLU).

Read Cache Policy

- Read Cache – The read cache is enabled.

- Read Ahead – The read cache and the read-ahead feature are enabled. Read-ahead anticipates the next read and performs it before the request is made. Can increase read performance.

- No Cache – The read cache is disabled.

Write Cache Policy

- Write Back – Data is written first to the cache, then to the physical drive. Better performance. VTrak has a cache backup battery to protect data in the cache from a sudden power failure.

- Write Thru – Also “Write Through”. Data is written to the cache and the physical drive at the same time. Safer.

If Write Policy is set to Write Back, and 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.

If Write Policy is set to Write Back, and the Adaptive Writeback Cache feature is enabled, the Write Policy will remain at Write Back even when the battery is offline. Any data in the controller cache will be lost in the event of a power failure.

Adaptive Writeback Cache

On the VTrak subsystem, you can set the logical drive write cache policy to Write Through 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 physical 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 until service is restored.

Normally, if the cache backup battery is not present or the battery is being reconditioned, your logical drive write cache policy is automatically set to Write Through, so no data is stored in the controller cache. This action slightly reduces performance but avoids data loss in the event of a power failure. When a battery is installed or finishes reconditioning, the write cache policy is automatically reset to Write Back.

The Adaptive Writeback Cache option enables you to set your logical drive write cache policy to Write Back, even if no cache backup battery is present or the battery is being reconditioned. This action improves performance but also risks a loss of data in the event of a power failure.

To enable the Adaptive Writeback Cache option, click the Controller Settings tab. See “Making Controller Settings” on page 93 (WebPAM PROe) or page 138 (CLU).

Also see "Replacing a Cache Battery" on page 211.

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, physical drives of different sizes will work but the system must adjust 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 select the Method in the Controller Settings menu. See page 93 or page 138. 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 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 will not permit the use of a replacement physical drive that is slightly smaller than the remaining working drive(s).

Initialization

Initialization is 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 for all new logical drives. See “Initializing a Logical Drive” on page 121 (WebPAM PROe) or page 160 (CLU).

Caution

When you initialize a logical drive, all the data on the logical drive will be lost. Backup any important data before you initialize a logical drive.

Hot Spare Drive(s)

A hot spare is a disk drive that is connected to the disk array system but is not assigned as a member of the disk array. In the event of the failure of a drive within a functioning fault tolerant disk array, the hot spare is activated as a member of the disk array to replace a drive that has failed.

VTrak will replace a failing disk drive in a disk array with an unassigned drive, if one is available. The unassigned drive is not part of any disk array. Such a drive is called a hot spare drive. There are two types:

• Global – An unassigned disk drive available to any disk array on the VTrak.
• Dedicated – An unassigned disk drive that can only be used by a specified disk array.

The hot spare policy function lets you select whether a disk array will access any unassigned disk drive or a designated drive in the event of disk drive failure. See "Managing Spare Drives" on page 125 (WebPAM PROe) or page 176 (CLU) for information on how to make this setting.

The spare drive effectively takes the place of the failed drive and the RAID system immediately begins to rebuild data onto the drive. When the rebuild is complete, the disk array is returned to fault tolerant status.

VTrak includes a function that enables you to return a hot spare drive from a disk array back to spare status. When you create the hot spare drive, check the Revertible box to enable this feature. See “Transition” on page 239.

See also "Critical & Offline Disk Arrays" on page 269.

Partition and Format the Logical Drive

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.

RAID Level Migration

To migrate a disk array is to do one or both:

• Change its RAID level
• Increase the number of disk drives (sometimes called Expansion)

Migration takes place on an existing Functional disk array without disturbing the existing data. While the disk array is migrating, you can access the data as before. When migration is complete, your disk array will have a different RAID level and/or a larger capacity.

Different types of disk arrays use different organizational models and have varying benefits. The following outline breaks down the properties for each type of RAID supported by Promise products.

From To

Increase Redundancy

Capacity Performance Add Lose

RAID 50 RAID 10 •

RAID 5 •*

RAID 1E •

RAID 0 •

RAID 10 RAID 50 •

RAID 5 •

RAID 1E

RAID 0 •

•

From To		Increase Redundancy		Lose
		Capacity	Performance Add
RAID 5 RAID	D 50 •
	RAID 10 • •
	RAID 1E •
	RAID 0 • • •
RAID 1E RAID	D 50 •
	RAID 10 •
	RAID 5 •
	RAID 0 • •
RAID 1 RAID	D 50 • •
	RAID 10 •
	RAID 5 • •
	RAID 1E •
	RAID 0 • • •
RAID 0 RAID	D 50 • •
	RAID 10 • •
	RAID 5 •
	RAID 1E • •
	RAID 1 •
* Decreases the existing redundancy

Important

• The Target disk array may require more disk drives than the Source disk array
• If the Target disk array requires an EVEN number of disk drives but the Source disk array has an ODD number, ADD a disk drive as part of the migration process
• You cannot reduce the number of disk drives in your disk array, even if the Target disk array requires fewer disk drives than the Source disk array
• RAID 1 (mirroring) works with two drives only. Only a single-drive RAID 0 disk array or a single-drive JBOD 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
• You cannot migrate to or from RAID 6. You must create a new disk array and move your data to it

Ranges of Disk Array Expansion

The Windows 2000 and XP (32-bit) operating systems support a 10-byte LBA format. As a result, these OSes can only recognize 4 billion addresses. If you create a logical drive using the default 512 B sector size, the logical drive will be limited to 2 TB of data, even if there is more space available on your disk drives.

This limitation does not apply to Windows XP (64-bit), 2003 Server, Vista, and Linux OSes with the 2.6 kernel. Linux OSes with the 2.4 kernel do not support variable sector sizes, therefore you cannot apply the solution described here to those OSes.

For Windows 2000 and XP (32-bit) operating systems, you can direct WebPAM PROe to expand a logical drive beyond the maximum 2 TB expansion size. When the expansion is finished:

• WebPAM PROe will show the logical drive in the desired size.
• Your operating system might show the logical drive at 2 TB.
  • Additional capacity might appear as unpartitioned and unformatted.

At this point, you can format the unpartitioned/unformatted capacity as a second logical drive.

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. Media Patrol does not check unconfigured drives.

Media Patrol will also check spare drives, if those drives have Media Patrol enabled. Media Patrol for spare drives is enabled by default. You can disable it in VTrak's Command Line Interface (CLI).

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.

You can run Media Patrol from the subsystem. See “Running Media Patrol” on page 52 (WebPAM PROe) or page 136 (CLU).

You can also run Media Patrol on a disk array in WebPAM PROe. See page 115.

Predictive Data Migration (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 page 52 (WebPAM PROe) or page 155 (CLU).

After the data is copied from the suspect disk drive, the controller marks it with a Stale configuration and a PFA error.

You can clear the Stale configuration and PFA error and put the disk drive back into service. See “Clearing Stale and PFA Conditions” on page 102 (WebPAM PROe) or page 145 (CLU). In some cases, however, you might remove the disk drive for repair or replacement.

PDM Triggers

The following actions trigger PDM:

• A disk drive with unhealthy status (see below)
  • Media Patrol finds a disk critical error*
• 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 has a capacity of 512 reassigned blocks and 1024 error blocks.

When the table fills to a specified percentage of its capacity, PDM triggers a migration of data from the suspect drive (the disk drive with the bad sectors) to a spare disk drive.

During data migration, you will have access to the Logical Drive but it will 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 drive.

See “Making Background Activity Settings” on page 51 (WebPAM PROe) or page 172 (CLU).

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 non-revertible 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 page 126 (WebPAM PROe) or page 176 (CLU).
• 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 below.

Example

Following is an example to explain the Transition function.

graph TD
    A["Array Drives"] --> B["Spare"]
    B --> C["6"]
    style A fill:#f9f,stroke:#333
    style B fill:#ccf,stroke:#333
    style C fill:#cfc,stroke:#333

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.

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 drive. In this example, physical drive 3 failed and the array is rebuilt using physical drive 6, the revertible spare drive.

graph TD
    A["1"] --> B["2"]
    B --> C["3"]
    C --> D["4"]
    D --> E["5"]
    E --> F["6"]
    style A fill:#f9f,stroke:#333
    style F fill:#f9f,stroke:#333
    note right of A Array Drives
    note left of A
    note right of B
    note right of C
    note right of D
    note right of E
    note right of F

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.

Automatic Transition

At this juncture, you would replace the failed drive in slot 3 with a new one of the same or greater capacity.

graph TD
    A["Array Drives"] --> B["Spare"]
    B --> C["1"]
    C --> D["2"]
    D --> E["3"]
    E --> F["4"]
    F --> G["5"]
    G --> H["6"]

When the VTrak controller detects the new drive in slot 3, it will:

• Automatically transition the data on drive 6 to drive 3

- Return 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 page 116 (WebPAM PROe) or page 155 (CLU).

graph TD
    A["Array Drives"] --> B["Spare"]
    B --> C["6"]
    style A fill:#f9f,stroke:#333
    style B fill:#ccf,stroke:#333
    style C fill:#cfc,stroke:#333

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 will be unconfigured until you assign it to a disk array or as a spare.

Chapter 8: Troubleshooting

This chapter covers the following topics:

• VTrak is Beeping (page 244)
• LEDs Display Amber or Red (page 245)
• CLU Reports a Problem (page 250)
• WebPAM PROe Reports a Problem (page 252)
• LEDs Display Amber or Red (page 245)
• Event Notification Response (page 255)
• Critical & Offline Disk Arrays (page 269)
- Incomplete Array (page 272)
• Physical Drive Problems (page 273)
• Enclosure Problems (page 275)
- Connection Problems (page 278)
- Browser Does Not Connect to WebPAM PROe (page 280)
- Unsaved Data in the Controller Cache (page 281)

VTrak is Beeping

VTrak's alarm has five different patterns, as shown below.

Figure 1. Audible alarm sound patterns

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 for red or amber LEDs, as described above.
• If email notification is enabled, check for new messages.
• Check for yellow !s red Xs in Tree View (see page 252).
• Check the event log. See page 48 (WebPAM PROe) or page 174 (CLU).

When a continuous tone sounds, there are multiple alarm patterns sounding at the same time.

To make alarm settings or cancel an alarm, see page 99 (WebPAM PROe) or page 197 (CLU).

LEDs Display Amber or Red

Front Panel

When the power is switched on, the LEDs on the front of the VTrak will light up.

Figure 2. VTrak front panel LED display. The M610i is shown

When boot-up is finished and the VTrak is functioning normally:

• Controller Heartbeat LED blinks once every two seconds.
• Power, FRU, and Logical Drive LEDs display green continuously.
• The RAID Controller LED flashes green if there is activity on a iSCSI port.

See the table below.

LEDs	State
	Dark	Steady Green	Flashing Green	Amber Red
Power System Off Normal
FRU* System Off Normal				Fan, battery or PSU Problem	Fan, battery or PSU Failed
Logical Drive	System Off	Normal		Logical Drive Critical	Logical Drive Offline
Controller Activity	No Activity	Activity
Controller Heartbeat	System Off	Normal**
* Field Replacement Unit: includes fan, battery, and power supply unit (PSU). ** Blinks once every two seconds.

See page 199 for more information about field-replaceable components. See page 269 for a discussion of critical and offline logical drives.

Drive Status Indicators

There are two LEDs on each Drive Carrier. They report the presence of power and a disk drive, and the current condition of the drive.

The VTrak spins up the disk drives sequentially in order to equalize power draw during start-up. After a few moments the Power/Activity and Disk Status LEDs should display green.

Figure 3. VTrak drive carrier LEDs

LEDs	State
	Dark	Steady Green	Flashing Green	Amber Red
Power/Activity	No Drive	Drive Present	Activity
Status	No Power/No Drive	Drive OK		Drive Rebuilding	Drive Error

See “Critical & Offline Disk Arrays” on page 269 for a discussion of rebuilding and failed disk drives.

Back of Enclosure

When the FRU Status LED on VTrak's front panel shows Amber or Red, check the LEDs on the back of VTrak. These LEDs give the status of the field replaceable units.

Figure 1. VTrak M610i rear view

Figure 2. VTrak M310i and M210i rear view

Figure 4. Fan LED (left: M610i, right: M310i/M210i)

Under normal conditions, the power supply and fan LEDs should display green.

LEDs	State
	Dark Green Amber Red
Power supply N	Not detected OK	Fan failed Failed
Fan Not detected	OK Wrong speed	Failed

To check a component's installation, follow the same procedure as replacing the component, except that you reinstall the original component rather than a new one. 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 199 for instructions.

The Controller Location LEDs, on the back of the VTrak subsystem, will flash for one minute.

Figure 5. The VTrak controller LEDs

Under normal conditions, the Controller Status LED (marked with √icon) is green and the Dirty Cache LED (marked with △icon is dark. See the table below.

LEDs	State
	Dark Green Amber			Flashing Amber
Status	no power OK		Error
Dirty Cache OK			Unsaved data in cache	OK

If the Controller Status LED is amber, restart the VTrak. See “Restarting the Subsystem” on page 90 or page 196.

If the Controller Status LED continues to display amber after startup, contact Promise Technical Support. See “Contacting Technical Support” on page 285.

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. See “Browser Does Not Connect to WebPAM PROe” on page 280 for more information.

CLU Reports a Problem

The CLU reports information passively—you must determine which functions to check based on the sound of the VTrak's audible alarm (see page 244) and any amber or red LEDs (see page 245).

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:

• 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.

Press the up and down arrow keys to scroll through the log.

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. From the Main Menu, highlight Event Viewer and press Enter.

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 – (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.

• Press the up and down arrow keys to scroll through the log.

Checking a Reported Component

In this example, let us check disk array status.

1. Open the CLU.
2. Highlight Disk Array Management and press Enter.
3. 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 : 1	Physical Capacity : 189.06GB
OperationalStatus : Degraded	MaxContiguousCapacity : 11.18GB
FreeCapacity : 179.68 GB	ConfigurableCapacity : 179.68GB
SupportedRAIDLevels: 0 5 10 1E

Disk Array Alias : DA1

MediaPatrol : Enabled

PDM : Enabled

Transport

Rebuild

Predictive Data Migration

Transition

Dedicated Spare Drives in the Array

Physical Drives in the Array

Logical Drives in the Array

[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 “Critical & Offline Disk Arrays” on page 269.

WebPAM PROe Reports a Problem

WebPAM PROe aids in troubleshooting your logical drives and enclosure by continuous monitoring and reporting to the User in the following ways:

• Displays yellow !s red Xs in Tree View.

Figure 6. Yellow !s and red Xs in Tree View

• Sends email messages, per your configuration.
• Displays popup messages, per your configuration.

To set up email and popup message notification, see "Setting-up User Event Subscriptions" on page 58.

Figure 7. An example of a popup message

- Keeps a record in the Event Log.

Figure 8. The Event Log

E	Device	Event ID	Severity	Time V	Description
34	DA 0	Dx000F0001	Into	May 12, 2005 13:28:47	Rebuild is completed
33	LD 0	Dx00090006	Into	May 12, 2005 13:28:47	Rebuild marks the logical drive synchronized upon rebuild completion
32	LD 0	Dx00090002	Into	May 12, 2005 13:28:47	Logical drive has been placed online
31	DA 0	Dx000F0000	Into	May 12, 2005 13:28:03	Rebuild is started
30	PD 5	Dx000D00CB	Into	May 12, 2005 13:28:02	Physical Disk has been removed
29	LD 0	Dx00090004	Major	May 12, 2005 13:28:02	Logical drive has been set to critical
28	PD 5	Dx000D001A	Major	May 12, 2005 13:28:02	Physical Disk is marked as DEAD due to removal
27	Spare 0	Dx001D0001	Into	May 12, 2005 02:00:26	Spare check completed successfully on the given spare drive
26	Spare 1	Dx001D0001	Into	May 12, 2005 02:00:26	Spare check completed successfully on the given spare drive
25	Spare 0	Dx001D0000	Into	May 12, 2005 02:00:26	Spare check started on the given spare drive

• Keeps a record in the Event Log.
• Displays full information in Management View.

Figure 9. A failed disk drive shown in Management View

Also see these troubleshooting topics:

• "Event Notification Response" on page 255
• “Critical & Offline Disk Arrays” on page 269
• "Frequently Asked Questions" on page 283

Event Notification Response

When you select 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 “Setting-up User Event Subscriptions” on page 58.

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 255)
• Blowers (page 256)
• Cache (page 257)
• Controller (page 257)
• Disk Array (page 257)
• Drive Interface Controller (page 258)
• Enclosure (page 258)
  • Event Log (page 258)
• Host Interface Controller (page 258)
• iSCSI (page 259)
  • Logical Drive (page 259)
  • Media Patrol (page 260)
  • Online Capacity Expansion (page 261)
• PDM (page 261)

• Physical Disk (page 262)
• PSU (Power Supply Units) (page 263)
- PSU Fans (page 264)
• RAID Level Migration (page 264)
- Rebuild (page 265)
- Redundancy Check (page 265)
• Resource (page 266)
- Spare Check (page 266)
- Spare Drives (page 266)
- SMART (page 267)
- Stripe Level Migration (page 267)
• Synchronization (page 267)
- System (VTrak) (page 268)
• Transition (page 268)
• Watermark (page 268)

Reported Event Corrective Action
Battery
Battery temperature is above the threshold	The battery is too hot. Verify proper airflow around the through the VTrak. If airflow is OK, replace the battery. See page 211.
Battery temperature is normal	Normal.
Battery capacity is below the threshold	Battery is drained. Run battery reconditioning. See page 98.
Battery capacity is normal	Normal.
Battery is discharging Battery	is undergoing reconditioning.
Battery is charging Battery	is being recharged.
Battery reconditioning is complete	Battery reconditioning is finished.
Battery is malfunctioning Run battery reconditioning. See page 98. If this message reappears, replace the battery.
Battery reconditioned successfully	Battery reconditioning is finished.
Battery reconditioning has failed	Replace the battery. See page 211.
Battery is reaching end of life	Replace the battery. See page 211.
Battery is removed The battery was disconnected or removed. Reinstall the battery. See page 211.
Battery charging failed Replace the battery. See page 211.
Battery reconditioning started	Battery reconditioning has begun.
Battery recondition terminated	The battery was disconnected or removed during reconditioning. Reinstall the battery. See page 211.
Blowers
Blowers have started Normal.
Blowers have stopped Verify that the cooling unit is properly installed. If the blower still does not turn, replace the blowers. See page 205.
Blower speed is increased	Check the VTrak for overheating. See page 275.
Blower speed is decreased	Temporary overheat condition was corrected.
Blowers are NOT functioning	Replace the blowers. See page 205.
Blowers have been inserted	Normal.
Blowers have been removed	Reinstall the cooling unit(s). If the blowers does not turn, replace the blowers. See page 205.
Blowers are functioning normally	Normal.
Blowers are NOT installed	Reinstall the cooling unit(s). If the blowers does not turn, replace the blowers. See page 205.
Blower status is unknown	Check for airflow out of the cooling unit. If there is none, check for proper installation.
Cache
BBU flushing has started VTrak's cache is being flushed.
BBU flushing has ended VTrak's cache has been flushed.
BBU flushing has failed VTrak's cache could not be flushed. Check your cache flush interval setting. See page 93.
Controller
The controller parameter(s) changed by user	The user successfully change controller settings. See page 93.
The controller has new crash information	Check the event logs. See page 48.
Controller temperature is above the threshold/warning threshold	The VTrak controller is overheating. Check for airflow around and through the controller, and verify that all fans are working. Replace fans as needed.
Controller temperature is above the critical threshold	The VTrak controller is seriously overheating. Check for airflow around and through the controller, and verify that all fans are working. Replace fans as needed.
Disk Array
New disk array has been created	Result of settings or user action. Normal.
Disk array has been deleted	Result of settings or user action. Normal.
Disk array has been added	Result of settings or user action. Normal.
Disk array has been removed	The physical drives of the disk array were removed from the enclosure.
Disk array settings have been changed	The user successfully disk array settings. See page 111.
Drive Interface Controller
Drive-interface controller found	Normal.
Drive-interface controller is NOT found	Restart the VTrak. See page 90. If this message appears repeatedly, contact Technical Support. See page 285.
Drive-interface diagnostics has passed	Normal.
Drive-interface diagnostics has failed	Restart the VTrak. See page 90. If this message appears repeatedly, contact Technical Support. See page 285.
Drive-interface controller has generated a general/data parity error.	Drive-to-controller parity error. If this message appears repeatedly, contact Technical Support. See page 285.
Enclosure
Enclosure temperature is above the threshold/warning threshold	The VTrak is overheating. Check for airflow around and through the VTrak, and verify that all fans are working. Replace fans as needed. See page 205.
Enclosure temperature is above the critical threshold	The VTrak is seriously overheating. Check for airflow around and through the VTrak, and verify that all fans are working. Replace fans as needed. See page 205.
Enclosure temperature is within the normal range	Normal.
Event Log
Event logging is enabled	Event logging has been successfully enabled.
Event logging is disabled	Event logging has been disabled.
Event log buffer is cleared in RAM	The event log was cleared.
Event log buffer is cleared in NVRAM	The non-volatile RAM event log was cleared.
Event log buffer is cleared in MDD	The MDD (disk drive) event log was cleared.
Host Interface Controller
Host-interface controller has detected bus reset	The initiator sent a reset command. If this message appears repeatedly, contact Technical Support. See page 285.
Host-interface controller has encountered an unrecoverable error	Restart the VTrak. See page 90.
Host-interface controller has received an abort-task/ abort task set/clear task set command.	Result of user action. Normal.
Host-interface controller has received an clear ACA command.	Result of clearing an auto contingent alliance condition. If this message appears repeatedly, contact Technical Support. See page 285.
Host-interface controller has received a LUN reset command.	Result of user action. Normal.
Host-interface controller has received a bus reboot	The VTrak rebooted itself. If this message appears repeatedly, contact Technical Support. See page 285.
Host-interface controller has encountered an unknown error	An unidentified error occurred. If this message appears repeatedly, contact Technical Support. See page 285.
Host-interface controller has encountered a system error	A VTrak system error occurred. If this message appears repeatedly, contact Technical Support. See page 285.
Host-interface controller has encountered a fatal error	Restart the VTrak. See page 90. If this message appears repeatedly, contact Technical Support. See page 285.
Host-interface controller settings have changed	Result of user action. Normal.
iSCSI
iSCSI link is up iSCSI link	connected and ready. Normal.
iSCSI link is down iSCSI link	linked and ready. Normal.
Logical Drive
Logical drive initialization has started	Result of user action. Normal.
Logical drive initialization has completed	Logical drive is ready to use. Normal.
Logical drive initialization has paused	Initialization paused because of user intervention, schedule or a higher priority background activity.
Logical drive initialization has resumed	Initialization has resumed again after a pause.
Logical drive initialization has stopped	Initialization stopped because of user intervention, schedule or the logical drive was deleted or went critical or offline.
Logical drive initialization marks the logical drive offline	Initialization failure due to a failed disk drive. Replace the disk drive, delete and recreate the logical drive. See page 15, then page 105.
Logical drive initialization is aborted due to an internal error.	System resources are low. Reduce system load or restart the VTrak. See page 90.
Logical drive initialization is queued	Initialization has been set manually or by schedule.
A new logical drive has been created	Result of user action. Normal.
Logical drive has been deleted	Result of user action. Normal.
Logical drive has been placed online	The physical drives of the array are restored to online status.
Logical drive has been placed online. Possible data loss	One or more physical drives in the array went offline. See page 269.
Logical drive has been set to critical.	One or more physical drives in the array went offline. See page 269.
Logical drive axle has been placed online	RAID 50. One of the axles (RAID 5 arrays) returned on online status.
Media Patrol
Media patrol is started Result of settings or user action. Normal.
Media patrol is completed Normal.
Media patrol is paused Media patrol paused because of user intervention, schedule or a higher priority background activity.
Media patrol is resumed Media patrol has resumed again after a pause.
Media patrol is stopped Media patrol stopped because of user intervention, schedule or the logical drive was deleted or went critical or offline.
Media patrol is aborted due to an internal error.	System resources are low. Reduce system load or restart the VTrak. See page 90.
Media patrol is queued Media patrol has been set manually or by schedule.
Media patrol is stopped internally	Media patrol stopped because the disk array was deleted or removed.
Online Capacity Expansion
Online capacity expansion has started	Result of settings or user action. Normal.
Online capacity expansion has completed	Normal.
Online capacity expansion has paused	Expansion paused because of user intervention, schedule or higher priority background activity.
Online capacity expansion has resumed	Expansion has resumed again after a pause or a reboot.
Online capacity expansion has stopped	Expansion stopped because of user intervention, schedule or the logical drive was deleted or went critical or offline.
Online capacity expansion has encountered a physical disk error	Bad block found on a disk drive. Migration will finish. Check the disk drive check table after migration and replace disk drive as needed. See page 123.
Online capacity expansion is aborted due to an internal error.	System resources are low. Reduce system load or restart the VTrak. See page 90.
Online capacity expansion is queued	Synchronization has been set manually or by schedule.
PDM
PDM is started Result of settings or user action. Normal.
PDM is completed Normal.
PDM is paused PDM paused because of user intervention, schedule or a higher priority background activity.
PDM is resumed PDM has resumed again after a pause.
PDM is stopped PDM stopped because of user intervention, schedule or the logical drive was deleted or went critical or offline.
PDM is switched to rebuild.	PDM changed to rebuild because the logical drive went critical
PDM is stopped internally	The destination drive was removed or used for a rebuild.
Physical Disk
Physical disk is marked online	Disk drive restored to normal operation.
Physical disk is marked online	Disk drive removed from service due to errors. If necessary, try to force the disk online. See page 103.
Physical disk is marked as dead.	Disk drive failure. Replace the disk drive. See page 16.
Physical disk has been reset	Disk drive reset after error and should function normally.
Physical disk assigned as global spare	Result of settings or user action. Normal.
Physical disk is no longer assigned as global spare	Result of settings or user action. Normal.
Physical disk assigned as dedicated spare	Result of settings or user action. Normal.
Physical disk is no longer assigned as dedicated spare	Result of settings or user action. Normal.
Physical disk has been inserted	A disk drive has been inserted into the VTrak subsystem.
Physical disk has been removed	A disk drive has been removed from the VTrak subsystem.
Bad sector is found on physical disk	Disk drive has a bad sector. The drive should remap around the bad sector. If this message appears repeatedly, replace the disk drive.
Error is detected in remap sectors	Disk drive has a bad remap sectors. If this message appears repeatedly, replace the disk drive.
Command times out on physical drive	Disk drive not responding to commands. If this message appears repeatedly, replace the disk drive.
Physical disk negotiation speed is decreased.	Disk drive had to reduce its data rate. If this message appears repeatedly, replace the disk drive.
Previously configured disk is no longer found	Disk drive may have failed or was removed from the enclosure. Replace or reinstall the disk drive as needed.
A physical disk has encountered an unknown (non-ECC) media error.	Disk drive experienced an unknown error. If this message appears repeatedly, replace the disk drive.
A physical disk has encountered PFA condition	A potentially faulty address or bad sector was found.
A configured dead physical drive has been inserted	The disk drive inserted into the VTrak was marked as dead and will not work on the VTrak. Replace the disk drive.
A physical drive page 0/1 settings have been changed	Result of settings or user action. Normal.
Physical disk is marked as dead due to removal/failure of reassign sectors/PFA condition/forced offline state	Replace the disk drive.
PSU (Power Supply Units)
PSU is not inserted/has been removed	A power supply unit is missing from the VTrak. Reinstall the power supply unit.
PSU is off A power supply	unit is present but turned off. Turn on he power supply.
PSU is on Normal.
PSU is installed/ operational and turned on	Normal.
PSU is installed/ operational and turned off	A power supply unit is present but turned off. Turn on he power supply.
PSU is malfunctioning and turned on/off	Replace the power supply unit.
PSU 12V/5V/3.3V power is out of the threshold range	Replace the power supply unit.
PSU 12V/5V/3.3V power is within the range	Normal.
PSU Fans
PSU fan has turned on. Normal.
PSU fan has turned off. Verify that the power supply is turned on. If the fan still does not turn, replace the power supply. See page 204.
PSU fan speed increased.	Check the VTrak for overheating. See page 275.
PSU fan speed decreased.	Temporary overheat condition was corrected.
PSU fan is malfunctioning Replace the power supply. See page 204.
PSU fan is functioning normally	Normal.
PSU fan status is unknown.	Check for airflow out of the power supply. If there is none, check for proper installation and turn the power supply on.
RAID Level Migration
RAID Level migration is started	Result of settings or user action. Normal.
RAID Level migration is completed	Normal.
RAID Level migration is paused	Migration paused because of user intervention, schedule or a higher priority background activity.
RAID Level migration is resumed	Migration has resumed again after a pause.
RAID Level migration is stopped	Migration stopped because of user intervention, schedule or the logical drive was deleted or went critical or offline.
RAID Level migration has encountered a physical disk error	Bad block found on a disk drive. Migration will finish. Check the disk drive check table after migration and replace disk drive as needed. See page 123.
RAID Level migration is aborted due to an internal error.	System resources are low. Reduce system load or restart the VTrak. See page 90.
RAID Level migration is queued	Migration has been set manually or by schedule.
Migration has detected/cleared stale NV Watermark	Watermarks are progress markers left as the result of interrupted RAID migrations. If the watermark was cleared, migration should finish.
Array was incomplete due to missing NV Watermark	RAID migration was interrupted by a shutdown.If array is online, try migration again. See page 113.If array is offline, delete and recreate array. See page 109 and page 105.
Rebuild
Rebuild is started Result of settings or user action. Normal.
Rebuild is completed Normal.
Rebuild is paused Rebuild	paused because of user intervention,schedule or a higher priority background activity.
Rebuild is resumed Rebuild	has resumed again after a pause.
Rebuild is stopped Rebuild	stopped because of user intervention,schedule or the logical drive was deleted or the target disk drive encountered an error. If rebuild stopped by user intervention, restart the rebuild. See page 114.
Rebuild stopped internally	The logical drive is offline. See page 269.
Rebuild is aborted due to an internal error.	System resources are low. Reduce system load or restart the VTrak. See page 90.
Rebuild is queued Rebuild	has been set manually or by schedule.
Rebuild marks logical drive synchronized upon rebuild completion	Result of successful rebuild. Normal.
Redundancy Check
Redundancy Check is started	Redundancy Check has started manually or by schedule.
Redundancy Check is completed	Redundancy Check has finished.
Redundancy Check is paused	Redundancy Check paused because of user intervention, schedule or a higher priority background activity.
Redundancy Check is resumed	Redundancy Check has resumed again after a pause.
Redundancy Check is stopped	Redundancy Check stopped because of user intervention, schedule or the logical drive was deleted or went critical or offline.
Redundancy Check is aborted due to internal error	System resources are low. Reduce system load or restart the VTrak. See page 90.
Redundancy Check encountered inconsistent block(s)	Check the logical drive's inconsistent block table. See page 123. Rebuild the disk array if necessary. See page 114.
Redundancy Check task is queued	Redundancy Check has been set manually or by schedule.
Redundancy Check task is stopped internally	The logical drive is offline. See page 269.
Resource
Resource is NOT available	System resources are low. Reduce system load or restart the VTrak. See page 90.
Spare Check
Spare check started on the given spare drive	Result of settings or user action. Normal.
Spare check completed successfully on the given spare drive	Normal.
Spare Drives
Physical disk assigned as global spare	Result of settings or user action. Normal.
Physical disk is no longer assigned as global spare	Result of settings or user action. Normal.
Global Spare has been deleted	Result of settings or user action. Normal.
Physical disk assigned as dedicated spare	Result of settings or user action. Normal.
Physical disk is no longer assigned as dedicated spare	Result of settings or user action. Normal.
Dedicated Spare has been deleted	Result of settings or user action. Normal.
SMART
SMART error is received A	disk drive reported a SMART error. If this message appears repeatedly, replace the disk drive.
Stripe Level Migration
Stripe Level migration is started	Result of settings or user action. Normal.
Stripe Level migration is completed	Normal.
Stripe Level migration is paused	Migration paused because of user intervention, schedule or a higher priority background activity.
Stripe Level migration is resumed	Migration has resumed again after a pause.
Stripe Level migration is stopped	Migration stopped because of user intervention, schedule or the logical drive was deleted or went critical or offline.
Stripe Level migration has encountered a physical disk error	Bad block found on a disk drive. Migration will finish. Check the disk drive check table after migration and replace disk drive as needed. See page 123.
Stripe Level migration is aborted due to an internal error.	System resources are low. Reduce system load or restart the VTrak. See page 90 or page 196.
Stripe Level migration is queued	Migration has been set manually or by schedule.
Synchronization
Synchronization is started	Result of settings or user action. Normal.
Synchronization is completed	Normal.
Synchronization is paused	Synchronization paused because of user intervention, schedule or higher priority background activity.
Synchronization is resumed	Synchronization has resumed again after a pause or a reboot.
Synchronization is stopped	Synchronization stopped because of user intervention, schedule or the logical drive was deleted or went critical or offline.
Synchronization is aborted due to an internal error.	System resources are low. Reduce system load or restart the VTrak. See page 90.
Synchronization is queued	Synchronization is already running on another logical drive in the same array.
Synchronization is stopped internally	Synchronization stopped because the disk array was deleted or removed.
System (VTrak)
The system is started The	VTrak has been started.
The system is stopped The	VTrak was shut down.
Transition
Transition is started Result of settings or user action. Normal.
Transition is completed Normal.
Transition is paused Transition paused because of user intervention, schedule or a higher priority background activity.
Transition is resumed Transition has resumed again after a pause.
Transition is stopped Transition stopped because of user intervention or the logical drive was deleted.
Transition was switched to rebuild	Transition changed to rebuild because the logical drive went critical.

Critical & Offline Disk Arrays

A fault-tolerant disk array—RAID 1, 1E, 5, 10, and 50—goes critical when a disk drive is removed or fails. A RAID 6 disk array—goes degraded when a disk drive is removed or fails and critical when two disk drives are removed of fail.

Due to the fault tolerance of the disk array, the data is still available and online. However, once the disk array goes critical, the disk array has lost its fault tolerance, and performance may be adversely affected.

If the fault was caused by a failed drive that was removed, the drive must be replaced by another drive, either identical or larger, in order for the RAID system to rebuild and restore optimal configuration.

If your fault-tolerant disk array—RAID 1, 1E, 5, 6, 10, and 50—goes offline, contact Promise Technical Support. See “Contacting Technical Support” on page 285.

Warning

Take no further corrective action until you have consulted with Promise Technical Support.

A non-fault tolerant disk array—RAID 0—goes offline when a disk drive is removed or fails. Since the disk array is not fault tolerant, the data stored in the disk array is no longer accessible.

If one disk drive fails, all of the data on the disk array is lost. You must replace the failed drive. Then, if the disk array had more than one disk drive, delete the disk array and re-create it. Restore the data from a backup source.

When a Physical Drive Fails

VTrak provides both audible and visual indicators to alert you of a disk drive failure. The following will occur when a disk drive fails or goes offline:

• The Logical Drive LED changes from green to amber. See page 245.
• The Disk Carrier Status LED changes from green to red. See page 246.
• The audible alarm repeatedly sounds two short beeps. See page 244.
• WebPAM PROe reports the condition. See page 252.

Also see "Physical Drive Problems" on page 273.

With a Hot Spare Drive

When a physical drive in a disk array fails and a spare drive of adequate capacity is available, the disk array will begin to rebuild automatically using the spare drive.

After the disk array rebuilds itself using the spare drive, you must replace the failed drive.

To set up a spare drive, see “Creating a Spare Drive” on page 126 (WebPAM PROe) or page 176 (CLU).

Without a Hot Spare Drive

If there is no hot spare drive of adequate capacity, you must remove the failed drive and install an unconfigured replacement drive of the same or greater capacity in the same slot as the failed drive. Until you install the replacement drive, the logical drive will remain Degraded.

• If the Auto Rebuild function is ENABLED, the disk array will begin to rebuild automatically as soon as you replace the failed drive.
• If the Auto Rebuild function is DISABLED, you must manually rebuild the disk array after you replace the failed drive.

To enable Automatic Rebuild, see “Making Background Activity Settings” on page 51 (WebPAM PROe) or page 172 (CLU).

To set Hot Spare Policy, see “Making Spare Drive Settings” on page 127 (WebPAM PROe) or page 177 (CLU).

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 Stale and PFA Conditions” on page 102 (WebPAM PROe) or page 145 (CLU).

Rebuild Operation

During rebuild:

• The alarm sounds a single short beep, repeated
• No warning icon displays over the Disk Array or Logical Drive in the Tree.
  Management View reports the Disk Array's Operational Status as OK, Rebuilding.
• The drive carrier holding the rebuilding physical drive displays a green Activity (lower) LED while the Status (upper) LED flashes green once per second.

Figure 10. Drive carrier LEDs

During rebuilding, you can still read and write data to the logical drive. However, fault tolerance is lost until the Disk Array returns to OK (not-rebuilding) status.

After a successful rebuild:

• The alarm is silent
- The Disk Array's Operational Status as OK
• The rebuilt disk drive Status LED displays steady green

Incomplete Array

An incomplete array results from a physical drive that fails or becomes missing during:

• RAID level migration under NVRAM
• Physical drive transport

See "Physical Drive Failed" on page 273 for more information.

When VTrak discovers an incomplete array, WebPAM PROe 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 Disk Drives" on page 16.

If you choose to accept the incomplete array:

1. Click OK in the incomplete array dialog box.

2. Check the operational status of the logical drives in the array.

3. If the logical drives are critical or degraded, proceed with a rebuild. See “Rebuilding a Disk Array” on page 114 or page 154.

4. If the logical drives are offline, contact Technical Support. See “Contacting Technical Support” on page 285

5. Restore your data from a backup source, if required.

The CLU displays the option Accept Incomplete Array on the Disk Array Info and Settings screen. Highlight the option and press Enter to accept the incomplete array.

If you choose NOT to accept the incomplete array:

1. Click Cancel in the incomplete array dialog box.

2. Do one of the following:

3. Delete the array. See "Deleting a Disk Array" on page 109 or page 151.

4. Replace the missing physical drive.

Physical Drive Problems

Physical Drive Offline

Check the drive for:

• PFA Condition – Caused by a bad block or sector. See “Clearing Stale and PFA Conditions” on page 102.
• Stale Configuration – Caused by obsolete array information on the physical drive. Identify the disk array to which the physical drive belongs. Then delete the disk array. See “Deleting a Disk Array” on page 109 or page 151.

If the error condition remains on the physical drive, clear the error condition.

See “Clearing Stale and PFA Conditions” on page 102 or page 145.

Physical Drive Failed

When physical drive status shows failed, the physical drive cannot be repaired. You must replace the failed drive.

Physical Drive Fails during Migration

VTrak has two methods for migrating a disk array:

• DDF – The default setting. Slower but reliable
• NVRAM – An optional setting that requires special access. Faster but risks data loss

Normally, RAID level migration is done under the default Disk Data Format (DDF) setting. If a physical drive or the controller fails during migration, the disk array goes critical, and you can rebuild it. Migration under DDF can take up to several hours depending on the number and size of the physical drives and data input/output activity.

You can set the VTrak to migrate disk arrays under Non-Volatile Random Access Memory (NVRAM), a much faster process because it writes data to the memory in the controller. However, if a physical drive or the controller fails during migration, the logical drives will go offline and you will lose data. See “Incomplete Array” on page 272.

Because the setting for migration under NVRAM requires special access, most users will not encounter this condition.

Physical Drive Fails during Transport

Transport is the action of moving the physical drives of a disk array:

• To different slots in the same VTrak enclosure
• From one VTrak 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 will display an incomplete array. See “Incomplete Array” on page 272.

Enclosure Problems

WebPAM PROe displays yellow !s! red Xs ✗in Tree View to identify components that need attention.

When a yellow ! appears over a Subsystem in Tree View, click the Enclosure icon. The Enclosure screen will display (below).

Figure 11. Enclosure information in Management View

In this example, a power supply has failed. The Enclosure Diagram displays color and motion changes to identify the failed power supply. In this case, you must replace the power supply.

Note that the image above was shortened to fit on the page.

Overheating

Temperature Sensors

Overheating

Too Warm

Normal

Overheating is a potentially serious condition because the excessively high temperatures can lead to disk drive failure and controller malfunction.

Overheating usually results from:

• Fan failure
• Poor air circulation around the enclosure

WebPAM PROe reports failed fans along with elevated temperature. On VTrak, there are two kinds of fans:

• Power supply, 2 fans each
• Cooling units, 1 fan each

If a power supply fan fails, you must replace the power supply. If a cooling unit fan fails, you can remove the cooling unit and replace only the fan itself.

Cooling Unit and Power Supply Fan Condition

No tools are required for either procedure. See page 205 for instructions on replacing the fans.

OK

Air circulation around the VTrak enclosure may 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 5 inches (13 cm) space between the back of the VTrak and the wall or other object
- Ambient temperature above 95^ircF (35°C) where the VTrak is operating

Replace Now

To cool down a VTrak:

• Correct any problems identified above
  • Power it down and let it sit for an hour or longer

Power Supplies

VTraks are equipped with redundant power supplies. The advantage of dual power supplies is that, should one fail, the other will continue powering the subsystem until the faulty one can be replaced. VTrak is capable of operating on a single power supply. As a result, if one power supply fails you must watch the front panel LEDs or WebPAM PROe in order to become aware of the condition.

The power supplies are hot-swappable, meaning you can leave the VTrak running when you replace the bad one. Be careful, however, to remove the faulty power supply and not the good one, or VTrak will come to an immediate stop and your data will be unavailable until the system is powered and booted again.

As noted above, if a power supply fan fails, you must replace the power supply. Without the fan to cool it, the power supply will overheat and eventually fail anyway.

No tools are required for the procedure. See your page 204 for instructions on replacing a power supply.

Battery

VTrak uses a battery as backup power for the cache. Should a power failure occur, the battery enables the cache to hold data up to 72 hours. The battery recharges during normal VTrak operation.

In most cases, installing a replacement battery will correct a marginal or failed condition. The battery is located in the cooling unit above the controller. Remove the cooling unit for access. The battery is hot-swappable.

No tools are required for the procedure. See page 211 for instructions on replacing the battery.

Also see "Reconditioning a Battery" on page 98 or page 142.

Connection Problems

When you install your Promise product following the instructions in the Quick Start Guide and this Product Manual, you should have little trouble getting your equipment to work the first time. But connection problems can arise that are not the User's or Installer's fault. Every conceivable problem cannot be covered in the documentation but some guidelines could be helpful.

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 VTrak.

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 will 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 23. This issue is discussed further under Network Connections (below). See the “Making Serial Cable Connections” on page 20 for more information on making the connection.

The CLI and CLU control and manage but they do not move data. They communicate through a null-modem cable, supplied with the VTrak. A straight-through serial cable will 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, to be sure it will be there when you need it.

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 an IP address of 10.0.0.1. You must change this address to one that will work with your network. You make the initial IP address setting using the CLI or CLU. See “Setting up the Serial Connection” on page 23.

Figure 12. Management port connection on the RAID controller

LEDs	State
	Dark Green	Flashing	Green
Connectivity 10	BaseT 100BaseT
Activity No a	activity Activity

Note that VTrak Management Port can accept IP address assignments from a DHCP server. Use VTrak's Command Line Utility (CLU) to enable this feature. If you have not activated DHCP support but there is a DHCP server on your network, there is a chance that it will inadvertently assign the VTrak's Management Port IP address to another node. You might see a warning to this effect on your PC's monitor. If this happens, WebPAM PROe may not be able to connect. See your network administrator to work out a suitable arrangement.

iSCSI Connections

A recent variation of the SCSI interface is Internet or IP SCSI (iSCSI), which converts SCSI commands to TCP/IP commands for communication over a network. VTrak uses two Gigabit Ethernet network connections to move data under the iSCSI protocol. The iSCSI ports will accept IP address assignments from a DHCP server. Also, you can use WebPAM PROe for the initial setup.

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 VTrak's 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 management port in order to direct your browser to the VTrak and start WebPAM PROe.

To access the new IP address:

1. Start your PC's terminal VT100 or ANSI emulation program.
2. Press Enter once to launch the CLI.
3. At the Login prompt, type administrator and press Enter.
4. At the Password prompt, type password and press Enter.
5. Type net and press Enter.

administrator@cli> net

CId Port Type IP Mask Gateway Link

1 1 Mgmt 192.168.10.44 255.255.255.0 192.168.10.3 Up
1 1 iSCSI 192.168.10.90 255.255.255.0 192.168.10.3 Up
1 2 iSCSI 192.168.10.79 255.255.255.0 192.168.10.3 Up

The new management port IP address and other network settings display.

1. Enter the new IP address into your browser to log into WebPAM PROe.

For more information, see “Setting up the Serial Connection” on page 23 and “Logging out of WebPAM PROe” on page 35.

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.

Figure 13. The VTrak dirty cache LED

If there is unsaved data in the controller's cache, the Dirty Cache LED shines amber. During this time, do NOT power down the VTrak. Wait until the LED will goes dark.

Chapter 9: Support

This chapter covers the following topics:

• Frequently Asked Questions (below)
- Contacting Technical Support (page 285)
- Limited Warranty (page 288)
- Returning product for repair (page 289)

Frequently Asked Questions

What kind of disk drives can I use with VTrak?

VTrak supports 1.5 and 3.0 Gb/s Serial ATA disk drives.

Can I take the disk drives from my UltraTrak, put them into the VTrak and keep my disk array or logical drive intact?

Yes. UltraTrak and early VTrak subsystems used a proprietary method of disk metadata, stored in the reserve sector of each physical drive. VTrak M610i, M310i, and M210i use the industry-standard DDF and has a metadata-to-DDF conversion feature. To use the conversion feature, you must restart the VTrak after installing disk drives from an older system.

VTrak M610i, M310i, and M210i do not support Parallel ATA (PATA) disk drives.

Note that if you move the disk drives from the VTrak M610i, M310i, or M210i to the older subsystems, they will not recognize your disk array or logical drive.

How can I tell when the VTrak has fully booted?

When the VTrak is fully booted up, the Power and FRU LEDs will light up green. If a disk array is present, the Logical Drive LED will light up green also. The Controller heartbeat LED blinks once every two seconds.

Why does VTrak come with a Command Line Utility?

First, to assign your VTrak an IP address in order for the WebPAM management software to connect to it. Second, in the event of a network failure, you can still access the VTrak. Third, some users prefer the Command Line Utility.

WebPAM connection was working OK. But later on, it timed out. What do I do now?

The network condition can time-out for several reasons. When an open connection has no action for a specific amount of time (the Administrator can change it), the connection times-out automatically for security reasons.

When you attempt to use WebPAM, it returns to the login screen. Enter your user name and password and click Login, and WebPAM will establish a new connection. See “Making Web Server Settings” on page 77.

I can access the VTrak over my company's intranet. But I can't 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.

With other Promise VTraks, I used the Server's IP address in WebPAM to connect with the RAID subsystem. Why are VTrak M610i, M310i, and M210i different?

VTrak M610i, M310i, and M210i have the server software embedded. With the earlier models, you point your browser directly to the VTrak rather than a server. Also, with M610i, M310i, and M210i, you do not have to create a subsystem because the subsystem already exists.

Why can a RAID 1 logical drive on VTrak consist of only two disk drives?

On VTrak, RAID 1 logical drives work in mirrored physical drive pairs. You could create up to eight RAID 1 logical drives, depending on which subsystem model you have. Or you can create a single RAID 10 logical drive with data mirroring and up to 16 physical drives. If you have an odd number of drives but still want data mirroring, use RAID 1E.

See “Installing Disk Drives” on page 16 and “Introduction to RAID” on page 219 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.

I have two UltraTraks and use WebPAM to monitor them. Can I use my existing WebPAM setup to monitor the VTraks also?

No. Use the WebPAM embedded with the VTrak M610i, M310i, or M210i.

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.

Remotely: Check the Tree Icons in WebPAM. If there are no yellow or red warning icons displayed, VTrak is functioning normally.

What happens if a logical drive goes critical?

On the front of VTrak, the logical drive LED turns amber and an audible alarm sounds. See “Critical & Offline Disk Arrays” on page 269.

Can VTrak run using just one power supply?

Yes, it is possible to run VTrak on a single power supply. There are two power supplies so that VTrak will continue running if one of the power supply 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.

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 model(s), SATA/ATA/ATAPI drives & devices, and other controllers.

Technical Support Services

Promise Online™ Web Site http://www.promise.com/support

(technical documents, drivers, utilities, etc.)

United States

E-mail Support e-Support On-Line
Fax Support [phone] Attn: Technical Support
Phone Support [phone] option 4
If you wish to write us for support:	Promise Technology, Inc.580 Cottonwood DriveMilpitas, CA 95035, USA

The Netherlands

E-mail Support e-Support On-Line
Fax Support [phone] Attn: Technical Support
Phone Support [phone]
If you wish to write us for support:	Promise Technology Europe B.V. Science Park Eindhoven 5542 5692 EL Son, The Netherlands

Germany

E-mail Support e-Support On-Line
Fax Technical Support +49 (0)	2 31 56 76 48 - 29Attn: Technical Support
Phone Technical Support +49 (0)	2 31 56 76 48 - 10
If you wish to write us for support:	Promise Technology GermanyEuropaplatz 944269 Dortmund, Germany

Italy

E-mail Support e-Support On-Line
Fax Support 0039 06 367 12400 Attn: Technical Support
Phone Support 0039 06 367 12626
If you wish to write us for support:	Promise Technology ItalyPiazza del Popolo 1800187 Roma, Italia

Taiwan

E-mail Support e-Support On-Line
Fax Support [phone] Attn: Technical Support
Phone Support [phone] (ext. 8811)
If you wish to write us for support:	Promise Technology, Inc.2F, No. 30, Industry E. Rd. IXScience-based Industrial ParkHsin-Chu 30075, Taiwan (R.O.C.)

China

E-mail Support [e-mail]
Fax Support	[phone] Attn: Technical Support
Phone Support [phone]/8095
If you wish to write us for support:	Promise Technology ChinaRoom 1205, Tower CWebok Time Center, No.17South Zhong Guan Cun StreetHai Dian District, Beijing 100081, China

Limited Warranty

Promise Technology, Inc. ("Promise") warrants that for three (3) years from the time of the delivery of the product to the original end user:

a) the product will conform to Promise's specifications;

b) the product will be free from defects in material and workmanship under normal use and service.

This warranty:

a) applies only to products which are new and in cartons on the date of purchase;

b) is not transferable;

c) is valid only when accompanied by a copy of the original purchase invoice.

d) Is not valid on spare parts, fans, and power supplies

This warranty shall not apply to defects resulting from:

a) improper or inadequate maintenance, or unauthorized modification(s), performed by the end user;

b) operation outside the environmental specifications for the product;

c) 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.

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.

Promise's sole responsibility with respect to any product is to do one of the following:

a) replace the product with a conforming unit of the same or superior product;
b) 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.

Returning 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 will assist you in determining whether the product requires repair. If the product needs repair, the Technical Support Department will issue 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.), with a copy of your proof of purchase to:

USA and Canada: Promise Technology, Inc.

Customer Service Dept.

Attn.: RMA # ____

47654 Kato Road

Fremont, CA 94538

Other Countries: 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 product's problem(s)
• Write an attention line on the box with the RMA number
• Include a copy of proof of purchase

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 will be under warranty for the remainder of the original warranty term from purchase date, or 30 days, whichever is longer.

Promise will pay for standard return shipping charges only. You will be required to pay for any additional shipping options (such as express shipping).

Appendix A: Useful Information

The appendix covers the following topics:

• Serial Connector Pinout (page 291)
  • SNMP MIB Files (page 292)

Serial Connector Pinout

Below is the pinout diagram for the DB-9 serial connector on all VTrak models.

The diagrams represent the connector as you see it looking at the back of the VTrak controller.

Pin Signal
1	-
2	RXD
3	TXD
4	-
5	GND
6	-
7	-
8	-
9	-

SNMP MIB Files

Promise supplies four MIB files to integrate the VTrak subsystem into your SNMP system. These files are in the SNMP folder on the VTrak Product CD. The MIB files include:

- FCMGMT-MIB.mib

• ISCSI-MIB.mib

- IF-MIB.mib

• r a i d 4 . m i b

Loading MIB Files

Use a MIB browser to load these files. You can load the MIB files in any order. For help with this procedure, see the instructions that came with your MIB browser.

Index

Numerics

10 GB Truncate 93, 139, 233

2 TB Limitation 284

A

about this manual 1

adaptive writeback cache 94, 139

defined 232

alarm

cancel 99, 197

sounding 244, 269

alias

controller 93, 139

disk array 108, 111, 112, 150, 156

logical drive 34, 108, 121, 150

physical drive 102, 145

subsystem 47, 136

architectural description 3

array incomplete, reported events 268

Auto Fix 54, 122, 160

Auto Rebuild 51, 114, 172, 270

axles

RAID 50 34, 108, 112, 150, 156, 226

B

background activities

deleting schedule 54

list of scheduled 53

running 52

scheduling 53

settings 51, 172

view 50

batteries 97, 142

battery

failure 277

recondition 98, 142

replace 211

reported events 255, 256

Battery Reconditioning 53

BBU, reported events 257

blower, reported events 256

browser

does not connect 280

SNMP 79

web server settings 77

WebPAM PROe 29, 38

buzzer

settings 99, 197

silence 99, 197

sounding 244, 269

test 99, 197

C

cache batteries 97, 142

cancel alarm 99, 197

capacity coercion 93, 139

defined 233

capacity, specify for logical drive

34, 108, 112, 150, 156

certificate, security 36

change RAID level 113, 154, 235

CHAPs

adding 71, 170

deleting 72, 171

editing 72, 171

viewing 71, 170

check table, logical drive 123, 158

CIM

service 82, 188

settings 81, 188

clear statistics 88, 192

CLU

log in 132

log out 134

main menu 133

online help 134

problem reporting 250

serial connection 132

Telnet connection 132

Command Line Interface (CLI) 23

Command Line Utility (CLU) 23, 283

command queuing, physical drives 101, 144

configuration status, physical drive 101

connection

power 21

problems 278

connector

RJ45 278

serial 20

controller

adaptive writeback cache 94

alias 93, 139

cache flush interval 94, 139

heartbeat LED 245, 283

information 92, 138

locate 91, 139

replace 216

reported events 257, 258, 259

settings 93, 138

statistics 93

status LED 249

unsaved data in cache 281

view 91

cooling unit

LED 248

status 96, 141

create 31

disk array 105, 147

logical drive 111, 156

create, cont.

spare drive 126, 176

user 60, 181

critical

disk array 110, 152

logical drive 119, 158

D

data ports

stattistics 69, 169

date and time, subsystem 25, 27, 48, 137

dedicated spare drive 125, 126, 127, 176, 177, 234

logical drive 113, 157

spare drive 127

user 61, 183

deleting schedule, background activities 54

DHCP server changed IP address 280

dirty cache LED 249

Discover button 46

disk array 31

advanced creation 34, 108, 150

alias 108, 111, 112, 150, 156

automatic creation 32, 106, 148

create 31, 105, 147

critical 110, 152, 269

delete 109, 151

expand 154

expansion 237

express creation 33, 106, 149

incomplete array 153

information 110, 152

locate 110, 156

disk array, cont.

manual rebuild 115

Media Patrol 115

migrate 113, 154

offline 269

operational status 110, 152

PDM 116, 155

physical drive selection 34, 108, 150

rebuild 114, 154, 270

rebuilding 111, 152

reported events 257

settings 111, 152, 153

synchronizing 110, 152

transition 116

transport 117, 153

transport ready 111, 152

view 105

disk drives, installing 15

disk status LED 95, 246, 269, 270, 271

DMA mode, SATA drives 101, 144

download firmware image file 199, 202

E

email

service 77, 185

settings 76, 184

test message 59, 76

email messages 252

enclosure

information 96, 140

locate 95, 143

overheat 276

reported events 258

settings 97, 141

temperature 96, 141

view 95

voltage 96, 141

error block threshold 51, 173

event

iSCSI 259

notification response 255

severity 58, 82, 189

subscriptions 58

event log

clear 49, 50, 174, 175

NVRAM 174, 250

problem reporting 252

reported events 258

runtime 48, 174, 250

save 49, 50

expand disk array 113, 154

expansion ranges 237

export user database 84

F

failed

battery 277

power supply 275, 277

failure recovery, physical drive 269

FCC statement 7

Features

highlights 4

operational 5

subsystem and controller 5

system management 6

firmware

update in CLU 202

update in WebPAM PROe 199

firmware image file, download 199, 202

firmware update

from PC 200

from TFTP server 199, 202

WebPAM PROe 199, 202

flush interval, controller cache 94, 139

force offline 103, 146

force online 103, 146

forced unlock 55

FRU LED 245

FRU status LED 247

FRU VPD 97, 140

full initialization 121, 160

G

GB Truncate 93, 139, 233

global spare drive 125, 126, 127, 176, 177

Group Rounding 94, 139, 233

H

heartbeat LED 245

High 51

hot spare drive 234, 269

|

import user database 85

incomplete array 153, 272

inconsistent block table 123, 158

information

controller 92, 138

disk array 110, 152

enclosure 96, 140

FRU VPD 97, 140

logical drive 118, 129, 158

physical drive 101, 145

subsystem 47

initialization

defined 234

settings 51, 173

initialize logical drive 121, 160

initiator

adding 73, 179

deleting 73, 180

iSCSI 73, 179

installing disk drives 15

Internet access to WebPAM PROe 36

intranet access to WebPAM PROe 284

IP address

DHCP or static 24

DHCP server changed 280

email (SMTP) server 76, 184

iSCSI port 63, 163

iSNS 170

management port 24, 25, 27, 29, 38, 62, 132, 162, 279, 280

netsend recipient 83

netsend recipient PC 82, 189

subsystem in WebPAM PROe 43

trap sink 80, 187

viewing 24

VLAN 70, 169

iSCSI

CHAPs 71, 72, 170, 171

connection problems 279

connections 72, 171

data port settings 62, 163

initiator 73

IP address 63, 163

iSNS 70, 169

jumbo frames 63, 164

LUN map 74

LUN masking 74, 179

node 67, 167

node settings 68, 168

ping 72, 171

port statistics 69, 169

port targets 69

portal 70, 169

session 70, 169

target ports 168

iSCSI Port IP address

CLI 25

iSNS

making settings 71, 170

view information 70, 169

J

jumbo frames, enable 63, 164

L

language selection, WebPAM

PROe 31, 40

LED

controller 245

controller heartbeat 283

controller status 91, 139, 249

cooling unit 248

dirty cache 91, 139, 249, 281

disk status 95, 246, 269, 270, 271

drive carrier 21

Ethernet connector 279

fan 248

FRU 245, 283

FRU status 247

heartbeat 245, 283

logical drive 245, 269

power 245, 283

power supply 248

power/activity 246

red or amber 245

RJ45 connector 279

link aggregation

changing 66, 166

creating 65, 166

deleting 66, 166

viewing 65, 165

locate

controller 91, 139

disk array 110, 156

enclosure 95, 143

logical drive 119, 161

locate, cont.

physical drive 100, 146

power supply 96, 140

spare drive 125

lock

releasing 55, 137

renewing 55, 137

setting 55, 136

subsystem 54, 136

view status 54, 136

log in

CLI 23, 280

CLU 132

WebPAM PROe 29, 38

log out

CLU 134

WebPAM PROe 35, 45

logical drive

alias 34, 108, 121, 150

capacity 34, 108, 112, 150, 156

check table 123, 158

create 111, 156

critical 119, 158

delete 113, 157

information 118, 129, 158

initialize 121, 160

LED 269

locate 119, 161

LUN 123, 179

offline 119, 159

partition and format 235

RAID level 34, 108, 112, 150

rebuilding 118, 158

Redundancy Check 122, 160

reported events 259, 260

settings 120, 159

status 118, 158

synchronization 120

synchronizing 118, 158

logical drive, cont. transport ready 119, 159 view list of all 129, 158 Logical Drive Summary 129 logout other users 61 LUN logical drive 123 map, view 74 masking, enable 74, 179

M

MAC address, viewing 24

main menu, CLU 133

Management Port IP address 24 MAC address 24 settings 62, 162

Media Patrol 115 defined 238 enable 34, 51, 108, 153, 172 reported events 260 run 52, 136 schedule 53

MIB files 292

migrate disk array 113, 154 reported events 264

Migration settings 51, 172

mount VTrak in a rack 10

N

NetSend recipients 82, 189 requirements 83, 190 service 83, 189 settings 82, 188

node information 67, 167 node settings 68, 168

null-modem cable 132 NVRAM event log 174, 250

0

offline logical drive 119, 159 physical drive 103, 146 online capacity expansion 235 reported events 261

online help CLU 134 WebPAM PROe 42

operational status disk array 110, 152

orphan watermark 138 overheated enclosure 276 overview of VTrak 2

P

partition and format 235 password CLI/CLU 23, 132 CLU 182 WebPAM PROe 30, 38, 59

Pause on Error 54, 122, 160 PDM 108, 116, 150, 153, 155 defined 238 enable 34, 111 reported events 261 running 52 settings 51, 173 trigger settings 51, 173 triggers 238

PFA condition 102, 145 physical drive alias 102, 145 capacity coercion 93, 139, 233 command queuing 101, 144 configurational status 101 DMA mode 101, 144

physical drive, cont.

failure recovery 269

force offline or online 103, 146

from older subsystem 283

information 101, 145

locate 100, 146

operational status 101

read cache 101, 144

reported events 262

select for array 34, 108, 150

select for spare 126, 176

settings 102, 145

stale and PFA condition 102, 145, 270, 273

statistics 102

supported 283

write cache 101, 144

physical drives

global settings 100, 144

list 100, 144

physical drives, installing 15

pinout, serial connector 291

popup messages 252

port target Information 69

portal

information 70, 169

power

connection 21

LED 245

power supply

failed 275, 277

fan failure 276

fan reported events 264

LED 248

locate 140

replace 204

reported events 263

status 96, 140

power/activity LED 21, 246

Predictive Data Migration 238

privileges

CLU user 182

WebPAM PROe user 60

problem reporting

CLU 250

WebPAM PROe 252, 269

Q

quick initialization 121, 160

R

rackmount the VTrak 10

RAID

block and double parity stripe 224, 229

block and parity stripe 223, 229

enhanced mirror 222, 229

introduction 219

mirror 221, 228

mirror + stripe 225, 230

stripe 220, 228

striping of distributed parity 226, 230

RAID level

change 235

logical drive 34, 108, 112, 150

RAID levels

choosing 228

RAID 0 220, 228

RAID 1 221, 228

RAID 10 225, 230

RAID 1E 222, 229

RAID 5 223, 229

RAID 50 226, 230

RAID 6 224, 229

read cache

physical drive 101, 144

policy 35, 109, 112, 121, 150, 156

read cache, cont.

policy defined 232

read check table 123, 158

reassigned block threshold 51, 173

rebuild

disk array 114, 154, 270

reported events 265

settings 51, 172

rebuilding

disk array 111, 152

logical drive 118, 158

recipients, NetSend 82

recondition a battery 98, 142

red × 244, 252, 275

Redundancy Check 53, 54, 122, 160

reported events 265

settings 51, 173

regulatory statements 7

releasing lock 55, 137

renewing lock 55, 137

repair, returning product for 289

replace

battery 211

blower 205

controller 216

fan 205

power supply 204

reported events

array incomplete 268

battery 255, 256

BBU 257

blower 256

controller 257, 258, 259

disk array 257

enclosure 258

event log 258

iSCSI 259

logical drive 259, 260

Media Patrol 260

online capacity expansion 261

reported events, cont.

PDM 261

physical drive 262

power supply 263

stripe level migration 267

synchronization 267

system 268

transition 268

resource not available reported

event 266

response to event notification 255

restart the subsystem 90, 196,

201, 202, 203

restore default settings 87, 193

returning product for repair 289

revertible spare drive 116, 125,

126, 127, 176, 177, 239

RJ45 connector 278

RMA number 290

RS232 connection 20

running background activities 52

runtime event log 48, 174, 250

s

SATA disk drive, install 17

scheduling background activities

53

screws, counter-sink 16

sector size 34, 109, 112, 150, 156

sector size, defined 231

security certificate 36

serial cable connections 20

serial connection 132

setting up 23

serial connector pinout 291

session information 70, 169

setting lock 55, 136

settings

background activities 51, 172

buzzer 99, 197

CIM 81, 188

controller 93, 138

disk array 111, 152, 153

email 76, 184

enclosure 97, 141

initialization 51, 173

iSCSI data port 62, 163

logical drive 120, 159

Migration 51, 172

NetSend 82, 188

PDM 51, 173

physical drives 100, 102, 144

rebuild 51, 172

Redundancy Check 51, 173

restore default 87, 193

SLP 77, 185

SNMP 79, 186

spare drive 127, 177

subsystem management port 62, 162

synchronization 51, 173

Telnet 79, 186

temperature 97, 141

Transition 51, 173

user 57, 58, 182, 183

Web Server 77, 185

severity of events 58, 82, 189

shutdown the subsystem 89, 194

SLP

service 77, 185

settings 77, 185

SMART 93, 139

SMART error 267

SNMP

MIB files 292

service 81, 187

settings 79, 186

trap sinks 80, 187

Software Services 76

Spare Check 128, 177

reported events 266

spare drive 234, 269

create 126, 176

delete 127

locate 125

reported events 266

select physical drive 126, 176

settings 127, 177

Spare Check 128, 177

transition 116

view 125

Spare Drive Check 53

specifications 6

stale condition 102, 145

statistics

clear 88, 192

controller 93, 138

data ports 69, 169

logical drive 120, 158

physical drive 102, 145

status

controller 91, 138

cooling unit 96, 141

logical drive 118, 158

physical drive 101, 145

power supply 96, 140

spare drive 125

subsystem lock 54, 136

Storage Network 46

stripe level migration reported

event 267

stripe size 34, 109, 112, 150, 156

stripe size, defined 231

subsystem

alias 47, 136

date and time 25, 27, 48, 137

fully booted 283

information 47

iSCSI data port settings 62, 163

lock 54, 55, 136

maintenance 199

management port settings 62, 162

Media Patrol 136

restart 90, 196, 201, 202, 203

shutdown 89, 194

subsystems

logging into 46

on the storage network 46

synchronization 113

disk array 110, 152

logical drive 118, 120, 158

reported events 267

settings 51, 173

system reported event 268

T

Table Rounding 94, 139, 233

target port information 168

TCP offload engine 69, 168

Technical Support, contact 285

Telnet

connection 132

service 79, 186

settings 79, 186

temperature, enclosure 96, 141

terminal emulation program 23

test

buzzer 99

email 59, 76

TFTP server 199, 202

timing out, WebPAM PROe 284

TOE 69, 168

Transition

automatic 241

defined 239

manual 241

settings 51, 173

spare drive 116

transition, reported events 268

transport disk array 117, 153

transport ready

disk array 111, 152

logical drive 119, 159

trap sinks 80, 187

U

unpacking the VTrak 9

user

create 60, 181

delete 61, 183

event subscriptions 58

logout others 61

password, change 59

privileges 60, 182

settings 57, 58, 182, 183

view sessions 61

user database

export 84

import 85

username and password

CLI/CLU 23, 132

WebPAM PROe 30, 38

users, view 57, 181

V

view

background activities 50

controllers 91

disk arrays 105

enclosure 95

list of all logical drives 129

lock status 54

view, cont.

physical drives 100

scheduled activities 53

spare drives 125

users 57, 181

virtual LANs

changing 64, 165

creating 63, 164

deleting 65, 165

jumbo frames 64, 165

viewing 63, 164

VLANs

changing 64, 165

creating 63, 164

deleting 65, 165

jumbo frames 64, 164, 165

viewing 63, 164

voltage, enclosure 96, 141

VTrak

architectural description 3

beeping 244, 269

features and benefits 4

overview 2

rackmounting 10

specifications 6

unpacking 9

warranty 7, 288

W

warranty 7, 288

Web Server

service 78, 186

settings 77, 185

WebPAM PROe 31, 40

access over an intranet 284

access over the Internet 36

browser 29, 38

Event Frame 44

Header 42

initial VTrak setup 29

interface 41

log in 29, 38

log out 35, 45

Management View 44

no browser connection 280

problem reporting 252, 269

storage network 46

times out 284

Tree View 43

username and password 30, 38

write cache

physical drive 101, 144

policy 35, 109, 112, 121, 150, 156

policy defined 232

write check table 123, 158

Y

yellow! 244, 252, 275