Q-Logic 2-8C User Manual

Download

Simplify

SANbox2-8c Fibre Channel Switch

Installation Guide

Firmware Version 4.1

59042-06 A Page i

SANbox2-8c Fibre Channel Switch 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.

QLogic, SANbox, SANbox2, SANsurfer Switch Manager, SANblade, SANsurfer, SANsurfer Management Suite, and Multistage are trademarks or registered trademarks of QLogic Corporation.

Gnome is a trademark of the GNOME Foundation Corporation. Java and Solaris are registered trademarks of Sun Microsystems, Inc. Geode is a registered trademark of National Semiconductor Corporation. Linux is a registered trademark of Linus Torvalds. Microsoft, Windows NT, and Windows 2000/2003, and Internet Explorer are registered trademarks of Microsoft

Corporation. Netscape Navigator and Mozilla are trademarks or registered trademarks of Netscape Communications

Corporation. Red Hat is a registered trademark of Red Hat Software Inc. SANmark is a registered trademark of the Fibre Channel Industry Association. All other brand and product names are trademarks or registered trademarks of their respective owners.

Document Revision History

Release, Revision A, May 2004 Firmware Version 4.1

SANsurfer Switch Manager Version 4.01

First Printed: May 2001

Page ii 59042-06 A

Section 1 Introduction

1.1 Intended Audience ............................................................................................. 1-1

1.2 Related Materials ............................................................................................... 1-1

1.3 New in this Release............................................................................................ 1-2

1.4 Safety Notices .................................................................................................... 1-3

1.5 Sicherheitshinweise............................................................................................ 1-3

1.6 Notes informatives relatives à la sécurité........................................................... 1-3

1.7 Communications Statements.............................................................................. 1-4

1.7.1 Federal Communications Commission (FCC) Class A Statement ............1-4

1.7.2 Canadian Department of Communications Class A

Compliance Statement .............................................................................. 1-4

1.7.3 Avis de conformité aux normes du ministère des

Communications du Canada ..................................................................... 1-5

1.7.4 CE Statement ............................................................................................ 1-5

1.7.5 VCCI Class A Statement ........................................................................... 1-6

1.7.6 BSMI Class A Statement ........................................................................... 1-6

1.8 Laser Safety Information .................................................................................... 1-7

1.9 Electrostatic Discharge Sensitivity (ESDS) Precautions .................................... 1-7

1.10 Accessible Parts................................................................................................. 1-8

1.11 Pièces Accessibles............................................................................................. 1-8

1.12 Zugängliche Teile ............................................................................................... 1-8

1.13 General Public License ...................................................................................... 1-9

1.13.1 Preamble ................................................................................................... 1-9

1.13.2 Terms And Conditions For Copying, Distribution And Modification ......... 1-10

1.13.3 How to Apply These Terms to Your New Programs ................................ 1-14

1.14 Technical Support............................................................................................. 1-16

1.14.1 Availability................................................................................................1-16

1.14.2 Training....................................................................................................1-16

1.14.3 Contact Information ................................................................................. 1-16

Section 2 General Description

2.1 Chassis Controls and LEDs ............................................................................... 2-2

2.1.1 Maintenance Button...................................................................................2-2

2.1.1.1 Resetting a Switch............................................................................ 2-2

2.1.1.2 Placing the Switch in Maintenance Mode......................................... 2-3

2.1.2 Chassis LEDs............................................................................................ 2-3

59042-06 A Page iii

SANbox2-8c Fibre Channel Switch Installation Guide

2.1.2.1 Over Temperature LED (Amber)....................................................... 2-3

2.1.2.2 Fan Fail LED (Amber)....................................................................... 2-4

2.1.2.3 Heartbeat LED (Amber).................................................................... 2-4

2.1.2.4 Input Power LED (Green) ................................................................. 2-4

2.2 Fibre Channel Ports ........................................................................................... 2-4

2.2.1 Port LEDs .................................................................................................. 2-5

2.2.1.1 Port Logged-In LED.......................................................................... 2-5

2.2.1.2 Port Activity LED............................................................................... 2-5

2.2.2 Small Form-Factor Pluggable (SFP) Transceivers .................................... 2-6

2.2.3 Port Types ................................................................................................. 2-6

2.3 Ethernet Port ...................................................................................................... 2-7

2.4 Serial Port........................................................................................................... 2-8

2.5 Power Supply and Fan....................................................................................... 2-9

2.6 Switch Management........................................................................................... 2-9

2.6.1 SANsurfer Switch Manager ....................................................................... 2-9

2.6.2 SANsurfer Switch Manager Web Applet.................................................. 2-10

2.6.3 Command Line Interface ......................................................................... 2-10

2.6.4 SANsurfer Switch Manager Application Programming Interface............. 2-10

2.6.5 Simple Network Management Protocol ................................................... 2-10

2.6.6 File Transfer Protocol .............................................................................. 2-11

Section 3 Planning

3.1 Devices............................................................................................................... 3-1

3.2 Device Access.................................................................................................... 3-2

3.2.1 Soft Zones ................................................................................................. 3-3

3.2.2 Access Control List Hard Zones................................................................ 3-3

3.3 Performance.......................................................................................................3-4

3.3.1 Distance.....................................................................................................3-4

3.3.2 Bandwidth.................................................................................................. 3-5

3.3.3 Latency...................................................................................................... 3-5

3.4 Multiple Chassis Fabrics .................................................................................... 3-6

3.4.1 Optimizing Device Performance................................................................ 3-6

3.4.2 Domain ID, Principal Priority, and Domain ID Lock ...................................3-7

3.4.3 Common Topologies.................................................................................. 3-8

3.4.3.1 Cascade Topology ............................................................................ 3-8

3.4.3.2 Mesh Topology .................................................................................3-9

3.4.3.3 Multistage Topology........................................................................ 3-10

3.5 Fabric Security ................................................................................................. 3-11

3.5.1 User Account Security............................................................................. 3-11

3.5.2 Fabric Services........................................................................................ 3-11

Page iv 59042-06 A

SANbox2-8c Fibre Channel Switch

3.6 Fabric Management ......................................................................................... 3-12

Installation Guide

Section 4 Installation

4.1 Site Requirements..............................................................................................4-1

4.1.1 Fabric Management Workstation............................................................... 4-1

4.1.2 Switch Power Requirements ..................................................................... 4-1

4.1.3 Environmental Conditions.......................................................................... 4-2

4.2 Installing a Switch............................................................................................... 4-2

4.2.1 Mount the Switch....................................................................................... 4-3

4.2.2 Install SFP Transceivers............................................................................ 4-4

4.2.3 Connect the Workstation to the Switch...................................................... 4-5

4.2.4 Configure the Workstation......................................................................... 4-6

4.2.4.1 Setting the Workstation IP Address for Ethernet Connections ......... 4-6

4.2.4.2 Configuring the Workstation Serial Port............................................ 4-6

4.2.5 Install SANsurfer Switch Manager............................................................. 4-8

4.2.5.1 SANsurfer Management Suite Disk - Windows Installation.............. 4-8

4.2.5.2 SANsurfer Management Suite Disk - Linux Installation.................... 4-9

4.2.5.3 SANsurfer Management Suite Disk - Solaris Installation................ 4-10

4.2.5.4 SANsurfer Switch Manager Installation Disk -

Windows Installation....................................................................... 4-11

4.2.5.5 SANsurfer Switch Manager Installation Disk - Linux Installation .... 4-11

4.2.5.6 SANsurfer Switch Manager Installation Disk - Solaris Installation .. 4-12

4.2.6 Start SANsurfer Switch Manager............................................................. 4-12

4.2.7 Connect the Switch to AC Power ............................................................ 4-13

4.2.8 Configure the Switch ............................................................................... 4-16

4.2.9 Cable Devices to the Switch.................................................................... 4-17

4.3 Install Firmware ................................................................................................4-18

4.3.1 Using SANsurfer Switch Manager to Install Firmware............................. 4-19

4.3.2 Using the CLI to Install Firmware ............................................................ 4-19

4.3.3 Using FTP and the CLI to Install Firmware.............................................. 4-20

4.4 Powering Down a Switch.................................................................................. 4-22

Section 5 Diagnostics/Troubleshooting

5.1 POST Diagnostics.............................................................................................. 5-1

5.1.1 Heartbeat LED Blink Patterns.................................................................... 5-2

5.1.1.1 Internal Firmware Failure Blink Pattern ............................................ 5-2

5.1.1.2 System Error Blink Pattern ............................................................... 5-2

5.1.1.3 Configuration File System Error Blink Pattern .................................. 5-3

5.1.2 Logged-In LED Indications ........................................................................ 5-6

5.1.2.1 E_Port Isolation ................................................................................ 5-7

59042-06 A Page v

SANbox2-8c Fibre Channel Switch Installation Guide

5.1.2.2 Excessive Port Errors ....................................................................... 5-8

5.2 Chassis Diagnostics......................................................................................... 5-10

5.2.1 Over Temperature LED is Illuminated...................................................... 5-10

5.2.2 Input Power LED Is Extinguished............................................................ 5-11

5.2.3 Fan Fail LED is Illuminated...................................................................... 5-11

5.3 Recovering a Switch......................................................................................... 5-12

5.3.1 Maintenance – Exit.................................................................................. 5-13

5.3.2 Maintenance – Image Unpack................................................................. 5-13

5.3.3 Maintenance – Reset Network Config..................................................... 5-14

5.3.4 Maintenance – Reset User Accounts to Default...................................... 5-14

5.3.5 Maintenance – Copy Log Files................................................................ 5-14

5.3.6 Maintenance – Remove Switch Config.................................................... 5-14

5.3.7 Maintenance – Remake Filesystem ........................................................ 5-14

5.3.8 Maintenance – Reset Switch................................................................... 5-14

5.3.9 Maintenance – Show Firmware Versions ................................................ 5-15

5.3.10 Maintenance – Set Active Image............................................................. 5-15

Appendix A Specifications

A.1 Fabric Specifications ..........................................................................................A-1

A.2 Maintainability.....................................................................................................A-2

A.3 Fabric Management ...........................................................................................A-3

A.4 Dimensions.........................................................................................................A-3

A.5 Electrical.............................................................................................................A-3

A.6 Environmental ....................................................................................................A-4

A.7 Regulatory Certifications ....................................................................................A-5

Appendix B Command Line Interface

B.1 Logging On to a Switch ......................................................................................B-1

B.2 User Accounts....................................................................................................B-1

B.3 Working with Switch Configurations...................................................................B-2

B.3.1 Modifying a Configuration..........................................................................B-2

B.3.2 Backing up and Restoring Switch Configurations......................................B-3

B.4 Commands .........................................................................................................B-5

Admin Command.......................................................................................B-7

Alias Command .........................................................................................B-8

Config Command.....................................................................................B-10

Date Command .......................................................................................B-13

Fallback Command..................................................................................B-14

Hardreset Command ...............................................................................B-15

Help Command........................................................................................B-16

Page vi 59042-06 A

SANbox2-8c Fibre Channel Switch

Installation Guide

History Command....................................................................................B-17

Hotreset Command .................................................................................B-18

Image Command.....................................................................................B-19

Lip Command ..........................................................................................B-20

Passwd Command ..................................................................................B-21

Ping Command........................................................................................B-22

Ps Command...........................................................................................B-23

Quit Command ........................................................................................B-24

Reset Command......................................................................................B-25

Set Command..........................................................................................B-31

Set Config Command ..............................................................................B-33

Set Log Command...................................................................................B-44

Set Port Command..................................................................................B-47

Set Setup Command ...............................................................................B-49

Show Command......................................................................................B-55

Show Config Command...........................................................................B-70

Show Log Command...............................................................................B-73

Show Perf Command ..............................................................................B-76

Show Setup Command............................................................................B-78

Shutdown Command...............................................................................B-81

Test Command ........................................................................................B-82

Uptime Command....................................................................................B-85

User Command .......................................................................................B-86

Whoami Command..................................................................................B-89

Zone Command.......................................................................................B-90

Zoneset Command..................................................................................B-94

Zoning Command....................................................................................B-96

Glossary

Index

59042-06 A Page vii

SANbox2-8c Fibre Channel Switch Installation Guide

Figures

Figure Page

2-1 SANbox2-8c Fibre Channel Switch................................................................................ 2-1

2-2 Chassis Controls and LEDS........................................................................................... 2-2

2-3 Chassis LEDs.................................................................................................................2-3

2-4 Fibre Channel Ports ....................................................................................................... 2-4

2-5 Port LEDs....................................................................................................................... 2-5

2-6 SFP Transceiver ............................................................................................................ 2-6

2-7 Ethernet Port.................................................................................................................. 2-7

2-8 Serial Port and Pin Identification.................................................................................... 2-8

3-1 Cascade-with-a-Loop Topology ..................................................................................... 3-8

3-2 Mesh Topology...............................................................................................................3-9

3-3 Multistage Topology..................................................................................................... 3-10

4-1 SANbox2-8c Fibre Channel Switch................................................................................ 4-2

4-2 Ethernet and Serial Cable Connections......................................................................... 4-5

5-1 Logged-In LED............................................................................................................... 5-6

5-2 Logged-In LED Indications............................................................................................. 5-6

5-3 Chassis LEDs............................................................................................................... 5-10

Tables

Table Page

2-1 Serial Port Pin Identification........................................................................................... 2-8

3-1 Zoning Database Limits ................................................................................................. 3-2

3-2 Port-to-Port Transmission Combinations ....................................................................... 3-5

3-3 Port-to-Port Latency....................................................................................................... 3-5

4-1 Management Workstation Requirements....................................................................... 4-1

B-1 Command-Line Completion ...........................................................................................B-5

B-2 Commands Listed by Authority Level.............................................................................B-6

B-3 Switch Configuration Defaults ......................................................................................B-26

B-4 Port Configuration Defaults..........................................................................................B-27

B-5 Port Threshold Alarm Configuration Defaults...............................................................B-28

B-6 Zoning Configuration Defaults......................................................................................B-28

B-7 SNMP Configuration Defaults ......................................................................................B-29

B-8 System Configuration Defaults.....................................................................................B-30

B-9 Set Config Port Parameters .........................................................................................B-33

B-10 Set Config Switch Parameters .....................................................................................B-36

B-11 Set Config Threshold Parameters................................................................................B-38

B-12 Set Config Zoning Parameters.....................................................................................B-39

B-13 SNMP Configuration Settings ......................................................................................B-49

B-14 System Configuration Settings.....................................................................................B-50

