HP McDATA 4Gb SAN Switch Installation Manual

McDATA® 4Gb SAN Switch for HP p-Class

BladeSystem

installation guide

Part number: AA–RW1XB–TE Second edition: December 2005

Legal and notice information

Hewlett-Packard Company makes no warranty of any kind with regard to this material, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Hewlett-Packard shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance, or use of this material.

This document contains proprietary information, which is protected by copyright. No part of this document may be photocopied, reproduced, or translated into another language without the prior written consent of Hewlett-Packard. The information is provided “as is” without warranty of any kind and is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.

Java is a registered trademark of Sun Microsystems, Inc.

Linux is a registered trademark of Linus Torvalds.

McDATA is a registered trademark of McDATA Corporation.

Microsoft, Windows, Windows XP, and Windows 2000/2003 are U.S. registered trademarks of Microsoft Corporation.

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

PowerPC is registered trademark of International Business Machines Corporation.

Red Hat is a registered trademark of Red Hat Software Inc.Adobe® and Acrobat® are trademarks of Adobe Systems Incorporated.

SANtegrity Enhanced is a trademark of McDATA Corporation.

McDATA Web Server is a trademark of McDATA Corporation.

McDATA® 4Gb SAN Switch for HP p-Class BladeSystem installation guide

About this guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Intended audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Related documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Document conventions and symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

HP technical support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

HP-authorized reseller. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Helpful web sites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

1 General description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Switch LEDs and controls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Switch LEDs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

System Fault LED (amber) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Heartbeat LED (green) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Power LED (green). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Maintenance button . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Resetting a switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Placing the switch in maintenance mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

FC ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

External port LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Port Logged-in LED (green) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Port Activity LED (green). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Transceivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Port types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Ethernet port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Switch management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

McDATA Web Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

McDATA Element Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Command Line Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Simple Network Management Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

File Transfer Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

2 Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Device access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Performance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Distance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Bandwidth . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Latency. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Multiple switch fabrics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Optimizing device performance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Domain ID, principal priority, and domain ID lock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Switch services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Fabric security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Connection security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Device security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

User account security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Fabric management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

3 Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Preparing for installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Fabric management workstation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Environmental conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Upgrading the Interconnect switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

McDATA® 4Gb SAN Switch for HP p-Class BladeSystem installation guide 3

Installing the SAN Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Connect the management workstation to the switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Start McDATA Web Server or McDATA Element Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Configure the switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Cable devices to the switch. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Installing firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Using McDATA Web Server or McDATA Element Manager to install firmware . . . . . . . . . . . . . . . . . . 32

Using the CLI to install firmware. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Installing PFE keys. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

4 Diagnostics and troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Switch diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Power LED is extinguished . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

System Fault LED is illuminated . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Power On Self Test diagnostics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Heartbeat LED blink patterns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Internal firmware failure blink pattern . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

System error blink pattern . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Configuration file system error blink pattern . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Over temperature blink pattern . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Logged-in LED diagnostics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

E_Port isolation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Excessive port errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Recovering a switch using maintenance mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Exiting maintenance mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Unpacking the firmware image file in maintenance mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Resetting the network configuration in maintenance mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Restoring factory user accounts in maintenance mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Copying log files in maintenance mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Removing the switch configuration in maintenance mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Recreating the switch file system in maintenance mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Resetting the switch in maintenance mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Updating the Boot Loader in maintenance mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

A Regulatory compliance and safety . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Regulatory compliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Federal Communications Commission notice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Class A equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Class B equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Declaration of conformity for products marked with the FCC logo, United States only . . . . . . . . . . . 46

Modifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Regulatory compliance identification numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Laser device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Laser safety warning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Certification and classification information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Laser product label . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

International notices and statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Canadian notice (avis Canadien) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Class A equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Class B equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

European Union notice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

