HP Brocade 4Gb SAN Switch for HP BladeSystem p-Class User Manual

HP StorageWorks

Fabric OS 5.0.0 procedures

user guide

Part number:AA–RW1PA–TE First edition: May 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.

Windows is a U.S. registered trademarks of Microsoft Corporation.

UNIX® is a registered trademark of The Open Group.

Linux® is a U.S. registered trademark of Linus Torvalds.

Java

is a U.S. trademark of Sun Microsystems, Inc.

Fabric OS 5.0.0 procedures user guide

About this guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Intended audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Related documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Document conventions and symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

HP technical support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

HP Storage web site. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

HP authorized reseller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

1 Introducing Fabric OS CLI procedures . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Changes to this guide for OS v5.0.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Brocade 4Gb SAN Switch for HP p-Class BladeSystem. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

About procedural differences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Scope and references . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

About the CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Help information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Displaying command help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Displaying additional help topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

2 Performing basic configuration tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Connecting to the CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Setting the IP address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Setting the default account passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Setting the date and time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Maintaining licensed features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Customizing the switch name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Customizing the chassis name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Disabling and enabling a switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Disabling and enabling a port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Activating Ports on Demand . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Making basic connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Connecting to devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Connecting to other switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Working with domain IDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Linking through a gateway. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Checking status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Tracking and controlling switch changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

3 Configuring standard security features . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Ensuring network security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Configuring the telnet interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Blocking listeners . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Accessing switches and fabrics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Creating and maintaining user-defined accounts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

To display account information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

To create a user-defined account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

To delete a user-defined account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

To change account parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

To recover user-defined accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Changing an account password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Setting up RADIUS AAA service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Fabric OS 5.0.0 procedures user guide 3

Configuring the RADIUS server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Windows 2000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Configuring the switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Enabling and disabling local authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Configuring for the SSL protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Browser and Javatm support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Summary of SSL procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Choosing a CA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Generating a public/private key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Generating and storing a CSR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Obtaining certificates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Installing a switch certificate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Activating a switch certificate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Configuring the browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Installing a root certificate to the Java Plug-in. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Displaying and deleting certificates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Troubleshooting certificates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Configuring for SNMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Setting the security level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Using the snmpconfig command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Using legacy commands for SNMPv1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Configuring secure file copy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Setting the boot PROM password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

With a recovery string . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Without a recovery string . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Recovering forgotten passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

4 Maintaining configurations and firmware . . . . . . . . . . . . . . . . . . . . . . . . 75

Maintaining configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Displaying configuration settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Backing up a configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Restoring a configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

Downloading configurations across a fabric . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Editing configuration files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Printing hard copies of switch information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Maintaining firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Obtaining and unzipping firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Checking connected switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

About the download process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

Effects of firmware changes on accounts and passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

Considerations for downgrading firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

Upgrading HP StorageWorks SAN switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

Summary of the upgrade process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

SAN Switch upgrade procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

Upgrading the Core Switch 2/64 and the SAN Director 2/128 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Summary of the upgrade process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Core Switch 2/64 and SAN Director 2/128 upgrade procedure. . . . . . . . . . . . . . . . . . . . . . . . . 84

Troubleshooting firmware downloads . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

5 Configuring the Core Switch 2/64 and the SAN Director 2/128. . . . . . . . 89

Identifying ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

By slot and port number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

By port area ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

Basic card management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

Powering port cards on and off . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

Disabling and enabling cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

Conserving power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

Setting chassis configurations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

4Contents

Obtaining slot information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

Configuring a new SAN Director 2/128 with two domains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Converting an installed SAN Director 2/128 to support two domains . . . . . . . . . . . . . . . . . . . . . . . . 94

Combining Core Switch 2/64 and SAN Director 2/128 cards in one chassis . . . . . . . . . . . . . . . . . . 95

Setting the card beacon mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

6 Routing traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

About routing policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

Specifying the routing policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

Assigning a static route . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

Specifying frame order delivery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

Using dynamic load sharing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

Viewing routing path information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

Viewing routing information along a path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

7 Administering extended fabrics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

About extended link buffer allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

SAN Switch 2/8V, SAN Switch 2/16V, SAN Switch 2/32, Core Switch 2/64, and SAN Director 2/128 . 107

SAN Switch 4/32 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

Fabric considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

Choosing an extended ISL mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

Configuring an extended ISL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

Trunking over distance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

8 Administering ISL trunking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

Standard trunking criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

Fabric considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

Initializing trunking on ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

Monitoring traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

Enabling and disabling ISL trunking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116

Setting port speeds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

Displaying trunking information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

Trunking over extended fabrics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

Troubleshooting trunking problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120

Listing link characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120

Recognizing buffer underallocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120

9 Administering advanced zoning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

Zoning terminology. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

Zoning concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

Zone types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

Zone objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

Zone aliases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

Zone configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

Zoning enforcement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

Software-enforced zoning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

Hardware-enforced zoning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

Rules for configuring zones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130

Creating and managing zone aliases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

Creating and maintaining zones. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133

Creating and modifying zoning configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134

Managing zoning configurations in a fabric . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

Adding a new switch or fabric . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

Splitting a fabric . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139

