Quantum SNC 4000 User Manual

m

®

ADIC SNC

4000 User’s Guide

ADVANCED DIGITAL INFORMATION CORPORATION

www.adic.co

Copyright © 2002-2003 ADIC



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.

Copyright © 2002-2003 ADIC Europe

TM

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
Tel.: [phone]
Fax: [phone]
ATAC: 1-800-827-3822
http://www.adic.com

ADIC Europe
ZAC des Basses Auges
1, rue Alfred de Vigny
78112 Fourqueux, France
Tel.: [phone]

ADIC Germany Beteiligungs GmbH, KG

Eschenstraße 3
D-89558

Böhmenkirch, Germany

Tel:[phone]

Fax: [phone]

Published: Nov 2003 Document Number: 62-2308-03 Rev A

ADIC • 11431 WILLOWS ROAD, NE • REDMOND, WASHINGTON, USA • 1-800-336-1233

ADIC • 8560 UPLAND DRIVE • ENGLEWOOD, COLORADO, USA • 1-800-827-3822

ADIC • 10 BROWN ROAD • ITHACA, NEW YORK, USA • 1-607-241-4800

Contents

1 SNC 4000 Introduction 1

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

Document Organization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Associated Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Explanation of Symbols and Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Environmental Notices and Statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Product Recycling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Laser Safety . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Usage Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Technical Assistance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

2 Description 5

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Configuration Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

FC Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Service Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

LED Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Firmware 4.40 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Multi-path Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

WWN Change Capability. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

DHCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Supported Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Supported Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Operating Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Operating Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Power Consumption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

ADIC Management Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

3 Getting Started 11

Unpacking and Inspecting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Pre-Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Post Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Configuration Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Saving a Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

SNC 4000 User’s Guide iii

Loading a Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Updating Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

4 Scalar Firewall Manager 19

Host Registration Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Installing the Host Registration Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Adding a Host to the SAN Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Combining SFM with Channel Zoning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

5 Connecting to the Service Port 23

Service Port Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Connecting the Service Terminal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Hardware Required . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Connecting using HyperTerminal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Connecting using Telnet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Verifying the Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

6 Removal and Replacement Procedures 27

Handling Electrostatic Discharge-Sensitive Parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Removing and Replacing the SFP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Removing the SFP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Replacing the SFP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Before Removing or Replacing the SNC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Removing and Replacing the SNC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Removing the SNC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Replacing the SNC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Final Diagnostic Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Final Test Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Fibre Channel Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Test Fibre Channel Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Test SCSI Port 1 and 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Ethernet Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Network Setup for the SNC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Updating the SNC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Post-Repair Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

A Maintenance Action Plans 35

Event Codes and Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Check Event Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Action Reference Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Event Viewing Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Start MAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Event Code or Obvious Symptom . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Visually Inspect LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Check for Problems on Attached Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Check Host Versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

iv Contents

Check SNC Product Versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Quick Component Check. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Perform Health Check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Check the Host Event Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Database Full MAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Device Access MAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Check Fibre Channel Port Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Check SCSI Channel Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Check Channel Zoning Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

SCSI Channel MAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Get SCSI Information for the SNC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Check Attached SCSI Devices from the Service Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Compare Listed versus Physical Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Compare Listed versus Supported Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Check SCSI Bus Termination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Check for Multiple SCSI IDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Improper Device Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Examine SCSI Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Examine SCSI Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

SCSI Health Check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

SCSI Loop Back Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Testing SCSI Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Isolating SCSI Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Restore SCSI Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Fibre Channel MAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Verify FC Connections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Test SFP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Examine Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Fibre Channel Loop Back Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Testing Fibre Channel Optic Cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Replace Fibre Channel Cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Replace Fibre Channel Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

MAP for the SNC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Observe Operational LED Behavior . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Temperature MAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Notification of Problems in Temperature Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Temperature Warnings or Alarms Received . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Fan Speed is in Warning or Alarm Range . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Power MAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Ethernet MAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Service Port MAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Check the RS-232 Cable. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Check Connection with Boot Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Scalar Firewall Manager Settings MAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Check Scalar Firewall Manager Access Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Verify Host Access to Devices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

B Service Port Command Reference 63

Managing the SNC 4000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

SNC 4000 User’s Guide v

C Diagnostic Command Reference 135

Boot Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

Entering Diagnostic Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

Restoring Normal Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136

Special Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136

Health Check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136

Retrieving the Code 43 Dump File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

Boot Mode Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

Diagnostic Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138

D POST Error Codes 143

POST Boot Behavior . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

ROM Init . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

Initial POST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144

Secondary POST. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

POST Service Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147

Error Displays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148

E Startup Message Reference 149

Bootrom Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149