BSMI notice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Japanese notice. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Korean notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Safety . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Power cords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Japanese power cord notice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Electrostatic discharge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Preventing electrostatic damage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Grounding methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Waste Electrical and Electronic Equipment directive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Czechoslovakian notice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Danish notice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Dutch notice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

English notice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Estonian notice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Finnish notice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

French notice. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

German notice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Greek notice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Hungarian notice. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Italian notice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Latvian notice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Lithuanian notice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Polish notice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Portuguese notice. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Slovakian notice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Slovenian notice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Spanish notice. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Swedish notice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

B Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

FC specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Maintainability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Fabric management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Electrical . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Environmental . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Regulatory certifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

C Factory configuration defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Factory switch configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Factory port configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Factory port threshold alarm configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Factory zoning configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Factory SNMP configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Factory RADIUS configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Factory switch service configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Factory system configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Factory security configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Figures

1 McDATA 4Gb SAN Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

2 Front panel switch controls and LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

3 Switch LEDs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

4 FC ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

5 External port LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

6 Ethernet port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

7 Installing the SAN Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

8 Ethernet cable connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

9 Installing SFPs in the SAN Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

10 Features Licenses dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

McDATA® 4Gb SAN Switch for HP p-Class BladeSystem installation guide 5

11 Add License Key dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

12 Switch LED diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

13 Logged-in LED diagnostics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

14 Class 1 laser product label . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Tables

1 Document conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

2 Zoning limits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

3 Port-to-port latency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

4 Management workstation requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

5 FC specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

6 Maintainability specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

7 Fabric management specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

8 Dimenensional specifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

9 Electrical specifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

10 Environmental specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

11 Regulatory certifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

12 Factory switch configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

13 Factory port configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

14 Factory port threshold alarm configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

15 Factory zoning configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

16 Factory SNMP configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

17 Factory RADIUS configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

18 Factory switch service configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

19 Factory system configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

20 Factory security configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

About this guide

This guide provides information about:

• Becoming acquainted with the switch features and capabilities

• Installing and configuring a McDATA

• Planning a fabric including devices, device access, performance, multiple chassis fabrics, switch

services, fabric security, and fabric management.

• Diagnosing and troubleshooting switch problems

Intended audience

This guide is intended for individuals who are responsible for installing and servicing storage area network equipment.

Prerequisites

Prerequisites for installing or using this product include:

• Knowledge of operating systems

• Knowledge of related hardware/software

Document conventions and symbols

Table 1 Document conventions

Convention Element

Medium blue text: Figure 1 Cross-reference links and e-mail addresses