B-15 Show Port Parameters.................................................................................................B-57

B-16 Switch Operational Parameters ...................................................................................B-60

B-17 Zoning Database Limits ...............................................................................................B-97

Page viii 59042-06 A

Section 1

Introduction

This manual describes the features and installation of the SANbox2-8c Fibre Channel switch, firmware version 4.1. This manual is organized as follows:

 Section 1 describes the intended audience, related materials, safety notices,

communications statements, laser safety information, electrostatic discharge sensitivity precautions, accessible parts, general program license, and technical support.

 Section 2 is an overview of the switch. It describes indicator LEDs and all

user controls and connections.

 Section 3 describes the factors to consider when planning a fabric.

 Section 4 explains how to install and configure the switch.

 Section 5 describes the diagnostic methods and troubleshooting

procedures.

 Appendix A lists the switch specifications.

 Appendix B describes the Command Line Interface.

Please read the communications statements and laser safety information later in this section. Use this manual with the SANbox2-8c/16 Switch Management User’s Guide.

1.1

Intended Audience

This manual introduces users to the switch and explains its installation and service. It is intended for users who are responsible for installing and servicing network equipment.

1.2

Related Materials

The following manuals and materials are referenced in the text and/or provide additional information.

 SANbox2-8c/16 Switch Management User’s Guide, publication number

59022-09.

 QLogic Switch Interoperability Guide v3.0. This PDF document can be

downloaded at http://www.qlogic.com/interopguide/info.asp#inter.

 Fibre Channel-Arbitrated Loop (FC-AL-2) Rev. 6.8.

 Fibre Channel-10-bit Interface Rev. 2.3.

59042-06 A 1-1

1 – Introduction New in this Release

 Definitions of Managed Objects for the Fabric Element in Fibre Channel

Standard (draft-ietf-ipfc-fabric-element-mib-04.txt).

The Fibre Channel Standards are available from:

Global Engineering Documents, 15 Inverness Way East, Englewood, CO 80112-5776 Phone: (800) 854-7179 or (303) 397-7956 Fax: (303) 397-2740.

1.3

New in this Release

The following items are new in the current firmware release:

 Expanded zoning database limits

 SANsurfer Switch Manager web applet embedded on the switch. The

firmware includes an enable parameter and an inactivity timeout.

 Network Time Protocol (NTP) client support for synchronizing switch time

 Automatic port tuning for Multiple Frame Sequence (MFS) bundling, Link

Control Frame (LCF) preference routing, and Virtual Interface (VI) routing.

The following items are new in the current SANsurfer Switch Manager release:

 SANbox Manager is renamed SANsurfer Switch Manager.

 SANsurfer Fabric View is renamed SANsurfer Performance Viewer.

 Fabric Tracker menu option has been added to record the fabric hardware

and firmware composition.

 Nicknames for device port world wide names

 Zoning wizard menu option has been added to assist in zoning a fabric.

 Name Server and FDMI data windows are combined into Devices data

window.

 Export Name Server and Export FDMI menu options are combined into

Export Devices.

 SNMP properties has been removed from Network Properties dialog to form

SNMP Properties dialog.

1-2 59042-06 A

1.4

Safety Notices

A Warning notice indicates the presence of a hazard that has the potential of causing personal injury.

A Caution notice indicates the presence of a hazard that has the potential of causing damage to the equipment.

1.5

Sicherheitshinweise

Ein Warnhinweis weist auf das Vorhandensein einer Gefahr hin, die möglicherweise Verletzungen zur Folge hat.

Ein Vorsichtshinweis weist auf das Vorhandensein einer Gefahr hin, die möglicherweise Geräteschäden zur Folge hat.

1.6

Notes informatives relatives à la sécurité

Une note informative Avertissement indique la présence d’un risque pouvant entraîner des blessures.

1 – Introduction

Safety Notices

Une note informative Attention indique la présence d’un risque pouvant entraîner des dégâts matériels.

59042-06 A 1-3

1 – Introduction Communications Statements

1.7

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.

1.7.1

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 undesired operation.

1.7.2

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.

1-4 59042-06 A

1 – Introduction

1.7.3

Communications Statements

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.

1.7.4

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/A11:1997 – “Safety of Information Technology Equipment,

Including Electrical Business Equipment”.

 EN55022:1998 – “Limits and Methods of Measurement of Radio

Interference Characteristics of Information Technology Equipment”.

 EN55024-1:1998 – “Electromagnetic compatibility - Generic immunity

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

 IEC1000-4-2:1995 – “Electrostatic Discharge Immunity Test”

 IEC1000-4-3:1995 – “Radiated, Radio-Frequency, Electromagnetic

Field Immunity Test”

 IEC1000-4-4:1995 – “Electrical Fast Transient/Burst Immunity Test”

 IEC1000-4-5:1995 – “Surge Immunity Test”

 IEC1000-4-6:1996 – “Immunity To Conducted Disturbances, Induced

By Radio-Frequency Fields”

 IEC1000-4-8:1993 – "Power Frequency Magnetic Field Immunity Test”

 IEC1000-4-11:1994 – “Voltage Dips, Short Interruptions And Voltage

Variations Immunity Tests”

 EN61000-3-2:1995 – “Limits For Harmonic Current Emissions (Equipment

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

 EN61000-3-3:1995 – “Limitation Of Voltage Fluctuations And Flicker In

Low-Voltage Supply Systems For Equipment With Rated Current Less Than Or Equal To 16 A”

59042-06 A 1-5

1 – Introduction Communications Statements

1.7.5

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.

1.7.6

BSMI Class A Statement

Warning:

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

1-6 59042-06 A

1.8

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.

1 – Introduction

Laser Safety Information

1.9

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.

59042-06 A 1-7

1 – Introduction Accessible Parts

1.10

Accessible Parts

The Field Replaceable Units (FRUs) in the SANbox2-8c switch are the following:

 Small Form-Factor Pluggable (SFP) optical transceivers

1.11

Pièces Accessibles

Les pièces remplaçables, Field Replaceable Units (FRU), du commutateur SANbox2-8c Fibre Channel Switch sont les suivantes:

 Interfaces aux media d’interconnexion appelés SFP transceivers.

1.12

Zugängliche Teile

Nur die folgenden Teile im SANbox2-8c Fibre Channel Switch können kundenseitig ersetzt werden:

 Schnittstellen für die Zwischenverbindungsträger, SFP transceivers

genannt.

1-8 59042-06 A

1.13

General Public License

QLogic® Fibre Channel switches 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 6321 Bury Drive Eden Prairie, MN 55346-1739 Attention: Technical Support - Source Request

Warning: 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:

1 – Introduction

General Public License

1.13.1

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 other 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 free programs; and that you know you can do these things.

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.

59042-06 A 1-9

1 – Introduction General Public License

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' reputations.

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

1.13.2

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.

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

You may charge a fee for the physical act of transferring a copy, and you may at your option offer warranty protection in exchange for a fee.

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

1-10 59042-06 A

1 – Introduction

General Public License

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, 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 a whole which is a work based on the Program, the distribution 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 or distribution medium does not bring the other work under the scope of this 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 Sections 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 Sections 1 and 2 above on a medium customarily used for software interchange; or,

59042-06 A 1-11

1 – Introduction General Public License

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 Sections 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 Subsection b above.)

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

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

1-12 59042-06 A

1 – Introduction

General Public License

rights granted herein. You are not responsible for enforcing compliance by third parties to this License.

8. If, as a consequence of a court judgment 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, 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, 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.

9. If the distribution and/or use of the Program is restricted in certain countries either by patents or by copyrighted 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

59042-06 A 1-13

1 – Introduction General Public License

12. If you wish to incorporate parts of the Program into other free programs

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

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

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 software generally.

NO WARRANTY

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 THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

END OF TERMS AND CONDITIONS

1.13.3

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.

1-14 59042-06 A

1 – Introduction

General Public License

one line to give the program's name and an idea of what it does.

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.

This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.

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 add 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 show 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:

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.

59042-06 A 1-15

1 – Introduction Technical Support

1.14

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.

Visit the QLogic support Web site listed in Contact Information for the latest firmware and software updates.

1.14.1

Availability

QLogic Technical Support is available from 7:00 AM to 7:00 PM Central Standard Time, Monday through Friday, excluding QLogic-observed holidays.

1.14.2

Training

QLogic offers certification training for the technical professional for both the SANblade™ HBAs and the SANbox2™ switches. From the training link at

www.qlogic.com, you may choose Electronic-Based Training or schedule an

intensive "hands-on" Certification course.

Technical Certification courses include installation, maintenance and troubleshooting QLogic SAN products. Upon demonstrating knowledge using live equipment, QLogic awards a certificate identifying the student as a Certified Professional. The training professionals at QLogic may be reached by email at tech.training@qlogic.com.

1.14.3

Contact Information

Telephone: +1 952-932-4040

Fax: +1 952-932-4018

Email: Technical Service Technical Training

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

support@qlogic.com tech.training@qlogic.com

1-16 59042-06 A

Section 2

General Description

This section describes the features and capabilities of the SANbox2-8c Fibre Channel switch. The following topics are described:

 Chassis controls and LEDs

 Fibre channel ports

 Ethernet port

 Serial port

 Power supply and fan

 Switch management

Fabrics are managed with the SANsurfer Switch Manager™ switch management application (version 4.01) and the Command Line Interface (CLI). Refer to the SANbox2-8c/16 Switch Management User’s Guide for information about using the SANsurfer Switch Manager application. Refer to Appendix B Command Line

Interface for more information about the command line interface.

Figure 2-1. SANbox2-8c Fibre Channel Switch

59042-06 A 2-1

2 – General Description Chassis Controls and LEDs

2.1

Chassis Controls and LEDs

The Maintenance button shown in Figure 2-2 is the only chassis control and is used to reset a switch or to recover a disabled switch. The chassis LEDs provide information about the switch’s operational status. These LEDS include the Over Temperature LED, Fan Fail LED, Heartbeat LED, and the Input Power LED. To apply power to the switch, plug the power cord into the switch AC power receptacle and into a 110 or 230 VAC power source.

AC Power

Receptacle

Chassis LEDs

Figure 2-2. Chassis Controls and LEDS

2.1.1

Maintenance Button

The Maintenance button is a dual-function momentary switch on the front panel. Its purpose is to reset the switch or to place the switch in maintenance mode. Maintenance mode sets the IP address to 10.0.0.1 and provides access to the switch for maintenance purposes when flash memory or the resident configuration file is corrupted. Refer to ”Recovering a Switch” on page 5-12 for more information about using maintenance mode.

Maintenance

Button

2.1.1.1

Resetting a Switch

To reset the switch, use a pointed tool to momentarily press and release (less than 2 seconds) the Maintenance button. The switch will respond as follows:

1. All of the chassis LEDs will illuminate and then extinguish leaving only the Input Power LED illuminated.

2. After approximately 1 minute, the Power-On Self Test (POST) begins illuminating all chassis LEDs.

3. When the POST is complete, the chassis LEDs extinguish leaving the Input Power LED illuminated and the Heartbeat LED flashing once per second.

2-2 59042-06 A

2.1.1.2

Placing the Switch in Maintenance Mode

To place the switch in maintenance mode, do the following:

1. Isolate the switch from the fabric.

2. Press and hold the Maintenance button with a pointed tool for 2–4 seconds. When the Input Power LED alone is illuminated, release the button.

3. After approximately 1 minute, the POST begins illuminating all chassis LEDs.

4. When the POST is complete, the chassis LEDs extinguish leaving the Input Power LED and the Heartbeat LED illuminated. The Heartbeat LED illuminates continuously while the switch is in maintenance mode.

To exit maintenance mode and return to normal operation, momentarily press and release the Maintenance button to reset the switch.

2.1.2

Chassis LEDs

2 – General Description

Chassis Controls and LEDs

The chassis LEDs shown in Figure 2-3 provide status information about switch operation. Refer to ”Port LEDs” on page 2-5 for information about port LEDs.

Over Temperature LED

(Amber)

Fan Fail LED

(Amber)

Figure 2-3. Chassis LEDs

2.1.2.1

Over Temperature LED (Amber)

The Over Temperature LED provides status information about the air temperature inside the switch. This LED illuminates to indicate that the switch logic circuitry is overheating. Refer to Section 5 Diagnostics/Troubleshooting for information about troubleshooting over temperature conditions.

Input Power LED

(Green)

Heartbeat LED

(Amber)

59042-06 A 2-3

2 – General Description Fibre Channel Ports

2.1.2.2

Fan Fail LED (Amber)

The Fan Fail LED indicates operational status of the fan. This LED illuminates if the speed of the fan falls below the normal range. If the Fan Fail LED illuminates, isolate the switch from the fabric, unplug the switch from the AC power source, and contact your authorized maintenance provider.

2.1.2.3

Heartbeat LED (Amber)

The Heartbeat LED indicates the status of the internal switch processor and the results of the Power On Self Test (POST). Following a normal power-up, the Heartbeat LED blinks about once per second to indicate that the switch passed the POST and that the internal switch processor is running. In maintenance mode, the Heartbeat LED illuminates continuously. Refer to ”Heartbeat LED Blink

Patterns” on page 5-2 for more information about Heartbeat LED blink patterns.

2.1.2.4

Input Power LED (Green)

The Input Power LED indicates the voltage status at the switch logic circuitry. During normal operation, this LED illuminates to indicate that the switch logic circuitry is receiving the proper DC voltages.

2.2

Fibre Channel Ports

The SANbox2-8c switch has 8 Fibre Channel ports numbered 0–7 as shown in

Figure 2-4. Each of these ports is served by a Small Form-Factor Pluggable (SFP)

optical transceiver. The port LEDs are located above their respective ports and provide port login and activity status information. The ports self discover the proper mode when connected to public devices and other switches.

Port LEDs

Fibre Channel

Port

Figure 2-4. Fibre Channel Ports

2-4 59042-06 A

2.2.1

Port LEDs

2 – General Description

Fibre Channel Ports

Each Fibre Channel port has its own Logged-In LED and Activity LED as shown in

Figure 2-5.

2.2.1.1

Port Logged-In LED

The Logged-in LED indicates the logged-in or initialization status of the connected devices. After successful completion of the POST, the switch extinguishes all Logged-In LEDs. Following a successful loop initialization or port login, the switch illuminates the corresponding logged-in LED. This shows that the port is properly connected and able to communicate with its attached devices. The Logged-In LED remains illuminated as long as the port is initialized or logged in. If the port connection is broken or an error occurs that disables the port, the Logged-In LED will flash. Refer to ”Logged-In LED Indications” on page 5-6 for more information about the Logged-In LED.

