AdminiStor Storage Management Software Guide

Adm6.book Page i Thursday, May 6, 2004 10:06 AM

S O F T W A R E G U I D E

AdminiStor

S t o r a g e M a n a g e m e n t S o f t w a r e

Adm6.book Page ii Thursday, May 6, 2004 10:06 AM

Adm6.book Page 1 Thursday, May 6, 2004 10:06 AM

S O F T W A R E G U I D E

AdminiStor

S t o r a g e M a n a g e m e n t S o f t w a r e


Fujitsu Europe Limited

Restricted Rights and Liability

No part of this manual may be reproduced, stored in a retrieval system, or transmitted, in any form or by any means, electronic, mechanical, recording, or otherwise, in whole or part, without prior written permission from Fujitsu Europe Limited.

Fujitsu Europe Limited shall not be liable for any damages or for the loss of any information resulting from the performance or use of the information contained herein. Your rights to the software are governed by the license agreement included with any accompanying software. Fujitsu Europe Limited reserves the right to periodically revise this manual without notice. Product features and specifications described are subject to change without notice.

Copyright

Fujitsu Europe LimitedHayes Park CentralHayes End RoadHayes, Middlesex, England UB4 8FE

Copyright © 2004 Fujitsu Europe Limited. All Rights Reserved.

imageRAID and the imageRAID logo are registered trademarks of Fujitsu Europe Limited, Fujitsu is a registered trademark of Fujitsu Limited.

Other company and product names herein may be trademarks or registered trademarks of their respective companies.

Contents


About this Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vWelcome . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vFeatures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viCustomer Care . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viiProduct Identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1AdminiStor Plus Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4AdminiStor Plus Host and Server . . . . . . . . . . . . . . . . . . . . . . . . 5AdminiStor GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

RAID Configuration Utility (RCU) . . . . . . . . . . . . . . . . . . . . . . . . 6Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7DataBase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Security and Encryption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8SNMP Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

2 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Setup Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Installations for Microsoft Windows NT/Windows 2000 . . . . . . . . 12System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Before You Install AdminiStor on a Windows System . . . . . . . . 12Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Removing AdminiStor (Windows) . . . . . . . . . . . . . . . . . . . . . . . 20

Installations for Solaris . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Before You Install AdminiStor on a Solaris System . . . . . . . . . . . 21Solaris Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Removing AdminiStor (Solaris) . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Installations for Linux (Red Hat v6.2, v7.1, and v7.2) . . . . . . . . . . 26System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26Before You Install AdminiStor on a Red Hat Linux System . . . . . 26

i

Table of Contents

ii


Red Hat Linux Version 6.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Recompile the Kernel for Red Hat Linux v 6.2 . . . . . . . . . . . . . 27Installing the FC HBA on Red Hat Linux v 6.2 . . . . . . . . . . . . . 29

Red Hat Linux Version 7.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Upgrading the Kernel for Red Hat Linux v7.1 . . . . . . . . . . . . . 31

Installing the FC HBA on Red Hat Linux v7.1 . . . . . . . . . . . . . . . 31Configure Red Hat Linux v7.1 for Multi-LUN Support . . . . . . . . 34

Red Hat Linux Version 7.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Modularized Kernel for Red Hat Version 7.2 . . . . . . . . . . . . . . 38

AdminiStor Installation On Red Hat Linux . . . . . . . . . . . . . . . . . 44Installation of Java on Red Hat Linux . . . . . . . . . . . . . . . . . . . . . 46Removing AdminiStor (Linux) . . . . . . . . . . . . . . . . . . . . . . . . . . 47

3 Startup & Navigation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49AdminiStor Component Overview . . . . . . . . . . . . . . . . . . . . . . . 49AdminiStor Plus Server Module . . . . . . . . . . . . . . . . . . . . . . . . . 49AdminiStor Plus Host Module . . . . . . . . . . . . . . . . . . . . . . . . . . 49AdminiStor GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Starting AdminiStor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50Starting AdminiStor Plus Server and AdminiStor Plus Host . . . . . 50Starting AdminiStor GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Signing On to a Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52Access Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Viewer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52Operator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52Administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Signing On . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53Navigating AdminiStor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55Buttons, Menus, and Menubar . . . . . . . . . . . . . . . . . . . . . . . . . . 55Function Control Buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55Pull-Down Menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Session Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56Domains Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Components of the AdminiStor GUI Window . . . . . . . . . . . . . . 59Components of the Client View Menu . . . . . . . . . . . . . . . . . . . . 60

Physical Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60Logical Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66Progress Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69System Menu Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

User Interface Icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72Status Indicator Icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Exiting AdminiStor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74Closing the Domain Connection . . . . . . . . . . . . . . . . . . . . . . . . 74

Table of Contents

Adm6.book Page iii Thursday, May 6, 2004 10:06 AM

Disconnecting from the AdminiStor Server . . . . . . . . . . . . . . . . . 75Quitting the AdmimiStor GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . 75Exiting AdminiStor Server and AdminiStor Host . . . . . . . . . . . . . 76

Notification Configuration and Preference Settings . . . . . . . . . . . 77E-mail Setup and Configuration . . . . . . . . . . . . . . . . . . . . . . . . . 77E-mail Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78SNMP Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

4 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85Setting Up and Modifying Controller Options . . . . . . . . . . . . . . . 86Function Control Buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

Scan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94Reboot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94Shutdown Both. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94Flash Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94Host Configuration Tab (Restore and Apply buttons) . . . . . . . . 94

Running RAID Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95Drive Requirements for Specific RAID Levels . . . . . . . . . . . . . . . 95Entering RAID Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96Automatic Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98Assisted Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100Manual Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

Other Configuration Activities . . . . . . . . . . . . . . . . . . . . . . . . . . 112Editing Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

Changing an Array Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113Deleting an Array . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113Creating a Partition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114Changing A Partition Name . . . . . . . . . . . . . . . . . . . . . . . . . . . 116Changing A Partition LUN . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117Deleting A Partition. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118Adding A Pool Spare. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

Expanding Array Capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120Increasing the Capacity (Expanding Array Size or Expanding

Partition Size) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121Other Utility Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125Changing Array Ownership . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125Trusting an Array . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126Synchronizing Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128Kill Other Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129Changing the Operating Mode . . . . . . . . . . . . . . . . . . . . . . . . . . 131Clearing Metadata from a Drive . . . . . . . . . . . . . . . . . . . . . . . . . 133Adding a Hot Spare . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134

iii

Table of Contents

iv

Adm6.book Page iv Thursday, May 6, 2004 10:06 AM

Viewing Array Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136Verifying the Array . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138Viewing Drive Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139Viewing Drive Status from Controller Channels . . . . . . . . . . . . . 140Locating a Disk Drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140Downing a Disk Drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141Updating Controller Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . 142

5 Monitoring and Notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145Enclosure Services Monitoring (AdminiStor Plus Only) . . . . . . . . 145Controller Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147Event Monitoring (System Log) . . . . . . . . . . . . . . . . . . . . . . . . . 152

Exporting the Log. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154

A Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157

B Domains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167Domains Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168Viewing the Domain Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168Modifying Device Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171Selecting Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172Creating a Logical Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173Modifying Logical Domains . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175Deleting a Device from a Logical Domain . . . . . . . . . . . . . . . . . 176

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177

Preface

Adm6.book Page v Thursday, May 6, 2004 10:06 AM

About this Manual

Welcome

Congratulations on the purchase of AdminiStor Storage Management Software from

Fujitsu Europe Limited. AdminiStor is a powerful and full-featured tool designed to

monitor, manage, and configure imageRAID™ SCSI Series Storage Systems both

centrally and remotely thus providing an unparalleled storage management software.

The explosive growth in storage capacity connected to multiple distributed servers

has created an environment that is increasingly difficult to manage. Designed for

heterogeneous environments, AdminiStor is an advanced software solution that

greatly reduces the complexity of storage management leading to administrative

costs.

AdminiStor is a graphical user interface software suite used to define RAID

configurations, monitor and report enclosure and component status, and manage

disk arrays in direct connect or SAN-wide storage solutions. It provides a centralized,

remote management software resource to control primary storage assets vital to

ensuring maximum data reliability, network up-time, and system serviceability.

AdminiStor provides a drill-down, tree-like structure allowing users to access

installed RAID and storage controllers, physical components and logical arrays, all

using point-and-click technology. Operating system-specific host software resides on

most platforms to help configure and maintain storage. AdminiStor running from a

Java-enabled specific browser allows users to manage nStor storage resources from

anywhere in the world.

v

About this Manual

vi

Adm6.book Page vi Thursday, May 6, 2004 10:06 AM

AdminiStor provides three security levels of user access rights allowing for

different levels of management from system administrators. The security access

can be configured uniquely for each different storage element.

Using push technology, AdminiStor eliminates network traffic typical of

polling-based systems. With its easy to use graphical interface, AdminiStor

eliminates the confusing views of SAN storage as seen from individual system

storage managers. And AdminiStor provides complete historical database

management of events for each managed storage sub-system.

Features

The following are major features of the AdminiStor Storage Management

software:

� Supports Java-enabled web browsers through a Java plug-in (Windows and

Solaris).

� Manage single or multiple imageRAID SCSI Series Storage Systems locally

or across the network providing higher availability.

� Complete RAID configuration capabilities.

� Automatic alert notifications are provided via “push” technology.

� Consolidated view of all nStor storage system within a workgroup,

department, or enterprise.

� User defined access to permit specific levels of access to specific users and

groups of user to the storage systems. This sets limitations to what levels of

user access control they may have to the specific storage systems.

� A historical database integration that maintains event logs, device

information, logging, and tracking/monitoring of all events and SNMP traps

in a JDBC-compliant database.

� Embedded private socket web server.

� Monitored notifications provided via SNMP traps and email.

� GUI interface with a industry standard tree-like display of components

familiar to most Windows users.

Features

About this Manual

Adm6.book Page vii Thursday, May 6, 2004 10:06 AM

Customer Care

You will find warranty, customer service and technical support on the Fujitsu

web site. Refer to http://www.fel.fujitsu.com/home/help.

Product Identification

Cross-Reference Product Identification

Storage Enclosure Number of Controllers Model of Controller

IRS-JBOD0 JBOD

(4000S)

IRS-1U160xx-xx1 imageRAID Controller (JSS122)

(4110S/4120S)

IRS-2U160xx-xx2 imageRAID Controller (JSS122)

(4110S/4120S)

Customer Care vii

About this Manual

viii

Adm6.book Page viii Thursday, May 6, 2004 10:06 AM

Product Identification

Chapter 1


Introduction

Overview

Today, system administrators face many challenges in supporting a

heterogeneous network. A typical network environment has several computer

servers running different types of operating systems, storage systems, and

workstations. Monitoring these storage systems can be a very difficult task.

AdminiStor makes this task much easier. Now a centralized view of the storage

systems is available simply by using your favorite web browser and connecting

via the Internet or intranet.

AdminiStor has an enhanced package known as AdminiStor Plus that is designed

to monitor and manage imageRAID SCSI Series Storage Systems, from simple

single computer installations to complex networks and multiple Storage Area

Networks (SANs). In order to achieve this, AdminiStor Plus runs continuously on

selected systems connected to the storage, and coordinates the actions and

reporting among those systems.

There are three major sets of functionality. First is the AdminiStor Plus Host,

which connects to the storage either directly or remotely. Automatic monitoring

programs in these AdminiStor Plus Hosts check on the health of the storage

generating messages as needed, and provide the ability to adjust, configure, and

interact with the storage systems. All AdminiStor Plus Hosts, in a given customer

installation, can communicate with each other so their activities can be

coordinated. This allows AdminiStor Plus to greatly simplify complex storage

architectures, such as SANs.

1

Chapter 1 - Introduction

2


One of the AdminiStor Plus Hosts is selected to become the AdminiStor Plus

Server. The AdminiStor Plus Server is where all of the activities are coordinated, a

database of activity and status are kept, and the messages and notifications

originate. The AdminiStor Plus Server also includes a web server to enable access

by users and system administrators.

The AdminiStor Graphical User Interface (GUI) runs within the context of a

Netscape or Internet Explorer browser, meaning that the GUI is available

anywhere in the world where connections are allowed to the AdminiStor Plus

Server system. The AdminiStor GUI is where people can see the status of the

storage, change configurations, review and evaluate events that have happened

within the storage system, and perform operational tasks such as device

replacement and consistency checks.

AdminiStor supports any number of instances of GUIs, at any number of

locations, all running at the same time. There is no need to go to a dedicated

location, or worry about shutting down one AdminiStor GUI before another can

be used. During times when the AdminiStor GUI is normally not in use, the

AdminiStor Hosts communicate all problems and status changes to the

AdminiStor Server which can notify users through events placed in the system

log, Emailed to individuals, groups, or pagers, or send them via SNMP traps to

other management stations. This event notification can be customized to ensure

that only the changes of interest to the user are communicated. The AdminiStor

Hosts are on watch continuously 24 hours per day – seven days a week.

In a simple, single computer environment all of these modules will be located on

the same host computer system, and there is usually only one or two people that

will interact with AdminiStor Plus. These systems will be able to use a straight

forward installation without confusion.

In a modest SAN environment, several computers will be connected to the same

storage systems, perhaps with some parts shared among computers, and perhaps

with some parts exclusively assigned to certain computers. These systems will

benefit from the coordination accomplished by the AdminiStor Plus Server, by

collecting the information from the various computers running the AdminiStor

Plus Host and presenting a unified view of the storage. The status of shared

storage is presented as a single status, eliminating the confusion of various

computers each acting as if the shared storage were unique to that system.

Overview



In larger storage environments, there is a need to coordinate storage management

across the entire network, but there is also a requirement to delegate responsibility

for various subsets to different people. AdminiStor Plus allows storage domains to

be defined, each with a different password. Every module in the storage system

can be assigned to storage domains as needed and can belong to multiple

domains if desired. This means that a system administrator can have a single

password to access all storage assigned to his domain, no matter what computer

systems the storage is able to communicate with. This powerful capability allows

the system manager to grant limited access to storage management without

needing to expose full privileged access to any operating system.

In addition to defined storage domains, AdminiStor Plus has physical domains.

These reflect the reality that a system administrator with privileged access to a

computer has the need and the right to make changes to the storage components

available to that computer. All storage managed by AdminiStor Plus belongs to at

least one physical domain, defined by the AdminiStor Plus Host that can

communicate with that component. In the case of shared storage components,

they will belong to multiple physical domains, each defined by the AdminiStor

Plus Host that can access the storage.

The combination of physical domains, plus user defined domains, creates a rich

environment to support any system administration management structure desired.

Operating system administrators have the access they need to configure and

manage the storage they use, while storage administrators can effectively deal

with their storage, independent of the various computers using that storage.

AdminiStor Plus recognizes that not all storage management system users need to

perform the same tasks. Some users simply need to be able to evaluate the

current status, others must deal with maintenance issues, and selected individuals

will reconfigure and deploy the storage. There are three levels of access defined

for AdminiStor.

The first level is <Viewer>, where all aspects of the storage components can be

seen, but nothing can be changed. <Viewer> access is especially useful to allow

power users to see what is going on inside their systems, without opening the

system up to unexpected changes.

Overview 3


4


The second level is <Operator>, where actions needed to maintain storage can be

performed. This would include replacement of failed components and rebuilding

or checking redundancy information. No changes that would impact data

integrity or availability are allowed.

The highest level (third level) is <Administrator>, which allows full access to the

storage configuration. Only at this level can storage be reassigned, and data

impacted.

The three level privilege mechanism, combined with the physical and logical

domains, can support a wide variety of management styles over a range of

organizations. This ensures that AdminiStor Plus can grow with your company,

and adapt to the changes that are now a part of modern business reality. Yet all

of this comes in a package that is easy to install and use on a single computer.

AdminiStor Plus Modules

Illustration of Installed AdminiStor Modules

LAN

AdminiStor GUI

AdminiStorHost

Installed

AdminiStorHost

Installed

AdminiStorHostInstalled

AdminiStorHostInstalled

AdminiStorHost

Installed

AdminiStorServer

Installed

imageRAID Storage System

Switch

Host ServerHost Server

Host Server Host Server

imageRAID Storage System

Host Server Host Server

AdminiStor Plus Modules



AdminiStor Plus Host and Server

The AdminiStor Plus Host (ADM Host) provides the communication interface to

the AdminiStor Plus Server (ADM Server) for management and control of the hosts’

attached storage.

The AdminiStor Plus Server module is installed on a local host system. It has no

user interface and the storage system is accessed via the client GUI module using

a web browser. There will be at least one AdminiStor Plus Server in the

environment. It provides the communication interface to the AdminiStor GUI and

to each of the AdminiStor Plus Hosts. It may or may not have imageRAID SCSI

Series Storage Systems attached.

Events that occur are logged in AdminiStor Plus’s historical database which can

be reviewed at any time and can be integrated into a JDBC-compliant database.

If a storage system is shared among hosts, similar to what is found with a SAN,

the AdminiStor Host that finds the storage system first will “claim” ownership of

the system. When a subsequent AdminiStor Host(s) identify these already

“claimed” storage systems, they will mark them as passive devices and they

become the passive or redundant path owners. When you examine the tree

structure from the Client View window and you are logged in to a Domain that

has an AdminiStor Host which is a passive owner, you will notice the icons will

have a blue “P” overlaid on the icon of the redundant path devices. These icons

identify the passive devices and indicate that you are communicating through a

passive ADM Host to the primary owner ADM Host. If you are logged into a

Domain with a passive ADM Host, devices below the controller are not

displayed. You will still have management and control abilities from the passive

ADM Host through the active ADM Host.

If the primary AdminiStor Host owner of that storage fails, then one of the

passive AdminiStor Host will become the new owner of that storage. This is

determined by which passive ADM Host discovers the storage system first.

A result of this feature causes AdminiStor to be considered a fault tolerant

environment. Although, if the AdminiStor Server fails, the AdminiStor Server will

not be able to send messages to its established user’s. Each AdminiStor Host(s)

will continuously check to determine if the AdminiStor Server is alive, once that

occurs, they will once again communicate with each other normally.

AdminiStor Plus Host and Server 5


6


The level of fault tolerance is provided by the multiple path feature. The

AdminiStor Host that has ownership of the storage system is responsible for all

communication and management, and the redundant path or passive AdminiStor

Host(s) are waiting in the event the primary AdminiStor Host owner should go

down. If that occurs, the first AdminiStor Host to discover the storage system(s)

will become the new owner and the remaining AdminiStor Host(s) will remain

the passive redundant paths. When the AdminiStor Host that was the primary

owner comes back online, it will then become a passive owner.

Also, there is no particular order in which the AdminiStor Server and AdminiStor

Host are required to be started. Because of this feature should an AdminiStor

Server system go down, once it is back online communication will resume in a

normal fashion with the AdminiStor Host(s), as the ADM Host will continue to

poll until they locate the ADM Server. The same applies to the ADM Host, where

it will resume normal communication anytime it comes online.

AdminiStor GUI

The AdminiStor GUI provides the user interface allowing the ability to monitor,

configure, and manage your imageRAID SCSI Series Storage Systems. This

AdminiStor GUI runs from within a standard web browser installed on your

system.

The AdminiStor GUI module presents the overall system in a tree-like structure

that permits administrators or users to easily view the entire system, the status of

all components (e.g., controller cards, channels, drives, cabinet enclosures, fans,

temperature, and power supplies, etc.), and will launch the RAID Wizard to

configure imageRAID Controllers, as well as perform the LUN Mapping.

RAID Configuration Utility (RCU)

The AdminiStor RCU capabilities include a RAID Wizard, which allows automatic,

assisted, or manual configuration of the disk array hardware. This ensures that

the novice can have optimized storage, while the expert can set up the system to

the most exacting specifications.

Included with AdminiStor RCU is management of hot spares and component

replacement. Any failures within the imageRAID system can be dealt with easily

and effectively.

AdminiStor GUI



Monitoring

The most important ongoing function of AdminiStor Plus is its ability to monitor

the health and status of each storage system. Each disk drive is examined on a

periodic basis to check for acceptable soft error rates, and ensure that the data is

available to the AdminiStor Plus Host systems. Warnings are issued when

conditions are not good, and urgent messages are sent when there are failures

that impact data availability. The storage system imageRAID controllers are

checked for accessibility and health, and any problems are then reported. The

automatic error recovery performed by the imageRAID controllers is observed,

and urgent messages sent when automated recovery is not possible.

All of this monitoring is performed by the AdminiStor Plus Host, with the findings

forwarded to the AdminiStor Plus Server. The AdminiStor Plus Server is then

responsible for notifying the user in the appropriate manner. When an

AdminiStor GUI is displaying the status of the system, each storage component is

shown with a green, yellow, or red status indicator LED, showing if the

component is OK, has a recoverable problem, or is down. This allows the

AdminiStor GUI user to easily find the trouble spots in the storage system, and

drill down to the problem.

Notification

Problems and events within the storage systems are reported to any AdminiStor

GUI that has logged in to a domain containing that storage. An event log is

available, including historical events. This allows the AdminiStor GUI user to

easily see any global issues, such as loss of power in a section of the system, as

well as sequences of events which led up to a more serious problem.

Since problems with individual storage subsystems are normally rare, most of the

time there will not be any AdminiStor GUI observing the storage. AdminiStor Plus

can be configured to send events to the system error log, via Email to any valid

Email address, and via SNMP to other management systems. The events can be

selected such that only ones with the level of severity desired are sent out. Thus,

an Email enabled pager might receive all events, or just events indicating serious

problems. This is configured dynamically in the AdminiStor GUI, by those with

AdminiStor System <Administrator> access privileges. Refer to “E-mail

Preferences” on page 78 for detailed information and setup procedures.

Monitoring 7


8


DataBase

AdminiStor Plus keeps a record of all events, along with the status of all storage

components, in a relational database. This is a Java Data Base Connectivity

(JDBC) compliant database, embedded as part of AdminiStor Plus.

The data stored here allows easy access to information about the operational

history of the storage system, as well as current details about each part.

AdminiStor Plus uses this to provide information to the AdminiStor GUI and

notification facility. The historical information kept here survives operating

system restarts, keeping that information available across any system disturbance.

The database is also where the AdminiStor Plus Server coordinates the

information coming in from the various AdminiStor Plus Hosts. This is the