Medium blue, underlined text (

http://www.hp.com)

Bold font

Web site addresses

• Key names

• Text typed into a GUI element, such as into a box

• GUI elements that are clicked or selected, such as menu and list

items, buttons, and check boxes

Italics font Text emphasis

Monospace font

Monospace, italic font

• File and directory names

• System output

• Code

• Text typed at the command-line

• Code variables

• Command-line variables

Monospace, bold font Emphasis of file and directory names, system output, code, and text

typed at the command line

WARNING! Indicates that failure to follow directions could result in bodily harm or death.

CAUTION: Indicates that failure to follow directions could result in damage to equipment or data.

IMPORTANT: Provides clarifying information or specific instructions.

NOTE: Provides additional information.

TIP: Provides helpful hints and shortcuts.

HP technical support

Telephone numbers for worldwide technical support are listed on the HP support web site:

http://www.hp.com/support/

Collect the following information before calling:

• Technical support registration number (if applicable)

• Product serial numbers

• Product model names and numbers

• Applicable error messages and information on what has been done prior to the occurrence of a

problem

• Operating system type and revision level

• Detailed, specific questions

For continuous quality improvement, calls may be recorded or monitored.

HP strongly recommends that customers sign up online using the Subscriber's choice web site:

http://www.hp.com/go/e-updates

• Subscribing to this service provides you with e-mail updates on the latest product enhancements, newest

versions of drivers, and firmware documentation updates as well as instant access to numerous other product resources.

• After signing up, you can quickly locate your products by selecting Business support and then Storage

under Product Category.

HP-authorized reseller

For the name of your nearest HP-authorized reseller:

• In the United States, call 1-800-282-6672.

• Elsewhere, visit the HP web site: http://www.hp.com

telephone numbers.

Helpful web sites

For other product information, see the following HP web sites:

• http://www.hp.com

• http://www.hp.com/go/storage

• http://www.hp.com/support/

• http://www.docs.hp.com

• http://h71028.www7.hp.com/enterprise/cache/80316-0-0-0-121.html

. Then click Contact HP to find locations and

McDATA® 4Gb SAN Switch for HP p-Class BladeSystem installation guide 9

1 General description

This section describes the features and capabilities of the McDATA 4Gb SAN Switch in an HP p-Class BladeSystem server blade chassis. The following topics are described:

• Switch LEDs and controls, page 12

• FC ports, page 14

• Ethernet port, page 16

• Switch management, page 16

Fabrics are managed with the McDATA Web Server™ switch management application, the McDATA Element Manager™ switch management application, and the Command Line Interface (CLI). With the corresponding Product Feature Enablement (PFE) key, you can manage a single switch through the High Availability Fabric Manager™ (HAFM) application using McDATA Element Manager™. See the McDATA 4Gb SAN Switch for HP p-Class BladeSystem user guide for information about using the McDATA Web Server application, McDATA Element Manager application, and the CLI.

Figure 1 McDATA 4Gb SAN Switch

McDATA® 4Gb SAN Switch for HP p-Class BladeSystem installation guide 11

Switch LEDs and controls

The switch LEDs provide information about the switch’s operational status. These LEDs include the Identifier LED, System Fault LED, and Power LED. The Maintenance button shown in Figure 2 is the only front panel switch control and is used to reset a switch or to recover a disabled switch.

Maintenance

button

Figure 2 Front panel switch controls and LEDs

Switch LEDs

The switch LEDs shown in Figure 3 provide status information about switch operation. See ”External port

LEDs” on page 14 for information about port LEDs.

Figure 3 Switch LEDs

Power LED

Heartbeat LED

System Fault LED

12 General description

System Fault LED (amber)

The System Fault LED illuminates to indicate an over temperature condition or a POST error. Also illuminated on an internal firmware error (heartbeat blink 2), voltage fault, or corrupt config error (heartbeat blink 4).

Heartbeat LED (green)

The Heartbeat LED indicates the status of the internal switch processor and the results of the 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. See ”Heartbeat LED blink patterns” on page 36 for more information about Heartbeat LED blink patterns.

Power LED (green)

The 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. When the switch is in maintenance mode, this LED is extinguished.

Maintenance button

The Maintenance button shown in Figure 2 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. See ”Recovering a switch using maintenance mode” on page 41 for more information about using maintenance mode. The Maintenance button can be used if the user forgets the switch IP address or admin password.

Resetting a switch

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

• All switch LEDs will illuminate, then the System Fault LED extinguishes, leaving only the Power LED

illuminated.

• After approximately 1 minute, the POST begins.

• When the POST is complete, the Power LED is illuminated.

Placing the switch in maintenance mode

To place the switch in maintenance mode, perform the following procedure:

1. Isolate the switch from the fabric.

2. Press and hold the Maintenance button with a pointed tool for 10 seconds. The maintenance mode

firmware initializes.

To exit Maintenance mode and return to normal operation, perform the following procedure:

1. Press and release the Maintenance button momentarily to reset the switch.

McDATA® 4Gb SAN Switch for HP p-Class BladeSystem installation guide 13

FC ports

The switch has 2 external FC ports through which to connect to devices or other switches, and 8 internal ports connecting to the server backplane. Each of the external FC ports is served by a Small Form-Factor Pluggable (SFP) optical transceiver and is capable of 1-Gbps, 2-Gbps, or 4-Gbps transmission. SFPs are hot-pluggable. External ports can self-discover both the port type and transmission speed when connected to public devices or other switches. The internal ports operate at 2-Gbps.

The external ports are named Ext:0, Ext:9 and are labeled 0 and 9 as shown in Figure 4. The external port LEDs provide port login and activity status information. Internal ports are named Int:1–Int:8 and numbered 1–8. The ports 1–8 correspond to server blade slots 1–8 in the server chassis.

External ports

Figure 4 FC ports

External port LEDs

Each external port has its own Logged-in LED and Activity LED as shown in Figure 5.

Activity LEDs

Figure 5 External port LEDs

Logged-in LEDs

14 General description

Port Logged-in LED (green)

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 connection is broken the Logged-in LED will be extinguished. If an error occurs that disables the port or the port is taken offline or down, the Logged-in LED will flash. See ”Logged-in LED diagnostics” on page 38 for more information about the Logged-in LED.

Port Activity LED (green)

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.

Transceivers

Switches support SFP optical transceivers for the FC ports. A transceiver converts electrical signals to and from optical laser signals to transmit and receive data. Duplex fiber optic cables plug into the transceivers which then connect to the devices. An FC port is capable of transmitting at 1-Gbps, 2-Gbps, or 4-Gbps; however, the transceiver must also be capable of delivering at these rates.

The SFP transceivers are hot pluggable. This means that you can remove or install a transceiver while the switch is operating without harming the switch or the transceiver. However, communication with the connected device will be interrupted.

Port types

Switches support auto-discovering fabric ports (F_Port, FL_Port, E_Port). Switches come from the factory with external ports (0, 9) configured as GL_Ports, and internal ports (1—8) configured as FL_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 (point-to-point), or as an E_Port when connected to another switch. 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.

• A G_Port self-configures as an F_Port when connected to a single public device (point-to-point), or as

an E_Port when connected to another switch.

• An FL_Port supports a loop of up to 32 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 (point-to-point).

• An F_Port supports a single public device (point-to-point).

E_Ports enable you to expand the fabric by connecting switches with other switches. Switches self-discover all inter-switch connections. See ”Multiple switch fabrics” on page 21 for more information about multiple chassis fabrics. See the McDATA 4Gb SAN Switch for HP p-Class BladeSystem user guide for information about defining port types.

McDATA® 4Gb SAN Switch for HP p-Class BladeSystem installation guide 15

Ethernet port

The Ethernet port shown in Figure 6 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

a Linux Ethernet connection using the McDATA Web Server, CLI, or SNMP.

The Ethernet port has two LEDs: the Status LED (green) and the Activity LED (green). 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.

workstation that is used to configure and manage the switch. You can manage the switch over an

Ethernet port

Activity LED (green)

Status LED (green)

Figure 6 Ethernet port

Switch management

The switch supports the following management tools:

• McDATA Web Server, page 16

• McDATA Element Manager, page 17

• Command Line Interface, page 17

• Simple Network Management Protocol, page 17

• File Transfer Protocol, page 17

McDATA Web Server

McDATA Web Server is a graphical user interface (GUI) that provides both fabric and switch module management functions. Because McDATA Web Server resides in the switch firmware, no installation is needed. You can run one instance of the McDATA Web Server at a time by opening the switch IP address with an internet browser. McDATA Web Server is best used to manage a single fabric consisting only of McDATA 4Gb SAN switches. See ”Fabric management workstation” on page 27 for workstation requirements.

16 General description

McDATA Element Manager

IMPORTANT: McDATA Element Manager is available only with the Element Manager PFE key. See

”Installing PFE keys” on page 34 for more information about installing a PFE key. To obtain the McDATA 4Gb SAN Switch serial number and PFE key, follow the step-by-step instructions on the "firmware feature entitlement request certificate" for the PFE key. One of the license key retrieval options is via the web:

www.webkey.external.hp.com

McDATA Element Manager is a graphical user interface for managing a single McDATA 4Gb SAN Switch through HAFM. HAFM and McDATA Element Manager are essential tools for managing multiple fabrics or a single fabric consisting of McDATA 4Gb SAN Switches and McDATA M-series switches.

Command Line Interface

The CLI provides monitoring and configuration functions by which the administrator can manage switch. The CLI is available by Telnet over an Ethernet connection. See the McDATA 4Gb SAN Switch for HP p-Class BladeSystem user guide for more information.

Simple Network Management Protocol

Simple Network Management Protocol (SNMP) provides monitoring and trap functions for the fabric. The switch 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.

File Transfer Protocol

File Transfer Protocol (FTP) provides the CLI for exchanging files between the switch and the management workstation. These files include firmware image files, configuration files, and log files. See the McDATA 4Gb SAN Switch for HP p-Class BladeSystem user guide for an example of using FTP to transfer configuration backup files.

McDATA® 4Gb SAN Switch for HP p-Class BladeSystem installation guide 17

18 General description

2 Planning

Consider the following when planning a fabric:

• Devices, page 19

• Device access, page 19

• Performance, page 20

• Multiple switch fabrics, page 21

• Switch services, page 23

• Fabric security, page 24

• Fabric management, page 26

Devices

When planning a fabric, consider the number of public devices and the anticipated demand. This will determine the number of ports that are needed and in turn the number of switches. See the HP StorageWorks SAN Design Guide for more information.

For the two external FC ports, the switch uses SFP optical transceivers, but the device you are connecting to these ports may not. Consider whether the FC ports on the device use SFP or Gigabit Interface Converters (GBIC) transceivers, and choose fiber optic cables accordingly. Use LC-type cable connectors for SFP transceivers and SC-type cable connectors for GBIC transceivers. Also consider the transmission speed compatibility of your devices, HBAs, switches, and SFPs.

Consider the distribution of targets and initiators. An F_Port supports a single public device. An FL_Port can support up to 32 public devices in an arbitrated loop.

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

• Separate devices that have no need to communicate with other devices in the fabric or have classified

data.

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

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, or by device worldwide name (WWN). Devices can communicate only with devices within the same zone. The switch supports one zone set; that is, the active zone set. The active zone set contains the zones that determine the current fabric zoning.

Zoning divides the fabric for purposes of controlling device discovery. Devices in the same zone automatically discover and communicate freely with all other members of the same zone. The following rules apply to zones:

• Zones that include members from multiple switches need not include the ports of the inter-switch links.

• Zones can overlap; that is, a port can be a member of more than one zone.

• Membership can be defined by domain ID and port number, or port worldwide name.

• Zoning supports FL_Ports and F_Ports.

McDATA® 4Gb SAN Switch for HP p-Class BladeSystem installation guide 19

A zoning database is maintained on each switch consisting of the active zone set, all zones, and all zone members. Table 2 describes the zoning database limits. See the McDATA 4Gb SAN Switch for HP p-Class BladeSystem user guide for more information.

Table 2 Zoning limits

Limit Description

MaxZoneSets Maximum number of zone sets (1).

MaxZones Maximum number of zones (2047).

MaxTotalMembers Maximum number of zone members (10,000) that can be

MaxZonesInZoneSets Maximum number of zones that are components of the

MaxMembersPerZone Maximum number of members in a zone (10,000)

Performance

The switch supports class 2 and class 3 FC service with a maximum frame size of 2148 bytes at transmission rates of 1-Gbps, 2-Gbps, or 4-Gbps. An external port adapts its transmission speed to match that of the device to which it is connected prior to login when the connected device powers up. Related performance characteristics include the following:

stored in the switch’s zoning database.

active zone set (2047), excluding the orphan zone set, that can be stored in the switch’s zoning database.

• Distance, page 20

• Bandwidth, page 20

• Latency, page 21

Distance

Consider the physical distribution of devices and switches in the fabric. Choose SFP transceivers that are compatible with the cable type, distance, FC revision level, and the device. See ”Specifications” on page 57 for more information about cable types and transceivers.

Each FC port is supported by a data buffer with an 8-credit capacity; that is, 8 maximum sized frames. For fibre optic cables, this enables full bandwidth over the following approximate distances:

• 13 kilometers at 1-Gbps (0.6 credits/Km)

• 6 kilometers at 2-Gbps (1.2 credits/Km)

• 3 kilometers at 4-Gbps (2.4 credits/km)

Beyond these distances, however, there is some loss of efficiency because the transmitting port must wait for an R_RDY response before sending the next frame.

Bandwidth

Bandwidth is a measure of the volume of data that can be transmitted at a given transmission rate. An FC port can transmit or receive at nominal rates of 1-Gbps, 2-Gbps, or 4-Gbps depending on the device to which it is connected. This corresponds to actual bandwidth values of 106 MB, 212 MB, and 425 MB. Multiple source ports can transmit to the same destination port if the destination bandwidth is greater than or equal to the combined source bandwidth. For example, two 1-Gbps source ports can transmit to one 2-Gbps destination port. Similarly, one source port can feed multiple destination ports if the combined destination bandwidth is greater than or equal to the source bandwidth.

In multiple switch fabrics, each link between switches contributes 106, 212, or 425 MB of bandwidth between those switches depending on the speed of the link. When additional bandwidth is needed between devices, increase the number of links between the connecting switches.

20 Planning

Latency

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

Table 3 Port-to-port latency

Destination Rate

Gbps 1 2 4

1 < 0.6 µsec < 0.8 µsec

2 < 0.5 µsec < 0.4 µsec < 0.4 µsec

4 < 0.4 µsec < 0.3 µsec < 0.3 µsec

Source Rate

1. Based on minimum frame size of 36 bytes. Latency increases for larger frame sizes.

Multiple switch 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 can automatically resolve domain ID conflicts. Because the FC ports are self-configuring, you can connect switches together in a wide variety of topologies. See the SAN Design Reference Guide for topology guidelines.

Optimizing device performance

< 0.8 µsec

When choosing a topology for a multiple switch 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.

The switch provides the lowest latency of any product in its class. See ”Performance” on page 20 for information about latency. However, the highest performance is achieved on FC 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

McDATA® 4Gb SAN Switch for HP p-Class BladeSystem installation guide 21

Domain ID, principal priority, and domain ID lock

The following switch configuration settings affect multiple switch fabrics:

• Domain ID

• Principal priority

• Domain ID lock

The domain ID is a unique number that identifies each switch in a fabric. The valid domain ID range depends on the interoperability mode:

• When the interoperability mode is Standard, the domain ID can be 97–127.

• When the interoperability mode is McDATA Fabric Mode, the domain ID can be 1–31.

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–Default) or prevents (True) the reassignment of the domain ID on that switch. Switches come from the factory with the domain ID set to 97, the domain ID lock set to False, and the principal priority set to 254. See the McDATA 4Gb SAN Switch for HP p-Class BladeSystem user guide for information about changing the domain ID and domain ID lock using McDATA Web Server or McDATA Element Manager. See the Set Config command in the McDATA 4Gb SAN Switch for HP p-Class BladeSystem user guide for information about changing the default domain ID, domain ID lock, and principal priority parameters.

