IQstor Admin Guide

iQstor SAN Manager
Administrators Guide
Beta 1.0
August 2002
iQstor Networks, Inc.
P/N 800-006623 REV 1
Copyright 2002 iQstor Networks, Inc. All rights reserved.

This publication, the iQstor SAN Manager printed circuit board, and related documentation are protected by Federal copyright law,
with all rights reserved. No part of this product may be copied, photocopied, reproduced, stored in a retrieval system, translated,
transcribed or transmitted, in any form or by any means manual, electric, electronic, electromagnetic, mechanical, optical or otherwise, in whole or in part without prior explicit written consent from iQstor Networks, Inc.
Included software, including all files and data, and the magnetic media on which it is contained (the Licensed Software), is
licensed to you, the end user, for your own internal use. You do not obtain title to the licensed software. You may not sublicense,
rent, lease, convey, modify, translate, convert to another programming language, decompile, or disassemble the licensed software
for any purpose.
You may a) only use the software on a single machine; b) copy only the software into any machine-readable or printed form for
backup in support of your use of the program on the single machine; and c) transfer the programs and license to use by another
party if the other party agrees to accept the terms and conditions of the licensing agreement. If you transfer the programs, you must
at the same time either transfer all copies whether in printed or machine-readable form to the same party or destroy any copies not
transferred.
Limitation of Liability
Information presented by iQstor Networks, Inc. in this manual is believed to be accurate and reliable. However, iQstor Networks,
Inc. assumes no responsibility for its use. No license is granted by implication or otherwise to any rights of iQstor Networks, Inc.
Product specifications and prices are subject to change without notice.
Trademark References
iQstor and the iQstor logo are registered trademarks of iQstor Networks, Inc. The iQstor SAN Manager is a trademark of iQstor
Networks, Inc.
Sun Microsystems and Sun Workstation are registered trademarks of Sun Microsystems, Inc. Solaris, OpenWindows, and SPARCstation are trademarks of Sun Microsystems, Inc.
All SPARC trademarks, including the SCD Compliant Logo, are trademarks or registered trademarks of SPARC International, Inc.
UNIX is a registered trademark of AT&T.
Registered Rights Legend

Use, duplication, or disclosure by the Government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in
Technical Data and Computer Software clause at DFARS 52.227 7013 (Oct. 1988) and FAR 52.227 19(c) (Jun. 1987).
ii
iQstor 1000 Administrators Guide
Contents
Chapter 1
Using iQstor SAN Manager
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Understanding the iQstor Solution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Theory of Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Installing Middleware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Uninstalling Middleware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Manually Starting Middleware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Shutting Down Middleware. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Starting the Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
The Web Browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Logging Into the Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
SAN Manager Desktop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Main SAN Manager Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Keyboard and Menu Shortcuts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Toolbar. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
SAN Topology Layer Window Pane. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
The SAN Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
SAN Event Monitor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Becoming an Administrator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Logout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Changing Your Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
User Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Viewing User Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Configuring User Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
User Groups and Access Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Preferences. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Warning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Remote Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Polling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
SAN Discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Device Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
DISK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
iQ1000 User Guide
iii
Contents
RAID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
POOL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
VDISK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Snapshot. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
VDISK Access Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Local Mirror . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Remote Replication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
VDISK I/O Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ICM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Event Monitoring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Event Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Event Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Set Event Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
The Policy Definition Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Policy Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Upgrading Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Zoning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Zoning Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuring Zoning Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
The Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Creating Zones. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Power Management (iQstrip) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Power On/Off a Slot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Power Configure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Chapter 2
RAID Configuration Parameters and Maintenance
39
44
47
50
55
59
62
66
68
71
71
71
72
77
77
78
83
86
86
86
87
90
94
94
94
95
RAID Set Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

Choosing the RAID Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
LUN Verification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Chapter 3
Using the Command Line Interface
Online Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SCSI Port Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
RAID Set Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Spare Pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
BootUp. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Snapshot. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LUN Masking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LUN Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Remote Replication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Local Mirroring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SV Log. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SV Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SAN FS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Enclosure Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ICM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
iv
iQ1000 User Guide
103
103
104
105
111
112
116
121
123
125
126
127
128
129
139
142
Contents
Chapter 4
Using The ASCII Graphical User Interface
145
Connecting to the GUI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Navigating the ASCII GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Using Administration Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Reviewing Current RAID Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Creating a RAID Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Adding Disks to the RAID Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Changing the Host Interface SCSI ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Modifying a RAID Set. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Deleting a RAID Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuring a Spares Pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Adding a Disk to a Spares Pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Deleting a Disk to a Spares Pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Modifying Disk Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Viewing Drive Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
System Log Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Chapter 5
GUI Error Messages
146
146
146
147
148
150
152
153
153
154
154
154
154
156
157
159
iQ1000 User Guide
vi
iQ1000 User Guide
Chapter 1
Using iQstor SAN Manager

Overview
The iQstor SAN Manager application features a Web-based Graphical User Interface
(GUI) tool that provides simple point-and-click mouse operations to configure and
monitor your Storage Area Network (SAN).
iQstor SAN Manager enables you to view iQ1000 status, configure the system, and
perform repair or replacement procedures.
iQstor middleware is a daemon program running on the server to which the RAIDs/JBODs
are connected. Currently, iQstor middleware supports Windows, NT4.0, and Solaris 2.X
platforms. Other popular system support will be added in the near future.
Note: The iQstor Storage Management Software is one of three available interfaces for
system administration. See also Chapter 3, Using the Command Line Interface and
Chapter 4, Using The ASCII Graphical User Interface.
See FAQs (Frequently Asked Questions) at the end of this chapter for the answers to
common questions about the GUI.
Understanding the iQstor Solution

The iQstor Storage Management Software provides superior data management solution
with easy-to-use administration tools. Benefits are:
Friendly graphical user interface.
Operable locally from the host and remotely from an Internet/Intranet node.
Comprehensive implementation of iQstor management functionality.

Platform-independence (the GUI client may be run on any JDK1.1 supported Java
Virtual Machine [VM]).
Multiple iQstor devices and multi-user support.

Password protection.
Event LOG, E-mail warning notification, and SNMP event notification.
Online help
Chapter 1: Using iQstor SAN Manager

Overview
Network diagram
The diagram below illustrates a simple network with RAID, JBODs, Host and several GUI
Clients connected through a Network ( see Figure 1-1).
Figure 1-1.
Network Overview
Features
3-tier (client, logic and resource) management model

Java Swing user interface (JDK1.3)
SAN topology display
Device automatic discovery
Real time event monitor
Real time storage I/O statistics report
Real time warning notification (Email, Trap and Pager)
XML
In-band (SSMON) and out-band (SNMP/UDP) device management
RAID and SV (Storage Virtualization) operation support

Overview
Theory of Operation
Management software is based on a 3-tier model:
Applet (client)
Middleware (logic)
SAN device (resources) layer. Figure 1-2 shows the layers of the architecture.
View (Applet)
Client
Browser
Data/Model (Applet)
TCP
TCP
JAVA Applet Server
HTTP Server
Email / Trap / Pager
Middleware
Cached Data
Device Manager
Event Queue
Event Service
SNMP
SAN Devices
Figure 1-2.
RAID Switch
Warning
Service
UDP
ESP2
Software Architecture
Applet
The Applet comprises View Objects and Data/Model Objects. View is responsible for GUI
display and input, such as graphic framework, window management, keyboard/mouse
handler and more. Data/Model caches the latest SAN status in the format of Java Objects.
It is also responsible for transferring user request to middleware and parsing the return
back.
WWW explorer (with JRE1.4 support) is necessary for Applet downloading and
execution.

Overview
Middleware
Middleware comprises five software components: HTTP server, Applet server, device
manager, event service, and warning service.
The HTTP server is responsible for feeding WWW explorer with Applet byte-code.
The Device manager maintains device communication channels (SNMP and UDP),
submits commands to devices (RAID or JBOD), and updates cached data with device
replies.
Event service listens for traps and events coming from devices, and places them into
an event queue. It may also inform the device manager to take some action, like
refresh device status by device status change event.
Warning service periodically checks the event queue to see whether there are any
warning events. If so, corresponding warning messages are sent via email, SNMP
traps or pager messages.
The Applet server handles requests from Applet clients. Message format between
them is XML encoded and GZIP compressed.

Getting Started
Getting Started
This section shows you how to begin using the iQstor SAN Manager. It including: system
requirements, installing and uninstalling software, and manually starting and shuttingdown the middleware.
Requirements
System
Table 1-1.
System Requirements
Element
Specified Requirements
MC
Solaris 2.7/8 SAN Manager with modem setup
PC Client
Win2k/NT, Java Plug-in (JRE)v1.4.0_01, Netscape6.0/IE6.0 or above
PC Server
Win 2k/NT, Email server, SNMPc v5
Management Console (MC)
Solaris 2.7 or above.

At least 2 Megabytes of hard disk space.
Client
A www browser with JRE 1.4 (Java Runtime Environment) plug-in is necessary to run
the iQstor Manager. Netscape 6.1 or later includes the JRE 1.4.
There are three types of installation for Netscape:
Recommended
Full
Custom
You need to select either the Full or Custom option to install JRE 1.4.
Netscape 6.1 is available from ftp.iqstor.com for free.
Note: For other browsers (Netscape 6.0 or earlier or IE), you will need to install the
JRE 1.4 plug-in. You can pre-install it or install it in run-time. Java 1.4 plug-in can be
downloaded from the SUN web site.

Getting Started
Installing Middleware
The following procedure must be followed when installing the middleware software on the
Solaris platform (Solaris 7 and above).
1
Log in as root.
Download the latest software from: ftp.iqstor.com
Run #pkgadd -d IQSTiqsm and follow the steps to finish the installation.
After installation, the GUI files will be located in the /opt/IQSTgui/IQstor directory.
Uninstalling Middleware
The following procedure must be followed when uninstalling the middleware software
from the Solaris 2.X.
1
Log in as root.
Run #pkgrm IQSTiqsm and follow the steps to finish the uninstallation.
Manually Starting Middleware

Although the GUI middleware is automatically started after installation or with system
startup, you can manually start it and shut it down using the following commands:
Start with ESP2 support:

#/opt/IQSTiqsm/IQstor/IQstord/-esp2 1
#/IQstord
Start with ESP2 disabled:

#/opt/IQSTiqsm/IQstor/IQstord
shutdown
/opt/IQSTiqsm/IQstor/IQstord/guikill
Once the Middleware is started manually, a message will appear (see Figure 1-3) that
identifies which port the GUI is running on.
Figure 1-3.
GUI Start Message

Getting Started
Middleware Start-up Options

IQstord: (see Figure 1-4).
[-www WWW_PORT]
WWW service port # (Def: 8002)
[-service SERVICE_PORT]
iQstor SAN Manager service port # (Def: 8102)
[-udp UDP_PORT]
MC UDP communication port # (Def: 31926)
[-esp2 ESP2_PORT]
ESP2 UDP communication port # (Def: 31927)
[-zip on|off]
GZIP switch in communication (Def: ON)
[-ssmon on|off]
SSMON channel support switch (Def: OFF)
[-snmpch on|off]
SNMP channel support switch (Def: ON)
[-sannet SAN_SUBNET]
SAN subnet (e.g., 192.168.1)
[-fcclust on|off]
Enable FC clustering configuration (Def: OFF)
[-poolcache POOLCACHE_MB]
Default POOL cache size in MB (Def: 4)
[-bindretry RETRIES]
Socket binding retry times (Def: 1)
[-binddelay DELAY]
Socket binding retry delay time in seconds (Def: 15)
[-bindmore MOREPORTS]
Number of subsequent ports to bind (Def: 100)

Above 3 only effective to WWW_PORT and SERVICE_PORT.
[-envboxid on|off]
Use environment variable BOXID as enclosure ID (Def: ON)
Figure 1-4.
IQstord Start-up Options
Alternate Ways to Start the Middleware

You can also start middleware through other files besides "IQstord". These files are:
guistart
(== ./IQstord)
guiall
(== ./IQstord -ssmon on -snmpch on)
guissmon
(== ./IQstord -ssmon on -snmpch off)
guisnmp
(== ./IQstord -ssmon off -snmpch on)
guinull
(== ./IQstord -snmpch off -ssmon off)
Shutting Down Middleware

GUI middleware will be shutdown with MC system shutdown. To manually shutdown
middleware, follow the following procedure:
1
At the # prompt enter cd /opt/IQSTgui/IQstor
At the # prompt enter ./guikill
Note: If you want to shutdown middleware and delete all intermediate files (LOG file,
data file, etc.) at the same time, use ./guiterm instead.

Starting the Client
Starting the Client

To start the client you must begin by launching the iQstor SAN Manager.
The Web Browser

Your iQstor SAN Manager is launched through your Web Browser. Follow these steps to
launch your software:
1
Check to see that you are using the required browser (seeRequirements on page 5).
Type URL http://server IP Address:Port into the browser Address field. The iQstor
SAN Manager home page will appear (Figure 1-5).
Note: The actual Port Number is shown in Figure 1-3 on page 6. In some cases you may
have to add a slash "/" at the end of the link address.
Start
Button
Figure 1-5.
SAN System Administrator window (iQstor Home Page)

3
Click the Start button.

