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

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

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

vi Notices . or service that does not infringe on any IBM intellectual property right may be used instead. this statement may not apply to you. therefore. For additional information. Some states do not allow disclaimer of express or implied warranties in certain transactions.Y. it is the user’s responsibility to evaluate and verify the operation of any non-IBM product. program. 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. program. program. INCLUDING. BUT NOT LIMITED TO. program.S. However. IBM may not offer the products.ibm.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. Changes are periodically made to the information herein. EITHER EXPRESS OR IMPLIED. in writing to: IBM Director of Licensing IBM Corporation North Castle Drive Armonk. MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Any reference to an IBM product. services. This information could include technical inaccuracies or typographical errors.S. or features discussed in this document in other countries.A.A. 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. IBM may have patents or pending patent applications covering subject matter described in this document. 10504-1785 U. or service. The furnishing of this document does not give you any license to these patents. 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. You can send license inquiries. these changes will be incorporated in new editions of the publication.Notices This information was developed for products and services offered in the U. or service is not intended to state or imply that only that IBM product. or service may be used. Consult your local IBM representative for information on the products and services currently available in your area. Any functionally equivalent product. THE IMPLIED WARRANTIES OF NON-INFRINGEMENT.

compatibility or any other claims related to non-IBM products. Furthermore. Any performance data contained herein was determined in a controlled environment. Actual results may vary. the results obtained in other operating environments may vary significantly. Information concerning non-IBM products was obtained from the suppliers of those products. Notices vii . If you are viewing this information in softcopy. Users of this document should verify the applicable data for their specific environment. some measurement may have been estimated through extrapolation. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products. the photographs and color illustrations may not appear. Therefore. 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. 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. IBM has not tested those products and cannot confirm the accuracy of performance.

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

routing. 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. it emphasizes the characteristics of the storage system. CIFS. 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. Some features described in the product software documentation are neither offered nor supported by IBM. It also assumes that you are familiar with how to configure the storage system and how the NFS. Information about supported features can also be found at the following Web site: www. This guide does not cover basic system or network administration topics. The guide also describes how to cable virtual channels and how to use zoning and traffic isolation zoning. Linux®. and Windows® 2003.ibm. Please contact your local IBM representative or reseller for further details. Supported features IBM System Storage™ N series systems and expansion boxes are driven by NetApp® Data ONTAP® software. such as UNIX®.com/storage/support/nas/ Preface xi . and network topology. such as IP addressing. and HTTP protocols are used for file sharing or transfers. 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.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.

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.com/storage/nas/ ◆ For NAS support information. go to the following Web site: www.com/storage/support/nas/ xii . you will find a wide variety of sources available from IBM to assist you.com/storage/nas/ Getting information. help. ◆ For NAS product information. or technical assistance or just want more information about IBM products. service. ◆ Use an IBM discussion forum on the IBM Web site to ask questions. ◆ Use the troubleshooting information in your system documentation and use the diagnostic tools that come with your system. 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.com/storage/support/nas/ Data ONTAP software publications are available as PDF files on the IBM NAS support Web site: www. ◆ Check the power switches to make sure that the system is turned on. and whom to call for service. go to the following Web site: www.ibm.A listing of currently available N series products and features can be found at 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. and service If you need help. what to do if you experience a problem with your IBM System Storage N series product. The same documentation is available as PDF files on the IBM NAS support Web site: www.ibm. Before you call Before you call. This section contains information about where to go for additional information about IBM and IBM products. if it is necessary.ibm.

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

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

or loss of data. type Used to mean pressing one or more keys on the keyboard. 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. What is in this guide… What it means… hyphen (-) Used to separate individual keys. Ctrl-D means holding down the Ctrl key while pressing the D key.Keyboard conventions Special messages This guide uses capitalization and some abbreviations to refer to the keys on the keyboard. 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. a system crash. Preface xv . For example. the key is named Return on some keyboards. Enter Used to refer to the key that generates a carriage return. Attention An attention notice contains instructions that you must follow to avoid damage to the equipment.

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

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