Logged-In

LED (Green)

Figure 2-5. Port LEDs

Activity LED

(Green)

2.2.1.2

Port Activity LED

The Activity LED indicates that data is passing through the port. Each frame that the port transmits or receives causes this LED to illuminate for 50 milliseconds. This makes it possible to observe the transmission of a single frame. When extending credits, the Activity LED for a donor port will reflect the traffic of the recipient port. Refer to ”Distance” on page 3-4 for more information about extended credits and donor ports.

59042-06 A 2-5

2 – General Description Fibre Channel Ports

2.2.2

Small Form-Factor Pluggable (SFP) Transceivers

An SFP transceiver, like the one shown in Figure 2-6, converts electrical signals to and from optical laser signals to transmit and receive. SFP transceivers plug into the ports; duplex fiber optic cables plug into the transceivers which then connect to the devices. A port is capable of transmitting at 1-Gbps or 2-Gbps; however, the transceiver must be capable of 2-Gbps for the port to deliver at that rate.

The SFP transceivers are hot pluggable. This means that you can remove or install an SFP transceiver while the switch is operating without harming the switch or the transceiver. However, communication with the connected device will be interrupted. Refer to ”Install SFP Transceivers” on page 4-4 for information about installing and removing SFP optical transceivers.

2.2.3

Port Types

Figure 2-6. SFP Transceiver

SANbox2-8c switches support generic ports (G_Port, GL_Port), fabric ports (F_Port, FL_Port), and expansion ports (E_Port). Switches come from the factory with all ports configured as GL_Ports. Generic, fabric, and expansion ports function as follows:

 A GL_Port self-configures as an FL_Port when connected to a public loop

device, as an F_Port when connected to a single public device, or as an E_Port when connected to another FC-SW-2 compliant switch.

 A G_Port self-configures as an F_Port when connected to a single public

device, or as an E_Port when connected to another FC-SW-2 compliant switch.

 An FL_Port supports a loop of up to 126 public devices. An FL_Port can also

configure itself during the fabric login process as an F_Port when connected to a single public device (N_Port).

 An F_Port supports a single public device. If the device is a single device on

a loop, the GL_Port will attempt to configure first as an F_Port, then if that fails, as an FL_Port.

2-6 59042-06 A

E_Ports enable you to expand the fabric by connecting SANbox2-8c switches with other FC-SW-2 compliant switches. SANbox2-8c switches self-discover all inter-switch connections. Refer to ”Multiple Chassis Fabrics” on page 3-6 for more information about multiple chassis fabrics. Refer to the SANbox2-8c/16 Switch Management User’s Guide for more information about defining port types.

2.3

Ethernet Port

The Ethernet port shown in Figure 2-7 is an RJ-45 connector that provides a connection to a management workstation through a 10/100 Base-T Ethernet cable. A management workstation can be a Windows®, Solaris™, or a Linux®, workstation that is used to configure and manage the switch fabric. You can manage the switch over an Ethernet connection using SANsurfer Switch Manager, the Command Line Interface (CLI), or SNMP. The switch through which the fabric is managed is called the fabric management switch.

The Ethernet port has two LEDs: the Link Status LED (green) and the Activity LED (amber). The Link Status LED illuminates continuously when an Ethernet connection has been established. The Activity LED illuminates when data is being transmitted or received over the Ethernet connection.

2 – General Description

Ethernet Port

Link Status LED

(Green)

Figure 2-7. Ethernet Port

Activity LED

(Amber)

RJ-45 Ethernet Port

59042-06 A 2-7

2 – General Description Serial Port

2.4

Serial Port

The SANbox2-8c switch is equipped with an RS-232 serial port for maintenance purposes. The serial port location is shown in Figure 2-8. You can manage the switch through the serial port using the CLI.

Serial Port

Figure 2-8. Serial Port and Pin Identification

The serial port connector requires a null-modem F/F DB9 cable. The pins on the switch RS-232 connector are shown in Figure 2-8 and identified in Table 2-1. Refer to ”Connect the Workstation to the Switch” on page 4-5 for information about connecting the management workstation through the serial port.

Table 2-1. Serial Port Pin Identification

Pin Number Description

1 Carrier Detect (DCD)

2 Receive Data (RxD)

3 Transmit Data (TxD)

4 Data Terminal Ready (DTR)

5 Signal Ground (GND)

6 Data Set Ready (DSR)

7 Request to Send (RTS)

8 Clear to Send (CTS)

9 Ring Indicator (RI)

2-8 59042-06 A

2.5

Power Supply and Fan

The power supply converts standard 110 or 230 VAC to DC voltages for the various switch circuits. An internal fan provides cooling. Air flow can be front-to-back or back-to-front depending on the switch model. To energize the switch, plug the power cord into the switch AC receptacle and into a 110 or 230 VAC power source.

Note: The power supply and fan are not field replaceable units.

2.6

Switch Management

The switch supports the following management tools:

 SANsurfer Switch Manager

 SANsurfer Switch Manager web applet

2 – General Description

Power Supply and Fan

 SANsurfer Switch Manager Application Programming Interface (API)

 Command line interface (CLI)

 Simple Network Management Protocol (SNMP)

 File Transfer Protocol (FTP)

2.6.1

SANsurfer Switch Manager

SANsurfer Switch Manager is a workstation-based Java® application that provides a graphical user interface for fabric management. This includes SANsurfer Performance Viewer which graphs port performance. SANsurfer Switch Manager can run on a Windows, Solaris, or Linux workstation. A management workstation connects to the fabric through the Ethernet port of one or more switches and can provide in-band management for all other switches in the fabric. Refer to the SANbox2-8c/16 Switch Management User’s Guide for information about the SANsurfer Switch Manager application and its use.

59042-06 A 2-9

2 – General Description Switch Management

2.6.2

SANsurfer Switch Manager Web Applet

To make switch management less dependent on a particular workstation, each switch contains a SANsurfer Switch Manager web applet. One instance of the web applet can be run at a time by opening the switch IP address with an internet browser. The switch comes from the factory with the web applet enabled, but you can disable it using the EmbeddedGUIEnabled parameter of the Set Setup System command. An inactivity timeout can also be set. Refer to ”Set Setup

Command” on page B-49 for more information.

The applet possesses the same features as the workstation-based version with the following exceptions:

 Extended Credits wizard

 Zoning Wizard

 SANsurfer Performance Viewer

 Condensed online help

2.6.3

Command Line Interface

The command line interface (CLI) provides monitoring and configuration functions by which the administrator can manage the fabric and its switches. The CLI is available over an Ethernet connection or a serial connection. Refer to

Appendix B Command Line Interface for more information.

2.6.4

SANsurfer Switch Manager Application Programming Interface

The SANsurfer Switch Manager API enables an application provider to build a management application for QLogic switches. The library is implemented in ANSI standard C, relying only on standard POSIX run-time libraries (except for the Windows NT build). Contact your distributor or authorized reseller for information about the SANsurfer Switch Manager API.

2.6.5

Simple Network Management Protocol

SNMP provides monitoring and trap functions for the fabric. SANbox2 firmware supports SNMP versions 1 and 2, the Fibre Alliance Management Information Base (FA-MIB) version 4.0, and the Fabric Element Management Information Base (FE-MIB) RFC 2837. Traps can be formatted using SNMP version 1 or 2. Refer to the SANbox/SANbox2 Simple Network Management Protocol Reference Guide for more information about using SNMP.

2-10 59042-06 A

2.6.6

File Transfer Protocol

FTP provides the command line interface for exchanging files between the switch and the management workstation. These files include firmware image files, configuration files, and log files. ”Backing up and Restoring Switch Configurations”

on page B-3 provides an example of using FTP to transfer configuration files.

2 – General Description

Switch Management

59042-06 A 2-11

2 – General Description Switch Management

Notes

2-12 59042-06 A

3.1

Devices

Section 3

Planning

Consider the following when planning a fabric:

 Devices

 Device access

 Performance

 Multiple chassis fabrics

 Fabric security

 Fabric management

When planning a fabric, consider the number of devices and the anticipated demand. This will determine the number of ports that are needed and the number of switches. Consider how many and what types of switches are needed.

The switch uses SFP optical transceivers, but the device host bus adapters you are using may not. Consider whether the device adapters use SFP transceivers or Gigabit Interface Converters (GBIC), and choose fiber optic cables accordingly. Use LC-type cable connectors for SFP transceivers and SC-type cable connectors for GBIC transceivers.

SANbox2 switches support public initiator and target devices. Consider the distribution of target and initiator devices. An F_Port supports a single public device. An FL_Port can support up to 126 public devices in an arbitrated loop.

59042-06 A 3-1

3 – Planning Device Access

3.2

Device Access

Consider device access needs within the fabric. Access is controlled by the use of zones and zone sets. Some zoning strategies include the following:

 Group devices by operating systems.

 Separate devices that have no need to communicate with other devices in

 Separate devices into department, administrative, or other functional group.

 Reserve a path and its bandwidth from one port to another.

A zone is a named group of devices that can communicate with each other. Membership in a zone can be defined by switch domain ID and port number, port Fibre Channel address, or by device worldwide name (WWN). Devices can communicate only with devices that are within the same zone. A zone can be a member of more than one zone set. Several zone sets can be defined for a fabric, but only one zone set can be active at one time. The active zone set determines the current fabric zoning.

the fabric or have classified data.

A zoning database is maintained on each switch consisting of all inactive zone sets, the active zone set, all zones, aliases, and their membership. Tab le 3- 1 describes the zoning database limits, excluding the active zone set. Refer to the SANbox2-8c/16 Switch Management User’s Guide for more information about zoning.

Table 3-1. Zoning Database Limits

Limit Description

MaxZoneSets Maximum number of zone sets (256).

MaxZones Maximum number of zones (1000).

MaxAliases Maximum number of aliases (2500).

MaxTotalMembers Maximum number of zone and alias members (10000)

that can be stored in the switch’s zoning database.

MaxZonesInZoneSets Maximum number of zones that are components of

zone sets (1000), excluding the orphan zone set, that can be stored in the switch’s zoning database. Each instance of a zone in a zone set counts toward this maximum.

MaxMembersPerZone Maximum number of members in a zone (2000)

MaxMembersPerAlias Maximum number of members in an alias (2000)

3-2 59042-06 A

3.2.1

Soft Zones

3 – Planning

Device Access

Soft zoning divides the fabric for purposes of controlling device discovery. Devices in the same soft zone automatically discover and communicate freely with all other members of the same zone. The soft zone boundary is not secure; traffic across soft zones can occur if addressed correctly. The following rules apply to soft zones:

 Soft zones that include members from multiple switches need not include

the ports of the inter-switch links.

 Soft zone boundaries yield to ACL zone boundaries.

 Soft zones can overlap; that is, a port can be a member of more than one

soft zone.

 Membership can be defined by Fibre Channel address, domain ID and port

number, or worldwide name.

 Soft zoning supports FL_Ports and F_Ports.

3.2.2

Access Control List Hard Zones

Access Control List (ACL) zoning divides the fabric for purposes of controlling discovery and inbound traffic. ACL zoning is a type of hard zoning that is hardware enforced. This type of zoning is useful for controlling access to certain devices without totally isolating them from the fabric. Members can communicate with each other and transmit outside the ACL zone, but cannot receive inbound traffic from outside the zone. The following rules apply to ACL zones:

 The ACL zone boundary is secure against inbound traffic.

 ACL zones can overlap; that is, a port can be a member of more than one

ACL zone.

 ACL zones that include members from multiple switches need not include

the ports of the inter-switch links.

 ACL zone boundaries supersede soft zone boundaries.

 Membership can be defined only by domain ID and port ID. A switch port

can be a member of multiple ACL zones whose combined membership does not exceed 128.

59042-06 A 3-3

3 – Planning Performance

3.3

Performance

The SANbox2-8c switch supports class 2 and class 3 Fibre Channel service at transmission rates of 1-Gbps or 2-Gbps with a maximum frame size of 2148 bytes. A port can transmit or receive at 1-Gbps or 2-Gbps depending on the device to which it is connected. The port discovers the transmission speed prior to login when the connected device powers up. Related performance characteristics include the following:

 Distance

 Bandwidth

 Latency

3.3.1

Distance

Consider the physical distribution of devices and switches in the fabric. Choose SFP transceivers that are compatible with the cable type, distance, Fibre Channel revision level, and the device host bus adapter. Refer to

Appendix A Specifications for more information about cable types and SFP

transceivers.

Each port is supported by a data buffer with a 12 credit capacity; that is, 12 maximum sized frames. For fibre optic cables, this enables full bandwidth over a distance of 20 kilometers at 1-Gbps (0.6 credits/Km), or 10 kilometers at 2-Gbps (1.2 credits/Km). Beyond this distance, however, there is some loss of efficiency because the transmitting port must wait for an acknowledgement before sending the next frame.

Longer distances can be spanned at full bandwidth by extending credits on G_Ports and F_Ports. Each port can donate 11 credits to a pool from which a recipient port can borrow. For example, you can configure a recipient port to borrow up to 66 credits from 6 ports for a total of 78 credits. This will support communication over approximately 130 Km at 1 Gbps (78÷0.6) or 65 Km at 2 Gbps (78÷1.2).

You can configure recipient and donor ports using SANsurfer Switch Manager or the Set Config command. Refer to ”Set Config Command” on page B-33 for more information.

3-4 59042-06 A

3.3.2

Bandwidth

3 – Planning

Performance

Bandwidth is a measure of the volume of data that can be transmitted at a given transmission rate. A port can transmit or receive at 1-Gbps or 2-Gbps depending on the device to which it is connected. The switch supports all transmission rate combinations as shown in Tab le 3 -2 .

Table 3-2. Port-to-Port Transmission Combinations

Source Port Rate Destination Port Rate Maximum Bandwdith

1-Gbps 1-Gbps 100 MB

1-Gbps 2-Gbps 100 MB

1-Gbps x 2 ports 2-Gbps 200 MB

2-Gbps 1-Gbps x 2 ports

2-Gbps 2-Gbps 200 MB

Bandwidth will be less for larger sequence sizes.

100 MB each port

3.3.3

Latency

In multiple chassis fabrics, each link between chassis contributes 100 or 200 megabytes of bandwidth between those chassis. When additional bandwidth is needed between devices, increase the number of links between the connecting switches. The switch guarantees in-order-delivery with any number of links between chassis.