Figure 1-6 on page 9).
and the Login dialog window will appear (see

Starting the Client
Logging Into the Network

To Log in to the Network, follow these steps:.
Figure 1-6.
Login dialog window
Type a User Name in the User Name field.
Type a Password into the Password field.
Click the OK button.

The main SAN Manager window will appear as shown in Figure 1-7.
MiniView
SAN
Tree
SAN
Topology
Layout
SAN
Event
Monitor
Figure 1-7.
SAN Manager window

SAN Manager Desktop
SAN Manager Desktop

iQstor SAN Manager provides users with many features designed to help manage the
Storage Area Network efficiently.
Main SAN Manager Window

The main SAN Manager window is a three pane window, (Figure 1-7 on page 9) from
which management functions such as logging in, changing passwords, and viewing
information on devices in the current configuration. The three window panes are:
The SAN topology layout

The SAN tree
The Event Monitor
Note: It also offers a Mini View option that is super-imposed on the SAN topology pane.
Keyboard and Menu Shortcuts

All underlined letters in menus indicate a corresponding shortcut for that menu command.
Keyboard:
Menu:
10
Press <Alt>+<Underlined letter> to execute the menu command.

Press underlined letter in pull-down menu to open a sub-menu or
to execute the command.

SAN Manager Desktop
Toolbar
A shortcut toolbar is provided to increase speed of use and ease of operation. Toolbar
icons are dynamically changed (enabled or disabled, active or inactive) depending upon
the state of the object selected.
Device Properties
Configure Device
Show MiniView
Remove Device
Rename Device
Hide MiniView
Refresh Topology View

Arrange Topology
Save Topology
iQstor SAN Manager
Load Topology
Preferences
Manage Users
SAN Event Filter
View Online Users
Set New Password
Help Center
Logout
View Event Log
About iQstor SAN Manager
Figure 1-8.
SAN Manager Desktop Toolbar
Viewing toolbar button (icon) definitions
Place your cursor above the toolbar button. A pop-up message will appear indicating
the function of that button (see Figure 1-9).
Figure 1-9.
Toolbar Button Pop-Up Messages
Toolbar and button (icon) definitions can also be seen by using the status bar.
11

SAN Manager Desktop
Menus
The Main Menu Bar from the SAN Manager window provides options that help you
control and monitor your network. These menu options are described in Table 1-2.
Table 1-2.
Menus
Menu
Option
Hot Key
Description
Admin
Logout
Alt-L
Disables Admin control but does not drop

the session.
New Password
Alt-N
Provides a method of changing the

password.
Online Users
Alt-U
Provides a list of current online users and

information about them.
User Management
Alt-M
Provides a method to configure

Administration access user rights.
Exit
Topology
12
Disconnects Admin control and drops the

session.
Load
Ctrl-L
Brings up the last saved Topology Layer

view.
Save
Ctrl-S
Saves the current Topology Layer view.
Auto Arrange
F7
Sets up the Topology Layer into its default

presentation view.
Refresh
F5
Updates the current Topology Layer view.
Hide MiniView
F3
Causes the MiniView window to disappear

from view.
Show MiniView
F4
Causes the MiniView window to appear in

the SAN Topology Layer.

SAN Manager Desktop
Table 1-2.
Menus (continued)
Menu
Option
Hot Key
Description
Options
Configure
Ctrl-G
Allows you to set and/or modify device

parameters.
Remove
<Delete>
Allows you to remove off-line devices

from the SAN Topology layer.
Rename
Alt-R
Allows you to rename on-line devices

from the SAN Topology layer.
Properties
Alt-P
Allows you to view device properties.
Preferences
Ctrl-P
Allows you to set or modify global

parameters.
Event Filter
Alt-E
Allows you to set or modify event filters.
View Event Log
Alt-V
Allows you to view all previously logged

events.
Help
F1
Allows user access to Help Menu.
About iQstor
SAN Manager
Alt-Q
Displays software version and date.
Help
SAN Topology Layer Window Pane

In SAN topology, nodes are displayed in three columns according to their device type:
Host (HBA)
Switch
Enclosure
Node icon drag and drop

You may use drag and drop functionality to move nodes within a column. However, nodes
cannot be moved out of their designated column and into another column.
Save and Load

When you close the iQstor SAN Manager desktop, the SAN topology layout is saved
automatically and will be restored the next time SAN Manager starts up.
13

SAN Manager Desktop
To Refresh the Topology Layer Display

1
Select Topology->Refresh from iQstor SAN Manager frame menu, or right click in
the blank area of the device tree or topology area and select Refresh from the dropdown menu, or use the hot key F5.
Topology Layout Operations

To change the topology layout
1
Select device in the topology layer of the iQstor SAN Manager frame.
Drag and drop to change the position.
To save the current layout

1
Select Topology->Save from the iQstor SAN Manager frame menu, or right click in
the blank area of the topology layer and select Save from the drop-down menu, or use
the hot key Ctrl-S.
To manually restore the last saved layout

1
Select Topology->Load from the iQstor SAN Manager frame menu, or right click in
the blank area of the topology kayer and select from the Load drop-down menu, or
use the hot key Ctrl-L.
To get device status
14
Select Device on the topology layer of the iQstor SAN Manager frame.
Hold mouse over the selected object for a while. A tip window will appear.
Move the mouse to close the tip window.

SAN Manager Desktop
MiniView Inset Window

A MiniView inset window can be placed into the Topology Layer.
To show the MiniView window on the Topology Layer

1
Select Topology->Show MiniView from the iQstor SAN Manager frame menu, or
right click in the blank area of the topology layer and select Show MiniView from the
drop-down menu, or use the hot key F4.
To hide the MiniView window

1
Select Topology->Hide MiniView from the iQstor SAN Manager frame menu, or
right click in the blank area of the topology layer and select Hide MiniView from the
drop-down menu, or use the hot key F3.
To move the Mini View inset window

1
Click in the headline of the MiniView window and do not release the mouse button.
Then, drag the Mini View inset window to its new location and release the button.
The SAN Tree

The SAN Tree provides a simple way to access information about hardware components.
SAN Tree Components

The SAN Tree lists the following hardware components:
The Cabinet
Contains the enclosures and JBODs
The Enclosure
The iQ1000 storage system (max 15 disk drives per enclosure)
JBOD (just a bunch of disks)

Storage expansion chassis (max 15 disk drives per JBOD)
The Switch
Fibre Channel Switch
HBA (Host Bus Adapter)

The interface adapter connected to the host
Misc.
15

SAN Manager Desktop
SAN Tree Window Pane

The SAN Tree is displayed in the SAN Tree window pane (see Figure 1-10).
The SAN tree window shown

here contains three enclosures
Figure 1-10.
The SAN Tree Window Pane
Highlighting a component in the SAN Tree displays that component in the Topology
Layer window pane.
SAN Event Monitor

The SAN Event Monitor window pane displays a five column table. Information regarding
each event is displayed in each column.The table contains the following categories of
information:
Level
Source
Type
Time
Description
The Event monitor is shown in Figure 1-11 and Figure 1-12 on page 17.
16

SAN Manager Desktop
The Event Table

1
The Event Table shows the last 200 events.
Click column header to sort events by that column.
Move the column header splitter to resize column width.
Column Sort
1
Figure 1-11.
Column Sort - Ascending
Figure 1-12.
Click once in the desired column to enable customization. (All tables in the applet
support column sort)
Click a second time to change (customize) your sort Policy.
Column - Descending
Click a third time to disable your customized sort.
17

Becoming an Administrator
To begin using the iQstor SAN Manager, you must become an administrator. You do so by
using the login function. First you must start the client as shown previously in Starting
the Client on page 8.
Login
The procedure below shows you how to login as an administrator and then change your
password.
1
Click the Start button or choose Admin-> Login. The Login dialog window will
appear (Figure 1-13). The default User Name is administrator.
Figure 1-13.
Login dialog window
Type in the Administrator Password (the default admin password is null). When you
change it, you must input a non-null password, and click the OK button.
Note: Once you have logged in as Administrator, you can then change your password.
Logout
You can logout by using a toolbar shortcut icon or a file menu selection on the iQstor SAN
Manager desktop (see Figure 1-14).
Logout disables Admin control but does not drop the session.
Figure 1-14.
18
Logout Menu Option and Toolbar Icon

Changing Your Password

As an Administrator you may change the current password.
Note: For all built-in user names, the default password is NULL. When you create a new
password, you may not use NULL.
Setting a New Password

To change your password, follow these steps:
1
Choose Admin-> New Password from the drop-down menu, or click the toolbar icon
button, or use the hot key Alt-N. The Set New Password dialog window will appear as
shown in Figure 1-15.
Figure 1-15.
New Password dialog window
The User Name default is administrator, therefore no entry is necessary.
Enter your current password in the Old Password field.
Enter your new password in the New Password field.
Enter the new password again in the Confirm Password field.
Enter your User Title in the Description field.
Click the OK button to make the change and close the New Password dialog window.
19

User Management
User Management
This section describes how to manage users (to add, delete, or edit users), and defines the
different user groups and access levels. User Management includes:
Viewing the list of current and online users.

Configuring user accounts.
Defining user groups and levels.
Viewing User Lists

The iQstor SAN Manager allows you to view both Current Users (signed up but not
logged on), and Online Users (currently logged on to the network).
Current Users
To access the current user list, select Admin-> User Management, or use the hot key AltM. The Users dialog window will appear showing the current users (see Figure 1-16).
Figure 1-16.
Current User dialog window - Configure User window
Online Users
To get online user information, select Admin-> Online User, or use the hot key Alt-U.
The Online Users dialog window (Figure 1-17 on page 21) will appear showing the online
users that have logged on to the ntework.
20

User Management
Figure 1-17.
Online User dialog window - User Information window
Configuring User Accounts

In addition to viewing current and online users, you can add, delete, or modify a user
through the User Management dialog window (Figure 1-18).
Figure 1-18.
User Management dialog window - Configure User window
21

User Management
Adding a New User

To add a new user, follow these steps:
1
Select Admin-> User Management, or use the hot key Alt-M. The User Management dialog window will appear.
Click the Add button. The Add Users dialog window will appear (see Figure 1-19).
Figure 1-19.
Add User dialog window
Enter the name of the new user in the User Name field.
Enter a password in the Password field.
Enter the password again in the Confirm Password field.
Enter a description in the Description field.
Choose and click a group from the Group radio button .
Click Add button to add the new user and close the Add User dialog window.
Click the OK button to close the Users dialog window.
Deleting a User
To delete a user, follow these steps:
22
Select Admin-> User Management, or use the hot key Alt-M. The User Management dialog window (Configure User window) will appear (see Figure 1-18 on
page 21).
Select the line of user that is to be deleted.
Click the Remove button or right-click and select Remove. A confirmation dialog
window will appear.

User Management
Click OK to confirm you want to delete the user. The user is deleted.
Click OK to close the Users dialog window.
Editing a User
To edit a user, follow these steps:
1
Select Admin-> User Management, or use the hot key Alt-M. The User Management dialog window (Configure User window) will appear.
Select the line of user to edit.
Click the Change button. The Edit User dialog window will appear (see Figure 1-20).
Figure 1-20.
Edit User dialog window
Enter a password in the Password field.
Enter the password again in the Confirm Password field.
Enter a description in the Description field.
Check group from the Group radio box.
Click OK to apply your changes and close the Edit User dialog window.
Click OK to close the Users dialog window.

Note: Online Users cannot be deleted or edited.
23

User Management
User Groups and Access Levels

There are four built-in user groups.
Administrator
Planner
Doctor
Guest
Each group has access rights to at least one set of features. The Group Access Levels table
(see Table 1-3) displays which features are enjoyed by each group.
Table 1-3.
Group Access Levels
Access Features
View of SAN components,
topology, events, remote
diagnostic operation list.
iQstor SAN terminal.
iQstor SAN configuration.
iQstor power management,
User account management,
Device upgrade.
24
Guest
Doctor
Planner
Administrator

Preferences
Preferences
To enable certain options, global preferences must be set first.
Warning
There are three types of Warning Notifications: E-Mail, SNMP, and Pager.
To Enable Warning Notifications

1
Select Options->Preferences from iQstor SAN Manager menu, or use the hot key
Ctrl-P. The Preferences dialog will appear.
Select the Warning tab (see Figure 1-21).
Figure 1-21.
Preferences dialog window - Warning Tab window
25

Preferences
E-Mail
To define e-mail notifications
Refer to Figure 1-21 on page 25.
3
Check the Email Warning checkbox to enable warning Notification by Email.
Type E-mail server name or IP address in the SMTP Server field.
Type E-mail recipient inthe Recipient field.
Type E-mail sender name in the Email Sender field.
Type E-mail account (to be authenticated with E-mail server) in the Email Account
field.
Type the account password in the Email Password field.
Type the duration to send a warning E-mail in the Interval field.
10 Click OK to make the setting and close dialog.
SNMP Trap Forwarding

To define SNMP trap forwarding
11 Check SNMP Warning checkbox to enable warning Notification by SNMP trap.
12 Type SNMP manager host name or IP address in the Recipient in field.
13 Type SNMP community in the Community field.
Pager Notification
To define pager notification
15 Check Pager Warning checkbox to enable warning Notification by Pager.
16 Select Serial Port (connected with modem to issue pager messages) from Serial Port
field drop-down menu.
17 Type Pager Number in the Pager Number field.
26

Preferences
Remote Support
There are several types of remote telephone support that are set in the preferences.
Call Home
To define remote diagnostics
1
Select Options->Preferences from iQStor SAN Manager menu, or use the hot key
Ctrl-P. The Preferences dialog window will appear.
Select the Remote Support tab (see Figure 1-22).
Figure 1-22.
Preferences dialog window - Remote Support tab
Check Auto Dialout checkbox to enable auto dialout support.
Type Telephone Number in Callback Phone field.
27

Preferences
Type Telephone Number in Home Phone field.
Type TCP Port Number in Home Port field.
Type User Name in Remote User field.
Type User Password in Remote Password field.
Type Domain in Remote Domain field.
10 Click OK to save the setting and close the dialog window.
Modem Setup
Currently SUN workstations only support external modems.
Define Modem:
1
Setting up the modem

If your modem is not Quantum Active 288UF plus (external, 28k),
edit file /etc/uucp/Dialers and change the modem initialization command.
Set modem to auto-answer mode.
Connect the external modem with one of the serial ports. Or insert the modem card to
the Sun workstation.
Run # admintool & on the Management Console and create the user as shwn below:
User
*****
Password
*****
Login Shell
/user/sbin/aspppls
Home Directory
/tmp2
Configure the Management Console shell scripts

# cd /opt/IQSTiqsm/IQstor
# ./guikill
# cd ./remote
# ./pppsetup.sh (if you ran ./pppsetup.sh before, please run ./unsetup.sh first).
Configure the serial port for dial out:
28
Run # admintool & on the Management Console
Select the Browser menu, and click Serial Port from the drop-down menu,
Select the Edit menu, and modify the following parameters from the drop-down
menu:
Template
Modem - Dial out Only
Baud Rate
9600
Click OK and close Admintool.

Preferences
Test Communications with the modem

9
If your modem is attached to the first serial port:

Type # tip /dev/cua/a
If your modem is attached to the second serial port:
Type # tip /dev/cua/b and the command should respond: connected.
10 If it responds: All ports busy, it means either that your serial port is configured incorrectly, perhaps for dial in instead of dial out, or that there is a more fundamental problem in communicating with the port. In this case, have a look at Celeste Stokely's
Tutorial on Solaris 2.x Modems & Terminals which contains a wealth of useful information about modems.
11 Type: ATZ and the modem should respond: OK
12 Type: ATS0=1 and the modem should respond: OK
13 If there is no response from the modem, check that you're using a straight-through
cable with pin 2 at one end connected to pin 2 at the other end, pin 3 to pin 3 and so
on. A "null-modem" or cross-over cable, designed for use with a terminal, will not
work.
Test dial-out to a normal telephone

14 Type ATDT followed by the telephone number.
For example, to dial out to a phone number 123-4567
Type: ATDT1234567
You should hear the local modem dialing, followed by audio tones. Then the phone you
dailed to rings and CONNECT string from the local modem should appear.
Connected or BUSY string appear if the phone you dailed to is online.
15 Quit from "tip" command and the modem is ready to send warning pages by MC.
29

Preferences
Polling
iQstor SAN Manager will automatically discover devices through SNMP channel. It will
discover devices in the default IP network segment or in the subnet defined in the -sannet
option when the middleware is started. However, it cannot find the Fibre Channel switch
until it knows the switch's IP address.
Setting Polling Preferences

1
Select Options->Preferences from iQstor SAN Manager menu, or use the hot key
Ctrl-P. The Preferences dialog will appear.
Select the Polling tab (see Figure 1-23)
Only Display
Online Devices
Enter the Fibre

Channel switch's
IP Address here
Figure 1-23.
30
Preferences dialog window - Polling Tab

Preferences
Enabling Switch Discovery (Identifying the FC Switch)

3
Check the Outband Discovery check box in the SAN Topology Discovery section.
Enter the IP address of the Fibre Channel switch in the Seed field.
Click OK to apply the setting and close the Preferences dialog.
The iQstor Storage Management Software cannot discover (find) the switch if SNMP
discovery is disabled or the IP address of switch is not specified.
6
Select Refresh from the Tool menu or the Refresh icon in the toolbar.
You can also simply right-click the blank area of the SAN tree panel to get a popup
Refresh menu option, or you can sinply use the hot key F5.
Note: The detected FC switch and HBA will be shown in the SAN tree as well as in the
topology layout of the SAN Manager window.
31

SAN Discovery
SAN Discovery
When you log in as an administrator, the iQstor SAN Manager automatically discovers
devices in the default IP network segment. The types of devices it can discover include:
Cabinets
Enclosures
JBODs
Fibre Channel Switches
Fibre Channel HBAs.
This section shows you how to verify that the iQstor SAN Manager is properly set up to
discover. Polling must be set up properly to enabled switch discovery.
Setting Polling to Discover Your SAN

By default, the iQstor SAN Manager automatically discovers devices through the SNMP
channel. To ensure the discovery functions properly, make sure that:
MC has only one home IP address, or MC has an IP addresss in B subnet (192.168.*.*

or 10.9.*.*).
The RAIDs IP address is in the same C subnet as the MC.

Enable Switch Discovery on the Preferences dialog window under the Polling Tab
(see Polling on page 30).
Discovering Your SAN

To discover your SAN, follow these steps:
32
Power-on the Fibre Channel switch and wait until it is fully up (this normally takes
several minutes).
Power-on the storage devices (RAID, JBOD).
Power-on and boot host.
Start iQstor SAN Manager and login as administrator.
The iQstor SAN Manager will discover devices in the default IP network segment
automatically. The detected FC switch, HBA and other devices will be shown in the
SAN Tree as well as Topology Layout (Figure 1-24 on page 33).

SAN Discovery
Figure 1-24.
iQstor SAN Manager Window (after discovery)
For a description of the features of the iQstor SAN Manager Window, including how to
view information on the devices, see Main SAN Manager Window on page 10).
33

SAN Discovery
Device Properties
To View Device Properties:
1
Select Device from the SAN device tree or Topology Layer in the iQstor SAN Manager frame.
Right click and select Properties from the drop-down menu, or select Options->
Properties from the frame menu, or use the hot key Alt-P. The Enclosure Properties
window will appear (see Figure 1-25 on page 34).
Figure 1-25.
34
Enclosure Properties Window
Click OK to close the Enclosure Properties window.

SAN Discovery
To Remove Device
1
Select device from the device tree or the Topology Layer in the iQstor SAN Manager
frame.
Right click and select Remove from the drop-down menu, or select Options->
Remove from the frame menu, or use the hot key <del> to remove a device. A confirmation dialog window will appear.
Click OK to close the confirmation dialog window and remove the device from the
SAN.
Notes:
Only offline devices can be removed.

Two devices may not have the same name.
To Rename Device
1
Select a device from the device tree or the Topology Layer in the iQstor SAN Manager frame.
Right click and select Rename from the drop-down menu, or select Options->
Rename from the frame menu, or use the hot key Alt-R to rename a device. The
Rename dialog window will appear.
Type the new name in the New Name field.
Click OK to make the change and close the Rename dialog window.
35

