Quantum ADIC User Manual
™
ADIC Management Console
4.4
User’s Guide
Scalar i2000 ADIC Management Console User’s Guide, 6-00064-08, March 2007, Made in USA.
Quantum Corporation provides this publication “as is” without warranty of any kind, either express or implied, including
but not limited to the implied warranties of merchantability or fitness for a particular purpose. Quantum Corporation
may revise this publication from time to time without notice.
COPYRIGHT STATEMENT
Copyright 2007 by Quantum Corporation. All rights reserved.
Your right to copy this manual is limited by copyright law. Making copies or adaptations without prior written
authorization of Quantum Corporation is prohibited by law and constitutes a punishable violation of the law.
TRADEMARK STATEMENT
Quantum, DLT, DLTtape, the Quantum logo, and the DLTtape logo are all registered trademarks of Quantum
Corporation.
SDLT and Super DLTtape are trademarks of Quantum Corporation.
Published: March 2007 Document Number: 6-00064-08
Contents
1 About This Guide and Your Product 1
Explanation of Symbols and Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Other Documents you Might Need . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Getting More Information or Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
2 Description 3
ADIC Management Console Functionality. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Using the SAN Client. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Using a Library Management Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
ADIC Management Console Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Event Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Heartbeat. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Health Checks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Channel Zoning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Data Mover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Scalar® Firewall Manager / Virtual Private SAN®. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
extended VPS® . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Virtual Private Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
SNMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Library RMU Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Network Discovery. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Configuration Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Updating Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Obtaining Drive Dumps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Command Flow Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
3 Getting Started 7
Installation Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Server System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Client System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Before Installing AMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Installing the AMC Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Installing the Server on a Windows System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Installing the Server on a UNIX System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
ADIC Management ConsoleUser’s Guide iii
Launching the AMC Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Launching a Windows Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Launching a UNIX Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Installing the AMC Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Before Installing the Client. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Installing a Windows AMC Client. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Installing a UNIX Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Launching the AMC Client. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Launching a Windows Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Launching a UNIX Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Connecting to the Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Logging on. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Logging off. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Exiting the AMC Client. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Shutting Down the AMC Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
4 Frequently Asked Questions 19
What is a SAN? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
What if I cannot see any SAN components after I install?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
What is the i-platform series? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Can I manage a SAN from an i-platform library?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Do I have to install a server or client? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Can I configure e-mail even if I skip that step during installation?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
How do I interpret interface components?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
How do I create a SAN administrator account?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
What is a portal? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
How do I create user accounts? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
How do I create portals for my users? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
What privileges does each user type have? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
How do I update firmware? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
How do I modify the discovery configuration? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
How do I create policies? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
5 The SAN Management Interface 23
Menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Panels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Received Event Trap Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Reading the SAN Management Information Panels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Navigation Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Device Numbering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Graphical Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Data Panel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Status/Message Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Common SAN Management Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Auto-Categorize. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Creating a new Category . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Move Items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Find . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
iv Contents
6 Managing User Accounts 35
Changing the Administrator Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Understanding User Privilege Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Creating, Modifying and Deleting User Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Adding a New User Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Modifying a User Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Deleting a User Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
7 Working with Portals 39
Creating a New Portal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Modifying a Portal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Deleting a Portal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Setting Permissions for Portal Access. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
8 Working with Categories and Views 43
Working with SAN Categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Auto-Categorizing the SAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Creating a new Category . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Renaming a Category . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Deleting a Category. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Moving a Category . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Working With Category Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Moving Items by Drag and Drop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Moving Items by Using the Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Working With Views. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Opening Saved Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Creating Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Saving Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Deleting Views. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Searching the Current View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Reporting the Current View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
9 Performing Administrative Tasks 53
Configuring E-mail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Configuring Policies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Discovering the SAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Rediscovering a Segment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Discovering a particular appliance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Configuring the SNMP Community Strings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Managing the SAN Appliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Refreshing Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Saving and Loading the Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Updating Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Using Restart. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Getting Information About a Library. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Displaying RMU Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
ADIC Management Console User’s Guide v
10 Configuring Channels and Devices 63
Managing the SCSI Channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Rescanning the SCSI Channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Resetting the SCSI Channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Configuring the SCSI Channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Managing the Fibre Channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Rescanning the Fibre Channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Resetting the Fibre Channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Configuring the Fibre Channel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Understanding Port Mode Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Understanding Connection Type Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Host Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Loop ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Frame Size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Managing a Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Updating Firmware on a Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Editing Device Maps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Pre-Assigning Device Numbers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
11 Configuring SAN Access 71
Enabling Licensed Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Data Mover Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Using Channel Zoning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Installing HRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Installing the Host Registration Service for Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Installing the Host Registration Service for Solaris . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Installing the Host Registration Service for HP-UX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Installing the Host Registration Service for AIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Installing the Host Registration Service for Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Using Scalar Firewall Manager (SFM). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Installing SFM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Configuring Access Through SFM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Adding SFM Hosts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Deleting SFM Hosts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Using eVPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Installing eVPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Configuring Access Through eVPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Adding or Modifying eVPS Hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Deleting eVPS Hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Using the eVPS View Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Using VPM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
12 Troubleshooting the SAN 89
Monitoring and Managing Event Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Printing the Event Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Saving a Copy of Currently Displayed Entries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Interpreting the Event Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Setting the Event Trap Threshold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Receiving Event Traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
vi Contents
Monitoring Received Event Traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Monitoring the LED Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Using Identify. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Monitoring Environmental Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Using Health Check. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Performing Health Check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Configuring Health Check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Checking the Heartbeat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Obtaining a Drive Dump . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Checking the Command Flow Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Interpreting CFL Output. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
A Glossary 103
ADIC Management Console User’s Guide vii
viii Contents
About This Guide and Your Product
WARNING
CAUTION
Note
This guide contains information and instructions necessary for the normal operation and management of
the ADIC Management Console. This guide is intended for system administrators, operators, or anyone
interested in learning about or using the ADIC Management Console. Be aware that administrator level
privileges are required to configure many of the features described in this guide.
Explanation of Symbols and Notes
The following symbols appear throughout this document to highlight important information.
INDICATES A POTENTIALLY HAZARDOUS SITUATION WHICH, IF NOT
AVOIDED, COULD RESULT IN DEATH OR BODILY INJURY.
Indicates a situation that may cause possible damage to equipment, loss of
data, or interference with other equipment.
Indicates important information that helps you make better use of your system.
Other Documents you Might Need
The following documents are also available for this product. These documents can be found on the product
CD or at www.quantum.com/support
• Scalar i2000 Planning Guide (6-00418-xx)
• Scalar i2000 User’s Guide (6-00421-xx)
• Scalar i2000 Installation Guide (6-00752-xx)
• ADIC Management Console User’s Guide (6-00064-xx)
• System, Safety, and Regulatory Information Guide (6-00618-xx)
ADIC Management Console User’s Guide 1
.
Note
Release Notes are also available for this product. The Release Notes describe changes
to your system or firmware since the last release, provide compatibility information, and
discuss any known issues and workarounds. The Release Notes can be found in the
product box or at www.quantum.com/support
Getting More Information or Help
More information about this product is available on the Service and Support website at
www.quantum.com/support
including answers to frequently asked questions (FAQs). You can also access software, firmware, and
drivers through this site.
For further assistance, or if training is desired, contact Quantum:
. The Service and Support Website contains a collection of information,
Quantum Technical Assistance Center in the
USA:
For additional contact information: www.quantum.com/support
To open a Service Request: www.quantum.com/esupport
For the most updated information on Quantum Global Services, please visit: www.quantum.com/support
www.quantum.com/osr
2 About This Guide and Your Product
Description
This chapter describes AMC (the ADIC Management Console). AMC is a fully-featured management tool
for storage-area networks (SANs) with storage networking controller (SNC) or management control blade
(MCB) connectivity. A SAN is a network linking servers or workstations to disk arrays, tape backup systems,
switches, bridges, and other devices, over high-speed transports such as Fibre Channel or gigabit Ethernet.
SANs keep storage traffic away from network traffic without compromising rapid access to stored data. See
Figure 1
Figure 1 Example of typical storage-area network (SAN)
.
ADIC Management Console User’s Guide 3
AMC provides several levels of access permissions and the ability to customize views and portals. By
keeping track of different client views, you can recall a saved view from any client. The server provides
security features by maintaining account names and passwords on behalf of the client application. AMC also
provides functionality to support server-less backup, tools for LUN mapping, and easy channel zoning.
ADIC Management Console Functionality
AMC uses a three-tier client/server model. The three parts are: agent, server, and client. The agent
communicates with the server and other managed agents via both Simple Network Management Protocol
(SNMP) and SCSI over IP (SOIP) protocols. The server communicates with the agent as well as with the
client or clients.
The Java Remote Method Invocation (RMI) API is used to communicate from the client to the server. You
can install one or more instances of the server onto systems in the SAN running any of the UNIX or Windows
platform software that are remote from MCBs or SNCs. Do not install more than one server per client
system.
Using the SAN Client
The SAN client for the Scalar series of libraries is the AMC. Using AMC is an easy way to manage Scalar
libraries as part of a SAN solution. When you choose to install both server and client from the product CD—
this is called the Full installation—the default client is the AMC SAN client. The default AMC client consists
of a Java-based user interface window and a trap event window. You can install one or more instances of
the AMC client in your SAN.
Using a Library Management Client
If your SAN includes a library in the intelligent platform (i-platform) series—for example a Scalar i2000 or a
Pathlight VX—you can launch a library management client from the AMC SAN interface. The library
management client launched in this way is identical to the interface that runs on the library’s touch screen.
ADIC Management Console Features
AMC provides status and controls for library and SNC features. The following features define the
management capabilities of AMC:
Event Logging
You can retrieve and view event logs. Filtering based upon the significance of events simplifies fault
isolation. For more information, refer to Monitoring and Managing Event Logs
Policies on page 54.
Reports
You can print or save reports that you have configured to meet your reporting requirements. For more
information, refer to Reporting the Current View
on page 51.
on page 89 and Configuring
4 Description
Heartbeat
AMC monitors system components to ensure continuity of service. If an SNC or MCB is no longer available,
the server component notifies monitoring clients.For more information, refer to Checking the Heartbeat
page 99.
on
Health Checks
Instantaneous and periodic health checks allow monitoring of each appliance and the devices attached to
it. For more information, refer to Using Health Check
on page 98.
Channel Zoning
Channel zoning is a means of managing the access security between SAN connections and SCSI or FC
devices on a channel by channel basis.
• Channel zoning can be used to secure access between a server and its storage, segregating them,
for example, from other servers and their respective storage.
• The default settings allow all SAN connections to access all SCSI or FC devices.
Data Mover
The SNC can move data directly between storage devices that are attached to it. Data Mover frees-up
valuable system resources on the server and substantially increases the speed of backup and restore
operations.
Data Mover is the engine for server-free backup and restore and hierarchical storage management
applications that support the extended copy specification (ANSI T10/99-143r1).
Scalar® Firewall Manager / Virtual Private SAN
Scalar® Firewall Manager (SFM) and Virtual Private SAN® (VPS) technology enable SANs with multiple
users to share the same connectivity channels in order to access the same or different storage elements by
creating multiple virtual private connections.
SFM and VPS manage the access between an initiator (user, host, system) and a target/logical unit number
(LUN).
extended VPS
The extended Virtual Private SAN® (eVPS) functionality enables access control and mapping of FC and
SCSI devices and provides the flexibility to map the attached devices to any user-defined LUN separately
and individually for each Fibre Channel attached host. Because eVPS is backwardly compatible, current
users of VPS and SFM can preserve current mappings when their licenses are upgraded.
®
®
Virtual Private Map
Virtual Private Map (VPM) technology enables legacy and new systems equipped with SCSI host bus
adapters to access Fibre Channel devices. VPM allows Fibre Channel and SCSI target devices to be
mapped to private SCSI host channels.
ADIC Management Console User’s Guide 5
SNMP
SNMP (Simple Network Management Protocol) community strings are a part of the software agent’s
messaging functionality that serve to group network devices into logical collections for management
purposes. The community strings on the server must match those on the appliance(s) you wish to manage.
Three strings are defined:
• Read— for querying the appliance
•Write—for controlling the appliance
• Trap—for receiving event messages from the appliance
The appliance can maintain 32 read and 32 write community strings and one trap community string.
A set of commands is provided for manipulating the Read and Write SNMP community strings. These
strings logically group devices into management communities.
Library RMU Support
Data obtained from a Scalar library’s RMU (remote management unit) includes global status data, drive
data, and mover data. These data are displayed in the AMC data panel. RMU data can also be displayed
from a library’s right-click menu.
Security
Four levels of user privilege are defined, each with specific capabilities. For more information, see Table 1
on page 36.
Network Discovery
Network discovery allows you to locate any appliance based on network addresses and ranges. This allows
management of an appliance without knowing the specific Internet Protocol (IP) address beforehand.
Configuration Options
You can set up an appliance with a number of non-default parameters, channel settings, and event
management variables. For more information, refer to Performing Administrative Tasks
Configuring SAN Access
on page 71.
on page 53, and
Updating Firmware
You can update appliance and device firmware from the client. For more information, refer to Updating
Firmware on page 60.
Obtaining Drive Dumps
You can download and save the drive's transaction and error logs. Sometimes this information is requested
by service personnel for analysis. For more information, refer to Obtaining a Drive Dump
on page 99.
Command Flow Logging
Logs of the SCSI commands processed by the SNC can be retrieved for analysis by service personnel. For
more information, refer to Checking the Command Flow Log
6 Description
on page 100.
Getting Started
Note
The AMC server communicates over Ethernet to its clients. To manage a SAN, install an instance of the
server onto any open-platform system that is connected via Ethernet to each SNC and each AMC client.
You must install at least one instance of the server to manage your SAN with AMC. The AMC client can be
launched from any connected system on which it is installed. For intelligent-platform libraries, a library
management client can also be launched from the AMC SAN client.
A client capable of managing the SAN cannot be launched from the library
management client on an i-platform library.
Installation Requirements
Minimum configuration guidelines for each system are presented below for the AMC 4.4 version of software.
Server System Requirements
Java Runtime Environment 1.4.1 is installed with AMC. The version of the operating system you choose
must support this level.
Windows
The installation requirements for Microsoft® Windows® 2000, Microsoft® Windows® XP, or Microsoft®
Windows® 2003 are as follows:
• Windows 2000, Microsoft Windows XP, or Microsoft Windows 2003
• Minimum memory: 96MB
• Free hard disk space: 40MB
• Ethernet with TCP/IP protocol installed
AIX
The minimum installation requirements for AIX are as follows:
• AIX® 5.3
• 128 MB system memory
• 60 MB of free disk space on destination partition
ADIC Management Console User’s Guide 7
HP-UX
Note
The installation requirements for HP-UX are as follows.
•HP-UX
• 80MB or greater system memory
• 80MB free disk space in the destination partition
TM
11.0 or later
Solaris
The installation requirements for Solaris are as follows.
•Solaris
• 80MB or greater system memory
• 60MB free disk space in the destination partition
• Common Desktop Environment (CDE)
TM
9 (5.9). The maintenance level must support JDK 1.4.1
Limitations in the OpenWindows Desktop Environment inhibit drag and drop
editing functions in AMC’s Device Mapping and VPM dialog boxes. If you
need to use either of these AMC features, you must use the CDE rather than
the OpenWindows Desktop Environment.
Linux
The installation requirements for Red Hat Linux are as follows.
• Advanced Server 2.1 or Enterprise Server 3.0
• Minimum memory: 80 MB
• Free hard disk space: 60 MB
• Ethernet with TCP/IP protocol installed
• Video adapter board for graphical input
Client System Requirements
Windows
• Windows 2000, Microsoft Windows XP, or Microsoft Windows 2003
• Minimum memory: 96 MB
• Free hard disk space: 30 MB
• Ethernet with TCP/IP protocol installed
UNIX platforms
Follow the requirements for the appropriate server platform, above.
8 Getting Started
Before Installing AMC
CAUTION
CAUTION
AMC uses Ethernet to communicate. Your Ethernet network must be in place before AMC is installed.
Verify that you have enough space, about 100 MB, in the temporary
directory to be able to complete the installation.
1 Obtain the network parameters for the client, the server, as well as any other Scalar libraries in the SAN.
• Use static IP addresses.
• If the Scalar libraries in the SAN are not on the same TCP/IP subnet as the server, assign a
default network gateway address and/or route table entries.
2 Save this configuration information for future reference.
3 Run Ethernet cable from the server to the network hub or switch.
4 Run Ethernet cable from clients to the network hub.
5 Run Ethernet cable from the network hub to the Scalar libraries in the SAN.
6 Configure the network according to the procedures for the operating system you are using.
Installing the AMC Server
To manage your SAN, you must install an instance of the server onto a system that is connected by Ethernet
to your storage products and the systems where the clients are running. This server cannot be identical to
the server embedded in the i-platform libraries.
Installing the Server on a Windows System
Install the AMC server after you have completed the steps in Before Installing AMC on page 9.
1 Load the product CD.
2 Click the install link under the ADIC Management Console.
3 Click OK.
This starts the InstallAnywhere program, which prompts you throughout the installation.
4 When you are prompted to choose an installation set, select Server Only if you do not wish to run the
AMC client on that host, or Full if you do.
AMC server version must match AMC client version. When the client
and the server are different versions, they may not be able to
communicate.
5 When you are asked to configure network discovery, be sure the network segment you define includes
the SAN components you identified in Step 2
of Before Installing AMC on page 9.
6 The e-mail configuration portion of the installation requires the following information:
• Network name of your mail server, for example, MyMailServer.
• Valid e-mail account for the specified SMTP server, for example, Joan.Dow
• Valid password for this e-mail account, for example, *u!nBe
ADIC Management Console User’s Guide 9
• E-mail address that you want mail recipients to see when AMC contacts them. This need not be an
CAUTION
CAUTION
e-mail address that has been previously validated by a working mail server, for example,
AMCAlert@MyCompany.com
7 Proceed to Launching the AMC Server
on page 11.
Installing the Server on a UNIX System
Install the AMC server after you have completed the steps in Before Installing AMC on page 9.
1 Load the product CD.
2 Navigate to the ADIC Management Console folder.
3 Open the folder and copy the image file to a temporary folder on the host.
Verify that you have enough space, about 100 MB, in the temporary
directory to be able to complete the installation. On Solaris systems,
if the /tmp directory is not large enough for InstallAnywhere to
operate, the installation fails, even if the temporary directory is
resized later.
Set the IATEMPDIR environment variable to the name of a directory
that is big enough. InstallAnywhere uses that directory instead of
/tmp.
To set the variable for Bourne shell (sh), ksh, bash and zsh:
$IATEMPDIR=/your/free/space/directory $ export
IATEMPDIR -
To set the variable for C shell (csh) and tcsh:
$ setenv IATEMPDIR /your/free/space/directory
4 From the temporary folder, type: chmod 777 <filename>, for example,
chmod 777 MC043SOL.bin
and press Enter.
5 If the temporary folder is NOT in the user's path, type [space]./<filename>, for example,
./MC043HPX.bin
and press Enter.
This launches the installation from the current directory.
If the temporary folder is in the user's path, simply type: <filename> (including extension),
for example,
MC043LIN.bin
and press Enter.
This starts the InstallAnywhere program, which prompts you throughout the installation.
6 When you are prompted to choose an installation set, select Server Only if you do not wish to run the
AMC client on that host, or Full if you do.
AMC server version must match AMC client version. When the client
and the server are different versions, they may not be able to
communicate.
10 Getting Started
7 When you are asked to configure network discovery, be sure the network segment you define includes
Note
Note
the SAN components you identified in Step 2
8 The e-mail configuration portion of the installation requires the following information:
• Network name of your mail server, for example, MyMailServer.
• Valid e-mail account for the specified SMTP server, for example, Joan.Dow
• Valid password for this e-mail account, for example, *u!nBe
• E-mail address that you want mail recipients to see when AMC contacts them. This need not
be an e-mail address that has been previously validated by a working mail server, for example,
AMCAlert@MyCompany.com
of Before Installing AMC on page 9.
9 Proceed to Launching the AMC Server
.
Launching the AMC Server
After you launch the server, be sure it completes network discovery before you launch the client. When a
server has completed network discovery and is ready to receive connections, the message Ready.
Waiting for commands is displayed above the prompt in the server window.
Launching a Windows Server
Launch the server at the beginning of your SAN Management session, but do not exit the server when you
are finished. Leave the server running.
1 Select the Start button, point to Programs.
2 Point to ADIC Management Console. Then select Server.
If you installed the AMC server on a non-default path, launch it from that location instead.
Once you launch the server, a window opens on your monitor. You will know that network discovery has
been completed when you see the message Ready. Waiting for commands followed by a
command prompt.
If your configuration consists of many large or remote network segments, discovery can take several
minutes to complete.
Do not close the server window. Follow the exit procedure in Shutting Down the
AMC Server on page 17 to shut the server down.
3 Proceed to Launching the AMC Client
on page 13.
Launching a UNIX Server
Launch the server at the beginning of your SAN Management session, but do not exit the server when you
are finished. Leave the server running.
• To launch the AMC server from a UNIX system, type Server from a terminal window, and press
Enter.
Server <enter>
Uppercase S is mandatory.
ADIC Management Console User’s Guide 11
The server window is displayed.
Note
If your configuration consists of many large or remote network segments, discovery can take several
minutes to complete.
Do not close the server window. Follow the exit procedure in Shutting Down the
AMC Server on page 17 to shut the server down.
Proceed to Launching the AMC Client
on page 13.
Installing the AMC Client
The AMC Client is used to manage your SAN.
Before Installing the Client
If you have already installed an instance of the client, and want to install another, or if you have already
installed an instance of the AMC server using the Server Only installation option, proceed to either Installing
a Windows AMC Client or to Installing a UNIX Client.
If you have already installed an instance of AMC using the Full option, and do not want to install another
client, proceed to Launching the AMC Client
Otherwise, complete the sections Before Installing AMC
9 before proceeding with the client installation.
Installing a Windows AMC Client
An AMC Windows client can run on Windows 2000 or Windows XP.
1 Load the product CD.
on page 13.
on page 9 and Installing the AMC Server on page
2 Click the install link under the ADIC Management Console.
3 Click OK.
This starts the InstallAnywhere program, which prompts you throughout the installation.
4 When you are prompted to choose an installation set, select Client Only.
5 Proceed to Launching the AMC Client
on page 13.
Installing a UNIX Client
An AMC client can run over Solaris, Linux, HP-UX, or AIX.
1 Load the product CD.
2 Navigate to the ADIC Management Console folder.
3 Open the folder and copy the image file to a temporary folder on the host.
12 Getting Started
CAUTION
Verify that you have enough space, about 80 MB, in the temporary
Note
directory to be able to complete the installation. On Solaris systems,
if the /tmp directory is not big enough for InstallAnywhere to operate,
the installation fails, even if the temporary directory is resized later.
Set the IATEMPDIR environment variable to have the name of a
directory which is big enough. Then InstallAnywhere will use that
directory instead of /tmp.
To set the variable for Bourne shell (sh), ksh, bash and zsh:
$IATEMPDIR=/your/free/space/directory $ export
IATEMPDIR -
To set the variable for C shell (csh) and tcsh:
$ setenv IATEMPDIR /your/free/space/directory
4 From the temporary folder, type: chmod 777 <filename>, e.g.
chmod 777 MC043SOL.bin
5 If the temporary folder is NOT in the user's path, type [space]./<filename>, e.g.
./MC043SOL.bin
This launches the installation from the current directory.
If the temporary folder is in the user's path, simply type: <filename> (including extension),
e.g.
MC043SOL.bin
This starts the InstallAnywhere program, which prompts you throughout the installation.
6 When you are prompted to choose an installation set, select Client Only.
7 Proceed to Launching the AMC Client
.
Launching the AMC Client
To manage your SAN, connect your client to an instance of the AMC server that is remote to the Scalar
i2000, Scalar i500, or Pathlight VX.
When a remote server is ready to receive connections, the message Ready.
Waiting for commands is displayed above the prompt in the server
window.
Use one of the following procedures to start the client, depending on the operating system your client is
running:
Launching a Windows Client
If you launch the client before the remote server has completed discovery, the client will not attach to the
server.
1 If you accepted the defaults during the installation, select the ADIC Management Console program
group on the Start menu to see the client icon. If you chose a program group other than the default, go
there instead.
ADIC Management Console User’s Guide 13
2 Select Client to launch the program.
CAUTION
Note
Note
Note
When the client launches, both the ADIC Management Console window and a Receive Event Traps
window appear. If event traps are issued, messages appear in the Received Event Traps window. You
cannot close the Received Event Traps while the client is running but you can minimize it.
3 If the remote server is running on a system that is also remote to the client, the client window displays
a prompt for you to connect to a server. Proceed to Connecting to the Server
If the remote server is running on the same system as the client, connection to the server is automatic.
The client window displays a logon prompt. Proceed to Logging on
After the initial log in, set up another SAN administrator. Setting up a
SAN administrator will disable the default admin logon name. Refer to
Adding a New User Account on page 37
on page 15.
.
.
Launching a UNIX Client
If you launch the client before the remote server has completed discovery, the client will not attach to the
server.
1 To start the HP-UX, AIX, Solaris, or Linux client, start a terminal window and type
Client <enter>
and press Enter.
Uppercase C is mandatory.
When the client launches, both the ADIC Management Console window and a Received Event Traps
window appear. If and when event traps are issued, messages appear in the Received Event Traps
window. You cannot close the Received Event Traps while the client is running. You can minimize it.
2 If the server is running on a system that is remote to the client, the client window prompts you to connect
to a server. Proceed to Connecting to the Server
If the server is running on a system that is local to the client, connection to the server is automatic. The
client window displays a logon prompt. Proceed to Logging on
.
on page 15.
Connecting to the Server
If the client is local to the server, connection is automatic.
1 In the Connect to Server dialog box, type the network name or IP address of the remote server.
If you type the IP address of an i-platform library, you will not be able to
manage your SAN. The servers installed on i-platform libraries are used to
manage library operations.
2 Select OK.
If your client is already launched, you can display the dialog box by selecting
the Session menu, and then selecting Connect to Server.
3 Proceed to Logging on
14 Getting Started
on page 15.
Logging on
CAUTION
The Log On dialog box is displayed automatically when a new connection to the server has been
established. It can also be displayed when you select Session and then select Log On. The Logon dialog
box is also displayed when you select the Log On toolbar button.
In the Logon dialog box, type "admin" as the user name. Type "password" as password, if this is the first
time you have logged on.
After the initial log in, set up another SAN administrator. Setting up a
SAN administrator will disable the default admin logon name. Refer to
Adding a New User Account on page 37
If you make an error logging on, the logon dialog box disappears and Unsuccessful log on appears in the
Status/Message Area of the screen. Refer to Status/Message Area
and re-type your logon information.
If your log on is successful, the client displays a status bar as it downloads master portal data. For more
about the master portal and portals in general, refer to Working with Portals
.
on page 33. Select Session > Log On,
on page 39.
ADIC Management Console User’s Guide 15
The default master portal consists of all the devices discovered, according to the discovery configuration
file. When the download is complete, the AMC screen is filled with data. For information about this screen,
refer to Reading the SAN Management Information Panels
on page 24.
Logging off
Log off after you finish using AMC. You will not need to restart the client before your next management
session.
1 Select the Session menu, then select Log Off.
A warning dialog box is displayed.
You can also launch the Log Off dialog box by selecting the Log Off toolbar button.
The warning dialog box is displayed.
2 Select Yes if you want to log off. If you select Yes, you are prompted to save your current view, if it has
changed.
The Save Current View dialog box is displayed.
16 Getting Started
Select No if you have changed your mind. If you select No, you are returned to your view.
Note
3 Select Yes if you have made changes to the view that you want to save.
Select No if you do not want to save changes.
Exiting the AMC Client
Exit stops the AMC client application and closes its window.
Use Exit if you want to restart the client application the next time you use AMC. Normally you will only log
off, and leave the client running between sessions.
1 After logging off, select Session > Exit.
The Exit dialog box is displayed.
2 Select Yes if you want to exit. Your view is closed.
Select No if you have changed your mind.
If you select No, you are returned to your closed view.
Shutting Down the AMC Server
The way that the AMC server is shut down is the same for all platforms.
You cannot shut down the server that is embedded in an i-platform library.
1 After you have logged off (refer to Logging off
AMC Client), position the cursor after the command prompt in the server window.
2 Type "exit", then press the Enter key.
The server window disappears.
on page 16), and exited the client (refer to Exiting the
ADIC Management Console User’s Guide 17
18 Getting Started
Frequently Asked Questions
This section provides a reference of commonly asked questions and their answers.
What is a SAN?
A storage area network (SAN) links servers or workstations to disk arrays, tape backup systems, switches,
bridges, and other devices, over high-speed transports such as Fibre Channel or gigabyte Ethernet.
What if I cannot see any SAN components after I install?
If you did not change the sample network segment statement (1.1.1.1 - 1.1.1.2) that appears in the
Configure Discovery Settings screen of the installation wizard, SAN components will not be discovered.
Follow the instructions in Discovering the SAN
statements that reflect your network environment. Add a separate statement for every subnet. Instructions
are also given in this section for re-discovering the SAN.
on page 55 to modify the sample statement and to add
What is the i-platform series?
The intelligent platform (i-platform) libraries all have integrated management services within intelligent
storage devices designed specifically for operation in a storage network.
Can I manage a SAN from an i-platform library?
No. For libraries in the i-platform—such as the Scalar i2000, Scalar i500, and Pathlight VX—AMC is
available only from a remote client.
Do I have to install a server or client?
To manage the SAN you must install at least one instance of the AMC server and client on at least one
remote system. Refer to Before Installing AMC
per client computer. You should upgrade both server and client when or if you upgrade, so that the server
and the client communicate most effectively.
on page 9. Do not install more than one instance of a server
To manage a Scalar i2000 remotely (that is, not from the touch panel) you must install a SAN client.
ADIC Management Console User’s Guide 19
Can I configure e-mail even if I skip that step during installation?
Refer to Configuring E-mail on page 53.
How do I interpret interface components?
Refer to Reading the SAN Management Information Panels on page 24.
How do I create a SAN administrator account?
Refer to Adding a New User Account on page 37.
What is a portal?
A portal is a collection of storage area networking devices that represent a particular user’s universe. The
SAN administrator’s default portal is the entire set of SAN-capable appliances and associated storage on
the subnet to which the AMC has access. This is called the master portal. Other users are granted privileges
to subsets of the master portal by the SAN administrator.
How do I create user accounts?
Refer to Creating, Modifying and Deleting User Accounts on page 37.
How do I create portals for my users?
Refer to Creating a New Portal on page 39.
What privileges does each user type have?
See Table 1 on page 36.
How do I update firmware?
For the SNC and the devices connected to it, refer to Updating Firmware on page 60. For i-platform libraries,
use the appropriate library management client.
How do I modify the discovery configuration?
Refer to Discovering the SAN on page 55.
20 Frequently Asked Questions
How do I create policies?
For the SAN, refer to Configuring Policies on page 54. For i-platform libraries, use the appropriate library
management client.
ADIC Management Console User’s Guide 21
22 Frequently Asked Questions
Loading...