Latency is a measure of how fast a frame travels from one port to another. The factors that affect latency include transmission rate and the source/destination port relationship as shown in Tab le 3- 3.

Table 3-3. Port-to-Port Latency

Source/Destination Rates Same Switch I

1-Gbps – 1-Gbps < 1 µsec

2-Gbps – 2-Gbps < 0.4 µsec

59042-06 A 3-5

3 – Planning Multiple Chassis Fabrics

3.4

Multiple Chassis Fabrics

By connecting switches together you can expand the number of available ports for devices. Each switch in the fabric is identified by a unique domain ID, and the fabric will automatically resolve domain ID conflicts. Because the Fibre Channel ports are self-configuring, you can connect SANbox2-8c and other FC-SW-2 compliant switches together in a wide variety of topologies.

3.4.1

Optimizing Device Performance

When choosing a topology for a multiple chassis fabric, you should also consider the locality of your server and storage devices and the performance requirements of your application. Storage applications such as video distribution, medical record storage/retrieval or real-time data acquisition can have specific latency or bandwidth requirements. Refer to ”Performance” on page 3-4 for information about latency and bandwidth. However, the highest performance is achieved on Fibre Channel switches by keeping traffic within a single switch instead of relying on ISLs. Therefore, for optimal device performance place devices on the same switch under the following conditions:

 Heavy I/O traffic between specific server and storage devices.

 Distinct speed mismatch between devices such as the following:

 A 2-Gbps server and a slower 1-Gbps storage device

 A high performance server and slow tape storage device

3-6 59042-06 A

3.4.2

Domain ID, Principal Priority, and Domain ID Lock

The following switch configuration settings affect multiple chassis fabrics:

 Domain ID

 Principal priority

 Domain ID lock

The domain ID is a unique number from 1–239 that identifies each switch in a fabric. The principal priority is a number (1–255) that determines the principal switch which manages domain ID assignments for the fabric. The switch with the highest principal priority (1 is high, 255 is low) becomes the principal switch. If the principal priority is the same for all switches in a fabric, the switch with the lowest WWN becomes the principal switch.

The domain ID lock allows (False) or prevents (True) the reassignment of the domain ID on that switch. Switches come from the factory with the domain ID set to 1, the domain ID lock set to False, and the principal priority set to 254. Refer to the SANbox2-8c/16 Switch Management User’s Guide for information about changing the domain ID and domain ID lock using SANsurfer Switch Manager. Refer to the ”Set Config Command” on page B-33 for information about changing the default domain ID, domain ID lock, and principal priority parameters.

3 – Planning

Multiple Chassis Fabrics

An unresolved domain ID conflict means that the switch with the higher WWN will isolate as a separate fabric, and the Logged-In LEDs on both switches will flash green to show the affected ports. If you connect a new switch to an existing fabric with its domain ID unlocked, and a domain ID conflict occurs, the new switch will isolate as a separate fabric. However, you can remedy this by resetting the new switch or taking it offline then back online. The principal switch will reassign the domain ID and the switch will join the fabric.

Note: Domain ID reassignment is not reflected in zoning that is defined by

domain ID/port number pair or Fibre Channel address. You must reconfigure zones that are affected by domain ID reassignment. To prevent zoning definitions from becoming invalid under these conditions, lock the domain IDs using SANsurfer Switch Manager or the Set Config Switch command.

59042-06 A 3-7

3 – Planning Multiple Chassis Fabrics

3.4.3

Common Topologies

The SANbox2-8c switch supports three commonly used fabric topologies:

 Cascade

 Mesh

 Multistage®

3.4.3.1

Cascade Topology

A cascade topology describes a fabric in which the switches are connected in series. If you connect the last switch back to the first switch, you create a cascade-with-a-loop topology as shown in Figure 3-1. The loop reduces latency because any switch can route traffic in the shortest direction to any switch in the loop. The loop also provides failover should a switch fail.

The cascade fabric shown in Figure 3-1 has the following characteristics:

 Each chassis link contributes up to 200 MB/s of bandwidth between chassis,

400 MB/s in full duplex. However, because of the sequential structure, that bandwidth will be shared by traffic between devices on other chassis.

 Latency between any two ports is no more than two chassis hops.

 24 Fibre Channel ports are available for devices.

Figure 3-1. Cascade-with-a-Loop Topology

3-8 59042-06 A

3.4.3.2

Mesh Topology

A mesh topology describes a fabric in which each chassis has at least one port directly connected to each other chassis in the fabric. The example mesh fabric shown in Figure 3-2 has the following characteristics:

 Each link contributes up to 200 MB/s of bandwidth between switches, 400

 Latency between any two device ports is one chassis hop.

 20 Fibre Channel ports are available for devices.

3 – Planning

Multiple Chassis Fabrics

MB/s in full duplex. Because of multiple parallel paths, there is less competition for this bandwidth than with a cascade or a Multistage topology.

Figure 3-2. Mesh Topology

59042-06 A 3-9

3 – Planning Multiple Chassis Fabrics

3.4.3.3

Multistage Topology

A Multistage topology describes a fabric in which two or more edge switches connect to one or more core switches. Each additional core switch increases the bandwidth to each edge switch by 200 MB/s. The Multistage fabric shown in

Figure 3-3 has the following characteristics:

 Each link contributes up to 200 MB/s of bandwidth between chassis.

Competition for this bandwidth is less than that of a cascade topology, but greater than that of the mesh topology.

 Latency between any two device ports is no more than two chassis hops.

 26 Fibre Channel ports are available for devices

Core Switch

Edge Switch Edge Switch

Edge Switch

Figure 3-3. Multistage Topology

3-10 59042-06 A

3.5

Fabric Security

Fabric security consists of the following:

 User account security

 Fabric services

3.5.1

User Account Security

User account security consists of the administration of account names, passwords, expiration date, and authority level. If an account has Admin authority, all management tasks can be performed by that account in both SANsurfer Switch Manager and the Command Line Interface. Otherwise only monitoring tasks are available. The default account name, Admin, is the only account that can administer user accounts. Consider your management needs and determine the number of user accounts, their authority needs, and expiration dates.

Account names and passwords are always required when connecting to a switch through Telnet. However, SANsurfer Switch Manager does not authenticate account names when opening a fabric unless user authentication is enabled. User authentication is disabled by default and can be changed using the Set Setup System command. Refer to the ”Set Setup Command” on page B-49 for more information. User authentication must be configured the same for all switches in the fabric. If user authentication is disabled, SANsurfer Switch Manager ignores the account name and password entries and logs you in with the default account name and password (admin, password). Consider your user accounts and determine whether user authentication is necessary.

3 – Planning

Fabric Security

3.5.2

Fabric Services

Fabric services include security-related functions such as inband management and SNMP. Inband management is the ability to manage switches across inter-switch links using SANsurfer Switch Manager, SNMP, management server, or the application programming interface. The switch comes from the factory with inband management enabled. If you disable inband management on a particular switch, you can no longer communicate with that switch by means other than a direct Ethernet or serial connection.

59042-06 A 3-11

3 – Planning Fabric Management

You can also enable or disable the Simple Network Management Protocol (SNMP). SNMP is the protocol governing network management and monitoring of network devices. SNMP security consists of a read community string and a write community string, that are the passwords that control read and write access to the switch. The read community string ("public") and write community string ("private") are set at the factory to these well-known defaults and should be changed if SNMP is enabled. If SNMP is enabled (default) and the read and write community strings have not been changed from their defaults, you risk unwanted access to the switch. SNMP is enabled by default. Consider how you want to manage the fabric and what switches you do not want managed or monitored through other switches.

3.6

Fabric Management

The SANsurfer Switch Manager application and CLI execute on a management workstation that provides for the configuration, control, and maintenance of multiple fabrics. Supported platforms include Windows, Solaris, and Linux. The application can be installed and executed on the workstation, or you can run the SANsurfer Switch Manager web applet that is resident on the switch.

Consider how many fabrics will be managed, how many management workstations are needed, and whether the fabrics will be managed with the CLI, SANsurfer Switch Manager, or the SANsurfer Switch Manager web applet.

A switch supports a combined maximum of 19 logins reserved as follows:

 4 logins or sessions for internal applications such as management server

and SNMP

 9 high priority Telnet sessions

 6 logins or sessions for SANsurfer Switch Manager inband and out-of-band

logins, Application Programming Interface (API) inband and out-of-band logins, and Telnet logins. Additional logins will be refused.

3-12 59042-06 A

Section 4

Installation

This section describes how to install and configure the SANbox2-8c switch. It also describes how to load new firmware and how to recover a disabled switch.

4.1

Site Requirements

Consider the following items when installing a SANbox2-8c switch:

 Fabric management workstation

 Power requirements

 Environmental conditions

4.1.1

Fabric Management Workstation

The requirements for fabric management workstations running SANsurfer Switch Manager are described in Table 4-1:

Table 4-1. Management Workstation Requirements

Operating System

Memory 256 MB or more

Disk Space 150 MB per installation

Processor 500 MHz or faster

Hardware

Internet Browser Microsoft® Internet Explorer® 5.0 or later

Telnet workstations require an RJ-45 Ethernet port or an RS-232 serial port and an operating system with a Telnet client.

4.1.2

 Windows® NT 4.0/2000/2003  Linux® 7.2 Red Hat®, Gnome™ 1.4  Solaris™ 2.8/2.9, CDE

CD-ROM drive,

Netscape Navigator® 4.72 and later Mozilla™ 1.02 and later

Switch Power Requirements

Power requirements are 1 Amp at 90 to 137 Vac and 0.45 Amps at 180 to 264 Vac.

RJ-45 Ethernet port, RS-232 serial port (optional)

59042-06 A 4-1

4 – Installation Installing a Switch

4.1.3

Environmental Conditions

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

 Operating temperature range: 5 – 50°C (41 – 122°F)

 Relative humidity: 15 – 80%, non-condensing

4.2

Installing a Switch

Unpack the switch and accessories. The SANbox2-8c product is shipped with the components shown in Figure 4-1:

 SANbox2-8c Fibre Channel Switch (1) with firmware installed

 Power cord

 Rubber feet (4)

 CD-ROM containing the SANsurfer Switch Manager switch management

application, release notes, and documentation.

Figure 4-1. SANbox2-8c Fibre Channel Switch

4-2 59042-06 A

Installing a SANbox2-8c switch involves the following steps:

1. Mount the switch.

2. Install SFP transceivers.

3. Connect the management workstation to the switch.

4. Configure the management workstation.

5. Install the SANsurfer Switch Manager application.

6. Start the SANsurfer Switch Manager application.

7. Connect the switch to the AC power source.

8. Configure the switch.

9. Cable devices to the switch.

4.2.1

Mount the Switch

The switch can be placed on a flat surface and stacked or mounted in a 19” EIA rack. The top of each chassis has dimples to receive the rubber feet of a second chassis stacked on top. Without the rubber feet, the switch occupies 1U of space in an EIA rack. Mounting rails are required for rack installation and are available through QLogic Corporation.

4 – Installation

Installing a Switch

WARNING!!

AVERTISSEMENT!!

WARNUNG!!

Mount switches 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.

Installer les commutateurs 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.

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

59042-06 A 4-3

4 – Installation Installing a Switch

CAUTION!

4.2.2

 If the switch is mounted in a closed or multi-unit rack assembly, make sure that the operating temperature inside the rack enclosure does not exceed the maximum rated ambient temperature. Refer to ”Environmental” on page A-4.

 The switch must rest on rails or a shelf in the rack or cabinet. Allow 16 cm (6.5 in) minimum clearance at the front and rear of the rack for service access and ventilation.

 Do not restrict chassis air flow. Allow 16 cm (6.5 in) minimum clearance at the front and rear of the 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 switches on the circuit. Refer to ”Electrical” on

page A-3.

 Reliable grounding in the rack must be maintained from the switch chassis to the AC power source.

Install SFP Transceivers

The switch has been validated with transceivers that support a variety of interconnection media. To install, 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 the tension, then pull on the release tab or lever and remove the transceiver. Different transceiver manufacturers have different release mechanisms. Consult the documentation for your transceiver.

Note: The SFP transceiver will fit only one way. If the SFP does not install

under gentle pressure, flip it over and try again.

4-4 59042-06 A

4.2.3

Connect the Workstation to the Switch

You can manage the switch using SANsurfer Switch Manager or the command line interface. SANsurfer Switch Manager requires an Ethernet connection to the switch. The command line interface can use an Ethernet connection or a serial connection. Choose a switch management method, then connect the management workstation to the switch in one of the following ways:

 Indirect Ethernet connection from the management workstation to the switch

RJ-45 Ethernet connector through an Ethernet switch or a hub. This requires a 10/100 Base-T straight cable as shown in Figure 4-2. With this method, you can manage the switch with the SANsurfer Switch Manager application or Command Line Interface.

 Direct Ethernet connection from the management workstation to the switch

RJ-45 Ethernet connector. This requires a 10/100 Base-T cross-over cable as shown in Figure 4-2. With this method, you can manage the switch with the SANsurfer Switch Manager application or Command Line Interface.

 Serial port connection from the management workstation to the switch

RS-232 serial port connector. This requires a null modem F/F DB9 cable as shown in Figure 4-2. With this method, you can manage the switch with Command Line Interface.

4 – Installation

Installing a Switch

Indirect Ethernet

RJ-45 Connection

Direct Ethernet

RJ-45 Connection

Serial RS-232

Connection

Figure 4-2. Ethernet and Serial Cable Connections

59042-06 A 4-5

4 – Installation Installing a Switch

4.2.4

Configure the Workstation

If you plan to use the command line interface to configure and manage the switch, you must configure the workstation. This involves setting the workstation IP address for Ethernet connections, or configuring the workstation serial port. If you plan to use SANsurfer Switch Manager to manage the switch, the Configuration Wizard manages the workstation IP address for you – proceed to ”Install

SANsurfer Switch Manager” on page 4-8.

4.2.4.1

Setting the Workstation IP Address for Ethernet Connections

The default IP address of a new switch is 10.0.0.1. Many workstations must be configured to communicate with the 10.0.0 subnet.

 For a Windows workstation, do the following:

1. Choose the Start button. Choose Settings>Control Panel>Network

and Dial-Up Connections.

2. Choose Make New Connection.

3. Click the Connect to a private network through the Internet radio

button then click the Next button.

4. Enter 10.0.0.253 for the IP address.

 For a Linux or Solaris workstation, open a command window and enter the

following command where (interface) is your interface name:

iconfig (interface) ipaddress 10.0.0.253 netmask 255.255.255.0 up