An unresolved domain ID conflict means that the switch with the higher WWN will isolate as a separate fabric, and the Logged-in LEDs 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. It is recommended to assign sequential domain IDs to switches to avoid domain ID conflicts and to keep port addressing the same.

NOTE: Domain ID reassignment is not reflected in zoning that is defined by domain ID/port number pair.

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 McDATA Web Server, McDATA Element Manager, or the Set Config command with the Switch operand. HP recommeds defining zone members by WWN.

22 Planning

Switch services

You can configure your switch to suit the demands of your environment by enabling or disabling a variety of switch services. Familiarize yourself with the following switch services and determine which ones you need:

• Telnet—Provides for the management of the switch over a Telnet connection. Disabling this service is not

recommended. The default is enabled.

• Secure Shell (SSH)—Provides for secure remote connections to the switch using SSH. Your workstation

must also use an SSH client. The default is disabled.

• Switch Management—Provides for out-of-band management of the switch with Telnet, McDATA Web

Server, and CIM. The switch can be managed by SNMP supported management programs. SNMP is supported both inband and out-of-band. If this service is disabled, the switch can only be managed inband. The default is enabled.

• Inband Management—Provides for the management of the switch over FC using the McDATA Web

Server, SNMP, or management server. If you disable inband management and out of band management, you can no longer communicate with that switch. The default is enabled. Access to an entry switch via ethernet is required.