Using zoning to administer security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139

Resolving zone conflicts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140

Fabric OS 5.0.0 procedures user guide 5

10 Administering advanced performance monitoring . . . . . . . . . . . . . . . . . 143

Displaying and clearing the CRC error count . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

Monitoring end-to-end performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

Adding end-to-end monitors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146

Setting a mask for end-to-end monitors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148

Deleting end-to-end monitors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149

Monitoring filter-based performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149

Adding standard filter-based monitors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150

Adding custom filter-based monitors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150

Deleting filter-based monitors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152

Monitoring ISL performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152

Monitoring trunks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152

Displaying monitor counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153

Clearing monitor counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155

Saving and restoring monitor configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156

Collecting performance data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156

11 Configuring the distributed management server . . . . . . . . . . . . . . . . . . . 157

Enabling and disabling the platform services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157

Controlling access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158

Configuring the server database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161

Controlling topology discovery. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162

12 Working with diagnostic features . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165

Viewing power-on self test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165

Viewing switch status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166

Viewing port information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168

Viewing equipment status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171

Viewing the system message log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172

Viewing the port log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173

Configuring for syslogd . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175

Configuring the Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176

Configuring the switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176

Viewing and saving diagnostic information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177

Setting up automatic trace dump transfers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178

13 Troubleshooting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181

Most common problem areas. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182

Gathering information for technical support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182

Analyzing connection problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184

Restoring a segmented fabric . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186

Correcting zoning setup issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187

Recognizing MQ-WRITE errors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189

Correcting I2C bus errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190

Correcting device login issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191

Identifying media-related issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194

Correcting link failures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196

Correcting marginal links. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198

Inaccurate information in the system message log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200

Recognizing the port initialization and FCP auto discovery process. . . . . . . . . . . . . . . . . . . . . . . . . . . . 200

A Configuring the PID format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203

About PIDs and PID binding. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203

Summary of PID formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204

Impact of changing the fabric PID format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204

Host reboots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205

Static PID mapping errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205

Changes to configuration data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205

6Contents

Selecting a PID format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206

Evaluating the fabric . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207

Planning the update procedure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209

Online update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209

Offline update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210

Hybrid update. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210

Changing to core PID format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211

Changing to extended edge PID format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212

Performing PID format changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213

Basic procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214

HP–UX procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215

AIX procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216

Swapping port area IDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217

B Configuring interoperability mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219

Vendor switch requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219

HP StorageWorks switch requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219

Supported HP StorageWorks features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220

Unsupported HP StorageWorks features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220

Configuration recommendations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221

Configuration restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221

Zoning restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221

Zone name restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222

Enabling and disabling interoperability mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222

C Using Remote Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225

D Understanding legacy password behavior. . . . . . . . . . . . . . . . . . . . . . . 229

Password management information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229

Password prompting behaviors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232

Password migration during firmware changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233

Password recovery options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235

E Zone merging scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237

F Upgrading firmware in single mode . . . . . . . . . . . . . . . . . . . . . . . . . . . 239

Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267

Figures

1 Hardware-enforced non-overlapping zones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129

2 Hardware-enforced overlapping zones. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129

3 Zoning with hardware assist (mixed port and WWN zones) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130

4 Overlapping hardware-enforced zoning with soft porting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130

5 Setting end-to-end monitors on a port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147

6 Proper placement of end-to-end performance monitors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147

7 Mask positions for end-to-end monitors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148

8 Configure command on a switch running Fabric OS 3.1.2

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213

9 Configure command on a switch running Fabric OS 4.2.0 and later . . . . . . . . . . . . . . . . . . . . . . . 213

Tables

1 Document conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

2 Brocade 4Gb SAN Switch for HP p-Class BladeSystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

3 Conversion from UTC to local time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Fabric OS 5.0.0 procedures user guide 7

4 Standard ISL modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

5 Blocked listener applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

6 Access details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

7 SSL certificate files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

8 Recommended CAs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

9 Commands for displaying and deleting SSL certificates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

10 SSL messages and actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

11 Recommended firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

12 Effect of firmware on accounts and passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

13 Supported options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

14 Header fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

15 Extended ISL modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

16 SAN Switch 2/8V, 2/16V, 2/32, Core Switch 2/64, and SAN Director 2/128 . . . . . . . . . . . . . . . 109

17 SAN Switch 4/32 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

18 Types of zoning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

19 Approaches to fabric-based zoning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .125

20 Enforcing hardware zoning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128

21 Zoning database limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

22 Considerations for zoning architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140

23 Advanced performance monitoring commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144

24 Commands to add filter-based monitors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .150

25 Predefined values at offset 0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

26 Error summary description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170

27 Commands for port log management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174

28 Fabric OS to UNIX message severities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .176

29 Common troubleshooting problems and tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182

30 Types of zone discrepancies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187

31 Commands for debugging zoning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188

32 Component test descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194

33 Switch component tests. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195

34 SwitchShow output and suggested action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198

35 Effects of PID format changes on configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205

36 PID format recommendations for adding new switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207

37 PID format and management interface names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211

38 Earliest Fabric OS versions for extended edge PID format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212

39 Account and password characteristics matrix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229

40 Password prompting matrix. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232

