Quantum SNC FIRMWARE 5, SNC FIRMWARE 4 User Manual

Quantum SNC Firmware 4 and 5

6-00676-05

Quantum SNC Firmware 4 and 5

SNC

Firmware

Reference Guide Reference Guide Reference Guide Reference Guide

Quantum SNC Firmware 4 and 5 Reference Guide, 6-00676-05, Ver. A, March 2007, Made in USA.

Quantum Corporation provides this publication “as is” without warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability or fitness for a particular purpose. Quantum Corporation may revise this publication from time to time without notice.

Your right to copy this manual is limited by copyright law. Making copies or adaptations without prior written authorization of Quantum Corporation is prohibited by law and constitutes a punishable violation of the law.

TRADEMARK STATEMENT

Quantum, DLT, DLTtape, the Quantum logo, and the DLTtape logo are all registered trademarks of Quantum Corporation.

SDLT and Super DLTtape are trademarks of Quantum Corporation.

Other trademarks may be mentioned herein which belong to other companies.

1 About This Guide and Your Product 1

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

Other Documents you Might Need . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Getting More Information or Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

2 Description 3

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

Firmware 4 and 5 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Data Path Conditioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

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

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

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

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

Alien Firmware Download Prevention . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Enhanced Data Streaming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

3 Setup and Configuration Routines 7

Preparing SAN Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Preparing Fibre Channel Hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Preparing Fibre Channel Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Preparing SCSI Tape or Disk Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Preparing SCSI Hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Preparing FC Tape or Disk Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Configuring a Fibre Channel Host SAN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Configuring a SCSI Host SAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Configuring the Ethernet Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Using DHCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Setting the Date and Time. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Setting the Real Time Clock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Adding a Host System Running Timeserver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Disabling the Timeserver Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

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

Creating User Accounts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Configuring Ports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Mapping Multiple Paths to Targets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Configuring Channel Zoning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

SNC Firmware 4 and 5 Reference Guide iii

Configuring VPM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Configuring eVPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Using the WWN Lock Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Configuring Host Port Failover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Replacing a SCSI Drive. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Saving a Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Updating Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Loading a Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Changing the WWN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

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

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

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

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

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

Retrieving Information About Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Event Log Dump . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Retrieving the Code 43 Dump File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Working With Command Flow Log Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

4 Service Port Command Reference 41

Managing the SNC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

5 Diagnostic Command Reference 155

Boot Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155

Entering Diagnostic Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155

Diagnostic Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156

Restoring Normal Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159

6 Troubleshooting 161

Event Codes and Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162

Checking Event Logs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162

Checking Reported Event Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163

Action Reference Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166

Start MAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167

Visually Inspecting the LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167

Checking for Problems on Attached Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168

Checking Host Versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168

Checking SNC Product Versions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169

Checking ADIC Management Console Version. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169

Checking Firmware Code Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169

Checking Hardware Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169

Checking Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169

Performing Health Check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170

Checking the Host Event Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170

Database Full MAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170

Device Access MAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171

Checking Fibre Channel Port Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171

iv Contents

Checking SCSI Channel Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171

Checking Channel Zoning Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171

SCSI Channel MAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172

Getting SCSI Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172

Checking Attached SCSI Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173

Comparing Listed versus Physical Devices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173

Comparing Listed versus Supported Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173

Checking SCSI Bus Termination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173

Checking for Multiple SCSI IDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174

Checking Device Type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174

Examining SCSI Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175

Examining SCSI Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175

Performing SCSI Health Check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176

Performing SCSI Loop Back Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176

Testing SCSI Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177

Isolating SCSI devices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177

Restoring SCSI Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178

Fibre Channel MAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178

Verifying Fibre Channel Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178

Testing the GBIC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179

Examining Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179

Performing Fibre Channel Loop Back Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179

Testing Fibre Channel Optical Cable. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180

Replacing Fibre Channel Cable. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180

Replacing Fibre Channel Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180

MAP for the SNC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181

Observing Operational LED Behavior . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181

Temperature MAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181

Interpreting Problems in the Temperature Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181

Receiving Temperature Warnings or Alarms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182

Receiving Fan Speed Warnings or Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182

Power MAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182

Ethernet MAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183

Service Port MAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187

Check the RS-232 Cable. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187

Checking the Connection with Boot Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187

VPM MAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187

Checking Virtual Private Map Access Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188

Verifying SCSI Host Configuration Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188

Verifying VPM Device Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189

SFM/VPS/eVPS MAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189

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

Verifying FC Host Configuration Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190

Removing an FC Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191

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

A Vendor Unique Codes 193

B Glossary 195

