Data ONTAP 7.

2
Brocade 3000 Series
Switch Configuration Guide
NetApp, Inc.
495 East Java Drive
Sunnyvale, CA 94089 U.S.A.
Telephone: +1 (408) 822-6000
Fax: +1 (408) 822-4501
Support telephone: +1 (888) 4-NETAPP
Documentation comments: doccomments@netapp.com
Information Web: http://www.netapp.com
Part number 215-03781_A0
Updated for Data ONTAP 7.2.5 on 5 May 2008
ii Copyright and trademark information
Copyright and trademark information
Copyright
information
Copyright 19942008 NetApp, Inc. All rights reserved. Printed in the U.S.A.
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 systemwithout 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
19801995 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:
1. Redistributions of source code must retain the above copyright notices, this list of conditions,
and the following disclaimer.
2. 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.
3. All advertising materials mentioning features or use of this software must display this text:
This product includes software developed by the University of California, Berkeley and its
contributors.
4. 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.
Copyright and trademark information iii
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 19951998, 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. NetApp modified the libxml2 software on December 6, 2001, to
enable it to compile cleanly on Windows, Solaris, and Linux. The changes have been sent to the
maintainers of libxml2. The unmodified libxml2 software can be downloaded from
http://www.xmlsoft.org/.
Copyright 19942002 World Wide Web Consortium, (Massachusetts Institute of Technology,
Institut National de Recherche en Informatique et en Automatique, Keio University). All Rights
Reserved. http://www.w3.org/Consortium/Legal/
Software derived from copyrighted material of the World Wide Web Consortium is subject to the
following license and disclaimer:
Permission to use, copy, modify, and distribute this software and its documentation, with or without
modification, for any purpose and without fee or royalty is hereby granted, provided that you include
the following on ALL copies of the software and documentation or portions thereof, including
modifications, that you make:
The full text of this NOTICE in a location viewable to users of the redistributed or derivative work.
Any pre-existing intellectual property disclaimers, notices, or terms and conditions. If none exist, a
short notice of the following form (hypertext is preferred, text is permitted) should be used within the
body of any redistributed or derivative code: Copyright [$date-of-software] World Wide Web
Consortium, (Massachusetts Institute of Technology, Institut National de Recherche en Informatique
et en Automatique, Keio University). All Rights Reserved. http://www.w3.org/Consortium/Legal/
Notice of any changes or modifications to the W3C files, including the date changes were made.
THIS SOFTWARE AND DOCUMENTATION IS PROVIDED AS IS, AND COPYRIGHT
HOLDERS MAKE NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO, 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, COPYRIGHTS,
TRADEMARKS OR OTHER RIGHTS.
COPYRIGHT HOLDERS WILL NOT BE LIABLE FOR ANY DIRECT, INDIRECT, SPECIAL OR
CONSEQUENTIAL DAMAGES ARISING OUT OF ANY USE OF THE SOFTWARE OR
DOCUMENTATION.
iv Copyright and trademark information
The name and trademarks of copyright holders may NOT be used in advertising or publicity
pertaining to the software without specific, written prior permission. Title to copyright in this
software and any associated documentation will at all times remain with copyright holders.
Software derived from copyrighted material of NetApp, Inc. is subject to the following license and
disclaimer:
NetApp reserves the right to change any products described herein at any time, and without notice.
NetApp assumes no responsibility or liability arising from the use of products described herein,
except as expressly agreed to in writing by NetApp. The use or purchase of this product does not
convey a license under any patent rights, trademark rights, or any other intellectual property rights of
NetApp.
The product described in this manual may be protected by one or more U.S.A. patents, foreign
patents, or pending applications.
RESTRICTED RIGHTS LEGEND: Use, duplication, 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.277-7103 (October 1988) and FAR 52-227-19 (June 1987).
Trademark
information
NetApp, the Network Appliance logo, the bolt design, NetAppthe Network Appliance Company,
DataFabric, Data ONTAP, FAServer, FilerView, FlexClone, FlexVol, Manage ONTAP, MultiStore,
NearStore, NetCache, NOW NetApp on the Web, SecureShare, SnapDrive, SnapLock, SnapManager,
SnapMirror, SnapMover, SnapRestore, SnapValidator, SnapVault, Spinnaker Networks, SpinCluster,
SpinFS, SpinHA, SpinMove, SpinServer, StoreVault, SyncMirror, Topio, VFM, and WAFL are
registered trademarks of NetApp, Inc. in the U.S.A. and/or other countries. Cryptainer, Cryptoshred,
Datafort, and Decru are registered trademarks, and Lifetime Key Management and OpenKey are
trademarks, of Decru, a NetApp, Inc. company, in the U.S.A. and/or other countries. SANScreen is a
registered trademark of Onaro, Inc., a NetApp, Inc. company, in the U.S.A. and/or other countries.
gFiler, Network Appliance, SnapCopy, Snapshot, and The evolution of storage are trademarks of
NetApp, Inc. in the U.S.A. and/or other countries and registered trademarks in some other countries.
The NetApp arch logo; the StoreVault logo; ApplianceWatch; BareMetal; Camera-to-Viewer;
ComplianceClock; ComplianceJournal; ContentDirector; ContentFabric; EdgeFiler; FlexShare;
FPolicy; Go Further, Faster; HyperSAN; InfoFabric; LockVault; NOW; ONTAPI; RAID-DP;
ReplicatorX; RoboCache; RoboFiler; SecureAdmin; Serving Data by Design; SharedStorage;
Simplicore; Simulate ONTAP; Smart SAN; SnapCache; SnapDirector; SnapFilter; SnapMigrator;
SnapSuite; SohoFiler; SpinMirror; SpinRestore; SpinShot; SpinStor; vFiler; VFM Virtual File
Manager; VPolicy; and Web Filer are trademarks of NetApp, Inc. in the U.S.A. and other countries.
NetApp Availability Assurance and NetApp ProTech Expert are service marks of NetApp, Inc. in the
U.S.A.
IBM, the IBM logo, AIX, and System Storage are trademarks and/or registered trademarks of
International Business Machines Corporation.
Apple is a registered trademark and QuickTime is a trademark of Apple, Inc. in the U.S.A. and/or
other countries. Microsoft is a registered trademark and Windows Media is a trademark of Microsoft
Corporation in the U.S.A. and/or other countries. RealAudio, RealNetworks, RealPlayer,
RealSystem, RealText, and RealVideo are registered trademarks and RealMedia, RealProxy, and
SureStream are trademarks of RealNetworks, Inc. in the U.S.A. and/or other countries.
All other brands or products are trademarks or registered trademarks of their respective holders and
should be treated as such.
NetApp, Inc. is a licensee of the CompactFlash and CF Logo trademarks.
NetApp, Inc. NetCache is certified RealSystem compatible.
Table of Contents
Table of Contents v
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii
Chapter 1 Brocade MetroCluster Overview. . . . . . . . . . . . . . . . . . . . . . . . 1
Brocade 3000 series MetroCluster . . . . . . . . . . . . . . . . . . . . . . . . 2
Chapter 2 Brocade Switch Cabling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Cabling a Brocade 3000 series switch . . . . . . . . . . . . . . . . . . . . . . 6
Brocade 3000 series switches. . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Chapter 3 Brocade 3000 Series Switch Configuration . . . . . . . . . . . . . . . . . . 9
Configuring Brocade switches . . . . . . . . . . . . . . . . . . . . . . . . . 10
Completing the configuration. . . . . . . . . . . . . . . . . . . . . . . . . . 13
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
vi Table of Contents
Preface vii
Preface
About this guide
This guide describes how Brocade 3000 series switch models operate with a Met-
roCluster, how to configure a Brocade switch in a fabric-attached MetroCluster,
and how to set up a fabric-attached MetroCluster.
Audience This guide is for system administrators who are familiar with operating systems
that run on the storage systems clients, such as UNIX