4.2.4.2

Configuring the Workstation Serial Port

To configure the workstation serial port, do the following:

1. Connect a null modem F/F DB9 cable from a COM port on the management workstation to the RS-232 serial port on the switch.

2. Configure the workstation serial port according to your platform:

 For Windows:

a. Open the HyperTerminal application on a Windows platform.

Choose the Start button, select Programs, Accessories, HyperTerminal, and HyperTerminal.

b. Enter a name for the switch connection and choose an icon in the

Connection Description window. Choose the OK button.

c. Select the COM port in the Connect To window and choose the

OK button.

4-6 59042-06 A

4 – Installation

Installing a Switch

d. Enter the following COM Port settings in the COM Properties

window and choose the OK button.

 Bits per second: 9600

 Data Bits: 8

 Parity: None

 Stop Bits: 1

 Flow Control: None

 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 "pr" setting to match the workstation port to which you connected the switch.

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.

 For Solaris: Modify the /etc/remote file to include the following lines.

/dev/term/a refers to serial port a. Choose the "dv" setting to match the workstation port to which you connected to the switch.

SANbox2: \:dv=/dev/term/a:br#9600:el=^C^S^Q^U^D:ie=%$:oe=^D:

3. Proceed to ”Connect the Switch to AC Power” on page 4-13.

59042-06 A 4-7

4 – Installation Installing a Switch

4.2.5

Install SANsurfer Switch Manager

If your switch was shipped with a SANsurfer Management Suite™ Disk, use one of the following to install SANsurfer Management Suite on a Windows, Linux, or Solaris workstation.

 4.2.5.1 SANsurfer Management Suite Disk - Windows Installation

 4.2.5.2 SANsurfer Management Suite Disk - Linux Installation

 4.2.5.3 SANsurfer Management Suite Disk - Solaris Installation

If your switch was shipped with a SANsurfer Switch Manager Installation Disk, use one of the following to install SANsurfer Switch Manager on a Windows, Linux, or Solaris workstation:

 4.2.5.4 SANsurfer Switch Manager Installation Disk - Windows Installation

 4.2.5.5 SANsurfer Switch Manager Installation Disk - Linux Installation

 4.2.5.6 SANsurfer Switch Manager Installation Disk - Solaris Installation

Refer to the SANbox2-8c/16 Switch Management User’s Guide for more information about using, exiting, and uninstalling SANsurfer Management Suite and SANsurfer Switch Manager.

4.2.5.1

SANsurfer Management Suite Disk - Windows Installation

To install the SANsurfer Switch Manager application on Windows from the SANsurfer Management Suite Disk, do the following:

1. Close all programs currently running, and insert the SANsurfer Management Suite Disk into the management workstation CD-ROM drive. If the SANsurfer Management Suite start page does not open in your default browser, do the following:

a. Using Windows Explorer, double-click the drive letter which contains

the SANsurfer Management Suite Disk.

b. Locate and double-click the Start_Here.htm file to open the SANsurfer

Management Suite start page in your default browser.

2. On the SANsurfer Management Suite start page, click the SANbox Switch Software button.

3. On the SANbox® Switch Software page, scroll to the SANbox2 Series area.

4. In the Operating System column, click the Win NT/2000 link.

5. Click the SANsurfer Management Software link to open the File Download dialog.

4-8 59042-06 A

6. You have a choice of running the installation file from the CD-ROM or downloading the installation file to your hard drive. Choose one of the following:

 Open the installation file from the CD-ROM and follow the SANsurfer

Switch Manager installation instructions.

 Specify a location in which to save the

sansurfer_windows_install.exe file, and click the Save button. Double-click the saved sansurfer_windows_install.exe file and follow the installation instructions.

4.2.5.2

SANsurfer Management Suite Disk - Linux Installation

To install the SANsurfer Switch Manager application on Linux from the SANsurfer Management Suite Disk, do the following:

1. Insert the SANsurfer Management Suite Disk into the management workstation CD-ROM drive. If a file browser dialog opens showing icons for the contents of the CD-ROM, double-click the Start_Here.htm file to open the SANsurfer Management Suite start page. If a file browser does not open, double-click the CD-ROM icon to open the browser. If there is no CD-ROM icon, do the following:

4 – Installation

Installing a Switch

a. Open an xterm or other terminal window.

b. Mount the CD-ROM. From a shell prompt, enter the following

command:

mount /mnt/cdrom

c. Execute your web browser to view the Start_Here.htm document

using one of the following commands:

mozilla file:/mnt/cdrom/Start_Here.htm

netscape file:/mnt/cdrom/Start_Here.htm

d. The SANsurfer Management Suite start page opens in your browser.

2. On the SANsurfer Management Suite start page, click the SANbox Switch Software button.

3. On the SANbox Switch Software page, scroll to the SANbox2 Series area.

4. In the Operating System column, click the Linux link.

5. Click the SANsurfer Management Software link to open the File Download dialog.

6. Enter a path name to save the sansurfer_linux_install.bin file, and click the Save button.

59042-06 A 4-9

4 – Installation Installing a Switch

7. Open a terminal window for the directory in which the sansurfer_linux_install.bin file was saved, and make the file executable.

chmod +x sansurfer_linux_install.bin

8. Execute the install program:

./sansurfer_linux_install.bin

9. Follow the installation instructions.

4.2.5.3

SANsurfer Management Suite Disk - Solaris Installation

To install the SANsurfer application on Solaris from the SANsurfer Management Suite CD-ROM, do the following:

1. Insert the SANsurfer Management Suite Disk into the management workstation CD-ROM drive. If the SANsurfer Management Suite start page does not open in your default browser, do the following:

a. Right-click the Workspace Menu.

b. Select File, then select File Manager.

c. In File Manager, double-click the CD-ROM folder, and then

double-click the Sansurfer folder.

d. In the Sansurfer folder, double-click the Start_Here.htm file to open

the SANsurfer Management Suite start page in your default browser.

2. On the SANsurfer Management Suite start page, click the SANbox Switch Software button.

3. On the SANbox Switch Software page, scroll to the SANbox2 Series area.

4. In the Operating System column, click the Solaris SPARC link.

5. Click the SANsurfer Management Software link to open the Save As dialog.

6. Enter a path name to save the sansurfer_solaris_install.bin file and click the Save button.

7. Open a terminal window for the directory in which the sansurfer_solaris_install.bin file was saved, and enter the following:

chmod +x sansurfer_solaris_install.bin

8. Execute the install program:

./sansurfer_solaris_install.bin

9. Follow the installation instructions.

Note: If you download SANsurfer Management Suite from a server, be sure

the downloaded file has execute permission before installing.

4-10 59042-06 A

4 – Installation

4.2.5.4

Installing a Switch

SANsurfer Switch Manager Installation Disk - Windows Installation

To install the SANsurfer Switch Manager application on Windows from the SANsurfer Switch Manager Installation Disk, do the following:

1. Close all programs currently running, and insert the SANsurfer Switch Manager Installation Disk into the management workstation CD-ROM drive.

2. Using Windows Explorer, double-click the drive letter which contains the SANsurfer Switch Manager Installation Disk.

3. Double click the Switch_Manager folder, then double click the Windows folder.

4. Double click the executable file and follow the SANsurfer Switch Manager installation instructions.

4.2.5.5

SANsurfer Switch Manager Installation Disk - Linux Installation

To install the SANsurfer Switch Manager application on Linux from the SANsurfer Switch Manager Installation Disk, do the following:

1. Insert the SANsurfer Switch Manager Installation Disk into the management workstation CD-ROM drive. If a file browser does not open, double-click the CD-ROM icon to open the browser. Double click the Switch_Manager folder, then double click the Linux folder. If there is no CD-ROM icon, do the following:

a. Open an xterm or other terminal window.

b. Mount the CD-ROM. From a shell prompt, enter the following

command:

mount /mnt/cdrom

c. Change directory to location of the install program:

cd /mnt/cdrom/Switch_Manager/Linux

2. Using File Manager, double-click the drive letter which contains the SANsurfer Switch Manager Installation Disk.

3. Double click the Switch_Manager folder, then double click the Linux folder.

4. Double click the executable file and follow the SANsurfer Switch Manager installation instructions.

59042-06 A 4-11

4 – Installation Installing a Switch

4.2.5.6

SANsurfer Switch Manager Installation Disk - Solaris Installation

To install the SANsurfer Switch Manager application on Solaris from the SANsurfer Switch Manager Installation Disk, do the following:

1. Insert the SANsurfer Switch Manager Installation Disk into the management workstation CD-ROM drive.

2. Open a terminal window. If the disk isn’t already mounted, enter the following command:

volcheck

3. Move to the directory on the disk that contains the executable. Enter the following command:

cd cdrom/cdrom0/Switch_Manager/solaris

4. Run the executable and follow the SANsurfer Switch Manager installation instructions. Enter the following command:

pkgadd -d sol_pkg

4.2.6

Start SANsurfer Switch Manager

You can start SANsurfer Switch Manager from SANsurfer Management Suite or as a standalone application.

 To start SANsurfer Switch Manager from SANsurfer Management Suite, do

the following.

1. Start the SANsurfer Management Suite application using one of the

following methods:

 For Windows, double-click the SANsurfer shortcut, or select

SANsurfer from Start menu, depending on how you installed the SANsurfer application. From a command line, enter the following command:

<install_directory>\SANsurfer.exe

 For Linux or Solaris enter the SANsurfer command:

<install_directory>/SANsurfer

2. From the SANsurfer Management Suite home page, click the

SANsurfer Switch Manager button.

3. In the Initial Start dialog, click the Open Configuration Wizard button.

When you power up the switch, the Configuration Wizard will recognize the switch and lead you through the configuration process.

4-12 59042-06 A

4 – Installation

Installing a Switch

 To start SANsurfer Switch Manager as a standalone application, do the

following.

1. Start the SANsurfer Switch Manager using one of the following

methods:

 For Windows, double-click the SANsurfer Switch Manager

shortcut, or select SANsurfer Switch Manager from Start menu, depending on how you installed the SANsurfer Switch Manager application. From a command line, you can enter the SANsurferSwitchManager command:

<install_directory>SANsurferSwitchManager.exe

 For Linux or Solaris, enter the SANsurferSwitchManager

command:

<install_directory>SANsurferSwitchManager

 To open the SANsurfer Switch Manager web applet, enter the

switch IP address in an internet browser. If your workstation does not have the Java 2 Run Time Environment program, you will be prompted to download it.

2. In the Initial Start dialog, click the Open Configuration Wizard button.

When you power up the switch, the Configuration Wizard will recognize the switch and lead you through the configuration process.

4.2.7

Connect the Switch to AC Power

WARNING!! This product is supplied with a 3-wire power cable and plug for

the user’s safety. Use this power cable in conjunction with a properly grounded outlet to avoid electrical shock. An electrical outlet that is not correctly wired could place hazardous voltage on metal parts of the switch chassis. It is the responsibility of the customer 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 you use must meet the following requirements:

 For 125 Volt electrical service, the cable must be rated at 10 Amps and be approved by UL and CSA.

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

59042-06 A 4-13

4 – Installation Installing a Switch

AVERTISSEMENT!!

Pour la sécurité de l’utilisateur, l’appareil est livré avec un câble d’alimentation trifilaire et une fiche. Pour éviter toute secousse électrique, enficher ce câble à une prise correctement mise à la terre.Une prise électrique dont les fils sont mal branchés peut créer une tension dangereuse dans les pièces métalliques du châssis switch. Pour éviter toute secousse électrique, s’assurer que les fils sont correctement branchés et que la prise est bien mise à la terre.

Dans certains pays les prises électriques sont de modèle différent; on ne peut y enficher le câble de l’appareil. On doit donc en utiliser un autre ayant les caractéristiques suivantes:

 Alimentation 125 V: Câble pour courant nominal de 10 A, agréé LAC et CSA.

 Alimentation 250 V: Câble pour courant nominal de 10 A, conforme au H05VV-F, et agréé VDE, SEMKO et DEMKO.

WARNUNG!!

Dieses Produkt wird mit einem 3-adrigen Netzkabel mit Stecker geliefert. Dieses Kabel erfüllt die Sicherheitsanforderungen und sollte an einer vorschriftsmäßigen Schukosteckdose angeschlossen werden, um die Gefahr eines elektrischen Schlages zu vermeiden.Elektrosteckdosen, die nicht richtig verdrahtet sind, können gefährliche Hochspannung an den Metallteilen des switch-Gehäuses verursachen. Der Kunde trägt die Verantwortung für eine vorschriftsmäßige Verdrahtung und Erdung der Steckdose zur Vermeidung eines elektrischen Schlages.

In manchen Ländern ist eventuell die Verwendung eines anderen Kabels erforderlich, da der Stecker des mitgelieferten Kabels nicht in die landesüblichen Steckdosen paßt. In diesem Fall müssen Sie sich ein Kabel besorgen, daß die folgenden Anforderungen erfüllt:

 Für 125 Volt-Netze: 10 Ampere Kabel mit UL- und CSA-Zulassung.

 Für 250 Volt-Netze: 10 Ampere Kabel gemäß den Anforderungen der H05VV-F und VDE-, SEMKO- und DEMKO-Zulassung.

4-14 59042-06 A

4 – Installation

Installing a Switch

To energize the switch, connect the power cord to the AC power receptacle on the front of the switch chassis and to a grounded AC outlet. The switch responds in the following sequence:

1. The chassis LEDs (Fan Fail, Over Temperature, Heartbeat, Input Power) illuminate followed by all port Logged-In LEDs.

2. After a couple seconds, the Over Temperature, Fan Fail, and Heartbeat LEDs are extinguished while the Input Power LED remains illuminated.

3. After approximately one minute, the POST executes and all LEDs illuminate.

4. When the POST is complete, all LEDs are extinguished except the Input Power LED and the Heartbeat LED:

 The Input Power LED remains illuminated indicating that the switch

logic circuitry is receiving DC voltage. If not, contact your authorized maintenance provider.

 The Heartbeat LED indicates the results of the POST. The POST tests

the condition of firmware, memories, data-paths, and switch logic circuitry. If the Heartbeat LED blinks steadily about once per second, the POST was successful, and you can continue with the installation process. Any other blink pattern indicates that an error has occurred. Refer to ”Heartbeat LED Blink Patterns” on page 5-2 for more information about error blink patterns.

59042-06 A 4-15

4 – Installation Installing a Switch

4.2.8

Configure the Switch