LIC Initialization Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149

Final Startup Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150

F Warranty and EULA 151

ADIC Limited Product Warranty . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

ADIC End User License Agreement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152

G Acronyms 155

vi Contents

SNC 4000 Introduction

This manual contains information and instructions necessary for the operation of the SNC 4000.

Intended Audience

This guide is intended for general use by anyone interested in learning about or using the SNC 4000.

Document Organization

The section topics in this guide include:

• Introduction - Provides an overview of the contents of the manual.

• Description - Provides general information about the SNC 4000 and its components.

• Getting Started - Describes the basic set-up procedures for your SNC 4000.

• Connecting to the Service Port - Describes how to connect to the service port on the SNC 4000.

• Removal and Replacement Procedures - Describes how to remove and replace the customer­replaceable components of the SNC.

• Appendix A: Maintenance Action Plans - Describes how to troubleshoot and maintenance the SNC

4000.

• Appendix B: Service Port Command Reference - Provides a list of service port commands and
descriptions of each.

• Appendix C: Diagnostic Command Reference - Provides a list of the diagnostic commands and a
description of each.

• Appendix D: POST Error Codes - Describes the power-on self test process.

• Appendix E: Startup Message Reference - Describes the licensed internal code boot loader
process.

• Appendix F: Warranty and EULA - Provides warranty and licensing information for the SNC 4000.

• Appendix G: Acronyms - Describes acronyms used in SNC4000 documentation.

SNC 4000 User’s Guide 1

Associated Documents

The following documents are associated with this guide:

• Scalar 24 Installation and Operation Guide (62-2301-01 Rev. A)

• ADIC Management Console 3.2 User’s Guide (6-00064-01 Rev. B)

Explanation of Symbols and Notes

The following symbols and highlighted passages note important information:

Symbol Damage to ... Signal Word Definition Consequence

Person WARNING: Imminent

hazardous electrical
situation

Material CAUTION: Potential damaging

situation

NOTE: Indicates important

information that
helps make better
use of the system

Death or serious injury

Possible damage to
the product, data, or
environment

No hazardous or
damaging
consequences

Environmental Notices and Statements

The following are the environmental notices and statements for the SNC 4000.

Product Recycling

This unit contains recyclable materials. These materials should be recycled where processing sites are
available and according to local regulations.

Lithium Battery

WARNING

RISK OF FIRE, EXPLOSION, OR BURNS. DO NOT SHORT
CIRCUIT, CRUSH, HEAT ABOVE 100
DISASSEMBLE THE BATTERY.

N

C, INCINERATE, OR

Laser Safety

This unit may contain a single-mode or multi-mode transceiver, both of which are Class 1 laser products.
The transceiver complies with IEC 825-1 and FDA 21 CFR 1040.10 and 1040.11. The transceiver must be
operated under the recommended operating conditions.

Usage Restrictions

The optical ports of the modules must be terminated with an optical connector or with a dust plug.

2 SNC 4000 Introduction

Technical Assistance

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

Outside the USA, toll free: 00.800.9999.3822

Internet: www.adic.com

SNC 4000 User’s Guide 3

4 SNC 4000 Introduction

Description

This chapter describes the SNC (Storage Networking Controller) 4000.

Overview

The Scalar 24 enables customers to use and manage the library in a storage area network, via an integrated
SNC 4000. When configured as a storage networking library, the Scalar 24 delivers the following
functionality:

• The ability to create separate data paths between heterogeneous hosts library and components
(drives and/or media changer) using Scalar Firewall Manager (SFM). SFM allows the zoning of
resources so that hosts are restricted to seeing only storage they need. This endpoint security is
standard in ADIC storage networking libraries and is OS, HBA, and switch/hub independent.
Heterogeneous support also enables multiple hosts with varying OSs and backup applications to
access the same library.

• End-to-end path verification between the library and open system host interfaces that enables
administrators to discover and remedy path failures before the library is needed for backup
applications.

• Drive performance optimization to eliminate protocol bridging latencies and keep drives streaming
by pre-fetching data and overlapping commands via an ADIC patent-pending technique.

• Serverless backup via an integrated Data Mover Module.

One possible configuration of the of the SNC 4000 is illustrated in Figure 1

SNC 4000 User’s Guide 5

.

Figure 1 Configuration Overview

Configuration Support

The SNC provides one FC interface. The FC interface is configured with a small form factor pluggable
transceiver (SFP). In addition, the SNC has two Ultra2 SCSI interfaces.

Address Mapping