, Linux

, and Windows

2003. It also assumes that you are familiar with how to configure the storage
system and how the NFS, CIFS, and HTTP protocols are used for file sharing or
transfers. This guide does not cover basic system or network administration
topics, such as IP addressing, routing, and network topology; it emphasizes the
characteristics of the storage system.
Terminology
Storage systems that run Data ONTAP

are sometimes also referred to as

appliances, storage appliances, or systems. The name of the graphical user
interface for Data ONTAP (FilerView) reflects one of these common usages.
FilerView as an
alternative to
commands
As a storage system administrator, you can perform tasks by entering commands
at the console, in configuration files, or through a Telnet session or Remote Shell
connection.
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. FilerView is easy to use, and it includes Help that explains FilerView
features and how to use them.
For more information about accessing a storage system using FilerView, and
about FilerView Help, see the Storage Management Guide.
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, the command syntax
and output might differ, depending on your version of UNIX.
viii
Formatting
conventions
The following table lists different character formats used in this guide to set off
special information.
Keyboard
conventions
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.
Formatting
convention Type of information
Italic type Words or characters that require special attention.
Placeholders for information you must supply.
For example, if the guide requires you to enter the
fctest adaptername command, you enter the
characters fctest followed by the actual name of
the adapter.
Book titles in cross-references.
Monospaced font Command and daemon names.
Information displayed on the system console or
other computer monitors.
The contents of files.
Bold monospaced
font
Words or characters you type. What you type is
always shown in lowercase letters, unless your
program is case-sensitive and uppercase letters are
necessary for it to work properly.
What is in this guide What it means
hyphen (-) Used to separate individual keys. For example,
Ctrl-D means holding down the Ctrl key while
pressing the D key.
Enter Used to refer to the key that generates a carriage
return; the key is named Return on some
keyboards.
type Used to mean pressing one or more keys on the
keyboard.
enter Used to mean pressing one or more keys and then
pressing the Enter key.
Preface ix
Special messages 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.
Attention
An attention notice contains instructions that you must follow to avoid damage to
the equipment, a system crash, or loss of data.
x
Chapter 1: Brocade MetroCluster Overview 1
1
Brocade MetroCluster Overview
About this chapter This chapter describes a Brocade switch MetroCluster and defines a switch
fabric.
Topics in this
chapter
This chapter discusses the following topic:
Description of a MetroCluster configuration on page 2
2 Brocade 3000 series MetroCluster

