Quantum SNC FIRMWARE 4 User Manual

SNC

Firmware 4 User’s Guide

ADVANCED DIGITAL INFORMATION CORPORATION

www.adic.co

The information contained in this document is subject to change without notice.

This document contains proprietary information which is protected by copyright. All rights are reserved. No part of this document may be photocopied, reproduced, or translated to another language without prior written consent of ADIC.

ADIC shall not be liable for errors contained herein or for incidental or consequential damages (including lost profits) in connection with the furnishing, performance or use of this material whether based on warranty, contract, or other legal theory.

All trademarks within this document are the property of their respective owners.

All rights reserved. No part of this document may be copied or reproduced in any form or by any means, without prior written permission of ADIC Europe, ZAC des Basses Auges, 1 rue Alfred de Vigny, 78112 Fourqueux, France.

ADIC Europe assumes no responsibility for any errors that may appear in this document, and retains the right to make changes to these specifications and descriptions at any time, without notice.

This publication may describe designs for which patents are pending, or have been granted. By publishing this information, ADIC Europe conveys no license under any patent or any other right.

ADIC Europe makes no representation or warranty with respect to the contents of this document and specifically disclaims any implied warranties of merchantability or fitness for any particular purpose. Further, ADIC Europe reserves the right to revise or change this publication without obligation on the part of ADIC Europe to notify any person or organization of such revision of change.

Every effort has been made to acknowledge trademarks and their owners. Trademarked names are used solely for identification or exemplary purposes: any omissions are unintentional.

ADIC is a registered trademark and ADIC Europe is a trademark of Advanced Digital Information Corporation.

ADIC USA 11431 Willows Road NE Redmond, Washington 98052-4952 Tel.: 1-800-336-1233 Fax: 1-425-881-2296

ADIC Europe ZAC des Basses Auges 1, rue Alfred de Vigny 78112 Fourqueux, France Tel.: 33-0-1-30-87-53-00 Fax: 33-0-1-30-87-53-01

ADIC-Germany GmbH&Co.KG Eschenstraße 3

89558 Böhmenkirch

Germany Tel: 49-0-7332-83-0 Fax: 49-0-7332-83-135

Published: December 2004 Document Number: 6-00676-03 Rev A

Contents

1 Introduction 1

Intended Audience. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Explanation of Symbols and Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Getting More Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

ADIC Technical Assistance Center . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

2 Description 3

Compatible SNC Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Firmware 4 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Data Path Conditioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Multi-Path Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

WWN Change Capability. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

eVPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Fibre Channel Host Port Failover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

3 Setup and Configuration Routines 5

Preparing SAN Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Preparing Fibre Channel Hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Preparing Fibre Channel Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Preparing SCSI Tape or Disk Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Preparing SCSI Hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Preparing FC Tape or Disk Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Configuring a Fibre Channel Host SAN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Configuring a SCSI Host SAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Configuring the Ethernet Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Using DHCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Setting the Date and Time. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Setting the Real Time Clock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Adding a Host System Running Timeserver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Disabling the Timeserver Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Synchronizing the Real Time Clock with the Timeserver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Creating User Accounts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Configuring Ports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Mapping Multiple Paths to Targets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Configuring Channel Zoning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Configuring VPM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

SNC Firmware 4 User’s Guide iii

Configuring eVPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Using the WWN Lock Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Configuring Host Port Failover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Replacing a SCSI Drive. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Saving a Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Updating Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Updating Firmware Using FTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Updating Firmware Using the Serial Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Loading a Configuration File Using HyperTerminal. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Changing the WWN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Before You Change the WWN on a Replacement SNC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Changing the WWN for all FC Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Changing a WWN for one FC port. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Clearing Changes to the WWN for all FC ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Clearing Changes to the WWN for one FC Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Retrieving Information About Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Event Log Dump . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Retrieving the Code 43 Dump File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Working With Command Flow Log Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

4 Service Port Command Reference 39

Managing the SNC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

5 Diagnostic Command Reference 143

Boot Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

Entering Diagnostic Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

Diagnostic Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144

Restoring Normal Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147

6 Troubleshooting 149

Event Codes and Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150

Checking Event Logs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150

Checking Reported Event Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

Action Reference Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154

Start MAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154

Visually Inspecting the LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154

Checking for Problems on Attached Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155

Checking Host Versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156

Checking SNC Product Versions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156

Checking ADIC Management Console Version. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156

Checking Firmware Code Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156

Checking Hardware Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156

Checking Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157

Performing Health Check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157

Checking the Host Event Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157

Database Full MAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157

Device Access MAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158

iv Contents

Checking Fibre Channel Port Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158

Checking SCSI Channel Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159

Checking Channel Zoning Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159

SCSI Channel MAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159

Getting SCSI Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159

Checking Attached SCSI Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160

Comparing Listed versus Physical Devices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160

Comparing Listed versus Supported Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160

Checking SCSI Bus Termination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161

Checking for Multiple SCSI IDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161

Checking Device Type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162

Examining SCSI Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162

Examining SCSI Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163

Performing SCSI Health Check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163

Performing SCSI Loop Back Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163

Testing SCSI Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164

Isolating SCSI devices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164

Restoring SCSI Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165

Fibre Channel MAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165

Verifying Fibre Channel Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166

Testing the GBIC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166

Examining Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166

Performing Fibre Channel Loop Back Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167

Testing Fibre Channel Optical Cable. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167

Replacing Fibre Channel Cable. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167

Replacing Fibre Channel Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168

MAP for the SNC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168

Observing Operational LED Behavior . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168

Temperature MAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169

Interpreting Problems in the Temperature Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169

Receiving Temperature Warnings or Alarms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169

Receiving Fan Speed Warnings or Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169

Power MAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170

Ethernet MAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170

Service Port MAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174

Check the RS-232 Cable. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174

Checking the Connection with Boot Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175

VPM MAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175

Checking Virtual Private Map Access Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175

Verifying SCSI Host Configuration Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176

Verifying VPM Device Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176

SFM/VPS/eVPS MAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177

Checking SFM/VPS/eVPS Access Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177

Verifying FC Host Configuration Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178

Removing an FC Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179

Verifying SFM/VPS/eVPS Device Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180

A Vendor Unique Codes 181

B Glossary 183