41 Password migration behavior during firmware upgrade and downgrade . . . . . . . . . . . . . . . . . . . . . 233

42 Password recovery options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235

43 Zone merging scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237

8Contents

About this guide

This document provides information to assist fabric administrators in using the web-based graphical user interface to monitor and modify their HP StorageWorks switch fabrics.

This preface discusses the following topics:

• Intended audience, page 9

• Related documentation, page 9

• Document conventions and symbols, page 10

• HP technical support, page 11

Intended audience

This book is intended for use by those responsible for monitoring and modifying their HP StorageWorks switch fabric.

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 • Key names

Italics

font Text emphasis

Monospace font • File and directory names

Monospace italic font • Code variables

Monospace, bold font Emphasis of file and directory names, system

Web site addresses

• 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

• System output

• Code

• Text typed at the command-line

• Command-line variables

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.

10 About this guide

HP technical support

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

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

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

Obtain the following information before calling:

• Technical support registration number (if applicable)

• Product serial numbers

• Product model names and numbers

• Applicable error messages

• Operating system type and revision level

• Detailed, specific questions

HP Storage web site

The HP web site has the latest information on this product, as well as the latest drivers. Access storage at:

http://www.hp.com/country/us/eng/prodserv/storage .html

or solution.

. From this web site, select the country of origin.

. From this web site, select the appropriate product

HP authorized reseller

For the name of your nearest HP authorized reseller:

• In the United States, call 1-800-345-1518.

• Elsewhere, visit http://www.hp.com

and click Contact HP to find locations and telephone numbers.

Fabric OS 5.0.0 procedures user guide 11

12 About this guide

1 Introducing Fabric OS CLI procedures

This guide contains procedures for configuring and managing an HP StorageWorks Storage Area Network (SAN) using the Fabric OS Command Line Interface (CLI). This chapter consists of the following sections:

• Changes to this guide for OS v5.0.0, page 13

• About procedural differences, page 15

• Scope and references, page 16

• About the CLI, page 16

• Help information, page 17

The guide applies to the following HP products:

• HP StorageWorks Switches: 1-GB switches, SAN Switch 2/8V, SAN Switch 2/16V, SAN Switch

2/32, and SAN Switch 4/32.

These switches contain a fixed number of ports (they are called fixed-port switches). The SAN Switch 4/32 allows you to license and activate extra fixed ports with the Ports on Demand feature.

• Core Switch 2/64 and SAN Director 2/128.

These switches can contain a variable number of ports, which you install by plugging port cards into the director chassis.

Changes to this guide for OS v5.0.0

The following changes are new to v5.0.0 and are not included elsewhere in this guide.

• Add “Brocade 4Gb SAN Switch for HP p-Class BladeSystem ” everywhere that the HP StorageWorks

SAN Switch 4/32 is mentioned, except as specified in the following sections.

• On page 43, in the section “Creating and maintaining a user-defined account,” change the following definition item:

-r rolename Specifies the role: either admin or user in nonsecure mode; admin, user, or nonfcsadmin in secure mode.

to:

-r rolename Specifies the role: either admin or user in nonsecure mode or admin, user, switchAdmin, or nonfcsadmin in secure mode.

• On page 44, in the section “To change account parameters,” change the following definition item:

-r rolename Specifies the role: either admin or user in nonsecure mode; admin, user, or nonfcsadmin in secure mode.

to:

-r rolename Specifies the role: either admin or user in nonsecure mode; admin, user, switchAdmin, or nonfcsadmin in secure mode.

Fabric OS 5.0.0 procedures user guide 13

• On page 107, in the section “SAN Switch 4/32” add the following:

For the Brocade 4Gb SAN Switch for HP p-Class BladeSystem, each port group contains four ports and buffer credits are shared among all ports on the switch.

14 Introducing Fabric OS CLI procedures

• On page 108, in the section “Choosing an extended ISL mode,” add the following:

Brocade 4Gb SAN Switch for HP p-Class BladeSystem

The number of ports that can be configured at various distances is summarized in Table 2.

Table 2 Brocade 4Gb SAN Switch for HP p-Class BladeSystem

Speed (Gbit/sec)

128615411088

2143775544

4 71.5 38.5 27.5 22

• On page 146, in the section “Adding end-to-end monitors,” change the following paragraph:

The HP StorageWorks SAN Switch 2/8V, SAN Switch 2/16V, SAN Switch 2/32, Core Switch 2/64, SAN Director 2/128, allow up to eight end-to-end monitors allow up to eight end-to-end monitors.

to:

The HP StorageWorks SAN Switch 2/8V, SAN Switch 2/16V, SAN Switch 2/32, Core Switch 2/64, SAN Director 2/128, and Brocade 4Gb SAN Switch for HP p-Class BladeSystem allow up to eight end-to-end monitors.

Number of ports allowed at distance (km)

1 2 3 4

• On page 149, in the section “Monitoring filter-based performance,” change the following

paragraph:

For HP StorageWorks SAN Switch 2/8V, SAN Switch 2/16V, SAN Switch 2/32, Core Switch 2/64, and SAN Director 2/128, the maximum number of filters is eight per port, in any combination of standard filters and user-defined filters.

to:

For HP StorageWorks SAN Switch 2/8V, SAN Switch 2/16V, SAN Switch 2/32, Core Switch 2/64, SAN Director 2/128, and Brocade 4Gb SAN Switch for HP p-Class BladeSystem, the maximum number of filters is eight per port, in any combination of standard filters and user-defined filters.

• On page 219, in the section “HP StorageWorks switch requirements,” add the following:

Brocade 4Gb SAN Switch for HP p-Class BladeSystem running Fabric OS 5.0.0 or later.

About procedural differences

As a result of the differences between fixed-port and variable-port devices, procedures sometimes differ between HP StorageWorks switch models. Also, because the domain architecture of the Core Switch 2/64 differs from that of the SAN Director 2/128, there are sometimes procedural differences between these two.

When procedures or parts of procedures apply to some models but not others, this guide identifies the specifics for each model. For example, a number of procedures that apply only to variable-port devices are found in ”Configuring the Core Switch 2/64 and the SAN Director 2/128” on page 89. Procedures that apply only to the SAN Switch 4/32 are labeled as such.

Fabric OS 5.0.0 procedures user guide 15

NOTE: When command examples in this guide show user input enclosed in quotation marks, the

quotation marks are required for versions earlier than v4.0.0. They are optional in later versions, unless specifically called for in the procedures.

Scope and references

Although many different software and hardware configurations are tested and supported by HP, documenting all possible configurations and scenarios is beyond the scope of this document. In some cases, earlier releases are highlighted to present considerations for interoperating with them.

The hardware reference manuals for HP StorageWorks products describe how to power up devices and set their IP addresses. After the IP address is set, you can use the CLI procedures contained in this guide.

This guide provides only the level of detail required to perform the procedures. If you need more information about the commands used in the procedures, refer to online help or to the HP StorageWorks Fabric OS 4.x command reference guide.

There are several access methods that you can use to configure a switch. These are listed with their respective documents:

• For Advanced Web Tools procedures, refer to the HP StorageWorks Fabric OS 4.x Advanced Web

Tools user guide.

• For Fabric Manager procedures, refer to the HP StorageWorks Fabric OS 4.4.x Fabric Manager user

guide.

• For third-party application procedures, refer to the third-party API documentation.

About the CLI

Fabric OS CLI is the complete fabric management tool for HP SANs that enables you to:

• Access the full range of Fabric OS features, based on license keys.

• Configure, monitor, dynamically provision, and manage every aspect of the SAN.

• Configure and manage the HP fabric on multiple efficient levels.

• Identify, isolate, and manage SAN events across every switch in the fabric.

• Manage switch licenses.

• Perform fabric stamping.

To manage a switch using telnet, SNMP, and HP Advanced Web Tools, the switch must be connected to a network through the switch Ethernet port (out of band) or from the Fibre Channel (in band). The switch must be configured with an IP address to allow for the network connection. Refer to the hardware manual for your switch for information on physically connecting to the switch.

You can access switches from different connections, such as Advanced Web Tools, CLI, and API. When these connections are simultaneous, changes from one connection may not be updated to the other, and some modifications may be lost. When simultaneous connections are used, make sure that you do not overwrite the work of another connection.

In a mixed fabric containing switches running various Fabric OS versions, you should use the latest-model switches running the most recent release for the primary management tasks. The principal management

16 Introducing Fabric OS CLI procedures

access should be set to the core switches in the fabric. For example, to run Secure Fabric OS, use the latest-model switch as the primary FCS, the location to perform zoning tasks, and the time server.

A number of management tasks are designed to make fabric-level changes; for example, zoning commands make changes that affect the entire fabric. When executing fabric-level configuration tasks, allow time for the changes to propagate across the fabric before executing any subsequent tasks. For a large fabric, it may be take a few minutes.

Help information

Each Fabric OS command provides Help information that explains the command function, its possible operands, its level in the command hierarchy, and additional pertinent information.

Displaying command help

To display help information:

1. Connect to the switch and log in as admin.

2. To display a list of all command help topics, issue the help command with no arguments.

3. To display help for a specific command, enter help command, where command is the name of the

command for which you need information, as shown in the following example:

switch:admin> help configure

Administrative Commands configure(1m)

NAME

configure - change system configuration settings

SYNOPSIS

configure

AVAILABILITY

admin

DESCRIPTION

This command changes some system configuration settings,

including:

o Arbitrated loop settings

o Switch fabric settings

o System services settings

o Virtual channel settings

(output truncated)

Displaying additional help topics

The following commands provide help files for specific topics:

diagHelp Diagnostic help information

fwHelp Fabric Watch help information

licenseHelp License help information

perfHelp Performance Monitoring help information

routeHelp Routing help information

trackChangesHelp Track Changes help information

zoneHelp Zoning help information

Fabric OS 5.0.0 procedures user guide 17

18 Introducing Fabric OS CLI procedures

2 Performing basic configuration tasks

This chapter contains procedures for performing basic switch configuration tasks using the Fabric OS CLI and contains the following sections:

• Connecting to the CLI, page 19

• Setting the IP address, page 21

• Setting the default account passwords, page 21

• Setting the date and time, page 22

• Maintaining licensed features, page 25

• Customizing the switch name, page 27

• Customizing the chassis name, page 28

• Disabling and enabling a switch, page 28

• Disabling and enabling a port, page 29