method that lets AdminiStor Plus report on the actual storage elements, rather

than what might appear as multiple shared resources seen by various operating

systems.

Security and Encryption

The integrity and security of data communications between AdminiStor

components is ensured through the use of public key encryption techniques. In

order to avoid any issues with exporting to other countries, the data stream is not

encrypted, but a digital signature is exchanged. It is this digital signature that uses

public key encryption and since it is part of the standard Java distribution, there

are no export issues.

This means that it is possible to see all the data passing between AdminiStor

components (Server and Host), but it is not possible to change, add, or remove

any of that data. This prevents outside code from being able to join in to an

AdminiStor group.

Since the data is transmitted in the clear, AdminiStor uses a means to transmit

passwords in a manner in which they can not be intercepted and repeated from

another session. AdminiStor uses a public key encryption to create a digital

signature of any password, and verify on the basis of digital signature matching.

This key is unique for each GUI session, so a captured signature is not valid on

any other session, and therefore cannot be inserted into the data to gain access.

Only the signature is sent over the network, never the password itself.

DataBase



However, there is one area of vulnerability. When you create new passwords or

change an old password, the actual password must be sent to the AdminiStor

Server. It is required at the AdminiStor Server so the digital signature can be

generated for each GUI session. During this time any creation of passwords on

the GUI is open to possible capture.

Therefore, it is strongly recommended that new or changed passwords

operations be entered at the local host system GUI running on the same

computer as the AdminiStor Server. Using this method prevents the password

from being transmitted over the network. If the LAN connected to the AdminiStor

Server is considered secure, then a GUI on that LAN may be used. Any other

method is not considered secure and is a high risk.

SNMP Services

AdminiStor can be configured to send SNMP traps to any network management

system. These traps carry all the information that appears in the AdminiStor log

entries for all monitored storage device.

All SNMP traps will be sent from the AdminiStor Server, even if the event

originates in a storage system attached to an AdminiStor Host elsewhere.

Therefore, all of the host names and/or IP addresses given in the list of SNMP

managers are interpreted from the point of view of the AdminiStor Server system.

Refer to “SNMP Preferences” on page 81 for detailed information and setup

procedures.

SNMP Services 9


10


SNMP Services

Chapter 2


Installation

Setup Overview

The process of installing, setting up, and configuring AdminiStor can be

described for a small scale storage environment or a complex networked storage

environment. Establishing a deployment plan will ensure a smooth setup process.

If you are installing AdminiStor RCU, configuration software for imageRAID

Controllers, follow the normal and specially marked procedures labeled

“AdminiStor RCU Only” installations. You may disregard the procedures marked

“AdminiStor Plus Only.”

If you are installing the complete package, AdminiStor Plus, you must have a

license key and a serial number. This license key and serial number are included

with the AdminiStor Plus package.

11

Chapter 2 - Installation

12


Installations for Microsoft Windows NT/Windows 2000

This section is applicable to installation on Microsoft Windows-based systems.

System Requirements

Before You Install AdminiStor on a Windows System

Before beginning the installation of AdminiStor on your server, you should first

ensure the following have been completed:

1 Install and set up the imageRAID SCSI Series Storage Systems. (Refer to the

specific user’s guides that accompanied the storage system.)

2 Install and/or set up Microsoft Windows NT/2000 software. (Refer to your

Microsoft Windows documentation.)

Setup

You should now be ready to begin the software installation.

1 Insert the Software/Documentation Disc into your CD-ROM drive.

The autorun program will automatically start the navigation menu, click on

the Software button.

2 Click the AdminiStor button and choose Install.

An InstallShield Wizard screen will appear and extract the necessary files.

You can stop the installation by clicking the Cancel button.

Group Requirement

Hardware:

Software:

Intel Pentium-based (400 MHz) system or higher, or equivalent128 MB RAM200 MB of free disk space for software installationVideo support for 256 colors (8-bit)CD-ROM DriveimageRAID SCSI Series Storage Systems.

Microsoft Windows NT v4.0 [Build 1381] with Service Pack 3 or later

orMicrosoft Windows 2000 (Build 2195) or later

Web Browser: Netscape Communicator (Navigator) ver. 4.6 or later or Microsoft Internet Explorer ver 5.0 or later

Installations for Microsoft Windows NT/Windows 2000



Package Extraction Screen

Once the file extraction is complete, InstallShield will automatically start the

setup program. A welcome screen will appear. You will be prompted to

continue the installation or cancel. Select Next to continue.

AdminiStor Setup Welcome Screen

3 You will be presented with the AdminiStor License Agreement screen. Read

the license agreement and if you agree to the terms and conditions click Yes.

You must accept this agreement to install the software.

Setup 13


14


License Agreement Screen

If you choose No, the setup program will quit.

4 You are now presented with the AdminiStor Installation Package selection

screen. Click the radio button next to the package you will be installing and

then click Next.

Package Selection Screen

NOTE: Choosing AdminiStor Plus Installation Package requires a serial

number and license key.

5 (AdminiStor RCU Only) You will now be prompted for an administrator

password for user access to allow configuration and management of the disk

arrays. Enter the desired password and click the Next button.

Setup



Skip now to step 11 to complete the AdminiStor RCU installation.

6 (AdminiStor Plus Only) Setup will now prompt you to enter customer

information and the software serial number.

Customer Information Screen

Enter the user name, company name (if applicable) and the software serial

number. You must enter a correct serial number before the Next button will

become active. After you have completed the fields click the Next button.

7 (AdminiStor Plus Only) Enter the software license key and click the Next

button.

Installation Key Screen

8 (AdminiStor Plus Only) Select the AdminiStor Plus package you will be

installing and click the Next button.

Setup 15


16


Choose the “Server” selection if this host computer system is to be the

AdminiStor Plus Server, otherwise, choose “Host.” Refer to “AdminiStor Plus

Modules” on page 4 for more details on the Host and Server modules.

AdminiStor Plus Package Screen

9 (AdminiStor Plus Host Only) If you selected Host, setup will now prompt you

to enter the AdminiStor Server IP Address or domain name. Enter the IP

Address or name, and click the Next button.

Host IP Address Screen

10 (AdminiStor Plus Only) If you selected Server or Host, you will be prompted

to enter passwords for each of the Access levels. Enter a password for each

Access level and click the Next button.

Setup



Access Level Password Screen

You must enter a password for each Access level. If a field is left blank an

information message box will appear indicating you must complete all fields.

It is recommended that a different password be used for each Access level.

NOTE: These passwords are internal to the AdminiStor software and may or

may not be the same as user passwords.

11 (AdminiStor Plus Only) If you selected Server or Host, you will be prompted

to enter the System Administrator login and password information which is

used by AdminiStor. This login allows the user to make changes to e-mail,

SNMP, and System preferences.

It is recommended to use a different user name and password than that

which is used for the operating system administrator. Complete the fields and

click the Next button.

System Information Screen

Setup 17


18


NOTE: It is advisable to make a record of all these user names, passwords,

and Access level passwords.

12 Next you will choose the destination location where the software is installed.

The default location is “Program Files” and “admstr” folders on your local

hard disk. If you elect to use the default path, click the Next button. If you

wish to use a different drive or directory, click the Browse button and enter

your desired directories.

Destination Location Screen

13 You are now prompted to indicate the name of the Program folder where the

software will reside.

The default location is “AdminiStor.” If you elect to use the default choice,

click the Next button. If you wish to use a different folder, enter your desired

name.

Program Folder Name Screen

Setup



Setup will now begin installing the software components. Once the

installation is complete, you are presented with the following screen.

Click the close button on this screen and the InstallShield Wizard Complete

screen will appear.

InstallShield Wizard Complete Screen

14 Select “Yes” to restart your computer and click the Finish the button.

If you choose “No” you will receive a message window that reminds you to

reboot your system. This system reboot is necessary for the settings to take

effect.

The software installation is now complete. To start the software refer to “Starting

AdminiStor” on page 50.

NOTE: At the first start of the software within the browser a check will be

performed to determine if the appropriate Java Plug-In component is

installed. If the correct version is not available you will be directed to

install the correct plug-in. The software plug-in installer was copied to

the local directory during the installation, and the software plug-in

installer will be started from the local drive. You will not be required to

access the internet to obtain the appropriate Java Plug-In component.

Setup 19


20


Removing AdminiStor (Windows)

To uninstall the AdminiStor software:

1 From the Windows host computer where the software is installed, click the

Start button and choose Control Panels. Double-click Add/Remove Programs

and select the AdminiStor program. Click the Remove button.

InstallShield will open the following dialog window.

2 Select the Remove radio button and click the Next button.

InstallShield Wizard Remove Software Screen

3 InstallShield will prompt you to confirm removal of the software component.

Click the OK button.

The software will be removed.

NOTE: Windows Services will automatically be stopped and removed during this

uninstall process.

Removing AdminiStor (Windows)



Installations for Solaris

This section is applicable to installation on Solaris-based systems.

System Requirements

Before You Install AdminiStor on a Solaris System


ensure the following has been completed:

� Install and setup the imageRAID SCSI Series Storage Systems. (Refer to the

specific user’s guides that accompanied the storage system.)

Group Requirement

Hardware:

Software:

Sun Microsystems SPARC-based Workstations and Enterprise systems running Solaris 5.6 through 5.8/Solaris 2.6 through 8128 MB RAM (minimum)160 MB of free disk space for software installationVideo support for 256 colors (8-bit)CD-ROM DriveimageRAID SCSI Series Storage Systems.

Solaris 5.6 through 5.8/Solaris 2.6 through 8

Web Browser: Netscape Communicator (Navigator) ver. 4.6 or later

Installations for Solaris 21


22


Solaris Installation

You should now be ready to begin the software installation. To install the AdminiStor software use the “pkgadd” command.

NOTE: The default installation directory is /opt/AdminiStor/. The Application Package name is “NSOadmstr.”

1 Login as “root” and insert the Software/Documentation Disc into the CD-ROM drive.

2 From the command prompt type the following (case sensitive),

pkgadd -d [CDROM mount point path]/software/administor/

sun/admsun.pkg and press <Enter>.

NOTE: To view a list of the CD mount point paths, type df -k and press

<Enter>.

3 Press <Enter> to select AdminiStor 6.2.1 package (“NSOadmstr”).

4 Read the License Agreement and if you agree, type “yes” or “y”.

Do you agree to the above license terms? [yes or no]

5 Type the Company Name or press <Enter> to skip.

Please enter company name

Company Name: [no default]

6 Select which package of AdminiStor you would like to install.

Please select the product to install:

1. AdminiStor Plus

2. AdminiStor RCU

3. Exit

Enter choice [ ]:

NOTE: If you enter option #1, proceed to step 7, otherwise if you choose

option #2 proceed to step 8.

Please enter the product Serial Number: [no default]

7 (AdminiStor Plus Only) Type the serial number and press <Enter>. Skip to

step 9.

8 (AdminiStor RCU Only) Enter the password.

Please enter the password for user access

Password: [ ]

Type the password and press <Enter>. Skip to step 14.




9 (AdminiStor Plus Only) Type the key number and press <Enter>.

Please enter the Key Number

Installation Key: [ ]

If the key is incorrect, you will be asked to choose the AdminiStor version

again, step 6.

10 If the key is correct, you will be prompted to select the setup type.

Select Type:

1. Server

2. Host

Choose the setup type that best suits your

needs. Select <Server> for AdminiStor

installation if this is for the only or

primary AdminiStor installation. Select

<Host> if this system is attached to storage

and will report to another system with the

<Server> component installed.

Enter choice [1]:

If you typed “1” or just pressed <Enter>, proceed to step 12.

11 If you selected “Host”, you will be asked to enter the IP Address or domain

name of the AdminiStor Server.

Please enter the IP address or the domain name of the

AdminiStor Server.

Sample: "192.197.13.56" or "myhost"

Enter the IP Address and press <Enter>.

12 Establish passwords for different Access levels to storage devices.

Establish the password to have the access to storage

devices that belong to the physical domain on the current

system.

It is recommended to have different passwords for each

access level. These passwords are internal to AdminiStor

and may be the same or different than the actual user

passwords already on the system.

Please enter the passwords for each level of user access.

View: [no default]

Solaris Installation 23


24


Type the password and press <Enter>.

Operate: [no default]


Admin: [no default]


13 Establish the System Administrator information.

Please enter the System Administrator information for use

by Administor 6.2.1

It is recommended to have a different System Administrator User Name and password then the current existing administrator account.

User Name: [admin]

Type the User Name or press <Enter>, in this case the User Name will be

“admin.”

Password: [no default]


Description: [no default]

Type the description and press <Enter> or press <Enter> to skip.

14 Allow package add scripts to be executed.

Do you want this directory created now [y, n, ?]

Type “yes” or “y” and press <Enter>.

This package contains scripts which will be executed with

super-user permission during the process of installing this

package.

Do you want to continue with the installation of <NSOadmst>

[y, n, ?]

Type “yes” or “y”. The installation will proceed and when complete,

AdminiStor starts automatically.

The software installation is now complete.




Removing AdminiStor (Solaris)

To remove the AdminiStor software:

1 Login with “superuser” rights.

2 From the command prompt type the following:

pkgrm NSOadmstr and press <Enter>.

3 You are prompted to confirm the removal of this product, enter “Yes” and

press <Enter>.

4 You will be prompted again to confirm continuing the removal of the

software package, enter “Yes” and press <Enter>.

Removing AdminiStor (Solaris) 25


26


Installations for Linux (Red Hat v6.2, v7.1, and v7.2)

This section is applicable to installation on Red Hat Linux-based systems.

CAUTION: These installation procedures require a Linux knowledge level of a

system administrator.

System Requirements

Before You Install AdminiStor on a Red Hat Linux System


ensure the you have installed and setup the imageRAID SCSI Series Storage

Systems. (Refer to the specific user’s guides that accompanied the storage

system.)

For Red Hat Linux v6.2, see “Red Hat Linux Version 6.2” on page 27.



Group Requirement

Hardware:

Software:

Intel Pentium-based (400 MHz) system or higher, or equivalent

128 MB RAM (minimum)160 MB of free disk space for software installationVideo support for 256 colors (8-bit)CD-ROM DriveimageRAID SCSI Series Storage Systems.

Red Hat Linux 6.2, Red Hat Linux 7.1, or Red Hat Linux 7.2

Web Browser: Netscape Communicator (Navigator) ver. 4.6 or later

Installations for Linux (Red Hat v6.2, v7.1, and v7.2)



Red Hat Linux Version 6.2

Complete the described procedures for Red Hat Linux version 6.2, then complete

the procedure for installing AdminiStor, see “AdminiStor Installation On Red Hat

Linux” on page 44

Recompile the Kernel for Red Hat Linux v 6.2

This process will update the kernel:

1 Insert the CD-ROM Red Hat 6.2 into the CD-ROM drive. If necessary, mount

the CD-ROM. Type: mount /dev/cdrom /mnt/cdrom and press <Enter>.

2 Open a terminal window and issue the following commands:

cd /mnt/cdrom/RedHat/RPMS

rpm -iv --force dev86-0.15.0-2.i386.rpm

rpm -iv --force cpp-1.1.2-30.i386.rpm

rpm -iv --force egcs-1.1.2-30.i386.rpm

rpm -iv --force glibc-devel-2.1.3-15.i386.rpm

rpm -iv --force kernel-headers-2.2.14-5.0.i386.rpm

rpm -iv --force kernel-source-2.2.14-5.0.i386.rpm

rpm -iv --force make-3.78.1-4.i386.rpm

rpm -iv --force ncurses-5.0-11.i386.rpm

rpm -iv --force ncurses-devel-5.0-11.i386.rpm

3 Compile the kernel, issue the following commands:

cd /usr/src/linuxmake mrpropercp -p configs/kernel-2.2.14-i686.config arch/i386/defconfig

Answer yes to overwrite if necessary.

make oldconfigmake xconfig

4 Click on the SCSI Support button.

5 Select “Y” on SCSI Support.

6 Select “Y” on Probe All Luns On Each Scsi Device.

7 Click the Main Menu button.

8 Click Save and Exit, and click OK.

9 Issue the following commands:

pico Makefile, edit line 4 EXTRAVERSION = -5.0nstor

Red Hat Linux Version 6.2 27


28


10 Compile and install, issue the following commands:

make depmake bzImage

make modulescp /usr/src/linux/arch/i386/boot/bzImage /boot/vmlinuz-2.2.14-5.0nstor

make modules_install

11 Post install, issue the following commands:mkinitrd /boot/initrd-2.2.14-5.0nstor.img 2.2.14-5.0nstorcp /usr/src/linux/System.map /boot/System.map-2.2.14-5.0nstorcp /usr/src/linux/.config /boot/config-2.2.14-5.0nstor

12 Use a text editor to make changes to the /etc/lilo.conf file and save the

changes (e.g., pico /etc/lilo.conf):

Add/change the following line from:boot=/dev/hdamap=/boot/mapinstall=/boot/boot.bprompttimeout=50lineardefault=linuximage=/boot/vmlinuz-2.2.14-5.0label=linuxinitrd=/boot/initrd-2.2.14-5.0.imgread-onlyroot=/dev/hd5

to:boot=/dev/hdamap=/boot/mapinstall=/boot/boot.bprompttimeout=50lineardefault=nstorimage=/boot/vmlinuz-2.2.14-5.0label=linuxinitrd=/boot/initrd-2.2.14-5.0.imgread-onlyroot=/dev/hd5

image=/boot/vmlinuz-2.2.14-5.0nstorlabel=nstorinitrd=/boot/initrd-2.2.14-5.0nstor.imgread-onlyroot=/dev/hd5

13 Issue the following command:

/sbin/lilo and press <Enter>.

14 Shut down your system: Type shutdown -r now and press <Enter>.

Recompile the Kernel for Red Hat Linux v 6.2



Installing the FC HBA on Red Hat Linux v 6.2

1 Login as “root” and insert the AdminiStor CD-ROM into the CD-ROM drive. If necessary to mount the CD-ROM drive, type: mount /dev/cdrom /mnt/cdrom and press <Enter>.

2 Copy the driver module. Type:

cp /mnt/cdrom/redhat/qla2x0062.o

/lib/modules/2.2.14-5.0nstor/scsi and press <Enter>.

3 Rename the old QLogic driver, type mv /lib/modules/2.2.14-5.0nstor/scsi/qlogicfc.o/lib/modules/2.2.14-5.0nstor/scsi/qlogicfc.sav and press <Enter>.

4 Use a text editor to make changes to the /etc/conf.modules file and save the

changes (pico /etc/conf.modules):

Change the following line from:

alias scsi_hostadapter qlogicfc

to

alias scsi_hostadapter qla2x0062

5 Issue the following command to create a new boot image.

/sbin/mkinitrd /boot/newinitrd-admstr.img 2.2.14-5.0nstor

and press <Enter>.

6 Use a text editor to make changes to the /etc/lilo.conf file and save the

changes (pico /etc/lilo.conf):

Add/change the following lines from:

boot=/dev/hdamap=/boot/mapinstall=/boot/boot.bprompttimeout=50lineardefault=linuximage=/boot/vmlinuz-2.2.14-5.0label=linuxinitrd=/boot/initrd-2.2.14-5.0.imgread-onlyroot=/dev/hd5image=/boot/vmlinuz-2.2.14-5.0nstorlabel=nstorinitrd=/boot/initrd-2.2.14-5.0nstor.imgread-onlyroot=/dev/hd5

Installing the FC HBA on Red Hat Linux v 6.2 29


30


to:

boot=/dev/hdamap=/boot/mapinstall=/boot/boot.bprompttimeout=50lineardefault=admstrimage=/boot/vmlinuz-2.2.14-5.0label=linuxinitrd=/boot/initrd-2.2.14-5.0.imgread-onlyroot=/dev/hd5

image=/boot/vmlinuz-2.2.14-5.0nstorlabel=nstorinitrd=/boot/initrd-2.2.14-5.0nstor.imgread-onlyroot=/dev/hd5

image=/boot/vmlinuz-2.2.14-5.0nstorlabel=admstrinitrd=/boot/newinitrd-admstr.imgread-onlyappend=”max_scsi_luns=128”root=/dev/hd5




9 Verify boot of the “HBA” driver by issuing the following command:

Type lsmod and press <Enter>.

Installing the FC HBA on Red Hat Linux v 6.2




Complete the described procedures for version 7.1, then complete the procedure for

installing AdminiStor, see “AdminiStor Installation On Red Hat Linux” on page 44

Upgrading the Kernel for Red Hat Linux v7.1

This process will update the kernel:

1 Insert the CD-ROM Red Hat 7.1 Disc #1 into the CD-ROM drive. If necessary,

mount the CD-ROM. Type: mount /dev/cdrom /mnt/cdrom and press

<Enter>.

2 Type: cd /mnt/cdrom/RedHat/RPMS and press <Enter>.

3 Type: rpm -Uv kernel-headers-*.rpm and press <Enter>.

4 Type: cd / and press <Enter>.

5 Unmount the CD-ROM. Type: umount /mnt/cdrom and press <Enter>.

6 Eject the CD-ROM. Type: eject and press <Enter>.

7 Once complete, unmount and remove the CD-ROM Red Hat 7.1 Disc #1.

8 Insert the CD-ROM Red Hat 7.1 Disc #2 into the CD-ROM drive. If necessary,

mount the CD-ROM. Type: mount /dev/cdrom /mnt/cdrom and press

<Enter>.

9 Type: cd /mnt/cdrom/RedHat/RPMS and press <Enter>.

10 Type: rpm -Uv kernel-source-*.rpm and press <Enter>.

11 Type: cd / and press <Enter>.

12 Unmount the CD-ROM. Type: umount /mnt/cdrom and press <Enter>.

13 Eject the CD-ROM. Type: eject and press <Enter>.

14 Reboot the system. Type shutdown -r now and press <Enter>

Installing the FC HBA on Red Hat Linux v7.1

1 Insert the AdminiStor CD-ROM into the CD-ROM drive. If necessary, mount

the CD-ROM. Type: mount /dev/cdrom /mnt/cdrom and press <Enter>



32


2 Create a folder, example “install” by typing:

mkdir /install and press <Enter>.

3 Type cd /install and press <Enter>.