SNC Firmware 4 User’s Guide v

vi Contents

Introduction

This manual contains information necessary for command line management of SNCs (Storage Networking Controllers) in the 5000 and 6000 product lines, as well as for the the SNC 4000. The SNC 6404 is sometimes referred to as the FC blade (FCB) or the I/O blade (IOB). With the restrictions, noted for individual commands or command sequences, command line operation of the SNC 6404 is also within the scope of this document. The level of the firmware code (4.4x.xx) appropriate to a particular SNC is stated in the compatibility matrix portion of the Release Notes for the current library or product release.

Intended Audience

This guide is intended for system administrators, operators, service engineers, or anyone interested in learning about or using SNC Firmware 4. Users are expected to understand the SAN architecture they are implementing before using this firmware.

Explanation of Symbols and Notes

The following symbols appear throughout this document to highlight important information.

Note

CAUTION

WARNING

The following is a list of formatting conventions used throughout this document:

Italics • Book title, for example, Quick Start Guide

Bold • Menu name, or command on a menu, for example, Setup

SNC Firmware 4 User’s Guide 1

Indicates important information that helps you make better use of your system.

Indicates a situation that may cause possible damage to equipment, loss of data, or interference with other equipment.

INDICATES A POTENTIALLY HAZARDOUS SITUATION WHICH, IF NOT AVOIDED, COULD RESULT IN DEATH OR BODILY INJURY.

• File name, for example, v44020.bin

Wizard

Courier • command line input and output

Getting More Information

If you want more information about your product, go to the ADIC website or contact ADIC Technical Assistance Center (ATAC).

ADIC Technical Assistance Center

If problems cannot be solved with the aid of this document or if training is desired, contact the ADIC Technical Assistance Center (ATAC).

In the USA: 800-827-3822

In Europe and Japan: 00-800-9999-3822

For other contact numbers: www.adic.com/contact

To open a Service Request online: www.adic.com/techsup

2 Introduction

Description

This chapter describes the functionality of the Storage Networking Controller (SNC) Firmware 4.

The SNC interface between storage and host provides Fibre Channel to SCSI connectivity or Fibre Channel to Fibre Channel connectivity.

The SNC firmware enables you to map addresses across and between different interfaces, to configure private maps for security purposes, to condition the data path, and to preserve the persistency of the address maps when systems, devices, switches, and the SNC are turned on and off. The SNC supports up to 2048 unique storage devices across multiple interfaces.

Compatible SNC Hardware

This SNC firmware is the operational firmware for the SNC 4000, the Pathlight 5000, SNC 5100, SNC 5101, SNC 6101, and the Fibre Channel I/O blades in the Scalar i2000 Library and the Pathlight VX solution.

Firmware 4 Features

Firmware 4 released functionality builds upon the feature set of previous releases, although not all features are available across product lines. The Firmware 4 code includes the following features:

Data Path Conditioning

Data path conditioning technology is a set of utilities in the SNC that protect the integrity of the paths carrying data. They make data transmission faster and more reliable, and they improve overall system availability. Health checks and heartbeats are conducted at intervals established by the administrator so that fault conditions can be discovered prior to moving data through the fabric. Error recovery is performed in the data path to prevent errors in the Fibre Channel layer from causing data transmission (a backup or a restore) to fail. The error recovery feature requires no administrator intervention. The Host Registration Service (HRS) is a small utility that can be loaded onto attached hosts, to provide data path checks from the host perspective.

SNC Firmware 4 User’s Guide 3

Multi-Path Mapping

Multi-path mapping enables an administrator to map a single Fibre Channel-attached storage device through all Fibre Channels on the SNC to provide redundancy. Both manual and automatic versions of the multi-path feature are available. The automatic version of this feature is used by specialized, highavailability host software. Both versions require a license.

WWN Change Capability

The world wide name (WWN) change capability enables an administrator to change the WWN on the SNC. Text is posted during the procedure regarding the requirement to maintain a globally unique name. A password is required in order to complete the change. The world wide node name or just the world wide port name can be changed. This feature is being implemented to facilitate SNC replacement.

eVPS

The extended virtual private SAN (eVPS) feature enables an administrator to map any physical device to any logical unit number (LUN) on any host. This is an additional layer of LUN mapping that is unique for each initiator attached to the SNC through a Fibre Channel port. eVPS automatically provides backwards compatibility with virtual private SAN (VPS), a legacy mapping system, so you can upgrade to firmware that supports this feature transparently. Basic configuration is provided through command line interface (CLI) configuration functions, but the recommended management tool is the graphical user interface for your SNC—either the ADIC Management Console or the Library Management Console. eVPS also supports inband management through Application Programming Interface (API) extensions to the existing maintenance in/out functions supported by VPS.

Fibre Channel Host Port Failover

This feature establishes one Fibre Channel port as the operating port and the other as the alternate port. The alternate port is on standby for the operating port. If an operating port fails, the alternate port takes over transparently. The configuration is persistent. This feature requires two Fibre Channel ports to be configured as targets in point-to-point mode.

Both SNC FC connections or at least two FC blade connections are run to a FC switch. A single connection to the FC host is then run from the FC switch. No explicit changes to the host driver, host bus adapter firmware or application software is required.

Note

This feature requires a license. Please contact your ADIC representative.

4 Description

Setup and Configuration Routines

CAUTION

This section contains detailed procedures for basic configuration:

• Preparing SAN Components

• Configuring a Fibre Channel Host SAN

• Configuring a SCSI Host SAN

• Configuring the Ethernet Network

• Using DHCP

• Setting the Date and Time

• Creating User Accounts

• Configuring Ports

For using special features:

• R

eplacing a SCSI Drive

• Configuring Channel Zoning

• Configuring Host Port Failover

• Configuring eVPS

This procedures in this section are not intended to be used with FCBs in Scalar i2000 libraries or Pathlight VX systems.

• Using the WWN Lock Mode

• Configuring Host Port Failover

For maintaining and troubleshooting the SNC:

eplacing a SCSI Drive

• R

• Saving a Configuration File

• Updating Firmware

• Loading a Configuration File Using HyperTerminal

• Changing the WWN

• Retrieving Information About Events