Configuration
Configuration
Table-style
Configure RAID enclosure is based on table-style. That means, you must select one or
more table rows before you can execute any functions. You can also sort tables by clicking
in the table header.
Toolbar Icons
In the device configuration frame, toolbar icons are dynamically changed (displayed or not
displayed, active or inactive) with the selection of different objects.
You can get icon definitions in the tips window or in the status bar.
Device
To Configure a Device
1
Select a device from the SAN Tree or TopologyLayer in the iQstor SAN Manager
frame.
Right click and select Configure from the drop-down menu, or select Options->
Configure from the frame menu, or use the hot key Ctrl-G. The Device Configuration Frame will appear.
Click the X button on the top right to close the frame.
Note:
Only the Enclosure configuration is supported at this time.
DISK
To View Physical Disks in an Enclosure
36
Select an Enclosure from the SAN Tree pane.
Select Options->Configure from the iQstor SAN Manager menu, or use the hot key
Ctrl-G. The Device frame will appear.
Select Enclosure->Storage->Disk from the device tree. The DISK table will appear
on the right panel (see Figure 1-26 on page 37).

Configuration
SAN Tree:
DISK Drive
Table
Figure 1-26.
The DISK Table
To Add a Spare Disk to the Spare Pool

1
Select an Enclosure from SAN frame.
Select Enclosure->Storage->Disk from object tree. The DISK table will appear on
the right panel.
Select a free disk from the table.
Select Configuration->Disk->Add To Spare from the Device menu, or click Add To

Spare button in toolbar, or right click and select Add To SPARE from the drop-down
menu (see Figure 1-27 on page 38).
37

Configuration
Figure 1-27.
A confirmation dialog window will appear (see Figure 1-28).
Figure 1-28.
.DISK Table - Add To Spare
Warning - Confirmation Add Disk window
Click Yes to close the confirmation window and add the spare disk.
To Remove a Spare Disk From the Spare Pool
38
Select Enclosure->Storage->Disk from the device tree. The DISK table will appear
on the right panel.
Select a spare disk from the table.

Configuration
Select Configuration->Disk->Remove From Spare from the Device menu, or click

the Remove From Spare button on the toolbar, or right click and select Remove
From SPARE from the drop-down menu (see Figure 1-29).
Figure 1-29.
DISK Table - Remove From SPARE
A confirmation dialog window will appear.
Click Yes to close the confirmation dialog and remove the spare disk.
RAID
To Create a RAID
1
Select an Enclosure from SAN Tree pane.
Select Options->Configure from the iQstor SAN Manager menu. The Device frame
will appear (see Figure 1-30 on page 40).
39

Configuration
Figure 1-30.
Select Configuration->RAID->Create from the device menu, or right click in the

Topology Layer and select Create from the drop-down menu. The Create RAID dialog window will appear (see Figure 1-31)..
Figure 1-31.
40
Device Table - Create RAID
Create RAID dialog window

Configuration
Select RAID level, Backends type and IO Size from the dialog window.
Click the Next button. The Select Backends window will appear (see Figure 1-32).
Figure 1-32.
Create RAID - Select Backends window
Select a Free disk and click the direction arrow (>) to move it to the Selected Backends list box, or click the double arrow (>>) to move all Free disks to the Selected
Backends list box.
Click the Finish button and wait until a summary of newly created RAIDs appears
(see Figure 1-33 on page 42).
41

Configuration
Figure 1-33.
Create RAID window - Summary
Click Close to close the Create RAID window.
To Remove a RAID
Only free RAIDs can be removed. When you highlight a free RAID, the corresponding
"Remove" toolbar icon and file menu will be activated.
42
will appear.
Select Enclosure->Storage->RAID from the object tree. The RAID table will appear
on the right panel (see Figure 1-34 on page 43).

Configuration
Figure 1-34.
RAID Table - Remove RAID
Select the RAID that you want to remove.
Select Configuration->RAID-> Remove from device menu, or click Remove button

in the toolbar, or right click and select Remove from the drop-down menu.
A confirmation dialog window will appear.

Click Yes to close the confirm dialog window and remove the RAID.
To Save the Current RAID Configuration file to disk

1
Click File->Configuration File from Enclosure management frame. The Configuration File dialog will appear.
Type file name in File Name filed or select file from File List table.
Click Save to save current configuration and close Configuration File dialog.
To Load the RAID Configuration From a Disk File

1
Click Load to load configuration from the file and close Configuration File dialog.
To remove configuration file
43

Configuration
Click Remove to delete the file from MC and close Configuration File dialog.
RAID Problems
To get RAID problem information
1
Select Tools->Problem List from the Enclosure Management frame or click the
Problem List button in the toolbar. The Problem List dialog window will appear.
POOL
To Create a POOL
1
Select an enclosure from SAN frame.
will appear.
Select Configuration->POOL->Create from device menu. The Create POOL wizard dialog window will appear (see Figure 1-35 on page 44).
Figure 1-35.
44
Create POOL window
Type POOL Name in the POOL Alias Name field, Select underlying RAID level
from Available RAID level list and chunk size from Available IO Size list.
Click Next button, and the Select RAID window appears (see Figure 1-36 on
page 45).

Configuration
Figure 1-36.
Create POOL - Select RAID window
Select a free RAID and click the direction arrow (>) to move it to the Selected RAID
list box. Click double arrow (>>) to move all free RAIDs to Selected RAID list box.
Click Finish, then wait for a POOL summary to appear (see Figure 1-37).
Figure 1-37.
Create POOL window - Pool Created Successfully
Click Close to close the wizard dialog window.
45

Configuration
To Grow a POOL
A free RAID with the same RAID level and I/O size can be added into an exisiting POOL:
1
will appear.
Select Enclosure->Storage->POOL from the object tree. The POOL table will
appear on the right panel (see Figure 1-38).
Figure 1-38.
46
POOL Table - Grow Pool window
Select the POOL that you want to grow.
Select Configuration->POOL->Grow from the device menu, or click the Grow button in the toolbar, or right click and select Grow from the drop-down menu. The
Grow POOL dialog window will appear (see Figure 1-38).
Select a RAID from the Available RAID list.
Click Grow to grow the POOL and close the dialog window.

Configuration
VDISK
To Create a VDISK
1
will appear.
Select Configuration->VDISK->Create from the device menu. The Create VDISK

dialog window will appear (see Figure 1-39).
Figure 1-39.
Create VDISK window
Select a POOL from Available POOL list box.
Select VDISK size from size spin box.
Click Create, then wait for a VDISK summary to appear (see Figure 1-40 on
page 48).
47

Configuration
Figure 1-40.
VDISK Summary window
Click Close to close Create VDISK dialog.
To Configure a VDISK
1
Select Options->Configure from the iQstor SAN Manager menu.The Device frame
will appear.
Select Enclosure->Storage->VDISK from the object tree. The VDISK list for the
selected enclosure will display on the right panel.
Select the VDISK that you want to configure.
Select Configuration->VDISK->Config from the device menu, or click the Config

button in the toolbar, or right click and select Config from the drop-down menu. The
Config VDISK dialog window will appear.
Type Group Name in the Group field.
Click Config button to make the change and close the dialog.
To Grow a VDISK
48
will appear.
Select Enclosure->Storage->VDISK from the object tree. The VDISK list of

Select the VDISK that you want to grow.
Select Configuration->VDISK->Grow from device menu, or click the Grow button

in the toolbar, or right click and select Grow from the drop-down menu. The Grow
VDISK dialog window will appear (see Figure 1-41 on page 49).

Configuration
Figure 1-41.
Grow VDISK dialog window
Select Grow Size (512M - 18944M) in the Size field.
Click OK button to grow the VDISK and close the dialog window.
To Remove a VDISK
1
will appear.
Select Enclosure->Storage->VDISK from the object tree. The VDISK list of

Select the VDISK that you want to remove.
Select Configuration->VDISK->Remove from the device menu, or click the

Remove button in the toolbar, or right click and select Remove from the drop-downmenu. A confirmation dialog window will appear.
Click Yes to close the confirmation dialog window and remove the VDISK.
To Repair a Disk
1
Select an Enclosure from the SAN frame.
Click Enclosure->Storage->DISK in the object tree. The DISK table will appear on
the right.
From the table, select the DISK to be repaired.
Select Configuration->DISK->Repair from the device menu, or click the Repair

button in the toolbar, or right click and select Repair from the drop-down menu. A
confirmation dialog window will appear.
Click YES to close the confirmation dialog window and start the repair.
49

Configuration
To Replace a Disk
1
Click Enclosure->Storage->DISK in the object tree. The DISK table will appear on
the right.
From the table, select the DISK to be replaced.
Select Configuration->DISK->Replace from the device menu, or click the Replace

button in the toolbar, or right click and select Replace from the drop-down menu. A
Click YES to close the confirmation dialog window and start the replacement.
Snapshot
To Create a Snapshot
1
Select Options->Configure from the SAN menu.The Device frame will appear (see
Figure 1-42).
Figure 1-42.
50
Device Menu - Configure Snapshot window
Select Configuration->Snapshot->Create from device menu. The Create Snapshot

window will appear (see ).

Configuration
Figure 1-43.
Create Snapshot window - Select Primary VDISK
Select a Primary VDISK from the dialog window.
Click NEXT button and Create Snapshot - Group Table will appear (see Figure 1-44).
Figure 1-44.
Create Snapshot window - Group Table
51

Configuration
Select the group you want the snapshot to belong to (see Figure 1-44 on page 51).
Click Close to close the dialog window, then wait and a Created Successfully message
will appear (see Figure 1-45).
Figure 1-45.
52
Creat Snapshot window - Created Successfully

Configuration
To Configure a Snapshot
1
Select an Enclosure from The SAN frame.
Select Options->Configure from the SAN menu. The Device frame will appear.
Select Enclosure->Data Services->Snapshot from the Enclosure tree on the left

panel of the device frame. The Snapshot list of the selected enclosure will display on
the right panel of the device frame (see Figure 1-46).
Figure 1-46.
Device Frame window - Configure Snapshot
Select the Snapshot that you want to configure from the Snapshot list.
Select Configuration->Snapshot->Config from the device menu, or click the Configure Snapshot button in the toolbar, or right click and select Configure Snapshot
from the drop-down menu. The Config Snapshot dialog will appear (see Figure 1-47
on page 54).
53

Configuration
Figure 1-47.
Snapshot dialog window
Type the Life Span you desire in the Hour and Min fields.
Type the Recreate Interval you desire in the Recreate Interval Hour/Min fields.
Type the Auto Grow Threshold you desire in the Auto Grow Threshold % field.
Select the Read radio button or the Read and Write radio button in the Permission
area of the dialog window.
10 Click OK to finish configuring the snapshot..
To Remove a Snapshot
54
Select Options->Configure from the SAN Tree menu. The Device frame will appear.
Select Enclosure->Data Services->Snapshot from Enclosure tree on the left panel of

the device frame. A Snapshot list of the selected enclosure will display on the right
panel of the device frame.
Select the Snapshot that you want to remove from the Snapshot list.
Select Configuration->Snapshot->Remove from the device menu, or click the

Remove button in the toolbar, or right click and select Remove from the drop-down
menu. A confirmation dialog window will appear.
Click Yes to confirm and remove the snapshot.

Configuration
VDISK Access Security

LUN Mapping
1
Select Options->Configure from SAN menu. The Device frame will appear.
Select Configuration->LUN Mapping->Create from device menu. The Create

LUN Mapping window will appear (see Figure 1-48).
Figure 1-48.
Create LUN Mapping - Select Host WWN window
Select a VDISK from the dialog window.
Select the Host from the list.
Select the Host from the HLUN list.
Click Finish button, and a message box of created mapping will appear.
Click Close to close the message dialog window.
To Remap a LUN Map

1
Select Enclosure->Access->LUN Mapping from the Enclosure tree on the left panel
of the device frame. The LUN Map list of the selected enclosure will display on the
right panel of device frame.
55

Configuration
Figure 1-49.
Select the LUN Map that you want to remap.
Select Configuration->LUN Mapping->Remap from device menu, or click the

Remap button in the toolbar, or right click and select Remap from the drop-down
menu. The Remap LUN dialog window will appear (see Figure 1-50 on page 56).
Figure 1-50.
56
LUN Mapping window - Remap
Remap LUN Dialog window
Select new LUN from the Host LUN list
Click Remap button to make the remapping and close the dialog window.

Configuration
To Remove LUN Mapping

1
Select Enclosure->Access->LUN Map from the Enclosure tree on the left panel of
the device frame. The LUN Map list of selected the enclosure will display on the
right panel of the device frame (see Figure 1-51 on page 57).
Figure 1-51.
Device Frame window - Remove LUN Mapping
Select the LUN Map that you want to remove
Select Configuration->LUN Mapping->Remove from the device menu, or click the

Remove button from the toolbar, or right click and select Remove from the dropdown menu. A confirmation dialog will pop up.
Click Yes to close the confirmation dialog and remove the LUN Mapping.
57

Configuration
LUN Masking
1
Select Configuration->LUN Masking->Create from the device menu. The Create

LUN Masking wizard dialog window will appear (see Figure 1-52).
Figure 1-52.
Create LUN Masking window
Select a RAID from the dialog, and click Next button.
Select Host WWN to be Masked with this RAID.
Click Finish button, and wait for short minute, a Message box of creating result will
appear, Click Close to close the windows.
To Remove LUN Masking
58
Select Enclosure->Access->LUN Mask from the Enclosure tree on the left panel of
device frame. The LUN Mask list of the selected enclosure will display on the right
panel of device frame (see Figure 1-53 on page 59).

Configuration
Figure 1-53.
Device Frame window - Remove LUN Masking
Select the LUN Mask that you want to remove from LUN Mask list.
Select Configuration->LUN Masking->Remove from the device menu, or click the

Remove button on the toolbar, or right click and select Remove from the drop-down
Click Yes to confirm and remove the LUN Masking.
Local Mirror
To Create a Local Mirror
1
Select Configuration->Mirror->Create from the device menu. The Create Mirror

wizard dialog window will appear (see ).
59

Configuration
Figure 1-54.
Create Mirror window
Select a Primary RAID from the dialog window and click the Next button.
Select a Target POOL from the dialog window.
Click the Finish button, and a Creating Results message box will appear. Click Cancel to close the dialog window.
To Suspend a Local Mirror
60
Select Enclosure->Data Services->Local mirror from tyhe Enclosure tree on the

left panel of the device frame. The Local mirror list of the selected enclosure will
display on the right panel of device frame (see Figure 1-55 on page 61).

Configuration
Figure 1-55.
Device Frame window - Suspend Local Mirror
Select the mirror that you want to suspend from the Mirror list.
Select Configuration->Mirror->Suspend from device menu, or click the Suspend

button on the toolbar, or right click and select Suspend from the drop-down menu. A
Click Yes to confirm and finish suspending the mirror
To Resync a Local Mirror

1
Select Enclosure->Data Services->Local mirror from the Enclosure tree on the left
panel of the device frame.The Local mirror list of the selected enclosure will display
on the right panel of device frame.
Select the mirror that you want to resync from the Mirror list.
Select Configuration->Mirror->Resync from the device menu, or click the Resync

button on the toolbar, or right click and select Resync from the drop-down menu. A
Click Yes to confirm and finish the re-synchronization of the mirror.

Note: Only a suspended mirror can be re-synchronized.
61

Configuration
To Reverse Resynchronization of a Local Mirror

1
panel of the device frame. The Local mirror list of the selected enclosure will display
on the right panel of the device frame.
Select the mirror that you want to reverse resync from Mirror list.
Select Configuration->Mirror->Reverse Resync from the device menu, or click the

Reverse Resync button on the toolbar, or right click and select Reverse Resync from
the drop-down menu. A confirmation dialog window will appear.
Click Yes to confirm and finish to reverse re-synchronization of the mirror.
Note: Only a suspended mirror can be reverse re-synchronized.
To Split a Local Mirror

1
panel of the device frame. The Local mirror list of the selected enclosure will display
on the right panel of the device frame.
Select the mirror that you want to split from the Mirror list.
Select Configuration->Mirror->Split from the device menu, or click the Split button
on the toolbar, or right click and select Split from the drop-down menu. A confirmation dialog window will appear.
Click Yes to confirm and split the mirror.
Note: The Split function does not remove the mirror VDISK. Use the VDISK Table to
remove the VDISK.
Remote Replication
To Connect a Remote Replication
62
Select Configuration->Remote Replication->Create from the device menu. The

Create Remote Replication wizard dialog window will appear (see Figure 1-56 on
page 63).

Configuration
Figure 1-56.
Create Remote Replication window
Select a Source VDISK from the dialog window and click the Next button.
Select a Destination Name, Destination WWN, Host LUN from the dialog window.
Select a Local Port from local port group.
Click Finish button, and a message box for connecting result will appear.
Click Close to close the dialog window.
To Start a Remote Replication