SNC Firmware 4 and 5 Reference Guide v

vi Contents

About This Guide and Your Product

WARNING

CAUTION

Note

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

Explanation of Symbols and Notes

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

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

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

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

Getting More Information or Help

StorageCare™, Quantum's comprehensive service approach, leverages advanced data access and diagnostics technologies with cross-environment, multi-vendor expertise to resolve backup issues faster and at lower cost.

Accelerate service issue resolution with these exclusive Quantum StorageCare services:

• Service and Support Website -- Register products, license software, browse Quantum Learning courses, check backup software and operating system support, and locate manuals, FAQs, firmware downloads, product updates and more in one convenient location. Benefit today at

www.quantum.com/support

• eSupport -- Submit online service requests, update contact information, add attachments, and receive status updates via email. Online Service accounts are free from Quantum. That account can also be used to access Quantum's Knowledgebase, a comprehensive repository of product support information. Sign up today at www.quantum.com/esupport

• StorageCare Guardian -- Securely links Quantum hardware and the diagnostic data from the surrounding storage ecosystem to Quantum's Global Services Team for faster, more precise root cause diagnosis. StorageCare Guardian is simple to set up through the internet and provides secure, two-way communications with Quantum's Secure Service Center. More StorageCare Guardian information can be found at www.quantum.com/guardian

For further assistance, or if training is desired, contact Quantum Technical Assistance Center:

North America: +1-800-284-5101

UK, France and Germany: 00800 4 QUANTUM

EMEA: +44 1256 848 766

For worldwide support: www.quantum.com/contactsupport

For the most updated information on Quantum Global Services, please visit www.quantum.com/support

2 About This Guide and Your Product

Description

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

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

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

Compatible SNC Hardware

This SNC firmware is the operational firmware for:

• SNC 4000, 5000, 6000, and 7000 series

• Pathlight 5000 and Pathlight VX solutions

• Fibre Channel I/O blades in intelligent libraries ("i" series libraries, such as the Scalar i2000 Library and Scalar i500 Library)

The version of SNC firmware depends on which SNC blade the library uses:

• SNC Firmware 4 is the operational firmware for SNC 4000, 5000, and 6000 series blades, such as the SNC 6404 blade in the Scalar i2000.

• SNC Firmware 5 is the operational firmware for SNC 7000 series blades, such as the SNC 7404 blade in the Scalar i2000 and Scalar i500.

SNC Firmware 4 and 5 Reference Guide 3

Firmware 4 and 5 Features

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

Data Path Conditioning

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

Multi-Path Mapping

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

WWN Change Capability

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

eVPS

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

Fibre Channel Host Port Failover

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

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

4 Description

Alien Firmware Download Prevention

The SNC firmware now prevents the wrong POST image from being programmed into flash.

Enhanced Data Streaming

Enhanced Data Streaming is a function to allow continuous activity on all Fibre Channel ports. It is primarily used for environmental testing, but it is also useful for testing at customer sites.

SNC Firmware 4 and 5 Reference Guide 5

6 Description

Setup and Configuration Routines

CAUTION

The procedures in this section are not intended to be used with Fibre Channel Blades (FCBs) in intelligent libraries ("i" series libraries, such as Scalar i2000 and Scalar i500) or Pathlight VX systems. Use the appropriate graphical user interface.

This section contains detailed procedures for basic configuration:

• Preparing SAN Components

• Configuring a Fibre Channel Host SAN

• Configuring a SCSI Host SAN

• Configuring the Ethernet Network

• Using DHCP

• Setting the Date and Time

• Creating User Accounts

• Configuring Ports

For using special features:

• R

eplacing a SCSI Drive

• Configuring Channel Zoning

• Configuring Host Port Failover

• Configuring eVPS

• Using the WWN Lock Mode

• Configuring Host Port Failover

For maintaining and troubleshooting the SNC:

• R

eplacing a SCSI Drive

• Saving a Configuration File

• Updating Firmware

• Loading a Configuration File

• Changing the WWN

SNC Firmware 4 and 5 Reference Guide 7

• Retrieving Information About Events

Preparing SAN Components

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

• Has desktop or rack mount hardware installed

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

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

Preparing Fibre Channel Hosts

Make sure that the host systems:

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

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

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

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

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

Preparing Fibre Channel Switch

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

• The switch or subsystem has been configured

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

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

• The FC cables are secured

• The switch is turned on and operational

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

Preparing SCSI Tape or Disk Devices

If SCSI devices are being used, make sure that:

• SCSI IDs have been configured

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