SNC Firmware 4 User’s Guide 5

Preparing SAN Components

Before connecting FC (Fibre Channel) or SCSI cables to the SNC, make sure that the SNC:

• Has desktop or rack mount hardware installed

• Has Ethernet cable from the network hub or switch connected to its 10/100 BaseT RJ-45 Ethernet port for remote management and optional service access

• Has a null modem RS-232 cable connected from its 9-pin service port to a service terminal (PC or laptop) and a terminal emulation session (for example, HyperTerminal) running on the service terminal at 19.2K-8-N-XON/XOFF

Preparing Fibre Channel Hosts

Make sure that the host systems:

• Are running the required versions of host platform software and operating system patches. Download what you need from the manufacturer’s website

• Have compatible Fibre Channel HBAs (Host Bus Adapters) and the appropriate HBA firmware, BIOS, and device driver installed

• Have HBA(s) configured for Fibre Channel (FC) Loop if they are attached to the SNC, or Point-ToPoint, if attaching to an FC switch

• Have labeled FC cables attached to them, but not yet attached to the SNC (they may be attached to an intermediate switch, if there is one)

• Have the optional HRS (Host Registration Service) installed if virtual private map (VPM), Scalar firewall manager (SFM) or extended virtual private SAN (eVPS) is being used

Preparing Fibre Channel Switch

If an FC switch or FC disk subsystem is being used, make sure that:

• The switch or subsystem has been configured

• Its FC cables are labeled and have been run to the SNC, but are not yet connected

• The FC cables are long enough to ensure adequate strain relief

• The FC cables are secured

• The switch is turned on and operational

Refer to the device manufacturer’s documentation for configuration information.

Preparing SCSI Tape or Disk Devices

If SCSI devices are being used, make sure that:

• SCSI IDs have been configured

• The SCSI cables have been labeled and are connected to the SNC

• The SCSI cables have adequate strain relief

• The SCSI cables are secured with mounting screws

• The SCSI devices are turned on and operational

Refer to the device manufacturer’s documentation for configuration information.

6 Setup and Configuration Routines

Preparing SCSI Hosts

Make sure that the host systems:

• Are running the required versions of host platform software and operating system patches

• Have compatible HBAs (host bus adapters) and the appropriate HBA firmware, BIOS and device driver installed. Download what you need from the manufacturer’s websites.

• Have labeled SCSI cables attached to them and to the SNC

• Have the optional HRS (host registration service) installed to facilitate use of VPM (virtual private map)

• Are turned on

Preparing FC Tape or Disk Devices

If FC devices are being used, make sure:

• That the FC cables have been labeled and are connected to the SNC

• That the FC cables have adequate strain relief

• That the FC cables are secured

• That the FC devices are turned on and operational

Refer to the device manufacturer’s documentation for configuration information.

Configuring a Fibre Channel Host SAN

After you have prepared system components according to the section Preparing SAN Components on page 6, configure the SAN. Configure features such as HPF before attaching hosts to the SAN.

CAUTION

1 Connect a service terminal to the service port. For the location of this port, see Figure 1

the User’s Guide for your SNC.

Note

2 Turn the power on the SNC. For the location of this switch, refer to the User’s Guide for your SNC.

Allow sufficient time for the SNC to boot up completely.

3 Press the Enter key on the service terminal.

If the prompt is not displayed, go to Service Port MAP

Within one minute, the RDY LED on most SNCs should start flashing once per second and the done executing startup script message should be displayed on the service terminal. On the SNC 6101, it may take a little longer.

Do not use this procedure if you are using an FCB in a Scalar i2000 Library or a Pathlight VX system. Use the appropriate graphical user interface.

on page 11, or

Instructions for connecting a service terminal are included in the User’s Guide for your SNC.

on page 174.

For the location of the RDY LED, see Figure 1

SNC Firmware 4 User’s Guide 7

on page 11, or the User’s Guide for your SNC.

From the service terminal, issue the initializeBox command to return the SNC to its default settings. For more information about this command, refer to initializeBox

on page 84. This command

causes the SNC to reboot.

CAUTION

SNC. This command resets the Fibre and SCSI Channels, clears the device map and the event log, and disables all enabled features.

4 Issue the version command to make sure that the proper version of the operational firmware is

Only use the initializeBox command on a new or a replacement

installed. For more information about this command, refer to version

5 Configure the Ethernet connection. For instructions, refer to Configuring the Ethernet Network

on page 126.

on page

11.

6 Optionally, add a user account for telnet. For instructions, refer to Creating User Accounts

on page 15.

7 Issue the targets command from the service terminal. It can take several minutes for the devices to

be available for discovery. For more information about this command, refer to targets

If results are not as expected, follow the procedures in the SCSI Channel MAP

on page 121.

on page 159.

8 Issue the hostTypeShow command to view host type settings for the Fibre Channel ports. For more

information about this command, refer to hostTypeShow

Note

If you are using SFM, VPS, or eVPS, go to the next step. SFM, VPS, and eVPS use an internal setting for the host type.

on page 78.

Table 1 Host Type Settings for Fibre Channel Ports

Host Type Alias Usage

AIX Not Applicable AIX

AS400 as/400, os/400, os400 AS400

Autosense/NT Not Applicable functions identically to “NT”

NT windows “NT” is the default setting

Gateway fcr-2, pv-136t-fc, adic snc Gateway

Generic Not Applicable The host does not use a supported host type

HPUX hp-ux HPUX

Linux Not Applicable Linux

Netware Not Applicable Netware

Solaris sun, linux Solaris

Unknown Not Applicable The host type is unknown or is based on the value

set by VPS

Unisys Not Applicable Unisys

If the hosts to be connected are not the type shown in the output of the command, issue the setHost command to set the host type for each incorrect Fibre Channel port. For more information about this command, refer to setHost [port],"OS"

on page 106.

9 Turn off the FC host(s).

8 Setup and Configuration Routines

CAUTION

10 If you are going to configure host port failover (HPF), refer to Configuring Host Port Failover on page 24

before turning on the FC host(s).

11 Connect the FC cables from the FC HBA(s) to the SNC (or from the intermediate switch to the SNC).