1
Select Options->Configure from the SAN menu The Device frame will appear.
Select Enclosure->Data Services->Remote Replication from the Enclosure tree on

the left panel of the device frame. The Remote Replication list of the selected Enclosure will display on the right panel of the device frame.
From the Remote Replication list, select the remote replication that you want to start.
Select Configuration->Remote Replication->Start from the device menu, or click

the Start button on the toolbar, or right click and select Start from the drop-down
menu. A confirmation dialog window will appear (see Figure 1-57 on page 64).
63

Configuration
Figure 1-57.
Warning Message - Confirm Start Destination
Click Yes to confirm and start the remote replication.
The Remote Replication window is shown in Figure 1-58.
Figure 1-58.
64
Remote Replication window

Configuration
To Suspend a Remote Replication

1

From the Remote Replication list, select the remote replication that you want to suspend.
Select Configuration->Remote Replication->Suspend from the device menu, or

click the Suspend button on the toolbar, or right click and select Suspend from the
drop-down menu. A confirmation dialog window will appear.
Click Yes to confirm and suspend the remote replication.
To Rejoin a Remote Replication

1

From the Remote Replication list, select the remote replication that you want to
rejoin.
Select Configuration->Remote Replication->Rejoin from the device menu, or click

the Rejoin button on the toolbar, or right click and select Rejoin from the drop-down
Click Yes to confirm and rejoin the remote replication.
To Split a Remote Replication

1

From the Remote Replication list, select the remote replication that you want to split.
Select Configuration->Remote Replication->Split from the device menu, or click

the Split button on the toolbar, or right click and select Split from the drop-down
Click Yes to confirm and start the remote replication.
65

Configuration
To Disconnect a Remote Replication

1

From the Remote Replication list, select the remote replication that you want to disconnect.
Select Configuration->Remote Replication->Disconnect from the device menu, or

click the Disconnect button on the toolbar, or right click and select Disconnect from
the drop-down menu. A confirmation dialog window will appear.
Click Yes to confirm and disconnect the remote replication.
To Configure a Remote Replication

1

the left panel of the device frame. The Remote Replication list of the selected Enclosure will display on the right panel of device frame.
Select the remote replication that you want to configure from Remote Replication
List.
Select Configuration->Remote Replication->Configure from the device menu. The

Configure Remote Replication dialog window will appear.
Type the Scoreboard Log in the Scoreboard Log field.
Type the Sync Time in the Sync Time field.
Type the Sync Time Interval in the Sync Time Interval field.
Click the Configure button to execute the configuration.
10 Click the Finish buttons to close the dialog window.
VDISK I/O Statistics