You can configure the switch using the SANsurfer Switch Manager application or the command line interface. When you power up the switch, the Configuration Wizard recognizes the switch, logs in to the switch, and leads you through the configuration process. Refer to the SANbox2-8c/16 Switch Management User’s Guide for more information about configuring a switch. The Configuration wizard explains and prompts you for the following configuration information:

Temporary IP address

Temporary subnet mask

Archive template file

Switch domain ID (1–-239)

Domain ID Lock (Locked/Unlocked)

Switch name

Permanent IP address

Permanent subnet mask

Permanent gateway address

Permanent network discovery method

Date and time

Admin account password

Create a configuration archive?

To configure the switch using the command line interface, do the following:

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

 Ethernet (all platforms): Open a Telnet session with the default switch

IP address and log in to the switch with default account name and password (admin/password).

telnet 10.0.0.1 SANbox Login: admin Password: *******

 Serial – Windows: Open the HyperTerminal application on a Windows

platform.

4-16 59042-06 A

4 – Installation

Installing a Switch

a. Choose the Start button, select Programs, Accessories,

HyperTerminal, and HyperTerminal.

b. Select the connection you created earlier and choose the OK

button.

 Serial – Linux: Open a command window and enter the following

command:

minicom

 Serial – Solaris: Open a command window and enter the following

command:

tip sanbox2

2. Open an admin session and enter the Set Setup System command. Enter the values you want for switch IP address (Eth0NetworkAddress) and the network mask (Eth0NetworkMask). Refer to ”Set Setup Command” on

page B-49 for more information about this command.

SANbox2 #> admin start SANbox2 (admin) #> set setup system

4.2.9

Cable Devices to the Switch

Connect cables to the SFP transceivers and their corresponding devices, and then energize the devices. Device host bus adapters can have SFP (or SFF) transceivers or GigaBit Interface Converters (GBIC). LC-type duplex fiber optic cable connectors are designed for SFP transceivers, while SC-type connectors are designed for GBICs. Duplex cable connectors are keyed to ensure proper orientation. Choose the fiber optic cable with the connector combination that matches the device host bus adapter.

59042-06 A 4-17

4 – Installation Install Firmware

4.3

Install Firmware

The switch comes with current firmware installed. You can upgrade the firmware from the management workstation as new firmware becomes available. Firmware installation involves loading the firmware image file onto the switch, unpacking the image file, and then resetting the switch to activate the new firmware.

Note: You can load and activate version 4.1 firmware on an operating switch

without disrupting data traffic or having to re-initialize attached devices under the following conditions:

 The current firmware version is a 2.x, 3.x, or a 4.x version that

precedes the upgrade version.

 No changes are being made to switches in the fabric including

powering up, powering down, disconnecting or connecting ISLs, and switch configuration changes.

 No port in the fabric is in the diagnostic state.

 No zoning changes are being made in the fabric.

 No changes are being made to attached devices including

powering up, powering down, disconnecting, connecting, and HBA configuration changes.

Attempts to activate firmware before version 2.0 will be disruptive. Ports that are stable when the non-disruptive activation begins, then change states, will be reset. When the non-disruptive activation is complete, SANsurfer Switch Manager sessions reconnect automatically. However, Telnet sessions must be restarted manually.

You can use the SANsurfer Switch Manager application or the CLI to install new firmware:

 The SANsurfer Switch Manager application loads and unpacks the firmware

image file in one operation. Refer to ”Using SANsurfer Switch Manager to

Install Firmware” on page 4-19.

 When using the CLI on a workstation that has an FTP server, you can open

a Telnet session and load and unpack the firmware image file using the CLI Image command. Refer to ”Using the CLI to Install Firmware” on page 4-19.

 When using the CLI on a workstation without an FTP server, you must open

an FTP session through the switch to load the image file, then open a Telnet session to unpack it with the CLI Image command. Refer to ”Using FTP and

the CLI to Install Firmware” on page 4-20.

4-18 59042-06 A

4.3.1

Using SANsurfer Switch Manager to Install Firmware

To install firmware using SANsurfer Switch Manager, do the following:

1. Select a switch in the topology display and double-click to open the Faceplate display. Open the Switch menu and select Load Firmware.

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

3. In the Firmware Upload window, click the Start button to begin the loading process. When the firmware is finished loading, the Bytes Transferred field displays the number of bytes that have been transferred.

4. Click the Close button to close the Firmware Upload window.

5. SANsurfer Switch Manager will attempt a hot reset, if possible, to activate the firmware without disrupting data traffic. Click the OK button to reset the switch and activate the new firmware. During a non-disruptive activation, all Logged-In LEDs are illuminated. If a non-disruptive activation is not possible, SANsurfer Switch Manager gives you the opportunity to reset the switch and perform a disruptive activation.

4 – Installation

Install Firmware

4.3.2

Using the CLI to Install Firmware

To install firmware using the CLI when an FTP server is present on the management workstation, do the following:

1. Connect to the switch through the Ethernet or the serial port and open a Telnet session.

2. Enter the following account name and password:

SANbox2 Login:admin Password: password

3. To start an admin session, enter the following:

SANbox2 $> admin start

4. Retrieve the firmware file. The device on which the firmware file is stored must be running an FTP server. Enter the following command to retrieve the firmware file from the specified IP address:

SANbox2 (admin) #> image fetch username 10.0.0.254 firmwarefilenametoload firmwarefilenameonswitch

Connected to 10.0.0.254.

Note: If prompted for your password, enter your password (for that IP

Address) and press the Enter key.

59042-06 A 4-19

4 – Installation Install Firmware

331 Password required for username. Password: 230 User username logged in. bin 200 Type set to I. verbose Verbose mode off.

5. Enter the following command to display the list of firmware files:

SANbox2 (admin) #> image list

6. Enter the following command to install the new firmware:

SANbox2 (admin) #>image unpack filename

7. Review the conditions for a non-disruptive activation on page 4-18 and determine whether a non-disruptive activation is possible. Enter the Hotreset command to perform a non-disruptive activation. During a non-disruptive activation, all Logged-In LEDs are illuminated.

SANbox2 (admin) $>hotreset

If a non-disruptive activation is not possible, a message will prompt you to perform a disruptive activation.

SANbox2 (admin) $>reset

4.3.3

Using FTP and the CLI to Install Firmware

To install firmware using the CLI when the management workstation does not have an FTP server, do the following:

1. Connect to the switch through the Ethernet or the serial port.

2. Move to the folder or directory on the workstation that contains the new firmware image file.

3. Establish communications with the switch using the File Transfer Protocol (FTP). Enter one of the following on the command line:

>ftp xxx.xxx.xxx.xxx

>ftp switchname

where xxx.xxx.xxx.xxx is the switch IP address, and switchname is the switch name associated with the IP address.

4. Enter the following account name and password:

user:images password: images

4-20 59042-06 A

4 – Installation

Install Firmware

5. Activate binary mode and copy the firmware image file on the switch:

ftp>bin ftp>put filename

6. Wait for the transfer to complete, then close the FTP session.

xxxxx bytes sent in xx secs. ftp>quit

7. Establish communications with the switch using the CLI. Enter one of the following on the command line:

telnet xxx.xxx.xxx.xxx

telnet switchname

where xxx.xxx.xxx.xxx is the switch IP address, and switchname is the switch name associated with the IP address.

8. A Telnet window opens prompting you for a login. Enter an account name and password. The default account name and password are (admin, password).

9. Open an Admin session to acquire the necessary authority.

SANbox2 $>admin start

10. Display the list of firmware image files on the switch to confirm that the file was loaded. Refer to the ”Image Command” on page B-19 for more information.

SANbox2 (admin) $>image list

11. Unpack the firmware image file to install the new firmware in flash memory.

SANbox2 (admin) $>image unpack filename

12. Wait for the unpack to complete.

image unpack command result: Passed

13. Review the conditions for a non-disruptive activation on page 4-18 and determine whether a non-disruptive activation is possible. Enter the Hotreset command to perform a non-disruptive activation. During a non-disruptive activation, all Logged-In LEDs are illuminated.

SANbox2 (admin) $>hotreset

If a non-disruptive activation is not possible, a message will prompt you to perform a disruptive activation.

SANbox2 (admin) $>reset

59042-06 A 4-21

4 – Installation Powering Down a Switch

4.4

Powering Down a Switch

Simply unplugging the switch from the power source does not allow the switch to complete executing tasks and could lead to flash memory corruption. For this reason, open a Telnet session and use the Shutdown command to initiate an orderly shut down, then power down the switch. Refer to the ”Shutdown

Command” on page B-81.

4-22 59042-06 A

Diagnostic information about the switch is available through the chassis LEDs and the port LEDs. Diagnostic information is also available through the SANsurfer Switch Manager and CLI event logs and error displays. This section describes two types of diagnostics: Power On Self Test (POST) and chassis. POST diagnostics describe the Heartbeat LED and the port Logged-In LED indications. Chassis diagnostics cover power supply and fan diagnostics as well as over temperature conditions. This section also describes how to use maintenance mode to recover a disabled switch.

5.1

POST Diagnostics

The switch performs a series of Power On Self Tests (POST) as part of its power-up procedure. The POST diagnostic program performs the following tests:

 Checksum tests on the boot firmware in PROM and the switch firmware in

flash memory

 Internal data loopback test on all ports

 Access and integrity test on the ASIC

Section 5

Diagnostics/Troubleshooting

During the POST, the switch logs any errors encountered. Some POST errors are critical, others are not. The switch uses the Heartbeat LED and the Logged-In LED to indicate switch and port status. A critical error disables the switch so that it will not operate. A non-critical error allows the switch to operate, but disables the ports that have errors. Whether the problem is critical or not, contact your authorized maintenance provider.

If there are no errors, the Heartbeat LED blinks at a steady rate of once per second. If a critical error occurs, the Heartbeat LED will show an error blink pattern. If there are non-critical errors, the switch disables the failed ports and flashes the associated Logged-In LEDs. Refer to ”Heartbeat LED Blink Patterns”

on page 5-2 for more information about Heartbeat LED blink patterns.

59042-06 A 5-1

5 – Diagnostics/Troubleshooting POST Diagnostics

5.1.1

Heartbeat LED Blink Patterns

The Heartbeat LED indicates the operational status of the switch. When the POST completes with no errors, the Heartbeat LED blinks at steady rate of once per second. When the switch is in maintenance mode, the Heartbeat LED illuminates continuously. Refer to ”Recovering a Switch” on page 5-12 for more information about maintenance mode. All other blink patterns indicate critical errors.

The Heartbeat LED shows an error blink pattern for the following conditions:

 2 blinks - Internal Firmware Failure Blink Pattern

 3 blinks - System Error Blink Pattern

 4 blinks - Configuration File System Error Blink Pattern

5.1.1.1

Internal Firmware Failure Blink Pattern

An internal firmware failure blink pattern is 2 blinks followed by a two second pause. The 2-blink error pattern indicates that the firmware has failed, and that the switch must be reset. Momentarily press and release the Maintenance button to reset the switch.

5.1.1.2

System Error Blink Pattern

A system error blink pattern is 3 blinks followed by a two second pause. The 3-blink error pattern indicates that a POST failure or a system error has left the switch inoperable. If a system error occurs, contact your authorized maintenance provider. Momentarily press and release the Maintenance button to reset the switch.

2 seconds

5-2 59042-06 A

5.1.1.3

Configuration File System Error Blink Pattern

A configuration file system error blink pattern is 4 blinks followed by a two second pause. The 4-blink error pattern indicates that a configuration file system error has occurred, and that the configuration file must be recreated. Refer to ”Recovering a

Switch” on page 5-12 for more information.

2 seconds

To recreate the configuration file, do the following:

CAUTION! Recreating the configuration file will delete all switch configuration

settings.

5 – Diagnostics/Troubleshooting

POST Diagnostics

1. Open a Telnet session and use the Shutdown command to close activity on the switch, then power down the switch. Refer to the ”Shutdown Command”

on page B-81.

2. Place the switch in maintenance mode. Press and hold the Maintenance button for 2–4 seconds. Refer to ”Recovering a Switch” on page 5-12 for more information about placing the switch in maintenance mode.

3. Establish a Telnet session with the switch using the default IP address

10.0.0.1.

telnet 10.0.0.1

4. Enter the account name (prom) and password (prom), and press the Enter key.

Sanbox2 login: prom Password:xxxx [username@host:Itasca]% telnet 10.0.0.1 Trying 10.0.0.1... Connected to 10.0.0.1. Escape character is '^]'.

59042-06 A 5-3

5 – Diagnostics/Troubleshooting POST Diagnostics

5. The following menu is displayed. Enter "6" (Remake Filesystem) and press the Enter key to recreate the configuration file.

0) Exit

1) Image Unpack

2) Reset Network Config

3) Reset User Accounts to Default

4) Copy Log Files

5) Remove Switch Config

6) Remake Filesystem

7) Reset Switch

8) Show Firmware Versions

9) Set Active Image Option: 6

6. When the recreate process is complete, select option 7 to reset the switch and exit maintenance mode.

7. If a previously saved configuration file is available for the switch, do the following to restore the configuration file.

a. Establish communications with the switch using the File Transfer

Protocol (FTP). Enter one of the following on the command line:

>ftp xxx.xxx.xxx.xxx

>ftp switchname

where xxx.xxx.xxx.xxx is the switch IP address and switchname is the switch name associated with the IP address.

b. Enter the following account name and password:

user:images password:images

c. Activate binary mode and copy the configuration file from the

workstation to the switch. The configuration file must be named "configdata".

ftp>bin ftp>put configdata

d. Close the FTP session.

ftp>quit

5-4 59042-06 A

5 – Diagnostics/Troubleshooting

POST Diagnostics

e. Establish communications with the switch using Telnet. Enter one of

the following on the command line:

telnet xxx.xxx.xxx.xxx

telnet switchname

where xxx.xxx.xxx.xxx is the switch IP address and switchname is the switch name associated with the IP address.

f. A Telnet window opens prompting you for a login. Enter an account

name and password. The default account name and password are (admin, password).

g. Open an admin session to acquire the necessary authority.

SANbox2 $>admin start

h. Restore the configuration file. When the restore is complete, the switch

will reset.

SANbox2 (admin) $>config restore

59042-06 A 5-5

5 – Diagnostics/Troubleshooting POST Diagnostics

5.1.2

Logged-In LED Indications

Port diagnostics are indicated by the Logged-In LED for each port as shown in

Figure 5-1.

Figure 5-1. Logged-In LED

The Logged-In LED has three indications:

Logged-In LED

 Logged in - Continuous illumination.

 Logging in - Flashes at roughly once per second as shown in Figure 5-2.

 Error - Flashes at roughly twice per second as shown in Figure 5-2.

Logging In

Error

If a Logged-In LED shows an error indication, review the event browser for alarm messages regarding the affected port. You can also inspect the event log using the Show Alarm command. Pertinent alarm messages will point to one or more of the following conditions:

 E_Port isolation

 Excessive port errors

1 second

Figure 5-2. Logged-In LED Indications

5-6 59042-06 A

5.1.2.1

E_Port Isolation

A Logged-In LED error indication is often the result of E_Port isolation. An isolated E_Port is indicated by a red link in the SANsurfer Switch Manager topology display. E_Port isolation can be caused by the following:

 FL_Port is connected to another switch

 Conflicting domain IDs

 Conflicting timeout values

 Conflicting zone membership between active zone sets

Refer to the SANbox2-8c/16 Switch Management User’s Guide for information about how to change domain IDs, timeout values, and edit zoning.

Review the event browser and do the following to diagnose and correct an isolated E_Port:

1. Does the event browser show a repeating alarm about an unsupported

5 – Diagnostics/Troubleshooting

POST Diagnostics

E_Port command on the affected port?

 Yes - The port is configured as an FL_Port and connected to another

switch. Correct the port connection or the port type.

 No - Continue.

2. Display the fabric domain IDs using the Show Domains command or the Switch data tab in the SANsurfer Switch Manager topology display. Are all domain IDs in the fabric unique?

 Yes - C on ti nue .

 No - Correct the domain IDs on the offending switches using the Set

Config Switch command or the SANsurfer Switch Manager Switch Properties window. Reset the port. If the condition remains, continue.

3. Compare the RA_TOV and ED_TOV timeout values for all switches in the fabric using the Show Config Switch command or the Switch data tab of the SANsurfer Switch Manager topology display. Is each timeout value the same on every switch?

 Yes - C on ti nue .

 No - Correct the timeout values on the offending switches using the

Set Config Switch command or the SANsurfer Switch Manager Switch Properties dialog. Reset the port. If the condition remains, continue.

59042-06 A 5-7

5 – Diagnostics/Troubleshooting POST Diagnostics

4. Display the active zone set on each switch using the Zoning Active command or the Active Zoneset tab of the SANsurfer Switch Manager topology display. Compare the zone membership between the two active zone sets. Are they the same?

 Yes - Contact your authorized maintenance provider.

 No - Deactivate one of the active zone sets or edit the conflicting zones

so that their membership is the same. Reset the port. If the condition remains, contact your authorized maintenance provider.

Note: This can be caused by merging two fabrics whose active

5.1.2.2

Excessive Port Errors

The switch monitors a set of port errors and generates alarms based on user-defined sample windows and thresholds. These port errors include the following:

zone sets have two zones with the same name, but different membership.

 CRC errors

 Decode errors

 ISL connection count

 Login errors

 Logout errors

 Loss-of-signal errors

Port threshold alarm monitoring is disabled by default. Refer to the SANbox2-8c/16 Switch Management User’s Guide for information about managing port threshold alarms.

If the count for any of these errors exceeds the rising trigger for three consecutive sample windows, the switch generates an alarm and disables the affected port, changing its operational state to “down”. Port errors can be caused by the following:

 Triggers are too low or the sample window is too small

 Faulty Fibre Channel port cable

 Faulty SFP

 Faulty port

 Fault device or HBA

5-8 59042-06 A

5 – Diagnostics/Troubleshooting

POST Diagnostics

Review the event browser to determine if excessive port errors are responsible for disabling the port. Look for a message that mentions one of the monitored error types indicating that the port has been disabled, then do the following:

1. Examine the alarm configuration for the associated error using the Show Config Threshold command or the SANsurfer Switch Manager application. Refer to the ”Show Config Command” on page B-70. Refer to Ta bl e B- 5 for a list of the alarm configuration defaults. Are the thresholds and sample window correct?

 Yes - C on ti nue

 No - Correct the alarm configuration. If the condition remains, continue.

2. Reset the port, then perform an external port loopback test to validate the port and the SFP. Refer to the ”Test Command” on page B-82 or the SANbox2-8c/16 Switch Management User’s Guide for information about testing ports. Does the port pass the test?

 Yes - C on ti nue

 No - Replace the SFP and repeat the test. If the port does not pass the

test, contact your authorized maintenance provider. Otherwise continue.

3. Replace the Fibre Channel port cable. Is the problem corrected?

 Yes - C om pl ete.

 No - Continue.

4. Inspect the device to which the affected port is connected and confirm that the device and its HBA are working properly. Make repairs and corrections as needed. If the condition remains, contact your authorized maintenance provider.

59042-06 A 5-9

5 – Diagnostics/Troubleshooting Chassis Diagnostics

5.2

Chassis Diagnostics

Chassis diagnostics are indicated by the chassis LEDs as shown in Figure 5-3.

Over Temperature LED

(Amber)

Fan Fail LED

(Amber)

Figure 5-3. Chassis LEDs

The following conditions are described:

 Over Temperature LED is illuminated

 Input Power LED is extinguished

 Fan Fail LED is illuminated

5.2.1

Over Temperature LED is Illuminated

The Over Temperature LED illuminates to indicate that the switch logic circuitry is has exceeded the failure temperature threshold. The default failure temperature threshold is 70° C. You can set the failure temperature threshold using the Set Setup System command. Refer to the ”Set Setup Command” on page B-49 for more information. If the Over Temperature LED illuminates, do the following:

1. Enter the Show Setup System command to display the failure temperature threshold. The default is 70° C. Is the failure temperature threshold to low?

Input Power LED

(Green)

Heartbeat LED

(Amber)

 Yes - Use the Set Setup System command to set the failure

temperature threshold to 70° C.

 No - Continue.

5-10 59042-06 A

2. Inspect the chassis fan. Is the intake opening clear? Is the fan operating and producing air flow?

 Yes - C on ti nue .

 No - Remove any debris from fan intake and exhaust if necessary. If

the condition remains, continue.

3. Consider the ambient air temperature near the switch and clearance around the switch. Make necessary corrections. If the condition remains, contact your authorized maintenance provider.

5.2.2

Input Power LED Is Extinguished

The Input Power LED illuminates to indicate that the switch logic circuitry is receiving proper voltages. If the Input Power LED is extinguished, do the following:

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

5 – Diagnostics/Troubleshooting

Chassis Diagnostics

 Yes - Make necessary corrections or repairs. If the condition remains,

continue.

 No - Continue.

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

 Yes - C on ti nue

 No - Make necessary repairs. If the condition remains, contact your

authorized maintenance provider.

5.2.3

Fan Fail LED is Illuminated

The Fan Fail LED illuminates to indicate a malfunction with the chassis fan. If the Fan Fail LED illuminates, isolate the switch from the fabric, unplug the switch from the AC power source, and contact your authorized maintenance provider.

59042-06 A 5-11

5 – Diagnostics/Troubleshooting Recovering a Switch

5.3

Recovering a Switch

A switch can become inoperable or unmanageable for the following reasons:

 Firmware becomes corrupt

 IP address is lost

 Switch configuration becomes corrupt

 Forgotten password

In these specific cases, you can recover the switch using maintenance mode. Maintenance mode temporarily returns the switch IP address to 10.0.0.1 and provides opportunities to do the following:

 Unpack a firmware image file

 Restore the network configuration parameters to the default values

 Remove all user accounts and restore the Admin account name password to

the default.

 Copy the log file

 Restore factory defaults for all but user accounts and zoning

 Restore all switch configuration parameters to the factory default values

 Reset the switch

 Display firmware versions stored on the switch

 Select the firmware image to activate

To recover a switch, do the following:

1. Place the switch in maintenance mode. Press and hold the Maintenance button with a pointed tool for 2–4 seconds. When the Input Power LED alone is illuminated, release the button.

2. Allow one minute for the switch to complete its tests. When the switch is in maintenance mode, the Input LED will be illuminated and the Heartbeat LED will illuminate continuously. All other chassis LEDs will be extinguished.

3. Establish a Telnet session with the switch using the maintenance mode IP address 10.0.0.1.

4. Enter the maintenance mode account name and password (prom, prom), and press the Enter key.

Sanbox login: prom Password:xxxx [username@anteater:Itasca]% telnet 10.0.0.1 Trying 10.0.0.1... Connected to 10.0.0.1. Escape character is '^]'.

5-12 59042-06 A

5. The maintenance menu displays several recovery options. To select a switch recovery option, press the corresponding number (displayed in option: field) on the keyboard and press the Enter key.

These options and their use are described in the following subsections.

5.3.1

Maintenance – Exit

This option closes the current login session. To log in again, enter the maintenance mode account name and password (prom, prom). To return to normal operation, momentarily press and release the Maintenance button or power cycle the switch.

5 – Diagnostics/Troubleshooting

Recovering a Switch

0) Exit

1) Image Unpack

2) Reset Network Config

3) Reset User Accounts to Default

4) Copy Log Files

5) Remove Switch Config

6) Remake Filesystem

7) Reset Switch

8) Show Firmware Versions

9) Set Active Image Option:

5.3.2

Maintenance – Image Unpack

This option unpacks and installs new firmware when the current firmware has become corrupt. Before using this option, you must load the new firmware image file onto the switch. The steps to install new firmware using this option are as follows:

1. Place the switch in maintenance mode. Refer to the procedure for maintenance mode in ”Recovering a Switch” on page 5-12.

2. Use FTP to load a new firmware image file onto the switch. Refer to ”Using

FTP and the CLI to Install Firmware” on page 4-20. Do not unpack the

firmware image file with the Image command.

3. Select option 1 from the maintenance menu. When prompted for a file name prompt, enter the firmware image file name.

Image filename: filename Unpacking ’filename’, please wait... Unpackage successful.

4. Select option 7 to reset the switch and exit maintenance mode.

59042-06 A 5-13

5 – Diagnostics/Troubleshooting Recovering a Switch

5.3.3

Maintenance – Reset Network Config

This option resets the network properties to the factory default values and saves them on the switch. Refer to Table B-8 for the default network configuration values.

5.3.4

Maintenance – Reset User Accounts to Default

This option restores the password for the Admin account name to the default (password) and removes all other user accounts from the switch.

5.3.5

Maintenance – Copy Log Files

This option copies all log file buffers to a file on the switch named logfile. You can use FTP to download this file to the management workstation. You must download the logfile before resetting the switch.

5.3.6

Maintenance – Remove Switch Config

This option deletes all configurations from the switch except for the default configuration. This restores switch configuration parameters to the factory defaults except for user accounts and zoning. Refer to Table B-3 though Tab le B -8 for the factory default values.

5.3.7

Maintenance – Remake Filesystem

In the event of sudden loss of power, it is possible that the switch configuration may become corrupt. The file system on which the configuration is stored must be re-created. This option resets the switch to the factory default values including user accounts and zoning. Refer to Table B-3 though Tab le B -8 for the factory default values.

CAUTION!

5.3.8

If you choose the Remake Filesystem option, you will lose all changes made to the fabric configuration that involve that switch, such as password and zoning changes. You must then reconfigure the portions of the fabric that involve the switch.

Maintenance – Reset Switch

This option closes the Telnet session, exits maintenance mode and reboots the switch using the current switch configuration. All unpacked firmware image files that reside on the switch are deleted.

5-14 59042-06 A

5.3.9

Maintenance – Show Firmware Versions

This option displays the image numbers and firmware versions that are stored on the switch.

5.3.10

Maintenance – Set Active Image

This option specifies the firmware version to be used when the switch returns to normal operation. A message reminds you of the pending firmware version and gives you an opportunity to change it by selecting the other image number.

5 – Diagnostics/Troubleshooting

Recovering a Switch

59042-06 A 5-15

5 – Diagnostics/Troubleshooting Recovering a Switch

Notes

5-16 59042-06 A

This appendix contains the specifications for the SANbox2-8c Fibre Channel switch. Refer to Section 2 General Description for the location of all connections, switches, controls, and components.

A.1

Fabric Specifications

Fibre Channel Protocols ................. FC-PH Rev. 4.3

Appendix A

Specifications

FC-PH-2 FC-PH-3 FC-AL Rev 4.5 FC-AL-2 Rev 7.0 FC-FLA FC-GS-3 FC-FG FC-Tape FC-VI FC-SW-2 Fibre Channel Element MIB RFC 2837 Fibre Alliance MIB Version 4.0

Fibre Channel Classes of Service .. Classes 2 and 3

Modes of Operation ........................ Fibre Channel Classes 2 and 3,

connectionless

Port Types....................................... F_Port

FL_Port E_Port G_Port GL_Port

Port Characteristics ........................ All ports are auto-discovering and

self-configuring.

Number of Fibre Channel Ports...... 8 ports per chassis

Scalability........................................ Maximum 239 switches depending on

configuration

Maximum User Ports ...................... > 475,000 ports depending on

configuration

59042-06 A A-1

A – Specifications Maintainability

Buffer Credits.................................. 12 buffer credits per port

Media Type ..................................... Small Form Pluggable (SFP) optical

Fabric Port Speed........................... 1.0625 or 2.125-Gbps

Maximum Frame Size..................... 2148 bytes (2112 byte payload)

System Processor........................... 266 MHz Geode® processor

Fabric Latency (best case) ............. <0.4 µsec.

Fabric Point-to-Point Bandwidth ..... 1.0625 or 2.125-Gbps, full duplex

Fabric Aggregate Bandwidth .......... 16 Gb/s for a single switch

A.2

Maintainability

transceivers. Hot swappable. 3.3 Volts.

Diagnostics ..................................... Power On Self Test (POST) tests all

functional components except SFP transceivers. Port tests include online, internal, and external tests.

User Interface ................................. LED indicators

A-2 59042-06 A

A.3

Fabric Management

Management Methods.................... SANsurfer Switch Manager Graphical User

Maintenance Connection................ RS-232 connector; null modem F/F DB9

Ethernet Connection....................... RJ-45 connector; 10/100 BASE-T cable

Switch Agent................................... Allows a network management station to

A – Specifications

Fabric Management

Interface Application Programming Interface Command Line Interface GS-3 Management Server SNMP FTP

cable

obtain configuration values, traffic information, and failure data pertaining to the Fibre Channels using SNMP through the Ethernet interface.

A.4

Dimensions

A.5

Electrical

Width...............................................

Height .............................................

Depth ..............................................

Weight............................................. 8.5 lbs (3.86 Kg)