12 Turn on the FC host(s).

• If the appropriate FC connection status LEDs for the attached hosts are not on, check FC cables.

If this SNC is a replacement, and the WWN of the replacement SNC must be the same as the WWN of the replaced SNC, refer to Changing

the WWN on page 30.

•See Figure 1 series SNC or SNC 6101.

• You may have to change the polarity of the FC cables.

• You may have to change port configuration. For instructions on doing so, refer to C on page 16.

• If problems persist, go to the Fibre Channel MAP

13 Issue the fcShow command to show the status of the FC interface that is installed and connected. For

more information about this command, refer to fcShow [level]

14 Issue the fcShowDevs command to show SCSI target devices that are connected as seen by the Fibre

Channel interface. For more information about this command, refer to fcShowDevs

• Look for FW State=Ready for each FC interface. If any other state is specified, go to the Fibre

Channel MAP on page 165.

• If FW State=Ready, but devices are not all displaying, go to the SCSI Channel MAP

15 Use appropriate host system utilities for disk and/or tape. If all devices are not available, reboot the host

system(s) and check again.

16 Save the configuration to a location you will be able to access if the SNC fails. Refer to S

Configuration File on page 27.

17 Issue the fcShowNames command and save the output to a location you will be able to access if the

SNC fails. For more information about this command, refer to fcShowNames

on page 11 for the placement of the FC1 and FC2 connection status LEDs on a 5000

onfiguring Ports

on page 165.

on page 67.

on page 69.

on page 159.

aving a

on page 69.

18 Attach the hosts (or the switch to which the hosts are attached) to the SNC.

Configuring a SCSI Host SAN

Note

After you have prepared system components according to the section Preparing SAN Components on page 6, configure the SAN. Configure features such as AMP before attaching hosts to the SAN.

1 Connect a service terminal to the service port of your SNC. For the location of this port, see Figure 1

page 11, or the User’s Guide for your SNC.

Note

SNC Firmware 4 User’s Guide 9

If you are running the 6101 or the 6404, you cannot configure a SCSI Host SAN.

Instructions for connecting a service terminal are included in the User’s Guide for your SNC.

2 Turn the power on the SNC. For the location of this switch, refer to the User’s Guide for your SNC.

Allow sufficient time for the SNC to boot up completely.

3 Press the Enter key on the service terminal.

If the prompt is not displayed, go to Service Port MAP

on page 174.

Within one minute, the RDY LED should start flashing once per second and the done executing startup script message should be displayed on the service terminal.

For the location of the RDY LED, see Figure 1

on page 11, or the User’s Guide for your SNC.

4 From the service terminal, issue the initializeBox command to return the SNC to its default

settings.

For a discussion of this command and its output, refer to initializeBox

on page 84.

Only use the initializeBox command on a new or a replacement

CAUTION

SNC. This command resets the Fibre and SCSI Channels, clears the device map and the event log, and disables all enabled features.

5 From the service terminal, issue the version command to make sure the proper version of operational

firmware is installed. For more information about this command, refer to version

6 Issue the

scsiHostChanSet command, setting the channel where the host will be connected to

"Target." For more information about this command, refer to scsiHostChanSet [channel],[mode]

on page 126.

page 100.

7 Issue the

snReset command. For more information about this command, refer to snReset [channel]

on page 116.

8 Issue the

pmFeatureEnable "licensekeystring" on page 129.

vpmFeatureEnable command. For more information about this command, refer to

CAUTION

following the procedure specified above, the preferred interface for managing VPM is the graphical user interface.

While it is acceptable to enable VPM from the command line by

• If you are going to use automatic multi-pathing (AMP), go to R

eplacing a SCSI Drive on page 25.

• If you configured AMP, issue the mapRebuildDatabase command. For more information about this command, refer to mapRebuildDatabase

on page 90.

9 To determine what device IDs are available for use, issue the targets command.

For an example of the targets command and its output, refer to targets

on page 121. Take note of the target devices to which you have access. The numbers you need are in the "Idx" column. If you are using AMP, targets will appear twice in the list. Do not map any target more than once.

10 Configure the Ethernet connection.

For instructions, refer to Configuring the Ethernet Network

11 Issue the

setScsiAssign [devID], [channel], [id], [lun]

setScsiAssign command. For more informationabout this command, refer to

on page 106.

on page 11.

While it is possible to configure VPM assignments from the command

CAUTION

line, the code to be manipulated can be so complex, that users are encouraged to use the graphical user interface.

12 Issue the showScsiAssign command.

10 Setup and Configuration Routines

• Verify that all target devices are available to the host system.

• Use appropriate host system utilities for disk and/or tape.

• If results are not as expected, refer to V

13 Save the configuration to a location you will be able to access if the SNC fails. Refer to S

Configuration File on page 27.

14 Attach the hosts to the SAN.

PM MAP on page 175 or Start MAP on page 154.

aving a

Configuring the Ethernet Network

CAUTION

Note

The SNC can be accessed over an Ethernet connection in addition to access by means of the service port.

1 Connect a service terminal to the service port. For the location of this port, see Figure 1

the User’s Guide for your SNC.

Note

The recommended interface for FCBs in the Scalar i2000 or Pathlight VX solution is the graphical user interface.

If you are configuring an SNC 4000, 51xx, or 6101, you can choose to use DHCP instead of static IP addresses. Refer to Using DHCP

Instructions for connecting a service terminal are included in the User’s Guide for your SNC.

on page 11, or

Figure 1 SNC connector and LED panel

RDY LED

Note

FC1 and FC2 connection LEDs

The placement of the LEDs, SCSI ports, and service port on your SNC may not be the same as in this example. Refer to the Hardware User’s Guide for your SNC.

Ethernet port

service port

SNC Firmware 4 User’s Guide 11

CAUTION

2 Issue the hostNameSet command to set the SNC name.

In the example shown, the host name of the SNC was “SN60023”, and it is now being set to “foster.” The shell prompt will change to reflect the new name.

SN60023 > hostNameSet "foster" Target hostname set to foster value = 0 = 0x0 foster >

In all of subsequent steps of this procedure, use the name and number values that your network manager and you have agreed to use.

