Qlogic iSR6152 Installation guide

Add to my manuals
122 Pages

advertisement

Qlogic iSR6152 Installation guide | Manualzz

ISR651103-00 C

iSR6152

Intelligent Storage Router

Installation Guide

iSR6152 Intelligent Storage Router

Installation Guide

Information furnished in this manual is believed to be accurate and reliable. However, QLogic Corporation assumes no responsibility for its use, nor for any infringements of patents or other rights of third parties which may result from its use. QLogic Corporation reserves the right to change product specifications at any time without notice. Applications described in this document for any of these products are for illustrative purposes only. QLogic Corporation makes no representation nor warranty that such applications are suitable for the specified use without further testing or modification. QLogic Corporation assumes no responsibility for any errors that may appear in this document.

Document Revision History

Revision A, March 9, 2011

Revision B, April 14, 2011

Revision C, August 11, 2011

Changes Sections Affected

Updated guide to latest QLogic template.

Removed reference to the SmartWrite feature and removed the bullet describing support for two remote SAN islands (SmartWrite not currently supported).

Removed the “Remote SAN Island Connectivity” section (SmartWrite not currently supported).

Renamed “Licensed Features” section and removed reference to SmartWrite (SmartWrite not currently supported)

Removed the “Topology” section (SmartWrite not currently supported).

Removed references to configuring the iSR6152 using SANsurfer iSCSI/FC Router Manager’s Configuration Wizard (Configuration Wizard not currently supported).

All

“Router Capabilities” on page 1-1

Chapter

1 Introduction

“Licensed Feature—Data Migration” on page 1-2

Chapter

2 Planning

“Configuring the Router” on page 3-10

ii ISR651103-00 C

1

Table of Contents

Preface

Intended Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

What’s in This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Related Materials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Documentation Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Communications Statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

xi xii

xiii Federal Communications Commission (FCC) Class A Statement . . .

Canadian Department of Communications Class A Compliance

Statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Avis de conformité aux normes du ministère des Communications du Canada. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

CE Statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

xiii

VCCI Class A Statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Laser Safety Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Electrostatic Discharge Sensitivity (ESDS) Precautions . . . . . . . . . . . . . . .

Accessible Parts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

License Agreements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

General Public License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Preamble . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

xvi

Terms And Conditions For Copying, Distribution, and

Modification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

xvii

How to Apply These Terms to Your New Programs . . . . . . . . . . . . . .

xxii

xv xv

xvi xvi

xiii

xiv

xv xv

Technical Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

xxiii

Training . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

xxiii

Contact Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

xxiv

Knowledge Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

xxiv

ix ix

x

Introduction

Router Capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1-1

Licensed Feature—Data Migration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1-2

Fibre Channel over IP (FCIP). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1-2

ISR651103-00 C iii

iSR6152 Intelligent Storage Router

Installation Guide

2

3

Chassis LEDs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1-3

Input Power LED (Green) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1-3

Heartbeat LED (Green) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1-3

System Fault LED (Amber) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1-3

Chassis Controls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1-4

Maintenance Button. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1-4

Reset a Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1-4

Reset and Select Boot Image. . . . . . . . . . . . . . . . . . . . . . . . . . .

1-5

Reset IP Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1-5

Enable DHCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1-5

Restore Factory Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1-5

Fibre Channel Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1-6

Fibre Channel Port LEDs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1-6

Fibre Channel SFP Transceivers . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1-7

GbE Port LEDs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1-8

Ethernet Management Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1-9

Serial Port. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1-9

Planning

Devices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2-1

Fibre Channel Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2-2

Distance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2-2

Bandwidth . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2-2

Latency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2-3

GbE Performance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2-3

Performance Tuning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2-3

Fibre Channel Switch Ports and Zoning Requirements . . . . . . . . . . . . . . . .

2-7

Multiple Routers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2-7

Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2-7

Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2-7

Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2-8

Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2-8

Installation

Site Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3-1

Management Workstation Requirements . . . . . . . . . . . . . . . . . . . . . .

3-1

Power Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3-2

Environmental Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3-2 iv ISR651103-00 C

4

5

A

iSR6152 Intelligent Storage Router

Installation Guide

Installing the iSR6152 Router. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3-2

Pre-Installation Check List. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3-4

Mounting the Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3-4

Installing the Transceivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3-6

Connecting the Management Workstation to the Router. . . . . . . . . . .

3-6

Configuring the Management Workstation . . . . . . . . . . . . . . . . . . . . .

3-6

Setting the Workstation IP Address . . . . . . . . . . . . . . . . . . . . . .

3-7

Configuring the Workstation Serial Port . . . . . . . . . . . . . . . . . . .

3-7

Installing Router Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3-8

Windows Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3-8

Linux Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3-9

Starting Router Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3-9

Connecting the Router to AC Power . . . . . . . . . . . . . . . . . . . . . . . . . .

3-10

Configuring the Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3-10

Cabling Devices to the Router. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3-11

Installing the Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3-11

Using Router Manager to Install Firmware . . . . . . . . . . . . . . . . . . . . .

3-12

Using the CLI to Install Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3-12

Diagnostics and Troubleshooting

Chassis Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4-1

Input Power LED is Off . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4-2

System Fault LED is On . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4-2

Power-On Self-Test Diagnostics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4-2

LED Blink Patterns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4-2

Heartbeat Blink Pattern . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4-3

System Error Blink Pattern . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4-3

Management Port IP Address Conflict Blink Pattern . . . . . . . . . . . . . .

4-3

Over-Temperature Blink Pattern . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4-4

Recovering a Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4-4

Removal and Replacement

Removing and Replacing SFP Transceivers . . . . . . . . . . . . . . . . . . . . . . . .

5-1

Removing and Replacing the Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5-1

Removing the Router. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5-1

Replacing the Router. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5-2

Simple Network Management Protocol (SNMP)

SNMP Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

A-1

SNMP Trap Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

A-2

ISR651103-00 C v

iSR6152 Intelligent Storage Router

Installation Guide

B

Glossary

Index

Management Information Base (MIB) . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

A-2

System Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

A-3

Network Port Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

A-3

Fibre Channel Port Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

A-6

Sensor Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

A-8

Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

A-10

Notification Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

A-10

Agent Start Up Notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

A-11

Agent Shut Down Notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

A-11

Network Port Down Notification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

A-11

Fibre Channel Port Down Notification . . . . . . . . . . . . . . . . . . . . . . . . .

A-11

Sensor Notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

A-12

Generic Notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

A-12

Log Messages

Informational Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B-1

Application Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B-2

iSCSI Driver. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B-4

Fibre Channel Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B-4

User Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B-6

FCIP Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B-8

TOE Driver. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B-9

System Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B-9

Error Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B-9

Application Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B-10

iSCSI Driver. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B-18

Fibre Channel Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B-19

User Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B-22

System Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B-24

Fatal Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B-24

iSCSI Driver. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B-24

Fibre Channel Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B-27

TOE Driver. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B-29

System Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B-30 vi ISR651103-00 C

iSR6152 Intelligent Storage Router

Installation Guide

List of Figures

Figure Page

1-1 iSR6152 Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1-1

1-2 Chassis LEDs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1-3

1-3 Chassis Controls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1-4

1-4 Fibre Channel Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1-6

1-5 GbE Ports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1-8

1-6 Ethernet Management Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1-9

1-7 Serial Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1-9

3-1 iSR6152 Router and Accessories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3-3

4-1 Chassis Diagnostic LEDs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4-1

List of Tables

Table Page

1-1 System Fault LED Blink Patterns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1-3

1-2 Port LEDs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1-7

2-1 T1 / DS-1—1.554 Mbps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2-3

2-2 T3 / DS-3—45 Mbps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2-4

2-3 DS-5—400 Mbps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2-4

2-5 OC-3—150 Mbps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2-5

2-4 OC-1—50 Mbps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2-5

2-6 OC-12 and Above—621 Mbps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2-6

3-1 Management Workstation Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3-1

3-2 Pre-Installation Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3-4

4-1 System Fault LED Blink Patterns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4-3

A-1 SNMP Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

A-1

A-2 SNMP Trap Configuration Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

A-2

B-1 Application Modules—Informational Log Messages . . . . . . . . . . . . . . . . . . . . . . . .

B-2

B-2 iSCSI Driver—Informational Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B-4

B-3 Fibre Channel Driver—Informational Log Messages. . . . . . . . . . . . . . . . . . . . . . . .

B-4

B-4 User Modules—Informational Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B-6

B-5 FCIP Module—Informational Log Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B-8

B-6 TOE Driver—Informational Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B-9

B-7 System Modules—Informational Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . .

B-9

B-8 Application Modules—Error Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B-10

B-9 iSCSI Driver—Error Log Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B-18

B-10 Fibre Channel Driver—Error Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B-19

B-11 User Modules—Error Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B-22

B-12 System Modules—Error Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B-24

B-13 iSCSI Driver—Fatal Log Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B-25

B-14 Fibre Channel Driver—Fatal Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B-27

B-15 TOE—Fatal Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B-29

B-16 System—Fatal Log Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B-30

ISR651103-00 C vii

iSR6152 Intelligent Storage Router

Installation Guide viii ISR651103-00 C

Preface

This guide describes the features and installation of the QLogic iSR6152

Intelligent Storage Router (iSR6152), also referred to as the iSR6152 router or simply router.

Intended Audience

This guide is for users who are responsible for installing, managing, and servicing the iSR6152 router and the storage area network (SAN) equipment to which it is attached.

What’s in This Guide

This guide contains the information needed to plan for the iSR6152 router, to install and configure the router, software, and firmware, and to troubleshoot possible problems. It also provides details about how the router uses Simple

Network Management Protocol (SNMP), and lists log messages that you may encounter.

This preface specifies the intended audience, explains the typographic conventions used in this guide, and lists related documents. In addition, the preface provides communications statements and safety information, lists accessible parts, defines license agreements, and explains how to obtain technical support.

The remainder of this guide is organized into the following chapters and appendices:

Chapter 1 Introduction describes the features and capabilities of the

iSR6152 router.

Chapter 2 Planning describes how to plan for the iSR6152 router.

Chapter 3 Installation

provides procedures for installing and configuring an iSR6152 router, and installing the firmware.

 Chapter

4 Diagnostics and Troubleshooting provides guidance to diagnostic

information about the router available through the chassis LEDs and the port

LEDs, as well as through Router Manager and command line interface (CLI) event logs and error messages.

ISR651103-00 C ix

x

Preface

Related Materials

Chapter 5 Removal and Replacement

provides procedures for removing and replacing the field replaceable units (FRU): SFP transceivers and iSR6152 routers.

Appendix A Simple Network Management Protocol (SNMP) provides

reference material for the simple network management protocol (SNMP) protocol, which you can use to manage the iSR6152 router using a third-party SNMP management application.

Appendix B Log Messages 

provides reference material on messages logged to a file, which you can retrieve using the Router Manager or CLI.

Following the appendices are a glossary of terms used and an index that will help you quickly find the information you need.

Related Materials

Refer to the following documents for additional information:

iSR6152 Intelligent Storage Router Quick Start Guide

iSR6152 Router CLI User's Guide

iSR6152 Router Manager User's Guide

Internet Protocol, Version 6 (IPv6) Specification, RFC2460

Neighbor Discovery for IP Version 6 (IPv6), RFC2461

IPv6 Stateless Address Autoconfiguration, RFC2462

 Internet Control Message Protocol (ICMPv6) for the Internet Protocol

Version 6 (IPv6) Specification, RFC2463

Transmission of IPv6 Packets over Ethernet Networks, RFC2464

 iSCSI draft standard draft-ietf-ips-iSCSI-20

 Internet engineering task force (IETF) – iSCSI Requirements and Design

Considerations, iSCSI Naming and Discovery, Internet Protocol

Specification (IPv4), RFC793

 Transmission Control Protocol (TCP) Specification, RFC1122, Requirements

for Internet Hosts-Communication Layers

TCP Extensions for High Performance, RFC1323

TCP Congestion Control, RFC2581

NewReno Modification to TCP’s Fast Recovery Algorithm, RFC2582

ISR651103-00 C

Preface

Documentation Conventions

 ANSI SCSI – SCSI-3 Architecture Model (SAM), X3T10/994D/Rev 18,

SCSI-3 Controller Command Set, X3T10/Project 1047D/Rev 6c. IEEE –

802.1Q Virtual LAN (VLAN), 802.1p Priority of Service, 802.3x Flow Control,

802.3ad Link Aggregation

SCSI-3 Fibre Channel Protocol (SCSI-FCP), X3.269:1996

Fibre Channel Physical and Signaling Interface (FC-PH), X3.230:199

Fibre Channel 2nd Generation (FC-PH-2), X3.297:1997

 Third Generation Fibre Channel Physical and Signaling Interface (FC-PH-3),

X3.303:1998, Fibre Channel-Arbitrated Loop (FC-AL-2), working draft, revision 6.4, August 28, 1998

 Fibre Channel Fabric Loop Attachment Technical Report (FC-FLA)

NCITS/TR-20:1998, Fibre Channel-Private Loop Direct Attach Technical

Report (FC-PLDA)

SCSI Fibre Channel Protocol-2 (FCP-2) working draft, revision 3, October1,

1999

Fibre Channel over TCP/IP (FCIP), RFC3821

ANSI Information Technology-SCSI 3 Architecture Model, revision 18,

November 27, 1995

Documentation Conventions

This guide uses the following documentation conventions:

NOTE: provides additional information.

CAUTION! indicates the presence of a hazard that has the potential of causing damage to data or equipment.

WARNING!! indicates the presence of a hazard that has the potential of causing personal injury.

 Text in blue font indicates a hyperlink (jump) to a figure, table, or section in this guide, and links to Web sites are shown in underlined blue . For example:

 Table 9-2 lists problems related to the user interface and remote agent.

 See “Installation Checklist” on page 3-6 .

 For more information, visit www.qlogic.com

.

ISR651103-00 C xi

Preface

Communications Statements

 Text in bold font indicates user interface elements such as a menu items, buttons, check boxes, or column headings. For example:

 Click the Start button, point to Programs, point to Accessories, and then click Command Prompt.

 Under Notification Options, select the Warning Alarms check box.

 Text in Courier font indicates a file name, directory path, or command line text. For example:

 To return to the root directory from anywhere in the file structure:

Type cd /root, and then press ENTER.

 Enter the following command: sh ./install.bin

 Key names and key strokes are indicated with UPPERCASE:

 Press CTRL+P.

 Press the UP ARROW key.

 Text in italics indicates terms, emphasis, variables, or document titles. For example:

 For a complete listing of license agreements, refer to the QLogic

Software End User License Agreement.

 What are shortcut keys?

 To enter the date, type mm/dd/yyyy (where mm is the month, dd is the day, and yyyy is the year).

 Topic titles between quotation marks identify related topics either within this guide or in the help system.

Communications Statements

The following statements apply to this product. The statements for other products intended for use with this product appear in their accompanying manuals.

xii ISR651103-00 C

Preface

Communications Statements

Federal Communications Commission (FCC) Class A

Statement

This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment. This equipment generates, uses, and can radiate radio frequency energy, and, if not installed and used in accordance with the instruction manual, may cause harmful interference to radio communications.

Operation of this equipment in a residential area may cause unacceptable interference, in which case the user will be required to correct the interference at their own expense.

Neither the provider nor the manufacturer is responsible for any radio or television interference caused by unauthorized changes or modifications to this equipment.

Unauthorized changes or modifications could void the user's authority to operate the equipment. This device complies with Part 15 of the FCC Rules. Operation is subject to the following two conditions:

 This device may not cause harmful interference, and

 This device must accept any interference received, including interference that may cause unwanted operation.

Canadian Department of Communications Class A

Compliance Statement

This equipment does not exceed Class A limits for radio emissions for digital apparatus, set out in Radio Interference Regulation of the Canadian Department of Communications. Operation in a residential area may cause unacceptable interference to radio and TV reception requiring the owner or operator to take whatever steps necessary to correct the interference.

Avis de conformité aux normes du ministère des

Communications du Canada

Cet équipement ne dépasse pas les limites de Classe A d'émission de bruits radioélectriques por les appareils numériques, telles que prescrites par le

Réglement sur le brouillage radioélectrique établi par le ministère des

Communications du Canada. L'exploitation faite en milieu résidentiel peut entraîner le brouillage des réceptions radio et télé, ce qui obligerait le propriétaire ou l'opérateur à prendre les dispositions nécwssaires pour en éliminer les causes.

ISR651103-00 C xiii

Preface

Communications Statements

CE Statement

The CE symbol on the equipment indicates that this system complies with the

EMC (Electromagnetic Compatibility) directive of the European Community

(89/336/EEC) and to the Low Voltage (Safety) Directive (73/23/EEC). Such marking indicates that this system meets or exceeds the following technical standards:

 EN60950-1, A11:2004 – “Safety of Information Technology Equipment,

Including Electrical Business Equipment”.

 EN 55022:1998, A1:2000, A2:2003 – “Limits and Methods of Measurement of Radio Interference Characteristics of Information Technology Equipment”.

 EN 55024:1998, A1:2001, A2:2003 – “Electromagnetic compatibility -

Generic immunity standard Part 1: Residential commercial, and light industry.”

 EN 61000-4-2: 1995, A1:1998, A2: 2001 – “Electrostatic Discharge

Immunity Test”

 EN 61000-4-3: 2002 – “Radiated, Radio-Frequency, Electromagnetic

Field Immunity Test”

 EN 61000-4-4: 1995, A1:2001, A2:2001 – “Electrical Fast

Transient/Burst Immunity Test”

 EN 61000-4-5: 1995, A1:2001 – “Surge Immunity Test”

 EN 61000-4-6: 1996, A1:2001 – “Immunity To Conducted

Disturbances, Induced By Radio-Frequency Fields”

 EN 61000-4-8: 1993, A1:2001 – “Power Frequency Magnetic Field

Immunity Test”

 EN 61000-4-11 Second Edition: 2004 – “Voltage Dips, Short

Interruptions And Voltage Variations Immunity Tests”

 EN 61000-3-2: 2000 – “Limits For Harmonic Current Emissions (Equipment

Input Current Less Than/Equal To 16 A Per Phase)” Class A

 EN 61000-3-3: 1995, A1:2001 – “Limitation Of Voltage Fluctuations And

Flicker In Low-Voltage Supply Systems For Equipment With Rated Current

Less Than Or Equal To 16 A” xiv ISR651103-00 C

Preface

Laser Safety Information

VCCI Class A Statement

This is a Class A product based on the standard of the Voluntary Control Council

For Interference by Information Technology Equipment (VCCI). If this equipment is used in a domestic environment, radio disturbance may arise. When such trouble occurs, the user may be required to take corrective actions.

Laser Safety Information

This product may use Class 1 laser optical transceivers to communicate over the fiber optic conductors. The U.S. Department of Health and Human Services

(DHHS) does not consider Class 1 lasers to be hazardous. The International

Electrotechnical Commission (IEC) 825 Laser Safety Standard requires labeling in

English, German, Finnish, and French stating that the product uses Class 1 lasers. Because it is impractical to label the transceivers, the following label is provided in this manual.

Electrostatic Discharge Sensitivity (ESDS)

Precautions

The assemblies used in the switch chassis are ESD sensitive. Observe ESD handling procedures when handling any assembly used in the switch chassis.

Accessible Parts

The following field replaceable units (FRUs) are supported by the iSR6152 router:

 Small form-factor pluggable (SFP) optical transceivers

ISR651103-00 C xv

Preface

License Agreements

License Agreements

Refer to the QLogic Software End User License Agreement for a complete listing of all license agreements affecting this product.

General Public License

QLogic routers are powered by the Linux operating system. A machine-readable copy of the Linux source code is available upon written request to the following address. A nominal fee will be charged for reproduction, shipping, and handling costs in accordance with the General Public License.

QLogic Corporation

26600 Aliso Viejo Parkway

Aliso Viejo, CA 92656

Attention: Technical Support—Source Request

CAUTION!

Installation of software or files not authorized by QLogic will immediately and irrevocably void all warranty and service contracts on the affected units.

The following General Public License has been reproduced with permission from:

GNU General Public License

Version 2, June 1991

Copyright 1989, 1991 Free Software Foundation, Inc.

59 Temple Place – Suite 330, Boston, MA 02111-1307, USA

Preamble

The licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU General Public License is intended to guarantee your freedom to share and change free software - to make sure the software is free for all its users. This General Public License applies to most of the

Free Software Foundation’s software and to any other program whose authors commit to using it. (Some Free Software Foundation software is covered by the

GNU Library General Public License instead). You can apply it to your programs, too.

When we speak of free software, we are referring to freedom, not price. Our

General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for this service if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new programs, and that you know you can do these things.

xvi ISR651103-00 C

Preface

General Public License

To protect your rights, we need to make restrictions that forbid anyone to deny you these rights or to ask you to surrender the rights. These restrictions translate to certain responsibilities for you if you distribute copies of the software, or if you modify it.

For example, if you distribute copies of such a program, whether gratis or for a fee, you must give the recipients all the rights that you have. You must make sure that they, too, receive or can get the source code. And you must show them these terms so they know their rights.

We protect your rights with two steps: (1) copyright the software, and (2) offer you this license which gives you legal permission to copy, distribute and/or modify the software.

Also, for each author’s protection and ours, we want to make certain that everyone understands that there is no warranty for this free software. If the software is modified by someone else and passed on, we want its recipients to know that what they have is not the original, so that any problems introduced by others will not reflect on the original authors’ reputation.

Finally, any free program is threatened constantly by software patents. We wish to avoid the danger that redistributors of a free program will individually obtain patent licenses, in effect making the program propriety. To prevent this, we have made it clear that any patent must be licensed for everyone’s free use or not licensed at all.