The SNC maps addresses across and between these different interfaces and preserves the persistency of
the address maps across power ups of systems, devices, and the SNC.

Interface Protocol Awareness

The SNC processes SCSI-3 and SCSI-2 protocols for disk, tape, and tape medium changer devices. It can
report the host and devices that are attached to its interfaces. The SNC has the capability to manage the
access security between end points on the FC interface and the SCSI channels.

FC Interface

Interfaces for host and device attachment include one, 1- and 2-Gb/s bi-directional Short Wave connection.

The SFP can interoperate with both 2 Gb/s and 1 Gb/s data links. The SFP is hot-swappable and is the only
component, except for the SNC module itself that is a field replaceable unit (FRU). Refer to Removing and

Replacing the SFP on page 27.

Cables should have a duplex LC connector on the SFP end and a connector appropriate to the HBA in use
on the host end.

The FC interface supports the following Public and Private Loop modes:

• Target

6 Description

• Initiator

• Target and Initiator

The FC Interface also supports the following connection options:

• Loop

• Point-to-Point

• Loop Preferred

The FC interface controller is in compliance with the following standards and specifications:

• Fibre Channel Arbitrated Loop (FC-AL-2) working draft, rev 6.4, August 28, 1998

• Fibre Channel Fabric Loop Attachment (FC-FLA) working draft, rev 2.7, August 12, 1997

• Fibre Channel Private Loop SCSI Direct Attach (FC-PLDA) working draft, rev 2.1, September 22,
1997

• Fibre Channel Tape (FC-TAPE) profile, T11/98-124vD, rev 1.13, February 3, 1999

• Fibre Channel protocol SCSI (FCP-SCSI)

• Fibre Channel internet protocol (IP)

• Fibre Channel virtual interface (FC-VI)

SCSI I/O Interfaces

The Scalar 24's SNC supports SCSI-3 commands over an Ultra2 bus. The SNC is Ultra160 hardware
compatible and will support Ultra160 bus speeds via a planned firmware upgrade. The SNC contains two
Low Voltage Differential/Single-Ended (LVD/SE) Ultra2 SCSI channels with internal termination. The SCSI
channels have automatic speed and width negotiation capability for wide or narrow bus widths and
Standard, Fast, Ultra or Ultra2 speeds. These parameters can be viewed from the ADIC Management
Console.

The SCSI interfaces are compliant with the following SCSI specifications:

• ANSI T10/1071D Rev. 6, SCSI-3 Fast-20

• ANSI T10/375D Rev. 10t, SCSI-2

• ANSI T10/1142D Rev 20b, SCSI-3 Parallel Interface-2

Ethernet

The 10/100 Base-T Ethernet port has an RJ-45 connector for out-of-band management. It can be connected
to a network hub, switch, or router using an unshielded twisted-pair Ethernet cable. The Ethernet port
complies with the IEEE 802.3 specification.

Service Port

The service port is an RS-232 connection with a 9-pin D-shell connector. It connects to the host serial port
with a 9-pin to 9-pin straight through cable. It is compatible with serial ports on personal computers.

The service port is used for local service and diagnostics when you use a terminal session to access the
shell interface.

The service port is configured at:

• VT100 or ANSIW terminal emulation

• 19,200 Baud

SNC 4000 User’s Guide 7

• 8 data bits

• No parity

• One stop-bit

• Hardware Flow Control or Xon/Xoff

LED Indicators

The interface panel of the SNC provides LEDs that indicate the status and activity of the SNC and its
interfaces.

Figure 2 LEDs

When the SNC is first turned on, some of the LEDs will be on and others will flash while it is booting.

The following list briefly describes how to interpret the LED signals. See also POST Error Codes

143.

FC

• For the FC channel, the LED will be OFF when the channel is not connected. It will be ON when the
channel is connected to a live FC device. It will flash when there is activity on the channel.

S1 and S2

• For each SCSI channel, the LED will be OFF when no devices have been detected on the port. It
will be ON when a target has been found on the channel. The LED will return to the OFF state if the
channel is reset.

PWR

•The PWR (Power) LED will be ON when the SNC has power. It will flash if the on-board power
sensors determine that any of the required supply voltages are out of range.

RDY

• The RDY (Ready) LED indicates status of Ready. Normally the RDY LED flashes when the SNC
has finished booting. If the RDY LED remains ON or OFF for more than a few seconds, it means
there is a problem.

on page

• The RDY LED will flash rapidly, four times per second, when the SNC is running in diagnostic mode.

ERR

• The ERR (Error) LED indicates that an error condition exists. This may indicate such errors as over­temperature conditions, fan stalled or other internally detected error conditions. See POST Error