• The SCSI cables have adequate strain relief

• The SCSI cables are secured with mounting screws

8 Setup and Configuration Routines

• The SCSI devices are turned on and operational

CAUTION

Note

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

Preparing SCSI Hosts

Make sure that the host systems:

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

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

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

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

• Are turned on

Preparing FC Tape or Disk Devices

If FC devices are being used, make sure:

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

• That the FC cables have adequate strain relief

• That the FC cables are secured

• That the FC devices are turned on and operational

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

Configuring a Fibre Channel Host SAN

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

Do not use this procedure if you are using an FCB in an intelligent library ("i" series library, such as Scalar i2000 and Scalar i500) or Pathlight VX system. Use the appropriate graphical user interface.

To configure the SAN

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

the User’s Guide for your SNC.

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

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

on page 14, or

Allow sufficient time for the SNC to boot up completely.

3 Press the Enter key on the service terminal.

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

SNC Firmware 4 and 5 Reference Guide 9

on page 187.

Within one minute, the RDY LED on most SNCs should start flashing once per second and the done

CAUTION

Note

executing startup script message should be displayed on the service terminal. On the SNC 6101, it may take a little longer.

For the location of the RDY LED, see Figure 1

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

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

on page 92. This command

causes the SNC to reboot.

Only use the initializeBox command on a new or a replacement SNC. This command resets the Fibre and SCSI Channels, clears the device map and the event log, and disables all enabled features.

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

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

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

on page 136.

on page

13.

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

on page 18.

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

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

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

on page 132.

on page 172.

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

information about this command, refer to hostTypeShow

on page 86.

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

Table 1 Host Type Settings for Fibre Channel Ports

Host Type Alias Usage

AIX Not Applicable AIX

AS400 as/400, os/400, os400 AS400

Autosense/NT Not Applicable functions identically to “NT”

NT windows “NT” is the default setting

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

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

HPUX hp-ux HPUX

Linux Not Applicable Linux

Netware Not Applicable Netware

Solaris sun, linux Solaris

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

set by VPS

Unisys Not Applicable Unisys

10 Setup and Configuration Routines

If the hosts to be connected are not the type shown in the output of the command, issue the setHost

CAUTION

Note

command to set the host type for each incorrect Fibre Channel port. For more information about this command, refer to setHost [port],"OS"

9 Turn off the FC host(s).

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

the WWN on page 33.

on page 114.

10 If you are going to configure host port failover (HPF), refer to C

before turning on the FC host(s).

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

12 Turn on the FC host(s).

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

•See Figure 1 series SNC or SNC 6101.

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

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

• If problems persist, go to the Fibre Channel MAP

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

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

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

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

• If you are running the 5000 or 6000 series, look for FW State=Ready for each FC interface. If FW State=Ready, but devices are not all displaying, go to the SCSI Channel MAP

• If you are running 7404, or if any state other than Ready is specified, go to the Fibre Channel MAP on page 178.

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

on page 178.

onfiguring Host Port Failover on page 27

onfiguring Ports

on page 73.

on page 75.

on page 172.

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

system(s) and check again.

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

Configuration File on page 30.

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

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

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

on page 76.

aving a

Configuring a SCSI Host SAN

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

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

SNC Firmware 4 and 5 Reference Guide 11

To configure the SAN

Note

CAUTION

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

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

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

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

Allow sufficient time for the SNC to boot up completely.

3 Press the Enter key on the service terminal.

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

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

For the location of the RDY LED, see Figure 1

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

settings.

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

Only use the initializeBox command on a new or a replacement SNC. This command resets the Fibre and SCSI Channels, clears the device map and the event log, and disables all enabled features.

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

on page 187.

on page 92.

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

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

6 Issue the

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

7 Issue the

on page 125.

8 Issue the

pmFeatureEnable "licensekeystring" on page 140.

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

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

For an example of the targets command and its output, refer to targets target devices to which you have access. The numbers you need are in the "Idx" column. If you are using AMP, targets will appear twice in the list. Do not map any target more than once.

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

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

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

While it is acceptable to enable VPM from the command line by following the procedure specified above, the preferred interface for managing VPM is the graphical user interface.

eplacing a SCSI Drive on page 28.

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

on page 97.

on page 132. Take note of the

on page 136.

10 Configure the Ethernet connection.

For instructions, refer to Configuring the Ethernet Network

12 Setup and Configuration Routines

on page 13.

11 Issue the setScsiAssign command. For more informationabout this command, refer to

CAUTION

Note

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