The precise terms and conditions for copying, distribution and modification follow.

Terms And Conditions For Copying, Distribution, and

Modification

1.

This license applies to any program or other work which contains a notice placed by the copyright holder saying it may be distributed under the terms of this General Public License. The “Program”, below, refers to any such program or work, and a “work based on the Program” means either the

Program or any derivative work under copyright law – that is to say, a work containing the Program or a portion of it, either verbatim or with modifications and/or translated into another language. (Hereinafter, translation is included without limitation in the term “modification”.) Each licensee is addressed as “you”.

Activities other than copying, distribution and modification are not covered by this License – they are outside its scope. The act of running the Program is not restricted, and the output from the Program is covered only if its contents constitute a work based on the Program (independent of having been made by running the Program). Whether that is true depends on what the Program does.

ISR651103-00 C xvii

Preface

General Public License

2.

You may copy and distribute verbatim copies of the Program’s source code as you receive it, in any medium, provided that you conspicuously and appropriately place on each copy an appropriate copyright notice and disclaimer of warranty; keep intact all the notices that refer to this License and to the absence of any warranty; and give any other recipients of the

Program a copy of this License along with the Program.

3.

You may modify your copy or copies of the Program or any portion of it, thus forming a work based on the Program, and copy and distribute such modifications or work under the terms of Section 1 above, provided that you also meet all of these conditions: a.

You must cause the modified files to carry prominent notices stating that you changed the files and the date of any change.

b.

You must cause any work that you distribute or publish, that in whole or in part contains or is derived from the Program or any part thereof, to be licensed as a whole at no charge to all third parties under the terms of this License.

c.

If the modified program normally reads commands interactively when run, you must cause it, when started running for such interactive use in the most ordinary way, to print or display an announcement including an appropriate copyright notice and a notice that there is no warranty

(or else, saying that you provide a warranty) and that users may redistribute the program under these conditions, and telling the user how to view a copy of this License. (Exception – if the Program itself is interactive but does not normally print such an announcement, your work based on the Program is not required to print an announcement.)

These requirements apply to the modified work as a whole. If identifiable sections of that work are not derived from the Program, and can be reasonably considered independent and separate works in themselves, and then this License, and its terms, do not apply to those sections when you distribute them as separate works. But when you distribute the same sections as part of the whole must be on the terms of this License, whose permissions for other Licensees extend to the entire whole, and thus to each and every part regardless of who wrote it.

Thus, it is not the intent of this section to claim rights or contest your rights to work written entirely by you; rather, the intent is to exercise the right to control the distribution of derivative or collective works based on the

Program.

In addition, mere aggregation of another work not based on the Program with the Program (or with a work based on the Program) on a volume of a storage distribution medium does not bring the other work under the scope of this License.

xviii ISR651103-00 C

Preface

General Public License

4.

You may copy and distribute the Program (or a work based on it, under

Section 2) in object code or executable form under the terms of paragraphs

1 and 2 above provided that you also do one of the following: a.

Accompany it with the complete corresponding machine-readable source code, which must be distributed under the terms of paragraphs

1 and 2 above on a medium customarily used for software interchange

– or, b.

Accompany it with a written offer, valid for at least three years, to give any third party, for a charge no more than your cost of physically performing source distribution, a complete machine-readable copy of the corresponding source code, to be distributed under the terms of paragraphs 1 and 2 above on a medium customarily used for software interchange; or, c.

Accompany it with the information you received as to the offer to distribute corresponding source code. (This alternative is allowed only for noncommercial distribution and only if you received the program in object code or executable form with such an offer, in accord with paragraph b.)

The source code for a work means the preferred form of the work for making modifications to it. For an executable work, complete source code means all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and installation of the executable. However, as a special exception, the source code distributed need not include anything that is normally distributed (in either source or binary form) with the major components (compiler, kernel, and so on) of the operating system on which the executable runs, unless that component itself accompanies the executable.

If distribution of executable or object code is made by offering access to copy from a designated place, and then offering equivalent access to copy the source code from the same place counts as distribution of the source code, even though third parties are not compelled to copy the source along with the object code.

5.

You may not copy, modify, sublicense, or distribute the Program except as expressly provided under this License. Any attempt otherwise to copy, modify, sublicense or distribute the Program is void, and will automatically terminate your rights under this License. However, parties who have received copies, or rights, from you under this License will not have their licenses terminated so long as such parties remain in full compliance.

ISR651103-00 C xix

Preface

General Public License

6.

You are not required to accept this License, since you have not signed it.

However, nothing else grants you permission to modify or distribute the

Program or its derivative works. These actions are prohibited by law if you do not accept this License. Therefore, by modifying or distributing the

Program (or any work based on the Program), you indicate your acceptance of this License to do so, and all its terms and conditions for copying, distributing or modifying the Program or works based on it.

7.

Each time you redistribute the Program (or any work based on the Program), the recipient automatically receives a license from the original Licensor to copy, distribute or modify the Program subject to these terms and conditions.

You may not impose any further restrictions on the recipients’ exercise of the rights granted herein. You are not responsible for enforcing compliance by third parties of this License.

8.

If, as a consequence of a court judgement or allegation of patent infringement or for any other reason (not limited to patent issues), conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot distribute so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, and then, and then as a consequence you may not distribute the

Program at all. For example, if a patent license would not permit royalty-free redistribution of the Program by all those who receive copies directly or indirectly through you, and then the only way you could satisfy both it and this License would be to refrain entirely from distribution of the Program.

If any portion of this section is held invalid or unenforceable under any particular circumstance, the balance of the section is intended to apply and the section as a whole is intended to apply in other circumstances.

It is not the purpose of this section to induce you to infringe any patents or other property right claims or to contest validity of any such claims; this section has the sole purpose of protecting the integrity of the free software distribution system, which is implemented by public license practices. Many people have made generous contributions to the wide range of software distributed through that system in reliance on consistent application of that system; it is up to the author/donor to decide if he or she is willing to distribute software through any other system and a licensee cannot impose that choice.

This section is intended to make thoroughly clear what is believed to be a consequence of the rest of this License.

xx ISR651103-00 C

Preface

General Public License

9.

If the distribution and/or use of the Program is restricted in certain countries either by patents or by copyright interfaces, the original copyright holder who places the Program under this License may add an explicit geographical distribution limitation excluding those countries, so that distribution is permitted only in or among countries not thus excluded. In such case, this

License incorporates the limitation as if written in the body of this License.

10. The Free Software Foundation may publish revised and/or new versions of the General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns.

11.

Each version is given a distinguishing version number. If the Program specifies a version number of this License which applies to it and “any later version”, you have the option of following the terms and conditions either of that version or of any later version published by the Free Software

Foundation. If the Program does not specify a version number of this

License, you may choose any version ever published by the Free Software

Foundation.

12. If you wish to incorporate parts of the Program into other free programs whose distribution conditions are different, write to the author to ask for permission. For software which is copyrighted by the Free Software

Foundation, write to the Free Software Foundation; we sometimes make exceptions for this. Our decision will be guided by the two goals of preserving the free status of all derivatives of our free software and of promoting the sharing and reuse of the software generally.

NO WARRANTY

13. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS

NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY

APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING

THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE

PROGRAM “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER

EXPRESSED OR IMPLIED, INCLUDING BUT NOT LIMITED TO, THE

IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A

PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND

PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE

PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL

NECESSARY SERVICING, REPAIR OR CORRECTION.

14. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED

TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER

PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE PROGRAM AS

PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING

ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL

DAMAGES ARISING OUT OF USE OR INABILITY TO USE THE

ISR651103-00 C xxi

Preface

General Public License

PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA

BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR

ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY

HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

END OF TERMS AND CONDITIONS

How to Apply These Terms to Your New Programs

If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it free software which everyone can redistribute and change under these terms.

To do so, attach the following notices to the program. It is safest to attach them to the start of each source file to most effectively convey the exclusion of warranty; and each file should have at least the “copyright” line and a pointer to where the full notice is found.

One line to give the program’s name and an idea of what it does.

Copyright (C) yyyy name of author

This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software

Foundation; either version 2 of the License, or (at your option) any later version.

You should have received a copy of the GNU General Public License along with this program; if not write to the Free Software Foundation, Inc., 59 Temple Place -

Suite 330, Boston, MA 02111-1307, USA.

Also information on how to contact you by electronic and paper mail.

If the program is interactive, make it output a short notice like this when it starts in an interactive mode:

Gnomovision version 69, Copyright (C) year name of author

Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type ’show w’. This is free software, and you are welcome to redistribute it under certain conditions; type ’show c’ for details.

The hypothetical commands ’show w’ and ’show c’ should the appropriate parts of the General Public License. Of course, the commands you use may be called something other than ’show w’ and ’show c’; they could even be mouse-clicks or menu items - whatever suits your program.

You should also get your employer (if you work as a programmer) or your school, if any, to sign a “copyright disclaimer” for the program, if necessary. Here is a sample; alter the names: xxii ISR651103-00 C

Preface

Technical Support

Yoyodyne, Inc., hereby disclaims all copyright interest in the program

’Gnomovision’ (which makes passes at compilers) written by James Hacker.

signature of Ty Coon, 1 April 1989

Ty Coon, President of Vice

This General Public License does not permit incorporating your program into proprietary programs. If your program is a subroutine library, you may consider it more useful to permit linking proprietary applications with the library. If this is what you want to do, use the GNU Library General Public License instead of this

License.

Technical Support

Customers should contact their authorized maintenance provider for technical support of their QLogic switch products. QLogic-direct customers may contact

QLogic Technical Support; others will be redirected to their authorized maintenance provider.

For details about available service plans, or for information about renewing and extending your service, visit the Service Program Web page at http://www.qlogic.com/services .

Training

QLogic offers training for technical professionals for all iSCSI, InfiniBand, and

Fibre Channel products. From the main QLogic Web page at www.qlogic.com

, click the Support tab at the top, and then click the Education & Training on the left. The QLogic Global Training Portal offers online courses, certification exams, and scheduling of in-person training.

Technical Certification courses include installation, maintenance, and troubleshooting QLogic products. Upon demonstrating knowledge using live equipment, QLogic awards a certificate identifying the student as a certified professional. You can reach the training professionals at QLogic by e-mail at [email protected]

.

ISR651103-00 C xxiii

Preface

Technical Support

Contact Information

QLogic Technical Support for products under warranty is available during local standard working hours excluding QLogic Observed Holidays. For customers with extended service, consult your plan for available hours. For Support phone numbers, see the Contact Support link at http://support.qlogic.com.

Support Headquarters QLogic Corporation

4601 Dean Lakes Blvd.

Shakopee, MN 55379 USA

QLogic Web Site www.qlogic.com

Technical Support Web Site http://support.qlogic.com

Technical Support E-mail [email protected]

Technical Training E-mail [email protected]

Knowledge Database

The QLogic knowledge database is an extensive collection of QLogic product information that you can search for specific solutions. We are constantly adding to the collection of information in our database to provide answers to your most urgent questions. Access the database from the QLogic Support Center: http://support.qlogic.com

.

xxiv ISR651103-00 C

1

Introduction

This chapter describes the following features and capabilities of the iSR6152 router:

“Router Capabilities” on page 1-1

“Licensed Feature—Data Migration” on page 1-2

“Fibre Channel over IP (FCIP)” on page 1-2

“Chassis LEDs” on page 1-3

“Chassis Controls” on page 1-4

“Fibre Channel Ports” on page 1-6

“Fibre Channel SFP Transceivers” on page 1-7

“GbE Port LEDs” on page 1-8

“Ethernet Management Port” on page 1-9

“Serial Port” on page 1-9

Router Capabilities

Figure 1-1

shows the front of the iSR6152 Intelligent Storage Router.

Figure 1-1. iSR6152 Router

The iSR6152 is a bi-directional Fibre Channel to gigabit Ethernet (GbE) router. It supports the following topology:

 FCIP, Fibre Channel over IP (see

page 1-2

)

ISR651103-00 C 1-1

1–Introduction

Licensed Feature—Data Migration

When using the iSR6152 to connect two Fibre Channel SANs, E_Ports are not required on the Fibre Channel switches. This allows you to connect multi-vendor

Fibre Channel SANs (switches) without concern for the compatibility of the

E_Ports and N_Ports between different switch vendors.

The iSR6152 also has optional, additional servers and ports to expand connectivity.

Licensed Feature—Data Migration

The iSR6152 router also provides data migration as an optional, licensed feature.

The iSR6152-based data migration feature is block-based and independent of a

SAN, server, storage protocol (Fibre Channel and iSCSI), and storage vendor.

Because application downtime during data migration is always critical, iSR6152 data migration supports both online (local and remote) and offline data migration across Fibre Channel and iSCSI storage arrays. Even offline data migration using the iSR6152 is designed to minimize application downtime by allowing you to configure all migration related tasks while the application remains online, and to migrate the data at a very high speed while the application is offline. This feature is designed such that any person with knowledge of SAN or SAN storage administration can migrate data.

Fibre Channel over IP (FCIP)

The iSR6152 router supports Fibre Channel over IP (FCIP). The FCIP protocol as implemented in the router is not guaranteed nor has it been tested to be compatible with other vendor FCIP implementations. The router supports up to two FCIP routes; each route requires a dedicated Fibre Channel and GbE port pair.

 Merge Fibre Channel fabrics over LAN or WAN

 N_Port to fabric over LAN or WAN

 N_Port to N_Port over LAN or WAN

FCIP is generally used as an inter-switch link (ISL) between local and remote

SANs. The ISL enables the SAN fabrics to merge, and requires that both SANs use compatible Fibre Channel switches (typically from the same vendor).

FCIP can also operate as an N_Port extender to connect a remote Fibre Channel device into a SAN. This configuration requires a direct connection between the remote router and the Fibre Channel device.

1-2 ISR651103-00 C

1–Introduction

Chassis LEDs

Chassis LEDs

The chassis LEDs shown in

Figure 1-2

provide information about the router’s operational status. These LEDs include the input power LED, heartbeat LED, and the system fault LED. To apply power to the router, plug the power cord into the router AC power receptacle and into a 100 VAC to 240 VAC, 50 Hz to 60 Hz power source.

Heartbeat LED Power LED

Figure 1-2. Chassis LEDs

System Fault LED

Input Power LED (Green)

The power LED shows the voltage status at the router logic circuit board. During normal operation, this LED lights up to show that the router logic circuit board is receiving the DC voltage from the power supply.

Heartbeat LED (Green)

The heartbeat LED blinks once per second as long the router firmware is operational.

System Fault LED (Amber)

The system fault LED lights up to show that a fault exists in the router firmware or hardware. Fault conditions include POST errors and over-temperature conditions.

The LED shows a blink code for POST errors and the over-temperature condition.

See

Figure 1-2 and Table 1-1

.

Table 1-1. System Fault LED Blink Patterns

System

Fault LED

Off

3 Blinks

4 Blinks

5 Blinks

Condition

Okay (operational)

System error

Management port IP address conflict

Over temperature

ISR651103-00 C 1-3

1–Introduction

Chassis Controls

Table 1-1. System Fault LED Blink Patterns (Continued)

System

Fault LED

1 Blink

Condition

Beacon, synchronized with the heartbeat LED

Chassis Controls

The maintenance button shown in

Figure 1-3 is the only chassis control. Pressing

this button resets the router or recovers the router if it has become disabled.

Maintenance Button

Figure 1-3. Chassis Controls

Maintenance Button

The maintenance button is a multifunction momentary switch on the front panel. It has the following functions:

Reset a Router

(see

page 1-5

)

Reset and Select Boot Image (see page 1-5 )

Reset IP Address (see section page 1-5 )

Enable DHCP (see section page 1-5 )

Restore Factory Defaults

(see

page 1-5 )

Reset a Router

To reset the router, use a pointed, nonmetallic tool to momentarily press and release (less than two seconds) the maintenance button. The router responds as follows:

1.

All the chassis LEDs light up.

2.

After about two seconds, the POST begins, turning off the heartbeat and system fault LEDs.

3.

When the POST is complete, the power LED is on and the heartbeat LED flashes once per second.

1-4 ISR651103-00 C

1–Introduction

Chassis Controls

Reset and Select Boot Image

You can reset the router using either the primary or secondary boot image:

Primary Image. To reset the router and select the primary boot image, use a pointed, nonmetallic tool to press and hold the maintenance button until the heartbeat LED flashes once, and then release the button. The router boots from the primary boot image. The boot time is less than one minute.

Secondary Image. To reset the router and select the secondary boot image, use a pointed, nonmetallic tool to press and hold the maintenance button until the heartbeat LED flashes twice, and then release the button.

The heartbeat LED flashes twice. The router boots from the secondary boot image. The boot time is less than one minute.

Reset IP Address

To reset the router and restore the maintenance port IP address to the default

(10.0.0.1), use a pointed, nonmetallic tool to press and hold the maintenance button until the heartbeat LED flashes six times, and then release the button. The router boots and sets the maintenance port to IP address 10.0.0.1. The boot time is less than one minute.

The IP address set by this method is not persistent (saved upon reboot). To make the change persistent, use the command line interface (CLI) or Router Manager to set the IP address. For more information, see the iSR6152 Router Manager

User's Guide or the iSR6152 Router CLI User's Guide.

Enable DHCP

To reset the router and configure the maintenance port to use DHCP to acquire its

IP address, use a pointed, nonmetallic tool to press and hold the maintenance button until the heartbeat LED flashes seven times, and then release the button.

The router boots and configures the maintenance port for DHCP. The boot time is less than one minute.

Enabling DHCP by this method is not persistent; to make the change persistent, use the command line interface (CLI) or Router Manager to enable DHCP. For details, see the iSR6152 Router Manager User's Guide or the iSR6152 Router

CLI User's Guide.

Restore Factory Defaults

To reset the router and restore it to the factory default configuration, use a pointed, nonmetallic tool to press the maintenance button and hold it until the heartbeat LED flashes 20 times, and then release the button. The router boots and is restored to the factory defaults. The boot time is less than one minute.

The router does the following when restored to the factory defaults:

 Resets all passwords.

 Resets the maintenance port IP address to 10.0.0.1.

ISR651103-00 C 1-5

1–Introduction

Fibre Channel Ports

 Disables the GbE ports and sets the IP address to 0.0.0.0.

 Erases all presentations.

 Erases all discovered initiators and targets.

Fibre Channel Ports

The iSR6152 router has two Fibre Channel ports, labeled FC1 and FC2, as shown

in Figure 1-4 .

2Gbps Activity LED

4Gbps Activity LED 8Gbps Activity LED

Figure 1-4. Fibre Channel Ports

Each port is served by a small form-factor pluggable (SFP) optical transceiver and is capable of 2Gbps, 4Gbps, or 8Gbps transmission. SFPs are hot-pluggable: you can remove or install a transceiver while the router is operating without harming the router or the transceiver. Fibre Channel ports can self-discover both the connection type and transmission speed when connected to public devices or switches.

Fibre Channel Port LEDs

The Fibre Channel port LEDs are located to the right of their respective ports and provide status and activity information. Each port has three LEDs:

 The amber (top) LED shows activity for data passing through the port at

2Gbps speed.

 The green LED (middle) shows activity for data passing through the port at

4Gbps speed.

 The yellow LED (bottom) shows activity for data passing through the port at

8Gbps speed.

1-6 ISR651103-00 C

1–Introduction

Fibre Channel Ports

Table 1-2 describes the port LED blink patterns and their meanings.

Table 1-2. Port LEDs

Activity

Yellow LED

(8Gbps)

Green LED

(4Gbps)

Amber LED

(2Gbps)

Power OFF

Power ON

(before firmware initialization)

Power ON

(after firmware initialization)

Firmware initialization error a

Online, 2Gbps link—I/O activity

Online, 4Gbps link—I/O activity

Online, 8Gbps link—I/O activity

Beacon

OFF

ON

Flashing

Alternate flashing

OFF

OFF

ON and flashing

Flashing

OFF

ON

Flashing

Alternate flashing

OFF

ON and flashing

OFF

OFF

OFF

ON

Flashing

Alternate flashing

ON and flashing

OFF

OFF

Flashing a Yellow, green, and amber LEDs flash alternatively to indicate firmware initialization errors.

Fibre Channel SFP Transceivers

The iSR6152 router supports SFP optical transceivers for the Fibre Channel ports.

A transceiver converts electrical signals to and from optical laser signals to transmit and receive data. Duplex fibre optic cables plug into the transceivers, which then connect to the devices. The Fibre Channel ports are capable of transmitting at 2Gbps, 4Gbps, or 8Gbps; the transceiver must also be capable of delivering these rates.

Although the SFP transceivers are hot-pluggable, this interrupts communication

with the connected device. For more information, see “Removing and Replacing

SFP Transceivers” on page 5-1

.

ISR651103-00 C 1-7

1–Introduction

GbE Port LEDs

GbE Port LEDs

The four GbE ports shown in Figure 1-5

are RJ45 connectors that provide connection to an Ethernet SAN through a 100/1000 Base-T Ethernet cable.

Link Status LED Activity LED

Link Status LED Activity LED

Figure 1-5. GbE Ports

The GbE ports are labeled GE1, GE2, GE3, and GE4. Each GbE port has two

LEDs:

 The green (left) link status LED lights up to indicate that the link is up.

 The yellow (right) activity LED lights up when the router sends or receives data over the connection.

Ports GE1 and GE3 LEDs are located at the bottom left and right corners of each port. Ports GE2 and GE4 LEDs are located at the top left and right corners of each port.

1-8 ISR651103-00 C

1–Introduction