Codes on page 143.

8 Description

Firmware 4.40 Features

This chapter describes the functionality of the Storage Networking Controller (SNC) Firmware 4.40. The
SNC interface between storage and host provides Fibre Channel to SCSI 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.

Features highlighted with this release are described below.

Multi-path Mapping

Multi-path mapping enables an administrator to map a single Fibre Channel-attached storage device
through all SCSI communication 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,
high-availability 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.

DHCP

DHCP enables an administrator to configure network parameters such as IP addresses and lease durations
for a device from a common server. When DHCP is enabled, the SNC requests configuration data from the
DHCP server and configures the Ethernet interface based on the results. DHCP can be activated in
environments in which the SNC is attached to a private network and the AMC is not used for direct SNC
control. DNS is used by target devices to determine the IP addresses of named hosts and is active
whenever DHCP is enabled.

Supported Platforms

The SNC is a platform-independent product. You can connect a host to the SNC after you have installed
the appropriate host bus adapter and drivers. You can also connect host systems with different operating
systems to the SNC through the FC.

For a current list of supported platforms, configurations, and host bus adapters, see www.adic.com/

scalar24.

Supported Devices

The SNC supports connections to the Scalar 24 and supports all tape drives available for that unit.

Operating Specifications

This section contains the physical, electrical, and environmental specifications for the product.

SNC 4000 User’s Guide 9

The SNC is integrated in the Scalar 24. The interface panel of the unit is visible from the back of the Scalar

24.

The external dimensions are:

•3” high

• 7” deep

• 6” wide

• weight: 2.19 lbs.

In order to provide a safety margin and permit adequate cooling, the unit is fitted with a 12 VDC tach-output
blower. Should temperatures exceed specifications, an environmental alarm violation is sent and logged,
permitting environmental causes of failure to be determined. This information can be viewed using the ADIC
Management Console.

Operating Environment

The operating environment is as follows:

• Operating Temperature: 5° C to 45° C (50° F to 113° F)

• Storage Temperature: -40° C to 70° C (-40° F to 158° F)

• Humidity: 10%-85% Operating, Non-Condensing
5%-95% Non-operating, Non-Condensing

Power Consumption

The SNC is powered by the Scalar 24. Maximum power consumption is 58 watts, in active mode. The power
supply status is monitored and is reported by the PWR LED and to the ADIC Management Console.

ADIC Management Console

The ADIC Management Console (AMC) offers remote, centralized management of Scalar storage
networking libraries. Features of the AMC include:

• Management and monitoring of multiple Scalar libraries at the same time

• Customizable graphical view of ADIC libraries

• Policy based event logging and email notification

• Device-level diagnostics, reporting, and configuration

All of these functions are embedded into a point and click interface designed to simplify management. The
AMC receives information from Scalar storage networking libraries using the industry standard SNMP
protocol. Because ADIC uses an industry standard protocol, information can be directed from ADIC libraries
to framework applications. These framework applications can use SNMP Traps to generate reports and
pager alerts as part of an enterprise management program. For more information, see the ADIC

Management Console User’s Guide.

10 Description

Getting Started

This section describes how to install and set up the SNC 4000, SCSI devices, and the Host Bus Adapter.
Installation is divided into four sections:

• Unpacking and Inspecting

• Pre-installation

• Installation

• Post-installation

Unpacking and Inspecting

Unpack the SNC from the carton. Check to make sure that the following items are included with your SNC
and that none of them are damaged:

• One SFP

• Product documentation and software CD-ROM

• Two HD68/VHDCI SCSI cables

• One LVD terminator

NOTE: Save the CD-ROM in a safe location for future reference.

Pre-Installation

It is important that the items in the steps below are verified before installation of the SNC begins. This
ensures a successful installation of the product.

Required Tools Required Software Other Resources

RS-232 straight through cable ADIC Management Console

server/client software

RJ-45 patch cable SNC firmware System with HyperTerminal

SC/LC fibre cables Server to run ADIC

SNC 4000 User’s Guide 11

IP information for the SNC

Management Console

1 Install the ADIC Management Console server and client software. For installation instructions, see the

ADIC Management Console User’s Guide. It is recommended that you use this software to verify
connections and during the post-installation process.

2 Check that you have the latest firmware for the SNC by going to www.adic.com/downloads/firmware.

3 Verify that host OS and service pack are up to date and supported by the library.

4 Verify that Host Bus Adapter (HBA) have been installed on SAN attached hosts and configured

properly. HBA BIOS and device drivers should be at the most current level.

