You are on page 1of 64

IBM System Storage N series

Brocade 300 and Brocade 5100 Switch
Configuration Guide

GC53-1167-00
NA 210-04419_A0

Copyright and trademark information

Copyright
information

Copyright ©1992 - 2009 Network Appliance, Inc. All rights reserved. Printed in the U.S.A.
Portions copyright © 2009 IBM Corporation. All rights reserved.
US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP
Schedule Contract with IBM Corp.
No part of this document covered by copyright may be reproduced in any form or by any means—
graphic, electronic, or mechanical, including photocopying, recording, taping, or storage in an
electronic retrieval system—without prior written permission of the copyright owner.
References in this documentation to IBM products, programs, or services do not imply that IBM
intends to make these available in all countries in which IBM operates. Any reference to an IBM
product, program, or service is not intended to state or imply that only IBM’s product, program, or
service may be used. Any functionally equivalent product, program, or service that does not infringe
any of IBM’s or NetApp’s intellectual property rights may be used instead of the IBM or NetApp
product, program, or service. Evaluation and verification of operation in conjunction with other
products, except those expressly designated by IBM and NetApp, are the user’s responsibility.
Portions copyright © 1998–2001 The OpenSSL Project. All rights reserved.
No part of this document covered by copyright may be reproduced in any form or by any
means—graphic, electronic, or mechanical, including photocopying, recording, taping, or storage in
an electronic retrieval system—without prior written permission of the copyright owner.
Portions of this product are derived from the Berkeley Net2 release and the 4.4-Lite-2 release, which
are copyrighted and publicly distributed by The Regents of the University of California.
Copyright © 1980–1995 The Regents of the University of California. All rights reserved.
Portions of this product are derived from NetBSD, copyright © Carnegie Mellon University.
Copyright © 1994, 1995 Carnegie Mellon University. All rights reserved. Author Chris G. Demetriou.
Permission to use, copy, modify, and distribute this software and its documentation is hereby granted,
provided that both the copyright notice and its permission notice appear in all copies of the software,
derivative works or modified versions, and any portions thereof, and that both notices appear in
supporting documentation.
CARNEGIE MELLON ALLOWS FREE USE OF THIS SOFTWARE IN ITS “AS IS” CONDITION.
CARNEGIE MELLON DISCLAIMS ANY LIABILITY OF ANY KIND FOR ANY DAMAGES
WHATSOEVER RESULTING FROM THE USE OF THIS SOFTWARE.
Software derived from copyrighted material of The Regents of the University of California and
Carnegie Mellon University is subject to the following license and disclaimer:
Redistribution and use in source and binary forms, with or without modification, are permitted
provided that the following conditions are met:
Redistributions of source code must retain the above copyright notices, this list of conditions, and the
following disclaimer.
Redistributions in binary form must reproduce the above copyright notices, this list of conditions, and
the following disclaimer in the documentation and/or other materials provided with the distribution.

ii

Copyright and trademark information