• Secure Socket Layer (SSL)—Provides for secure SSL connections for the McDATA Web Server, McDATA

Element Manager, and CIM. To enable secure SSL connections, you must first synchronize the date and time on the switch and workstation. Enabling SSL automatically creates a security certificate on the switch. The default is disabled.

• Embedded GUI—Provides for access to both McDATA Web Server and McDATA Element Manager.

McDATA Web Server enables you to point at a switch with an internet browser and run switch management application through the browser. McDATA Element Manager enables you to manage the switch through HAFM. The default is enabled.

• SNMP—Provides for the management of the switch through third-party applications that use the SNMP.

Security consists of a read community string and a write community string that serve as passwords that control read and write access to the switch. These strings are set at the factory to these well-known defaults and should be changed if SNMP is to be enabled. Otherwise, you risk unwanted access to the switch. The default is enabled.

• Network Time Protocol (NTP)—Provides for the synchronizing of switch and workstation dates and times

with an external NTP server. This helps to prevent invalid SSL certificates and timestamp confusion in the event log. The default is disabled.

• Common Information Module (CIM)—Provides for the management of the switch through third-party

applications that use CIM. The default is enabled.

• File Transfer Protocol (FTP)—Provides for transferring files rapidly between the workstation and the

switch. The default is enabled.