5 Install the Host Registration Service on hosts that will be connected to the library.

6 Ensure that all necessary FC cables are present.

Note

7 Label both ends of each SCSI cable with drive ID and SNC connector number.

8 If you are using the ADIC Management Console to manage the SNC 4000, configure an Ethernet

environment. You will need to set the following network parameters:

Static IP address____________

Netmask _________

User-defined SNC name __________________

Default Gateway _____________________

CAUTION

Note

The Scalar 24 uses an LC high density connection. In environments where the
library will attach to SC interfaces (GBIC, 1x9, etc.) make sure that SC to LC
cables are available.

Use of incorrect network parameters can cause problems on the
Ethernet network.

The default network name is the unit’s serial number. If you choose a different
name, it becomes the prompt displayed on the service terminal. Choosing a
different name may be useful if you have more than one SNC 4000. To change
the name, use the hostNameSet command. For more information, see

hostNameSet

on page 89.

9 Connect the Ethernet port on the SNC to the LAN. Library connectivity and monitoring parameters can

be managed from the ADIC Management Console.

Installation

Follow the instructions below to install the SNC with SCSI attached storage and FC attached hosts.

1 Power down your Scalar 24 and disconnect the AC line cord from the AC source outlet.

2 From the rear of the Scalar 24, locate the available SNC slot. Loosen the four thumbscrews on the cover

plate and remove the cover plate. Store the cover plate in a convenient place. It is required for proper
operation and cooling of the library if the SNC is ever removed.

12 Getting Started

Figure 3 Cover Plate Removal

3 Slide the SNC into position until it mates with the connector then tighten the thumbscrews.

SNC 4000 User’s Guide 13

Figure 4 SNC Installation

4 Connect one end of the RS-232 cable to the service port on the SNC and the other end to a service

terminal.

5 Start a terminal emulation session using HyperTerminal and the following settings:

• VT100 or ANSW terminal emulation

• 19,200 Baud

• 8 data bits

• No parity

• One stop-bit

• Hardware Flow Control or Xon/Xoff

6 Run the Ethernet cable from the network hub to the SNC.

7 Connect the SCSI cables to the library. An example of typical cabling for two drives connected to each

of the SCSI channels on the SNC is shown below. Both drives must have the last device on the SCSI
bus terminated, as shown.

14 Getting Started

Figure 5 SCSI Cabling for Two Drives

8 Turn on the Scalar 24.

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

9 Configure the network information by typing the following at the service terminal:

ethAddrSet "ip_address","subnet_mask"

where “ip_address” and “subnet_mask” are replaced with actual values, for example:

ethAddrSet “172.16.32.12”,“172.16.1.1

Then enter:

gateAddrSet "default_gateway_ip"

where “default_gateway_ip” is replaced with the default gateway IP address.

Then enter:

hostNameSet "name"

where “name” is replaced with the name you would like displayed in the ADIC Management Console.

10 Configure the date and time. You can either set the real time clock manually, or use a timeserver. Refer

to the procedures below to set the date and time.

”

Setting the Time and Date

Follow the procedure below to set the Real Time Clock (RTC). For more information on the commands used
in this procedure, see Commands Listed Alphabetically by Function

1 Use the rtcDateSet command to manually set the Real Time Clock. The rtcDateSet command

takes the following arguments:

[year],[month],[day_of_month],[day_of_week],[hour],[minute],[second]

For example:

SNC4000 > rtcDateSet 2001,1,26,5,9,30,00

on page 63.

2 Use the dateSetFromRTC command to set the RTC as the source of date display:

SNC4000 > dateSetFromRTC
value = 0 = 0x0

3 Use the tzSet command to set the time zone. EST is used in the example for Eastern Standard Time:

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

SNC 4000 User’s Guide 15

4 Use the date command to confirm.

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

CAUTION

Use 24 hour time when programming the real time clock. The time will
be one hour off while Daylight Savings time is in effect.

Adding a Host System Running Timeserver

Follow the procedure below to configure the date to be automatically set. For more information on the
commands used in this procedure, see Commands Listed Alphabetically by Function

1 To enable the timeserver functionality use the setNettime command.

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

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

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

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

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

4 Use the tzSet command to set the timezone. In the following example, EST is used for Eastern

Standard Time.

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

on page 63.

5 To confirm, use the date command.

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

Synchronizing the Real Time Clock with the Timeserver

Follow this procedure to synchronize the real time clock with the timeserver. For more information on the
commands used in this procedure, see Commands Listed Alphabetically by Function

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