All advertising materials mentioning features or use of this software must display the following
acknowledgment:
This product includes software developed by the University of California, Berkeley and its
contributors.
Neither the name of the University nor the names of its contributors may be used to endorse or
promote products derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS “AS IS” AND
ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS
BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER
IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Portions of the software were created by Netscape Communications Corp.
The contents of those portions are subject to the Netscape Public License Version 1.0 (the “License”);
you may not use those portions except in compliance with the License. You may obtain a copy of the
License at http://www.mozilla.org/NPL/.
Software distributed under the License is distributed on an “AS IS” basis, WITHOUT WARRANTY
OF ANY KIND, either express or implied. See the License for the specific language governing rights
and limitations under the License.
The Original Code is Mozilla Communicator client code, released March 31, 1998.
The Initial Developer of the Original Code is Netscape Communications Corp. Portions created by
Netscape are Copyright © 1998 Netscape Communications Corp. All rights reserved.
This software contains materials from third parties licensed to NetApp Inc. which is sublicensed, and
not sold, and title to such material is not passed to the end user. All rights reserved by the licensors.
You shall not sublicense or permit timesharing, rental, facility management or service bureau usage of
the Software.
Portions developed by the Apache Software Foundation (http://www.apache.org/). Copyright © 1999
The Apache Software Foundation.
Portions Copyright © 1995–1998, Jean-loup Gailly and Mark Adler
Portions Copyright © 2001, Sitraka Inc.
Portions Copyright © 2001, iAnywhere Solutions
Portions Copyright © 2001, i-net software GmbH
Portions Copyright © 1995 University of Southern California. All rights reserved.
Redistribution and use in source and binary forms are permitted provided that the above copyright
notice and this paragraph are duplicated in all such forms and that any documentation, advertising
materials, and other materials related to such distribution and use acknowledge that the software was
developed by the University of Southern California, Information Sciences Institute. The name of the
University may not be used to endorse or promote products derived from this software without
specific prior written permission.
Portions of this product are derived from version 2.4.11 of the libxml2 library, which is copyrighted
by the World Wide Web Consortium.

Copyright and trademark information

iii

All Rights Reserved. The use or purchase of this product does not convey a license under any patent rights. provided that you include the following on ALL copies of the software and documentation or portions thereof.) THIS SOFTWARE AND DOCUMENTATION IS PROVIDED “AS IS.” AND COPYRIGHT HOLDERS MAKE NO REPRESENTATIONS OR WARRANTIES.w3. with or without modification. or terms and conditions. All Rights Reserved. Software derived from copyrighted material of NetApp. Solaris. patents. (Massachusetts Institute of Technology.org/. If none exist. is subject to the following license and disclaimer: NetApp reserves the right to change any products described herein at any time. or disclosure by the government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252. that you make: The full text of this NOTICE in a location viewable to users of the redistributed or derivative work. The unmodified libxml2 software can be downloaded from http://www. including the date changes were made. (Massachusetts Institute of Technology. and distribute this software and its documentation. Title to copyright in this software and any associated documentation will at all times remain with copyright holders. NetApp assumes no responsibility or liability arising from the use of products described herein. 2001.A. EXPRESS OR IMPLIED. Software derived from copyrighted material of the World Wide Web Consortium is subject to the following license and disclaimer: Permission to use. The name and trademarks of copyright holders may NOT be used in advertising or publicity pertaining to the software without specific. COPYRIGHT HOLDERS WILL NOT BE LIABLE FOR ANY DIRECT. Keio University). or pending applications. written prior permission.NetApp modified the libxml2 software on December 6. duplication. modify. Institut National de Recherche en Informatique et en Automatique.xmlsoft. iv Copyright and trademark information . (We recommend you provide URLs to the location from which the code is derived. and Linux. except as expressly agreed to in writing by NetApp. and without notice. TRADEMARKS OR OTHER RIGHTS. WARRANTIES OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF THE SOFTWARE OR DOCUMENTATION WILL NOT INFRINGE ANY THIRD PARTY PATENTS. Any pre-existing intellectual property disclaimers. foreign patents. INCLUDING BUT NOT LIMITED TO. http://www.org/Consortium/Legal/” Notice of any changes or modifications to the W3C files. Institut National de Recherche en Informatique et en Automatique. Inc.277-7103 (October 1988) and FAR 52-227-19 (June 1987). COPYRIGHTS. The product described in this manual may be protected by one or more U.w3.S. to enable it to compile cleanly on Windows. RESTRICTED RIGHTS LEGEND: Use. The changes have been sent to the maintainers of libxml2. trademark rights. notices. including modifications. a short notice of the following form (hypertext is preferred. SPECIAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF ANY USE OF THE SOFTWARE OR DOCUMENTATION. text is permitted) should be used within the body of any redistributed or derivative code: “Copyright © [$date-of-software] World Wide Web Consortium. http://www. Keio University). copy. for any purpose and without fee or royalty is hereby granted. or any other intellectual property rights of NetApp. INDIRECT. Copyright © 1994–2002 World Wide Web Consortium.org/Consortium/Legal/.

DataFabric. A complete and current list of other IBM trademarks is available on the Web at http://www.A. and Web Filer are trademarks of NetApp. in the U. Serving Data by Design. or both. the bolt design. FPolicy. SpinStor. Network Appliance. SnapLock. SnapManager. Simulate ONTAP. Faster. Copyright and trademark information v . Network Appliance is a licensee of the CompactFlash and CF Logo trademarks. FilerView. NetApp.S. The NetApp arch logo. SnapMirror. SpinServer. SpinCluster. LockVault. SpinRestore. NetApp Availability Assurance and NetApp ProTech Expert are service marks of NetApp. RAID-DP.A. the IBM logo. and the Windows logo are trademarks of Microsoft Corporation in the United States. and/or other countries. ComplianceClock. NOW. SyncMirror.Trademark information IBM.S. other countries. Inc. NOW NetApp on the Web. FlexVol. Virtual File Manager. or both. other countries. SpinShot. ContentFabric. SnapVault. StoreVault. and WAFL are registered trademarks of NetApp. ContentDirector. Windows NT.com are trademarks or registered trademarks of International Business Machines Corporation in the United States. Inc. SpinMirror. SpinMove. SnapValidator. VFM (Virtual File Manager).com/legal/copytrade. SharedStorage. SecureAdmin. SecureShare. Manage ONTAP. Simplicore. Lifetime Key Management. Go Further. in the U. SnapRestore. All other brands or products are trademarks or registered trademarks of their respective holders and should be treated as such. RoboCache. RoboFiler. ONTAPI. HyperSAN. SnapDrive. SohoFiler. Spinnaker Networks. NetCache. SpinFS. Cryptainer. vFiler. or both.S.ibm. MultiStore. Decru. and ibm. OpenKey. VFM. Cryptoshred. SnapMigrator. Network Appliance NetCache is certified RealSystem compatible. SnapDirector. NetApp—the Network Appliance Company. Topio. the StoreVault logo. FlexShare. Snapshot. InfoFabric. SANscreen. SnapCopy. in the U.shtml Linux is a registered trademark of Linus Torvalds in the United States. Smart SAN. and/or other countries and registered trademarks in some other countries. Inc. ApplianceWatch.A. EdgeFiler. Windows. and The evolution of storage are trademarks of NetApp. BareMetal. Camera-to-Viewer. FAServer. gFiler. FlexClone.A. Microsoft. the Network Appliance logo. in the U. SnapMover. Inc. ComplianceJournal. other countries. SnapSuite. UNIX is a registered trademark of The Open Group in the United States and other countries. SpinHA. DataFort. SnapCache. Data ONTAP. ReplicatorX. SnapFilter. VPolicy. and other countries.S. NearStore.

EITHER EXPRESS OR IMPLIED. N. Any references in this information to non-IBM web sites are provided for convenience only and do not in any manner serve as an endorsement of those web sites. visit the web at: http://www. vi Notices . services.A. or service is not intended to state or imply that only that IBM product. IBM may not offer the products. However. or features discussed in this document in other countries. You can send license inquiries. or service that does not infringe on any IBM intellectual property right may be used instead.Y. Consult your local IBM representative for information on the products and services currently available in your area. THE IMPLIED WARRANTIES OF NON-INFRINGEMENT. The furnishing of this document does not give you any license to these patents. The materials at those web sites are not part of the materials for this IBM product and use of those web sites is at your own risk. Any reference to an IBM product.Notices This information was developed for products and services offered in the U. BUT NOT LIMITED TO.S. 10504-1785 U. these changes will be incorporated in new editions of the publication. Any functionally equivalent product. Changes are periodically made to the information herein.S.com/ibm/licensing/contact/ The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION “AS IS” WITHOUT WARRANTY OF ANY KIND. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. This information could include technical inaccuracies or typographical errors. this statement may not apply to you.A.ibm. IBM may have patents or pending patent applications covering subject matter described in this document. For additional information. INCLUDING. in writing to: IBM Director of Licensing IBM Corporation North Castle Drive Armonk. Some states do not allow disclaimer of express or implied warranties in certain transactions. MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. or service. therefore. program. or service may be used. program. program. it is the user’s responsibility to evaluate and verify the operation of any non-IBM product. program.

Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products. Furthermore. some measurement may have been estimated through extrapolation. IBM has not tested those products and cannot confirm the accuracy of performance. If you are viewing this information in softcopy. Actual results may vary. the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Information concerning non-IBM products was obtained from the suppliers of those products. compatibility or any other claims related to non-IBM products. Notices vii . Therefore. Users of this document should verify the applicable data for their specific environment. Any performance data contained herein was determined in a controlled environment. the photographs and color illustrations may not appear. their published announcements or other publicly available sources.IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you.

viii

Notices

Table of Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .ix

Chapter 1

Fabric MetroCluster Overview. . . . . . . . . . . . . . . . . . . . . . . . . 1
Fabric MetroCluster Switch Overview . . . . . . . . . . . . . . . . . . . . . . 2

Chapter 2

Switch Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
How switch ports are grouped . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Chapter 3

Virtual Channel Cabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Description of the virtual channel feature . . . . . . . . . . . . . . . . . . . 10
Virtual channel and destination port map . . . . . . . . . . . . . . . . . . . 11
Virtual channel cabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Chapter 4

Configuring Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Configuring a switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Completing the configuration. . . . . . . . . . . . . . . . . . . . . . . . . . 20

Chapter 5

Switch Zoning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Zoning feature description . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Configuring zones on the primary and secondary fabric . . . . . . . . . . . . 25

Chapter 6

Traffic Isolation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Traffic Isolation feature description . . . . . . . . . . . . . . . . . . . . . . 32
TI zone failover operation . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
TI zone configuration rules . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Configuring TI zones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
TI zone command syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Table of Contents

ix

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

x

Table of Contents

It also assumes that you are familiar with how to configure the storage system and how the NFS. The guide also describes how to cable virtual channels and how to use zoning and traffic isolation zoning. such as IP addressing. it emphasizes the characteristics of the storage system. routing. Linux®.ibm. and network topology. This guide does not cover basic system or network administration topics. and Windows® 2003. Some features described in the product software documentation are neither offered nor supported by IBM.Preface About this guide This guide describes how Brocade® 300 (IBM® System Storage SAN24B-4 Express) and Brocade 5100 (IBM System Storage SAN40B-4) switch models operate with a MetroCluster and how to configure these switches in a fabricattached MetroCluster. Supported features IBM System Storage™ N series systems and expansion boxes are driven by NetApp® Data ONTAP® software. except where the name of a specific model is required for clarity. The term switch is used in this guide to refer to the Brocade 300 and Brocade 5100 switches and their IBM equivalents. CIFS. and HTTP protocols are used for file sharing or transfers.com/storage/support/nas/ Preface xi . such as UNIX®. Brocade and IBM product and model number matrix The following table identifies IBM products that are equivalent to the Brocade products mentioned in this publication. Brocade product name IBM product name IBM machine type and model number Brocade 300 IBM System Storage SAN24B-4 Express 2498 Models B24 and 24E Brocade 5100 IBM System Storage SAN40B-4 2498 Models B40 and 40E Audience This guide is for system administrators who are familiar with operating systems that run on the storage system’s clients. Information about supported features can also be found at the following Web site: www. Please contact your local IBM representative or reseller for further details.

The same documentation is available as PDF files on the IBM NAS support Web site: www. if it is necessary. go to the following Web site: www. ◆ Use an IBM discussion forum on the IBM Web site to ask questions. Before you call Before you call. Information about the N series product and Data ONTAP software is available in printed documents and a documentation CD that comes with your system.ibm.ibm.ibm. and whom to call for service. you will find a wide variety of sources available from IBM to assist you. go to the following Web site: www.com/storage/support/nas/ Web sites IBM maintains pages on the World Wide Web where you can get the latest technical information and download device drivers and updates.com/storage/nas/ ◆ For NAS support information.ibm. make sure that you have taken these steps to try to solve the problem yourself: Using the documentation ◆ Check all cables to make sure that they are connected properly. ◆ Use the troubleshooting information in your system documentation and use the diagnostic tools that come with your system. help. what to do if you experience a problem with your IBM System Storage N series product. service. This section contains information about where to go for additional information about IBM and IBM products. or technical assistance or just want more information about IBM products. and service If you need help. ◆ Check the power switches to make sure that the system is turned on.A listing of currently available N series products and features can be found at the following Web site: www.ibm.com/storage/nas/ Getting information.com/storage/support/nas/ xii .com/storage/support/nas/ Data ONTAP software publications are available as PDF files on the IBM NAS support Web site: www. ◆ For NAS product information.

in configuration files. To determine the latest supported attachments. or systems. See the Software Setup Guide for more information on updating firmware. storage appliances.ibm. or through a Telnet session or Remote Shell connection.com/storage/support/nas/ Drive firmware updates As with all devices.ibm. follow the link to the Interoperability matrices on the following Web site: www.com/planetwide Supported servers and operating systems IBM N series products attach to many servers and many operating systems.com/storage/support/nas/ Hardware service and support You can receive hardware service through IBM Integrated Technology Services. you can perform tasks by entering commands at the console. The name of the graphical user interface for Data ONTAP (FilerView) reflects one of these common usages. go to the following Web site: www. visit the following Web site: www.com/storage/support/nas/ Verify that the latest level of firmware is installed on your machine before contacting IBM for technical support. it is recommended that you run the latest level of firmware.ibm. Preface xiii .ibm. which can be downloaded by visiting the following Web site: www. FilerView as an alternative to commands As a storage system administrator.◆ For AutoSupport information.com/storage/support/nas/ Accessing online technical support For online Technical Support for your IBM N series product. Terminology Storage systems that run Data ONTAP are sometimes also referred to as appliances. Visit the following Web site for support telephone numbers: www.ibm.

Command conventions You can enter storage system commands on the system console or from any client that can obtain access to the storage system using a Telnet session. In examples that illustrate commands executed on a UNIX workstation. and it includes Help that explains FilerView features and how to use them. For example. Monospaced font Bold monospaced font xiv Words or characters you type. What you type is always shown in lowercase letters. ◆ The contents of files. . Formatting conventions The following table lists different character formats used in this guide to set off special information.Another method of performing common tasks is to use the FilerView® graphical management interface for viewing and managing a storage system from a Web browser. if the guide requires you to enter the fctest adaptername command. ◆ Book titles in cross-references. FilerView is easy to use. depending on your version of UNIX. ◆ Command and daemon names. see the Storage Management Guide. and about FilerView Help. Formatting convention Type of information Italic type ◆ Words or characters that require special attention. For more information about accessing a storage system using FilerView. you enter the characters “fctest” followed by the actual name of the adapter. unless your program is case-sensitive and uppercase letters are necessary for it to work properly. ◆ Information displayed on the system console or other computer monitors. the command syntax and output might differ. ◆ Placeholders for information you must supply.

Ctrl-D means holding down the Ctrl key while pressing the D key. or loss of data.Keyboard conventions Special messages This guide uses capitalization and some abbreviations to refer to the keys on the keyboard. Preface xv . a system crash. For example. This guide contains special messages that are described as follows: Note A note contains important information that helps you install or operate the system efficiently. The keys on your keyboard might not be labeled exactly as they are in this guide. enter Used to mean pressing one or more keys and then pressing the Enter key. Enter Used to refer to the key that generates a carriage return. What is in this guide… What it means… hyphen (-) Used to separate individual keys. Attention An attention notice contains instructions that you must follow to avoid damage to the equipment. type Used to mean pressing one or more keys on the keyboard. the key is named Return on some keyboards.

you can direct your mail to: International Business Machines Corporation Information Development Dept.How to send your comments Your feedback is important in helping us provide the most accurate and highquality information. you grant IBM a nonexclusive right to use or distribute the information in any way it believes appropriate without incurring any obligation to you.com or use the Readers’ Comments form at the back of this publication.ibm. When you send information to IBM. xvi . GZW 9000 South Rita Road Tucson. If you have comments or suggestions for improving this document. Include the following: ◆ Exact publication title ◆ Form number (for example. send us your comments by e-mail to starpubs@us. GC26-1234-02) ◆ Page numbers to which you are referring If the Readers’ Comments Form in the back of this manual is missing.A.S. AZ 85744–0001 U.

Topics in this chapter This chapter discusses the following topic: “Fabric MetroCluster Switch Overview” on page 2.Fabric MetroCluster Overview About this chapter This chapter introduces the MetroCluster configuration and switch fabrics. Chapter 1: Fabric MetroCluster Overview 1 1 .

2. When the distance between the two systems is greater than 500 meters. you use four Fibre Channel switches in a fabric configuration to connect the two systems.6 and later ◆ 7.3 and later SFP requirements for these switches These switches can be used with Brocade small-form pluggables (SFPs) that are set to either 4 Gbit. Definition of MetroCluster switch fabrics A fabric-attached MetroCluster contains two switch fabrics. 2 Fabric MetroCluster Switch Overview . You can place these two systems in different locations. or 1 Gbit per second. This configuration is called a fabric-attached MetroCluster. Note Do not mix switch models within a single fabric-attached MetroCluster or across a fabric-attached MetroCluster.1 ◆ 7.2. as shown in the following illustration. A switch fabric consists of a switch on the local half of the MetroCluster connected to a switch on the remote half of the MetroCluster. The two switches are connected to each other through long-distance Inter-Switch Link (ISL) cables.Fabric MetroCluster Switch Overview Data ONTAP® requirements for these switches These switches (and IBM equivalents) require one of the following Data ONTAP® releases to be used in a MetroCluster configuration: ◆ 7.5. 2 Gbit. Description of a MetroCluster configuration The MetroCluster configuration uses two storage systems that are connected to provide high availability and data mirroring.

Dual Fabric Metro Cluster Fabric 1 SW1 SW3 Fabric 2 SW2 Chapter 1: Fabric MetroCluster Overview SW4 3 . The second fabric is created using Switch 2 on the local node.Sample diagram of a MetroCluster switch fabric For example. connected through a second ISL cable to the second switch (Switch 4) on the remote node. consider a Fabric MetroCluster configuration in which the first fabric begins at Switch 1 on the local node and is completed by connecting the ISL cable to the first switch (Switch 3) on the remote node. This example is illustrated in the following diagram.

4 Fabric MetroCluster Switch Overview .

2 Switch Ports About this chapter This chapter illustrates switch ports and how they are grouped into port groups. Topics in this chapter This chapter discusses the following topics: Chapter 2: Switch Ports ◆ “How switch ports are grouped” on page 6 5 .

or storage loops. based on the total number of ports enabled with the Ports on Demand (POD) license. FC initiator adapter ports. or 4 Gbits per second. Note Do not install Small Form Pluggables (SFPs) in non-licensed ports. 4 Gbit SFPs are supported only with the transfer rates 1. Note You cannot use the auto-sensing speed mode with switch ports that are connected to FC-VI adapter ports. The number of groups available differs. You must set the speed of these switch ports to the speed supported by the port at the other end of the link by using the portcfgspeed command. Ports and port groups in the Brocade 300 switch The Brocade 300 switch has 24 ports. See the sections that follow for each individual switch. Ports 8 through 15 and ports 16 through 23 can also be licensed. RJ45 RJ45 USB console Ethernet port port 6 Port group enabled by default Port groups licensed by POD How switch ports are grouped . the 8 Gbit SFPs are supported only with the transfer rates 2 or 4 Gbits per second.How switch ports are grouped Port groupings The switch ports are divided into eight-port groups. Ports 0 through 7 are enabled by default. This might cause Data ONTAP to erroneously assign pools to the unlicensed ports. or a 24-port switch. See the following diagram for port numbering. 2. See “Completing the configuration” on page 20. but can be licensed as an 8-port switch. Note If you are using SFPs with the switches. 2. a 16-port switch. and 4 Gbits per second. The ports auto-sense link speeds and support transfer rates of 1.

a 32-port switch.Ports and port groups in the Brocade 5100 switch The Brocade 5100 switch has 40 ports. See “Completing the configuration” on page 20. Ports 24 through 31 and ports 32 through 39 can also be licensed. You must set the speed of these switch ports to the speed supported by the port at the other end of the link by using the portcfgspeed command. or storage loops. or a 40-port switch. Note If you are using SFPs with the switches. RJ45 RJ45 USB console Ethernet port port Chapter 2: Switch Ports Port group enabled by default Port group enabled by default Port group enabled by default Port group licensed by POD Port group licensed by POD 7 . or 4 Gbits per second. The ports auto-sense link speeds and support transfer rates of 1. Ports 0 through 23 are enabled by default. 4Gbit SFPs support only the transfer rates 1. 2. but can be licensed as an 24-port switch. See the following diagram for port numbering. and 4 Gbits per second. FC initiator adapter ports. 2. Note You cannot use the auto-sensing speed mode with switch ports that are connected to FC-VI adapter ports. the 8 Gbit SFPs support only the transfer rates 2 or 4 Gbits per second.

8 How switch ports are grouped .

Topics in this chapter This chapter discusses the following topics: ◆ “Description of the virtual channel feature” on page 10 ◆ “Virtual channel cabling” on page 12 ◆ “Virtual channel and destination port map” on page 11 Chapter 3: Virtual Channel Cabling 9 .Virtual Channel Cabling 3 About this chapter This chapter describes the virtual channel feature and provides sample cabling diagrams for virtual channels.

Each of the eight virtual channels within an ISL includes a physical circuit as well as components for flow control and buffer credit management. Distance consideration for virtual channels The virtual channel feature can be used only with ISLs that are 10km or less. your storage system platforms must use software-based disk ownership. What the virtual channel feature does You can use the virtual channel feature to separate cluster interconnect (FCVI) traffic and ISL traffic from storage traffic. Storage system platforms that support software-based disk ownership enable you to use virtual channel technology to isolate interconnect traffic from the storage traffic stream. 10 Description of the virtual channel feature . The virtual channel feature logically partitions bandwidth within each ISL into eight virtual channels. Note Hardware-based disk ownership is not supported when using the Brocade 5100 switch.Description of the virtual channel feature Virtual channel feature platform requirement To use the virtual channel feature. When the ISL distance is greater than 10 KM. Virtual channel technology applies only to ISLs. all virtual channels are collapsed into one for buffer credit purposes. no single controller can monopolize all the bandwidth of an ISL and block out traffic from other controllers. you cannot use the Brocade 5100 switch in a MetroCluster that uses IBM System Storage N5200 or IBM System Storage N5500 storage systems. This ensures ISL reliability by preventing port blocking. Hardware-based disk ownership must be used in a MetroCluster when your storage systems are IBM System Storage N5200 or IBM System Storage N5500. All other storage system platforms qualified for MetroCluster use software-based disk ownership. Therefore. When you use virtual channel technology.

16. 28 0. 30. 19. 21 1. 7. 9. 38 Storage traffic 5 3. 15. Virtual channel Destination ports 8-port switch Destination ports for 16-port switch Destination ports for 24-port switch Destination ports for 32-port switch Destination ports for 40-port switch 2 0. 9. 7. 23 3. 18. 17. 7. 11. 4. 15. 14. 18. 6. 6. The eight virtual channels are numbered 0 through 7. 29 1. 29. 20 0. 6. 30 2. 26. 4. 5.Virtual channel and destination port map Virtual channel and destination port mapping limitations You can map each virtual channel to up to ten destination ports. 15. 22. 31 3. 22 2. 24. 12. 21. 4 0. 18. 34. 14. 14 2. 13. 27. 4. 4. 23. 9. 31. 25. 32. 12 0. 10. 14. 7 3. 10. 6 2. 10. 27. 20. 12. 8. 37 Storage traffic 4 2. 11. 17. 10. 5. 33. 11. 8. 21. 6. 35. 11. Map of virtual channels to ports The following table shows how the virtual channels map to switch destination ports and the typical usage of the virtual channels. 12. 19. 24. 13. 16. 9. 7. You can use virtual channels 2 through 5 for either Class 2 or Class 3 data traffic. 20. 8. 5. 13 1. 13. 5 1. 22. 28. 25. 26. 39 Storage traffic Chapter 3: Virtual Channel Cabling Usage 11 . 19. 23. 15 3. depending on how many of your switch ports are enabled. 36 Interconnect and ISL traffic 3 1. 17. 8. 16. 5.

using Brocade 300 switches to create a Fabric MetroCluster.Virtual channel cabling Sample diagram of Brocade 300 8-port cabling 12 The following sample diagram shows 8-port cabling. Virtual channel cabling . You should spread disk shelves across ports before adding a second shelf to each loop.

. Chapter 3: Virtual Channel Cabling 13 .Sample diagram of Brocade 300 16-port cabling The following sample diagram shows 16-port cabling. using Brocade 300 switches to create a Fabric MetroCluster. You should spread disk shelves across ports before adding a second shelf to each loop.

Sample diagram of Brocade 5100 40-port cabling The following sample diagram shows 40-port cabling. using Brocade 5100 switches to create a Fabric MetroCluster. . You should spread disk shelves across ports before adding a second shelf to each loop. 14 Virtual channel cabling .

Topics in this chapter This chapter discusses the following topics: ◆ “Configuring a switch” on page 16 ◆ “Completing the configuration” on page 20 Chapter 4: Configuring Switches 4 15 .Configuring Switches About this chapter This chapter explains how to configure a switch.

complete the following steps.1 for information about command syntax and options. ◆ You must use these procedures instead of the switch configuration procedures in the Cluster Installation and Administration Guide or the Active/Active Configuration Installation and Administration Guide. 16 Configuring a switch . using the console port and your Windows HyperTerminal application (not available in Windows Vista versions). Step Action 1 If this switch has not been configured before. note the following information: Configuring a switch initially ◆ These procedures must be performed on each switch in the MetroCluster configuration.Configuring a switch Before you begin Configuring these switches for a fabric-attached MetroCluster includes the following tasks: ◆ Configuring the switch initially ◆ Setting the switch parameters Before you begin the configuration. To configure a switch initially. and set the following values. using the switch IP address. see the Brocade Fabric OS Command Reference Manual Supporting Fabric OS 6. as described in the switch hardware reference manual for your switch: ◆ IP address ◆ Default account passwords (administrator and user) ◆ Date and time Note Use the telnet command for subsequent switch login sessions. log in to the switch. Note For all of the Brocade switch commands.

to set the addresses for switch number 1: ipaddrset sw 1 3 Set the password by using the following command: passwd <user_account> 4 Synchronize timestamps across the switch and controllers on the NTP server by using the following command: tsclockserver <ntp-ip-address>.123 5 Set the time zone for the switch by using the following command. Chapter 4: Configuring Switches 17 . which allows you to choose from lists of available selections: tstimezone --interactive 6 Set the idle timeout value for a switch login session by using the following command (the default is 10 minutes). contact your sales representative before proceeding.123.Step Action 2 Set the IP address for the switch by using the following command. <ntp-ip-address> For example: tsclockserver 123.123. ipaddrset sw <switch number> For example. timeout <minutes> For example: timeout 60 7 Display the licenses installed on the switch by entering the following command: licenseshow Result: You should have the following licenses: ◆ Fabric License (or two Domain Licenses) ◆ Extended Fabric License (for ISL distances over 10 km) If you do not have these licenses.

by entering the following command: switchname switch_name Note Use a name that is meaningful. such as node name and switch.brocade.com/storage/support/nas/ to identify the currently supported version of the switch firmware. 11 If your switch firmware is not the supported version. 9 Determine the switch firmware by entering the following command: version Result: The currently installed switch firmware is displayed.jsp and install it. as described in the Brocade switch hardware reference manual for your switch. Download the switch firmware from www. 18 10 Access the IBM N series Fabric MetroCluster Switch Interoperability Matrix at www. Configuring a switch . Reboot the switch.com/support/downloads.Step Action 8 Set the switch name. complete the following substeps: a.ibm. b. if needed.

you can use any unique number. 2. or 4. 1. set the switch parameters by completing the following steps. Step Action 1 Disable the switch by entering the following command: switchdisable 2 Clear any preexisting configuration by entering the following commands: cfgclear cfgdisable cfgsave 3 Configure the switch with default settings by entering the following command: configdefault 4 Set the switch parameters by entering the following command: configure Note The domain ID might be specified by your system administrator. You should set only the following parameters: ◆ ◆ Fabric parameters = y ❖ Domain_id = XXX ❖ Disable device probing = 1 Arbitrated Loop parameters = y ❖ Chapter 4: Configuring Switches Send FAN frames = 0 19 . 3. for example.Setting the switch parameters After performing the initial switch configuration. If not.

0. Step Action 1 Exit the configuration utility by entering the following command: ctrl-d 2 Reboot the switch so that the new settings take effect by entering the following command: fastboot 3 Log in to the switch and disable it by entering the following command: switchdisable 4 Complete the following substeps only for the ports to which disks are attached: a. Set all ports attached to disk loops to Locked L-Port by entering the following command for each port number: portCfgLPort <disk_port>.0. complete the configuration by performing these steps.0.Completing the configuration Steps After setting the switch parameters.1 20 Completing the configuration . Set all ports attached to disk loops to half duplex by entering the following command for each port number: portCfgLPort <disk_port>.1 b.1.

each switch port connected to an FC-VI adapter must be configured with a speed of 4Gbits per second using: portcfgspeed <port number>. Set the switch port speed by using the following command: portcfgspeed port_number. speed For example. or disk shelf loops. if each FC-VI adapter port supports 4Gbits per second. 4 6 Ensure that the disk loop port is showing ON in both the Locked L_Port and Locked Loop HD fields by entering the following commands: portCfgShow portCfglport Result: ON is displayed in both the Locked L_Port and Locked Loop HD fields. 7 If your switch has the trunking license installed. set the switch port speed to the actual speed supported by the FC-VI adapter ports. disable trunking on the ISL port by entering the following command: portcfgtrunkport <ISL_port#> 0 Chapter 4: Configuring Switches 21 . Note Switch ports attached to FC-VI adapters. the FC initiator adapter ports. FC initiator adapters and disk shelves loops cannot use speed auto-sensing mode. or the disk shelf ports. the FC initiator adapter ports or the disk shelves ports. The speed must be set to the actual speed supported by the FC-VI adapter ports. FC initiator adapters.Step Action 5 If you have switch ports that are attached to FC-VI adapters.

Then specify the distance.Step Action 8 To configure the long-distance ISL port for your ISL length. enter the following command: portcfglongdistance [slotnumber/portnumber] [distance_level] [VC_Translation_Link_Init] [desired_distance] distance_level is one of the following values: ◆ As a normal switch port. ◆ For distances beyond 10 km. use LO. ◆ For distances up to 10 km. or specify 0 to deactivate this mode. use LS. use LE. Specify 1 to activate longdistance link initialization sequence. you use the following command: portCfgLongDistance 13 LS 1 18 9 Enable the switch by entering the following command: switchenable 10 Verify that the switch settings are correct by entering the following command: configshow 22 Completing the configuration . Example: If your ISL length is 18 km and your ISL is connected to port 13.

Topics in this chapter This chapter discusses the following topics: Chapter 5: Switch Zoning ◆ “Zoning feature description” on page 24 ◆ “Configuring zones on the primary and secondary fabric” on page 25 23 .5 Switch Zoning About this chapter This chapter describes how to configure zones on the primary and secondary fabric of a switch.

The zoning license is enabled by default when the switches are shipped. 24 Zoning feature description . Zoning feature uses You can use the zoning feature to set up two or more zones on the same switch. you can isolate systems with different uses or protect systems in a heterogeneous environment. or zones. For example. You can use zones to provide controlled access to fabric segments and to establish barriers between operating environments.Zoning feature description Zoning feature requirements No additional license is needed for zoning. Zone members can access only other members of the same zone. over the physical configuration of the fabric. Zones let you arrange fabric-connected storage devices into logical groups.

Configuring zones on the primary and secondary fabric Configuration rules You need to create two zones on a switch—a zone for a Fibre Channel Virtual Interface (FCVI) from a local node to a remote node.ibm. and a second zone from the local node to local storage shelves. log in to switch 1. complete the following steps. search for the Active/Active Configuration Guide for your version of Data ONTAP at www. Note You cannot include the ISL port in a zone. You configure these zones on a primary and a secondary fabric. Chapter 5: Switch Zoning 25 . Step Action 1 Connect to a switch in the primary fabric by using the telnet command. For example.com/storage/support/nas . You can use any other port. Note You must configure the primary and the secondary fabrics separately. For more information. Configuring zones on the primary fabric To configure zones on the primary fabric of a switch.

zonecreate "STOR". cfgcreate "Zone_net".1. FCVI. "switch.port" zonename is the name of the zone. Example The following example creates a zone called "STOR" that includes switch 1 ports 1. 3.5.10.port zonename is the name of the zone.0" 3 Create a zone for the storage traffic from the local node to local disk shelves by entering the following command: zonecreate "zonename".Step Action 2 Create a zone for the FCVI traffic by entering the following command: zonecreate "zonename". 1.6. and 10. switch. "1.port. zonecreate "FCVI".port is the switch ID and port number you want to include in this zone.5. STOR 26 Configuring zones on the primary and secondary fabric . "1. 3. 5. switch.port is the switch ID and port number you want to include in this zone.6. 9.0. 3.9. port 0 on the remote node. switch. 5. 9. port 0 on the local node.1. 3.9. and 10.10" 4 Create the zoned configuration by entering the following command: cfgcreate "Zone_<name>" <zonename>. and switch 3. switch. 6. 6. <zonename> Enter the zoned configuration name followed by the names of the zones you created in the previous steps. and switch 3 ports 1. Example The following example creates a zoned configuration named “Zone_net” that includes the zones named FCVI and STOR. 3. 1. 3. 1. Example The following example creates a zone called “FCVI” that includes switch 1. 1.

cfgenable "Zone_net" Note Alternatively. 6 View the effective zoned configuration at any time by entering the following command: cfgshow Chapter 5: Switch Zoning 27 .Step Action 5 Save and enable the zoned configuration by entering the following command: cfgenable "Zone_<name>" Example The following example saves and enables the Zone_net zoned configuration. you can save the zoned configuration into flash memory by using the command sfgsave instead of cfgenable.

log in to switch 2.port zonename is the name of the zone.0" 28 Configuring zones on the primary and secondary fabric . For example. zonecreate "FCVI". Example The following example creates a zone called “FCVI” that connects switch 2. "2.0. you can use the same zone names on the primary and secondary fabrics for simplicity. Step Action 1 Connect to a switch in the secondary fabric by using the telnet command. port 0 on your remote node. 4. port 0 on your local node and switch 4. 2 Create a zone for the FCVI traffic by entering the following command: zonecreate "zonename". switch. Note Because switches 1 and 3 are on a different fabric than switches 2 and 4. Follow these steps.port is the switch ID and port number you want to include in this zone. switch.Configuring zones on the secondary fabric Repeat the previous procedure to configure zones on the secondary fabric.

4.member zonename is the name of the zone. Example The following example creates a zoned configuration named “Zone_net” that includes the zones named FCVI and STOR. 4.Step Action 3 Create a zone for the storage traffic from the local node to local disk shelves by entering the following command: zonecreate "zonename". 4.10. "2. 5. 9. STOR 5 Save and enable the zoned configuration by entering the following command: cfgenable "Zone_<name>" Example The following example saves and enables the Zone_net zoned configuration. 2. member. you can save the zoned configuration into flash memory by using the command cfgsave instead of cfgenable. 6. 2. 4. FCVI. 2. 6. 4. zonecreate "STOR".1. 2. Example The following example creates zone “STOR” that includes switch 2 ports 1.9.10" 4 Create the zoned configuration by entering the following command: cgfcreate "Zone_<name>" <zonename>. and 10. Chapter 5: Switch Zoning 29 . and 10.6.6. 9. 5. <zonename> Enter the zoned configuration name followed by the names of the zones you created in the previous steps.5. cfgenable "Zone_net" Note Alternatively.1.9. member is the switch ID and port number you want to include in this zone. and switch 4 ports 1. cfgcreate "Zone_net".5.

Step Action 6 View the effective zoned configuration at any time by entering the following command: cfgshow 30 Configuring zones on the primary and secondary fabric .

Topics in this chapter ◆ “Traffic Isolation feature description” on page 32 ◆ “TI zone configuration rules” on page 34 ◆ “TI zone command syntax” on page 41 ◆ “Configuring TI zones” on page 35 Chapter 6: Traffic Isolation 31 .6 Traffic Isolation About this chapter This chapter describes the Traffic Isolation (TI) features available for the switches. including TI zone failover. TI zone rules. and configuration of TI zones.

avoid interruption or congestion caused by storage traffic. The fabric also attempts to exclude traffic not in the TI zone from using ISLs within that TI zone. The TI feature enables you to control the flow of ISL traffic by creating a dedicated path for traffic flowing from a specific set of source ports (N_Ports).1 or later. Implementing traffic isolation involves using a special zone. which are considered high-priority traffic. TI feature requirements TI feature usage examples How TI zones work Note the following requirements for using the TI feature: ◆ The TI feature requires Data ONTAP 7. When you activate a TI zone. such as that for miroring NVRAM. ◆ When you want to force high-volume. host-to-target traffic such as cluster interconnect traffic. the fabric attempts to isolate all ISL traffic entering from a member of the zone to only those ISLs that are included in the zone.0b or later. low-priority traffic onto a particular ISL to limit the effect of this high traffic pattern on the fabric. called a TI zone. you can dedicate InterSwitch links (ISLs) to certain traffic. A TI zone indicates the set of ports and ISLs that will be used for a specific traffic flow. 32 Traffic Isolation feature description . You can use the TI feature in the following scenarios: ◆ When you want to dedicate an ISL to high-priority. ◆ Ports in a TI zone must belong to switches that run Brocade Fabric OS 6. The TI feature helps Fibre Channel Virtual Interface (FCVI) messages.2.6.0b and later.Traffic Isolation feature description Description of the TI feature In the Brocade Fabric Operating System 6.

traffic is not routed onto the nondedicated ISL and the TI-zoned route remains inoperable. Chapter 6: Traffic Isolation ◆ When a failed TI-zoned route is restored. traffic is routed onto the non-dedicated ISL. When failover is disabled in traffic flow with TI zones and the TI-zoned E_Port fails. When failover is enabled in traffic flow with TI zones. TI moves traffic to another E_Port in the same TI zone. 33 . failover is automatically enabled. the following occurs: ◆ A Registered State Change Notification is generated listing the path failure. but does not move traffic to an E_port outside of the TI zone. because it is the only available route. the TI zone failover setting determines the outcome. When paths within a TI zone go offline. If no other E_Ports are available in that TI zone. traffic is moved to another E_Port in the same TI zone. traffic is moved to another equivalent-cost E_Port. the following situations occur: ◆ If a TI-zoned route fails.TI zone failover operation Failover operation when TI zone failover is enabled The TI feature contains a TI zone failover setting that you can enable or disable. If you use the default settings when you create a TI zone. Failover operation when TI zone failover is disabled ◆ When a failed TI-zoned route is restored. if available. traffic automatically fails back to the original route and a Registered State Change Notification is generated listing the path restoration. if one is available. ◆ If the dedicated ISL fails. ◆ If the dedicated ISL fails. traffic is automatically failed back to the original route.

You cannot use other zoning commands. ◆ You use the zone command with options to create and modify TI zones.TI zone configuration rules Configuration rules for TI zones The following configuration rules apply to TI zones: ◆ A given N_Port can be a member of only a single TI zone. ◆ An E_Port can be a member of only a single TI zone. the various source ports for that zone are load balanced across the specified E_Ports. ◆ Each TI zone is interpreted by each switch. ◆ If multiple E_Ports on the lowest-cost route to a domain are configured. Inclusion of N_Ports is optional. The same checking is done as described for N_Ports. No consideration is given to the overall topology or to whether the TI zones accurately provide dedicated paths through the whole fabric. 34 TI zone configuration rules . such as zoneCreate. and each switch considers only the routing required for its local ports. ◆ The TI zones appear in the defined zone configuration only and do not appear in the effective zone configuration. aliCreate. A TI zone only provides Traffic Isolation and is not a “regular” zone. This rule is enforced during zone creation or modification. ◆ A TI zone must include a set (two or more) of E_Ports forming an end-toend path. and cfgCreate to manage TI zones.

and a storage zone. Ste p 1 Action Connect to a switch in the primary fabric by using the telnet command. The following sample procedure shows how to create a configuration that includes a TI zone. ◆ FCVI designates an FCVI zone.Configuring TI zones Configuring TI zones with failover enabled To create a TI zone with failover enabled and the TI zone activated on a primary fabric and a secondary fabric. complete the following steps. FCVI. zonetype" configuration name is the name you give the configuration and zonetype is the type of zone you want to include in the configuration. Note You must configure the zones in the primary and the secondary fabrics separately. Note The examples in this procedure correspond with the diagram shown in “Sample diagram of Brocade 300 16-port cabling” on page 13. and a storage zone: cfgcreate "Zone_net". ◆ FCVI_TI designates an FCVI TI zone. the following command creates a configuration named Zone_net that includes a TI zone. STOR" Chapter 6: Traffic Isolation 35 . 2 Create a configuration on the primary fabric by using the cfgcreate command: cfgcreate "configuration name". "zonetype. For example. log in to switch 1. "FCVI_TI. an FCVI zone. For example. an FCVI zone. zonetype. ◆ STOR designates a storage zone.

you can create the TI zone with failover disabled by including option d. For detailed command syntax. "switch. and switch 3.0.port. 3. "1. and switch.0" 36 Configuring TI zones . port 0 on the local node. and switch 3 ports 0 and 4.Ste p 3 Action Create the TI zone on the primary fabric by using the zone --create command. The following example creates a zone called FCVI that includes switch 1. 3. The example includes switch 1 ports 0 and 4.0. zone --create [-t objtype] [-o optionlist} zonename -p [portlist] The following example creates a TI zone called FCVI_TI with failover enabled and the TI zone activated. see “TI zone command syntax” on page 41. zonecreate "FCVI". see “TI zone command syntax” on page 41. zone --create -t ti "FCVI_TI" -p "1. so you do not have to enter them in the command.0. switch.port" zonename is the name of the zone.4" 4 Create the FCVI zone on the primary fabric by using the zonecreate command: zonecreate "zonename".4. For all options. Note Failover enabled (option f) and TI zone activated (option a) are default settings. 1.port is the switch ID and port number that you want to include in this zone. 3. port 0 on the remote node. Note Optionally.

and switch.9. 3. 3. "switch.1.5. 5.port" zonename is the name of the zone. 3. 6. "1. 1. and switch 3 ports 1. The following example creates a zone called "STOR" that includes switch 1 ports 1. 9. zonecreate "STOR". 3. 9. 1. 3. 10.10" 6 Save the configuration by using the cfgsave command: cfgsave 7 Commit all commands and enable the configuration by using the cfgenable command: cfgenable "configuration name" For example.5. and 10.port. 5.6. using the configuration name “Zone_net”: cfgenable "Zone_net" 8 Connect to a switch in the secondary fabric by using the telnet command.port is the switch ID and port number that you want to include in this zone. Chapter 6: Traffic Isolation 37 . 1.1.Ste p 5 Action Create the storage zone on the primary fabric by using the zonecreate command: zonecreate "zonename".6.10.9. switch. For example. 1. 6. log in to switch 2.

◆ FCVI designates an FCVI zone. FCVI. an FCVI zone.Ste p 9 Action Create a configuration on the secondary fabric by using the cfgcreate command: cfgcreate "configuration name". you can use the same zone names on the primary and secondary fabrics for simplicity. the following command creates a configuration named Zone_net that includes a TI zone. Note Because switches 1 and 3 are on a different fabric than switches 2 and 4. zonetype" configuration name is the name you give the configuration and zonetype is the type of zone you want to include in the configuration. zonetype. STOR" 38 Configuring TI zones . For example. and a storage zone: cfgcreate "Zone_net". ◆ STOR designates a storage zone. "FCVI_TI. ◆ FCVI_TI designates an FCVI TI zone. "zonetype.

see “TI zone command syntax” on page 41.port. "2. and switch 4. switch.0.port" zonename is the name of the zone. you can create the TI zone with failover disabled by including option d. and switch. For all options. Note Optionally. port 0 on the local node. zone --create [-t objtype] [-o optionlist} zonename -p [portlist] The following example creates a TI zone called FCVI_TI with failover enabled and the TI zone activated. "switch.Ste p 10 Action Create the TI zone on the secondary fabric by using the zone --create command.port is the switch ID and port number that you want to include in this zone. The following example creates a zone called FCVI that includes switch 2. see “TI zone command syntax” on page 41. zonecreate "FCVI". 2.4" 11 Create the FCVI zone on the secondary fabric by using the zonecreate command: zonecreate "zonename". 4. Note Failover enabled (option f) and TI zone activated (option a) are default settings.0" Chapter 6: Traffic Isolation 39 . zone --create -t ti "FCVI_TI" -p "2. port 0 on the remote node.0.4. 4. For detailed command syntax. 4. so you do not have to enter them in the command.0.

6. 9.9. using the configuration name “Zone_net”: cfgsave "Zone_net" 14 Commit all commands and enable the configuration by using the cfgenable command: cfgenable "configuration name" For example.5.9. switch. 2. The following example creates a zone called "STOR"that includes switch 2 ports 1. "switch. zonecreate "STOR". and switch 4 ports 1. 10. 4. 2.10. 5.Ste p 12 Action Create the storage zone on the secondary fabric by using the zonecreate command: zonecreate "zonename". "2. 2.6. 6. 2.6.1.port" zonename is the name of the zone.port is the switch ID and port number that you want to include in this zone. 5. using the configuration name “Zone_net”: cfgenable "Zone_net" 40 Configuring TI zones . 4. 4. 4. 4. and 10. 9.port.1.5.10" 13 Save the configuration by using the cfgsave command: cfgsave "configuration name" For example. and switch.

Note zone commands are used only with the TI feature. You use ti to specify a TI zone. -p portlist is the list of ports to be included in the TI zone. not with existing zoning. so you do not have to enter them in the command. ❖ a means activate ❖ d means deactivate ❖ n means disable failover ❖ f means enable failover zonename is the name that you want to give to the TI zone. You designate ports by using the “domain. ◆ You can activate a TI zone by entering the following command: zone --activate <zonename> ◆ You can deactivate a zone by entering the following command: zone --deactivate <zonename> Chapter 6: Traffic Isolation 41 . followed by a space. Note Failover enabled (option f) and TI zone activated (option a) are default settings. index” format. -o optionlist is a list of options for activating the zone and controlling failover mode. ◆ You can create a TI zone with specified options and port list by entering the following command: zone --create [-t objtype] [-o optionlist} zonename -p [portlist] -t objtype is the type of zone. Note A cfgenable command is required to commit all TI zone commands. Multiple ports are separated by a semicolon.TI zone command syntax TI zone command syntax You can use the following commands when configuring TI zoning.

◆ You can delete TI zones from the defined configuration by entering the following command: zone --delete <zonename> ◆ You can view the effective TI zone configuration at any time by entering the following command: zone --show 42 TI zone command syntax .

failover enabled 35 failover disabled 33 failover enabled 33 overview 32 43 .Index Numerics M 16-port cabling for Brocade 300 13 16-port cabling for Brocade 5100 14 8-port cabling for Brocade 300 12 mapping virtual channels to physical ports 11 MetroCluster overview 2 B Brocade 300 ports 6 Brocade 5100 ports 7 C command syntax for TI feature 41 configuring zoning feature on primary fabric 25 configuring zoning feature on secondary fabric 28 conventions keyboard xiii text formatting xii P parameters for switch configuration 19 ports Brocade 300 6 Brocade 5100 7 diagram. definition 2 T text formatting conventions xii TI zones overview 32 traffic isolation feature command syntax 41 configuring TI zones. Brocade 5100 7 trunk groups 6 R Data ONTAP requirements 2 requirements Data ONTAP 2 SFPs 2 Virtual Channel feature 10 rules for TI zone configuration 34 rules for zoning feature 25 E S D equivalent product names for IBM ix F fabric-attached MetroCluster overview 2 sample diagram 2 FilerView xi I IBM switch names ix initial switch configuration 16 K keyboard conventions xiii Index SFP requirements 2 switch configuration completing 20 initial 16 parameters 19 switch fabric. Brocade 300 6 diagram.

primary fabric 25 configuration procedure. secondary fabric 28 configuration rules 25 requirements 24 Index .requirements 32 TI zones configuration rules 34 TI zones overview 32 V virtual channel feature cabling diagram for 16-port 13 cabling diagram for 16-port Brocade 5100 14 cabling diagram for 8-port 12 mapping to physical ports 11 44 overview 10 requirements 10 Z zoning feature advantages 24 configuration procedure.

your IBM business partner. you grant IBM a nonexclusive right to use or distribute your comments in any way it believes appropriate without incurring any obligation to you. subject matter. accuracy. When you send comments to IBM.Readers’ Comments — We’d Like to Hear from You IBM System Storage N series Brocade 300 and Brocade 5100 Switch Configuration Guide Publication No. or completeness of this book. Please comment on specific errors or omissions. please contact your IBM branch office. GC53-1167-00 We appreciate your comments about this publication. IBM or any other organizations will only use the personal information that you supply to contact you about the issues that you state on this form. please fill in the following information: Name Address Company or Organization Phone No. Comments: Thank you for your support. For technical questions and information about products and prices. or your authorized remarketer. Send your comments to the address on the reverse side of this form. If you would like a response from IBM. The comments you send should pertain to only the information in this manual or product and the way in which the information is presented. E-mail address . organization.

AZ U.S.GC53-1167-00 ??? _________________________________________________________________________________ Readers’ Comments — We’d Like to Hear from You Cut or Fold Along Line Fold and Tape Please do not staple Fold and Tape __________________________________________________________________________ NO POSTAGE NECESSARY IF MAILED IN THE UNITED STATES BUSINESS REPLY MAIL FIRST-CLASS MAIL PERMIT NO. NEW YORK POSTAGE WILL BE PAID BY ADDRESSEE International Business Machines Corporation Information Development Dept. 40 ARMONK. 85744-0001 __________________________________________________________________________ Fold and Tape GC53-1167-00 Please do not staple Fold and Tape Cut or Fold Along Line . GZW 9000 South Rita Road Tucson.A.

.

??? NA 210-04419_A0. Printed in USA GC53-1167-00 .