• Activating Ports on Demand, page 30

• Making basic connections, page 30

• Working with domain IDs, page 31

• Linking through a gateway, page 32

• Checking status, page 33

• Tracking and controlling switch changes, page 35

Connecting to the CLI

You can connect to the CLI either through a telnet connection or through the serial port. To connect with telnet:

1. Verify that the switch is connected to the IP network through the RJ-45 Ethernet port.

Switches in the fabric that are not connected via Ethernet can be managed through switches that are using IP over Fibre Channel. The embedded port must have an assigned IP address.

2. Open a telnet connection to the switch.

The login prompt is displayed when the telnet connection finds the switch in the network.

For the Core Switch 2/64 and SAN Director 2/128, enter the logical switch name (sw0 or sw1).

3. Enter the account ID (defaults are user or admin) at the login prompt.

4. Enter the password. The default password is password.

If you have not changed the system passwords from the default, you are prompted to change them.

5. Enter the new system passwords, or press Ctrl+c to skip the password prompts.

Fabric OS 5.0.0 procedures user guide 19

6. Verify that the login was successful. The prompt displays the switch name and user ID to which you

are connected:

password: xxxxxxx

switch:admin>

Consider the following for telnet connections:

• Never change the IP address of the switch while two telnet sessions are active; if you do, your next

attempt to log in fails. To recover, gain access to the switch by one of these methods:

• Use Advanced Web Tools and perform a fast boot. When the switch comes up, the telnet quota is cleared. For instructions on performing a fast boot with Advanced Web Tools, refer to the HP StorageWorks Fabric OS 4.x Advanced Web Tools user guide.

• If you have the required privileges, you can connect through the serial port, log in as root, and use operating system commands to identify and kill the telnet processes without disrupting the fabric.

• For admin level accounts, Fabric OS limits the number of simultaneous telnet sessions per switch to

two. For more details on session limits, see ”Configuring the telnet interface” on page 40 and ”Creating and maintaining user-defined accounts” on page 43.

To connect through the serial port:

1. Connect the serial cable to the serial port on the switch and to an RS-232 serial port on

the workstation.

If the serial port on the workstation is RJ-45 instead of RS-232, remove the adapter on the end of the serial cable and insert the exposed RJ-45 connector into the RJ-45 serial port on the workstation.

2. Open a terminal emulator application (such as HyperTerminal on a PC, or TERM, TIP, or Kermit in a

UNIX® environment), and configure the application as follows:

• In a Windows® environment:

Parameter Value Bits per second 9600 Databits 8 Parity None Stop bits 1 Flow control None

• In a UNIX environment, enter the following string at the prompt: tip /dev/ttyb -9600

If ttyb is already in use, you can use ttya (enter tip /dev/ttya -9600).

Consider the following for serial connections:

• Some procedures require that you connect through the serial port; for example, setting the IP address

or setting the boot PROM password.

• If secure mode is enabled, connect through the serial port of the primary FCS switch.

• For the Core Switch 2/64 and SAN Director 2/128, you can connect to CP0 or CP1 using either of

the two serial ports.

20 Performing basic configuration tasks

Setting the IP address

You must connect through the serial port to set the IP address (see ”To connect through the serial port:” on page 20). After connecting, use the ipaddrset command to set the IP address.

CAUTION: The use of IP address 0.0.0.0 is not supported. Do not use this address.

Fabric OS v2.6.0, v3.1.0, and v4.0.0 supports Classless Inter-Domain Routing (CIDR).

Setting the default account passwords

For each logical switch (domain), there are admin and user default access accounts. These accounts designate different levels of authorization—called roles—for using the system:

• The admin level is for administrative use.

• The user level is for nonadministrative use, such as monitoring system activity.

Two accounts—factory and root—are reserved for development and manufacturing. You can change their passwords, which is optional, but you should not use these accounts under normal circumstances.

For the SAN Switch 2/8V, SAN Switch 2/16V, SAN Switch 2/32, SAN Switch 4/32, and SAN Director 2/128 (default configuration with one domain), there is one set of default access accounts.

For the Core Switch 2/64 and SAN Director 2/128, configured with two domains, each logical switch has its own set of default access accounts. The default account names and passwords are the same for both of the logical switches.

You can also create up to 15 additional accounts per logical switch and designate their roles as either admin or user. See the procedures in ”Creating and maintaining user-defined accounts” on page 43.

For large enterprises, Fabric OS supports RADIUS services, as described in ”Setting up RADIUS AAA

service” on page 46.

In addition to the account access passwords, each switch can set a boot PROM password. For greater security, HP recommends that you set this password to protect system boot parameters from unauthorized access. See ”Setting the boot PROM password” on page 70.

Each of the default access accounts has an associated password. The first time you connect to a Fabric OS switch you are prompted to change these default account passwords.

If you do not change the default passwords, you are prompted to do so at each subsequent login until all system passwords have been changed from the default values. Thereafter, use the passwd command to change passwords.

For more background information on passwords, see ”Changing an account password” on page 45.

To change the default passwords at login:

1. Connect to the switch and log in as admin.

2. At each of the Enter new password prompts, either enter a new password or skip the prompt.

Skip a prompt by pressing Enter. You can bypass all further prompts by pressing Ctrl+c.