Brocade 3000 series MetroCluster
Description of a
MetroCluster
configuration
The MetroCluster configuration uses two storage systems that are connected to
provide high availability and data mirroring.You can place these systems in
different locations. When the distance between the two systems is greater than
500 meters, use four Brocade Fibre Channel switches in a fabric configuration to
connect the two systems. This configuration is called a fabric-attached
MetroCluster.
Switch fabrics A fabric-attached MetroCluster contains two switch fabrics. A switch fabric
consists of a switch on the local half of the cluster connected to a switch on the
remote half of the cluster. The two switches are connected to each other through
long-distance Inter-Switch Link (ISL) cables, as shown in the following diagram.
For example, consider a 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. The second fabric is
created using Switch 2 on the local node, connected through a second ISL cable
to the second switch (Switch 4) on the remote node.
Note
Each fabric supports only one ISL.
Chapter 1: Brocade MetroCluster Overview 3

Dual Fabric Metro Cluster
Fabric 1
Fabric 2
SW2 SW4
SW3 SW1
4 Brocade 3000 series MetroCluster

Chapter 2: Brocade Switch Cabling 5
2
Brocade Switch Cabling
About this chapter This chapter illustrates how to cable Brocade 3000 series switches.
Topics in this
chapter
This chapter discusses the following topics:
Cabling a Brocade 3000 series switch on page 6
Brocade 3000 series switches on page 8
6 Cabling a Brocade 3000 series switch