SNC4000 > setTimeHost “butter”
Time Host butter value = 0 = 0x0

2 Synchronize the Real Time Clock with the timeserver using the rtcSetCurrent command.

SNC4000 > rtcSetCurrent

value = 0 = 0x0

on page 63.

Disabling the Timeserver Host

Follow the step below to disable a timeserver host.

1 To disable the timeserver functionality, use the setNettime command.

SNC4000 > setNettime 0
Nettime 0 value = 0 = 0x0

The time will revert to the time set on the Real Time Clock.

16 Getting Started

Post Installation

Perform the procedures below to verify connections, set up the FC port, SNMP traps, and email alerts. You
will need to use the ADIC Management Console. For more information, see the ADIC Management Console
User’s Guide.

1 Using the ADIC Management Console, confirm that all attached devices are displayed under each

channel.

2 Verify/set configuration for the FC Port. The speed and connectivity settings of the SNC default to auto

detect and in most configurations no additional configuration should be necessary. However, if the
install environment requires custom settings, the following should be confirmed:

Speed

Connection
Options

Loop ID: Soft / Hard and specific ID

Port Mode Target or Target & Initiator

For more information about configuring FC and the implications of each setting see the ADIC Management
Console User's Guide.

CAUTION

3 Configure all SNMP Traps. For more information, see the ADIC Management Console User’s Guide.

4 Save your current configuration in case you need to restore it in the future. For more information, see

Configuration Files

5 If you are not running the most current level of SNC firmware, update your firmware. For more

information, see Updating Firmware

1Gbps or 2Gbps

Point to Point (Fabric), Loop, or Loop
Preferred

Do not set Port Mode to Initiator for this library. Setting Mode to
Initiator will prevent hosts from seeing library drives and media
changer. Initiator mode makes the SNC appear as a host instead of a
storage device.

.

.

6 Configure email alerts. For more information, see the ADIC Management Console User’s Guide.

Configuration Files

It is recommended that you save a copy of your configuration in case you need to restore it at a future date.
The ADIC Management Console is the simplest and most efficient tool for saving/loading configurations.
For more information, see the ADIC Management Console User’s Guide. You can also use the service
terminal as an alternate method to perform these operations. The procedures below explain how to save
and load configuration files using the service terminal.

Saving a Configuration File

Follow the procedure below to save your configuration.

1 From the HyperTerminal window type sz “config.cfg” and press Enter.

“config.cfg” is an example of a name. You can specify a different filename but it must be in quotes,
it must be eight characters or less, and it must end in .cfg.

SNC 4000 User’s Guide 17

2 From the HyperTerminal window, select Transfer and Receive File.

3 From the Receive File dialog enter the path to the folder where you want to save the file or click the

Browse button and navigate to it.

4 For the Receiving protocol select Zmodem and press the Receive button.

5 Wait for the Configuration Download Complete status message to be displayed on the service

terminal indicating successful completion.

6 If HyperTerminal reports an error, try to receive the file again.

Loading a Configuration File

Follow the steps below to load a saved configuration file.

1 From the HyperTerminal window, at the SNC4000> command prompt, type rz and press Enter.

2 From the HyperTerminal window select Transfer and Send File.

3 From the Send File dialog enter the path and file name where the firmware file is located or click the

Browse button and navigate to it. In the Protocol field, select Zmodem and click the Send button.

4 Wait for the Configuration Update Complete status message to be displayed on the service

terminal indicating successful completion.

5 Reboot the SNC for the update to take effect.

6 If HyperTerminal reports an error, try to send the file again.

Updating Firmware

You can upgrade the firmware on the SNC 4000 using the ADIC Management Console. For more
information, see the ADIC Management Console User’s Guide.

18 Getting Started

Scalar Firewall Manager

Scalar Firewall Manager (SFM) is a software feature that collects all host and target information and
manages the end-to-end access control in the SAN. It allows the system administrator to control access
privileges between individual Host Bus Adapters (HBAs) and target devices connected to the SNC’s SCSI
and Fibre Channels. The system administrator uses the ADIC Management Console to administrate SFM.

• SFM technology enables Storage Area Networks with multiple users to share the same connectivity
channels or pipes to access the same or different storage elements or resources. Therefore,
multiple virtual private connections can be created on the same Storage Networking infrastructure.

• SFM is completely host independent and requires no software components on the host (an optional
automatic Host Registration Service that provides periodic host status information is included). It
has no interface dependencies and supports Fibre Channel, SCSI, or any other SAN interface. It is
also independent of the storage elements and requires no change in legacy or new storage devices.