2. When the distance between the two systems is greater than 500 meters. Description of a MetroCluster configuration The MetroCluster configuration uses two storage systems that are connected to provide high availability and data mirroring. Note Do not mix switch models within a single fabric-attached MetroCluster or across a fabric-attached MetroCluster. as shown in the following illustration.5. you use four Fibre Channel switches in a fabric configuration to connect the two systems. You can place these two systems in different locations.6 and later ◆ 7.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.1 ◆ 7. The two switches are connected to each other through long-distance Inter-Switch Link (ISL) cables. or 1 Gbit per second. 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.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.2. 2 Fabric MetroCluster Switch Overview . Definition of MetroCluster switch fabrics A fabric-attached MetroCluster contains two switch fabrics. 2 Gbit. This configuration is called a fabric-attached MetroCluster.

Dual Fabric Metro Cluster Fabric 1 SW1 SW3 Fabric 2 SW2 Chapter 1: Fabric MetroCluster Overview SW4 3 . connected through a second ISL cable to the second switch (Switch 4) on the remote node.Sample diagram of a MetroCluster switch fabric For example. The second fabric is created using Switch 2 on the local node. This example is illustrated in the following diagram. 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.

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 .

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

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 4 Gbits per second. Ports 0 through 23 are enabled by default. 2. The ports auto-sense link speeds and support transfer rates of 1. See the following diagram for port numbering. or storage loops. 2. but can be licensed as an 24-port switch. FC initiator adapter ports. See “Completing the configuration” on page 20. and 4 Gbits per second. or a 40-port switch. 4Gbit SFPs support only the transfer rates 1.Ports and port groups in the Brocade 5100 switch The Brocade 5100 switch has 40 ports. the 8 Gbit SFPs support only the transfer rates 2 or 4 Gbits per second. 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 . Note You cannot use the auto-sensing speed mode with switch ports that are connected to FC-VI adapter ports. Ports 24 through 31 and ports 32 through 39 can also be licensed. Note If you are using SFPs with the switches. a 32-port switch.

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.

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

13. The eight virtual channels are numbered 0 through 7. 15. 17. 14. 21. 34. 14. 24. 21 1. 9. 5. 25. 10. 11. 10. 19. 23. 25. 37 Storage traffic 4 2. 4 0. 18. 14 2. 8. 12. 23 3. 6. 9. 20. 22 2. 16. 8. 28. 18. 15. 31. 17. 22. 9. 5. 19. 11. 12. 5. 21. 7. 5. 9. 6. 6. 20. 6. 11. 13.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. 39 Storage traffic Chapter 3: Virtual Channel Cabling Usage 11 . 35. 4. 26. 38 Storage traffic 5 3. 10. 32. 36 Interconnect and ISL traffic 3 1. 5 1. 7. 13 1. 15 3. 4. 27. 26. 20 0. 16. 19. 12. 7 3. 13. 15. depending on how many of your switch ports are enabled. 24. 7. 4. 8. 4. 14. 7. 11. 23. 30 2. 28 0. 17. 33. 22. 8. 31 3. 16. 10. 18. 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. 29 1. 12 0. You can use virtual channels 2 through 5 for either Class 2 or Class 3 data traffic. 30. 29. 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. 27. 6 2.

You should spread disk shelves across ports before adding a second shelf to each loop. 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 .

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

14 Virtual channel cabling . . 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.

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.

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. complete the following steps. 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. see the Brocade Fabric OS Command Reference Manual Supporting Fabric OS 6. using the switch IP address. using the console port and your Windows HyperTerminal application (not available in Windows Vista versions). note the following information: Configuring a switch initially ◆ These procedures must be performed on each switch in the MetroCluster configuration. Step Action 1 If this switch has not been configured before. ◆ 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 . Note For all of the Brocade switch commands. log in to the switch. and set the following values.1 for information about command syntax and options. To configure a switch initially.

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. 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. <ntp-ip-address> For example: tsclockserver 123. contact your sales representative before proceeding. Chapter 4: Configuring Switches 17 .Step Action 2 Set the IP address for the switch by using the following command. ipaddrset sw <switch number> For example.123. 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).123.

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