Cabling a Brocade 3000 series switch
Diagram of a
Brocade switch
cabled through the
switch fabric
The following illustration shows how the local storage system and the remote
storage system are cabled together through the switch fabric. This diagram is for
storage systems that support hardware-based disk ownership.
Pool
0
Local
Shelf
1
Out In
In Out
A
B
Pool
0
Local
Shelf
2
Out In
In Out
A
B
Pool
1
Remote
Shelf 1
Mirror
Out In
In Out
A
B
Pool
1
Remote
Shelf 2
Mirror
Out In
In Out
A
B
Pool
0
Local
Shelf
1
Out In
In Out
A
B
Pool
0
Local
Shelf
2
Out In
In Out
A
B
Pool
1
Remote
Shelf 1
Mirror
Out In
In Out
A
B
Pool
1
Remote
Shelf 2
Mirror
Out In
In Out
A
B
SW1
Pool
0
1
1 0 2 3 9 8 10 11
5 4 6 7 13 12 14 15
SW3
SW2 SW4
Long
Haul
FC
Equipment
Local Node Remote Node
Pool
0
1
1 0 2 3 9 8 10 11
5 4 6 7 13 12 14 15
Pool
0
1
1 0 2 3 9 8 10 11
5 4 6 7 13 12 14 15
Pool
0
1
1 0 2 3 9 8 10 11
5 4 6 7 13 12 14 15
Chapter 2: Brocade Switch Cabling 7

Switch banks and
quadrants
The Fibre Channel switches are divided into banks and quadrants. Each switch
has two banks, that divide the switch into two equal parts. (See the switch
illustrations that follow.)
The banks are further divided into two quadrants of two or four ports each
(depending on the number of ports in the switch). These quadrants combine to
form pools, which function the same way in a fabric-attached MetroCluster as in
a mirrored cluster. Quadrants 1 and 3 belong to Pool 0, and Quadrants 2 and 4
belong to Pool 1. Each switch bank contains a Pool 0 and a Pool 1.
8 Brocade 3000 series switches

Brocade 3000 series switches
Switches in the
Brocade 3000 series
The Brocade 3000 series of switches includes the Brocade 3800 and 3850
switches and the Brocade 3200 and 3250 switches.
16-port switches The Brocade 3800 and 3850 switches are 16-port switches and have ports 0
through 15 licensed and operational, as shown in the following 16-port switch
illustration.
8-port switches The Brocade 3200 and 3250 switches are 8-port switches and have eight ports, as
shown in the following illustration.
Chapter 3: Brocade 3000 Series Switch Configuration 9
3
Brocade 3000 Series Switch Configuration
About this chapter This chapter contains configuration information for the Brocade 3000 series
switches.
Topics in this
chapter
This chapter discusses the following topics:
Configuring Brocade switches on page 10
Completing the configuration on page 13
10 Configuring Brocade switches

Configuring Brocade switches
Points to know
before you begin
To configure a Brocade 3000 series switch for a fabric-attached MetroCluster
configuration, complete the following procedures.
Note
You must perform these procedures on each switch in the MetroCluster
configuration.
Use these procedures instead of the switch configuration procedure in the Cluster
Installation and Administration Guide or the Active/Active Configuration
Installation and Administration Guide.
Configuring a
switch
To configure a switch, complete the following steps.
Step Action
1 If this switch has not been configured before, log in to the switch,
using the console port and your Windows HyperTerminal application
(not available in Windows Vista versions), and set the following
values, as described in the Brocade switch hardware reference
manual for your switch:
IP address
Default account passwords (administrtor and user)
Date and time
Note
Use the Telnet command for subsequent switch login sessions, using
the switch IP address.
Chapter 3: Brocade 3000 Series Switch Configuration 11

