ADIC Scalar 1000, SNC 5100 User Manual

SNCTM 5100 for the

Scalar ® 1000 and 10K

User Guide

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

This document contains pr oprietar y info rmation which is protect ed by cop yright . All ri ghts are r eser ved. No part of this document may be photocopied, reprodu ced, or translated to anoth er language without pri or written consent of ADIC.

ADIC shall not be liable for errors contained here in or for incidental or consequential damages (includ ing 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 made unintentionally.

ADIC and ADIC Europe are trademarks of Advanced Digital Information Corporation.

Advanced Digital Information Corporation ADIC Europe ADIC/GRAU Storage Systems GmbH Tel.: +1 303-705-3900 (USA) ZAC des Basses Auges Eschenstraße 3 Fax: +1 303-792-2465 (USA) 1, rue Alfred de Vigny D-89558 Böhmenkirch, Germany Customer Assistance: 1-800-827-3822 78112 Fourqueux, France Tel:+00.800.9999.3822 World Wide Web: http://www.adic.com Tel.: +33.1.3087.5300

Fax: +33.1.3087.5301

Document number: 6-00020-02

See the release notes for information about system requirements and pre-installation procedure

ADIC CORPORATE • 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-266-4000

SNC 5100

Notices

Welcome . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1

Safety Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1

Safety Inspection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1

Remove AC Power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2

External Machine Check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2

Safety Label Check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2

Fusing Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3

Environmental Notices and Statements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3

Product Recycling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3

Lithium Battery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3

Laser Safety . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3

General Restrictions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4

Usage Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4

Regulatory Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4

Electronic Emission Statements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4

Federal Communications Commission (FCC) Statement . . . . . . . . . . . . . . . . . . . .4

Industry Canada Compliance Statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5

European Community Compliance Statement. . . . . . . . . . . . . . . . . . . . . . . . . . . . .5

VCCI Notice (Japan Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6

BSMI Notice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6

EN 55022 Compliance (Czech Republic Only). . . . . . . . . . . . . . . . . . . . . . . . . . . .6

CE Notice. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7

Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8

Introduction

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9

Configuration Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10

Address Mapping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10

Interface Protocol Awareness . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10

Hardware Product Description and Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11

Fibre Channel Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11

Ultra2 SCSI I/O Interfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12

SCSI Command Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13

Ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13

Service Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13

LED Indicators. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14

FC 1-2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14

6-00020-02 iii

SNC 5100

SCSI 1-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15

PWR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15

RDY. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15

ERR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15

Supported Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15

Supported Devices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16

Operating Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16

Operating Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16

Power Consumption. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17

Power Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17

Install the SNC 5100

Pre-installation Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19

Installation Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20

Host Utility Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23

Post-Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24

Other Installation Issues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24

Attaching SCSI Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24

Maximum Number of LUNs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24

Transfer Rates: Ultra, Fast, and Asynchronous. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25

Wide and Narrow SCSI Buses. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25

Table of SCSI Terminology and Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26

SCSI Bus Termination. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27

Problems on the SCSI Bus. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27

Missing terminator at the end of a SCSI bus. . . . . . . . . . . . . . . . . . . . . . . . . . . . .28

Excessive termination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28

Multiple devices at the same ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28

Target device set to initiator’s ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28

Bent pins in a SCSI connector. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28

Improper device type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28

Improper terminator type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28

Inadequate cables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29

Mixed cable types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29

Unshielded cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29

Fuses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29

Host Bus Adapter Setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29

Installing the SAN Explorer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30

Installing the Host Registration Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30

Power-Up and Boot Sequence Guidelines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30

iv 6-00020-02

SNC 5100

Maintenance Action Plans

Event Codes and Actions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34

Check Event Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34

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

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

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

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

Visually Inspect LEDs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43

Check for Problems on Attached Devices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44

Check Host Versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44

Check SNC 5100 Product Versions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44

ADIC Management Console version. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44

Firmware version. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45

Hardware version. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45

Quick Component Check. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .46

Perform Health Check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .46

Check the Host Event Log. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47

Database Full MAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47

Device Access MAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48

Check Fibre Channel Port Status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49

Check SCSI Channel Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49

Check Channel Zoning Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50

SCSI Channel MAP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50

Get SCSI Information for the SNC 5100 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50

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

Compare Listed versus Physical Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52

Compare Listed versus Supported Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52

Check SCSI Bus Termination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .53

Check for Multiple SCSI IDs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54

Improper Device Type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55

Examine SCSI Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .56

Examine SCSI Connectors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .57

SCSI Health Check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .57

SCSI Loop Back Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .58

Testing SCSI Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59

Isolating SCSI devices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59

Restore SCSI Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60

Fibre Channel MAP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61

Verify Fibre Channel Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61

Test GBIC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .62

6-00020-02 v

SNC 5100

Examine Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63

Fibre Channel Loop Back Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63

Testing Fibre Channel Optical Cable. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .64

Replace Fibre Channel Cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65

Replace Fibre Channel Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65

MAP for the SNC 5100 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .66

Observe Operational LED Behavior . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .66

Temperature MAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .66

Notification of Problems in Temperature Subsystem . . . . . . . . . . . . . . . . . . . . . . . . .67

Temperature Warnings or Alarms Received . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67

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

Power MAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .68

Ethernet MAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .69

Service Port MAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .75

Check the RS-232 Cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .76

Check Connection with Boot Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .76

Virtual Private SAN®Scalar Firewall Manager Settings MAP. . . . . . . . . . . . . . . . . . . . .77

Check Scalar Firewall Manager Access Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . .77

Verify Host Access to Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .78

Removal and Replacement Procedu re s

Handling Electrostatic Discharge-Sensitive Parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .81

Removing and Replacing the GBIC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .82

Removing the GBIC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .82

Replacing the GBIC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .82

Before Removing or Replacing the Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .82

Removing and Replacing the Unit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .83

Removing the SNC 5100. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .83

Replacing the SNC 5100 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .84

Final Diagnostic Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .84

Final Test Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .84

Fibre Channel Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .85

Test Fibre Channel Port 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .85

Test Fibre Channel Port 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .85

Test SCSI Port 1 and 2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .86

Test SCSI Port 3 and 4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .86

Ethernet Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .86

Network Setup for the SNC 5100 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .87

Updating the SNC 5100. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .90

Post-Repair Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .91

vi 6-00020-02

SNC 5100

Connecting to the Service Port

Service Port Connections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .95

Connecting the Service Terminal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .96

Hardware Required . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .96

Initial Setup of HyperTerminal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .97

Verifying the Connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .97

Updating Firmware and Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .98

Updating SNC 5100 Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .98

Saving a Configuration File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .99

Loading a Configuration File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .99

Zmodem Status Code Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .100

Setting the Time and Date . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .101

Setting the Real Time Clock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .101

Adding a Host System Running Timeserver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .102

Disabling the Timeserver Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .103

Synchronizing the Real Time Clock with a Timeserver . . . . . . . . . . . . . . . . . . . . . .104

Service Port Command Reference

Managing the SNC 5100 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .105

Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .105

Diagnostic Command Reference

Boot Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .187

Entering Diagnostic Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .187

Restoring Normal Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .188

Special Procedures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .188

Health Check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .188

Manual Health Check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .188

Event Log Dump . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .189

Retrieving the Code 43 Dump File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .189

Boot Mode Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .191

Diagnostic Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .191

6-00020-02 vii

SNC 5100

POST Error Codes

POST Boot Behavior. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .197

ROM Init . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .197

Initial POST. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .198

Simple Access Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .198

Bitwalk Test. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .199

Memory Size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .199

Pattern Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .199

Address Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .200

Secondary POST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .200

Identify and Execute bootrom . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .200

Start of Bootrom . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .201

POST Service Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .201

A - Cold boot from [A]lternate bootrom . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .202

B - Cold [B]oot from primary bootrom . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .202

R - [R]eceive new boot image from serial port . . . . . . . . . . . . . . . . . . . . . . . . . .203

V- full [V]ersion information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .203

Error Displays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .203

Startup Message Reference

Bootrom Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .205

LIC Initialization Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .206

Final Startup Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .207

Glossary

Acronyms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .209

Warranty and EUL A

ADIC Limited Product Warranty . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .211

ADIC End User License Agreement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .213

INDEX

viii 6-00020-02

SNC 5100

Notices

Welcome

ADIC is the leading expert in open systems data storage solutions. Your new SNC 5100 is an intelligent storage networking appliance. It pro vides

a management platform for any-to-any connectivity, increases interoperability, integrates protocol-aware services, and improves reliability, security, and manageability in the Storage Area Network (SAN).

This manual is intended to provide hardware and firmware reference support for ADIC customers and professional services team members.

Safety Notices

The CAUTION notice indicates the possibility of damage to a program, device, system, or data.

The DANGER notice warns you of conditions or procedures that could result in death or severe personal injury.

DANGER An electrical outlet that is not correctly wired could place hazardous voltage on

metal parts of the system or the devices that attach to the system. It is the responsibility of the user to ensure that the outlet is correctly wired and grounded to prevent an electrical shock.

Safety Inspection

Perform the following safety checks to identify unsafe conditions. Be cautious of potential safety hazards not covered in the safety checks. If unsafe conditions are present, determine how serious the hazards are and whether you should continue before correcting the problem.

6-00020-02

Welcome 1

SNC 5100

Remove AC Power

If the SNC 5100 is not po wered off, perform the following st eps to remove A C power.

Step 1. Perform a controlled system shutdown of attached host systems. Step 2. Set the Power switch on the SNC 5100 to the off position. Step 3. Disconnect the power cord from the power source.

External Machine Check

Perform the following external machine check: Step 1. Verify that the external cov er and front bezel of the unit are present

and not damaged.

Step 2. Check the power cord for damage. Step 3. Check the external signal cable for damage. Step 4. Check the cover for sharp edges, damage, or alterations that expose

the internal parts of the device.

Step 5. Correct any problems that you find.

Safety Label Check

Perform the following label check: Step 1. Verify that the safety label shown in Figure 1 is installed on the

SNC 5100.

Figure 1 Safety Label

2Safety Notices

6-00020-02

SNC 5100

Step 2. Check the voltage label on the bottom of the device to ensure it

matches the voltage at the power source.

Step 3. Check the voltage level at the power source.

Fusing Requirements

The SNC 5100 power supply has a 3.15 A, 250 VA C time delay fuse on the AC line input, and the AC harness uses an axial lead, 3A, 250 VAC time delay fuse in the neutral line. There are no user-serviceable parts in the SNC 5100.

Environmental Notices and Statements

Product Recycling

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

Lithium Battery

DANGER

Risk of fire, explosion, or burns. Do not short circuit, crush, heat above 100 C, incinerate, or disassemble the battery.

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.

6-00020-02

Environmental Notices and Statements 3

SNC 5100

General Restrictions

The classification is valid only if the module is operated within the specified temperature and voltage limits. The system using the module must provide power supply protection that guarantees that the system power source will cease to provide power if the maximum recommended operation limit or more is detected on the +3.3 V/+5 V at the power source. The operating temperature of the module must be in the temperature range given in the recommended operating limits. These limits guarantee the laser safety.

Usage Restrictions

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

Regulatory Notices

Electronic Emission Statements

This section gives the electronic emission notices or statements for the United States and other countries.

Federal Communications Commissi on (FCC) Statement

This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment. This equipment generates, uses, and can radiate radio frequency energy and, if not installed and used in accordance with the instruction manual, may cause harmful interference to radio communications. Operation of this equipment in a residential area is likely to cause harmful interference, in which case the user will be required to correct the interference at his own expense.

4 Environmental Notices and Statements

6-00020-02

SNC 5100

Properly shielded and grounded cables and connectors must be used in order to meet FCC emission limits. ADIC is not responsible for any radio or television interference caused by using other than recommended cables and connectors or by unauthorized changes or modifications to this equipment. Unauthorized changes or modifications could void the user’s authority to operate the equipment.

This device complies with Pa rt 15 of the FCC Rules. Operation is subject to the following two conditions: (1) this device may not cause harmful interference, and (2) this device must accept any interference received, including interference that may cause undesired operation.

Industry Canada Compliance Statement

This Class A digital apparatus complies with Canadian ICES-003. Avis de conformité à la réglementation d’Industrie Canada: Cet appareil

numérique de la classe A est conform à la norme NMB-003 du Canada.

European Community Compliance Statement

This product is in conformity with the protection requirements of EC Council Directive 89/336/EEC on the approximation of the laws of the Member States relating to electromagnetic compatibility. ADIC cannot accept responsibility for any failure to satisfy the protection requirements resulting from a non-recommended modification of the product, including the fitting of non-ADIC option cards.

This product has been tested and found to comply with the limits for Class A Information Technology Equipment according to European Standard EN

55022. The limits for Class A equipment were derived for commercial and industrial environments to provide reasonable protection against interference with licensed communication equipment.

Caution

This is a Class A product. In a domestic environment, this product may cause radio interference in which case the user may be required to take adequate measures.

Where shielded or special cables (for example, cables fitted with ferrites) are used in the test to make the product comply with the limits.

6-00020-02

Environmental Notices and Statements 5

SNC 5100

Properly shielded and grounded cables and connectors must be used in order to reduce the potential for causing interference to radio and TV communications and to other electrical or electronic equipment. Such cables and connectors are available from ADIC authorized dealers. ADIC cannot accept responsibility for any interference caused by using other than recommended cables and connectors.

VCCI Notice (Japan Only)

BSMI Notice

EN 55022 Compliance (Czech Republic Only)

This device belongs to category B devices as described in EN 55022, unless it is specifically stated that it is a category A device on the specification label. The following applies to devices in category A of EN 55022 (radius of protection up to 30 meters). The user of the device is obliged to take all steps necessary to remove sources of interference to telecommunication or other devices.

6 Environmental Notices and Statements

6-00020-02

SNC 5100

Pokud nenÌ na typovÈm ötitku poËÌtaËe uvedeno, ûe spad· do t¯Ìdy A podle EN 55022, spad· automaticky do t¯Ìdy B podle EN 55022. Pro za¯ÌzenÌ za¯azen· do t¯Ìdy A (ochrannÈ p·smo 30m) podle EN 55022 platÌ n·sledujÌcÌ. Dojde-li k ruöenÌ telekomunikaËnÌch nebo jin ych za¯ÌzenÌ, je uûi v atel po vinen provÈst takov· opat¯enÌ, aby ruöenÌ odstranil.

CE Notice

Marking by the indicates compliance of this tape library to the EMC (Electromagnetic Compatibility) directive of the European Community. Such marking is indicative that this tape library meets or exceeds the following technical standards:

• EN 55022:1998 — “Limits and Methods of Measurement of Radio Interference Characteristics of Information Technology Equipment.”

• EN 55024:1998 — “Information technology equipment – Immunity characteristics – Limits and methods of measurements.”

• EN 61000-3-2 — “Harmonic current emissions test.”

• EN 61000-3-3 — “Voltage fluctuations and flicker in low-voltage supply systems test.”

• EN 61000-4-2 — “Electrostatic discharge immunity test.”

• EN 61000-4-3 — “Radiated, radio-frequency, electromagnetic field immunity test.”

• EN 61000-4-4 — “Electrical fast transient/burst immunity test.”

• EN 61000-4-5 — “Surge immunity test.”

• EN 61000-4-6 — “Immunity to conducted disturbances, induced by radio-frequency fields.”

• EN 61000-4-8 — “Power frequency magnetic field immunity test.”

• EN 61000-4-11 — “Voltage dips, short interruptions and voltage variations immunity test.”

• EN 60950:1992 + Amd1:1993 + Amd2:1993 with considerations to

Amd.3:1995 — “Safety of Information Technology Equipment including Electrical Business Equipment.”

A “Declaration of Conformity” in accordance with the preceding standards has been made and is on file at ADIC Europe, ZAC de Basses Auges, 1, rue Alfred de Vigny, 78112 Fourqueux, FRANCE.

6-00020-02

Environmental Notices and Statements 7

SNC 5100

Documentation

Although the material contained herein has been carefully reviewed, ADIC does not warrant it to be free of errors or omissions. We reserve the right to make corrections, updates, revisions, or changes to the information contained herein.

• Send e-mail to: techdocs@adic.com

8 Documentation

6-00020-02

SNC 5100

Introduction

This chapter describes the SNC 5100. It provides the following information:

• Overview

• Configuration Support

• Hardware Product Description and Features

• Supported Platforms

• Supported Devices

• Operating Specifications

Overview

The SNC 5100 is a 1U high, half-rack width, AC powered storage networking controller.

It is the interface between storage and Open System Host interfaces and provides Fibre Channel to SCSI connectivity. One possible configuration is illustrated in Figure 2.

Figure 2 Configuration Overview

6-00020-02

Overview 9

SNC 5100

Configuration Support

The SNC 5100 provides two Fibre Channel interfaces. The FC interfaces are configured with Giga Bit Interface Converter (GBIC) modules.

In addition, the SNC 5100 has four Ultra2 SCSI interfaces. The Ultra2 interfaces are Low Voltage Differential (LVD).

See Figure 3.

Figure 3 Configuration Detail

Address Mapping

The SNC 5100 maps addresses across and between these different interfaces and preserves the persistency of the address maps across po wer ups of sy stems, devices, and the SNC 5100. The SNC 5100 supports the attachment of up to 2048 unique devices across multiple interfaces.

Interface Protocol Awareness

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

10 Configuration Support

6-00020-02

SNC 5100

Hardware Product Description and Features

This section describes the capabilities of the product and outlines some of the key features of its interfaces.

• An IBM 405GP 200 MHz processor, with integrated instruction and data caches, and internal serial I/O and Ethernet interfaces.

• An Intel 80303 100 MHz Processor, with integrated instruction and data caches.

• QLogic 23x0 Fibre Channel protocol chip

• 32 MB ECC protected SDRAM program memory.

• 128 MB ECC protected SDRAM data buffer memory.

• FLASH memory for operational firmware, power on self-test code,

diagnostic functions, and system utilities.

• Non-volatile SRAM for persistent configuration tables and event logs.

• VxWorks real-time operating system (RTOS).

Fibre Channel Interfaces

Interfaces for host and device attachment include two 2-Gb/s bi-directional Short Wave connections.

Table 1: Fibre Channel Connections

GBIC speed Cable Type Distance

1.062.5 Mb/sec 62.5 µ multimode 300 m

1.062.5 Mb/sec 50 µ multimode 500 m

2.125 Mb/se c 62.5 µ multimode 300 m

2.125 Mb/se c 50 µ multimode 500 m

The Giga-Bit Interface Converter (GBIC) can interoperate with both 2 Gb/sec and 1 Gb/sec data links. The GBIC is hot-swappable and is the only component, except for the SNC 5100 unit itself that is a Field Replaceable Unit (FRU). See “Removing and Replacing the GBIC” on page 82.

6-00020-02

Hardware Product Description and Features 11

SNC 5100

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

Fibre Channel interfaces support the following Public and Priv ate Loop modes:

• Target

• Initiator

• Target and Initiator

The maximum number of initiators connected via Fibre Channel is 64 per Fibre Channel port.

Fibre Channel Interfaces also support the following connection options:

• Loop

• Point-to-Point

• Loop Preferred

The Fibre Channel controller is compliant 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 and Tape Medium Changers (FC-Tape), Rev 1.17, Technical Report, T11/99-069v4

• Fibre Channel protocol SCSI (FCP-SCSI)

Ultra2 SCSI I/O Interfaces

• Four Low Voltage Differentia l (LVD) Ultra2 SCSI channels with internal termination.

• SCSI channels have automatic speed and width negotiation capability for wide or narrow bus widths and Standard, Fast, Ultra or Ultra2 speeds.

• SCSI channel support for up to 15 SCSI target IDs and up to 32 LUNs per ID (subject to an overall total of 2048 devices). The SNC 5100 uses one

12 Hardware Product Description and Features

6-00020-02

SNC 5100

LUN for command and control so that the remaining 2047 LUNs are available for SCSI devices. For each Fibre Channel interface, the SNC 5100 occupies one Fibre Channel ID and all SCSI target devices are available as LUNs on the same Fibre Channel ID.

• The maximum number of initiators that can be connected via SCSI Channel is 1 per SCSI Channel.

• The unit provides four SCSI-3 VHDCI connectors for maximum mechanical reliability.

The SCSI interfaces are compliant with the following SCSI specifications:

• ANSI X3T9.2 375D Rev. 101, SCSI - 2

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

SCSI Command Support

• SCSI-3 SCSI Architecture Model - 2 (SAM-2)

• SCSI-3 SCSI Primary Commands - 2 (SPC-2)

• SCSI-3 SCSI Block Commands - 2 (SBC-2)

• SCSI-3 Stream Commands (SSC)

• SCSI-3 Medium Changer Commands (SMC)

• SCSI-3 Multi-Media Commands - 2 (MC-2)

• SCSI-3 Controller Commands - 2 (SCC-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 (DTE). It connects to the host serial port with a 9-pin to 9-pin null-modem cable. It is compatible with serial ports on personal computers.

6-00020-02

Hardware Product Description and Features 13

SNC 5100

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:

• 19,200 Baud

• 8 data bits

• No parity

• One stop-bit

• Hardware Flow Control or Xon/Xoff or other internally detected error

conditions

LED Indicators

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

Figure 4 LEDs When the SNC 5100 is first turned on, so me of the LEDs wi ll be on an d others

will flash while it is booting. The following list briefly describes how to interpret the LED signals. See also

“POST Error Codes” on page 197.

FC 1-2

For each 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 Fibre Channel device. It will flash when there is activity on the Channel.

14 Hardware Product Description and Features

6-00020-02

SNC 5100

SCSI 1-4

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. It will flash when there is activity 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 5100 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 5100 has finished booting. If the RDY LED remains ON or OFF for more than a few seconds, it means there is a problem.

The RDY LED will flash rapidly, four times per second, when the SNC 5100 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 197.

Supported Platforms

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

For a current list of supported platforms, configurations, and host bus adapters, visit

www.adic.com.

6-00020-02

Supported Platforms 15

SNC 5100

Supported Devices

The architecture and implementation of the SNC 5100 software has full SCSI-2 and SCSI-3 target and initiator support. The SNC 5100 has support for disk, tape, and medium changer devices. The product supports all these devices with the same firmware. Multiple target device type drivers coexist to support different device types.

For a current list of supported devices, visit

www.adic.com.

Operating Specifications

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

The enclosure is designed for strength, durability, and electromagnetic and radio frequency interference (EMI/RFI) immunity.

The external dimensions are:

• 1.61” high

• 12” deep

• 8.61” wide

• weight: 2.70 kg (~5.93 lb.) with bezel

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 in a non-volatile location immune from user erasure, permitting environmental causes of failure to be determined.

Operating Environment

• Operating Temperature: 10° C to 40° C

• Storage Temperature: -40

• Humidity: 10%-90% Operating, Non-Condensing

16 Supported Devices

° C to 65° C

5%-95% Non-operating, Non-Condensing

6-00020-02

SNC 5100

Power Consumption

The power consumption of this product depends on the number and type of installed interface options. Maximum power consumption is 45 watts in active mode. The SNC 5100 can provide up to 3.25 watts of termination power per SCSI channel.

Power Requirements

The power supply status is monitored as part of th e Enclosure Monitor Register and is reported by the front panel LED.

For more information on LEDs, see the ADIC Management Console User Guide.

• Input voltage range of 85-264 VAC, 47-63 Hz.

• Maximum power draw for the 90 watt supply running at 72% typical

efficiency is 65 watts.

• Maximum input current of 1.05 amps max at 120 VAC, 0.51 amps m ax at 230 VAC.

• Input surge current (cold start) of 17A at 120 VAC, 32A at 230 VAC.

6-00020-02

Operating Specifications 17

SNC 5100

18 Operating Specifications

6-00020-02

SNC 5100

Install the SNC 5100

This section covers installation of the SNC 5100, SCSI devices, and Host Bus Adapter.

Before you or your service representative installs the SNC 5100, you must perform the steps in the "Pre-installation Procedure".

Pre-installation Procedure

It is important that the steps in this procedure are completed before you begin the installation of the SNC 5100. This ensures a successful installation of the product.

Table 2: Pre-Installation Checklist

Step Actions Comments and References

Verify that the required host platform

operating system version is compatible with the installed Fibre Channel Host Bus Adapter (HBA).

Verify that the HBA BIOS and device

drivers have been procured and are installed in host system(s).

Optionally, install the Host

Registration Service on the hosts that will be connected to the SNC 5100.

Ensure that all host Fibre Channel

cables ° Have been ordered with the product or ° Have been preinstalled and checked and ° Are labeled with host system identifier.

For the most current list of supported platforms, required host platform code updates, and information on how to obtain them, visit www.adic.com.

For the most current list of supported HBAs, the required BIOS and device driver, visit www.adic.com. See “Host Bus Adapter Setup” on page 29.

Consult your service representative.

For more information on Access Options, see the ADIC Management

Console User Guide.

Refer to the HBA Specification provided with your HBA.

6-00020-02

Pre-installation Procedure 19

SNC 5100

Table 2: Pre-Installation Checklist

Step Actions Comments and References

Label both ends of each SCSI cable

with: ° Drive ID and SNC 5100 connector number

If you are using the ADIC

Management Console to manage the SNC 5100, configure an Ethernet environment. Decide on network parameters: Ethernet port configuration decisions: Static IP address____________ Netmask (if required)_________ User-defined SNC 5100 name (optional)__________________

You may need to assign a default network gateway address and/or route table entries: ________________________ Caution: Save this configuration information for future reference.

If you are using the ADIC

Management Console to manage the SNC 5100, run the Ethernet cable from the server (the computer that is designated to run the management software’s Server) to the network hub.

None.

For more information, see the ADIC

Management Console User Guide.

Obtain the network parameters from your network administrator.

Caution: 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 i f you hav e more than one SNC 5100. To change the name, use the command on page 138.

For more information, see the ADIC

Management Console User Guide.

"hostNameSet"

Installation Procedure

The installation checklist has instructions on how to install t he SNC 5100 with SCSI attached storage and Fibre Channel attached hosts.

Step Actions Comments and References

20 Installation Procedure

Table 3: Installation Checklist

Acquire information for Ethernet installation.

Refer to Step 6 in Table 2: Pre-Installation Checklist.

6-00020-02

SNC 5100

Table 3: Installation Checklist

Step Actions Comments and References

Unpack the SNC 5100. Check the

components against the packing slip. Install into rack or on the desktop. See “” on page 24.

Connect the power cord to the SNC

5100. Connect the service terminal to the

Service Port and start a terminal emulation session.

Run the Ethernet cable from the network

hub to the SNC 5100.

Power on the SNC 5100 and observe the

startup messages on the service terminal.

None.

See “Fuses” on page 29.

See “Connecting to the Service Port” on page 95 for the required parameters.

If you are using the ADIC Management Console application, you must configure an Ethernet environment.

For more information, see the ADIC

Management Console User Guide.

Look for “done executing startup script” message. See “Startup Message Reference” on page 205.

Within one minute, the RDY LED should start flashing once per second. If the “done executing startup script” message is not seen or the RDY LED is not flashing as expected, go the “Start MAP” on page 42.

6-00020-02

Look for the “done executing startup

script” message on the service terminal, then power down the SNC 5100.

Connect the SCSI cables from the target

devices to the SNC 5100. Turn on the SCSI target devices.

Turn on the SNC 5100. Within one minute, the RDY LED on the

None.

SNC 5100 should start flashing once per second and the “done executing startup script” message should be displayed on the service terminal.

Installation Pr oc e dure 21

SNC 5100

Table 3: Installation Checklist

Step Actions Comments and References

Configure the Et hernet Port (Host Name,

Address, Routes, reboot).

Observe Ethernet Link LED.

12 Issue hostTypeShow command from

the service terminal to view host type settings for the Fibre Channel ports.

If the hosts that will be connected are not the type shown, issue

setHost

command from the service terminal to set the host type for each Fibre Channel port.

If you are using the ADIC Management Console, you must configure an Ethernet environment.

For more information, see the ADIC

Management Console User Guide

Configure the Ethernet Port using information in Step 6 in Table 2: Pre-Installation Checklist.

Refer to “Network Setup for the SNC 5100” on page 87.

If the Ethernet Link LED is not on, go to “Ethernet MAP” on page 69.

See the "hostTypeShow" command on page 138.

See the

"setHost [port],“OS”"

command on page 162.

14 Issue the fcShow command from the

22 Installation Procedure

Power down the FC host(s).

Connect the FC cables from the FC HBA(s) to the SNC 5100.

Power up the FC host(s).

service terminal to show the status of the FC interface that is installed and connected.

fcShowDevs command from the

Issue service terminal to show SCSI target devices that are connected as seen by the Fibre Channel interface.

If the FC1 and / or FC2 Connection Status LED for the attached host(s) is not on, check FC cables. You may have to change the polarity of the FC cables. If the problem persists, go to “Fibre Channel MAP” on page 61.

See the "fcShow [level ]" command on page 127.

Look for FW State=Ready for each FC interface. If FW State NOT=Ready, go to “Fibre Channel MAP” on page 61.

See the

"fcShowDevs" command on

page 129. If all devices are not shown, go to “SCSI Channel MAP” on page 50.

6-00020-02

SNC 5100

Table 3: Installation Checklist

Step Actions Comments and References

Verify all target devices are available to

the host system.

Use appropriate host system utilities for disk and tape. See Table 4. If all devices are NOT available, reboot host system(s) and check again.

If problem persists, go to “Start MAP” on page 42.

Host Utility Software

Table 4: Host Utility Software

Platform Host Utility Software Name Host Utility Software Function

Windows Disk Administrator

SCSI Adapter control panel applet Tape Devices control panel applet

Solaris

st.conf

reboot -- -r

show attached devices show installed scsi adapters show installed tape device drivers

specify LUNs to be scanned for tape

devices rescan

6-00020-02

AIX

ls/dev/rmt

lsdev -Cc tape lsdev -Cc adapter rmdev - dl fcs[n] -R

where [n] is the

number of the device

cfgmgr

show mapped tape devices list all tape devices

list all adapters remove devices no longer present

reconfigure

HP-UX ioscan -C disk scan for devices

NOTE:

Because systems vary it is generally not possible to ju st replac e the e x isting sd .c on f or st.con f with a new

one. Therefore you will have to add multiple LUN entries for SCSI ID 0 to sd.conf. After the existing line:

name=”st” class=”scsi” target=0 lun=0;

add lines of the form:

name=”st” class=”scsi” target=0 lun=1; until you have as many lines as are needed, one line per storage device or volume. Be sure to increase the LUN number appropriately.

Installation Pr oc e dure 23

SNC 5100

Post-Installation

The ADIC Management Console application allows you to manage multiple SNC 5100s from any location on your network.

For installation and operating instructions, see the ADIC Management Console User Guide.

Other Installation Issues

The SNC 5100 is 8.61" wide x 12.0" deep x 1.61" high. All the connectors, and the air outlets, are at one end of the unit. The air inlet

and power switch at the other. A minimum of 3" clearance is required at the connector end for cables, though 4-5” is recommended. A minimum of 0.75" clearance at the air inlet end and a supply of air at ambient temperature and pressure are required. There are no side clearance requirements.

Attaching SCSI Devices

SCSI devices are attached to any of the SCSI connectors on the rear of the . The device types and speeds, as well as cabling, target IDs, and termination are discussed below.

High quality cables with the correct latches or screws must be used at all times to ensure reliable connections. Cables are not provided with the .

Caution

Ensure that you read this section before you attach any devices to the . A summary table appears at the end of this discussion.

Maximum Number of LUNs

The SNC 5100 supports up to 2048 LUNs.

Caution

Do not attach more than 2048 LUNs to the SNC 5100. Exceeding the 2048 LUN limit will result in unreliable behavior.

24 Post-Installation

6-00020-02

SNC 5100

Transfer Rates: Ultra, Fast, and Asynchronous

The SCSI protocol defines two methods of data transfer: synchronous and asynchronous. Asynchronous transfers may run as fast as 5 MB/sec, while synchronous transfers may run as fast as 180 MB/sec (Ultra2/3) at block sizes of 256 k. Performance is system and configuration dependent.

The rate of transfer is negotiated between a SCSI initiator, such as the SNC 5100, and each target. For each target device identified during a bus scan, the SNC 5100 will request a transfer rate at the fastest transfer rate supported by the SNC 5100. The target will then reply with the maximum transfer rate it wil l support.

Caution

In general, devices that are capable of running at Ultra2/3 speeds s hould not be mixed on a b us with slo wer de vi ces, since the bus speed will be set to mat ch the slowest device on the bus.

Wide and Narrow SCSI Buses

A SCSI bus may be either narrow (8 bit) or wide (16 bit). The SNC 5100 SCSI buses are all wide, but may be connected to narrow devices with the correct cable adapters.

Although it is possible to mix narrow and wide devices on a single SCSI bus, this configuration is not recommended. If any of the devices supports Ultra2/3 speeds, then a mix of narrow and wide devices is prohibited.

In order for the SNC 5100 to locate and communicate with the devices, each device on the SCSI b us must be assigned a unique target ID. On a wide (16 bit) SCSI bus, the SCSI standard allows for a total of 16 tar get IDs. On a narrow (8 bit) SCSI bus, the SCSI standard allows for a total of 8 target IDs. There are no requirements about the ordering or position of the target IDs on the SCSI bus. The only requirement is that there be no duplicate target IDs. By default, the SNC 5100 uses ID 7. Thus, peripheral devices may be assigned IDs 0 through 6 and 8 through 15, typically selected by a switch or jumpers. These settings may be changed.

Caution

Make sure you do not assign more than one device on a bus to the same target ID. This will prevent that bus from working properly.

6-00020-02

Other Installation Issues 25

SNC 5100

The SCSI protocol also defines a priority-based arbitration method, based on the target ID of the device attaching to the bus. The SCSI ID priority order is, from highest to lowest, 7, 6, 5, 4, 3, 2, 1, 0, 15, 14, 13, 12, 11, 10, 9, 8.

Table of SCSI Terminology and Limitations

The following table (look for updates at http://www.scsita.org/) defines the number of devices supported, based on the negotiated transfer type. When reviewing the limitati ons of a bus, the capabilities of the f astest de vices must be considered. The bus length indicates total SCSI bus length, including any internal device cables, rather than the length between any two devices.

Table 5: SCSI Trade Association Terminology

Max.

Bus

Endorsed Terminology

for SCSI Parallel

Interface Technology

Max. Bus Spee d ,

MB/Sec

Bus

Width,

Bits

Lengths

Meters

(1)

Max.

Devices

LVD SCSI 1 (2) 5 8 25 8 Fast SCSI (2) 10 8 25 8 Fast Wide SCSI (2) 20 16 25 16 Ultra SCSI (2) 20 8 25 8 Ultra SCSI (2) 20 8 - 4 Wide Ultra SCSI 40 16 25 16 Wide Ultra SCSI 40 16 - 8 Wide Ultra SCSI 40 16 - 4 Ultra2 SCSI (2,3) 40 8 25 8 Wide Ultra2 SCSI (3) 80 16 25 16 Ultra3 SCSI or Ultra 160 (5) 160 16 (4) 16 Ultra320 320 16 (4) 16

26 Other Installation Issues

6-00020-02

SNC 5100

Table 5: SCSI Trade Association Terminology

Notes:

The listed maximum bus lengths may be exceeded in Point-to-Point and engi neered applications.

Use of the word "Narrow", preceding SCSI, Ultra SCSI, or Ultra2 SCSI is optional.

Single-ended is not defined for speeds beyond Ultra.

Not defined for speeds beyond Ultra2.

After Ultra2 all new speeds are wide only.

SCSI Bus Termination

Each end of a SCSI bus must be terminated correctly. The SNC 5100 provides termination on each of its buses. The terminators can be disabled using a jumper on the SNC 5100 motherboard.

The terminators can also be enabled or disabled from the ADIC Management Console. For more information on SCSI Channel configuration, see the ADIC Management Console User Guide.

Caution

Improper SCSI bus termination may result in excessiv e errors on the SCSI b us, and may lead to data corruption or the inability to communicate with target devices.

The SNC 5100 provides termination power on all SCSI buses for external terminators.

Many SCSI target devices have internal terminators. It is imperative that the terminators be disabled for all devices EXCEPT those at the physical ends of the SCSI bus.

Problems on the SCSI Bus

When a SCSI bus fa ils to operate correc tly, it is most often caused by incorrect connections to the SCSI bus. Common problems include:

6-00020-02

Other Installation Issues 27

SNC 5100

Missing terminator at the end of a SCSI bus

Check that an external terminator is attached or that the end device has termination enabled.

Excessive termination

Check that all devices other than the end devices have termination disabled.

Multiple devices at the same ID

If two or more devices are configured at the same SCSI ID, only one of those devices will be seen by the SNC 5100, and data transfers to that device will be unreliable. Check that only one device is set to each ID.

Target device set to initiator’s ID

If a target device is set to the same ID as the SNC 5100 (ID 7), the bus will be unstable and targets will not be identified. Check that no target devices are set to ID 7, or if one must be set to 7, change the SNC 5100 Initiator ID.

Bent pins in a SCSI connector

The pins in the SCSI connectors are somewhat fragile. Inspect each connector to find pins that were bent when the connector was attached. Replace any cables with bent pins.

Improper device type

A DE device on an SE bus or a n SE devic e on a DE bu s will cause the b us to be unusable.

Improper terminator type

A DE terminator on an SE bus or an SE terminator on a DE bus will cause the bus to be unusable.

28 Other Installation Issues

6-00020-02

SNC 5100

Inadequate cables

Older cables may not be suitable for running at Ultra speeds. Be sure all cables are rated for Ultra.

Mixed cabl e types

If a SCSI bus has both round cables and flat ribbon cables, it may suffer problems when running at Ultra speeds. Use the same cable type consistently for all segments of the SCSI bus.

Unshielded cables

An unshielded SCSI cable used external to a cabinet may cause reliability problems, due to interference from other electrical devices. Use only shielded cables.

Fuses

The SNC 5100 has a 3.15A, 250 VAC, time delay fuse on the AC line input, and the AC harness uses an axial lead, 250 VAC time delay fuse in the neutral line. There are no user-serviceable parts in the SNC 5100.

Host Bus Adapter Setup

Hosts are connected to the SNC 5100 through specific Host Bus Adapters (HBAs). The installation procedure varies slightly, depending on which adapter you will be using. The procedure involves these steps:

Step 1. Install the adapter in the host system, following the manufacturer’s

recommendations.

Step 2. Power on the host system and update the adapter firmware, if

necessary.

Step 3. Boot the operating system and install the device driver for the HBA. Step 4. Reboot and verify that the device driver has started and that

expected target devices are seen by the operating system.

6-00020-02

Other Installation Issues 29

SNC 5100

Step 5. Install optional utility software, if desired. Perform steps 4 and 5 after the SNC 5100 is installed and connected to the host

system.

Installing the SAN Explorer

The SAN Explorer software is only available for hosts running the Windows NT or Windows 2000 operating systems. It allows you to view the LUN mapping through switches to which your SNC 5100 may be attached.

It includes the Host Registration Service. The Host Registration Service provides the SNC 5100 with periodic host status information including the host name, host type and HBA. The default notification period is 15 minutes.

See the readme file on the CD-ROM for installation instructions. For software updates, visit www.adic.com.

Installing the Host Registration Service

The Host Registration Service is available without the SAN Explorer software for host operating systems other than Windows NT or Windows 2000. It provides the SNC 5100 with periodic host status information including the host name, host type and HBA. The default notification period is 15 minutes.

See the readme file on the CD-ROM for installation instructions. For software updates, visit www.adic.com.

Power-Up and Boot Sequence Guidelines

The SNC 5100 scans the SCSI buses after it boots. If you add or remove SCSI devices after the SNC 5100 has booted, it will not detect the changes until you invoke a SCSI rescan or reboot.

Before you turn on or restart the hosts that are connected to the SNC 5100, you must wait until the SNC 5100 has finished booting. You will know that the SNC 5100 has finished booting when the RDY LED on the user panel blinks at intervals of one second.

30 Other Installation Issues

6-00020-02

SNC 5100

Some operating systems provide you with software methods that allow you to add or remove SCSI devices dynamically after the host has booted. To ensure reliable operation, reboot the host.

If you update SNC 5100 firmware you must reboot in order to use the new firmware. To ensure compatibility between the firmware features or functions and the host, reboot the host.

If you update SCSI device firmware, the SAN Explorer application does not display the new firmware version until you rescan the appropriate SCSI Channel on the SNC 5100.

6-00020-02

Other Installation Issues 31

SNC 5100

32 Other Installation Issues

6-00020-02

SNC 5100

Maintenance Action Plans

This section describes the Maintenance Action Plans (MAPs) for the SNC

5100. MAPs exist for all of the SNC 5100’s component systems. If it is clear that a particular component system is at fault in a problem

situation, go directly to the MAP for that component by consulting Table 6. If it is not clear which component system is at fault in a problem situation,

choose one of the following options:

• W ork through the Event Codes and Actions in Table 7 on page 35 in order to determine the appropriate MAP.

• Work through the “Start MAP” on page 42 in order to determine the appropriate MAP.

Table 6: Maintenance Action Plans Troubleshooting Table

Component Subsystem Go To

If Event Code 42 has been reported “Database Full MAP” on page 47 If you are unable to access SCSI or Fibre

devices If SCSI I/O fails or errors on the SCSI bus are

reported If the SAN Connection LED is off or Fibre

Channel errors are reported If the SNC 5100 continually reboots or all

LEDs are off If the temperature W arnin g or Alarm LEDs are on“Temperature MAP” on page 66

If all LEDs are off or the SNC 5100 fails to respond to any method of management

If Client and Server cannot communicate or the Ethernet LED is off

If the Client is communicating with the Server, but the Service Terminal does not respond

“Device Access MAP” on page 48

“SCSI Channel MAP” on page 50

“Fibre Channel MAP” on page 61

“MAP for the SNC 5100” on

page 66

“Power MAP” on page 68

“Ethernet MAP” on page 69

“Service Port MAP” on page 75

6-00020-02

SNC 5100

Event Codes and Actions

Review all visual observations and Event Codes against Table 7 on page 35.

Check Event Log

Step 1. To determine what Events are in the Event Log, follow the

procedures in the ADIC Management Console User Guide.

Step 1. If the ADIC Management Console application is not available,

connect a service terminal to the SNC 5100. For information about how to do this, see “Connecting to the

Service Port” on page 95.

Step 2. Press the Enter key on the service terminal.

If the prompt is not displayed, go to “Service Port MAP” on page 75.

Step 3. Issue the

For more information, see the

loggerDump command from the service terminal.

"loggerDump [number]"

command on page 141. Messages that looks like the ones in Figure 5 display:

Figure 5: Event Log Listing From Service Port

34 Event Codes and Actions

6-00020-02

SNC 5100

Figure 6: Detail of Event Log Listing From Service Port Step 4. Check the listed Event Codes against the Event Code column of

Table 7 on page 35. See Figure 6 to interpret the log listing.

Step 5. Read across Table 7 to the Action column to see the associated

Action number.

Step 6. Find the Action number in the Action column of Table 8 on

page 41.

Step 7. Complete the indicated MAP or action. Step 8. To see additional log messages, follow the procedure “Event Log

Dump” on page 189.

Step 9. If there are no abnormal events, go to “Perform Health Check” on

page 46.

Table 7: Event Codes and Actions

Default

Trap

Threshold

Description

Visual Observations

second after power has been on for one minute

Action

Event

Code

N.A. N.A. N.A. All LEDs are off 5 N.A. N.A. N.A. RDY LED not blinking once per

N.A. N.A. N.A. Temperature Warning LED on 4 N.A. N.A. N.A. Temperature Alarm LED on 4

Viewing

Level

6-00020-02

N.A. N.A. N.A. SNC 5100 not responding 3

Event Codes and Actions 35

SNC 5100

Table 7: Event Codes and Actions

Event

Code

Viewing

Level

Default

Trap

Threshold

Description

N.A. N.A. N.A. Persistent reboots 3 N.A. N.A. N.A. Host application error message or host

log entry indicates SCSI target error N.A. N.A. N.A. Host cannot access attached devices 12 N.A. N.A. N.A. SAN Connection LED off although

2 cables are attached and host systems are on and have booted

N.A. N.A. N.A. Heartbeat failure 7 N.A. N.A. N.A.

fcShow command returns

2, 0

Firmware State = Sync Lost

N.A. N.A. N.A. ADIC Management Console failure 7 N.A. N.A. N.A. Service terminal connection failure 8

Generic Event Descriptions

8 2 0 Sense data recorded follo wing a check

0 condition Caution: Normally, the host system will request and process send data and then perform error recovery

Action

9 1 0 LUN reports a “unit attention”

11 1 1 ADIC Management Console repor ts a

13 1 1 SNC 5100 is shutting down as

14 0 0 Additional status information used for

36 Event Codes and Actions

0 condition on a non-remov ab l e media device

4 temperature change (event message indicates the change to High, Very High, Reduced, to High, or OK

0 requested by the ADIC Management Console (a Restart was requested )

0 diagnostics

6-00020-02

SNC 5100

Table 7: Event Codes and Actions

Event

Code

Viewing

Level

Default

Trap

Threshold

Description

16 1 1 A SCSI bus reports an unexpected

interrupt

17 1 1 Fibre Channel interface reports a LIP

reset was received from a host

18 1 1 Fibre Channel interface reports a

system error

19 1 1 Fibre Channel interface reports an

error processing a request

20 1 1 Fibre Channel interface reports an

error processing a response

21 1 1 SNC 5100 processor memory fault

detected

22 1 10 Fibre Channel interface detected a

LIP

23 2 0 Fibre Channel interface reports a loop up0

Action

0, 2

1, 2, 3

24 2 0 Fibre Channel interface reports a loop

down

25 1 1 SNC 5100 PCI bus parity error

detected

26 1 1 SNC 5100 PCI interface error

detected

27 2 0 A device has been added to a SCSI

bus

28 1 0 A SCSI bus reports a reset has been

detected

29 1 1 SNC 5100 has added a device to its

configuration table Caution: The trap is held off until the SNC 5100 has been up for 60 seconds

30 1 1 SNC 5100 has remov ed a de vi ce from

its configuration

31 2 0 SNC 5100 logging service has started 0

3, 2, 1

0, 1, 2

6-00020-02

Event Codes and Actions 37

SNC 5100

Table 7: Event Codes and Actions

Event

Code

Viewing

Level

1 1 An interface has detected a bus fault

Default

Trap

Threshold

Description

(event message indicates the specific interface)

1 1 An interface has detected a device

fault (event message indicates the specific interface)

35 1 1 A SCSI interface reported an

unexpected disconnect by a device

36 1 1 A parity error was detected on a SCSI

bus

37 2 0 Fibre Channel Port Database change

detected

39 1 1 Directory Server on Fabric has

changed

40 1 1 Maximum LUN limit has been

exceeded

Action

1, 2

41 1 0 Fibre Channel transfer failure

(Caution: error recovery may have succeeded)

42 1 1 Maximum device limit has been

exceeded (persistent Address Map database is full)

43 1 1 Fibre Channel interface driver

reported debug file dump (event log contains further information)

58 1 1 Power has returned to Nominal from

Warning or Alarm Stage

59 1 1 Power has entered Warning Range

from Nominal Range (Power falling) or Alarm Range (Power improving)

60 1 1 Power has entered Alarm Range 5

38 Event Codes and Actions

6-00020-02

SNC 5100

Table 7: Event Codes and Actions

Event

Code

Viewing

Level

1 1 Inlet Air, Outlet Air, or I/O Processor

Default

Trap

Threshold

Description

temperatures have entered Nominal Range from a Warning or Alarm Range

1 1 Inlet Air Temperature has entered

Warning Range from Nominal Range (heating up) or Alarm Range (cooling down)

63 1 1 Inlet Air Temperature has entered

Alarm Range

1 1 Outlet Air Temperature or I/O

Processor Temperature has entered Warning Range from Nominal or Alarm Ranges

65 1 1 Outlet Air Temperature or I/O

Processor Temperature has entered Alarm Range

Action

66 1 1 Fan is operating in Nominal Range

after operating in a fault state

67 1 1 Fan speed has entered W arning Range

(Tachometer fans only)

68 1 1 Fan speed has entered Alarm Range

(Tachometer fans) or is stalled (rotor stall fans)

1 1 Firmware upload completed 0

1 1 SNC 5100 restart completed 0

72 1 1 Maximum number of initiators has

been exceeded

150 1 1 The event log is about to overwrite

the earliest events

Health Check Event Descriptions

100 1 1 Power supply is out of specification 5

6-00020-02

Event Codes and Actions 39

SNC 5100

Table 7: Event Codes and Actions

Default

Trap

Threshold

Description

Action

4, 0

Event

Code

Viewing

Level

102 1 Temperature change detected since

the last report (event message indicates the change to High, Very High, Reduced to High, or OK)

106 1 1 Fibre Channel interface failed Health

2 Check

107 1 1 SCSI interface failed Health Check 1 109 1 1 Target device failed Health Check 1 110 1 1 Fibre Channel link status changed 0, 2 111 1 1 Fibre Channel tr ansfer failures

0 detected since the last report Caution: error recovery may have succeeded

112 1 1 Blower/Fan is running in Warning or

4 Alarm Range

113 1 1 Power is running in Warning or

5 Alarm Range

114 1 1 Temperature is running in Warning or

115 1 1 Network is running at 10 Mb/sec 7

200

201

6,7

202

40 Event Codes and Actions

Alarm Range

Heartbeat Event Descriptions

Caution:

These event codes are not

logged in the Event Log. Notification of these events occurs fr om th e ADIC Management Console. For more information on Heartbeat, see the

ADIC Management Console User Guide.

N.A. N.A. The Server could not verify the

connection to the SNC 5100

N.A. N.A. The Client could not communicate

with the Server

N.A. N.A. The Server could not communicate

with the Client

7,3

7,9

6-00020-02

SNC 5100

Table 7: Event Codes and Actions

Event

Code

6,8

203

Viewing

Level

N.A. N.A. Heartbeat communication restored 0

Default

Trap

Threshold

Description

Action

Notes:

See Table 9 on page 42 .

See Table 8 on page 41 .

Default Trap Threshold settings are explained “Events” in the ADIC Management Console User

Guide.

Check the Event Log to find out which interface (FCAL or SCSI) caused this event. Then use the

appropriate action number.

This trap signals a change in state. A string sent with the tr ap will ind ic ate the natur e o f the previous

state.

Events not logged in SNC 5100 Event Log.

Not Reported. View the Server Log.

Event reported only when ADIC Management Console 2.7 or above is running

Action Reference Table

Numerical references from the Action column in Table 7: Event Codes and Actions are associated with the appropriate MAP in Table 8: Action Reference Table.

Table 8: Action Reference Table

Action

Number Action

0 No action necessary 1Go to “SCSI Channel MAP” on page 50 2Go to “Fibre Channel MAP” on page 61 3Go to “MAP for the SNC 5100” on page 66 4Go to “Temperature MAP” on page 66 5Go to “Power MAP” on page 68

6-00020-02

Event Codes and Actions 41

SNC 5100

Table 8: Action Reference Table

Action

Number Action

7Go to “Ethernet MAP” on page 69 8Go to “Service Port MAP” on page 75 9 Contact your network administrator 10 Reduce the number of target devices attached to the SNC 5100 11 Go to “Start MAP” on page 42 12 Go to “Device Access MAP” on page 48 13 Go to “Retrieving the Code 43 Dump File” on page 189

Event Viewing Levels

Numerical equivalents for the Event viewing levels from the Viewing Level column of Table 8 are explained in Table 9.

Table 9: Event Viewing Levels

Number Level Explanation

0 No tice Events recorded in the Event Log but not displayed by the

Event Viewer

1 Warning Includes events that should always be reported, such as

device removals, and changes to temperature or power systems

2 Information Includes events that might result in later problems

Start MAP

Gather as much information as possible before performing a repair action. When gathering information, you may need to connect the service terminal to the service port. See “Connecting to the Service Port” on page 95.

For the latest information on the SNC 5100, visit

Event Code or Obvious Symptom

www.adic.com.

42 Start MAP

Either an Event Code has been reported by the ADIC Management Console or an error has been observed by other means.

6-00020-02

SNC 5100

For more information on Events, see the ADIC Management Console User Guide.

If the event code is known, go to Table 7, “Event Codes and Actions,” on page 35 with that event code and perform the recommended action.

If the symptom is obvious, go to Table 6, “Maintenance Action Plans Troubleshooting Table,” on page 33.

If the event code or error symptom is not known, go to “Event Codes and Actions” on page 34.

Otherwise, proceed to "Visually Inspect LEDs".

Visually Inspect LEDs

Use this procedure to visually inspect the LEDs. Step 1. Observe front-panel SNC 5100 LED status indicators.

For information about expected LED behavior, see “LED Indicators” on page 14.

If the RDY LED is flashing as expected but the SCSI, Ethernet and SAN Connection LEDs are off, the SNC 5100 may hav e been left in diagnostic mode.

The device drivers for SCSI, Fibre Channel and Ethernet interfaces are disabled when in diagnostic mode.

If the command prompt on the service terminal is return the SNC 5100 to normal mode by entering the

diagmode >,

normalBoot

command on the service terminal. For more information, see “Boot Modes” on page 187.

Step 2. Check LED observation against Table 7, “Event Codes and

Actions,” on page 35. The Visual Observations area at the beginning of the Table

includes several descriptions of situations signalled by LED states.

Step 3. Refer to Table 8, “Action Reference Table ,” on page 41 and

complete the action.

6-00020-02

Start MAP 43

SNC 5100

Step 4. If LED observations did not solve the problem, proceed to "Check

for Problems on Attached Devices".

Check for Problems on Attached Devices

Check the following in order to find problems on attached devices:

• LEDs

• Display panels

• Firmware levels

• Operability

Check Host Versions

Check the following in order to find problems on attached Hosts:

• Operating system version

• Service pack version

• Hot-fix version

• HBA hardware version

• HBA firmware version

• HBA device driver version

If an update is required, perform the update. For an updated list of supported SNC 5100 host platforms and Fibre Channel

Host Bus Adapters, visit www.adic.com.

Check SNC 5100 Product Versions

For an current list of required updates, visit www.adic.com.

ADIC Management Console version

44 Start MAP

Use this procedure to check the version level of the ADIC Management Console application.

6-00020-02

SNC 5100

Step 1. Start the ADIC Management Console Server and Client.

For installation and operating instructions, as well as access to version information, see the ADIC Management Console User Guide.

Step 2. If an update is needed, download the update from www.adic.com,

and perform the update.

Firmware version

Use this procedure to check the firmware version level. Step 1. Connect a service terminal to the SNC 5100.

For information about how to do this, see “Connecting to the Service Port” on page 95.

Step 2. Press the Enter key on the service terminal.

If the prompt is not displayed, go to “Service Port MAP” on page 75.

Step 3. Issue the

showVersions command.

For more information, see the "showVersions" command on page

170.

Step 4. If an update is required, download the update from www.adic.com,

and perform the update.

Hardware version

Use this procedure to check the hardware version information. Step 1. Connect a service terminal to the SNC 5100.

For information about how to do this, see “Connecting to the Service Port” on page 95.

Step 2. Press the Enter key on the service terminal.

If the prompt is not displayed, go to “Service Port MAP” on page 75.

6-00020-02

Start MAP 45

SNC 5100

Step 3. Issue the sysVpdShow command.

For more information, see the

sysVpdShowAll"

command on page 175.

"sysVpdShow or

Step 4. Report this information to your service representative, if you are

asked for it.

Quick Component Check

Use this procedure to check system components: Step 1. Connect a service terminal to the SNC 5100.

For information about how to do this, see “Connecting to the Service Port” on page 95.

Step 2. Press the Enter key on the service terminal.

If the prompt is not displayed, go to “Service Port MAP” on page 75.

Step 3. From the service terminal, enter the

showBox command.

For more information, see the "showBox" command on page 170.

Step 4. If an installed component does not show up i n the display, go to the

correct MAP. For example, if a SCSI interface is missing, go to “"SCSI Channel

MAP"” on page 50. If a Fibre Channel is missing, go to “"Fibre Channel MAP"” on

page 61.

Step 5. If all components display properly, proceed to "Perform Health

Check".

Perform Health Check

Step 1. Stop all I/O. Step 2. Remove the Ethernet cable if installed.

46 Start MAP

6-00020-02

SNC 5100

Step 3. Connect a service terminal to the SNC 5100.

For information about how to do this, see “Connecting to the Service Port” on page 95.

Step 4. Press the Enter key on the service terminal.

If the prompt is not displayed, go to “Service Port MAP” on page 75.

Step 5. From the service terminal, issue the

hlthChkNow command.

For other commands associated with healthchecks, see terms beginning with the

hlthChk prefix in “Service Port Command

Reference” on page 105.

Step 6. Check the results displayed on the service te rminal to det ermine the

status of the interfaces and attached devices. If a failure is indicated, perform the appropriate MAP.

Check the Host Event Log

Check the event log on the Fibre Channel host. Look for the most recent entries and check to see if there are any Fibre Channel HBA driver errors. If there are, go to “Fibre Channel MAP” on page 61.

Database Full MAP

Perform these steps if Event Code 42 is reported. Event Code 42 indicates that the persistent address map database is full.

6-00020-02

There cannot be more than 2048 devices in the database. If devices were moved to different ports or channels, Event Code 42 can be reported, e ven when fe wer than 2048 devices are actually present.

Use the following procedure to free up database entries that are no longer needed, and keep the devices that are currently attached at the same Assigned LUNs.

Caution:

Use this procedure only when you are sure that the devices you are interested in are connected and available to the SNC 5100. Devices

Database Full MAP 47

SNC 5100

that are not currently attached will be removed from the database. You must reboot the SNC 5100 after performing this procedure for the changes to take effect.

Step 1. Connect a service terminal to the SNC 5100.

For information about how to do this, see “Connecting to the Service Port” on page 95.

Step 2. Press the Enter key on the service terminal.

If the prompt is not displayed, go to “Service Port MAP” on page 75.

Step 3. From the service terminal, enter the

mapShowDatabase command

to display the contents of the database. For more information, see “mapShowDatabase” on page 146.

Step 4. From the service terminal, enter the

mapShowDevs command to

display LUN assignments for the attached devices that have been mapped.

For more information, see the

"mapShowDevs" command on page

147.

Step 5. From the service terminal, enter the

mapWinnowDatabase

command to remove LUN assignments for devices that no longer need to be kept.

For more information, see the

"mapWinnowDatabase" command

on page 148.

Step 6. Reboot the SNC 5100. Step 7. After the SNC 5100 has finished booting, repeat steps 3 and 4 to

verify that all attached devices have been mapped.

Device Access MAP

Perform these steps if a host is not able to access SCSI or Fibre Channel devices.

Step 1. Connect a service terminal to the SNC 5100.

48 Device Access MAP

6-00020-02

SNC 5100

For information about how to do this, see “Connecting to the Service Port” on page 95.

Step 2. Press the Enter key on the service terminal.

If the prompt is not displayed, go to “Service Port MAP” on page 75.

Check Fibre Channel Port Status

Step 1. Enter the fcShow command from the service terminal.

For more information, see the "f cShow [level]" command on page 127.

If the

fcShow command does not display a Firmware State of

Ready for the attached Fibre Channel SAN connections, go to

“Fibre Channel MAP” on page 61.

Step 2. If a Fibre Channel host should have access to SCSI Channel

devices, verify that the FC port mode is Target. The SNC 5100 Fibre Channel ports are set by default to Target

mode. If the port mode for the host connection was changed to Initiator, the host will not be able to see the SCSI devices.

For more information on setting Channel modes, see the ADIC Management Console User Guide.

Step 3. If the host should have access to devices on a Fibre Channel, verify

that the FC port mode is set to Initiator or Target and Initiator. If the port mode for the host connection is set to Target, the host

will not be able to see the attached Fibre Channel devices. For more information on setting Channel modes, see the ADIC

Management Console User Guide.

Check SCSI Channel Devices

Enter the scsiShow command from the service terminal.

6-00020-02

For more information, see the "scsiShow" command on page 160.

Device Access MAP 49

SNC 5100

If all of the attached SCSI devices are not displayed, go to “SCSI Channel MAP” on page 50.

Check Channel Zoning Settings

Step 1. Enter the fcShowDevs command from the service terminal.

For more information, see the "fcShowDevs" command on page

129. Look at the display for each Fibre Channel interface. If all of the

SCSI devices are displayed under each Fibre Channel interface, then host access to SCSI devices is not being restricted by Channel Zoning.

Step 2. Use the ADIC Management Console to change Channel Zoning

settings. For information on Channel Zoning, see the ADIC Management

Console User Guide.

SCSI Channel MAP

Perform these steps if:

• Errors are reported on the SCSI bus

• SCSI I/O fails to operate

• Parity errors are detected on the SCSI bus

• SCSI device reports unit attention on non-removable device

• Unexpected SCSI bus reset occurs

• Unexpected SCSI disconnect reported by a SCSI device

Get SCSI Information for the SNC 5100

Step 1. Connect a service terminal to the SNC 5100.

For information about how to do this, see “Connecting to the Service Port” on page 95.

50 SCSI Channel MAP

6-00020-02

SNC 5100

Step 2. Press the Enter key on the service terminal.

If the prompt is not displayed, go to “Service Port MAP” on page 75.

Step 3. If the SNC 5100 is off, then turn it on. Step 4. Verify that the RDY LED is blinking once per second.

As the SNC 5100 is booting, several status messages should be displayed on the service terminal. The last status message is “Done executing startup script”.

If no status messages are displayed, go to “Service Port MAP” on page 75.

Step 5. Enter the

showBox command from the service terminal.

For more information, see the "showBox" command on page 170.

Step 6. Write down the information for each SCSI channel.

Example: SCSI -1 requires Low Voltage Differential cable

Step 7. If the SCSI interfaces are not all displayed, replace the SNC 5100.

Go to “Before Removing or Replacing the Unit” on page 82. Continue through “Replacing the SNC 5100” on page 84. Exit this MAP. If the SCSI interfaces display properly , go to "Check Attached SCSI

Devices from the Service Port".

Check Attached SCSI Devices from the Service Port

6-00020-02

Caution

The SNC 5100 supports up to 2048 LUNs. If more than 2048 LUNs are attached, unreliable behavior will result. The SNC 5100 takes up one LUN (0) as its Command and Control LUN. Therefore, only 2047 LUNs are available to the user.

SCSI Channel MAP 51

SNC 5100

Step 1. Issue the scsiShow command from the service terminal to display

a list of attached SCSI devices. For more information, see the

"scsiShow" command on page 160.

Step 2. For each SCSI channel, make a list of attached devices. Include

SCSI device ID, manufacturer, and device status/flags.

Step 3. Go to "Compare Listed versus Physical Devices".

Compare Listed versus Physical Devices

For each SCSI channel, compare the list of attached devices with the physical devices.

If any of the physical devices are not shown, go to “Check SCSI Bus Termination” on page 53.

If all the physical devices are shown, go to "Compare Listed versus Supported

Devices".

Compare Listed versus Supported Devices

Step 1. Compare the attached devices to the list of supported devices listed. Step 2. If the attached devices are all supported, go to “SCSI Loop Back

Test” on page 58. If any attached devices are not supported, report them to the system

administrator for possible replacement.

Caution

If all other diagnostic procedures fail to isolate a SCSI problem, and there are unsupported SCSI devices attached to the SNC 5100, those devices will need to be removed or replaced.

52 SCSI Channel MAP

6-00020-02

SNC 5100

Check SCSI Bus Termination

Caution

If in this procedure you determine that you need to remove a SCSI cable or terminator, all I/O to the SNC 5100 must be stopped and the SNC 5100 must be turned off.

Step 1. Verify the termination for the end device attached to the channel in

question. The last physical device on a chain of SCSI devices needs to be

terminated. If the end device has internal termination, be sure it is enabled. Otherwise check that an external terminator is attached to the

device. A Differential (DE) terminator on a Single Ended (SE) bus or an SE

terminator on a DE bus will cause the bus to be unusable.

Step 2. Verify the termination for the other devices attached to the channel

in question. Check that all SCSI devices other than the end de vices ha ve internal

termination disabled. A Differential (DE) terminator on a Single Ended (SE) bus or an SE

terminator on a DE bus will cause the bus to be unusable.

Step 3. If there are SCSI termination problems, power down the SNC 5100

down and correct them. If you corrected SCSI termination problems, go to "SCSI Health

Check".

If SCSI termination is OK, go to "Check for Multiple SCSI IDs".

Step 4. If you powered down the SNC 5100 down, turn it back on.

6-00020-02

SCSI Channel MAP 53

SNC 5100

Check for Multiple SCSI IDs

If two or more devices on the same SCSI channel are configured at the same SCSI ID, only one of those devices will be seen by the SNC 5100. Data transfers to that device will be unreliable.

Caution

If in this procedure you determine that you need to correct any SCSI IDs, all I/O to the SNC 5100 must be stopped and the SNC 5100 must be turned off.

Step 1. Enter the

scsiShow command from the service terminal.

For more information, see the "scsiShow" command on page 160.

Step 2. Write down the SCSI IDs of all devices connected to each SCSI

channel.

Step 3. Check that only one device is set to each ID for each SCSI channel.

Assign a new SCSI ID to any conflicting target device.

Step 4. Check that for each SCSI Channel, no devices are set to ID 7 e xcept

the SNC 5100 channel ID. If a target device is set to the same ID as the SNC 5100 (ID 7), the

bus will be unstable and data corruption may result.

Step 5. If you do not need to correct any SCSI IDs, go to "Improper Device

Type".

Step 6. If you corrected any SCSI IDs, reboot the SNC 5100. Step 7. After it finishes booting, enter the

scsiShow command.

Step 8. Compare the list of attached devices with the physical devices.

54 SCSI Channel MAP

For more information, see the "scsiShow" command on page 160.

If not all of the physical devices are sho wn, go to "Improper De vice

Type".

If all of the physical devices are shown, go to "SCSI Hea lth Check".

6-00020-02

SNC 5100

Improper Device Type

Step 1. Check to be sure that all the devices attached to a single SCSI bus

are of the same type. Only low voltage differential devices must be attached to low

voltage differential SCSI channels. When a mix of Ultra2/3 SCSI and Ultra SCSI de vices are connected

to a single bus, the b us will run at the Ultra SCSI speed. Beca use the bus will auto-adjust to the slo west spee d, it is not recommended that you run both Ultra2/3 SCSI and Ultra SCSI devices on the same bus.

Caution

If in this procedure you determine that you need to replace a SCSI device, all I/O to the SNC 5100 must be stopped and it must be turned off.

Step 2. Replace any improper SCSI device with a proper device. Step 3. Reconnect the SCSI cable. Step 4. If you do not have to replace an improper device, go to "Examine

SCSI Cables".

If you replaced any devices, reboot the SNC 5100.

Step 5. After the SNC 5100 finishes booting, enter the scsiShow command

from the service terminal. For more information, see the

"scsiShow" command on page 160.

Step 6. Compare the list of attached devices with the physical devices.

If not all of the physical devices are shown, go to "Examine SCSI

Cables".

If all of the physical devices are sho wn, go to "SCSI Health Check".

6-00020-02

SCSI Channel MAP 55

SNC 5100

Examine SCSI Cables

Caution

If in this procedure you determine that you need to remove a SCSI cable, all I/O to the SNC 5100 must be stopped and the SNC 5100 must be turned off.

Step 1. Look for damaged cables.

Check for breaks in the cable jacket, exposed or frayed cable shield, exposed or broken wires.

Step 2. Replace any damaged cables. Step 3. Look for inadequate cables.

Older SCSI cables may not be suitable for running at Ultra2/3 speeds. Be sure all cables are rated for Ultra2/3.

Step 4. Replace any cables not suitable for running at Ultra 2/3 speeds. Step 5. Check for mixed cable types.

If a SCSI bus has both round cables and flat ribbon cables, it may suffer problems when running at Ultra2/3 speeds.

Use the same cable type consistently for all segments of the SCSI bus.

Step 6. Replace any cables that are of the wrong type. Step 7. Check for unshielded cables.

An unshielded SCSI cable used external to a cabinet may cause reliability problems, due to interference from other electrical devices.

Step 8. Replace all unshielded cables.

If no cables are replaced, go to "Examine SCSI Connectors". If cables were replaced, go to "SCSI Health Check".

56 SCSI Channel MAP

6-00020-02

SNC 5100

Examine SCSI Connectors

Caution

Before removing a SCSI cable, all I/O to the SNC 5100 must be stopped and the SNC 5100 must be turned off.

Step 1. Inspect each connector to find out if pins were bent when the

connector was attache

Step 2. Replace any cables that have bent pins. Step 3. If you did not have to replace or re-secure a SCSI cable, go to

"SCSI Loop Back Test".

Step 4. If you replaced or re-secured a SCSI cable, turn on the SNC 5100.

Step 5. After it finishes booting, enter the

scsiShow command from the

service terminal. For more information, see the

"scsiShow" command on page 160.

Step 6. Compare the list of attached devices with the physical devices.

If not all of the physical devices are shown, go to "SCSI Loop Back

Test".

If all of the physical devices are sho wn, go to "SCSI Health Check".

SCSI Health Check

Step 1. Perform a Health Check.

For more information, see “Perform Health Check” on page 46.

Step 2. Check the Event Log for SCSI errors.

For more information, see “Check the Host Event Log” on page 47.

Step 3. Perform a component check.

6-00020-02

For more information, see“Quick Component Check” on page 46.

Step 4. If errors are still indicated, go to "SCSI Loop Back Test".

If no errors are reported, exit this MAP.

SCSI Channel MAP 57

SNC 5100

SCSI Loop Back Test

Caution

Before performing diagnostics, all FC and SCSI cables must be disconnected from the SNC 5100. Before changing any SCSI cables, all I/O to the SNC 5100 must be stopped and the SNC 5100 must be turned off. Do not perform SCSI loop back tests on SCSI channels that are attached to SCSI target devices. If you do this, you will corrupt the data on the device.

Step 1. If the SNC 5100’s command prompt on the terminal is not

diagmode >, enter the diagBoot command on the servi ce terminal

For more information, see “Entering Diagnostic Mode” on page 187.

Step 2. Power down the SNC 5100. Step 3. In addition to the suspect SCSI channel, choose one of the other

SCSI channels to use for the loop back test.

Step 4. Label and remove those cables. Step 5. Connect a short SCSI loopback test cable to those two SCSI

channels.

Step 6. Power on the system. Step 7. Wait for the SNC 5100 to finish booting. Step 8. Enter the scsiChannelTest(1,2) command. The following

example shows a loop back test on SCSI channels 1 and 2.

Example: diagmode > scsiChannelTest (1,2) SCSI-1 -> SCSI-2 [##########] 10 iterations PASSED SCSI-2 -> SCSI-1 [##########] 10 iterations PASSED value=0=0x0

Step 9. If the SNC 5100 returns a PASSED status, go to "Testing SCSI

Cables".

58 SCSI Channel MAP

6-00020-02

SNC 5100

Testing SCSI Cables

If the cables of the devices attached to a channel have a compatible pinout on both sides, the SNC 5100 can test the cable using the loop back test.

Step 1. Stop all I/O to the SNC 5100. Step 2. If the SNC 5100’s command prompt on the terminal is not

diagmode > place the SNC 5100 in diagnostic mode

For more information, see “Entering Diagnostic Mode” on page 187.

Step 3. Shut down the SNC 5100. Step 4. Remove the cable from one attached SCSI device, and attach it as a

loop back cable to the SNC 5100.

Step 5. Power on the SNC 5100. Step 6. After the SNC 5100 has finished booting, enter the

scsiChannelTest(x,y) command from the service terminal

(where ‘ cable) to perform a loop back test.

x’ and ‘y’ are the slot numbers connected by the loopback

For an example, see “SCSI Loop Back Test” on page 58, Step 8.

Step 7. If the SNC 5100 returns a FAILED status, the cable is faulty and

must be replaced. If the SNC 5100 returns a PASSED status, go to "Isolating SCSI

devices" to isolate bad devices on the SCSI bus.

Isolating SCSI devices

Step 1. Restore the SNC 5100 to normal operation.

See “Restoring Normal Mode” on page 188.

Step 2. Power down the SNC 5100. Step 3. Perform Steps 4 - 11 for each SCSI device that was found missing

in Step 1 under “Compare Listed versus Physical Devices” on page 52.

6-00020-02

SCSI Channel MAP 59

SNC 5100

Step 4. Remove all devices from the SCSI buses. Step 5. Attach ONLY the device in question to the SCSI channel it was

originally connected to using a known-good SCSI cable and terminators.

Step 6. Power the SNC 5100 back on. Wait for it to finish booting. Step 7. Enter the

scsiShow command from the se rvice termi nal and v eri fy

the device’s presence. For more information, see the

"scsiShow" command on page 160.

Step 8. If the device is missing from the display, it needs to be replaced

and/or serviced. Inform the system administrator of any suspected bad devices

found in this step. Replace or remove any bad devices.

Step 9. If the device is present, perform a health check.

For more information, see “Perform Health Check” on page 46.

Step 10. Review the host event log.

For more information, see “Check the Host Event Log” on page 47.

Step 11. If SCSI errors are found, then inform the system administrator that

the connected device appears to be bad.

Step 12. After all possible device checks are performed go to "Restore SCSI

Restore SCSI Setup

Step 1. Shut down the SNC 5100. Step 2. Reconnect all available SCSI devices to their proper channel

60 SCSI Channel MAP

Replace or remove any bad devices.

Setup".

assignments. Use the original configuration, except where changes have been

made per this MAP.

6-00020-02

SNC 5100

Step 3. Wait for the SNC 5100 to finish booting. Step 4. If the SNC 5100 is in diagnostic mode (command prompt =

diagmode >), then restore normal operation.

For more information, see “Restoring Normal Mode” on page 188.

Step 5. Perform a health check.

For more information, see “Perform Health Check” on page 46.

Step 6. Review the host event log.

For more information, see “Check the Host Event Log” on page 47. If all attached SCSI devices and cables are determined to be good,

yet SCSI errors persist, replace the SNC 5100. Go to “Before Removing or Replacing the Unit” on page 82. Proceed through “Replacing the SNC 5100” on page 84. Exit this MAP.

Fibre Channel MAP

Perform these steps if:

• The Fibre Channel interface reports a reset or system error

• The Fibre Channel interface reports an error processing a request or

response

• The Fibre Channel interface reports an excess of 10 LIPs in a 10-minute interval

• Other Fibre Channel errors reported

• FC connection LED is off

Verify Fibre Channel Connections

Step 1. Connect the service terminal to the Service Port.

6-00020-02

For more information, see “Connecting to the Service Port” on page 95.

Fibre Channel MAP 6 1

SNC 5100

Step 2. Press the Enter key on the service terminal.

If the prompt is not displayed, go to “Service Port MAP” on page 75.

Step 3. From the service terminal, enter the

For more information, see the

showBox command.

"showBox" command on page 170.

Step 4. Confirm that the Fibre Channel connections are correctly displayed.

showBox displays the Fibre Channel connections correctly, go to

"Examine Cables".

Step 5. If the Fibre Channel connections do not display correctly in the

showBox display, remove the GBIC and replace it with a

known-good GBIC. Go to “Removing the GBIC” on page 82. Proceed through “Replacing the GBIC” on page 82.

Step 6. Proceed to "Test GBIC".

Test GBIC

Caution

You must stop I/O at the Fibre Channel host.

Step 1. With a known-good GBIC installed, confirm that the SNC 5100’s

Step 2. If the output of the showBox command matches the Fibre Channel

62 Fibre Channel MAP

Fibre Channel connections are correctly displayed by issuing the

showBox command from the service terminal.

For more information, see the "showBox" command on page 170.

configuration, exit this MAP. If the output of the

showBox command, still does not match the

Fibre Channel configuration, remove the known-good GBIC and reinstall the original GBIC.

Go to "Examine Cables".

6-00020-02

SNC 5100

Examine Cables

Caution

If in this procedure, you need to remove or replace the Fibre Channel cable, you must stop I/O at the Fibre Channel host.

Step 1. Remove the cables. Step 2. If any cables are obviously damaged, replace them. Step 3. Use dusting spray/compressed gas to dust off optical connectors on

the GBIC and cable ends.

Step 4. Reconnect the cables. Step 5. Perform Health Check.

For more information, see “Perform Health Check” on page 46.

Step 6. View the event log at viewing level 3.

For more information, see Table 9, “Event Viewing Levels,” on page 42.

Step 7. If errors are gone, exit this MAP.

If errors persist, go to "Fibre Channel Loop Back Test".

Fibre Channel Loop Back Test

Caution

Before performing diagnostics, the Fibre Channel cables must be removed from the SNC 5100. All I/O to the SNC 5100 must be stopped.

Step 1. Attach a Fibre Channel loop back plug to the Fibre Channel port. Step 2. If the front-panel FC Connection Status LED is not on, replace the

SNC 5100. For more information, see Figure 4 on page 14. Go to “Before Removing or Replacing the Unit” on page 82.

6-00020-02

Continue through “Replacing the SNC 5100” on page 84.

Fibre Channel MAP 6 3

SNC 5100

Exit this MAP. If the front-panel FC Connection Status LED is on, proceed to S tep

Step 3. If the SNC 5100’s command prompt on the service terminal is not

diagmode >, place the SNC 5100 in diagnostic mode.

For more information, see “Entering Diagnostic Mode” on page 187.

Step 4. Substituting the Fibre Channel slot number for

fcSlotTest x command.

For more information, see "fcSlotTest [x]" command on page

192.

Step 5. If the test failed, replace the SNC 5100.

Go to “Before Removing or Replacing the Unit” on page 82. Continue through “Replacing the SNC 5100” on page 84. Exit this MAP. If the test passed, the Fibre Channel port is good.

Step 6. Remove the loop back plug.

Go to "Testing Fibre Channel Optical Cable".

Testing Fibre Channel Optical Cable

Caution

x, enter the

Step 1. If the cables are already removed, reattach them.

Step 2. Substituting the Fibre Channel slot number for x, from the service

64 Fibre Channel MAP

If the Fibre Channel cable is extremely long it may be more practical to replace the Fibre Channel device first; then if the problem is not resolved, replace the cable.

Attach matching cable ends (red-to-red or ‘A’-to-’A’ and so on) to both slots of the Fibre Channel port.

terminal enter the

fcSlotTest x command.

6-00020-02

SNC 5100

For more information, see "fcSlotTest [x]" command on page

192.

Step 3. If the test passes, the Fibre Channel optical cable is good.

Go to "Replace Fibre Channel Device". If the test fails, go to "Replace Fibre Channel Cable".

Replace Fibre Channel Cable

Step 1. Replace the cables to the Fibre Channel ports with known good

cables.

Step 2. Perform Health Check.

For more information, see “Perform Health Check” on page 46.

Step 3. View the event log at viewing level 3.

For more information, see Table 9, “Event Viewing Levels,” on page 42.

Step 4. If problems persist, inform the network administrator that there

seems to be a problem with a device or a host bus adapter. If problems are gone, exit this MAP.

Step 5. Replace external devices that are attached to the Fibre Channel

ports. Go to "Replace Fibre Channel Device".

Replace Fibre Channel Device

The device that needs to be replaced is one of the following:

• Fibre Channel HBA

• Fibre Channel Switch

• Fibre Channel Hub

6-00020-02

Fibre Channel MAP 6 5

SNC 5100

Step 1. Inform the system administrator that it is necessary to replace the

Fibre Channel device connected to the SNC 5100 to resolve the Fibre Channel errors.

Step 2. Repeat this MAP, beginning with the section “Verify Fibre Channel

Connections” on page 61, after replacing the external component.

MAP for the SNC 5100

Perform these steps if:

• RDY LED not blinking once per second after power has been on for one minute

• The SNC 5100 is not responding

• SNC 5100 processor memory fault detected

• SNC 5100 PCI bus parity error detected

• SNC 5100 PCI interface error detected

• The ADIC Management Console Server could not verify the connection

to the SNC 5100

Observe Operational LED Behavior

When the SNC 5100 is first powered on, the front-panel’s LEDs flash a variety of patterns as it performs the Power On Self Test (POST) and then starts booting.

For more information, see “POST Error Codes” on page 197. Within one minute, the SNC 5100 should have booted successfully and the

Ready LED should be blinking once per second. If the Ready LED is not blinking as expected, go to “Start MAP” on page 42.

Temperature MAP

Perform these steps if:

• The SNC 5100 generates Trap Event Codes 62, 64, or 67 (Inlet Air , Outlet Air, I/O Processor, or Fan have entered a Warning Range)

66 MAP for the SNC 5100

6-00020-02

SNC 5100

• The SNC 5100 generates Trap Event Codes 63, 65, or 68 (Inlet Air, Outlet Air, I/O Processor, or Fan have entered Alarm Range)

• Health Check generates Trap Event Code 112 or 114 (Fan or Power are running in Warning or Alarm Range)

Notification of Problems in Temperature Subsystem

System operators are normally notified of problems or potential problems in SNC 5100 subsystems by the event traps that appear in the “Received Event Trap” window of the ADIC Management Console client.

For more information, see the ADIC Management Console User Guide. However, when sensors detect a Warning or Alarm condition in the

Temperature subsystem, not only are Trap Event Codes 62, 63, 64, or 65 generated, but a pop-up dialog box immediately alerts the user.

See the

"envMonShow" command on page 118 for operational temperature

ranges that will generate these messages. If the temperature problems are due to a reduction in blower functionality,

Event Codes 62, 63, 64, or 65 will be accompanied by Event Codes 67 or 68. See the

"envMonRangeShow" command on page 119 for conditions that will

generate these messages.

Temperature Warnings or Alarms Received

Step 1. Verify that room temperature is within satisfactory limits. Step 2. If room temperature is not within satisfactory limits, adjust it. Step 3. If the room temperature is within satisfactory limits, and alarm or

warning messages are being generated, check the air intake for obstructions.

Caution

The Inlet Air sensor is at the end with the plastic bezel and the on/off switch. The Outlet Air sensor is the end with the connectors.

6-00020-02

Temperature MAP 67

SNC 5100

Step 4. If obstructions are found, remove them and permit the SNC 5100 to

cool.

Step 5. If temperatures stabilize, exit this MAP. Step 6. If no obstructions are found, or temperatures do not stabilize, check

the SNC 5100’s Air Outlet for obstructions.

Step 7. If obstructions are found, remove them and permit the SNC 5100 to

cool.

Step 8. If temperatures stabilize, exit this MAP. Step 9. If no obstructions are found, or temperatures do not stabilize,

replace the unit. Proceed to “Before Removing or Replacing the Unit” on page 82. Continue through “Replacing the SNC 5100” on page 84.

Fan Speed is in Warning or Alarm Range

If you were directed to this MAP because of Trap Event Code 67, indicating that the Fan is in Warning Range--replace the SNC 5100 at the next scheduled maintenance.

If you were directed to this MAP because of Trap Event Code 68, indicating that the Fan is in Alarm Range , Proceed to “Before Removi ng or Replacing the Unit” on page 82.

Continue through “Replacing the SNC 5100” on page 84.

Power MAP

Perform these steps if:

• All LEDs are off

• The SNC 5100 generates Trap Event Codes 59 or 60, indicating that the

Power is running in the Warning or Alarm Range. A string accompanying a Trap Event will indicate which power supply is specifically involved.

68 Power MAP

• Health Check generates a Trap Event Code 113, indicating that Power is running in Warning or Alarm Range

6-00020-02

SNC 5100

Step 1. Verify that the SNC 5100 is plugged into an active AC power

source.

Step 2. Verify the status of the SNC 5100 Power LED.

For more information, go to Figure 4 on page 14.

Step 3. If the Power LED remains off, try a different power cord. Step 4. If the Power LED remains off, remove the SNC 5100.

Proceed to “Before Removing or Replacing the Unit” on page 82. Continue through “Replacing the SNC 5100” on page 84.

Ethernet MAP

The network administrator must provide the following information before you can perform this MAP:

• The IP address for the SNC 5100 - REQUIRED

• The net mask for the SNC 5100 in decimal and hex formats - REQUIRED

• The network gateway IP address for the SNC 5100 - if assigned

• The IP address of a computer on the same subnet as the SNC 5100 for

PING tests - REQUIRED

• The IP address of the ADIC Management Console Server - REQUIRED. For more information, see the ADIC Management Console User Guide.

Step 1. The SNC 5100 must be booted and its Ethernet Port must be

attached to the local area network. For the position of the Ethernet port on the SNC 5100, see Figure 7.

6-00020-02

Figure 7: Ethernet Port on Faceplate

Ethernet MAP 69

SNC 5100

Step 2. Verify that the Ethernet Link LED, which is the green LED on the

left, is on.

Step 3. If the LED is on, go to step 4.

If the LED is not on, proceed to “Before Removing or Replacing the Unit” on page 82.

Continue through “Replacing the SNC 5100” on page 84. Exit this MAP.

Step 4. Determine the speed of the network, by following the procedure in

“Perform Health Check” on page 46. If the Health Check generates a Trap Event Code of 115, then the

SNC 5100’s yellow Speed LED should be on. Verify that the yellow Speed LED, which is the yellow LED on the

right, correctly reflects the speed of the network.

Step 5. If the yellow Speed LED correctly reflects the speed of the

network, go to Step 7. If the yellow Speed LED does not correctly reflect the speed of the

network, go to Step 6.

Step 6. Inform the System Administrator that there may be a problem with

the Ethernet cable quality, the intermediate link speeds or interconnect speeds.

If the System Administrator can find no problems with the Ethernet cable quality, the intermediate link speeds, or interconnect speeds, but the SNC 5100 yellow Speed LED does correctly reflect the network speed, go to “Before Removing or Replacing the Unit” on page 82.

Continue through “Replacing the SNC 5100” on page 84. Exit this MAP.

Step 7. Remove the Ethernet cable from the SNC 5100 Ethernet Port and

attach the Ethernet loop back plug.

Step 8. Verify that the Ethernet LEDs are functioning correctly.

70 Ethernet MAP

If they are, proceed to Step 9.

6-00020-02

SNC 5100

If they are not, inform the system administrator that there is a network hardware problem where the SNC 5100 is attached.

Exit this MAP.

Step 9. Remove the Ethernet loop back plug. Step 10. Obtain another Ethernet cable. Step 11. Use this cable to attach the SNC 5100 to the local area network. Step 12. Connect the service terminal to the Service Port.

For more information, see “Connecting to the Service Port” on page 95.

Step 13. Press the Enter key on the service terminal.

If the prompt is not displayed, go to “Service Port MAP” on page 75.

Step 14. From the service terminal, enter the

For more information, see the "ifShow" command on page 139.

Example:

SN60023 > ifShow ibmEmac (unit number 0):

Flags: (0x8063) UP BROADCAST MULTICAST ARP RUNNING Type: ETHERNET_CSMACD Internet address: 172.16.76.211 Broadcast address: 172.16.255.255 Netmask 0xffff0000 Subnetmask 0xffff0000 Ethernet address is 00:60:45:17:02:f0 Metric is 0 Maximum Transfer Unit size is 1500 114192 packets received; 364 packets sent 114023 multicast packets received 116 multicast packets sent 0 input errors; 0 output errors 0 collisions; 0 dropped

ifShow command.

6-00020-02

Ethernet MAP 71

SNC 5100

lo (unit number 0):

Flags: (0x8069) UP LOOPBACK MULTICAST ARP RUNNING Type: SOFTWARE_LOOPBACK Internet address: 127.0.0.1 Netmask 0xff000000 Subnetmask 0xff000000 Metric is 0 Maximum Transfer Unit size is 32768 0 packets received; 0 packets sent 0 multicast packets received 0 multicast packets sent 0 input errors; 0 output errors 0 collisions; 0 dropped

value = 29 = 0x1d

Step 15. If there is no entry for ibmEmac, replace the SNC 5100.

Go to “Before Removing or Replacing the Unit” on page 82. Continue through “Replacing the SNC 5100” on page 84. Exit this MAP. If there is an entry for ibmEmac, write down the values of the:

- internet address,

- netmask,

- subnetmask

Step 16. Verify that the internet address is the same as the IP address

supplied by the network administrator.

Step 17. Verify that the netmask value is the same as the netmask in hex

format supplied by the network administrator.

Step 18. Verify that the subnetmask is the same as the netmask. If these

values are correct, go to step 21. If these values are not correct, proceed to Step 19.

Step 19. Use the ethAddrSet command to set the correct IP address and

netmask values.

72 Ethernet MAP

For more information, see the

121.

"ethAddrSet" command on page

6-00020-02

SNC 5100

Step 20. From the service terminal, enter the reboot command and wait for

the SNC 5100 to finish booting. Go back to step 14.

Step 21. Enter the command

IP address> <host IP address > is the address provided by the network

ping “<host IP address> ”, where <host

is four decimal numbers separated by periods.

administrator for PING testing. Display of successful PING test:

Example: SN60023 > ping “192.168.1.1”,10 PING 192.168.1.1: 56 data bytes 64 bytes from 192.168.1.1: icmp_seq=0. time=0. ms 64 bytes from 192.168.1.1: icmp_seq=0. time=0. ms 64 bytes from 192.168.1.1: icmp_seq=0. time=0. ms 64 bytes from 192.168.1.1: icmp_seq=0. time=0. ms 64 bytes from 192.168.1.1: icmp_seq=0. time=0. ms 64 bytes from 192.168.1.1: icmp_seq=0. time=0. ms 64 bytes from 192.168.1.1: icmp_seq=0. time=0. ms 64 bytes from 192.168.1.1: icmp_seq=0. time=0. ms 64 bytes from 192.168.1.1: icmp_seq=0. time=0. ms 64 bytes from 192.168.1.1: icmp_seq=0. time=0. ms

----192.168.1.1 PING Statistics---10 packets transmitted, 10 packets received, 0% packet loss round-trip (ms) min/avg/max = 0/0/0 value=0=0x0

6-00020-02

Display of failed PING test:

Example: SN60023 > ping “192.168.1.251”,10 PING 192.168.1.251: 56 data bytes request timed out value = -1 = 0xfffffff

Step 22. If the PING test passes, go to step 23.

If the PING test fails, inform t he system admi nistrator that there is a network hardware problem where the SNC 5100 is attached.

Exit this MAP.

Ethernet MAP 73

SNC 5100

Step 23. Remove the Ethernet cable from the SNC 5100 and install the

Ethernet loop back plug.

Step 24. From the service terminal, enter the

diagBoot command.

For more information, see “Entering Diagnostic Mode” on page 187.

Step 25. Wait for the SNC 5100 to finish booting. Step 26. Verify that the Step 27. From the service port, enter the

Example: diagmode > elTest ==== Testing Ethernet ==== Init complete. Ethernet OK value=0=0x0

diagmode> prompt is displayed.

elTest command.

Step 28. If the test fails, replace the SNC 5100.

Go to “Before Removing or Replacing the Unit” on page 82. Continue through “Replacing the SNC 5100” on page 84. Exit this MAP. If the test passes, remove the Ethernet loop back plug. Proceed to Step 29.

Step 29. From the service terminal, enter the

normalBoot command and

wait for the SNC 5100 to finish booting.

Step 30. Reattach the Ethernet cable to the SNC 5100. Step 31. From the service terminal, enter the

gateAddrGet command and

write down the network gateway address that is displayed. For more information, see the

"gateAddrGet" command on page

131.

Step 32. Compare this address to the one provided by the network

administrator.

74 Ethernet MAP

6-00020-02

SNC 5100

If both addresses are the same, go to step 33.

Example: SN60023 > gateAddrGet Gateway Address set to 192.168.1.1 value=0=0x0

If the network gateway address is incorrect, set it to the value provided by the network administrator using the command.

gateAddrSet

For more information, see the

"gateAddrSet" command on page

131.

Step 33. From the service terminal, enter the

reboot command.

Step 34. Wait until the SNC 5100 has finished booting. Step 35. From the service terminal, use the ping command to PING the IP

address of the ADIC Management Console Server. For more information, see the ADIC Management Console User

Guide.

Step 36. From the host running the ADIC Management Console Server,

PING the SNC 5100. If both PING tests succeed, exit this MAP. If a PING test fails, inform the network administrator to check and

correct the network connection, route tables, and network gateway addresses for both the ADIC Management Console Server and the SNC 5100.

6-00020-02

Service Port MAP

These steps are performed if the SNC 5100 boots and responds to the ADIC Management Console, but the Service Port does not respond.

For more information, see the ADIC Management Console User Guide.

Service Port MAP 7 5

SNC 5100

Check the RS-232 Cable

This test requires another laptop or desktop computer with a functioning RS-232 9-pin port. Terminal emulation software must be installed and running.

Step 1. Remove the RS-232 null-modem cable from the service port. Step 2. Connect it to the compatible port on the other computer. Step 3. Connect the service terminal to the cable. Step 4. Set the service terminal and the other computer to 19200 baud, 8

data bits, no parity, one stop, Xon/Xoff flow control.

Step 5. Enter test lines in the service terminal and the other computer. Step 6. Confirm that they are displayed on each other.

If this fails, replace the RS-232 cable. If this succeeds, remove the cable from the other computer Go to "Check Connection with Boot Messages".

Check Connection with Boot Messages

Step 1. Reconnect the terminal to the SNC 5100 with the RS-232 null

modem cable.

Step 2. Stop all I/O to the SNC 5100. Step 3. Shut down the SNC 5100 and keep the power off for 5 seconds. Step 4. Turn the SNC 5100 on.

If boot messages fail to appear on the service terminal, then replace the SNC 5100.

Go to “Before Removing or Replacing the Unit” on page 82. Proceed through “Replacing the SNC 5100” on page 84.

Step 5. Reboot the SCSI host.

76 Service Port MAP

If devices are still unavailable, proceed to "SCSI Channel MAP".

6-00020-02

SNC 5100

Virtual Private SAN®Scalar Firewall Manager Settings MAP

Perform these steps if SFM devices are unavailable.

Check Scalar Firewall Manager Access Settings

Step 1. Connect the service terminal to the Service Port.

For more information, see “Connecting to the Service Port” on page 95.

Step 2. Press the Enter key on the service terminal.

If the prompt is not displayed, go to “Service Port MAP” on page 75.

Step 3. Enter the

sfmShow -1 command from the service terminal.

For more information, see the "sfmShow [hostIndex]" command on page 168

Step 4. If SFM State: Inactive is displayed, Scalar Firewall Manageris not

controlling access between the host and target devices. Proceed to Step 5.

If SFM State: Active is displayed, Scalar Firewall Manager®is controlling access between the host and the target devices. Proceed to Step 8.

Step 5. Enter the

sfmFeatureEnable command from the service

terminal. For more information, see the or the

“license key string”"

command on page 166.

"sfmFeatureEnable

If SFM devices are available, exit this MAP. If SFM devices are not available, proceed to Step 6.

Step 6. Enter the

licenseShow command from the service terminal.

6-00020-02

Virtual Private SAN®Scalar Firewall Manager Settings MAP 77

SNC 5100

For more information, see the "licenseShow" command on page

141.

Example: License "s2zhq-7xdhd": Valid

Features: SFM

Value=2=0x2

Step 7. If the output from the licenseShow command shows that SFM is

Valid, as in the example, proceed to Step 8. If the output from the

licenseShow command shows that SFM is

not Valid, exit this MAP and contact your service representative.

Step 8. Use the ADIC Management Console to verify the host and target

device access settings. For more information, see the ADIC Management Console User

Guide. Exit this MAP. If the ADIC Management Console is not available, you can

temporarily make SFM inacti ve to veri fy that the host can access all devices. Proceed to "Verify Host Access to Devices".

Verify Host Access to Devices

Step 1. Shut down all of the hosts. Step 2. Enter the

For more information, see the page 167.

sfmInactive Set command from the service terminal.

"sfmInactiveSet" command on

Step 3. Startup one of the hosts. Step 4. If the host can access all of the target devices, shut down the host

and repeat steps 2 and 3 for each of the other hosts. If each host can access all devices then there is a problem with the

Scalar Firewall Manager Access settings. Go to step 5.

78 Virtual Private SAN®Scalar Firewall Manager Settings MAP

6-00020-02

SNC 5100

If the host cannot access all of the target devices, then there is a problem with the devices or their SAN connections. Proceed to“Device Access MAP” on page 48 or “Fibre Channel MAP” on page 61.

Step 5. Shut down all of the hosts. Step 6. Enter the

sfmActiveSet command from the service terminal.

For more information, see the "sfmActiveSet" command on page

165.

Step 7. Use the ADIC Management Console to verify the host and target

device access settings. For more information, see the ADIC Management Console User

Guide.

6-00020-02

Virtual Private SAN®Scalar Firewall Manager Settings MAP 79

SNC 5100

80 Virtual Private SAN®Scalar Firewall Manager Settings MAP

6-00020-02

SNC 5100

Removal and Replacement Procedures

This section describes the removal and replacement procedures for the SNC 5100 in its entirety or for one or more of its GBICs.

Handling Electrostatic Discharge-Sensitive Parts

Caution

It is highly recommended that you follow industry best practice when handling Electrostatic Discharge (ESD) Sensitive Parts.

• Keep the ESD-sensitive part in a static-protective bag until you are ready to install the part into the machine.

• Make the fewest possible movements with your body to prevent an increase of static electricity from clothing, fibers, carpets, and furniture.

• If instructed to do so, switch off the machine power before you remove ESD-sensitive parts.

• Just before touching the ESD-sensitive part, discharge to the machine any static electricity in your body by touching the metal frame or cover of the machine. If possible, keep one hand on the frame when you install or remove an ESD-sensitive part.

• You may opt to wear an ESD wrist strap.

• Do not place any ESD-sensitive parts on the machine cover or on a metal

table because large metal objects can become discharge paths if they are not grounded. If you must set aside an ESD-sensitive part, first place it into the ESD static-protective bag.

• Prevent ESD-sensitive parts from being accidentally touched by other personnel.

• If possible, keep all ESD-sensitive parts in a grounded metal case.

• Be very careful when you work with ESD-sensitive parts in cold weather.

Low humidity and heating increase static electricity.

6-00020-02

Handling Electrostatic Discharge-Sensitive Parts 81

SNC 5100

Removing an d Repl acing the GBIC

Caution

Shut down the host systems to ensure that all I/O through the SNC 5100 has stopped.

Removing the GBIC

Caution

You must stop I/O at the Fibre Channel host. Step 1. Review “Handling Electrostatic Discharge-Sensitive Parts” on

page 81.

Step 2. Unplug the Fibre Channel cable. Step 3. Slide the GBIC out of the slot. Step 4. Place the GBIC in a static-protective bag.

Replacing the GBIC

Caution

You must stop I/O at the Fibre Channel host. Step 1. Review “Handling Electrostatic Discharge-Sensitive Parts” on

page 81.

Step 2. Insert the known good GBIC into the slot. Step 3. Remove the dust caps from a known good GBIC. Step 4. Plug the Fibre Channel cables back in, being sure to use the correct

polarity.

Step 5. If you were sent here by another MAP, return to it.

Before Removin g or Replacin g the Unit

These steps are performed if a repair action is required for any component of the SNC 5100, except for a GBIC.

82 Removing and Replacing the GBIC

6-00020-02

SNC 5100

Caution

Shut down the host systems to ensure that all I/O through the SNC 5100 has stopped.

Step 1. Verify that the latest configuration has been saved.

For more information on saving the configuration, see the ADIC Management Console User Guide.

Step 2. Shut the SNC 5100 down and disconnect the power cord. Step 3. For each cable attached to the SNC 5100, repeat the following:

- Remove the cable.

- Mark what the cable was connected to (for example, SNC 5100 number 3, SCSI channel 1).

- If the final cable has been removed, then return to the MAP that sent you here, or continue with "Removing and Replacing the Unit".

Removing an d Repl acing the Unit

Caution

Follow all ESD-sensitive parts procedures while performing this procedure. For ESD information, see “Handling Electrostatic Discharge-Sensitive Parts” on page 81.

This procedure describes how to remove and replace the SNC 5100.

Removing the SNC 5100

Step 1. Complete all steps in “Before Removing or Replacing the Unit” on

page 82.

Step 2. After the final cable has been removed, pop off the plastic

rack-mount bezel, if installed on your unit. Pull it straight out to detach it.

Step 3. Unscrew the four 4-40 x 3/8" screws that hold the units to the rack

bracket.

6-00020-02

Removing and Replacing t he Unit 83

SNC 5100

Step 4. Remove the rack bracket from across the width of the 19" rack by

unscrewing the two 10-32 x 5/8" screws.

Step 5. Slide the unit out of the rack.

Replacing the SNC 5100

Step 1. Remove the SNC 5100 from the protective bag.

Install the new SNC 5100 in the rack.

Step 2. Plug the power cable in. Step 3. Complete the "Final Diagnostic Tests".

Final Diagnostic Tests

After the unit has been replaced, a complete diagnostic check must be performed to ensure that no new problems have been introduced.

For further information about the procedures and commands used in this section, see “Connecting to the Service Port” on page 95 and “Diagnostic Command Reference” on page 187.

Final Test Preparation

Step 1. Connect a service terminal to the SNC 5100.

For information about how to do this, see “Connecting to the Service Port” on page 95.

Step 2. Reattach the power cord to the SNC 5100. Step 3. Turn on the SNC 5100 and wait until it finishes booting. Step 4. Press the Enter key on the service terminal.

If the prompt is not displayed, go to “Service Port MAP” on page 75.

Step 5. From the Service Terminal, enter the

diagBoot command.

Step 6. Wait until the SNC 5100 has finished booting into diagnostic mode.

84 Final Diagnostic Tests

6-00020-02

SNC 5100

Step 7. From the Service Terminal, enter the showBox command.

For more information, see the

"showBox" command on page 194.

Step 8. Verify that the SNC 5100 accurately displays the channel

information.

showBox display is accurate, go to step 9.

If the If not, go to “Start MAP” on page 42.

Step 9. Proceed to "Fibre Channel Tests"

Fibre Channel Tests

For further information about the procedures and commands used in this section, see “Connecting to the Service Port” on page 95 and “Diagnostic Command Reference” on page 187.

Test Fibre Channel Port 1

Step 1. Attach the Fibre Channel loop back plug to the GBIC in FC 1. Step 2. From the service terminal, enter the fcSlotTest 1 command.

For more information, see the "f cSlotTest [x]" command on page 192.

Step 3. If the test passes, remove the loop back plug and go to "Test Fibre

Channel Port 2".

If the test does not pass, go to “Start MAP” on page 42.

Test Fibre Channel Port 2

Step 1. Attach the Fibre Channel loop back plug to the GBIC in FC 2. Step 2. From the service terminal, enter the fcSlotTest 2 command.

For more information, see the "f cSlotTest [x]" command on page 192.

6-00020-02

Final Diagnostic Tests 85

SNC 5100

Step 3. If the test passes, remove the loop back plug and go to "Test SCSI

Port 1 and 2".

If the test does not pass, go to “Start MAP” on page 42.

Test SCSI Port 1 and 2

Step 1. Attach the appropriate VHDCI cable between SCSI 1 and 2. Step 2. From the service terminal, enter the scsiChannelTest 1,2

command. For more information, see the "scsiChannelTest (x,y)"

command on page 193.

Step 3. If the test passes, remove the loop back cable and go to "Test SCSI

Port 1 and 2".

If the test does not pass, go to “Start MAP” on page 42.

Test SCSI Port 3 and 4

Step 1. Attach the appropriate VHDCI loop back cable between SCSI 3

and SCSI 4.

Step 2. From the service terminal, enter the

scsiChannelTest 3,4

command. For more information, see the "scsiChannelTest (x,y)"

command on page 193.

Step 3. If the test passes, remove the loop back cable and go to "Ethernet

Test".

If the test does not pass, go to “Start MAP” on page 42.

Ethernet Test

For further information about the procedures and commands used in this section, see “Connecting to the Service Port” on page 95 and “Diagnostic Command Reference” on page 187.

86 Final Diagnostic Tests

6-00020-02

SNC 5100

Step 1. If you did not replace the SNC 5100, go to Step 3. Step 2. Obtain the SNC 5100’s Ethernet network parameters.

Configure the Ethernet Port Host Name, Address, Routes, Enable Ethernet.

For more information, see "Network Setup for the SNC 5100".

Step 3. Attach the Ethernet loop back plug to the Ethernet port. Step 4. From the service terminal, enter the

elTest command.

For more information, see the "elTest" command on page 192.

Step 5. If the test passes, go to Step 6.

If the test does not pass, go to See “Start MAP” on page 42.

Step 6. Remove the Ethernet loop back plug. Step 7. Proceed to "Updating the SNC 5100".

Network Setup for the SNC 5100

The SNC 5100 must be connected to a 10/100-base-T Ethernet network for use with the ADIC Management Console software.

For more information, see the ADIC Management Console User Guide. An RJ-45 connector is located on the rear panel of the SNC 5100 for

connection to the Ethernet. See Figure 8.

6-00020-02

You will need to connect a terminal or terminal emulator to the Service Port of the SNC 5100 in order to configure the IP address.

Network Setup for the SNC 5100 87

SNC 5100

Figure 8 Ethernet Port Step 1. To configure the network, connect to the SNC 5100 Service Port.

For more information, see “Connecting to the Service Port” on page 95.

In all of the subsequent steps, substitute the values you determined in Step 6 of Table 2, “Pre-Installation Checklist,” on page 19.

Step 2. Enter the

hostNameSet command to set the Host name.

For more information, see the "hostNameSet" command on page

138. In the example shown, the host name of the SNC 5100 was

“SN60023” and is now being set to “foster.” The shell prompt will change to reflect the new name.

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

Step 3. Use the ethAddrSet command to set the host network address:

For more information, see the "ethAddrSet" command on page

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

periods.

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

88 Network Setup for the SNC 5100

6-00020-02

SNC 5100

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

Example: foster > ethAddrSet “10.0.0.2”, “255.0.0.0”

If you need a network route and/or default gateway, you must specify it.

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

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

Specify the address of the gateway that is reachable on the local subnet.

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

Step 4. Optionally, add User account for Telnet

If you want to access the SNC 5100’s command line interface through its Ethernet port using a Telnet session, you need to add a user account.

The user name you specify must be 3 or more characters. The password you specify must be 8 or more characters.

For more information, see the commands beginning with the “Service Port Command Reference” on page 105.

Example: foster > userAdd “username”,”password” value=0=0x0 foster >

Step 5. Enter the reboot command to reboot the SNC 5100:

For more information, see the

Example: foster > reboot

"ethAddrSet" command on page 121.

user in

6-00020-02

Network Setup for the SNC 5100 89

SNC 5100

Updating the SNC 5100

Step 1. From the service terminal, enter the normalBoot command.

For more information, see the

"normalBoot" command on page

191.

Step 2. Wait until the SNC 5100 has finished booting. Step 3. From the service terminal, enter the

version command.

For more information, see the "version" command on page 185.

Step 4. Write down the operating software version number. Step 5. Determine whether the SNC 5100’s firmware version requires an

update. If an update is required, download the new file or files and the

associated readme. You will install the new firmware as you complete the "Post-Repair

Checklist".

Step 6. If you replaced the SNC 5100, enter the ridTag command and type

the identifier.

Caution

You must perform this step if you replaced the SNC 5100.

Step 7. Shut down the SNC 5100. Step 8. Unplug the power cord. Step 9. Disconnect the RS-232 cable from the SNC 5100. Step 10. Proceed to "Post-Repair Checklist".

90 Updating the SNC 5100

For more information, see the page 152.

"ridtag [“value”]" command on

6-00020-02

SNC 5100

Post-Repair Checklist

It is important that the items in this checklist are verified after you have completed a repair action. This ensures a successful reinstall of the product.

Table 4-1: Post-Repair Checklist

Step Actions Comments and References

4 5

Reinstall the SNC 5100 in its original location.

Ensure that the FC hosts are turned off. if not, disconnect the FC cables now.

Attach the Service Terminal to the SNC 5100

Turn on the SNC 5100. None. Wait for the SNC 5100

to finish booting.

From the service terminal, enter the

targets command.

See “Replacing the SNC 5100” on page 84

If you cannot turn off the FC hosts you must disconnec t the FC hosts befo re turning on th e SNC

5100. This is a safety precaution that ensures that FC hosts cannot perform any I/O to the SCSI tar g et devices prior to res torin g the S NC 5100 configuration in step 8, below.

None.

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

If not, go to “Start MAP” on page 42. See “Service Po rt Comma nd Refe rence” on page 105.

If all attached SCSI devices are not shown, go to “Start MAP” on page 42.

6-00020-02

If you replaced the SNC

5100, configure the network parameters.

Obtain the network parameters.

Post-Repair Checklist 91

SNC 5100

Table 4-1: Post-Repair Checklist

Step Actions Comments and References

Perform the following:

• Start the ADIC Management Console Server and Client.

• Log on with administrator privileges.

• Connect to the SNC

5100.

• If you downloaded new operating software in Step 5 of “Updating the SNC 5100” on page 90, update the firmware.

• Load the configuration file you saved in Step 1 of “Before Removing or Replacing the Unit” on page 82 into the SNC 5100.

• Restart the SNC

5100.

This step must be performed if you replaced the SNC 5100

For more information, see the ADIC Management Console User Guide.

92 Post-Repair Checklist

Reconnect the FC cables or, if you turned off the FC hosts, turn them back on.

If FC1 and/or FC2 Connection Status LEDs for the attached hosts are not on, check the FC cables.

You may have to change the polarity of the FC cables. If the problem persists, go to “Start MAP” on page 42.

6-00020-02

ADIC Scalar 1000, SNC 5100 User Manual

Specifications and Main Features

Frequently Asked Questions

User Manual

Notices

Welcome

Safety Notices

Safety Inspection

Remove AC Power

External Machine Check

Safety Label Check

Fusing Requirements

Environmental Notices and Statements

Product Recycling

Lithium Battery

Laser Safety

General Restrictions

Usage Restrictions

Regulatory Notices

Electronic Emission Statements

Federal Communications Commissi on (FCC) Statement

Industry Canada Compliance Statement

European Community Compliance Statement

VCCI Notice (Japan Only)

BSMI Notice

EN 55022 Compliance (Czech Republic Only)

CE Notice

Documentation

Introduction

Overview

Configuration Support

Address Mapping

Interface Protocol Awareness

Hardware Product Description and Features

Fibre Channel Interfaces

Ultra2 SCSI I/O Interfaces

SCSI Command Support

Ethernet

Service Port

LED Indicators

FC 1-2

SCSI 1-4

Supported Platforms

Supported Devices

Operating Specifications

Operating Environment

Power Consumption

Power Requirements

Install the SNC 5100

Pre-installation Procedure

Installation Procedure

Host Utility Software

Post-Installation

Other Installation Issues

Attaching SCSI Devices

Maximum Number of LUNs

Transfer Rates: Ultra, Fast, and Asynchronous

Wide and Narrow SCSI Buses

Table of SCSI Terminology and Limitations

SCSI Bus Termination

Problems on the SCSI Bus

Missing terminator at the end of a SCSI bus

Excessive termination

Multiple devices at the same ID

Target device set to initiator’s ID

Bent pins in a SCSI connector

Improper device type

Improper terminator type

Inadequate cables

Mixed cabl e types

Unshielded cables

Fuses

Host Bus Adapter Setup

Installing the SAN Explorer

Installing the Host Registration Service

Power-Up and Boot Sequence Guidelines

Maintenance Action Plans

Event Codes and Actions

Check Event Log

Action Reference Table