Although the root and factory accounts are not meant for general use, you should change their passwords if prompted to do so and save the passwords in case they are needed for recovery purposes.

Fabric OS 5.0.0 procedures user guide 21

Passwords can be from 8 to 40 characters long and must begin with an alphabetic character. They can include numerals, the dot (.), and the underscore (_). They are case sensitive, and they are not displayed when you enter them on the command line. You cannot reuse the default passwords.

NOTE: Record the passwords exactly as entered and store them in a secure place; recovering

passwords requires significant effort and fabric downtime.

Example:

login: admin Password: Please change your passwords now. Use Control-C to exit or press 'Enter' key to proceed. for user - root Changing password for root Enter new password: ***** Password changed. Saving password to stable storage. Password saved to stable storage successfully. Please change your passwords now. for user - factory Changing password for factory Enter new password: ***** Password changed. Saving password to stable storage. Password saved to stable storage successfully. Please change your passwords now. for user - admin Changing password for admin Enter new password: ***** Password changed. Saving password to stable storage. Password saved to stable storage successfully. Please change your passwords now. for user - user Changing password for user Enter new password: ***** Password changed. Saving password to stable storage. Password saved to stable storage successfully. switch:admin>

Setting the date and time

Switches maintain the current date and time in nonvolatile memory. Date and time are used for logging events. Switch operation does not depend on the date and time; a switch with an incorrect date and time value still functions properly. However, because the date and time are used for logging, you should set them correctly.

NOTE: The date and tsclockserver commands are disabled when the security feature is enabled.

With security enabled you can view the current date setting only on the primary FCS switch.

22 Performing basic configuration tasks

To set the date and time:

1. Connect to the switch and log in as admin.

2. Enter the date command at the command line using the following syntax:

date “MMDDhhmmYY”

The values represent the following:

• MM is the month; valid values are 01 through 12.

• DD is the date; valid values are 01 through 31.

• hh is the hour; valid values are 00 through 23.

• mm is minutes; valid values are 00 through 59.

• YY is the year; valid values are 00 through 99 (values greater than 69 are interpreted as 1970 through 1999, and values less than 70 are interpreted as 2000 through 2069).

NOTE: The date function does not support daylight savings time or time zones, so such changes must be

reset manually.

Example:

switch:admin> date

Fri May 5 21:50:00 UTC 1989

switch:admin>

switch:admin> date “0624165203”

Tue Jun 24 16:52:30 UTC 2003

switch:admin>

You can synchronize the local time of the principal or primary Fabric Configuration Server (FCS) switch to an external NTP server.

To synchronize local time with an external source:

1. Connect to the switch and log in as admin.

2. Issue the following command:

tsclockserver ipaddr

where ipaddr is the IP address of the NTP server, which the switch must be able to access. This operand is optional; by default this value is LOCL, which uses the local clock of the principal or primary switch as the clock server.

Example:

switch:admin> tsclockserver

LOCL

switch:admin> tsclockserver “132.163.135.131”

switch:admin> tsclockserver

132.163.135.131

switch:admin>

HP recommends that you synchronize time with an external NTP server, as described on page 23. If you cannot do so, use the next procedure.

Fabric OS 5.0.0 procedures user guide 23

To set the time zone:

1. Connect to the switch and log in as admin.

2. Issue the tstimezone command as follows:

tstimezone [houroffset [, minuteoffset]]

• For Pacific Standard Time enter tsTimeZone -8,0

• For Central Standard Time enter tsTimeZone -6,0

• For Eastern Standard Time enter tsTimeZone -5,0

The default time zone for switches is Universal Time Conversion (UTC), which is 8 hours ahead of (later than) Pacific Standard Time (PST). For additional time zone conversions, see Table 3.

The parameters do not apply if the time zone of the switch has already been changed from the default (8 hours ahead of PST).

Refer to the tstimezone command in the HP StorageWorks Fabric OS 4.x command reference guide for more detailed information about the command parameters.

3. Repeat the procedure on all switches for which the Time Zone needs to be set. This needs to be done

only once, because the value is written to nonvolatile memory.

For U.S. time zones, use Table 3 to determine the correct parameter for the tstimezone command.

Table 3 Conversion from UTC to local time

Local time tstimezone conversion

parameter

Atlantic Standard -4,0

Atlantic Daylight -3,0

Eastern Standard -5,0

Eastern Daylight -4,0

Central Standard -6,0

Central Daylight -5,0

Mountain Standard -7,0

Mountain Daylight -6,0

Pacific Standard -8,0

Pacific Daylight -7,0

Alaskan Standard -9,0

Alaskan Daylight -8,0

Hawaiian Standard -10,0

24 Performing basic configuration tasks

Maintaining licensed features

Feature licenses might be part the licensed Paper Pack supplied with switch software, or you can purchase licenses separately from your switch vendor, who will provide you with keys to unlock the features. License keys are provided on a per-chassis basis, so for products that support multiple logical switches (domains), a license key applies to all domains within the chassis.

To unlock a licensed feature, you can either use the license key in the Paper Pack supplied with switch software, or launch an internet browser and go to the HP licensing web site at

http://webkey.external.hp.com/welcome.asp

generate the key.

NOTE: You need the following items for each chassis to be licensed:

• Transaction key, which is in the Paper Pack supplied with switch software. Or, when you purchase a