Ethernet Management Port

Ethernet Management Port

The Ethernet management port shown in Figure 1-6

is an RJ45 connector that provides a connection to a management workstation through a 10/100 Base-T

Ethernet cable. The port is labeled MGMT.

Link Status LED Activity LED

Figure 1-6. Ethernet Management Port

You can use a Windows ® or Linux ® workstation to configure and manage the router over an Ethernet connection using the Router Manager, CLI, or SNMP (see

Appendix A Simple Network Management Protocol (SNMP)

).

The management Ethernet port has two LEDs:

 The green (left) link status LED lights up to indicate that the link is up.

 The yellow (right) activity LED lights up when the router sends or receives data over the connection.

Serial Port

The iSR6152 router is equipped with an RS232 serial port for maintenance purposes.

Figure 1-7

shows the serial port location. It is labeled IOIOI. You can manage the router through the serial port using the CLI.

Serial Port

Figure 1-7. Serial Port

The serial port connection requires a standard, eight-wire Ethernet cable and the

RJ45-to-DB9F adapter (supplied) to convert the Ethernet RJ45 connector to a female DB9 connector.

ISR651103-00 C 1-9

1–Introduction

Serial Port

1-10 ISR651103-00 C

2

Planning

This chapter describes how to plan for the iSR6152 router. This includes the following considerations:

“Devices” on page 2-1

“Fibre Channel Performance” on page 2-2

“GbE Performance” on page 2-3

“Performance Tuning” on page 2-3

“Fibre Channel Switch Ports and Zoning Requirements” on page 2-7

“Multiple Routers” on page 2-7

“Management” on page 2-7

“Recovery” on page 2-7

“Services” on page 2-8

“Security” on page 2-8

Devices

When planning to use the router, consider the number of devices and the anticipated demand. The device quantity determines the required number of ports, and in turn the number of routers.

The router uses small form-factor pluggable (SFP) transceivers in the 2Gbps,

4Gbps, or 8Gbps Fibre Channel ports, but some Fibre Channel devices may not use the same transceivers. Consider whether the Fibre Channel device to be connected to the router uses SFP or gigabit interface converters (GBIC) transceivers, and choose fiber optic cables accordingly. Use LC-type cable connectors for SFP transceivers and SC-type cable connectors for GBIC transceivers. Also consider the transmission speed compatibility of your devices, adapters, switches, and SFPs.

ISR651103-00 C 2-1

2–Planning

Fibre Channel Performance

Fibre Channel Performance

The iSR6152 router supports Fibre Channel service at transmission rates of

2Gbps, 4Gbps, or 8Gbps with a maximum frame size of 2,148 bytes. It supports

Ethernet service at transmission rates of 1000Mbps or 100Mbps with a maximum transmission unit (MTU) size of 1,500 bytes or 9,000 bytes (jumbo frames).

NOTE:

An MTU size greater than 1,500 should only be used when the router is connected to a 1000Mbps Ethernet network and all links (switches, routers, and so on) that make up the LAN or WAN support greater than 1,500byte frames and are configured for frames greater than 1,500bytes.

Related performance characteristics include the following:

“Distance” on page 2-2

“Bandwidth” on page 2-2

“Latency” on page 2-3

Distance

Consider the physical distance between Fibre Channel devices. Choose SFP transceivers that are compatible with the cable type and distance you need.

Each Fibre Channel port is supported by a data buffer with a three-credit capacity; that is, five maximum-sized frames. For fiber optic cables, this enables full bandwidth over the following approximate distances:

 2.5km at 2Gbps (1.2 credits/km)

 1.25km at 4Gbps (2.5 credits/km)

 0.625km at 8Gbps (5 credits/km)

Transmitting data beyond these distances reduces efficiency because the transmitting port must wait for an acknowledgement before sending the next frame.

Bandwidth

Bandwidth measures the amount of data transmitted over a channel or network. A

2Gbps, 4Gbps, or 8Gbps Fibre Channel port can transmit or receive at nominal rates of 2Gbps, 4Gbps, or 8Gbps, depending on the device to which it is connected. This corresponds to actual bandwidth values of 106MB and 212MB, respectively. WAN data rates range from 1.5Mbps (T1) to greater than 600Mbps

(OC-12).

2-2 ISR651103-00 C

2–Planning

GbE Performance

Latency

Latency measures how long a transaction takes to travel through the router or over a communication link.

GbE Performance

The iSR6152 router supports Ethernet service at transmission rates of 1000Mbps or 100Mbps with a MTU size of 1,500 or 9,000 (jumbo frames).

NOTE:

An MTU size greater than 1,500 should only be used when the router is connected to a 1000Mbps Ethernet network and all links (switches, routers, and so on) that make up the LAN/WAN support greater than 1,500byte frames and are configured for frames greater than 1,500bytes.

Consider the physical distance between routers, which is usually measured in round-trip delay. Round-trip delay ranges anywhere from less than 1ms to as great as 250ms.

Performance Tuning

Properly configuring the router maximizes its performance. Knowing the round-trip delay (distance) between routers and the WAN effective data rate (connection type) allows you to tune the routers for optimal performance. The following tables provide TCP Window Scaling Factor and Window Size settings for specific

WAN environments.

NOTE:

For high loss networks, QLogic recommends decreasing the TCP Window

Size from the initial recommended setting until the network achieves optimal performance.

Round Trip Delay

(ms)

250

100

50

Table 2-1. T1 / DS-1—1.554 Mbps

Total Window Size

(bytes)

64K

32K

32K

Scaling Factor

1

0

0

ISR651103-00 C 2-3

2–Planning

Performance Tuning

Table 2-1. T1 / DS-1—1.554 Mbps (Continued)

Round Trip Delay

(ms)

25

20

15

10

5

2.5

1 or less

Total Window Size

(bytes)

32K

32K

32K

32K

32K

32K

32K

Scaling Factor

0

0

0

0

0

0

0

Round Trip Delay

(ms)

20

15

10

5

250

100

50

25

2.5

1 or less

Table 2-2. T3 / DS-3—45 Mbps

Total Window Size

(bytes)

1MB

512K

256K

128K

128K

64–128K

64K

32K

32K

32K

Scaling Factor

2

1 or 2

1

0

0

0

3

2

5

4

Round Trip Delay

(ms)

250

100

Table 2-3. DS-5—400 Mbps

Total Window Size

(bytes)

1MB

1MB

Scaling Factor

5

5

2-4 ISR651103-00 C

ISR651103-00 C

2–Planning

Performance Tuning

Table 2-3. DS-5—400 Mbps (Continued)

Round Trip Delay

(ms)

50

25

20

15

10

5

2.5

1 or less

Total Window Size

(bytes)

1MB

1MB

1MB

1MB

512K

256K

128K

64K

Scaling Factor

2

1

4

3

5

5

5

5

Round Trip Delay

(ms)

20

15

10

5

250

100

50

25

2.5

1 or less

Table 2-4. OC-1—50 Mbps

Total Window Size

(bytes)

1MB

512K

256K

128K

128K

64–128K

64K

32K

32K

32K

Scaling Factor

2

1 or 2

1

0

0

0

3

2

5

4

Round Trip Delay

(ms)

250

Table 2-5. OC-3—150 Mbps

Total Window Size

(bytes)

1MB

Scaling Factor

5

2-5

2–Planning

Performance Tuning

Table 2-5. OC-3—150 Mbps (Continued)

Round Trip Delay

(ms)

100

50

25

20

15

10

5

2.5

1 or less

Total Window Size

(bytes)

1MB

1MB

512K

512K

256K

256K

128K

64K

32K

Scaling Factor

2

1

3

3

0

4

4

5

5

Table 2-6. OC-12 and Above—621 Mbps

Round Trip Delay

(ms)

20

15

10

5

250

100

50

25

2.5

1 or less

Total Window Size

(bytes)

1MB

1MB

1MB

1MB

1MB

1MB

1MB

512K

256K

64K

Scaling Factor

5

4

5

5

3

1

5

5

5

5

2-6 ISR651103-00 C

2–Planning

Fibre Channel Switch Ports and Zoning Requirements

Fibre Channel Switch Ports and Zoning

Requirements

The iSR6152 Fibre Channel ports are configured either as loop ports or in N_Port

ID virtualization (NPIV). Therefore, the Fibre Channel switch port, (where iSR6152

Fibre Channel port is connected) must be configured to support a loop topology such as fibre loop port (FL_Port), generic port (G_Port), or NPIV.

The iSR6152 uses its local Fibre Channel ports for discovering local Fibre

Channel devices in the SAN.

QLogic recommends that any Fibre Channel switch connected to the iSR6152 use

Fibre Channel world wide port name (WWPN)-based zoning. This requires adding the router’s Fibre Channel WWPNs in all local switch zones and the remote router’s Fibre Channel WWPNs in all remote switch zones.

Multiple Routers

By connecting multiple routers between your Fibre Channel SANs, you can eliminate any router as a single point of failure.

Management

The Router Manager utility and CLI run on a management workstation that enables you to configure, control, and maintain the router. Support platforms include Windows and Linux.

The router supports the following management interfaces:

Router Manager is a graphical user interface tool that runs on a management workstation (see the iSR6152 Router Manager User's Guide).

CLI runs on the router, which you can access using Telnet or the serial port

(see the iSR6152 Router CLI User's Guide).

SNMP provides router status, traps, and alerts (see Appendix A

).

Recovery

It is prudent to have a recovery process in case a router fails. Consider the following when developing a router recovery process:

 Save all firmware image files (updates) in a safe, well-known place, because you may:

 Want to revert to a previous firmware version.

 Need the firmware image when replacing a router.

 Need the firmware image when adding a router to your site.

ISR651103-00 C 2-7

2–Planning

Services

 Save the router’s configuration (as a new file) after every configuration change, because you may:

 Want to revert to a previous configuration.

 Need to configure a replacement router.

 Save the router’s mappings (as a new file) after every mapping change, because you may:

 Want to revert to a previous mapping.

 Need to map a replacement router.

 Want to duplicate the mapping on a second router (for backup).

Services

You can configure the iSR6152 router to suit the demands of your environment using a variety of router services. Familiarize yourself with the following router services and determine which ones you need:

Telnet enables router management over a Telnet connection.

Router management provides for out-of-band router management using

Router Manager.

SNMP provides monitoring of the router using third-party applications that use SNMP.

Network time protocol (NTP) enables synchronizing the router and the workstation dates and times with an NTP server. NTP is disabled (and not configured) by default.

File transfer protocol (FTP) enables transferring files rapidly between the workstation and router using FTP.

Security

Passwords provide router security. Router Manager requires a password each time a user logs into the utility. When connected, Router Manager prompts for an administrative password before it accepts configuration changes.

The CLI also requires the user to enter a user ID and password to start. CLI must be in an admin session to perform any set operations. An admin session requires a password.

The default password for both these management tools is “password” for the default user ID of “guest.” The default administrative password is “config.”

After you are logged on, you can change the password using the utility’s security features.

2-8 ISR651103-00 C

3

Installation

This chapter describes how to install and configure an iSR6152 router, and to install the firmware. It contains the following sections:

Site Requirements

“Installing the iSR6152 Router” on page 3-2

“Installing the Firmware” on page 3-11

Site Requirements

The following sections identify the site requirements for installing an iSR6152 router:

Management Workstation Requirements

“Power Requirements” on page 3-2

“Environmental Conditions” on page 3-2

Management Workstation Requirements

The management workstation running Router Manager must meet the requirements listed in

Table 3-1 .

Table 3-1. Management Workstation Requirements

Item

Operating system

Memory

Disk space

Processor

Hardware

Description

One of the following:

 Windows ® 2003, 2008, and XP

 Red Hat Enterprise Linux ® (RHEL) 3, 4, and 5

 SUSE ® Enterprise Linux Server (SLES) 9 and 10

 Mac OS ® X 10.3

256MB or more

150MB per installation

500MHz or faster

CD-ROM drive, RJ45 Ethernet port, RS232 serial port

(optional)

ISR651103-00 C 3-1

3–Installation

Installing the iSR6152 Router

Table 3-1. Management Workstation Requirements (Continued)

Item

Internet browser

Description

One of the following:

 Microsoft Internet Explorer 7.0 and later

 Safari™

 Java 2 runtime environment to support the Web applet

Power Requirements

Power requirements for the iSR6152 router are 0.5Amps at 100–125 VAC, 50Hz to 60Hz or 0.25Amps at 200–240 VAC, 50Hz to 60Hz.

Environmental Conditions

Consider the factors that affect the climate in your facility, such as equipment heat dissipation and ventilation. The router requires the following operating conditions:

 Operating temperature range: 5–40 ° C (41–104 ° F)

 Relative humidity: 15–90 percent, non-condensing

Installing the iSR6152 Router

This section provides information about installing, configuring, and connecting the hardware and software, including:

“Pre-Installation Check List” on page 3-4

“Mounting the Router” on page 3-4

“Installing the Transceivers” on page 3-6

“Connecting the Management Workstation to the Router” on page 3-6

“Configuring the Management Workstation” on page 3-6

“Installing Router Manager” on page 3-8

“Starting Router Manager” on page 3-9

“Connecting the Router to AC Power” on page 3-10

“Configuring the Router” on page 3-10

“Cabling Devices to the Router” on page 3-11

3-2 ISR651103-00 C

3–Installation

Installing the iSR6152 Router

Prior to installing the router, unpack the router and accessories. The iSR6152 router is shipped with the following components, shown in

Figure 3-1 :

 Power cord.

 Adapter (RJ45 to DB9F) for connecting the router’s serial port to a workstation used for configuring and managing the router. A standard Cat5

Ethernet cable is required (not supplied) to connect the adapter to the router.

The adapter connects directly to the workstation’s serial (COM) port.

Figure 3-1 iSR6152 Router and Accessories

To install the iSR6152 router:

1.

Complete the pre-installation checklist (see page 3-4 ).

2.

Mount the router (see

page 3-4

).

3.

Install the transceivers (see page 3-6

).

4.

Connect the management workstation to the router (see page 3-6

).

5.

Configure the management workstation (see page 3-6 ).

6.

Install the management utility (see

page 3-8 ).

7.

Start the management utility (see

page 3-9 ).

8.

Connect the router to AC power (see page 3-10

).

9.

Configure the router (see page 3-10

).

10. Cable Fibre Channel and GbE devices to the router (see page 3-11

).

ISR651103-00 C 3-3

3–Installation

Installing the iSR6152 Router

Pre-Installation Check List

During the initial configuration process, the system prompts you for the

parameters listed in Table 3-2 . Complete this table before installation to expedite

the configuration process.

Table 3-2. Pre-Installation Checklist

My System Item

Symbolic name of iSR6152

Management Port

(MGMT)

GbE Port 1 (GE1)

GbE Port 2 (GE2)

GbE Port 3 (GE3)

GbE Port 4 (GE4)

IP Address (if not using DHCP):

Subnet Mask (if not using DHCP):

Gateway (if not using DHCP):

IP Address:

Subnet Mask:

Gateway:

IP Address:

Subnet Mask:

Gateway:

IP Address:

Subnet Mask:

Gateway:

IP Address:

Subnet Mask:

Gateway:

Mounting the Router

You can place the router on a flat surface or mount it in a standard 19-inch

Electronic Industries Association (EIA) rack. See the product specification for weight and dimensions. Rack mounting requires a QLogic rack mounting kit (Part

No. ISR614X-RACKKIT). Contact QLogic for more information.

3-4 ISR651103-00 C

3–Installation

Installing the iSR6152 Router

WARNING!!

Mount routers in the rack so that the weight is distributed evenly. An unevenly loaded rack can become unstable, possibly resulting in equipment damage or personal injury.

AVERTISSEMENT!!

Installer les routeurs dans l’armoire informatique de sorte que le poids soit réparti uniformément. Une armoire informatique déséquilibré risque d'entraîner des blessures ou d'endommager l'équipement.

WARNUNG!!

Bauen Sie die Router so in das Rack ein, dass das Gewicht gleichmäßig verteilt ist. Ein Rack mit ungleichmäßiger Gewichtsverteilung kann schwanken/umfallen und Gerätbeschädigung oder Verletzung verursachen.

¡ADVERTENCIA!

Monte los enrutadores en el estante de modo que el peso se distribuya de manera uniforme. Un estante cuya carga no esté distribuida de manera uniforme puede ser inestable y podría dañar el equipo o causar lesiones personales.

CAUTION!

 If the router is mounted in a closed or multi-rack assembly, the operating temperature of the rack environment may be greater than the ambient temperature. Be sure to install the chassis in an environment that is compatible with the maximum rated ambient temperature.

 Do not restrict chassis air flow. Allow 16 cm (6.5 in) minimum clearance at the front and rear of the router (surface mount) or rack for service access and ventilation.

 Multiple rack-mounted units connected to the AC supply circuit may overload that circuit or overload the AC supply wiring. Consider the power source capacity and the total power usage of all routers on the circuit.

 Reliable grounding in the rack must be maintained from the router chassis to the AC power source.

ISR651103-00 C 3-5

3–Installation

Installing the iSR6152 Router

Installing the Transceivers

The router supports a variety of SFP transceivers.

 To install a transceiver, insert the transceiver into the port and gently press until it snaps in place.

 To remove a transceiver, gently press the transceiver into the port to release tension, and then pull the release tab or lever and remove the transceiver.

Different transceiver manufactures have different release mechanisms.

Consult the documentation of your transceiver.

NOTE:

The transceiver fits only one way. If the transceiver does not install under gentle pressure, flip it over and try again.

Connecting the Management Workstation to the Router

You can manage the router using Router Manager or the CLI. Router Manager requires an Ethernet connection to the router. The CLI can use an Ethernet connection or a serial connection. Choose the router management method, and then connect the management workstation to the router in one of the following ways:

 Indirect Ethernet connection from the management workstation to the router

RJ45 connector through an Ethernet switch or hub. This requires a 10/100

Base-T straight-through cable.

 Direct Ethernet connection from the management workstation to the router

RJ45 Ethernet connector. This requires a 10/100 Base-T crossover cable.

 Serial port connection from the management workstation to the router

RS232 serial port connector. This requires a 10/100 Base-T straight-through cable and an RJ45-to-DB9F adapter (included with the router).

Configuring the Management Workstation

The router comes from the factory with a default IP address (10.0.0.1). Prior to product installation, follow the procedures based on your configuration method:

 If you plan to configure the router through the management Ethernet port

(using Router ManagerI or CLI using Telnet), you must initially configure the workstation as described in

“Setting the Workstation IP Address” on page 3-7

.

 If you plan to configure the router using the management COM port,

configure the workstation as described in “Configuring the Workstation

Serial Port” on page 3-7

.

3-6 ISR651103-00 C

3–Installation

Installing the iSR6152 Router

Setting the Workstation IP Address

The IP address of a new router is 10.0.0.1. To ensure that your workstation is configured to communicate with the 10.0.0 subnet, refer to the following instructions for your workstation:

 Steps for different versions of Windows vary. For a Windows 2000 workstation, follow these steps: a.

From the Windows Start menu, select Settings>Control

Panel>Network and Dial-up Connections.

b.

Click Make New Connection.

c.

Click Connect to a private network through the Internet, and then click Next.

d.

For the IP address, type 10.0.0.253.

 For other versions of Windows, consult the Windows Help files.

 For a Linux workstation, open a command window and enter the following command, where <interface> is your interface name: ifconfig <interface> ipaddress 10.0.0.253 netmask

255.255.255.0 up

Configuring the Workstation Serial Port

To configure the workstation serial port:

1.

Connect the cable with RJ45-to-DB9F adapter from a COM port on the management workstation to the serial port on the router.

2.

Configure the workstation serial port according to your platform. These steps may vary according to the version of operating system you use:

 For Windows: a.

Open the HyperTerminal application. From the Windows Start menu, select Programs>

Accessories>HyperTerminal>HyperTerminal.

b.

Enter a name for the router connection, choose an icon in the

Connection Description window, and then click OK.

c.

Enter the following COM Port settings in the COM Properties window and click OK.

Bits per second—115200

Data Bits—8

Parity—None

Stop Bits—1

Flow Control—None

ISR651103-00 C 3-7

3–Installation

Installing the iSR6152 Router

 For Linux: a.

Set up minicom to use the serial port. Create or modify the

/etc/minirc.dfl file with the following content: pr portdev/ttyS0 pu minit pu mreset pu mhangup pr portdev/ttyS0 specifies port 0 on the workstation.

Choose the pr setting to match the workstation port to which you connected the router.

b.

Verify that all users have permission to run minicom. Review the

/etc/minicom.users file and confirm that the line ALL exists or that there are specific user entries.

3.

Connect the router to the power (see page 3-10

).

Installing Router Manager

You can manage the router using the Router Manager utility. The following sections describe how to install the utility on either a Windows or Linux workstation. See the iSR6152 Router Manager User's Guide for information on how to use the Router Manager.

Windows Installation

Perform the following steps to install Router Manager from the QLogic Web site to a PC workstation.

To install Router Manager on Windows

1.

Close all currently running programs.

2.

Go to the QLogic Driver Downloads/Documentation page: http://driverdownloads.qlogic.com

3.

Under Downloads, click QLogic Products.

4.

Under QLogic Products, click the Routers link.

5.

In the product selection window, click the iSR6152 model number, and then then click Go.

6.

On the iSR6152 Downloads page under Management Tools, click the link to the Router Manager for your operating system.

7.

On the End User Software License Agreement page, read the license agreement, and then click I Agree to continue.

8.

Save the installation file to your local machine.

9.

Run the Router Manager installer by following the system prompts.

3-8 ISR651103-00 C

3–Installation

Installing the iSR6152 Router

Linux Installation

Perform the following steps to install Router Manager from the QLogic Web site to a Linux workstation.

To install Router Manager on Linux

1.

Go to the QLogic Driver Downloads/Documentation page: http://driverdownloads.qlogic.com

2.

Under Downloads, click QLogic Products.

3.

Under QLogic Products, click the Routers link.

4.

In the product selection window, click the iSR6152 model number, and then then click Go.

5.

On the iSR6152 Downloads page under Management Tools, click the link to the Router Manager for your operating system.

6.

On the End User Software License Agreement page, read the license agreement, and then click I Agree to continue.

7.

Save the installation file to your local machine.

8.

Uncompress the downloaded file, and then execute the Linux_x.xx.bin install program.

9.

Follow the installation instructions.

Starting Router Manager

For Windows, double-click the Router Manager shortcut, or select Router

Manager from the Start menu, depending on how you installed the utility.

Or, from a command line, enter the command for your operating system:

 On Windows, enter the following command:

<install_directory>SANsurfer_Router_Manager.exe

 On Linux, enter the following command:

<install_directory>./SANsurfer_Router_Manager

ISR651103-00 C 3-9

3–Installation

Installing the iSR6152 Router

Connecting the Router to AC Power

WARNING!!

This product is supplied with a three-wire power cable and plug for the user’s safety. To avoid electrical shock, use this power cable in conjunction with a properly grounded outlet. An electrical outlet that is not correctly wired could place hazardous voltage on metal parts of the router chassis. It is the customer’s responsibility to ensure that the outlet is correctly wired and grounded to prevent electrical shock.

You may require a different power cable in some countries because the plug on the cable supplied with the equipment will not fit your electrical outlet. In this case, you must supply your own power cable. The cable must meet the following requirements:

For 125Volt electrical service: The cable must be rated at 10 Amps and be approved by UL and CSA.

For 250Volt electrical service: The cable must be rated at 10 Amps, meet requirements of H05VV-F, and be approved by VDE, SEMKO, and

DEMKO.

To power up the router, connect the power cord to the power receptacle on the router chassis and to a grounded AC outlet. The router responds in the following sequence:

1.

The chassis LEDs (input power, heartbeat, system fault) light up, and then all port LEDs light up.

2.

After a couple of seconds the heartbeat and system fault LEDs go off, while the input power LED stays on. The router is executing the POST.

3.

The POST completes after about 45 seconds and the heartbeat LED starts flashing at a one second rate. If an error has occurred, the System Fault

LED blinks a pattern that indicates the fault reason. For more information see

“System Error Blink Pattern” on page 4-3

.

Configuring the Router

You can configure the router using the CLI.

3-10 ISR651103-00 C

3–Installation

Installing the Firmware

To configure the router using the command line interface:

1.

Open a command window according to the type of workstation and connection:

Ethernet (all platforms). Open a Telnet session with the default router

IP address and log into the router with the default account name and password (guest/password) as follows.

telnet 10.0.0.1

user name – guest password – ********

Serial. On Windows, open the HyperTerminal application. The next steps may vary according to the version of Windows you use: a.

On the Windows Start menu, point to Programs, Accessories,

HyperTerminal, and then click HyperTerminal.

b.

Select the connection you created earlier, and then click OK.

Serial. On Linux, open a command window and issue the following command: minicom

2.

Open an Admin session and issue the set mgmt command to set up the management interface. See the iSR6152 Router CLI User's Guide for command descriptions.

QRouter #> admin start

Password – ******

QRouter (admin) #> set mgmt

Cabling Devices to the Router

Connect cables to the SFP transceivers and their corresponding devices. Devices can have either SFP or gigabit interface converters (GBIC). Lucent (LC)-type duplex fiber optic cable connectors are designed for SFP transceivers, while subscriber-connector (SC)-type connectors are designed for GBICs. Choose the fiber optic cable with the connector combination that matches the device you are connecting to the router.

Installing the Firmware

The router comes installed with the current firmware. As new firmware becomes available, you can upgrade the firmware from the management workstation. You can use Router Manager or the CLI to install new firmware.

ISR651103-00 C 3-11

3–Installation

Installing the Firmware

WARNING!!

Installing new firmware disrupts the router connectivity because you must reboot the router to activate the new firmware. T he reboot may result in the transfer of incorrect data between devices connected to the router. QLogic recommends that you suspend activity on the interfaces before activating the new firmware.

Using Router Manager to Install Firmware

To install firmware using Router Manager:

1.

In the topology view, double-click the router.

2.

In the Firmware Upload window, click Select to browse for and select the firmware file you want to upload.

3.

To begin the firmware load process, click Start.

A message box warns that the router will be reset to activate the firmware.

4.

To continue firmware installation, click OK, or click Cancel to terminate the firmware installation.

Using the CLI to Install Firmware

To use the CLI to install the firmware, transfer the firmware image file from a workstation to the router. Then use the CLI image unpack command to install the new firmware image.

To install firmware using the CLI:

1.

At the workstation prompt, enter the ftp command to go to the location on the router where you want to transfer the firmware image. For example:

C:\fwImage>ftp 172.17.137.190

Connected to 172.17.137.190.

220 (none) FTP server (GNU inetutils 1.4.2) ready.

2.

Enter your user name and password. For example:

User (172.17.137.190:(none)) – ftp

331 Guest login ok, type your name as password.

Password – ftp

230 Guest login ok, access restrictions apply.

3.

At the ftp prompt, type BIN to set binary mode. For example: ftp> bin

200 Type set to I.

3-12 ISR651103-00 C

3–Installation

Installing the Firmware

4.

Use the put command to transfer the firmware image file from the workstation to the router. For example: ftp> put isr-6152-3_3_0_x.bin

200 PORT command successful.

150 Opening BINARY mode data connection for

'isr-6152-3_3_0_x.bin'.

226 Transfer complete.

ftp – 4822816 bytes sent in 0.41Seconds 11878.86Kbytes/sec.

5.

Type quit.

The firmware image has been transferred to the router.

6.

Log on to the router as an administrator. For example: iSR6152 login: guest

Password: ********

Welcome to iSR6152

******************************************************

* *

* iSR6152 *

* *

****************************************************** iSR6152 #> admin start

Password : ****** iSR6152 (admin) #>

7.

Type the following command from the router, where x stands for the firmware image name: image unpack isr-6152-3_3_0_x.bin

The following message appears:

Unpack Completed. Please reboot the system for FW to take affect.

8.

Type reboot.

The following message appears:

Are you sure you want to reboot the System (y/n):

9.

To reboot the system, type y.

ISR651103-00 C 3-13

3–Installation

Installing the Firmware

3-14 ISR651103-00 C

4

Diagnostics and

Troubleshooting

Diagnostic information about the router is available through the chassis LEDs and the port LEDs. Diagnostic information is also available through the Router

Manager and CLI event logs and error messages. This chapter provides the following diagnostic and maintenance information:

Chassis Diagnostics

“Power-On Self-Test Diagnostics” on page 4-2

“LED Blink Patterns” on page 4-2

“Recovering a Router” on page 4-4

Chassis Diagnostics

The chassis LEDs show chassis diagnostics as shown in

Figure 4-1 .

Heartbeat LED Power LED

Figure 4-1. Chassis Diagnostic LEDs

System Fault LED

This section describes the following conditions:

“Input Power LED is Off” on page 4-2

“System Fault LED is On” on page 4-2

ISR651103-00 C 4-1

4–Diagnostics and Troubleshooting

Power-On Self-Test Diagnostics

Input Power LED is Off

The input power LED lights up to show that the router logic circuitry is receiving proper voltages. If the input power LED is off, follow these steps:

1.

Inspect power cord and connectors. Is the cord unplugged? Is the cord or connector damaged?

Yes—Make necessary corrections or repairs. If the condition remains, continue with

Step 2 .

No—Continue with

Step 2 .

2.

Inspect AC power source. Is the power source delivering the proper voltage?

Yes—Continue with Step 3

.

No—Make the necessary repairs. If the condition remains, continue with

Step 3 .

3.

Replace the router.

System Fault LED is On

The system fault LED blinks a specific pattern to indicate the problem. If the

system fault LED lights up, take necessary actions (see “LED Blink Patterns” on page 4-2 ).

Power-On Self-Test Diagnostics

The router performs a series of tests as part of its power-on procedure. The POST diagnostic program performs the following tests:

 Memory

 Flash validation

 PCI device discovery

 Management Ethernet port

LED Blink Patterns

The heartbeat and system fault LEDs show the operational status of the router.

When the POST completes with no errors, the heartbeat LED blinks once every second. When the router is in maintenance mode, the heartbeat and system fault

LEDs are on continuously.

All other system fault blink patterns show critical errors. The heartbeat LED shows an error blink pattern for the conditions listed in

Table 4-1 .

4-2 ISR651103-00 C

4–Diagnostics and Troubleshooting

LED Blink Patterns

Table 4-1. System Fault LED Blink Patterns

System Fault LED

OFF

3 Blinks, followed by pause

4 Blinks, followed by pause

5 Blinks, followed by pause

Condition

OK - Operational

System error

Management port IP address conflict

Over temperature

Heartbeat Blink Pattern

A blink pattern on the heartbeat LED of one second ON followed by one second

OFF means that the router is operating normally. The heartbeat LED shows this pattern when the router firmware is operational:

System Error Blink Pattern

The system fault LED generates a three-blink pattern (once per second) followed by a two second pause to indicate a system error:

Management Port IP Address Conflict Blink Pattern

The system fault LED generates a four-blink pattern (once per second) followed by a two second pause when the router detects an IP address conflict on the management Ethernet port:

You can clear the IP address conflict blinking using the CLI or the Router

Manager. Use the beacon OFF function.

ISR651103-00 C 4-3

4–Diagnostics and Troubleshooting

Recovering a Router

Over-Temperature Blink Pattern

The system fault LED generates a five-blink pattern (once per second) followed by a two-second pause when the router is in an over-temperature condition. For example, this occurs when the air temperature inside the router is over the failure temperature of 70 ° C (158 ° F).

If the system alert LED shows the over-temperature blink pattern, follow these steps:

1.

Inspect the chassis air vents. Are the intake and exhaust vents clear?

Yes—Continue with Step 2

.

No—Remove any debris from the fan intake and exhaust if necessary.

If the condition remains, continue with Step 2

.

2.

Consider the ambient air temperature near the router and clearance around the router. Make necessary corrections. If the condition remains: a.

Open a command line window and log on to the router. b.

Enter the shutdown command.

c.

Power down the router. d.

Contact your authorized maintenance provider.

Recovering a Router

You may have to recover a router for one of the following reasons:

 The password was changed and has been forgotten.

 The router’s management IP address is unknown.

To recover the router’s password, reset the password to the default by using the maintenance button (see

“Maintenance Button” on page 1-4 ).

You can recover the router’s IP address using either of the following methods:

 Connect to the serial console port (see

“Serial Port” on page 1-9 ), and then

use the CLI set mgmt command reconfigure the management port (see the iSR6152 Router CLI User's Guide).

 Use the maintenance button to reset the management port’s IP to the factory

default of 10.0.0.1 (see “Maintenance Button” on page 1-4

).

4-4 ISR651103-00 C

5

Removal and Replacement

This chapter provides removal and replacement procedures for the following field replaceable units (FRUs):

 SFP transceivers

 iSR6152 router

Removing and Replacing SFP Transceivers

You can remove and replace the SFP transceivers while the router is operating without damaging the router or the transceiver. However, doing so interrupts transmission on the affected port until the transceiver is installed.

To remove a transceiver, gently press the transceiver into the port to release the tension, and then pull the release tab or lever and remove the transceiver. Different transceiver manufactures have different release mechanisms. Consult the documentation for your transceiver.

To install a transceiver, insert the transceiver into the port and gently press until it snaps in place.

NOTE:

The SFP transceiver fits only one way. If the SFP does not install under gentle pressure, flip it over and try again.

Removing and Replacing the Router

Before you can remove and replace the router, you must turn off the power to the router and disconnect its power cable. The router loses all the Fibre Channel and

Ethernet connections.

Removing the Router

Perform the following steps, as applicable, to remove a router.

ISR651103-00 C 5-1

5–Removal and Replacement

Removing and Replacing the Router

To remove a router:

1.

Make sure all traffic (I/O operations to the router) subsides at the initiator systems.

2.

Save the configuration data of the router using the CLI FRU command (see the iSR6152 Router CLI User's Guide).

3.

Power down the router.

4.

Disconnect the power cable.

5.

Label all the cables so you can connect them to the same ports on the replacement router.

6.

Remove all the Fibre Channel and Ethernet cables.

7.

Remove the router from the enclosure where it is mounted.

Replacing the Router

Before replacing a router, you must first remove the previously installed router (as described in the preceding).

To install a replacement router:

1.

Mount the router in the enclosure.

2.

Reconnect the Fibre Channel and Ethernet cables to the ports where they were previously connected.

3.

Connect the power cable to the router.

4.

Using a management station, configure the management port IP address

(see “Configuring the Management Workstation” on page 3-6 ).

5.

Using a management workstation, restore the saved configuration or reconfigure the router as needed (see the iSR6152 Router CLI User's

Guide).

The replacement router should now be operational.

5-2 ISR651103-00 C

A

Simple Network

Management Protocol

(SNMP)

SNMP provides monitoring and trap functions for managing the router through third-party applications that support SNMP. The router firmware supports SNMP versions 1 and 2 and a QLogic (see

page A-2

). You may format the traps using

SNMP version 1 or 2 (see page A-10

).

SNMP Properties

You can set the SNMP properties using either the command line interface (CLI)

(see the iSR6152 Router CLI Users Guide) or Router Manager (see the iSR6152

Router Manager Users Guide).

Table A-1 lists the SNMP properties.

Parameter

Read community

Trap community

System location

Table A-1. SNMP Properties

Description

A password that authorizes an SNMP management server to read information from the router. This is a write-only field. The value on the router and the SNMP management server must be the same. The read community password can be up to

32 characters excluding the number sign (#), semicolon (;), and comma (,). The default is password is public.

A password that authorizes an SNMP management server to receive traps. This is a write-only field. The value on the router and the SNMP management server must be the same. The trap community password can be up to 32 characters excluding the number sign (#), semicolon (;), and comma (,). The default password is public.

Name of the router location. The name can be up to 64 characters excluding the number sign (#), semicolon (;), and comma

(,). The default is undefined.

ISR651103-00 C A-1

A–Simple Network Management Protocol (SNMP)

SNMP Trap Configuration

Parameter

System contact

Authentication traps

Table A-1. SNMP Properties (Continued)

Description

Name of the person to be contacted to respond to trap events.

The name can be up to 64 characters excluding the number sign (#), semicolon (;), and comma (,). The default is undefined.

Enables or disables authentication trap generation in response to authentication failures. The default is disabled.

SNMP Trap Configuration

SNMP trap configuration supports setting up to eight trap destinations. Choose from Traps 1–Trap 8 to configure each trap.

Table A-2 describes the parameters

for configuring a SNMP trap.

Table A-2. SNMP Trap Configuration Parameters

Parameter Description

Trap n enabled

Trap address *

Enables or disables trap n. If disabled, the trap is not configured.

IP address to which the SNMP traps are sent. A maximum of eight trap addresses are supported. The default address for traps is

0.0.0.0.

Port number on which the trap is sent. The default is 162.

Trap port *

Trap version SNMP version (1 or 2) with which to format traps.

Table Notes

* Trap address (other than 0.0.0.) and trap port combinations must be unique. For example, if trap 1 and trap 2 have the same address, and then they must have different port values. Similarly, if trap 1 and trap 2 have the same port value, they must have different addresses.

Management Information Base (MIB)

The following sections describe the QLogic management information base (MIB).

The MIB consists of four object groups:

System Information

Network Port Table

Fibre Channel Port Table

Sensor Table

A-2 ISR651103-00 C

A–Simple Network Management Protocol (SNMP)

Management Information Base (MIB)

System Information

The system information objects provide the system serial number, version numbers (hardware/software/agent), and number of ports (FC/GE).

qsrSerialNumber

Syntax: SnmpAdminString

Access: Read only

Description: System serial number.

qsrHwVersion

Syntax: SnmpAdminString

Access: Read only

Description: System hardware version number.

qsrSwVersion

Syntax: SnmpAdminString

Access: Read only

Description: System software (firmware) version number.

qsrNoOfFcPorts

Syntax: Unsigned32

Access: Read only

Description: Number of Fibre Channel ports on the system.

qsrNoOfGbEPorts

Syntax: Unsigned32

Access: Read only

Description: Number of GbE ports on the system.

qsrAgentVersion

Syntax: SnmpAdminString

Access: Read only

Description: Version number of the agent software on the system.

Network Port Table

The network port table contains a list of network ports that are operational on the router. The entries in this table include the management port and the GbE ports on the router.

ISR651103-00 C A-3

A–Simple Network Management Protocol (SNMP)

Management Information Base (MIB) qsrNwPortTable

Syntax: Sequence of QsrNwPortEntry

Access: Not accessible

Description: Entries in this table include the management port and the GbE ports on the router.

qsrNwPortEntry

Syntax: QsrNwPortEntry

Access: Not accessible

Description: Each entry (row) contains information about a specific network port.

QsrNwPortEntry

A network port entry consists of the following sequence of objects: qsrNwPortRole qsrNwPortIndex qsrNwPortAddressMode qsrIPAddressType qsrIPAddress qsrNetMask qsrGateway qsrMacAddress qsrNwLinkStatus qsrNwLinkRate

QsrPortRole unsigned32

INTEGER

InetAddressType

InetAddress

InetAddress

InetAddress

MacAddress

QsrLinkStatus

QsrLinkRate qsrNwPortRole

Syntax: QsrPortRole

Access: Not accessible

Description: Operational role of this port: management port or GbE port.

qsrNwPortIndex

Syntax: Unsigned32

Access: Not accessible

Description: A positive integer indexing each network port in a specific role.

A-4 ISR651103-00 C

A–Simple Network Management Protocol (SNMP)

Management Information Base (MIB) qsrNwPortAddressMode

Syntax: INTEGER

1 = Static

2 = DHCP

3 = Bootp

4 = RARP

Access: Read only

Description: Method by which the port gets its IP address.

qsrIPAddressType

Syntax: InetAddressType

Access: Read only

Description: IP address type: ipv4 or ipv6.

qsrIPAddress

Syntax: InetAddress

Access: Read only

Description: IP address of the port.

qsrNetMask

Syntax: InetAddress

Access: Read only

Description: Subnet mask for this port.

qsrGateway

Syntax: InetAddress

Access: Read only

Description: Gateway for this port.

qsrMacAddress

Syntax: IMacAddress

Access: Read only

Description: MAC address for this port.

qstNwLinkStatus

Syntax: QsrLinkStatus

Access: Read only

Description: Operational link status for this port.

ISR651103-00 C A-5

A–Simple Network Management Protocol (SNMP)

Management Information Base (MIB) qsrNwLinkRate

Syntax: QsrLinkRate

Access: Read only

Description: Operational link rate for this port.

Fibre Channel Port Table

This table contains a list of the Fibre Channel ports on the router.There are as many entries in this table as there are Fibre Channel ports on the router.

qsrFcPortTable

Syntax: Sequence of QsrFcPortEntry

Access: Not accessible

Description: List of the Fibre Channel ports on the router.There are as many entries in this table as there are Fibre Channel ports on the router.

qsrFcPortEntry

Syntax: QsrFcPortEntry

Access: Not accessible

Description: Each entry (row) contains information about a specific Fibre Channel port.

QsrFcPortEntry

A Fibre Channel port entry consists of the following sequence of objects: qsrFcPortRole qsrFcPortIndex qsrFcPortNodeWwn qsrFcPortWwn qsrFcPortId qsrFcPortType qsrFcLinkStatus qsrFcLinkRate

QsrPortRole

Unsigned32

PhysAddress

PhysAddress

PhysAddress

Unsigned32

QsrLinkStatus

QsrLinkRate qsrFcPortRole

Syntax: QsrPortRole

Access: Not accessible

Description: Operational role of this port: FCP mode or frame shuttle mode.

A-6 ISR651103-00 C

A–Simple Network Management Protocol (SNMP)

Management Information Base (MIB) qsrFcPortIndex

Syntax: Unsigned32

Access: Not accessible

Description: A positive integer indexing each Fibre Channel port in a specified role.

qsrFcPortNodeWwn

Syntax: PhysAddress

Access: Read only

Description: World wide name of the node that contains this port.

qsrFcPortWwn

Syntax: PhysAddress

Access: Read only

Description: World wide name for this port.

qsrFcPortId

Syntax: PhysAddress

Access: Read only

Description: Interface's 24-bit Fibre Channel address identifier.

qsrFcPortType

Syntax: Unsigned32

Access: Read only

Description: Type of Fibre Channel port, as indicated by the use of the appropriate value assigned by IANA.

The IANA-maintained registry for Fibre Channel port types can be found at: www.iana.org/assignments/fc-port-types qsrFcLinkStatus

Syntax: QsrLinkStatus

Access: Read only

Description: Current link status for this port.

ISR651103-00 C A-7

A–Simple Network Management Protocol (SNMP)

Management Information Base (MIB) qsrFcLinkRate

Syntax: QsrLinkRate

Access: Read only

Description: Current link rate for this port.

Sensor Table

This table contains a list of all the sensors on the router. There are as many entries (rows) in this table as there are sensors.

qsrSensorTable

Syntax: Sequence of QsrSensorEntry

Access: Not accessible

Description: List of all the sensors on the router. There are as many entries (rows) in this table as there are sensors.

qsrSensorEntry

Syntax: QsrSensorEntry

Access: Not accessible

Description: Each entry (row) corresponds to a single sensor.

QsrSensorEntry

A sensor entry consists of the following sequence of objects: qsrSensorType qsrSensorIndex qsrSensorUnits qsrSensorValue qsrUpperThreshold qsrLowerThreshold qsrSensorState

INTEGER

Unsigned32

INTEGER

Integer32

Integer32

Integer32

INTEGER qsrSensorType

Syntax: INTEGER

Temperature = 1

Access: Not accessible

Description: Type of data being measured by this sensor.

A-8 ISR651103-00 C

A–Simple Network Management Protocol (SNMP)

Management Information Base (MIB) qsrSensorIndex

Syntax: Unsigned32

Access: Not accessible

Description: A positive integer identifying each sensor of a specific type.

qsrSensorUnits

Syntax: INTEGER

Celsius = 1

Access: Read only

Description: Unit of measurement for the sensor.

qsrSensorValue

Syntax: Integer32

Access: Read only

Description: Current value of the sensor.

qsrUpperThreshold

Syntax: Integer32

Access: Read only

Description: Upper-level threshold for this sensor.

qsrLowerThreshold

Syntax: Integer32

Access: Read only

Description: Lower-level threshold for this sensor.

ISR651103-00 C A-9

A–Simple Network Management Protocol (SNMP)

Notifications qsrSensorState

Syntax: INTEGER

Access: Read only

Description: The state of this sensor, indicating the health of the system.

Unknown—Sensor value/thresholds cannot be determined.

Normal—Sensor value is within normal operational limits.

Warning—Sensor value is approaching a threshold.

Critical—Sensor value has crossed a threshold.

Notifications

This section describes the following router notification types and objects they use:

Notification Objects

Agent Start Up Notification

Agent Shut Down Notification

Network Port Down Notification

Fibre Channel Port Down Notification

Sensor Notification

Generic Notification

Notification Objects

This section defines the objects used in notifications.

qsrEventSeverity

Syntax: INTEGER

Access: Accessible for notify

Description: This notification indicates the severity of the event. The value clear specifies that a condition that caused an earlier trap is no longer present.

qsrEventDescription

Syntax: SnmpAdminString

Access: Accessible for notify

Description: A textual description of the event that occurred.

A-10 ISR651103-00 C

A–Simple Network Management Protocol (SNMP)

Notifications qsrEventTimeStamp

Syntax: DateAndTime

Access: Accessible for notify

Description: This notification indicates when the event occurred.

Agent Start Up Notification

The agent startup notification indicates that the agent on the router has started running.

qsrAgentStartup uses the following object:

 qsrEventTimeStamp

Agent Shut Down Notification

The agent shut down notification indicates that the agent on the router is shutting down.

qsrAgentShutdown uses the following object:

 qsrEventTimeStamp

Network Port Down Notification

The network port down notification indicates that the specified network port is

down. The next time the port comes up, this event is sent with the

qsrEventSeverity object set to clear.

qsrNwPortDown uses the following objects:

 qsrNwLinkStatus

 qsrEventTimeStamp

 qsrEventSeverity

Fibre Channel Port Down Notification

The Fibre Channel port down notification indicates that the specified Fibre

Channel port is down. The next time the port comes up, this event is sent with the

qsrEventSeverity object set to clear.

qsrFcPortDown uses the following objects:

 qsrFcLinkStatus

 qsrEventTimeStamp

 qsrEventSeverity

ISR651103-00 C A-11

A–Simple Network Management Protocol (SNMP)

Notifications

Sensor Notification

The sensor notification indicates that the state for the specified sensor is not

normal. When the sensor returns to the normal state, this event is sent with the

qsrEventSeverity object set to clear.

qsrSensorNotification uses the following objects:

 qsrSensorValue

 qsrSensorState

 qsrEventTimeStamp

 qsrEventSeverity

Generic Notification

The generic notification reports events other than the defined event types. It provides a description object that identifies the event in clear text.

qsrGenericEvent uses the following objects:

 qsrEventTimeStamp

 qsrEventSeverity

 qsrEventDescription

A-12 ISR651103-00 C

B

Log Messages

This appendix provides reference material on messages logged to a file. You can retrieve these message logs using either the CLI (see the iSR6152 Router CLI User’s Guide) or Router Manager (see the iSR6152 Router Manager User’s

Guide).

The message log is persistent, maintained across router power cycles and reboots. Log message categories include the following:

“Informational Log Messages” on page B-1

“Error Log Messages” on page B-9

“Fatal Log Messages” on page B-24

Informational Log Messages

The following sections list and describe the informational log messages by reporting module:

“Application Modules” on page B-2

“iSCSI Driver” on page B-4

“Fibre Channel Driver” on page B-4

“User Modules” on page B-6

“FCIP Module” on page B-8

“TOE Driver” on page B-9

“System Modules” on page B-9

ISR651103-00 C B-1

B–Log Messages

Informational Log Messages

Application Modules

Table B-1 lists informational log messages generated by the application modules.

ID

53254

53357

54274

54275

54276

54277

54306

54307

54308

54309

Table B-1. Application Modules—Informational Log Messages

Log Message No.

Description

System (router) Booting up

QLBA_ProcessTpb: De-compression failed. Disabling compression temporarily

QLFC_Login: Origin 0x%x, VP Index 0x%x, Id 0x%x

6

109

Router is booting up.

De-compression failed and is temporarily disabled.

1026 Fibre Channel login occurred, origin xx (1 = HBA,

2 = target, 3 = initiator), VP (virtual port) xx, ID (loop ID) xx.

QLFC_Login: Port ID %.2x%.2x%.2x

1027 Fibre Channel login occurred with port ID xx.xx.xx.

QLFC_Login: Node Name

%.2x%.2x%.2x%.2x%.2x%.2x%.2x%.2x

1028 Fibre Channel login occurred with WWNN xx.xx.xx.xx.xx.xx.xx.xx.

QLFC_Login: Port Name

%.2x%.2x%.2x%.2x%.2x%.2x%.2x%.2x

1029 Fibre Channel login occurred with WWPN xx.xx.xx.xx.xx.xx.xx.xx.

QLFC_Logout: Origin 0x%x, VP Index 0x%x, Id 0x%x 1058 Fibre Channel logout occurred, origin xx (1 = HBA,

2 = target, 3 = initiator), VP (virtual port) xx, ID (loop ID) x.

QLFC_Logout: Port ID %.2x%.2x%.2x

QLFC_Logout: Node Name

%.2x%.2x%.2x%.2x%.2x%.2x%.2x%.2x

QLFC_Logout: Port Name

%.2x%.2x%.2x%.2x%.2x%.2x%.2x%.2x

1059 Fibre Channel logout occurred with port ID xx.xx.xx.

1060 Fibre Channel logout occurred with WWNN xx.xx.xx.xx.xx.xx.xx.xx.

1061 Fibre Channel logout occurred with WWPN xx.xx.xx.xx.xx.xx.xx.xx.

B-2 ISR651103-00 C

B–Log Messages

Informational Log Messages

ID

54359

54368

54938

54939

54940

54941

54943

54945

54947

54948

54963

54986

55299

Table B-1. Application Modules—Informational Log Messages (Continued)

Log Message

QLFC_HandleTeb: FC Login. VP 0x%x

QLFC_CreateVirtualInitiatorObject: Maximum host

(%d) limit reached.

QLIS_HandleTeb: UTM_EC_OPEN_CONNECTION

QLIS_HandleTeb: UTM_EC_CLOSE_CONNECTION or

UTM_EC_CONNECTION_CLOSED

QLIS_HandleTeb: UTM_EC_CONNECTION_OPENED

QLIS_HandleTeb:iSNS Server Open Connection succeeded

QLIS_HandleTeb: UTM_EC_ISNS_SCN

QLIS_HandleTeb: UTM_EC_ISNS_CLIENT_DISCOVERED

QLIS_HandleTeb: UTM_EC_CLOSE_CONNECTION

QLIS_HandleTeb: UTM_EC_CONNECTION_CLOSED

QLIS_SetDdbEntryContinue:[%d:%d] Remote system connection established

QLIS_HandleSessionTimer: Re-enabling compression

QLSC_CollectBUVUIO: Freeing dead TRB: State

0x%02X, AbortReason %d, Flags 0x%02X

No.

Description

1111 Fibre Channel login event notification, VP (virtual port) xx.

1120 Maximum number of support hosts dd has been reached.

1690 Event notification: iSCSI open connection request.

1691 Event notification: iSCSI close connection request or connection closed.

1692 Event notification: iSCSI connection opened.

1693 Event notification: connection opened with iSNS server.

1695 Event notification: iSNS SCN received.

1697 Event notification: iSNS client discovered.

1699 iSCSI close connection request received.

1700 iSCSI connection closed.

1715 Remote system connection established using DDB d:d.

1738 Re-enabling compression.

2051 TRB freed, State xx, Abort Reason d, Flags xx.

ISR651103-00 C B-3

B–Log Messages

Informational Log Messages

ID

86343

86347

86349

86352

86874 iSCSI Driver

Table B-2 lists the informational log messages that are common to all iSCSI ports: 1 (GE1), 2 (GE2), 3 (GE3), and 4

(GE4). Log messages beginning with #0 denote iSCSI port 1 (GE1), #1 denotes iSCSI port 2 (GE2), #2 denotes iSCSI port 3 (GE3), and #3 denotes iSCSI 4 (GE4).

Table B-2. iSCSI Driver—Informational Log Messages

Log Message

#%d: QLPortUp: Set link configuration 0x%x

#%d: QLDisable: Restart RISC

#%d: QLEnable: Restart RISC to update EEPROM

#%d: QLPortDown: Set link configuration 0x%x

#%d: QLIsrDecodeMailbox: Link up

No.

327

331

333

336

858

Description iSCSI port enabled, port up.

Restart iSCSI processor (RISC).

EEPROM updated, restart iSCSI processor (RISC).

iSCSI port disabled, port down.

Link up reported by iSCSI processor for GE1 or GE 2.

Fibre Channel Driver

Table B-3 lists the informational log messages that are common to both Fibre Channel ports: 1 (FC1) and 2 (FC2). Log

messages beginning with #0 denote Fibre Channel port 1 (FC1) and log messages beginning with #1 denote Fibre

Channel port 2 (FC2).

ID

118882

Table B-3. Fibre Channel Driver—Informational Log Messages

Log Message

#%d: QLIoctlDisable: Reset adapter

No.

98

Description

Request to reset the Fibre Channel processor (adapter) received from IOCTL interface.

B-4 ISR651103-00 C

B–Log Messages

Informational Log Messages

ID

119088

119089

119090

119092

119093

119097

119552

119553

119554

Table B-3. Fibre Channel Driver—Informational Log Messages (Continued)

Log Message

#%d: QLIsrEventHandler: LIP occurred (%x): mailbox1 = %x

#%d: QLIsrEventHandler: LIP reset occurred (%x): mailbox1 = %x

#%d: QLIsrEventHandler: Link up (%x) mailbox1

= %x

#%d: QLIsrEventHandler: Link mode up (%x): Run-

TimeMode=%x

#%d: QLIsrEventHandler: RSCN update (%x) rscnInfo: %x

#%d: QLIsrEventHandler: Port update (%x) mb1-3 %x %x %x

#%d: QLFcipIsrEventHandler: Link up (%x) mailbox1 = %x

#%d: QLFcipIsrEventHandler: Link down (%x)

#%d: QLFcipIsrEventHandler: Link mode up (%x)

No.

304

305

306

308

309

313

768

769

770

Description

Fibre Channel loop initialization procedure (LIP) occurred. The LIP type is reported, as is the contents of the Fibre Channel processor’s mailbox 1 register.

Fibre Channel LIP reset occurred. The LIP reset type is reported, as is the contents of the Fibre Channel processor’s mailbox 1 register.

Fibre Channel link up occurred. Event status is reported, as is the contents of the Fibre Channel processor’s mailbox 1 register.

Fibre Channel link up occurred. Event status is reported, as is the RunTimeMode (0 = loop, 1 = point-to-point).

A RSCN was received. Event status is reported, as is the RSCN information.

Request to reset the Fibre Channel processor (adapter) received from IOCTL interface.

Fibre Channel loop initialization procedure (LIP) occurred. The LIP type is reported, as is the contents of the Fibre Channel processor’s mailbox 1 register.

Fibre Channel LIP reset occurred. The LIP reset type is reported, as is the contents of the Fibre Channel processor’s mailbox 1 register.

Fibre Channel link up occurred. Event status is reported, as is the contents of the Fibre Channel processor’s mailbox 1 register.

ISR651103-00 C B-5

B–Log Messages

Informational Log Messages

User Modules

Table B-4 lists the log messages generated by the user modules.

Table B-4. User Modules—Informational Log Messages

ID Log Message

151842 FW Upgrade performed: new version is: %d.%d.%d.%d

151843 REBOOT/SHUTDOWN Command from user. Code=%d

151889 #%d: qapisetfcinterfaceparams_1_svc: FC port configuration changed

151890 #%d: qapisetiscsiinterfaceparams_1_svc: iSCSI port configuration changed

151891 #%d: qapisetisns_1_svc:iSNS configuration changed

151892 qapisetntpparams_1_svc: NTP configuration changed

151893 #%d: qapisetvlanparams_1_svc: VLAN configuration changed

151896 qapisetmgmintfcparams_1_svc:Management port configuration changed

151897 qapisetbridgebasicinfo_1_svc:Bridge configuration changed

151898 qapimapremote_1_svc: Remotemap added for local device %.2x:%.2x:%.2x:%.2x:%.2x:%.2x:%.2x:%.2x

No.

290

291

337

338

339

340

341

344

345

346

Description

Performed router firmware upgrade, new version number is d.d.d.d.

User performed a router reboot or shutdown.

Fibre Channel port configuration has been modified.

iSCSI port configuration has been modified.

iSNS configuration has been modified.

NTP configuration has been modified.

VLAN configuration has been modified.

Management Ethernet port configuration has been modified.

Router configuration has been modified.

Remotemap added for local Fibre Channel device

WWPN xx.xx.xx.xx.xx.xx.xx.xx.

B-6 ISR651103-00 C

B–Log Messages

Informational Log Messages

Table B-4. User Modules—Informational Log Messages (Continued)

ID Log Message

151899 qapimapremote_1_svc: Remotemap added to remote device %.2x:%.2x:%.2x:%.2x:%.2x:%.2x:%.2x:%.2x

151900 qapiunmapremote_1_svc: Remotemap removed for local device

%.2x:%.2x:%.2x:%.2x:%.2x:%.2x:%.2x:%.2x

151901 qapiunmapremote_1_svc: Remotemap removed to remote device

%.2x:%.2x:%.2x:%.2x:%.2x:%.2x:%.2x:%.2x

151902 qapimaptargettoinitiator_1_svc: Localmap added for initiator

%.2x:%.2x:%.2x:%.2x:%.2x:%.2x:%.2x:%.2x

151903 qapimaptargettoinitiator_1_svc: Localmap added to target device

%.2x:%.2x:%.2x:%.2x:%.2x:%.2x:%.2x:%.2x

151904 qapiunmaptargettoinitiator_1_svc: Localmap removed for initiator device

%.2x:%.2x:%.2x:%.2x:%.2x:%.2x:%.2x:%.2x

151905 qapiunmaptargettoinitiator_1_svc: Localmap removed to target device

%.2x:%.2x:%.2x:%.2x:%.2x:%.2x:%.2x:%.2x

151906 qapimaptargettoinitiator_1_svc: Localmap added for initiator %s

151907 qapiunmaptargettoinitiator_1_svc: Localmap removed for initiator %s

No.

347

348

349

350

351

352

353

354

355

Description

Remotemap added for remote Fibre Channel device

WWPN xx.xx.xx.xx.xx.xx.xx.xx.

Remotemap removed for local Fibre Channel device

WWPN xx.xx.xx.xx.xx.xx.xx.xx.

Remotemap removed for remote Fibre Channel device

WWPN xx.xx.xx.xx.xx.xx.xx.xx.

Localmap added for Fibre Channel initiator WWPN xx.xx.xx.xx.xx.xx.xx.xx.

Localmap added to Fibre Channel target device WWPN xx.xx.xx.xx.xx.xx.xx.xx.

Localmap removed for Fibre Channel initiator.

Localmap removed to Fibre Channel target device.

Localmap added for iSCSI initiator

"iqn.dddd-dd.ttt.ttt.ttt.......".

Localmap removed for iSCSI initiator

"iqn.dddd-dd.ttt.ttt.ttt.......".

ISR651103-00 C B-7

B–Log Messages

Informational Log Messages

Table B-4. User Modules—Informational Log Messages (Continued)

ID Log Message

151908 GE%d: Port status changed by user to ENABLED.

151909 GE%d: Port status changed by user to DISABLED.

151910 FC%d: Port status changed by user to ENABLED.

151911 FC%d: Port status changed by user to DISABLED.

152069 qapisetfcipparams_1_svc: FCIPROUTE %d Added

152070 qapisetfcipparams_1_svc: FCIPROUTE %d Modified

152071 qapisetfcipparams_1_svc: FCIPROUTE %d Removed

No.

356

357

358

359

517

518

519

Description

User enabled GE port d.

User disabled GE port d.

User enabled Fibre Channel port d.

User disabled Fibre Channel port d.

FCIP route #d added.

FCIP route #d modified.

FCIP route #d removed.

FCIP Module

Table B-5 lists the informational log messages generated by the FCIP module.

Table B-5. FCIP Module—Informational Log Messages

ID Log Message

184524 qlFcip_Linkchange#%d: GigE Link Down

184525 qlFcip_Linkchange#%d: GigE Link Up

No.

204

205

Description

FCIP Route GbE link d (1 or 2) is down.

FCIP Route GbE link d (1 or 2) is up.

B-8 ISR651103-00 C

B–Log Messages

Error Log Messages

TOE Driver

Table B-6 lists the informational log messages generated by the TOE driver.

Table B-6. TOE Driver—Informational Log Messages

ID Log Message

217350 QL3022:eth%x: Interface is down

No.

262

Description

The GbE interface d (0 or 1) used for an FCIP route is down.

System Modules

Table B-7 lists the informational log messages generated by the system modules.

Table B-7. System Modules—Informational Log Messages

ID Log Message

249862 “Temperature is back to normal range %d\n"

No.

6

Description

The router temperature has returned to the normal operating range and is d (C).

Error Log Messages

The following sections list and describe the error log messages by reporting module:

“Application Modules” on page B-10

“iSCSI Driver” on page B-18

“Fibre Channel Driver” on page B-19

“User Modules” on page B-22

“System Modules” on page B-24

ISR651103-00 C B-9

B–Log Messages

Error Log Messages

Application Modules

Table B-8 lists the error log messages generated by the application modules.

ID

40967

40996

41004

41058

41060

41067

41077

41096

41106

Table B-8. Application Modules—Error Log Messages

Log Message

QLBA_NullDoorbell: driver unloaded, port disabled

QLBA_ProcessTrb: Processing unsupported ordered tag command

QLBA_ProcessTrb: Processing unsupported head of queue tag command

QLBA_CreateTargetDeviceObject: Too many devices

QLBA_CreateTargetNodeObject: Too many devices

QLBA_CreateLunObject: LunObject memory unavailable

QLBA_CreateInitiatorObject: Too many initiators

QLBA_DisplayTargetOperationStatus: PCI Error,

Status 0x%.2x

QLBA_DisplayInitiatorOperationStatus: DMA Error,

Status 0x%.2x

No.

7

36

44

98

100

107

117

136

146

Description

NULL doorbell routine for unloaded drivers. When a driver is unloaded, the doorbell routine is redirected to this NULL routine.

Processing unsupported ordered tag task management command.

Processing unsupported head-of-queue task management command.

Unable to create an object for the target device: exceeded the maximum number of target devices.

Unable to create an object for the target node: exceeded the maximum number of target devices.

Memory unavailable for LUN object.

Unable to create an object for initiator object: exceeded the maximum number of initiators.

Process control block status indicates that a PCI error occurred during a target operation.

Process control block status indicates that a DMA error occurred during an initiator operation.

B-10 ISR651103-00 C

B–Log Messages

Error Log Messages

ID

41107

41111

41234

41238

41257

41265

41267

41268

41270

41272

Table B-8. Application Modules—Error Log Messages (Continued)

Log Message

QLBA_DisplayInitiatorOperationStatus: Transport

Error, Status 0x%.2x

QLBA_DisplayInitiatorOperationStatus: Data

Overrun, Status 0x%.2x

QLIS_LoginPduContinue: Operation failed.

Initiator 0x%x, TPB status 0x%x

QLKV_ValidateLoginTransitCsgNsgVersion failed

(status 0x%x)

QLIS_LoginPduContinue: Invalid initiator name.

Initiator:

QLIS_LoginPduContinue: Target not configured for

Portal

QLIS_LoginPduContinue: Target not found. Target name:

QLIS_LoginPduContinue: Missing target name

QLIS_LoginPduContinue: TSIH is 0 but

InitiatorName key/value not provided

QLIS_LoginPduContinue: CONN_STATE_IN_LOGIN,

Unknown InitTaskTag

No.

147

151

274

278

297

305

307

308

310

312

Description

Process control block status indicates that a transport error (protocol) occurred during an initiator operation.

Process control block status indicates that a data overrun error occurred during an initiator operation.

iSCSI login failed between receipt of PDU and request for the data segment.

iSCSI login failed due to unsupported version number in received login PDU.

iSCSI Login PDU contains invalid initiator name. The format and character set used to form the initiator name is invalid.

iSCSI target login was attempted to a portal (iSCSI1 or iSCSI2) on which the target is not presented.

iSCSI Login PDU received for a target with a target name unknown to the router.

iSCSI Login PDU received without a target name for a normal session. iSCSI Login PDU received without an initiator name key/value.

iSCSI Login PDU received with an incorrect initiator task tag for a session which is partially logged in. This would occur if a login PDU other than the initial login PDU used an initiator task tag which was different than the initiator task tag provided in the initial login PDU.

ISR651103-00 C B-11

B–Log Messages

Error Log Messages

ID

41283

41284

41353

41354

41508

41626

41629

Table B-8. Application Modules—Error Log Messages (Continued)

Log Message

QLIS_LoginPduContinue: TSIH 0x%x out of range

QLIS_LoginPduContinue: Session does not exist, invalid TSIH 0x%x

QLIS_LoginPduContinue CHAP Validation Failure

QLIS_LoginPduContinue Unexpected CHAP key detected

QLBI_SetPortInfo: QLUT_AllocatePortalObject failed (PortType 0x%x, PortId 0x%x)

QLBI_GetLunInfo: INQUIRY failed, TPB status 0x%x

QLBI_GetLunInfo: QLBI_PassthruCommand failed for

INQUIRY (page code 0x83)

No.

323

324

393

394

548

666

669

Description iSCSI Login PDU was received with a TSIH out of range.

This would occur if the iSCSI initiator attempting the login failed to used the TSIH value provided in the Target Login

Response PDU (router is target) in subsequent login

PDUs.

iSCSI Login PDU was received with an invalid TSIH value. The TSIH is invalid because there is no session with that TSIH value. This would occur if the iSCSI initiator attempting the login failed to used the TSIH value provided in the target login response PDU (router is target) in subsequent login PDUs.

CHAP validation failed during login.

Unexpected CHAP key.

Failed to allocate an object for Set Port Info IOCTL processing:

PortType: 0 = Fibre Channel, 1 = iSCSI

PortId: 0 = FC1 or iSCSI1(GE1), 1 = FC2 or iSCSI2 (GE2)

Inquiry command failed. The Inquiry command was issued by the router as part of its discovery process.

Pass-Through command for Inquiry command for page

83 failed. The Inquiry command was issued by the router as part of its discovery process.

B-12 ISR651103-00 C

B–Log Messages

Error Log Messages

ID

41635

41636

41696

41700

41701

41717

41750

41768

Table B-8. Application Modules—Error Log Messages (Continued)

Log Message

QLBI_GetLunInfo: QLBI_PassthruCommand failed for

READ CAPACITY

QLBI_GetLunInfo: READ CAPACITY failed, TPB status

0x%x

QLBI_PassthruCommandCompletion: Passthru command aborted

QLBI_Passthru: Invalid CDB length %d bytes

QLBI_Passthru: Invalid data length %d bytes

QLBI_PassthruCommand: command interrupted or timed out

QLBI_Ioctl: ERROR: Operation (0x%x) not supported in this mode

QLBI_GetLunList: REPORT LUNS command failed

No.

675

676

736

740

741

757

790

808

Description

Pass-Through command for Read Capacity command failed. The Read Capacity command was issued by the router as part of its discovery process.

Read Capacity command failed. The Read Capacity command was issued by the router as part of its discovery process.

Pass-Through command issued by management utiltiy

(such as Router Manager) was aborted.

Pass-Through command issued by management utility

(such as the Router Manager) failed due to invalid CDB length.

Pass-Through command issued by management utility

(such as the Router Manager) failed due to invalid data length.

Pass-Through command issued by management application (such as the Router Manager) was interrupted or timed out.

IOCTL operation unsupported. Operation code provided in log message.

Report LUNs command failed. The Report LUNs command was issued by the router as part of its discovery process.

ISR651103-00 C B-13

B–Log Messages

Error Log Messages

ID

41769

41771

41994

41995

42002

42024

42027

42068

42069

42072

Table B-8. Application Modules—Error Log Messages (Continued)

Log Message

QLBI_GetLunList: REPORT LUNS command failed with

CHECK CONDITION, SCSI STATUS 0x%02X

QLBI_GetLunList: Lun allocation failed for

LunId %d

QLFC_Login: VpIndex (%d) out of range

No.

809

811

Description

Report LUNs command failed with check condition status. The Report LUNs command was issued by the router as part of its discovery process.

Failed to allocate LUN object: out of resources.

QLFC_Login: VP Index 0x%x not configured

QLFC_Login: Can't open connection

QLFC_Logout: No active path to device. WWPN:

%.2X%.2X%.2X%.2X%.2X%.2X%.2X%.2X

QLFC_Logout: VP Index 0x%x not configured

QLFC_HandleTeb: System Error

QLFC_HandleTeb: Driver Fatal Error

QLFC_HandleTeb: FC Logout

1034 Login attempted using Fibre Channel virtual port (VP) index that is out-of-range (range = 0–31). Index reported in log message.

1035 Login attempted using Fibre Channel VP index that has not been configured. Operation attempted on an unconfigured VP.

1042 Attempting login but Fibre Channel connection cannot be opened.

1064 Attempting logout of device for which there is no active path (WWPN not found).

1067 Logout attempted using Fibre Channel VP index that has not been configured. Operation attempted on an unconfigured VP.

1108 Event notification: Fibre Channel processor encountered a system error (unrecoverable firmware error).

1109 Event notification: Fibre Channel driver encountered a fatal error.

1112 Event notification: Fibre Channel port logged out.

B-14 ISR651103-00 C

B–Log Messages

Error Log Messages

ID

42242

42252

42258

42404

42648

42649

42654

43012

43013

43265

43267

Table B-8. Application Modules—Error Log Messages (Continued)

Log Message No.

Description

QLIS_AllocateSessionObject: Out of session resources

QLIS_EnqueueiScsiPdu: Duplicate PDU, CmdSN %d

(0x%x), dropping it

QLIS_InstantiateSession: Can't add Initiator to the database

QLIS_ProcessStartTrb: [%d] CmdSN %ld is out of range (%ld - %ld), Cdb[0] 0x%02X, DataXferLen

0x%x.

1282 Failed to allocate object for iSCSI session: out of session resources.

1292 Received iSCSI PDU with duplicate command sequence number (CmdSN). Command PDU is dropped.

1298 Unable to allocate iSCSI initiator object while instantiating session.

QLIS_HandleTeb: Driver Fatal Error

QLIS_HandleTeb: Unload Driver

1444 Failed to execute iSCSI Command PDU because its

CmdSN is out-of-range. Log message contains the incorrect CmdSN, the valid CmdSN range, the first byte of the CDB, and the data length.

1688 Event notification: iSCSI driver encountered a fatal error.

1689 Event notification: an IOCTL request was received to unload the iSCSI driver.

QLIS_HandleTeb: iSNS Connection Failed

QLSC_CollectBUVUIO: Allocation of DSD failed

QLSC_CollectBUVUIORecover: Allocation of DSD failed

1694 Event notification: attempt to connect to the iSNS server failed.

2052

2053 iSNS connection failed.

Break up I/O DSD allocation failed.

QLUT_AllocateTpbExtension: TPB allocation failed 2305 Break up I/O recover DSD allocation failed.

QLUT_AllocateTpbExtension: Data buffer allocation failed (length %d)

2307 Data buffer allocation failed (length %d) during tpb extension allocation.

ISR651103-00 C B-15

B–Log Messages

Error Log Messages

ID

43268

43269

43270

43271

43272

43273

43280

43281

43282

43283

43284

43285

43286

43287

Table B-8. Application Modules—Error Log Messages (Continued)

Log Message No.

Description

QLUT_AllocateTpbExtension: Alloc of DSD failed for buffer len %d

2308 Allocation of DSD failed during Tpb extension allocation.

Buffer length %d.

QLFCIP_IncomingFrame: BUGCHECK: Trb (0x%p)

ValidFlag (0x%x) Direction (0x%x)

QLFCIP_IncomingFrame: GetFcipMapPortal failed

QLFCIP_IncomingFrame: Got Status aborted pTrb->pBufDescList[0]:%p Trb Direction:0x%x

2309 FCIP incoming frame: BUGCHECK: Trb (0x%p)

ValidFlag (0x%x) Direction (0x%x).

2310 FCIP incoming frame: GetFcipMapPortal failed.

2311 FCIP incoming frame: Got Status aborted pTrb->pBufDescList[0]:%p Trb Direction:0x%x.

QLFCIP_SystemError: System error

QLFCIP_SystemError: QLOP_IssuePortEnable failed

QLFCIP_HandleTeb: Driver Fatal error

2312 FCIP system error.

2313 FCIP system error: QLOP_IssuePortEnable failed.

2320 FCIP handle Teb: Driver Fatal error.

2321 FCIP configure portal: Find portal object failed for

QLUT_TYPE_FC, PortId (%d).

QLFCIP_ConfigPortal: Find portal object failed for QLUT_TYPE_FC, PortId (%d)

QLFCIP_ConfigPortal: QLFCIP_ConfigPortal:

Invalid PortId for FCIP link PortID(%d)

2322 FCIP configure portal: QLFCIP_ConfigPortal: Invalid

PortId for FCIP link PortID(%d).

QLUT_AllocateFcipTrbPool: Allocation failed

(size 0x%x))

2323 FCIP allocate TRB pool: Allocation failed (size 0x%x).

QLUT_GetFcipTrb: Null portal object in map table 2324 FCIP Trb: Null portal object in map table.

QLUT_GetFcipTrb: Unable to get the Free Trb 2325 FCIP get TRB: Null portal object in map table.

QLUT_GetFcipTrb: Duplicate allocation of FcipTrb

(0x%p)

2326 FCIP get TRB: Duplicate allocation of FcipTrb (0x%p).

QLUT_FreeFcipTrb: Null portal object in map table 2327 FCIP free TRB: Null portal object in map table.

B-16 ISR651103-00 C

B–Log Messages

Error Log Messages

ID

43288

43289

43296

43297

43298

43299

43300

43521

43522

Table B-8. Application Modules—Error Log Messages (Continued)

Log Message

QLUT_FreeFcipTrb: Duplicate Free of FcipTrb

(0x%p)

QLUT_InitializeFcipBufDescPool: Memory allocation for FCIP_BUF_EXT_DESC failed (size

0x%x)

QLUT_FreeFcipDataBuffers: Duplicate Freeing of

DataBuf (0x%p)

QLUT_AllocateFcipDataBuffers: Duplicate allocation of DataBuffer (0x%p)

QLUT_AllocateFcipDataBuffer: Got NULL PORTAL

Object in map table MEM LEAK!!!!!

QLUT_DeallocateFcipDataBuffer: Null portal object in map table

QLUT_CreateFcipDataBufferpool: Allocation of 32K buffers from LargeBufferPool failed

QLSC_BreakupVUIOAllocPhase: TPB allocation failed

QLSC_BreakupVUIOAllocPhase: Data buffer and TPB allocation failed

No.

Description

2328 FCIP free TRB: Duplicate Free of FcipTrb (0x%p).

2329 FCIP initialize buffer descriptor pool: memory allocation for FCIP_BUF_EXT_DESC failed (size 0x%x).

2336 FCIP free data buffers: Duplicate Freeing of DataBuf

(0x%p).

2337 FCIP allocate data buffers: Duplicate allocation of

DataBuffer (0x%p).

2338 FCIP allocate data buffer: Got NULL PORTAL Object in map table MEM LEAK.

2339 FCIP de-allocate data buffer: Null portal object in map table.

2340 FCIP create data buffer pool: Allocation of 32K buffers from LargeBufferPool failed.

2561 Break up I/O: TPB allocation failed.

2562 Break up I/O: Data buffer and TPB allocation failed.

ISR651103-00 C B-17

B–Log Messages

Error Log Messages iSCSI Driver

Table B-9 lists the error log messages common to all iSCSI ports: 1 (GE1), 2 (GE2), 3 (GE3), and 4 (GE4). Log

messages beginning with #0 denote iSCSI port 1 (GE1), #1 denotes iSCSI port 2 (GE2), #2 denotes iSCSI port 3

(GE3), and #3 denotes iSCSI 4 (GE4).

ID

73990

74046

74056

74057

74065

74241

74577

74587

74656

74661

Table B-9. iSCSI Driver—Error Log Messages

Log Message

#%d: QLUtmIoctlEnable: Initialize FW failed

#%d: QLPortUp: MBOX_CMD_SET_PORT_CONFIG %04x failed %04x

#%d: QLRunDiag: MBOX Diag test internal loopback failed %x %x

#%d: QLRunDiag: MBOX Diag test external loopback failed %x %x

#%d: QLPortDown: MBOX_CMD_SET_PORT_CONFIG %04x failed %04x

#%d: QLiSNSEnableCallback: iSNS Server TCP Connect failed

#%d: QLIsrDecodeMailbox: NVRAM invalid

#%d: QLIsrDecodeMailbox: Link down

#%d: QLReadyTimer: Adapter missed heartbeat for %d seconds. Time left %d

#%d: QLTimer: Abort pTpb=%p, Type %x, Timeout

0x%x DrvCount 0x%x, DdbIndex 0x%x

No.

262

318

328

329

337

513

849

859

928

933

Descriiption

The iSCSI processor failed firmware initialization.

The iSCSI processor command to enable a GE port failed.

The iSCSI processor failed the internal loopback test.

The iSCSI processor failed the external loopback test.

The iSCSI processor command to disable a GE port failed.

The iSCSI processor could not connect with the iSCSI name server (iSNS).

The iSCSI processor reported that the iSCSI port

NVRAM contains invalid data (checksum error).

The iSCSI processor reported a link down condition.

The driver failed to receive a heartbeat from the iSCSI processor for the specified number of seconds.

The driver timed out an iSCSI processor operation and is aborting the operation.

B-18 ISR651103-00 C

B–Log Messages

Error Log Messages

ID

74663

74665

74784

74800

Table B-9. iSCSI Driver—Error Log Messages (Continued)

Log Message

#%d: QLReadyTimer: MBOX_CMD %04x %04x %04x %04x

%04x %04x %04x %04x timed out

#%d: QLReadyTimer: QLiSNSReenable failed.

#%d: QLUpdateInitiatorData: No more room in Initiator Database.

#%d: QLSetTargetData: No more room in Target

Database.

No.

Descriiption

935

937

The driver timed out an iSCSI processor mailbox command.

The driver timed out while attempting to reconnect with the iSNS.

1056 The driver’s initiator database is full. The driver is capable of storing 1024 iSCSI initiators in its database. Use the CLI or Router Manager to remove unwanted/unused iSCSI initiators.

1072 The driver’s target database is full. Use the CLI or

Router Manager to remove unwanted/unused iSCSI targets.

Fibre Channel Driver

Table B-10 lists the error log messages common to both Fibre Channel ports, 1 (FC1) and 2 (FC2). Log messages

beginning with #0 denote Fibre Channel port 1 (FC1); log messages beginning with #1 denote Fibre Channel port 2

(FC2).

Table B-10. Fibre Channel Driver—Error Log Messages

ID Log Messages

106583 #%d: QLUtmReceiveIo: Path invalid/FW No resource count %x

No.

87

Description

The Fibre Channel processor received a SCSI command for an unknown target path or has run out of resources to execute additional commands.

ISR651103-00 C B-19

B–Log Messages

Error Log Messages

Table B-10. Fibre Channel Driver—Error Log Messages (Continued)

ID Log Messages

106589 #%d: QLIoctlEnable: Adapter disabled

106590 #%d: QLIoctlEnable: Initialize FW error

106592 #%d: QLIoctlRunDiag: Diagnostic loopback command failed %x

% %x %x

106593 #%d: QLIoctlDisable: Re-initialize adapter failed

106595 #%d: QLUtmReceiveIo: Invalid VP Loop Id 0x%x

106803 #%d: QLIsrEventHandler: Link down (%x)

No.

93

94

96

97

99

307

Description

The Fibre Channel processor was disabled by an IOCTL request to the driver.

The Fibre Channel processor firmware failed initialization. The request to initialize was received by the driver in an IOCTL request.

The Fibre Channel processor failed the external loopback test.

106813 #%d: QLIsrEventHandler: Unexpected async event

(%x), MB1=%x, MB2=%x, MB3=%x, MB4=%x, MB5=%x,

MB6=%x, MB7=%x

106846 #%d: QLProcessResponseQueueFS: TRB is NULL: %d

106853 #%d: QLTimer: Link error count (0x%x) exceeded, link down

106912 #%d: QLReserveLoopId: out of loop Ids

317

350

357

416

The Fibre Channel processor failed to re-initialize in response to an IOCTL disable request.

Invalid Virtual Port loop ID.

The Fibre Channel processor reported a link down condition.

The Fibre Channel processor reported an unexpected asynchronous event. The mailbox registers provide status, event code, and data related to the event.

FCIP Response queue entry TRB pointer is NULL.

The driver has determined that the Fibre Channel link is unreliable and unusable due to the number of errors encountered. The link has been taken down.

The Fibre Channel processor was unable to obtain the number of loop IDs required. This failure occurs only when the Fibre Channel processor is running multi-ID firmware.

B-20 ISR651103-00 C

B–Log Messages

Error Log Messages

Table B-10. Fibre Channel Driver—Error Log Messages (Continued)

ID Log Messages

106928 #%d: QLMarkDeviceOffline: Device Id: %x marked offline, cLinkDownTimeout = %x, cPortDownRetryCount=%x

106948 #%d: QLSnsGetAllNext: Name server login FAILED %x

107029 #%d: QLUpdateDeviceData: out of slots in host database

107030 #%d: QLUpdateDeviceData: out of slots in target database

107041 #%d: QLUpdateDeviceDatabase 0x%x: GET_ID failed %x

107056 #%d: QLUpdateDeviceDatabase 0x%x: out of slots in host database

107058 #%d: QLUpdateDeviceDatabase 0x%x:

MBOX_CMD_GET_VP_DATABASE failed %x

107078 #%d: QLUpdatePort 0x%x: out of slots in host database

107254 #%d: QLUpdateSinglePortCont 0x%x: out of slots in host database

107267 #%d: QLFcipIsrEventHandler: System error event

(%x), MB1=%x, MB2=%x, MB3=%x, MB4=%x, MB5=%x,

MB6=%x, MB7=%x

No.

432

452

533

534

545

560

562

582

758

771

Description

The driver was unable to re-establish connection to the target within the timeout and retry counts, and is therefore marking it offline.

The Fibre Channel processor is unable to log into the

Fibre Channel fabric name server.

The driver’s host (initiator) database is full.

The driver’s target database is full.

The driver’s target database is full.

The driver’s host (initiator) database is full. Maximum host database is 64.

Fibre Channel processor "Get VP Database entry command" failed.

The drivers host (initiator) database is full.

No slots available in host database.

FCIP system error event.

ISR651103-00 C B-21

B–Log Messages

Error Log Messages

User Modules

Table B-11 lists the error log messages generated by the user modules.

Table B-11. User Modules—Error Log Messages

ID Log Message

139265 QBRPC_Initialize: Entered

139266 QBRPC_Initialize:GetBridge Mem Allocation error

139267 QBRPC_Initialize:GetBridgeAdv Mem Allocation error

139268 QBRPC_Initialize:GetMgmt Mem Allocation error

139269 QBRPC_Initialize:GetIscsi Mem Allocation error

139270 QBRPC_Initialize:GetIscsiAdv Mem Allocation error

139271 QBRPC_Initialize:GetIsns Mem Allocation error

139272 QBRPC_Initialize:GetFcIntfc Mem Allocation error

No.

1

4

5

6

7

8

2

3

Description

RPC (remote procedure call) server initialization entry point.

Get System API memory allocation failed.

Get System Advanced API memory allocation failed.

Get Management API memory allocation failed.

Get iSCSI API memory allocation failed.

Get iSCSI advanced API memory allocation failed.

139273 QBRPC_Initialize:GetFcAdv Mem Allocation error

139280 QBRPC_Initialize:GetFcSfp Mem Allocation error

139281 QBRPC_Initialize:GetLog Mem Allocation error

139282 QBRPC_Initialize:GetStats Mem Allocation error

139283 QBRPC_Initialize:InitListMem Allocation error

9

16

17

18

19

Get iSNS API memory allocation failed.

Get Fibre Channel Interface API memory allocation failed.

Get Fibre Channel Advanced API memory allocation failed.

Failed memory allocation for Get Fibre Channel SFP API.

Failed memory allocation for Get Log API.

Failed memory allocation for Get Statistics API.

Failed memory allocation for Get Initiator List API.

B-22 ISR651103-00 C

B–Log Messages

Error Log Messages

Table B-11. User Modules—Error Log Messages (Continued)

ID Log Message

139284 QBRPC_Initialize:TargetList Mem Allocation error

139285 QBRPC_Initialize:LunList MemAllocation error

139286 QBRPC_Initialize:PresTarget Mem Allocation error

139287 QBRPC_Initialize:LunMask Mem Allocation error

139288 QBRPC_Initialize:Init Mem Allocation error

139289 QBRPC_Initialize:TgtDevice Mem Allocation error

139296 QBRPC_Initialize:FcTgt Mem Allocation error

139297 QBRPC_Initialize:BridgeStatus Mem Allocation error

139298 QBRPC_Initialize:Diag Mem Allocation error

139299 QBRPC_Initialize:DiagLog Mem Allocation error

139300 QBRPC_Initialize:FruImage Mem Allocation error

139301 QBRPC_Initialize:OemMfg Mem Allocation error

139302 QBRPC_Initialize:Status Mem Allocation error

139303 QBRPC_Initialize:TcpIpStats Mem Allocation error

139304 QBRPC_Initialize:NtpStats Mem Allocation error

139305 QBRPC_Initialize:LunList MemAlloc error

139315 QBRPC_FreeResources:Entered

No.

20

21

22

38

39

40

34

35

36

37

41

51

23

24

25

32

33

Description

Failed memory allocation for Get Target List API.

Failed memory allocation for Get LUN List API.

Failed memory allocation for Get Presented Targets List

API.

Failed memory allocation for Get LUN Mask API.

Failed memory allocation for Initiator API.

Failed memory allocation for Target Device API.

Failed memory allocation for Fibre Channel Target API.

Failed memory allocation for System Status API.

Failed memory allocation for Diagnostic API.

Failed memory allocation for Diagnostic Log API.

Failed memory allocation for FRU Image API.

Failed memory allocation for OEM Manufacturing API.

Failed memory allocation for Status API.

Failed memory allocation for TCP/IP Statistics API.

Failed memory allocation for NTP Status API.

Failed memory allocation for LUN List API.

RPC free resources entry point.

ISR651103-00 C B-23

B–Log Messages

Fatal Log Messages

Table B-11. User Modules—Error Log Messages (Continued)

ID Log Message

139553 checkDuplicateIp: Detected Error %08x %08x%04x

No.

289

Description

Detected duplicate IP address for management port.

System Modules

Table B-12 lists the error log messages generated by the system modules.

Table B-12. System Modules—Error Log Messages

ID Log Message

237572 "Failed to kill sys killer %d\n"

237573 "Temperature over high threshold %d\n"

No

4

5

Description

Failed to kill system task.

Reporting router exceeds maximum operating temperature.

Fatal Log Messages

The following sections list and describe the fatal log messages by reporting module:

“iSCSI Driver” on page B-24

“Fibre Channel Driver” on page B-27

“TOE Driver” on page B-29

“System Modules” on page B-30

iSCSI Driver

Table B-13 lists the fatal log messages common to all iSCSI ports: 1 (GE1), 2 (GE2), 3 (GE3), and 4 (GE4). Log

messages beginning with #0 denote iSCSI port 1 (GE1), #1 denotes iSCSI port 2 (GE2), #2 denotes iSCSI port 3

(GE3), and #3 denotes iSCSI 4 (GE4).

B-24 ISR651103-00 C

B–Log Messages

Fatal Log Messages

ID

69652

69653

69654

69655

69656

69941

69951

69964

69966

70224

70400

70417

70432

Table B-13. iSCSI Driver—Fatal Log Messages

Log Message

#%d: qlutm_init: Diagnostic failed, invalid SRAM

#%d: qlutm_init: Diagnostic failed, fail reboot

#%d: qlutm_init: Diagnostic failed, invalid NVRAM

#%d: qlutm_init: Diagnostic failed, invalid DRAM

#%d: qlutm_init: Failed to return diagnostic result to Bridge

#%d: QLUtmProcessResponseQueue: Invalid handle %x EntryType %x

#%d: QLSetNvram: QLRebootTimer failed AF %x RS %x

Time %d

#%d: QLDisable: QLRebootTimer failed AF %x RS %x

Time %d

#%d: QLEnable: QLRebootTimer failed AF %x RS %x

Time %d

#%d: QLProcSrblessiSNSResponse: Invalid handle %x

#%d: QLInitializeDevice: QLStartAdapter failed

#%d: QLInitializeAdapter: QLInitializeFW failed

#%d: QLDoInterruptServiceRoutine: PortFatal interrupt. PortFatalErrorStatus %08x CSR %08x

AS %x AF %x

No.

309

319

332

334

592

768

785

800

20

21

22

23

24

Description

iSCSI processor SRAM test failed.

iSCSI processor failed diagnostic reboot.

iSCSI processor failed NVRAM diagnostic.

iSCSI processor failed DRAM diagnostic.

iSCSI processor failed to return diagnostic results.

Response queue entry contains an invalid handle.

Set NVRAM reboot timer failed.

Port disable reboot timer failed.

Port enable reboot timer failed.

iSNS response contains an invalid handle.

Start iSCSI processor failed.

iSCSI processor firmware initialization failed.

iSCSI processor port fatal error.

ISR651103-00 C B-25

B–Log Messages

Fatal Log Messages

ID

70448

70489

70499

70501

70502

70524

70544

70563

70564

70609

70610

70784

70835

Table B-13. iSCSI Driver—Fatal Log Messages (Continued)

Log Message

#%d: QLStartAdapter: QLRebootTimer failed AF %x

RS %x Time %d

#%d: QLIsrDecodeMailbox: System Error 8002

MB[1-7] %04x

%04x %04x %04x %04x %04x %04x

#%d: QLProcessResponseQueue: Invalid handle for

ET_PASSTHROUGH_STATUS

#%d: QLProcessResponseQueue: Invalid entry type in response queue %x

#%d: QLProcessResponseQueue: Invalid handle %x

EntryType %x

#%d: QLProcessAen: Invalid event %x

#%d: QLRebootTimer: Reboot failed!

#%d: QLReadyTimer: Adapter missed heartbeat for

0x%x seconds. Rebooting

#%d: QLReadyTimer: Abort pTpb=%p failed, DrvCount

0x%x

#%d: QLProcessSystemError: Restart RISC

#%d: QLProcessSystemError: RebootHba failed

#%d: QLConfigChip: invalid NVRAM

#%d: QLStartFw: MBOX_CMD_SET_FLASH failed %x

No.

816

857

867

869

870

Description

Start iSCSI processor reboot timer failed.

iSCSI processor fatal system error.

Response queue invalid handle for ET pass-through.

Response queue invalid entry type.

Response queue invalid handle for specified entry type.

892

912

931

Asynchronous event for unknown event type.

Reboot timer failed.

iSCSI driver missed iSCSI processor heartbeat. iSCSI processor rebooted.

932 iSCSI processor failed to complete operation before timeout.

977 iSCSI processor system error restart.

978 iSCSI processor reboot failed.

1152 iSCSI processor NVRAM invalid (checksum error).

1203 iSCSI Flash (NVRAM) command failed.

B-26 ISR651103-00 C

B–Log Messages

Fatal Log Messages

ID

70836

70837

Table B-13. iSCSI Driver—Fatal Log Messages (Continued)

Log Message

#%d: QLStartFw: Invalid Fw loader state 0x%x

#%d: QLStartFw: Load Fw loader timeout

No.

Description

1204 iSCSI firmware loader invalid state.

1205 iSCSI failed to load firmware in time allotted.

Fibre Channel Driver

Table B-14 lists the fatal log messages common to both Fibre Channel ports, 1 (FC1) and 2 (FC2). Log messages

beginning with #0 denote Fibre Channel port 1 (FC1); log messages beginning with #1 denote Fibre Channel port 2

(FC2).

ID

Table B-14. Fibre Channel Driver—Fatal Log Messages

Log Message

102419 #%d: qlutm_init: Diagnostic failed, port 1 invalid SRAM

102420 #%d: qlutm_init: Diagnostic failed, port 1 POST failed

102421 #%d: qlutm_init: Diagnostic failed, port 2 invalid SRAM

102422 #%d: qlutm_init: Diagnostic failed, port 2 POST failed

102423 #%d: qlutm_init: Failed to return diagnostic result to Bridge

102656 #%d: QLInitializeAdapter: Reset ISP failed

No.

19

20

21

22

23

256

Description

FC1 processor SRAM test failed.

FC1 processor power-on self-test (POST) failed.

FC2 processor SRAM test failed.

FC2 processor POST failed.

Fibre Channel processor failed to return diagnostic results.

Fibre Channel processor failed reset.

ISR651103-00 C B-27

B–Log Messages

Fatal Log Messages

Table B-14. Fibre Channel Driver—Fatal Log Messages (Continued)

ID Log Message

102657 #%d: QLInitializeAdapter: Load RISC code failed

102658 #%d: QLInitializeAdapter: Load ISP2322 receive sequencer code failed

102659 #%d: QLInitializeAdapter: Load ISP2322 transmit sequencer code failed

102662 #%d: QLInitializeAdapter: Verify Checksum command failed (%x)

102680 #%d: QLInitializeFW: FAILED

102688 #%d: QLInterruptServiceRoutine: Risc pause %x with parity error hccr %x, Disable adapter

102689 #%d: QLInterruptServiceRoutine: Invalid interrupt status: %x

10691 #%d: QLFcipInterruptServiceRoutine: Risc pause

%x with parity error hccr %x, Disable adapter

10692 #%d: QLFcipInterruptServiceRoutine: Invalid interrupt status: %x

102716 #%d: QLIsrEventHandler: System error event (%x),

MB1=%x, MB2=%x, MB3=%x, MB4=%x, MB5=%x, MB6=%x,

MB7=%x

102746 #%d: QLProcessResponseQueue: Invalid handle %x, type %x

No.

257

258

259

262

280

288

289

291

292

316

346

Description

Fibre Channel processor firmware load failed.

Fibre Channel processor receive sequencer code load failed.

Fibre Channel processor transmit sequencer code load failed.

Fibre Channel processor firmware checksum failed.

Fibre Channel processor firmware initialization failed.

Fibre Channel processor paused due to internal parity error.

Fibre Channel processor returned an invalid interrupt status.

Fibre Channel processor invalid interrupt status.

Fibre Channel processor paused due to RAM parity error.

Fibre Channel processor system error.

Response queue entry contains an invalid handle.

B-28 ISR651103-00 C

B–Log Messages

Fatal Log Messages

Table B-14. Fibre Channel Driver—Fatal Log Messages (Continued)

ID Log Message

102747 #%d: QLProcessResponseQueueFS: Invalid buffer type: %x

102748 #%d: QLProcessResponseQueueFS: Invalid EntryType

(0x%x)

102749 #%d: QLProcessResponseQueueFS: Invalid handle

0x%x, type 0x%x

102752 #%d: QLTimer: Ext Ram parity error exceed limit cnt 0x%x, limit 0x%x, Disabled adapter

102755 #%d: QLTimer: Heartbeat failed

102800 #%d: QLRestartRisc: restart RISC

No.

347

348

349

352

355

400

Description

FCIP: Response queue entry contains an invalid buffer type.

FCIP: Response queue entry contains an invalid entry type.

FCIP: Response queue entry contains an invalid handle.

Fibre Channel processor external SRAM parity error count exceeded limit: Fibre Channel port disabled.

Fibre Channel processor heartbeat failed.

Fibre Channel processor being restarted.

TOE Driver

Table B-15 lists the fatal log messages generated by the TOE driver.

ID

Table B-15. TOE—Fatal Log Messages

Log Message

200721 QL3022:ql3xxx_probe: Adapter eth#%d, Invalid

NVRAM parameters

200725 QL3022:eth%x: Resetting chip. PortFatalErrStatus register = 0x%x

No.

17

21

Description

Encountered invalid parameters in TOE NVRAM.

TOE chip reset due to detection of fatal error.

ISR651103-00 C B-29

B–Log Messages

Fatal Log Messages

System Modules

Table B-16 lists the fatal log messages generated by the system modules.

Table B-16. System—Fatal Log Messages

ID Log Message

233473 "memory monitor: Detected Uncorrectable

Ecc %08lx system is rebooting in 5 secs\n"

233474 "Failed to register interrupt handler!\n"

233475 "%s class_simple_create failed\n"

No.

1

2

3

Description

Uncorrectable memory error detected at address provided in log message.

Attempt to register the interrupt handler failed.

Failed class_simple_create system call from memory monitor initialization routine.

B-30 ISR651103-00 C

Glossary

activity LED

A port

LED that indicates when frames are entering or leaving the port.

adapter

The board that interfaces between the host system and the

target devices.

Adapter is synonymous with host bus

adapter (HBA), host adapter, and adapter

board.

adapter port

A port on the adapter board.

adapter port beacon

An LED on the adapter. Flashing it enables you to locate the adapter.

arbitrated loop

A circular (ring) topology (versus

point-to-point) where two or more port s

can be interconnected, but only two ports can communicate at a time. All communication passes through all ports connected to the loop. bandwidth

A measure of the volume of data that can be transmitted at a specific transmission rate. A 1Gbps or 2Gbps Fibre Channel

port

can transmit or receive at nominal rates of 1 or 2Gbps, depending on the device to which it is connected. This corresponds to actual bandwidth values of

106MB and 212MB, respectively.

challenge-handshake authentication protocol

See CHAP

.

CHAP

Challenge-handshake authentication protocol. CHAP is used for remote logon, usually between a client and server or a

Web browser and Web server. A challenge/response is a security mechanism for verifying the identity of a person or process without revealing a secret password that is shared by the two entities. CHAP is also referred to as a

three-way handshake.

CLI

Command line interface. A program interface driven by entering commands and parameters.

command line interface

See CLI

.

device

A target

, typically a disk drive. Hardware such as a disk drive, tape drive, printer, or keyboard that is installed in or connected to a system. In Fibre Channel, a target device.

ISR651103-00 C Glossary-1

iSR6152 Intelligent Storage Router

Installation Guide

DHCP

Dynamic host configuration protocol.

Enables computers on an IP network to extract their configuration from servers that have information about the computer only after it is requested.

driver

The software that interfaces between the file system and a physical data storage device or network media.

E_Port

Expansion port. A port in a Fibre Channel

switch that connects to another Fibre

Channel switch or bridge device by an inter-switch link. E_Ports are used to link

Fibre Channel switches to form a multi-switch

fabric .

EEPROM

Electrically erasable programmable read-only memory. Memory that can be erased (entirely, not selectively) using higher electrical voltages.

electrically erasable programmable read-only memory

See

EEPROM

.

Enhanced Ethernet

Also called data center Ethernet or

converged enhanced Ethernet. Refers to new enhancements to the existing

Ethernet standard that eliminate

Ethernet’s inherently lossy nature and make 10Gb Ethernet a viable storage networking transport.

Ethernet

The most widely used LAN technology that transmits information between computer, typically at speeds of 10 and 100 million bits per second (Mbps).

expansion port

See E_Port .

F_Port

The fabric port in a Fibre Channel fabric switch provides a point-to-point link attach-

ment to a single N_Port . F_Ports are inter-

mediate ports in virtual point-to-point links between end ports, for example N_Port to

F_Port to F_Port to N_Port using a single

Fibre Channel fabric switch.

fabric

A fabric consists of cross-connected Fibre

Channel devices and switches.

fabric loop port

See FL_Port

.

fabric port

A F_Port or

FL_Port

.

fabric switch

Also, switched fabric. A fabric switch connects multiple devices from independent Fibre Channel-arbitrated loops

(FC-ALs) and point-to-point topologies into a fabric using Fibre Channel switches. failover path

Software feature that ensures data availability and system reliability by assigning alternate path and automatic

adapter

failover for device resources. This feature is available only in Windows

2000/Windows Server 2003/Windows

Vista, Novell NetWare, and Red Hat/SUSE

Linux. (Windows XP and Windows Server

2008 do not support failover.)

FC

See Fibre Channel .

Glossary-2 ISR651103-00 C

iSR6152 Intelligent Storage Router

Installation Guide

FC-IP mode

Data transportation mode in which the iSR6152 transports Fibre Channel frames over a TCP/IP connection using the

FCIP

protocol to connect two iSR6152 routers.

In FC-IP mode, a port pair (one Fibre

Channel port and an IP port on the same router) on local iSR6152 and another port pair on a remote router form an FCIP route.

FCIP

Fibre Channel over IP. Protocol that enables transmission of Fibre Channel information by tunneling data on a

SAN

over IP networks.

FCP

Fibre Channel protocol. SCSI to Fibre

Channel mapping.

Fibre Channel

A high-speed serial interface technology that supports other higher layer protocols

such as SCSI

and IP

.

Fibre Channel over IP

See

FCIP

.

field replaceable unit

See

FRU .

FL_Port

Fabric loop port. In Fibre Channel, the

fabric switch

is capable of Fibre Channel arbitrated loop operations and is connected to one or more

NL_Port

s by a

Fibre Channel Arbitrated Loop. An

FL_Port becomes a shared entry point for public NL_Port devices to a Fibre Channel fabric. FL_Ports are intermediate ports in virtual point-to-point links between end ports that do not reside on the same loop, for example NL_Port to FL_Port to F_Port to N_Port through a single Fibre Channel fabric switch.

Flash

Non-volatile memory where the boot code is saved. At times, Flash and boot code are used interchangeably.

Flash BIOS

A QLA2xxx adapter 's Flash programmable

read-only memory (PROM) contains the code that allows booting from the adapter at startup. frame

Data unit consisting of a start-of-frame

(SOF) delimiter, header, data payload,

CRC, and an end-of-frame (EOF) delimiter.

FRU

Field replaceable unit. Component that can be replaced in the field upon failure.

G_Port

Generic port. A port that can operate as either an E_Port or an F_Port. A G_Port can determine operating mode at switch port initialization, F_Port when an N_Port attachment is determined, E_Port when an

E_Port attachment is determined. See

E_Port , F_Port

,

FL_Port

, L_Port

, N_Port

,

NL_Port .

ISR651103-00 C Glossary-3

iSR6152 Intelligent Storage Router

Installation Guide generic port

See

G_Port

.

heartbeat LED

A chassis LED that indicates the router status.

hot replaceable

Also known as hot swappable, this means you can add new devices or remove existing ones when the system is running.

IANA

Internet Assigned Numbers Authority

(IANA) is responsible for the global coordination of the DNS root, IP addressing, and other Internet protocol resources.

initiator

System component, such as a network interface card, that originates an I/O operation.

Internet Assigned Numbers Authority

See

IANA

.

Internet Protocol

See

IP .

Internet small computer system interface

See

iSCSI

.

IOCTL

Input/output control. A system call in

UNIX/Linux systems that allows an application to control or communicate with a device driver outside usual read/write operations.

IP

Internet Protocol. A method by which data is sent from one computer to another over the Internet. IP specifies the format of packets, also called datagrams, and the addressing scheme.

iSCSI

Internet small computer system interface.

Protocol that encapsulates data into IP packets to send over Ethernet connections.

iSNS

Internet simple name service is used for discovery and management of IP-based

SANs.

jumbo frames

Large IP

frames used in high-performance networks to increase performance over long distances. Jumbo frames generally means 9,000 bytes for Gigabit

Ethernet

,

but can refer to anything over the IP MTU ,

which is 1,500 bytes on an Ethernet.

L_Port

Loop port. Does arbitrated loop functions and protocols. NL_Ports and FL_Ports are examples of loop-capable ports. See

E_Port , F_Port

,

FL_Port , G_Port ,

N_Port

,

NL_Port .

loop port

See loop port .

latency

A measure of how fast a transaction travels through the router.

LIP

Loop initialization process. The initialization process in an arbitrated loop that occurs when the loop is powered up or a new device is added. One function of a LIP is to assign addresses. All data transmission on the loop is suspended during a LIP.

Glossary-4 ISR651103-00 C

iSR6152 Intelligent Storage Router

Installation Guide load balancing

A software feature that improves system performance by balancing device access between multiple ports for maximum resource efficiency. loop initialization process

See

LIP .

loopback

Diagnostic tool that routes transmit data through a loopback connector back to the same adapter.

LUN

Logical unit number, a subdivision of a

SCSI target. It is the small integer handle that differentiates an individual disk drive or partition (volume) within a common

SCSI target device such as a disk array.

A LUN can be a single physical disk drive, multiple physical disk drives, or a portion

(volume) of a single physical disk drive.

However, LUNs are typically not entire disk drives but rather virtual partitions

(volumes) of a RAID set.

Using LUNs, the Fibre Channel host can address multiple peripheral devices that may share a common controller.

maintenance button

Multifunction momentary switch on the front panel of the router.

management workstation

PC workstation used to manage routers remotely by connecting to the routers using SANsurfer Router Manager or CLI commands.

maximum transmission unit

See

MTU .

media

Physical-layer information carriers. Fibre

Channel supports several different physical media: copper, multimode optical, and single-mode optical. All Fibre Channel protocols are supported on all media.

MIB

Management information base. A set of guidelines and definitions for SNMP functions.

MTU

Maximum transmission unit. Refers to the size (in bytes) of the largest packet (IP datagram) that a specified layer of a communications protocol can transfer.

N_Port

Node port. Connects by a point-to-point link to either a single N_Port or a single

F_Port . N_Ports handle creation, detec-

tion, and flow of message units to and from the connected systems. N_Ports are end ports in virtual point-to-point links through a fabric, for example N_Port to F_Port to

F_Port to N_Port using a single Fibre

Channel fabric switch. See also

FL_Port

.

ISR651103-00 C Glossary-5

iSR6152 Intelligent Storage Router

Installation Guide

NL_Port

Node loop port. A port capable of arbitrated loop functions and protocols. An

NL_Port connects through an arbitrated loop to other NL_Port and at most a single

FL_Port. NL_Ports handle creation, detection, and flow of message units to and from the connected systems. NL_Ports are end ports in virtual point-to-point links through a fabric, for example NL_Port to

F_Port to F_Port to N_Port using a single

Fibre Channel fabric switch. In the absence of a fabric switch FL_Port,

NL_Ports can communicate with other

NL_Ports in virtual point-to-point links through an FC_AL open loop circuit often through FC_AL (Arbitrated Loop) hub or loop switch devices. See:

E_Port , F_Port ,

FL_Port , G_Port ,

N_Port

.

network time protocol

See

NTP .

non-volatile random access memory

See

NVRAM

.

NTP

Network time protocol. NTP is used for distributing the Coordinated Universal

Time (UTC) by means of synchronizing the clocks of computer systems over packet-switched, variable-latency data networks.

NVRAM

Non-volatile random access memory.

NVRAM is a type of memory that retains data (including configuration settings) even when power is removed. You can configure NVRAM settings manually or restore them from a file.

path

A path to a device is a combination of a adapter

port instance

and a target port as distinct from internal paths in the fabric network. A fabric network appears to the operating system as an opaque network between the adapter (initiator) and the target.

Because a path is a combination of an adapter and a target port, it is distinct from another path if it is accessed through a different adapter and/or it is accessing a different target port. Consequently, when switching from one path to another, the driver might be selecting a different adapter (initiator), a different target port, or both.

This is important to the driver when selecting the proper method of failover notification. It can make a difference to the target device, which might have to take different actions when receiving retries of the request from another initiator or on a different port.

point-to-point

Also FC-P2P. Two Fibre Channel nodes directly connected (not in a loop). port

Access points in a device where a link attaches. There are four types of ports, as follows:

N_Port —a Fibre Channel port that

supports point-to-point topology.

NL_Port —a Fibre Channel port that

supports loop topology.

FL_Port

—a port in a fabric where an

N_Port can attach.

FL_Port

—a port in a fabric where an

NL_Port can attach.

Glossary-6 ISR651103-00 C

iSR6152 Intelligent Storage Router

Installation Guide port instance

The number of the port in the system.

Each adapter may have one or multiple ports, identified with regard to the adapter as port 0, port 1 and so forth. To avoid confusion when dealing with a system containing numerous ports, each port is assigned a port instance number when the system boots up. So Port 0 on an adapter might have a port instance number of 8, for example, if it is the eighth port discovered by the system.

POST

Power-on self test. Diagnostics that the router performs at start-up.

power-on self test

See

POST .

reduced instruction set computer

See

RISC

.

registered state change notification

See

RSCN .

RISC

Reduced instruction set computer. A computer microprocessor that performs fewer types of computer instructions, thereby operating at higher speeds.

RSCN

Registered state change notification.

RSCN is a Fibre Channel fabric notification sent to all specified nodes when any major fabric changes occur. This notification allows nodes to immediately gain knowledge about the fabric and react accordingly.

router log

Log of messages describing events that occur on the intelligent storage router.

SAN

Storage area network. Multiple storage units (disk drives) and servers connected by networking topology.

SANsurfer Router Manager

Workstation-based router management utility that provides a graphical user interface (GUI) used to configure and monitor intelligent storage routers.

SCSI

Small computer system interface. A high-speed interface used to connect devices, such as hard drives, CD drives, printers, and scanners, to a computer. The

SCSI can connect many devices using a single controller. Each device is accessed by an individual identification number on the SCSI controller bus.

SFP

Small form-factor pluggable. A transceiver device, smaller than a GigaBit Interface

Converter, that plugs into the Fibre

Channel port.

simple network management protocol

See SNMP

.

small computer system interface

See SCSI .

small form-factor pluggable

See SFP

.

SNMP

Simple network management protocol.

SNMP is a networking protocol that enables you to monitor the router using third-party applications that use SNMP. storage area network

See SAN

.

ISR651103-00 C Glossary-7

iSR6152 Intelligent Storage Router

Installation Guide target

The storage-device endpoint of a SCSI session. Initiators request data from targets. Targets are typically disk-drives, tape-drives, or other media devices.

Typically a SCSI peripheral device is the target but an adapter may, in some cases, be a target. A target can contain many

LUNs.

A target is a device that responds to a requested by an initiator (the host system).

Peripherals are targets, but for some commands (for example, a SCSI COPY command), the peripheral may act as an initiator.

TCP

Transmission control protocol. A set of rules to send data in packets over the

Internet protocol.

TOE

TCP/IP offload engine. Technology for improving TCP/IP performance by offloading processing onto a state-based offload engine directly on the adapter.

virtual logical area network

See

VLAN .

VLAN

Virtual logical area network (LAN). A group of hosts with a common set of requirements that communicate as if they were attached to the same wire, regardless of their physical location. Although a VLAN has the same attributes as a physical LAN, it allows for end stations to be grouped together even if they are not located on the same LAN segment. VLANs enable network reconfiguration through software, instead of physically relocating devices.

world wide name

See

WWN .

world wide node name

See WWNN

.

world wide port name

See WWPN

.

WWN

World wide name. A unique 64-bit address assigned to a device by the device manufacturer.

WWNN

World wide node name. A unique 64-bit address assigned to a device.

WWPN

World wide port name. A unique 64-bit address assigned to each port on a device. One WWNN may contain multiple

WWPN addresses.

Glossary-8 ISR651103-00 C

Index

A

AC power, connecting router 3-10

accessible parts support

xv

accessories included with router

3-3

activity LED

definition of Glossary-1

Ethernet management port 1-9

GbE ports 1-8

adapter

definition of Glossary-1

port beacon, definition of

Glossary-1

port, definition of

Glossary-1

application modules

error log messages B-10

informational log messages

B-2

arbitrated loop, definition of Glossary-1

audience ix

authentication trap, enabling/disabling A-2

B

bandwidth

definition of Glossary-1

fiber optic cables

2-2

Fibre Channel devices

2-2

blink pattern

heartbeat LED 4-3

management port IP address conflict LED

4-3

system fault LED

1-3 ,

4-3

boot image, selecting 1-5

C

cabling devices to router

3-11

capabilities 1-1

CHAP definition of

Glossary-1

key error

B-12

validation error

B-12

chassis

controls 1-4

diagnostics

4-1

LEDs

1-3

check list, pre-installation

3-4

CLI definition of

Glossary-1

firmware, installing

3-12

command line interface, See CLI

communications statements

xii

community read

A-1 trap A-1

configuring the router

3-10

controls, chassis

1-4

conventions, documentation

xi

D

data migration, licensed feature

1-2

database, knowledge

xxiv

definitions of terms Glossary-1

device definition of

Glossary-1

planning for router 2-1

ISR651103-00 C Index-1

iSR6152 Intelligent Storage Router

Installation Guide

DHCP

definition of Glossary-2

enabling 1-5

diagnostics chassis

4-1

POST

4-2

discovered initiators, erasing 1-6

discovered targets, erasing

1-6

disk space

requirements 3-1

workstation requirements

3-1

documentation conventions

xi

driver, definition of Glossary-2 dynamic host configuration protocol, See

DHCP

E

E_Port

definition of Glossary-2

on Fibre Channel switches 1-2

EEPROM

definition of Glossary-2

updated message

B-4

electrically erasable programmable read-only memory, See EEPROM

electrostatic discharge sensitivity precautions

xv

environmental conditions

3-2

error log messages

B-9

application modules

B-10

Fibre Channel driver B-19

iSCSI driver

B-18

system modules B-24

user modules

B-22

ESDS precautions xv

Ethernet

definition of Glossary-2

port management 1-9

expansion port, See E_Port

F

F_Port, definition of Glossary-2

fabric definition of

Glossary-2

Fibre Channel, merging

1-2

name server log error B-21

fabric loop port, definition of

Glossary-3

fabric port, definition of

Glossary-2 fabric switch, definition of Glossary-2

factory defaults, restoring

1-5

failover path, definition of Glossary-2

fatal log messages B-24

Fibre Channel driver

B-27

iSCSI driver

B-24

system modules

B-30

TOE driver

B-29

FCIP data buffer pool error

B-17

definition of

Glossary-3

error message

B-16

, B-17

fatal errors B-29

GigE interface down message B-9

incoming frame error

B-16

link down message

B-8

link up message

B-8

protocol, supported

1-2

response queue error B-20

route added message

B-8 route modified message B-8 route removed message B-8

routes, supported

1-2 support for 1-2

system error B-16

system error event B-21

FC-IP mode, definition of Glossary-3

FCIP module, informational log messages

B-8

FCP definition of

Glossary-3

mode, port A-6

features, licensed 1-2

Index-2 ISR651103-00 C

Fibre Channel

error log messages B-19

over IP 1-2

performance

2-2

port, MIB

A-6

ports 1-6

SFP transceivers

1-7

Fibre Channel driver

error log messages B-19

fatal log messages B-27

informational log messages

B-4

Fibre Channel over IP, See FCIP

Fibre Channel protocol, See FCP field replaceable unit, See FRU

firmware installing

3-11

installing using CLI 3-12

FL_Port

definition of Glossary-3

loop topology support

2-7

Flash iSCSI failure

B-26

validation with POST 4-2

Flash BIOS, definition of Glossary-3

Flash, definition of Glossary-3

frame

definition of Glossary-3

incoming FCIP B-16

jumbo

2-2

,

2-3

shuttle mode A-6

size, maximum 2-2

FRU

accessible parts support xv

CLI command, removing router 5-2

definition of Glossary-3

image API failure error

B-23

removing and replacing 5-1

FTP services

2-8

ISR651103-00 C iSR6152 Intelligent Storage Router

Installation Guide

G

G_Port definition of

Glossary-3

loop topology support 2-7

GbE

performance 2-3

port LEDs

1-8

general public license

xvi

gigabit Ethernet, See GbE

glossary of terms

Glossary-1

H

hardware, workstation requirements

3-1

heartbeat LED

blink pattern 1-3

,

4-2

, 4-3

boot image, selecting 1-5

definition of

Glossary-4

DHCP, enabling

1-5 factory defaults, restoring 1-5

IP address, resetting

1-5

location of

1-3

router, powering up

3-10

router, resetting 1-4 system fault synchronized with 1-4

hot replaceable/hot swappable, definition of

Glossary-4

I

IANA definition of

Glossary-4

Fibre Channel port type

A-7

image unpack command 3-12

image, boot, selecting 1-5

informational log messages

B-1

application modules B-2

FCIP module

B-8

Fibre Channel driver

B-4

iSCSI driver

B-4

system modules

B-9

Index-3

iSR6152 Intelligent Storage Router

Installation Guide

informational log messages (continued)

TOE driver B-9

user modules

B-6

initiator

definition of Glossary-4

erasing discovered 1-6

input power LED 1-3

input/output control, See IOCTL

installing

firmware, router 3-11

pre-installation check list 3-4

SANsurfer Router Manager on Windows

3-8

transceivers

3-6

installing, router

3-2

instance (port), definition of Glossary-7

Internet Assigned Numbers Authority, See

IANA

Internet browser, workstation requirements

3-2

Internet Protocol, See IP

Internet simple name service, See iSNS

Internet small computer system interface, See

iSCSI

IOCTL

definition of Glossary-4

disable request error B-20

interface, resetting adapter B-4

,

B-5

iSCSI driver unload request

B-15

object allocation failure

B-12

operation unsupported

B-13

request by driver failed

B-20 request to driver error B-20

IP address

resetting 1-5

workstation 3-7

IP, definition of Glossary-4

iSCSI

definition of Glossary-4

error log messages B-18

fatal log messages B-24

login PDF error

B-12

name server connection failure B-18

performance

2-3

iSCSI driver error log messages

B-18

fatal log messages

B-24

informational log messages B-4

iSNS connection failure

B-18

definition of

Glossary-4

J

jumbo frames definition of

Glossary-4

MTU size 2-2 ,

2-3

K

key, license

1-2

knowledge database xxiv

L

L_Port, definition of Glossary-4

laser safety information xv

latency definition of

Glossary-4

Fibre Channel devices

2-3

LED blink patterns

heartbeat 4-3

management port IP address conflict

4-3

system fault

4-3

LEDs

activity, definition of Glossary-1

adapter port beacon, definition of

Glossary-1

chassis 1-3

chassis diagnostics

4-1

Fibre Channel ports

1-6

GbE ports

1-8

heartbeat 1-3

heartbeat, definition of

Glossary-4

input power

1-3

, 4-2

Index-4 ISR651103-00 C

iSR6152 Intelligent Storage Router

Installation Guide

LEDs (continued)

power

1-3 system fault 1-3

,

4-2

license

agreements (EULA) xvi

general public

xvi

licensed features, key 1-2

link status LED

Ethernet management port 1-9

GbE ports 1-8

Linux, installing SANsurfer Router Manager

3-9

LIP

definition of Glossary-4

log message

B-5

load balancing

definition of Glossary-5 load balancing, definition of Glossary-5

localmap messages B-7

location name, router A-1

log messages B-1

error

B-9

fatal

B-24

informational B-1

logical unit number (LUN), definition of

Glossary-5

loop (arbitrated), definition of Glossary-1

loop initialization process, See LIP loop port (L_Port), definition of Glossary-4

loopback, definition of

Glossary-5

LUN

allocation failure B-14

definition of Glossary-5

memory allocation failure B-23

object memory error

B-10

report command failure B-13 ,

B-14

M

maintenance button 1-4

definition of Glossary-5

router, resetting

1-4

management router utilities

2-7

workstation requirements 3-1

workstation, configuring 3-6

workstation, connecting to router

3-6

workstation, definition of Glossary-5

management port IP address conflict LED

blink pattern 4-3

maximum transmission unit, See MTU media, definition of Glossary-5

memory, workstation requirements 3-1

messages

error B-9

fatal B-24

informational

B-1 logged to file B-1

MIB definition of

Glossary-5

Fibre Channel ports

A-6

network ports A-3

notifications

A-10

objects

A-2

sensors A-8

system information objects A-3

Microsoft Internet Explorer, browser 3-2

migration, data

1-2

mounting the router 3-4

MTU definition of

Glossary-5

size, jumbo frames

2-2

, 2-3

N

N_Port compatibility between switches

1-2

definition of

Glossary-5

FCIP support for 1-2

network ports, MIB A-3

network time protocol, See NTP

NL_Port, definition of

Glossary-6

node

loop port, definition of Glossary-6

port (N_Port), definition of Glossary-5

ISR651103-00 C Index-5

iSR6152 Intelligent Storage Router

Installation Guide

non-volatile random access memory, See

NVRAM notification

agent shut down A-11

agent start up

A-11

Fibre Channel port down

A-11

generic A-12

MIB A-10

network port down

A-11

objects

A-10

sensor

A-12

NTP

definition of Glossary-6

services 2-8

NVRAM

definition of Glossary-6

invalid data in

B-18

O

objects, notification A-10

operating system requirements, workstation

3-1

P

path, definition of

Glossary-6

performance

Fibre Channel

2-2

GbE 2-3

tuning

2-3

planning

for the router 2-1 router device considerations 2-1

point-to-point

definition of Glossary-6

Fibre Channel link

B-5

port

definition of Glossary-6

Fibre Channel

1-6

instance, definition of

Glossary-7

management, Ethernet

1-9 serial 1-9

POST after power up

3-10

completion with no errors

4-2

definition of

Glossary-7

diagnostic testing

4-2

errors indicated by system fault LED 1-3

failure log message

B-27

resetting router 1-4

power LED

1-3

power requirements 3-2

power-on self test, See POST

precautions, ESDS xv

pre-installation check list 3-4

primary boot image 1-5

processor, workstation requirements 3-1

properties, SNMP A-1

public license, general xvi

R

rack mounting router 3-4

read community A-1

recovering a router 4-4

recovery process, router failure 2-7

reduced instruction set computer, See RISC registered state change notification, See

RSCN related materials

x

remotemap messages B-6

,

B-7

removing router

5-1

SFP transceivers 5-1

replacing router

5-2

SFP transceivers 5-1

requirements power

3-2

site 3-1

restoring factory defaults 1-5

RISC definition of

Glossary-7

iSCSI processor, restarting B-4

Index-6 ISR651103-00 C

router

AC power, connecting to

3-10

capabilities of

1-1

configuring

3-10

description, features, capabilities

1-1

devices, cabling to

3-11

location

A-1

mounting

3-4

multiple, connecting

2-7

recovering 4-4

removing

5-1

replacing

5-2

resetting 1-4

security with passwords

2-8 services 2-8

workstation, connecting to 3-6

router log B-1

definition of Glossary-7

RSCN

definition of Glossary-7

receive message

B-5

S

Safari browser

3-2

safety, laser xv

SAN

definition of Glossary-7

SANsurfer Router Manager 3-9

definition of Glossary-7

firmware, installing 3-12

installing

3-8

installing on Linux

3-9

starting

3-9

saving router files for system recovery 2-7

SCSI, definition of Glossary-7

secondary boot image

1-5

security, router 2-8

sensors, MIB

A-8

serial port

RS232 on router

1-9

workstation 3-7

iSR6152 Intelligent Storage Router

Installation Guide services

FTP

2-8

NTP

2-8

router

2-8

SNMP 2-8

Telnet

2-8

SFP definition of

Glossary-7

transceivers, removing and replacing

5-1

SFP transceivers, Fibre Channel 1-7

site requirements for router installation

3-1

small computer system interface (SCSI),

definition of Glossary-7 small computer system interface, See SCSI small form-factor pluggable, See SFP

SNMP definition of

Glossary-7

introduction

A-1

properties, setting

A-1

services

2-8

trap configuration

A-2

statements, communications xii

status LED

Ethernet management port

1-9

GbE ports

1-8

storage area network, See SAN

switch ports

2-7

switched fabric, definition of

Glossary-2

system

contact for trap events A-2

location A-1

MIB objects A-3

system error, FCIP B-16

system fault LED

1-3

system fault LEDs

1-3

blink pattern 4-3

system modules error log messages

B-24

fatal log messages

B-30

informational log messages B-9

ISR651103-00 C Index-7

iSR6152 Intelligent Storage Router

Installation Guide

T

target

definition of Glossary-8

database full error

B-21

devices exceeded

B-10

driver connection error

B-21

driver database full error B-19

erasing discovered 1-6

failed memory allocation error B-23

iSCSI login error

B-11 iSCSI login PDU error B-11

,

B-12

localmap for

B-7

operation, PCI error during B-10

unknown path error

B-19

TCP

connection failure B-18

definition of Glossary-8

window scaling factor

2-3

window size

2-3

TCP/IP offload engine, See TOE

technical support xxiii

Telnet service 2-8

terms and definitions

Glossary-1

TOE driver

fatal log messages B-29

informational log messages

B-9

TOE, definition of

Glossary-8

topologies, supported 1-1

training offered by QLogic

xxiii

transceivers

Fibre Channel SFP, description

1-7

SFP, installing 3-6

transmission control protocol, See TCP

trap authentication, enabling/disabling

A-2

community

A-1

tuning, router configuration, maximizing 2-3

U

user modules error log messages

B-22

informational log messages B-6

V

virtual LAN, See VLAN virtual logical area network, See VLAN

VLAN

configuration modified message B-6

definition of

Glossary-8

W

window scaling factor, TCP

2-3 window size, TCP 2-3

Windows installing router manager

3-8

SANsurfer Router Manager, installing 3-8

workstation disk space requirements

3-1

hardware requirements

3-1

Internet browser requirements 3-2

IP address 3-7

management, definition of Glossary-5

memory requirements

3-1 processor requirements 3-1

serial port

3-7

world wide name, See WWN world wide node name, See WWNN world wide port name, See WWPN

WWN definition of

Glossary-8

port name

A-7 port node A-7

WWNN definition of

Glossary-8

Fibre Channel login error

B-2

Fibre Channel logout error

B-2

Index-8 ISR651103-00 C

WWPN

definition of Glossary-8

Fibre Channel login error B-2

localmap for initiator

B-7 localmap for target B-7

not found during logout

B-14

remotemap for local

B-6 ,

B-7 remotemap for remote B-7

zoning based on 2-7

Z

zoning, switch ports

2-7

iSR6152 Intelligent Storage Router

Installation Guide

ISR651103-00 C Index-9

Corporate Headquarters QLogic Corporation 26650 Aliso Viejo Parkway Aliso Viejo, CA 92656 949.389.6000 www.qlogic.com

International Offices UK | Ireland | Germany | France | India | Japan | China | Hong Kong | Singapore | Taiwan

© 2011 QLogic Corporation. Specifications are subject to change without notice. All rights reserved worldwide. QLogic and the QLogic logo are trademarks or registered trademarks of QLogic Corporation. AMCC is a registered trademark of Applied Micro Circuits Corporation. Brocade is a registered trademark of Brocade Communications Systems, Inc. Cisco is a registered trademark of Cisco Systems, Inc. EMC, SAN Copy, MirrorView, and SRDF are trademarks or registered trademarks of EMC Corporation. Gnome is a trademark of the GNOME Foundation Corporation. Hitachi and TrueCopy are registered trademarks of Hitachi,

Ltd., and/or its affiliates. IBM and PowerPC are registered trademarks of International Business Machines Corporation. Java and Solaris are trademarks or registered trademarks of Sun Microsystems, Inc. Pentium is a registered trademark of Intel Corporation. Linux is a registered trademark of Linus Torvalds. MacOS and Safari are registered trademarks of Apple, Inc. McDATA is a registered trademark of McDATA Corporation. Microsoft, Windows, and Internet Explorer are registered trademarks of

Microsoft Corporation. Red Hat is a registered trademark of Red Hat, Inc. SANmark is a trademark of the Fibre Channel Industry Association. SUSE is a trademark of

Novell, Inc. All other brand and product names are trademarks or registered trademarks of their respective owners. Information supplied by QLogic Corporation is believed to be accurate and reliable. QLogic Corporation assumes no responsibility for any errors in this brochure. QLogic Corporation reserves the right, without notice, to make changes in product design or specifications.

advertisement

Was this manual useful for you? Yes No
Thank you for your participation!

* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project

Related manuals

Download PDF

advertisement

Table of contents