Note

3 Configure a static IP address, by issuing the ethAddrSet

The IP address is specified as four decimal numbers, separated by periods.

foster > ethAddrSet "192.168.1.54" Host Address set to 192.168.1.54 for Ethernet interface value = 0 = 0x0

If you need to set a netmask, specify it after the network address:

foster > ethAddrSet "10.0.0.2", "255.0.0.0"

If you need a network route and/or default gateway, use gateAddrSet

foster > gateAddrSet "192.168.1.1" value = 0 = 0x0

When more complicated routing is required, use the route as a full address (single host) or as an abbreviated subnet address.

foster > route "add", "206.0.0", "192.168.1.1" value = 0 = 0x0

4 If you want to add users, follow the procedure in Creating User Accounts

5 Issue the reboot

Step 2 is optional.

command to set the host network address.

to specify it.

command to specify the destination address,

command to reboot the SNC.

below, before rebooting.

Using DHCP

CAUTION

An IP address assigned to a device by a Dynamic Host Configuration Protocol (DHCP) server does not change unless the device is disconnected from the network for a period that exceeds the lease period defined by the DHCP server. This time period is typically around 3 days. The SNC stores information from the DHCP server in its boot parameters and attempts to reuse it on subsequent boots in case the DHCP Server is unreachable.

1 Make sure that a DHCP server is present on the network.

12 Setup and Configuration Routines

This procedure is not intended to be used with FCBs in Scalar i2000 libraries or in Pathlight VX systems.

CAUTION

2 Connect a service terminal to the service port. For the location of this port, see Figure 1 on page 11, or

the User’s Guide for your SNC.

If a DHCP server is unreachable, the SNC Ethernet port will be unusable.

Note

3 Issue the dhcpEnable command. Refer to dhcpEnable

4 Reboot the SNC for the change to take effect.

5 Connect to the SNC serial port and issue the bootShow command to determine the assigned network

address. Refer to bootShow

Note

6 If you were referred to this section by another procedure, return to that procedure.

Instructions for connecting a service terminal are included in the User’s Guide for your SNC.

on page 58.

on page 51.

You must know the IP address in order to use telnet or the ADIC Management Console (AMC).

Setting the Date and Time

CAUTION

The recommended interface for FCBs in the Scalar i2000 or Pathlight VX solution is the graphical user interface.

The SNC allows you to set the real time clock, to add a timeserver to the system, and to synchronize the real time clock to the timeserver.

Setting the Real Time Clock

1 Connect a service terminal to the service port. Alternatively, connect a service computer to the network

that the SNC is on or to the Ethernet port of the SNC. For the location of these ports, see Figure 1 page 11, or the User’s Guide for your SNC.

Note

2 Use the rtcDateSet command to set the real time clock.

SNC > rtcDateSet 2001,1,26,5,9,30,00 value = 0 = 0x0 SNC >

Instructions for connecting a service terminal are included in the User’s Guide for your SNC.

If you are using Ethernet, open a telnet program to connect to the SNC. Before you connect by means of telnet, configure a user account. For instructions, refer to Creating User Accounts

on page 15.

SNC Firmware 4 User’s Guide 13

For detailed information about the parameters taken by the rtcDateSet command, refer to rtcDateSet

[year],[month],[dayofmonth],[dayofweek],[hour],[minute],[second] on page 97.

In the example, the time is set for 9:30 in the morning on January 26, 2001.

Note

3 Use the dateSetFromRTC command to set the real time clock on the SNC as the source of date

display. For more information about this command, refer to dateSetFromRTC

SNC > dateSetFromRTC value = 0 = 0x0 SNC >

4 Use the tzSet command to set the timezone. EST, used in the example, stands for Eastern Standard

Time. For more information about this command, refer to tzSet "timezone"

SNC> tzSet "EST" TZ Set TIMEZONE = EST:EDT:300:040202:101502 value = 0 = 0x0 SNC >

Table 2 Valid Timezone Settings

Timezone GMT offset Associated Areas

Use 24 hour time when programming the real time clock.

Use Greenwich Mean Time.

on page 56:

on page 124.

UTC 0 Greenwich, England

GMT 0 Greenwich Meridian Time

EST GMT -5 Eastern Time (U.S. and Canada), Indiana (East)

