Quantum SNC 4000 User Manual

Download

ADIC SNC

4000 User’s Guide

ADVANCED DIGITAL INFORMATION CORPORATION

www.adic.co



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

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

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

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

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

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

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

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

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

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

ADIC USA Tel.: +1 303-705-3900 Fax: +1-303-792-2465 ATAC: 1-800-827-3822 http://www.adic.com

ADIC Europe ZAC des Basses Auges 1, rue Alfred de Vigny 78112 Fourqueux, France Tel.: +33.1.3087.5300

ADIC Germany Beteiligungs GmbH, KG

Eschenstraße 3 D-89558

Böhmenkirch, Germany

Tel:+00.800.9999.3822

Fax: +33.1.3087.5301

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

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

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

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

Contents

1 SNC 4000 Introduction 1

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

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

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

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

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

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

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

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

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

2 Description 5

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

3 Getting Started 11

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

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

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

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

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

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

SNC 4000 User’s Guide iii

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

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

4 Scalar Firewall Manager 19

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

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

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

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

5 Connecting to the Service Port 23

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

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

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

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

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

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

6 Removal and Replacement Procedures 27

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

A Maintenance Action Plans 35

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

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

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

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

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

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

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

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

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

iv Contents

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

B Service Port Command Reference 63

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

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

SNC 4000 User’s Guide v

C Diagnostic Command Reference 135

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

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

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

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

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

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

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

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

D POST Error Codes 143

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

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

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

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

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

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

E Startup Message Reference 149

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

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

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

F Warranty and EULA 151

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

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

G Acronyms 155

vi Contents

SNC 4000 Introduction

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

Intended Audience

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

Document Organization

The section topics in this guide include:

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

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

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

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

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

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

4000.

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

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

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

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

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

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

SNC 4000 User’s Guide 1

Associated Documents

The following documents are associated with this guide:

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

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

Explanation of Symbols and Notes

The following symbols and highlighted passages note important information:

Symbol Damage to ... Signal Word Definition Consequence

Person WARNING: Imminent

hazardous electrical situation

Material CAUTION: Potential damaging

situation

NOTE: Indicates important

information that helps make better use of the system

Death or serious injury

Possible damage to the product, data, or environment

No hazardous or damaging consequences

Environmental Notices and Statements

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

Product Recycling

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

Lithium Battery

WARNING

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

C, INCINERATE, OR

Laser Safety

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

Usage Restrictions

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

2 SNC 4000 Introduction

Technical Assistance

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

In the USA: 800.827.3822

Outside the USA, toll free: 00.800.9999.3822

Internet: www.adic.com

SNC 4000 User’s Guide 3

4 SNC 4000 Introduction

Description

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

Overview

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

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

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

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

• Serverless backup via an integrated Data Mover Module.

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

SNC 4000 User’s Guide 5

Figure 1 Configuration Overview

Configuration Support

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

Address Mapping

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

Interface Protocol Awareness

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

FC Interface

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

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

Replacing the SFP on page 27.

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

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

• Target

6 Description

• Initiator

• Target and Initiator

The FC Interface also supports the following connection options:

• Loop

• Point-to-Point

• Loop Preferred

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

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

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

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

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

• Fibre Channel protocol SCSI (FCP-SCSI)

• Fibre Channel internet protocol (IP)

• Fibre Channel virtual interface (FC-VI)

SCSI I/O Interfaces

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

The SCSI interfaces are compliant with the following SCSI specifications:

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

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

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

Ethernet

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

Service Port

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

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

The service port is configured at:

• VT100 or ANSIW terminal emulation

• 19,200 Baud

SNC 4000 User’s Guide 7

• 8 data bits

• No parity

• One stop-bit

• Hardware Flow Control or Xon/Xoff

LED Indicators

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

Figure 2 LEDs

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

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

143.

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

S1 and S2

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

PWR

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

RDY

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

on page

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

ERR

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

Codes on page 143.

8 Description

Firmware 4.40 Features

This chapter describes the functionality of the Storage Networking Controller (SNC) Firmware 4.40. The SNC interface between storage and host provides Fibre Channel to SCSI connectivity.

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

Features highlighted with this release are described below.

Multi-path Mapping

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

WWN Change Capability

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

DHCP

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

Supported Platforms

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

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

scalar24.

Supported Devices

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

Operating Specifications

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

SNC 4000 User’s Guide 9

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

24.

The external dimensions are:

•3” high

• 7” deep

• 6” wide

• weight: 2.19 lbs.

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

Operating Environment

The operating environment is as follows:

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

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

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

Power Consumption

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

ADIC Management Console

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

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

• Customizable graphical view of ADIC libraries

• Policy based event logging and email notification

• Device-level diagnostics, reporting, and configuration

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

Management Console User’s Guide.

10 Description

Getting Started

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

• Unpacking and Inspecting

• Pre-installation

• Installation

• Post-installation

Unpacking and Inspecting

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

• One SFP

• Product documentation and software CD-ROM

• Two HD68/VHDCI SCSI cables

• One LVD terminator

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

Pre-Installation

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

Required Tools Required Software Other Resources

RS-232 straight through cable ADIC Management Console

server/client software

RJ-45 patch cable SNC firmware System with HyperTerminal

SC/LC fibre cables Server to run ADIC

SNC 4000 User’s Guide 11

IP information for the SNC

Management Console

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

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

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

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

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

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

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

6 Ensure that all necessary FC cables are present.

Note

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

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

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

Static IP address____________

Netmask _________

User-defined SNC name __________________

Default Gateway _____________________

CAUTION

Note

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

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

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

hostNameSet

on page 89.

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

be managed from the ADIC Management Console.

Installation

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

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

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

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

12 Getting Started

Figure 3 Cover Plate Removal

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

SNC 4000 User’s Guide 13

Figure 4 SNC Installation

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

terminal.

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

• VT100 or ANSW terminal emulation

• 19,200 Baud

• 8 data bits

• No parity

• One stop-bit

• Hardware Flow Control or Xon/Xoff

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

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

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

14 Getting Started

Figure 5 SCSI Cabling for Two Drives

8 Turn on the Scalar 24.

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

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

ethAddrSet "ip_address","subnet_mask"

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

ethAddrSet “172.16.32.12”,“172.16.1.1

Then enter:

gateAddrSet "default_gateway_ip"

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

Then enter:

hostNameSet "name"

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

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

to the procedures below to set the date and time.

”

Setting the Time and Date

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

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

takes the following arguments:

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

For example:

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

on page 63.

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

SNC4000 > dateSetFromRTC value = 0 = 0x0

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

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

SNC 4000 User’s Guide 15

4 Use the date command to confirm.

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

CAUTION

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

Adding a Host System Running Timeserver

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

1 To enable the timeserver functionality use the setNettime command.

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

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

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

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

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

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

Standard Time.

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

on page 63.

5 To confirm, use the date command.

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

Synchronizing the Real Time Clock with the Timeserver

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

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

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

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

SNC4000 > rtcSetCurrent

value = 0 = 0x0

on page 63.

Disabling the Timeserver Host

Follow the step below to disable a timeserver host.

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

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

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

16 Getting Started

Post Installation

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

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

channel.

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

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

Speed

Connection Options

Loop ID: Soft / Hard and specific ID

Port Mode Target or Target & Initiator

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

CAUTION

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

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

Configuration Files

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

information, see Updating Firmware

1Gbps or 2Gbps

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

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

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

Configuration Files

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

Saving a Configuration File

Follow the procedure below to save your configuration.

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

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

SNC 4000 User’s Guide 17

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

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

Browse button and navigate to it.

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

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

terminal indicating successful completion.

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

Loading a Configuration File

Follow the steps below to load a saved configuration file.

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

2 From the HyperTerminal window select Transfer and Send File.

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

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

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

terminal indicating successful completion.

5 Reboot the SNC for the update to take effect.

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

Updating Firmware

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

18 Getting Started

Scalar Firewall Manager

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

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

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

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

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

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

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

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

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

SNC 4000 User’s Guide 19

Host Registration Service

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

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

Note

CAUTION

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

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

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

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

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

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

Installing the Host Registration Service

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

1 Insert the SNC software CD into the host.

2 Browse to the client software directory.

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

for installing the package.

4 Install the package.

5 Reboot the server.

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

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

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

www.adic.com

20 Scalar Firewall Manager

Note

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

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

Adding a Host to the SAN Configuration

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

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

Attaching a New Host to the SAN

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

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

1 Connect the host to the SAN.

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

20.

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

ADIC Management Console User’s Guide.

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

Guide.

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

host.

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

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

on page 17.

on page

Adding a Host Before Attaching it to the SAN

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

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

Removing a Host from the SAN Configuration

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

User’s Guide.

ADIC Management Console

SNC 4000 User’s Guide 21

Combining SFM with Channel Zoning

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

22 Scalar Firewall Manager

Connecting to the Service Port

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

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

Note

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

Service Port Connections

The figure below shows the service port connections.

Figure 6 Service Port Pinout

Connections are listed in the following table.

Table 1 DB-9 RS-232 Connector Pin Assignments

Pin Number

Signal Name Abbreviation

Direction relative to SNC 4000

1 Carrier Detect CD In

2 Transmit Data TD Out

3 Receive Data RD In

4 Data Terminal Ready DTR Out

5 Signal Ground SG -

SNC 4000 User’s Guide 23

Table 1 DB-9 RS-232 Connector Pin Assignments

6 Data Set Ready DSR In

7 Clear to Send CTS In

8 Request to Send RTS Out

9 Ring Indicator RI In

Connecting the Service Terminal

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

Hardware Required

• RS-232 DB9F straight through cable

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

Connecting using HyperTerminal

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

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

(COM) port to the SNC service port.

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

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

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

chosen and click OK.

In the COM Properties dialog box select the following:

• Bits per second:19200

• Data bits:8

• Parity:None

• Stop bits:1

• Flow Control: Hardware or Xon/Xoff

5 Click OK.

Connecting using Telnet

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

24 Connecting to the Service Port

CAUTION

Before users can obtain remote access to the SNC, there are several configuration steps that must be performed.

Modifications made to the SNC while using Telnet are permanent. There is no Cancel key to back out of changes.

Create User Accounts for Telnet Access

Telnet user accounts are separate from those created in the AMC. Each SNC maintains its own list of user accounts and passwords. To create a user, establish a serial connection to the SNC and enter the following command:

addUser "xxxx","yyyy"

where xxxx is the user name and yyyy is the password.

Create additional users as necessary.

Unlock the Shell

The SNC uses a command called shellLock to prevent Telnet access to the SNC. This command is used to guarantee that an administrator can always access the SNC through the serial port and perform diagnostic/troubleshooting tasks. shellLock was implemented because VxWorks (the underlying OS of the SNC and most SAN devices) only allows one command line session at time. Allowing only a single diagnostic connection (telnet or serial) is beneficial because it prevents administrators from making simultaneous changes which might destabilize the device. Since only one user can access the command line at a time, it is possible for a Telnet user to open a session and lock out all other administrators. The only way to clear this lock is through a reboot of the SNC.

Note

To prevent a Telnet user from locking the command line shell, make a command line connection to the SNC and enter:

shellLock 1

To unlock the shell enter:

shellLock 0

Even when the shell is locked, the ADIC Management Console will be able to manage the SNC.

Using Telnet

When opening a Telnet connection to the SNC, the following must be true:

• A valid user account and password must exist

• shellLock is set to 0

• No other administrator is accessing the SNC through Telnet

To open a session to the SNC, start telnet and enter open x.x.x.x where x.x.x.x is the IP address of the SNC. Alternatively you could just type telnet x.x.x.x.

Once a session is opened the connection will remain locked until the telnet session is closed or the SNC is rebooted.

SNC 4000 User’s Guide 25

CAUTION

Once a telnet session is open, no other users may administer the SNC from the command line. This includes both telnet and serial port connections. This is a function of the VxWorks operating system to prevent simultaneous updates by multiple users.

Note

Even when the shell is locked, the ADIC Management Console will be able to manage the SNC

Verifying the Connection

If the SNC is already on, characters typed in the terminal should be visible to the operator. The simplest test is to press Enter. The SNC responds by displaying a command prompt:

SNC4000 >

When the SNC is rebooting, several messages are displayed on the service terminal. A successful boot is indicated by the last message: Done executing startup script.

26 Connecting to the Service Port

Removal and Replacement Procedures

This section describes the removal and replacement procedures for the SNC in its entirety or for its SFP.

Handling Electrostatic Discharge-Sensitive Parts

When handling the SFP, it is highly recommended that you follow the guidelines below:

• 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.

• 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 ESDsensitive 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.

Removing and Replacing the SFP

Follow the procedures below to remove and replace the SFP.

CAUTION

SNC 4000 User’s Guide 27

Before performing these procedures, shutdown the host systems to ensure that all I/O through the SNC has stopped.

Removing the SFP

1 Unplug the FC cable.

2 Slide the SFP out of the slot.

3 Place the SFP in a static-protective bag.

Replacing the SFP

1 Insert the known good SFP into the slot.

2 Remove the dust caps from a known good SFP.

3 Plug the FC cables back in, being sure to use the correct polarity.

4 If you were sent here by another MAP, return to it.

Before Removing or Replacing the SNC

These steps are performed if a repair action is required for any component of the SNC, except for a SFP.

CAUTION

1 Verify that the latest configuration has been saved. For more information on saving the configuration,

see Saving a Configuration File

2 Shutdown the Scalar 24 and disconnect the power cord.

3 For each cable attached to the SNC, repeat the following:

• Remove the cable.

• Mark what the cable was connected to (for example, SNC number 3, SCSI channel 1).

• If the final cable has been removed, then return to the MAP that sent you here.

Shut down the host systems to ensure that all I/O through the SNC has stopped.

on page 17 or the ADIC Management Console User’s Guide.

Removing and Replacing the SNC

This procedure describes how to remove and replace the SNC.

CAUTION

Follow all ESD-sensitive parts procedures while performing this procedure. For ESD information, see Handling Electrostatic Discharge-Sensitive Parts on page 27

Removing the SNC

1 Complete all steps in Before Removing or Replacing the SNC on page 28.

2 Loosen the four thumbscrews on the back of the SNC.

3 Slide the SNC out of the Scalar 24.

Replacing the SNC

1 Remove the SNC from the protective bag.