While it is possible to configure VPM assignments from the command line, the code to be manipulated can be so complex, that users are encouraged to use the graphical user interface.

12 Issue the showScsiAssign command.

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

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

on page 115.

• If results are not as expected, refer to V

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

Configuration File on page 30.

14 Attach the hosts to the SAN.

PM MAP on page 187 or Start MAP on page 167.

aving a

Configuring the Ethernet Network

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

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

To configure an IP address for the SNC

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

the User’s Guide for your SNC.

on page 14, or

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

SNC Firmware 4 and 5 Reference Guide 13

Figure 1 SNC connector and LED panel

Note

CAUTION

Note

RDY LED

FC1 and FC2 connection LEDs

service port

Ethernet port

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

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

2 Issue the hostNameSet

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

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

Step 2 is optional.

3 Configure a static IP address, by issuing the ethAddrSet

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

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

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

foster > ethAddrSet "10.0.0.2", "255.0.0.0"

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

command to set the SNC name.

command to set the host network address.

to specify it.

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

14 Setup and Configuration Routines

When more complicated routing is required, use the route command to specify the destination address,

CAUTION

Note

as a full address (single host) or as an abbreviated subnet address.

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

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

5 Issue the reboot

command to reboot the SNC:

below, before rebooting.

Using DHCP

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

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

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

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

the User’s Guide for your SNC.

on page 14, or

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

3 If you’re using FW 4 and an SNC 4000 or 510x, issue the dhcpEnable command.

4 Reboot the SNC for the change to take effect.

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

address. Refer to bootShow

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

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

on page 55.

SNC Firmware 4 and 5 Reference Guide 15

Setting the Date and Time

CAUTION

Note

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

Setting the Real Time Clock

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

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

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

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

on page 18.

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

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

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

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

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

Use 24 hour time when programming the real time clock.

Use Greenwich Mean Time.

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

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

SNC > dateSetFromRTC value = 0 = 0x0 SNC >

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

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

on page 63:

on page 134.

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

16 Setup and Configuration Routines

value = 0 = 0x0 SNC >

Table 2 Valid Timezone Settings

Timezone GMT offset Associated Areas

UTC 0 Greenwich, England

GMT 0 Greenwich Meridian Time

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

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

MST GMT -7 Mountain Standard Time

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

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

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

ate on page 63.

Adding a Host System Running Timeserver

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

command, refer to setNettime [value]

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

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

about this command, refer to setTimeHost "timeserver"

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

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

information about this command, refer to rdate "timeserver"

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

on page 115.

on page 116.

on page 103.

4 Use the tzSet command to set the timezone

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

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

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

63.

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

SNC Firmware 4 and 5 Reference Guide 17

ate on page

Disabling the Timeserver Host

CAUTION

Note

To disable the timeserver functionality issue the setNettime 0 command.

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

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

Synchronizing the Real Time Clock with the Timeserver

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

information about this command, refer to setTimeHost "timeserver"

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

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

For more information about this command, refer to r

SNC > rtcSetCurrent value = 0 = 0x0 SNC >

tcSetCurrent on page 107.

on page 116.

Creating User Accounts

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

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

To add a user account

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

the User’s Guide for your SNC.

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

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

beginning with user in the Service Port Command Reference

on page 41.

on page 14, or

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

18 Setup and Configuration Routines

Note

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

CAUTION

Note

you specify must be eight or more characters.

Configuring Ports

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

Table 3 Default SNC Channel Settings

Fibre Channels Public, Target, Loop

Host Type: NT

SCSI Channels Initiator

Termination Enabled

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

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

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

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

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

default settings. For example, if your system contains few devices that are capable only of arbitrated loop, the default connection type can be changed to from "loop" to "loop preferred." Refer to Table 4 and Table 5

on page 18.

Ready for attaching FCAL Windows NT or 2000 Hosts

Ready for attaching SCSI disk or tape devices

SNC Firmware 4 and 5 Reference Guide 19

Table 4 Fibre Channel Configuration Quick Reference

FC Device Attachment Required Channel Settings Service Port Commands

FC Host type

NT (default) AIX AS400

setHost [port], “OS”

and

reboot

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

FC Switch Point-to-Point

Target (default)

fcConnTypeSet [port], [connection]

and

fcRestart

FC disk or FC tape device

Loop (default) Initiator

fcPortModeSet [port], [mode]

and

fcRestart

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

Table 5 SCSI channel configuration quick reference

SCSI Device Attachment

Required Channel Settings

Service Port Commands