CST GMT -6 Central Standard Time (U.S. and Canada

MST GMT -7 Mountain Standard Time

PST GMT -8 Pacific Standard Time (Western U.S. and Canada)

5 Use the date command to confirm. For more information about this command, refer to date

SNC > date SNC > FRI JAN 26 9:30:49 2001 SNC >

on page 56.

Adding a Host System Running Timeserver

1 To enable the timeserver functionality use the setNettime command. For more information about this

command, refer to setNettime [value]

SNC > setNettime 1 Nettime 1 value = 0 = 0x0 SNC >

on page 106.

14 Setup and Configuration Routines

2 Add a host running timeserver to the SNC using the setTimeHost command. For more information

about this command, refer to setTimeHost "timeserver"

SNC > setTimeHost "butter" Time Host butter value = 0 = 0x0 SNC >

3 Set the remote system as the source of date/time display using the rdate command. For more

information about this command, refer to r

SNC > rdate "butter" Get time from butter using UDP/SNTP value = 0 = 0x0 SNC >

4 Use the tzSet command to set the timezone

EST, used in the example, stands for Eastern Standard Time.

SNC > tzSet "EST" TZ Set TIMEZONE = EST:EDT:300:040202:101502 value = 0 = 0x0 SNC >

date "timeserver" on page 95.

on page 107.

5 To confirm, use the date command. For more information about this command, refer to date

56.

SNC > date WED JUL 18 14:51:59 2001 value = 0 = 0x0 SNC >

on page

Disabling the Timeserver Host

To disable the timeserver functionality issue the setNettime 0 command.

SNC > setNettime 0 Nettime 0 value = 0 = 0x0 SNC >

The time will revert to the time set on the real time clock on the SNC.

Synchronizing the Real Time Clock with the Timeserver

1 Use the setTimeHost command to add a host running timeserver to the SNC system. For more

information about this command, refer to setTimeHost "timeserver"

SNC > setTimeHost "butter" Time Host butter value = 0 = 0x0 SNC >

2 Synchronize the real time clock on the SNC with the timeserver using the rtcSetCurrent command.

For more information about this command, refer to r

tcSetCurrent on page 99.

on page 107.

SNC > rtcSetCurrent value = 0 = 0x0 SNC >

Creating User Accounts

CAUTION

SNC Firmware 4 User’s Guide 15

The recommended interface for FCBs in the Scalar i2000 or Pathlight VX solution is the graphical user interface.

Before you access the SNC using telnet, add a user account.

Note

1 Connect a service terminal to the service port. For the location of this port, see Figure 1

the User’s Guide for your SNC.

Note

2 Issue the userAdd command. For more information about this command, refer to the commands

beginning with user in the Service Port Command Reference

foster > userAdd "username","password" value = 0 = 0x0 foster >

Note

For inband connections, the default user account name is admin and the default user account password is password.

on page 11, or

Instructions for connecting a service terminal are included in the User’s Guide for your SNC.

on page 39.

The user name you specify must be three or more characters. The password you specify must be eight or more characters.

Configuring Ports

CAUTION

The settings in Table 3 are the default settings on the SNC:

Table 3 Default SNC Channel Settings

Fibre Channels Public, Target, Loop

SCSI Channels Initiator

1 Connect a service terminal to the service port. Alternatively, connect a service computer to the network

that the SNC is on or to the Ethernet port of the SNC. For the location of these ports, see Figure 1 page 11, or the User’s Guide for your SNC.

Note

The recommended interface for FCBs in the Scalar i2000 or Pathlight VX solution is the graphical user interface.

Ready for attaching FCAL

Host Type: NT

Termination Enabled

Instructions for connecting a service terminal are included in the User’s Guide for your SNC.

If you are using Ethernet, open a telnet program to connect to the SNC. Before you connect by means of telnet, configure a user account. For instructions, refer to Creating User Accounts

on page 15.

Windows NT or 2000 Hosts

Ready for attaching SCSI disk or tape devices

2 Use appropriate firmware commands to accommodate SAN configurations that do not conform to the

default settings. For example, if your system contains few devices that are capable only of arbitrated

16 Setup and Configuration Routines

loop, the default connection type can be changed to from "loop" to "loop preferred." Refer to Table 4 and Table 5

Table 4 Fibre Channel Configuration Quick Reference

FC Device Attachment Required Channel Settings Service Port Commands

FC Host type

NT (default) AIX AS400

setHost [port], “OS”

and

reboot

Autosense/NT Gateway Generic HP-UX Linux Netware Solaris Unknown Unisys

FC Switch Point-to-Point

Target (default)

fcConnTypeSet [port], [connection]

and

fcRestart

FC disk or FC tape device

Loop (default) Initiator

fcPortModeSet [port], [mode]

and

fcRestart

1 If eVPS is being used, the FC Host type does not need to be configured manually. 2 The SNCs that use Firmware 4 support 64 initiators per Fibre Channel port

Table 5 SCSI channel configuration quick reference

SCSI Device Attachment

Required Channel Settings

Service Port Commands

SCSI Host Target scsiHostChanSet

[channel],[mode]

and

reboot

SCSI disk and tape SCSI Bus shared (dual paths)

SCSI Bus Reset on Power Up Disabled

scsiResetDisableSet [channel],[mode]

and

reboot

SCSI disk and tape SCSI Y-cable (SNC not at end of SCSI bus)

Termination Disabled scsiTermSet

[channel],[termination]

and

reboot

SNC Firmware 4 User’s Guide 17

Mapping Multiple Paths to Targets

CAUTION

The automatic multi-path mapping (AMP) and manual multi-path mapping (MMP) features allow you to map alternate paths to the SNC from switch-attached FC devices.

Note

1 Be sure that the devices, the switch, the host, and the SNC have been powered on and have finished

booting. The SNC connects at least two of its Fibre Channel connections to the switch, which connects to the devices.

CAUTION

2 Connect a service terminal to the service port. Alternatively, connect a service computer to the network

that the SNC is on or to the Ethernet port of the SNC. For the location of these ports, see Figure 1 page 11, or the User’s Guide for your SNC.

Note

The recommended interface for FCBs in the Scalar i2000 or Pathlight VX solution is the graphical user interface.

Both automatic and multipath mapping require licensing.

These instructions do not take into account zoning software that may be on the switch.

Instructions for connecting a service terminal are included in the User’s Guide for your SNC.

Note

CAUTION

3 Issue the ampFeatureEnable command. For more information about this command, refer to

ampFeatureEnable “license”

4 Disconnect SNC Fibre Channel cables from the switch.

5 Clear the map database by issuing the mapWinnowDatabase command. For more information about

this command, refer to mapWinnowDatabase

6 Set the multi-path mapping configuration by issuing the mapMultipathSet command.

Use manual mode (mapMultipathSet 1) when using special host software. Manual mode exposes all paths to devices, including paths that are hidden because one target device’s World Wide Port Name is identical to another target device’s World Wide Port Name. Manual mode is used in conjunction with special host software, so that the user does not inadvertantly identify a single device as two devices, which can lead to data corruption. Host software allows the user to set one path to the device as primary and the other as secondary.

If you are using Ethernet, open a telnet program to connect to the SNC. Before you connect by means of telnet, configure a user account. For instructions, refer to Creating User Accounts

If you are configuring multiple paths to targets after host connections have been established, the change in target IDs can damage host configurations. Optimally, configure multipath mapping as part of setup.

on page 51.

on page 15.

on page 92.

18 Setup and Configuration Routines

SNC > mapMultipathSet 1 Multipath mode set to manual mode. value = 1 = 0x1 SNC >

Use automatic mode (mapMultipathSet 2) when special host software is not available and all devices are capable of responding to an inquiry with a unique serial number. Each target drive must also have two ports, both of which are connected to separate switches. Each switch must be connected to an SNC FC port. If either switch fails or any cables or GBICs fail on one path, failover automatically occurs to the other path.

SNC > mapMultipathSet 2 Multipath mode set to automatic mode. value = 2 = 0x2 SNC >

For more information about this multipath settings, refer to mapMultipathSet

7 Reconnect SNC Fibre Channel cables to the switch.

8 Issue the fcRescan command. For more information about this command, refer to fcRescan [port]

page 66.

9 Issue the mapShowDevs command to confirm that devices have been remapped using the multi-path

configuration that was selected.

CAUTION

If devices have already been mapped, and they need to be remapped, use the mapRemoveDevice command. Then issue the fcRescan command.

on page 88.

Configuring Channel Zoning

CAUTION

Access between ports configured for host access and ports configured for storage access can be enabled or disabled as required. The ability to create restricted access on a full-channel basis is called channel zoning. The default configuration is for all Fibre Channels to have access to all SCSI channels. Channel zoning is also possible from an FC target channel to an FC initiator channel.

The recommended interface for FCBs in the Scalar i2000 or Pathlight VX solution is the graphical user interface.

In certain instances, customers may wish to combine the channel level security of channel zoning with the advanced LUN level security of Scalar Firewall Manager (SFM) to enable a mix of load balancing and host specific security. In this instance, channel zoning is used to provide load balancing while SFM delivers resource security and heterogenous host support.

Channel zoning enables load balancing by configuring certain SCSI channels to only be accessible across specific SAN connections. This is typically done by defining SCSI channels 1 and 2 to be accessible through FC port 1of the SNC, and SCSI channels 3 and 4 to be to be accessible through FC port 2. This insures that data traffic is split across the SNC SAN interfaces.

SFM is configured as usual, but the administrator must be aware that SFM does not override channel zoning. A host must have LUN level access to a drive through SFM, and be bound to the correct SNC FC port. If the host is incorrectly connected to the SNC, the combination of channel zoning and SFM may prevent the host from seeing resources.

SNC Firmware 4 User’s Guide 19

CAUTION

line by following the procedure specified below, the preferred interface for channel zoning is the ADIC Management Console (AMC). For instructions on installing and using AMC, refer to the ADIC

Management Console User’s Guide.

1 Connect a service terminal to the service port. Alternatively, connect a service computer to the network

While it is possible to configure channel zoning from the command

that the SNC is on or to the Ethernet port of the SNC. For the location of these ports, see Figure 1

page 11, or the User’s Guide for your SNC.

Note

Instructions for connecting a service terminal are included in the User’s Guide for your SNC.

If you are using Ethernet, open a telnet program to connect to the SNC. Before you connect by means of telnet, configure a user account. For instructions, refer to Creating User Accounts

on page 15.

2 Issue the setFcChanMask command.

Channel Zoning settings take precedence over settings made by VPS/

CAUTION

SFM, and eVPS.

This command uses bitmasked values to enable or disable access. For a complete discussion of the formula used to obtain appropriate values, refer to setFcChanMask [channel, bitmask]

Table 6

lists some common values. The examples in Table 6 are all given for Fibre Channel 1, but the

on page 104.

bitmasked values representing SCSI Channel access would not change if Fibre Channel 2 were specified instead.

Table 6 Common Channel Zoning Configuration Codes

Command String Effect

SNC> setFcChanMask 1,1008

Enables access to SCSI channels 1 - 4 for Fibre Channel 1.

SNC> setFcChanMask 1,1022

Enables access to SCSI channel 1 for Fibre Channel

SNC> setFcChanMask 1,1021

Enables access to SCSI channel 2 for Fibre Channel

SNC> setFcChanMask 1,1019

Enables access to SCSI channel 3 for Fibre Channel

SNC> setFcChanMask 1,1015

Enables access to SCSI channel 4 for Fibre Channel

20 Setup and Configuration Routines

Table 6 Common Channel Zoning Configuration Codes

Command String Effect

SNC> setFcChanMask 1,1020

SNC> setFcChanMask 1,1011

3 After issuing the setFcChanMask command, reboot for the changes to take effect.

Enables access to SCSI channels 1-2 for Fibre Channel 1.

Enables access to SCSI channels 3-4 for Fibre Channel 1.

Configuring VPM

The VPM (Virtual Private Map) software configures access to specific LUNs for certain SCSI hosts. A maximum of 256 LUNs per host can be mapped.

CAUTION

While it is possible to configure VPM from the command line by following the procedure specified below, the preferred interface for VPM is the ADIC Management Console (AMC). For instructions on installing and using AMC, refer to the ADIC Management Console User’s Guide.

Optionally, before configuring VPM, install the HRS on the hosts involved. Instructions for doing so are in the User’s Guide for your SNC. It is available for Windows, AIX, HP-UX, Linux, and Solaris hosts.

Note

1 Connect a service terminal to the service port. Alternatively, connect a service computer to the network

that the SNC is on or to the Ethernet port of the SNC. For the location of these ports, see Figure 1 page 11, or the User’s Guide for your SNC.

Note

2 Issue the vpmFeatureEnable command. For more information about this command, refer to

pmFeatureEnable "licensekeystring" on page 129.

3 Issue the targets command. For more information about this command, refer to targets

Take note of the target devices to which you have access. The numbers you need are in the "Idx" column.

You must have a license to use VPM.

Instructions for connecting a service terminal are included in the User’s Guide for your SNC.

If you are using Ethernet, open a telnet program to connect to the SNC. Before you connect by means of telnet, configure a user account. For instructions, refer to Creating User Accounts

on page 15.

on page 121.

4 Issue the setScsiAssign command. For more information about this command, refer to

setScsiAssign [devID], [channel], [id], [lun]

5 Issue the showScsiAssign command.

SNC Firmware 4 User’s Guide 21

on page 106.

If results are not as expected, refer to VPM MAP on page 175.

6 Reboot the host(s) or use host utilities to rescan available targets.

Configuring eVPS

CAUTION

The eVPS (extended Virtual Private SAN) software configures access to specific LUNs for certain Fibre Channel hosts. Access to these LUNs can be ordered in different, host-appropriate ways for each host. A maximum of 256 LUNs per host can be mapped, up to an overall device total of 2048.

CAUTION

Optionally, before configuring eVPS, install HRS on the hosts involved. Instructions for doing so are in the ADIC Management Console User’s Guide. HRS is available for Windows, AIX, HP-UX, Linux, and Solaris hosts.

Note

1 Connect a service terminal to the service port. Alternatively, connect a service computer to the network

that the SNC is on or to the Ethernet port of the SNC. For the location of these ports, see Figure 1 page 11, or the User’s Guide for your SNC.

The recommended management interface for FCBs in the Scalar i2000 or Pathlight VX solution is the graphical user interface.

While it is possible to configure eVPS from the command line by following the procedure specified below, the preferred interface for eVPS is the ADIC Management Console (AMC). For instructions on installing and using AMC, refer to the ADIC Management Console User’s Guide.

You must have a license to use eVPS.

Note

2 Issue the vpsFeatureEnable command. For more information about this command, refer to

vpsFeatureEnable "license key string"

3 Issue the vpsShow command. For more information about this command, refer to vpsShow [hostIndex]

on page 137.

Take note of the host index number. The host index number is the number in the ID column.

4 Issue the targets command. For more information about this command, refer to targets

Take note of the target devices to which you have access. The numbers you need are in the "Idx" column.

22 Setup and Configuration Routines

Instructions for connecting a service terminal are included in the User’s Guide for your SNC.

If you are using Ethernet, open a telnet program to connect to the SNC. Before you connect by means of telnet, configure a user account. For instructions, refer to Creating User Accounts

on page 132.

on page 15.

on page 121.

5 If you are configuring access to all contiguous LUNs, issue the vpsAccessSet command. For more

information about this command, refer to vpsAccessSet [hostIndex],[Starting lun],[Ending lun],[Access] on page 130.

Use the number you noted in Step 3 output by the targets command you issued in Step 4 highest number that was output by the targets command you issued in Step 4 [Ending lun]. Use an access value of "1" to enable access to these LUNs.

If LUNS are not contiguous, use the vpsSparseAccessSet command. For more information about this command, refer to vpsSparseAccessSet[hostindex],"LUN string",[

6 Issue the vpsAccessApply command.

7 Reboot the host(s) or use host utilities to rescan available targets.

for the value [hostIndex]. Use the lowest number that was

as the value for the [Starting lun]. Use the

as the value for the

access] on page 138.

Using the WWN Lock Mode

The wwnLockModeSet command gives a SAN administrator more direct control over which hosts (initiators) are able to access the library. SFM/VPS/eVPS must already be enabled for it to be used.

A maximum of 64 initiators can be connected per FC port. If the VPS host table is forced to retain host entries for initiators that do not have authority to access LUNs available through that SNC, then hosts which are authorized to access those LUNs may not be able to connect to the SAN. In situations where there are large numbers of initiators, and SFM/VPS/eVPS has been enabled, the contents of the host table can be controlled by setting the wwnLockMode to ‘1” (enabled). Then use vpsInitDelete [host ID] unauthorized hosts and vpsInitAdd

The WWN lock mode default state is disabled.

[hiWWN],[loWWN] to add authorized hosts to the host table.

to remove

1 Connect a service terminal to the service port. Alternatively, connect a service computer to the network

that the SNC is on or to the Ethernet port of the SNC. For the location of these ports, see Figure 1 page 11, or the User’s Guide for your SNC.

Note

2 Before you enable WWN lock mode, check to see if if SFM/VPS/eVPS is enabled. If not, enable it first.

For instructions, refer to sfmFeatureEnable "license key string"

"license key string" on page 132.

3 Issue the wwnLockModeSet command:

SNC > wwnLockModeSet 1 WWN Locking Mode: Enabled value = 1 = 0x1 SNC >

All hosts whose names are unknown in the VPS host table are deleted.

Instructions for connecting a service terminal are included in the User’s Guide for your SNC.

If you are using Ethernet, open a telnet program to connect to the SNC. Before you connect by means of telnet, configure a user account. For instructions, refer to Creating User Accounts

on page 15.

on page 109 or vpsFeatureEnable

Note

SNC Firmware 4 User’s Guide 23

The wwnLockMode persists across reboots.

4 Check the state of the WWN lock mode, by issuing the wwnLockModeShow command.

SNC > wwnLockModeShow WWN Locking Mode: Disabled value = 0 = 0x0 SNC >

5 Display a list of hosts that have access to the SNC by issuing the sfmShow command or the vpsShow

command:

SNC > sfmShow

The sfmShow command and the vpsShow command display all the hosts in the VPS host table. For more information, refer to sfmShow [hostIndex]

on page 111.

Note

a. Remove any unwanted hosts from the VPS host table by issuing the vpsInitDel command.

b. Add hosts to the VPS table by issuing the vpsInitAdd command. For more information, refer

Only the hosts in the VPS host table have access to the command and control LUN when WWN lock mode is enabled.

For more information, refer to vpsInitDelete [host ID]

to vpsInitAdd

[hiWWN],[loWWN] on page 135.

on page 135.

Configuring Host Port Failover

CAUTION

The host port failover (HPF) feature uses an active/passive methodology. An active (primary) port is used for host communications, while the passive (standby) port is kept idle. Port failover occurs when connectivity between the primary port and the SAN ceases to function correctly. This can be caused by a loss of signal between the ports or excessive errors on the connection. The Fibre Channel ports are connected to the host computer by means of a switch.

Note

The recommended interface for FCBs in the Scalar i2000 or Pathlight VX solution is the graphical user interface.

This feature requires a license. Please contact your ADIC representative.

Note

1 Connect a service terminal to the service port. Alternatively, connect a service computer to the network

that the SNC is on or to the Ethernet port of the SNC. For the location of these ports, see Figure 1 page 11, or the User’s Guide for your SNC.

Note

24 Setup and Configuration Routines

Use automatic or manual multi-pathing (AMP or MMP) to enhance data path protection for the part of the data path that connects the SNC to devices. Refer to R

eplacing a SCSI Drive on page 25.

Instructions for connecting a service terminal are included in the User’s Guide for your SNC.

If you are using Ethernet, open a telnet program to connect to the SNC. Before you connect by means of telnet, configure a user account. For instructions, refer to Creating User Accounts

on page 15.

+ 164 hidden pages