for example. 3. you can use any unique number. 2. or 4. 1.Setting the switch parameters After performing the initial switch configuration. 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. If not. set the switch parameters by completing the following steps. 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 .

complete the configuration by performing these steps.1 b.0.0.0.Completing the configuration Steps After setting the switch parameters. 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>.1.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>.

the FC initiator adapter ports. 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. set the switch port speed to the actual speed supported by the FC-VI adapter ports. FC initiator adapters and disk shelves loops cannot use speed auto-sensing mode. The speed must be set to the actual speed supported by the FC-VI adapter ports. FC initiator adapters. the FC initiator adapter ports or the disk shelves ports.Step Action 5 If you have switch ports that are attached to FC-VI adapters. Set the switch port speed by using the following command: portcfgspeed port_number. or disk shelf loops. Note Switch ports attached to FC-VI adapters. or the disk shelf ports. 7 If your switch has the trunking license installed. each switch port connected to an FC-VI adapter must be configured with a speed of 4Gbits per second using: portcfgspeed <port number>. speed For example. if each FC-VI adapter port supports 4Gbits per second. disable trunking on the ISL port by entering the following command: portcfgtrunkport <ISL_port#> 0 Chapter 4: Configuring Switches 21 .

◆ For distances beyond 10 km. or specify 0 to deactivate this mode. ◆ For distances up to 10 km. 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.Step Action 8 To configure the long-distance ISL port for your ISL length. Then specify the distance. use LO. use LS. 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 . Specify 1 to activate longdistance link initialization sequence. Example: If your ISL length is 18 km and your ISL is connected to port 13. use LE.

5 Switch Zoning About this chapter This chapter describes how to configure zones on the primary and secondary fabric of a switch. 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 .

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

You can use any other port.com/storage/support/nas . search for the Active/Active Configuration Guide for your version of Data ONTAP at www. log in to switch 1. and a second zone from the local node to local storage shelves. You configure these zones on a primary and a secondary fabric. Note You cannot include the ISL port in a zone. For example. complete the following steps. Chapter 5: Switch Zoning 25 . Note You must configure the primary and the secondary fabrics separately. Configuring zones on the primary fabric To configure zones on the primary fabric of a switch. Step Action 1 Connect to a switch in the primary fabric by using the telnet command. For more information.ibm.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.

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

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. cfgenable "Zone_net" Note Alternatively. you can save the zoned configuration into flash memory by using the command sfgsave instead of cfgenable.

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

5. 4. 5.5. Example The following example creates a zoned configuration named “Zone_net” that includes the zones named FCVI and STOR. 9. 6. 2. 5. 2.1. "2. 4. 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. 6. Example The following example creates zone “STOR” that includes switch 2 ports 1. 4. and switch 4 ports 1. cfgenable "Zone_net" Note Alternatively.6. cfgcreate "Zone_net". 4. you can save the zoned configuration into flash memory by using the command cfgsave instead of cfgenable. 4. member is the switch ID and port number you want to include in this zone.9.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". and 10.10.6. 2.10" 4 Create the zoned configuration by entering the following command: cgfcreate "Zone_<name>" <zonename>.1. 9. FCVI. <zonename> Enter the zoned configuration name followed by the names of the zones you created in the previous steps.member zonename is the name of the zone. zonecreate "STOR".9. member. and 10. Chapter 5: Switch Zoning 29 . 2.

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 .

6 Traffic Isolation About this chapter This chapter describes the Traffic Isolation (TI) features available for the switches. and configuration of TI zones. 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 . TI zone rules. including TI zone failover.