4 Type: cp /mnt/cdrom/software/administor/redhat/qla2x00src-v5.36.tgz

/install and press <Enter>.

5 Issue the following command, type: tar -xvzf *.tgz and press <Enter>.

6 Issue the following command, type: make OSVER=linux-2.4 and press

<Enter>.

7 Issue the following command, type: rmmod qla2x00 and press <Enter>.

8 Issue the following command, type: cp /install/qla2x00.o /lib/modules/2.4.2-2/kernel/drivers/scsi/qlanstor.o

and press <Enter>.

9 Issue the following command, type:

insmod /lib/modules/2.4.2-2/kernel/drivers/scsi/qlanstor.o and press

<Enter>.

10 Verify the changes with lsmod and press <Enter>.

11 Use an editor to make changes to the /etc/modules.conf file and save the

changes:

Add the following line:

alias scsi_hostadapter qlanstor

Comment out the following line if it exists:

#alias scsi_hostadapter qla2x00


/sbin/mkinitrd /boot/qlanstor 2.4.2-2 and press <Enter>.

13 Use an editor to make changes to the lilo.conf file and save the changes:

Add/change the following line from:boot=/dev/hdamap=/boot/mapinstall=/boot/boot.bprompttimeout=50lineardefault=linux

Installing the FC HBA on Red Hat Linux v7.1



image=/boot/vmlinuz-2.4.2-2label=linuxinitrd=/boot/initrd-2.4.2-2.imgread-onlyroot=/dev/hda5

to:boot=/dev/hdamap=/boot/mapinstall=/boot/boot.bprompttimeout=50lineardefault=qlanstorimage=/boot/vmlinuz-2.4.2-2label=linuxinitrd=/boot/initrd-2.4.2-2.imgread-onlyroot=/dev/hda5

image=/boot/vmlinuz-2.4.2-2label=qlanstorinitrd=/boot/qlanstorread-onlyappend=”max_scsi_luns=128”root=/dev/hda5




16 Verify boot of the “HBA” driver by issuing the following command: Type

lsmod and press <Enter>.

Installing the FC HBA on Red Hat Linux v7.1 33


34


Configure Red Hat Linux v7.1 for Multi-LUN Support

This process will enable you to see more than one LUN. Caution should be used

to ensure that the commands are type exactly as they appear.

1 Open a terminal window.

2 Change directories, type: cd /etc and press <Enter>.

3 Using an text editor, open the file “rc.sysinit” and make the following

changes. Scroll down and add the following BEFORE “Add raid devices.”

#!/bin/sh for H in 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 ; do for C in 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 ; do for I in 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 ; do for L in 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 ; do echo "scsi add-single-device $H $C $I $L" >/proc/scsi/scsi done for L in 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 ; do echo "scsi add-single-device $H $C $I $L" >/proc/scsi/scsi done done donedone

4 Exit and save the file.

5 Reboot your system. Type shutdown -r now and press <Enter>.

Configure Red Hat Linux v7.1 for Multi-LUN Support




Complete the described procedures for Red Hat Linux version 7.2, then complete

the procedure for installing AdminiStor, see “AdminiStor Installation On Red Hat

Linux” on page 44

NOTE: HBA’s must use either the QLogic driver v4.28 or higher, embedded in

Red Hat v7.2 operating system.

Perform the following:

1 Issue the following command, type: insmod qla2x00 and press <Enter>.

2 Use a text editor to make changes to the /etc/modules.conf file and save the

changes. Add the following line if it does not already exists:

alias scsi_hostadapter qla2x00

3 Verify the changes with Ismod and press <Enter>.

4 Issue the following command, type: uname -r and press <Enter>.

NOTE: You will use the results from this command in step 5.

5 Issue the following command, type /sbin/mkinitrd/boot/qlanstor.img

[results from step 4] and press <Enter>.

6 If you are using GRUB, skip to step 10.

7 Use a text editor to make changes to the lilo.conf file and save the changes.

(Lines indicated in “bold” text were changed or added.)

Add or change the following lines from:

boot=/dev/hda

map=/boot/map

install=/boot/boot.b

prompt

timeout=50

linear

default=linux

image=/boot/vmlinuz-2.4.7-10

label=linux

initrd=/boot/initrd-2.4.7-10.img

read-only

root=/dev/hda5



36


to:

boot=/dev/hda

map=/boot/map


prompt

timeout=50

linear

default=qlanstor


label=linux

initrd=/boot/initrd-2.4.7-10.img

read-only

root=/dev/hda5

image=/boot/vmlinuz-2.4.7-10label=qlanstorinitrd=/boot/qlanstor.imgread-onlyroot=/dev/hda5

8 Issue the following command, type /sbin/lilo and press <Enter>.

9 Skip to step 11. (Step 10 is for those using GRUB.)

10 Make a new boot image. Add the following lines using a text editor to the

/boot/grub/brub.conf file:

title Red Had Linux-nStor (2.4.7-10)

root (hd0,0)

kernel /vmlinuz-2.4.7-10 ro root=/dev/hda2

initrd /boot/qlanstor.img




Default /boot/grub/grub.conf file:

# grub.conf generated by anaconda

#

# Note that you do not need to re-run grub after making changes to this file

# NOTICE: You have a /boot partition. This means that

# all kernel and initrd paths are relative to /boot/, eg.

# root (hd0,0)

# kernel /vmlinuz-version ro root=/dev/hda2

# initrd /initrd-version.img

#boot=/dev/hda

default=0

timeout=10

splashimage=(hd0,0)/grub/splash.xpm.gz

title Red Hat Linux (2.4.7-10)

root (hd0,0)


initrd /initrd-2.4.7-10.img

The new modified /boot/grub/grub.conf file:


#

# Note that you do not need to re-run grub after making changes to this file

# NOTICE: You have a /boot partition. This means that

# all kernel and initrd paths are relative to /boot/, eg.

# root (hd0,0)



#boot=/dev/hda

default=0

timeout=10


title Red Had Linux-nStor (2.4.7-10)

root (hd0,0)





38



root (hd0,0)



11 Shut down your system, type shutdown -r now and press <Enter>.

12 Verify boot of the “HBA” driver by issuing the following command, type

lsmod and press <Enter>.

13 If your kernel has not been configured to support multiple LUNs, then you

will need to recompile the 2.4.7-10 kernel to scan for multiple LUNs under

each target ID. Refer to “Modularized Kernel for Red Hat Version 7.2” on

page 38, below.

Modularized Kernel for Red Hat Version 7.2

The following steps will guide you through building a custom kernel for the x86

architecture.

NOTE: This example uses kernel version 2.4.7-10. Your kernel might be

different. To determine the kernel version you have, type the command

uname -r and press <Enter>. If necessary replace 2.4.7-10 with your

kernel version.

1 You must have both the kernel-headers and kernel-source packages installed.

Issue the following command, type rpm -q kernel-headers and press

<Enter> and rpm -q kernel-source and press <Enter>.

This will determine the versions, if they are installed. If they are not installed,

you will need to install them from the Red Hat Linux CD 1 or the Red Hat

FTP site (ftp://ftp.redhat.com).

2 At the shell prompt, change to the directory from which all commands are to

be issued, type cd /usr/src/linux-2.4.7-10 and press <Enter>.

3 It is important that you begin a kernel build with the source tree in a known

condition. Therefore, it is recommended that you begin with the command,

make mrproper.

This will remove any configuration files along with the remains of any

previous builds that may be scattered around the source tree.




4 Red Hat supplies configuration templates appropriate for different processor

configurations. Copy the configuration template which is correct for your

hardware. For example, type cp -p configs/kernel-2.4.7-i686.config

arch/i386/defconfig and press <Enter>.

5 Create an initial “.config” file from which to start, type make oldconfig and

press <Enter>.

6 Customize the “.config” file, type make xconfig and press <Enter>.

This will bring up a window, from which you will click on “SCSI Support.”

7 Change “Probe all LUNs on each SCSI device” to Yes.

8 Click on “Main Menu.”

9 Click on “Save and Exit.”

10 Click on “OK,” if prompted.

11 Edit “/usr/src/linux-2.4.7-10/Makefile” and modify the line beginning with

EXTRAVERSION = to create a “unique” kernel version by appending the date

to the end of the string. For example, if you are compiling kernel version

2.4.7-10, you can append the flag to look similar to EXTRAVERSION =

-10-nstor). This will allow you to have the old working kernel and the new

kernel, version 2.4.7-10-nstor, on your system at the same time.

12 After modifying and saving the “/usr/src/linux-2.4.7-10/.config” file, set up all

of the dependencies by typing the command make dep and press <Enter>.

13 Compile the new kernel by typing the command make bzImage and press

<Enter>.

14 Compile the kernel modules by typing the command make modules and

press <Enter>.

15 Install the new kernel to the /boot directory by typing the command cp /usr/src/linux-2.4.7-10/arch/i386/boot/bzImage

/boot/vmlinuz-2.4.7-10-nstor and press <Enter>.

16 Install the new kernel modules (even if you didn’t build one) by typing the

command make modules_install and press <Enter>.

Make sure that you enter the underscore (_). This will install the kernel

modules into the directory path /lib/modules/ using the path name that was

specified in the Makefile. Our example would be /lib/modules/2.4.7-10-nstor/.

Modularized Kernel for Red Hat Version 7.2 39


40


17 If you have a SCSI adapter and you made your SCSI driver modular, you will

need to build a new initial ramdisk image by typing the command mkinitrd

/boot/qlanstor-multilun.img 2.4.7-10-nstor and press <Enter>.

NOTE: There are few practical reasons to make the SCSI driver modular in a

custom kernel.

18 Save a copy of the symbol table to the new kernel by typing the command cp /usr/src/linux-2.4.7-10/System.map /boot/System.map-2.4.7-10-nstor

and press <Enter>.

19 Keep a copy of the configuration file used to create the new kernel by typing

the command cp /usr/src/linux-2.4.7-10/.config /boot/config-2.4.7-10-nstor

and press <Enter>.

20 In order to provide a redundant boot source which protects from a possible

error in a new kernel, you should keep the original kernel available.

Depending on which loader you are using, this can be accomplished by

either updating the /boot/grub/grub.conf file or the /etc/lilo.conf file.

21 If you are using GRUB, skip to step 27.

22 Use a text editor to add your new kernel to LILO. Copy the following lines to

the new one and modify it to boot your new kernel image (and initrd image

if you have any SCSI devices and created an initrd image). Also, rename the

label of the old kernel to something such as “linux-old.”

Default /etc/lilo.conf file:

boot=/dev/had

map=/boot/map


prompt

timeout=50

linear

default=qlanstor


label=linux

initrd=initrd-2.4.7-10.img

read-only

root=/dev/hda5





label=qlanstor

initrd=/boot/qlanstor.img

read-only

root=/dev/hda5

The new modified /etc/lilo.conf file (the modified lines appear in bold):

boot=/dev/had

map=/boot/map


prompt

timeout=50

linear

default=qlanstor-multilun


label=linux

initrd=initrd-2.4.7-10.img

read-only

root=/dev/hda5


label=qlanstor

initrd=/boot/qlanstor.img

read-only

root=/dev/hda5

image=/boot/vmlinuz-2.4.7-10-nstorlabel=qlanstor-multiluninitrd=/boot/qlanstor-multilun.imgread-onlyroot=/dev/hda5

23 To activate your changes in the /etc/lilo.conf file, by typing the command




42


If all goes well, you will see output similar to the following:

Added qlanstor-multilun *

Added qlanstor

Added linux

24 The “*” after qlanstor-multilun means that the section labeled

qlanstor-multilun is the default kernel that LILO will boot.

From now on, when the system boots you will see linux, qlanstor and

qlanstor-multilun as LILO boot options.

25 To boot the new kernel (qlanstor-multilun) simply press <Enter>, or wait for

LILO to time out. If you want to boot the old kernel (qlanstor or linux),

choose qlanstor or linux and press <Enter>.

26 Skip to step 30. (Steps 27-29 are for those using GRUB.)

27 Use a text editor to add your new kernel to GRUB. Copy the following lines

to the new one and modify it to boot your new kernel image (and initrd

image if you have any SCSI devices and created an initrd image). Also,

rename the label of the old kernel to something such as “linux-old.”

Default /boot/grub/grub.conf file:


#

# Note that you do not have to rerun grub after making changes to this file

# NOTICE: You have a /boot partition. This means that# all kernel and initrd paths are relative to /boot/, eg.

# root (hd0,0)



#boot=/dev/hda

default=0

timeout=10


title Red Hat Linux-nStor (2.4.7-10)

root (hd0,0)




root (hd0,0)






The new modified /boot/grub/grub.conf (the modified lines appear in bold):


#

# Note that you do not have to rerun grub after making changes to this file

# NOTICE: You have a /boot partition. This means that# all kernel and initrd paths are relative to /boot/, eg.

# root (hd0,0)



#boot=/dev/hda

default=0

timeout=10


title Red Hat Linux-nStor-multi-lun(2.4.7-10)root (hd0,0)kernel /vmlinuz-2.4.7-10-nstor ro root=/dev/hda2initrd /boot/qlanstor-multilun.img

title Red Hat Linux-nStor (2.4.7-10)

root (hd0,0)




root (hd0,0)



28 From now on, when the system boots you will see Red Hat Linux-nStor-multi-lun, Red Hat Linux-nStor and Red Hat Linux as GRUB boot options.

29 To boot the new kernel (Red Hat Linux-nStor-multi-lun) simply press

<Enter>, or wait for GRUB to time out. If you want to boot the old kernels,

choose one and press <Enter>.

30 You can begin testing your new kernel by rebooting your computer and

watching the messages to ensure your hardware is detected properly.



44


AdminiStor Installation On Red Hat Linux

You should now be ready to begin the software installation. To install the AdminiStor software use the “rpm” command.

NOTE: The default installation directory is /opt/AdminiStor/. The Application Package name is “admlinux-6.2.1-p.”

1 Login as “root” and insert the nStor Software/Documentation Disc into the CD-ROM drive. If necessary, mount the CD-ROM. Type: mount /dev/cdrom /mnt/cdrom and press <Enter>

2 From the command prompt type the following (case sensitive),

rpm -iv --nodeps --force /mnt/cdrom/software/administor/

redhat/admlinux.rpm and press <Enter>.

3 Read the License Agreement and if you agree, type “yes” or “y”.

Do you agree to the above license terms? [yes or no]

4 Type the Company Name or press <Enter> to skip.

Please enter company name

Company Name: [no default]

5 Select which package of AdminiStor you would like to install.

Please select the product to install:

1. AdminiStor Plus

2. AdminiStor RCU

3. Exit

Enter choice [ ]:

NOTE: If you enter option #1, proceed to step 6, otherwise if you choose

option #2 proceed to step 7.

Please enter the product Serial Number: [no default]

6 (AdminiStor Plus Only) Type the serial number and press <Enter>. Skip to

step 8.

7 (AdminiStor RCU Only) Enter the password.

Please enter the password for user access

Password: [ ]

Type the password and press <Enter>. Skip to step 13.

AdminiStor Installation On Red Hat Linux



8 (AdminiStor Plus Only) Type the key number and press <Enter>.

Please enter the Key Number

Installation Key: [ ]

If the key is incorrect, you will be asked to choose the AdminiStor version

again, step 6.

9 If the key is correct, you will be prompted to select the setup type.

Select Type:

1. Server

2. Host

Choose the setup type that best suits your

needs. Select <Server> for AdminiStor

installation if this is for the only or

primary AdminiStor installation. Select

<Host> if this system is attached to storage

and will report to another system with the

<Server> component installed.

Enter choice [1]:

If you typed “1” or just pressed <Enter>, proceed to step 11.

10 If you selected “Host”, you will be asked to enter the IP Address or domain

name of the AdminiStor Server.

Please enter the IP address or the domain name of the

AdminiStor Server.

Sample: "192.197.13.56" or "myhost"

Enter the IP Address and press <Enter>.

11 Establish passwords for different Access levels to storage devices.

Establish the password to have the access to storage

devices that belong to the physical domain on the current

system.

It is recommended to have different passwords for each

access level. These passwords are internal to AdminiStor

and may be the same or different than the actual user

passwords already on the system.

AdminiStor Installation On Red Hat Linux 45


46


Please enter the passwords for each level of user access.

View: [no default]


Operate: [no default]


Admin: [no default]


12 Establish the System Administrator information.

Please enter the System Administrator information for use

by Administor 6.2.1

It is recommended to have a different System Administrator User Name and password then the current existing administrator account.

User Name: [admin]

Type the User Name or press <Enter>, in this case the User Name will be

“admin.”

Password: [no default]


Description: [no default]

Type the description and press <Enter> or press <Enter> to skip.

13 Allow installation scripts to be executed.

The AdminiStor software installation is now complete.

Installation of Java on Red Hat Linux

After you complete the installation and the first time you run AdminiStor, it will

prompt you to down load the latest Java plug-in.

1 Start the AdminiStor software, open a terminal window and type

cd /opt/AdminiStor/bin.

2 Issue the following command, type: ./StartAdminiStor and press <Enter>.

3 Open a browser window.

Installation of Java on Red Hat Linux



4 Enter the following URL: http://localhost:9191 and press <Enter>.

5 If the appropriate Java Plug-In file does not exists, you will be prompted to

download the Java Plug-In for Linux.

Download the Linux Java file (j2re-1.3.1_01-linux-*.bin) to the /root directory.

Note the filename that is downloaded for later use in Step 9.

NOTE: RedHat v7.2 users must download the Java Plug-in v1.4 Beta from

Sun Microsystem's website: http://java.sun.com/j2se/1.4/jre/.

6 At a console, change the working directory to /root. Type: cd /root and

press <Enter>.

7 Issue the following command, type: chmod +x * and press <Enter>.

8 Issue the following command, type: ls -l j2re-1_3_1_01-linux-* and

press <Enter>.

9 Using the filename in Step 8, Issue the following command, type:

./j2re-1_3_1_01-linux-*.bin and press <Enter>.

10 Press the <Space Bar> to go to the end of the License and select Yes to agree

to the above terms of the software agreement.

11 Issue the following command, type: export NPX_PLUGIN_PATH=/root/

jre1.3.1_01/plugin/i386/ns4 and press <Enter>.

12 Issue the following command, type: netscape & and press <Enter>.

13 In the browser window, enter in the URL location: http://localhost:

9191/administor/index.html.

Removing AdminiStor (Linux)

To remove the AdminiStor software:

1 Login with “superuser” rights.

2 From the command prompt type the following:

rpm -e admlinux-6.2.1-p and press <Enter>.

3 You are prompted to confirm the removal of this product, enter “Yes” and

press <Enter>.

4 You will be prompted again to confirm continuing the removal of the

software package, enter “Yes” and press <Enter>.

Removing AdminiStor (Linux) 47


48


Removing AdminiStor (Linux)

Chapter 3


Startup & Navigation

AdminiStor Component Overview

AdminiStor Plus Server Module

The AdminiStor Plus Server module runs on a host server where the imageRAID

SCSI Series Storage Systems may or may not be attached, and performs the

following functions:

� Monitors imageRAID SCSI Series Storage Systems.

� Manages the controller(s) and associated disk in the imageRAID SCSI Series

Storage Systems.

� Sends information to and receives request from the AdminiStor GUI

component.

� Communicates with the AdminiStor Plus Host component for control and

management.

AdminiStor Plus Host Module

The AdminiStor Plus Host module interfaces with the AdminiStor Plus Server

component for management and control of their attached storage. One or more

of these components may be installed into the environment.

49

Chapter 3 - Startup & Navigation

50


AdminiStor GUI

The AdminiStor GUI provides the user interface from which control and monitoring

of nStor storage systems are maintained. The AdminiStor GUI requires no

installation with the exception of the correct browser Java plug-in. It is accessed by

launching your web browser and entering the correct IP Address or preferably the

name defined for that AdminiStor Server followed by the port number “9191.”

Starting AdminiStor

Starting AdminiStor Plus Server and AdminiStor Plus Host

During the installation process the Service (Windows) or Daemon (Solaris) is

automatically turned on. It therefore does not require manual interaction,

however, should the need arise to manually turn on these components, do the

following:

Windows NT

Click on Start then select Control Panel and select Services and locate and

select the service “AdminiStor,” then click “Start.” This action will start the

Windows NT Service.

Windows 2000

Click on Start then select Programs and select Administrative Tools followed

by Services and locate and select the service “AdminiStor,” then click on

Action and select “Start.” This action will start the Windows 2000 Service.

Solaris

Type the following commands:

/etc/init.d/AdminiStor start and press <Enter>.

Red Hat Linux


/cd/opt/AdminiStor/bin and press <Enter>.

./StartAdminiStor and press <Enter>.

AdminiStor GUI



Starting AdminiStor GUI

To start the AdminiStor GUI:

1 From your local system or from a system attached to the same network

(internet or intranet), start your web browser.

2 In the URL Address box enter the appropriate IP Address or Name for the

AdminiStor Server (ADM Server) followed by “:9191” and press the Enter