Operating voltage ........................... 90 to 137 Vac; 47 to 63 Hz

Power source loading ..................... 1.0 Amps maximum at 90 to 137 Vac

Heat Output (maximum) 70 watts

Circuit Protection ............................ Internally fused

8.5” (216 mm), 19 inch rack mount

1.75” (44 mm) (1U)

20.0” (508 mm)

180 to 264 Vac; 47 to 63 Hz

0.45 Amps maximum at 180 to 264 Vac

59042-06 A A-3

A – Specifications Environmental

A.6

Environmental

Temperature

 Operating ..................................

 Non-operating ...........................

Humidity

 Operating ..................................

 Non-operating ...........................

Altitude

 Operating ..................................

 Non-operating ...........................

5 to 50°C (41 to 122°F)

-40 to 65°C (-40 to 149°F)

15% to 80%, non-condensing 25% to 90%, non-condensing

0 to 3048m (0 to 10,000 feet) 0 to 15,240m (0 to 50,000 feet)

Vibration

 Operating ..................................

 Non-operating ...........................

Shock

 Operating ..................................

 Non-operating ...........................

Air flow............................................ Front-to-back or back-to-front, by model

IEC 68-2 5-500 Hz, random, 0.21 G rms, 10 minutes 5-500 Hz, random, 2.09 G rms, 10 minutes

IEC 68-2 4 g, 11ms, 20 repetitions 30g, 292 ips, 3 repetitions, 3 axis

A-4 59042-06 A

A.7

Regulatory Certifications

Safety Standards ............................ UL1950, CSA 22.2 No. 950, EN60950

Emissions Standards ...................... FCC Part 15B Class A

Voltage Fluctuations ....................... EN 61000-3-3

Harmonics....................................... EN 61000-3-2

Immunity ......................................... EN 55024:1998

Marking........................................... FCC Part 15,UL (United States), cUL

A – Specifications

Regulatory Certifications

ICES-03 Issue 3

VCCI Class A ITE BSMI Class A CISPR 22, Class A EN 55022, Class A

(Canada), TUV, VCCI, BSMI, CE

SANmark® SCD 3001, 3002, 3010, 3020

59042-06 A A-5

A – Specifications Regulatory Certifications

Notes

A-6 59042-06 A

Command Line Interface

The command line interface (CLI) enables you to perform a variety of fabric and switch management tasks through an Ethernet or a serial port connection. This section describes the following:

 Logging on to a switch

 User accounts

 Working with switch configurations

 Commands

B.1

Logging On to a Switch

To log on to a switch using Telnet, open a command line window on the workstation and enter the Telnet command followed by the switch IP address:

# telnet ip_address

A Telnet window opens prompting you for a login. Enter an account name and password.

Appendix B

To log on to a switch through the serial port, configure the workstation port with the following settings:

 9600 baud

 8-bit character

 1 stop bit

 No parity

Enter an account name and password when prompted.

B.2

User Accounts

Switches come from the factory with the following user account already defined:

This user account provides full access to the switch and its configuration. After planning your fabric management needs and creating your own user accounts, consider changing the password for this account. Refer to ”Commands” on

page B-5 for more information about authority levels. Refer to the ”User Command” on page B-86 for information about creating user accounts.

Account name: admin Password: password Authority: Admin

59042-06 A B-1

B – Command Line Interface Working with Switch Configurations

Note: A switch supports a combined maximum of 19 logins or sessions

reserved as follows:

 4 logins or sessions for internal applications such as management

server and SNMP

 9 high priority Telnet sessions

 6 logins or sessions for SANsurfer Switch Manager inband and

out-of-band logins, Application Programming Interface (API) inband and out-of-band logins, and Telnet logins. Additional logins will be refused.

B.3

Working with Switch Configurations

Successful management of switches and fabrics with the command line interface depends on the effective use of switch configurations. Modifying configurations, backing up configurations, and restoring configurations are key switch management tasks.

B.3.1

Modifying a Configuration

A switch supports up to 10 configurations including the default configuration. Each switch configuration contains switch, port, port threshold alarm, and zoning configuration components.

The Show Switch command displays the name of the active configuration. A configuration name can have up to 31 characters excluding the pound symbol (#), semicolon (;), and comma (,). By editing the latest configuration and saving the results under a new name, you can create a history of configuration changes. Use the Config List command to display the names of the configurations stored on the switch

SANbox2 #> config list Current list of configurations

----------------------------- default config_10132003

To modify a switch configuration you must open an Admin session with the Admin Start command. An Admin session prevents other accounts from making changes at the same time either through Telnet or SANsurfer Switch Manager. You must also open a Config Edit session with the Config Edit command and indicate which configuration you want to modify. If you do not specify a configuration name the active configuration is assumed. The Config Edit session provides access to the

B-2 59042-06 A

B – Command Line Interface

Working with Switch Configurations

Set Config commands with which you make modifications to the port, switch, port threshold alarm, or zoning configuration components as shown:

SANbox2 #> admin start SANbox2 (admin) #> config edit default The config named default is being edited. SANbox2 (admin-config)#> set config port . . . SANbox2 (admin-config)#> set config switch . . . SANbox2 (admin-config)#> set config threshold . . . SANbox2 (admin-config)#> set config zoning . . .

The Config Save command saves the changes you made during the Config Edit session. In this case, changes to the configuration named Default are being saved to a new configuration named config_10132003. However, the new configuration does not take effect until you activate it with the Config Activate command as shown:

SANbox2 (admin-config)#> config save config_10132003 SANbox2 (admin-config)#> config activate config_10132003 SANbox2 (admin-config)#> admin end SANbox2 #>

The Admin End command releases the Admin session for other administrators when you are done making changes to the switch.

B.3.2

Backing up and Restoring Switch Configurations

Backing up and restoring a configuration is useful to protect your work or for use as a template in configuring other switches. The Config Backup command creates a file on the switch, named configdata. This file can be used to restore a switch only with the command line interface; it cannot be used to restore a switch using SANsurfer Switch Manager.

SANbox2 #> admin start SANbox2 (admin) #> config backup

The configdata file contains all of the switch configuration information including the following:

 All named switch configurations including the default configuration. This

includes port, switch, port threshold alarm, and zoning configuration components.

 All SNMP and network information defined with the Set Setup command.

 The zoning database included all zone sets, zones, and aliases

59042-06 A B-3

B – Command Line Interface Working with Switch Configurations

You use FTP to download the configdata file to your workstation for safe keeping and to upload the file back to the switch for the restore function. To download the configdata file, open an FTP session on the switch and login with the account name images and password images. Transfer the file in binary mode with the Get command as shown:

>ftp ip_address user:images password: images

ftp>bin ftp>get configdata xxxxx bytes sent in xx secs. ftp>quit

You should rename the configdata file on your workstation with the switch name and date, config_switch_169_10112003, for example.

The restore operation begins with FTP to upload the configuration file from the workstation to the switch, then finishes with a Telnet session and the Config Restore command. To upload the configuration file, config_switch_169_10112003 in this case, open and FTP session with account name images and password images. Transfer the file in binary mode with the Put command as shown:

ftp ip_address user:images password: images ftp> bin ftp> put config_switch_169_10112003 configdata ftp>quit

The restore process replaces all configuration information on the switch and afterwards the switch is automatically reset. If the restore process changes the IP address, all management sessions are terminated. Use the Set Setup System command to return the IP configuration to the values you want. Refer to the ”Set

Setup Command” on page B-49. To restore the switch, open a Telnet session,

then enter the Config Restore command from within an Admin session as shown:

SANbox2 #> admin start SANbox2 (admin) #> config restore The switch will be reset after restoring the configuration. Please confirm (y/n): [n] y

B-4 59042-06 A

B.4

Commands

B – Command Line Interface

Commands

The command syntax is as follows:

command

key

word keyword [value] keyword [value1] [value2]

The Command is followed by one or more keywords. Consider the following rules and conventions:

 Commands and keywords are case insensitive.

 Required keyword values appear in standard font: [value]. Optional values

are shown in italics: [value].

 Underlined portions of the keyword in the command format indicate the

abbreviated form that can be used. For example the Del abbreviated Del.

ete keyword can be

The command-line completion feature makes entering and repeating commands easier. Ta bl e B-1 describes the command-line completion keystrokes.

Table B-1. Command-Line Completion

Keystroke Effect

Tab Completes the command line. Enter at least one character and

press the tab key to complete the command line. If more than one possibility exists, press the Tab key again to display all possibilities.

Up Arrow Scrolls backward through the list of previously entered commands.

Down Arrow Scrolls forward through the list of previously entered commands.

Control-A Moves the cursor to the beginning of the command line

Control-E Moves the cursor to the end of the command line.

59042-06 A B-5

B – Command Line Interface Commands

The command set performs monitoring and configuration tasks. Commands related to monitoring tasks are available to all account names. Commands related to configuration tasks are available only within an admin session. An account must have Admin authority to enter the Admin Start command, which opens an admin session. Refer to the ”Admin Command” on page B-7.

The commands and their page numbers are listed in Table B-2.

Monitoring Commands Configuration Command

Table B-2. Commands Listed by Authority Level

Help History Ping Ps Quit Show Show Config Show Log Show Perf Show Setup Uptime Whoami

(B-16) (B-17) (B-22) (B-23) (B-24) (B-55) (B-70) (B-73) (B-76) (B-78) (B-85) (B-89)

Admin (B-7)

Admin Session Commands

Alias

Config

Date Fallback Hardreset Hotreset Image Lip Passwd Reset

Set Set Config Set Log Set Port

Set Setup Shutdown Te st

1 2

User

Zone Zoneset Zoning

Some keywords do not require an Admin session.

Some keywords can be executed only by the Admin account name.

(B-8) (B-10) (B-13) (B-14) (B-15) (B-18) (B-19) (B-20) (B-21) (B-25) (B-31) (B-33) (B-44) (B-47) (B-49) (B-81) (B-82) (B-86) (B-90) (B-94) (B-96)

B-6 59042-06 A

Admin Command

Opens and closes an Admin session. The Admin session provides commands that change the fabric and switch configurations. Only one Admin session can be open on the switch at any time. An inactive Admin session will time out after a period of time which can be changed using the Set Setup System command. Refer to the ”Set Setup Command” on page B-49.

Authority Admin

Syntax admin

start (or begin) end (or stop) cancel

Keywords start (or begin)

Opens the admin session.

end (or stop)

Closes the admin session. The Hardreset, Hotreset, Logout, Shutdown, and Reset Switch commands will also end an admin session.

B – Command Line Interface

Admin Command

cancel

Terminates an Admin session opened by another user. Use this keyword with care because it terminates the Admin session without warning the other user and without saving pending changes.

Notes Closing a Telnet window during an admin session does not release the session. In

this case, you must either wait for the admin session to time out, or use the Admin Cancel command.

Examples The following example shows how to open and close an Admin session:

SANbox2 #> admin start

SANbox2 (admin) #>

. . .

SANbox2 (admin) #> admin end SANbox2 #>

59042-06 A B-7

B – Command Line Interface Alias Command

Alias Command

Creates a named set of ports/devices. Aliases make it easier to assign a set of ports/devices to many zones. An alias can not have a zone or another alias as a member.

Authority Admin session for all keywords except List and Members

Syntax alias

add [alias] [member_list] copy [alias_source] [alias_destination] create [alias] del

ete [alias] list members [alias] remove [alias] [member_list] rename [alias_old] [alias_new]

Keywords add [alias] [member_list]

Specifies one or more ports/devices given by [member_list] to add to the alias named [alias]. Use a <space> to delimit ports/devices in [member_list]. An alias can have a maximum of 2000 members. A port/device in [member_list] can have any of the following formats:

 Domain ID and port number pair (Domain ID, Port Number). Domain IDs can

be 1–-239; port numbers can be 0–-255.

 6-character hexadecimal device Fibre Channel address (hex)

 16-character hexadecimal worldwide port name (WWPN) with the format

xx:xx:xx:xx:xx:xx:xx:xx.

The application verifies that the [alias] format is correct, but does not validate that such a port/device exists.

copy [alias_source] [alias_destination]

Creates a new alias named [alias_destination] and copies the membership into it from the alias given by [alias_source].

create [alias]

Creates an alias with the name given by [alias]. An alias name must begin with a letter and be no longer than 64 characters. Valid characters are 0-9, A-Z, a-z, _, $, ^, and -. The zoning database supports a maximum of 256 aliases.

del

ete [alias]

Deletes the specified alias given by [alias] from the zoning database. If the alias is a member of the active zone set, the alias will not be removed from the active zone set until the active zone set is deactivated.

list

Displays a list of all aliases. This keyword does not require an admin session.

B-8 59042-06 A

Q-Logic 2-8C User Manual

Specifications and Main Features

Frequently Asked Questions

User Manual

Table of Contents

Figures

Tables

Intended Audience

Related Materials

New in this Release

Safety Notices

Sicherheitshinweise

Notes informatives relatives à la sécurité

Communications Statements

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

VCCI Class A Statement

BSMI Class A Statement

Laser Safety Information

Electrostatic Discharge Sensitivity (ESDS) Precautions

Accessible Parts

Pièces Accessibles

Zugängliche Teile

General Public License

Preamble

Terms And Conditions For Copying, Distribution And Modification

How to Apply These Terms to Your New Programs

Technical Support

Availability

Training

Contact Information

Chassis Controls and LEDs

Maintenance Button

Resetting a Switch

Placing the Switch in Maintenance Mode

Chassis LEDs

Over Temperature LED (Amber)

Fan Fail LED (Amber)

Heartbeat LED (Amber)

Input Power LED (Green)

Fibre Channel Ports

Port LEDs

Port Logged-In LED

Port Activity LED

Small Form-Factor Pluggable (SFP) Transceivers

Port Types

Ethernet Port

Serial Port

Power Supply and Fan

Switch Management

SANsurfer Switch Manager

SANsurfer Switch Manager Web Applet

Command Line Interface

SANsurfer Switch Manager Application Programming Interface

Simple Network Management Protocol

File Transfer Protocol

Devices

Device Access

Soft Zones

Access Control List Hard Zones

Performance

Distance

Bandwidth

Latency

Multiple Chassis Fabrics

Optimizing Device Performance

Domain ID, Principal Priority, and Domain ID Lock

Common Topologies

Cascade Topology

Mesh Topology

Multistage Topology

Fabric Security

User Account Security

Fabric Services

Fabric Management

Site Requirements

Fabric Management Workstation

Switch Power Requirements