0b and later.0b or later. A TI zone indicates the set of ports and ISLs that will be used for a specific traffic flow.2. called a TI zone. The TI feature helps Fibre Channel Virtual Interface (FCVI) messages. host-to-target traffic such as cluster interconnect traffic.Traffic Isolation feature description Description of the TI feature In the Brocade Fabric Operating System 6. low-priority traffic onto a particular ISL to limit the effect of this high traffic pattern on the fabric. you can dedicate InterSwitch links (ISLs) to certain traffic. avoid interruption or congestion caused by storage traffic. Implementing traffic isolation involves using a special zone. which are considered high-priority traffic. 32 Traffic Isolation feature description . The fabric also attempts to exclude traffic not in the TI zone from using ISLs within that TI zone. 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.1 or later. such as that for miroring NVRAM. 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. ◆ Ports in a TI zone must belong to switches that run Brocade Fabric OS 6. ◆ When you want to force high-volume. 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).6. You can use the TI feature in the following scenarios: ◆ When you want to dedicate an ISL to high-priority.

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

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

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

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

6. 5.port. zonecreate "STOR". 3.5. For example.6.9. switch. 1. and switch. log in to switch 2. 9.port" zonename is the name of the zone.10. 3. 1. 6. 6. and switch 3 ports 1.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. using the configuration name “Zone_net”: cfgenable "Zone_net" 8 Connect to a switch in the secondary fabric by using the telnet command.5. 3. "1.1. 10.Ste p 5 Action Create the storage zone on the primary fabric by using the zonecreate command: zonecreate "zonename".9. 5. The following example creates a zone called "STOR" that includes switch 1 ports 1. "switch. 9. 3. Chapter 6: Traffic Isolation 37 . 1.1. 1. and 10.port is the switch ID and port number that you want to include in this zone. 3.

the following command creates a configuration named Zone_net that includes a TI zone. ◆ STOR designates a storage zone. STOR" 38 Configuring TI zones . "FCVI_TI. For example. Note Because switches 1 and 3 are on a different fabric than switches 2 and 4. you can use the same zone names on the primary and secondary fabrics for simplicity. 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. FCVI. ◆ FCVI designates an FCVI zone. and a storage zone: cfgcreate "Zone_net". ◆ FCVI_TI designates an FCVI TI zone. "zonetype.Ste p 9 Action Create a configuration on the secondary fabric by using the cfgcreate command: cfgcreate "configuration name". an FCVI zone.

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

4. 9. 6. switch. "2. 4. 2. 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.port.10" 13 Save the configuration by using the cfgsave command: cfgsave "configuration name" For example. 5. 9. using the configuration name “Zone_net”: cfgenable "Zone_net" 40 Configuring TI zones . 4.6.1.9. 6.9. 5.port" zonename is the name of the zone. "switch. 2. and 10.port is the switch ID and port number that you want to include in this zone. 10. 2.6. and switch 4 ports 1. and switch. zonecreate "STOR".5.1.Ste p 12 Action Create the storage zone on the secondary fabric by using the zonecreate command: zonecreate "zonename". 2. 4. The following example creates a zone called "STOR"that includes switch 2 ports 1.10. 4.

-p portlist is the list of ports to be included in the TI zone. You designate ports by using the “domain. Note Failover enabled (option f) and TI zone activated (option a) are default settings. -o optionlist is a list of options for activating the zone and controlling failover mode. followed by a space. index” format. ◆ 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. so you do not have to enter them in the command. You use ti to specify a TI zone. Note A cfgenable command is required to commit all TI zone commands. ❖ 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.TI zone command syntax TI zone command syntax You can use the following commands when configuring TI zoning. ◆ 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 . not with existing zoning. Note zone commands are used only with the TI feature. Multiple ports are separated by a semicolon.

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

definition 2 T text formatting conventions xii TI zones overview 32 traffic isolation feature command syntax 41 configuring TI zones.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. 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. failover enabled 35 failover disabled 33 failover enabled 33 overview 32 43 .

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.

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

A. NEW YORK POSTAGE WILL BE PAID BY ADDRESSEE International Business Machines Corporation Information Development Dept.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. 40 ARMONK. AZ U. GZW 9000 South Rita Road Tucson. 85744-0001 __________________________________________________________________________ Fold and Tape GC53-1167-00 Please do not staple Fold and Tape Cut or Fold Along Line .S.

.

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