button. (If the storage system is directly attached to your system, you may

use “http://localhost:9191.”)

The “Name” is the name established during initial setup of the host computer

system. (e.g., on Windows NT system the name is found by selecting the

Control Panel and choosing Network.) The AdminiStor main screen is displayed.

Starting the AdminiStor GUI

You will see the message that the GUI is contacting the AdminiStor Server.

Once the connection is made you will see the message “Session with

AdminiStor established.”

The first time you start the AdminiStor applet you will see a screen which

prompts you to register the java applet. Select the option to “Grant Always.”

Starting AdminiStor GUI 51


52


Starting the AdminiStor GUI

Refer to “Signing On to a Domain” on page 52 and “Domains Menu” on

page 56 for information about logging into and establishing access privileges

for a selected Domain.

Signing On to a Domain

Access Levels

Accessing a domain is based on the same procedure as logging into the system

and will require a password. The passwords are established during the installation.

There are three levels of access control, <Viewer>, <Operator>, and

<Administrator>.

Viewer

Viewer access allows the user to see the device configuration tree, information

about the devices, see the current status of any of the devices managed, view

events from each domain you are logged into, retrieve the history of events on

any logged in domain, and view the on-line help.

Operator

An Operator access has all the same privileges of <Viewer>, plus the <Operator>

can set the controller rebuild speed, view array performance, perform parity test

and restore device parity.

Signing On to a Domain



Administrator

Administrator access has all the privileges of <Operator> and <Viewer>, plus the

<Administrator> can configure email settings, configure logical arrays, change login

names, change controller parameters and establish custom names for domains.

Signing On

To gain access to an AdminiStor Domain with <Administrator>, <Operator>, or

<Viewer> access, perform the following:

1 Establish a connection.

a Open your web browser and enter the IP Address or the host name

followed by “:9191” and press the Enter key. Once the connection is

established continue with step 2, or

b If the web browser is already started and the AdminiStor applet is loaded

you can re-establish a connection by clicking on the Session menu and

choosing Establish.

In the Connections Status window you will see the message “Session

with AdminiStor established.”

2 Click on the Domain menu and choose Physical Domains, then select Alive

or All Known.

Domains Menu – Physical Domains Menu

You are then presented with the login dialog window.

You may also use the “Domains > Open” menu choice and enter the domain

name along with the password. Using the “Alive” or “All Known” option

allows the administrator or user with a list menu of all physical domains that

can be seen.

Administrator 53


54


Login Dialog Window

NOTE: Refer to “Access Levels” on page 52 to review the different access

level rights and privileges. For setup and configuration you will need

to log into the domain with <Administrator> access level rights.

3 Click on the Access pull-down and choose from <Viewer>, <Operator>, or

<Administrator>. (<Administrator> is the default choice.) For this example

choose <Administrator>.

4 Enter the password for the <Administrator> Access level and click Log In.

Signing On



Navigating AdminiStor

Buttons, Menus, and Menubar

NOTE: The term “host system” is used throughout this manual to mean the host

computer system. It should not be confused with the AdminiStor Host

(ADM Host).

The AdminiStor graphical interface contains a series of function control buttons

and pull-down menus. Each are briefly described below:

Function Control Buttons

Click Apply to enact the settings made in the dialog window.

Click Cancel to exit the window without accepting the changes.

Click Close to close the active dialog box or window.

Click OK to accept the command or apply the change.

Click Restore All to reset all the parameters to the default settings.

Click Restore Page to reset the current page settings to their defaults.

Pull-Down Menus

Pull-Down Menus

The following describe the pull-down menus for AdminiStor. In the examples

shown some selections are only available during specific operations.

Navigating AdminiStor 55


56


Session Menu

From this menu you may select from the available options: “Establish,” “Shutdown,” or “Terminate Requests.” The Establish option performs the necessary task of making a connection to the AdminiStor Server. The Disconnect option closes off the connection with the AdminiStor Server. The Terminate Requests option allows you to stop all commands that have been submitted.

Session Menu

Domains Menu

From this menu you can access and log into the AdminiStor Host(s) physical and logical domains. You are provided the options to Open a connection to a specific domain (or a local system), open a connection to one of the Alive or All Known Physical Domains, refresh the current display, or Select All open domains. You can also Close, or Modify a domain, or Edit the names of the open domains.

NOTE: Only the Open menu choice is available with AdminiStor RCU.

Domains Menu

The physical domain consist of a host system and it’s devices (i.e., host computer, controller, physical disks, enclosures, channels, logical drives (LUNs), etc.). It is the physical components that compose the host system.

The logical domain comprise a mixture of the physical attributes of the physical domains and can include components of other previously created logical domains. Once you have logged into the physical domains, you can create a logical domain by choosing components of those physical domains which will be contained in the logical domain. This allows the user the ability to create customized domains by creating and performing a single login for a specific logical domain.

Session Menu



Rather than having to log into each physical domain which could be numerous

depending on the size and number of the topology of storage within the user’s

environment. These logical domains may or may not contain a subset of the

components of the physical domain, and allows the administrator the ability to

grant access privileges only to that subset.

This is a very powerful feature of AdminiStor Plus which allows the administrator to

customize and manage storage and user access to the storage.

For example; the user could log into several physical domains then pick disks from

one physical domain, and/or disks from another physical domain, selected

controllers, and logical drives and then create a new logical domain. Once created

then the login becomes necessary for the logical domain thus providing a view and

access to all of those physical domain devices. You can also specify the type of

access of that logical domain (<Viewer>, <Operator>, and <Administrator>) and

create additional logical domains from the original logical domain. The maximum

access level is only available to the access rights you have logged in with and

cannot be greater. This means that if you log in as an <Operator> you can only

grant <Viewer> or <Operator> access, not <Administrator>, since you were only

logged in as <Operator>. Refer to “Domains” on page 167.

Notification Menu

NOTE: These Notification options are enabled only for AdminiStor Plus

installations and are not available in AdminiStor RCU.

The Notification Menu provides the administrator or user’s with administrator

access rights the ability to setup recipients of Email notifications.

Notification Email Setup Menu

The Setup sub-menu provides the option to setup Email recipients.

To configure AdminiStor for E-mail services and SNMP traps, you will need to log

into the system as “admin” and access the Preferences option. From here you can

select the E-mail or SNMP tabs, and complete the necessary fields. Refer to

“E-mail Setup and Configuration” on page 77.

Domains Menu 57


58


Notification Preferences Setup

NOTE: The feature tabs for System Event Log, Launch Applications and Log

Table are not implemented in this release.

System Menu

Within the System menu you have the option to open the Log Tool to view the log

files for a specified timed period, access the Client View windows (Physical,

Logical, or Progress), or access the Options menu. The Options menu allows the

user to choose whether or not to display icons in the Client View windows and

RAID Wizard dialogs, specify the parameters for Tooltip pop-up’s, or stipulate the

parameters for a AdminiStor Host connection status by clicking on the specific tab.

System Menu

Windows Menu

This menu allows you to close all open windows or select a specific window that

is currently open. The latter feature is helpful when a specific window is hidden

behind another window and being able to bring it back to the front as the active

window.

Domains Menu


in Level

ain

ofoggedomain


Windows Menu

Help Menu

From the Help menu the user can select the Contents option to display the on-line

help system or the About option to display software version information.

Help Menu

Components of the AdminiStor GUI Window

Upon startup (with pre-defined servers), the AdminiStor GUI main window is

displayed, consisting of pull-down menus, the domain session window and the

connection status window.

.

AdminiStor GUI Window

Pull-Down

ConnectedDomain

Menus

Opens a dialog

Connection

Refresh the

to log into a

current display

Sort Button

DomainSession Window

Status Window

new domain

Status Indicator

List of loggedin Domains

LoggedAccess

Type of Dom

NumberUsers Lin that d

Components of the AdminiStor GUI Window 59


60


Components of the Client View Menu

From the System menu, the Client View selection allows the user to open the

Client View window which displays the physical or logical domain in one of

three modes: Physical, Logical, and Progress.

Physical Mode

The Physical mode displays all the physical components of the nStor storage

system which is seen by the AdminiStor Server(s) and AdminiStor Host(s).

Double-clicking on any of the components will open a window which displays

specific component data or a dialog window that allows specific parameters of

the component to be modified.

Physical View Window

AdminiStor Server

AdminiStor Host

Controller

Controller Channel

Disk Device (statusunknown - no icon)

Disk Drive (on-lineor hot spare green “�”

Expands andCollapses the

Component tree

status icon displayed)

Red “�” status iconindicates a failed drive.

SES/SAF-TE EnclosureServices Panel Icon

Disk Device (yellow “–”status - error detected)

Passive Path Device

Components of the Client View Menu



Clicking on the toggle adjacent to the component icon (if present) will expand

and collapse the display of the components. This allows you to view the

sub-components of the selected object.

Passive Ownership (Redundant Path)

As described in the Introduction chapter, each AdminiStor Host will perform a

discovery of the storage systems and the AdminiStor Host which is first to identify

the storage system will take ownership of that storage system. The other

subsequent AdminiStor Host(s) will display the icons representing the storage

systems owned by the primary or active AdminiStor Host with a blue “P”

overlaid. This indicates it has a redundant path to the storage system besides the

AdminiStor Host you are logged into. Should the AdminiStor Host which has

ownership shutdown or experience a failure, the other AdminiStor Host(s) will

poll and identify the storage systems providing a redundant path. Again, the first

AdminiStor Host to identify the storage system will become the new owner.

If you are logged in with the appropriate access rights to an AdminiStor Host that

is a passive path, you will still have full access to manage and configure that

storage. However, you will be accessing the storage system through the primary

path of the AdminiStor Host that has primary or active ownership.

AdminiStor Server and AdminiStor Host Panel

Double-clicking on the “AdminiStor Server” icon will display a window showing

the server component information. Click the Close button to exit this window.

AdminiStor Server Panel

Physical Mode 61


62


Double-clicking on the AdminiStor Host icon will display a window showing the

host information. Click the Close button to exit this window.

AdminiStor Host Panel

Controller Panel

Double-clicking on the Controller icon will display a window allowing the user to

view and change controller parameters from basic information through Advanced,

Expert, and Fibre. Refer to the product specific Configuration chapter for detailed

information on setting your controller parameters. Click the Close button to exit this

window.

Controller Panel

Physical Mode



Drive Channel Panel

Double-clicking on the Drive Channel icon will display a window allowing the

user to view information on the disk devices on that channel. Placing the mouse

over each icon will display a pop-up with detailed information about the device.

Click the Close button to exit this window.

Drive Channel Panel

In the Drive Channel Panel illustration on the previous page, the pop-up displays a

disk device with a Target ID of 5 on channel 0 of the #37 Controller. The pop-up

also displays information on the drive such as the drive’s physical size, its current

status, the product identification, the drive’s serial number and its world wide

name.

Notice that anytime the mouse passes over an object, Tool Tips will display a

pop-up containing information about the object.

The channel number is displayed at the top of the window along with other data

pertinent to that controller. The icon of the device you are inquiring about displays

a number which is the target ID of that device.

Physical Mode 63


64


Disk Device Panel

Double-clicking on the Drive icon will display a window allowing the user to

view information for that disk drive. From this window the user can execute

some or all of the options located at the bottom of the window, depending on

the state of the disk drive. In the example below and on the next page, this drive

can be removed from the array and placed offline. The user also has the option

to locate the disk drive in the enclosure by clicking the “Locate” button. This will

flash the selected drive’s LED on the storage system front bezel or litepipe. Click

the Close button to exit this window.

NOTE: Some screen may be slightly different depending on the specific model

controller you have installed.

Disk Device Panel (JBOD Attached Device) - AdminiStor Plus Only

Physical Mode



Enclosure Service Panel

NOTE: This feature is not available with AdminiStor RCU only installations.

Double-clicking on the Enclosure Service icon will display a window that allows

the user to view the monitored devices within the NexStor storage enclosures.

They include components such as power supplies, cooling fans, speaker(s), disk

drives, and cabinet temperature sensors. The status (LED) icons adjacent to the

object icon will indicate the status of the component. The conditions for these

status icons are normal (green), failed (red), and unknown (yellow). There is also

a textual indicator as well describing the condition.

NOTE: Additional controller information such as voltage and temperature can be

viewed when Client View - Physical mode is selected, double-click the

subject controller icon and choose the Environmentals tab in the

Controller panel.


Below the enclosure components is a layout of the drive bay slots. If a slot has a

disk drive inserted in the slot it, will be displayed by a disk drive icon. The status

icon adjacent to the drive indicates the present status of that disk drive. A missing

drive is indicated by the text “Absent.” The layout of the drive bay is dynamic and

changes to indicate the number of bays for the specific storage system enclosure.

Click the Close button to exit this window.

Physical Mode 65


66


Logical Mode

The Logical mode displays all logical components that are defined on controllers

from opened Domains. In this mode you can view all configured logical arrays,

as well as, create new, add, edit, or expand the logical arrays.

Logical View Window

Clicking on the toggle next to the component icon will expand and collapse the

display. This allows you to view the sub-components of the adjacent object.

To start the RAID Wizard program (RCU), double-click on the controller icon.

This allows you to create, modify, expand, or delete logical arrays for the

selected controller.

Double-clicking on any of the components will open a dialog window displaying

information about the selected component. such as AdminiStor Server,

AdminiStor Host, logical arrays, etc.

Redundant path or passive objects will be displayed with a blue “P” overlaid on

the icon. This indicates that control of the object’s primary path and ownership is

via another AdminiStor Host. Refer to “Passive Ownership (Redundant Path)” on

page 61.

AdminiStor Server

AdminiStor Host

Controller(Opens the RAID Wizard

assistant program)

Logical Array Icons

Logical Mode




Double-clicking on the AdminiStor Server icon will display a window showing the

AdminiStor Server components information. Click the Close button to exit this

window.



Double-clicking on the AdminiStor Host icon will display a window showing the

AdminiStor Host information. Click the Close button to exit this window.


Logical Mode 67


68


Controller Icon Panel (RAID Wizard)

Double-clicking on the controller icon will launch the RAID Wizard (RCU). This

will allow the user to setup and configure logical arrays, modify existing arrays,

remove existing arrays, and perform LUN Mapping.

RAID Wizard Welcome Screen

Logical Drive Panel

Double-clicking on the Array icon will display the Logical Drive Panel. In this

panel you can review data about the Logical Drive in the top section. You can

review the disk cache information and monitor activity on the array. as well as

view the used and unused capacity of the array. Function buttons at the bottom

of the panel execute Trust Array, Verify Array, Flush Cache, Free Cache, and View

Statistics operations. You can also change the array’s owner (controller) from

within this panel. Click the Close button to exit this panel.

Logical Drive (Array) Panel

Logical Mode



Progress Mode

The Progress mode displays any of the following: consistency checks, logical

drive initializations, rebuild progress, and expand progress.

Progress View Window

System Menu Options

The System menu Options selection allows the user to display icons and set the

icon size for the Client View windows (Physical and Logical) and the RAID

Wizard window. It also provides the options for setting the parameters for the

ToolTips Manager, and connection status options for time settings and

enabling/disabling alarm beep options.

Click the System menu and choose Options. Select the desired option by clicking

the appropriate tab.

System Menu - Options

To set the option to display icons for the Client View windows click the

AdminiStor Client View tab.

AdminiStor Client View Tab

AdminiStor Server

AdminiStor Host

Controller

Logical Array

Shows a consistencycheck in progress on

controller #21,logical drive 0.

Progress Mode 69


70


To enable icons to be displayed adjacent to Client View objects click the check

box for “Show Icons.” Next click the radio button for small or large icons.

To set the option to display icons for the RAID Wizard windows click the RAID

Wizard tab.

RAID Wizard Tab

To enable icons to be displayed adjacent to Client View objects click the check

box for “Show Icons.” Next, click the radio button for small or large icons.

To set the parameters for the ToolTips Manager click the ToolTips tab.

ToolTips Tab

You can choose to enable or disable ToolTips by clicking the appropriate

radio button.

Set the Initial Delay of ToolTips by adjusting the slider as desired. The values

are shown in seconds, 0 indicating no delay and 10 is the greatest delay with

a value of 10 seconds. If the mouse pointer is placed over an object for the

specified period of time Tooltips display the appropriate information window

for the object indicated.

Dismiss Delay and Reshow Delay function similar to the Initial Delay options

for slider operation. Leaving the mouse pointer in position will dismiss the

ToolTips by the designated period of time and reshow will re-display the

ToolTips as designated by the amount of time set by the slider.

System Menu Options



The Enclosures tab features the ability to display temperature in degree’s celsius

or fahrenheit. This feature is not available with this software release.

The Connection Status tab has two functionalities. You can set the amount of time

the connection allows the log messages to be stored in the connection status

window while the controller is running expressed in minutes and the option to have

an audio beep to sound when taking an action. Click the Connection Status tab.

Set the amount of time specified for the connection status window where log

messages are stored while the controller is running. The default time setting

is 2 minutes. Change the time period by adjusting the slider. The values are

displayed in minutes.

Connection Status Tab

You can enable or disable the audible beep tone to ring when taking an

action, finishing an action or anytime any other action occurs.

The Log File Selection option is for use by technical support. It allows the log

of events to be sent to a file or the Java console for debug use.

System Menu Options 71


72


User Interface Icons

The following table shows a list of the AdminiStor GUI interface icons and a

description of each icon.

Icon and Icon Name Description

AdminiStor Server Icon This icon represents each AdminiStor Server. The information adjacent to the icon indicates the server name.

AdminiStor Host Icon This icon represents each AdminiStor Host. The information adjacent to the icon indicates the host name.

Channel Icon This icon represents each channel on the imageRAID controller.

Cooling Fan Icon This icon represents a single cooling fan.

Controller Icon This icon represents a imageRAID controller.

Consistency Check Icon This icon represents a consistency check in progress.

Disk Drive Icon This icon represents each target disk drive.

Enclosure Services Icon This icon represents an SES/SAF-TE enclosure, and clicking this icon will open a window displaying the status of the monitored components.

Initialize Progress Icon This icon represents an initialization is in progress.

Logical Array Icon This icon represents each configured logical array.

Power Supply Icon This icon represents a single power supply.

Rebuild Progress Icon This icon represents a data rebuild operation is in progress.

Speaker Icon This icon represents a single speaker. A yellow LED indicator adjacent to the icon indicates the speaker is sounding an alarm.

Temperature Icon This icon represents a single temperature sensor.

User Interface Icons



Status Indicator Icons

Located adjacent to many devices and logical icons are status indicator icons.

These status icons will give an indication as to the status of the physical device or

logical device. The table below describes symptoms or general characteristics of

the conditions that might generate a specific status icon.

Device Red Status Icon Yellow Status Icon Green Status Icon

ADM Server • Critical state. • Requires attention. • OK.

ADM Host • Critical state. • Requires attention. • OK.

Disk Drive • Failed drive.• Unrecoverable.• Unavailable.

• Critical state. • OK.

Controller • Lost connection. • Not fault tolerant • Dual-Active mode.

Logical Drive • Failed. • Critical state.• In rebuild mode.

• Optimal.

Cooling Fan • Failed. • Non-redundant, one or more fans have failed.

• Normal condition.

Power Supply • Failed.• Installed but not

available.

• N/A • Normal condition.• OK.• Non critical.

Speaker • Failed.• Installed but not

available.


Temperature Sensor

• Failed.• Installed but not

available.


Drive Channel • N/A • N/A • N/A

A missing status icon means the device is unknown or unconfigured.

Status Indicator Icons 73


74


Exiting AdminiStor

There are three options here: you can close or terminate a login session with an

AdminiStor Server, disconnect from the AdminiStor Server, or quit the web

browser (quits AdminiStor GUI).

Closing the Domain Connection

To log out from a domain:

1 In the Domain window, click on the domain you wish to log out.

Selecting a Session Server

2 Click the Domains menu and choose For Selection. From the sub-menu

choose Close.

Domains - For Selection Menu

3 You will receive a confirmation dialog. Click OK to disconnect from that

domain.

NOTE: You may also use the right mouse button function to select the Domain

Name, and right click again and choose Close.

Exiting AdminiStor



Disconnecting from the AdminiStor Server

This feature allows the user to completely log off and disconnect from the

AdminiStor Server. You must re-establish a connection to log into any AdminiStor

Server once you have disconnected. This feature differs from closing the domain

connection. When you close the connection to the domain you can log into

another domain since you are still attached to the AdminiStor Server.

From the main GUI window, click on the Session menu and choose

Disconnect. This action will completely disconnect you from the AdminiStor

Server.

To re-establish a new connection you must click on the Session menu and

choose Establish and log back into the AdminiStor Server. Refer to “Domains

Menu” on page 56 for information about establishing access privileges to the

selected domain.

Session Disconnect

Quitting the AdmimiStor GUI

After you have logged out from a session and closed the connection with the

AdminiStor Server, you can quit the web browser to completely shut down the

AdminiStor GUI.

Follow the procedures above and once completed, from web browser click on

the File menu and choose Exit.

Disconnecting from the AdminiStor Server 75


76


Exiting AdminiStor Server and AdminiStor Host

AdminiStor Server and AdminiStor Host are either a Windows Service or a Unix

Daemon, to exit the Server/Host component do the following:

Windows NT

Click on Start then select Control Panel and select Services and locate and

select the service “AdminiStor v6.2,” then click “Stop.” This action will

completely stop the Windows NT Service.

Windows 2000

Click on Start then select Programs and select Administrative Tools followed

by Services and locate and select the service “AdminiStor v6.2,” then click on

Action and select “Stop.” This action will completely stop the Windows 2000

Service.

Solaris


/etc/init.d/AdminiStor stop and press <Enter>

Linux


/cd/opt/AdminiStor/bin and press <Enter>

./StopAdminiStor and press <Enter>

Exiting AdminiStor Server and AdminiStor Host



Notification Configuration and Preference Settings

E-mail Setup and Configuration

AdminiStor Plus can provide E-mail notification to specified users with a valid

e-mail addresses. To setup the list of E-mail recipients, do the following:

1 Click on the Notifications menu and choose Setup, then select Email.

Notification E-mail Setup Menu

The Notification Setup window will appear.

2 Click the Add button to add a new recipient.

Adding E-mail Recipient

3 Type a valid E-mail address and click the OK button.

Adding E-mail Recipient Input Dialog Window

Notification Configuration and Preference Settings 77


78


4 Select the options for this recipient by clicking the appropriate check box.

Then click the Apply button.

You will receive an informational message that indicates the setup was

completed successfully.

Testing the E-mail Address

5 Test the newly added recipient by selecting the address in the “E-mail

Address” window and clicking the Test button.

You will receive an informational message that indicates the status of the test.

The e-mail recipient will also receive a test message.

6 After you have completed setting up your e-mail list, click the Close button at

the top right corner of the window.

NOTE: To delete a recipient, select the name from the “E-mail Address” list

window and click the Delete button. You will receive confirmation of the

action taken.

E-mail Preferences

AdminiStor’s E-mail notification system is implemented entirely in Java and is

based on a standard SMTP protocol to which it communicates with a SMTP-

compliant mail servers. Depending on the type of mail server you are using, you

will need to specify the outgoing SMTP mail server. Also, it is highly recommended

to enter the full E-mail address of those selected to receive E-mail notifications.

E-mail Preferences



To configure the E-mail Notification preferences:

1 Log in to your AdminiStor Server using the Domain ID “admin.” Do this by

clicking on the Domains menu and choosing Open.

2 Enter the Domain ID “admin” (case sensitive) or the name you choose to

enter during the installation for System Administration Information, followed

by the appropriate password, and click the Log In button.

NOTE: This password was created and entered during installation.

Domain ID and Password Login

3 Click on the Notification menu and choose Preferences, then select the Email

tab.

Notification Preferences – E-mail Setup

NOTE: Clicking the Default button resets the options to the factory settings,

clicking the Restore button, resets the options to your previous settings.

4 In the “Email Server Name” field, enter the full name of your E-mail SMTP-compliant server or it’s IP address.

E-mail Preferences 79


80


5 Under the option “Enable notification for events with severity more than:” you will select a preset condition from the “Tune” pull-down menu or choose manual to set the values using the slider handle.

AdminiStor classifies events that have happened from disabled to informative

to error problems. The selections are additive, meaning you can select to

include just serious events such as “down” or both “down” and “error”, or a

combination of all three events. Selecting Disable turns off the feature.

If you select Manual, you can adjust the slider handle to choose the sets of events that determine if an action is required. Selecting any of the preset conditions from the “Tune” pull-down menu will disable the slider handle.

E-mail Preference Tuning

6 Edit the contents of the Signature field. Place the mouse cursor over the item you wish to change, drag the mouse to highlight and type the new information for that item.

The minimum suggested changes would be to add your Company name.

Alternately, you may wish to enter your server URL, so whenever you receive

an E-mail message, you would also have a URL link to click that would take

you to AdminiStor to resolve the issue (e.g., http://myserver.xxxx.com:9191).

7 After you have completed all of your changes, click the Apply button and close the window.

E-mail Preferences



8 You will receive a message indicating the Preferences were successfully changed. Click Ok, then click the Close button.

Be sure to log out after this session for security purposes. Do this by selecting the “admin” domain name and right clicking the mouse on the “admin” name and choosing Close.

SNMP Preferences

AdminiStor can be configured to send SNMP traps to any number of network

management systems (NMS). These SNMP traps carry all of the information that

appears in the AdminiStor log entries for all the monitored storage systems and

their components.

All SNMP traps are sent from the AdminiStor Server regardless of where the event

originated. Therefore, all of the AdminiStor Host names and/or IP addresses

given in the list of SNMP managers are interpreted from the point of view of the

server system.

NOTE: All SNMP traps are sent with the community value “public” using the

UDP protocol and directed to port 162. If these values do not work in

your environment, please contact technical support for special

instructions to change these values.

The SNMP configuration can be set with a severity level, and no traps will be sent

for messages that are lower than a specified level. The severity level is used to

derive the specific trap number that will be sent to the network manager. Every

SNMP trap is associated with the nStor enterprise (.1.3.6.1..4.1.1793) and

references the nStor.administor.admTrap.admTrapInfo object

(.1.3.6.1.4.1.1793.2.1.1). The traps are all enterprise specific, with specific trap

numbers as defined in the following table.

reportOK 9984 The log entry is reporting that the situation is normal.

reportINFO 9985 The log entry is reporting some information that may be of interest, but does not require immediate attention.

reportWARNING 9986 The log entry is giving a warning of minor problems or the potential for an error.

reportERROR 9987 This reports a problem that is serious, and often means loss of redundant capability.

SNMP Preferences 81


82


Along with every trap is message text that defines the exact problem. This is sent

as ASN.1 (Abstract Syntax Notation One) type “Octet String” (4) as defined in

ISO/IS 8824 and ISO/IS 8825 and may be up to 440 characters in length. This

message is in the same language as used by Email notification, and has the same

contents. In order to make the message more useful in network manager

environments, multiple spaces are compressed to a single space, and multiple

lines are joined into a single line.

Most users would configure their network manager to respond to AdminiStor

traps by launching a browser and pointing it at the AdminiStor Server. This allows

the administrator to investigate and further deal with the problem reported.

To configure the SNMP Notification system:

1 Log in to your AdminiStor Server using the Domain ID “admin.” Do this by

clicking on the Domains menu and choosing Open.

2 Enter the Domain ID “admin” (case sensitive) or the name you choose to

enter during the installation for System Administration Information, followed

by the appropriate password, and click the Log In button.

This password was entered during installation.

Domain ID and Password Login

3 Click on the Notification menu and choose Preferences, then select the SNMP

tab.

reportFAIL 9988 This message is sent when there is a failure in the ability to use some monitored component.

reportUNKNOWN 9989 This message is not supposed to be sent. If it is seen, it contains information about a message that could not be classified, and the contents of the message should be reported to your service provider.

SNMP Preferences



4 Add your IP addresses of the SNMP manager station. Click the Add button

and enter the IP address or “local host” and click OK.

You may add as many IP addresses as you desire.

Notification Preferences - SNMP Setup

5 Under the option “Enable notification for events with severity more than:” you will select a preset condition from the “Tune” pull-down menu or choose manual to set the values using the slider handle.

AdminiStor classifies events that have happened from disabled to informative

to error problems. The selections are additive, meaning you can select to

include just serious events such as “down” or both “down” and “error”, or a

combination of all three events. Selecting Disable turns off the feature.

SNMP Preference Tuning

SNMP Preferences 83


84


If you select Manual, you can adjust the slider handle to choose the sets of events that determine if an action is required. Selecting any of the preset conditions from the “Tune” pull-down menu will disable the slider handle.

6 Activate the new IP addresses. Select each address you have entered and

click the Apply button. You will receive a message indicating the Preferences

were successfully changed.

7 Click Ok, then click the Close button.

Be sure to log out after this session for security purposes. Do this by selecting the “admin” domain name and right clicking the mouse on the “admin” name and choosing Close.

You can confirm the SNMP message setup by examining the AdminiStor Log. Similar to the example below.

Log Messages

SNMP Preferences

Chapter 4


Configuration

Introduction

This chapter will provide information on how to use the RCU component of

AdminiStor to configure the imageRAID SCSI Controller (JSS122). These

controllers are referred to as the “imageRAID Controller” for the Ultra160-

to-Ultra160 models (JSS122).

Configuration activities involve some of the following:

� Setting up the controller options

� Creating logical arrays and partitions

Other activities that are accomplished through the RCU component are:

� Managing specific tasks and controller parameters

� Modifying existing logical arrays or partitions

� Deleting logical arrays or partitions

� Modifying array capacity by adding drives to the logical array.

NOTE: During configuration, some RAID Wizard screens will have a “Notes”

section appear in the window to assist you with any question you may

have relevant to the object selected. The screen captures in this chapter

have those note sections removed for printing layout purposes.

85

Chapter 4 - Configuration

86


Setting Up and Modifying Controller Options

1 After you have established <Administrator> access, click on the System menu

and choose Client View, then select Physical.

TIP: You can double-click the Domain Name in the AdminiStor GUI window,

which will automatically open the Client View - Physical window.

2 Open the Controller panel by double-clicking on the Controller icon in the

Physical View tree.

Client View – Physical (Accessing Controller Options)

The Controller panel is displayed with the Information tab selected. You can

access the different controller options by clicking the desired tabs at the top

of the panel.

Under the Information tab, you will see controller hardware and firmware

parameter settings. You will also see the host connection information which

provides the user with the name of the host system that is connected to the

selected controller, along with the controller number, channel number and its

target ID number.

Controller Icon(Double-clickto open the

Controller panel)




Controller Panel – Information Tab

NOTE: Along the bottom on the Controller panel, you will find function control buttons that scan the bus, reboot controller(s), shutdown controller(s), access the flash utility to update the controller’s firmware and close the window panel. These control buttons are available regardless of which tab is selected.

3 Click the Environmentals tab to display monitored health information for the imageRAID controller(s) and the enclosure.

Controller Panel – Environmentals Tab

Setting Up and Modifying Controller Options 87


88


Write Back Cache Stats – Indicates whether the option is enabled or disabled.

Battery Months Old – This displays the number of months since the

battery was configured as new or a specific age set in the Flash Utility.

(Note that you can move a battery from one controller to another, and a

feature in the Flash Utility allows you to set the existing number of

months already accumulated on the battery being installed. For example

if the battery had been used for 12 months in another controller and it is

a 36 month battery, when you install it in a different controller, you

would use the Flash Utility to set its age at 12 months. Then with each

new month, based on the computer systems’ date/time, the monitor will

increment the age of the battery accordingly.

Battery State – Displays the charge condition of the backup battery.

Battery Status – Displays the current condition of the backup battery.

RAID Controller Enclosure – This monitored data provides information

on the imageRAID Controller Enclosure cooling fan status and its power

supply status.

You can change the display temperature values for the controllers to either

celsius or fahrenheit, by selecting the appropriate radio button.

4 Click the Parameters tab to display controller specific options and settings.

Controller Panel – Parameters Tab




External Target ID Control – Check to enable and uncheck to disable.

This allows the external enclosure to provide the SCSI target ID.

Environmental Temperature Enable – Check to enable. This option

allows the controller’s temperature information to be sent to the

environmentals package.

Environmental Auto Slot Flags – Check to enable and uncheck to disable.

This option allows the “slot flags,” which controls whether the controller

sends commands to the SEP to update the status of each enclosure slot.

The default setting should be enabled.

Environmental Global Slot Flags – Check to enable and uncheck to

disable. This option determines whether the controller sends commands

to the SEP to update the overall status of the enclosure.

Disable Battery Option – Check to disable. This option allows the user to

disable the battery condition monitor which also puts the controller in

write-back mode. If you have a backup battery pack in your controller,

you will see a notification when its life time has expired. (Refer to the

Environmentals tab to view the current age of the battery.) If you do not

have a battery pack installed you will also receive a notification for that

condition. If you do not have a backup battery installed and wish to

eliminate the alarm, you can disable the battery option. The default

setting is enabled (unchecked).

If you have replaced a battery you will need to reset the Battery Age

and Life monitor. This operation is accomplished through the VT-100

terminal using the Flash Utility. Refer to Chapter 5 of the VT-100

Software Guide for imageRAID SCSI Controller and follow the

procedures described. This process requires that you have a VT-100

terminal (or emulation) connected to one of the controller RS-232

ports.

Alarm Mute – Check to enable and uncheck to disable. An audible alarm

sounds when the controller becomes too hot, detects low or high

voltage, or an array becomes critical or offline. Changing the mute setting

lets you turn off the alarm when it is sounding. You should turn it back

on after resolving the problem causing the alarm.



90


Cache Lock – Check to enable and uncheck to disable. You can prevent

host systems from using SCSI mode select commands to change the

controller’s write-back cache setting. Some operating systems disable

write cache. If cache lock is enabled, the host cannot modify the cache

setting. The default setting is disabled (unchecked).

Operating Mode – Click the pull-down menu to select the appropriate

operating mode. You can change controller’s operating mode:

Stand-Alone Single Port, Stand-Alone Dual Port, Active-Active Single Port,

Active-Active Dual Port, and Active-Passive Dual Port. If you are using a

dual configuration (Active-Active/Active-Passive) a change to either

controller’s setting is immediately sent to the other controller, unless you

change to a Stand-Alone mode.

Operating Mode Models Available Description

Stand-Alone Dual Port

JSS122 This option allows the controller to operate with two host ports. In this mode, the same LUNs display on the two separate host ports. Stand-Alone Dual Port mode allows the host to achieve greater throughput by balancing I/O operations across the two host ports. Host port fault tolerance is also achieved, because the host can continue to access the controller if one host channel fails.

Stand-Alone Single Port

JSS122 This option allows the controller to operate with one host port and three or four disk channels. Select Stand-Alone Single Port mode if you do not want to run in dual port mode, or your host operating system does not support it

Active-Active Single Port

JSS122 This option allows both controllers to operate independently and as in an active-active pair. Active-Active modes allow two controllers to cooperate in system operation in a fault-tolerant manner. If one controller fails while in Active-Active mode, the other controller assumes its activities, allowing host access to continue.

When both controllers are online, each controller presents its LUNs on only one port.

Active-Passive Dual Port

JSS122 This option allows you to use just one controller with the second controller acting only as a backup in case of a failure of the controller in use.

When you change to this mode on one controller, you must reboot both controllers at the same time. After rebooting, both controllers will automatically be in Active-Passive Dual Port mode.




NOTE: You must reboot the controller for these changes to take effect.

Internal Hubs – This feature allows the user to enable (checked) or

disable (unchecked) the internal hubs. When enabled, the internal hubs

provide built-in connections for up to four (4) independent hosts. The

internal hubs replace the requirement for an external hub.

Environmental Poll Interval – This is the time interval, in seconds, that

the controller polls the SEPs for changes in status. The default setting is 5

seconds.

Create Array Backoff Percent – This setting backs off or reduces the

capacity of the array by the given percentage. The backoff percentage

helps when you assign spares by compensating for minor capacity

differences that occur between drive vendors. The default setting is 1%.

Drive Write Back Cache – You can control the write-back cache setting

for all of your disk drives at once. Changes take effect after the next

rescan or reboot. This can be set to “Enable,” “Disable,” or “Don’t

Modify.” The default setting is “Don’t Modify.”

Drive Smart – You can enable or disable the ability to change the

Self-Monitoring, Analysis and Reporting Technology (SMART) settings for

all drives connected to the controller. this can be set to “Enable,”

“Disable,” or “Don’t Modify (which means the controller should not

change any drive’s SMART settings.) The default setting is “Don’t

Modify.”

Utility Priority – You can change the priority at which all utilities (Verify,

Reconstruct, Expand, Initialize, etc.) run when there are active I/O

operations competing for the controller’s CPU time. The choices are:

High (default), Medium, and Low.

Dynamic Spare Rescan Rate – This tells the controller how often it should

look for an available drive by rescanning the bus. Remember that

rescanning the bus frequently can affect performance. If you have a SEP,

the dynamic spare configuration will not rescan the bus. The SEP will

detect the new drive and tell the controller to rescan; the rescan rate you

set here will not affect the system. Adjust the slider control to set the

rescan rate in minutes.

Click the Apply button to make you changes active.

NOTE: Host configuration options are specific to the controller model.

5 Complete the following Host Configuration options.



92


a Click the Host Configuration tab to display settings for the Controller

LUN, SEP LUNs, enabling/disabling the controller channels,

enabling/disabling host resets on failover, and Host Channel Target IDs.

Controller Panel – Host Configuration Tab

Controller LUN – Sometimes referred to as the Host Controller LUN

(RAID Controller LUN), supports up to sixty-four (64) SCSI Logical Unit

Numbers (LUNs) that are numbered 0 through 63. Some operating

systems require you to set the controller LUN to a higher value than all

the array LUNs. If for some reason you are not seeing your array(s) after

creating them and rebooting, you may need to change this setting. The

default and recommended setting is LUN 0.

SEP LUNs – Allows access to SEPs. A SEP LUN may be set to a value of 0

through 63. The setting “None” means the SEP cannot be accessed via a

LUN.

Host Channels - Enable – This option is available only when using a

single controller (Stand-Alone mode). Use this option to enable or

disable the host channel.




Target ID – This option allows the user to select the desired SCSI ID for

the host channel’s SCSI target ID. You can set the target ID to any

number between 0 and 15.

Host Reset on Failover – This option is available only when using a dual

controller (Active-Active or Active-Passive mode). If you have enabled

this option, the controller will reset the host buses whenever a failover or

failback event occurs.

6 Click the Apply button to make you changes active.



94



Function Control Buttons reside at the bottom of the Controller panels. They

remain constant regardless of which tab is selected.

Controller Panel Function Control Buttons

Scan

The Scan button allows the user to begin a rescan of the bus. When you click this

button you will be prompted to proceed, click the “Yes” button to continue with

the controller scan of the bus.

Reboot

Clicking this button will reboot one or both controllers, depending on whether

your are operating in a Standalone mode or an Active-Active/Active-Passive

mode. The button name will change dynamically depending on the operating

mode; “Reboot Controller” for Standalone and “Reboot Both Controllers” for

Active-Active/Active-Passive modes.

This feature is necessary since you may need to shut down and restart the

controller(s) after making certain configuration changes. A normal shutdown

ensures that the write-back cache has been flushed to the disk.

Shutdown Both

The “Shutdown Controller” or “Shutdown Both Controllers” button will perform a

graceful and if necessary simultaneous shutdown of the controller(s). The button

name will change dynamically depending on the operating mode; Standalone or

Active-Active/Active-Passive, “Shutdown Controller” for Standalone and

“Shutdown Both Controllers” for Active-Active/Active-Passive modes.

Flash Utility

This button allows the user to upload new firmware to the RAID Controller. Refer

to “Updating Controller Firmware” on page 142 for more details.

Host Configuration Tab (Restore and Apply buttons)

On the Host Configuration screen, the Restore button will reset the parameters to

their default values without affecting any settings on previous screens. Clicking

the Apply button will make your changes active.




Running RAID Wizard

RAID Wizard is the AdminiStor GUI “assistant” for setting up, configuring, and

modifying new and existing logical arrays.

Drive Requirements for Specific RAID Levels

You can create an array at anytime. The table below describes the drive

requirements for each RAID level.

NOTE: Before you create more than one array, you must be sure that your host

operating system supports multiple Logical Unit Numbers (LUNs). Most

operating systems do, or have an option you can enable to support

multiple LUNs. If your operating system does not support multiple LUNs,

the host will only be able to see one array at LUN 0.

Before you create an array, you must decide whether you want to partition the

array. You can create an array one of two ways:

� Single-partition array – an array that stores all data in a single partition and

is accessed by a single LUN.

� Multiple-partition array – an array that can has more than one partition,

where each partition is assigned its own LUN.

NOTE: You must create at least one partition before using the array.

Drive Requirements by RAID Level

RAID Level Minimum No. of Drives Maximum No. of Drives

Volume (JBOD) 1 1

0 2 16

3 3 16

4 3 16

5 3 16

50 6 32

1 (Mirrored) 2 2

10 (Mirrored) 4 16

Running RAID Wizard 95


96


Entering RAID Wizard

1 Follow the procedures to sign on to the Administor Server, refer to “Signing

On to a Domain” on page 52.

2 Click on the System menu and choose Client View, then select Logical.

3 Start the RAID Wizard, double-click the Controller icon that you wish to

make changes to in the Client View - Logical tree. Then choose either

Automatic, Assisted, or Manual Configuration, described on the following

pages.

Client View – Logical

The RAID Wizard “Welcome” dialog window will appear.

• Click the Automatic Configuration (“Automatic Configuration” on

page 98) button if you want the RAID Wizard to configure your array.

• Click the Assisted Configuration (“Assisted Configuration” on page 100)

button if you want a series a prompted steps to configure the array.

• Click the Manual Configuration (“Manual Configuration” on page 106)

button if you want full control over your configuration setup.

• Click Cancel if you want to exit the RAID Wizard without any changes.

• Click the Current Configuration button to display the current

configuration information for the selected host system.


RAID Wizard)

Entering RAID Wizard



RAID Wizard – Welcome Screen

WARNING: Selecting a new configuration in either configuration mode

(Automatic, Assisted, or Manual), will delete the current

configuration and all data will be lost. To add another array to

existing configurations, choose Edit Configuration.

The configuration is a file that contains all the information about the

logical arrays, partitions, and controller parameters. Selecting New

Configuration will delete the contents of this file.

The selection New Configuration should only be used on a new

installation or when all existing arrays and partitions are no longer

needed, or where you decide to start over with a clean system. To add

new arrays from unassigned drives to an existing configuration, always

use the Edit Configuration selection to create a new array.

Entering RAID Wizard 97


98


Automatic Configuration

The Automatic Configuration option allows the RAID Wizard to automatically

create an optimum configuration based on the number of available drives. The

automatic configuration feature uses the maximum number of drives for the

auto-selected RAID level, and the full capacity of the drives to provide a fault

tolerant RAID level when able. The process creates at least one hot spare drive

for every eight (8) drives used. If the maximum number of drives for the RAID

level is reached, then a second array is automatically created if more drives are

available. The number of logical drives created is dependent on the total number

of physical drives discovered and the maximum number allowable.

To Start an Automatic New Configuration:

1 Sign on to the Administor Server, refer to “Signing On to a Domain” on

page 52.

2 Click on the Session menu and choose Client View, then select Logical.


make changes to in the Client View Logical tree.

The RAID Wizard Welcome screen will appear.

4 Click on the Automatic Configuration button. The Automatic Configuration

screen appears.

Automatic Configuration Welcome Screen

5 To start a new configuration, click on the New Configuration button.

You are presented with the results of what the wizard will create automatically.

Before you click the Apply button to create the array(s), review the

configuration displayed on the screen. If you are satisfied, click the Close

button.

Automatic Configuration



Automatic New Configuration – Finish

6 Click the Apply button to accept the configuration. You will be prompted to

confirm the operation.

7 Type YES and click OK. If you do not want this configuration click the

Cancel button.

8 Once the configuration is complete, a series of warning and confirmation

windows will appear, click OK in each.

If an error occurs, refer to the log table to determine why the error occurred.

9 You are presented with an updated configuration screen which you can

review and then click the Close button. You are returned to the RAID Wizard

Welcome screen.

NOTE: The controller will automatically perform a reset/reboot function, it may

take several minutes, followed by initialization of the Logical Drive(s).

The Controller Panel will indicate that the reset/reboot is executing.

10 You will now be ready to prepare and use the newly defined storage. Be

sure to access the storage from your operating system and prepare it as

necessary, (i.e., define, mount, format, etc.).

Automatic Configuration 99


100


Assisted Configuration

The Assisted Configuration through the RAID Wizard walks the user through a

series of screen prompts to perform an optimum configuration. The user is

prompted to set options such as High Availability, RAID levels, Access and

Number of Arrays, and Optimization. The Assisted Configuration uses the

maximum number of drives for the selected RAID level, and the full capacity of

the drives to provide a fault tolerant RAID level when able. If the maximum

number of drives for the RAID level is reached, then a second array is

automatically created if more drives are available. Remember the New

Configuration option sets up a new configuration file which deletes any previous

configuration and data.

To Perform an Assisted New Configuration:


page 52.



make changes to in the Client View Logical tree. The RAID Wizard Welcome

screen will appear.

RAID Wizard – Welcome Screen




4 Click on the Assisted Configuration button.

The RAID Wizard Assisted Configuration Welcome screen will appear.

Assisted Configuration – Welcome Screen

Assisted Configuration will walk you step by step through a new

configuration. Each “tab” in the Assisted Configuration screen collects

information from your input to setup the configuration.

5 Click on the New Configuration button.

The wizard opens the Assisted Configuration screen with the High

Availability tab selected.

Assisted Configuration – High Availability Screen

6 First we must consider the option of setting up a redundant disk array (RAID

1, 10, 3, or 5). Select Yes if you wish for this configuration to use part of the

storage for redundant data, and/or having a hot spare. Otherwise click the No

radio button.

Assisted Configuration 101


102


Selecting “No” will allow you to setup a JBOD or RAID 0 configuration. The

Pool Spare option will be grayed out and unavailable.

NOTE: A red asterik will appear next to each completed task.

7 If you choose High Availability, you will need to consider setting up a drive

as a pool spare. If you wish for this configuration to have a pool spare drive,

select Yes.

Pool spare disk drives will automatically replace a failed disk drive in a high

availability disk array, otherwise click the No radio button.

Once you have completed your selections, click the Next button.

8 Select the appropriate RAID level for the disk array.

This option is based on the High Availability option being selected

previously.

If High Availability is selected on the previous screen, the RAID levels are

expressed in Parity error correction; distributed parity stripe for RAID 5,

Dedicated Parity Drive in RAID 3, or Fully Redundant Drives in RAID 1 or

RAID 10. Click the appropriate radio button followed by the Next button.

RAID Level Screen – High Availability Selected

If High Availability is not selected in the previous screen, the options are

JBOD and RAID 0. See the illustration on the following page.




9 Click the appropriate radio button followed by the Next button.

RAID Level Screen – High Availability Not Selected

10 Choose the number of Array’s you wish to create.

Assisted Configuration – Array Screen

If you need access to the Array’s immediately while they are initializing,

select Yes. If you don’t need to have them available prior to the initialization,

then select No which performs the initialization offline and when complete

are ready for normal use.



104


11 Select the chunk size (stripe size) you wish to implement, then click the Next

button.

Chunk size, otherwise known as “stripe size,” is the amount of contiguous

data that is written to an array member before moving to the next member of

the array. To determine the appropriate chunk size, refer to your operating

system documentation. The default chunk size is 64 KB. Click on the

pull-down menu option to select from the available choices.

Assisted Configuration –Optimization Screen

The Finish tab is automatically displayed with a summary of the pending

configuration.

Assisted Configuration – Finish Screen



P

L

erray

rive


12 If you desire, click the Details button and review your configuration settings.

After you have reviewed the settings, click the Close button.

Assisted Configuration Details Window




Cancel button.






Welcome screen.

Note that the controller will automatically perform a reset function (may take

several minutes) followed by initialization, if selected, of the Logical Drive(s).

The Controller Panel will indicate that the reset is executing. The Logical

Drive panel will indicate the initialization is occurring.

The progress of each initialization can be monitored by clicking the Progress

mode in the Client View window and selecting the Initialization Progress icon.

Usable size ofdisc array

Controller

List of Arrays

Array being created

List of Physical Discsincluded in the array

hysical Drives in array

ist of Hot Spare Drives

Total physical sizof drives in the a

Physical total dsize



106


Manual Configuration

Manual Configuration provides two options:

� Edit Configuration – Displays the current configuration (disk arrays and

partitions), and allows you to make any changes to existing arrays.

� New Configuration – Sets up a new configuration on the controller,

deleting the previous configuration, arrays, partitions, and data (if any).

To Perform a Manual New Configuration:


page 52.


3 Start the RAID Wizard, double-click the Controller icon representing the

RAID Controller that you wish to make changes to in the Client View Logical

tree.


4 Click on the Manual Configuration button. The Manual Configuration menu

screen appears.

Manual Configuration Menu Screen

5 To start a new configuration, click on the New Configuration button.

Remember when you create a “New Configuration” this process will clear the

previous configuration. The definition of the configuration is a file that

contains all the information about the arrays, partitions, and controller

parameters. Selecting New Configuration will delete the contents of this file.




The selection New Configuration should only be used on a new installation

or when all existing arrays and partitions are no longer needed, or where you

decide to start over with a clean system. To add new arrays from unassigned

drives to an existing configuration, always use the Edit Configuration

selection to create a new array.

You are presented with the New Configuration panel. From this panel, you

will select the array to which you will add drives to build the array.

New Array Screen

You will now add disk drives to the new array.

6 Click on the “Disk” item listed below the “New Array” item in the Selected

Arrays pane.

Adding Drives to New Array

Select Disks toadd drives to

the new array.

Select a Disk,then click “<<“button to add.

Manual Configuration 107


108

t


7 From the Available Drives pane, begin selecting and clicking the “<<” button

which adds the drive to the new array.

Continue selecting disk drives from the Available Drives list until you have

populated the array with the desired number of disk drives. Note that you can

also use the <Control> key to select multiple disk drives before adding them.

8 Select “New Array” to display the Array Properties pane. From here you will

set the specific properties for this array.

Setting Array Properties

9 In the Array Properties pane, set the following:

• RAID Level – The available RAID levels will be determined by the

number of drives added to the array. There must be a sufficient

number of drives added for redundant RAID levels to be active.

• Chunk Size – Otherwise known as “stripe size,” this is the amount of

contiguous data that is written to an array member before moving to

the next member of the array. To determine the appropriate chunk

size, refer to your operating system documentation. The default chunk

size is 64 KB.

• Creation Priority – This option allow the user to set the controller’s

process priority for array creation over other utilities such as rebuilds,

etc. The available choices are high, medium, and low. The default

setting is High.

Select New Arrayo access the Array

Properties pane.

Array Properties




• Initialization – This option allows you to choose whether you want the

array created offline meaning users must wait for the initialization to be

completed, or online where the array can be used while it’s being

created. The latter option takes longer. The default setting is Offline.

• Name – The plain language name that is user defined for the array.

You can use up to 20 characters. Note that only 15 characters can be

displayed in the OCP display. If you do not want to name the array,

you can accept the default, Array 1, and this can be changed later

using the Edit Configuration option.

10 Choose whether this array will have a single partition or multiple partitions.

You must create at least one partition on the array before you can use the

array. To create a “single” partition, select the check box “Only One Full

Partition.”

If you want to create multiple partitions, leave the check box unchecked.

Follow the instructions provided after creating the array to create and name

each partition.

11 Click the Create Array button to create the logical array.

12 If your choice was to create multiple partitions, follow the substeps below,

otherwise skip to step 13.

a Click the “Free Space” item in the newly created array. This will enable

the New Partition Properties pane on the right.

Setting the Partition Properties

Select Free Spaceto make changes.



110


b Enter a name for the partition.

c Set the LUN number for the partition. By default the controller is

assigned LUN 0, the software will automatically increment the LUN

numbers for each partition. You can also set the array LUNs manually or

just allow the software to select them sequentially.

d Enter the size of the partition, expressed in MBs.

e Click the Create Partition button.

NOTE: When you create partition(s) on a fault tolerant array, the partition(s)

will not be displayed if you choose offline initialization until the

array has completed initialization. If you view the configuration, it

will indicate in red text in the Array Properties pane that the array is

offline or a utility is running.

f Repeat the above substeps for each additional partition. You can leave

some free space available, and of course define it later.

Partition Properties Being Changed




Cancel button.



Enter newPartition name.







Welcome screen.

NOTE: If during the initialization, you experience a power failure, when

power is restored to the systems the controller will start the

initialization again. However, the partition(s) will not be create

under these circumstances, since the partition(s) are not created until

after the initialization. If you encounter this situation, allow the

controller to complete the initialization, then refer to “Creating a

Partition” on page 114 to recreate the partition(s).

If you desire to create additional arrays or changes, click the appropriate

button on the Welcome screen, otherwise close this window.

NOTE: You can monitor the status by double-clicking Progress icon in the

Client View window with Progress selected.






112


Other Configuration Activities

As described in the beginning of this chapter, other activities that can be

accomplished with the AdminiStor RCU are: modifying existing logical arrays or

partitions, delete logical arrays and partitions, and modify the array capacity by

adding drives to the logical arrays or increasing the partition size.

Editing Configurations

To perform many of the above configuration activities:


page 52.


3 Start the RAID Wizard, double-click the Controller icon representing the

RAID Controller that you wish to make changes to in the Client View Logical

tree.


4 Click on the Manual Configuration button. The Manual Configuration menu

screen appears.

Manual Configuration Menu Screen

5 To modify an existing configuration, click on the Edit Configuration button.

From this point you can perform many of the following configuration

modifications:

Other Configuration Activities


Pro


Changing an Array Name

1 Select an array to which you wish to make changes.

Modifying Array Names

2 Enter a new array name and press <Enter>.

3 Click the Apply button to make the changes active, or click the Cancel button

to discard any changes.

Deleting an Array

1 Select an array that you wish to delete.

Deleting an Array

Select Array tomake the Array

Enter newArray name

perties pane active

Select Array tomake the Array

Properties pane active

Click Delete Array

Changing an Array Name 113


114

toPro


2 Click the Delete Array button.

3 Click the Apply button to delete the array, or click the Cancel button to

discard any changes.

Creating a Partition

1 Select the “Free Space” item under the chosen array. This will enable the

New Partition Properties pane on the right.


2 Enter a name for the partition.

3 Set the LUN number for the partition. By default the controller is assigned

LUN 0, the software will automatically increment the LUN numbers for each

partition. You can also set the array LUNs manually or just allow the software

to select them sequentially.

4 Enter the size of the partition, expressed in MBs.

You may choose to use all of the available size for one partition or only a

portion of the available size for this partition. You can create additional

partitions or choose to leave the remaining available space for other

partition(s) that can be created at a later time.

Select Free Space make the Partitionperties pane active




5 Click the Create Partition button.

6 If you chose to use a portion of the available space and also wish to create

more partitions from the new remaining available space, repeat the

preceding steps (1-5) for each additional partition using any of the remaining

available “free space.”




Cancel button.






Welcome screen.

If you desire to create additional arrays or changes, click the appropriate

button on the Welcome screen, otherwise close this window.

NOTE: You can monitor the status by double-clicking Progress icon in the

Client View window with Progress selected.




Creating a Partition 115


116


Changing A Partition Name

1 Select a partition to which you wish to make changes.

Modifying Partition Names

2 Enter a new partition name and press <Enter>.

Partition Name Changed



Select Partition tomake the Partition


Enter newpartition name

Changing A Partition Name



Changing A Partition LUN

1 Select a partition you to which you wish to make changes.

Selecting a Partition

2 Click on the LUN pull-down menu and choose a new LUN ID number.

Selecting a New LUN





Select a LUN IDfrom the LUN

pull-down menu

Changing A Partition LUN 117


118

P


Deleting A Partition

1 Select a partition that you wish to delete.

Deleting a Partition

2 Click the Delete Partition button.



Adding A Pool Spare

1 Select the Pool Spare item in the Selected Arrays pane.

2 From the Available Drives pane, select a drive and click the “<<” button

which adds the drive to the pool spare.

Selecting a Disk Drive

Click Delete Partition


roperties pane active

Select Pool Spare


Deleting A Partition





New Pool Spare Added

NOTE: Adding a Pool Spare can also be accomplished using the Client View –

Physical selection and double-clicking the Disk Device icon you wish

to make a spare. From this window select the Make Pool Spare button.

New Pool Spare

Adding A Pool Spare 119


120


Expanding Array Capacity

You can expand array capacity without stopping I/O activity, so you can

continue using the array while the expansion process runs. You can only expand

one array at a time.

NOTE: Expanding an array does not change the size of the host operating system

partitions that reside on the array, this is due to our controller working at

the block level not the file system level of the operating system. To use

the new space, you must create a new partition using the newly added

space or use a third-party application specific to the operating system to

change the partition size.

How you create a new partition or resize an existing one depends upon

the operating system. Most operating systems cannot resize an existing

partition. Refer to your operating system documentation.

The number of drives you can add to an array depends upon the RAID level as

shown in the table on the following page. You also cannot exceed the maximum

number of drives for each RAID level.

NOTE: When expanding a RAID 50 array, you must choose the exact number of

drives in the RAID 5 array that comprise the RAID 50 array. Example: if

your RAID 5 array contains three (3) drives, you must choose a total of

three (3) drives to perform the expansion. Choosing a different number of

drives, greater or less than, will cause the expansion operation to fail.

Drive Additions by RAID Level

RAID Level Number of Drives You Can Add Maximum Number of Drives

RAID 0 1 to 4 at a time up to the maximum. 16

RAID 1 (mirrored) Cannot expand N/A

Volume Cannot expand N/A

RAID 10 2 or 4 at a time up to the maximum. 16

RAID 3, 4, or 5 1 to 4 at a time up to the maximum. 16

RAID 50 All RAID 5 arrays must contain the same number of drives. You must choose the exact number of drives in the RAID 5 array to perform the expansion. Choosing a number of drives that are different from the RAID 5 array will cause the expansion to fail.

32

Expanding Array Capacity



If you are expanding a multiple-partition array, you add free space at the end of

the array. Once you start expanding array operation, you cannot stop it. The

expand function may take an hour or more to complete, depending on the array

type, array size, drive speed, and other processes running on the controller.

Increasing the Capacity (Expanding Array Size or Expanding Partition Size)

You can expand an existing array by adding additional drives to the array thus

increasing its capacity by making new free space available.

Expanding the Array

To Expand the Array:


page 52.




screen will appear.

4 Click on the Manual Configuration button. The Manual Configuration screen

appears.

5 Modify an existing configuration, click the Edit Configuration button.

6 Select the Disk(s) item in the Selected Arrays pane under the array that you

wish to expand.

Selecting a Disk Item to Expand

Select Disk Item

Increasing the Capacity (Expanding Array Size or Expanding Partition Size) 121


122


7 Select one or more drives in the “Available Drives” pane to add to the

selected array and click the “<<” button to add them to the array.

Expanded Array With New Size Displayed

You will notice the Total size of the array and the Free Space size increased

as the disk(s) were added.



9 Use the procedures to add a partition to create new usable space on the

existing array.

NOTE: You can monitor the status of the expansion by double-clicking the

Progress icon in the Client View window.


Select Disk item




Expanding the Partition

To Expand the Partition:

When you choose to expand a partition, the free space must occur directly after

the partition you wish to expand. When you select the Disk(s) item and add

drive(s), the “free space” will always occur after the last partition. So only the last

partition can be expanded. However, if a partition that is not last in the list must

be expanded, then you must delete all the remaining partitions first before adding

the new drives. This will cause the “free space” to occur after the desired partition.

WARNING: If you delete a partition, you will lose the data on that partition.

Therefore, in order to preserve any data on partitions that must be

deleted, copy that data to another drive or back up the data, then

delete the partitions, perform the expansion and recreate the

partitions from a portion of the new free space.


page 52.




screen will appear.


appears.

5 Choose to modify an existing configuration, click the Edit Configuration

button.

6 Select the Disk(s) item in the Selected Arrays pane under the array that you

wish to expand.

7 Select one or more drives in the Available Drives pane to add to the selected

array item and click the “<<” button to add them to the array. Use the

<Control> key to make multiple selections.

You will notice the total size of the array and the Free Space size increased as

the disk(s) were added.

Increasing the Capacity (Expanding Array Size or Expanding Partition Size) 123


124


Expanded Partition

8 Select the partition immediately preceding the new “free space” and change

the size value to all or a portion of the new “free space.”

9 Click the Expand Partition button.



11 (If necessary) Use the procedures to create partitions, to recreate any

partitions that were removed or delete if this process was used.

NOTE: You can monitor the status of the expansion by double-clicking the

Progress icon in the Client View window.




Other Utility Operations

The following functions and procedures are described for operations that may be

used during normal operations, maintenance, or problem resolutions. The initial

steps of each procedure assume the position from sign on to the AdminiStor

Server, if you are already logged in, you may choose to skip these steps.

Changing Array Ownership

If you are using Active-Active mode, you can change the ownership of any array

between controllers.

You might want to change ownership if you plan to replace or repair one

controller. Changing ownership allows you to continue using an array without

interruption and makes the array visible on the controller you change it to. You

can no longer see the array on the original controller that owned the array.

NOTE: When you change the ownership of an array, the LUNs assigned to the

array’s partition become invalid. After changing ownership, you must

assign a new LUN to each array partition.

To change array ownership:


page 52.


3 Double-click the array under the controller you wish to change owners.

Changing Array Ownership

Other Utility Operations 125


126


4 Click the “Switch Array Owner” button.

You will receive a confirmation message, click YES to proceed or NO to

cancel.

5 Change the LUN for each partition of the arrray, refer to “Changing A

Partition LUN” on page 117.

Trusting an Array

You can use the Trust Array function to bring an array back online by

re-synchronizing the time and date stamp and any other metadata on a bad disk.

This makes the disk an active member of the array again. You might need to do

this when:

� One or more disks of an array start up more slowly or were powered on

after the rest of the disks in the array. This causes the date and time stamps

to differ, which the controller interprets as a problem with the “late” disks.

In this case, the array will function normally after using Trust Array.

� An array is offline because a drive is failing, you have no data backup, and

you want to try to recover the data from the array. In this case, the Trust

Array function may work, but only as long as the failing drive continues to

operate.

Before you can use this function, your array must be offline. When the array is

offline the “Trust Array” button becomes active.

CAUTION: It is highly recommended that you immediately backup your data

when the array is brought online using the Trust Array feature.

Afterwards, you can troubleshoot the problem through the log files.

WARNING: The Trust Array feature can cause unstable operations and data loss

if used improperly. This allows possible corrupt data to be seen by

the host system. This feature is intended for disaster recovery.

To trust an array:


page 52.


Trusting an Array



3 Double-click the array under the controller that is offline; indicated by a “red

‘x’” icon adjacent to the array icon.

Trusting an Array

4 Click the “Trust Array” button.

5 You will receive a confirmation message, click OK to proceed to force the

array online or trust the array or Cancel.

Trusting an Array 127


128


Synchronizing Time

The Synchronize Time feature allows the user to set the controller(s) date and

time based on the host system computers date and time setting. When using the

VT-100 terminal method, the user must manually enter the date and time. In

AdminiStor, a single-click button (Synchronize Time) is provided to set the time

automatically based on the host computer’s time/date.

To set the controller time:


page 52.

2 Click on the Session menu and choose Client View, then select Physical.

3 Double-click the controller icon.

It is not necessary to select one or the other controller (Active/Active or

Active/Passive operations), since the time is automatically set on both

controller.

Controller Panel – Synchronizing Time (Information Tab)

4 Click the Synchronize Time button.

5 You will receive a confirmation message, click YES to proceed with

synchronizing the time, or NO to cancel.

Synchronizing Time



Kill Other Controller

In an Active-Active configuration, you can force (non-gracefully) the other

controller offline, which will cause the current controller to assume control of the

other controller’s arrays.

CAUTION: You should only use the Kill Controller option as a last resort to

regain control of the other controller. Use of “Kill Controller” may

disrupt host I/O activity. If the other controller needs to be taken

offline, you should either try a local shutdown or use the “Shutdown

Both” controller option first.

To kill the other controller:


page 52.


3 Double-click the controller icon which is not representing the controller you

wish to kill or force offline.

In the Controller panel – Information tab will display the controller which is

the currently selected controller and its partner. Clicking the Kill Controller

button will force offline the partner controller.

Controller Panel – Kill Controller (Information Tab)

Kill Other Controller 129


130


4 Click the Kill Controller button.

5 You will receive a confirmation message, click YES to proceed with killing

the other controller, or NO to cancel.

To unkill the other controller:


page 52.


3 Double-click the controller icon which is not representing the controller you

killed or forced offline.

In the Controller panel – Information tab will display the controller which is

the currently selected controller and its partner. Clicking the Unkill Controller

button will failback the partner controller.

Controller Panel – Kill Controller (Information Tab)

4 Click the Unkill Controller button.

5 You will receive a confirmation message, click YES to proceed with unkilling

the other controller, or NO to cancel.

Kill Other Controller



Changing the Operating Mode

You can change the controller’s operating mode: In a dual controller configuration

(Active-Active or Active-Passive mode), a change to either controller’s setting is

immediately sent to the other controller, unless you change to a Stand-Alone mode.

CAUTION: When using any dual port mode, the host operating system and

drivers must support dual port accesses. If the host system does not

support dual port access, do not configure the controller in dual port

mode, because the operating system may believe that a single LUN is

really two independent arrays, resulting in possible data corruption.

Host Channel Setting Description

Stand-Alone Single Port This option allows the controller to operate as one of two controllers in an Active-Active pair. Active-Active mode allows two controllers to cooperate in system operation in a fault-tolerant manner. If one controller fails while in Active-Active mode, the other controller assumes its activities, allowing host access to continue.

Stand-Alone Dual Port This option allows the controller to operate with two host ports. In this mode, the same LUNs display on the two separate host ports. Stand-Alone Dual Port mode allows the host to achieve greater throughput by balancing I/O operations across the two host ports. Host port fault tolerance is also achieved, because the host can continue to access the controller if one host channel fails.

Active-Active Single Port This option allows both controllers to operate independently and as in an active-active pair. Active-Active modes allow two controllers to cooperate in system operation in a fault-tolerant manner. If one controller fails while in Active-Active mode, the other controller assumes its activities, allowing host access to continue.

When both controllers are online, each controller presents its LUNs on only one port.

Active-Passive Dual Port This option allows you to use just one controller with the second controller acting only as a backup in case of a failure of the controller in use.

When you change to this mode on one controller, you must reboot both controllers at the same time. After rebooting, both controllers will automatically be in Active-Passive Dual Port mode.

Changing the Operating Mode 131


132


To change the operating mode:


page 52.


3 Double-click on a controller icon that represents the controller to which you

wish to make changes.

Controller Panel – Change Operating Mode (Parameters Tab)

4 Click the Parameters tab.

5 Click the Operation Mode pull-down menu and select the desired operating

mode.

6 Click the Apply button.

7 You will receive a confirmation message, click YES to proceed change the

operating mode, or NO to cancel.

Changing the Operating Mode



Clearing Metadata from a Drive

All of the member drives in an array contain metadata in the first sectors of the

drive. The controller uses the metadata to identify array members after restarting

or changing controllers.

You can clear the metadata from a drive if you have a drive that was previously a

member of an array. Drives in this state display Leftover in the Display Drives

screen. After you clear the metadata, you can use the drive in an array or as a spare.

To clear metadata from a drive:


page 52.


3 Double-click on a disk device icon to which you wish to remove metadata.

Disk Device Panel – Clear Metadata

4 Click the Clear Metadata button.

5 You will receive a message indicating the metadata was cleared successfully,

click OK to proceed.

Clearing Metadata from a Drive 133


134


Adding a Hot Spare

Dedicated spares are unused disk drives that you assign as a spare to a specific

array. The disk must be as large as the smallest member of the array. You cannot

use a dedicated spare drive in an array as a pool spare.

Although using a dedicated spare is the most secure way to provide spares for

your arrays, it is also expensive to keep an idle drive assigned to each array. An

alternative method is to assign one or more idle drives to the spare pool. See

“Adding A Pool Spare” on page 118.

You assign dedicated spare drives to a specific array. If a member drive in the

array fails, the controller uses a dedicated spare drive to automatically reconstruct

the array. You can add dedicated spare drives to mirrored (RAID 1 and RAID 10)

and parity (RAID 3, RAID 4, RAID 5, and RAID 50) arrays when you create the

array or afterward. You can assign up to four dedicated spare drives to an array.

CAUTION: A spare cannot be added that does not have enough capacity to

replace the smallest member in the array.

To add a dedicated spare:


page 52.


3 Start the RAID Wizard. Double-click the Controller icon that you wish to


screen will appear.


appears.

5 Choose to modify an existing configuration, click the Edit Configuration

button.

6 Select the Dedicated Spare item under the Array tree you wish to assign it to

in the Selected Arrays pane.

Adding a Hot Spare



Selecting Dedicated Spare Item

7 From the Available Drives pane, select a drive and click the “<<” button

which adds the drive as a dedicated spare. (When selected, the drive

identification string will change from blue text to red text.)

Dedicated Spare Added

Select Dedicated


Spare

Dedicated SpareAdded

Adding a Hot Spare 135


136





Cancel button.




Viewing Array Information

You can view information and the current status of an array which includes the

following:

� State – Online, Offline, Critical, or Fault-tolerant.

� Serial number – Unique number the controller assigns to each array.

� Name – Is the name you give to the array.

� RAID level – Array type (0, 3, 4, 5, 50, Volume, or Mirrored). The term

“mirrored” is used for both RAID 1 and RAID 10 arrays.

� Number of drives – Is the number of drives in the array when fault-tolerant.

For example, if you create a three-drive RAID 5 array and lose one drive,

the number will still display 3.

� Number of drives per sub-array – For RAID 50 only; number of drives in

each underlying RAID 5 array.

� Number of spare drives – Number of spare drives dedicated to this array.

� Size – Is the size of the entire array.

� Chunk size – Array’s chunk size.

� Date created – Is the date the array was created.

� Utility – Is the utility running (None, Verify, Reconstruct, Expand, or

Initialize).

� Number of partitions – Number of partitions created on the array.

� Free partition total – Amount of free space (no partition) on the array.

To view the status of an array:


page 52.


Viewing Array Information



Logical View Window

3 Double-click the Array icon under the Controller icon to which you wish to

view information.

Logical Drive Panel (Array)

4 After reviewing the information displayed, click the Close button.

Double-click Array

Array Information

Array Status

Array Capacity Used

Function ControlButtons

Viewing Array Information 137


138


Verifying the Array

The Verify function allows you to verify the data on the selected array (RAID 3,

RAID 4, RAID 5, RAID 50, and mirrored arrays only):

� RAID 3, RAID 4, RAID 5, and RAID 50 – Verifies all parity blocks in the

selected array and corrects any bad parity.

� Mirrored – Compares the primary and secondary drives. If a mismatch

occurs, the primary is copied to the secondary.

You may want to verify an array when you suspect there is a problem.

To verify an array:


page 52.


3 Double-click the Array icon under the Controller icon to which you wish to

verify.

4 Click the Verify Array button.

Logical Drive Panel – Verify Array

5 You will be prompted to restore array if errors are found during the verify.

Click the YES button to continue and restore the array, NO to perform the

verify but choose not to restore the array, or CANCEL to close without

executing the operations.

Verifying the Array



6 You can monitor the condition by noting the Status has changed to

“Verifying...” or close the Logical Drive Panel and access the Client View –

Progress window, then double-click the Verify in Progress icon.

7 Click the Close button when you have finished.

Viewing Drive Information

You can view information and the current status of a disk drive which includes

the following:

� Drive information – This includes drive vendor, model, firmware version,

and serial number,.

� Channel number – Back-end disk bus number.

� ID - SCSI ID.

� Smart Technology – Indicates whether the drive supports SMART

technology.

� Array Information - Includes the array number and the drives’ position in

the array.

� Drive State – Which includes the Bus Speed, size, and its status.

� Status – If a member of an array, this displays the array name and member

number. If a spare, this displays the type of spare. If unused, this displays

Available. If the drive was part of an array that no longer exists, this

displays Leftover.

NOTE: If a drive has failed or malfunctioned, it may not be listed.

To view drive status:


page 52.


3 Double-click the Drive icon to which you wish to examine.


Viewing Drive Information 139


140


Viewing Drive Status from Controller Channels

You can also view disk device information and the current status of a disk drive

from the Drive Channel panel. Refer to “Drive Channel Panel” on page 63.

Locating a Disk Drive

You can blink the disk drive’s Activity LED in the storage enclosure to assist in

identifying a drive. The LED will blink three times, stop blinking, and then blink

three more times.

To blink the disk drive’s Activity LED:


page 52.


3 Double-click the Drive icon to which you wish to locate.

Disk Drive Panel – Locating Disk Drive

4 Click the Locate button.

5 Examine the storage enclosure front panel for the blinking LED.

It may take a few attempts to locate the drive if there is considerable activity

on that particular drive since the Activity LED will be flashing indicating

activity.


Viewing Drive Status from Controller Channels



Downing a Disk Drive

The Down Drive function sets the status of a disk drive in a fault-tolerant array to

“dead.” This forces the controller to remove the drive from the array and marks

the array as critical. At this point, you will be unable to down any additional

drives in the array.

To make the drive display again, you must use the “Rescan” function. After you

rescan, you must clear the metadata from the drive before you can use it in an

array or as a spare.

To take down a disk drive:


page 52.


3 Double-click the Drive icon to which you wish to take down.

Disk Drive Panel – Downing Disk Drive

4 Click the Down Drive button.

You will receive a confirmation request indicating the drive will be marked as

“dead.”

5 Click the OK button to down the drive, or CANCEL to exit the operation.


Downing a Disk Drive 141


142


Updating Controller Firmware

You can upgrade the firmware on the controller. Information regarding the latest

release of firmware and firmware updates is available on our support web site.

AdminiStor’s Flash Utility button is not the same as the Flash Utility provided

through VT-100 controller boot operation. AdminiStor’s Flash Utility button

allows the user to update the controller firmware and it prevents a situation with

dual controllers, where one controller has newly updated firmware and it is now

different from the other controller. Under this condition, the first controller to

boot senses the difference in firmware and kills the other controller. To prevent

this, AdminiStor employs a method that updates both controllers at one time.

Also, AdminiStor uses an in-band method to update the firmware by using the

SCSI bus rather than the RS-232 port.

You use the Flash Utility to download a new firmware file (.fla file) for your

controller.

If your controller is set to Active-Active/Active-Passive mode, you must stop all

I/O operations prior to updating the firmware.

To upgrade the controller’s firmware:


page 52.


You can also just double-click the domain name in the main GUI window to

open the Client View – Physical window.

3 Double-click on a controller icon that represents the controller to which you

wish to make changes.

In the Controller panel, any tab can be selected since the Flash Utility button

is located in the Function Control buttons located at the bottom of each panel

tab.




Controller Panel – Flash Utility

4 Click the Flash Utility button.

5 You will receive a confirmation request, that confirms you must stop all I/O

operations to perform this procedure. Click OK.

Confirmation Request

6 The Flash Utility window opens. Click the Browse button and locate the “.fla”

firmware file. The file must reside on a local disk (internal hard disk or floppy

disk drive), the utility cannot access a firmware file across a network drive.

Flash Utility Screen

Updating Controller Firmware 143


144


7 Click the Apply button to flash the firmware.

Flash Utility Screen with Firmware File Loaded

8 You will receive a confirmation message indicating the firmware update was

successful, click OK to continue.


Chapter 6


Monitoring and Notification

AdminiStor Plus provides advanced monitoring of the health and report the status of

your imageRAID SCSI Series Storage Systems. The monitoring includes E-mail

notification, activity status in a JDBC-compliant database, Event Logs (system logs),

GUI interface notifications, and SNMP traps to an NMS.

Monitoring

AdminiStor Plus monitors the status of all imageRAID SCSI Series Storage

Systems. It will also detect standalone SCSI disk drives like those found in the

JBOD enclosures attached to the host platform and displays them in the physical

tree.

Enclosure Services Monitoring (AdminiStor Plus Only)

AdminiStor Plus will monitor and report the status of the health of imageRAID

SCSI Series Storage Systems’ imageRAID controllers and the storage system

components (i.e., cooling fans, power supplies, audible alarms, enclosure

temperature sensors, and disk drives).

The GUI interface displays the status of each storage system component with a

green, yellow, or red icon status indicator. These icons are displayed adjacent to

each component object in the Client View – Physical tree.

145

Chapter 6 - Monitoring and Notification

146


To view the status of the storage enclosure components:

1 From the Main window in the browser, ensure that you are logged into the

specific Domain.

2 Select the System menu and choose Client View, then select Physical.

The AdminiStor Client View – Physical window is displayed.

Client View - Physical

3 Locate and double-click on the Enclosure Services icon.

The Enclosure Services window will appear (see the illustration on the

following page). A green, yellow, or red status icon will appear adjacent to

each component to indicate the status of the component.

Double-clickthe icon to open

the EnclosureServices monitoring

panel

Enclosure Services Monitoring (AdminiStor Plus Only)




4 After viewing the status of the components, click the Close button to exit this

window.

The Update Firmware button will allow the user to update the imageRAID SCSI

Series Storage Systems SES card firmware. This feature is not implemented in this

version release, refer to your storage system user’s guide for information about

updating SES/SAF-TE card firmware.

Controller Monitoring

You can view the status and monitor the performance of each imageRAID

controller. This is accomplished by accessing the Client View – Physical window

and viewing the Controller panel.

To monitor a RAID controller:

1 Click on the System menu and choose Client View, then select Physical.

Client View – Physical Menu Selection



Status Icon

Controller Monitoring 147


148


2 From the physical tree, double-click on the Controller icon that you wish to

view the status.

Client View – Physical (Accessing Controller Options)

The Controller panel will appear.



Controller panel)





3 Click the Environmentals tab to view the imageRAID Controller health status

and the enclosure component status information.

Controller Panel – Environmentals Tab

When the Environmentals tab is selected, only the Voltage and Temperature

data will be available. The enclosure section will be blank. That enclosure

information is found when you double-click the Enclosure Services icon, see

Enclosure Services Monitoring (AdminiStor Plus Only) on page 145.



150


In this panel, detailed information about the imageRAID Controller’s voltage

and temperature is displayed. You can also change the scale of the

temperature displayed for the iamgeRAID Controller from celsius to

fahrenheit by clicking the appropriate radio button.

NOTE: You can update the status of the selected controller you are viewing

by clicking the Scan button.

4 After you have reviewed the information, click the Close button to exit this

window.

To view details of the drives:

1 Click on the System menu and choose Client View, then select Physical.

Client View – Physical Menu Selection



2 Double-click on one of the Controller’s Drive Channel icon(s).

Selecting a Controller Channel

ControllerChannel Icon




The Drive Channel pane will appear.

Drive Channel Panel

Placing the mouse over any of the disk devices for a moment, it will display

a pop-up window with details on that disk device.

3 Click the Close button when you have finished viewing details of the drive

device.

Alternate method of viewing details of the drives:


page 52.


3 Double-click the Drive icon to which you wish to examine.

Disk Drive Panel – Viewing Information




152


Event Monitoring (System Log)

AdminiStor Plus monitors activity and performance of all devices and controllers

attached to the server. When an identified activity occurs which results in an

“event” (whether severe, such as a hard disk failure, or informational, such as

assignment of a drive to hot spare status), the event is sent to selected hosts.

Events are displayed in the AdminiStor Log. An “event” can be any of the

following:

� Error or warning condition in the storage system enclosure (such as a power, fan, or drive failure).

� Any administrative activity (taking a drive off-line, killing or rebuilding a drive).

To access the AdminiStor Log:

1 Click on the System menu and choose Log Tool. Then select the time period

from which you wish to view a history of events.

System Menu – Log Tool Selection

The AdminiStor Log is displayed.

AdminiStor Log

Event Monitoring (System Log)



2 Select the event you wish to inquire about, and double-click on its message

column item.

The Log Message window appears.

Log Message Window

You can view information about this event or cycle through the list of events

displayed by clicking the First, Previous, Next, and Last buttons.

3 To ensure the latest event list, click the Refresh button.

4 After you have finished viewing the details, click the Close button.

Event Monitoring (System Log) 153


154


Exporting the Log

The Export Log feature allows the user to save the AdminiStor Log to a comma

delimited file. This can be a useful tool when troubleshooting some types of

problems.

To export the AdminiStor Log:

1 Click on the System menu and choose Log Tool. Then select the time period

from which you wish to view a history of events.

The AdminiStor Log is displayed.

2 Select the Tools menu and choose Export Log.

Export Log Selection

3 The export Save dialog window will appear. Choose the Look in: pull-down

menu and choose the location to which you wish to save the file.

Enter a name for the file, or use the default name and click the Save button.

Exporting the Log



Saving Log File

You may use any third-party software program that supports the .csv file

format to view and manipulate the file contents.

Click the Cancel button to close the window without saving the file.

Exporting the Log 155


156


Exporting the Log

Appendix A


Glossary

Term Definition

Active-Active Mode In Active-Active mode, two controllers cooperate to provide redundancy. If one controller fails, the remaining controller will take over the failed controller’s functionality.

Active-Passive Mode In Active-Passive mode, one controller enables both its host ports and presents all LUNs on both ports. The other controller keeps both its host ports passive, and does not service any LUNs. Both controllers monitor each other’s heart beats and the passive controller receives write data and parity logs from the active controller.

BBU See “Battery Backup Unit” on page 157.

Bad Block Table (or Bad Data Table)

There are two bad-block tables that the controller automatically maintains: The Rebuild Bad Block Table stores information on bad blocks encountered during a rebuild or consistency check process. The Write-Back Bad Block Table stores information on all irrecoverable write-back errors that occur. AdminiStor provides an Error Table in which you can see Bad Block Data and Request Sense Data.

Battery Backup Unit A Battery Backup Unit is an add-on module that provides power to an the imageRAID Controller cache memory in the event of a power failure. The battery backup module monitors the write back cache on the controller, and provides power to the cache if it contains data not yet written to the drives when power is lost.

Cache Controller memory used to speed up data transfer to and from a disk.

Cache Flush Refers to an operation where all unwritten blocks in a Write-Back Cache are written to the target disk. This operation is necessary before powering down the system.

157

Appendix A - Glossary

158


Cache Line Size The Cache Line Size function, available in Controller Options or Manual Configuration, is set in conjunction with stripe size and represents the size of the data “chunk” that will be read or written at one time. The cache line size should be based on the stripe size you selected.

Channel Refers to one bus on the imageRAID Controller. Each controller provides at least one channel, and additional channels with optional upgrades.

Chunk Size The chunk size is the amount of contiguous data that is written to an array member before moving to the next member of the array. This is also know as stripe size.

Consistency Check Refers to a process where the integrity of redundant data is verified. For example, a consistency check of a mirrored drive will make sure that the data on both drives of the mirrored pair is exactly the same. For RAID Level 5 redundancy, a consistency “connect” is a function that allows a target device (typically a disk drive that received a request to perform a relatively long I/O operation) to release the bus so that the controller can send commands to other devices. When the operation is complete and the bus is needed by the disconnected target again, it is “reconnected.”

Critical: A Logical Drive is in a “critical” state if...

It has been configured at RAID level 1, 3, 5, or 0+1; andOne (and only one) of its member drives is not “online.”A logical drive is considered “critical” because any failure of another of its member drives may result in a loss of data.

NOTE: I/O operation can only be performed with logical drives that are online or critical.

Dead: A disk drive is in a “dead” state if it...

Is not present; or

If it is present but not powered on; or

If it failed to operate properly and was “killed” by the RAID Controller.

When the controller detects a failure on a disk, it “kills” that disk by changing its state to “dead.” A drive in a dead state does not participate in any I/O activity. No commands are issued to dead drives.

Disk Failure Detection The controller automatically detects disk failures. A monitoring process running on the controller checks, among other things, elapsed time on all commands issued to disks. A time-out causes the disk to be “reset” and the command to be retried. If the command times out again, the disk could be “killed” (taken “offline”) by the controller (its state changed to “dead”).

Term Definition

Glossary



Disk Media Error Management

The RAID Controllers transparently manage disk media errors. Disks are programmed to report errors, even ECC-recoverable errors. When a disk reports a media error during a read, the controller reads the data from the mirror (RAID 1 or 0+1), or computes the data from the other blocks (RAID 3, RAID 5), and writes the data back to the disk that encountered the error. If the write fails (media error on write), the controller issues a “reassign” command to the disk, and then writes the data to a new location. Since the problem has been resolved, no error is reported to the system.When a disk reports a media error during a write, the controller issues a “reassign” command to the disk, and writes the data out to a new location on the disk.

Disk Array A disk array is a group of individual disk drives (preferably identical) that are logically tied to each other and are addressed as a single unit. In some cases this may be called a drive “pack” when referring to just the physical devices.All the physical devices in a drive array should have the same size, otherwise each of the disks in the group will effectively have the capacity of the smallest member. The total size of the drive array will be the size of the smallest disk in the group multiplied by the number of disks in the group. For example, if you have 4 disks of 400MB each, and 1 disk of 200MB in a pack, the effective capacity available for use is only 1000MB (4*200), not 1800MB

Dual-Active (Duplex) Mode

A method of interconnecting multiple RAID controllers that share a common set of drives. In addition to increasing overall performance, this method allows a surviving controller to take over resources of a failed controller. This “failover” process is transparent to the host.

Duplex Mode See “Dual-Active (Duplex) Mode” on page 159.

Error Table See ““Bad Block Table (or Bad Data Table)” on page 157”.

Failback In Active-Active mode, failback is the act of returning ownership of controller resources from a surviving controller to a previously failed (but now active) controller. The resources include disk arrays, cache data, and host ID information.

Failover In Active-Active mode, failover is the act of temporarily transferring ownership of controller resources from a failed controller to a surviving controller. The resources include disk arrays, cache data, and host ID information.

Term Definition

Glossary 159


160


Hot Replacement of Disks (“Hot Swap”)

The design of the RAID Controllers allows for the replacement of failed hard disk drives without interruption of system service. In the event of a drive failure on a properly configured system (where the data redundancy features of the controller are used), system service continues without interruption. A message is generated by the system to alert the system operator.When a replacement drive becomes available, the system operator can remove the failed disk drive, install a new disk drive, and instruct the controller to “rebuild” the data on the new drive, all without interrupting system operations.Once the rebuild is complete, the controller will be brought back into a fault tolerant state.

Host To LUN Mapping The Host To LUN mapping feature is intended for use in configurations in which multiple host computers attach to one or more RAID Controllers. This is also referred to as a Storage Area Network (SAN) configuration. The host to LUN mapping feature restricts host access to configured system drives. Access to a configured system drive is granted only to a single host or group of hosts. (3000F Only.)

Intelligent Battery Backup Unit

The Intelligent Battery Backup Unit (IBBU) is an add-on module that provides power to the RAID Controller cache memory in the event of a power failure. The battery backup module monitors the write back cache on the controller, and provides power to the cache if it contains data not yet written to the drives when power is lost.

JBOD Sometimes referred to as “Just a Bunch of Drives.” Each drive is operated independently like a normal disk drive, or drives may be spanned and seen as a single drive. This level does not provide data redundancy.

NOTE: The host operating system drivers and software utilities remain unchanged regardless of the level of RAID chosen. The controller makes the physical configuration and RAID level implementation transparent to the host operating system.

Logical Drives A logical drive is equivalent to a “system” drive. Logical drives are presented to the operating system as available disk drives, each with a capacity specified by the RAID Controller.

Logical Drive States The state of a logical (system) drive can be either ONLINE, CRITICAL, or OFFLINE. Notice that the same term “online” is used for both physical and logical drives.

Logical Unit Number (LUN)

A representation of a system drive (logical drive) on a given channel and target ID.

Term Definition

Glossary



LUN See “Logical Unit Number (LUN)” on page 160.

LUN Mapping (3000F Only)

LUN Mapping allows logical drives (or system drives) to be made available or unavailable on one or more host ports. The mapping is performed by assigning Logical Unit Numbers (LUNs) to logical drives. The LUN assignments are per host port and are independent of the assignments on other host ports.By not assigning a LUN to a logical drive on a particular host port, that logical drive is made inaccessible to that host port.

Management Information Base (MIB)

A MIB is a database of managed objects accessed by network management protocols. An SNMP MIB is a set of parameters that an SNMP management station can query or set in the SNMP agent of a network device.

Mirroring Refers to the 100% duplication of data on one disk drive to another disk drive. Each disk will be the mirror image of the other.

Online: A Logical Drive is in an “online” state if...

All of its member drives are “online” and available.

Offline: A Logical Drive is in an “offline” state if...

No data can be read from it or written to it.System commands issued to offline logical drives are returned with an error status: no operations can be performed on offline logical drives. A logical drive can be “offline” under one of two situations described below:

• It is configured with a redundant RAID level (1, 3, 5, or 0+1), and two or more of its member drives are not “online”; or

• It is configured at RAID level 0, JBOD, or in a spanned set (PCI only), and one or more of its member drives are not “online.”

Online: A disk drive is in an “online” state if it...

Is powered on; and

Has been defined as a member of a drive array; and

Is operating properly.

Other Controller In Active-Active mode, the opposite controller from the one currently being used (that is, not the local controller) is referred to as the other controller.

Ownership In an Active-Active configuration, a single controller has ownership of he following resources: arrays and dedicated spares. When a controller fails, the other controller assumes temporary ownership of its resources.

Pack See “Disk Array” on page 159.

Term Definition

Glossary 161


162


Parity See “Rotated XOR Redundancy” on page 163.

Physical Drive States Refers to a drive’s current operational status. At any given time, a drive can be in one of five states: READY, ONLINE, STANDBY, DEAD, or REBUILD.The controller stores the state of the attached drives in its non-volatile memory. This information is retained even after power-off. Hence, if a disk drive is labeled DEAD in one session, it will stay in the DEAD state until a change is made either by using a system level utility or after a rebuild. Each of the states is described below:

Pool Spare Pool spares are one or more disk drives set aside for redundant arrays that will automatically be selected to replace a failed drive, should that occur. These are different from hot spare drives where hot spares are assigned to a specific redundant array.

RAID RAID stands for Redundant Array of Independent Disks. Several different forms of RAID implementation have been defined. Each form is usually referred to as a “RAID level.” The basic RAID levels supported by the RAID Controllers are shown below.

The appropriate RAID level for a system is selected by the system manager or integrator. This decision will be based on which of the following are to be emphasized:

• Disk Capacity

• Data Availability (redundancy or fault tolerance)

• Disk Performance

RAID Controller The controller acts as a bridge between host channels and drive channels, and implements the RAID function. On the drive channels, the controller acts as an initiator. The host channel ports are implemented as target IDs, with logical drives presented as LUNs under the target IDs.

RAID Operation imageRAID Controllers use their host ports to connect to one or more Host Bus Adapters in one or more host computer systems.Each configured logical drive consumes a particular bus-target ID-LUN on the host system. Multiple sets of disk drives are connected to the controller via its drive channels.

In duplex, or Active-Active mode, two identical imageRAID Controllers are connected to the same hosts via their host ports, to the same drives via their drive channels, and to each other via a special hardware link for heartbeat sensing. This forms a redundant controller system. The two controllers work together handling data traffic and mirror their write data in each other’s cache memory. If one of the controllers fails or otherwise becomes non-operational, the surviving controller takes over its responsibilities with no loss of data.

Term Definition

Glossary



RAID Levels RAID Advisory Board-approved RAID levels (RAID 0, RAID 1, RAID 3, RAID 5) and several special RAID levels (RAID 0+1, RAID 00, RAID 10, RAID 30, RAID 50, and JBOD).

Level 0 Block “striping” across multiple drives is provided, yielding higher performance than is possible with individual drives. This level does not provide any redundancy.

Level 1 Drives are paired and mirrored. All data is 100% duplicated on a drive of equivalent size.

Level 3 Data is “striped” across several physical drives. Maintains parity information which can be used for data recovery.

Level 5 Data is “striped” across several physical drives. For data redundancy, drives are encoded with rotated XOR redundancy.

Level 0+1 Combines RAID 0 striping and RAID 1 mirroring. This level provides redundancy through mirroring.

Levels 00, 10, 30, and 50.

Multi-layer RAID levels which span RAID levels 0, 1, 3, and 5 by striping data across drive arrays (RAID Drives).

Rebuild: A disk drive is in a “rebuild” state...

While it is in the process of being rebuilt. During this process, data is regenerated and written to the disk drive. This state is sometimes referred to as “Write-Only”’ (WRO).

Rotated XOR Redundancy This term (also known as “parity” or “consistency data”) refers to a method of providing complete data redundancy while requiring only a fraction of the storage capacity of mirroring. In a system configured under RAID 3 or RAID 5 (which require at least three drives), all data and parity blocks are divided between the drives in such a way that if any single drive is removed (or fails), the data on it can be reconstructed using the data on the remaining drives. (XOR refers to the Boolean “Exclusive-OR” operator.) In any RAID 3 or RAID 5 array, the capacity allocated to redundancy is the equivalent of one drive.

SCSI Drive A disk drive equipped with a SCSI interface (sometimes referred to as a SCSI Disk). Each disk drive will be assigned a SCSI address (or SCSI ID), which is a number from 0 to 7 (0 to 15 under Wide or Ultra SCSI). The SCSI address uniquely identifies the drive on the SCSI bus or channel.

Simplex Mode See “Single Controller (Simplex) Mode” on page 163.

Single Controller (Simplex) Mode

A single controller attached to a set of drives that offers RAID functionality without the controller fault tolerance inherent in dual-active mode.

Term Definition

Glossary 163


164


Simple Network Management Protocol (SNMP)

SNMP is the Internet standard protocol, defined in STD 15, RFC 1157, developed to manage nodes on an Internet Protocol (IP) network.

Standard Disk Drive This term refers to a hard disk drive with SCSI, IDE, or other interface, that is attached to the host system through a standard disk controller.

Standby Replacement of Disks (“Hot Spare”)

The “Standby Replacement” (or “Hot Spare”) is one of the most important features the controller provides to achieve automatic, non-stop service with a high degree of fault-tolerance. The rebuild operation will be carried out by the controller automatically when a disk drive fails and both of the following conditions are true:

• A “standby” disk drive of identical or larger size is found attached to the same controller;

• All of the system drives that are dependent on the failed disk are redundant system drives, e.g., RAID 1, RAID 3, RAID 5, RAID 0+1.

NOTE: The automatic rebuild will only happen on the SAME controller, never across controllers.

During the automatic rebuild process, system activity continues as normal. System performance may degrade slightly during the rebuild process.

To use the automatic rebuild feature, you should always maintain a hot spare drive in your system. When a drive fails, the hot spare will automatically replace the failed drive and the data will be rebuilt. The system administrator can disconnect and remove the bad drive and replace it with a new drive. The administrator can then make this new drive a hot spare.

Stripe Order The order in which disk drives appear within a drive array. This order must be maintained to access the data correctly, and is critical to the controller’s ability to ‘Rebuild’ failed drives.

Stripe Size The stripe size is defined as the size, in kilobytes (1024 bytes) of a single I/O operation. A stripe of data (data residing in actual physical disk sectors, which are logically ordered first to last) is divided over all drive array disks.

Stripe Width The number of striped drives within a drive array.

Striping Refers to the storing of a sequential block of incoming data across multiple drives in a group. For example, if there are 3 drives in a group, the data will be separated into blocks and block 1 of the data will be stored on drive 1, block 2 on drive 2, block 3 on drive 3, block 4 on drive 1, block 5 on drive 2 and so on. This storage method increases the disk system throughput by ensuring a balanced load among all drives.

Term Definition

Glossary



System Drive Affinity See “LUN Mapping (3000F Only)” on page 161.

System Drives See ““Logical Drives” on page 160”.

Target A target is a device (peripheral) that responds to an operation requested by an initiator (host system). Although peripherals are generally targets, a peripheral may be required to at temporarily as an initiator for some commands (for example, SCSI EXTENDED COPY command).

Target ID A target ID is the ID of a device attached to a controller.

Topology A network topology refers to the physical layout of nodes on a network. Topologies range from local network topologies to WAN topologies. FC topologies include point-to-point, FC-AL, and fabric.

Trap In the context of SNMP, a trap is an unsolicited message sent by an agent to a management station. The purpose is to notify the management station of some unusual event.

Unconfigured: A disk drive is in a “unconfigured” state if it...

Is powered on; and

Is able to operate properly; and

Was NOT defined as part of any drive array.

Unkill In Active-Active mode, when a surviving controller removes the reset from the other controller, it unkills it. The other controller will reboot and attempt to come online.

Write Back Cache Refers to a caching strategy whereby write operations result in a completion signal being sent to the host operating system as soon as the cache (not the disk drive) receives the data to be written. The target drive will receive the data at a more appropriate time, in order to increase controller performance. An optional cache battery backup or an Uninterruptable Power Supply (UPS) can be used to protect against data loss as a result of a power failure or system crash during the time the data is only in the cache.

Write Through Cache Refers to a caching strategy whereby data is written to the drive before completion status is returned to the host OS. This caching strategy is considered more secure, since a power failure is less likely to cause loss of data. However, a write through cache results in a slightly lower performance.

Term Definition

Glossary 165


166


Glossary

Appendix B


Domains

As described in chapter 3 – Startup and Navigation, the Domains menu provides

administrator’s of AdminiStor Plus with the ability to customize the viewing and

managing of enterprise wide imageRAID SCSI Series Storage System. This is

accomplished through the creation of logical domains, which differs from the

physical domains.

The physical domain consist of a host system and it’s devices (i.e., host computer, controller, physical disks, enclosures, channels, logical drives (LUNs), etc.). It is the physical components that compose the host system.

The logical domain comprise a mixture of the physical attributes of the physical domains and can include components of other previously created logical domains. Once you have logged into the physical domains or logical domains, you can create a logical domain by choosing components of those physical domains which will be contained in the logical domain. Creating logical domains is useful when a user is responsible for devices on more than one physical domain. If you add all the devices in the physical domain they “own”, then they will only have to log on to one logical domain as opposed to the physical domain. This allows the user the ability to create customized domains by creating and performing a single login for a specific logical domain.

To maintain a proper topology, if a device is added to a logical domain but the “parent” of that device is not added, the parent will show in the Client View tree but no access is given to the Client View panel.

In this appendix we will describe using the Domains menu features to enable

you to create and manage customized logical domains.

167

Appendix B - Domains

168


Domains Menu

From this menu the user can access and log into the domains. You are provided the options to Open a connection to a specific domain (or a local system), open a connection to one of the Alive or All Known Physical Domains, refresh the current display, or Select All open domains. You can also Close, or Modify a domain, or Edit the names of the open domains.

Domains Menu

Viewing the Domain Map

This feature allows the administrator to view the domain map for a physical

domain and enable the creation of logical domains.

1 Establish a connection.

a Open your web browser and enter the IP Address or the host name

followed by “:9191” and press the Enter key. Once the connection is

established continue with step 2, or

b If the web browser is already started and the AdminiStor applet is loaded

you can re-establish a connection by clicking on the Session menu and

choosing Establish.

In the Connections Status window you will see the message “Session

with AdminiStor established.”

2 Click on the Domains menu and choose Physical Domains, then select Alive

or All Known.

Alive are domains that have actively been pinged by the AdminiStor Server,

and All Known are current and past domains that have been pinged by the

AdminiStor Server.

Domains Menu



Domains - Physical Domains Menu

You are then presented with the Password login dialog.

NOTE: You can log into more than one domain (physical or logical) at a

time.

Password Log In Dialog

You may also use the Domains Open menu choice and enter the domain ID

along with the password. Using the Alive or All Known option allows the

administrator or user with a pull-down menu listing all physical domains

seen.

NOTE: Refer to “Access Levels” on page 52 to review the different access

level rights and privileges. For setup and configuration you will need

to log into the domain with <Administrator> access level rights.

3 Click on the Access pull-down and choose <Administrator>.

4 Enter the password for the <Administrator> Access level and click Log In.

5 In the Domain Session window, select the domain to which you log into. Do

this by simply clicking on the domain name. Refer to “Components of the

AdminiStor GUI Window” on page 59.

Viewing the Domain Map 169


170


6 Click on the Domains menu and choose For Selection. Then select Modify.

You can also click with the right mouse button on the Domain in the Domain

Session window and select Modify.

Domains Menu

The Domain Map for that physical domain is displayed.

Domain Map Window

From this window you can scroll up and down to examine all the physical

components that compose the physical domain.

Viewing the Domain Map



Modifying Device Names

This feature allows the administrator to customize the names of the devices,

making it easier to identify specific nStor storage components. For example: if a

particular storage on this domain is located in accounting or engineering, you

may wish to name the storage system components based on their physical

location. Any changes made in the Domain Map window will be reflected in the

Client View windows.

1 Follow the procedures outlined in “Viewing the Domain Map” on page 168

to display the domain map.

2 Click on the Edit Names menu and click the box selection for Enable.

Domain Edit Names Menu

3 Select the device you wish to modify its name by clicking on the device

name within the Device column.

4 Press the <Space Bar> which will allow you to modify the name. Use the

mouse pointer and highlight the entire name.

5 Enter the desired name you wish to represent this device and press the Enter

key.

Continue editing the names of devices you wish to change.

Modifying Device Names 171


172


6 Click the Edit Names menu and choose Apply.

NOTE: If you make a mistake, you may click on the Edit Names menu and

choose the option to Restore Last or if you wish to cancel all changes

you have made choose Restore All.

7 Click the Close window button to exit.

NOTE: To verify your changes click the Systems menu and choose Client View

then select Physical. You will see the device name changes you have

made.

Selecting Devices

This menu option allows the administrator to make specific selections of devices

in the domain map.



2 Click on the Select menu and parameter of the devices by which you wish to

make selections.

Domain Select Menu

The choices are to select all devices with Administrator access, Operator

access, all devices, or all new devices found.

Selecting Devices



NOTE: New Devices are indicated when the AdminiStor database has

detected a device which was not in the database from a previous

scan. Therefore, if a new device is added you can quickly select

those devices through this menu selection. Logging out of the

domain and logging back in will clear the new device indications.

3 After you have selected the devices you may continue with creating a new

logical domain or copying/cutting the devices from this domain into another

domain. Refer to the next section.

Creating a Logical Domain

This option allows the administrator the ability to create customized logical

domains from the physical domains. In large managed networks this feature can

be beneficial to allow some user’s access to specific domain devices while

restricting them from other domain devices.



2 Select the device(s) you wish to include in the new Logical Domain.

Domain Map Window

Creating a Logical Domain 173


174


3 Click the Create New button at the bottom of the window.

New Logical Domain Dialog Window

4 Enter the new Domain ID, Domain Name, the Access Level, and the

Password. Click the Execute button.

Domain ID is similar to your user name (login ID) and Domain Name is

similar to your full name (or description). The Domain Name is displayed in

the Domain Session window.

If you change your mind, click the Cancel button.

CAUTION: The Domain ID is not shown anywhere for security reasons. Be

sure to make a hard copy list of the Domain ID names and their

passwords. When you wish to log into a Logical Domain, you will

be prompted for the Domain ID and you will need to refer to the

list you have made. There is no way to locate the names.


Creating a Logical Domain



Modifying Logical Domains

If you are logged into more than one Logical Domain, you can copy or move

devices across these Domains.

To modify a Logical Domain:



2 Select the device(s) you wish to copy or move to another Logical Domain.

3 Select the Copy To or Move To from the current Domain and add them to the

other Domain.

The “Copy To” will leave the device(s) in its original Logical Domain and put

a copy into the new Logical Domain, while the “Move To” will remove the

device(s) from the current Logical Domain to the new Logical Domain.

4 You will be prompted to select the Logical Domain to which you wish to

copy or move the device(s).

5 Click the Execute button. If you wish to cancel the operation, simply click the

Cancel button and close the Domain map window.

Modifying Logical Domains 175


176


Deleting a Device from a Logical Domain

This option allows the administrator the ability to remove devices from the logical

domains or the entire logical domain.


to display the domain map of the Logical Domain from which you wish to

remove devices.

NOTE: You can select multiple devices by using <Ctrl> or <Shift> keys.

2 Select the device(s) you wish to remove and click the Delete button at the

bottom of the window.

Domain Map Window

3 Repeat step 2 until you have completed removing all the desired devices.

NOTE: If you remove all devices from the logical domain, it will

subsequently remove the logical domain also.


Deleting a Device from a Logical Domain

Index


AAccess Levels 52Active-Active Mode 157Active-Active Single Port mode

defined 90, 131Active-Passive Dual Port mode, defined 90, 131Active-Passive Mode 157Adding a Hot Spare 134Adding A Pool Spare 118Adding Drives 107AdminiStor GUI 6AdminiStor Host Panel 67AdminiStor Plus Host 5AdminiStor Plus Modules 4AdminiStor Plus Server 5AdminiStor RCU 6AdminiStor Server Panel 67Administrator

Access level 53Alarm Mute 89Array

Force Online 126Ownership, Changing 125Trusting 126Verify 138

Array Information 136Array Types

maximum number of drives 95Array types

minimum number of drives 95Assisted Configuration 100Automatic Configuration 98

BBad Data Table 157Battery Backup Unit 157Battery Months Old 88Battery State 88Battery Status 88BBU 157

Buttons 55

CCache 157, 158Cache Flush 157Cache Line Size 158Cache Lock 90Changing A Partition Lun 117Changing Array Name 113Changing Array Ownership 125Channel 158Clearing Metadata 133Closing the Domain Connection 74Configuration Utility 6Configure Linux

Multi-LUN Support 34Consistency Check 158Controller Icon Panel (RAID Wizard) 68Controller LUN 92Controller Monitoring 147Controller Panel 62

Host Configuration Tab 92Information Tab 87

Create Array Backoff Percent 91Creating a Logical Domain 173Creating a Partition 114Cross-Reference Product vii

DDatabase

Overview 8Deleting a Device from a Logical Domain 176Deleting A Partition 118Deleting Array 113Disable Battery Option 89Disconnecting 75Disk Device Panel 64Disk drives

Maximum by array type 95Minimum by array type 95

177

178


Disk Failure Detection 158Disk Media Error Management 159Domains 167Domains Menu 56, 168Downing a Disk Drive 141Drive Channel Panel 63Drive Groups 159Drive Requirements for Specific RAID Levels 95Drive Smart 91Drive Write Back Cache 91drives

Maximum by array type 95Minimum by array type 95

Dual-Active Mode 159Duplex Mode 159Dynamic Spare Rescan Rate 91

EEditing Configurations 112E-mail

Configuration 77Setup 77

E-mail SetupPreferences 78

Enclosure Service Panel 65Enclosure Services Monitoring 145Encryption

Overview 8Entering RAID Wizard 96Environmental Auto Slot Flags 89Environmental Global Slot Flags 89Environmental Poll Interval 91Error Table 159Event Monitoring 152Events 152Exiting

AdminiStor Host 76AdminiStor Server 76

Expanding Array Capacity 120Expanding Array Size 121Expanding Partition Size 121Expanding the Array 121Expanding the Partition 123Exporting Log 154Exporting the Log 154External RAID Controller 162External RAID Operation 162External Target ID Control 89

FFeatures viFirmware

Updating, controller 142

Flash Utility 94, 142Force offline

Controller 129Force Online 126Function Control Buttons 55

Controller panels 94

HHelp Menu 59Host Channel Target ID 92Host Channels 92Hot Replacement of Disks 160Hot Spare 134

IIcons 72Increasing the Capacity 121Installation

Java on Red Hat Linux 46Linux 26Solaris 21Windows NT 12

Installing the FC HBA on Red Hat Linux v7.1 31Installing the HBA on Red Hat Linux v6.2 29Intelligent Battery Backup Unit 160Internal Hub 91

KKill Other Controller 129

LLinux Installation

Red Hat 44Locating a Disk Drive 140Log 152Logical Domain

Deleting a Device 176Logical Domains

Creating 173Modifying 175

Logical Drive Panel 68Logical Drive States 160Logical Drives 160Logical Mode 66Logical Unit Number 160LUN 161LUN Mapping 161

MManual Configuration 106Manual New Configuration 106Menubar 55Menus 55

Index


Metadata 133Mirroring 161, 162Modifying Device Names 171Modifying Logical Domains 175Modularized Kernel

Red Hat v 7.2 38Monitoring 145

Overview 7

NNavigating AdminiStor 55New Array 107Notification

Configuration 77Overview 7Preferences 77

Notification Menu 57

OOperating Mode 90

Changing 131Operating Modes

Changing 131Operator

Access level 52Options

AdminiStor Client View 69Connection Status 71RAID Wizard 70ToolTips 70

PPackage Selection

Windows 13Passive Ownership 61Physical Drive States 162Physical Mode 60Preferences

E-mail Setup 78SNMP Setup 81

Product Identification viiProgress Mode 69Pull-Down Menus 55

QQuitting AdmimiStor 75

RRAID 162RAID Levels 163RAID Wizard 68RCU 6Reboot 94

Reboot Controllers 94Recompile the Kernel

Red Hat Linux 6.2 27Redundant Path 61Removing AdminiStor

Linux 47Solaris 25Windows 20

reportERROR 81reportFAIL 82reportOK 81reportUNKNOWN 82reportWARNING 81Restore 94Rotated XOR Redundancy 163

SSaving Log File 155Scan 94SCSI Drive 163Security

Overview 8Selecting Devices 172SEP LUN 92Session Menu 56Setting Array Properties 108Setting the Partition Properties 109Setup

Linux 26Red Hat Linux Version 6.2 27Red Hat Linux Version 7.1 31Solaris 22Windows 12

Setup Overview 11Shutdown Both 94Shutdown Controllers 94Signature 80Signing On

Domain 53Simplex Mode 163Single Controller (Simplex) Mode 163SNMP Services

Overview 9SNMP Setup

Preferences 81Solaris Installation 22Spare

Dedicated 134Stand-Alone Dual Port mode

defined 90, 131Stand-Alone Single Port mode

defined 90Standby Replacement of Disks 164

Index 179

180


Starting AdminiStor 50Starting AdminiStor GUI 51Starting AdminiStor Plus Host 50Starting AdminiStor Plus Server 50Status Indicator Icons 73Stripe Order 164Stripe Size 164Stripe Width 164Striping 164Synchronizing Time 128System Drive Affinity 165System Log 152System Menu 58System Requirements

Linux 26Solaris 21Windows 12

TTarget ID 165Trusting an Array 126

UUninstalling AdminiStor

Windows 20Unkill Controller 130Unkill other controller 130Updating Controller Firmware 142Upgrading the Kernel

Red Hat Linux v7.1 31User Interface Icons 72Utility Priority 91

VVerifying the Array 138Viewer

Access level 52Viewing Array Information 136Viewing Drive Information 139Viewing Drive Status from Controller Channels 140Viewing the Domain Map 168

WWindows Menu 58Write Back Cache 165Write Back Cache Stats 88Write Cache 165Write Through Cache 165

Index



www.fel.fujitsu.com 91-9-94689001 (Y1) May 2004

Fujitsu Europe LimitedHayes Park CentralHayes End RoadHayes, Middlesex, England UB4 8FE44.208.573.4444

Documents

AdminiStor Storage Management Software Guide