28 Removal and Replacement Procedures

2 Install the new SNC in the Scalar 24.For more information, see Installation on page 12.

3 Complete the Final Diagnostic Tests

on page 29.

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 23 and Diagnostic Command Reference on page 135.

Final Test Preparation

1 Connect a service terminal to the SNC. For information about how to do this, see Connecting to the

Service Port on page 23.

2 Turn on the Scalar 24 and wait until the SNC finishes booting.

3 Press the Enter key on the service terminal.

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

4 From the Service Terminal, enter the diagBoot command.

5 Wait until the SNC has finished booting into diagnostic mode.

6 From the Service Terminal, enter the showBox command.

on page 60.

7 Verify that the SNC accurately displays the channel information.If the showBox display is accurate, go

to Fibre Channel Tests

on page 29. If not, go to Start MAP on page 42.

Fibre Channel Tests

For further information about the procedures and commands used in this section, see Connecting to the

Service Port on page 23 and Diagnostic Command Reference on page 135.

Test Fibre Channel Port

1 Attach the FC loop back plug to the FC in FC 1.

2 From the service terminal, enter the fcSlotTest 1 command. For more information, see the

fcSlotTest [x]

3 If the test passes, remove the loop back plug and go to Test SCSI Port 1 and 2

does not pass, go to Start MAP

Test SCSI Port 1 and 2

1 Attach the appropriate VHDCI cable between SCSI 1 and 2.

2 From the service terminal, enter the scsiChannelTest 1,2 command. For more information, see

the scsiChannelTest (x,y)

on page 138.

on page 29. If the test

on page 42.

on page 139.

3 If the test passes, remove the loop back cable and go to Ethernet Test

pass, go to Start MAP

SNC 4000 User’s Guide 29

on page 42.

on page 30. If the test does not

Ethernet Test

For further information about the procedures and commands used in this section, see Connecting to the

Service Port on page 23 and Diagnostic Command Reference on page 135.

1 If you did not replace the SNC, go to Step 4

2 Obtain the SNC’s Ethernet network parameters.

3 Configure the Ethernet port host name, address, routes, enable Ethernet. For more information, see

Network Setup for the SNC

4 Attach the Ethernet loop back plug to the Ethernet port.

5 From the service terminal, enter the elTest command.

6 If the test passes, go to Step 7

7 Remove the Ethernet loop back plug.

8 Proceed to Updating the SNC

on page 30.

. If the test does not pass, go to Start MAP on page 42.

on page 31.

Network Setup for the SNC

The SNC must be connected to a 10/100-base-T Ethernet network for use with the ADIC Management Console software. An RJ-45 connector is located on the rear panel of the SNC for connection to the Ethernet. See Ethernet port of the SNC in order to configure the IP address. For more information, see the ADIC Management Console User’s Guide.

Figure 7 Ethernet Port

on page 7. You will need to connect a terminal or terminal emulator to the service

1 To configure the network, connect to the SNC service port. For more information, see Connecting to the

Service Port on page 23.

In all of the subsequent steps, substitute the values you configured during installation. For more information on the commands used in this procedure, see Commands Listed Alphabetically by Function on page 63.

2 Enter the hostNameSet command to set the host name.

30 Removal and Replacement Procedures

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

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

3 Use the ethAddrSet command to set the host network address. The IP address is specified as four

decimal numbers, separated by periods.

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

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

foster > ethAddrSet "10.0.0.2", "255.0.0.0"

If you need a network route and/or default gateway, you must specify it.

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.

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

4 Optionally, add User account for Telnet

If you want to access the SNC’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 three or more characters. The password you specify must be eight or more characters.

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

5 Enter the reboot command to reboot the SNC:

foster > reboot

Updating the SNC

Follow the steps below to update the SNC. For more information on the commands used in this procedure, see Commands Listed Alphabetically by Function

1 From the service terminal, enter the normalBoot command.

2 Wait until the SNC has finished booting.

3 From the service terminal, enter the version command.

4 Write down the operating software version number.

5 Determine whether the SNC’s firmware version requires an update.

on page 63.

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

6 If you replaced the SNC, enter the ridTag command and type the identifier.

SNC 4000 User’s Guide 31

on page 32.

CAUTION

7 Shutdown the Scalar 24 and unplug the power cord.

8 Disconnect the RS-232 cable from the SNC.

You must perform this step if you replaced the SNC.

9 Proceed to the Post-Repair Checklist

on page 32.

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 2 Post-Repair Checklist

Step Actions Comments and References

1 Reinstall the SNC in its original

location.

2 Ensure that the FC hosts are

turned off. If not, disconnect the FC cable now.

3 Attach the service terminal to the

SNC

4 Turn on the Scalar 24. None.

See Replacing the SNC

If you cannot turn off the FC hosts you must disconnect the FC hosts before turning on the SNC. This is a safety precaution that ensures that FC hosts cannot perform any I/O to the SCSI target devices prior to restoring the SNC configuration in

Step 8

, below.

None.

on page 28.

5 Wait for the SNC to finish

booting.

6 From the service terminal, enter

the targets command.

7 If you replaced the SNC,

configure the network parameters.

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

If not, go to Start MAP

See Service Port Command Reference

63. If all attached SCSI devices are not shown, go to

Start MAP

Obtain the network parameters.

on page 42.

on page

32 Removal and Replacement Procedures

Table 2 Post-Repair Checklist

Step Actions Comments and References

8 Perform the following:

• Start the ADIC Management Console Server and Client.

• Log on with administrator privileges.

• Connect to the SNC.

• If you downloaded new operating software in Step 5

Updating the SNC

on page 31,

update the firmware.

• Load the configuration file you saved in Step 1

of Before

Removing or Replacing the SNC on page 28 into the SNC.

• Restart the SNC.

9 Reconnect the FC cable or, if

you turned off the FC hosts, turn them back on.

10 From the service terminal, enter

the fcShow command to show the status of each FC interface that is installed and connected.

From the service terminal, enter the fcShowDevs command to show the SCSI target devices that are connected as seen by the FC interface.

This step must be performed if you replaced the SNC.

For more information, see the ADIC Management Console User’s Guide.

If the FC LED for the attached host is not on, check the FC cable.

You may have to change the polarity of the FC cable. If the problem persists, go to Start MAP

page 42.

In the output of the fcShow command, look for the Firmware State column.

If the word Ready does not appear, go to Fibre

Channel MAP on page 52.

Check to see that all SCSI target devices are seen by the FC interface.

If not, go to SCSI Channel MAP

on page 46.

11 Verify that all (or the designated)

target devices are available to

If the designated devices are NOT available, reboot the host and check again.

the host systems.

If the problem persists, go to Start MAP

on page

42.

12 Disconnect the RS-232 cable

None. from the SNC and the service terminal.

13 End of repair.

SNC 4000 User’s Guide 33

34 Removal and Replacement Procedures

Maintenance Action Plans

This section describes the maintenance action plans (MAPs) for the SNC. MAPs exist for all of the SNC’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 3 at fault in a problem situation, choose one of the following options:

. If it is not clear which component system is

• Work through the event codes and Actions in Event Codes and Actions determine the appropriate MAP.

• Work through the Database Full MAP

Table 3 Maintenance Action Plans Troubleshooting Table

Component Subsystem Go To

If event code 42 has been reported Database Full MAP

If you are unable to access SCSI or fibre devices Device Access MAP

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

If the SAN connection LED is off or FC errors are reported

If the SNC continually reboots or all LEDs are off MAP for the SNC

If the temperature warning or alarm LEDs are on Temperature MAP

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

If client and server cannot communicate or the Ethernet LED is off

on page 45 in order to determine the appropriate MAP.

SCSI Channel MAP

Fibre Channel MAP

Power MAP

Ethernet MAP

on page 56

on page 35 in order to

on page 45

on page 46

on page 52

on page 55

If the client is communicating with the server, but the service terminal does not respond

Service Port MAP

on page 60

Event Codes and Actions

Review all visual observations and event codes against Event Codes and Actions on page 35.

SNC 4000 User’s Guide 35

Check Event Log

Follow this procedure to check the event log. For more information on the commands used in this procedure, see Commands Listed Alphabetically by Function

1 To determine what events are in the event log, follow the procedures in the ADIC Management Console

User’s Guide.

2 If the ADIC Management Console application is not available, connect a service terminal to the SNC.

For information about how to do this, see Connecting to the Service Port

3 Press Enter on the service terminal.

on page 63.

on page 23.

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

5 Issue the loggerDump command from the service terminal.

An output similar to the following will be displayed:

SNC4000> loggerDump *** Dumping 1535 (1 through 1535) of 1535 records *** SEQUENCE TIME CODE DESCRIPTION 0160 10248 day(s) 13:32:29 14 Debug 0: sntEnt:LU Comm Error:k/ c/q=0b/08/88 0161 10248 day(s) 13:32:32 14 Debug 0: sntEnt:LU Comm Error:k/ c/q=0b/08/88 0162 10248 day(s) 13:32:35 14 Debug 0: sntEnt:LU Comm Error:k/ c/q=0b/08/88 0163 10248 day(s) 13:32:43 14 Debug 0: sntEnt:LU Comm Error:k/ c/q=0b/08/88 0164 10248 day(s) 13:32:46 14 Debug 0: sntEnt:LU Comm Error:k/ c/q=0b/08/88 0165 10248 day(s) 13:32:49 14 Debug 0: sntEnt:LU Comm Error:k/ c/q=0b/08/88 0166 10248 day(s) 13:32:52 14 Debug 0: sntEnt:LU Comm Error:k/ c/q=0b/08/88 0167 10248 day(s) 13:32:55 14 Debug 0: sntEnt:LU Comm Error:k/ c/q=0b/08/88 0168 10248 day(s) 13:32:58 14 Debug 0: sntEnt:LU Comm Error:k/ c/q=0b/08/88 0169 10248 day(s) 13:33:01 14 Debug 0: sntEnt:LU Comm Error:k/ c/q=0b/08/88 0170 10248 day(s) 13:33:04 14 Debug 0: sntEnt:LU Comm Error:k/ c/q=0b/08/88 0171 10248 day(s) 13:33:07 14 Debug 0: sntEnt:LU Comm Error:k/ c/q=0b/08/88 0172 10248 day(s) 13:33:15 14 Debug 0: sntEnt:LU Comm Error:k/ c/q=0b/08/88 0173 10248 day(s) 13:33:18 14 Debug 0: sntEnt:LU Comm Error:k/ c/q=0b/08/88 0174 10248 day(s) 13:33:21 14 Debug 0: sntEnt:LU Comm Error:k/ c/q=0b/08/88 0175 10248 day(s) 13:33:24 14 Debug 0: sntEnt:LU Comm Error:k/ c/q=0b/08/88 0176 10248 day(s) 13:33:27 14 Debug 0: sntEnt:LU Comm Error:k/ c/q=0b/08/88 0177 10248 day(s) 13:33:30 14 Debug 0: sntEnt:LU Comm Error:k/ c/q=0b/08/88 0178 10248 day(s) 13:33:33 14 Debug 0: sntEnt:LU Comm Error:k/ c/q=0b/08/88

on page 60.

36 Maintenance Action Plans

0179 10248 day(s) 13:33:36 14 Debug 0: sntEnt:LU Comm Error:k/ c/q=0b/08/88

Figure 8 Detail of Event Log Listing From Service Port

6 Check the listed event codes against the Event Code column of Table 4

. See Figure 8 to interpret the

log listing.

7 Read across Table 4

8 Find the Action number in the Action column of Table 4

to the Action column to see the associated Action number.

9 Complete the indicated MAP or action.

10 To see additional log messages, follow the procedure Event Log Dump

11 If there are no abnormal events, go to Perform Health Check

on page 44.

on page 136.

Table 4 Event Codes and Actions

Event Code

Viewing

Level

Default Trap Threshold

Description Action

Visual Observations

NA NA NA All LEDs are off 5

NA NA NA RDY LED not blinking once per second after

power has been on for one minute

NA NA NA Temperature warning LED on 4

NA NA NA Temperature alarm LED on 4

NA NA NA SNC not responding 3

NA NA NA Persistent reboots 3

NA NA NA Host application error message or host log

entry indicates SCSI target error

NA NA NA Host cannot access attached devices 12

NA NA NA FC LED off although cables are attached

and host systems are on and have booted

NA NA NA Heartbeat failure 7

NA NA NA fcShow command returns Firmware

2, 0

State = Sync Lost

SNC 4000 User’s Guide 37

Table 4 Event Codes and Actions

Event Code

Viewing

Level

Default Trap Threshold

Description Action

NA NA NA ADIC Management Console failure 7

NA NA NA Service terminal connection failure 8

Generic Event Descriptions

8 2 0 Sense data recorded following a check

condition

CAUTION: Normally, the host system will request and process send data and then perform error recovery.

9 1 0 LUN reports a “unit attention” condition on a

non-removable media device

11 1 1 ADIC Management Console reports a

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

13 1 1 SNC is shutting down as requested by the

ADIC Management Console (a Restart was requested)

14 0 0 Additional status information used for

diagnostics

16 1 1 A SCSI bus reports an unexpected interrupt 1

17 1 1 FC interface reports a LIP reset was

0, 2

received from a host

18 1 1 FC interface reports a system error 2

19 1 1 FC interface reports an error processing a

request

20 1 1 FC interface reports an error processing a

response

21 1 1 SNC processor memory fault detected 1, 2, 3

22 1 10 FC interface detected a LIP 2

23 2 0 FC interface reports a loop up 0

24 2 0 FC interface reports a loop down 0

25 1 1 SNC PCI bus parity error detected 3, 2, 1

26 1 1 SNC PCI interface error detected 3, 2, 1

27 2 0 A device has been added to a SCSI bus 0

28 1 0 A SCSI bus reports a reset has been

detected

38 Maintenance Action Plans

Table 4 Event Codes and Actions

Event Code

Viewing

Level

Default Trap Threshold

Description Action

29 1 1 SNC has added a device to its configuration

table.

CAUTION: The trap is held off until the SNC has been up for 60 seconds

30 1 1 SNC has removed a device from its

configuration

31 2 0 SNC logging service has started 0

1 1 An interface has detected a bus fault