To View VDISK Statistics
66
Select Options->Configure from the SAN menu. The Device frame will appear (see

Configuration
Figure 1-59.
Device Table - VDISK Statistics window
Select Configuration->VDISK->Statistics from the device menu, or click the Statistics button on the toolbar, or right click and select Statistics from the drop-down
menu. The VDISK Statistics Monitor window will appear (see Figure 1-60).
Figure 1-60.
VDISK Statistics Monitor window
67

Configuration
Select VDISK from VDISK group.
Select Statistics Type from Statistics Type group.
View the Statistics graph.
ICM
The ICM function allows you to view the Partition List as well as a directory of the
contents of each partition.
To View the ICM Partition List.

1
Select Enclosure->ICM from Enclosure tree on the left panel of the device frame.
The ICM Partition List of the selected Enclosure will be displayed on the right panel
of the device frame (see Figure 1-61).
Figure 1-61.
ICM Table - Partition List
To View the Directory of ICM Partitions
68
Select Options->Configure from the SAN menu. The Device frame will appear (see

Configuration
Figure 1-62.
Device Frame- ICM Table - View the Directory
Select Enclosure->ICM from the Enclosure tree on the left panel of the device frame.
The ICM Partition List of the selected Enclosure will display on the right panel of
the device frame.
Select an ICM Partition from the ICM Partition List. Each row of the ICM table represents a single partition in a VDISK.
Right click on a selected row and select View the Directory from the drop-down
menu. The File Information window will appear (see Figure 1-63).
Figure 1-63.
The File Information window
69

Configuration
Controller Information
1
Open the Enclosure management frame.
Click Enclosure->Controller in the object tree. The Controller table will appear on
the right.
Terminal
1
Click Tools->Terminal from Enclosure management frame or click the Terminal

button in the toolbar. The Terminal dialog window will appear (see Figure 1-64).
Figure 1-64.
70
Terminal - Command Line
Type the appropriate command in the text field.
Click the Run button to execute the command.
Click the Clear button to empty the contents of the text area.
Click Close to close the Terminal dialog window.

Event Monitoring
Event Monitoring
Event Sources
There are two sources for reporting events:
IQstor SAN Management software itself

RAID enclosure
Event Level
There are three event severity levels:
Information
Warning
Fatal
Events are shown in UTC time (see the Event Monitor pane Figure 1-65).
Figure 1-65.
Event Monitor Pane of the SAN Manager window
71

Event Monitoring
Set Event Filter

Choose "Event Filter" from the iQstor SAN Manager "Option" menu to open the Event
Filter setting window (see Figure 1-66)
Figure 1-66.
Event Filter window
To Define the Event Filter
72
Click Options->Event Filter from the iQStor SAN Manager menu. The Event Filter dialog window will appear.
Check the Filter Enable checkbox in the dialog window.
Check the appropriate items in the Event Type and Event Category groups to determine which events are to be received.
Click OK to close the Event Filter dialog window.

Event Monitoring
Current Event Overview
Table 1-4.
Event Overview
Level
Source
Info
RAID Enclosure
Type
Controller powered down
Controller powered up
Controller rebooting
Controller SCSI ID changed
Controller takeover
Firmware upgrade begin
Firmware upgrade end
Hearbeat link broken
Controller ready
Sensor status changed
DISK plugged in
DISK pulled out
DISK Repairing
DISK replacing
SPARE added
SPARE removed
Manually DISK repair needed
Manually DISK replace needed
RAID created
RAID removed
RAID initialized
POOL created
73

Event Monitoring
Table 1-4.
Event Overview (continued)
Level
Source
Info
RAID Enclosure
Type
POOL removed
POOL modified
POOL grow
POOL configure recovered
VDISK created
VDISK removed
VDISK grow
VDISK modified
VDISK LUN map created
VDISK LUN map remapped
VDISK LUN map removed
VDISK LUN mask ON
VDISK LUN mask OFF
VDISK LUN mask created
VDISK LUN mask removed
VDISK ICM Threshold set
Warning
VDISK capacity warning

VDISK performance warning
VDISK ICM warning
Controller Warning
Temperature high
Temperature low
DISK performance warning
Failure
74
Power DC failure

Event Monitoring
Table 1-4.
Event Overview (continued)
Level
Source
Failure
RAID Enclosure
Type
Power AC failure
POOL failure
VDISK failure
Controller failure
Hearbeat failure
DISK data faulty
Info
iQSAN Manager
iQstor SAN Manager Report

User login
User logout
J1800/U1800 hardware changed
Warning
iQstor SAN Manager Warning

Cabinet AC slot lowload
Cabinet AC slot overload
J1800/iQ1000 warning
Cabinet warning
Failure
iQstor SAN Manager Failure

Device Not Responding
75

Event Monitoring
To View the Historical Event Report

1
Click Options->View Event Log from the iQStor SAN Manager menu, or use the
hot key Alt-V.. The Historical Event Report browser window will appear (see
Figure 1-67).
Figure 1-67.
76
Historical Event Report Browser window
Select the Month from the Month Index on the left panel. The Date Index of that
month will appear on the top of the right panel.
Select the Date from the Data Index to display that days event table.

Policy
Policy
Currently there are three categories of Policy Definitions:
Pool Size Management

ICM Partition Policys
Spare Disk Policys
The Policy Definition Window

To View the Policy Definition Window
1
Select Option->Configure from the SAN menu. The Device frame appears (see
Figure 1-68).
Figure 1-68.
Device Frame: Storage - Tools Menu
Select Tools->Policy Definition from the device menu.The Policy Definition window
will appear.(see Figure 1-69 on page 78).
77

Policy
Three
Tabs are
provided
Click New
to add a
new
policy.
Figure 1-69.
Policy Definition window
The Policy Definition window contains three tabs. Each tab provides access to a specific
screen for specifying parameters for that particular Policy.
Pool Expansion
ICM
Spare Pool
Policy Management
Policy Management provides the user with the ability to: edit, disable, enable, or change
priorities (Move Up/Move Down) and to remove Policys
To Define a Policy
78
Select Option->Configure from the SAN menu. The Device frame will appear.
Select Tools->Policy Definition from the device menu.The Policy Definition window
will appear as shown in Figure 1-69 on page 78.
Select the appropriate tab from the Policy Definition window, for the new Policy that
you intend to add. In this example assume the Pool Expansion tab is selected.
Click New to add the new Pool Expansion policy. The appropriate Add Policy Definition window will appear. In this example the Add New Pool Expansion Policy will
appear (see Figure 1-70 on page 79).

Policy
Figure 1-70.
Add Pool Expansion Policy window
If you select the ICM Tab and click New. The Add ICM Policy window appears (see
Figure 1-71).
Figure 1-71.
Add ICM Policy window
79

Policy
For each new Policy, enter a value into the appropriate field.
Click OK and view the newly added Policy.
Note: A newly added Policy will be set to "Enabled" automatically.
Editing a Pool Expansion Policy

1
Select the Pool Expansion tab from the Policy Definition window (see Figure 1-72).
Figure 1-72.
80
Policy Definition - Pool Expansion Tab
Click the Edit button on the Policy Definition window - Pool Expansion tab.
Click any Policy in the Policy Table to make the Policy Manegement menu become
active.
Edit the Policy by changing its parameters.
Click OK to execute the changes and view the newly edited Policy.

Policy
Editing an ICM Policy

1
Select ICM Policy from the Policy Definition window (see Figure 1-73).
Figure 1-73.
Policy Definition - ICM Policy Tab
Click the Edit button on the Policy Definition window - ICM tab.
Click any Policy in the Policy Table to make the Policy Manegement menu become
active.
Edit the Policy by changing its parameters.
Click OK to execute the changes and view the newly edited Policy.
81

Policy
Editing a Spare Pool Policy

1
Select the Spare Pool tab from the Policy Definition window (see Figure 1-74).
Figure 1-74.
82
Policy Definition - Spare Pool Tab
Using the Radio Buttons, edit the Policy by changing its level.
High:
Keep at least two unused spare disks. If two unused spares are not available, they will
be created automatically.
Medium:
Keep at least one unused spare disk anytime. If at least one unused spare is not
available, it will be created automatically.
Low:
Policy will not create any spare disks. Users may create spare disks by themselves.
Click OK to execute the change.

Upgrading Firmware
Upgrading Firmware
1
Select Enclosure->Controller from the Enclosure tree on the left panel of the device
frame. The Controller List of the selected Enclosure will display on the right panel of
the device frame (see Figure 1-75).
Figure 1-75.
Storage Processor - Controller Firmware Upgrade
Select the controller whose firmware you wish to upgrade.
Click File->Firmware Upgrade from the Enclosure Management frame main menu,
or right click on a selected controller and select Firmware Upgrade from the dropdown menu. The Upgrade Controller - Firmware File List window will appear (see
Click File->Firmware Upgrade from the Enclosure Management frame main menu,
or right click on a selected controller and select Firmware Upgrade from the dropdown menu. The Upgrade Controller - Firmware Channel Selection window will
appear (see Figure 1-76 on page 84).
83

Upgrading Firmware
Figure 1-76.
If you select the In band channel, the Upgrade Controller - Firmware File List window will appear (seeFigure 1-77).
Figure 1-77.
84
Firmware Upgrade Controller - Select Channel
Upgrade Controller - Firmware File List
Select an Upgrade File from the Firmware File List table.
Click OK to upgrade the firmware and close the dialog window. A Confirmation
message window will appear (see Figure 1-78 on page 85).

Upgrading Firmware
Figure 1-78.
Information Window - Confirm Firmware Upgrade
Click OK to complete the firmware upgrade.
10 If you select the Out of band channel, the Upgrade Controller - TFTP window will
appear (see Figure 1-79).
Figure 1-79.
Upgrade Controller - TFTP Server
11 Enter the TFTP IP Address, the Port, and the full path of the Firmware File.
12 Click Finish to upgrade the firmware and close the dialog window.
13 When the upgrade is complete, a confirmation window will appear (see Figure 1-78).
14 Click OK to complete the firmware upgrade.
Note: If the upgrade is successful, you may reboot to activate.
85

Zoning
Zoning
In a Fibre Channel SAN environment, zoning is used as a method of creating barriers on
the fabric to prevent groups of devices from interacting with each other. Zoning sets up
efficient methods of managing, partitioning, and controlling pathways to and from storage
devices on the SAN fabric. As a result, storage resources are maximized, and data
integrity and data security are maintained.
Zoning Types
There are two types of zoning:
Soft zoning
Hard zoning
Soft Zoning
The soft zoning process uses the name server database to store port numbers and world
wide names (WWN) used to identify devices during the zoning process.
Hard Zoning
The hard zoning process uses only WWNs to specify each device. The benefit of this
approach is that the switch can regulate data transfers through verified zones. Hard zoning
requires each device to pass through the switch's route table. This will allow an
administrator to physically move an FC cable connection without losing the zoning
relationship between the zones' components.
Note: iQstor recommends the hard zoning process in all production environments.
Configuring Zoning Components

Zone configurations are based on either the WWN of the device or the physical port that
the device plugs into. Zoning components include:
Zones
Zone Members
Zone Sets
Zones
A zone is made up of servers and storage devices on the SAN fabric that can access each
other through managed port-to-port connections. Devices in the same zone can recognize
and communicate with each other, but not necessarily with devices in other zones, unless a
device in that zone is configured for multiple zones.
86

Zoning
Zone Members
Zone members are devices within the same assigned zone. Zone member devices are
restricted to intra-zone communications, meaning that these devices can only interact with
members within their assigned zone. Unless a device is configured for multiple zones, a
zone member interacting with devices outside its assigned zone is not permitted.
Zone Sets
A zone set is a group of zones that function together on the SAN fabric. All devices in a
zone see only devices assigned to their zone, but any device in that zone can be a member
of other zones.
The Switch
As described above, Zoning involves the SAN Fabric. To view switch characteristics and
parameters, users should begin by logging into the Fibre Channel switch.
Logging In To The Switch

To log in to the fibre channel switch, follow the following steps:
1
Select the switch from the SAN Tree or Topology Layer in the iQstor SAN Manager
frame (see Figure 1-80).
Figure 1-80.
iQstor SAN Manager Frame
Right click and select Configure from the drop-down menu, or select Options->Configure from the frame menu, or use the hot key Ctrl-G. The Login Switch dialog
window will appear (see Figure 1-80 on page 87)
87

Zoning
Figure 1-81.
Type a User Name in the User Name field.
Type a Password in the Password field.
Click the OK button to log in and close the dialog window.
The main Switch and Zoning window will appear (see Figure 1-82).
Figure 1-82.
88
Login Switch Dialog window
Switch and Zoning window

Zoning
To View Switch Information

Select Fabric->Switch->Switch Name from the device tree. The Switch Information
Table will appear on the right panel (see Figure 1-83 on page 89).
Figure 1-83.
Switch Information Table
The Switch Information Table contains the Port ID, Port Type, WWN of the Switch,
FC ID, Online/Offline status, and Port connection state.
89

Zoning
Creating Zones
To create a new zone, users must give a Name to the new zone, and then make a Port
selection for Port Zoning or a Host WWN selection for WWN Zoning.
To Create a Zone
1
Select Zone->Create from the device menu. The Create Zone window will appear
(see Figure 1-84).
Figure 1-84.
90
Create Zone window
Type the Zone Name into the Zone Name field.
Click the Next button to continue. The Create Zone - Select Switch Port(s) window
appears (see Figure 1-85).

Zoning
Figure 1-85.
Create Zone - Select Switch Port(s) window
If the user wants to do port zoning, select the Available Ports to be zoned or
"grouped" together and click the direction arrow (>) to move it to the Selected Port
list box, or click the double arrow (>>) to move all Available Ports to the Selected
Port list (see Figure 1-85).
Click the Next button to continue. The Create Zone - Select Host WWN window
appears (see Figure 1-86 on page 91).
Figure 1-86.
Create Zone - Select Host WWN window
91

Zoning
If the user wants to do WWN zoning, select the Available WWN of the devices to be
zoned together and click the direction arrow (>) to move it to the Selected WWN list
box, or click the double arrow (>>) to move all Available WWN to the Selected
WWN list (see Figure 1-86).
Click the Finish button and wait until the Create Zone - Summary window for the
newly created Zone appears (see Figure 1-87).
Figure 1-87.
92
Create Zone - Summary window
Click Close to close the Create Zone window.

Zoning
Select Fabric->Zoning->Zone from the object tree. The Zone Table will appear on
the right panel (see Figure 1-88).
Figure 1-88.
Create Zone - Zone Table
93

Power Management (iQstrip)
Power Management (iQstrip)

Right-click on the cabinet node in the SAN frame and click "Configure" to open the
power management window:
Power On/Off a Slot

Click a ACSlot row in slot table, then the power management menu will be active, press
"Power On" or "Power Off" to power on or power off the slot. Then system will enter
"Waiting" state.
Power on may cost quite a while and when "Waiting" status is displayed, do not press
other buttons.
Power Configure
You can configure Lowload and Overload limen. Once the real value is higher than the
overload or lower than the lowload, a warning event will be sent.
Press "Configure" to enable the settings.
94
Chapter 2
RAID Configuration Parameters and

Maintenance
You can review or modify the iQstor SAN Managers software configuration by using any
of three administration tools:
iQStor Networks SAN Manager browser-based Graphical User Interface (see your
Administration and Operations User Guide).
Command Line Interface (see your Administration and Operations User Guide).
ASCII text-based Graphical User Interface (see your Administration and Operations
User Guide).
This chapter provides detailed information on the parameters whose values you set by
using these tools. Refer to the chapters above for information on using each tool.
For information on advanced options, including the features and best uses of the different
RAID levels, refer to your Administration and Operations User Guide.
Note: With Solaris systems, we recommend that you always probe the iQstor SAN
Manager, using the format command, after changing any configuration parameters. See
Probing the iQstor SAN Manager in Chapter 2.
95
Chapter 2: RAID Configuration Parameters and Maintenance

RAID Set Parameters
RAID Set Parameters

Table 2-1, RAID Set Configuration Parameters, on page 96 summarizes the parameters
that configure a RAID set.
Note:
Some parameter settings are required. Others are optional.

Some values may not be modified after the iQstor SAN Manager starts up or has
been used. Others may be modified after start-up and use.
All parameter values may be modified if you wish to create a new RAID set. The
data in the previous RAID set is erased.
Table 2-1.
RAID Set Configuration Parameters
Function
Parameter
Required?
Modifiable After Use*?
RAID Set Name
-name
Yes
Yes
RAID Level
-type
Yes
No
Size (MB)
-size
Yes
Before use
Backend Size (MB)
-backendsize
Yes
No
I/O Mode
-iomode
Yes
Yes
Host Interfaces
-hostif
Yes
Yes
Cache (MB)
-cache
No
Yes
Backends
-backends
Yes
No
Chunk Size (Kbytes)
-iosize
Yes
Before use
Queue Length
-qlen
No
Yes
Boot mode.
-boot
No
Yes
Additional Arguments
-stargs
No
Yes
Initial RAID Set Status
-state
No
Yes
I/O Usage Flag
-usezoneio
No
Yes
Spares Usage Flag
-usespares
No
Yes
* All parameters may be modified if you wish to create a new RAID set. The data in
the previous RAID set is erased.
96

Choosing the RAID Level
Choosing the RAID Level

The -type parameter defines the RAID set level, which in turn determines the file system
that will be used to organize data on the disks. To optimize the iQstor SAN Managers
performance, you first need to understand which RAID level is best for your application.
See Introduction to RAID Technology in Chapter 1, for the characteristics of the
different RAID levels.
For advanced information on RAID file systems, see your Administration and Operations
User Guide. It provides detailed information on the file systems for each RAID level,
guidelines on setting values for related parameters, and describes the memory
requirements for RAID levels 3 and 5.
Note: For RAID level 3 or 5, a spare drive should be configured and the usespares
attribute should be enabled (see RAID Set Configuration on page 105). This allows the
iQstor SAN Managers auto-repair capability to respond to a drive failure, if one occurs, as
soon as it is detected. When you configure the iQstor SAN Manager using the ASCII GUI
or iQstor SAN Manager, the automatic configuration function always configures a spare
drive for RAID level 3 or 5, if a spare drive is available.
97

LUN Verification
LUN Verification
This section shows you how to perform LUN verification. This process involves both LUN
masking, and LUN mapping.
LUN Masking
LUN masking allows you to decide whether you want any hosts connected to the iQstor
SAN Manager to be able to recognize virtual disks (Vdisks). You determine this by either
enabling, or disabling LUN masking as follows:
LUN masking ON: Hosts do not recognize Vdisks.

LUN masking OFF: Hosts do recognize Vdisks.
Use the following commands to perform LUN masking:
98
vdmask -add [-vn vname] -wwn wwn

Create the maximum number of Vdisk possible (128 allowed).
Add 64 different WWNs for each Vdisk.
Add more than 64 WWNs on a Vdisk (error message).
Use this command without providing a Vdisk name.
Verify that the WWN has been added to all the available Vdisks in the table.
Add a duplicate WWN entry on the same Vdisk (error)
Add a lun masking table for an invalid Vdisk name (error)
vdmask rm [-vn vname] [-wwn wwn]

Create the maximum number of Vdisks allowed.
Remove a specific WWN and Vdisk combination.
Use this command providing only the Vdisk (do not provide the WWN).
Verify that all the entries for the Vdisk are removed.
Use this command providing only the WWN (do not provide the Vdisk name).
Verify that all the entries for that WWN are removed.
Use this command without providing any parameters.
Verify that all the entries are deleted.
Remove many entries randomly by providing different WWNs and different
Vdisk names.
vdmask [-vn vname] ON|OFF

Create 128 Vdisks (max allowed).
Turn all of them OFF.
Verify.
Turn all of them ON.
Verify.

LUN Verification
vdmask print [-vn vname]|[-wwn wwn]

Use this command without providing a parameter:
This should print all entries.
Use this command with a Vdisk name:
This should print all the entries associated with that particular Vdisk.
Use this command with a WWN:
This should print all the entries associated with that particular WWN.
.getwwn
Connect as many HOSTs available.

Use this command to make sure they are all connected and recognized by the controller.
LUN Mapping
LUN mapping allows you to map or associate hosts and Vdisks on a specific LUN
number. You do this by creating LUN map entries that define the host, Vdisk, and LUN
number relationships.
Important: Use LUN mapping for initial setup and configuration. Do not use it on a
mounted file system.
Use the following commands to perform LUN mapping:

1
vdmap -map -vn vname -wwn wwn -hl hlun

map a HOST WWN to an invalid Vdisk name.(error).
Map a HOST WWN to two different VDISKs using the same LUN number
(error).
Verify LUN mapping table after each configuration.
vdmap -remap -vn vname -wwn wwn [-hl hlun] -nl newhlun
ap a HOST WWN with a valid Vdisk on a Lun number then remap the same
HOST WWN and Vdisk pair to a new HOSt LUN number.
Map a HOST WWN with a valid Vdisk on two HOST Lun numbers then remap
to a new LUN number without providing the hlun parameter.Verify that the first
instance of the WWN, Vdisk pair is changed or remaped to the new Lun number.
Remap a <WWN, Vname, hlun> triplet to an invalid triplet(not present in the
mapping table).
99

LUN Verification
100
vdmap -rm [-mult] [-vn vname] [-wwn wwn] [-hl hlun]

Map 10 (WWN, Vdisks, hlun) triplets.
Remove/delete map entry using only the hlun (not allowed).
Remove/delete an invalid entry or combination (error).
With the -mult option, remove multiple <WWN, hlun> pairs.
Without the multi option remove an entry providing the Vdisk only.
Without the multi option remove an entry providing the WWN only:
this removes all the entries associated with that particular WWN.
Without the multi option, remove an entry providing the WWN, Vdisk combination: this will remove all the entries associated with that particular entry (pair).
Without the multi option, remove an entry providing the WWN, Vdisk, hlun
triplets: this removes all the entries associated with that particular entry (triplet).
Without the multi option, remove an entry providing the Vdisk only: this
removes all the entries associated with that particular Vdisk.
vdmap -print [-vn vname] [wwn wwn]

try the print command providing:
only the Vdisk parameter.
only the WWN parameter.
both the WWN, hlun parameters.
No parameters: verify the whole lun mapping table is displayed.
vdmap -freehl wwn wwn [-hluns N]

This is based on the LUN masking and LUN mapping tables information not on the
HOST (sd.conf).
Create 10 lun mapping entries on a HOST.
Use this command to check which LUNs are available.
LUN mapping and LUN masking could be combined:
randomly create 5 LUN masking entries on different HOSTs.
use this command to check which LUNs are available per HOST WWN (on
each HOST).
vdmap -usedhl -wwn wwn [-hluns N]

Create 10 lun mapping entries on a HOST.
Use this command to check which LUNs are being used by the HOST.
LUN mapping and LUN masking could be combined:
randomly create 5 LUN masking entries on different HOSTs.
Use this command to check which LUNs are used by each HOST WWN (on each
HOST).

LUN Verification
vdmap -collisions wwn wwn

Set a collision as follows:
Create 4 Vdisks.
Turn LUN masking OFF.
Create an additional 4 Vdisks.
Set LUN mapping of the new Vdisks to use the first four HOST Luns. The
HOST should see only the mapped virtual disks (the last four new Vdisks).
Use the vdmap collisions command to identify which LUNs have a collision.
101
102
Chapter 3
Using the Command Line Interface

Online Manual
The following command provides access to the online help manuals.
man
- display online manual pages
Usage:
man [command_name]
Note: Use "man -l" to print out a list of commands.
103
Chapter 3: Using the Command Line Interface

SCSI Port Configuration
SCSI Port Configuration

The following commands are SCSI Port related commands.
hconf
- display, assign, or modify the SCSI ID
Usage:
hconf [options]
-delete [controller] [scsi_port]
remove SCSI Port ID
-list [controller] [scsi_port]
display SCSI Port ID
-modify [controller] [scsi_port] [scsi_id]
change SCSI Port ID
Notes:
Normally, the controller value is 0.
A scsi_port of 0 refers to port A while a scsi_port of 1 refers to port B.
If the SCSI ID field contains only a dash ( - ) it indicates that there is no SCSI
ID on the port.
Default display format:

"controller_number SCSI_port_number SCSI_ID."
Sample:
Find the SCSI ID on port A

: raid; hconf
005
Modify the SCSI ID on port A to 2

: raid; hconf -modify 0 0 2
104
Caution: Do not delete the SCSI port that connects the iQ1000 to the host. If you do, the
host will be unable to sense the iQ1000.

RAID Set Configuration

The following commands are RAID set related commands.
rconf
- create, modify, display, or delete RAID set
Usage:
rconf [options]
-add
create a new RAID set
-type raidtype
-name raidname
-size raidsize
-iomode read-write|read-only|write-only
-iosize raidchunksize
-hostif mflag controller host_port scsi_lun
-backendsize backends_size
-backends backend1,backend2,,backendn
[-rfsck]
[-boot auto|manual]
[-cache raidcachesize]
[-state active|inactive]
[-usespares on|off]
[-usezoneio on|off]
[-qlen nqueues]
[-stargs {xstargd_args}]
[-hostif mflag controller host_port scsi_lun]
[-astape]
-delete raidname
remove RAID set from iQ1000's

EEPROM
-list [raidname] [-v]
display RAID set information
-modify
configuration
modify the RAID set
-name raidname
105

[-iomode read-write|read-only|write-only]
[-newname newraidname]
[-hostif mflag controller host_port scsi_lun]
[-boot auto|manual] [-cache raidcachesize]
[-state active|inactive]
[-usespares on|off]
[-rfsck]
[-usezoneio on|off]
[-qlen nqueues]
[-stargs {xstargd_args}]
[-astape]
-init
erase the iQ1000 software

configuration
Notes:
106
The synopsis above lists some parameters separately. You can enter
parameters on the same line.
Any parameters you do not include in an rconf -add command are left at their
default.
New RAID sets become active when you reboot the iQ1000 by using the
reboot command.
If you delete a RAID set accidentally, you can still access the original
backend data by recreating an exact duplicate of the deleted RAID set. Data
can only be recovered if you have not written to the backend disks after the
original RAID set was deleted.
You can only modify parameters that have no effect on the format of data
stored on the backend disks. For example, you may not modify the iosize
parameter value. Once you have defined the RAID level (-type) for a RAID
set and stored data on the RAID set, you must keep that format to retrieve
stored data.
Caution: Only use the rconf -init command if you are an experienced system administrator or with the assistance of iQstor Technical Support. It erases all configuration data,
including definitions for RAID sets, spare pools, and disk configurations, making the
iQ1000 a "blank" system.

Sample:
Create a RAID set with the following characteristics: level 5, name R5, total size
8388608 in 512KB blocks, host can both read from the RAID set and write to it, read/
write requests are in "chunks" of 64KB, SCSI connection uses LUN 0 on port A and
LUN 0 on port B, backend disk size is 2097152 in 512 KB blocks (or 1 GB total),
cache size is 10 MB, RAID set boots automatically, uses a spare disk in the spare
pool, uses the read-ahead option, and has backend drives named D0.0.0, D1.0.0,
D0.1.0, D1.1.0, and D2.0.0.
: raid; rconf -add -type 5 -name R5 -size 8388608 -iomode read-write \
-iosize 64K -hostif M 0 0 0 -hostif M 0 1 0 -backendsize 2097152 \
-cache 10M -boot auto -usespares on -stargs {-L 32} -backends \
D0.0.0,D1.0.0,D0.1.0,D1.1.0,D2.0.0
Display RAID set R0's information

: raid; rconf -v
Name: R1Type: 1 Flags: Active,Used,NoRfsck,Autoboot,UseSpares,BFailDrop
Raid Size :
Cache Size:
71687232 ( 35003.531MB) IOSize : 8192

33554432 (
32.000MB)IO Mode: read-write
Queues: 16Host Interface(s): 1 M0.0.0

BackendSize: 71687242 (
35003.536MB)
Backends: D0.69.0,D0.71.0
Additional stargd args: {-L 16}
Mem usage estimate: 40475328 (
38.600MB)Max procs: C0 - 37
mkraid
- initialize the RAID set
Usage:
mkraid `rconf -list [raidname]'
Note: When using dual controllers, to initialize the RAID set on the other controller,
issue the command: rrcii -C {mkraid `rconf -list [raidname]'}.
107

raidaction
- start or stop a RAID set
Usage:
rconf [raidname] [up|down]
Notes:
To modify a RAID set's configuration, you must first stop the RAID set. This
logically disconnects the RAID set from the SCSI bus, so that the host no
longer has access to it.
When a RAID set is stopped, its data is in a static state.
You can also use the reboot command to start a RAID set after reconfiguring
it.
After modifying a RAID set's configuration, you must start the RAIS set.
When a RAID set is started, its data in is a dynamic state.This presents it ot
the SCSI interface, so that the host can gain access to it.
Sample:
Stop RAID set R5 so you can reconfigure it

: raid; raidaction R5 down
Start RAID set R5 after it has been reconfigured

: raid; raidaction R5 up
repair
- manually repair faulty drive in a RAID set
Usage:
repair [raidname] [faulty_drive]
Notes:
108
In order to repair a faulty drive, there must be a suitable drive in the spare
pool with a capacity at least as large as the capacity of the failed drive.
The repair procedure can take about 30 to 60 minutes, depending on the

workload of the RAID set during data reconstruction.
When repairing has completed, the spare drive replaces the failed drive and
the RAID set returns to normal operational speed.

Sample:
Repair RAID set R3 whose faulty drive is D1.1.0

: raid; repair R3 D1.1.0
replace
- replace a faulty drive with a new backend
Usage:
replace [raidname] [faulty_drive]
Note: In order to replace a faulty drive, the replacement drive's capacity must be at least
as large as the capacity of the failed drive.
Sample:
Replace RAID set R3 whose faulty drive is D1.1.0

: raid; replace R3 D1.1.0
setraid
- configure the RAID set quickly
Usage:
setraid [raid_level] [IOsize_in_KB]
Sample:
Configure a RAID level 5 with 8 KB IOsize and use all the available memory as cache
: raid; setraid 5 8
Configure a RAID level 3 with 128 KB IOsize and use all the available memory as
cache
: raid; setraid 3 128
Configure a RAID level 0 with 64 KB IOsize and use all the available memory as
cache
109

Configure a RAID level 6, when using only 6 drives, with 128 KB IOsize and use all
the available memory as cache
110

Spare Pool
Spare Pool
The following commands are spare pool related commands.
spool
- create, modify, display or delete spare pool
Usage:
spool [options]
-add
add a disk into the spare pool
-name backend
-backendsize backends_size
-type hot|warm
[-ctrl controller_number]
-delete -name backend
remove a disk from the spare pool
-list
display the disks in the spare pool
Notes:
Each disk in a pool can be defined as warm or hot. A warm disk requires
spinning up before it can be used. A hot disk is kept spun up and can be used
immediately.
The synopsis above lists some parameters separately. You can enter
parameters on the same line.
Sample:
Add one disk D2.0.0 as a backend disk with 4197276 logical blocks (2GB). It will be
kept spun-up (hot) for immediate use, if needed.
: raid; spool -add -name D2.0.0 -backendsize 4197276 -type hot
List all the spare disks

: raid; spool -list
D2.0.0 4197276 hot Any Unused Working
Note: This listing shows that backend D2.0.0 is a spare disk in the pool, its size is
4197276 logical blocks (2 GB), it is spun-up (hot), it is currently not used by any RAID
set, and it is in good condition (Working).
111

BootUp
BootUp
The following commands are boot up related commands.
reboot
- reinitialize the iQ1000
Usage:
reboot
Note: If you are using the cu utility to gain access to the iQ1000 system console, you
will see the following messages during initialization:
================================
| iQstor Networks
| Automating Storage Expertise |

================================
Boot Code: BETA-5003
Initializing 128MB
Board ID 0000000E RD48 100MHz
Config 204264B0 SC=P *=4 SE=off
PRId
2733
Type SPACE to abort: ...............

--- Loading
--- Booting
iQstor RD48 Class Kernel

init_stargen[pid=70] Local_Message_Ptr = 0xa07c0000
FNS network device gt0 installed at 0x0
[Note: additional lines of output will appear here during the bootup]
11:51:36 09/10/02; 365

: raid;
112

BootUp
Note: If you are using the ssmon program to gain access to the iQ1000 system console,
the program will exit after you type the reboot command. Because ssmon has no access to
the iQ1000 during boot-up, you must restart the program when the system has finished
initializing.
113

BootUp
boot
- boot a selected RAID set on the iQ1000
Usage:
boot [raidname]
Note: If you are using the cu utility to gain access to the iQ1000 system console, you
will see the following messages during initialization:
================================
| iQstor Networks
| Automating Storage Expertise |

================================
Boot Code: BETA-5003
Initializing 128MB
Board ID 0000000E RD48 100MHz
Config 204264B0 SC=P *=4 SE=off
PRId
2733
Type SPACE to abort: ...............

--- Loading
--- Booting
iQstor RD48 Class Kernel

init_stargen[pid=70] Local_Message_Ptr = 0xa07c0000
FNS network device gt0 installed at 0x0
[Note: additional lines of output will appear here during the bootup]
11:51:36 09/10/02; 365

: raid;
114

BootUp
Note: If you are using the ssmon program to gain access to the iQ1000 system console,
the program will exit after you type the reboot command. Because ssmon has no access to
the iQ1000 during boot-up, you must restart the program when the system has finished
initializing.
115

Snapshot
Snapshot
The following commands are snapshot related commands.
snapadd
- create snapshot
Usage:
snapadd [source_vdisk_name] [options]
-n name
user defined snapshot name.
-s size
snapshot_vdisk_size in half_GB, size must be multiple of 0.5GB

default to approximately 10% of source vdisk size
-c size
snapshot_chunksize in KB, must be power of 2

default to 128KB, or equal to or larger than iosize
-p [r | rw]
snapshot access permission, initial value must be rw(default)
-e minutes
expire_in_minutes, default to 0
-i minutes
interval to re-create, default to 0
-u percentage
usage threshold upon which autogrow will be activated
Notes:
116
Except Source vdisk name, all other options are optional and usually can be
omitted.
Snapshot chunk is the operation unit when comparing and coping data
between source disk and snapshot disk. Default size of 128 KB should apply
to most of situations. Don't change this value unless you know what you
want.
If backend access flag is Off, all the operation is performed at the Cache
level.

Snapshot
Sample:
Create snapshot on source disk V0010

: raid; snapadd V0010
Create snapshot mysnap on source disk V0010. Set the size of mysnap to 10GB, the
usage threshold to 80% and the hours of re-create interval to 24 hours
: raid; snapadd V0010 -n mysnap -s 20 -u 80 -i 1440
snapinfo
- display snapshot information of vdisk
Usage:
snapinfo [snapshot_name] [options]
-verbose
output detailed information
-grp
output snapshot group info
-gui
formatted output
output help info
Notes:
If leave both vdisk name and options blank, snapinfo will display all the
snapshots in the current sanfs.
Default GUI display name format.

"snap src lifespan interval chksize size used_local usage_local used
usage threshold grp_id seq_id seq# modified_time."
Group ID range: 1 - 8; sequential Number range: 1 - 127.
117

Snapshot
Sample:
Display information for snapshot V0003

: raid; snapinfo V0003 -verbose
----VDISK NAME:
V0003
NODE TYPE:
VNODE_SNAPW
State:
OK
Gui display name:
V0001_1_1_V0003
Host Access Right:
RW
Creation time:
10:56:03,Wednesday,08/28/2002
Total Size:
2.31 GB
IOsize:
65536 bytes
Serial number:
0003000564295870
number:
Original vdisk:
V0001
Original vdisk size:
1.93 GB
Life span:
0000:00
Time to expire:
0000:00
Re-create intervals:
0000:00
Time to next recreate:
0000:00
Space usage:
Physical: 1.87 GB / 2.31 GB = 81%, Logical: 1.87 GB

/ 2.31 GB = 81%
118
Usage threshold:
90%
Snapchunk size:
128 KB
COW table entries:
15368 / 18944
COW on-disk size:
222 KB
Last written time:
00:00:00, ?day, 00/00/0000
Seq# in group:
Flag bitmap:
0x100

Snapshot
Snapshot group peers:
G1: V0003
EOC
snaprm
- delete snapshot
Usage:
snaprm [snapshot_name | snapshot_source_name] [-force]
Notes:
In the case of multiple snapshots for a certain source vdisk, only the first
snapshot can be removed.
Use -force option to remove a corrupted snapshot.
If vdisk is the source_vdisk, all the snapshots attached to source_vdisk will
be removed.
snapctrl
- snapshot properties control
Usage:
snapctrl [vdisk_name] [options]
-s size|+size|-size
Set, add or shrink size in 0.5GB
-p r|rw
Change access permission
-i minutes
Change re-create interval
-e minutes
Change expire time, counted since creation
-u percentage
Change usage threshold
-load
Load snapshot metadata from disk
-flush
Flush snapshot metadata back to disk
-reset [-force]
Reinitialize source or recreate snapshot
-q
Ignore quiescence mode
-v
Print snapshot software version
119

Snapshot
Notes:
This command is used to reset snapshot default values.
Load command will load on-disk snapshot data into memory and overwrite
the current snapshot in-core data.
Flush command saves the current in-core snapshot data back to disk.
Reset command clears both the in-core and on-disk snapshot data and creates
another snapshot with the same name on the current physical snapshot vdisk.
The net result is the same as:
1) Remove the old snapshot.
2) Create a new snapshot using the data structure of the old snapshot.
Sample:
Save snapshot V0011 metadata to source disk.

: raid; snapctrl -flush V0011
Re-create a snapshot V0011 on the current source disk, change the usage percentage
to 80% and add one vdisk chunk to the snapshot disk size.
: raid; snapctrl -reset V0011 -u 80 -s +1
120

LUN Masking
LUN Masking
The following commands are LUN masking related commands.
vdmask
- control vdisk LUN masking
Usage:
vdmask [options]
-add [-vn vname] -wwn wwn
add wwn to vdisk(s) masking table
-rm [-vn vname] [-wwn wwn]
remove entry from vdisk masking table
[-vn vname] [ON|OFF]
turn masking flag on a vdisk ON or OFF
-print [-vn vname]|[-wwn wwn]
print lun masking entries
Notes:
When adding a wwn, if no vname is given then the wwn will be entered into
every vdisk's masking table. A maximum of 64 different wwns can be
entered for each vdisk. Trying to add a duplicate wwn to a given vname's
masking table will be rejected.
Multiple <vname, wwn> pairs can be removed at once by adding more pairs
to the -rm command. There is no set limit to how many entries can be
deleted but there is a limit on the ssmon line buffer.
When the masking flag of a vdisk is OFF then any host connected to the raid
machine will be able to access that vdisk. When the masking flag is ON, then
only those wwns within the vdisk's masking table will have access to the
virtual disk. If no vname is given then all vdisk's masking flag will be set
accordingly.
When printing lun masking entries, if no parameters are given then the
masking table of all vdisks will be printed. If only the vname is given then
the masking table of only that vdisk will be printed. If only the wwn is given
then masking entries w/ that given wwn will be printed.
121

LUN Masking
Sample:
Removing all wwns from the masking table for every vdisk
vdmask -rm
Removing all wwn entries for a given vdisk

vdmask -rm -vn vname
Removing a given wwn for every vdisk

vdmask -rm -wwn wwn
Removing a given wwn from a given vdisk

vdmask -rm -vn vname -wwn wwn
Removing multiple wwns

vdmask -rm -vn vname1 -wwn wwn1 -vn vname2 -wwn wwn2 -vn vname2 -wwn
wwn3 . . . etc
122

LUN Mapping
LUN Mapping
The following commands are LUN mapping related commands.
vdmap
Usage:
- map vdisks to a LUN number on a host

vdmap [options]
-map -vn vname -wwn wwn -hl hlun

map vdisk to specified host LUN
-remap -vn vname -wwn wwn [-hl hlun] -nl newhlun
remap vdisk from a specified host LUN to a new host LUN
-rm [-vn vname] [-wwn wwn] [-hl hlun]
remove lun mapping entries
-rmulti -wwn wwn -hl hlun [-wwn wwn] [-hl hlun] ..
remove multiple lun mapping entries at one time
-print [-vn vname] [-wwn wwn]
print out lun mapping entries
-freehl -wwn wwn [-hluns N]
print out all of the available host luns for the given wwn
-usedhl -wwn wwn [-hluns N]
print out all of the used host luns of the given wwn
-collisions -wwn wwn
prints out the vdisks that have collided
Notes:
Mapping a particular <wwn,hlun> pair to multiple (different) vdisks is not

allowed.
When remapping a host LUN, if the hlun is not given, then the command will
simply remap the first instance of the given <vname,wwn> found in the
mapping table to use the newhlun.
There is no limit to the number of LUN mapping entries that can be removed
at once, but there is a limit on the ssmon line buffer.
The available host luns are calculated based on both lun mapping and
masking.
123

LUN Mapping
The [-hluns N] option sets a limit on the number of hluns scanned for
availability. If this option is not given then the command will display all
available hluns up to 31 (0-31).
A collision occurs when 2 vdisks reside on the same host lun and set up so
both vdisks are "supposed" to be viewable by the same host on the same host
lun.
Sample:
Removing all LUN mapping entries

vdmap -rm
Removing all LUN mapping entries with a given vname

vdmap -rm -vn vname
Removing all LUN mapping entries with a given wwn

vdmap -rm -wwn wwn
Removing all <vname,wwn> pairs.

vdmap -rm -vn vname -wwn wwn
Removing all <vname,wwn,hl> triplets.

vdmap -rm -vn vname -wwn wwn -hl hlun
Print out the entire LUN mapping table

vdmap -print
Print mappings with a given vname

vdmap -print -vn vname
Print mappings with a given wwn.

vdmap -print -wwn wwn
Print all given <vname,wwn> mappings.

vdmap -print -vn vname -wwn wwn
124

Remote Replication
Remote Replication
The following commands are remote replication related commands.
vdrep
- remote replication
Usage:
vdrep [options]
-connect -src vname:outbound_CnPm_list -dst hlun:portname_list -rsite

remote_site_name
-disconnect -src vname -rsite remote_site_name
-modify -src vname -rsite remote_site_name [-newrsite new_rsitename]
[-dst hlun:new_portname_list] [-newsrc]
-start -src vname -rsite remote_site_name [-full|-rfull|-rfast]
-suspend [-src vname] -rsite remote_site_name
-rejoin [-src vname] -rsite remote_site_name
-rrejoin [-src vname] -rsite remote_site_name
-split [-src vname] -rsite remote_site_name
-state -src vname -rsite remote_site_name
-compare [-full] [-ssync|-rsync] -src vname -rsite remote_site_name
-event [-rm] [-scap scoreboard_log_size] [-stime HHMM] [-sitime HHMM] -src vname
-rsite remote_site_name
125

Local Mirroring
Local Mirroring
The following commands are local mirroring related commands.
vdmirror
- local mirroring
Usage:
vdmirror [Vdiskname] [ -suspend | -resync [-f] | -destroy | -split |

-rev_resync [-f] | -state | -raidc dest_RCname ]
Note: "-f" is used to indicate a full resync or full reverse resync.
126

SV Log
SV Log
The following command is a SV log related commands.
sfslog
Usage:
- storage virtualization logging

sfslog [-date1 MMDDYYYY | -date2 MMDDYYYY | -vdisk
Vdiskname | -raidc RCname | -ctrlno 0|1 | -p nentries | [-A | -D] ]
127

SV Utilities
SV Utilities
The following commands are SV utility related commands.
vdcpy
- copies a vdisk to another vdisk
Usage:
vdcpy [src_vdisk | remote_src] [dst_vdisk | remote_target]
Note: Snapshot vdisk can only be the source of a copy. Remote targets are specified as
"hlun:wwn".
128
vdcmp
- compares two vdisks
Usage:
vdcmp [src_vdisk] [dst_vdisk | remote_target] [-full]

SAN FS
SAN FS
The following commands are SANFS related commands.
__sfsmk
- build san file system on specified RAID
Usage:
__sfsmk [RCname] [options]
[sfs_pool_info]
user's note or guiname for the sanfs/pool
-wipeout
write over existing sanfs
Notes:
sfs_pool_info can be up to 80 characters long.

If the sfs_pool_info is not specified, it will be set to the RCname.
SANFS returns an error message if the user tries to make a new sanfs on a
raidset that currently has a sanfs on it. The user must pass the [-wipeout] flag
in order to build a new sanfs on the raidset. This prevents somebody from
accidentally creating a new sanfs. Returns "0" on success else "1" on failure.
sfsinfo
- displays the file system information on the

specified pool
Usage:
sfsinfo [options]
[RCname]displays system information for specified RCname

-full
display all file system information
Notes:
If RCname is not provided, all the info of all sanfs on the system will be
displayed.
By default, only the critical data will be printed.
size_in_halfGB represents the number of units in a vdisk.

1 unit = 512MB, 4 units = 2 GB.
Default display unless specified otherwise by the '-full' option:

"RCname size_in_GB free_capacity RAIDU_list creation_time
last_expansion_time cache_size(MB) GUIname."
129

SAN FS
sfsgrow
- grows the file system onto the specified RAID
Usage:
sfsgrow [RCname] [qualified_raidu_list]
sfsshrink
- shrinks the file system by the size of the

specified RAID
Usage:
sfsshrink [RCname] [takeout_raidu_list]
sfsnewinfo
Usage:
sfsnewinfo [RCname] [new_poolinfo]
sfsck
- checks if there are errors in the main metadata

of the file system
Usage:
sfsck [RCname]
Notes:
130
- modify the pool information
Automatically checks all sanfs if RCname is not provided.

Automatically repairs any errors found.
Prints nothing if successful.
It recovers from the backup metadata but if the back is also corrupted then a
message is printed that the user should recover from the host backup file
because both metadatas are corrupted.
sfsrec
- recovers the front metadata using the backup

metadata as a source
Usage:
sfsrec [RCname]

SAN FS
Note: It will not recover if the backup metadata is corrupted. The command will print
a message stating this.
SFSREC_HOST
Usage:
- recovers the front and backup metadata

from the host backup file given by the path
SFSREC_HOST [RCname] [path_to_host_backup_file] [-LMAP]
Notes:
This command only works on SSMON.
"-LMAP" is an optional flag to recover the lun mapping table that was backed
up.
A word of caution, if there are more than one raidsets to be recovered, the
entire mapping table may not be fully recovered if all the raidsets are also not
also recovered. This is because the mapping table can consist of vdisks
across multiple raidsets. Therefore, only mapping entries w/ valid vdisks
(vdisks in the incore table) will be recovered.
Reboot is necessary after recovery.
SFSBAK_HOST
Usage:
- create a backup file of the metadata onto the

host
SFSBAK_HOST[RCname]
[path_to_host_file_for_metabackup]
Note: This command only works on SSMON.
Sample:
Create a host backup file, sanfs_R3.bak, of R3 in the /tmp directory

SFSBAK_HOST R3 /tmp/sanfs_R3.bak
131

SAN FS
vdadd
- add a virtual node to the file system
Usage:
vdadd [Sanfsname] [size_in_halfGB] [options]
-pn port_number
port number vdisk will be presented on
-ilun lun
internal LUN
-gname Vdiskgrpname
-diskinfo GUIname
-temp
temporary storage virtual node
Notes:
132
size_in_halfGB represents the number of units in a vdisk.

1 unit = 512MB, 4 units = 2 GB.
For the RD48 there is only one port so port 0 is the only one accepted.
The LUN number can be any LUN not in use. A message indicating failure
will be displayed if chosen LUN is already in use.
Vdiskgrpname by default is RCname.
When the '-temp' flag is set, the vdisk will now be allocated from the end of
the raidset instead of from the beginning.
After the vdadd command is completed, it will print the following

information:
"Vdiskname RCname size_in_MB ilun."
Error checking is done by command to verify valid port numbers. If no port

number is passed in by the user then a port will be chosen that will balance
the load between all ports.
GUIname is stored as the vdisk_info in the vdisk structure. By default, the

GUIname will be the same as Vdiskname. This allows the user to specify a
name to reference the vdisk through the gui.
vdrm
- remove a virtual node from the file system.
Usage:
vdrm [Vdiskname] [-wipeout]

SAN FS
Notes:
VDISK V9999 should never be removed from sanfs since this is used by
SMON.
Several vdisks can be passed in for removal at once (e.g. vdrm V0000 V0001
V0002).
Vdrm will first do a check if there is a valid label on the vdisk. If there is a
valid label then a warning message is printed stating that the vdisk contains
data and cannot be removed unless the '-wipeout' flag is passed.
The '-wipeout' flag forces the removal of the vdisk even if it detected to
contain data.
Only one vdisk can be removed at a time if a '-wipeout' option is used. If one
fails to be removed the command still continues to remove the rest.
vdinfo
- prints out all vdisk information
Usage:
vdinfo [options]
[Vdiskname]
display a specific vdisk
-full
display all vdisk information
-raidc RCname
display vdisk information for the specified pool
Notes:
vdinfo will print out all vdisks' information if Vdiskname is not provided.
The default output is in the following format:
"Vdiskname RCname type attribute size ilun right dual-controller
lun_masking_flag status guiname"
vdmod
Usage:
- modify specific vdisk parameters

vdmod [Vdiskname] [options]
-gname [newgrpname]
-rw [r|w|rw]
-diskinfo [newdiskinfo]
-dualcontroller 0|1|2|3|4 (0 = AA, 1 = AP_0, 2 = AP_1, 3 = APL_0, 4 = APL_1)
133

SAN FS
-pn [port_num]
-threshold [percent]
-icmthreshold {index, percent}
-bitmap ON|OFF
get_rseqno
- get the environment variable RAID_SEQ_NO
Usage:
get_rseqno [options]
-assign
increment RAID_SEQ_NO to the next available value
get_vseqno
- get the environment variable VDISK_SEQ_NO
Usage:
get_vseqno [raidset_name]
set_vseqno
- set starting VDISK_SEQ_NO for a specified

pool
Usage:
set_vseqno [raidset_name] [seq_no]
get_luns
- get the environment variable

VDISK_LUN_BITMAP for all ports.
Usage:
get_luns
set_lun
- set the specified lun in the

VDISK_LUN_BITMAP of the specified port
Usage:
set_lun [lun] [port_number]
Note: If the lun is already set, a message is displayed stating the error.
134

SAN FS
reset_lun
- resets the specified lun in

VDISK_LUN_BITMAP of the specified port
Usage:
reset_lun [lun] [port_number]
Note: If the lun is already reset then a message is displayed stating the error.
sfs_backup_rconfig - copies the configuration area "dev/flash

/conf" on the flash and stores it in the
sanfs for backup purposes.
Usage:
sfs_backup_rconfig [RCname]
sfs_load_rconfig
Usage:
- loads the backup copy on the configura

tion stored on sanfs onto the flash.
sfs_load_rconfig [RCname]
Notes:
The environment variable OverWriteFromFlash is set.

A message telling the user to "reboot -i" in order to make the backup
configuration current is displayed.
vdgrow
- grows the virtual disk by the specified size.
Usage:
vdgrow [Vdiskname] [size_in_halfGB] [options]
-temp
indicates vdisk is temporary
-wipeout
forces a vdisk to grow
135

SAN FS
Notes:
Virtual disk grow will not succeed if partition misalignment is detected or the
current OS on the server is not on the supported list. Vdgrow cannot
guarantee that the partition information will be saved in these cases. But
using the '-wipeout' flag overrides these warnings and forces the virtual disk
growth.
Loss of the partition information can occur with the '-wipeout' option.
The '-wipeout' option will skip the procedure of generating an update disk
label. It will now be up to the user to update the label on the disk.
vdboot
- build the incore vdisk table
Usage:
vdboot [-add Vdiskname | -delete Vdiskname | -modify Vdiskname]
Notes:
Vdboot is called during boot up.
The add/delete flags are used to add a single vdisk into the incore table.The
add/delete flags are used to add a single vdisk into the incore table.
Supplying the '-add Vdiskname' will only bring that specific vdisk into
incore. If the vdisk does not exist on a sanfs then this command has no effect.
The '-delete Vdiskname' arguments are features for dual-controllers. The

vdisk is removed from the incore memory and unbounded.
The '-modify Vdiskname' setting is used in case during a vdgrow failure to

update the incore table. This will copy the updated version of the vdisk in
sanfs into the incore table. If one vdisk fails, the command still continues to
complete execution.
vdcontrol
- control the ONLINE attributes (to hosts) of a

vdisk
Usage:
vdcontrol -spinup|-shutdown|-qon|-qoff [options]
-hostif ctrlno portno
specifies which controller and host port vdcontrol is applied on
-vname Vnnnn
136

SAN FS
Notes:
vdcontrol only modifies the vd_t incore portion, it does not touch the vdisk
media copy.
The vdisk must be established in the vd_t table.
-spinup will have the quiescent off by default. -spinup will bring up the
stargd threads for the vdisk(s).
-shutdown will stop the stargd threads.
If vdiskname is NOT supplied, then vdcontrol applies to all vdisks

established in the pvdtbl.
There is no add/remove in the pvdtbl.

If -hostif is not supplied, vdcontrol will apply to all hostifs specified in the
vdisk(s).
probectrl
- probes the controller information of the box
Usage:
probectrl
Notes:
The following information is printed:

CtrlID Local/Remote PortType MaxScsiId SCSI_target_id_list IPAddr
HeartbeatState FirmwareVersion MemSize(MB) FreeMemSize(MB)
node_name,port_name."
If netparameters are not supported then IPAddr will display 'N/A'.
If on a single controller system, HeartbeatState will display 'N/A'.
__sfsshutdown
Usage:
- removes sv incore metadata

__sfsshutdown [-all | RCname]
Note: This command should be used before rconf -init, rconf -fullinit, or rconf -delete.
137

SAN FS
138
sfsparams
- displays all vital kernel variables for SV
Usage:
sfsparams

Enclosure Monitoring
The following commands are enclosure monitoring related commands.
encbuild
- initializes the internal enclosure table
Usage:
encbuild [options]
-v
print in verbose mode
Sample:
encbuild -v
encprint
- prints the data of enclosure table
Usage:
encprint
enconf
- manages the enclosure table
Usage:
enconf [-build] [-e enc_id | -w enc_wwn] [-print] [-backend]
-build
equal to encbuild
-print
equal to encprint
-e
addressing enclosure by enclosure ID
-w
addressing enclosure by enclosure WWN
-backend
list all backend drives for enclosures
Sample:
Display list of backend drives for enclosure 0

enconf -e 0 -backend
139

encstatus
- prints out the current status of a given

enclosure
Usage:
encstatus [-d Dc.s.1 | -e enc_id | -w enc_wwn] [-v]
-e
-w
-d
addressing enclosure by hard disk
-v
Notes:
The enclosure is addressed by -e, -w, or -d options. If none of the option is

used, this command prints out all enclosure status.
The command prints out a 4 byte numbers for each enclosure the byte 0 is the
current temperature reading of enclosure, Byte 1 is the status of fans, and
byte 2 is the status of power supplies.
A '1' in the bitmap of the status word indicates an error status corresponding
to the fan or power supply.
Use -v to get full text enclosure hardware status report.
Sample:
Display status of enclosure 0

encstatus -e 0
encled
- turn on or off the failure (amber) LED of hard

disk addressed by
Dc.s.1
140
Usage:
encled [on|off] [Dc.s.1]
On
turn failure LED of Dc.s.1 on
Off
turn failure LED of Dc.s.1 off

Sample:
Turn failure LED of D0.0.0 on

encled on D0.0.0
encbuzzer
- turn on or off the enclosure buzzer addressed

by -e or -w option.
Usage:
encbuzzer [on|off] [-e enc_id | -w seswwn]
On
turn buzzer of enclosure addressed by -e or -w on
Off
turn buzzer of enclosure addressed by -e or -w off
-e
-w
Sample:
Turn buzzer on.

encbuzzer on
141

ICM
ICM
The following commands are ICM related commands.
vdicm
- display partition and file system information on

vdisk(s)
Usage:
vdicm [options] [Vdiskname | all]
-k
print in kilobytes
-m
print in megabytes (default)
+|-[0-12]
set time zone adjustment
-v
-h
print help information
-V
print version number
Sample:
Display partition information for a single vdisk

vdicm V0001
Display partition information for all vdisks

vdicm all
icmopen
- specifies which vdisk and partition will be

explored
Usage:
icmopen [Vdiskname] [Partition_number]
Notes:
142
icmopen must be used before we can use the other ICM directory commands.
The Vdisk name and Partition number are currently case sensitive.
icmopen will check for valid vdisk name.
An invalid partition number will display nothing or the default partition.

ICM
Sample:
Explore VDisk V0002, partition 4

icmopen V0002 P4
icmexit
- exits file system browser
Usage:
icmexit
Note: icmexit should be used after the user is finished exploring the current partition.
icmcd
- change the current directory
Usage:
icmcd {Directory name}
Notes:
The directory name is case sensitive.
icmcd requires the user input a directory name.
Use "icmcd .." to go to the parent directory of the current directory. Using
"icmcd ." will remain in the current directory.
A directory name with space must be enclosed by {}.

Currently we only support single level directory change, e.g. "icmcd dir1",
but not "icmcd dir1/dir2".
Sample:
Change directories where directory name does not have a space

icmcd mydir
Change directories where directory name does have a space

icmcd {My Documents}
143

ICM
icmls
- display the directory entries inside the current

directory
Usage:
icmls -l
Notes:
144
"icmls" displays only the filename.
"icmls -l" displays the filename, file size, and modification time of the file (in
Greenwich Mean Time, GMT).
It is recommended to used "icmls -l", since for long file names "icmls" would
cause the display to be unaligned.
icmpwd
- display current path information
Usage:
icmpwd
Chapter 4
Using The ASCII Graphical User

Interface
The iQ1000 comes with a fully functional text-based ASCII Graphical User Interface that
provides quick access to administration functions without the use of a web browser. The
ASCII GUI requires no additional software and runs on a serial connection to your
administration workstation.
Note: The ASCII text-based GUI is one of three available interfaces for system
administration. See also Chapter 1, Using iQstor SAN Manager and Chapter 3, Using
the Command Line Interface.
To gain access to the ASCII GUI:

1
Attach a terminal or workstation to the iQ1000s serial port.
Set terminal type to VT100 with a baud rate of 9600 bps.
145
Chapter 4: Using The ASCII Graphical User Interface

Connecting to the GUI
Connecting to the GUI

At the raid; prompt, enter:
raid; agui [vt100 | dtterm | xterms | wyse75 ]
This gives you access to the RAID administration console window (see Figure 4-1 on
page 146).This provides basic information on the host interface, memory configuration,
disk names, RAID sets, back ends, hard disk availability, and status. It also provides
access to all administration commands.
Figure 4-1.
ASCII GUI Main Window
Navigating the ASCII GUI

Use the arrow keys to move between options in the ASCII GUI.
To select an administration option, type the first letter of the choice shown at the bottom of
the screen.
Using Administration Commands

You select the administration commands by typing the first letter of a choice shown on the
selection line at the bottom of the screen.
The administration commands enable you to:
146
Create and maintain RAID sets

Create and manage spares pools
Change the SCSI target ID when necessary
Maintain the system log

Reviewing Current RAID Sets
Reviewing Current RAID Sets

To review current RAID sets, select R[aidSets] from the Main selection line. This
takes you to the RAID Set Configuration window (see Figure 4-2).
Use the RAID Set Configuration window to review the current RAID sets (if configured).
To browse through RAID sets, select:
F[irst]
First RAID set (in sequence by set number)
L[ast]
Last RAID set
N[ext]
Next RAID set
P[revious]
Previous RAID set
Figure 4-2.
RAID Set Configuration Window
147

Creating a RAID Set
Creating a RAID Set

To add (create) a RAID set, select A[dd] from the Raid Sets selection line. Then follow
the instructions, step by step, to set value for the basic RAID set parameters, summarized
in Table 4-1.
Note: For the iQ1000, the controller ID, host port, and SCSI LUN should all be set to 0
for host interface selection.
When youve completed these steps, a new RAID Set Management window appears (see
Figure 4-8 on page 151). Use this window to fine-tune the configuration, if necessary.
Table 4-1.
Basic RAID Set Configuration Parameters
Parameter
Description
Name of RAID Set
Enter the RAID set name (example, R3).
RAID Set Type
Define the RAID level (0, 1, 3, or 5).
Initial Host Interface
Identify the host interface for the RAID set.
SCSI ID
Set the SCSI ID.
LUN
Set the Logical Unit Number.
Backend Disks
Backend devices.
Raid Set Configuration
Enter name of Raid Set: R3
Figure 4-3.
148
Naming the RAID Set

Creating a RAID Set
Enter name Raid Set Type (0, 1, 3 or 5)
Figure 4-4.
Selecting the RAID Level
Enter initial host interface - ctlr.hostport.scsilun: 0.0.0
Figure 4-5.
Selecting the Initial Host Interface
149

Adding Disks to the RAID Set

To add disks to the RAID set, select the disk number for the list of available disks. Once
selected, the drive will be shown in your RAID set.
Add disks as required.
When done, select Q[uit]. You will return to the Main menu for RAID set
configuration.
Select from: 0 - D0.0.0
3 - D0.1.0
1 - D1.0.0
4 - D1.1.0
2 - D2.0.0
5 - D2.1.0
Enter index from above (0 to 5) - A for all, m-n for range,

Q to quit:
Backends:
Enter initial host interface - ctrl.hostport.scsilun: 0.0.0
Figure 4-6.

Select from: 0 - D0.0.0
3 - D0.1.0
1 - D1.0.0
4 - D1.1.0
2 - D2.0.0
5 - D2.1.0
Enter index from above (0 to 5) - A for all, m-n for range,

Q to quit:
Backends: D0.0.0, D0.1.0, D2.1.0
Enter initial host interface - ctrl.hostport.scsilun: 0.0.0
Figure 4-7.
150
Choosing Disks in a RAID Set


Name: R5
Type: 5
Flags: Inactive Unused NoRfsck Bootmode: Auto
Raid Set Size: 17687072 blks (
Cache Size
:
2048 blks (
I/O Mode: read-write RW

Spares: Y
Zones: N
35003.453MB) IOSize:
1.000MB) Queues:
16 blks (
16
8.0K)
Host Interface: (1) M0.0.0

Backendsz:
Backends :
35843542 blks ( 17501.729MB) each

D0.0.0, D0.1.0, D2.1.0
Additional stargd Args:

Mem usage estimate
-L 16
9.204MB / C0 - 38
Raid Sets:[Q}uit[I]nst.[M]od.[A]dd[D]elete [F]st [L]st [N]xt [P]rv [O]pts
Figure 4-8.
Complete RAID Set Configuration Window
151

Changing the Host Interface SCSI ID
Changing the Host Interface SCSI ID

Use the Host Port Configuration window to change the SCSI ID of the host interface.
1
Select M[odify] to set a new SCSI ID.
When done, select I[nstall] to store the new SCSI ID.

Name: R5
Type: 5
Flags: Inactive Unused NoRfsck Bootmode: Auto
Raid Set Size: 17687072 blks (
Cache Size
:
2048 blks (
I/O Mode: read-write RW

Spares: Y
Zones: N
35003.453MB) IOSize:
1.000MB) Queues:
16 blks (
16
8.0K)
Host Interface: (1) M0.0.0

Backendsz:
Backends :
35843542 blks ( 17501.729MB) each

D0.0.0, D0.1.0, D2.1.0
Additional stargd Args:

Mem usage estimate
-L 16
9.204MB / C0 - 38
Raid Sets:[Q}uit[I]nst.[M]od.[A]dd[D]elete [F]st [L]st [N]xt [P]rv [O]pts
Host Port Configuration

Controller 0
Host Port A
Host Port B
SCSI ID = 5
SCSI ID = 5
Host Ports: [Q]uit [I]nstall [M]odify
Figure 4-9.
152
Host Port Configuration Window

Modifying a RAID Set
Modifying a RAID Set

To modify a RAID set:
1
Select an inactive RAID set as the current set.
Select M[odify].
Use this window to modify any of the RAID set parameters, including:
RAID Name
RAID Type
I/O Mode
Bootmode
Spares
Zones
Forwarding
Drop
IOSize
Cache Size
Queues
Host Interfaces
Args
Note: See Chapter 3, Configuration Parameters, for information on how to select values
for iQ1000 RAID set parameters.
To skip the cursor, between fields, use the arrow keys, <Tab>, or <Enter>.
To end editing, hit the <Esc> key twice.
When you are done, select I[nstallation] in the Main menu to store the new
configuration.
Deleting a RAID Set

To delete a RAID set:
1
Select an inactive RAID set as the current set.
Select D[elete].
153

Configuring a Spares Pool

The Spare Device Configuration window shows the currently defined spares pools. You
can use this window to add and delete disks or modify a disks configuration.
Spare Device Configuration

D2.1.0
Spares: [Q]uit [I]nstall [M]odify [A]dd [D]elete
Figure 4-10.
Spare Device Configuration Window
Adding a Disk to a Spares Pool

To add or create a new disk in the pool:
1
Select A[dd].
Specify the disk name.
Deleting a Disk to a Spares Pool

To delete a disk from the pool:
1
Select D[elete].
Modifying Disk Parameters

To modify the configuration of a disk in the pool:
154
Select M[odify].
Edit the drive parameters.
When done, hit <Esc> twice.
Select I[nstallation] in the Main menu to store the new configuration.

Spare Device Configuration

Spares : D1.1.0
35566370 Hot Ctlr Any Unused Working
Spares: [Q]uit [I]nstall [M]odify [A]dd [D]elete
Figure 4-11.
Modify Spare Device Parameters
155

Viewing Drive Information
Viewing Drive Information

Use the Device Information window to see information about the installed drives, RAID
sets, drive model and specifications.
For details on installed disks:
1
Select I[nformation].
Browse by using the selections in the Dinfo selection line:
F[irst]
First drive (in sequence by disk number)
L[ast]
Last drive
N[ext]
Next drive
P[revious]
Previous drive
Device Information
Device : D0.1.0
Vendor : QUANTUM
Retries:
0 reads
Sectors : 35566499
Cylinders:
8057
Zones: : 0
Zn
Product
0 writes
Serial No: PCB=20-11600

" QM318000TD-SCA RPM: 7200 Vers: N1B0
0 other
Sector Size: 512

Disk Size: 17366.545MB
Heads: 20
Sectors/Trk: 228
Blk Lo
Blk Hi S/T Zn
Blk Lo Blk Hi
Dinfo: [Q}uit [F]irst [L]ast [N]ext [P]revious
Figure 4-12.
156
Drive Information Window
S/T

System Log Information
System Log Information

Use the System Log Messages window to browse the system log.
You can review log records one at a time by using the selections in the Log selection line:
F[irst]
First message (in sequence by message number)
L[ast]
Last message
N[ext]
Next message
P[revious]
Previous message
System Log Messages

Type: INFO
@
0
Msg : Syslog Boot @ time (seconds) 0
Log: [Q}uit [F]irst [L]ast [N]ext [P]rev
Figure 4-13.
Drive Information Window
157
158
Chapter 5
GUI Error Messages

The table below contains all possible exception messages generated in RAID operations.
Those marked with HIGH priority are the most often encountered error messages.
Table 5-1.
RAID Operation Exception Messages
Operation
Failure
Message
Priority
General
RAID command
execution error
RAID command execution error: [error_msg].
Failure in
refreshing
RAID/POOL/
data
Failed to query RAID: [err_msg].
Internal memory
allocation failure
Failed to write return value: [err_msg].
159
Chapter 5: GUI Error Messages
Specified
object does
not exist
Refresh
enclosure
160
Specified DISK
does not exist
DISK [disk] does not exist.
Specified RAID
does not exist.
RAID [raid] does not exist.
Specified POOL
does not exist.
POOL [pool] does not exist.
Specified
VDISK does not
exist
VDISK [vdisk] does not exist.
Specified source
VDISK does not
exist
VDISK [source] does not exist.
Specified
VDISK is not a
snapshot
VDISK [snapshot] is not a Snapshot.
Specified source
VDISK has no
local mirror
VDISK [source] does not have a Local Mirror.
Specified RR
does not exist
Remote Replication VDISK ([source], [rsite]) does not exist.
Refresh
enclosure data
error
Failed to refresh Enclosure [BOXID]: [err_msg].
Create
POOL
Delete
POOL
More than 1
backend are
specified
POOL creation supports only one RAID backend selection.
Specified
backend RAID
does not exist
RAID [bkend] does not exist.
Specified
backend RAID
is not free
RAID [bkend] is already in use.
Fail to get RAID

sequence
number
Failed to obtain RAID sequence number.
Fail to create a
RAID of type 7
Failed to create POOL.
Firmware
prompts FAIL:
Cannot open
device
Reboot is required to make all RAID backends active.
POOL creation
not successful
finally
Failed to create POOL (sfs).
Deleting a POOL is not supported.
161
Expand
POOL
162
RAID type 7 is
not supported by
firmware
POOL expansion is not supported in firmware [version].
More than 1
backend are
specified
POOL creation supports only one RAID backend selection.
Specified
backend RAID
does not exist
RAID [bkend] does not exist.
Specified
backend RAID
is not free
RAID [bkend] is already in use.
Specified POOL
is not found in
sfsinfo after
expansion.
POOL [pool] cannot be found.
POOL
expansion not
successful
finally
Failed to expand POOL [pool].
Shrink
POOL
Shrinking POOL is not supported.
Set POOL
cache
Specifying POOL cache is not supported.
Create
RAID
Fail to get RAID

sequence
number
Failed to obtain RAID sequence number.
No backends are
specified.
No backends specified.
Incorrect
backend amount
RAID level 1.
RAID Level 1 creation requires two backends.
Incorrect
backend amount
RAID level 3.
RAID Level 3 creation requires the number of backends to be a

power of 2 plus 1 (2n+1).
Incorrect
backend amount
RAID level 5.
RAID Level 5 creation requires at least three backends.
One of the
specified
backend DISKs
does not exist
DISK [backend] does not exist.
One of the
specified
backend DISKs
is a SPARE.
DISK [backend] is used as a SPARE.
One of the
specified
backend DISKs
is not free.
DISK [backend] is already in use.
One of the
specified
backend RAIDs
does not exist
RAID [backend] does not exist.
One of the
specified
backend RAIDs
is not free.
RAID [backend] is already in use.
RAID creation
not successful
finally
Failed to create RAID.
163
Remove
RAID
Specified RAID
is not free.
RAID [raid] is used by a POOL.
RAID removal
not successful
finally
Failed to remove RAID [raid].
Specified DISK
is a SPARE
DISK [disk] is already used as a SPARE.
Specified DISK
is not free
DISK [disk] is already in use.
SPARE creation
is not successful
finally
Failed to add DISK [disk] into SPARE disk pool.
Specified DISK
is not a SPARE
DISK [disk] is not a SPARE.
Specified
SPARE is used
in data recovery
Cannot remove. SPARE [disk] is in use.
SPARE removal
is not successful
finally
Failed to remove DISK [disk] from SPARE disk pool.
Create
VDISK
No VDISK is
found in
vdadd output
or the new
created VDISK
is not found in
vdinfo
Failed to create VDISK.
Modify
VDISK
VDISK group
modification is
not successful
Failed to modify VDISK [vdisk].
Expand
VDISK
VDISK
expansion is not
successful
Failed to expand VDISK [vdisk].
VDISK size
after expansion
is not the same
as expected
VDISK [vdisk] is expanded to [size] MB.
Create
SPARE
Remove
SPARE
164
Remove
VDISK
Create
Snapshot
Specified
VDISK contains
data
Removing VDISK [vdisk] may cause data loss. Continue?
VDISK removal
is not successful
Failed to remove VDISK [vdisk].
Specified source
VDISK is not a
NORMAL one
Cannot create Snapshot. VDISK [source] is not a NORMAL

VDISK.
No VDISK is
found in
snapadd
output or the
new created
VDISK is not
found in
vdinfo
Failed to create a Snapshot for VDISK [source].
Snapshot
removal is not
successful
finally
Failed to remove Snapshot [snapshot].
Modify
Snapshot
Reset
Snapshot
Remove
Snapshot
165
Create
LocalMirror
Specified source
VDISK is not a
NORMAL one
Cannot create a Local Mirror. VDISK [source] is not a

NORMAL VDISK.
Specified source
VDISK have
been mirrored
already
VDISK [source] is already mirrored on [lmirror].
Specified source
VDISK have
been remote
replicated
already
Cannot create a Local Mirror. VDISK [source] is used for

remote replication.
LocalMirror
creation is not
successful
finally
Failed to create a Local Mirror for VDISK [source].
Failed to
suspend the
specified
LocalMirror
Failed to suspend Local Mirror ([source], [lmirror]).
Split
LocalMirror
Failed to split
the specified
LocalMirror
Failed to split Local Mirror ([source], [lmirror]).
Destroy
LocalMirror
Failed to destroy
the specified
LocalMirror
Failed to remove the Local Mirror [lmirror] of VDISK [source].
Suspend
LocalMirror
Resync
LocalMirror
RevResync
LocalMirror
166
Create
RemoteRep
Specified source
VDISK is not a
NORMAL one
Cannot create a Remote Replication. VDISK [source] is not a

NORMAL VDISK.
Specified source
VDISK have
been local
mirrored already
Cannot create a Remote Replication. VDISK [source] is used for

Local Mirroring.
RR creation is
not successful
finally
Failed to create a Remote Replication for VDISK [source].
Start
RemoteRep
Failed to start
the specified RR
Failed to establish a Remote Replication ([source], [rsite]).
Suspend
RemoteRep
Failed to
suspend the
specified RR
Failed to suspend the Remote Replication ([source], [rsite]).
Rejoin
RemoteRep
Failed to rejoin
the specified RR
Failed to rejoin the Remote Replication ([source], [rsite]).
RevRejoin
RemoteRep
Failed to
revrejoin the
specified RR
Failed to reverse rejoin the Remote Replication ([source],

[rsite]).
Split
RemoteRep
Failed to split
the specified RR
Failed to split the Remote Replication ([source], [rsite]).
Disconnect
RemoteRep
Failed to
disconnect the
specified RR
Failed to suspend the Remote Replication ([source], [rsite]).
Specified LUN
mask already
exists
LUN masking entry ([vdisk], [wwn]) already exists.
Failed to create a
new LUN mask
Failed to create LUN masking entry ([vdisk], [wwn]).
Specified LUN
has been mapped
LUN [hlun] of [wwn] is mapped to VDISK [mapped_vdisk].
Failed to create a
new LUN mask
Failed to create LUN mapping entry ([vdisk], [wwn], [hlun]).
Set events
for
RemoteRep
Create
LUNMask
Create
LUNMap
167
Remap LUN
Repair
Repair
168
Specified LUN
has not been
mapped
LUN [hlun] of [wwn] is not mapped to a VDISK.
Specified LUN
has been mapped
to another
VDISK
LUN [hlun] of [wwn] is already mapped to VDISK

[mapped_vdisk].
Failed to remap
LUN
Failed to remap VDISK [vdisk] from LUN [hlun] to [new_hlun]

of [wwn].
Specified DISK
is healthy
DISK [disk] is healthy. No repair needed.
Specified DISK
is free
DISK [disk] is not a backend in a RAID.
Container RAID
is healthy
RAID [raid] is healthy. No repair needed.
Container RAID
is under data
construction
RAID [raid] is under data reconstruction.
Container RAID
is failed
RAID [raid] cannot be repaired.
Failed to repair
the DISK
Failed to repair DISK [disk] in RAID [raid].
Specified DISK
is healthy
DISK [disk] is healthy. No replacement needed.
Specified DISK
is free
DISK [disk] is not a backend in a RAID.
Container RAID
is healthy
RAID [raid] is healthy. No replacement needed.
Container RAID
is under data
construction
RAID [raid] is under data reconstruction.
Container RAID
is failed
RAID [raid] cannot be repaired.
Failed to repair
the DISK
Failed to replace DISK [disk] in RAID [raid].
Browse ICM
directory
List
firmware file
Upgrade
firmware
List RAID
configuratio
n file
Specified
partition does
not exist
Partition #[par] does not exist on VDISK [vdisk].
Failed to list files

in the specified
directory.
Failed to list files in directory "[dir]".
Firmware
directory not
found
Firmware directory "./Firmware" not found.
Failed to list files

in firmware
directory
Failed to list firmware files. Please check directory "./Firmware".
Failed to
download
firmware file to
controller
Failed to download firmware [firmware] to RAID controller.
Timeout in
firmware
upgrade
Firmware upgrade timeout.
Failure in
firmware
upgrade
Failed to upgrade firmware.
RAID
configuration
directory not
found
RAID configuration directory "./Config" not found.
Failure in list
files in RAID
configuration
directory
Failed to list RAID configuration files. Please check directory "./

Config".
169
170
Index
B
BootUp Command 112
E
Enclosure Monitoring Commands 139
I
ICM Commands 142
IQStor 1
L
Local Mirroring Commands 126
LUN Mapping Commands 123
LUN Masking Commands 121
O
Online Help Command 103
P
Parameters 95
R
RAID level 97
RAID level, choosing 97
RAID set
parameters 96, 97
RAID Set Config Command 105
Remote Replication Commands 125
S
SAN FS Commands 129
SCSI Port Config Command 104
Snapshot Commands 116
Spare Pool Command 111
SV Log Command 127
SV Utilities Commands 128
iQ1000 User Guide
171

IQstor Admin Guide

Caricato da

Informazioni sul documento

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

IQstor Admin Guide

Caricato da

Copyright:

Formati disponibili

iQstor SAN Manager

iQstor Networks, Inc.

P/N 800-006623 REV 1

Copyright 2002 iQstor Networks, Inc. All rights reserved.

Registered Rights Legend

iQstor 1000 Administrators Guide

Using iQstor SAN Manager

iQ1000 User Guide

RAID Configuration Parameters and Maintenance

RAID Set Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

Using the Command Line Interface

iQ1000 User Guide

Using The ASCII Graphical User Interface

Connecting to the GUI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GUI Error Messages

iQ1000 User Guide

iQ1000 User Guide

Using iQstor SAN Manager

Understanding the iQstor Solution

Friendly graphical user interface.

Comprehensive implementation of iQstor management functionality.

Multiple iQstor devices and multi-user support.

iQstor 1000 Administrators Guide

Chapter 1: Using iQstor SAN Manager

3-tier (client, logic and resource) management model

iQstor 1000 Administrators Guide

Chapter 1: Using iQstor SAN Manager

JAVA Applet Server

iQstor 1000 Administrators Guide

Chapter 1: Using iQstor SAN Manager

iQstor 1000 Administrators Guide

Chapter 1: Using iQstor SAN Manager

Solaris 2.7/8 SAN Manager with modem setup

Win2k/NT, Java Plug-in (JRE)v1.4.0_01, Netscape6.0/IE6.0 or above

Win 2k/NT, Email server, SNMPc v5

Management Console (MC)

Solaris 2.7 or above.

iQstor 1000 Administrators Guide

Chapter 1: Using iQstor SAN Manager

Download the latest software from: ftp.iqstor.com

Manually Starting Middleware

Start with ESP2 support:

Start with ESP2 disabled:

GUI Start Message

iQstor 1000 Administrators Guide

Chapter 1: Using iQstor SAN Manager

Middleware Start-up Options

WWW service port # (Def: 8002)

iQstor SAN Manager service port # (Def: 8102)

MC UDP communication port # (Def: 31926)

ESP2 UDP communication port # (Def: 31927)

GZIP switch in communication (Def: ON)

SSMON channel support switch (Def: OFF)

SNMP channel support switch (Def: ON)

SAN subnet (e.g., 192.168.1)

Enable FC clustering configuration (Def: OFF)

Default POOL cache size in MB (Def: 4)

Socket binding retry times (Def: 1)

Socket binding retry delay time in seconds (Def: 15)

Number of subsequent ports to bind (Def: 100)

Use environment variable BOXID as enclosure ID (Def: ON)

IQstord Start-up Options

Alternate Ways to Start the Middleware

(== ./IQstord -ssmon on -snmpch on)