• SFM keeps track of Fibre Channel HBAs by their unique World Wide Name (WWN). Because Fibre
Channel switches also have a WWN, SFM can see FC switches connected to the SNC and control
their access.

• SFM manages access for hosts connected through FC switches and hubs to the SNC. The SNC
supports up to 2048 LUNs across all of its interfaces. It has a virtual limit for how many hosts (HBAs
or Initiators) are connected to each port. The default setting allows 64 initiators per port.
Consequently, with the default setting, an SNC with its two Fibre Channel ports can support up to
128 host connections.

• SFM creates and maintains a database in non-volatile memory to hold persistent information about
each HBA (or Initiator) and its LUN access privileges.

• When you perform a Save Configuration from the ADIC Management Console, it saves both the
persistent device map and the SFM database to a file. This allows all configuration settings to be
loaded onto another SNC in the event that the SNC needs to be replaced.

• When SFM is enabled for the first time, it takes a “snapshot” of the existing configuration. SFM
automatically assigns access between HBAs and the storage elements that they currently have
access to so that an existing configuration will not be affected. Consequently, online hosts attached
to an SNC will continue to retain their current access permissions to storage elements.

• Any HBA (or Initiator) that is added to a SAN connection at a later time will only have access to the
SNC Command and Control LUN. In this case, the system administrator must explicitly set access
privileges to the desired storage element for each host connection

SNC 4000 User’s Guide 19

.

Host Registration Service

The Host Registration Service (HRS) is a small service/daemon installed on hosts which access the library.
HRS simplifies security configuration and allows administrators to monitor host connections to the library.
To accomplish this, HRS sends a periodic data pulse through the host’s Fibre channel HBA to the library.
The pulse consists of the host’s WWN, network name, HBA type, and HBA driver level. The SNC records
this information and displays it in the AMC.

This information is used to simplify configuration of the embedded firewall, SFM. Instead of manually
associating an HBA WWN with a specific host, the Scalar Firewall Manager, SFM, is configured using well
known host names. HRS is also used to monitor the status of hosts connected to the library. When the SNC
receives a HRS pulse from a host, the host is displayed in the AMC as online. If the SNC does not receive
two consecutive HRS pulses, the host will be listed as offline.

Note

CAUTION

The SFM database contains separate fields to store the WWN, host name, host type, connection, host
status and a LUN Access field that holds information about LUNs assigned to it.

When the SNC is first booted, SFM initially treats all hosts as “offline” until a host sends an I/O request to
the SNC. SFM detects the I/O and obtains the WWN of the HBA or Initiator. If the WWN is already in the
database (already registered), SFM stores the value “online” in the status field.

If the WWN is not in the database, SFM adds it and stores the value “online” in the status field. SFM sets
the default value for each of the other parameter fields to “unknown”.

At this point, SFM has registered the HBA or Initiator but has minimal information about it. The system
administrator can proceed to complete the registration by using the SNC to manually enter the “unknown”
host information and assign access privileges to LUNs.

The AMC view must be refreshed to see status changes for hosts.

If SFM is not enabled, hosts will not appear in the AMC.

Installing the Host Registration Service

The Host Registration Service software is included on the CD that shipped with the SNC.

1 Insert the SNC software CD into the host.

2 Browse to the client software directory.

3 Open the directory for your Operating System and open the readme. This file lists specific instructions

for installing the package.

4 Install the package.

5 Reboot the server.

6

(Optional) Configure security for the SNC, channel zoning, and/or the Scalar Firewall Manager. For

definitions and specific instructions, see the ADIC Management Console User’s Guide.

Once installed, the service runs automatically and does not require further system administrator interaction.
From the ADIC Management Console, you can see the Fibre Channel that the host is connected to and you
can tell whether the host is online or offline. For software updates, visit “Service and Support” at

www.adic.com

20 Scalar Firewall Manager

.

Note

After SFM is enabled, you may want to add a Host (or Initiator) to the SAN configuration or remove it from
the SAN configuration. This section describes how to add and remove hosts.

You have to refresh the SNC from the ADIC Management Console to see host
status changes.

Adding a Host to the SAN Configuration

You can connect a new host to the SAN at any time. SFM automatically adds the new host to the database
as soon as the host is attached to the SAN. If you want to attach a new host at this time, see Attaching a

New Host to the SAN. Otherwise, if you want to configure SFM before attaching the host, see Adding a Host
Before Attaching it to the SAN.

Attaching a New Host to the SAN