2 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, contact your sales representative
before proceeding.
3 Set the switch name, if needed, by entering the following command:
switchname switch_name
Note
Use a name that is meaningful, such as node name and switch.
4 Determine the switch firmware by entering the following command:
version
Result: The currently installed switch firmware is displayed.
5 Access the MetroCluster Compatibility Matrix on the NOW (NetApp
on the Web)

site at now.netapp.com to get the currently supported

version of the switch firmware.
Note
You can find this document under the Interoperability heading on the
Product Documentation page.
6 If your switch firmware is not the supported version, complete the
following steps:
a. Download the switch firmware from now.netapp.com and
install it, as described in the Brocade switch hardware
reference manual for your switch.
b. Reboot the switch.
Step Action
12 Configuring Brocade switches

Setting the switch
parameters
After configuring the switch, set the switch parameters by completing the
following steps.
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, you can use any unique number, for example, 1, 2, 3, or 4.
You should set only the following parameters:
Fabric parameters = y
Domain_id = XXX
Disable device probing = 1
Arbitrated Loop parameters = y
Send FAN frames = 0
Chapter 3: Brocade 3000 Series Switch Configuration 13

Completing the configuration
Completing the
switch
configuration
After the parameters are set, complete the configuration by performing these
steps.
1 After you have set the parameters listed in Step 4 in Setting the
switch parameters on page 12, 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 the switch by entering the following
command:
switchdisable
4 For all switches in the Brocade 3000 series (3800, 3850, 3200, and
3250), set all ports attached to disk loops to half duplex by entering
the following command for each port number:
Note
Perform this command only for the ports to which disks are attached.
Do not set ports attached to disk loops to Locked L-Port.
portCfgLPort <disk_port>,0,0,1
5 For the Brocade 3200 and 3250 switches, ensure that the disk loop
port is showing ON in the Locked Loop HD fields only by entering
the following commands:
portCfgShow
portCfglport
Result: ON is displayed in the locked Loop HD fields only.
Note
These commands do not work with the Brocade 3800 and 3850
switches.
14 Completing the configuration

6 If your switch has the trunking license installed, disable trunking on
the ISL port by entering the following command:
portcfgtrunkport <ISL_port#> 0
7 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, use LO.
For distances up to 10 km, use LE.
For distances beyond 10 km, use LS. Specify 1 to activate long-
distance link initialization sequence, or specify 0 to deactivate
this mode. Then specify the distance.
Example: If your ISL length is 18 km, and your ISL is connected to
port 13, you would use the following command:
portCfgLongDistance 13 LS 1 18
8 To enable the switch, enter the following command:
switchenable
9 To verify that the switch settings are correct, enter the following
command:
configshow
Index 15
Index
Numerics
16-port switch 8
3000 series switch 10
3800 switch 8
3850 switch 8
A
audience, intended for this book vii
B
banks 7
Brocade 3200 8
Brocade Fibre Channel switches 2
C
commands
configshow 14
configure 12
switchdisable 12
switchenable 14
switchname 11
version 11
configuration
completing 13
conventions
command vii
formatting viii
keyboard viii
D
default settings 12
disabling the switch 13
disk loops 13
disks 13
domain ID 12
E
Extended Fabric License 11
F
Fabric License 11
fabric-attached MetroCluster 7
FilerView vii
H
half duplex 13
I
ISL (Inter-Switch Link) cables 2
ISL length 14
L
long-distance ISL port 14
M
MetroCluster
configuring the switches in 9
description 2
fabric-attached 2
N
node name 11
P
parameters 12, 13
pools 7
port number 13
ports 7, 13
Q
quadrants 7
S
special messages ix
16 Index
switch fabric 2
switch firmware 11
switch parameters 12
switch settings 14
switches
banks 7
checking firmware revision 11
configuring for MetroCluster 9
disabling 12
pools 7
quadrants 7
setting the parameters 12
system administrator 12
T
terminology vii
trunking license 14