2014, Brocade Communications Systems, Inc. All Rights Reserved.
Brocade, the B-wing symbol, Brocade Assurance, ADX, AnyIO, DCX, Fabric OS, FastIron, HyperEdge, ICX, MLX, MyBrocade, NetIron,
OpenScript, VCS, VDX, and Vyatta are registered trademarks, and The Effortless Network and the On-Demand Data Center are trademarks
of Brocade Communications Systems, Inc., in the United States and in other countries. Other brands and product names mentioned may be
trademarks of others.
Notice: This document is for informational purposes only and does not set forth any warranty, expressed or implied, concerning any
equipment, equipment feature, or service offered or to be offered by Brocade. Brocade reserves the right to make changes to this document
at any time, without notice, and assumes no responsibility for its use. This informational document describes features that may not be
currently available. Contact a Brocade sales office for information on feature and product availability. Export of technical data contained in
this document may require an export license from the United States government.
The authors and Brocade Communications Systems, Inc. assume no liability or responsibility to any person or entity with respect to the
accuracy of this document or any loss, cost, liability, or damages arising from the information contained herein or the computer programs that
accompany it.
The product described by this document may contain open source software covered by the GNU General Public License or other open
source license agreements. To find out which open source software is included in Brocade products, view the licensing terms applicable to
the open source software, and obtain a copy of the programming source code, please visit http://www.brocade.com/support/oscd.
The document conventions describe text formatting conventions, command syntax conventions, and
important notice formats used in Brocade technical documentation.
Text formatting conventions
Text formatting conventions such as boldface, italic, or Courier font may be used in the flow of the text
to highlight specific words or phrases.
Format
bold text
italic text
Courier font
Description
Identifies command names
Identifies keywords and operands
Identifies the names of user-manipulated GUI elements
Identifies text to enter at the GUI
Identifies emphasis
Identifies variables and modifiers
Identifies paths and Internet addresses
Identifies document titles
Identifies CLI output
Identifies command syntax examples
Command syntax conventions
Bold and italic text identify command syntax components. Delimiters and operators define groupings of
parameters and their logical relationships.
Convention
bold textIdentifies command names, keywords, and command options.
valueIn Fibre Channel products, a fixed value provided as input to a command
option is printed in plain text, for example, --show WWN.
[ ]
{x| y| z}
x | y
< >
...
\
Syntax components displayed within square brackets are optional.
Default responses to system prompts are enclosed in square brackets.
A choice of required parameters is enclosed in curly brackets separated by
vertical bars. You must select one of the options.
In Fibre Channel products, square brackets may be used instead for this
purpose.
A vertical bar separates mutually exclusive elements.
Nonprinting characters, for example, passwords, are enclosed in angle
brackets.
Repeat the previous element, for example, member[member...].
Indicates a “soft” line break in command examples. If a backslash separates
two lines of a command input, enter the entire command at the prompt without
the backslash.
Notes, cautions, and warnings
Notes, cautions, and warning statements may be used in this document. They are listed in the order of
increasing severity of potential hazards.
NOTE
A note provides a tip, guidance, or advice, emphasizes important information, or provides a reference
to related information.
ATTENTION
An Attention statement indicates potential damage to hardware or data.
CAUTION
A Caution statement alerts you to situations that can be potentially hazardous to you or cause
damage to hardware, firmware, software, or data.
DANGER
A Danger statement indicates conditions or situations that can be potentially lethal or
extremely hazardous to you. Safety labels are also attached directly to products to warn of
these conditions or situations.
Visit the Brocade website to locate related documentation for your product and additional Brocade
resources.
You can download additional publications supporting your product at www.brocade.com.
•Adapter documentation is available on the Downloads and Documentation for Brocade Adapters
page. Select your platform and scroll down to the Documentation section.
•For all other products, select the Brocade Products tab to locate your product, then click the
Brocade product name or image to open the individual product page. The user manuals are
available in the resources module at the bottom of the page under the Documentation category.
To get up-to-the-minute information on Brocade products and resources, go to MyBrocade. You can
register at no cost to obtain a user ID and password.
Release notes are available on MyBrocade under Product Downloads.
White papers, online demonstrations, and data sheets are available through the Brocade website.
Brocade resources
Getting technical help
You can contact Brocade Support 24x7 online, by telephone, or by e-mail.
For product support information and the latest information on contacting the Technical Assistance
Center, go to http://www.brocade.com/services-support/index.html.
Use one of the following methods to contact the Brocade Technical Assistance Center.
OnlineTelephoneE-mail
Preferred method of contact for nonurgent issues:
•My Cases through MyBrocade
•Software downloads and
licensing tools
•Knowledge Base
Required for Sev 1-Critical and Sev
2-High issues:
•Continental US:
1-800-752-8061
•Europe, Middle East, Africa,
and Asia Pacific: +800-AT
FIBREE (+800 28 34 27 33)
•For areas unable to access toll
free number: +1-408-333-6061
•Toll-free numbers are available
in many countries.
To send feedback and report errors in the documentation you can use the feedback form posted with
the document or you can e-mail the documentation team.
Quality is our first concern at Brocade and we have made every effort to ensure the accuracy and
completeness of this document. However, if you find an error or an omission, or you think that a topic
needs further development, we want to hear from you. You can provide feedback in two ways:
•Through the online feedback form in the HTML documents posted on www.brocade.com.
•By sending your feedback to documentation@brocade.com.
Provide the publication title, part number, and as much detail as possible, including the topic heading
and page number if applicable, as well as your suggestions for improvement.
● What’s new in this document............................................................................................ 9
● Related publications........................................................................................................10
● How command information is presented in this guide.....................................................10
Introduction
This guide includes procedures for configuring the software. The software procedures show how to
perform tasks using the CLI. This guide also describes how to monitor Brocade products using statistics
and summary screens.
Supported hardware
This guide supports the following product families from Brocade:
•FastIron X Series devices (chassis models):
‐FastIron SX 800
‐FastIron SX 1600
•Brocade FCX Series (FCX) Stackable Switch
•Brocade ICX™ 6610 (ICX 6610) Stackable Switch
•Brocade ICX 6430 Series (ICX 6430)
•Brocade ICX 6450 Series (ICX 6450)
•Brocade ICX 6650 Series (ICX 6650)
•Brocade ICX 7750 Series (ICX 7750)
NOTE
The Brocade ICX 6430-C switch supports the same feature set as the Brocade ICX 6430 switch unless
otherwise noted.
NOTE
The Brocade ICX 6450-C12-PD switch supports the same feature set as the Brocade ICX 6450 switch
unless otherwise noted.
For information about the specific models and modules supported in a product family, refer to the
hardware installation guide for that product family.
What’s new in this document
This document includes the information from FastIron software release 08.0.10a.
•Brocade FastIron SX, FCX, and ICX Diagnostic Reference, 08.0.10a
•Unified IP MIB Reference
How command information is presented in this guide
For all new content, command syntax and parameters are documented in a separate command
reference section at the end of the publication.
In an effort to provide consistent command line interface (CLI) documentation for all products, Brocade
is in the process of preparing standalone Command References for the IP platforms. This process
involves separating command syntax and parameter descriptions from configuration tasks. Until this
process is completed, command information is presented in two ways:
•For all new content included in this guide, the CLI is documented in separate command pages.
The new command pages follow a standard format to present syntax, parameters, usage
guidelines, examples, and command history. Command pages are compiled in alphabetical order
in a separate command reference chapter at the end of the publication.
•Legacy content continues to include command syntax and parameter descriptions in the chapters
where the features are documented.
If you do not find command syntax information embedded in a configuration task, refer to the
command reference section at the end of this publication for information on CLI syntax and usage.
Lists traditional stacking features supported on FastIron devices.
The following table lists the individual BrocadeFastIron switches and the traditional stacking features
they support. These features are supported only on FastIron stackable devices, and are supported in
the Layer 2 and full Layer 3 software images, except where explicitly noted.
FeatureICX 6430ICX 6450FCXICX 6610ICX 6650FSX 800
FSX 1600
Building traditional stacking: Securesetup, Automatic configuration, Manual
configuration
Traditional stacking management08.0.0108.0.0108.0.0108.0.01NoNoNo
Traditional stacking management MAC
address
Traditional stacking partitioning08.0.0108.0.0108.0.0108.0.01NoNoNo
Persistent MAC address08.0.0108.0.0108.0.0108.0.01NoNoNo
Traditional stacking software upgrade08.0.0108.0.0108.0.0108.0.01NoNoNo
Traditional stacking and stack mismatch
troubleshooting
Trunking of stacked ports08.0.0108.0.01No08.0.01NoNoNo
Auto Image Copy for stack units08.0.0108.0.0108.0.0108.0.01NoNoNo
Stack port resiliencyNoNoNo08.0.10aNoNoNo
NOTE
Traditional stacking is not supported on the ICX 6430-C devices.
08.0.0108.0.0108.0.0108.0.01NoNoNo
Traditional stacking overview
This section gives a brief overview of traditional stacking technology, including traditional stacking
terminology. This section also lists the FastIron models that support stacking.
Traditional stacking features
ICX 7750
A stack is a group of devices that are connected so that they operate as a single chassis. Brocade
traditional stacking technology features include:
•Management by a single IP address
•Support for up to eight units per stack (ICX 6430 supports only up to four units in the stack)
•Flexible stacking ports
•Linear and ring stack topology support
•Secure-setup utility to make stack setup easy and secure
•Active controller, standby controller, and member units in a stack
•Active controller management of entire stack
•Active controller download of software images to all stack units
•Standby controller for stack redundancy
•Active controller maintenance of information database for all stack units
•Packet switching in hardware between ports on stack units
•All protocols operate on traditional stacking in the same way as on a chassis system
Brocade stackable models
FCX devices
All FCX devices can be active members of a Brocade IronStack. FCX-E and FCX-I models require an
optional 10 Gbps SFP+ module to support stacking. For information about how to install FCX devices,
refer to the Brocade FCX Series Hardware Installation Guide.
All FCX devices can be ordered from the factory as -ADV models with support for Layer 3 BGP.
All ICX 6610, ICX 6430, and ICX 6450 devices can be active members of a Brocade IronStack. For
information about how to install ICX 6610 devices, refer to the Brocade ICX 6610 Stackable SwitchHardware Installation Guide. For information about how to install ICX 6430 and ICX 6450 devices, refer
to the Brocade ICX 6430 and ICX 6450 Stackable Switches Hardware Installation Guide.
ICX devices also support trunked stacking ports. For ICX 6610 devices, refer to ICX 6610 stacking for
different topologies on page 18 for details. For ICX 6450 and ICX 6430 devices, refer to Connecting
ICX 6450 and ICX 6430 devices in a traditional stack on page 20.
All ICX 6610 devices can be ordered from the factory as -ADV models with support for Layer 3 BGP.
Brocade traditional stacking terminology
Stack unit roles
•Active controller - Handles stack management and configures all system- and interface-level
features.
‐Future active controller- The unit that will take over as active controller after the next
reload, if its priority has been changed to the highest priority. When a priority for a stack
unit is changed to be higher than the existing active controller, the takeover does not
happen immediately to prevent disruptions in the stack operation.
•Standby controller - The stack member with the highest priority after the active controller. The
standby controller takes over if the current active controller fails.
•Stack Member - A unit functioning in the stack in a capacity other than active or standby controller.
•Stack Unit - Any device functioning within the stack, including the active controller and standby
controller.
‐Upstream Stack Unit - An upstream unit is connected to the first stacking port on the
active controller. (The left-hand port as you face the stacking ports.)
‐Downstream Stack Unit - A downstream unit is connected to the second stacking port on
the active controller. (The right-hand port as you face the stacking ports.)
General traditional stacking terminology
•Bootup Role - the role a unit takes during the boot sequence. This role can be standalone, active
controller, standby controller, or stack member. The active controller or a standalone unit can
access the full range of the CLI. Until a stack is formed, the local consoles on the standby controller
and stack members provide access to a limited form of the CLI, such as the show, stack, and a
few debug commands. When the stack is formed, all local consoles are directed to the active
controller, which can access the entire CLI. The last line of output from the show version
command indicates the role of a unit, unless it is a standalone unit, in which case it is not shown.
For example:
My stack unit ID = 1, bootup role = active
•Clean Unit - A unit that contains no startup flash configuration or runtime configuration. To erase
old configuration information, enter the erase startup-config command and reset the unit. For FCX
devices, the runtime configuration on a clean unit may also contain default-port information,
•Control Path - A path across stacking links dedicated to carrying control traffic such as commands
to program hardware or software image data for upgrades. A stack unit must join the control path to
operate fully in the stack.
•Default Port - FCX devices use the default-port command to define stacking port candidates.
•Interprocessor Communications (IPC) - The process by which proprietary packets are
exchanged between stack unit CPUs.
•IronStack - A set of Brocade stackable units (maximum of eight) and their connected stacking
links so that: all units can be accessed through their common connections, a single unit can
manage the entire stack, and configurable entities, such as VLANs and trunk groups, can have
members on multiple stack units.
•Non-Functioning Stack Unit - A stack unit that is recognized as a stack member, and is
communicating with the active controller over the Control Path, but is in a non-functioning state. A
non-functioning stack unit will drop or discard traffic from non-stacked ports. This may be caused
by an image or configuration mismatch.
•Sequential Connection - Stack unit IDs, beginning with the active controller, are sequential. For
example, 1, 3, 4, 6, 7 is sequential if active controller is 1. 1, 7, 6, 4, 3 are non-sequential in a
linear topology, but become sequential in a ring topology when counted from the other direction
as: 1, 3, 4, 6, 7. Gaps in numbering are allowed.
•Standalone Unit - A unit that is not enabled for stacking, or an active controller without any
standby controller or stack members.
•Stacking Link - A cable that connects a stacking port on one unit to a stacking port on another
unit.
•Secure-setup - A software utility that establishes a secure stack.
•Unit Replacement - The process of swapping out a unit with a Clean Unit. No configuration
change is required.
•Reserved / Provisional Unit - A unit configuration number that has no physical unit associated
with it.
•Trunked Stacking Port (Trunk) - A trunk consists of multiple stacking ports and is treated as one
logical link. It provides more bandwidth and better resilience.
•Stack Path - A data path formed across the stacking links to determine the set of stack members
that are present in the stack topology, and their locations in the stack.
•Stacking Port - A physical interface on a stack unit that connects a stacking link. Stacking ports
are point-to-point links that exchange proprietary packets. Stacking ports must be 10 Gbps
Ethernet ports (except for the ICX 6430 that uses 1 Gbps ports), and cannot be configured for any
other purpose while operating as stacking ports. Brocade stacking units contain two ports that can
be stacking ports. However, the flexible stacking port feature also allows you to use one port as a
stacking port and the other port as a regular data port.
•Stack Slot - A slot in a stack is synonymous with line model in a chassis.
•Stack Topology - A contiguously-connected set of stack units in an IronStack that are currently
communicating with each other. All units that are present in the stack topology appear in output
from the show stack command.
•Static Configuration - A configuration that remains in the database of the active controller even if
the unit it refers to is removed from the stack. Static configurations are derived from the startup
configuration file during the boot sequence, are manually entered, or are converted from dynamic
configurations after a write memory command is issued.
•Dynamic Configuration - A unit configuration that is dynamically learned by a new stack unit
from the active controller. A dynamic configuration disappears when the unit leaves the stack.
Supported traditional stacking topologies
This section describes how to build traditional stack. Before you begin, you should be familiar with the
supported stack topologies and the software requirements. When you are ready to build your stack,
you can go directly to the instructions.
Brocade traditional stacking technology supports linear and ring stack topologies. Although Brocade
stackable units may be connected in a simple linear topology, Brocade recommends a ring topology
because it offers the best redundancy and the most resilient operation.
Stacks that contain more than one type of device are called mixed stacks. For example, a mixed stack
contains ICX 6610 and ICX 6450 devices. For information about configuring a mixed stack, refer to the
“Mixed Stacking” chapter.
Traditional stacks must contain devices of the same type or product line. For example, a traditional
stack cannot contain both FCX and ICX 6450 devices. However, because they are models in the same
product line, a traditional stack can contain a mixture of both ICX 6450 and ICX 6430 devices.
FCX stack topologies
A Brocade traditional stack can contain all one model, or any combination of the FCX models. You can
mix 24-port and 48-port FCX devices in a single stack, to a maximum of eight units per stack.
The procedure for cabling a stack of FCX devices differs depending on whether your stack contains
FCX-E and FCX-I devices. The following figure shows FCX-S and FCXS-F devices cabled in linear
and ring stack topologies. Note that these devices are cabled from the rear panel.
FIGURE 1 FCX linear and ring stack topologies
FIGURE 2 FCX-E ring topology stack using SFP+ module ports
FCX stack topologies shows FCX-E devices in a linear topology stack.
Traditional Stacking
FIGURE 3 FCX-E linear topology stack using SFP+ module ports
The following figure shows a mixed linear topology stack of FCX-S, FCXS-F, and FCX-E or FCX-I
devices. Because the FCX-E and FCX-I devices are cabled from the front panel, and FCX-S and FCXSF devices are cabled from the rear panel by default, you need to reconfigure the default stacking ports
on FCX-S or FCXS-F devices to the ports on the front panel. For more information about reconfiguring
default stacking ports, refer to Configuring default ports on FCX devices on page 36.
FIGURE 4 Mixed linear stack of FCX-E devices and FCX-S devices
ICX 6610 stacking for different topologies
Earlier generations of Brocade switches did not have ports exclusively dedicated to stacking. ICX 6610
devices include 4 ports on the back panel that are used entirely for this purpose. Note that these ports
cannot be used as data ports, even when stacking is not enabled.
There are the two 40-Gbps ports and two 4 x 10-Gbps ports arranged in two rows. By default, these
ports form stacked trunks. The figure below shows one stacked trunk on the top row between 1/2/1
and 1/2/2 and the second stacked trunk on the bottom row between 1/2/6 and 1/2/7.
FIGURE 5 ICX 6610 device back panel
To properly connect stacked trunk ports between devices, you must connect corresponding trucks
from one device to another. For example, the following figures show correctly connected ports. The
two stacked trunks can form either linear or ring topologies.
Connecting ICX 6450 and ICX 6430 devices in a traditional stack
In contrast, the following figure shows a linear and ring topology where trucks are not fully connected
and show missing or partial trunk cables. This configuration is functional but is not a trunked stacked
set of devices.
FIGURE 8 ICX 6610 linear and ring stack topologies with partially missing cables
Connecting ICX 6450 and ICX 6430 devices in a traditional stack
ICX 6430 and ICX 6450 support linear and ring stack topologies, and can also operate as standalone
devices. ICX 6430 and ICX 6450 devices have four ports on the front panel for a stacking
configuration. ICX 6430 and ICX 6450 devices ship with two default stacking ports configured. When
stacking is enabled, ports 1 and 3 are dedicated to stacking and cannot be used for data ports. Use
the stack-port command to select only one of these default ports as the stacking port. If you do not
select a default port as the stacking port, both default ports will operate as stacking ports. For more
information about using the stack-port command on ICX 6430 and ICX 6450 devices, refer to Error
messages encountered during the configuration of an ICX 6430 or ICX 6450 traditional stack on page
45. If stacking is not enabled on the ports, then all four stacking ports can be used for data or uplink
ports. By default, ICX 6430 and ICX 6450 devices are not configured for trunked stacking. You can
dynamically configure or remove a stacking trunk port configuration using the stack-trunk command or
the multi-stack-trunk command. For more information about these commands, refer to Configuring an
ICX 6430 and ICX 6450 traditional stack on page 43.
ICX 6450 and ICX 6430 devices support hitless stacking switchover and failover. The secure-setup
utility is supported for ICX 6450 and ICX 6430 devices.
ICX 6430 device supports up to four units in a stack.ICX 6450 device supports up to eight units in a
stack. You cannot mix and match stacking units between ICX 6430 and ICX 6450 devices.
Connecting ICX 6450 devices in a stack
ICX 6450 devices have 24 or 48 10/100/1000 Mbps data ports and 4 ports with 1-Gbps or 10-Gbps SFP
+ fiber uplink and stacking ports. The top row consists of ports 1 and 3, and the bottom row consists of
ports 2 and 4. By default, ports 1 and 3 are 10-Gbps stacking ports and do not have license based
restrictions. However, without a license, ports 2 and 4 boot-up in an error disabled state. To enable
ports 2 and 4 in 10-Gbps port speed, you must purchase the ICX6450-2X10G-LIC-POD license.
ICX 6450 devices are available with 4 1/10-Gbps optical (dual mode) ports. If you want to use more
than two 1-Gbps ports on the 6450 with the optical ports, you must enable the 10-Gbps ports as 1-Gbps
ports for uplinks.
For more information about enabling ports 2 and 4 to 10-Gbps port speed, refer to "Licensing for Ports
on Demand" section in the FastIron Ethernet Switch Administration Guide.
Configuring a 10-Gbps port for a 1-Gbps uplink
If you want to use more than two 1-Gbps ports on an ICX 6450 device with 4 1/10-Gbps optical (dual
mode) ports, you must enable the 10-Gbps ports as 1-Gbps ports for uplinks.
Perform this task to configure a 10-Gbps port for a 1-Gbps uplink on an ICX 6450 device equipped with
4 1/10-Gbps optical (dual mode) ports.
speed-duplex 1000-full-master
Connecting ICX 6430 devices in a stack
ICX 6430 devices have 24 or 48 10/100/1000 Mbps data ports and 4 1-Gbps SFP fiber uplink and
stacking ports. The default stacking ports are 1 and 3. The 4 1-Gbps ports are not eligible for an
upgrade to 10-Gbps port speed. Trunk stacking configuration is supported for ICX 6430 devices. LAG
configuration is supported for stacking or uplink ports when a pair of 1-Gbps ports are aggregated.
Trunking configuration considerations for ICX 6430 and ICX 6450
devices
The ICX 6430 and ICX 6450 stacking ports are grouped into two trunks. Follow these guidelines for
connecting and configuring the stacking ports:
NOTE
After enabling the ICX 6430 and ICX 6450 trunked stacking ports, it is recommended that you enter the
write memory command to save your configuration.
•You can connect one or both ports in a trunk. Connecting both ports in a trunk increases stacking
bandwidth and provides resiliency.
•You must enable stacking and connect cables properly for the stack to work. The active copper
cable lengths for 1-Gbps ports are 1 m (3.2 ft) and 5 m (16.4 ft). The copper cable lengths for 10Gbps ports are 1 m (3.2 ft), 3 m (9.8 ft), and 5 m (16.4 ft).
•The default stacking ports are always ports 1 and 3. You can trunk (or un-trunk) ports 1 to 2 and
or ports 3 to 4. One or both of the two sets of stacking ports can be trunked (or un-trunked).
•When creating a trunk, the ports in the same column are always trunked. For ICX 6450 devices,
all stack ports must be configured to 10-Gbps port speed to enable trunking. For ICX 6430
devices, all stack ports must be at 1-Gbps port speed to enable trunking. For example, you can
connect ports 1/2/3 to 1/2/4 to form one trunk on one device, and ports 2/2/1 to 2/2/2 to form a
second trunk on another device.
•If you connect both ports in a trunk, both ports must connect to both ports of one trunk on another
device.
ICX 6430 and ICX 6450 stack topologies
In a linear stack topology, there is a single stack cable connection between each switch that carries
two-way communications across the stack. In a ring stack topology, an extra cable is connected
between the top and bottom switches forming a "ring" or "closed-loop." The closed-loop cable provides
a redundant path for the stack link, so if one link fails, stack communications can be maintained. The
closed-loop cable provides more stacking bandwidth and shortens the paths between some units.
The following figures show stacking cabling configurations. All the stacking configuration examples are
applicable to both ICX 6430 and ICX 6450 switches.
The following figure shows both linear and ring stacking configurations when you only connect one port
per trunk. The one port per trunk topology is the most commonly configured stacking configuration.
FIGURE 9 ICX 6430 and ICX 6450 stacking with one port per trunk
The following figure shows how the stack cables are connected between switches in a linear stacking
configuration for dual linking.
FIGURE 10 ICX 6430 and ICX 6450 linear stacking configuration
The following figure shows how the stack cables are connected between switches in a ring stacking
configuration.
FIGURE 11 ICX 6430 and ICX 6450 ring stacking configuration
Software requirements
All units in a traditional stack must be running the same software version.
Traditional stack construction methods
There are three ways to build a traditional stack.
1.Use the secure-setup utility to form your stack. Secure-setup gives you control over the design of
your stack topology and provides security through password verification. For the secure-setup
procedure, refer to Scenario 1 - Three-member traditional stack in a ring topology using secure-
setup on page 25.
2.Automatic stack configuration. With this method, you enter all configuration information, including
the module type and the priorities of all members into the unit you decide will be the active
controller and set its priority to be the highest. When you enable stacking on the active controller
the stack then forms automatically. This method requires that you start with clean units (except for
the active controller) that do not contain startup or runtime configurations. Refer to Scenario 2 -
Three-member traditional stack in a ring topology using the automatic setup process on page 29.
3.Manual stack configuration. With this method, you configure every unit individually, and enable
stacking on each unit. Once the units are connected together, they will automatically operate as a
traditional stack. With this method the unit with the highest priority becomes the active controller,
and ID assignment is determined by the sequence in which you physically connect the units. Refer
to Scenario 3 - Three-member traditional stack in a ring topology using the manual configuration
process on page 31.
Traditional stacking configuration notes
Before you configure your traditional stack, consider the following guidelines:
•Consider the number of units and how the stacking ports on the units will be connected. For more
information, refer to the hardware installation guide for your device.
•The stack should be physically cabled in a linear or ring topology. Connect only those units that will
be active in the stack.
•Make sure all units intended for the stack are running the same software version. Use the show
version command on any of the console ports in the stack.
NOTE
If you are running a router image and there is a potential loop in your topology, you need to configure
the spanning tree protocol in the would-be active controller. Otherwise, the excessive looping packets
might affect stack formation. The Spanning Tree Protocol is enabled by default in switch images.
•When you have a full stack of 8 units, you may need to increase the trap hold time from the default,
which is 60 seconds, to five minutes (300 seconds). This will prevent the loss of initial boot traps.
To increase the trap hold time, use the following command.
The router image requires more time to boot than the switch image.
Scenario 1 - Three-member traditional stack in a ring topology using
secure-setup
This scenario describes how to build a traditional stack using the secure-setup utility. Secure-setup lets
you easily configure your entire stack through the active controller, which propagates the configuration
to all stack members. Secure-setup is the most secure way to build a traditional stack, and gives you
the most control over how your stack is built. For example, secure-setup offers three security features
that prevent unauthorized devices from accessing or joining a traditional stack:
Configuring a three-member traditional stack in a ring topology using secure-setup
•Authentication of secure-setup packets provides verification that these packets are from a
genuine Brocade stack unit. MD5-based port verification confirms stacking ports.
•Superuser password is required to allow password-protected devices to become members of a
traditional stack.
•The stack disable command. When this command is issued, a unit does not listen for or send
stacking packets, which means that no other device in the network can force the stackingdisabled unit to join a traditional stack.
Secure-setup can also be used to add units to an existing traditional stack and to change the stack IDs
of stack members.
When secure-setup is issued on a unit that is not already the active controller, this unit becomes the
active controller. If this unit does not already have an assigned priority, secure-setup will assign this
unit a priority of 128 by default, if no other units in the stack have a priority higher than 128. If another
unit in the stack has a priority of 128 or higher, secure-setup will give the active controller a priority
equal to the highest priority unit in the stack (which is by default the standby controller). When the
active controller and the standby controller have identical priorities, during a reset, the old active
controller cannot reassume its role from the standby controller (which has become the active controller
at the reset).
If the previous active controller again becomes active, and you want it to resume the role of active
controller, you should set the priority for the standby controller to a priority lower than 128. If you do
not want the previous active controller to remain active controller, you can set the same priority for
both active and standby controllers (higher than or equal to 128).
NOTE
Secure-setup works for units within a single stack. It does not work across stacks.
The following figure shows a traditional stack with three units in a ring topology. Refer to this figure as
you follow the procedure steps for this scenario.
FIGURE 12 Traditional stack with ring topology
Configuring a three-member traditional stack in a ring topology using secure-setup
1.Connect the devices using the stacking ports and stack cabling. For more information, refer to the
appropriate hardware installation guides.
5.Enter the stack secure-setup command. As shown in the following example, this command
triggers a Brocade proprietary discovery protocol that begins the discovery process in both
upstream and downstream directions. The discovery process produces a list of upstream and
downstream devices that are available to join the stack. Secure-setup can detect up to 7 units in
each direction (14 total), but because the maximum number of units in a stack is 8, you must select
a maximum of 7 units from both directions.
NOTE
To exit the secure-setup, enter ^C at any time.
You should see output similar to the following.
device# stack secure-setup
device# Discovering the stack topology...
Current Discovered Topology - RING
Available UPSTREAM units
Hop(s) Type MAC Address
1 FCX624 0000.0039.2d40
2 FCX624 0000.00d5.2100
Available DOWNSTREAM units
Hop(s) Type MAC Address
1 FCX624 0000.00d5.2100
2 FCX624 0000.0039.2d40
Do you accept the topology (RING) (y/n)?: y
If you accept the topology, you will see output similar to the following.
Selected Topology:
Active Id Type MAC Address
1 FCX648 0000.00ab.cd00
Selected UPSTREAM units
Hop(s) Id Type MAC Address
1 3 FCX624 0000.0039.2d40
2 2 FCX624 0000.00d5.2100
Selected DOWNSTREAM units
Hop(s) Id Type MAC Address
1 2 FCX624 0000.00d5.2100
2 3 FCX624 0000.0039.2d40
Do you accept the unit ids (y/n)?: y
To accept the unit ID assignments, type y. If you do not want to accept the ID assignments, type n.
You can use secure-setup to renumber the units in your stack. Refer to “Renumbering stack units.”
If you accept the unit IDs, the stack is formed, and you can see the stack topology using the showstack command.
device# show stack
alone: standalone, D: dynamic config, S: static config
ID Type Role MAC Address Pri State Comment
1 S FCX648 active 0000.00ab.cd00 128 local Ready
2 D FCX624 standby 0000.00d5.2100 60 remote Ready
3 D FCX624 member 0000.0039.2d40 0 remote Ready
active standby
+---+ +---+ +---+
-2/1| 1 |3/1--2/1| 2 |3/1--2/2| 3 |2/1 +---+ +---+ +---+
Current stack management MAC is 0000.00ab.cd00
In this output, D indicates a dynamic configuration. After you perform a write memory , this
display will change to S, for static configuration.
6.The active controller automatically checks all prospective stack members to see if they are
password-protected. If a unit is password- protected, you will be asked to enter the password
before you can add the unit. If you do not know the password, take one of the following actions:
•Discontinue secure-setup by entering ^C.
•Obtain the device password from the administrator.
•Skip this unit and continue the secure-setup for your stack. The password-protected device
and all devices connected behind it will not be included in the setup process.
In the following example, the second unit is password-protected, so you are asked for the
password.
device# stack secure-setup
device# Discovering the stack topology...
Verifying password for the password protected units...
Found UPSTREAM units
Hop(s) Type MAC Address
1 2 FCX648 0000.005e.c480
2 3 FCX648 0000.0005.0000
Enter password for FCX648 located at 2 hop(s): ****
Enter the number of the desired UPSTREAM units (1-2)[1]: 2
Selected Topology:
Active Id Type MAC Address
1 FCX624 0000.0001.4000
Selected UPSTREAM units
Hop(s) Id Type MAC Address
1 2 FCX648 0000.005e.c480
2 3 FCX648 0000.0005.0000
Do you accept the unit id's (y/n)?: y
7.When the active controller has finished the authentication process, you will see output that shows
the suggested assigned stack IDs for each member. You can accept these recommendations, or
you can manually configure stack IDs. Enter the show stack command to verify that all units are
in the ready state.
device# show stack
alone: standalone, D: dynamic config, S: static config
ID Type Role MAC Address Pri State Comment
1 S FCX624 active 0000.0001.4000
128 local Ready
2 S FCX648 standby 0000.005e.c480 0
remote Ready
3 S FCX648 member 0000.0005.0000 0
remote Ready
active standby
+---+ +---+ +---+
-2/1| 1 |3/1--2/1| 2 |3/1--2/2| 3 |2/1 | +---+ +---+ +---+ |
| |
|-------------------------------------|
Current stack management MAC is 0000.0001.4000
device#