When you attach a new host to the SAN, SFM automatically detects the host and adds it to the SFM
database. When you connect or refresh the SNC from the ADIC Management Console, you can see the
new host in the SFM Access Settings window. If the Host Registration Service is running on the host, SFM
automatically obtains the host parameters. If the Host Registration Service is not running on the host, SFM
only knows the WWN of the HBA. In this case, you can manually enter the other host parameters.

Follow these steps to add a new host to the SAN configuration:

1 Connect the host to the SAN.

2 If you need to install the Host Registration Service, see Installing the Host Registration Service

20.

3 If you need to determine LUN assignments for the devices you want to assign to the new host, see the

ADIC Management Console User’s Guide.

4 For further information about entering host parameters, see the ADIC Management Console User’s

Guide.

5 Refer to the see the ADIC Management Console User’s Guide to assign access permissions for the new

host.

6 Verify that the new host has access to the assigned devices.

7 Save your configuration, as explained in Saving a Configuration File

on page 17.

on page

Adding a Host Before Attaching it to the SAN

You can add a host that has not yet been attached to the SAN and configure its access permissions
beforehand. For more information, see the “Add VPS/SFM Hosts” section of the ADIC Management
Console User’s Guide.

After the new host has been added you can assign its access permissions.

Removing a Host from the SAN Configuration

You may want to remove a host from the SFM database. SFM will prevent you from removing a host that is
online. For more information, see the “Deleting VPS/SFM Hosts” section of the

User’s Guide.

ADIC Management Console

SNC 4000 User’s Guide 21

Combining SFM with Channel Zoning

Although it is possible to combine SFM and Channel Zoning, it is not recommended. SFM cannot assign
access to LUNs on channels rendered inaccessible by Channel Zoning. If you do have a legacy Channel
Zoning configuration, it is recommended that you edit the zones to permit all SAN Connections to have
access to all SCSI channels, or you may end up with inaccessible devices that you had intended to be
accessible.

22 Scalar Firewall Manager

Connecting to the Service Port

The service port on the SNC is an RS-232C port, configured at 19200 Baud, with 8 data bits, 1 stop bit, no
parity and either hardware flow control or Xon/Xoff flow control.

To connect the SNC service port, a service terminal will be required. The service terminal can be any
standard personal computer that contains a serial (COM) port. Connection between the SNC and the
service terminal is established using a 9-pin to 9-pin straight through cable.

Note

Some systems, such as Unix workstations, may require a different cable or
adapter to connect to the SNC service port.

Service Port Connections

The figure below shows the service port connections.

Figure 6 Service Port Pinout

Connections are listed in the following table.

Table 1 DB-9 RS-232 Connector Pin Assignments

Pin
Number

Signal Name Abbreviation

Direction relative to SNC
4000

1 Carrier Detect CD In

2 Transmit Data TD Out

3 Receive Data RD In

4 Data Terminal Ready DTR Out

5 Signal Ground SG -

SNC 4000 User’s Guide 23

Table 1 DB-9 RS-232 Connector Pin Assignments

6 Data Set Ready DSR In

7 Clear to Send CTS In

8 Request to Send RTS Out

9 Ring Indicator RI In

Connecting the Service Terminal

Once the service terminal has been attached to the SNC service port, a terminal emulation program will be
required to access the SNC's command line interface. Most operating systems come with HyperTerminal
or some other form of terminal emulation program by default. If a terminal emulation program is not present,
one should be available (or at least recommended) by your operating system provider.

Hardware Required

• RS-232 DB9F straight through cable

• RS-232 DTE terminal or desktop/laptop computer running terminal emulation software

Connecting using HyperTerminal

This section shows the steps to setup use the HyperTerminal program. Other terminal emulation programs
operate in a similar fashion.

1 Connect the straight through cable (and the 9- to 25-pin adapter if applicable) from the computer serial

(COM) port to the SNC service port.

2 On the service terminal, select the HyperTerminal icon and double-click on it.

3 In the New Connection dialog box enter SNC4000 for the name and click OK.

4 In the Connect To dialog box, for the Connect using field select the COM port number that you have

chosen and click OK.

In the COM Properties dialog box select the following:

• Bits per second:19200

• Data bits:8

• Parity:None

• Stop bits:1

• Flow Control: Hardware or Xon/Xoff

5 Click OK.

Connecting using Telnet

In instances where command line access to the SNC is required and local access is not permissible, it is
possible to Telnet into the SNC. Telnet access should be reserved for remote update of the SNC clock, IP
information, or collection of a supportdump. For all other management tasks, the ADIC Management
Console is the preferred method of updating information.

24 Connecting to the Service Port