Page 3
Trademarks The Ruckus, Ruckus Wireless, Ruckus logo, Big Dog design, BeamFlex, ChannelFly, EdgeIron, FastIron, HyperEdge, ICX, IronPoint, OPENG, Xclaim, and ZoneFlex and trademarks are registered in the U.S. and other countries. Ruckus Networks, Dynamic PSK, MediaFlex, FlexMaster, Simply Better Wireless, SmartCast, SmartCell, SmartMesh, SpeedFlex, Unleashed, ZoneDirector and ZoneFlex are Ruckus trademarks worldwide.
Contents Preface..........................................9 Document Conventions..................................9 Notes, Cautions, and Warnings...............................9 Command Syntax Conventions................................9 Document Feedback....................................10 Ruckus Product Documentation Resources............................10 Online Training Resources..................................10 Contacting Ruckus Customer Services and Support..........................11 What Support Do I Need?................................11 Open a Case....................................11 Self-Service Resources................................. 11 About This Guide......................................
Page 6
ICX 7450 stack configuration overview..............................53 ICX 7450 stacking topologies................................54 ICX 7450 stacking configuration notes............................57 Configuring 10-Gbps stacking ports on the ICX 7450........................58 Creating stacking trunks on the ICX 7450............................. 60 ICX 7450 secure-setup examples..............................62 Displaying basic information for an ICX 7450 stack........................71 Displaying details for an ICX 7450 stack............................72...
Page 7
Traditional Stack Management.................................. 111 Managing a traditional stack through one IP address..........................111 Enabling or disabling stacking mode..............................111 Disabling stacking mode................................112 Traditional stack unit identification .............................. 112 Controlling the stack through the CLI..............................112 Logging in through the console port............................113 CLI command syntax for stack units............................
Page 8
SNMP engine IDs for stackable devices............................135 Displaying traditional stack information............................... 135 Displaying stacking topology...............................136 Displaying running configuration information..........................136 How the show running-config command displays configured stacking ports................137 Displaying software version information............................138 Displaying traditional stack flash information..........................139 Displaying traditional stack memory information.......................... 140 Displaying traditional stack chassis information ..........................
Preface • Document Conventions............................. 9 • Command Syntax Conventions..........................9 • Document Feedback............................... 10 • Ruckus Product Documentation Resources......................10 • Online Training Resources............................10 • Contacting Ruckus Customer Services and Support....................11 Document Conventions The following tables list the text and notice conventions that are used throughout this guide. TABLE 1 Text conventions Convention Description...
Preface Document Feedback Convention Description italic text Identifies a variable. Syntax components displayed within square brackets are optional. Default responses to system prompts are enclosed in square brackets. { x | y | z } A choice of required parameters is enclosed in curly brackets separated by vertical bars. You must select one of the options.
Preface Contacting Ruckus Customer Services and Support Contacting Ruckus Customer Services and Support The Customer Services and Support (CSS) organization is available to provide assistance to customers with active warranties on their Ruckus Networks products, and customers and partners with active support contracts. For product support information and details on contacting the Support Team, go directly to the Support Portal using https:// support.ruckuswireless.com, or go to...
08.0.40b. NOTE Support information for LR4 optics has been revised for all FastIron 08.0.40 releases and above to indicate that ICX 7450 devices support LR4 optics for stacking. Refer to the updated section FastIron stacking distances and optics by device on page 21.
Campus Fabric on page 16 and (also known as Campus Fabric) serve as a control bridge (CB) for attached ICX 7450 Planning to build a stack with 802.1br switch port units configured as port extenders (PEs). This makes extender capability...
A Brocade traditional stack contains from two to 12 units configured in a ring or linear topology. The units in a traditional stack are from the same model family; that is, a traditional stack contains only ICX 7250, ICX 7450, or ICX 7750 units.
Campus Fabric creates a more scalable architecture based on IEEE 802.1BR standards. Brocade Campus Fabric architecture adds Brocade ICX 7450 or ICX 7250 devices configured as port extenders (PEs), or PE units, to a set of Brocade ICX 7750 stack units configured as the control bridge.
Page 17
Stacking Overview Campus Fabric FIGURE 2 Campus Fabric domain build-out from an ICX 7750 CB stack The following figure depicts three separate campuses, each with its own Campus Fabric domain, interconnected with a high-speed backbone. Ruckus FastIron Stacking Configuration Guide, 08.0.40b Part Number: 53-1003910-11...
Brocade stackable models All ICX 7450 and ICX 7750 devices and some ICX 7250 devices can be members of a Brocade traditional stack. ICX 7750 devices installed in a traditional stack can also be configured as an 802.1br control bridge that manages ICX 7450 devices configured as port extender (PE) Brocade FastIron Switch Port Extender Configuration Guide for information on 802.1br configuration.
Stacking Overview Brocade traditional stacking terminology Brocade traditional stacking terminology Certain terms and roles specific to stacking are used throughout this guide. This section describes the roles stack units may assume as well as terms key to understanding stacking. NOTE Brocade FastIron Switch Port Extender Configuration Guide for terms specific to IEEE 802.1br and switch port Refer to the extender (SPX) capability.
Page 20
Stacking Overview Brocade traditional stacking terminology • IronStack - A set of Ruckus stackable units (maximum of twelve) 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.
Building a Stack • Planning to build a traditional stack......................... 21 • Planning to build a stack with 802.1br switch port extender capability..............25 • Traditional stack construction methods........................26 • Verifying a traditional stack configuration......................... 40 • Displaying information on stack connections......................42 Planning to build a traditional stack Before you begin to build a traditional stack, you should be familiar with supported stacking software requirements, topologies, and recommendations.
Page 22
Extended distance stacking on the ICX 7750 is restricted to certain ports. Refer to "Installing the ICX 7750 in a remote stack" in this guide. For data uplink only, the following 40-Gbps optics are available on ICX 7450 devices: 40G-QSFP-BiDi, 40-G-QSFP-LM4, 40G-QSFP-ER4 Ruckus FastIron Stacking Configuration Guide, 08.0.40b...
Page 23
LR optics can be used on ICX 7450 4X10-Gbps ports when a 4X10GF module is installed. LR optics can support distances up to 10 kilometers for data or stacking. Long-distance stacking with LR optics is supported on front panel ports 1/2/1 through 1/2/4. The following table summarizes LR support on the ICX 7450.
Page 24
Building a Stack Planning to build a traditional stack Port 1/1/2 : Type : 1G M-C (Gig-Copper) Port 1/1/3 : Type : 1G M-C (Gig-Copper) Port 1/1/4 : Type : 1G M-C (Gig-Copper) Port 1/1/5 : Type : 1G M-C (Gig-Copper) Port 1/1/6 : Type : 1G M-C (Gig-Copper) Port 1/1/7 :...
Only ICX 7750 devices can serve as the control bridge (CB). The CB can be a standalone unit or a stack of multiple units. • Only ICX 7450 devices can be configured as PE units attached to the CB. PE units can be attached to any CB unit. •...
Building a Stack Traditional stack construction methods Traditional stack construction methods NOTE The principles outlined in stack construction scenarios apply to all ICX devices. Figures used to illustrate a certain stack topology are not necessarily representative of other devices. For illustrations specific to a particular device, refer to the stack configuration section for that device, which also contains device-specific stacking considerations and configuration examples.
Building a Stack Traditional stack construction methods identical priorities, during a reset, the old active controller cannot reassume its role from the standby controller (which became 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.
Page 28
Building a Stack Traditional stack construction methods Enter the stack secure-setup command. As shown in the following example, this command triggers a Ruckus 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.
Page 29
Building a Stack Traditional stack construction methods Enter y to accept the topology. You should see output similar to the following. Selected Topology: Active Type Mac Address ICX7750-48XGF cc4e.246d.9e00 Selected UPSTREAM units Hop(s) Type Mac Address ICX7750-48XGF cc4e.246d.8d80 ICX7750-48XGF cc4e.246d.9b00 ICX7750-48XGF cc4e.246d.9c80 ICX7750-20QXG...
Page 30
Building a Stack Traditional stack construction methods If the Brocade device supports stacking trunks, the system next displays available trunk options in turn and requests your input on how many ports to include. The range is presented in parentheses, and the current setting is presented in square brackets. For example, (1-3) [ 1 ] indicates that the current connection is a single-port link, and you have the option of electing a 2-port or a 3- port trunk instead.
Page 31
Building a Stack Traditional stack construction methods Review the topology and the unit IDs that are displayed. When prompted, enter y if you want to accept the assigned unit IDs. NOTE You can also enter n to decline the assigned unit IDs. The system then prompts you to enter different IDs, warns that changing the unit IDs manually may modify stack configuration, and recommends that you save the configuration and reload it after the stack is ready.
Page 32
Building a Stack Traditional stack construction methods 10. Enter y to accept these recommendations, or enter n to reject the recommendations. NOTE You can use secure-setup to renumber the units in your stack. Refer to Renumbering stack units on page 131. After you accept the unit IDs, an active controller is elected, the stack is formed, and a standby controller is designated.
Page 33
Building a Stack Traditional stack construction methods T:20m10.2: Done hot swap: active controller u1 sets u5 to Ready. T:20m10.5: Done hot swap: active controller u1 sets u6 to Ready. T:20m10.9: Done hot swap: active controller u1 sets u7 to Ready. T:20m11.4: Done hot swap: active controller u1 sets u8 to Ready.
Page 34
Building a Stack Traditional stack construction methods 12. If you need additional information on individual ports, enter the show stack stack-ports command as shown in the following example. device# show stack stack-ports active =2/1|4|2/6==2/6|3|2/1==2/1|2|2/6==2/6|1|2/1==2/1|7|2/6==2/6|6|2/1= standby | --------------------------------------------------------2/1|5|2/6= Stack-port1 Stack-port2 up (1/2/1-1/2/5) up (1/2/6-1/2/10) up ports: 1/2/1, 1/2/2, 1/2/3, 1/2/4, 1/2/5 U# Stack-port1 Stack-port2...
Configure the rest of the units by assigning ID numbers and module information for each unit. The stack ID can be any number from 1 through 12 for ICX 7250, ICX 7450, and ICX 7750 devices. ICX7750-26Q Router# configure terminal...
Page 36
Building a Stack Traditional stack construction methods After configuring the last stack unit (unit 3 in this example), create any stacking trunks needed for your configuration. NOTE Each ICX 7750 stack unit can support two stacking trunks. NOTE If you configure stacking trunks on some, but not all, stack units, make sure both ends of a link have the same number of trunk ports.
Page 37
Building a Stack Traditional stack construction methods 10. Physically connect the devices in a stack topology. This triggers an election during which the stack is automatically configured. For more information about cabling the devices, refer to the appropriate hardware installation guide. NOTE When you are configuring individual stack units, you can skip ID numbers.
Page 38
Building a Stack Traditional stack construction methods 13. To display detailed information on each stack unit, enter the show version command. ICX7750-26Q Router# show version Copyright (c) 1996-2015 Brocade Communications Systems, Inc. All rights reserved. UNIT 1: compiled on Jul 31 2015 at 18:37:27 labeled as SWR08040b1 (20197181 bytes) from Primary SWR08040b1.bin SW: Version 08.0.40b1T203 UNIT 2: compiled on Jul 31 2015 at 18:37:27 labeled as SWR08040b1...
Building a Stack Traditional stack construction methods • In a ring topology, the same new unit might assume either ID if either direction produces sequential IDs. For example, in a four- member stack where IDs 2 and 4 are reserved, a new unit could assume the ID 2 or the ID 4, to create the ID sequence 1, 2, 3 or the sequence 1, 3, 4.
Building a Stack Verifying a traditional stack configuration Connect the devices in a stack topology. The active controller retains its ID. The rest of the units are assigned unique ID numbers depending on the sequence in which you connected them. For more information about cabling the devices, refer to the appropriate hardware installation guide.
Page 41
Building a Stack Verifying a traditional stack configuration ICX7750-48C Router# The output from the show stack command contains a visual diagram of the stack. In the following example, the dashed line between ports 1/2/1 and 2/2/4 indicates that this stack is configured in a ring topology. The double dashed lines (equal signs) between all units indicate stack trunk connections.
Building a Stack Displaying information on stack connections (20197181 bytes) from Primary SWR08040b1.bin SW: Version 08.0.40b1T203 Compressed Boot-Monitor Image size = 1835008, Version:10.1.01T205 (swz10101) Compiled on Fri Jun 27 22:01:35 2014 NOTE For field descriptions of the show running-config command, refer to “Displaying running configuration information.” NOTE For field descriptions of the show stack , show stack detail , and show version commands, refer to “Displaying stack information.”...
Page 43
Building a Stack Displaying information on stack connections In the following example, the show stack connection command output indicates that CPU-to-CPU connections are working properly between all 12 members of the stack. ICX7750-48F Router# show stack connection Probing the topology. Please wait ... ICX7750-48F Router# active +---+...
Traditional Stacking by Device ICX 7250 stack configuration overview TABLE 8 ICX 7250 traditional stacking capability (continued) Stacking capability ICX 7250 Additional information Configuration options Manual and automatic, including Secure-setup Refer to Traditional stack construction methods on page 26. Access methods TFTP, SCP Software images, boot images, and signatures can be downloaded to a stack using TFTP and...
Traditional Stacking by Device ICX 7250 stack configuration overview FIGURE 6 ICX 7250-24P linear stack FIGURE 7 ICX 7250-24P ring stack ICX 7250 stacking configuration notes All ICX 7250 platforms except the ICX 7250-24G support stacking on 10-Gbps links. The ICX 7250 requires a POD license for ports to operate at 10 Gbps.
Traditional Stacking by Device ICX 7250 stack configuration overview When stacking is configured, all stack ports and trunks must be either in the port range of 1/2/1 through 1/2/4 or in the port range 1/2/5 through 1/2/8. Ports 1/2/1 through 1/2/8 support both active cables and 10-Gbps SFP+ optics. Ports 1/2/5 through 1/2/8 have re-timers that support active cables.
Traditional Stacking by Device ICX 7250 stack configuration overview The following example designates ports 1/2/1 and 1/2/3 as stacking default ports and then creates two trunks. ICX7250-24P Router(config)# stack unit 1 ICX7250-24P Router(config-unit-1)# default-ports 1/2/1 1/2/3 ICX7250-24P Router(config-unit-1)# stack-trunk 1/2/1 to 1/2/2 ICX7250-24P Router(config-unit-1)# stack-trunk 1/2/3 to 1/2/4 The following example reassigns ports 1/2/5 and 1/2/7 as stacking default ports and creates two trunks.
Page 50
Traditional Stacking by Device ICX 7250 stack configuration overview ICX7250-24 cc4e.24b4.7740 Do you accept the topology (RING) (y/n)?: y ICX7250-24 Router# stack secure-setup ICX7250-24 Router# Discovering the stack topology... Current Discovered Topology - RING Available UPSTREAM units Hop(s) Type Mac Address ICX7250-24 cc4e.24b4.7740 ICX7250-24...
Traditional Stacking by Device ICX 7250 stack configuration overview ICX7250-24P cc4e.24b4.7bc0 ICX7250-24P cc4e.24b4.7efc ICX7250-24 cc4e.24b4.8670 ICX7250-24 cc4e.24b4.84c0 ICX7250-24 cc4e.24b4.8064 ICX7250-24 cc4e.24b4.83a0 ICX7250-48 cc4e.24b4.2514 ICX7250-48 cc4e.24b4.2820 ICX7250-24 cc4e.24b4.8988 ICX7250-48P cc4e.24b4.2f28 ICX7250-48P cc4e.24b4.2eb0 Do you accept the unit id's (y/n)?: y Displaying basic information for an ICX 7250 stack Enter the show stack command at the device level to display general information about the stack, including unit IDs, device type, role, MAC address, priority, status, and connections.
Traditional Stacking by Device ICX 7250 stack configuration overview Displaying detailed information for an ICX 7250 stack Use the show stack detail command to display information on all units in the stack, including their role, MAC address, priority, status, and stack connections.
30 minute(s) 3 second(s) ICX 7450 stack configuration overview The following table provides an overview of ICX 7450 stacking capabilities. From FastIron release 08.0.30, 4 x 10-Gbps stacking is available from module 2 as an option. TABLE 9 ICX 7450 traditional stacking capability...
ICX 7450 stacking topologies Up to 12 ICX 7450 units of any kind can be connected in a linear or ring topology. Default stacking ports are located on the rear panel as shown in the following figures. The default port numbers are 1/3/1 and 1/4/1 (unit/slot/port); that is, they are the single port located in modules 3 and 4 of the ICX 7450 as shown.
Page 55
The following figure shows the 4X10GF module and port numbers. FIGURE 9 ICX 7450 module 2 ports available for stacking The following figure shows ICX 7450 units connected from 1 X 40-Gbps ports on the rear in a linear stack. Ruckus FastIron Stacking Configuration Guide, 08.0.40b...
Page 56
ICX 7450 stack configuration overview FIGURE 10 ICX 7450 1 X 40-Gbps linear stack The following figure shows ICX 7450 units connected from 1 X 40-Gbps ports on the rear in a ring stack. NOTE The secure-setup utility starts discovery with the lowest numbered port. Assuming the top unit is the Active Controller, the cabling depicted is recommended so that units are discovered and numbered sequentially, starting from the Active Controller at the top.
• The ICX 7450 supports 10-Gbps stacking when a 4X10GF module is present in slot 2. Each unit must be individually configured with default stacking ports as 1/2/1 and 1/2/3 and reloaded to join a stack, or to use secure setup. Refer to...
Configuring 10-Gbps stacking ports on the ICX 7450 By default, the ICX 7450 uses 40-Gbps ports in slots 3 and 4 as stacking ports. When a 4X10GF module is installed in slot 2 on the front panel of an ICX 7450, 10-Gbps stacking can be configured.
Page 59
Converting ICX 7450 slot 2 ports for MACsec or stacking When a 4x10GF module is installed in slot 2 of the ICX 7450, it is enabled for MACsec even if the ports have not been configured. To use these ports for stacking, you must reconfigure them.
The ICX 7450 supports two stacking trunks per stack unit when the 4X10GF module in slot 2 is used for stacking. You can configure one or two stacking trunks on an ICX 7450 stand-alone after changing default stacking ports to 1/2/1 and 1/2/3 as shown in the following example.
Page 61
Default ports 1/3/1 and 1/4/1, which are 40-Gbps ports on the rear panel of the ICX 7450, do not support stacking trunks. Creating stacking trunks on live stacks Use the multi-stack trunk command to add or remove a stacking trunk on a live ICX 7450 stack. The following example creates two stacking trunks.
Use the stack secure-setup command to automatically form a correctly connected stack. For more information on stack construction, refer Traditional stack construction methods on page 26. In the following example, the stack secure-setup command is used to form a 12-unit ICX 7450 stack in a ring topology. ICX7450-48P Router# configure terminal ICX7450-48P Router(config)# stack enable Enable stacking.
Page 63
Traditional Stacking by Device ICX 7450 stack configuration overview ICX7450-48F cc4e.246d.1df8 ICX7450-48P cc4e.2489.8640 ICX7450-48F cc4e.246d.1478 ICX7450-48P cc4e.2489.b388 ICX7450-24P cc4e.2489.8a38 ICX7450-24P cc4e.246d.0520 ICX7450-48P cc4e.246d.2938 ICX7450-48F cc4e.246d.1838 ICX7450-48F cc4e.2489.a220 Do you accept the unit id's (y/n)?: y ICX7450-48P Router#T=13m8.4: Election, was alone --> active, ID=1, pri=128, 12U(1-12), A=u1, nbr#=11 11, reason: u7: SecureS, , Config changed due to add/del units.
Page 64
Traditional Stacking by Device ICX 7450 stack configuration overview T:15m39.7: Done hot swap: active controller u1 sets u8 to Ready. T:15m39.9: Done hot swap: active controller u1 sets u9 to Ready. T:15m40.4: Done hot swap: active controller u1 sets u10 to Ready.
Page 65
Current stack management MAC is cc4e.2489.b188 The following example configures an ICX 7450 to use 4 X 10-Gbps ports for stacking. First, default ports are reassigned, a write memory command is executed, and the unit is reloaded. When the unit reboots, the 4 X 10-Gbps default ports are configured, and the stack secure setup utility can be executed to form the stack.
Page 66
Traditional Stacking by Device ICX 7450 stack configuration overview --More--, next page: Space, next line: Return key, quit: Control-c^C ICX7450-24 Router(config)# exit ICX7450-24 Router# stack secure-setup ICX7450-24 Router# Discovering the stack topology... Available UPSTREAM units Hop(s) Type Mac Address ICX7450-48F cc4e.246d.1c78...
Page 67
Traditional Stacking by Device ICX 7450 stack configuration overview Selected UPSTREAM units Hop(s) Type Mac Address ICX7450-48F cc4e.246d.1c78 ICX7450-48F cc4e.246d.1b78 ICX7450-48F cc4e.246d.1ff8 ICX7450-48P cc4e.2489.8640 ICX7450-48F vcc4e.246d.1478 ICX7450-48P cc4e.2489.b388 ICX7450-48P cc4e.2489.b188 ICX7450-48P cc4e.246d.2938 ICX7450-48F cc4e.246d.1838 ICX7450-48P cc4e.246d.23b8 ICX7450-24P cc4e.246d.0520 Do you accept the unit id's (y/n)?: y ICX7450-24 Router#T=5m2.9: Election, was alone -->...
Page 68
Traditional Stacking by Device ICX 7450 stack configuration overview Detect stack member 9 POE capable Detect stack member 12 POE capable Detect stack unit 10 has different startup config flash, will synchronize it T=7m11.6: Synchronize webauth files to u10 Detect stack unit 11 has different startup config flash, will synchronize it T=7m11.6: Synchronize webauth files to u11...
Page 69
T=8m21.0: Running config sync to standby u2 is complete ICX7450-24 Router# The following example provides show stack command output for the ICX 7450 10-Gbps stack formed in the previous example. ICX7450-24 Router# show stack T=10m34.8: alone: standalone, D: dynamic cfg, S: static, A=10, B=11, C=12...
Page 70
2: 11/2/2 (T0) <---> 12/2/2 (T0) CPU to CPU packets are fine between 12 units. The following example provides output for the show stack detail command for the ICX 7450 10-Gbps stack formed in the previous example. ICX7450-24 Router# show stack detail...
4 minute(s) 37 second(s) 4 minute(s) 37 second(s) 4 minute(s) 38 second(s) ICX7450-24 Router# The following show stack neighbors command output provides information on neighbors for the ICX 7450 10-Gbps stack formed in the previous example. ICX7450-24 Router# show stack neighbors Stack-port1...
Use the show stack detail command to display information on all units in the stack, including their role, MAC address, priority, status, and stack connections. The following show stack detail command output provides information on a full ICX 7450 stack containing 12 units, with six different models among them.
Traditional Stacking by Device ICX 7750 stack configuration overview TABLE 10 ICX 7750 traditional stacking capability (continued) Stacking capability ICX 7750 Additional information Possible 6-port trunks: 1/2/1 through 1/2/6 1/3/1 through 1/3/6 Possible 3-port trunks: 1/2/1 through 1/2/3 1/2/4 through 1/2/6 1/3/1 through 1/3/3 1/3/4 through 1/3/6 Possible 2-port trunks:...
Page 75
Traditional Stacking by Device ICX 7750 stack configuration overview FIGURE 14 ICX 7750 default stacking ports on front panel FIGURE 15 ICX 7750-26Q default front panel stacking ports Available stacking ports on the ICX 7750 rear panel are ports 1/3/1 through 1/3/6. Default ports can be changed from front panel ports 1/2/1 and 1/2/4 to rear panel ports 1/3/1 and 1/3/4.
Page 76
Traditional Stacking by Device ICX 7750 stack configuration overview FIGURE 16 ICX 7750 default stacking ports on rear panel The following figure shows an ICX 7750 linear stack. FIGURE 17 ICX 7750 linear stack from rear panel The following figures show ICX 7750 ring stacks from the front and rear panels. Default stacking ports are located on the front panel, but they can be changed to the rear panel using the default-ports command.
Page 77
Traditional Stacking by Device ICX 7750 stack configuration overview FIGURE 18 ICX 7750 ring stack from front panel FIGURE 19 ICX 7750 ring stack from rear panel Ruckus FastIron Stacking Configuration Guide, 08.0.40b Part Number: 53-1003910-11...
Traditional Stacking by Device ICX 7750 stack configuration overview FIGURE 20 ICX 7750 fully populated ring stack from rear panel with three-port stacking trunks Installing the ICX 7750 in a remote stack The ICX 7750-26Q, ICX 7750-48C, and ICX 7750-48F can support stacking distances of 10 kilometers. To achieve maximum stacking distance, these ICX 7750 models must use Brocade LR4 fiber optics.
Page 79
Traditional Stacking by Device ICX 7750 stack configuration overview FIGURE 21 Module 2 front panel stacking ports (ICX 7750-26Q) FIGURE 22 Module 2 front panel stacking ports (ICX 7750-48C) Ruckus FastIron Stacking Configuration Guide, 08.0.40b Part Number: 53-1003910-11...
Page 80
Traditional Stacking by Device ICX 7750 stack configuration overview FIGURE 23 Module 3 rear panel stacking ports (ICX 7750-48C) The following example resets default ports to 1/2/5 and 1/2/6 in preparation for long-distance stacking before stacking is enabled and secure-setup is run. The resulting configuration is displayed as output of the show stack command. ICX7750-20Q Router(config)# stack unit 1 ICX7750-20Q Router(config-unit-1)# default-ports 1/2/5 1/2/6 ICX7750-20Q Router(config-unit-1)# stack enable...
Traditional Stacking by Device ICX 7750 stack configuration overview reason: u2: port-up, , T=9m55.7: Election, was active, no change, ID=1, pri=128, 2U(1-2), A=u1, nbr#=1 1, reason: u2: port-up, , T=9m58.6: reset unit 2: u2 bo-id=1 Debug: Jan 1 00:10:17 Config changed due to add/del units. Do write mem if you want to keep it Debug: Jan 1 00:10:18 T=10m1.6: Unit 1 loses all neighbors.
Traditional Stacking by Device ICX 7750 stack configuration overview • When module 3 on the rear of ICX 7750 devices is used for stacking, before performing secure-setup, change the default ports on the respective units as shown in the following example. Otherwise, the secure-setup utility will not be able to discover the stacking ports in module 3, and invalid stack trunk messages will be displayed.
Page 83
Traditional Stacking by Device ICX 7750 stack configuration overview In the next excerpt, 3 ports are available to form a trunk. You may elect to enter "2" for a two-port trunk or "3" for a full three-port trunk as shown. Confirm Stacking Links...
Page 84
Traditional Stacking by Device ICX 7750 stack configuration overview UPSTREAM Unit: Id new at 4 hop(s) ICX7750-20QXG cc4e.2439.2a80 Enter the desired links(1-3)[1]: 3 UPSTREAM Unit: Id new at 6 hop(s) ICX7750-20QXG cc4e.2439.3880 Enter the desired links(1-3)[1]: 3 UPSTREAM Unit: Id new at 10 hop(s) ICX7750-48XGC cc4e.2439.1d80 Enter the desired links(1-2)[1]: 2 UPSTREAM Unit: Id new at 11 hop(s) ICX7750-48XGC cc4e.2439.1280 Enter the desired links(1-2)[1]: 2...
Page 85
Traditional Stacking by Device ICX 7750 stack configuration overview T=18m56.0: Active U1 deletes U6 and its config because it is learned. T=18m56.1: Active U1 deletes U7 and its config because it is learned. T=18m56.2: Active U1 deletes U8 and its config because it is learned. T=18m56.3: Active U1 deletes U9 and its config because it is learned.
Traditional Stacking by Device ICX 7750 stack configuration overview D ICX7750-20QXG member cc4e.2439.2d00 0 remote Ready D ICX7750-48XGC member cc4e.2439.1a00 0 remote Ready 10 D ICX7750-48XGC member cc4e.2439.1680 0 remote Ready 11 D ICX7750-48XGC member cc4e.2439.1d80 0 remote Ready 12 D ICX7750-48XGC member cc4e.2439.1280 0 remote Ready...
Traditional Stacking by Device ICX 7750 stack configuration overview Converting an ICX 7750 trunk to a port connection in a live stack To remove a trunk and create a port connection on a live stack, use the multi-stack-port command. NOTE Only primary ports (stack module ports 1 and 4) can be designated in the multi-stack-port command.
Traditional Stacking by Device ICX 7750 stack configuration overview In the following example, port 2/2/6, which was previously part of a six-port trunk between stack unit 1 and stack unit 2, is ready to configure as a data port. ICX7750-48F Router(config)# interface ethernet 2/2/6 Error - command not allowed for stacking port: 2/2/6 ICX7750-48F Router(config)# stack unit 1 ICX7750-48F Router(config-unit-1)# multi-stack-trunk 1/2/1 to 1/2/5 and 2/2/1 to 2/2/5...
Page 89
Traditional Stacking by Device ICX 7750 stack configuration overview The following show stack detail output provides information on a 12-unit stack containing three different ICX 7750 models connected in a ring. ICX7750-48F Router# show stack detail alone: standalone, D: dynamic cfg, S: static, A=10, B=11, C=12 Type Role Mac Address...
Page 92
Hitless Stacking Hitless stacking behavior If you install a FastIron 8.0.20 or later image on a new system with no previous configuration, the hitless-failover command is enabled by default. If you upgrade to FastIron release 8.0.20 or later from a previous version that has hitless-failover enabled, hitless-failover is retained as the default.
Hitless Stacking Supported hitless stacking protocols and services Supported hitless stacking events The following events are supported by hitless stacking: • Failover • Switchover • Priority change • Role change Non-supported hitless stacking events The following events are not supported by hitless stacking. These events require a software reload, affecting data traffic. •...
Page 94
• Dos attack prevention • Media Access Control Security (MACsec), 802.1ae, when (TCP syn/ICMP) configured on an ICX 7450 stack, does not support hitless • DHCP snooping stacking because MACsec sessions must be re-established by • Dynamic ARP inspection device firmware.
Hitless Stacking What happens during a hitless stacking switchover or failover TABLE 11 Supported hitless stacking protocols and services (continued) Traffic type Supported protocols and services Impact After a switchover or failover, the new active controller will re-authenticate 802.1X or MAC authentication sessions that were being forwarded in hardware.
Hitless Stacking Standby controller role in hitless stacking When a stack is first booted and becomes operational, baseline synchronization occurs across all of the units in the stack. The active controller copies the current state of its CPU to all units of the stack, including the standby controller. The information received from the active controller is programmed locally in the hardware on all units.
Hitless Stacking Standby controller role in hitless stacking • The runtime configuration on the standby controller is synchronized with the active controller whenever there is a configuration change. • Protocols are configured in the runtime configuration, but no protocol packets are sent out on the standby controller. •...
Hitless Stacking Support during stack formation, stack merge, and stack split Support during stack formation, stack merge, and stack split The following figure illustrates hitless stacking support during stack formation. Operational stages 1 and 2 are also shown. FIGURE 24 Hitless stacking support during stack formation The following figure illustrates hitless stacking support during a stack merge.
Page 99
Hitless Stacking Support during stack formation, stack merge, and stack split FIGURE 25 Hitless stacking support during a stack merge The following figure illustrates hitless stacking support in a stack split. Ruckus FastIron Stacking Configuration Guide, 08.0.40b Part Number: 53-1003910-11...
Hitless Stacking Hitless stacking failover FIGURE 26 Hitless stacking support in a stack split Hitless stacking failover Hitless stacking failover provides automatic failover from the active controller to the standby controller without resetting any of the units in the stack and with sub-second or no packet loss to hitless stacking-supported services and protocols. For a description of the events that occur during a hitless failover, refer to What happens during a hitless stacking switchover or failover page 95.
Hitless Stacking Hitless stacking switchover Syntax: [no] hitless-failover enable Use the no form of the command to disable hitless stacking failover once it has been enabled. Hitless stacking failover example FIGURE 27 Hitless stacking failover when the active controller fails Hitless stacking switchover Hitless stacking switchover is a manually-controlled (CLI-driven) or automatic switchover of the active controller and standby controller without reloading the stack and without any packet loss to the services and protocols that are supported by hitless stacking.
Hitless Stacking Hitless stacking switchover For examples of hitless stacking switchover operation, refer to Hitless stacking switchover examples on page 102. Executing a hitless stacking switchover The following must be in effect before a hitless switchover (to the standby controller) is allowed: •...
Page 103
Hitless Stacking Hitless stacking switchover FIGURE 28 Manual switchover The following figure illustrates a hitless stacking switchover when the active controller goes down and then comes back up. The stack in this example has user-configured priorities. Ruckus FastIron Stacking Configuration Guide, 08.0.40b Part Number: 53-1003910-11...
Page 104
Hitless Stacking Hitless stacking switchover FIGURE 29 Hitless stacking switchover when the active controller comes back up The following figure illustrates a hitless stacking switchover after the network administrator increases the priority value of the standby controller. Ruckus FastIron Stacking Configuration Guide, 08.0.40b Part Number: 53-1003910-11...
Page 105
Hitless Stacking Hitless stacking switchover FIGURE 30 Scenario 1 - Hitless stacking switchover after a priority change The following figure illustrates a hitless stacking switchover after the network administrator increases the priority value of one of the stack members. FIGURE 31 Scenario 2 - Hitless stacking switchover after a priority change The following figure illustrates a hitless stacking switchover after the network administrator increases the priority value for two of the stack members.
Hitless Stacking Displaying information about hitless stacking FIGURE 32 Scenario 3 - Hitless stacking switchover after a priority change Displaying information about hitless stacking Use the show stack command to view information pertinent to a hitless stacking switchover or failover. The command output illustrates the active controller and standby controller, as well as the readiness of the standby controller to take over the role of active controller, if needed.
Hitless Stacking Displaying information about hitless stacking -2/1| 1 |2/4--2/1| 3 |2/4--2/1| 2 |2/4- +---+ +---+ +---+ |-------------------------------------| Standby u2 - protocols ready, can failover Current stack management MAC is 748e.f8f9.6300 Displaying information about stack failover Use the show stack failover command to view information about rapid failover.The show stack failover command provides information on the current standby controller and its status as shown in the following example.
Hitless Stacking Syslog messages for hitless stacking failover and switchover individual_ctrl_dest: 0 status_dest: 2 Syslog messages for hitless stacking failover and switchover Syslog messages are generated for the following events: • Switchover • Failover • Standby controller assignment The following table lists the supported syslog messages for hitless stacking failover and switchover. TABLE 12 Supported syslog messages for hitless stacking faiilover and switchover Message level Message...
Page 109
Hitless Stacking Syslog messages for hitless stacking failover and switchover 0d00h04m08s:I:System: Interface ethernet 1/2/2, state down 0d00h04m06s:I:System: Interface ethernet 8/2/2, state down Ruckus FastIron Stacking Configuration Guide, 08.0.40b Part Number: 53-1003910-11...
Traditional Stack Management • Managing a traditional stack through one IP address.....................111 • Enabling or disabling stacking mode........................111 • Controlling the stack through the CLI........................112 • Configuring default ports on FastIron devices......................115 • Traditional stack management MAC address......................115 •...
Traditional stack unit identification Stack units are identified by numbers 1 though 12 on ICX 7250, ICX 7450, and ICX 7750 devices (1 through 8 on some legacy devices). You can display stack unit IDs by entering the show stack command.
Traditional Stack Management Controlling the stack through the CLI NOTE By default, any user who can open a serial or Telnet connection to the traditional stack can access all of these CLI levels. To secure access, you can configure Enable passwords or local user accounts, or you can configure the active controller to use a RADIUS or TACACS/TACACS+ server for authentication.
Traditional Stack Management Controlling the stack through the CLI Traditional stack CLI commands FastIron Command For more information about a specific traditional stacking command, refer to its command reference page in the Reference . TABLE 13 Traditional stack configuration commands Configuration command Location of command description default-ports...
Traditional Stack Management Traditional stack management MAC address TABLE 15 Traditional stack show commands (continued) Show command Location of command description show stack detail Displaying general or detailed information about stack members on page show stack failover Displaying information about stack failover on page 107 show stack flash Displaying traditional stack flash information...
Traditional Stack Management Traditional stack management MAC address Manually allocating the traditional stack MAC address Beginning with FastIron release 8.0.20, when a stack is enabled, “hitless-failover enable” configuration is added, and a default stack MAC address is assigned if none is configured. The address assigned is the MAC address of the unit as shown in the output of the show stack command.
Traditional Stack Management Traditional stack device roles and elections stack-port 2/2/1 2/2/4 stack enable stack mac 0000.0000.0011 To display the stack MAC address, enter the show chassis command. ICX7450-48F Router# show chassis The stack unit 1 chassis info: Power supply 1 (AC - Regular) present, status ok Model Number: 23-0000144-02 Serial Number:...
Traditional Stack Management Traditional stack device roles and elections The active controller synchronizes its startup configuration with the standby controller and the rest of the stack members. You can recover the previous flash configuration of the standby controller and the stack members by issuing the stack unconfigure command. For an example of this command and the output generated, refer to Unconfiguring a traditional stack on page 134.
Lowest boot stack ID - The unit that has the lowest boot stack ID. Unit ID 1 is the lowest. The unit ID may be 1 through 8 (or 1 through 12 for ICX 7450 or ICX 7750 devices). •...
Traditional Stack Management Traditional stack device roles and elections Standby controller selection based on priority configuration You can choose a standby controller by configuring a stack unit with the second highest priority or with the same priority as the active controller.
Traditional Stack Management Traditional stack unit priority Traditional stack unit priority A unit with a higher priority is more likely to be elected active controller. The priority value can be from 0 through 255, with a priority of 255 being the highest. The default priority value assigned to the active controller and standby controller is 128. You can assign the highest priority value to the stack unit you want to function as the active controller.
Traditional Stack Management Traditional stack software images Changing the priority of a stack unit To change the priority value for a stack unit, enter the priority command at the stack unit configuration level. device# configure terminal device(config)# stack unit 1 device(config-unit-1)# priority 128 Syntax: priority num variable is a value from 0 through 255.
Traditional Stack Management Stack mismatches The active controller generates a log message whenever it puts a stack unit into a non-operational state. The following examples describe the types of mismatches and the related log message: • Advanced feature mismatch - The active controller is enabled for advanced features (such as BGP), and the stack unit is not enabled.
Traditional Stack Management Stack mismatches Major mismatch for stack units A major mismatch indicates an Interprocessor Communications (IPC)-related data structure change, an election algorithm change, or a version of the software that does not support stacking. This can happen when the software undergoes a major change (such as a change from 05.0.00 to 05.1.00).
Traditional Stack Management Stack mismatches Complete the following steps to recover from a configuration mismatch. Enter the show stack command to see the status of the stack, and the show running-config command to see the configurations of the stack units. ICX7750-26Q Router# show stack T=1h38m40.5: alone: standalone, D: dynamic cfg, S: static Type...
Traditional Stack Management Stack mismatches Auto Image Copy for stack units The Auto Image Copy feature ensures that all units in a stack are running the same flash image after a stack merge. This feature also enables automatic reload of the stack units. It prevents the image mismatch that occurs when one or more member units join the stack with a different running image and signature than the active controller and standby controller.
The unit-id-pri and unit-id-sec keywords are used to copy images to a stack member from the active controller primary and secondary unit-num , enter a valid stack unit number from 1 through 8 (1 through 12 for ICX 7450 or ICX 7750 devices).
Traditional Stack Management Configuring stacking trunks in a live environment Displaying multi-trunk stacking configuration The multi-stack-trunk command is used on live stacks and is effectively a combination of two stack-trunk commands to ensure that a trunk-to-trunk connection is created on both ends of a stack link simultaneously. When the multi-stack trunk command is used to create a trunk, the configuration is saved as stack trunk ports, and the running configuration displays the stack trunk details on both ends under the heading stack unit <unit>...
Traditional Stack Management Adding, removing, or replacing units in a traditional stack stack trunk. If you attempt to remove the stack port before removing the stack trunk, an error message similar to the following example is displayed. Please remove stack-trunk 1/2/3 - 1/2/4 using "stack-trunk" or "multi-stack-trunk" command before removing stack port 1/2/3.
Traditional Stack Management Adding, removing, or replacing units in a traditional stack Removing a unit from a traditional stack To remove a unit from the stack, disconnect the cables from the stacking ports. This can be done whether the units are powered on or powered off.
Traditional Stack Management Renumbering stack units NOTE Adding, removing, or replacing a stack unit that is not at the end of a linear topology may cause the other units in the stack to reset if these units lose their path to the active controller during the change. Adding or removing a unit in a ring topology should not cause the other units to reset because each unit can still find a path to the active controller.
Traditional Stack Management Reloading a stack unit 2 S ICX7750-48XGC standby 0000.00d5.2100 remote Ready 3 S ICX7750-48XGC member 0000.005d.9940 remote Ready Configuration notes for renumbering stack units • Renumbering may cause loss of a unit configuration if the stack unit base module does not match the configuration on the active controller.
Traditional Stack Management Merging traditional stacks unit-list variable can be a single ID, a list of IDs, a range of IDs, or a • unit-id - Designates stack member or members to reload. The combination, such as 2,4-6,8. Values must be separated by a comma, with no space. If you need to reload the active controller, use the stack switch-over command.
Traditional Stack Management Unconfiguring a traditional stack Unconfiguring a traditional stack The stack unconfigure command is a runtime command that returns stack units to their pre-stacking state. When a stack unit is unconfigured, its stacking flash is removed, and its startup-config.txt flash file is recovered. These actions apply to all units to which this command is applied, regardless of the role of the unit in the stack.
Traditional Stack Management Displaying traditional stack information Syslog, SNMP, and traps for stack units Syslog messages from stack units are forwarded to, and can be viewed from, the active controller. All stack units support SNMP gets, sets, and traps, which are managed by the active controller. An SNMP trap is sent from a stack unit to the stack active controller and forwarded from the active controller to an SNMP-configured server.
Traditional Stack Management Displaying traditional stack information Displaying stacking topology The show stack connection command displays the topology and a detailed connection report. It also displays connection errors or hardware failures as shown in the following sample output. ICX7750-48F Router# show stack connection Probing the topology.
Traditional Stack Management Displaying traditional stack information ver 08.0.30aT203 stack unit 1 module 1 icx7750-48-xgc-port-management-module module 2 icx7750-qsfp-6port-qsfp-240g-module stack-trunk 1/2/4 to 1/2/6 stack-port 1/2/1 1/2/4 stack unit 2 module 1 icx7750-48-xgc-port-management-module module 2 icx7750-qsfp-6port-qsfp-240g-module stack-trunk 2/2/4 to 2/2/6 stack-port 2/2/1 2/2/4 stack enable stack mac cc4e.2439.1680 ip dns domain-list englab.brocade.com...
Traditional Stack Management Displaying traditional stack information 2. When stacking is not enabled, neither stacking port is displayed. stack unit 1 module 1 icx7750-48-xgc-port-management-module module 2 icx7750-qsfp-6port-qsfp-240g-module 3. If one stacking port is configured, that port is displayed, whether or not stacking is enabled. stack unit 1 module 1 icx7750-48-xgc-port-management-module module 2 icx7750-qsfp-6port-qsfp-240g-module...
Traditional Stack Management Displaying traditional stack information STACKID 1 system uptime is 2 minute(s) 29 second(s) STACKID 2 system uptime is 1 minute(s) 26 second(s) STACKID 3 system uptime is 2 minute(s) 41 second(s) The system : started=warm start reloaded=by "reload" My stack unit ID = 1, bootup role = active unit-num command displays the software version running on an individual unit.
Traditional Stack Management Displaying traditional stack information Compressed Pri Code size = 20197181, Version:08.0.40T203 (SWR08040b1.bin) Compressed Sec Code size = 20194299, Version:08.0.40T203 (SWR08040.bin) Compressed Boot-Monitor Image size = 1835008, Version:10.1.03T205 Code Flash Free Space = 838475776 TABLE 18 Field definitions for the show flash command Field Description Compressed Pri Code size...
Page 141
Traditional Stack Management Displaying traditional stack information Fan speed switching temperature thresholds: Speed 1: NM<----->58 deg-C Speed 2: 50<-----> 82 deg-C (shutdown) Fan 1 Air Flow Direction: Front to Back Fan 2 Air Flow Direction: Front to Back Fan 3 Air Flow Direction: Front to Back Fan 4 Air Flow Direction: Front to Back...
Traditional Stack Management Displaying traditional stack information Displaying stack module information The show module command displays information about stack unit modules. Output resembles the following. ICX7750-26Q Router# show module Module Status Ports Starting MAC U1:M1 ICX7750-20QXG 20-port Management Module 748e.f8f9.6300 U1:M2 ICX7750-QSFP 6-port QSFP 240G Module 748e.f8f9.6315...
Page 143
Traditional Stack Management Displaying traditional stack information D ICX7750-20QXG member cc4e.2438.7280 0 remote Ready ICX7750-26Q Router# show stack 3 T=12m20.6: alone: standalone, D: dynamic cfg, S: static Type Role Mac Address Pri State Comment D ICX7750-20QXG standby cc4e.2438.7500 0 remote Ready If you add the detail keyword to the show stack command, output resembles the following example.
Traditional Stack Management Displaying traditional stack information NOTE The active controller removes the dynamic configuration of a unit when the unit leaves the stack. However, if there is a static trunk configuration associated with the unit, the active controller cannot remove the dynamic configuration. In this case, you must remove the static trunk and use the no stack unit stack-unit command to manually remove the configuration.
Traditional Stack Management Displaying traditional stack information Displaying reliable IPC statistics for stack units Use the show stack rel-ipc stats command to display session statistics for stack units. The following example shows reliable IPC statistics for stack unit 3. ICX7750-26Q Router# show stack rel-ipc stats unit 3 Unit 3 statistics: Msgs: sent 907 recv 384, Pkt sends failed: 0, KA: sent 1522 recv 1522...
Traditional Stack Management Displaying traditional stack information up (1/2/1-1/2/2) up (1/2/4-1/2/6) up ports: 1/2/1 up ports: 1/2/4 up (2/2/1) up (2/2/4-2/2/5) up ports: 2/2/4 up (3/2/1-3/2/3) up (3/2/4) up ports: 3/2/1 Syntax: show stack stack-ports TABLE 25 Field descriptions for the show stack stack-ports command Field Description The stack identification number for this unit...
Traditional Stack Management MIB support for traditional stack configurations Port Link State Dupl Speed Trunk Tag Pvid Pri MAC Name 1/2/1 Forward Full 40G None 748e.f8f9.6315 1/2/2 Down None None None None 748e.f8f9.6319 1/2/4 Forward Full 40G None 748e.f8f9.6321 1/2/5 Down None None None...
Traditional Stack Troubleshooting Troubleshooting an unsuccessful stack build NOTE Periodic background stack diagnosis is performed every minute. When you manually trigger stack diagnosis, the system may print the following message: There is a trunk probe going on. Please try later. Suppressing background stack diagnostic warnings You can control the automatic background stacking diagnosis that runs periodically when stacking is enabled.
Page 151
Traditional Stack Troubleshooting Troubleshooting an unsuccessful stack build Use the show stack ipc command to see if any traffic has been sent or received. Enter clear stack ipc to clear the traffic statistics and then enter show stack ipc again so you can easily see differences in traffic flow. ICX7750-26Q Router# show stack ipc V80, G4, src=748e.f8f9.6300, max_pkt_size=10264, delay_buf=10264 Recv: SkP0: 13788, P1: 16488, sum: 30276, since t=3028.1 ago...
Traditional Stack Troubleshooting Troubleshooting secure-setup If you run out of flash memory while performing a write memory, your stack devices may contain very large startup-config.v4 or startup-config.old files, which are preserved for recovery purposes. Enter the show dir command at the privileged EXEC level to see all flash files.
• The number of units in your stack does not exceed the maximum allowed (12 units for ICX 7250, ICX 7450, and ICX 7750 stacks). • The replacement unit is a clean unit (does not contain a startup-config.txt file).
Traditional Stack Troubleshooting Troubleshooting image copy issues To verify installed image files, enter the show_image command at the boot prompt as shown in the following example. ICX7450-Boot> show_image =========================== Primary : SPS08030b(28590276) Secondary: SPR08030b(31547588) To reset hardware and memory, enter the powercycle command at the boot prompt. This causes the system to execute a cold boot as shown in the following example.
Traditional Stack Troubleshooting Port down and aging Whenever a stack unit configuration parameter, such as the priority setting, is changed, an election is held to determine the active controller, and the result is written into the stacking.boot file. A prompt message appears on the console that recommends you use the write memory command.