license, your switch vendor gives you a transaction key to be used for obtaining a license key.

• License ID; to see a switch License ID, use the licenseIDShow command.

To unlock a licensed feature:

1. If you already have a license key, go to step 10.

If you do not have a key, launch an Internet browser and go to the HP web site:

http://www.hp.com/country/us/eng/prodserv/storage.html

. Click Generate a license key and follow the instructions to

2. Click products.

3. Click Software Products.

4. In the Related Links panel on the right side of the page, select Software License Keys.

The Software License Keys instruction page appears.

5. If you want to generate a single license key, select Generate 1 license key.

If you want to generate multiple license keys, select Batch Generation of Licenses.

The Software License Key instruction page appears.

6. Enter the requested information in the required fields.

When generating multiple license keys, enter the worldwide names and transaction keys in the table at the bottom of the screen. If you need additional rows in the table, select Add More Rows.

7. Click Next.

A verification screen appears.

8. Verify that the information appears correctly.

Click Submit if the information displayed is correct. If the information is incorrect, Click Previous and change the information.

9. After the information is corrected, click Submit.

An information screen displays the license keys.

You also receive an e-mail with the keys and installation instructions.

Fabric OS 5.0.0 procedures user guide 25

10.Activate and verify the license as follows:

a. Connect to the switch and log in as admin.

b. Activate the license using the licenseadd command. For example:

switch:admin> licenseadd “key”

The license key is case sensitive and must be entered exactly as given. The quotation marks are optional.

For the Core Switch 2/64 and SAN Director 2/128, the licenses are effective on both CPs and on all logical switches.

c. Verify that the license was added by issuing the licenseshow command. The licensed features

currently installed on the switch are listed. If the feature is not listed, issue the licenseadd command again.

d. Some features may require additional configuration , or you might need to disable and reenable

the switch to make them operational; see the feature documentation for details.

Example

switch:admin> licenseshow SbeSdQdQySyriTeJ: Web license Zoning license Fabric license Remote Switch license Extended Fabric license Fabric Watch license Performance Monitor license Trunking license Security license SbbebdQS9QTscfcB: Ports on Demand license - additional 8 port upgrade SbbebdQS9QTcgfcz: Ports on Demand license - additional 8 port upgrade

To remove a licensed feature:

1. Connect to the switch and log in as admin.

2. Issue the licenseshow command to display the active licenses.

3. Remove the license key using the licenseremove command. For example:

switch:admin> licenseremove “key”

The license key is case sensitive and must be entered exactly as given. The quotation marks are optional.

After removing a license key, the optionally licensed feature is disabled when the switch is rebooted or when a switch disable or enable is performed. For the Core Switch 2/64 and SAN Director 2/128, reboot both the primary and the secondary CP cards to ensure that HA features remain synchronized.

4. Issue the licenseshow command to verify that the license is disabled.

26 Performing basic configuration tasks

Example:

switch:admin> licenseshow bQebzbRdScRfc0iK: Web license Zoning license SybbzQQ9edTzcc0X: Fabric license switch:admin> licenseremove “bQebzbRdScRfc0iK” removing license key “bQebzbRdScRfc0iK” switch:admin>

After a reboot (or switchdisable and switchenable):

Example:

switch:admin> licenseshow SybbzQQ9edTzcc0X: Fabric license switch:admin>

If there are no license keys, licenseshow displays No licenses.

Customizing the switch name

Switches can be identified by IP address, Domain ID, World Wide Name (WWN), or by customized switch names that are unique and meaningful.

Version 4.0.0 and later switch names can be from 1 to 15 characters; they must begin with a letter and may can contain letters, numbers, and the underscore character. It is not necessary to use quotation marks.

The default names are:

• swd77 for the SAN Switch 2/8V, SAN Switch 2/16V, SAN Switch 2/32, and SAN Switch 4/32.

• For the Core Switch 2/64, the two logical switches have different default names. The name swd77 is

used for the logical switch containing the port cards in slots 1 through 4; swd76 is used for the logical switch containing the port cards in slots 7 through 10.

• swd77 for the SAN Director 2/128

NOTE: Changing the switch name causes a domain address format RSCN to be issued.

To customize the switch name:

1. For the SAN Switch 2/8V, SAN Switch 2/16V, SAN Switch 2/32, and SAN Switch 4/32, proceed

to the next step.

For the Core Switch 2/64 and the SAN Director 2/128, identify the serial console for the active CP. You can do so by issuing the hashow command from any Core Switch 2/64 and SAN Director 2/128 serial console, or by looking for the blue Active LED on the SAN Director 2/128.

2. Connect to the switch and log in as admin.

Fabric OS 5.0.0 procedures user guide 27

3. For the Core Switch 2/64 and the SAN Director 2/128, proceed to the next step.

For the SAN Director 2/128, if configured for one domain (the default) proceed to the next step. If configured with two domains, proceed as for the Core Switch 2/64.

For the Core Switch 2/64, choose the logical switch that you want to change. Enter the value that corresponds to that logical region:

•Enter 0 to configure logical switch 0 (slot 1 through 4).

•Enter 1 to configure logical switch 1 (slot 7 through 10).

4. Issue the switchname command at the command line with the following syntax:

switchname “newname”

where newname is the new name for the switch.