SCSI Host Target scsiHostChanSet

[channel],[mode]

and

reboot

SCSI disk and tape SCSI Bus shared (dual paths)

SCSI Bus Reset on Power Up Disabled

scsiResetDisableSet [channel],[mode]

and

reboot

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

Termination Disabled scsiTermSet

[channel],[termination]

and

reboot

20 Setup and Configuration Routines

Mapping Multiple Paths to Targets

CAUTION

Note

CAUTION

Note

CAUTION

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

Both automatic and multipath mapping require licensing.

To map multiple Fibre Channel paths to targets

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

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

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

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

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

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

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

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

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

mpFeatureEnable “license” on page 53.

4 Disconnect SNC Fibre Channel cables from the switch.

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

this command, refer to mapWinnowDatabase

on page 18.

on page 100.

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

SNC Firmware 4 and 5 Reference Guide 21

Use manual mode (mapMultipathSet 1) when using special host software. Manual mode exposes

CAUTION

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

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

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

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

For more information about this multipath settings, refer to mapMultipathSet

7 Reconnect SNC Fibre Channel cables to the switch.

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

page 73.

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

configuration that was selected.

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

on page 96.

Configuring Channel Zoning

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

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

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

22 Setup and Configuration Routines

SFM is configured as usual, but the administrator must be aware that SFM does not override channel

CAUTION

Note

CAUTION

zoning. A host must have LUN level access to a drive through SFM, and be bound to the correct SNC FC port. If the host is incorrectly connected to the SNC, the combination of channel zoning and SFM may prevent the host from seeing resources.

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

To configure Channel Zoning

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

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

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

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

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

on page 18.

2 Issue the setFcChanMask command.

Channel Zoning settings take precedence over settings made by VPS/ SFM, and eVPS.

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

Table 6

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

on page 112.

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

Table 6 Common Channel Zoning Configuration Codes

Command String Effect

SNC> setFcChanMask 1,1008 Enables access to SCSI channels 1 - 4 for Fibre

Channel 1

SNC> setFcChanMask 1,1022 Enables access to SCSI channel 1 for Fibre

Channel 1.

SNC> setFcChanMask 1,1021 Enables access to SCSI channel 2 for Fibre

Channel 1.

SNC> setFcChanMask 1,1019 Enables access to SCSI channel 3 for Fibre

Channel 1.

SNC> setFcChanMask 1,1015 Enables access to SCSI channel 4 for Fibre

Channel 1.

SNC> setFcChanMask 1,1020 Enables access to SCSI channels 1-2 for Fibre

Channel 1.

SNC Firmware 4 and 5 Reference Guide 23

CAUTION

Note

Table 6 Common Channel Zoning Configuration Codes (Continued)

Command String Effect

SNC> setFcChanMask 1,1011 Enables access to SCSI channels 3-4 for Fibre

Channel 1.

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

Configuring VPM

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

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

User Guide.

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

You must have a license to use VPM.

To configure VPM

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

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

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

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

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

pmFeatureEnable "licensekeystring" on page 140.

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

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

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

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

on page 18.

on page 132.

on page 115.

5 Issue the showScsiAssign command.

If results are not as expected, refer to V

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

24 Setup and Configuration Routines

PM MAP on page 187.

+ 176 hidden pages

Quantum SNC FIRMWARE 5, SNC FIRMWARE 4 User Manual

Specifications and Main Features

Frequently Asked Questions

User Manual

Contents

About This Guide and Your Product

Explanation of Symbols and Notes

Other Documents you Might Need

Getting More Information or Help

Description

Compatible SNC Hardware

Firmware 4 and 5 Features

Data Path Conditioning

Multi-Path Mapping

WWN Change Capability

eVPS

Fibre Channel Host Port Failover

Alien Firmware Download Prevention

Enhanced Data Streaming

Setup and Configuration Routines

Preparing SAN Components

Preparing Fibre Channel Hosts

Preparing Fibre Channel Switch

Preparing SCSI Tape or Disk Devices

Preparing SCSI Hosts

Preparing FC Tape or Disk Devices

Configuring a Fibre Channel Host SAN

Configuring a SCSI Host SAN

Configuring the Ethernet Network

Using DHCP

Setting the Date and Time

Setting the Real Time Clock

Adding a Host System Running Timeserver

Disabling the Timeserver Host

Synchronizing the Real Time Clock with the Timeserver

Creating User Accounts

Configuring Ports

Mapping Multiple Paths to Targets

Configuring Channel Zoning

Configuring VPM