(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 1

37 2 0 FC port database change detected 0

0, 1, 2

1, 2

39 1 1 Directory server on Fabric has changed 0

40 1 1 Maximum LUN limit has been exceeded 10

41 1 0 FC 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 FC 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

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

60 1 1 Power has entered Alarm Range 5

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

0 temperatures have entered Nominal Range from a Warning or Alarm Range

1 1 Inlet Air Temperature has entered Warning

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

63 1 1 Inlet Air Temperature has entered Alarm

4 Range

SNC 4000 User’s Guide 39

Table 4 Event Codes and Actions

Event Code

Viewing

Level

Default Trap Threshold

Description Action

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

66 1 1 Fan is operating in Nominal Range after

operating in a fault state

67 1 1 Fan speed has entered Warning 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 restart completed 0

72 1 1 Maximum number of initiators has been

exceeded

75 1 1 Connectivity with the host has been lost. 2

76 1 1 Connectivity with the host has been

0 established.

150 1 1 The event log is about to overwrite the

0 earliest events

Health Check Event Descriptions

100 1 1 Power supply is out of specification 5

102 1 Temperature change detected since the last

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

106 1 1 FC interface failed Health Check 2

107 1 1 SCSI interface failed Health Check 1

109 1 1 Target device failed Health Check 1

110 1 1 FC link status changed 0, 2

111 1 1 FC transfer failures detected since the last

0 report

CAUTION: error recovery may have

succeeded

112 1 1 Blower/Fan is running in Warning or Alarm

4 Range

113 1 1 Power is running in Warning or Alarm Range 5

40 Maintenance Action Plans

Table 4 Event Codes and Actions

Event Code

114 1 1 Temperature is running in Warning or Alarm

Viewing

Level

Default Trap Threshold

Description Action

4 Range

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

Heartbeat Event Descriptions

CAUTION: These event codes are not logged in the Event Log. Notification of these events occurs from the ADIC Management Console. For more information on Heartbeat, see the ADIC Management Console User’s Guide.

200

NA NA The server could not verify the connection to

7,3

the SNC

201

NA NA The client could not communicate with the

7,9

server

6,7

202

NA NA The server could not communicate with the

7,9

client

6,8

203

Notes:

action number.

NA NA Heartbeat communication restored 0

See Table 6 See Action Reference Table on page 41. Default Trap Threshold settings are explained “Events” in the ADIC Management Console User’s Guide. Check the Event Log to find out which interface (FCAL or SCSI) caused this event. Then use the appropriate

This trap signals a change in state. A string sent with the trap will indicate the nature of the previous state. Events not logged in SNC Event Log. Not Reported. View the Server Log. Event reported only when ADIC Management Console 2.7 or above is running

on page 42.

Action Reference Table

Numerical references from the Action column in Event Codes and Actions on page 37 are associated with the appropriate MAP in Action Reference Table

Table 5 Action Reference Table

Action Number

Action

0 No action necessary

1Go to SCSI Channel MAP

2Go to Fibre Channel MAP

3Go to MAP for the SNC

4Go to Temperature MAP

5Go to Power MAP

on page 56

7Go to Ethernet MAP

SNC 4000 User’s Guide 41

on page 46

on page 52

on page 55

on page 56

on page 41.

Table 5 Action Reference Table

Action Number

8Go to Service Port MAP

9 Contact your network administrator

10 Reduce the number of target devices attached to the SNC

11 Go to Start MAP

12 Go to Device Access MAP

Action

on page 60

on page 42

on page 45

Go to Retrieving the Code 43 Dump File

on page 137.

Event Viewing Levels

Numerical equivalents for the event viewing levels from the Viewing Level column of Table 5 are explained in Table 6

Table 6 Event Viewing Levels

Number Level Explanation

0 Notice 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

23.

Event Code or Obvious Symptom

Either an event code has been reported by the ADIC Management Console or an error has been observed by other means. For more information on events, see the ADIC Management Console User’s Guide.

If the event code is known, go to Table 4 action. If the symptom is obvious, go to Table 3

If the event code or error symptom is not known, go to Event Codes and Actions

Otherwise, proceed to Visually Inspect LEDs

on page 37 with that event code and perform the recommended

on page 35.

on page 42.

on page

Visually Inspect LEDs

Use this procedure to visually inspect the LEDs.

1 Observe interface panel SNC LED status indicators.

42 Maintenance Action Plans

For information about expected LED behavior, see LED Indicators on page 8.

2 If the RDY LED is flashing as expected but the SCSI, Ethernet, and FC Connection LEDs are off, the

SNC may have been left in diagnostic mode.

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

3 If the command prompt on the service terminal is diagmode >, return the SNC to normal mode by

entering the normalBoot command on the service terminal.

For more information, see Boot Modes

4 Check LED observation against Table 4

The Visual Observations area at the beginning of the Table includes several descriptions of situations signalled by LED states.

5 Refer to Table 5

6 If LED observations did not solve the problem, proceed to Check for Problems on Attached Devices

on page 41 and complete the action.

on page 135.

on page 37.

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 host platforms and FC HBAs, visit www.adic.com

Check SNC Product Versions

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

ADIC Management Console Version

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

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’s Guide.

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

, and perform the update.

SNC 4000 User’s Guide 43

Firmware Version

Use this procedure to check the firmware version level. For more information on the commands used in this procedure, see Commands Listed Alphabetically by Function

1 Connect a service terminal to the SNC.

on page 63.

2 Press Enter at the service terminal. If the prompt is not displayed, go to Service Port MAP

3 Issue the showVersions command.

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

, and perform the update.

on page 60.

Hardware Version

Use this procedure to check the hardware version information.

1 Connect a service terminal to the SNC.

2 Press the Enter key on the service terminal. If the prompt is not displayed, go to Service Port MAP

page 60.

3 Issue the sysVpdShow command.

For more information, see the sysVpdShow or sysVpdShowAll

4 Report this information to your service representative, if you are asked for it.

on page 117.

Quick Component Check

Use this procedure to check system components. For more information on the commands used in this procedure, see Commands Listed Alphabetically by Function

1 Connect a service terminal to the SNC.

on page 63.

2 Press Enter at the service terminal. If the prompt is not displayed, go to Service Port MAP

3 From the service terminal, enter the showBox command.

4 If an installed component does not show up in the display, go to the correct MAP.

For example, if a SCSI interface is missing, go to SCSI Channel MAP go to Fibre Channel MAP

5 If all components display properly, proceed to Perform Health Check

on page 52.

on page 46. If a FC is missing,

on page 60.

Perform Health Check

1 Stop all I/O.

2 Remove the Ethernet cable if installed.

3 Connect a service terminal to the SNC.

4 Press Enter at the service terminal. If the prompt is not displayed, go to Service Port MAP

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 page 63.

6 Check the results displayed on the service terminal to determine the status of the interfaces and

attached devices. If a failure is indicated, perform the appropriate MAP.

on page 60.

44 Maintenance Action Plans

Check the Host Event Log

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

on page 52.

Database Full MAP

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

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. For more information on the commands used in this procedure, see Commands Listed Alphabetically by Function

on page 63.

CAUTION

1 Connect a service terminal to the SNC.

2 Press Enter at the service terminal. If the prompt is not displayed, go to Service Port MAP

3 From the service terminal, enter the mapShowDatabase command to display the contents of the

database.

4 From the service terminal, enter the mapShowDevs command to display LUN assignments for the

attached devices that have been mapped.

5 From the service terminal, enter the mapWinnowDatabase command to remove LUN assignments for

devices that no longer need to be kept.

6 Reboot the SNC.

7 After the SNC has finished booting, repeat Step 3

been mapped.

Use this procedure only when you are sure that the devices you are interested in are connected and available to the SNC. Devices that are not currently attached will be removed from the database. You must reboot the Scalar 24 after performing this procedure for the changes to take effect.

on page 60.

and Step 4 to verify that all attached devices have

Device Access MAP

Perform these steps if a host is not able to access SCSI or FC devices. For more information on the commands used in this procedure, see Commands Listed Alphabetically by Function

on page 63.

1 Connect a service terminal to the SNC.

2 Press Enter at the service terminal. If the prompt is not displayed, go to Service Port MAP

on page 60.

Check Fibre Channel Port Status

1 Enter the fcShow command from the service terminal.

If the fcShow command does not display a Firmware State of Ready for the attached FC SAN connection, go to Fibre Channel MAP

2 If a FC host should have access to SCSI Channel devices, verify that the FC port mode is Target.

The SNC FC port is 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.

SNC 4000 User’s Guide 45

on page 52.

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

3 If the host should have access to devices on a FC, verify that the FC port mode is set to “Initiator,”

“Target,” 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 FC device.

Check SCSI Channel Devices

1 Enter the scsiShow command from the service terminal.

2 If all of the attached SCSI devices are not displayed, go to SCSI Channel MAP

on page 46.

Check Channel Zoning Settings

1 Enter the fcShowDevs command from the service terminal.

2 Look at the display for the FC interface. If all of the SCSI devices are displayed under the FC interface,

then host access to SCSI devices is not being restricted by Channel Zoning.

3 Use the ADIC Management Console to change Channel Zoning settings.

For information on Channel Zoning, see the ADIC Management Console User’s 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

1 Connect a service terminal to the SNC.

2 Press Enter at the service terminal. If the prompt is not displayed, go to Service Port MAP

3 If the SNC is off, then turn it on.

4 Verify that the RDY LED is blinking once per second.

5 As the SNC 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

6 Enter the showBox command from the service terminal.

7 Write down the information for each SCSI channel.

SCSI -1 requires Low Voltage Differential cable

8 If the SCSI interfaces are not all displayed, replace the SNC. Go to Before Removing or Replacing the

SNC on page 28. Continue through Replacing the SNC on page 28.

46 Maintenance Action Plans

on page 60.

9 Exit this MAP.

If the SCSI interfaces display properly, go to Check Attached SCSI Devices from the Service Port page 47.

Check Attached SCSI Devices from the Service Port

CAUTION

1 Issue the scsiShow command from the service terminal to display a list of attached SCSI devices.

2 For each SCSI channel, make a list of attached devices. Include SCSI device ID, manufacturer, and

device status/flags.

3 Go to Compare Listed versus Physical Devices

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

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

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

on page 47.

Compare Listed versus Supported Devices

1 Compare the attached devices to the list of supported devices listed.

2 If the attached devices are all supported, go to SCSI Loop Back Test

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, those devices will need to be removed or replaced.

on page 50.

Check SCSI Bus Termination

CAUTION

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.

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

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.

2 Verify the termination for the other devices attached to the channel in question.

SNC 4000 User’s Guide 47

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

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

3 If there are SCSI termination problems, power down the Scalar 24 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

4 If you powered down the Scalar 24, turn it back on.

on page 48.

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. Data transfers to that device will be unreliable.

CAUTION

1 Enter the scsiShow command from the service terminal.

For more information, see the scsiShow

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

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.

4 Check that for each SCSI Channel, no devices are set to ID 7 except the SNC channel ID.

If a target device is set to the same ID as the SNC (ID 7), the bus will be unstable and data corruption may result.

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

on page 106.

5 If you do not need to correct any SCSI IDs, go to Improper Device Type

6 If you corrected any SCSI IDs, reboot the Scalar 24.

7 After it finishes booting, enter the scsiShow command.

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

9 If not all of the physical devices are shown, go to Improper Device Type

10 If all of the physical devices are shown, go to SCSI Health Check

on page 48.

on page 50.

Improper Device Type

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 may be attached to low voltage differential SCSI channels.

When a mix of Ultra2/3 SCSI and Ultra SCSI devices are connected to a single bus, the bus will run at the Ultra SCSI speed. Because the bus will auto-adjust to the slowest speed, it is not recommended that you run both Ultra2/3 SCSI and Ultra SCSI devices on the same bus.

CAUTION

2 Replace any improper SCSI device with a proper device.

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

3 Reconnect the SCSI cable.

48 Maintenance Action Plans

4 If you do not have to replace an improper device, go to Examine SCSI Cables.

If you replaced any devices, reboot the Scalar 24.

5 After the SNC finishes booting, enter the scsiShow command from the service terminal.

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

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

8 If all of the physical devices are shown, go to SCSI Health Check

Examine SCSI Cables

CAUTION

1 Look for damaged cables.

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

2 Replace any damaged cables.

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.

4 Replace any cables not suitable for running at Ultra 2/3 speeds.

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.

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

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

6 Replace any cables that are of the wrong type.

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.

8 Replace all unshielded cables.

9 If no cables are replaced, go to Examine SCSI Cables

10 If cables were replaced, go to SCSI Health Check

Examine SCSI Connectors

CAUTION

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

2 Replace any cables that have bent pins.

3 If you did not have to replace or re-secure a SCSI cable, go to SCSI Loop Back Test

4 If you replaced or re-secured a SCSI cable, reboot the Scalar 24.

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

5 After it finishes booting, enter the scsiShow command from the service terminal.

SNC 4000 User’s Guide 49

For more information, see the scsiShow on page 106.

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

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

8 If all of the physical devices are shown, go to SCSI Health Check

SCSI Health Check

1 Perform a Health Check. For more information, see Perform Health Check on page 44.

2 Check the Event Log for SCSI errors. For more information, see Check the Host Event Log

3 Perform a component check. For more information, see Quick Component Check

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

If no errors are reported, exit this MAP.

on page 50.

on page 44.

SCSI Loop Back Test

CAUTION

Before performing diagnostics, all FC and SCSI cables must be disconnected from the SNC. Before changing any SCSI cables, all I/O to the SNC must be stopped and the SNC 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.

on page 45.

1 If the SNC’s command prompt on the terminal is not diagmode >, enter the diagBoot command on

the service terminal.

For more information, see Entering Diagnostic Mode

2 Power down the Scalar 24.

3 In addition to the suspect SCSI channel, choose one of the other SCSI channels to use for the loop back

test.

4 Label and remove those cables.

5 Connect a short SCSI loopback test cable to those two SCSI channels.

6 Power on the system.

7 Wait for the SNC to finish booting.

8 Enter the scsiChannelTest(1,2) command. The following example shows a loop back test on SCSI

channels 1 and 2.

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

9 If the SNC returns a PASSED status, go to Testing SCSI Cables

on page 135.

on page 50.

Testing SCSI Cables

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

1 Stop all I/O to the SNC.

50 Maintenance Action Plans

2 If the SNC’s command prompt on the terminal is not diagmode > place the SNC in diagnostic mode.

For more information, see Entering Diagnostic Mode

3 Shut down the SNC.

4 Remove the cable from one attached SCSI device, and attach it as a loop back cable to the SNC.

5 Power on the SNC.

6 After the SNC has finished booting, enter the scsiChannelTest(x,y) command from the service

terminal (where ‘x’ and ‘y’ are the slot numbers connected by the loopback cable) to perform a loop back test.

For an example, see SCSI Loop Back Test

If the SNC returns a FAILED status, the cable is faulty and must be replaced.

If the SNC returns a PASSED status, go to Isolating SCSI Devices on the SCSI bus.

on page 50.

on page 135.

on page 51 to isolate bad devices

Isolating SCSI Devices

1 Restore the SNC to normal operation.

See Restoring Normal Mode

2 Power down the Scalar 24.

3 Perform Step 4

versus Physical Devices on page 47.

- Step 11 for each SCSI device that was found missing in Step 1 under Compare Listed

on page 136.

4 Remove all devices from the SCSI buses.

5 Attach ONLY the device in question to the SCSI channel it was originally connected to using a known-

good SCSI cable and terminators.

6 Power the SNC back on. Wait for it to finish booting.

7 Enter the scsiShow command from the service terminal and verify the device’s presence.

For more information, see the scsiShow

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.

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

For more information, see Perform Health Check

10 Review the host event log.

For more information, see Check the Host Event Log

11 If SCSI errors are found, then inform the system administrator that the connected device appears to be

bad.

Replace or remove any bad devices.

12 After all possible device checks are performed go to Restore SCSI Setup

on page 106.

on page 44.

on page 45.

Restore SCSI Setup

1 Shut down the SNC.

2 Reconnect all available SCSI devices to their proper channel assignments.

SNC 4000 User’s Guide 51

Use the original configuration, except where changes have been made per this MAP.

3 Wait for the SNC to finish booting.

4 If the SNC is in diagnostic mode (command prompt = diagmode >), then restore normal operation.

For more information, see Restoring Normal Mode

5 Perform a health check.

For more information, see Perform Health Check

6 Review the host event log.

For more information, see Check the Host Event Log

7 If all attached SCSI devices and cables are determined to be good, yet SCSI errors persist, replace the

SNC.

8 Go to Before Removing or Replacing the SNC

9 Proceed through Replacing the SNC

10 Exit this MAP.

on page 28.

on page 136.

on page 44.

on page 45.

on page 28.

Fibre Channel MAP

Perform these steps if:

• The FC interface reports a reset or system error

• The FC interface reports an error processing a request or response

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

• Other FC errors reported

• FC LED is off

Verify FC Connections

1 Connect the service terminal to the service port.

2 Press Enter on the service terminal. If the prompt is not displayed, go to Service Port MAP

3 From the service terminal, enter the showBox command.

4 Confirm that the FC connection is correctly displayed. If showBox displays the FC connections

correctly, go to Examine Cables

5 If the FC connection does not display correctly in the showBox display, remove the SFP and replace it

with a known-good SFP.

Go to Removing the SFP

Proceed through Replacing the SFP

6 Proceed to Test SFP

on page 52

on page 53.

on page 28.

on page 60.

Test SFP

CAUTION

52 Maintenance Action Plans

You must stop I/O at the FC host.

1 With a known-good SFP installed, confirm that the SNC’s FC connection is correctly displayed by

issuing the showBox command from the service terminal.

2 If the output of the showBox command matches the FC configuration, exit this MAP.

If the output of the showBox command, still does not match the FC configuration, remove the knowngood SFP and reinstall the original SFP.

3 Go to Examine Cables

on page 53.

Examine Cables

CAUTION

1 Remove the cables.

2 If any cables are obviously damaged, replace them.

3 Use dusting spray/compressed gas to dust off optical connectors on the SFP and cable ends.

4 Reconnect the cables.

5 Perform Health Check. For more information, see Perform Health Check

6 View the event log at viewing level 3.

For more information, see Table 6

7 If errors are gone, exit this MAP.

If errors persist, go to Fibre Channel Loop Back Test

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

on page 44.

on page 42.

on page 53.

Fibre Channel Loop Back Test

CAUTION

1 Attach a FC loop back plug to the FC port.

2 If the front-panel FC LED is not on, replace the SNC.

3 Go to Before Removing or Replacing the SNC

Continue through Replacing the SNC

4 Exit this MAP.

If the interface panel FC LED is on, proceed to Step 5

5 If the SNC’s command prompt on the service terminal is not diagmode >, place the SNC in diagnostic

mode. For more information, see Entering Diagnostic Mode

6 Substituting the FC slot number for x, enter the fcSlotTest x command.

For more information, see fcSlotTest [x]

7 If the test failed, replace the SNC.

8 Go to Before Removing or Replacing the SNC

Continue through Replacing the SNC

9 Exit this MAP.

If the test passed, the FC port is good.

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

on page 28.

on page 135.

on page 138.

on page 28.

SNC 4000 User’s Guide 53

10 Remove the loop back plug.

Go to Testing Fibre Channel Optic Cable

on page 54.

Testing Fibre Channel Optic Cable

CAUTION

1 If the cables are already removed, reattach them.

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

2 Substituting the FC slot number for x, from the service terminal enter the fcSlotTest x command.

3 If the test passes, the FC optical cable is good.

Go to Replace Fibre Channel Device

If the test fails, go to Replace Fibre Channel Cable

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

on page 54.

Replace Fibre Channel Cable

1 Replace the cables to the FC ports with known good cables.

2 Perform Health Check.

For more information, see Perform Health Check

3 View the event log at viewing level 3.

For more information, see Table 6

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.

5 Replace external devices that are attached to the FC port.

Go to Replace Fibre Channel Device

on page 42.

on page 54.

on page 44.

Replace Fibre Channel Device

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

• FC HBA

• FC Switch

• FC Hub

• FC Disk subsystem

1 Inform the system administrator that it is necessary to replace the FC device connected to the SNC to

resolve the FC errors.

2 Repeat this MAP, beginning with the section Connect the service terminal to the service port.

52, after replacing the external component.

54 Maintenance Action Plans

on page

MAP for the SNC

Perform these steps if:

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

• The SNC is not responding

• SNC processor memory fault detected

• SNC PCI bus parity error detected

• SNC PCI interface error detected

• The ADIC Management Console Server could not verify the connection to the SNC

Observe Operational LED Behavior

When the SNC 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

Within one minute, the SNC should have booted successfully and the RDY LED should be blinking once per second. If the RDY LED is not blinking as expected, go to Start MAP

on page 42.

on page 143.

Temperature MAP

Perform the procedures in the sections below if:

• The SNC generates trap event codes 62, 64, or 67 (Inlet Air, I/O Processor, or Fan have entered a Warning Range)

• The SNC generates trap event codes 63, 65, or 68 (Inlet 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

Operators are normally notified of problems or potential problems in SNC 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’s 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

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 generate these messages.

on page 76 for operational temperature ranges that will generate these messages. If the

on page 77 for conditions that will

Temperature Warnings or Alarms Received

1 Verify that room temperature is within satisfactory limits.

2 If room temperature is not within satisfactory limits, adjust it.

3 If the room temperature is within satisfactory limits, and alarm or warning messages are being

generated, check the air intake for obstructions.

SNC 4000 User’s Guide 55

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

5 If temperatures stabilize, exit this MAP.

6 If no obstructions are found, or temperatures do not stabilize, check the SNC’s Air Outlet for

obstructions.

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

8 If temperatures stabilize, exit this MAP.

9 If no obstructions are found, or temperatures do not stabilize, replace the unit.

Proceed to Before Removing or Replacing the SNC

Continue through Replacing the SNC

on page 28.

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 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 Removing or Replacing the SNC

Continue through Replacing the SNC

on page 28.

Power MAP

Perform the steps below if:

• All LEDs are off

• The SNC 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.

• Health Check generates a trap event code 113, indicating that Power is running in Warning or Alarm Range

1 Verify that the SNC is correctly installed in a Scalar 24 SNC slot.

2 Verify the status of the PWR LED.

3 If the PWR LED remains off, try a different power cord.

4 If the PWR LED remains off, remove the SNC.

Proceed to Before Removing or Replacing the SNC

Continue through Replacing the SNC

on page 28.

Ethernet MAP

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

• The IP address for the SNC - REQUIRED

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

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

• The IP address of a computer on the same subnet as the SNC for PING tests - REQUIRED

56 Maintenance Action Plans

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

• The SNC 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, see Figure 9

Figure 9 Ethernet Port on Interface Panel

5 Verify that the Ethernet Link LED, which is the green LED on the left, is on. This LED is a combined link/

activity LED. If the link is up and there is activity, it will blink.

6 If the LED is on, go to Step 7

If the LED is not on, proceed to Before Removing or Replacing the SNC

Continue through Replacing the SNC

on page 28.

Exit this MAP.

7 Determine the speed of the network, by following the procedure in Perform Health Check

on page 44.

If the Health Check generates a trap event code of 115, then the SNC’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.

8 If the yellow Speed LED correctly reflects the speed of the network, go to Step 10

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

9 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 yellow Speed LED does correctly reflect the network speed, go to Ethernet MAP

Continue through Replacing the SNC

on page 56.

on page 28.

Exit this MAP.

10 Remove the Ethernet cable from the SNC Ethernet Port and attach the Ethernet loop back plug.

11 Verify that the Ethernet LEDs are functioning correctly.

If they are, proceed to Step 12

SNC 4000 User’s Guide 57

If they are not, inform the System Administrator that there is a network hardware problem where the SNC is attached.

Exit this MAP.

12 Remove the Ethernet loop back plug.

13 Obtain another Ethernet cable.

14 Use this cable to attach the SNC to the local area network.

15 Connect the service terminal to the service port.

16 Press Enter at the service terminal.

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

on page 60.

17 From the service terminal, enter the ifShow command.

SNC4000 > 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 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

18 If there is no entry for ibmEmac, replace the SNC. Go to Before Removing or Replacing the SNC

page 28.

Continue through Replacing the SNC

on page 28.

Exit this MAP.

If there is an entry for ibmEmac, write down the values of the:

• internet address,

• netmask,

• subnetmask

19 Verify that the internet address is the same as the IP address supplied by the network administrator.

58 Maintenance Action Plans

20 Verify that the netmask value is the same as the netmask in hex format supplied by the network

administrator.

21 Verify that the subnetmask is the same as the netmask. If these values are correct, go to Step 24

If these values are not correct, proceed to Step 22

22 Use the ethAddrSet command to set the correct IP address and netmask values.

For more information, see the ethAddrSet

on page 78.

23 From the service terminal, enter the reboot command and wait for the SNC to finish booting.

Go back to Step 17

24 Enter the command ping “<host IP address>”, where <host IP address> is four decimal

numbers separated by periods.

<host IP address> is the address provided by the network administrator for PING testing.

Display of successful PING test:

SNC4000 > 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

Display of failed PING test:

SNC4000 > ping "192.168.1.251",10 PING 192.168.1.251: 56 data bytes request timed out value = -1 = 0xfffffff

25 If the PING test passes, go to Step 26

If the PING test fails, inform the System Administrator that there is a network hardware problem where the SNC is attached.

Exit this MAP.

26 Remove the Ethernet cable from the SNC and install the Ethernet loop back plug.

27 From the service terminal, enter the diagBoot command.

For more information, see Diagnostic Command Reference

on page 135.

28 Wait for the SNC to finish booting.

29 Verify that the diagmode> prompt is displayed.

30 From the service port, enter the elTest command.

diagmode > elTest ==== Testing Ethernet ==== Init complete.

SNC 4000 User’s Guide 59

Ethernet OK value = 0 = 0x0

31 If the test fails, replace the SNC.

Go to Before Removing or Replacing the SNC

Continue through Replacing the SNC

Exit this MAP.

If the test passes, remove the Ethernet loop back plug.

Proceed to Step 32

32 From the service terminal, enter the normalBoot command and wait for the SNC to finish booting.

33 Reattach the Ethernet cable to the SNC.

34 From the service terminal, enter the gateAddrGet command and write down the network gateway

address that is displayed.

For more information, see the gateAddrGet

35 Compare this address to the one provided by the network administrator.

If both addresses are the same, go to Step 36

SNC4000 > 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 gateAddrSet command.

For more information, see the gateAddrSet

on page 28.

on page 85.

36 From the service terminal, enter the reboot command.

37 Wait until the SNC has finished booting.

38 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’s Guide.

39 From the host running the ADIC Management Console Server, PING the SNC.

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.

Service Port MAP

These steps are performed if the SNC boots and responds to the ADIC Management Console, but the service port does not respond. For more information, see the ADIC Management Console User’s Guide.

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.

1 Remove the RS-232 cable from the service port.

2 Connect it to the compatible port on the other computer.

3 Connect the service terminal to the cable.

60 Maintenance Action Plans

4 Set the service terminal and the other computer to 19200 baud, 8 data bits, no parity, one stop, Xon/

Xoff (or Hardware) flow control.

5 Enter test lines in the service terminal and the other computer.

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

Proceed to Check Connection with Boot Messages

Check Connection with Boot Messages

1 Reconnect the terminal to the SNC with the RS-232 cable.

2 Stop all I/O to the SNC.

3 Shut down the SNC and keep the power off for 5 seconds.

4 Turn the SNC on.

If boot messages fail to appear on the service terminal, then replace the SNC.

Go to Before Removing or Replacing the SNC

Proceed through Replacing the SNC

on page 28.

Scalar Firewall Manager Settings MAP

Perform the procedures in the sections below if SFM devices are unavailable.

Check Scalar Firewall Manager Access Settings

1 Connect the service terminal to the service port.

2 Press Enter on the service terminal.

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

3 Enter the sfmShow -1 command from the service terminal.

4 If SFM State: Inactive is displayed, Scalar Firewall Manager® is 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

5 Enter the sfmFeatureEnable command from the service terminal.

If SFM devices are available, exit this MAP.

If SFM devices are not available, proceed to Step 6

6 Enter the licenseShow command from the service terminal.

License "s2zhq-7xdhd": Valid Features: SFM Value = 2 = 0 x 2

7 If the output from the licenseShow command shows that SFM is Valid, as in the example, proceed to

Step 8

on page 60.

SNC 4000 User’s Guide 61

If the output from the licenseShow command shows that SFM is not Valid, exit this MAP and contact your service representative.

8 Use the ADIC Management Console to verify the host and target device access settings. For more

information, see the ADIC Management Console User’s Guide.

Exit this MAP.

If the ADIC Management Console is not available, you can temporarily make SFM inactive to verify that the host can access all devices. Proceed to Verify Host Access to Devices

on page 62.

Verify Host Access to Devices

1 Shut down all of the hosts.

2 Enter the sfmInactive Set command from the service terminal.

For more information, see the sfmInactiveSet

3 Startup one of the hosts.

4 If the host can access all of the target devices, shut down the host and repeat Step 2

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

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

5 Shut down all of the hosts.

6 Enter the sfmActiveSet command from the service terminal.

For more information, see the sfmActiveSet

7 Use the ADIC Management Console to verify the host and target device access settings. For more

information, see the ADIC Management Console User’s Guide.

on page 112.

and Step 3 for

on page 45 or Fibre Channel MAP on page 52.

on page 110.

62 Maintenance Action Plans

Service Port Command Reference

A “shell” interface provides access to the management and configuration commands referenced in this chapter. The shell is accessible by connecting a terminal or computer with terminal emulation software to the SNC 4000 service port. For more information, see Connecting to the Service Port

Managing the SNC 4000

The ADIC Management Console application is the preferred method for managing the SNC 4000. When you use the ADIC Management Console, the operations described in this reference are carried out through the client application. For more information, see the ADIC Management Console User’s Guide.

Commands

This section specifies the commands that are available to control, manage, and service the SNC 4000. The commands are listed alphabetically by function in Table 7. The commands are listed in alphabetical order beginning on page 71.

Table 7 Commands Listed Alphabetically by Function

on page 23.

Command or Command Group

disableCC Disable Command and Control Interface 75

enableCC Enable Command and Control Interface 76

setSnaCCLun Change Command and Control Interface LUN 109

Data Mover

sncFeatureEnable Enable the optional Data Mover feature 114

Data Path Conditioning (Multi-path mapping)

ampFeatureEnable Enable the optional multi-path mapping feature 71

ghostIOSet Change the length of time that commands to FC

SNC 4000 User’s Guide 63

Description Page

targets remain queued

Table 7 Commands Listed Alphabetically by Function

Command or Command Group

ghostIOShow Display the length of time that commands to FC

Description Page

targets remain queued

mapMultipathSet Change the setting for mapping new targets 95

mapMultipathShow Display the current setting for mapping new targets 95

mapRemoveDevice Remove a device from the persistent device map 96

tPathShow Display the state of targets mapped for failover 121

DHCP

dhcpClientShow

dhcpEnable

dhcpDisable

dhcpState

resolvParamShow

Diagnostics

Display data received from DHCP server 74

Enable DHCP 74

Display data received from DHCP server 74

Display state of DHCP 75

Display list of DNS servers 101

Diagnostic commands are located in Diagnostic

Command Reference on page 135.

Environmental Sensors

envMonShow Display all environmental channel states 76

Ethernet Network

arptabShow Display a list of known ARP entries 71

ethAddrGet Display Ethernet Port address 78

ethAddrSet Set Ethernet Port address 78

gateAddrGet Display network gateway address 85

gateAddrSet Set network gateway address 85

host “add” Add host table entries 88

host “delete” Delete network host table entries 88

host “list” List network host table entries 89

hostNameSet Change SNC 4000’s network name 89

icmpstatShow Display statistics for ICMP 90

ifShow Display Ethernet Port parameters and status 90

inetstatShow Display all Internet protocol sockets 91

ipstatShow Display statistics for IP 92

64 Service Port Command Reference

Table 7 Commands Listed Alphabetically by Function

Command or Command Group

macShow Display Ethernet Port Media Access Control

Description Page

address

mbufShow Display mbuf statistics 98

route Edit route table entries 101

route “add” Add network route table entries 102

route “delete” Delete network route table entries 102

route “list” List network route table entries 102

snmpCommunitiesShow Display list of Community names currently in use 115

snmpReadCommunityAdd Add Community name with Read permission 116

snmpReadCommunityRemove Remove Community name Read permission 116

snmpTrapCommunitySet Set Community name passed with traps 116

snmpWriteCommunityAdd Add Community name with Write permission 116

snmpWriteCommunityRemove Remove Community name Write permission 116

tcpstatShow Display statistics for TCP 121

trapDestAdd Add recipient IP address to trap destination table 122

trapDestRemove Remove recipient IP address from trap destination

122

table

trapDestShow Display trap destination table 122

udpstatShow Display statistics for UDP 123

userAdd Add a user and password to the password file 123

userDelete Delete a user from the password file 123

userList Display the contents of the password file 123

Event Logging

cleShow Display Command Log events for the specified

LUN

cleShowAll Display Command Log events for all LUNs 72

csClearLogFile Clear the Event Log 73

loggerDump Display Event Log records 92

loggerDumpCurrent Display Event Log records for current boot 93

supportDump Display information used in troubleshooting 140

Fibre Channel

SNC 4000 User’s Guide 65

Table 7 Commands Listed Alphabetically by Function

Command or Command Group

fcConnTypeGet Display the current setting of the FC port’s

Description Page

connection type

fcConnTypeSet Set the type of connection for a FC port 79

fcFibreSpeedGet Display maximum and current speeds of FC port 80

fcFibreSpeedSet Set FC port speed 80

fcGbicShow Display the SFP information for each installed SFP 80

fcPortModeGet Display the mode for the specified FC port 81

fcPortModeSet Set the mode for the FC port 81

fcRestart Restart the FC port 82

fcShow Display FC interface status 82

fcShowDevs Display attached SCSI and FC Target Devices

from FC port perspective

fcShowNames Display Node and Port names for the FC 84

fcTxDisable Disable the FC port transmitter 84

fcTxEnable Enable or re-enable the FC port transmitter 84

setFcFrameSize Set Frame Size for specific FC port 107

setFcHardId Set Loop ID for the FC port 107

setHost Set Host OS type for the FC port 107

sysNodeNameModeSet Change the FC Node Name mode 117

sysNodeNameModeShow Display the current FC Node Name mode 117

targets Display attached SCSI and FC Target devices 120

Flash File System

cd Set current working path 72

ll List directory contents in long format 93

ls List directory contents 93

rm Remove (delete) a file 101

rz Initiate a receive Zmodem file transfer session 103

sz Initiate a send Zmodem file transfer session 120

Health Check

hlthChkIntervalGet Display Health Check Interval 87

hlthChkIntervalSet Set Health Check Interval 87

66 Service Port Command Reference

Table 7 Commands Listed Alphabetically by Function

Command or Command Group

Description Page

hlthChkLevelGet Display Health Check Level 87

hlthChkLevelSet Set Health Check Level 87

hlthChkNow Perform a Health Check Now 87

Help

clehelp Display Command Log Entry command info 72

diagHelp Display Diagnostic command info 75

help Display info for all shell commands 86

hlthChkhelp Display Health Check command info 87

mapHelp Display Device Map command info 94

netHelp Display Network command info 99

snmpHelp Display SNMP command info 115

userHelp Display User account command info 124

Multi-path Mapping

See Data Path Conditioning

Product Data and Maintenance

clearReservation Force-clear a reservation on the specified target

LUN

initializeBox Restore factory defaults by deleting all

configuration files including persistent address map databases and then reboot

licenseShow Display information about installed software license

keys

mapCompressDatabase Remove inactive device entries and reassign

LUNS contiguously in persistent address map database

mapRebuildDatabase Delete and reconstruct persistent address map

database

mapShowDatabase Display all persistent address map database

entries

mapShowDevs Display persistent address map database entries

for attached devices only

mapWinnowDatabase Remove inactive device entries from persistent

address map database

mapWinnowDatabaseLun Remove specified device entry from persistent

address map database

shellLock Lock or unlock the shell command interface 113

SNC 4000 User’s Guide 67

Table 7 Commands Listed Alphabetically by Function

Command or Command Group

Description Page

showBox Display graphic of hardware 140

showVersions Displays the version of the operational firmware,

114 Power-On-Self-Test (POST), bootrom and Alternate bootrom

sysConfigShow Display configuration settings 116

sysVpdShow Display Vital Product Data 117

sysVpdShowAll Display Vital Product Data for all subsystems 117

version Display Firmware version 124

uptime Display time elapsed since last boot 123

SAN Access Security: Scalar Firewall Manager (SFM)

sfmAccessApply Apply access settings and save in Scalar Firewall

For commands used with Extended VPS (eVPS), see below.

109 Manager database

sfmAccessClear Disable Scalar Firewall Manager access to all

109 LUNs for all hosts

sfmAccessSet Set Scalar Firewall Manager access permission for

109 a specific host and a specific LUN range

sfmActiveSet Reactivate Scalar Firewall Manager if inactive 110

sfmConnectionSet Enter connection information for a specific host 110

sfmFeatureDisable Disable Scalar Firewall Manager 110

sfmFeatureEnable Enable Scalar Firewall Manager with license key 110

sfmFileShow Show the SFM data store in the file 111

sfmHostShow Display LUN access permissions for a specific host 111

sfmInactiveSet Deactivate Scalar Firewall Manager access control

112 allowing all hosts to access all LUNs

sfmNameSet Enter a name for a specific host 112

sfmShow Display status information for one or all registered

112 hosts

sfmSparseAccessSet Set access permission for a specific host and

113 specific LUNs

sfmTypeSet Enter Operating System information for a specific

113 host

SAN Access Security: Extended VPS (eVPS)

For commands used with Scalar Firewall Manager (SFM), see above.

vps See vpsShow 132

68 Service Port Command Reference

Table 7 Commands Listed Alphabetically by Function

Command or Command Group

vpsAccessApply Apply access settings and save in VPS or eVPS

Description Page

125 database

vpsAccessClear Disable eVPS access to all LUNs for all hosts 125

vpsAccessSet Set eVPS access permission for a specific host

125 and a specific LUN range

vpsActiveSet Reactivate VPS or eVPS if inactive 126

vpsConnectionSet Enter connection information for a specific VPS or

126 eVPS host

vpsDefaultInbandAccessGet Display in-band access settings for the SNC 126

vpsDefaultInbandAccessSet Set in-band access levels for the SNC 126

vpsFeatureDisable Disable VPS and eVPS 127

vpsFeatureEnable Enable VPS and eVPS 127

vpsFileShow Shows the VPS or eVPS data stored in the file 128

vpsHostInbandAccessGet Display in-band access settings for a particular

128 eVPS host

vpsHostInbandAccessSet Set the in-band access level for a single eVPS host 129

vpsHostShow Display LUN access permissions for a specific VPS

129 or eVPS host

vpsInactiveSet Deactivate VPS or eVPS if active 130

vpsMapAdd Assign a target device to an eVPS host 130

vpsMapDelete Delete a previous eVPS LUN assignment 131

vpsMapClear Clear all the mapping assignments for a specified

131 eVPS host

vpsMapShow List all available mapping information for an eVPS

131 host

vpsNameSet Enter a name for a specific VPS or eVPS host 131

vpsShow Display status information for one or all registered

132 VPS or eVPS hosts

vpsSparseAccessSet Set access permission for a specific VPS or eVPS

132 host and specific LUNs

vpsTypeSet Enter operating system information for a specific

133 VPS or eVPS host

wwnLockModeSet Set the state of the WWN Locking Mode 133

wwnLockModeShow Show the state of WWN locking mode 133

SCSI

SNC 4000 User’s Guide 69

Table 7 Commands Listed Alphabetically by Function

Command or Command Group

fcShowDevs Display SCSI and FC Target Devices from FC port

Description Page

84 perspective

scsiAltIdGet Display SCSI Alternate IDs 103

scsiAltIdSet Change SCSI Alternate IDs 103

scsiHostChanGet Display SCSI Host Channel Modes 104

scsiHostChanSet Set SCSI Host Channel Modes 104

scsiHostIdGet Display SCSI Host ID Numbers 104

scsiHostIdSet Set SCSI Host ID Numbers 105

scsiRescan Rescan for devices on one or all SCSI Channels 105

scsiResetDisableGet Display SCSI Bus Reset on Power-Up Setting 105

scsiResetDisableSet Set the SCSI Bus Reset on Power-Up Setting 105

scsiShow Display SCSI Channels and attached devices 106

scsiTermGet Display termination status information for SCSI

107 Channels

targets Display attached SCSI and FC Target devices 120

Startup

diagBoot Shutdown and restart in Diagnostic mode 137

normalBoot Shutdown and restart in Normal mode 100

reset Restart without shutdown 101

reboot Shutdown and restart 100

Time and Date

date Display the date and time 73

dateSetFromRTC Set the Real Time Clock as the source of date

73 display

hostShow Display the IP address of the system timeserver 89

rdate Set a remote system as the source of date display 100

rtcDateSet Manually set the Real Time Clock 102

rtcSetCurrent Synchronize the Real Time Clock with the

102 timeserver

setNettime Enable or disable timeserver functionality 108

setTimeHost Add a host running timeserver to the system 109

tzSet Set the time zone offset from Greenwich Mean

122 Time

70 Service Port Command Reference

Table 7 Commands Listed Alphabetically by Function

Command or Command Group

Description Page

Virtual Private Map

copyScsiAssign

deleteScsiAssign

setScsiAssign

showScsiAssign

vpmFeatureEnable

vpmFeatureEnabled

Copy SCSI assignments from a source channel to a destination channel

Delete an assignment previously created

Assign a target device to a SCSI channel

List the current assigned addresses for the indicated channel

Enable the optional Virtual Private Map feature

Display status information about Virtual Private Map

Each command outputs a status “value” in decimal and hexadecimal after execution and before a new prompt is displayed.

value = 0 = 0x0

Usually a value of 0 indicates success, but some successful commands return a different value.

ampFeatureEnable

The ampFeatureEnable command enables the optional multi-path mapping feature. You enable the feature by entering the unique license key.

SNC > ampFeatureEnable "N499F-ZZ" Copy OK: 60 bytes copied AMP Enabled, License is Valid value = 0 = 0x0 SNC >

If the license key was factory-installed, you can enter the word “enable” (in quotes) rather than the actual license key.

SNC > ampFeatureEnable "enable" AMP Enabled, License is Valid value = 0 = 0x0 SNC >

If value = 1 = 0x1 message is displayed, it means the license is already installed and multi-path mapping is already enabled.

If the value = -1 = 0xffffffff message is displayed, it means the license is not already installed and you do need to enter the license key.

arptabShow

The arptabShow command displays the contents of the ARP table. The ARP table contains the current Internet-to-Ethernet address mappings. This information may be useful to the LAN administrator.

SNC4000 > arptabShow

LINK LEVEL ARP TABLE destination gateway flags Refcnt Use Interface

SNC 4000 User’s Guide 71

------------------------------------------------------------------------

172.16.1.1 00:04:4e:15:64:8 405 0 10 ibmEmac0

172.16.34.209 00:60:97:ba:86:db 405 1 471 ibmEmac0

-----------------------------------------------------------------------value = 75 = 0x4b = 'K'

You can move to a different directory (usually in the flash file system) using the cd command.

SNC4000 > cd "MGMT" value = 0 = 0x0

clearReservation [devId]

The clearReservation command can be used to force-clear a reservation held by a host for the specified target device. It may be necessary to issue this command if a host that has a reservation for a shared device was disconnected from the SNC 4000 without properly shutting down the application software that issued the reservation. If this is the case, other hosts that attempt to access the shared device will repeatedly receive reservation conflict status from the device. Issuing this command may result in resetting the target device.

CAUTION

Parameter Value

devId The index of the device (LUN)

SNC4000 > clearReservation 4 value = 0 = 0x0

The above example shows the clearReservation command being used to clear a reservation on a target device at LUN 4.

Be sure to suspend I/O before initiating this command.

cleHelp

The cleHelp command displays a list of the Command Log Event facility commands.

SNC4000 > cleHelp CLE - Command Log Event facility cleShow <lun> - Displays Logged Events for a specific LUN cleShowAll - Displays Logged Events for All LUNs value = 0 = 0x0

cleShow <LUN>

The cleShow command displays the last 64 Command Log events for a device at the specified LUN. This log is not maintained for disk devices because the performance impact is significant. The manufacturer may request the contents of the command log for diagnostic purposes. Information about interpreting these events is not provided.

cleShowAll

The cleShowAll command performs a cleShow for all LUNs. The manufacturer may request the contents of the command log for diagnostic purposes. Information about interpreting these events is not provided.

72 Service Port Command Reference

copyScsiAssign [source channel], [dest channel]

Note

The copyScsiAssign command copies the SCSI assignments from a source channel to a destination channel.

SNC4000 > copyScsiAssign 1,2 value = 0 = 0x0

If you are using Firmware 4.40 on a Fibre Channel blade, this command is unavailable.

csClearLogFile

The csClearLogFile command clears the contents of the event log.

SNC4000 > csClearLogFile value = 0 = 0x0

date

The date command displays the system’s date and the time.

The system may be set to read its local Real Time Clock (see the dateSetFromRTC command) or a remote host. See the rdate “timeserver” command.

The local Real Time Clock can also be synchronized with a remote timeserver See the rtcSetCurrent command.

SNC4000 > date SNC4000 > THU JAN 25 20:32:49 2001

dateSetFromRTC

The dateSetFromRTC command sets the SNC 4000’s RTC as the source of the date display. Use the date command to display the date and time.

SNC4000 > dateSetFromRTC value = 0 = 0x0

deleteScsiAssign [dev ID],[channel], [id],[lun]

Note

The deleteScsiAssign command deletes assignments previously created.

Example 1, below, uses the output of Example 2, next page, to delete assignments from SCSI Channel 2.

Example 1:

SNC4000 > deleteScsiAssign 64,2,0,0 value = 0 = 0x0 SNC4000 > deleteScsiAssign 82,2,0,1 value = 0 = 0x0 SNC4000 > deleteScsiAssign 98,2,0,2 value = 0 = 0x0 SNC4000 > deleteScsiAssign 124,2,0,3 value = 0 = 0x0

When you are using Firmware 4.40 on a Fibre Channel blade, this command is unavailable.

SNC 4000 User’s Guide 73

Example 2:

SNC4000 > showScsiAssign SCSI 2 ID Lun DevId 0 0 64 0 1 82 0 2 98 0 3 124

dhcpClientShow

The dhcpClientShow command displays data received from the DHCP server, including IP addresses, domain names, and IP address lease duration information.

Snc4000 > dhcpClientShow

dhcpDisable

The dhcpDisable command disables DHCP.

SNC4000 > dhcpDisable value = 0 = 0x0

Example: SN9710012704 > dhcpClientShow Domain Name : (null) DNS Addr :

value = 0 = 0x0

dhcpEnable

The dhcpEnable command enables DHCP.

SNC4000 > dhcpEnable value = 1 = 0x1

Example: SN9710012704 > dhcpClientShow DHCP server: 172.16.33.10 Timer T1: 129526 seconds remaining. Timer T2: 226726 seconds remaining. DHCP server name: Boot file name: DNS domain name: adic.com Router discovery enabled. RFC 894 Ethernet encapsulation enabled. Maximum datagram size: 576 Default IP Time-to-live: 64 Interface MTU: 576 ARP cache timeout: 60 Default TCP Time-to-live: 64 TCP keepalive interval: 7200 Client lease origin: 1056992956 Client lease duration: 259200 Client renewal (T1) time value: 129600 Client rebinding (T2) time value: 226800 DHCP server: 172.16.33.10 Assigned IP address: 172.16.34.182

74 Service Port Command Reference

Client subnet mask: 255.255.248.0 Client router solicitation address: 255.255.255.255 Client IP routers: 172.16.32.2 Client DNS name servers:

172.16.9.63

172.16.40.24 Domain Name : adic.com DNS Addr : 172.16.9.63 Client DNS name servers:

172.16.9.63

172.16.40.24

dhcpState

The dhcpState command displays the state of the DHCP server: enabled or disabled.

SNC4000 > dhcpState

diagBoot

This command is used only to transition the SNC 4000 from normal operation to the special diagnostic mode.

CAUTION

It copies the existing bootline to a file in the ffs:mt directory on the SNC 4000 and installs a new bootline directing the SNC 4000 to boot using a special diagnostic startup script ffs:mt/diagnstk.rc. It renames the persistent map file config/device.map as config/device.bak (a new file will be generated after rebooting).Finally, diagBoot issues a reboot command to put the changes into effect.

After completing use of the diagnostic commands, use the normalBoot command to restore your system to normal operation.

diagHelp

The diagHelp command displays a list of the diagnostic commands.

SNC4000 > diagHelp ** Diagnostic commands: Available in Diagnostic Mode Only ** elTest Test Ethernet port w/loop-back cable fcSlotTest <portnum> Test specified Fibre Channel port w/loop-back cable normalBoot Shutdown and restart in normal mode scsiChannelTest <x,y> Test specified SCSI Channels w/loop-back cable

See User’s Guide for more information value = 0 = 0x0

disableCC [option number]

Disable the command and control interface (LUN 0) using the disableCC command. Specify one of two option parameters as follows.

Option Number

1 Hides the Command and Control interface and results in Inquiry data

SNC 4000 User’s Guide 75

Val ue

returning “device not available” for LUN 0.

Option Number

2 Completely disables all Command and Control functions

The SNC 4000 is addressable as a SCSI target device for command and control support. On a FC Interface, this device will be seen as logical unit number 0, (LUN 0). The LUN 0 device returns a device type of 0Ch in an inquiry command, indicating it is a controller device. Controller devices are defined in the SCSI-3 Controller Commands specification (SCC).

In some cases, it may be desirable to disable this feature. If LUN 0 is disabled, then a device type of 2Ch will be returned in an inquiry to LUN 0, indicating that the device is not presently available at this LUN. LUN 0 will remain reserved for the Command and Control interface and will not be allocated to another target device.

Other commands are available for re-enabling the Command and Control interface or reassigning it to a different LUN rather than hiding or disabling it. See the enableCC command and the setSnaCCLun command for further information.

Val ue

CAUTION

SNC4000 > disableCC value = 0 = 0x0 SNC4000 >

If you enter the disableCC command without specifying an option number, it has the same effect as disableCC 1.

enableCC

To restore the capability to send commands to the command and control interface (LUN 0), use the

enableCC command. The command is typically used to re-enable the interface after it was disabled by the disableCC command.

SNC4000 > enableCC value = 0 = 0x0

envMonShow

The envMonShow command lists all of the environmental channel states and their current values. Use the command envMonRangeShow to restrict output to a display of the ranges relevant to each state. The following channels have been defined:

Channel Name Description

Air Inlet Temp Temperature of the air as it enters the unit

IO Processor Temperature Temperature of the IO Processor

Input Power: +5 Volts Voltage level of the +5 input Input Power: +12 Volts Voltage level of the +12 input Local Power: +2.5 Volts Voltage level of the local +2.5 supply Local Power: +3.3 Volts Voltage level of the local +3.3 supply

Fan Fan running (for tachometer fans: RPM of fan)

SNC4000 > envMonShow Description State Value

76 Service Port Command Reference

-------------------------------------------------------Air Inlet Temp Nominal 27 C IO Processor Temp Nominal 30 C Input Power: +5 Volts Nominal 5.20 V Input Power: +12 Volts Nominal 12.25 V Local Power: +2.5 Volts Nominal 2.48 V Local Power: +3.3 Volts Nominal 3.29 V Fan Nominal 3245 RPM

All Power Nominal All Temp. Nominal Sample Count 2158

value = 1 = 0x1 snc4000 > envMonRangeShow Air Inlet Temp (C): Nominal: 5 to 45 Warning: 4 <= N < 5 or 45 < N <= 50 Alarm: N < 4 or N > 50

IO Processor Temp (C): Nominal: 5 to 80 Warning: 4 <= N < 5 or 80 < N <= 108 Alarm: N < 4 or N > 108

Input Power: +5 Volts (V): Nominal: 4.94 to 5.35 Warning: 4.83 <= N < 4.94 or 5.35 < N <= 5.46 Alarm: N < 4.83 or N > 5.46

Input Power: +12 Volts (V): Nominal: 11.62 to 12.62 Warning: 11.50 <= N < 11.62 or 12.62 < N <= 12.87 Alarm: N < 11.50 or N > 12.87

Local Power: +2.5 Volts (V): Nominal: 2.40 to 2.58 Warning: 2.36 <= N < 2.40 or 2.58 < N <= 2.62 Alarm: N < 2.36 or N > 2.62

Local Power: +3.3 Volts (V): Nominal: 3.20 to 3.39 Warning: 3.13 <= N < 3.20 or 3.39 < N <= 3.46 Alarm: N < 3.13 or N > 3.46

Fan (RPM): Nominal: 2520 to 3780 Warning: 2205 <= N < 2520 or 3780 < N <= 4095 Alarm: N < 2205 or N > 4095

value = 1 = 0x1

envMonRangeShow

The envMonRangeShow command specifies operational ranges for the SNC 4000's environmental channels. It displays ranges of values associated with the Nominal, Warning, and Alarm states for voltage, temperature, and fan/blower operation according to the channels defined in the envMonShow command:

SNC 4000 User’s Guide 77

SNC4000 > envMonRangeShow Air Inlet Temp (C): Nominal: 5 to 45 Warning: 4 <= N < 5 or 45 < N <= 50 Alarm: N < 4 or N > 50 Air Outlet Temp (C): Nominal: 5 to 50 Warning: 4 <= N < 5 or 50 < N <= 55 Alarm: N < 4 or N > 55 IO Processor Temp (C): Nominal: 5 to 80 Warning: 4 <= N < 5 or 80 < N <= 108 Alarm: N < 4 or N > 108 Input Power: +5 Volts (V): Nominal: 4.94 <= N <= 5.36 Warning: 4.84 <= N < 4.94 or 5.36 < N <= 5.46 Alarm: N < 4.94 or N > 5.46 Input Power: +12 Volts (V): Nominal: 11.00 to 12.93 Warning: 10.75 <= N < 11.00 or 12.93 < N <= 13.18 Alarm: N < 10.75 or N > 13.18 Local Power: +2.5 Volts (V): Nominal: 2.42 to 2.58 Warning: 2.36 <= N < 2.42 or 2.58 < N <= 2.62 Alarm: N < 2.36 or N > 2.62 Local Power: +3.3 Volts (V): Nominal: 3.20 to 3.39 Warning: 3.13 <= N < 3.20 or 3.39 < N <= 3.46 Alarm: N < 3.13 or N > 3.46 Fan : Nominal: 1; Alarm: 0 value = 1 = 0x1

ethAddrGet

The ethAddrGet command displays the IP address of the SNC 4000, specified as 4 decimal numbers separated by periods.

SNC4000 > ethAddrGet IP Address set to 192.168.1.176 value = 0 = 0x0

ethAddrSet

The ethAddrSet command changes the IP address of the SNC 4000. An IP address is specified as 4 decimal numbers separated by periods.

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

If a netmask is required, specify it after the IP address in “dotted decimal” form. For example:

SNC4000 > ethAddrSet "10.0.0.2","255.255.0.0" Inet Mask set to ffff0000 for Ethernet interface Write complete Host Address set to 10.0.0.2 for Ethernet interface value = 0 = 0x0

78 Service Port Command Reference

fcConnTypeGet [port]

The fcConnTypeGet command is used to display the current setting of a FC port’s connection type. See also the fcConnTypeSet command.

Parameter Value Meaning

port 1 The SNC 4000 Connection labeled FC1

connection type 0 Loop

1 Point-to-point

2 Loop preferred

The following example shows how the connection type is displayed when FC port 1 is specified and its connection type is loop.

SNC4000 > fcConnTypeGet 1 value = 0 = 0x0

fcConnTypeSet [port],[connection]

The fcConnTypeSet command is used to set the type of connection for a FC port. See also the fcConnTypeGet command.

Parameter Value Meaning

Port 1 The SNC 4000 Connection labeled FC1

Connection Type 0 Loop

1 Point-to-Point

2 Loop Preferred

The following example shows how to set the FC port connection type to point-to-point.

SNC4000 > fcConnTypeSet 1,1 value = 0 = 0x0

CAUTION

You must issue the fcRestart command or reboot the SNC 4000 for the new setting to take effect. See the fcRestart command for further information.

fcFibreSpeedGet [port]

The fcFibreSpeedGet command displays the requested speed of the FC port. The actual speed can be viewed in the output of the fcShow command. The example below shows that the FC port has a maximum speed of 1 Gb/sec.

SNC4000 > fcFibreSpeedGet 1 value = 1= 0x1

Parameter Value Meaning

port 1 The SNC 4000Connection labeled FC1

SNC 4000 User’s Guide 79

Parameter Value Meaning

value = 0 Speed is set to Autorange

1 Speed is set to 1 Gb/sec

2 Speed is set to 2 Gb/sec

fcFibreSpeedSet [port],[speed]

The fcFibreSpeedSet command sets the FC port speed to 1 Gb/sec or 2 Gb/sec for the FC port. The port can also be set to autorange, as in the example below.

Parameter Value Meaning

Port 1 The SNC 4000 connection labeled FC1

Speed 0 Autorange

1 1 Gb/sec

2 2 Gb/sec

SNC4000 > fcFibreSpeedSet 1,0 value = 0 = 0x0

CAUTION

You must issue the fcRestart command or reboot the SNC 4000 for the new setting to take effect. The initiator and the device must both be capable of the selected speed. See the fcRestart command for further information.

fcGbicShow [port]

The fcGbicShow command displays the SFP information for each installed SFP. Specifying the port number is optional.

Parameter Value Meaning

Port 1 The SNC 4000 connection labeled FC1

SNC4000 > fcGbicShow

-------------------------------------------------------------- Ctlr : Module : Module ID : Code : Information

-------------------------------------------------------------- 1 : 4 : Serial Module Definition Protocol : Connector Type --------------- SC : Nominal Speed ---------------- 2.5 Gb/sec : Link length for 9/125 um ----- 0 meters : Link length for 50/125 um ---- 5500 meters : Link length for 62.5/125 um -- 2700 meters : Vendor Name ------------------ FINISAR CORP. : Vendor OUI ------------------- 009065 : Vendor Part Number ----------- FTR-8519-3-2.5 : Vendor Revision -------------- 1A : Vendor Serial Number --------- B2557JC : Vendor Mfg. Date ------------- 10-26-2000

80 Service Port Command Reference

: RX LOS Implemented ----------- Yes : TX Fault Implemented --------- Yes : TX Disable Implemented ------- Yes

--------------------------------------------------------------

fcPortModeGet [port]

The fcPortModeGet command displays the mode for the specified FC port. The default port mode is Public Target. See also the fcPortModeSet

Parameter Value Meaning

Port 1 The SNC 4000 connection labeled FC1

After the command executes, the number displayed as a value indicates the port mode as follows:

Value Port Mode

1 Private Target

2 Private Initiator

3 Private Target and Initiator

command.

17 Public Target

18 Public Initiator

19 Public Target and Initiator

The following example shows how the connection type is displayed when the FC port is specified and the port mode is Private Target.

SNC4000 >fcPortModeGet 1 value = 1 = 0x1

CAUTION

You must issue the fcRestart command or reboot the SNC 4000 for the new setting to take effect. See the fcRestart command for further information.

fcPortModeSet [port],[mode]

The fcPortModeSet command sets the mode for the specified FC port. See also the fcPortModeGet command.

The default port mode is Public Target. Consequently, if attached to a Fabric device the SNC 4000 will register as a “Target” with the name server. If the port mode is “Private Target,” the SNC 4000 does not register with the name server and the Fabric device will not recognize the SNC 4000 as a Target.

The port must be in Initiator mode if you want the SNC 4000 to scan for target devices on the port. When the port is in “Private Initiator” mode, the SNC 4000 only scans for devices on the local loop. If the port mode is in “Public Initiator” mode, the SNC 4000 also scans for devices attached to a Fabric.

Parameter Value Meaning

Port 1 The SNC 4000 connection labeled FC1

SNC 4000 User’s Guide 81

Parameter Value Meaning

Mode 1 Private Target

2 Private Initiator

3 Private Target and Initiator

17 Public Target

18 Public Initiator

19 Public Target and Initiator

SNC4000 > fcPortModeSet 1 value = 0 = 0x0

CAUTION

You must issue the fcRestart command or reboot the SNC 4000 for the new setting to take effect. See the fcRestart command for further information.

fcRestart [port]

The fcRestart command restarts the specified FC port. You typically use this command to restart the port after changing its configuration settings so that the changes take effect. Issuing this command is an alternative to rebooting the SNC 4000 in order to make the configuration changes take effect.

CAUTION

Parameter Value Meaning

Port 1 The SNC 4000 connection labeled FC1

The following example shows the display when the FC port is specified.

SNC4000 > fcRestart 1 value = 0 = 0x0: Restart of FC Channel 1 succeeded

In order to get the command prompt (e.g. SNC4000 >) to show after you have executed the fcRestart command, you will need to press the Enter key.

This command interrupts traffic.

fcShow [level]

The fcShow command displays the channel status for the FC interface.

Level Meaning

0 or <blank>

1 displays the information displayed below, and appends a break-out

82 Service Port Command Reference

sets the verbosity level to the display in the example below

for each channel that includes Node Type, Node Name, Port Name and Port ID

Level Meaning

2 displays the information included at levels 0 and 1, and appends

loop ID link stats

SNC4000 > fcShow

------------------Fibre Channel Controllers----------------------Ctlr : PCI Addr : ISP : Firmware : Firmware : Loop : Fabric : Port : E xt. : Link Id : Bs Dv Fn : Type : State : Version : ID : Attached : Mode : F IFO : Speed

----------------------------------------------------------------- 1 : 00 07 00 : 2300 : Sync Lost : 3.00.25 : None : No : Targ : N one : 1 Gbps 2 : 00 08 00 : 2300 : Sync Lost : 3.00.25 : None : No : Targ : N one : 2 Gbps

------------------------------------------------------------------------

-----value = 95 = 0x5f = ‘_’

value = 95 = 0x5f = '_'

Ctlr Id Indicates the Port Number for this interface.

PCI Addr The PCI address of the interface, showing bus, device id, and function number.

ISP Type The type of FC Controller.

Firmware State The current state of the interface as reported by the FC controller. Firmware states are

listed below.

Configuration Wait Firmware is not initialized.

Waiting for AL_PA Firmware is performing or waiting to perform loop initialization.

Waiting for login Firmware is attempting port and process logins with all loop ports.

Ready Indicates that the interface is connected and operational and ready to process SCSI

commands. Any other value indicates intermediate states or interface failure.

Sync Lost The firmware has detected a loss-of-sync condition and is re-synchronizing the serial

link receiver. This is the state reported when the FC link does not detect a connection to a FC device.

Error The firmware has detected an unrecoverable error condition.

Nonparticipating The firmware is not participating on the loop since it did not acquire an AL_PA during

initialization.

Failed The firmware is not responding to commands.

Firmware Version The version of firmware on the FC controller.

Loop ID The FC Loop ID for this interface. PtoP indicates a point-to-point connection.

Fabric Attached Indicates whether the port is attached to a Fabric.

Port Mode Indicates whether the port is set to Target or Initiator mode

Ext. FIFO Indicates that FIFOs external to the FC controller are on the board. If they are, their

size in KB will be output into this column.

Link Speed Indicates the actual speed of the connection. This figure is only meaningful when the

Firmware State is reported as Ready.

SNC 4000 User’s Guide 83

CAUTION

If the Firmware State is anything but Ready, the information output by this command will be unreliable.

fcShowDevs

The fcShowDevs command displays information about the devices that are accessible from each FC interface. The display shows the LUN that the SNC 4000 has assigned to each device, the SCSI Channel that the device is attached to, the actual SCSI ID and LUN of the device, the vendor, product, revision and serial number of the device.

SNC4000 >fcShowDevs Targets Visible to Hosts on FC 1: LUN Chan Id Lun Vendor Product Rev SN

---------------------------------------------------- 0 0 0 0 ADIC Scalar SNC 413* 601526 1 1 6 0 ADIC Scalar 100 100A ADIC_1_07032002002 2 1 1 0 IBM ULT3580-TD1 22U0 6811088354 22 2 2 0 IBM ULT3580-TD1 22U0 6811085725fcShowNames

fcShowNames

The fcShowNames command displays the node and port names (addresses) of the FCs.

Ctlr Id Indicates the Channel Number for the interface

PCI Addr The PCI address of the interface, showing bus, device id, and function number.

ISPType The type of FC Controller, ISP2310.

Node Name The FC node name for the SNC 4000.

Port Name The FC port name for the interface.

fcTxDisable [port]

The fcTxDisable command disables a FC port transmitter.

Parameter Value Meaning

Port 1 The SNC connection labeled FC1

SNC4000 > fcTxDisable 1 value = 0 = 0x0

fcTxEnable [port]

The fcTxEnable command enables or re-enables a FC port transmitter

Parameter Value Meaning

Port 1 The SNC connection labeled FC1

SNC4000 > fcTxEnable 1 value = 0 = 0x0

84 Service Port Command Reference

gateAddrGet

The gateAddrGet command displays the default network gateway address if one has been set. This address is used when connections are made to a different subnet and there are no explicit routes defined for that subnet. Consult your network administrator for more information on the default gateway (sometimes referred to as default router) address.

SNC4000 > gateAddrGet Gateway Address set to 192.168.1.1 value = 0 = 0x0

gateAddrSet

The gateAddrSet command changes the default network gateway address. This address is used when connections are made to a different subnet and there are no explicit routes defined for that subnet. Consult your network administrator for more information on the default gateway (sometimes referred to as default router) address.

Successful gateAddrSet:

SNC4000 > gateAddrSet "10.0.0.1" value = 0 = 0x0

Failed gateAddrSet (1):

The following message is received when trying to set a new gateway address and that address is currently unreachable. The following message is sent to the terminal.

SNC4000 > gateAddrSet "10.0.0.1" gateAddrSet: Error setting current gate addr: S_errno_ENETUNREACH value = -1 = 0xffffffff = payloadChecksum + 0xffd418a3

The new gateway address is written to the bootup parameters to be used at the next boot. If at next boot, the address is reachable, then it will be written to the system file. If at next boot the gateway address is not reachable and therefore not written to the system file, the following message is displayed:

Failed gateAddrSet (2):

SNC4000 > gateAddrSet "172.16.76.1" gateAddrSet: Error deleting old gateway addr: S_errno_ESRCH Gateway Address set to 172.16.76.1 for Ethernet interface value = 0 = 0x0

ghostIOSet [ticks]

The ghostIOSet command changes the number of ticks that a command remains queued for transmissions to the target. Each tick is 1/60th of a second. The number of ticks can be set from 1 to 60. If ticks are set to 0, command queuing is disabled.

Parameter Value Valid Range Meaning

Ticks 1/60th of a second 0-60 Number of ticks commands remain

in queue

SNC > ghostIOSet 30 Ghost I/O support is enabled. Stale commands will be deleted after 30 ticks (500 ms). value = 30 = 0x1e SNC >

SNC 4000 User’s Guide 85

ghostIOShow

The ghostIOShow command displays the current status of command queuing. The value 0 is returned when command queuing is disabled. Otherwise the number of ticks that commands remain in queue is displayed.

SNC > ghostIOShow Ghost I/O is disabled. value = 0 = 0x0 SNC >

help

The help command displays a list of the shell commands.

SNC4000 > help

help Print this list cleHelp Print Command Log Entry info diagHelp Print Diagnostic Help info hlthChkHelp Print Health Check Help info ioHelp Print I/O Utilities Help info mapHelp Print Device Map Help info netHelp Print Network Help info snmpHelp Print SNMP Help info userHelp Print User account info h [n] Print (or set) shell history pwd Print working path shellLock Lock or unlock shell command interface version Print Version info whoami Print user name clearReservation [devId] Clear reservation on a target (may reset target) diagBoot Shutdown and restart in diagnostic mode initializeBox Delete all device maps, restore factory defaults, reboot ridTag ["value"] Display and set serial number of replaced base unit disableCC [option] Disable Command and Control Interface option 1 - Report as Invalid (AIX mode) option 2 - Fully disabled enableCC Enable Command and Control Interface scsiRescan [chan] Rescan SCSI Channel (all if chan not specified) scsiShow Display info for SCSI Channels fcShow Display info for Fibre Channels fcShowDevs Display devices available on each Fibre Channel fcShowNames Display Node and Port names for Fibre Channels hostTypeShow Display Default Host Type settings loggerDump [count] Display Logger Dump Records loggerDumpCurrent [level] Display Logger Dump Records for current boot reboot Shut down and restart reset Restart without shut down setFcFrameSize [chan],[size] Set FC Frame Size setFcHardId [chan],[id] Set FC Loop ID setHost [chan],["OS"] Set default host type for FC Channel OS may be "aix", "nt", "solaris","hpux" setSnaCCLun Set LUN for Controller Device (typically zero) showBox Display graphic of current hardware configuration sysConfigShow Display System Config Parameters sysVpdShow Display Vital Product Data

86 Service Port Command Reference

sysVpdShowAll Display Vital Product Data for all subsystems targets List all known target devices uptime Display time since last boot

See User’s Guide for more infomation

value = 39 = 0x27 = ‘’’

hlthChkHelp

The hlthChkHelp command displays a list of the Health Check commands.

SNC4000 > hlthChkHelp hlthChkIntervalGet - Show Check Interval hlthChkIntervalSet <interval> - Set Check Interval hlthChkLevelGet - Show Check Level hlthChkLevelSet <level> - Set Check Level hlthChkNow - Run Health Check Now

See User’s Guide for more information

value = 0 = 0x0

hlthChkIntervalGet

The current Health Check interval can be viewed using the hlthChkIntervalGet command. The example below shows the current interval is 60 minutes.

SNC4000 > hlthChkIntervalGet value = 60 = 0x3c = '<'

hlthChkIntervalSet

The Health Check interval controls how often the Health Check process runs. The interval may range from 1 to 65,535 minutes (about 45 days). Set the interval using the hlthChkIntervalSet command.

SNC4000 > hlthChkIntervalSet 60 value = 0 = 0x0

hlthChkLevelGet

To display the current Health Check level, use the hlthChkLevelGet command. The example below shows that the current level is 2.

SNC4000 > hlthChkLevelGet value = 2 = 0x02

hlthChkLevelSet

To set the Health Check level, use the hlthChkLevelSet command. The example below shows setting the level to 3.

SNC4000 > hlthChkLevelSet 3 value = 0 = 0x0

hlthChkNow

The hlthChkNow function causes the SNC 4000 to execute an immediate, level 4 Health Check. Results are displayed that will indicate which devices or subsystems failed the check.

SNC 4000 User’s Guide 87

SNC4000 > hlthChkNow Health Check: Starting level 4 check Health Check: Step 1 -- Checking System Health Check: Step 2 -- Checking Interfaces Health Check: Step 3 -- Checking Devices Health Check: Step 4 -- Checking Device States Health Check: Passed

value = 0 = 0x0

host “add”,“hostname”,“ipAddress”

The host “add” command adds the named host to the host table and host file. If the IP address is already assigned to a host, then the new name is added as an alias for the host. The host “add” command is invoked to add known hosts and their IP addresses. Alias names are supported, allowing multiple names to a single host.

The host utilities maintain a host file, nvfs:/mgnt/hosts, which is used at system startup to initialize the network hosts table. This table associates network names with IP addresses. Use of the hosts table is entirely optional, but might facilitate frequently needed connections. Each host entry is a single line of the format:

IP-address official_host_name nicknames ...

where

IP-address is a text string in standard IP Address format (i.e., 10.0.0.2).

official_host_name is the first name selected for this host.

nicknames is an optional list of additional aliases for the host (separated by spaces).

The following is an example of host file contents.

192.168.1.90 bruno

200.0.0.42 socrates

200.0.0.45 plato

200.0.0.47 fred

Note

SNC4000 > host "add","plato","200.0.0.45"

The host file does not exist until you enter the host “add” command.

host “delete”,“hostname”

The host “delete” command deletes the named host from the hosts table and hosts file. If the hostname is an alias, then only the alias is removed. If hostname is the official host name, the entry and

all aliases are removed.

IP-address official_host_name nicknames ...

where

IP-address is a text string in standard IP Address format (i.e., 10.0.0.2).

official_host_name is the first name selected for this host.

88 Service Port Command Reference

nicknames is an optional list of additional aliases for the host (separated by spaces).

The following is an example of host file contents.

192.168.1.90 bruno

200.0.0.42 socrates

200.0.0.45 plato

200.0.0.47 fred

SNC4000 > host "delete", "plato"

host “list”

The host “list” command prints the content of the hosts file.

IP-address official_host_name nicknames ...

where

IP-address is a text string in standard IP Address format (i.e., 10.0.0.2).

official_host_name is the first name selected for this host.

nicknames is an optional list of additional aliases for the host (separated by spaces).

The following is an example of host file contents.

SNC4000 > host "list"

192.168.1.90 bruno

200.0.0.42 socrates

200.0.0.45 plato

200.0.0.47 fred value = 0 = 0x0

hostNameSet

The hostNameSet command changes the network name of the SNC 4000. The shell prompt will be set to the new host name.

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

hostShow

The hostShow command displays the IP address and alias (if any) of the unit processing the hostShow command, the localhost and the timeserver host.

SNC4000 > hostShow hostname inet address aliases

-------- ------------ ------localhost 127.0.0.1 SNC4000 172.16.38.48 host 172.16.1.1 value = 0 = 0x0

SNC 4000 User’s Guide 89

hostTypeShow

The hostTypeShow command displays the host type setting for each FC. The possible host types are AIX, Gateway, ADIC SNC, HP-UX, Linux, NT (includes Windows 2000), Netware, Generic, Solaris, Autosense/NT, or Dell PV-132T-FC.

SNC4000 > hostTypeShow FC 1: Type 1 - nt

icmpstatShow

The icmpstatShow command displays ICMP statistics for the Ethernet network. Interpreting these statistics requires detailed knowledge of Internet networking protocols. This information may be useful to the LAN administrator.

SNC4000 > icmpstatShow ICMP: 0 call to icmp_error 0 error not generated because old message was icmp 0 message with bad code fields 0 message < minimum length 0 bad checksum 0 message with bad length 0 message response generated value = 30 = 0x1e

ifShow

The ifShow command is used to show the Ethernet port parameters and status as shown below. The SNC 4000 will show two devices. ibmEmac is the Ethernet port. lo is the local loopback port.

SNC4000 > ifShow ibmEmac (unit number 0): Flags: (0x8063) UP BROADCAST MULTICAST ARP RUNNING Type: ETHERNET_CSMACD Internet address: 172.16.38.48 Broadcast address: 172.16.255.255 Netmask 0xffff0000 Subnetmask 0xffff0000 Ethernet address is 00:00:60:00:00:00 Metric is 0 Maximum Transfer Unit size is 1500 0 octets received 0 octets sent 2354 packets received 2 packets sent 2354 unicast packets received 1 unicast packets sent 0 non-unicast packets received 1 non-unicast packets sent 0 input discards 0 input unknown protocols 0 input errors 102 output errors 0 collisions; 0 dropped lo (unit number 0): Flags: (0x8069) UP LOOPBACK MULTICAST ARP RUNNING Type: SOFTWARE_LOOPBACK Internet address: 127.0.0.1 Netmask 0xff000000 Subnetmask 0xff000000

90 Service Port Command Reference

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

inetstatShow

The inetstatShow command displays statistics about Internet protocol sockets for the Ethernet network. Interpreting these statistics requires detailed knowledge of Internet networking protocols. This information may be useful to the LAN administrator.

SNC4000 > inetstatShow Active Internet connections (including servers) PCB Proto Recv-Q Send-Q Local Address Foreign Address (state)

----- ----- ------ ------ ------------------ ------------------ ------1f43fa4 TCP 0 0 0.0.0.0.52787 0.0.0 .0.0 1f43e9c TCP 0 0 0.0.0.0.23 0.0.0.0.0 1f43e18 TCP 0 0 0.0.0.0.21 0.0.0.0.0 1f43c08 TCP 0 0 0.0.0.0.513 0.0.0.0.0 1f43f20 UDP 0 0 0.0.0.0.161 0.0.0.0.0 value = 1 = 0x1 SNC4000 > SNC4000 > SNC4000 > ipstatShow total 792 badsum 0 tooshort 0 toosmall 0 badhlen 0 badlen 0 infragments 0 fragdropped 0 fragtimeout 0 forward 0 cantforward 672 redirectsent 0 unknownprotocol 0 nobuffers 0 reassembled 0 outfragments 0 noroute 0 value = 1 = 0x1

initializeBox

The initializeBox command removes configuration files, such as management configuration and SCSI device maps, and then prompts to reboot.

CAUTION

SNC 4000 User’s Guide 91

Use this function with care as data may be lost as a result of devices moving to different LUNs when the mapping database is removed. Make sure all I/O has been stopped.

ipstatShow

The ipstatShow command displays Internet protocol statistics for the Ethernet network. Interpreting these statistics requires detailed knowledge of Internet networking protocols. This information may be useful to the LAN administrator.

SNC4000 > ipstatShow total 20012 badsum 0 tooshort 0 toosmall 0 badhlen 0 badlen 0 infragments 0 fragdropped 0 fragtimeout 0 forward 0 cantforward 16920 redirectsent 0 unknownprotocol 2 nobuffers 0 reassembled 0 outfragments 0 noroute 0

value = 1 = 0x1

licenseShow

The licenseShow command displays information about software license keys that are installed and the corresponding features that are available. The following example shows an SNC 4000 that contains a license key for the SFM and Data Mover Module features.

SNC4000 > licenseShow License "24Z48-3P3MN-6SAV9": Valid Features: Scalar Firewall Manager - SFM (TM), ADIC Management Console(TM).loggerDump [number]

loggerDump [number]

Dump records from the system event log to the console using the loggerDump command. A numeric parameter may be used to indicate the number of events to display. With no parameter specified, all events in the log file are displayed starting with the most recent events.

SNC4000 > loggerDump *** Dumping 10 of 10 records *** SEQUENCE TIME CODE DESCRIPTION 0001 FEB 21 2002 17:58:06 31 NOTICE: LOGGING STARTED 0002 FEB 21 2002 17:58:06 14 CS 1: Rev. 4.11.05 Built Feb 5 2002, 18:03:37 0003 FEB 21 2002 17:58:12 14SFM1: Enabled: State = Active, Hosts = 1 0004 FEB 21 2002 17:58:12 14 FCAL 1: External FIFO depth is unknown (0x0700) 0005 FEB 21 2002 17:58:12 14 FCAL 2: External FIFO depth is unknown (0x0700) 0006 FEB 21 2002 17:58:13 14 FCAL 1: LIP Initiated 0007 FEB 21 2002 17:58:13 14 FCAL 2: LIP Initiated 0008 FEB 21 2002 17:58:13 28 USCSI 2: Bus RESET

92 Service Port Command Reference

0009 FEB 21 2002 17:58:13 14 System 0: ES 1 CC 0/0 Prd 2 Snp 1 HP 1 fMax 254 RstI 0

loggerDumpCurrent [level]

Dump records from the system event log to the console with the loggerDumpCurrent command. Only records logged since the system was booted are dumped. Level specifies the event log level for the events as follows:

Number Level Explanation

0 Notice 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

SNC4000 > loggerDumpCurrent 2 *** Dumping 5 current records (of 13 total) with level <= 2 *** SEQUENCE TIME CODE DESCRIPTION 0007 FEB 26 2002 19:01:14 28 USCSI 2: Bus RESET 0010 FEB 26 2002 19:01:14 29 Mapping 1: Target Device Added: index 0 , handle 0x08fda380 0012 FEB 26 2002 19:01:26 29 Mapping 1: Target Device Added: index 1 , handle 0x09ffcf08 0013 FEB 26 2002 19:01:27 70 NOTICE: Reboot Complete value = 0 = 0x0 SNC4000 >

ls or ll

The SNC 4000 contains a file system in its flash memory. Use the ls command to display the files as shown below.

SNC4000 >ls license.dat sna.rc vxWorks.stvalue = 0 = 0x0

To obtain detailed information about the file, use the ll command instead.

macShow

The macShow command displays the Media Access Control (MAC) address for the Ethernet interface.

SNC4000 > macShow Enet MAC Address: 0.60.45.d.0.80 value = 33 = 0x21 = '!'

SNC 4000 User’s Guide 93

mapCompressDatabase

CAUTION

Occasionally, it may be necessary to eliminate inactive entries and reorder the active entries in the Persistent Device Map database. The mapCompressDatabase command removes entries for devices that are no longer present and reassigns existing device entries to new addresses. The devices will be assigned new addresses immediately and hosts must rescan for devices or be rebooted.

This may be required when a host system has a limited number of logical units that may be supported, and changing devices on the SNC 4000 has caused the logical unit numbers to increase beyond the host’s supported level.

When you run this command you will be given the option of also clearing the SFM access settings. Because devices will be assigned new addresses, clearing the SFM database ensures that hosts will not have access to the wrong LUNs. Accepting this option requires that the system administrator must reassign SFM access permissions between the hosts and LUNs.

SNC4000 > mapCompressDatabase

CAUTION: This command will compress the Persistent Device Map. Existing SFM Access Settings may become invalid and should be cleared because LUN assignments may change! Do you want to compress the Device Map? (y or n) y 0xc1689ac0 (tShell): Wrote 23 device maps to file 'nvfs:config/device.map' Device Map Compressed

- Do you want to clear SFM Access Settings? (y or n) y SFM Access Cleared value = 23 = 0x17

Compressing the map database will cause device addresses to change unpredictably. Use this command only when no host systems are expecting devices to remain at their current addresses.

If you have not been using SFM, the output of this command will not reference SFM.

SNC4000 > mapCompressDatabase This command will compress the Persistent Device Map.

Do you want to compress the Device Map? (y or n) y 0xc1689ac0 (tShell): Wrote 23 device maps to file 'nvfs:config/device.map' Device Map Compressed value = 23 = 0x17

mapHelp

The mapHelp command displays a list of the persistent address map database commands.

SNC4000 > mapHelp mapCompressDatabase - Compress Device Map Database (reboot required) mapRebuildDatabase - Rebuild Device Map Database (reboot required) mapShowDatabase - Show the Map Database mapShowDevs - Show currently attached devices mapWinnowDatabase - Remove unattached devices from database

See User’s Guide for more information

value = 0 = 0x0

SNC >

94 Service Port Command Reference

Quantum SNC 4000 User Manual

Specifications and Main Features

Frequently Asked Questions

User Manual

SNC 4000 Introduction

Intended Audience

Document Organization

Associated Documents

Explanation of Symbols and Notes

Environmental Notices and Statements

Product Recycling

Lithium Battery

Laser Safety

Usage Restrictions

Technical Assistance

Description

Overview

Configuration Support

Address Mapping

Interface Protocol Awareness

FC Interface

Ethernet

Service Port

LED Indicators

S1 and S2

Firmware 4.40 Features

Multi-path Mapping

WWN Change Capability

DHCP

Supported Platforms

Supported Devices

Operating Specifications

Operating Environment

Power Consumption

ADIC Management Console

Getting Started

Unpacking and Inspecting

Pre-Installation

Installation

Setting the Time and Date

Adding a Host System Running Timeserver

Synchronizing the Real Time Clock with the Timeserver

Disabling the Timeserver Host

Post Installation

Configuration Files

Saving a Configuration File

Loading a Configuration File

Updating Firmware

Scalar Firewall Manager

Host Registration Service

Installing the Host Registration Service

Adding a Host to the SAN Configuration

Attaching a New Host to the SAN

Adding a Host Before Attaching it to the SAN

Removing a Host from the SAN Configuration

Combining SFM with Channel Zoning

Connecting to the Service Port

Service Port Connections

Connecting the Service Terminal

Hardware Required

Connecting using HyperTerminal

Connecting using Telnet

Create User Accounts for Telnet Access

Unlock the Shell

Using Telnet

Verifying the Connection

Removal and Replacement Procedures

Handling Electrostatic Discharge-Sensitive Parts

Removing and Replacing the SFP

Removing the SFP

Replacing the SFP

Before Removing or Replacing the SNC

Removing and Replacing the SNC

Removing the SNC

Replacing the SNC

Final Diagnostic Tests

Final Test Preparation

Fibre Channel Tests

Test Fibre Channel Port

Test SCSI Port 1 and 2