5. Record the new switch name for future reference.

6. For the Core Switch 2/64 and the SAN Director 2/128 configured with two domains, disconnect

from the session and repeat the procedure for the second logical switch.

Example:

switch:admin> switchname “switch62” Committing configuration... Done. switch62:admin>

Customizing the chassis name

Beginning with Fabric OS v4.4.0, HP recommends that you customize the chassis name for each switch. Some system logs identify switches by chassis names, so if you assign meaningful chassis names in addition to meaningful switch names, logs are more useful.

To change the chassis name:

1. Connect to the switch and log in as admin.

2. Issue the chassisname command at the command line with the following syntax:

chassisname “newname”

Where newname is the new name for the chassis.

Chassis names can be from 1 to 15 characters, must begin with a letter, and can contain letters, numbers, and the underscore character. It is not necessary to use the quotation marks.

3. Record the new chassis name for future reference.

Disabling and enabling a switch

By default, the switch is enabled after power is applied and diagnostics and switch initialization routines have finished. You can disable and reenable it as necessary.

To disable a switch:

1. Connect to the switch and log in as admin.

28 Performing basic configuration tasks

2. Issue the switchdisable command at the command line.

All Fibre Channel ports on the switch are taken offline. If the switch was part of a fabric, the fabric reconfigures.

To enable a switch:

1. Connect to the switch and log in as admin.

2. Issue the switchenable command at the command line.

All Fibre Channel ports that passed the POST test are enabled. If the switch has interswitch links to a fabric, it joins the fabric.

Disabling and enabling a port

All licensed ports are enabled by default. You can disable and reenable them as necessary. Ports that you activate with Ports on Demand must be enabled explicitly, as described in ”Activating Ports on

Demand” on page 30.

To disable a port:

1. Connect to the switch and log in as admin.

2. For the SAN Switch 2/8V, SAN Switch 2/16V, SAN Switch 2/32, and SAN Switch 4/32, issue the

following command:

portdisable portnumber

where portnumber is the port number of the port you want to disable.

For the Core Switch 2/64 and the SAN Director 2/128, issue the following command:

portdisable slotnumber/portnumber

where slotnumber and portnumber are the slot and port numbers of the port you want to disable.

If the port is connected to another switch, the fabric might reconfigure.

To enable a port:

1. Connect to the switch and log in as admin.

2. For the SAN Switch 2/8V, SAN Switch 2/16V, SAN Switch 2/32, and SAN Switch 4/32, issue the

following command:

portenable portnumber

The portnumber is the port number of the port you want to enable.

For the Core Switch 2/64 and the SAN Director 2/128, issue the following command:

portenable slotnumber/portnumber

The slotnumber and portnumber are the slot and port numbers of the port you want to enable. (Slots are numbered 1 through 4 and 7 through 10, counting from left to right.)

If the port is connected to another switch, the fabric might reconfigure. If the port is connected to one or more devices, these devices become available to the fabric.

If you change port configurations during a switch failover, the ports might become disabled. Reissue the portenable command after the failover is complete to bring the ports online.

Fabric OS 5.0.0 procedures user guide 29

Activating Ports on Demand

The Core Switch 4/32 can be purchased with 16 or 32 licensed ports. As your needs increase, you can activate the remaining ports by purchasing and installig the optional HP StorageWorks 8-port upgrade license.

Ports on Demand is ready to be unlocked in the switch firmware. Its license might be part of the licensed Paper Pack supplied with switch software, or you can purchase the license separately from your switch vendor, who will provide you with a key to unlock it.

By default, ports 0 through 15 are enabled on the SAN Switch 4/32. To enable ports 16 through 23, purchase and install an 8-port upgrade license. To enable ports 24 through 31, purchase and install another 8-port upgrade license. The first license key must be already installed before you can use the second license.

You must enable the ports after you have installed the license keys. You can do so without disrupting switch operation using the portenable command on each port. Alternatively, you can disable and reenable the switch to activate all ports.

To enable an 8-port upgrade license, you can either use the supplied license key or generate a license key. If you need to generate a key, launch an Internet browser and go to the HP licensing web site at

http://webkey.external.hp.com/welcome.asp

generate the key.

To enable Ports on Demand:

. Click Generate a license key and follow the instructions to

1. Connect to the switch and log in as admin.

2. Optional: to verify the states of the ports, use the portshow command.

In the portshow output, the Licensed field shows whether the port is licensed.

3. Install the HP Ports on Demand licensed product.

For instructions, see ”Maintaining licensed features” on page 25.

4. Use the portenable command to enable the ports.

5. Optional: use the portshow command to check the newly activated ports.

If you remove an 8-port upgrade license, the licensed ports become disabled after the next platform reboot or the next port deactivation.

Making basic connections

You can make basic connections to devices and to other switches.

Before connecting a v4.0.0 or later switch to a fabric that contains switches running earlier firmware versions, you must first set the same PID format on all the switches. The presence of different PID formats in a fabric causes fabric segmentation.

For information on PID formats and related procedures, see ”Selecting a PID format” on page 206.

For information on configuring the routing of connections, see ”Routing traffic” on page 99.

For information on configuring extended interswitch connections, see ”Administering extended fabrics” on page 107.

30 Performing basic configuration tasks

+ 240 hidden pages