• Management Server (MS)—Enables or disables the management of the switch through third-party

applications that are compliant with the FC GS-3 Management Server Specification. The default is disabled.

McDATA® 4Gb SAN Switch for HP p-Class BladeSystem installation guide 23

+ 51 hidden pages

HP McDATA 4Gb SAN Switch Installation Manual

Specifications and Main Features

Frequently Asked Questions

User Manual

Contents

Intended audience

Prerequisites

Related documentation

Document conventions and symbols

Table 1 Document conventions

HP technical support

HP-authorized reseller

Helpful web sites

1 General description

Figure 1 McDATA 4Gb SAN Switch

Switch LEDs and controls

Figure 2 Front panel switch controls and LEDs

Switch LEDs

Figure 3 Switch LEDs

System Fault LED (amber)

Heartbeat LED (green)

Power LED (green)

Maintenance button

Resetting a switch

Placing the switch in maintenance mode

FC ports

Figure 4 FC ports

External port LEDs

Figure 5 External port LEDs

Port Logged-in LED (green)

Port Activity LED (green)

Transceivers

Port types

Ethernet port

Figure 6 Ethernet port

Switch management

McDATA Web Server

McDATA Element Manager

Command Line Interface

Simple Network Management Protocol

File Transfer Protocol

2 Planning

Devices

Device access

Table 2 Zoning limits

Performance

Distance

Bandwidth

Latency

Table 3 Port-to-port latency

Multiple switch fabrics

Optimizing device performance

Domain ID, principal priority, and domain ID lock

Switch services